From mailnull@www1.ietf.org  Mon Mar  3 03:52:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12133
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 03:52:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2392Ko25033
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 04:02:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2392Kp25030
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 04:02:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12116
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 03:51:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2391Jp24679;
	Mon, 3 Mar 2003 04:01:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h238xLp24541
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 03:59:21 -0500
Received: from sj-msg-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12057
	for <sipping@ietf.org>; Mon, 3 Mar 2003 03:48:56 -0500 (EST)
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.6) with ESMTP id h238ocHK027882;
	Mon, 3 Mar 2003 00:50:38 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id AEP88933;
	Mon, 3 Mar 2003 00:45:48 -0800 (PST)
Date: Mon, 3 Mar 2003 09:51:10 +0100
Subject: Re: [Sipping] I-D ACTION:draft-ietf-sipping-connect-reuse-reqs-00.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: "sipping@ietf.org" <sipping@ietf.org>
To: y01317@njupt.edu.cn
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <200211121200.gACC03UJ001521@proxy1.cisco.com>
Message-Id: <47FD61D8-4D55-11D7-92B0-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, November 12, 2002, at 01:03 PM, feng zhang wrote:

> Hi Rohan,
>
>    in lines.....
>> On Monday, November 11, 2002, at 07:11 AM, feng zhang wrote:
>>
>>> Another problem:
>>>
>>>   If using the reuse mechanism metioned in this draft, it will be 
>>> like
>>> this:
>>>
>>> 		  +-----------+                        +-----------+
>>>           |           |                        |           |
>>>           |   Node A  | 8293              5061 |   Node B  |
>>>           |           |<======================>|           |
>>>           |           |                        |           |
>>>           +-----------+                        +-----------+
>>>               UAC                                   UAS
>              Does Node A have to listen on port 8293 ?  If Node A only 
> listens on port 5061, what will happen? A can not receive B's 
> requests, right?

Node A has to listen on port 5061 (for new connections), AND has to be 
willing to receive new requests over an existing connection which 
happens to be on port 8293.  Once this connection drops however it does 
not need to continue listening on port 8293.

hope this helps.
thanks,
-rohan


>>>
>>>   Here , quote section 3:
>>>
>>>     " 3.  A connection sharing mechanism MUST NOT require UACs
>>> (clients) to
>>>        send all traffic from well-know SIP ports."
>>>                         ~~~~~
>>>                           from? I think it's "to"
>>>
>>>   I think the UAC DOES NOT send any traffic on well-known  SIP ports,
>>> why here is this requirment?
>>
>>
>> Node A in this example initiates its connections *from* an ephemeral
>> port (port 8293).  I assert that it is a requirement that Nodes can
>> continue to initiate new connections *from* ports other than 
>> well-known
>> ports, and still take advantage of connection sharing.
>>
>> thanks,
>> -rohan
>>
>>>   Maybe I am wrong, please clarify me.
>>>
>>>> Hello all,
>>>>
>>>>  I think the example in section 4. Overview of Proposed Mechanism is
>>>> bad.
>>>>
>>>>  quote section 4:
>>>>
>>>>     Assuming the Via header field value shown below from the most
>>>> recent
>>>>     request arrived over a connection from 60.54.32.1 port 8241:
>>>>
>>>>
>>>>      Via: SIP/2.0/TLS 60.54.32.1:5061;branch=z9hG4bKa7c8dze ;alias
>>>>
>>>>      The transport layer would create an alias in order to get to:
>>>>
>>>>      60.54.32.1:5061  send on->  connection with 60.54.32.1:8241
>>>>
>>>>  I do not understand why using the SAME IP address ?
>>>>
>>>>  We can use IP address 10.10.1.1:8241(IP:port) for UAC and
>>>> 60.54.32.1:5061(IP/port) for UAS in the example, right?
>>>>
>>>>  Best regards.
>>>>
>>>>
>>>> _______________________________________________
>>>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>> This list is for NEW development of the application of SIP
>>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>>> Use sip@ietf.org for new developments of core SIP
>>>>
>>>> .
>>> _______________________________________________
>>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>> This list is for NEW development of the application of SIP
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sip@ietf.org for new developments of core SIP
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sip@ietf.org for new developments of core SIP
>>
>> .

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 07:57:22 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22308
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 07:57:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23D7LK14598
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 08:07:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23D7Lp14589
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 08:07:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22252
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 07:56:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23D6Zp13958;
	Mon, 3 Mar 2003 08:06:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23D5pp13919
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 08:05:51 -0500
Received: from mgw-x4.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22151
	for <sipping@ietf.org>; Mon, 3 Mar 2003 07:55:21 -0500 (EST)
From: hisham.khartabil@nokia.com
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h23D0bZ26269
	for <sipping@ietf.org>; Mon, 3 Mar 2003 15:00:37 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60c0cbc933ac158f23077@esvir03nok.nokia.com>;
 Mon, 3 Mar 2003 14:57:21 +0200
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 3 Mar 2003 14:57:21 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Date: Mon, 3 Mar 2003 14:57:20 +0200
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7FE72F5@esebe019.ntc.nokia.com>
Thread-Topic: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Thread-Index: AcLfOU1Ftwn+VPZaRkGrv0M9J9bRKwCSsBsA
To: <jh@lohi.eng.song.fi>, <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: <BeckW@t-systems.com>, <sipping@ietf.org>, <stu.jacobs@labs.gte.com>,
        <mankin@psg.com>, <Jari.Arkko@lmf.ericsson.se>
X-OriginalArrivalTime: 03 Mar 2003 12:57:21.0037 (UTC) FILETIME=[6D9773D0:01C2E184]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h23D5pp13920
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

A server knows what realm to use for a certain interface (it can do its own mapping). It cannot rely of a UA telling it the realm.

There has to be some agreements and trust between networks in order for calls to complete. You cannot make a call from Sonera to Radiolinja (both Finnish operators) without both having trust relationships (or any relationship for that matter).

Regards,
Hisham

> -----Original Message-----
> From: ext jh@lohi.eng.song.fi [mailto:jh@lohi.eng.song.fi]
> Sent: Friday, February 28, 2003 3:45 PM
> To: Gonzalo Camarillo
> Cc: Beck01, Wolfgang; sipping@ietf.org; stu.jacobs@labs.gte.com;
> mankin@psg.com; Jari Arkko
> Subject: Re: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
> 
> 
> Gonzalo Camarillo writes:
> 
>  > You can change the contents of the From field. No problem. 
> In fact, one
>  > of the reasons we removed the To and From URIs from the dialog
>  > identifiers (only the tags remain) was to address this type of
>  > situation.
> 
> currently your text says:
> 
> The From URI of the request MUST be set to the local URI from 
> the dialog
> state.
> 
> ...
> 
> It is expected that mandatory reflection of the original To 
> and From URI
> in mid-dialog requests will be deprecated in a subsequent revision of
> this specification.
> 
> so before that is done and the text is changed so that the 
> from uri MUST
> be the from uri of the user sending the request, there can't be any
> challenging or accounting of requests within the dialog.
> 
> alternatively, we must add another header or field to the request that
> tells what realm the ua sending the request claims to belong to.
> 
> for example, take a look at eap/tls.  there the user has a 
> means to tell
> what realm he/she wants to authenticate with.  currently we 
> are lacking
> this possibility in sip, which is a major shortcoming.
> 
> -- juha
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 08:00:50 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22538
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 08:00:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23DAma14988
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 08:10:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23DAmp14985
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 08:10:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22532
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 08:00:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23DA5p14945;
	Mon, 3 Mar 2003 08:10:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23D9Xp14886
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 08:09:33 -0500
Received: from lohi.eng.song.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22480
	for <sipping@ietf.org>; Mon, 3 Mar 2003 07:59:04 -0500 (EST)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.36 #1 (Debian))
	id 18ppYz-0001Ti-00; Mon, 03 Mar 2003 15:01:01 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15971.21004.851283.381953@harjus.eng.song.fi>
Date: Mon, 3 Mar 2003 15:01:00 +0200
To: <hisham.khartabil@nokia.com>
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <stu.jacobs@labs.gte.com>, <mankin@psg.com>,
        <Jari.Arkko@lmf.ericsson.se>
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
In-Reply-To: <2038BCC78B1AD641891A0D1AE133DBB7FE72F5@esebe019.ntc.nokia.com>
References: <2038BCC78B1AD641891A0D1AE133DBB7FE72F5@esebe019.ntc.nokia.com>
X-Mailer: VM 7.07 under Emacs 21.2.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

hisham.khartabil@nokia.com writes:

 > A server knows what realm to use for a certain interface (it can do
 > its own mapping). It cannot rely of a UA telling it the realm.

what interface?  my sip proxy has a single ethernet ip interface and
supports simultaneously any number of realms.  

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 08:23:09 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24021
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 08:23:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23DX8B16280
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 08:33:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23DX8p16277
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 08:33:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23982
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 08:22:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23DWRp16158;
	Mon, 3 Mar 2003 08:32:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23DVup16126
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 08:31:56 -0500
Received: from mgw-x3.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23764
	for <sipping@ietf.org>; Mon, 3 Mar 2003 08:21:25 -0500 (EST)
From: aki.niemi@nokia.com
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x3.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h23DNPD04739
	for <sipping@ietf.org>; Mon, 3 Mar 2003 15:23:25 +0200 (EET)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60c0e39f30ac158f23077@esvir03nok.nokia.com>;
 Mon, 3 Mar 2003 15:23:23 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 3 Mar 2003 15:23:22 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Date: Mon, 3 Mar 2003 15:23:22 +0200
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD90194518E@esebe013.ntc.nokia.com>
Thread-Topic: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Thread-Index: AcLfH/fYaiqoEeR3RBu6sROvw+f4LQCZtOeg
To: <jh@lohi.eng.song.fi>, <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: <BeckW@t-systems.com>, <sipping@ietf.org>, <Jari.Arkko@lmf.ericsson.se>
X-OriginalArrivalTime: 03 Mar 2003 13:23:22.0669 (UTC) FILETIME=[106595D0:01C2E188]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h23DVup16127
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

Inline.

 > -----Original Message-----
 > From: ext jh@lohi.eng.song.fi [mailto:jh@lohi.eng.song.fi]
 > Sent: 28 February, 2003 13:44
 > To: Gonzalo Camarillo
 > Cc: Beck01, Wolfgang; sipping@ietf.org; stu.jacobs@labs.gte.com;
 > mankin@psg.com; Jari Arkko
 > Subject: Re: [Sip] Re: [Sipping] New version of the SIP-AAA 
 > reqs draft
 > 
 > 
 > Gonzalo Camarillo writes:
 > 
 >  > Here you have a figure of the scenario you have just described:
 >  > 
 >  >                        alice.com   . . .   bob.com
 >  >                  .       proxy              proxy     .
 >  >                .                                       .
 >  >          Alice  . . . . . . . . . . . . . . . . . . . .  Bob
 >  >       
 >  > We have an INVITE from alice@alice.com to bob@bob.com
 > 
 > no, originally, we have an invite from alice@alice.com to
 > 33983900@sip.song.fi that gets translated by enum to bob@bob.com.

Ok, so the only proxy in this case that can authenticate this INVITE is alice.com. If you don't have inter-domain AAA, that's the only proxy that alice has credentials with. Unless of course anonymous authentication is an option?

 >  > 
 >  > Now, you have a BYE from Bob to Alice. In your scenario, 
 > which proxy is
 >  > doing accounting, alice.com or bob.com?
 > 
 > both proxies account both placed and received calls of their 
 > own users.

I don't know why bob.com would want to authenticate bob's BYE, when it didn't have the tools to authenticate the original INVITE from alice? In other words, why would you accept accounting the unauthenticated INVITE, but not the BYE?

Cheers,
Aki

 > -- juha
 > 
 > _______________________________________________
 > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
 > This list is for NEW development of the application of SIP
 > Use sip-implementors@cs.columbia.edu for questions on current sip
 > Use sip@ietf.org for new developments of core SIP
 > 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 08:27:59 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24399
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 08:27:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23Dbwp17369
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 08:37:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23Dbwp17366
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 08:37:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24322
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 08:27:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23DbNp17092;
	Mon, 3 Mar 2003 08:37:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23Dahp16454
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 08:36:43 -0500
Received: from mgw-x1.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24251
	for <sipping@ietf.org>; Mon, 3 Mar 2003 08:26:11 -0500 (EST)
From: hisham.khartabil@nokia.com
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h23DQto05701
	for <sipping@ietf.org>; Mon, 3 Mar 2003 15:26:55 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60c0e80621ac158f2506f@esvir05nok.ntc.nokia.com>;
 Mon, 3 Mar 2003 15:28:11 +0200
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 3 Mar 2003 15:28:10 +0200
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 3 Mar 2003 15:28:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Date: Mon, 3 Mar 2003 15:28:10 +0200
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7FE72F7@esebe019.ntc.nokia.com>
Thread-Topic: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Thread-Index: AcLhhQLec7sQORcmQuyjri21Hu+/VwAAU2EQ
To: <jh@lohi.eng.song.fi>
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <stu.jacobs@labs.gte.com>, <mankin@psg.com>,
        <Jari.Arkko@lmf.ericsson.se>
X-OriginalArrivalTime: 03 Mar 2003 13:28:10.0491 (UTC) FILETIME=[BBF3BCB0:01C2E188]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h23Dahp16455
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Can the proxy challenge with all its realms? I really don't believe you can trust the UA supplying the realm it belongs to.

Regards,
Hisham

> -----Original Message-----
> From: ext jh@lohi.eng.song.fi [mailto:jh@lohi.eng.song.fi]
> Sent: Monday, March 03, 2003 3:01 PM
> To: Khartabil Hisham (NMP/Helsinki)
> Cc: Gonzalo.Camarillo@lmf.ericsson.se; BeckW@t-systems.com;
> sipping@ietf.org; stu.jacobs@labs.gte.com; mankin@psg.com;
> Jari.Arkko@lmf.ericsson.se
> Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
> 
> 
> hisham.khartabil@nokia.com writes:
> 
>  > A server knows what realm to use for a certain interface (it can do
>  > its own mapping). It cannot rely of a UA telling it the realm.
> 
> what interface?  my sip proxy has a single ethernet ip interface and
> supports simultaneously any number of realms.  
> 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 08:44:10 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25066
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 08:44:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23DsA718157
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 08:54:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23DsAp18154
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 08:54:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25057
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 08:43:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23DrAp18123;
	Mon, 3 Mar 2003 08:53:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1S82Wp05231
	for <sipping@optimus.ietf.org>; Fri, 28 Feb 2003 03:02:32 -0500
Received: from postkutsche.sys.uta.at (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16647
	for <sipping@ietf.org>; Fri, 28 Feb 2003 02:51:37 -0500 (EST)
Received: from atmailinet01.utalan.at (smtpmail.utalan.at [172.21.16.17])
	by postkutsche.sys.uta.at (8.12.6/8.12.6) with ESMTP id h1S7t61I016462;
	Fri, 28 Feb 2003 08:55:07 +0100
Received: by atmailinet01.utalan.at with Internet Mail Service (5.5.2653.19)
	id <16LG8NGH>; Fri, 28 Feb 2003 08:55:06 +0100
Message-ID: <239174FF942BD511B3C40080C8945C1A04FEFA67@atmail02.utalan.at>
From: Edler Franz <franz.edler@uta.at>
To: "'Eric Tremblay'" <etremblay@mediatrix.com>,
        Henry Sinnreich
	 <Henry.Sinnreich@wcom.com>,
        =?iso-8859-1?Q?J=F6rgen_Bj=F6rkner?=
	 <jorgen.bjorkner@hotsip.com>,
        sipforum-discussion@lists.su.se
Cc: sipping@ietf.org
Date: Fri, 28 Feb 2003 08:55:06 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1S82Wp05232
Subject: [Sipping] AW: [Sipforum-discussion] SIP Telephony Device Requirements, Conf
 iguration and Data
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi folks,

just a comment on SIP-25:

I am currently working on a PSTN - SIP migration concept avoiding to
re-invent all fancy features of the PSTN and in particular to re-implement
all legal/regulatory requirements (emergency call handling, legal
intercept). The concept builds upon a "dual homed" SIP-UA with one "line"
connected to the PSTN via V5 - SIP gateway and the other "lines" beeing free
for all new services of the SIP world. Therefore the requirement of multiple
identities on the SIP side and a static identitiy on the PSTN side is
essential, but I agree, if you are focused on analog adapters only, this
would mean an unnecessary burden. But I suggest to re-think the migration
perspective.

By the way, if anyone is interested in this "dual-homed" PSTN - SIP
migration concept let me know. I am convienced that this means a good chance
for a carrier to migrate towards SIP without heavy investments in
re-inventing what is already existing.

kind regards
Franz

---------------------------------------------------------------
Franz Edler
Strategy & Business Development

UTA Telekom AG
Donau-City-Strasse 11
A-1220 Wien
T: + 43/1/9009-3310
F: + 43/1/9009-93310
M: + 43/699/1388 3310
mailto:franz.edler@uta.at
http://www.uta.at
--------------------------------------------------------------

> -----Ursprüngliche Nachricht-----
> Von:	Eric Tremblay [SMTP:etremblay@mediatrix.com]
> Gesendet am:	Mittwoch, 26. Februar 2003 17:41
> An:	Henry Sinnreich; Jörgen Björkner; sipforum-discussion@lists.su.se
> Cc:	sipping@ietf.org
> Betreff:	RE: [Sipforum-discussion] SIP Telephony Device Requirements,
> Configuration and Data
> 
> Hi Henry, 
> 
> Here is a somewhat lengthy email with a few comments about the SIP
> Telephony Device Requirements draft: 
> 
> 
>   SIP-25, Dynamic login/logout for user mobility: SIP devices MUST 
>   support user mobility.  SIP clients MUST store a static profile in 
>   non-volatile memory so that this information is available during the 
>   power up sequence.  SIP clients MUST allow a user to walk up to a 
>   client, login, and be able to send and receive calls with his profile 
>   information. 
>   For emergency numbers (e.g. 911) the client MUST send the credentials 
>   (username/password) of the static profile. 
> 
> [EricT] 
> We are developing analog adapters and don't remember receiving such a
> request. I suggest either changing the MUST to SHOULD or adding some text
> to specify that it is a MUST for devices with the proper interface to do
> it and a SHOULD for devices with a limited interface. I know we could
> possibly configure this through a web interface, but the point is that
> there are a lot of vendore that currently just want to replace the wire,
> not the phone and its interface...
> 
> 
> 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 08:55:52 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25727
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 08:55:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23E5qY18710
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 09:05:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23E5qp18707
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 09:05:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25719
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 08:55:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23E5Dp18684;
	Mon, 3 Mar 2003 09:05:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23E4Rp18642
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 09:04:27 -0500
Received: from mail2.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25538;
	Mon, 3 Mar 2003 08:53:44 -0500 (EST)
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail2.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id h23DroDI001579;
	Mon, 3 Mar 2003 08:53:50 -0500 (EST)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <FFZFWXJW>; Mon, 3 Mar 2003 07:55:45 -0600
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3A64532@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Internet-Drafts@ietf.org'" <Internet-Drafts@ietf.org>
Cc: sipping@ietf.org
Subject: RE: [Sipping] I-D ACTION:draft-kotar-sipping-dss1-sip-iw-00.txt
Date: Mon, 3 Mar 2003 07:55:44 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

    "Annex A Cause Mapping between DSS1 and SIP 

     "A.1 Mapping between DSS1 causes and SIP 4xx-6xx response"

Out of curiosity, how many times are we, as a working group,
planning to go through the excercise of mapping Q.850 cause codes
to and from SIP response codes?

I strongly suggest that this work reference RFC 3398.

/a
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 09:58:25 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27787
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 09:58:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23F8QN24521
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 10:08:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23F8Qp24518
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 10:08:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27764
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 09:57:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23F7cp24434;
	Mon, 3 Mar 2003 10:07:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23F6ap23571
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 10:06:36 -0500
Received: from rautu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27657
	for <sipping@ietf.org>; Mon, 3 Mar 2003 09:55:58 -0500 (EST)
Received: from jh by rautu with local (Exim 3.35 #1 (Debian))
	id 18ptF4-0000GT-00; Mon, 03 Mar 2003 18:56:42 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15971.35145.991375.141646@lohi.eng.song.fi>
Date: Mon, 3 Mar 2003 18:56:41 +0200
To: <hisham.khartabil@nokia.com>
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <stu.jacobs@labs.gte.com>, <mankin@psg.com>,
        <Jari.Arkko@lmf.ericsson.se>
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
In-Reply-To: <2038BCC78B1AD641891A0D1AE133DBB7FE72F7@esebe019.ntc.nokia.com>
References: <2038BCC78B1AD641891A0D1AE133DBB7FE72F7@esebe019.ntc.nokia.com>
X-Mailer: VM 7.07 under Emacs 21.2.1
From: Juha Heinanen <jh@lohi.eng.song.fi>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

hisham.khartabil@nokia.com writes:

 > Can the proxy challenge with all its realms? I really don't believe
 > you can trust the UA supplying the realm it belongs to.

of course it can, since in order for the authentication to succeed, the
user must have a user name and password that is valid in the realm the user
claims to belong to.  check the digest or eap/ttls specs.

-- juha
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 10:02:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27937
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 10:02:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23FCge24727
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 10:12:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FCgp24724
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 10:12:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27906
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 10:02:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FC7p24674;
	Mon, 3 Mar 2003 10:12:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FBLp24623
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 10:11:21 -0500
Received: from lohi.eng.song.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27845
	for <sipping@ietf.org>; Mon, 3 Mar 2003 10:00:48 -0500 (EST)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.36 #1 (Debian))
	id 18prSq-0001aO-00; Mon, 03 Mar 2003 17:02:48 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15971.28311.844494.67383@harjus.eng.song.fi>
Date: Mon, 3 Mar 2003 17:02:47 +0200
To: <aki.niemi@nokia.com>
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <Jari.Arkko@lmf.ericsson.se>
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
In-Reply-To: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD90194518E@esebe013.ntc.nokia.com>
References: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD90194518E@esebe013.ntc.nokia.com>
X-Mailer: VM 7.07 under Emacs 21.2.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

aki.niemi@nokia.com writes:

 > Ok, so the only proxy in this case that can authenticate this INVITE
 > is alice.com. If you don't have inter-domain AAA, that's the only
 > proxy that alice has credentials with. Unless of course anonymous
 > authentication is an option? 

yes, the idea should be that each proxy authenticates requests that are
send by useres directly connected to them.  proxies then can trust each
other as you suggest.

the problem is that the proxy of the user sending bye, can't
authenticate the user sending it, because there is no way for the proxy
to figure out the realm of that user.  this is a big shortcoming in
current sip.

-- juha

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 10:06:50 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28357
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 10:06:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23FGqb25002
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 10:16:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FGqp24999
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 10:16:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28296
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 10:06:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FG9p24950;
	Mon, 3 Mar 2003 10:16:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FF7p24882
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 10:15:07 -0500
Received: from mgw-x4.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28127
	for <sipping@ietf.org>; Mon, 3 Mar 2003 10:04:34 -0500 (EST)
From: hisham.khartabil@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h23F9pY08648
	for <sipping@ietf.org>; Mon, 3 Mar 2003 17:09:51 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60c141f2f9ac158f24077@esvir04nok.ntc.nokia.com>;
 Mon, 3 Mar 2003 17:06:25 +0200
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 3 Mar 2003 17:06:24 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Date: Mon, 3 Mar 2003 17:06:24 +0200
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7FE72FF@esebe019.ntc.nokia.com>
Thread-Topic: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Thread-Index: AcLhlTHISJfaOUOPRxe+g4pRuGtm/AAAPWcw
To: <jh@lohi.eng.song.fi>
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <stu.jacobs@labs.gte.com>, <mankin@psg.com>,
        <Jari.Arkko@lmf.ericsson.se>
X-OriginalArrivalTime: 03 Mar 2003 15:06:24.0990 (UTC) FILETIME=[7558E7E0:01C2E196]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h23FF7p24883
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

I was offering a solution to your problem in the form of a question. Here it is again in the form of a suggestion:

If your poxy supports multiple realms on the same interface, then it can challenge with all the realms and therefore the UA does not have to supply the realm to the proxy.

Regards,
Hisham

> -----Original Message-----
> From: ext Juha Heinanen [mailto:jh@lohi.eng.song.fi]
> Sent: Monday, March 03, 2003 6:57 PM
> To: Khartabil Hisham (NMP/Helsinki)
> Cc: Gonzalo.Camarillo@lmf.ericsson.se; BeckW@t-systems.com;
> sipping@ietf.org; stu.jacobs@labs.gte.com; mankin@psg.com;
> Jari.Arkko@lmf.ericsson.se
> Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
> 
> 
> hisham.khartabil@nokia.com writes:
> 
>  > Can the proxy challenge with all its realms? I really don't believe
>  > you can trust the UA supplying the realm it belongs to.
> 
> of course it can, since in order for the authentication to 
> succeed, the
> user must have a user name and password that is valid in the 
> realm the user
> claims to belong to.  check the digest or eap/ttls specs.
> 
> -- juha
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 10:15:57 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29095
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 10:15:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23FPxx25586
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 10:25:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FPxp25583
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 10:25:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29083
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 10:15:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FPCp25544;
	Mon, 3 Mar 2003 10:25:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FOtp25468
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 10:24:55 -0500
Received: from lohi.eng.song.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28970
	for <sipping@ietf.org>; Mon, 3 Mar 2003 10:14:22 -0500 (EST)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.36 #1 (Debian))
	id 18prfy-0001bF-00; Mon, 03 Mar 2003 17:16:22 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15971.29126.48684.490203@harjus.eng.song.fi>
Date: Mon, 3 Mar 2003 17:16:22 +0200
To: <hisham.khartabil@nokia.com>
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <stu.jacobs@labs.gte.com>, <mankin@psg.com>,
        <Jari.Arkko@lmf.ericsson.se>
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
In-Reply-To: <2038BCC78B1AD641891A0D1AE133DBB7FE72FF@esebe019.ntc.nokia.com>
References: <2038BCC78B1AD641891A0D1AE133DBB7FE72FF@esebe019.ntc.nokia.com>
X-Mailer: VM 7.07 under Emacs 21.2.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

hisham.khartabil@nokia.com writes:

 > I was offering a solution to your problem in the form of a
 > question. Here it is again in the form of a suggestion:
 > 
 > If your poxy supports multiple realms on the same interface, then it
 > can challenge with all the realms and therefore the UA does not have
 > to supply the realm to the proxy.

if i understod your suggestion correctly, it makes no sense. an 
operator proxy can easily have several hundred realms configured in it.
are you suggesting sending several hundred 407s for each bye?

-- juha

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 10:22:58 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29333
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 10:22:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23FX0n26104
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 10:33:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FX0p26101
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 10:33:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29320
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 10:22:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FWCp26037;
	Mon, 3 Mar 2003 10:32:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FVTp25978
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 10:31:29 -0500
Received: from mgw-x4.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29259
	for <sipping@ietf.org>; Mon, 3 Mar 2003 10:20:54 -0500 (EST)
From: hisham.khartabil@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h23FQBY18917
	for <sipping@ietf.org>; Mon, 3 Mar 2003 17:26:11 +0200 (EET)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60c1510e48ac158f24077@esvir04nok.ntc.nokia.com>;
 Mon, 3 Mar 2003 17:22:55 +0200
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 3 Mar 2003 17:22:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Date: Mon, 3 Mar 2003 17:22:54 +0200
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7FE7300@esebe019.ntc.nokia.com>
Thread-Topic: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Thread-Index: AcLhl9ybUwZcpBf0Qgmg+DBKVbfb/AAAC/Sg
To: <jh@lohi.eng.song.fi>
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <stu.jacobs@labs.gte.com>, <mankin@psg.com>,
        <Jari.Arkko@lmf.ericsson.se>
X-OriginalArrivalTime: 03 Mar 2003 15:22:54.0428 (UTC) FILETIME=[C31929C0:01C2E198]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h23FVTp25981
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

I think you exaggerating here with several hundreds, but anyway, I was suggesting several hundreds of proxy-authenticate headers. Of course you can scale your network to be better than that. I'm trying to find a solution that doesn't rely on the UA to send its realm (You haven't objected to that yet).

/Hisham

> -----Original Message-----
> From: ext jh@lohi.eng.song.fi [mailto:jh@lohi.eng.song.fi]
> Sent: Monday, March 03, 2003 5:16 PM
> To: Khartabil Hisham (NMP/Helsinki)
> Cc: Gonzalo.Camarillo@lmf.ericsson.se; BeckW@t-systems.com;
> sipping@ietf.org; stu.jacobs@labs.gte.com; mankin@psg.com;
> Jari.Arkko@lmf.ericsson.se
> Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
> 
> 
> hisham.khartabil@nokia.com writes:
> 
>  > I was offering a solution to your problem in the form of a
>  > question. Here it is again in the form of a suggestion:
>  > 
>  > If your poxy supports multiple realms on the same 
> interface, then it
>  > can challenge with all the realms and therefore the UA 
> does not have
>  > to supply the realm to the proxy.
> 
> if i understod your suggestion correctly, it makes no sense. an 
> operator proxy can easily have several hundred realms 
> configured in it.
> are you suggesting sending several hundred 407s for each bye?
> 
> -- juha
> 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 10:33:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29716
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 10:33:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23Fhps27578
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 10:43:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23Fhpp27575
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 10:43:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29685
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 10:33:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FhHp27503;
	Mon, 3 Mar 2003 10:43:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23FgEp27438
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 10:42:14 -0500
Received: from lohi.eng.song.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29629
	for <sipping@ietf.org>; Mon, 3 Mar 2003 10:31:40 -0500 (EST)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.36 #1 (Debian))
	id 18prwi-0001ci-00; Mon, 03 Mar 2003 17:33:40 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15971.30164.363347.769011@harjus.eng.song.fi>
Date: Mon, 3 Mar 2003 17:33:40 +0200
To: <hisham.khartabil@nokia.com>
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <stu.jacobs@labs.gte.com>, <mankin@psg.com>,
        <Jari.Arkko@lmf.ericsson.se>
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
In-Reply-To: <2038BCC78B1AD641891A0D1AE133DBB7FE7300@esebe019.ntc.nokia.com>
References: <2038BCC78B1AD641891A0D1AE133DBB7FE7300@esebe019.ntc.nokia.com>
X-Mailer: VM 7.07 under Emacs 21.2.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

hisham.khartabil@nokia.com writes:

  > I think you exaggerating here with several hundreds, but anyway, I
  > was suggesting several hundreds of proxy-authenticate headers. Of
  > course you can scale your network to be better than that. I'm trying
  > to find a solution that doesn't rely on the UA to send its realm
  > (You haven't objected to that yet).

the realm can be infered from the from header in invite request, but not
in bye request.  as i have explained, there is no security risk when the
user tells the realm in which it want to get authenticated.  so i don't
see any problems with that and don't understand why yiou would need to
find another for the proxy to figure it out.   this is how eap works and
that is how sip should work.

-- juha

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar  3 22:35:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22449
	for <sipping-archive@odin.ietf.org>; Mon, 3 Mar 2003 22:35:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h243jma19536
	for sipping-archive@odin.ietf.org; Mon, 3 Mar 2003 22:45:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h243jmp19533
	for <sipping-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 22:45:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22438
	for <sipping-web-archive@ietf.org>; Mon, 3 Mar 2003 22:35:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h243ivp19509;
	Mon, 3 Mar 2003 22:44:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h243hpp19423
	for <sipping@optimus.ietf.org>; Mon, 3 Mar 2003 22:43:51 -0500
Received: from pmesmtp01.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22418
	for <sipping@ietf.org>; Mon, 3 Mar 2003 22:33:03 -0500 (EST)
Received: from pmismtp06.wcomnet.com ([166.38.62.54])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HB700I66GAG3M@firewall.wcom.com> for sipping@ietf.org; Tue,
 04 Mar 2003 03:27:52 +0000 (GMT)
Received: from pmismtp06.wcomnet.com by pmismtp06.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HB700L01GAF5I@pmismtp06.wcomnet.com>; Tue,
 04 Mar 2003 03:27:52 +0000 (GMT)
Received: from hsinnreich2 ([166.50.136.99])
 by pmismtp06.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HB700K57G9CJ0@pmismtp06.wcomnet.com>; Tue,
 04 Mar 2003 03:27:51 +0000 (GMT)
Date: Mon, 03 Mar 2003 21:27:12 -0600
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
In-reply-to: <239174FF942BD511B3C40080C8945C1A04FEFA67@atmail02.utalan.at>
To: "'Edler Franz'" <franz.edler@uta.at>,
        "'Eric Tremblay'" <etremblay@mediatrix.com>,
        "=?iso-8859-1?Q?'J=F6rgen_Bj=F6rkner'?=" <jorgen.bjorkner@hotsip.com>,
        sipforum-discussion@lists.su.se
Cc: sipping@ietf.org
Message-id: <002501c2e1fe$097ee890$638832a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=iso-8859-1
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h243hqp19424
Subject: [Sipping] RE: [Sipforum-discussion] SIP Telephony Device Requirements,
 Conf	iguration and Data
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Franz Edler writes:

>"dual homed" SIP-UA with one "line" connected 
> to the PSTN via V5 - SIP gateway and the other "lines" beeing 
> free for all new services of the SIP world.

Great minds think alike! :-) Some of us had actually the same
requirements. This may be a MAY...

The authors are still collecting all comments and we plan to consolidate
them with our follow-up into one single reply, for consistency reasons.
Please stay tuned.

Thanks, Henry

I've stopped 2,514 spam messages. You can too!
Get your free, safe spam protection at
http://www.cloudmark.com/spamnetsig/



> -----Original Message-----
> From: Edler Franz [mailto:franz.edler@uta.at] 
> Sent: Friday, February 28, 2003 1:55 AM
> To: 'Eric Tremblay'; Henry Sinnreich; Jörgen Björkner; 
> sipforum-discussion@lists.su.se
> Cc: sipping@ietf.org
> Subject: AW: [Sipforum-discussion] SIP Telephony Device 
> Requirements, Conf iguration and Data
> 
> 
> Hi folks,
> 
> just a comment on SIP-25:
> 
> I am currently working on a PSTN - SIP migration concept 
> avoiding to re-invent all fancy features of the PSTN and in 
> particular to re-implement all legal/regulatory requirements 
> (emergency call handling, legal intercept). The concept 
> builds upon a "dual homed" SIP-UA with one "line" connected 
> to the PSTN via V5 - SIP gateway and the other "lines" beeing 
> free for all new services of the SIP world. Therefore the 
> requirement of multiple identities on the SIP side and a 
> static identitiy on the PSTN side is essential, but I agree, 
> if you are focused on analog adapters only, this would mean 
> an unnecessary burden. But I suggest to re-think the 
> migration perspective.
> 
> By the way, if anyone is interested in this "dual-homed" PSTN 
> - SIP migration concept let me know. I am convienced that 
> this means a good chance for a carrier to migrate towards SIP 
> without heavy investments in re-inventing what is already existing.
> 
> kind regards
> Franz
> 
> ---------------------------------------------------------------
> Franz Edler
> Strategy & Business Development
> 
> UTA Telekom AG
> Donau-City-Strasse 11
> A-1220 Wien
> T: + 43/1/9009-3310
> F: + 43/1/9009-93310
> M: + 43/699/1388 3310
> mailto:franz.edler@uta.at
> http://www.uta.at
> --------------------------------------------------------------
> 
> > -----Ursprüngliche Nachricht-----
> > Von:	Eric Tremblay [SMTP:etremblay@mediatrix.com]
> > Gesendet am:	Mittwoch, 26. Februar 2003 17:41
> > An:	Henry Sinnreich; Jörgen Björkner; 
> sipforum-discussion@lists.su.se
> > Cc:	sipping@ietf.org
> > Betreff:	RE: [Sipforum-discussion] SIP Telephony Device 
> Requirements,
> > Configuration and Data
> > 
> > Hi Henry,
> > 
> > Here is a somewhat lengthy email with a few comments about the SIP 
> > Telephony Device Requirements draft:
> > 
> > 
> >   SIP-25, Dynamic login/logout for user mobility: SIP devices MUST 
> >   support user mobility.  SIP clients MUST store a static 
> profile in 
> >   non-volatile memory so that this information is available 
> during the 
> >   power up sequence.  SIP clients MUST allow a user to walk up to a 
> >   client, login, and be able to send and receive calls with 
> his profile 
> >   information. 
> >   For emergency numbers (e.g. 911) the client MUST send the 
> credentials 
> >   (username/password) of the static profile.
> > 
> > [EricT]
> > We are developing analog adapters and don't remember 
> receiving such a
> > request. I suggest either changing the MUST to SHOULD or 
> adding some text
> > to specify that it is a MUST for devices with the proper 
> interface to do
> > it and a SHOULD for devices with a limited interface. I 
> know we could
> > possibly configure this through a web interface, but the 
> point is that
> > there are a lot of vendore that currently just want to 
> replace the wire,
> > not the phone and its interface...
> > 
> > 
> > 
> > 
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 03:33:19 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09055
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 03:33:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h248hgx15560
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 03:43:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h248hfp15557
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 03:43:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09030
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 03:32:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h248Ysp14467;
	Tue, 4 Mar 2003 03:34:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h248Xbp14428
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 03:33:37 -0500
Received: from mgw-x1.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08887
	for <sipping@ietf.org>; Tue, 4 Mar 2003 03:22:43 -0500 (EST)
From: aki.niemi@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h248NQo07395
	for <sipping@ietf.org>; Tue, 4 Mar 2003 10:23:26 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60c4f8822aac158f21081@esvir01nok.ntc.nokia.com>;
 Tue, 4 Mar 2003 10:24:41 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 4 Mar 2003 10:24:41 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Date: Tue, 4 Mar 2003 10:24:40 +0200
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD90194518F@esebe013.ntc.nokia.com>
Thread-Topic: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Thread-Index: AcLhm8Zdv4krxafuTZeTN9WdYbhwxQAiTozQ
To: <jh@lohi.eng.song.fi>, <hisham.khartabil@nokia.com>
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <stu.jacobs@labs.gte.com>, <mankin@psg.com>,
        <Jari.Arkko@lmf.ericsson.se>
X-OriginalArrivalTime: 04 Mar 2003 08:24:41.0527 (UTC) FILETIME=[80FA1470:01C2E227]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h248Xbp14429
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

Inline.

 > -----Original Message-----
 > From: ext jh@lohi.eng.song.fi [mailto:jh@lohi.eng.song.fi]
 > Sent: 03 March, 2003 17:34
 > To: Khartabil Hisham (NMP/Helsinki)
 > Cc: Gonzalo.Camarillo@lmf.ericsson.se; BeckW@t-systems.com;
 > sipping@ietf.org; stu.jacobs@labs.gte.com; mankin@psg.com;
 > Jari.Arkko@lmf.ericsson.se
 > Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA 
 > reqs draft
 > 
 > 
 > hisham.khartabil@nokia.com writes:
 > 
 >   > I think you exaggerating here with several hundreds, but 
 > anyway, I
 >   > was suggesting several hundreds of proxy-authenticate headers. Of
 >   > course you can scale your network to be better than 
 > that. I'm trying
 >   > to find a solution that doesn't rely on the UA to send its realm
 >   > (You haven't objected to that yet).
 > 
 > the realm can be infered from the from header in invite 
 > request, but not
 > in bye request.  as i have explained, there is no security 
 > risk when the
 > user tells the realm in which it want to get authenticated.  
 > so i don't
 > see any problems with that and don't understand why yiou 
 > would need to
 > find another for the proxy to figure it out.   this is how 
 > eap works and
 > that is how sip should work.

I think these problems don't stem from inefficiency of SIP but of a particular type of network deployment. EAP doesn't have a concept of a realm, although some EAP types may. However, EAP does have the Identity request/response mechanism for querying the client's id. In SIP, digest doesn't have a way to do a similar Identity check. Instead the server challenges and issues its realm blindly without knowing the client's id, and the client can then choose a matching username/password pair. Digest authenticates the username, not the From field - these may not be exactly the same. 

This feature of blind challenges in digest has proven problematic before, and I agree that it would be nice if there was an EAP Identity request/response -type mechanism available in Digest. But it isn't an easy add-on.

Cheers,
Aki



 > 
 > -- juha
 > 
 > _______________________________________________
 > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
 > This list is for NEW development of the application of SIP
 > Use sip-implementors@cs.columbia.edu for questions on current sip
 > Use sip@ietf.org for new developments of core SIP
 > 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 03:34:39 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09111
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 03:34:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h248j2F15634
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 03:45:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h248j1p15629
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 03:45:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09083
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 03:34:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h248iCp15596;
	Tue, 4 Mar 2003 03:44:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h248gIp15520
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 03:42:27 -0500
Received: from lohi.eng.song.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09015
	for <sipping@ietf.org>; Tue, 4 Mar 2003 03:31:17 -0500 (EST)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.36 #1 (Debian))
	id 18q7rP-0002Zx-00; Tue, 04 Mar 2003 10:33:15 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15972.25802.979438.32847@harjus.eng.song.fi>
Date: Tue, 4 Mar 2003 10:33:14 +0200
To: <aki.niemi@nokia.com>
Cc: <hisham.khartabil@nokia.com>, <Gonzalo.Camarillo@lmf.ericsson.se>,
        <BeckW@t-systems.com>, <sipping@ietf.org>, <stu.jacobs@labs.gte.com>,
        <mankin@psg.com>, <Jari.Arkko@lmf.ericsson.se>
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
In-Reply-To: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD90194518F@esebe013.ntc.nokia.com>
References: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD90194518F@esebe013.ntc.nokia.com>
X-Mailer: VM 7.07 under Emacs 21.2.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

aki.niemi@nokia.com writes:

 > Digest authenticates the username,
 > not the From field - these may not be exactly the same.

i have never claimed that digest authenticates the from field, but in
case of an initial request, the proxy can get the realm to be used in
its challenge from the from field.  in subsequent requests this is not
anymore possible.

 > This feature of blind challenges in digest has proven problematic
 > before, and I agree that it would be nice if there was an EAP
 > Identity request/response -type mechanism available in Digest. But it
 > isn't an easy add-on.

we don't need an eap style identity request/response.  what we need is
an ability for the ua to tell in its requests to the proxy the realm it
claims to belong to so that the proxy can correctly challenge it.  this
can be easily fixed with a single new header or parameter.

-- juha

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 03:59:57 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09517
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 03:59:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h249AKE17687
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 04:10:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h249AKp17684
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 04:10:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09507
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 03:59:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2499dp17644;
	Tue, 4 Mar 2003 04:09:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2497Hp17265
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 04:07:17 -0500
Received: from mgw-x1.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09437
	for <sipping@ietf.org>; Tue, 4 Mar 2003 03:56:22 -0500 (EST)
From: aki.niemi@nokia.com
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h248v6o10448
	for <sipping@ietf.org>; Tue, 4 Mar 2003 10:57:06 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60c5175daaac158f25600@esvir05nok.ntc.nokia.com>;
 Tue, 4 Mar 2003 10:58:23 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 4 Mar 2003 10:58:23 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Date: Tue, 4 Mar 2003 10:58:21 +0200
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD901945190@esebe013.ntc.nokia.com>
Thread-Topic: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Thread-Index: AcLiKLid0UWYKFDHRmCBdiAfotH89AAAK0+Q
To: <jh@lohi.eng.song.fi>
Cc: <hisham.khartabil@nokia.com>, <Gonzalo.Camarillo@lmf.ericsson.se>,
        <BeckW@t-systems.com>, <sipping@ietf.org>, <stu.jacobs@labs.gte.com>,
        <mankin@psg.com>, <Jari.Arkko@lmf.ericsson.se>
X-OriginalArrivalTime: 04 Mar 2003 08:58:23.0112 (UTC) FILETIME=[35EF7880:01C2E22C]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2497Hp17266
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi Juha,

Inline.

 > -----Original Message-----
 > From: ext jh@lohi.eng.song.fi [mailto:jh@lohi.eng.song.fi]
 > Sent: 04 March, 2003 10:33
 > To: Niemi Aki (NMP/Helsinki)
 > Cc: Khartabil Hisham (NMP/Helsinki); 
 > Gonzalo.Camarillo@lmf.ericsson.se;
 > BeckW@t-systems.com; sipping@ietf.org; stu.jacobs@labs.gte.com;
 > mankin@psg.com; Jari.Arkko@lmf.ericsson.se
 > Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA 
 > reqs draft
 > 
 > 
 > aki.niemi@nokia.com writes:
 > 
 >  > Digest authenticates the username,
 >  > not the From field - these may not be exactly the same.
 > 
 > i have never claimed that digest authenticates the from field, but in
 > case of an initial request, the proxy can get the realm to be used in
 > its challenge from the from field.  in subsequent requests 
 > this is not
 > anymore possible.
 > 
 >  > This feature of blind challenges in digest has proven problematic
 >  > before, and I agree that it would be nice if there was an EAP
 >  > Identity request/response -type mechanism available in 
 > Digest. But it
 >  > isn't an easy add-on.
 > 
 > we don't need an eap style identity request/response.  what 
 > we need is
 > an ability for the ua to tell in its requests to the proxy 
 > the realm it
 > claims to belong to so that the proxy can correctly 
 > challenge it.  this
 > can be easily fixed with a single new header or parameter.

A UA can have valid credentials for hundreds of realms. Would it list all of them in this new header or param? In fact, I think what you describe above is exactly opposite to how digest works. A client never actually belongs to a single realm. By browser has stored username/passwords for about 20 different realms.

Cheers,
Aki
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 06:20:51 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12716
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 06:20:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24BVI627302
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 06:31:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24BVHp27299
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 06:31:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12698
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 06:20:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24BUUp27272;
	Tue, 4 Mar 2003 06:30:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24BTap27228
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 06:29:36 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12675
	for <sipping@ietf.org>; Tue, 4 Mar 2003 06:18:38 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h24BKYnS020779;
	Tue, 4 Mar 2003 12:20:34 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5W9BS54; Tue, 4 Mar 2003 12:20:34 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.6/8.12.6/lmf-2.1-jcs) with ESMTP id h24BKYGh024083;
	Tue, 4 Mar 2003 13:20:34 +0200 (EET)
Message-ID: <3E648C00.C8A5EEDE@lmf.ericsson.se>
Date: Tue, 04 Mar 2003 13:20:32 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Francois Audet <audet@nortelnetworks.com>
CC: "'sipping'" <sipping@ietf.org>
Subject: Re: [Sipping] New version of the early media draft
References: <2F1FC1DEA077D5119FAD00508BCFD6D206CADC51@zsc3c030.us.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Francois,

Thanks for the feedback.

About your suggestion, the paragraph you are referring to does not
recommend any particular behaviour. It only says that one possible
choice is mixing them. I do not think that we need to list all possible
things a gateway could do in that case. I believe that the reader gets
the idea by reading the paragraph as it is (i.e., there are multiple
behaviours to choose from).

Thanks,

Gonzalo



Francois Audet wrote:
> 
> Gonzallo,
> 
> I finally had a chance to read the new version of early media draft.
> Kind of interesting
> that this version didn't get much feedback at all.
> 
> It is a very good document. I think you have captured very well the
> very many issues that
> were discussed last year. I am very comfortable with this new version.
> 
> I have only one suggestion (and a minor one). In section 2.2 on page
> 7, in the paragraph that
> starts with "Note" just below point 3, I would change the lst sentence
> to the following:
> 
>    This type of gateway could choose to generate local ringback upon
> reception
>    of a 180 (Ringing) response, and override or mix it with any
> incoming media that
>    happens to arrive (if it does at all).
> 
> > -----Original Message-----
> > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > Sent: Monday, February 10, 2003 3:41 AM
> > To: sipping
> > Subject: [Sipping] New version of the early media draft
> >
> >
> > Folks,
> >
> > I have just sumitted a new version of the early media draft.
> > Until it appears in the archives, you can fetch it from:
> >
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-early-media-01.txt
> 
> I have included all the (long and useful) discussions we had in the
> mailing list. Therefore, the draft now keeps separate the "gateway"
> and the "application server" models. I have also removed the parts we
> did not agree on.
> 
> Feedback is, as usual, appreciated.
> 
> Thanks,
> 
> Gonzalo
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip Use
> sip@ietf.org for new developments of core SIP
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 06:24:06 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12786
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 06:24:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24BYXE27430
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 06:34:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24BYXp27427
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 06:34:33 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12776
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 06:23:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24BY3p27401;
	Tue, 4 Mar 2003 06:34:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24BXop27381
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 06:33:50 -0500
Received: from lohi.eng.song.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12762
	for <sipping@ietf.org>; Tue, 4 Mar 2003 06:22:52 -0500 (EST)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.36 #1 (Debian))
	id 18qAXR-0002jl-00; Tue, 04 Mar 2003 13:24:49 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15972.36097.393128.629111@harjus.eng.song.fi>
Date: Tue, 4 Mar 2003 13:24:49 +0200
To: <aki.niemi@nokia.com>
Cc: <hisham.khartabil@nokia.com>, <Gonzalo.Camarillo@lmf.ericsson.se>,
        <BeckW@t-systems.com>, <sipping@ietf.org>, <stu.jacobs@labs.gte.com>,
        <mankin@psg.com>, <Jari.Arkko@lmf.ericsson.se>
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
In-Reply-To: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD901945190@esebe013.ntc.nokia.com>
References: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD901945190@esebe013.ntc.nokia.com>
X-Mailer: VM 7.07 under Emacs 21.2.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

aki.niemi@nokia.com writes:

 > A UA can have valid credentials for hundreds of realms. Would it list
 > all of them in this new header or param? In fact, I think what you
 > describe above is exactly opposite to how digest works. A client
 > never actually belongs to a single realm. By browser has stored
 > username/passwords for about 20 different realms. 

i haven't seen any sip ua where i can configure more than one realm.  in
fact, i haven't sen any where i can explicitly configure any realm.
instead, some assume that the domain of the username must equal the
realm received from the proxy.

perhaps we should go back and start from the requiremnts.  i have
requirement that the proxy must be able to belong to multiple realms and
proxy aaa based on the realm.  the other requirement is that the proxy
must be able to authenticate each request that it receives from uas that
belong to the realms of the proxy .  today this is not possible in
practise.  

-- juha

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 06:42:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13172
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 06:42:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24Bqs128742
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 06:52:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Bqrp28739
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 06:52:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13162
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 06:41:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24BqHp28725;
	Tue, 4 Mar 2003 06:52:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24BpJp28694
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 06:51:19 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13145
	for <sipping@ietf.org>; Tue, 4 Mar 2003 06:40:22 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h24BgKnS027056;
	Tue, 4 Mar 2003 12:42:20 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5W9BXP5; Tue, 4 Mar 2003 12:42:20 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.6/8.12.6/lmf-2.1-jcs) with ESMTP id h24BgKGh025381;
	Tue, 4 Mar 2003 13:42:20 +0200 (EET)
Message-ID: <3E64911A.B77A3050@lmf.ericsson.se>
Date: Tue, 04 Mar 2003 13:42:18 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
CC: sipping <sipping@ietf.org>
Subject: Re: [Sipping] New version of the early media draft
References: <DBC3D7D0A071F743AE0767C9C6071EDA0482BB93@il0015exch010u.ih.lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ejzak,

the main problem with any SIP-layer mechanism that allows the UAS to
tell the UAC whether local ringback has to be generated or not is race
conditions. It really does not matter whether you use an Alert-Info
header field in a reponse, or a special status code, or a special body,
or whatever to signal it. You always have race conditions.

Let's say that the UAS tells the UAC to generate local ringback. After a
while, the callee picks up. The UAS sends back a 200 OK and starts
sending media. The 200 OK, for some reason, arrives much later than the
first media packets... what is the UAC supposed to do in the mean time?
Ignore the media? Play the media anyway?

Another scenario. The UAC starts receiving media before a provisional
response is received... what does it have to do?

The main point is that, since signalling and media are loosely
synchronized, you will always have race conditions and you will have to
make guesses about what to do during those race conditions anyway.

Thanks,

Gonzalo



"Ejzak, Richard P (Richard)" wrote:
> 
> Gonzalo,
> It seems the single greatest difficulty with the gateway model (as you point out in your draft) is the difficulty of depending on the arrival of media packets to determine whether or not to generate local ringing.  I have previously (last summer) suggested a solution to this (use 180 exclusively to indicate that local ringing should override any inband media and 183 otherwise) that is unacceptable since it does not satisfy the requirement that 180 be used to indicate alerting of the called party.
> 
> Have you considered using the Alert-Info header in the following way? Since the real problem is that we would like to be able to discriminate between cases when 180 should cause local ringing and when 180 should not (since inband media is available), and it is the UAS that knows conclusively which case applies, let's agree on an encoding of the Alert-Info header that indicates that local ringing should not be applied.  The following line is a syntactically valid header:
> 
> Alert-Info: <data:,>
> 
> This header identifies the Alert-Info as the null string, which seems unambiguously and efficiently interpretable within a 180 response as "do not play local ringing even though the called party is being alerted."  If the UAC does not recognize it or chooses not to interpret it for security reasons, it can be safely ignored.
> 
> This modest addition to your draft (or an equivalent mechanism) would make it unnecessary for the gateway model to depend on local policy or incoming media packet detection and is completely consistent with all of the constraints you have documented.
> 
> Another approach may be to actually specify the rtp stream as the source of the alert info (although this would require the definition of a new URI scheme type).  It might look like:
> 
> Alert-Info: <rtp:/12.34.56.78:90>
> 
> where the Alert-Info specifies the address and port of the rtp stream.  I don't like this mechanism since it is redundant with SDP and prone to error.  It is also ambiguous in the event of any subsequent media change using UPDATE (Do I begin to generate local ringing if the rtp stream source address changes?  Or do I continue to listen to the address specified in the Alert-Info and ignore any UPDATEs?  No to both.)
> 
> May I suggest including such a mechanism (preferably the first one) in your draft.
> 
> Richard Ejzak
> Lucent Technologies
> 
> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: Monday, February 10, 2003 5:41 AM
> To: sipping
> Subject: [Sipping] New version of the early media draft
> 
> Folks,
> 
> I have just sumitted a new version of the early media draft. Until it
> appears in the archives, you can fetch it from:
> 
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-early-media-01.txt
> 
> I have included all the (long and useful) discussions we had in the
> mailing list. Therefore, the draft now keeps separate the "gateway" and
> the "application server" models. I have also removed the parts we did
> not agree on.
> 
> Feedback is, as usual, appreciated.
> 
> Thanks,
> 
> Gonzalo
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 07:02:50 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13670
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 07:02:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24CDG930153
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 07:13:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CDFp30150
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 07:13:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13666
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 07:02:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CCfp30121;
	Tue, 4 Mar 2003 07:12:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CAHp30030
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 07:10:17 -0500
Received: from alaska.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13597;
	Tue, 4 Mar 2003 06:59:19 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by alaska.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h24C1HpX006559;
	Tue, 4 Mar 2003 13:01:18 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5XHKGWX; Tue, 4 Mar 2003 13:01:17 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.6/8.12.6/lmf-2.1-jcs) with ESMTP id h24C1GGh026659;
	Tue, 4 Mar 2003 14:01:16 +0200 (EET)
Message-ID: <3E64958A.9341D652@lmf.ericsson.se>
Date: Tue, 04 Mar 2003 14:01:14 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sip <sip@ietf.org>, sipping <sipping@ietf.org>
CC: Jon Peterson <Jon.Peterson@neustar.com>,
        Dean Willis <dean.willis@softarmor.com>, Rohan Mahy <rohan@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Agenda requests for SF
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

we are going to start gathering agenda requests for the next IETF
meeting in San Francisco. Please, let the chairs know if you would like
to request a slot.

Thanks,

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 07:16:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13948
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 07:16:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24CQkA30757
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 07:26:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CQkp30753
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 07:26:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13944
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 07:15:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CQ8p30738;
	Tue, 4 Mar 2003 07:26:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CQ0p30715
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 07:26:00 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13928
	for <sipping@ietf.org>; Tue, 4 Mar 2003 07:15:02 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id h24CH3nS008465;
	Tue, 4 Mar 2003 13:17:03 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5XHKMDY; Tue, 4 Mar 2003 13:16:59 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.6/8.12.6/lmf-2.1-jcs) with ESMTP id h24CGwGh027700;
	Tue, 4 Mar 2003 14:16:58 +0200 (EET)
Message-ID: <3E649938.17A93738@lmf.ericsson.se>
Date: Tue, 04 Mar 2003 14:16:56 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: jh@lohi.eng.song.fi
CC: "Beck01, Wolfgang" <BeckW@t-systems.com>, jon.peterson@neustar.biz,
        sipping@ietf.org
Subject: Re: [Sipping] proxy accounting, was:  New version of the SIP-AAAreqs 
 draft
References: <C3F9C806AEC6D5119643000347055E322089B4@G9JNW.mgb01.telekom.de>
		<15967.18652.915252.507261@lohi.eng.song.fi>
		<3E5F6787.A2229EF1@lmf.ericsson.se> <15967.26807.957641.310193@harjus.eng.song.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Juha,

RFC3261 compliant UAs do not take into account the To and From URIs to
perform dialog identification. However, systems that implement RFC2543
do... that's the only reason why the spec does not allow to change the
From and To URIs; backwards compatibility.

It would be nice to know how big is this backwards compatibility problem
(i.e., how many already installed systems implement that way of dialog
identification)...

Gonzalo

jh@lohi.eng.song.fi wrote:
> 
> Gonzalo Camarillo writes:
> 
>  > This is what I said in one of my previous mails. Per RFC 3261, you are
>  > free to change your URL if you want. No change to the spec needed.
> 
> the text that i quoted, doesn't say so.  in order to get this capability
> implemented in UAs, it must be a MUST in the text, or. alternatively, we
> must have a new header/field where the realm can be placed.  the same
> goes for the P header.  i don't know any general purpose sip ua that is
> implementing it.
> 
> -- juha
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 07:35:51 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15545
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 07:35:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24CkHE32486
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 07:46:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CkHp32483
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 07:46:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15475
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 07:35:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CjUp32335;
	Tue, 4 Mar 2003 07:45:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CeWp31970
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 07:40:32 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14916;
	Tue, 4 Mar 2003 07:29:35 -0500 (EST)
Message-Id: <200303041229.HAA14916@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 04 Mar 2003 07:29:34 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-config-framework-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: A Framework for SIP User Agent Configuration
	Author(s)	: D. Petrie
	Filename	: draft-ietf-sipping-config-framework-00.txt
	Pages		: 20
	Date		: 2003-3-3
	
This document defines the application of a set of protocols for 
configuring a SIP user agent.  The SIP user agent must discover how 
and from where to retrieve its initial configuration and be notified 
of changes and updates which impact its configuration.  The 
objective is to define a means for automatically configuring a user 
agent such that it can be functional without user or administrative 
intervention.  The framework for discovery, delivery, notification 
and updates of user agent configuration is defined here.  This 
framework is also intended to ease ongoing administration, 
configuration and upgrading of large scale deployments of SIP user 
agents.  The contents and format of the configuration data to be 
defined is outside the scope of this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-config-framework-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sipping-config-framework-00.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-config-framework-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:	<2003-3-3145021.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-config-framework-00.txt

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

Content-Type: text/plain
Content-ID:	<2003-3-3145021.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 07:35:55 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15558
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 07:35:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24CkLr32502
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 07:46:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CkLp32499
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 07:46:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15479
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 07:35:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Cjap32375;
	Tue, 4 Mar 2003 07:45:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Cebp31981
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 07:40:37 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14937;
	Tue, 4 Mar 2003 07:29:39 -0500 (EST)
Message-Id: <200303041229.HAA14937@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 04 Mar 2003 07:29:39 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-content-indirect-03.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Requirements for Content Indirection in Session 
                          Initiation Protocol (SIP) Messages
	Author(s)	: S. Olson
	Filename	: draft-ietf-sipping-content-indirect-03.txt
	Pages		: 10
	Date		: 2003-3-3
	
This specification defines requirements for a mechanism to indirectly
specify the content of a SIP message for the purpose of transferring
the content via a non-SIP channel.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-content-indirect-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sipping-content-indirect-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-sipping-content-indirect-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:	<2003-3-3145030.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-content-indirect-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-content-indirect-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-3145030.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 07:35:58 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15573
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 07:35:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24CkPo32519
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 07:46:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CkPp32516
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 07:46:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15483
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 07:35:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Cjcp32418;
	Tue, 4 Mar 2003 07:45:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Cehp31990
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 07:40:43 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14958;
	Tue, 4 Mar 2003 07:29:45 -0500 (EST)
Message-Id: <200303041229.HAA14958@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 04 Mar 2003 07:29:45 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-ua-prof-framewk-reqs-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Requirements for SIP User Agent Profile Delivery 
                          Framework
	Author(s)	: D. Petrie, C. Jennings
	Filename	: draft-ietf-sipping-ua-prof-framewk-reqs-00.txt
	Pages		: 20
	Date		: 2003-3-3
	
This document attempts to identify the requirements for a protocol 
framework to provide SIP user and device profiles to SIP user 
agents.  The objective is not to invent new special purpose 
protocols, but to identify the requirements such that a rational 
decision can be made as to what existing protocol(s) should be used 
to solve the problem of providing user and device profiles to SIP 
user agents.  This document also contains an evaluation of a set of 
applicable protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-ua-prof-framewk-reqs-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sipping-ua-prof-framewk-reqs-00.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-ua-prof-framewk-reqs-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:	<2003-3-3145039.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-ua-prof-framewk-reqs-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-ua-prof-framewk-reqs-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-3145039.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 09:03:03 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22128
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 09:03:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24EDXT07013
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 09:13:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24EDWp07010
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 09:13:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22077
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 09:02:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24ECcp06985;
	Tue, 4 Mar 2003 09:12:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24EBjp06935
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 09:11:45 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21942
	for <sipping@ietf.org>; Tue, 4 Mar 2003 09:00:44 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Tue, 4 Mar 2003 09:04:57 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D248851@zoe.office.snowshore.com>
Thread-Topic: New version of netann
Thread-Index: AcLiCx9vHwCwhWVmR3KSGMkt5RgyEQ==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h24EBjp06936
Subject: [Sipping] New version of netann
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Before it shows up in the archives, here is a copy:
http://flyingfox.snowshore.com/i-d/sip/draft-burger-sipping-netann-05.txt
http://flyingfox.snowshore.com/i-d/sip/draft-burger-sipping-netann-05.html


The -05 version of netann incorporates the following changes:

409 Result Code
===============
Due to popular demand, rather than using 487, we use 409.  See the text for more information.  Note that the case brought up on the list of a UAC that ignores 487 response codes is clearly a case of a broken UAC.  That UAC must terminate the dialog upon the receipt of ANY 4xx code.

100rel
======
Everyone we actually interoperate with uses 100rel.  It's now in the document as a SHOULD.

Conference Indicator
====================
The conference indicator is now simply "conf".  The conference identifier is now a parameter.  Some (non-conforming) proxies may not do the right thing.  Please read the "special note".



Other Issues Brought Up on the List:

Session Termination Timing
==========================
Bill Marshall brought up the possibility that a BYE from the media server might not arrive at the UAC at the same time as the end of the media.  In our experience, if the media server issues the BYE after finishing playing out the media, the BYE arrives at the UAC after the media finishes playing.

In the worst case, let's say the media server is sending 200ms buffers.  If the UAC flushes playing the buffer upon receipt of the BYE (which is very unlikely), the final 200ms will be clipped.  That probably will not be noticed.

One might have a media server that sends packets faster than real time.  For example, consider a six second prompt.  For 200ms packets, this would require 30 packets.  A media server that sends packets faster than real time would send packets faster than one every 200ms.  This could break the UAC.  That said, the media server, in this case, would be a VERY BAD INTERNET CITIZEN.  It would be breaking most of the RTP statistical multiplexing assumptions, and would most likely overflow the UAC's buffer.  Thus this is a corner case that netann does not have to deal with.

Dave Oran noted that most announcements get repeated, so clipping 200ms of a 12s+ prompt probably won't be noticed.

Moreover, just about all of the discussions about the different paths the RTP and SIP signaling take are about how much longer the SIP signaling takes versus the RTP.  That is, the UAC will have received and played out the buffer long before it receives the BYE.


IVR Use
=======
Luca Prati asked about using netann for IVR-style interactions, such as reading out advice of charging (a complex prompt) and mid-call announcements.

AOC can be done with sequences.  The netann document specifies an interface to sequences, but it does not describe how to specify prompt sequences.  A follow-on document will describe how this is done.

Mid-call announcements can be done by reinviting the call to the announcement service.  However, one would expect a more rich interactions, such as playing the announcement over the called party.  Netann is specifically NOT suited to this use and the document states that.  See mscml for one way of doing this.


"Early" URI Parameter
=====================
Christer Holmberg pointed out his preference for coming up with a generic "this session is early" mechanism.  At this time, I'm not sure that this is something that occurs in other situations.  Given that, we've left in the early parameter.

I would agree that the UAC might not support early media.  However, the onus would be on the proxy, not the media server, to enforce 100rel.  If the UAC doesn't support 100rel, then the proxy should request it.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 10:05:35 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25536
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 10:05:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24FG6L11644
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 10:16:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FG6p11641
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 10:16:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25476
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 10:05:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FFOp11602;
	Tue, 4 Mar 2003 10:15:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FEGp11567
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 10:14:16 -0500
Received: from fox.iptel.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25272
	for <sipping@ietf.org>; Tue, 4 Mar 2003 10:03:13 -0500 (EST)
Received: from jku07.fokus.fraunhofer.de (port-212-202-200-46.reverse.qdsl-home.de [212.202.200.46])
	by fox.iptel.org (8.11.6/8.11.6) with ESMTP id h24F4AJ21602;
	Tue, 4 Mar 2003 16:04:15 +0100
Message-Id: <5.2.0.9.0.20030304154559.047cd088@mailhost.fokus.gmd.de>
X-Sender: jku@mailhost.fokus.gmd.de (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 04 Mar 2003 16:01:27 +0100
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
From: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>
Subject: Re: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Cc: jh@lohi.eng.song.fi, Stuart Jacobs <stu.jacobs@labs.gte.com>,
        Allison Mankin <mankin@psg.com>, sipping@ietf.org
In-Reply-To: <3E5DCC24.D13CB979@lmf.ericsson.se>
References: <5.1.1.6.0.20030221110917.04229140@pophost.gte.com>
 <5.1.1.6.0.20030221110917.04229140@pophost.gte.com>
 <5.2.0.9.0.20030226125028.00b3e288@mailhost.fokus.gmd.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

At 09:28 AM 2/27/2003, Gonzalo Camarillo wrote:
>Juha,
>
>[removing SIP (but keeping SIPPING) from the cc: ]
>
>Do you mean that you would like to see a note along these lines added to
>the draft?
>
>"Note that, in order to perform accounting, a SIP proxy server should
>see and authenticate every message sent over the dialog."

It is more difficult than that.

First, you need to have some authentication criteria for calls. Authenticating 
everything is not an option (how about callers from other domains). So it is 
a matter of your domain's policy to tell what calls should go through AAA.
You decide that on receipt of INVITE. That's still trivial.

Now when you decide to authenticate and account a call, the more tricky part
is bye. If a proxy server decides to authenticate/account a call, it must
record-route the original INVITE with some "accounted call" hint. There is
in many cases no other way to correlate thee BYEs to the space of aaa-ed
calls. That's doable too. Just add Record-Route: <sip:foo.bar;lr;use_aaa=yes>

The most compelling issue to me now is integrity of Record-Routes. If 
the BYE originator can send a BYE and manipulate RR (e.g., 
<sip:foo.bar;lr;use_aaa=NO>, it will be obviously useless.

-Jiri 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 10:13:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26462
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 10:13:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24FNpO12103
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 10:23:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FNpp12099
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 10:23:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26419
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 10:12:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FN6p12075;
	Tue, 4 Mar 2003 10:23:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FMgp12038
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 10:22:42 -0500
Received: from fox.iptel.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26375
	for <sipping@ietf.org>; Tue, 4 Mar 2003 10:11:39 -0500 (EST)
Received: from jku07.fokus.fraunhofer.de (port-212-202-200-46.reverse.qdsl-home.de [212.202.200.46])
	by fox.iptel.org (8.11.6/8.11.6) with ESMTP id h24FD1J21661;
	Tue, 4 Mar 2003 16:13:01 +0100
Message-Id: <5.2.0.9.0.20030304160754.044e1ea0@mailhost.fokus.gmd.de>
X-Sender: jku@mailhost.fokus.gmd.de (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 04 Mar 2003 16:10:15 +0100
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>, jh@lohi.eng.song.fi
From: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>
Subject: Re: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Cc: "Beck01, Wolfgang" <BeckW@t-systems.com>, sipping@ietf.org,
        stu.jacobs@labs.gte.com, mankin@psg.com,
        Jari Arkko <Jari.Arkko@lmf.ericsson.se>
In-Reply-To: <3E5F3B69.913DE777@lmf.ericsson.se>
References: <C3F9C806AEC6D5119643000347055E322089AE@G9JNW.mgb01.telekom.de>
 <15966.1788.184832.423324@harjus.eng.song.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

The issue is that you do not wish to force all requests to authenticate.
(Your new potential customer could never call you otherwise).

It is easy to decide which INVITEs to authenticate, it is hard
to decide which subsequent in-dialog requests to authenticate.
You no longer know the INVITE r-uri, which might have been
a key to the policy question "authenticate" or not?".

-jiri

At 11:35 AM 2/28/2003, Gonzalo Camarillo wrote:
>Juha,
>
>I still do not quite understand your arguments. Could you please
>elaborate on why a proxy cannot know that a message comes from a
>particular UA?
>
>Thanks,
>
>Gonzalo
>
>
>jh@lohi.eng.song.fi wrote:
>> 
>> Beck01, Wolfgang writes:
>> 
>>  > What kind of accounting information do we want to collect: The number
>>  > > of SIP messages per user? This is possible with an accounting
>>  > proxy.
>> 
>> unfortunately not.
>> 
>> -- juha
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 10:18:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26725
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 10:18:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24FSpK12455
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 10:28:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FSpp12452
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 10:28:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26709
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 10:17:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FS9p12395;
	Tue, 4 Mar 2003 10:28:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FRkp12368
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 10:27:46 -0500
Received: from fox.iptel.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26670
	for <sipping@ietf.org>; Tue, 4 Mar 2003 10:16:43 -0500 (EST)
Received: from jku07.fokus.fraunhofer.de (port-212-202-200-46.reverse.qdsl-home.de [212.202.200.46])
	by fox.iptel.org (8.11.6/8.11.6) with ESMTP id h24FIAJ21712;
	Tue, 4 Mar 2003 16:18:10 +0100
Message-Id: <5.2.0.9.0.20030304161233.04329fb8@mailhost.fokus.gmd.de>
X-Sender: jku@mailhost.fokus.gmd.de (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 04 Mar 2003 16:15:25 +0100
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>, jh@lohi.eng.song.fi
From: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>
Subject: Re: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Cc: "Beck01, Wolfgang" <BeckW@t-systems.com>, sipping@ietf.org,
        stu.jacobs@labs.gte.com, mankin@psg.com,
        Jari Arkko <Jari.Arkko@lmf.ericsson.se>
In-Reply-To: <3E5F5590.412D66D8@lmf.ericsson.se>
References: <C3F9C806AEC6D5119643000347055E322089AE@G9JNW.mgb01.telekom.de>
 <15966.1788.184832.423324@harjus.eng.song.fi>
 <3E5F3B69.913DE777@lmf.ericsson.se>
 <E18ojso-0000GV-00@rautu>
 <3E5F3FDF.B5A878FD@lmf.ericsson.se>
 <15967.19340.437382.154213@harjus.eng.song.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

At 01:26 PM 2/28/2003, Gonzalo Camarillo wrote:
>Juha,
>
>OK, now I understand what you mean. Your proxy decides to perform or to
>not perform accounting for a particular request based on the From header
>field of the request. That is a poor choice. 

That is a very *good* choice.

There may be many conditions, which may make a server decide whether to
authenticate or not. From HF alone may or may not be sufficient, but there
are cases in which you definitely want to do that. In particular, you
do not wish foo.bar proxy to rubberstamp and forward a request with
foo.bar in From without verifying who is sending it.

-jiri

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 10:24:16 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26982
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 10:24:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24FYlx12848
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 10:34:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FYlp12845
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 10:34:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26969
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 10:23:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FY7p12825;
	Tue, 4 Mar 2003 10:34:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24FX3p12784
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 10:33:03 -0500
Received: from fox.iptel.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26903
	for <sipping@ietf.org>; Tue, 4 Mar 2003 10:22:01 -0500 (EST)
Received: from jku07.fokus.fraunhofer.de (port-212-202-200-46.reverse.qdsl-home.de [212.202.200.46])
	by fox.iptel.org (8.11.6/8.11.6) with ESMTP id h24FNRJ21762;
	Tue, 4 Mar 2003 16:23:28 +0100
Message-Id: <5.2.0.9.0.20030304161631.04008008@mailhost.fokus.gmd.de>
X-Sender: jku@mailhost.fokus.gmd.de (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 04 Mar 2003 16:20:41 +0100
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>, jh@lohi.eng.song.fi
From: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>
Subject: Re: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Cc: "Beck01, Wolfgang" <BeckW@t-systems.com>, sipping@ietf.org,
        stu.jacobs@labs.gte.com, mankin@psg.com,
        Jari Arkko <Jari.Arkko@lmf.ericsson.se>
In-Reply-To: <3E5F60C2.3BD1E9B4@lmf.ericsson.se>
References: <C3F9C806AEC6D5119643000347055E322089AE@G9JNW.mgb01.telekom.de>
 <15966.1788.184832.423324@harjus.eng.song.fi>
 <3E5F3B69.913DE777@lmf.ericsson.se>
 <E18ojso-0000GV-00@rautu>
 <3E5F3FDF.B5A878FD@lmf.ericsson.se>
 <15967.19340.437382.154213@harjus.eng.song.fi>
 <3E5F5590.412D66D8@lmf.ericsson.se>
 <15967.22989.940714.971963@harjus.eng.song.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

At 02:14 PM 2/28/2003, Gonzalo Camarillo wrote:
>And if you are not concerned about security either and you want to base
>your service in the contents of the To (or From) fields, then your UA
>can actually modify the To field. What it cannot modify is the tag.

That's absolutely not applicable due to backward compatibility issues.

>If your proxy does not trust the UA because it is a billing proxy, for
>instance, your proxy will only accept requests with proper credentials
>or requests that are going to be routed to a known (by the proxy) UA.

What makes it hard is there are some transaction that take AAA and some
that don't. You need to distinguish between them. Authenticating everything
is not an option.

>But ensuring that the UA does not cheat is outside of the scope of the
>requirements, and it can be done in several ways.

Actually, being cheating-proof is a very good accounting requirements,
don't you think so?

> also, if the proxy serves multiple realms, how can it know which realm
>> the user that send the request within a dialog belongs to so that it can
>> insert the proper realm in the digest challenge?  today there is no
>> header in the request where the user could tell that it belongs to a
>> certain realm.  the from header is the only one, but it only works for
>> sure for initial requests.
>
>You can change the contents of the From field. No problem. In fact, one
>of the reasons we removed the To and From URIs from the dialog
>identifiers (only the tags remain) was to address this type of
>situation.

backwards-incompatible.

-jiri 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 10:42:07 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27638
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 10:42:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24Fqds14716
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 10:52:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Fqdp14713
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 10:52:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27592
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 10:41:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Fq5p14687;
	Tue, 4 Mar 2003 10:52:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Fovp14577
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 10:50:57 -0500
Received: from fox.iptel.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27531
	for <sipping@ietf.org>; Tue, 4 Mar 2003 10:39:53 -0500 (EST)
Received: from jku07.fokus.fraunhofer.de (port-212-202-200-46.reverse.qdsl-home.de [212.202.200.46])
	by fox.iptel.org (8.11.6/8.11.6) with ESMTP id h24FfIJ21920;
	Tue, 4 Mar 2003 16:41:18 +0100
Message-Id: <5.2.0.9.0.20030304163740.030debb0@mailhost.fokus.gmd.de>
X-Sender: jku@mailhost.fokus.gmd.de (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 04 Mar 2003 16:38:14 +0100
To: hisham.khartabil@nokia.com, <jh@lohi.eng.song.fi>,
        <Gonzalo.Camarillo@lmf.ericsson.se>
From: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Cc: <BeckW@t-systems.com>, <sipping@ietf.org>, <stu.jacobs@labs.gte.com>,
        <mankin@psg.com>, <Jari.Arkko@lmf.ericsson.se>
In-Reply-To: <2038BCC78B1AD641891A0D1AE133DBB7FE72F5@esebe019.ntc.nokia.
 com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

At 01:57 PM 3/3/2003, hisham.khartabil@nokia.com wrote:
>A server knows what realm to use for a certain interface (it can do its own mapping). It cannot rely of a UA telling it the realm.

Why?

-jiri

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 10:50:15 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27940
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 10:50:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24G0lq15062
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 11:00:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24G0kp15059
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 11:00:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27926
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 10:49:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24G08p15012;
	Tue, 4 Mar 2003 11:00:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Fxdp14941
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 10:59:39 -0500
Received: from fox.iptel.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27887
	for <sipping@ietf.org>; Tue, 4 Mar 2003 10:48:36 -0500 (EST)
Received: from jku07.fokus.fraunhofer.de (port-212-202-200-46.reverse.qdsl-home.de [212.202.200.46])
	by fox.iptel.org (8.11.6/8.11.6) with ESMTP id h24Fo2J22052;
	Tue, 4 Mar 2003 16:50:02 +0100
Message-Id: <5.2.0.9.0.20030304164005.03218008@mailhost.fokus.gmd.de>
X-Sender: jku@mailhost.fokus.gmd.de (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 04 Mar 2003 16:41:37 +0100
To: hisham.khartabil@nokia.com, <jh@lohi.eng.song.fi>
From: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <stu.jacobs@labs.gte.com>, <mankin@psg.com>,
        <Jari.Arkko@lmf.ericsson.se>
In-Reply-To: <2038BCC78B1AD641891A0D1AE133DBB7FE72F7@esebe019.ntc.nokia.
 com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

At 02:28 PM 3/3/2003, hisham.khartabil@nokia.com wrote:
>Can the proxy challenge with all its realms? I really don't believe you can trust the UA supplying the realm it belongs to.

What is the security concern?

Think of it like about when you log on at your PC -- of course
uid is first supplied by user. The point is it is only accepted
if the password for that uid is good.

-Jiri 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 10:50:16 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27953
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 10:50:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24G0md15078
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 11:00:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24G0mp15075
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 11:00:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27929
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 10:49:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24G0Cp15037;
	Tue, 4 Mar 2003 11:00:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Fxep14945
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 10:59:40 -0500
Received: from fox.iptel.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27889
	for <sipping@ietf.org>; Tue, 4 Mar 2003 10:48:37 -0500 (EST)
Received: from jku07.fokus.fraunhofer.de (port-212-202-200-46.reverse.qdsl-home.de [212.202.200.46])
	by fox.iptel.org (8.11.6/8.11.6) with ESMTP id h24Fo3J22055;
	Tue, 4 Mar 2003 16:50:03 +0100
Message-Id: <5.2.0.9.0.20030304164221.030f6ec8@mailhost.fokus.gmd.de>
X-Sender: jku@mailhost.fokus.gmd.de (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 04 Mar 2003 16:47:01 +0100
To: hisham.khartabil@nokia.com, <jh@lohi.eng.song.fi>
From: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <stu.jacobs@labs.gte.com>, <mankin@psg.com>,
        <Jari.Arkko@lmf.ericsson.se>
In-Reply-To: <2038BCC78B1AD641891A0D1AE133DBB7FE72FF@esebe019.ntc.nokia.
 com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

At 04:06 PM 3/3/2003, hisham.khartabil@nokia.com wrote:
>I was offering a solution to your problem in the form of a question. Here it is again in the form of a suggestion:
>
>If your poxy supports multiple realms on the same interface, then it can challenge with all the realms and therefore the UA does not have to supply the realm to the proxy.

As Juha said, interfaces are unrelated to digest authentication.

I suspect that your solution is not usable. I really do not want to dump 
as many challenges in responses as  number of domains I server (1000?)

-Jiri 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 11:17:39 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29037
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 11:17:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24GSBQ17460
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 11:28:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24GSBp17457
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 11:28:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29027
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 11:17:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24GRVp17429;
	Tue, 4 Mar 2003 11:27:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24GO6p17242
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 11:24:06 -0500
Received: from fox.iptel.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28894
	for <sipping@ietf.org>; Tue, 4 Mar 2003 11:13:02 -0500 (EST)
Received: from jku07.fokus.fraunhofer.de (port-212-202-200-46.reverse.qdsl-home.de [212.202.200.46])
	by fox.iptel.org (8.11.6/8.11.6) with ESMTP id h24GERJ22368;
	Tue, 4 Mar 2003 17:14:27 +0100
Message-Id: <5.2.0.9.0.20030304164739.04263098@mailhost.fokus.gmd.de>
X-Sender: jku@mailhost.fokus.gmd.de (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 04 Mar 2003 17:11:31 +0100
To: hisham.khartabil@nokia.com, <jh@lohi.eng.song.fi>
From: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Cc: <Gonzalo.Camarillo@lmf.ericsson.se>, <BeckW@t-systems.com>,
        <sipping@ietf.org>, <stu.jacobs@labs.gte.com>, <mankin@psg.com>,
        <Jari.Arkko@lmf.ericsson.se>
In-Reply-To: <2038BCC78B1AD641891A0D1AE133DBB7FE7300@esebe019.ntc.nokia.
 com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

At 04:22 PM 3/3/2003, hisham.khartabil@nokia.com wrote:
>I think you exaggerating here with several hundreds, but anyway, I was suggesting several hundreds of proxy-authenticate headers. Of course you can scale your network to be better than that. I'm trying to find a solution that doesn't rely on the UA to send its realm (You haven't objected to that yet).
>
>/Hisham

First of all, as said previously, live with realms from UAC. They
are as trustworthy as user's id -- all is supplied by user and what
really matters is whether the credentials are ok. (And again, forget
interfaces, please.)

The real questions is whether to authenticate at all, and if so
which realm the server should use to challenge.

Let me give an example. A proxy maintains a policy which is 
a no relaying: drop requests which neither have my domain 
  in r-uri nor have my domain in From
b verify from: if request originator claims to be a part of
  my domain in From of a request, authenticate
c watch all: sessions are record-routed

Scenario:
1) a@other calls b@other which gets forwarded to b@mine
2) b@mine sends a BYE, it looks like:

BYE sip:originator@1.2.3.4
From: b@other
To: a@other
Route: <proxy@mine;lr>

What will you do now? Well with the policy above you would drop
it (point a). If you are smarter, you will see your Route and
infer "that's my Route, I must have accepted the previous INVITE"
and will not drop it. The questions are now:
- should you authenticate? (remember, you can't authenticate
  request originators from other domains)
- if so, with what realm
- how far can you trust the information in Route (actually, not at all)

-Jiri 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 12:29:39 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02647
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 12:29:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24HeDM25245
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 12:40:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24HeDp25242
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 12:40:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02622
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 12:29:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24HdNp25137;
	Tue, 4 Mar 2003 12:39:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24HcAp25082
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 12:38:10 -0500
Received: from mail1.mediatrix.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02544
	for <sipping@ietf.org>; Tue, 4 Mar 2003 12:27:04 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Received:  from www1.ietf.org ([132.151.1.50]) by mail1.mediatrix.com with Microsoft SMTPSVC(5.0.2195.4905); Thu, 29 Aug 2002 16:41:27 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Received:  from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7TK5Io03056; Thu, 29 Aug 2002 16:05:18 -0400
Received:  from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7TJxVo02866 for <sipping@optimus.ietf.org>; Thu, 29 Aug 2002 15:59:31 -0400
Received:  from mail.mediatrix.com (mail.mediatrix.com [66.129.134.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08880 for <sipping@ietf.org>; Thu, 29 Aug 2002 15:57:56 -0400 (EDT)
Received:  by MAIL with Internet Mail Service (5.5.2650.21) id <QSPWCQAH>; Thu, 29 Aug 2002 15:59:26 -0400
content-class: urn:content-classes:message
Subject: [Sipping] Media descriptor problem in SDP
Date: Tue, 4 Mar 2003 12:29:03 -0500
Message-ID: <2702075D4DE2B043BF5EB82E9CFAD45B4ED1AF@mail1.mediatrix.com>
Thread-Topic: [Sipping] Questions regarding the draft-ietf-sipping-realtimefax-00.txt
Thread-Index: AcJPnHJuVzKl3H9iTuuRhUCxZWEgPw==
From: "Louis Guindon" <lguindon@mediatrix.com>
To: <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h24HcAp25083
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

We are receiving the following SDP with an INVITE...
  m=audio 5004 RTP/AVP 8 8
  a=fmtp:8 ptime:20
  a=fmtp:8 ptime:30
  a=sendrecv
  a=ptime:20

After looking in the RFC2327 ABNF for those fields, I cannot find any problem with the grammar. However, it's doesn't make sense to me that we can put the media format twice on the media announcements line. Moreover, it doesn't make more sense to put two attribut for the same media format with different parameters.

Any idea where I can find about the validity/invadility of SDP packet? 

Regards,

Louis Guindon
Software Design Engineer
Mediatrix Telecom, Inc.
lguindon@mediatrix.com
Tel :  819-829-8749 ext. 242
Fax : 819-829-1973
4229, Garlock Street
Sherbrooke, Qc J1L 2C8

This message and its attachment(s) contain protected proprietary and
confidential information of Mediatrix.  It is intended solely for the
named addressee(s).  If you are not an addressee indicated in this message
(or responsible for delivery of the message to an addressee), you may not
copy or deliver this message or its attachment(s) to anyone.  Rather, you
should permanently delete this message and its attachment(s) and kindly
notify the sender by email.  No warranty is made that the email or
attachment(s) are free from computer virus or other defect.
 
Ce message et son(ses) fichier(s) adjoint(s) peuvent contenir de
l'information légale privilégiée ou confidentielle de Mediatrix.  Il est
destiné exclusivement au(x) destinataire(s) identifié(s).  Si vous n'êtes
pas un destinataire indiqué dans ce message (ou responsable de la
livraison du message au destinataire), vous ne pouvez copier ou livrer ce
message ou son(ses) fichier(s) adjoint(s) à quiconque.  Vous devriez
plutôt effacer de façon permanente ce message et son(ses) fichier(s)
adjoint(s) et aimablement en avertir l'expéditeur par courriel.  Aucune
garantie n'est donnée que ce courriel ou son(ses) fichier(s) adjoint(s) ne
contiennent pas de virus informatique ou autre défectuosité. 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 13:21:44 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04446
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 13:21:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24IWJQ01941
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 13:32:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24IWJ501938
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 13:32:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04436
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 13:21:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24IVM501876;
	Tue, 4 Mar 2003 13:31:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24ISv501769
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 13:28:57 -0500
Received: from zrc2s0jx.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04382
	for <sipping@ietf.org>; Tue, 4 Mar 2003 13:17:51 -0500 (EST)
Received: from zsc3c028.us.nortel.com (zsc3c028.us.nortel.com [47.81.138.28])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h24IJVr11382;
	Tue, 4 Mar 2003 12:19:32 -0600 (CST)
Received: by zsc3c028.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1LW225HR>; Tue, 4 Mar 2003 10:19:32 -0800
Message-ID: <2F1FC1DEA077D5119FAD00508BCFD6D206F5AF7D@zsc3c030.us.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Tue, 4 Mar 2003 10:19:30 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E27A.99502890"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E27A.99502890
Content-Type: text/plain

Agreed. I just think that mixing two ringing patterns may yield
unpredictable
results. It can be done, but I'm a bit sceptical that phone manufacturers
will
actually do this.

But, as you say, this is just a suggestion, so I don't have any real problem
with the current draft.

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se] 
> Sent: Tuesday, March 04, 2003 3:21 AM
> To: Audet, Francois [SC100:4K02:EXCH]
> Cc: 'sipping'
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Francois,
> 
> Thanks for the feedback.
> 
> About your suggestion, the paragraph you are referring to 
> does not recommend any particular behaviour. It only says 
> that one possible choice is mixing them. I do not think that 
> we need to list all possible things a gateway could do in 
> that case. I believe that the reader gets the idea by reading 
> the paragraph as it is (i.e., there are multiple behaviours 
> to choose from).

------_=_NextPart_001_01C2E27A.99502890
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Agreed. I just think that mixing two ringing patterns =
may yield unpredictable</FONT>
<BR><FONT SIZE=3D2>results. It can be done, but I'm a bit sceptical =
that phone manufacturers will</FONT>
<BR><FONT SIZE=3D2>actually do this.</FONT>
</P>

<P><FONT SIZE=3D2>But, as you say, this is just a suggestion, so I =
don't have any real problem</FONT>
<BR><FONT SIZE=3D2>with the current draft.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Tuesday, March 04, 2003 3:21 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Audet, Francois [SC100:4K02:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'sipping'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Francois,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks for the feedback.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; About your suggestion, the paragraph you are =
referring to </FONT>
<BR><FONT SIZE=3D2>&gt; does not recommend any particular behaviour. It =
only says </FONT>
<BR><FONT SIZE=3D2>&gt; that one possible choice is mixing them. I do =
not think that </FONT>
<BR><FONT SIZE=3D2>&gt; we need to list all possible things a gateway =
could do in </FONT>
<BR><FONT SIZE=3D2>&gt; that case. I believe that the reader gets the =
idea by reading </FONT>
<BR><FONT SIZE=3D2>&gt; the paragraph as it is (i.e., there are =
multiple behaviours </FONT>
<BR><FONT SIZE=3D2>&gt; to choose from).</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E27A.99502890--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 14:15:33 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06105
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 14:15:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24JQ9X05930
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 14:26:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24JQ9505925
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 14:26:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06099
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 14:15:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24JPK505886;
	Tue, 4 Mar 2003 14:25:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24JOJ505838
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 14:24:19 -0500
Received: from ihemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06054
	for <sipping@ietf.org>; Tue, 4 Mar 2003 14:13:12 -0500 (EST)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by ihemail2.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h24JFEB18251
	for <sipping@ietf.org>; Tue, 4 Mar 2003 14:15:14 -0500 (EST)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2653.19)
	id <1H3RFRS7>; Tue, 4 Mar 2003 13:15:13 -0600
Message-ID: <DBC3D7D0A071F743AE0767C9C6071EDA0482BBBD@il0015exch010u.ih.lucent.com>
From: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Tue, 4 Mar 2003 13:15:13 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Gonzalo,
Thanks for your response.  I understand and agree with your concerns about race conditions as well as the discussion of how to handle them.  But I do not want the UAS to blindly control when the UAC should apply local ringing.  I want the UAS to be able to indicate when the UAC should NOT apply local ringing.  There is a very important distinction here.  According to your draft, when a UAC receives a 180 it should be prepared to generate local ringing, and it is a matter of local policy what the UAC should do when there is concurrent in-band media.  Gateway resources should be allocated to detect in-band media and decide whether or not to generate ringing.  But under some circumstances the UAS knows that call progress information is available in-band and the UAC does not need to bother to allocate extra resources to monitor the media flow and optionally inject ringing.  I believe it is important for a UAS to be able to indicate this situation to a UAC.  These are processing !
resources that could be put to use elsewhere.  There are no race conditions in this situation - only the recognition that local ringing and packet detection are unnecessary.

I stand by my original suggestion and continue to request a modest addition to your draft based on this general approach (my previous email indicates one possible detailed solution).  Please let me know if you see any further issues.

Regards,
Richard Ejzak
Lucent Technologies



-----Original Message-----
From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
Sent: Tuesday, March 04, 2003 5:42 AM
To: Ejzak, Richard P (Richard)
Cc: sipping
Subject: Re: [Sipping] New version of the early media draft


Ejzak,

the main problem with any SIP-layer mechanism that allows the UAS to
tell the UAC whether local ringback has to be generated or not is race
conditions. It really does not matter whether you use an Alert-Info
header field in a reponse, or a special status code, or a special body,
or whatever to signal it. You always have race conditions.

Let's say that the UAS tells the UAC to generate local ringback. After a
while, the callee picks up. The UAS sends back a 200 OK and starts
sending media. The 200 OK, for some reason, arrives much later than the
first media packets... what is the UAC supposed to do in the mean time?
Ignore the media? Play the media anyway?

Another scenario. The UAC starts receiving media before a provisional
response is received... what does it have to do?

The main point is that, since signalling and media are loosely
synchronized, you will always have race conditions and you will have to
make guesses about what to do during those race conditions anyway.

Thanks,

Gonzalo



"Ejzak, Richard P (Richard)" wrote:
> 
> Gonzalo,
> It seems the single greatest difficulty with the gateway model (as you point out in your draft) is the difficulty of depending on the arrival of media packets to determine whether or not to generate local ringing.  I have previously (last summer) suggested a solution to this (use 180 exclusively to indicate that local ringing should override any inband media and 183 otherwise) that is unacceptable since it does not satisfy the requirement that 180 be used to indicate alerting of the called party.
> 
> Have you considered using the Alert-Info header in the following way? Since the real problem is that we would like to be able to discriminate between cases when 180 should cause local ringing and when 180 should not (since inband media is available), and it is the UAS that knows conclusively which case applies, let's agree on an encoding of the Alert-Info header that indicates that local ringing should not be applied.  The following line is a syntactically valid header:
> 
> Alert-Info: <data:,>
> 
> This header identifies the Alert-Info as the null string, which seems unambiguously and efficiently interpretable within a 180 response as "do not play local ringing even though the called party is being alerted."  If the UAC does not recognize it or chooses not to interpret it for security reasons, it can be safely ignored.
> 
> This modest addition to your draft (or an equivalent mechanism) would make it unnecessary for the gateway model to depend on local policy or incoming media packet detection and is completely consistent with all of the constraints you have documented.
> 
> Another approach may be to actually specify the rtp stream as the source of the alert info (although this would require the definition of a new URI scheme type).  It might look like:
> 
> Alert-Info: <rtp:/12.34.56.78:90>
> 
> where the Alert-Info specifies the address and port of the rtp stream.  I don't like this mechanism since it is redundant with SDP and prone to error.  It is also ambiguous in the event of any subsequent media change using UPDATE (Do I begin to generate local ringing if the rtp stream source address changes?  Or do I continue to listen to the address specified in the Alert-Info and ignore any UPDATEs?  No to both.)
> 
> May I suggest including such a mechanism (preferably the first one) in your draft.
> 
> Richard Ejzak
> Lucent Technologies
> 
> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: Monday, February 10, 2003 5:41 AM
> To: sipping
> Subject: [Sipping] New version of the early media draft
> 
> Folks,
> 
> I have just sumitted a new version of the early media draft. Until it
> appears in the archives, you can fetch it from:
> 
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-early-media-01.txt
> 
> I have included all the (long and useful) discussions we had in the
> mailing list. Therefore, the draft now keeps separate the "gateway" and
> the "application server" models. I have also removed the parts we did
> not agree on.
> 
> Feedback is, as usual, appreciated.
> 
> Thanks,
> 
> Gonzalo
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 14:43:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07055
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 14:43:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24JrsQ07921
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 14:53:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Jrs507918
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 14:53:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07038
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 14:42:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24JrB507888;
	Tue, 4 Mar 2003 14:53:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Jq7507847
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 14:52:07 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06985
	for <sipping@ietf.org>; Tue, 4 Mar 2003 14:41:00 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h24JgJC05625;
	Tue, 4 Mar 2003 19:42:19 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JRG0W>; Tue, 4 Mar 2003 14:42:23 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214EA7@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'jh@lohi.eng.song.fi'" <jh@lohi.eng.song.fi>, aki.niemi@nokia.com
Cc: hisham.khartabil@nokia.com, Gonzalo.Camarillo@lmf.ericsson.se,
        BeckW@t-systems.com, sipping@ietf.org, stu.jacobs@labs.gte.com,
        mankin@psg.com, Jari.Arkko@lmf.ericsson.se
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Date: Tue, 4 Mar 2003 14:42:20 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

A couple of notes about Digest and realms in SIP.

RFC3261 differs from RFC2617 in that it recommends hostname-based realm
names (well, RFC2617 does recommend this in some places, but
inconsistently). In other words, the name of a realm corresponds to a valid
hostname of the challenging UAS or proxy server.

The reason we did this is to make realm names unique. There could be realm
conflicts, where two proxies inadvertantly use the same realm name, that
could have confusing results for user agents. But also, if realm names are
arbitrary (like "foo"), then essentially any proxy server can challenge for
any realm. A malicious proxy that can anticipate the realm in which a UA
would like to authenticate can issue a challenge for that realm, essentially
posing as that proxy server; there are some possible credential-analysis
attacks that can arise from this. 

Tying the realm name to a hostname of the proxy server allows us to use
transport or network-layer authentication to ensure that the right proxy is
challenging with the right realm. When a UA connects to a proxy with TLS, it
can compare the subject of the certificate returned by TLS with the realm
name of a challenge. RFC3261 currently has language about this comparison
(see 26.3.2.1, for example).

This might initially seem to limit each proxy server to one realm, which
would be problematic, especially because some proxy servers have multiple
hostnames. However, this is a known problem for TLS in HTTP cases, and there
is a TLS-specific solution today. The TLS extensions draft defines a
'server_name' extension to the TLS HELLO message that allows the client to
say which hostname, of many possible virtual hosts at a single address, it
intends to connect to. Effectively, by choosing the hostname, in the SIP
case this would also choose the realm. See: 

http://www.ietf.org/internet-drafts/draft-ietf-tls-extensions-06.txt

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: jh@lohi.eng.song.fi [mailto:jh@lohi.eng.song.fi]
> Sent: Tuesday, March 04, 2003 12:33 AM
> To: aki.niemi@nokia.com
> Cc: hisham.khartabil@nokia.com; Gonzalo.Camarillo@lmf.ericsson.se;
> BeckW@t-systems.com; sipping@ietf.org; stu.jacobs@labs.gte.com;
> mankin@psg.com; Jari.Arkko@lmf.ericsson.se
> Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
> 
> 
> aki.niemi@nokia.com writes:
> 
>  > Digest authenticates the username,
>  > not the From field - these may not be exactly the same.
> 
> i have never claimed that digest authenticates the from field, but in
> case of an initial request, the proxy can get the realm to be used in
> its challenge from the from field.  in subsequent requests this is not
> anymore possible.
> 
>  > This feature of blind challenges in digest has proven problematic
>  > before, and I agree that it would be nice if there was an EAP
>  > Identity request/response -type mechanism available in 
> Digest. But it
>  > isn't an easy add-on.
> 
> we don't need an eap style identity request/response.  what we need is
> an ability for the ua to tell in its requests to the proxy 
> the realm it
> claims to belong to so that the proxy can correctly challenge 
> it.  this
> can be easily fixed with a single new header or parameter.
> 
> -- juha
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 15:11:10 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08589
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 15:11:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24KLle10108
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 15:21:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24KLl510105
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 15:21:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08554
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 15:10:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24KLA510070;
	Tue, 4 Mar 2003 15:21:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24KKq510014
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 15:20:52 -0500
Received: from dgesmtp02.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08454
	for <sipping@ietf.org>; Tue, 4 Mar 2003 15:09:43 -0500 (EST)
Received: from pmismtp01.wcomnet.com ([166.38.62.36])
 by firewall.wcom.com (Iplanet MTA )
 with ESMTP id <0HB800B1RQRM3J@firewall.wcom.com> for sipping@ietf.org; Tue,
 04 Mar 2003 20:11:46 +0000 (GMT)
Received: from pmismtp01.wcomnet.com by pmismtp01.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HB800E01QRLXG@pmismtp01.wcomnet.com>; Tue,
 04 Mar 2003 20:11:46 +0000 (GMT)
Received: from ajohnston.wcom.com ([166.50.107.46])
 by pmismtp01.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HB800DFRQRJBA@pmismtp01.wcomnet.com>; Tue,
 04 Mar 2003 20:11:45 +0000 (GMT)
Date: Tue, 04 Mar 2003 14:11:29 -0600
From: Alan Johnston <alan.johnston@wcom.com>
In-reply-to: <NIEFLFDIBJCPCKAMIGBPOEGLCFAA.vkenneally@cit.ie>
X-Sender: Alan.Johnston@pop.mcit.com
To: vkenneally@cit.ie, sipping@ietf.org
Cc: sdonovan@dynamicsoft.com, rsparks@dynamicsoft.com,
        ccunningham@dynamicsoft.com, kevin.summers@sonusnet.com
Message-id: <5.1.1.6.0.20030304140821.020efe28@pop.mcit.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset=us-ascii; format=flowed
Subject: [Sipping] Re: [Sip] Question on Basic Call flows document section 3.6
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

(trimmed to the sipping list)

Hi Val,

Thanks for your comments.  In this example, the initial INVITE gets a 
redirect with a Contact URI.  User A then does a DNS lookup on this new URI 
(probably SRV records) which then points to Proxy 3 where the request is 
sent.  There is no pre-loaded Route header involved.

Thanks,
Alan Johnston
WorldCom
sip:alan@digitalari.com

At 03:41 PM 3/4/2003 +0000, Valerie Kenneally wrote:
>Hi All,
>
>         In document at the below link
>
>http://www.ietf.org/internet-drafts/draft-ietf-sipping-basic-call-flows-01.t
>xt
>section 3.6 "Session via Redirect and Proxy Servers with the SDP in ACK".
>
>I am wondering if someone can explain to me how the INVITE (F4) is directed
>from User A to Proxy 3 without any Route header being included in the
>message.
>
>I have been trying to figure this out for a while and I'd really appreciate
>any feedback asap
>
>Thanks in advance,
>Val
>
>------------------------
>Val Kenneally,
>Post-Graduate,
>Electronic Eng. Dept.,
>CIT,
>Rossa Ave.,
>Bishopstown,
>Cork,
>Ireland.
>------------------------
>Tel: +353 87 2273668
>Fax: +353 21 4326625
>
>
>-------------------Legal  Disclaimer---------------------------------------
>
>The above electronic mail transmission is confidential and intended only 
>for the person to whom it is addressed. Its contents may be protected by 
>legal and/or professional privilege. Should it be received by you in error 
>please contact the sender at the above quoted email address. Any 
>unauthorised form of reproduction of this message is strictly prohibited. 
>The Institute does not guarantee the security of any information 
>electronically transmitted and is not liable if the information contained 
>in this communication is not a proper and complete record of the message 
>as transmitted by the sender nor for any delay in its receipt.
>
>----------------------------------------------------------------------------------------
>
>_______________________________________________
>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sipping@ietf.org for new developments on the application of sip

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 15:46:27 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09946
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 15:46:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24Kv5B12896
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 15:57:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Kv5512893
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 15:57:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09925
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 15:45:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24KuR512820;
	Tue, 4 Mar 2003 15:56:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24KtE512762
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 15:55:14 -0500
Received: from lohi.eng.song.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09885
	for <sipping@ietf.org>; Tue, 4 Mar 2003 15:44:05 -0500 (EST)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.36 #1 (Debian))
	id 18qJIY-0003cH-00; Tue, 04 Mar 2003 22:46:02 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15973.4234.597537.651256@harjus.eng.song.fi>
Date: Tue, 4 Mar 2003 22:46:02 +0200
To: "Peterson, Jon" <jon.peterson@neustar.biz>
Cc: aki.niemi@nokia.com, hisham.khartabil@nokia.com,
        Gonzalo.Camarillo@lmf.ericsson.se, BeckW@t-systems.com,
        sipping@ietf.org, stu.jacobs@labs.gte.com, mankin@psg.com,
        Jari.Arkko@lmf.ericsson.se
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
In-Reply-To: <15A2739B7DAA624D8091C65981D7DA8101214EA7@stntexch2.va.neustar.com>
References: <15A2739B7DAA624D8091C65981D7DA8101214EA7@stntexch2.va.neustar.com>
X-Mailer: VM 7.07 under Emacs 21.2.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Peterson, Jon writes:

 > The TLS extensions draft defines a
 > 'server_name' extension to the TLS HELLO message that allows the client to
 > say which hostname, of many possible virtual hosts at a single address, it
 > intends to connect to. Effectively, by choosing the hostname, in the SIP
 > case this would also choose the realm.

this seems to solve what i have been asking for, i.e., allowing the
client to tell to the proxy, which realm it belongs to.

the only problem is that today there exist very few UAs and proxies on
the market that implement TLS.

-- juha

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 16:14:05 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10676
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 16:14:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h24LOhH14915
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 16:24:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24LOh514912
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 16:24:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10668
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 16:13:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24LOB514878;
	Tue, 4 Mar 2003 16:24:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24LNH514818
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 16:23:17 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10632
	for <sipping@ietf.org>; Tue, 4 Mar 2003 16:12:08 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h24LDYC08369;
	Tue, 4 Mar 2003 21:13:34 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JR2B2>; Tue, 4 Mar 2003 16:13:38 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214EB0@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'jh@lohi.eng.song.fi'" <jh@lohi.eng.song.fi>
Cc: aki.niemi@nokia.com, hisham.khartabil@nokia.com,
        Gonzalo.Camarillo@lmf.ericsson.se, BeckW@t-systems.com,
        sipping@ietf.org, stu.jacobs@labs.gte.com, mankin@psg.com,
        Jari.Arkko@lmf.ericsson.se
Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
Date: Tue, 4 Mar 2003 16:13:37 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Understood, but I'd like to stress that TLS provides a very important
property to the Digest authentication process - being able to correlate the
realm with the certificate of the proxy is very valuable from a security
perspective. I wouldn't go so far as to say that Digest authentication is
useless without this property... but it is weakened. The two are best used
in concert. I hope that properties like this will encourage the further
deployment of TLS.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: jh@lohi.eng.song.fi [mailto:jh@lohi.eng.song.fi]
> Sent: Tuesday, March 04, 2003 12:46 PM
> To: Peterson, Jon
> Cc: aki.niemi@nokia.com; hisham.khartabil@nokia.com;
> Gonzalo.Camarillo@lmf.ericsson.se; BeckW@t-systems.com;
> sipping@ietf.org; stu.jacobs@labs.gte.com; mankin@psg.com;
> Jari.Arkko@lmf.ericsson.se
> Subject: RE: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
> 
> 
> Peterson, Jon writes:
> 
>  > The TLS extensions draft defines a
>  > 'server_name' extension to the TLS HELLO message that 
> allows the client to
>  > say which hostname, of many possible virtual hosts at a 
> single address, it
>  > intends to connect to. Effectively, by choosing the 
> hostname, in the SIP
>  > case this would also choose the realm.
> 
> this seems to solve what i have been asking for, i.e., allowing the
> client to tell to the proxy, which realm it belongs to.
> 
> the only problem is that today there exist very few UAs and proxies on
> the market that implement TLS.
> 
> -- juha
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar  4 18:50:11 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15835
	for <sipping-archive@odin.ietf.org>; Tue, 4 Mar 2003 18:50:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2500sB25385
	for sipping-archive@odin.ietf.org; Tue, 4 Mar 2003 19:00:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2500s525382
	for <sipping-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 19:00:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15816
	for <sipping-web-archive@ietf.org>; Tue, 4 Mar 2003 18:49:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2500J525366;
	Tue, 4 Mar 2003 19:00:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Nxe525288
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 18:59:40 -0500
Received: from gamma.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15805;
	Tue, 4 Mar 2003 18:48:25 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id h24NoSZ13242;
	Tue, 4 Mar 2003 15:50:28 -0800 (PST)
Message-Id: <200303042350.h24NoSZ13242@gamma.isi.edu>
To: IETF-Announce: ;
Cc: rfc-editor@rfc-editor.org, sipping@ietf.org, sip@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 04 Mar 2003 15:50:28 -0800
Subject: [Sipping] RFC 3485 on The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


--NextPart


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


        RFC 3485

        Title:      The Session Initiation Protocol (SIP) and Session
                    Description Protocol (SDP) Static Dictionary for
                    Signaling Compression (SigComp)
        Author(s):  M. Garcia-Martin, C. Bormann, J. Ott, R. Price,
                    A. B. Roach
        Status:     Standards Track
        Date:       February 2003
        Mailbox:    miguel.a.garcia@ericsson.com, cabo@tzi.org,
                    jo@tzi.org, richard.price@roke.co.uk,
                    adam@dynamicsoft.com
        Pages:      30
        Characters: 80195
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sipping-sigcomp-sip-dictionary-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3485.txt


The Session Initiation Protocol (SIP) is a text-based protocol for
initiating and managing communication sessions.  The protocol can be
compressed by using Signaling Compression (SigComp).  Similarly, the
Session Description Protocol (SDP) is a text-based protocol intended
for describing multimedia sessions for the purposes of session
announcement, session invitation, and other forms of multimedia
session initiation.  This memo defines the SIP/SDP-specific static
dictionary that SigComp may use in order to achieve higher efficiency.
The dictionary is compression algorithm independent.

This document is a product of the Session Initiation Proposal
Investigation Working Group and the Session Initiation Working Group
of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

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

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

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

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <030304154731.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3485

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc3485.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <030304154731.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 04:25:55 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22576
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 04:25:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h259anA07826
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 04:36:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h259an507823
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 04:36:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22566
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 04:25:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h259aC507791;
	Wed, 5 Mar 2003 04:36:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h259YV507719
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 04:34:31 -0500
Received: from alaska.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22507
	for <sipping@ietf.org>; Wed, 5 Mar 2003 04:23:05 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by alaska.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h259P70i023333;
	Wed, 5 Mar 2003 10:25:07 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5W9JA01; Wed, 5 Mar 2003 10:25:07 +0100
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.31.83])
	by hendrix.lmf.ericsson.se (8.12.6/8.12.6/lmf-2.1-jcs) with ESMTP id h259P6En000538;
	Wed, 5 Mar 2003 11:25:06 +0200 (EET)
Message-ID: <3E65C271.6A0426A3@lmf.ericsson.se>
Date: Wed, 05 Mar 2003 11:25:05 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] New version of netann
References: <4A3384433CE2AB46A63468CB207E209D248851@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi Eric,

I haven't had time to look at the new version of the draft yet, but I'd like to comment my comments :)

> "Early" URI Parameter
> =====================
> Christer Holmberg pointed out his preference for coming up with a generic "this session is early" mechanism.  At this time, I'm not sure that this is something that occurs in other situations.  Given that, we've left in the early parameter.

[CHH] I think that early media DO occur in other situations (at least in PSTN interworking). At least I assume so, since there has been much discussion about it lately...

> I would agree that the UAC might not support early media.  However, the onus would be on the proxy, not the media server, to enforce 100rel.  If the UAC doesn't support 100rel, then the proxy should request it.

[CHH] Do you mean that the proxy is going to insert Require: 100rel in the request, then handle the sending of PRACK, and make sure that retransmissions of 18x messages received by that proxy aren't forwarded back to the UAC, etc etc?

Or, do you mean that the proxy will send a 421 Extension Required response back to the UAC?

Regards,

Christer Holmberg
Ericsson Finland


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 05:40:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24392
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 05:40:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25ApDk13163
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 05:51:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25ApD513160
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 05:51:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24385
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 05:39:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25AoQ513135;
	Wed, 5 Mar 2003 05:50:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25AnY513092
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 05:49:34 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24338
	for <sipping@ietf.org>; Wed, 5 Mar 2003 05:38:07 -0500 (EST)
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h25Ae9B3001964;
	Wed, 5 Mar 2003 11:40:09 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id FDVM1NTC; Wed, 5 Mar 2003 11:40:08 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h25Ae77u008352;
	Wed, 5 Mar 2003 12:40:07 +0200 (EET)
Message-ID: <3E65D405.9E31819@lmf.ericsson.se>
Date: Wed, 05 Mar 2003 12:40:05 +0200
X-Sybari-Trust: c4cbcd5b 9ffcebbb a5ee123c 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>
CC: jh@lohi.eng.song.fi, Stuart Jacobs <stu.jacobs@labs.gte.com>,
        Allison Mankin <mankin@psg.com>, sipping@ietf.org
Subject: Re: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
References: <5.1.1.6.0.20030221110917.04229140@pophost.gte.com>
	 <5.1.1.6.0.20030221110917.04229140@pophost.gte.com>
	 <5.2.0.9.0.20030226125028.00b3e288@mailhost.fokus.gmd.de> <5.2.0.9.0.20030304154559.047cd088@mailhost.fokus.gmd.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Jiri,

> The most compelling issue to me now is integrity of Record-Routes. If
> the BYE originator can send a BYE and manipulate RR (e.g.,
> <sip:foo.bar;lr;use_aaa=NO>, it will be obviously useless.

This is ouside of the scope of the requirements. You can force a request
to traverse a certain proxy using different mechanisms. Those mechanisms
are not SIP-AAA specific.

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 05:45:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24586
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 05:45:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25AujD13446
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 05:56:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25Aui513443
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 05:56:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24560
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 05:45:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25Au6513406;
	Wed, 5 Mar 2003 05:56:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25AtT513382
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 05:55:29 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24515
	for <sipping@ietf.org>; Wed, 5 Mar 2003 05:44:02 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h25Ak3pC012855;
	Wed, 5 Mar 2003 11:46:03 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5W9J6AZ; Wed, 5 Mar 2003 11:46:02 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h25Aju7u008759;
	Wed, 5 Mar 2003 12:45:56 +0200 (EET)
Message-ID: <3E65D562.AA4B3C5@lmf.ericsson.se>
Date: Wed, 05 Mar 2003 12:45:54 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>
CC: jh@lohi.eng.song.fi, "Beck01, Wolfgang" <BeckW@t-systems.com>,
        sipping@ietf.org, stu.jacobs@labs.gte.com, mankin@psg.com,
        Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Subject: Re: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
References: <C3F9C806AEC6D5119643000347055E322089AE@G9JNW.mgb01.telekom.de>
	 <15966.1788.184832.423324@harjus.eng.song.fi> <5.2.0.9.0.20030304160754.044e1ea0@mailhost.fokus.gmd.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello,

a proxy can place this type of information in its Record-Route entry.

In Juha's example, the proxy routing the INVITE can notice that the To
field is for 0402345@whatever.com, but the request-URI is Bob@bob.com.
It can add a Record-Route entry that consists of this information
(encrypted with a key, if you want).

The proxy will not have to store state for the call, and will not have
to inspect the From field anymore.

Gonzalo



Jiri Kuthan wrote:
> 
> The issue is that you do not wish to force all requests to authenticate.
> (Your new potential customer could never call you otherwise).
> 
> It is easy to decide which INVITEs to authenticate, it is hard
> to decide which subsequent in-dialog requests to authenticate.
> You no longer know the INVITE r-uri, which might have been
> a key to the policy question "authenticate" or not?".
> 
> -jiri
> 
> At 11:35 AM 2/28/2003, Gonzalo Camarillo wrote:
> >Juha,
> >
> >I still do not quite understand your arguments. Could you please
> >elaborate on why a proxy cannot know that a message comes from a
> >particular UA?
> >
> >Thanks,
> >
> >Gonzalo
> >
> >
> >jh@lohi.eng.song.fi wrote:
> >>
> >> Beck01, Wolfgang writes:
> >>
> >>  > What kind of accounting information do we want to collect: The number
> >>  > > of SIP messages per user? This is possible with an accounting
> >>  > proxy.
> >>
> >> unfortunately not.
> >>
> >> -- juha
> >_______________________________________________
> >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >This list is for NEW development of the application of SIP
> >Use sip-implementors@cs.columbia.edu for questions on current sip
> >Use sip@ietf.org for new developments of core SIP

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 06:37:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26947
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 06:37:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25BmHU17821
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 06:48:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25BmH517818
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 06:48:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26930
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 06:36:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25BlR517732;
	Wed, 5 Mar 2003 06:47:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25BfK516969
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 06:41:20 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25833;
	Wed, 5 Mar 2003 06:29:52 -0500 (EST)
Message-Id: <200303051129.GAA25833@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 05 Mar 2003 06:29:52 -0500
Subject: [Sipping] I-D ACTION:draft-niemi-sipping-event-throttle-reqs-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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


	Title		: Requirements for Limiting the Rate of Event 
                          Notifications
	Author(s)	: A. Niemi
	Filename	: draft-niemi-sipping-event-throttle-reqs-01.txt
	Pages		: 9
	Date		: 2003-3-4
	
All event packages are required to specify a maximum rate at which
event notifications are generated by a single notifier.  Such a limit
is provided in order to reduce network congestion.  In addition to
the fixed limits introduced by specific event packages, further
mechanisms for limiting the rate of event notification are also
allowed to be defined by event package specifications but none have
been specified so far.  This memo discusses the requirements for a
throttle mechanism that allows a subscriber to further limit the rate
of event notification.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-niemi-sipping-event-throttle-reqs-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-niemi-sipping-event-throttle-reqs-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-niemi-sipping-event-throttle-reqs-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:	<2003-3-4174038.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-niemi-sipping-event-throttle-reqs-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-niemi-sipping-event-throttle-reqs-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-4174038.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 06:52:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27709
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 06:52:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25C3N519093
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 07:03:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25C3N519090
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 07:03:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27700
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 06:51:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25C2S519006;
	Wed, 5 Mar 2003 07:02:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25C1j518934
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 07:01:45 -0500
Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27644
	for <sipping@ietf.org>; Wed, 5 Mar 2003 06:50:16 -0500 (EST)
Received: from EEB174W2Kvk (unverified [157.190.81.172]) by cit.ie
 (Rockliffe SMTPRA 5.2.5) with SMTP id <B0000279792@mail.cit.ie> for <sipping@ietf.org>;
 Wed, 5 Mar 2003 11:39:17 +0000
Reply-To: <vkenneally@cit.ie>
From: "Valerie Kenneally" <vkenneally@cit.ie>
To: <sipping@ietf.org>
Date: Wed, 5 Mar 2003 11:52:27 -0000
Message-ID: <NIEFLFDIBJCPCKAMIGBPCEHDCFAA.vkenneally@cit.ie>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Change of IP mid session and Contact header question
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi All,

	I'm just trying to understand some SIP session scenarios and various
features.  My question is best explained by example

If a session is established using SIP between two endpoints (in a mobile
network) and during the session one of these endpoints moves such that it is
assigned a new ip, is it a MUST that this endpoint send a RE-INVITE with new
Contact information to the other communicating entity?

Thanks in advance,
Val Kenneally


-------------------Legal  Disclaimer---------------------------------------

The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.

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

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 08:34:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29849
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 08:34:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25DjSp26413
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 08:45:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25DjS526410
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 08:45:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29839
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 08:33:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25Diq526383;
	Wed, 5 Mar 2003 08:44:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25DhP526337
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 08:43:25 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29808
	for <sipping@ietf.org>; Wed, 5 Mar 2003 08:31:57 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] New version of netann
Date: Wed, 5 Mar 2003 08:36:10 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D2DF7F9@zoe.office.snowshore.com>
Thread-Topic: [Sipping] New version of netann
Thread-Index: AcLi+W3Y1iqNUPRiQP216e/kaF+jxwAIlSlA
From: "Eric Burger" <eburger@snowshore.com>
To: "Christer Holmberg" <christer.holmberg@lmf.ericsson.se>
Cc: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h25DhP526338
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Inline inline :-)

> Original Message From: Christer Holmberg 
> Hi Eric,
> 
> I haven't had time to look at the new version of the draft 
> yet, but I'd like to comment my comments :)
> 
> > "Early" URI Parameter
> > =====================
> > Christer Holmberg pointed out his preference for coming up 
> with a generic "this session is early" mechanism.  At this 
> time, I'm not sure that this is something that occurs in 
> other situations.  Given that, we've left in the early parameter.
> 
> [CHH] I think that early media DO occur in other situations 
> (at least in PSTN interworking). At least I assume so, since 
> there has been much discussion about it lately...
> 

If we can make this mechanism generic, that would be great.  I don't see how we can figure that out except for an explicit mechanism.

As an explicit mechanism, it could be a parameter or a header.  For some reason I have an aversion to inserting a new header, but I could be convinced to get over that phobia.

> > I would agree that the UAC might not support early media.  
> However, the onus would be on the proxy, not the media 
> server, to enforce 100rel.  If the UAC doesn't support 
> 100rel, then the proxy should request it.
> 
> [CHH] Do you mean that the proxy is going to insert Require: 
> 100rel in the request, then handle the sending of PRACK, and 
> make sure that retransmissions of 18x messages received by 
> that proxy aren't forwarded back to the UAC, etc etc?
> 
> Or, do you mean that the proxy will send a 421 Extension 
> Required response back to the UAC?

The latter (421 Extension Required).  In this case, signaling works :-)
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 09:28:00 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01260
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 09:28:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25Ecxx30489
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 09:38:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25Ecx530486
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 09:38:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01248
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 09:27:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25EcI530454;
	Wed, 5 Mar 2003 09:38:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25EbA530006
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 09:37:10 -0500
Received: from ihemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01220
	for <sipping@ietf.org>; Wed, 5 Mar 2003 09:25:40 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by ihemail2.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h25ERgh13774
	for <sipping@ietf.org>; Wed, 5 Mar 2003 09:27:42 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <XNTCL12B>; Wed, 5 Mar 2003 14:27:40 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EC33@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'vkenneally@cit.ie'" <vkenneally@cit.ie>, sipping@ietf.org
Subject: RE: [Sipping] Change of IP mid session and Contact header questio
	n
Date: Wed, 5 Mar 2003 14:23:29 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Apart from some author drafts using SIP for mobility itself, which are not being progressed by the working group, this question is outside IETF itself. IETF has been working with 3GPP and 3GPP2 on how to put SIP into a mobile environment.

In 3GPP release 5, not only does a new IP address necessitate the use of a new INVITE, it also necessitates the use of a new registration as well.

Normally mobile users retain their PDP context to the GGSN when moving, and therefore retain their IP address, and therefore the issue should not arise. Mobility is handled below the SIP layer.

3GPP2 are using mobile IP instead of GPRS, and therefore the same considerations apply.

Keith

Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 

> -----Original Message-----
> From: Valerie Kenneally [mailto:vkenneally@cit.ie]
> Sent: 05 March 2003 11:52
> To: sipping@ietf.org
> Subject: [Sipping] Change of IP mid session and Contact 
> header question
> 
> 
> Hi All,
> 
> 	I'm just trying to understand some SIP session 
> scenarios and various
> features.  My question is best explained by example
> 
> If a session is established using SIP between two endpoints 
> (in a mobile
> network) and during the session one of these endpoints moves 
> such that it is
> assigned a new ip, is it a MUST that this endpoint send a 
> RE-INVITE with new
> Contact information to the other communicating entity?
> 
> Thanks in advance,
> Val Kenneally
> 
> 
> -------------------Legal  
> Disclaimer---------------------------------------
> 
> The above electronic mail transmission is confidential and 
> intended only for the person to whom it is addressed. Its 
> contents may be protected by legal and/or professional 
> privilege. Should it be received by you in error please 
> contact the sender at the above quoted email address. Any 
> unauthorised form of reproduction of this message is strictly 
> prohibited. The Institute does not guarantee the security of 
> any information electronically transmitted and is not liable 
> if the information contained in this communication is not a 
> proper and complete record of the message as transmitted by 
> the sender nor for any delay in its receipt.
> 
> --------------------------------------------------------------
> --------------------------
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 10:02:47 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02711
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 10:02:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25FDlp01080
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 10:13:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25FDl501077
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 10:13:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02657
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 10:02:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25FCX500832;
	Wed, 5 Mar 2003 10:12:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25FB5500730
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 10:11:05 -0500
Received: from znsgs01r.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02363
	for <sipping@ietf.org>; Wed, 5 Mar 2003 09:59:31 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (europem01.nt.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h25F1Nt25762;
	Wed, 5 Mar 2003 15:01:24 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id FS3M4N2Z; Wed, 5 Mar 2003 15:01:24 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FS39ZS21>; Wed, 5 Mar 2003 15:00:08 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C2C@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Wed, 5 Mar 2003 15:00:03 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E327.E7061D44"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E327.E7061D44
Content-Type: text/plain;
	charset="iso-8859-1"

Gonzalo,

I would support this addition (or something like it - I confess to not
having followed all the details of this thread).

This same problem has come up again and again over the last two years. The
root issue is a distinction between explicit application layer indications
and implicit media layer indications. If the UAC is a distributed system
(e.g. Media Gateway and Media Gateway Controller), then the general model is
that the MG is controlled by the MGC. The MGC has only explicit app. layer
indications to work from - it cannot take actions on the basis of receipt of
not of media packets because it does not see them.

Sure, the MG can report and 'RTP received' event and the MGC can then
instruct it appropriately, but this takes time & I don't think it's
standardised.

So, there should be enough information *in the SIP signalling* for the UAC
to take an intelligent decision on whether to play media or local ringing. I
don't want to prescribe how it takes this decision, but at present there is
information available to the UAS at the SIP layer which is not communicated
to the UAC (at the SIP layer) - namely the availability of in-band media.
This can only result in the UAC taking inappropriate decisions in some
scenarios.

Perhaps we should not be telling the UAC to 'play local ringing' or 'don't
play local ringing', but if the UAS knows there is in-band information, it
should tell the UAC in SIP.

Regards...Mark




> -----Original Message-----
> From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com]
> Sent: 04 March 2003 19:15
> To: 'Gonzalo Camarillo'
> Cc: sipping
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> Gonzalo,
> Thanks for your response.  I understand and agree with your 
> concerns about race conditions as well as the discussion of 
> how to handle them.  But I do not want the UAS to blindly 
> control when the UAC should apply local ringing.  I want the 
> UAS to be able to indicate when the UAC should NOT apply 
> local ringing.  There is a very important distinction here.  
> According to your draft, when a UAC receives a 180 it should 
> be prepared to generate local ringing, and it is a matter of 
> local policy what the UAC should do when there is concurrent 
> in-band media.  Gateway resources should be allocated to 
> detect in-band media and decide whether or not to generate 
> ringing.  But under some circumstances the UAS knows that 
> call progress information is available in-band and the UAC 
> does not need to bother to allocate extra resources to 
> monitor the media flow and optionally inject ringing.  I 
> believe it is important for a UAS to be able to indicate this 
> situation to a UAC.  These are processing !
> resources that could be put to use elsewhere.  There are no 
> race conditions in this situation - only the recognition that 
> local ringing and packet detection are unnecessary.
> 
> I stand by my original suggestion and continue to request a 
> modest addition to your draft based on this general approach 
> (my previous email indicates one possible detailed solution). 
>  Please let me know if you see any further issues.
> 
> Regards,
> Richard Ejzak
> Lucent Technologies
> 
> 
> 
> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: Tuesday, March 04, 2003 5:42 AM
> To: Ejzak, Richard P (Richard)
> Cc: sipping
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Ejzak,
> 
> the main problem with any SIP-layer mechanism that allows the UAS to
> tell the UAC whether local ringback has to be generated or not is race
> conditions. It really does not matter whether you use an Alert-Info
> header field in a reponse, or a special status code, or a 
> special body,
> or whatever to signal it. You always have race conditions.
> 
> Let's say that the UAS tells the UAC to generate local 
> ringback. After a
> while, the callee picks up. The UAS sends back a 200 OK and starts
> sending media. The 200 OK, for some reason, arrives much 
> later than the
> first media packets... what is the UAC supposed to do in the 
> mean time?
> Ignore the media? Play the media anyway?
> 
> Another scenario. The UAC starts receiving media before a provisional
> response is received... what does it have to do?
> 
> The main point is that, since signalling and media are loosely
> synchronized, you will always have race conditions and you 
> will have to
> make guesses about what to do during those race conditions anyway.
> 
> Thanks,
> 
> Gonzalo
> 
> 
> 
> "Ejzak, Richard P (Richard)" wrote:
> > 
> > Gonzalo,
> > It seems the single greatest difficulty with the gateway 
> model (as you point out in your draft) is the difficulty of 
> depending on the arrival of media packets to determine 
> whether or not to generate local ringing.  I have previously 
> (last summer) suggested a solution to this (use 180 
> exclusively to indicate that local ringing should override 
> any inband media and 183 otherwise) that is unacceptable 
> since it does not satisfy the requirement that 180 be used to 
> indicate alerting of the called party.
> > 
> > Have you considered using the Alert-Info header in the 
> following way? Since the real problem is that we would like 
> to be able to discriminate between cases when 180 should 
> cause local ringing and when 180 should not (since inband 
> media is available), and it is the UAS that knows 
> conclusively which case applies, let's agree on an encoding 
> of the Alert-Info header that indicates that local ringing 
> should not be applied.  The following line is a syntactically 
> valid header:
> > 
> > Alert-Info: <data:,>
> > 
> > This header identifies the Alert-Info as the null string, 
> which seems unambiguously and efficiently interpretable 
> within a 180 response as "do not play local ringing even 
> though the called party is being alerted."  If the UAC does 
> not recognize it or chooses not to interpret it for security 
> reasons, it can be safely ignored.
> > 
> > This modest addition to your draft (or an equivalent 
> mechanism) would make it unnecessary for the gateway model to 
> depend on local policy or incoming media packet detection and 
> is completely consistent with all of the constraints you have 
> documented.
> > 
> > Another approach may be to actually specify the rtp stream 
> as the source of the alert info (although this would require 
> the definition of a new URI scheme type).  It might look like:
> > 
> > Alert-Info: <rtp:/12.34.56.78:90>
> > 
> > where the Alert-Info specifies the address and port of the 
> rtp stream.  I don't like this mechanism since it is 
> redundant with SDP and prone to error.  It is also ambiguous 
> in the event of any subsequent media change using UPDATE (Do 
> I begin to generate local ringing if the rtp stream source 
> address changes?  Or do I continue to listen to the address 
> specified in the Alert-Info and ignore any UPDATEs?  No to both.)
> > 
> > May I suggest including such a mechanism (preferably the 
> first one) in your draft.
> > 
> > Richard Ejzak
> > Lucent Technologies
> > 
> > -----Original Message-----
> > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > Sent: Monday, February 10, 2003 5:41 AM
> > To: sipping
> > Subject: [Sipping] New version of the early media draft
> > 
> > Folks,
> > 
> > I have just sumitted a new version of the early media 
> draft. Until it
> > appears in the archives, you can fetch it from:
> > 
> > 
http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-early-m
edia-01.txt
> 
> I have included all the (long and useful) discussions we had in the
> mailing list. Therefore, the draft now keeps separate the "gateway" and
> the "application server" models. I have also removed the parts we did
> not agree on.
> 
> Feedback is, as usual, appreciated.
> 
> Thanks,
> 
> Gonzalo
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Gonzalo,</FONT>
</P>

<P><FONT SIZE=3D2>I would support this addition (or something like it - =
I confess to not having followed all the details of this =
thread).</FONT>
</P>

<P><FONT SIZE=3D2>This same problem has come up again and again over =
the last two years. The root issue is a distinction between explicit =
application layer indications and implicit media layer indications. If =
the UAC is a distributed system (e.g. Media Gateway and Media Gateway =
Controller), then the general model is that the MG is controlled by the =
MGC. The MGC has only explicit app. layer indications to work from - it =
cannot take actions on the basis of receipt of not of media packets =
because it does not see them.</FONT></P>

<P><FONT SIZE=3D2>Sure, the MG can report and 'RTP received' event and =
the MGC can then instruct it appropriately, but this takes time &amp; I =
don't think it's standardised.</FONT></P>

<P><FONT SIZE=3D2>So, there should be enough information *in the SIP =
signalling* for the UAC to take an intelligent decision on whether to =
play media or local ringing. I don't want to prescribe how it takes =
this decision, but at present there is information available to the UAS =
at the SIP layer which is not communicated to the UAC (at the SIP =
layer) - namely the availability of in-band media. This can only result =
in the UAC taking inappropriate decisions in some scenarios.</FONT></P>

<P><FONT SIZE=3D2>Perhaps we should not be telling the UAC to 'play =
local ringing' or 'don't play local ringing', but if the UAS knows =
there is in-band information, it should tell the UAC in SIP.</FONT></P>

<P><FONT SIZE=3D2>Regards...Mark</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Ejzak, Richard P (Richard) [<A =
HREF=3D"mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 04 March 2003 19:15</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Gonzalo Camarillo'</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; Thanks for your response.&nbsp; I understand =
and agree with your </FONT>
<BR><FONT SIZE=3D2>&gt; concerns about race conditions as well as the =
discussion of </FONT>
<BR><FONT SIZE=3D2>&gt; how to handle them.&nbsp; But I do not want the =
UAS to blindly </FONT>
<BR><FONT SIZE=3D2>&gt; control when the UAC should apply local =
ringing.&nbsp; I want the </FONT>
<BR><FONT SIZE=3D2>&gt; UAS to be able to indicate when the UAC should =
NOT apply </FONT>
<BR><FONT SIZE=3D2>&gt; local ringing.&nbsp; There is a very important =
distinction here.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; According to your draft, when a UAC receives a =
180 it should </FONT>
<BR><FONT SIZE=3D2>&gt; be prepared to generate local ringing, and it =
is a matter of </FONT>
<BR><FONT SIZE=3D2>&gt; local policy what the UAC should do when there =
is concurrent </FONT>
<BR><FONT SIZE=3D2>&gt; in-band media.&nbsp; Gateway resources should =
be allocated to </FONT>
<BR><FONT SIZE=3D2>&gt; detect in-band media and decide whether or not =
to generate </FONT>
<BR><FONT SIZE=3D2>&gt; ringing.&nbsp; But under some circumstances the =
UAS knows that </FONT>
<BR><FONT SIZE=3D2>&gt; call progress information is available in-band =
and the UAC </FONT>
<BR><FONT SIZE=3D2>&gt; does not need to bother to allocate extra =
resources to </FONT>
<BR><FONT SIZE=3D2>&gt; monitor the media flow and optionally inject =
ringing.&nbsp; I </FONT>
<BR><FONT SIZE=3D2>&gt; believe it is important for a UAS to be able to =
indicate this </FONT>
<BR><FONT SIZE=3D2>&gt; situation to a UAC.&nbsp; These are processing =
!</FONT>
<BR><FONT SIZE=3D2>&gt; resources that could be put to use =
elsewhere.&nbsp; There are no </FONT>
<BR><FONT SIZE=3D2>&gt; race conditions in this situation - only the =
recognition that </FONT>
<BR><FONT SIZE=3D2>&gt; local ringing and packet detection are =
unnecessary.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I stand by my original suggestion and continue =
to request a </FONT>
<BR><FONT SIZE=3D2>&gt; modest addition to your draft based on this =
general approach </FONT>
<BR><FONT SIZE=3D2>&gt; (my previous email indicates one possible =
detailed solution). </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; Please let me know if you see any further =
issues.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Regards,</FONT>
<BR><FONT SIZE=3D2>&gt; Richard Ejzak</FONT>
<BR><FONT SIZE=3D2>&gt; Lucent Technologies</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Tuesday, March 04, 2003 5:42 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Ejzak, Richard P (Richard)</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Ejzak,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; the main problem with any SIP-layer mechanism =
that allows the UAS to</FONT>
<BR><FONT SIZE=3D2>&gt; tell the UAC whether local ringback has to be =
generated or not is race</FONT>
<BR><FONT SIZE=3D2>&gt; conditions. It really does not matter whether =
you use an Alert-Info</FONT>
<BR><FONT SIZE=3D2>&gt; header field in a reponse, or a special status =
code, or a </FONT>
<BR><FONT SIZE=3D2>&gt; special body,</FONT>
<BR><FONT SIZE=3D2>&gt; or whatever to signal it. You always have race =
conditions.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Let's say that the UAS tells the UAC to =
generate local </FONT>
<BR><FONT SIZE=3D2>&gt; ringback. After a</FONT>
<BR><FONT SIZE=3D2>&gt; while, the callee picks up. The UAS sends back =
a 200 OK and starts</FONT>
<BR><FONT SIZE=3D2>&gt; sending media. The 200 OK, for some reason, =
arrives much </FONT>
<BR><FONT SIZE=3D2>&gt; later than the</FONT>
<BR><FONT SIZE=3D2>&gt; first media packets... what is the UAC supposed =
to do in the </FONT>
<BR><FONT SIZE=3D2>&gt; mean time?</FONT>
<BR><FONT SIZE=3D2>&gt; Ignore the media? Play the media anyway?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Another scenario. The UAC starts receiving =
media before a provisional</FONT>
<BR><FONT SIZE=3D2>&gt; response is received... what does it have to =
do?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The main point is that, since signalling and =
media are loosely</FONT>
<BR><FONT SIZE=3D2>&gt; synchronized, you will always have race =
conditions and you </FONT>
<BR><FONT SIZE=3D2>&gt; will have to</FONT>
<BR><FONT SIZE=3D2>&gt; make guesses about what to do during those race =
conditions anyway.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;Ejzak, Richard P (Richard)&quot; =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; It seems the single greatest difficulty =
with the gateway </FONT>
<BR><FONT SIZE=3D2>&gt; model (as you point out in your draft) is the =
difficulty of </FONT>
<BR><FONT SIZE=3D2>&gt; depending on the arrival of media packets to =
determine </FONT>
<BR><FONT SIZE=3D2>&gt; whether or not to generate local ringing.&nbsp; =
I have previously </FONT>
<BR><FONT SIZE=3D2>&gt; (last summer) suggested a solution to this (use =
180 </FONT>
<BR><FONT SIZE=3D2>&gt; exclusively to indicate that local ringing =
should override </FONT>
<BR><FONT SIZE=3D2>&gt; any inband media and 183 otherwise) that is =
unacceptable </FONT>
<BR><FONT SIZE=3D2>&gt; since it does not satisfy the requirement that =
180 be used to </FONT>
<BR><FONT SIZE=3D2>&gt; indicate alerting of the called party.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Have you considered using the Alert-Info =
header in the </FONT>
<BR><FONT SIZE=3D2>&gt; following way? Since the real problem is that =
we would like </FONT>
<BR><FONT SIZE=3D2>&gt; to be able to discriminate between cases when =
180 should </FONT>
<BR><FONT SIZE=3D2>&gt; cause local ringing and when 180 should not =
(since inband </FONT>
<BR><FONT SIZE=3D2>&gt; media is available), and it is the UAS that =
knows </FONT>
<BR><FONT SIZE=3D2>&gt; conclusively which case applies, let's agree on =
an encoding </FONT>
<BR><FONT SIZE=3D2>&gt; of the Alert-Info header that indicates that =
local ringing </FONT>
<BR><FONT SIZE=3D2>&gt; should not be applied.&nbsp; The following line =
is a syntactically </FONT>
<BR><FONT SIZE=3D2>&gt; valid header:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Alert-Info: &lt;data:,&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; This header identifies the Alert-Info as =
the null string, </FONT>
<BR><FONT SIZE=3D2>&gt; which seems unambiguously and efficiently =
interpretable </FONT>
<BR><FONT SIZE=3D2>&gt; within a 180 response as &quot;do not play =
local ringing even </FONT>
<BR><FONT SIZE=3D2>&gt; though the called party is being =
alerted.&quot;&nbsp; If the UAC does </FONT>
<BR><FONT SIZE=3D2>&gt; not recognize it or chooses not to interpret it =
for security </FONT>
<BR><FONT SIZE=3D2>&gt; reasons, it can be safely ignored.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; This modest addition to your draft (or an =
equivalent </FONT>
<BR><FONT SIZE=3D2>&gt; mechanism) would make it unnecessary for the =
gateway model to </FONT>
<BR><FONT SIZE=3D2>&gt; depend on local policy or incoming media packet =
detection and </FONT>
<BR><FONT SIZE=3D2>&gt; is completely consistent with all of the =
constraints you have </FONT>
<BR><FONT SIZE=3D2>&gt; documented.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Another approach may be to actually =
specify the rtp stream </FONT>
<BR><FONT SIZE=3D2>&gt; as the source of the alert info (although this =
would require </FONT>
<BR><FONT SIZE=3D2>&gt; the definition of a new URI scheme type).&nbsp; =
It might look like:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Alert-Info: =
&lt;rtp:/12.34.56.78:90&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; where the Alert-Info specifies the address =
and port of the </FONT>
<BR><FONT SIZE=3D2>&gt; rtp stream.&nbsp; I don't like this mechanism =
since it is </FONT>
<BR><FONT SIZE=3D2>&gt; redundant with SDP and prone to error.&nbsp; It =
is also ambiguous </FONT>
<BR><FONT SIZE=3D2>&gt; in the event of any subsequent media change =
using UPDATE (Do </FONT>
<BR><FONT SIZE=3D2>&gt; I begin to generate local ringing if the rtp =
stream source </FONT>
<BR><FONT SIZE=3D2>&gt; address changes?&nbsp; Or do I continue to =
listen to the address </FONT>
<BR><FONT SIZE=3D2>&gt; specified in the Alert-Info and ignore any =
UPDATEs?&nbsp; No to both.)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; May I suggest including such a mechanism =
(preferably the </FONT>
<BR><FONT SIZE=3D2>&gt; first one) in your draft.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Richard Ejzak</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Lucent Technologies</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Gonzalo Camarillo [<A HREF=3D"mailto:=
Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson=
.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Monday, February 10, 2003 5:41 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: [Sipping] New version of the =
early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Folks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I have just sumitted a new version of the =
early media </FONT>
<BR><FONT SIZE=3D2>&gt; draft. Until it</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; appears in the archives, you can fetch it =
from:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sip=
ping-early-media-01.txt" =
TARGET=3D"_blank">http://standards.ericsson.net/gonzalo/papers/draft-cam=
arillo-sipping-early-media-01.txt</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I have included all the (long and useful) =
discussions we had in the</FONT>
<BR><FONT SIZE=3D2>&gt; mailing list. Therefore, the draft now keeps =
separate the &quot;gateway&quot; and</FONT>
<BR><FONT SIZE=3D2>&gt; the &quot;application server&quot; models. I =
have also removed the parts we did</FONT>
<BR><FONT SIZE=3D2>&gt; not agree on.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Feedback is, as usual, appreciated.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Sipping mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; This list is for NEW development of the =
application of SIP</FONT>
<BR><FONT SIZE=3D2>&gt; Use sip-implementors@cs.columbia.edu for =
questions on current sip</FONT>
<BR><FONT SIZE=3D2>&gt; Use sip@ietf.org for new developments of core =
SIP</FONT>
</P>

<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT =
SIZE=3D2>Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Sipping mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>This list is for NEW development of the application =
of SIP</FONT>
<BR><FONT SIZE=3D2>Use sip-implementors@cs.columbia.edu for questions =
on current sip</FONT>
<BR><FONT SIZE=3D2>Use sip@ietf.org for new developments of core =
SIP</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E327.E7061D44--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 13:02:08 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17497
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 13:02:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25ICkV03427
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 13:12:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25ICkO03424
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 13:12:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17428
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 13:01:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25IBwO03377;
	Wed, 5 Mar 2003 13:11:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25I7rO03126
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 13:07:53 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16877
	for <sipping@ietf.org>; Wed, 5 Mar 2003 12:56:43 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h25HwjpC026576;
	Wed, 5 Mar 2003 18:58:45 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5XHV8HK; Wed, 5 Mar 2003 18:58:44 +0100
Received: from lmf.ericsson.se (sealwa04-236.sw.ericsson.se [130.100.249.236])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h25HwelW004289;
	Wed, 5 Mar 2003 19:58:41 +0200 (EET)
Message-ID: <3E663ACF.57ACE28D@lmf.ericsson.se>
Date: Wed, 05 Mar 2003 19:58:39 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jiri Kuthan <kuthan@fokus.fraunhofer.de>
CC: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>, jh@lohi.eng.song.fi,
        Stuart Jacobs <stu.jacobs@labs.gte.com>,
        Allison Mankin <mankin@psg.com>, sipping@ietf.org
Subject: Re: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
References: <Pine.SUN.3.91.1030305115712.588A-100000@benetnash>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Jiri,

> On the other hand, general framework/requriements documents should imho
> spell such considerations as they are strongly tied to security of the
> system as a whole.


Yes, I believe that I will add some considerations to the draft. I
believe that it is worthwhile documenting at least some parts of our
discussions.

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 13:26:06 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19911
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 13:26:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25Iajj06068
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 13:36:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25IaiO06065
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 13:36:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19873
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 13:25:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25IZoO05986;
	Wed, 5 Mar 2003 13:35:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25IUvO05338
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 13:30:57 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19177
	for <sipping@ietf.org>; Wed, 5 Mar 2003 13:19:46 -0500 (EST)
Received: from esealnt610.al.sw.ericsson.se (alteon-nat3.sw.ericsson.se [153.88.254.120])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h25ILnpC029650;
	Wed, 5 Mar 2003 19:21:49 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id FD4JAW2A; Wed, 5 Mar 2003 19:21:49 +0100
Received: from lmf.ericsson.se (sealwa04-236.sw.ericsson.se [130.100.249.236])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h25ILjlW005537;
	Wed, 5 Mar 2003 20:21:46 +0200 (EET)
Message-ID: <3E664038.DA439C24@lmf.ericsson.se>
Date: Wed, 05 Mar 2003 20:21:44 +0200
X-Sybari-Trust: 187eb6b1 9ffcebbb 7a95d2f4 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Watson <mwatson@nortelnetworks.com>
CC: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>
Subject: Re: [Sipping] New version of the early media draft
References: <A3C2399B2FACD411A54200508BE39C74054F7C2C@zwcwd00r.europe.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mark,

many of your points have been discussed either in the draft or in the
mailing list before. The MGC-MG decomposition problem is discussed in
the draft, and the indication of the presence in-band media was
discussed in the previous version of the draft.

My initial proposal was to include an SDP parameter that provided
information about the intention of the sender. That is, the sender
intended to send early media... that was seen as too complex (and I
agree with that, by the way).

But using some type of *simpler* mechanism that only indicates that the
UAS does not want the UAC to generate local ringback (like the mechanism
proposed in this thread), would be sensible, IMO. 

How do people feel about using the header field below in a 18x response
to indicate that the UAS would like the UAC not to provide local
ringback (as proposed previously in this thread)?

Alert-Info: <data:,>

To me, once we have defined Alert-Info, this is not an unreasonable
thing to do with this header. Opinions?

Gonzalo


Mark Watson wrote:
> 
> Gonzalo,
> 
> I would support this addition (or something like it - I confess to not
> having followed all the details of this thread).
> 
> This same problem has come up again and again over the last two years.
> The root issue is a distinction between explicit application layer
> indications and implicit media layer indications. If the UAC is a
> distributed system (e.g. Media Gateway and Media Gateway Controller),
> then the general model is that the MG is controlled by the MGC. The
> MGC has only explicit app. layer indications to work from - it cannot
> take actions on the basis of receipt of not of media packets because
> it does not see them.
> 
> Sure, the MG can report and 'RTP received' event and the MGC can then
> instruct it appropriately, but this takes time & I don't think it's
> standardised.
> 
> So, there should be enough information *in the SIP signalling* for the
> UAC to take an intelligent decision on whether to play media or local
> ringing. I don't want to prescribe how it takes this decision, but at
> present there is information available to the UAS at the SIP layer
> which is not communicated to the UAC (at the SIP layer) - namely the
> availability of in-band media. This can only result in the UAC taking
> inappropriate decisions in some scenarios.
> 
> Perhaps we should not be telling the UAC to 'play local ringing' or
> 'don't play local ringing', but if the UAS knows there is in-band
> information, it should tell the UAC in SIP.
> 
> Regards...Mark
> 
> > -----Original Message-----
> > From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com]
> > Sent: 04 March 2003 19:15
> > To: 'Gonzalo Camarillo'
> > Cc: sipping
> > Subject: RE: [Sipping] New version of the early media draft
> >
> >
> > Gonzalo,
> > Thanks for your response.  I understand and agree with your
> > concerns about race conditions as well as the discussion of
> > how to handle them.  But I do not want the UAS to blindly
> > control when the UAC should apply local ringing.  I want the
> > UAS to be able to indicate when the UAC should NOT apply
> > local ringing.  There is a very important distinction here.
> > According to your draft, when a UAC receives a 180 it should
> > be prepared to generate local ringing, and it is a matter of
> > local policy what the UAC should do when there is concurrent
> > in-band media.  Gateway resources should be allocated to
> > detect in-band media and decide whether or not to generate
> > ringing.  But under some circumstances the UAS knows that
> > call progress information is available in-band and the UAC
> > does not need to bother to allocate extra resources to
> > monitor the media flow and optionally inject ringing.  I
> > believe it is important for a UAS to be able to indicate this
> > situation to a UAC.  These are processing !
> > resources that could be put to use elsewhere.  There are no
> > race conditions in this situation - only the recognition that
> > local ringing and packet detection are unnecessary.
> >
> > I stand by my original suggestion and continue to request a
> > modest addition to your draft based on this general approach
> > (my previous email indicates one possible detailed solution).
> >  Please let me know if you see any further issues.
> >
> > Regards,
> > Richard Ejzak
> > Lucent Technologies
> >
> >
> >
> > -----Original Message-----
> > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > Sent: Tuesday, March 04, 2003 5:42 AM
> > To: Ejzak, Richard P (Richard)
> > Cc: sipping
> > Subject: Re: [Sipping] New version of the early media draft
> >
> >
> > Ejzak,
> >
> > the main problem with any SIP-layer mechanism that allows the UAS to
> 
> > tell the UAC whether local ringback has to be generated or not is
> race
> > conditions. It really does not matter whether you use an Alert-Info
> > header field in a reponse, or a special status code, or a
> > special body,
> > or whatever to signal it. You always have race conditions.
> >
> > Let's say that the UAS tells the UAC to generate local
> > ringback. After a
> > while, the callee picks up. The UAS sends back a 200 OK and starts
> > sending media. The 200 OK, for some reason, arrives much
> > later than the
> > first media packets... what is the UAC supposed to do in the
> > mean time?
> > Ignore the media? Play the media anyway?
> >
> > Another scenario. The UAC starts receiving media before a
> provisional
> > response is received... what does it have to do?
> >
> > The main point is that, since signalling and media are loosely
> > synchronized, you will always have race conditions and you
> > will have to
> > make guesses about what to do during those race conditions anyway.
> >
> > Thanks,
> >
> > Gonzalo
> >
> >
> >
> > "Ejzak, Richard P (Richard)" wrote:
> > >
> > > Gonzalo,
> > > It seems the single greatest difficulty with the gateway
> > model (as you point out in your draft) is the difficulty of
> > depending on the arrival of media packets to determine
> > whether or not to generate local ringing.  I have previously
> > (last summer) suggested a solution to this (use 180
> > exclusively to indicate that local ringing should override
> > any inband media and 183 otherwise) that is unacceptable
> > since it does not satisfy the requirement that 180 be used to
> > indicate alerting of the called party.
> > >
> > > Have you considered using the Alert-Info header in the
> > following way? Since the real problem is that we would like
> > to be able to discriminate between cases when 180 should
> > cause local ringing and when 180 should not (since inband
> > media is available), and it is the UAS that knows
> > conclusively which case applies, let's agree on an encoding
> > of the Alert-Info header that indicates that local ringing
> > should not be applied.  The following line is a syntactically
> > valid header:
> > >
> > > Alert-Info: <data:,>
> > >
> > > This header identifies the Alert-Info as the null string,
> > which seems unambiguously and efficiently interpretable
> > within a 180 response as "do not play local ringing even
> > though the called party is being alerted."  If the UAC does
> > not recognize it or chooses not to interpret it for security
> > reasons, it can be safely ignored.
> > >
> > > This modest addition to your draft (or an equivalent
> > mechanism) would make it unnecessary for the gateway model to
> > depend on local policy or incoming media packet detection and
> > is completely consistent with all of the constraints you have
> > documented.
> > >
> > > Another approach may be to actually specify the rtp stream
> > as the source of the alert info (although this would require
> > the definition of a new URI scheme type).  It might look like:
> > >
> > > Alert-Info: <rtp:/12.34.56.78:90>
> > >
> > > where the Alert-Info specifies the address and port of the
> > rtp stream.  I don't like this mechanism since it is
> > redundant with SDP and prone to error.  It is also ambiguous
> > in the event of any subsequent media change using UPDATE (Do
> > I begin to generate local ringing if the rtp stream source
> > address changes?  Or do I continue to listen to the address
> > specified in the Alert-Info and ignore any UPDATEs?  No to both.)
> > >
> > > May I suggest including such a mechanism (preferably the
> > first one) in your draft.
> > >
> > > Richard Ejzak
> > > Lucent Technologies
> > >
> > > -----Original Message-----
> > > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> 
> > > Sent: Monday, February 10, 2003 5:41 AM
> > > To: sipping
> > > Subject: [Sipping] New version of the early media draft
> > >
> > > Folks,
> > >
> > > I have just sumitted a new version of the early media
> > draft. Until it
> > > appears in the archives, you can fetch it from:
> > >
> > >
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-early-media-01.txt
> 
> >
> > I have included all the (long and useful) discussions we had in the
> > mailing list. Therefore, the draft now keeps separate the "gateway"
> and
> > the "application server" models. I have also removed the parts we
> did
> > not agree on.
> >
> > Feedback is, as usual, appreciated.
> >
> > Thanks,
> >
> > Gonzalo
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> 
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> 
> --
> Gonzalo Camarillo         Phone :  +358  9 299 33 71
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> Telecom R&D               Fax   :  +358  9 299 30 52
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> Finland                   http://www.hut.fi/~gonzalo
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 13:33:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20557
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 13:33:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25IiCD07258
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 13:44:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25IiCO07255
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 13:44:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20530
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 13:33:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25IhdO07238;
	Wed, 5 Mar 2003 13:43:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25Ia3O06026
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 13:36:03 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14902
	for <sipping@ietf.org>; Wed, 5 Mar 2003 12:25:57 -0500 (EST)
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h25HS0B3025149;
	Wed, 5 Mar 2003 18:28:00 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id FDVMH61G; Wed, 5 Mar 2003 18:28:00 +0100
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.106.10])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h25HRxlW002759;
	Wed, 5 Mar 2003 19:27:59 +0200 (EET)
Message-ID: <3E66339D.A667172A@lmf.ericsson.se>
Date: Wed, 05 Mar 2003 19:27:57 +0200
X-Sybari-Trust: fccd0335 9ffcebbb a5ee123c 00000138
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] New version of netann
References: <4A3384433CE2AB46A63468CB207E209D2DF7F9@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi Eric,

> >>"Early" URI Parameter
> >>=====================
> >>Christer Holmberg pointed out his preference for coming up
> >>with a generic "this session is early" mechanism.  At this
> >>time, I'm not sure that this is something that occurs in
> >>other situations.  Given that, we've left in the early parameter.
> >
> >[CHH] I think that early media DO occur in other situations
> >(at least in PSTN interworking). At least I assume so, since
> >there has been much discussion about it lately...
>
> If we can make this mechanism generic, that would be great.  I don't see how we can figure that out except for an explicit mechanism.
>
> As an explicit mechanism, it could be a parameter or a header.  For some reason I have an aversion to inserting a new header, but I could be convinced to get over that phobia.

Have you read the latest version of Gonzalo's early media draft? How would that fit into this?

> >[CHH] Do you mean that the proxy is going to insert Require:
> >100rel in the request, then handle the sending of PRACK, and
> >make sure that retransmissions of 18x messages received by
> >that proxy aren't forwarded back to the UAC, etc etc?
> >
> >Or, do you mean that the proxy will send a 421 Extension
> >Required response back to the UAC?
>
> The latter (421 Extension Required).  In this case, signaling works :-)

Which means that a UAC MUST support PRACK, instead of SHOULD, right?

Regards,

Christer Holmberg
Ericsson Finland



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 14:17:07 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22813
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 14:17:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25JRkj10610
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 14:27:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JRkO10605
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 14:27:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22734
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 14:16:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JRBO10465;
	Wed, 5 Mar 2003 14:27:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Jk6507673
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 14:46:06 -0500
Received: from mailhub.fokus.fraunhofer.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06831
	for <sipping@ietf.org>; Tue, 4 Mar 2003 14:34:59 -0500 (EST)
Received: from benetnash (benetnash [193.175.133.195])
	by mailhub.fokus.fraunhofer.de (8.11.6/8.11.6) with SMTP id h24Japv05750;
	Tue, 4 Mar 2003 20:36:51 +0100 (MET)
Date: Tue, 4 Mar 2003 20:36:51 +0100 (MET)
From: Jiri Kuthan <kuthan@fokus.fraunhofer.de>
X-Sender: jku@benetnash
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
cc: jh@lohi.eng.song.fi, "Beck01, Wolfgang" <BeckW@t-systems.com>,
        jon.peterson@neustar.biz, sipping@ietf.org
Subject: Re: [Sipping] proxy accounting, was: New version of the SIP-AAAreqs draft
In-Reply-To: <3E649938.17A93738@lmf.ericsson.se>
Message-ID: <Pine.SUN.3.91.1030304203559.450C-100000@benetnash>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

> Juha,
> 
> RFC3261 compliant UAs do not take into account the To and From URIs to
> perform dialog identification. However, systems that implement RFC2543
> do... that's the only reason why the spec does not allow to change the
> >From and To URIs; backwards compatibility.
> 
> It would be nice to know how big is this backwards compatibility problem
> (i.e., how many already installed systems implement that way of dialog
> identification)...

To me knowledge, it is unfortunately a big problem and most end-devices
you can buy today can't live without it.

-Jiri
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 14:17:15 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22843
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 14:17:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25JRsv10650
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 14:27:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JRrO10647
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 14:27:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22752
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 14:16:42 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JRHO10525;
	Wed, 5 Mar 2003 14:27:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25Dlr526520
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 08:47:53 -0500
Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29893
	for <sipping@ietf.org>; Wed, 5 Mar 2003 08:36:23 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 5 Mar 2003 05:38:25 -0800
Received: from 203.196.139.114 by lw8fd.law8.hotmail.msn.com with HTTP;
	Wed, 05 Mar 2003 13:38:25 GMT
X-Originating-IP: [203.196.139.114]
From: "banibrata dutta" <bdutta@hotmail.com>
To: rishik@mahindrabt.com
Cc: sipforum-discussion@lists.su.se, sipping@ietf.org
Date: Wed, 05 Mar 2003 13:38:25 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F81sg8Kyg8COSd3CMMk00002d59@hotmail.com>
X-OriginalArrivalTime: 05 Mar 2003 13:38:25.0711 (UTC) FILETIME=[7F7A5BF0:01C2E31C]
Subject: [Sipping] Re: [Sipforum-discussion] SIP Telephony Device Requirements,Conf iguration and
 Data
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

you are absolutely right. SIP, brings the intelligent
for call-control right upto the user-agent, i.e. the
device used for making a SIP call, but that is just 1
of the several possibilities.

in the PSTN world we have the Access-network & the
Core-network. For the Access-network too we do have
protocols s.a. V5, ISDN, apart from the traditional
tip/ring protocol.

a "residential gateway" is a network-entity that can
allow the dumb-black-phones (i.e. non-SIP + analog phone)
to connect to the SIP network... somewhat similar in
spirit to the NT-1/NT-2 in ISDN n/ws.

then there are the signalling gateways which can do
interworking between SIP - SS7, SIP - H323, H323 - SS7 etc.
infact you need such a gateway everything you make a
call that crosses SIP-VoIP network boundary into the PSTN
network boundary, and vice-versa.

-bdutta.

From: rishi <rishik@mahindrabt.com>
CC: sipforum-discussion@lists.su.se, sipping@ietf.org
Subject: Re: [Sipforum-discussion] SIP Telephony Device Requirements,Conf 
iguration and Data
Date: Wed, 05 Mar 2003 03:48:46 +0530

Hi folks,
Just got interested in SIP world,would like to know how SIP can be related
to SS7 as both being signalling protocols,but SIP sits even on the client
device where as SS7 is completely invisible to client,and what are the major
differences of SIP and SS7
can some one help me in this ??
regards
Rishi

Henry Sinnreich wrote:

 > Franz Edler writes:
 >
 > >"dual homed" SIP-UA with one "line" connected
 > > to the PSTN via V5 - SIP gateway and the other "lines" beeing
 > > free for all new services of the SIP world.
 >
 > Great minds think alike! :-) Some of us had actually the same
 > requirements. This may be a MAY...
 >
 > The authors are still collecting all comments and we plan to consolidate
 > them with our follow-up into one single reply, for consistency reasons.
 > Please stay tuned.
 >
 > Thanks, Henry
 >
 > I've stopped 2,514 spam messages. You can too!
 > Get your free, safe spam protection at
 > http://www.cloudmark.com/spamnetsig/
 >
 > > -----Original Message-----
 > > From: Edler Franz [mailto:franz.edler@uta.at]
 > > Sent: Friday, February 28, 2003 1:55 AM
 > > To: 'Eric Tremblay'; Henry Sinnreich; Jörgen Björkner;
 > > sipforum-discussion@lists.su.se
 > > Cc: sipping@ietf.org
 > > Subject: AW: [Sipforum-discussion] SIP Telephony Device
 > > Requirements, Conf iguration and Data
 > >
 > >
 > > Hi folks,
 > >
 > > just a comment on SIP-25:
 > >
 > > I am currently working on a PSTN - SIP migration concept
 > > avoiding to re-invent all fancy features of the PSTN and in
 > > particular to re-implement all legal/regulatory requirements
 > > (emergency call handling, legal intercept). The concept
 > > builds upon a "dual homed" SIP-UA with one "line" connected
 > > to the PSTN via V5 - SIP gateway and the other "lines" beeing
 > > free for all new services of the SIP world. Therefore the
 > > requirement of multiple identities on the SIP side and a
 > > static identitiy on the PSTN side is essential, but I agree,
 > > if you are focused on analog adapters only, this would mean
 > > an unnecessary burden. But I suggest to re-think the
 > > migration perspective.
 > >
 > > By the way, if anyone is interested in this "dual-homed" PSTN
 > > - SIP migration concept let me know. I am convienced that
 > > this means a good chance for a carrier to migrate towards SIP
 > > without heavy investments in re-inventing what is already existing.
 > >
 > > kind regards
 > > Franz
 > >
 > > ---------------------------------------------------------------
 > > Franz Edler
 > > Strategy & Business Development
 > >
 > > UTA Telekom AG
 > > Donau-City-Strasse 11
 > > A-1220 Wien
 > > T: + 43/1/9009-3310
 > > F: + 43/1/9009-93310
 > > M: + 43/699/1388 3310
 > > mailto:franz.edler@uta.at
 > > http://www.uta.at
 > > --------------------------------------------------------------
 > >
 > > > -----Ursprüngliche Nachricht-----
 > > > Von:        Eric Tremblay [SMTP:etremblay@mediatrix.com]
 > > > Gesendet am:        Mittwoch, 26. Februar 2003 17:41
 > > > An: Henry Sinnreich; Jörgen Björkner;
 > > sipforum-discussion@lists.su.se
 > > > Cc: sipping@ietf.org
 > > > Betreff:    RE: [Sipforum-discussion] SIP Telephony Device
 > > Requirements,
 > > > Configuration and Data
 > > >
 > > > Hi Henry,
 > > >
 > > > Here is a somewhat lengthy email with a few comments about the SIP
 > > > Telephony Device Requirements draft:
 > > >
 > > >
 > > >   SIP-25, Dynamic login/logout for user mobility: SIP devices MUST
 > > >   support user mobility.  SIP clients MUST store a static
 > > profile in
 > > >   non-volatile memory so that this information is available
 > > during the
 > > >   power up sequence.  SIP clients MUST allow a user to walk up to a
 > > >   client, login, and be able to send and receive calls with
 > > his profile
 > > >   information.
 > > >   For emergency numbers (e.g. 911) the client MUST send the
 > > credentials
 > > >   (username/password) of the static profile.
 > > >
 > > > [EricT]
 > > > We are developing analog adapters and don't remember
 > > receiving such a
 > > > request. I suggest either changing the MUST to SHOULD or
 > > adding some text
 > > > to specify that it is a MUST for devices with the proper
 > > interface to do
 > > > it and a SHOULD for devices with a limited interface. I
 > > know we could
 > > > possibly configure this through a web interface, but the
 > > point is that
 > > > there are a lot of vendore that currently just want to
 > > replace the wire,
 > > > not the phone and its interface...
 > > >
 > > >
 > > >
 > > >
 > >

*********************************************************
Disclaimer

This message (including any attachments) contains
confidential information intended for a specific
individual and purpose, and is protected by law.
If you are not the intended recipient, you should
delete this message and are hereby notified that
any disclosure, copying, or distribution of this
message, or the taking of any action based on it,
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com


_________________________________________________________________
Cricket World Cup 2003- News, Views and Match Reports. 
http://server1.msn.co.in/msnspecials/worldcup03/

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 14:17:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22875
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 14:17:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25JS8o10695
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 14:28:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JS8O10692
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 14:28:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22798
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 14:16:57 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JRDO10485;
	Wed, 5 Mar 2003 14:27:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25AKN511061
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 05:20:23 -0500
Received: from shardagate.mahindrabt.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23469
	for <sipping@ietf.org>; Wed, 5 Mar 2003 05:08:56 -0500 (EST)
Received: from thisdomain (mailscan.sharda.mahindrabt.com [10.5.0.97])
	by shardagate.mahindrabt.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id PAA28374
	for <sipping@ietf.org>; Wed, 5 Mar 2003 15:40:54 +0530
Received: from intranet.sharda.mahindrabt.com by mahindrabt.com ; Wed, 05 Mar 2003 15:28:28 +0530
Date: Wed, 05 Mar 2003 15:28:28 +0530
X-Originating-IP: 10.5.0.15
X-Auth-User: rishik@mahindrabt.com
Received: from mahindrabt.com ([10.5.4.51])
	by intranet.sharda.mahindrabt.com (8.9.3/8.9.3) with ESMTP id PAA26974;
	Wed, 5 Mar 2003 15:40:45 +0530
Message-ID: <3E652646.B9EAAC8B@mahindrabt.com>
Date: Wed, 05 Mar 2003 03:48:46 +0530
From: rishi <rishik@mahindrabt.com>
Organization: MBT
X-Mailer: Mozilla 4.74 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
CC: sipforum-discussion@lists.su.se, sipping@ietf.org
References: <002501c2e1fe$097ee890$638832a6@hsinnreich2>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sipping] Re: [Sipforum-discussion] SIP Telephony Device Requirements,Conf
 iguration and Data
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi folks,
Just got interested in SIP world,would like to know how SIP can be related
to SS7 as both being signalling protocols,but SIP sits even on the client
device where as SS7 is completely invisible to client,and what are the major
differences of SIP and SS7
can some one help me in this ??
regards
Rishi

Henry Sinnreich wrote:

> Franz Edler writes:
>
> >"dual homed" SIP-UA with one "line" connected
> > to the PSTN via V5 - SIP gateway and the other "lines" beeing
> > free for all new services of the SIP world.
>
> Great minds think alike! :-) Some of us had actually the same
> requirements. This may be a MAY...
>
> The authors are still collecting all comments and we plan to consolidate
> them with our follow-up into one single reply, for consistency reasons.
> Please stay tuned.
>
> Thanks, Henry
>
> I've stopped 2,514 spam messages. You can too!
> Get your free, safe spam protection at
> http://www.cloudmark.com/spamnetsig/
>
> > -----Original Message-----
> > From: Edler Franz [mailto:franz.edler@uta.at]
> > Sent: Friday, February 28, 2003 1:55 AM
> > To: 'Eric Tremblay'; Henry Sinnreich; Jörgen Björkner;
> > sipforum-discussion@lists.su.se
> > Cc: sipping@ietf.org
> > Subject: AW: [Sipforum-discussion] SIP Telephony Device
> > Requirements, Conf iguration and Data
> >
> >
> > Hi folks,
> >
> > just a comment on SIP-25:
> >
> > I am currently working on a PSTN - SIP migration concept
> > avoiding to re-invent all fancy features of the PSTN and in
> > particular to re-implement all legal/regulatory requirements
> > (emergency call handling, legal intercept). The concept
> > builds upon a "dual homed" SIP-UA with one "line" connected
> > to the PSTN via V5 - SIP gateway and the other "lines" beeing
> > free for all new services of the SIP world. Therefore the
> > requirement of multiple identities on the SIP side and a
> > static identitiy on the PSTN side is essential, but I agree,
> > if you are focused on analog adapters only, this would mean
> > an unnecessary burden. But I suggest to re-think the
> > migration perspective.
> >
> > By the way, if anyone is interested in this "dual-homed" PSTN
> > - SIP migration concept let me know. I am convienced that
> > this means a good chance for a carrier to migrate towards SIP
> > without heavy investments in re-inventing what is already existing.
> >
> > kind regards
> > Franz
> >
> > ---------------------------------------------------------------
> > Franz Edler
> > Strategy & Business Development
> >
> > UTA Telekom AG
> > Donau-City-Strasse 11
> > A-1220 Wien
> > T: + 43/1/9009-3310
> > F: + 43/1/9009-93310
> > M: + 43/699/1388 3310
> > mailto:franz.edler@uta.at
> > http://www.uta.at
> > --------------------------------------------------------------
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von:        Eric Tremblay [SMTP:etremblay@mediatrix.com]
> > > Gesendet am:        Mittwoch, 26. Februar 2003 17:41
> > > An: Henry Sinnreich; Jörgen Björkner;
> > sipforum-discussion@lists.su.se
> > > Cc: sipping@ietf.org
> > > Betreff:    RE: [Sipforum-discussion] SIP Telephony Device
> > Requirements,
> > > Configuration and Data
> > >
> > > Hi Henry,
> > >
> > > Here is a somewhat lengthy email with a few comments about the SIP
> > > Telephony Device Requirements draft:
> > >
> > >
> > >   SIP-25, Dynamic login/logout for user mobility: SIP devices MUST
> > >   support user mobility.  SIP clients MUST store a static
> > profile in
> > >   non-volatile memory so that this information is available
> > during the
> > >   power up sequence.  SIP clients MUST allow a user to walk up to a
> > >   client, login, and be able to send and receive calls with
> > his profile
> > >   information.
> > >   For emergency numbers (e.g. 911) the client MUST send the
> > credentials
> > >   (username/password) of the static profile.
> > >
> > > [EricT]
> > > We are developing analog adapters and don't remember
> > receiving such a
> > > request. I suggest either changing the MUST to SHOULD or
> > adding some text
> > > to specify that it is a MUST for devices with the proper
> > interface to do
> > > it and a SHOULD for devices with a limited interface. I
> > know we could
> > > possibly configure this through a web interface, but the
> > point is that
> > > there are a lot of vendore that currently just want to
> > replace the wire,
> > > not the phone and its interface...
> > >
> > >
> > >
> > >
> >

*********************************************************
Disclaimer

This message (including any attachments) contains 
confidential information intended for a specific 
individual and purpose, and is protected by law. 
If you are not the intended recipient, you should 
delete this message and are hereby notified that 
any disclosure, copying, or distribution of this
message, or the taking of any action based on it, 
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 14:17:47 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22898
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 14:17:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25JSQ610731
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 14:28:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JSPO10728
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 14:28:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22858
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 14:17:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JR5O10445;
	Wed, 5 Mar 2003 14:27:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Fo0p14479
	for <sipping@optimus.ietf.org>; Tue, 4 Mar 2003 10:50:00 -0500
Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27504;
	Tue, 4 Mar 2003 10:38:57 -0500 (EST)
Received: from EEB174W2Kvk (unverified [157.190.81.172]) by cit.ie
 (Rockliffe SMTPRA 5.2.5) with SMTP id <B0000274812@mail.cit.ie>;
 Tue, 4 Mar 2003 15:28:00 +0000
Reply-To: <vkenneally@cit.ie>
From: "Valerie Kenneally" <vkenneally@cit.ie>
To: <sip@ietf.org>, <sipping@ietf.org>
Cc: <alan.johnston@wcom.com>, <sdonovan@dynamicsoft.com>,
        <rsparks@dynamicsoft.com>, <ccunningham@dynamicsoft.com>,
        <kevin.summers@sonusnet.com>
Date: Tue, 4 Mar 2003 15:41:07 -0000
Message-ID: <NIEFLFDIBJCPCKAMIGBPOEGLCFAA.vkenneally@cit.ie>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Question on Basic Call flows document section 3.6
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi All,

	In document at the below link

http://www.ietf.org/internet-drafts/draft-ietf-sipping-basic-call-flows-01.t
xt
section 3.6 "Session via Redirect and Proxy Servers with the SDP in ACK".

I am wondering if someone can explain to me how the INVITE (F4) is directed
from User A to Proxy 3 without any Route header being included in the
message.

I have been trying to figure this out for a while and I'd really appreciate
any feedback asap

Thanks in advance,
Val

------------------------
Val Kenneally,
Post-Graduate,
Electronic Eng. Dept.,
CIT,
Rossa Ave.,
Bishopstown,
Cork,
Ireland.
------------------------
Tel: +353 87 2273668
Fax: +353 21 4326625


-------------------Legal  Disclaimer---------------------------------------

The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.

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

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 14:34:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24025
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 14:34:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25Jj5K13274
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 14:45:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25Jj4O13271
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 14:45:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23995
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 14:33:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JenO12743;
	Wed, 5 Mar 2003 14:40:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JSCO10708
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 14:28:12 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22811
	for <sipping@ietf.org>; Wed, 5 Mar 2003 14:17:02 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h25JJ4B3008580;
	Wed, 5 Mar 2003 20:19:04 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5W9N97B; Wed, 5 Mar 2003 20:19:03 +0100
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.106.10])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h25JJ4lW008593;
	Wed, 5 Mar 2003 21:19:04 +0200 (EET)
Message-ID: <3E664DA6.B2CA81D@lmf.ericsson.se>
Date: Wed, 05 Mar 2003 21:19:02 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] New version of netann
References: <4A3384433CE2AB46A63468CB207E209D2DF7F9@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi Eric,

A question on the draft, related to the functionality.

Assuming there is a media stream service which consists of both audio and video, identified with different promt-urls, do I have to send separate INVITEs for those (in RTSP
separate SETUPs and PLAY are sent)? Or, is it possible to include multiple play parameters in a single INVITE Request-URI?

Regards,

Christer Holmberg
Ericsson Finland


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 15:07:50 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26253
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 15:07:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25KITC16428
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 15:18:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25KITO16423
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 15:18:29 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26178
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 15:07:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25KHOO16344;
	Wed, 5 Mar 2003 15:17:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25KGcO16301
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 15:16:38 -0500
Received: from zrc2s0jx.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25975
	for <sipping@ietf.org>; Wed, 5 Mar 2003 15:05:23 -0500 (EST)
Received: from zsc3c028.us.nortel.com (zsc3c028.us.nortel.com [47.81.138.28])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h25K7J017362;
	Wed, 5 Mar 2003 14:07:20 -0600 (CST)
Received: by zsc3c028.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1LW2LJ1A>; Wed, 5 Mar 2003 12:07:20 -0800
Message-ID: <2F1FC1DEA077D5119FAD00508BCFD6D20700C440@zsc3c030.us.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        "Mark Watson" <mwatson@nortelnetworks.com>
Cc: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'sipping'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Wed, 5 Mar 2003 12:07:16 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E352.D1E53C80"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E352.D1E53C80
Content-Type: text/plain

Would this alert info say:
1 - Do not play local ringback, or
2 - In-band alerting indication present?

My take is that 2 makes more sense since (1) is only applicable to
telephony applications.

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se] 
> Sent: Wednesday, March 05, 2003 10:22 AM
> To: Watson, Mark [MOP:EP10:EXCH]
> Cc: 'Ejzak, Richard P (Richard)'; sipping
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Mark,
> 
> many of your points have been discussed either in the draft 
> or in the mailing list before. The MGC-MG decomposition 
> problem is discussed in the draft, and the indication of the 
> presence in-band media was discussed in the previous version 
> of the draft.
> 
> My initial proposal was to include an SDP parameter that 
> provided information about the intention of the sender. That 
> is, the sender intended to send early media... that was seen 
> as too complex (and I agree with that, by the way).
> 
> But using some type of *simpler* mechanism that only 
> indicates that the UAS does not want the UAC to generate 
> local ringback (like the mechanism proposed in this thread), 
> would be sensible, IMO. 
> 
> How do people feel about using the header field below in a 
> 18x response to indicate that the UAS would like the UAC not 
> to provide local ringback (as proposed previously in this thread)?
> 
> Alert-Info: <data:,>
> 
> To me, once we have defined Alert-Info, this is not an 
> unreasonable thing to do with this header. Opinions?
> 
> Gonzalo
> 
> 
> Mark Watson wrote:
> > 
> > Gonzalo,
> > 
> > I would support this addition (or something like it - I 
> confess to not 
> > having followed all the details of this thread).
> > 
> > This same problem has come up again and again over the last 
> two years. 
> > The root issue is a distinction between explicit application layer 
> > indications and implicit media layer indications. If the UAC is a 
> > distributed system (e.g. Media Gateway and Media Gateway 
> Controller), 
> > then the general model is that the MG is controlled by the MGC. The 
> > MGC has only explicit app. layer indications to work from - 
> it cannot 
> > take actions on the basis of receipt of not of media 
> packets because 
> > it does not see them.
> > 
> > Sure, the MG can report and 'RTP received' event and the 
> MGC can then 
> > instruct it appropriately, but this takes time & I don't think it's 
> > standardised.
> > 
> > So, there should be enough information *in the SIP 
> signalling* for the 
> > UAC to take an intelligent decision on whether to play 
> media or local 
> > ringing. I don't want to prescribe how it takes this 
> decision, but at 
> > present there is information available to the UAS at the SIP layer 
> > which is not communicated to the UAC (at the SIP layer) - 
> namely the 
> > availability of in-band media. This can only result in the 
> UAC taking 
> > inappropriate decisions in some scenarios.
> > 
> > Perhaps we should not be telling the UAC to 'play local ringing' or 
> > 'don't play local ringing', but if the UAS knows there is in-band 
> > information, it should tell the UAC in SIP.
> > 
> > Regards...Mark
> > 
> > > -----Original Message-----
> > > From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com]
> > > Sent: 04 March 2003 19:15
> > > To: 'Gonzalo Camarillo'
> > > Cc: sipping
> > > Subject: RE: [Sipping] New version of the early media draft
> > >
> > >
> > > Gonzalo,
> > > Thanks for your response.  I understand and agree with 
> your concerns 
> > > about race conditions as well as the discussion of how to handle 
> > > them.  But I do not want the UAS to blindly control when the UAC 
> > > should apply local ringing.  I want the UAS to be able to 
> indicate 
> > > when the UAC should NOT apply local ringing.  There is a very 
> > > important distinction here. According to your draft, when a UAC 
> > > receives a 180 it should be prepared to generate local 
> ringing, and 
> > > it is a matter of local policy what the UAC should do 
> when there is 
> > > concurrent in-band media.  Gateway resources should be 
> allocated to
> > > detect in-band media and decide whether or not to generate
> > > ringing.  But under some circumstances the UAS knows that
> > > call progress information is available in-band and the UAC
> > > does not need to bother to allocate extra resources to
> > > monitor the media flow and optionally inject ringing.  I
> > > believe it is important for a UAS to be able to indicate this
> > > situation to a UAC.  These are processing !
> > > resources that could be put to use elsewhere.  There are no
> > > race conditions in this situation - only the recognition that
> > > local ringing and packet detection are unnecessary.
> > >
> > > I stand by my original suggestion and continue to request 
> a modest 
> > > addition to your draft based on this general approach (my 
> previous 
> > > email indicates one possible detailed solution).  Please 
> let me know 
> > > if you see any further issues.
> > >
> > > Regards,
> > > Richard Ejzak
> > > Lucent Technologies
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > Sent: Tuesday, March 04, 2003 5:42 AM
> > > To: Ejzak, Richard P (Richard)
> > > Cc: sipping
> > > Subject: Re: [Sipping] New version of the early media draft
> > >
> > >
> > > Ejzak,
> > >
> > > the main problem with any SIP-layer mechanism that allows 
> the UAS to
> > 
> > > tell the UAC whether local ringback has to be generated or not is
> > race
> > > conditions. It really does not matter whether you use an 
> Alert-Info 
> > > header field in a reponse, or a special status code, or a special 
> > > body, or whatever to signal it. You always have race conditions.
> > >
> > > Let's say that the UAS tells the UAC to generate local ringback. 
> > > After a while, the callee picks up. The UAS sends back a 
> 200 OK and 
> > > starts sending media. The 200 OK, for some reason, arrives much
> > > later than the
> > > first media packets... what is the UAC supposed to do in the
> > > mean time?
> > > Ignore the media? Play the media anyway?
> > >
> > > Another scenario. The UAC starts receiving media before a
> > provisional
> > > response is received... what does it have to do?
> > >
> > > The main point is that, since signalling and media are loosely 
> > > synchronized, you will always have race conditions and 
> you will have 
> > > to make guesses about what to do during those race conditions 
> > > anyway.
> > >
> > > Thanks,
> > >
> > > Gonzalo
> > >
> > >
> > >
> > > "Ejzak, Richard P (Richard)" wrote:
> > > >
> > > > Gonzalo,
> > > > It seems the single greatest difficulty with the gateway
> > > model (as you point out in your draft) is the difficulty of 
> > > depending on the arrival of media packets to determine whether or 
> > > not to generate local ringing.  I have previously (last summer) 
> > > suggested a solution to this (use 180 exclusively to 
> indicate that 
> > > local ringing should override any inband media and 183 otherwise) 
> > > that is unacceptable since it does not satisfy the 
> requirement that 
> > > 180 be used to indicate alerting of the called party.
> > > >
> > > > Have you considered using the Alert-Info header in the
> > > following way? Since the real problem is that we would like to be 
> > > able to discriminate between cases when 180 should cause local 
> > > ringing and when 180 should not (since inband media is 
> available), 
> > > and it is the UAS that knows conclusively which case 
> applies, let's 
> > > agree on an encoding of the Alert-Info header that indicates that 
> > > local ringing should not be applied.  The following line is a 
> > > syntactically valid header:
> > > >
> > > > Alert-Info: <data:,>
> > > >
> > > > This header identifies the Alert-Info as the null string,
> > > which seems unambiguously and efficiently interpretable 
> within a 180 
> > > response as "do not play local ringing even though the 
> called party 
> > > is being alerted."  If the UAC does not recognize it or 
> chooses not 
> > > to interpret it for security reasons, it can be safely ignored.
> > > >
> > > > This modest addition to your draft (or an equivalent
> > > mechanism) would make it unnecessary for the gateway 
> model to depend 
> > > on local policy or incoming media packet detection and is 
> completely 
> > > consistent with all of the constraints you have documented.
> > > >
> > > > Another approach may be to actually specify the rtp stream
> > > as the source of the alert info (although this would require the 
> > > definition of a new URI scheme type).  It might look like:
> > > >
> > > > Alert-Info: <rtp:/12.34.56.78:90>
> > > >
> > > > where the Alert-Info specifies the address and port of the
> > > rtp stream.  I don't like this mechanism since it is 
> redundant with 
> > > SDP and prone to error.  It is also ambiguous in the event of any 
> > > subsequent media change using UPDATE (Do I begin to 
> generate local 
> > > ringing if the rtp stream source address changes?  Or do 
> I continue 
> > > to listen to the address specified in the Alert-Info and 
> ignore any 
> > > UPDATEs?  No to both.)
> > > >
> > > > May I suggest including such a mechanism (preferably the
> > > first one) in your draft.
> > > >
> > > > Richard Ejzak
> > > > Lucent Technologies
> > > >
> > > > -----Original Message-----
> > > > From: Gonzalo Camarillo 
> [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > 
> > > > Sent: Monday, February 10, 2003 5:41 AM
> > > > To: sipping
> > > > Subject: [Sipping] New version of the early media draft
> > > >
> > > > Folks,
> > > >
> > > > I have just sumitted a new version of the early media
> > > draft. Until it
> > > > appears in the archives, you can fetch it from:
> > > >
> > > >
> > 
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-e
> > arly-media-01.txt
> > 
> > >
> > > I have included all the (long and useful) discussions we 
> had in the 
> > > mailing list. Therefore, the draft now keeps separate the 
> "gateway"
> > and
> > > the "application server" models. I have also removed the parts we
> > did
> > > not agree on.
> > >
> > > Feedback is, as usual, appreciated.
> > >
> > > Thanks,
> > >
> > > Gonzalo
> > > _______________________________________________
> > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > 
> > > This 
> list is for NEW development of the application of SIP Use 
> > > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > > sip@ietf.org for new developments of core SIP
> > 
> > --
> > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > Telecom R&D               Fax   :  +358  9 299 30 52
> > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> > Finland                   http://www.hut.fi/~gonzalo
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sip@ietf.org for new developments of core SIP
> 
> -- 
> Gonzalo Camarillo         Phone :  +358  9 299 33 71
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> Telecom R&D               Fax   :  +358  9 299 30 52
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> Finland                   http://www.hut.fi/~gonzalo
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 

------_=_NextPart_001_01C2E352.D1E53C80
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Would this alert info say:</FONT>
<BR><FONT SIZE=3D2>1 - Do not play local ringback, or</FONT>
<BR><FONT SIZE=3D2>2 - In-band alerting indication present?</FONT>
</P>

<P><FONT SIZE=3D2>My take is that 2 makes more sense since (1) is only =
applicable to</FONT>
<BR><FONT SIZE=3D2>telephony applications.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, March 05, 2003 10:22 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Watson, Mark [MOP:EP10:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'Ejzak, Richard P (Richard)'; =
sipping</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; many of your points have been discussed either =
in the draft </FONT>
<BR><FONT SIZE=3D2>&gt; or in the mailing list before. The MGC-MG =
decomposition </FONT>
<BR><FONT SIZE=3D2>&gt; problem is discussed in the draft, and the =
indication of the </FONT>
<BR><FONT SIZE=3D2>&gt; presence in-band media was discussed in the =
previous version </FONT>
<BR><FONT SIZE=3D2>&gt; of the draft.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; My initial proposal was to include an SDP =
parameter that </FONT>
<BR><FONT SIZE=3D2>&gt; provided information about the intention of the =
sender. That </FONT>
<BR><FONT SIZE=3D2>&gt; is, the sender intended to send early media... =
that was seen </FONT>
<BR><FONT SIZE=3D2>&gt; as too complex (and I agree with that, by the =
way).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; But using some type of *simpler* mechanism that =
only </FONT>
<BR><FONT SIZE=3D2>&gt; indicates that the UAS does not want the UAC to =
generate </FONT>
<BR><FONT SIZE=3D2>&gt; local ringback (like the mechanism proposed in =
this thread), </FONT>
<BR><FONT SIZE=3D2>&gt; would be sensible, IMO. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; How do people feel about using the header field =
below in a </FONT>
<BR><FONT SIZE=3D2>&gt; 18x response to indicate that the UAS would =
like the UAC not </FONT>
<BR><FONT SIZE=3D2>&gt; to provide local ringback (as proposed =
previously in this thread)?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Alert-Info: &lt;data:,&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; To me, once we have defined Alert-Info, this is =
not an </FONT>
<BR><FONT SIZE=3D2>&gt; unreasonable thing to do with this header. =
Opinions?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark Watson wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I would support this addition (or =
something like it - I </FONT>
<BR><FONT SIZE=3D2>&gt; confess to not </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; having followed all the details of this =
thread).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; This same problem has come up again and =
again over the last </FONT>
<BR><FONT SIZE=3D2>&gt; two years. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The root issue is a distinction between =
explicit application layer </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; indications and implicit media layer =
indications. If the UAC is a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; distributed system (e.g. Media Gateway and =
Media Gateway </FONT>
<BR><FONT SIZE=3D2>&gt; Controller), </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; then the general model is that the MG is =
controlled by the MGC. The </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; MGC has only explicit app. layer =
indications to work from - </FONT>
<BR><FONT SIZE=3D2>&gt; it cannot </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; take actions on the basis of receipt of =
not of media </FONT>
<BR><FONT SIZE=3D2>&gt; packets because </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; it does not see them.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sure, the MG can report and 'RTP received' =
event and the </FONT>
<BR><FONT SIZE=3D2>&gt; MGC can then </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; instruct it appropriately, but this takes =
time &amp; I don't think it's </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; standardised.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; So, there should be enough information *in =
the SIP </FONT>
<BR><FONT SIZE=3D2>&gt; signalling* for the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; UAC to take an intelligent decision on =
whether to play </FONT>
<BR><FONT SIZE=3D2>&gt; media or local </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ringing. I don't want to prescribe how it =
takes this </FONT>
<BR><FONT SIZE=3D2>&gt; decision, but at </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; present there is information available to =
the UAS at the SIP layer </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; which is not communicated to the UAC (at =
the SIP layer) - </FONT>
<BR><FONT SIZE=3D2>&gt; namely the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; availability of in-band media. This can =
only result in the </FONT>
<BR><FONT SIZE=3D2>&gt; UAC taking </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; inappropriate decisions in some =
scenarios.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Perhaps we should not be telling the UAC =
to 'play local ringing' or </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 'don't play local ringing', but if the UAS =
knows there is in-band </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; information, it should tell the UAC in =
SIP.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Regards...Mark</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: Ejzak, Richard P (Richard) [<A =
HREF=3D"mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sent: 04 March 2003 19:15</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; To: 'Gonzalo Camarillo'</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Cc: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Subject: RE: [Sipping] New version of =
the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Thanks for your response.&nbsp; I =
understand and agree with </FONT>
<BR><FONT SIZE=3D2>&gt; your concerns </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; about race conditions as well as the =
discussion of how to handle </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; them.&nbsp; But I do not want the UAS =
to blindly control when the UAC </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; should apply local ringing.&nbsp; I =
want the UAS to be able to </FONT>
<BR><FONT SIZE=3D2>&gt; indicate </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; when the UAC should NOT apply local =
ringing.&nbsp; There is a very </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; important distinction here. According =
to your draft, when a UAC </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; receives a 180 it should be prepared =
to generate local </FONT>
<BR><FONT SIZE=3D2>&gt; ringing, and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; it is a matter of local policy what =
the UAC should do </FONT>
<BR><FONT SIZE=3D2>&gt; when there is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; concurrent in-band media.&nbsp; =
Gateway resources should be </FONT>
<BR><FONT SIZE=3D2>&gt; allocated to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; detect in-band media and decide =
whether or not to generate</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ringing.&nbsp; But under some =
circumstances the UAS knows that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; call progress information is =
available in-band and the UAC</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; does not need to bother to allocate =
extra resources to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; monitor the media flow and optionally =
inject ringing.&nbsp; I</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; believe it is important for a UAS to =
be able to indicate this</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; situation to a UAC.&nbsp; These are =
processing !</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; resources that could be put to use =
elsewhere.&nbsp; There are no</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; race conditions in this situation - =
only the recognition that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; local ringing and packet detection =
are unnecessary.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; I stand by my original suggestion and =
continue to request </FONT>
<BR><FONT SIZE=3D2>&gt; a modest </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; addition to your draft based on this =
general approach (my </FONT>
<BR><FONT SIZE=3D2>&gt; previous </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; email indicates one possible detailed =
solution).&nbsp; Please </FONT>
<BR><FONT SIZE=3D2>&gt; let me know </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; if you see any further issues.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Regards,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Richard Ejzak</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Lucent Technologies</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sent: Tuesday, March 04, 2003 5:42 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; To: Ejzak, Richard P (Richard)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Cc: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Subject: Re: [Sipping] New version of =
the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Ejzak,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the main problem with any SIP-layer =
mechanism that allows </FONT>
<BR><FONT SIZE=3D2>&gt; the UAS to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; tell the UAC whether local ringback =
has to be generated or not is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; race</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; conditions. It really does not matter =
whether you use an </FONT>
<BR><FONT SIZE=3D2>&gt; Alert-Info </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; header field in a reponse, or a =
special status code, or a special </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; body, or whatever to signal it. You =
always have race conditions.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Let's say that the UAS tells the UAC =
to generate local ringback. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; After a while, the callee picks up. =
The UAS sends back a </FONT>
<BR><FONT SIZE=3D2>&gt; 200 OK and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; starts sending media. The 200 OK, for =
some reason, arrives much</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; later than the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; first media packets... what is the =
UAC supposed to do in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; mean time?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Ignore the media? Play the media =
anyway?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Another scenario. The UAC starts =
receiving media before a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; provisional</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; response is received... what does it =
have to do?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The main point is that, since =
signalling and media are loosely </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; synchronized, you will always have =
race conditions and </FONT>
<BR><FONT SIZE=3D2>&gt; you will have </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; to make guesses about what to do =
during those race conditions </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; anyway.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &quot;Ejzak, Richard P =
(Richard)&quot; wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; It seems the single greatest =
difficulty with the gateway</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; model (as you point out in your =
draft) is the difficulty of </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; depending on the arrival of media =
packets to determine whether or </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; not to generate local ringing.&nbsp; =
I have previously (last summer) </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; suggested a solution to this (use 180 =
exclusively to </FONT>
<BR><FONT SIZE=3D2>&gt; indicate that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; local ringing should override any =
inband media and 183 otherwise) </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; that is unacceptable since it does =
not satisfy the </FONT>
<BR><FONT SIZE=3D2>&gt; requirement that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; 180 be used to indicate alerting of =
the called party.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Have you considered using the =
Alert-Info header in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; following way? Since the real problem =
is that we would like to be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; able to discriminate between cases =
when 180 should cause local </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ringing and when 180 should not =
(since inband media is </FONT>
<BR><FONT SIZE=3D2>&gt; available), </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; and it is the UAS that knows =
conclusively which case </FONT>
<BR><FONT SIZE=3D2>&gt; applies, let's </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; agree on an encoding of the =
Alert-Info header that indicates that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; local ringing should not be =
applied.&nbsp; The following line is a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; syntactically valid header:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Alert-Info: =
&lt;data:,&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; This header identifies the =
Alert-Info as the null string,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; which seems unambiguously and =
efficiently interpretable </FONT>
<BR><FONT SIZE=3D2>&gt; within a 180 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; response as &quot;do not play local =
ringing even though the </FONT>
<BR><FONT SIZE=3D2>&gt; called party </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; is being alerted.&quot;&nbsp; If the =
UAC does not recognize it or </FONT>
<BR><FONT SIZE=3D2>&gt; chooses not </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; to interpret it for security reasons, =
it can be safely ignored.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; This modest addition to your =
draft (or an equivalent</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; mechanism) would make it unnecessary =
for the gateway </FONT>
<BR><FONT SIZE=3D2>&gt; model to depend </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; on local policy or incoming media =
packet detection and is </FONT>
<BR><FONT SIZE=3D2>&gt; completely </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; consistent with all of the =
constraints you have documented.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Another approach may be to =
actually specify the rtp stream</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; as the source of the alert info =
(although this would require the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; definition of a new URI scheme =
type).&nbsp; It might look like:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Alert-Info: =
&lt;rtp:/12.34.56.78:90&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; where the Alert-Info specifies =
the address and port of the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; rtp stream.&nbsp; I don't like this =
mechanism since it is </FONT>
<BR><FONT SIZE=3D2>&gt; redundant with </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; SDP and prone to error.&nbsp; It is =
also ambiguous in the event of any </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; subsequent media change using UPDATE =
(Do I begin to </FONT>
<BR><FONT SIZE=3D2>&gt; generate local </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ringing if the rtp stream source =
address changes?&nbsp; Or do </FONT>
<BR><FONT SIZE=3D2>&gt; I continue </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; to listen to the address specified in =
the Alert-Info and </FONT>
<BR><FONT SIZE=3D2>&gt; ignore any </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; UPDATEs?&nbsp; No to both.)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; May I suggest including such a =
mechanism (preferably the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; first one) in your draft.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Richard Ejzak</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Lucent Technologies</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; From: Gonzalo Camarillo </FONT>
<BR><FONT SIZE=3D2>&gt; [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Sent: Monday, February 10, 2003 =
5:41 AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; To: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Subject: [Sipping] New version =
of the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Folks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; I have just sumitted a new =
version of the early media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; draft. Until it</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; appears in the archives, you can =
fetch it from:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sip=
ping-e" =
TARGET=3D"_blank">http://standards.ericsson.net/gonzalo/papers/draft-cam=
arillo-sipping-e</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; arly-media-01.txt</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; I have included all the (long and =
useful) discussions we </FONT>
<BR><FONT SIZE=3D2>&gt; had in the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; mailing list. Therefore, the draft =
now keeps separate the </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;gateway&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the &quot;application server&quot; =
models. I have also removed the parts we</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; did</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; not agree on.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Feedback is, as usual, =
appreciated.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sipping mailing list&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; This </FONT>
<BR><FONT SIZE=3D2>&gt; list is for NEW development of the application =
of SIP Use </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; sip-implementors@cs.columbia.edu for =
questions on current sip Use </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; sip@ietf.org for new developments of =
core SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sipping mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; &gt; This list is for NEW development of the =
application of SIP Use </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; sip-implementors@cs.columbia.edu for =
questions on current sip Use </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; sip@ietf.org for new developments of core =
SIP</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -- </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>&gt; Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>&gt; Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>&gt; FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT SIZE=3D2>&gt; =
Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Sipping mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; This list is for NEW development of the =
application of SIP</FONT>
<BR><FONT SIZE=3D2>&gt; Use sip-implementors@cs.columbia.edu for =
questions on current </FONT>
<BR><FONT SIZE=3D2>&gt; sip Use sip@ietf.org for new developments of =
core SIP</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E352.D1E53C80--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 15:09:56 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22814
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 14:17:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25JRkH10622
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 14:27:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JRkO10607
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 14:27:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22737
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 14:16:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JRFO10505;
	Wed, 5 Mar 2003 14:27:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25BEn515061
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 06:14:49 -0500
Received: from mailhub.fokus.fraunhofer.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24937
	for <sipping@ietf.org>; Wed, 5 Mar 2003 06:03:21 -0500 (EST)
Received: from benetnash (benetnash [193.175.133.195])
	by mailhub.fokus.fraunhofer.de (8.11.6/8.11.6) with SMTP id h25B4Wv10761;
	Wed, 5 Mar 2003 12:04:42 +0100 (MET)
Date: Wed, 5 Mar 2003 12:04:32 +0100 (MET)
From: Jiri Kuthan <kuthan@fokus.fraunhofer.de>
X-Sender: jku@benetnash
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
cc: Jiri Kuthan <jiri.kuthan@fokus.fraunhofer.de>, jh@lohi.eng.song.fi,
        Stuart Jacobs <stu.jacobs@labs.gte.com>,
        Allison Mankin <mankin@psg.com>, sipping@ietf.org
Subject: Re: [Sip] Re: [Sipping] New version of the SIP-AAA reqs draft
In-Reply-To: <3E65D405.9E31819@lmf.ericsson.se>
Message-ID: <Pine.SUN.3.91.1030305115712.588A-100000@benetnash>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

> Jiri,
> 
> > The most compelling issue to me now is integrity of Record-Routes. If
> > the BYE originator can send a BYE and manipulate RR (e.g.,
> > <sip:foo.bar;lr;use_aaa=NO>, it will be obviously useless.
> 
> This is ouside of the scope of the requirements. You can force a request
> to traverse a certain proxy using different mechanisms. Those mechanisms
> are not SIP-AAA specific.

Using record-routing in transactional proxy to achieve dialog-based 
AAA functionality is what I have been proposing and I'm glad we
agree on that.

I maintain though, that if record-routing is used in this way and there 
is no integrity of record-routing information, it is not applicable to 
sensitive applications such as AAA.

I of course don't need any spec support to achieve integrity. I can 
add any parameter to record-route and one of them can be a digest value. 
On the other hand, general framework/requriements documents should imho 
spell such considerations as they are strongly tied to security of the 
system as a whole.

-Jiri
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 16:12:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28903
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 16:12:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25LN7I21206
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 16:23:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25LN7O21203
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 16:23:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28877
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 16:11:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25LMVO21149;
	Wed, 5 Mar 2003 16:22:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25LCwO20659
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 16:12:58 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28343
	for <sipping@ietf.org>; Wed, 5 Mar 2003 16:01:44 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] New version of netann
Date: Wed, 5 Mar 2003 16:05:58 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D2DF800@zoe.office.snowshore.com>
Thread-Topic: [Sipping] New version of netann
Thread-Index: AcLjTGX3jk+vvSKnRSWpK8MQ+tYaWQADohFw
From: "Eric Burger" <eburger@snowshore.com>
To: "Christer Holmberg" <christer.holmberg@lmf.ericsson.se>
Cc: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h25LCwO20660
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

As it stands now, you would need multiple INVITEs.

Otherwise, how would one correlate the play's with m-lines?

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Wednesday, March 05, 2003 2:19 PM
> To: Eric Burger
> Cc: Sipping (E-mail)
> Subject: Re: [Sipping] New version of netann
> 
> 
> 
> Hi Eric,
> 
> A question on the draft, related to the functionality.
> 
> Assuming there is a media stream service which consists of 
> both audio and video, identified with different promt-urls, 
> do I have to send separate INVITEs for those (in RTSP
> separate SETUPs and PLAY are sent)? Or, is it possible to 
> include multiple play parameters in a single INVITE Request-URI?
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 16:16:08 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29052
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 16:16:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25LQn321513
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 16:26:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25LQnO21510
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 16:26:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29022
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 16:15:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25LQDO21414;
	Wed, 5 Mar 2003 16:26:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25LHCO20932
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 16:17:12 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28684
	for <sipping@ietf.org>; Wed, 5 Mar 2003 16:06:00 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] New version of netann
Date: Wed, 5 Mar 2003 16:10:13 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D097C26@zoe.office.snowshore.com>
Thread-Topic: [Sipping] New version of netann
Thread-Index: AcLjPOK/MEUEEO+UTr6pIkMOntamSgAHYCFQ
From: "Eric Burger" <eburger@snowshore.com>
To: "Christer Holmberg" <christer.holmberg@lmf.ericsson.se>
Cc: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h25LHCO20933
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> Original Message From: Christer Holmberg 
[snip]
> > As an explicit mechanism, it could be a parameter or a 
> header.  For some reason I have an aversion to inserting a 
> new header, but I could be convinced to get over that phobia.
> 
> Have you read the latest version of Gonzalo's early media 
> draft? How would that fit into this?

I didn't see where his draft described a generic mechanism.  My reading was "early media happens".


[snip]
> Which means that a UAC MUST support PRACK, instead of SHOULD, right?

I went with SHOULD just because if one is in an engineered network, there is not a REQUIREMENT for 100rel.  We could say MUST.  However, this means that we would need machinery on the media server side to reject requests without 100rel.  I don't see the need -- if for one reason or another the UAC doesn't support 100rel *and* the service provider can live with that, I'm happy with having the proxy enforce policy (as it is a PEP) rather than the media server.

Gonzalo's paper describes this in section 2.2.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 16:24:06 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29523
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 16:24:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25LYmc22251
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 16:34:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25LYlO22248
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 16:34:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29467
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 16:23:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25LY8O22167;
	Wed, 5 Mar 2003 16:34:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25LXZO22130
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 16:33:35 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29366
	for <sipping@ietf.org>; Wed, 5 Mar 2003 16:22:22 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h25LOPpC016830;
	Wed, 5 Mar 2003 22:24:25 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5W933DF; Wed, 5 Mar 2003 22:24:24 +0100
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.106.10])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h25LOPlW014803;
	Wed, 5 Mar 2003 23:24:25 +0200 (EET)
Message-ID: <3E666B07.4302E8A9@lmf.ericsson.se>
Date: Wed, 05 Mar 2003 23:24:23 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] New version of netann
References: <4A3384433CE2AB46A63468CB207E209D2DF800@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi Eric,

> As it stands now, you would need multiple INVITEs.
>
> Otherwise, how would one correlate the play's with m-lines?

Well, you could define the play's as SDP attributes. Something like:

m=audio...
a=play:"http://audio.example.net/allcircuitsbusy.g711";
m=video...
a=play:"http://video.example.net/allcircuitsbusy.mpeg4";

I don't know if this would work (I haven't had time to think so much
about it) the way you've planned, though.

But, if we need multiple INVITEs, would it be possible to associate
them? We would have to use different call identifiers etc (I hope you
wouldn't want to use something similar to overlapping for this :)


Another question I have, is related to the media mode attributes.

Assume I send a re-INVITE during the session, to put the media
"on-hold". Now, does this mean that the stream will be "paused", or does
it mean that I just won't receive it? Personally I would say that the
second alternative is more according to the semantics, but in a
streaming environment some may disagree...

Regards,

Christer Holmberg
Ericsson Finland


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 17:39:03 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03382
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 17:39:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25MnkC30532
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 17:49:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25MnkO30529
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 17:49:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03358
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 17:38:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25MmQO30468;
	Wed, 5 Mar 2003 17:48:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25MlbO30427
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 17:47:37 -0500
Received: from hoemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03309
	for <sipping@ietf.org>; Wed, 5 Mar 2003 17:36:19 -0500 (EST)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by hoemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h25McLj12766
	for <sipping@ietf.org>; Wed, 5 Mar 2003 17:38:21 -0500 (EST)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2653.19)
	id <1H3RJYPN>; Wed, 5 Mar 2003 16:38:20 -0600
Message-ID: <DBC3D7D0A071F743AE0767C9C6071EDA0482BBC2@il0015exch010u.ih.lucent.com>
From: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
To: "'Francois Audet'" <audet@nortelnetworks.com>
Cc: "'sipping'" <sipping@ietf.org>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>,
        Mark Watson
	 <mwatson@nortelnetworks.com>
Subject: RE: [Sipping] New version of the early media draft
Date: Wed, 5 Mar 2003 16:38:17 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E367.EA97C7EC"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E367.EA97C7EC
Content-Type: text/plain

Francois,
I am comfortable with either meaning, and understand the preference expressed for (2).  I have a strong preference for using the Alert-Info header to provide this indication, however, since it exists.  It took me quite a while to come up with a syntactically valid absoluteURI (using the data scheme type) that could be immediately parsed to mean "null."  (Note that the Alert-Info header requires an absoluteURI.)  I think it would be a real abuse of this mechanism to include any text in the URI other than the null string (i.e. Alert-Info: <data:,>) to make it more "meaningful" (e.g. Alert-Info: <data:,In-band Alerting>).  Perhaps others don't share my concern here.
 
Do you think a null Alert-Info is sufficient to indicate in-band alerting?  (To me (1) is a more natural interpretation of null Alert-Info, but I don't have a problem with (2).)  Or do you have another suggestion?
 
Regards,
Richard Ejzak
Lucent Technologies

-----Original Message-----
From: Francois Audet [mailto:audet@nortelnetworks.com]
Sent: Wednesday, March 05, 2003 2:07 PM
To: 'Gonzalo Camarillo'; Mark Watson
Cc: 'Ejzak, Richard P (Richard)'; 'sipping'
Subject: RE: [Sipping] New version of the early media draft



Would this alert info say: 
1 - Do not play local ringback, or 
2 - In-band alerting indication present? 

My take is that 2 makes more sense since (1) is only applicable to 
telephony applications. 

> -----Original Message----- 
> From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se <mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> Sent: Wednesday, March 05, 2003 10:22 AM 
> To: Watson, Mark [MOP:EP10:EXCH] 
> Cc: 'Ejzak, Richard P (Richard)'; sipping 
> Subject: Re: [Sipping] New version of the early media draft 
> 
> 
> Mark, 
> 
> many of your points have been discussed either in the draft 
> or in the mailing list before. The MGC-MG decomposition 
> problem is discussed in the draft, and the indication of the 
> presence in-band media was discussed in the previous version 
> of the draft. 
> 
> My initial proposal was to include an SDP parameter that 
> provided information about the intention of the sender. That 
> is, the sender intended to send early media... that was seen 
> as too complex (and I agree with that, by the way). 
> 
> But using some type of *simpler* mechanism that only 
> indicates that the UAS does not want the UAC to generate 
> local ringback (like the mechanism proposed in this thread), 
> would be sensible, IMO. 
> 
> How do people feel about using the header field below in a 
> 18x response to indicate that the UAS would like the UAC not 
> to provide local ringback (as proposed previously in this thread)? 
> 
> Alert-Info: <data:,> 
> 
> To me, once we have defined Alert-Info, this is not an 
> unreasonable thing to do with this header. Opinions? 
> 
> Gonzalo 
> 
> 
> Mark Watson wrote: 
> > 
> > Gonzalo, 
> > 
> > I would support this addition (or something like it - I 
> confess to not 
> > having followed all the details of this thread). 
> > 
> > This same problem has come up again and again over the last 
> two years. 
> > The root issue is a distinction between explicit application layer 
> > indications and implicit media layer indications. If the UAC is a 
> > distributed system (e.g. Media Gateway and Media Gateway 
> Controller), 
> > then the general model is that the MG is controlled by the MGC. The 
> > MGC has only explicit app. layer indications to work from - 
> it cannot 
> > take actions on the basis of receipt of not of media 
> packets because 
> > it does not see them. 
> > 
> > Sure, the MG can report and 'RTP received' event and the 
> MGC can then 
> > instruct it appropriately, but this takes time & I don't think it's 
> > standardised. 
> > 
> > So, there should be enough information *in the SIP 
> signalling* for the 
> > UAC to take an intelligent decision on whether to play 
> media or local 
> > ringing. I don't want to prescribe how it takes this 
> decision, but at 
> > present there is information available to the UAS at the SIP layer 
> > which is not communicated to the UAC (at the SIP layer) - 
> namely the 
> > availability of in-band media. This can only result in the 
> UAC taking 
> > inappropriate decisions in some scenarios. 
> > 
> > Perhaps we should not be telling the UAC to 'play local ringing' or 
> > 'don't play local ringing', but if the UAS knows there is in-band 
> > information, it should tell the UAC in SIP. 
> > 
> > Regards...Mark 
> > 
> > > -----Original Message----- 
> > > From: Ejzak, Richard P (Richard) [ mailto:ejzak@lucent.com <mailto:ejzak@lucent.com> ] 
> > > Sent: 04 March 2003 19:15 
> > > To: 'Gonzalo Camarillo' 
> > > Cc: sipping 
> > > Subject: RE: [Sipping] New version of the early media draft 
> > > 
> > > 
> > > Gonzalo, 
> > > Thanks for your response.  I understand and agree with 
> your concerns 
> > > about race conditions as well as the discussion of how to handle 
> > > them.  But I do not want the UAS to blindly control when the UAC 
> > > should apply local ringing.  I want the UAS to be able to 
> indicate 
> > > when the UAC should NOT apply local ringing.  There is a very 
> > > important distinction here. According to your draft, when a UAC 
> > > receives a 180 it should be prepared to generate local 
> ringing, and 
> > > it is a matter of local policy what the UAC should do 
> when there is 
> > > concurrent in-band media.  Gateway resources should be 
> allocated to 
> > > detect in-band media and decide whether or not to generate 
> > > ringing.  But under some circumstances the UAS knows that 
> > > call progress information is available in-band and the UAC 
> > > does not need to bother to allocate extra resources to 
> > > monitor the media flow and optionally inject ringing.  I 
> > > believe it is important for a UAS to be able to indicate this 
> > > situation to a UAC.  These are processing ! 
> > > resources that could be put to use elsewhere.  There are no 
> > > race conditions in this situation - only the recognition that 
> > > local ringing and packet detection are unnecessary. 
> > > 
> > > I stand by my original suggestion and continue to request 
> a modest 
> > > addition to your draft based on this general approach (my 
> previous 
> > > email indicates one possible detailed solution).  Please 
> let me know 
> > > if you see any further issues. 
> > > 
> > > Regards, 
> > > Richard Ejzak 
> > > Lucent Technologies 
> > > 
> > > 
> > > 
> > > -----Original Message----- 
> > > From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se <mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > > Sent: Tuesday, March 04, 2003 5:42 AM 
> > > To: Ejzak, Richard P (Richard) 
> > > Cc: sipping 
> > > Subject: Re: [Sipping] New version of the early media draft 
> > > 
> > > 
> > > Ejzak, 
> > > 
> > > the main problem with any SIP-layer mechanism that allows 
> the UAS to 
> > 
> > > tell the UAC whether local ringback has to be generated or not is 
> > race 
> > > conditions. It really does not matter whether you use an 
> Alert-Info 
> > > header field in a reponse, or a special status code, or a special 
> > > body, or whatever to signal it. You always have race conditions. 
> > > 
> > > Let's say that the UAS tells the UAC to generate local ringback. 
> > > After a while, the callee picks up. The UAS sends back a 
> 200 OK and 
> > > starts sending media. The 200 OK, for some reason, arrives much 
> > > later than the 
> > > first media packets... what is the UAC supposed to do in the 
> > > mean time? 
> > > Ignore the media? Play the media anyway? 
> > > 
> > > Another scenario. The UAC starts receiving media before a 
> > provisional 
> > > response is received... what does it have to do? 
> > > 
> > > The main point is that, since signalling and media are loosely 
> > > synchronized, you will always have race conditions and 
> you will have 
> > > to make guesses about what to do during those race conditions 
> > > anyway. 
> > > 
> > > Thanks, 
> > > 
> > > Gonzalo 
> > > 
> > > 
> > > 
> > > "Ejzak, Richard P (Richard)" wrote: 
> > > > 
> > > > Gonzalo, 
> > > > It seems the single greatest difficulty with the gateway 
> > > model (as you point out in your draft) is the difficulty of 
> > > depending on the arrival of media packets to determine whether or 
> > > not to generate local ringing.  I have previously (last summer) 
> > > suggested a solution to this (use 180 exclusively to 
> indicate that 
> > > local ringing should override any inband media and 183 otherwise) 
> > > that is unacceptable since it does not satisfy the 
> requirement that 
> > > 180 be used to indicate alerting of the called party. 
> > > > 
> > > > Have you considered using the Alert-Info header in the 
> > > following way? Since the real problem is that we would like to be 
> > > able to discriminate between cases when 180 should cause local 
> > > ringing and when 180 should not (since inband media is 
> available), 
> > > and it is the UAS that knows conclusively which case 
> applies, let's 
> > > agree on an encoding of the Alert-Info header that indicates that 
> > > local ringing should not be applied.  The following line is a 
> > > syntactically valid header: 
> > > > 
> > > > Alert-Info: <data:,> 
> > > > 
> > > > This header identifies the Alert-Info as the null string, 
> > > which seems unambiguously and efficiently interpretable 
> within a 180 
> > > response as "do not play local ringing even though the 
> called party 
> > > is being alerted."  If the UAC does not recognize it or 
> chooses not 
> > > to interpret it for security reasons, it can be safely ignored. 
> > > > 
> > > > This modest addition to your draft (or an equivalent 
> > > mechanism) would make it unnecessary for the gateway 
> model to depend 
> > > on local policy or incoming media packet detection and is 
> completely 
> > > consistent with all of the constraints you have documented. 
> > > > 
> > > > Another approach may be to actually specify the rtp stream 
> > > as the source of the alert info (although this would require the 
> > > definition of a new URI scheme type).  It might look like: 
> > > > 
> > > > Alert-Info: <rtp:/12.34.56.78:90> 
> > > > 
> > > > where the Alert-Info specifies the address and port of the 
> > > rtp stream.  I don't like this mechanism since it is 
> redundant with 
> > > SDP and prone to error.  It is also ambiguous in the event of any 
> > > subsequent media change using UPDATE (Do I begin to 
> generate local 
> > > ringing if the rtp stream source address changes?  Or do 
> I continue 
> > > to listen to the address specified in the Alert-Info and 
> ignore any 
> > > UPDATEs?  No to both.) 
> > > > 
> > > > May I suggest including such a mechanism (preferably the 
> > > first one) in your draft. 
> > > > 
> > > > Richard Ejzak 
> > > > Lucent Technologies 
> > > > 
> > > > -----Original Message----- 
> > > > From: Gonzalo Camarillo 
> [ mailto:Gonzalo.Camarillo@lmf.ericsson.se <mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > 
> > > > Sent: Monday, February 10, 2003 5:41 AM 
> > > > To: sipping 
> > > > Subject: [Sipping] New version of the early media draft 
> > > > 
> > > > Folks, 
> > > > 
> > > > I have just sumitted a new version of the early media 
> > > draft. Until it 
> > > > appears in the archives, you can fetch it from: 
> > > > 
> > > > 
> > 
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-e <http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-e>  
> > arly-media-01.txt 
> > 
> > > 
> > > I have included all the (long and useful) discussions we 
> had in the 
> > > mailing list. Therefore, the draft now keeps separate the 
> "gateway" 
> > and 
> > > the "application server" models. I have also removed the parts we 
> > did 
> > > not agree on. 
> > > 
> > > Feedback is, as usual, appreciated. 
> > > 
> > > Thanks, 
> > > 
> > > Gonzalo 
> > > _______________________________________________ 
> > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping <https://www1.ietf.org/mailman/listinfo/sipping>  
> > 
> > > This 
> list is for NEW development of the application of SIP Use 
> > > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > > sip@ietf.org for new developments of core SIP 
> > 
> > -- 
> > Gonzalo Camarillo         Phone :  +358  9 299 33 71 
> > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35 
> > Telecom R&D               Fax   :  +358  9 299 30 52 
> > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com 
> > Finland                   http://www.hut.fi/~gonzalo <http://www.hut.fi/~gonzalo>  
> > _______________________________________________ 
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping <https://www1.ietf.org/mailman/listinfo/sipping>  
> > This list is for NEW development of the application of SIP Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sip@ietf.org for new developments of core SIP 
> 
> -- 
> Gonzalo Camarillo         Phone :  +358  9 299 33 71 
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35 
> Telecom R&D               Fax   :  +358  9 299 30 52 
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com 
> Finland                   http://www.hut.fi/~gonzalo <http://www.hut.fi/~gonzalo>  
> _______________________________________________ 
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping <https://www1.ietf.org/mailman/listinfo/sipping>  
> This list is for NEW development of the application of SIP 
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP 
> 


------_=_NextPart_001_01C2E367.EA97C7EC
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.50.4922.900" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=576534921-05032003>Francois,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=576534921-05032003>I am 
comfortable with either meaning, and understand the preference expressed for 
(2).&nbsp; I have a strong preference for using the Alert-Info header to provide 
this indication, however, since it exists.&nbsp; It took me quite a while to 
come up with a syntactically valid absoluteURI (using the data scheme type) that 
could be immediately parsed to mean "null."&nbsp; (Note that the Alert-Info 
header requires an absoluteURI.)&nbsp; I think it would be a real abuse of this 
mechanism to include any text in the URI other than the null string (i.e. 
Alert-Info: &lt;data:,&gt;) to make it more "meaningful" (e.g. Alert-Info: 
&lt;data:,In-band Alerting&gt;).&nbsp; Perhaps others don't share my concern 
here.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=576534921-05032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=576534921-05032003>Do you 
think a null Alert-Info is sufficient to indicate in-band alerting?&nbsp; (To me 
(1) is a more natural interpretation of null Alert-Info, but I don't have a 
problem with (2).)&nbsp; Or do you have another suggestion?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=576534921-05032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=576534921-05032003>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=576534921-05032003>Richard Ejzak</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=576534921-05032003>Lucent 
Technologies</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Francois Audet 
  [mailto:audet@nortelnetworks.com]<BR><B>Sent:</B> Wednesday, March 05, 2003 
  2:07 PM<BR><B>To:</B> 'Gonzalo Camarillo'; Mark Watson<BR><B>Cc:</B> 'Ejzak, 
  Richard P (Richard)'; 'sipping'<BR><B>Subject:</B> RE: [Sipping] New version 
  of the early media draft<BR><BR></FONT></DIV>
  <P><FONT size=2>Would this alert info say:</FONT> <BR><FONT size=2>1 - Do not 
  play local ringback, or</FONT> <BR><FONT size=2>2 - In-band alerting 
  indication present?</FONT> </P>
  <P><FONT size=2>My take is that 2 makes more sense since (1) is only 
  applicable to</FONT> <BR><FONT size=2>telephony applications.</FONT> </P>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: Gonzalo Camarillo [<A 
  href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>] 
  </FONT><BR><FONT size=2>&gt; Sent: Wednesday, March 05, 2003 10:22 AM</FONT> 
  <BR><FONT size=2>&gt; To: Watson, Mark [MOP:EP10:EXCH]</FONT> <BR><FONT 
  size=2>&gt; Cc: 'Ejzak, Richard P (Richard)'; sipping</FONT> <BR><FONT 
  size=2>&gt; Subject: Re: [Sipping] New version of the early media draft</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; Mark,</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  many of your points have been discussed either in the draft </FONT><BR><FONT 
  size=2>&gt; or in the mailing list before. The MGC-MG decomposition 
  </FONT><BR><FONT size=2>&gt; problem is discussed in the draft, and the 
  indication of the </FONT><BR><FONT size=2>&gt; presence in-band media was 
  discussed in the previous version </FONT><BR><FONT size=2>&gt; of the 
  draft.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; My initial 
  proposal was to include an SDP parameter that </FONT><BR><FONT size=2>&gt; 
  provided information about the intention of the sender. That </FONT><BR><FONT 
  size=2>&gt; is, the sender intended to send early media... that was seen 
  </FONT><BR><FONT size=2>&gt; as too complex (and I agree with that, by the 
  way).</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; But using some 
  type of *simpler* mechanism that only </FONT><BR><FONT size=2>&gt; indicates 
  that the UAS does not want the UAC to generate </FONT><BR><FONT size=2>&gt; 
  local ringback (like the mechanism proposed in this thread), </FONT><BR><FONT 
  size=2>&gt; would be sensible, IMO. </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; How do people feel about using the header field 
  below in a </FONT><BR><FONT size=2>&gt; 18x response to indicate that the UAS 
  would like the UAC not </FONT><BR><FONT size=2>&gt; to provide local ringback 
  (as proposed previously in this thread)?</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; Alert-Info: &lt;data:,&gt;</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; To me, once we have defined 
  Alert-Info, this is not an </FONT><BR><FONT size=2>&gt; unreasonable thing to 
  do with this header. Opinions?</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; Gonzalo</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; Mark Watson wrote:</FONT> <BR><FONT size=2>&gt; 
  &gt; </FONT><BR><FONT size=2>&gt; &gt; Gonzalo,</FONT> <BR><FONT size=2>&gt; 
  &gt; </FONT><BR><FONT size=2>&gt; &gt; I would support this addition (or 
  something like it - I </FONT><BR><FONT size=2>&gt; confess to not 
  </FONT><BR><FONT size=2>&gt; &gt; having followed all the details of this 
  thread).</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
  This same problem has come up again and again over the last </FONT><BR><FONT 
  size=2>&gt; two years. </FONT><BR><FONT size=2>&gt; &gt; The root issue is a 
  distinction between explicit application layer </FONT><BR><FONT size=2>&gt; 
  &gt; indications and implicit media layer indications. If the UAC is a 
  </FONT><BR><FONT size=2>&gt; &gt; distributed system (e.g. Media Gateway and 
  Media Gateway </FONT><BR><FONT size=2>&gt; Controller), </FONT><BR><FONT 
  size=2>&gt; &gt; then the general model is that the MG is controlled by the 
  MGC. The </FONT><BR><FONT size=2>&gt; &gt; MGC has only explicit app. layer 
  indications to work from - </FONT><BR><FONT size=2>&gt; it cannot 
  </FONT><BR><FONT size=2>&gt; &gt; take actions on the basis of receipt of not 
  of media </FONT><BR><FONT size=2>&gt; packets because </FONT><BR><FONT 
  size=2>&gt; &gt; it does not see them.</FONT> <BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; Sure, the MG can report and 'RTP received' 
  event and the </FONT><BR><FONT size=2>&gt; MGC can then </FONT><BR><FONT 
  size=2>&gt; &gt; instruct it appropriately, but this takes time &amp; I don't 
  think it's </FONT><BR><FONT size=2>&gt; &gt; standardised.</FONT> <BR><FONT 
  size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; So, there should be enough 
  information *in the SIP </FONT><BR><FONT size=2>&gt; signalling* for the 
  </FONT><BR><FONT size=2>&gt; &gt; UAC to take an intelligent decision on 
  whether to play </FONT><BR><FONT size=2>&gt; media or local </FONT><BR><FONT 
  size=2>&gt; &gt; ringing. I don't want to prescribe how it takes this 
  </FONT><BR><FONT size=2>&gt; decision, but at </FONT><BR><FONT size=2>&gt; 
  &gt; present there is information available to the UAS at the SIP layer 
  </FONT><BR><FONT size=2>&gt; &gt; which is not communicated to the UAC (at the 
  SIP layer) - </FONT><BR><FONT size=2>&gt; namely the </FONT><BR><FONT 
  size=2>&gt; &gt; availability of in-band media. This can only result in the 
  </FONT><BR><FONT size=2>&gt; UAC taking </FONT><BR><FONT size=2>&gt; &gt; 
  inappropriate decisions in some scenarios.</FONT> <BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; Perhaps we should not be telling the UAC to 
  'play local ringing' or </FONT><BR><FONT size=2>&gt; &gt; 'don't play local 
  ringing', but if the UAS knows there is in-band </FONT><BR><FONT size=2>&gt; 
  &gt; information, it should tell the UAC in SIP.</FONT> <BR><FONT size=2>&gt; 
  &gt; </FONT><BR><FONT size=2>&gt; &gt; Regards...Mark</FONT> <BR><FONT 
  size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; &gt; -----Original 
  Message-----</FONT> <BR><FONT size=2>&gt; &gt; &gt; From: Ejzak, Richard P 
  (Richard) [<A 
  href="mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; Sent: 04 March 2003 19:15</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; To: 'Gonzalo Camarillo'</FONT> <BR><FONT size=2>&gt; &gt; &gt; Cc: 
  sipping</FONT> <BR><FONT size=2>&gt; &gt; &gt; Subject: RE: [Sipping] New 
  version of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  Gonzalo,</FONT> <BR><FONT size=2>&gt; &gt; &gt; Thanks for your 
  response.&nbsp; I understand and agree with </FONT><BR><FONT size=2>&gt; your 
  concerns </FONT><BR><FONT size=2>&gt; &gt; &gt; about race conditions as well 
  as the discussion of how to handle </FONT><BR><FONT size=2>&gt; &gt; &gt; 
  them.&nbsp; But I do not want the UAS to blindly control when the UAC 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; should apply local ringing.&nbsp; I 
  want the UAS to be able to </FONT><BR><FONT size=2>&gt; indicate 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; when the UAC should NOT apply local 
  ringing.&nbsp; There is a very </FONT><BR><FONT size=2>&gt; &gt; &gt; 
  important distinction here. According to your draft, when a UAC 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; receives a 180 it should be prepared to 
  generate local </FONT><BR><FONT size=2>&gt; ringing, and </FONT><BR><FONT 
  size=2>&gt; &gt; &gt; it is a matter of local policy what the UAC should do 
  </FONT><BR><FONT size=2>&gt; when there is </FONT><BR><FONT size=2>&gt; &gt; 
  &gt; concurrent in-band media.&nbsp; Gateway resources should be 
  </FONT><BR><FONT size=2>&gt; allocated to</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; detect in-band media and decide whether or not to generate</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; ringing.&nbsp; But under some circumstances 
  the UAS knows that</FONT> <BR><FONT size=2>&gt; &gt; &gt; call progress 
  information is available in-band and the UAC</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; does not need to bother to allocate extra resources to</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; monitor the media flow and optionally inject 
  ringing.&nbsp; I</FONT> <BR><FONT size=2>&gt; &gt; &gt; believe it is 
  important for a UAS to be able to indicate this</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; situation to a UAC.&nbsp; These are processing !</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; resources that could be put to use elsewhere.&nbsp; 
  There are no</FONT> <BR><FONT size=2>&gt; &gt; &gt; race conditions in this 
  situation - only the recognition that</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  local ringing and packet detection are unnecessary.</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; I stand by my 
  original suggestion and continue to request </FONT><BR><FONT size=2>&gt; a 
  modest </FONT><BR><FONT size=2>&gt; &gt; &gt; addition to your draft based on 
  this general approach (my </FONT><BR><FONT size=2>&gt; previous 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; email indicates one possible detailed 
  solution).&nbsp; Please </FONT><BR><FONT size=2>&gt; let me know 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; if you see any further issues.</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  Regards,</FONT> <BR><FONT size=2>&gt; &gt; &gt; Richard Ejzak</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; Lucent Technologies</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; -----Original Message-----</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; From: Gonzalo Camarillo [<A 
  href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; Sent: Tuesday, March 04, 2003 5:42 AM</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; To: Ejzak, Richard P (Richard)</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; Cc: sipping</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; Subject: Re: [Sipping] New version of the early media draft</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; Ejzak,</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; the main problem with any 
  SIP-layer mechanism that allows </FONT><BR><FONT size=2>&gt; the UAS to</FONT> 
  <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; &gt; tell the UAC 
  whether local ringback has to be generated or not is</FONT> <BR><FONT 
  size=2>&gt; &gt; race</FONT> <BR><FONT size=2>&gt; &gt; &gt; conditions. It 
  really does not matter whether you use an </FONT><BR><FONT size=2>&gt; 
  Alert-Info </FONT><BR><FONT size=2>&gt; &gt; &gt; header field in a reponse, 
  or a special status code, or a special </FONT><BR><FONT size=2>&gt; &gt; &gt; 
  body, or whatever to signal it. You always have race conditions.</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; Let's 
  say that the UAS tells the UAC to generate local ringback. </FONT><BR><FONT 
  size=2>&gt; &gt; &gt; After a while, the callee picks up. The UAS sends back a 
  </FONT><BR><FONT size=2>&gt; 200 OK and </FONT><BR><FONT size=2>&gt; &gt; &gt; 
  starts sending media. The 200 OK, for some reason, arrives much</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; later than the</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; first media packets... what is the UAC supposed to do in the</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; mean time?</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; Ignore the media? Play the media anyway?</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; Another scenario. The UAC 
  starts receiving media before a</FONT> <BR><FONT size=2>&gt; &gt; 
  provisional</FONT> <BR><FONT size=2>&gt; &gt; &gt; response is received... 
  what does it have to do?</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; The main point is that, since signalling and 
  media are loosely </FONT><BR><FONT size=2>&gt; &gt; &gt; synchronized, you 
  will always have race conditions and </FONT><BR><FONT size=2>&gt; you will 
  have </FONT><BR><FONT size=2>&gt; &gt; &gt; to make guesses about what to do 
  during those race conditions </FONT><BR><FONT size=2>&gt; &gt; &gt; 
  anyway.</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; Thanks,</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; Gonzalo</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; "Ejzak, Richard P (Richard)" wrote:</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; Gonzalo,</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; It seems the single 
  greatest difficulty with the gateway</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  model (as you point out in your draft) is the difficulty of </FONT><BR><FONT 
  size=2>&gt; &gt; &gt; depending on the arrival of media packets to determine 
  whether or </FONT><BR><FONT size=2>&gt; &gt; &gt; not to generate local 
  ringing.&nbsp; I have previously (last summer) </FONT><BR><FONT size=2>&gt; 
  &gt; &gt; suggested a solution to this (use 180 exclusively to 
  </FONT><BR><FONT size=2>&gt; indicate that </FONT><BR><FONT size=2>&gt; &gt; 
  &gt; local ringing should override any inband media and 183 otherwise) 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; that is unacceptable since it does not 
  satisfy the </FONT><BR><FONT size=2>&gt; requirement that </FONT><BR><FONT 
  size=2>&gt; &gt; &gt; 180 be used to indicate alerting of the called 
  party.</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; Have you considered using the Alert-Info header in 
  the</FONT> <BR><FONT size=2>&gt; &gt; &gt; following way? Since the real 
  problem is that we would like to be </FONT><BR><FONT size=2>&gt; &gt; &gt; 
  able to discriminate between cases when 180 should cause local 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; ringing and when 180 should not (since 
  inband media is </FONT><BR><FONT size=2>&gt; available), </FONT><BR><FONT 
  size=2>&gt; &gt; &gt; and it is the UAS that knows conclusively which case 
  </FONT><BR><FONT size=2>&gt; applies, let's </FONT><BR><FONT size=2>&gt; &gt; 
  &gt; agree on an encoding of the Alert-Info header that indicates that 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; local ringing should not be 
  applied.&nbsp; The following line is a </FONT><BR><FONT size=2>&gt; &gt; &gt; 
  syntactically valid header:</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; Alert-Info: &lt;data:,&gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; This header identifies the Alert-Info as the null string,</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; which seems unambiguously and efficiently 
  interpretable </FONT><BR><FONT size=2>&gt; within a 180 </FONT><BR><FONT 
  size=2>&gt; &gt; &gt; response as "do not play local ringing even though the 
  </FONT><BR><FONT size=2>&gt; called party </FONT><BR><FONT size=2>&gt; &gt; 
  &gt; is being alerted."&nbsp; If the UAC does not recognize it or 
  </FONT><BR><FONT size=2>&gt; chooses not </FONT><BR><FONT size=2>&gt; &gt; 
  &gt; to interpret it for security reasons, it can be safely ignored.</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; This modest addition to your draft (or an equivalent</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; mechanism) would make it unnecessary for the gateway 
  </FONT><BR><FONT size=2>&gt; model to depend </FONT><BR><FONT size=2>&gt; &gt; 
  &gt; on local policy or incoming media packet detection and is 
  </FONT><BR><FONT size=2>&gt; completely </FONT><BR><FONT size=2>&gt; &gt; &gt; 
  consistent with all of the constraints you have documented.</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; Another 
  approach may be to actually specify the rtp stream</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; as the source of the alert info (although this would 
  require the </FONT><BR><FONT size=2>&gt; &gt; &gt; definition of a new URI 
  scheme type).&nbsp; It might look like:</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; Alert-Info: 
  &lt;rtp:/12.34.56.78:90&gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; where the Alert-Info specifies the 
  address and port of the</FONT> <BR><FONT size=2>&gt; &gt; &gt; rtp 
  stream.&nbsp; I don't like this mechanism since it is </FONT><BR><FONT 
  size=2>&gt; redundant with </FONT><BR><FONT size=2>&gt; &gt; &gt; SDP and 
  prone to error.&nbsp; It is also ambiguous in the event of any 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; subsequent media change using UPDATE 
  (Do I begin to </FONT><BR><FONT size=2>&gt; generate local </FONT><BR><FONT 
  size=2>&gt; &gt; &gt; ringing if the rtp stream source address changes?&nbsp; 
  Or do </FONT><BR><FONT size=2>&gt; I continue </FONT><BR><FONT size=2>&gt; 
  &gt; &gt; to listen to the address specified in the Alert-Info and 
  </FONT><BR><FONT size=2>&gt; ignore any </FONT><BR><FONT size=2>&gt; &gt; &gt; 
  UPDATEs?&nbsp; No to both.)</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; May I suggest including such a mechanism 
  (preferably the</FONT> <BR><FONT size=2>&gt; &gt; &gt; first one) in your 
  draft.</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; Richard Ejzak</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; Lucent Technologies</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; -----Original 
  Message-----</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; From: Gonzalo 
  Camarillo </FONT><BR><FONT size=2>&gt; [<A 
  href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
  <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; &gt; &gt; Sent: 
  Monday, February 10, 2003 5:41 AM</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  To: sipping</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; Subject: [Sipping] New 
  version of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; Folks,</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; I have 
  just sumitted a new version of the early media</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; draft. Until it</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; appears 
  in the archives, you can fetch it from:</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; 
  &gt; </FONT><BR><FONT size=2>&gt; <A target=_blank 
  href="http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-e">http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-e</A></FONT> 
  <BR><FONT size=2>&gt; &gt; arly-media-01.txt</FONT> <BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  I have included all the (long and useful) discussions we </FONT><BR><FONT 
  size=2>&gt; had in the </FONT><BR><FONT size=2>&gt; &gt; &gt; mailing list. 
  Therefore, the draft now keeps separate the </FONT><BR><FONT size=2>&gt; 
  "gateway"</FONT> <BR><FONT size=2>&gt; &gt; and</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; the "application server" models. I have also removed the parts 
  we</FONT> <BR><FONT size=2>&gt; &gt; did</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; not agree on.</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; Feedback is, as usual, appreciated.</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; Thanks,</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  Gonzalo</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  _______________________________________________</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; Sipping mailing list&nbsp; </FONT><BR><FONT size=2>&gt; <A 
  target=_blank 
  href="https://www1.ietf.org/mailman/listinfo/sipping">https://www1.ietf.org/mailman/listinfo/sipping</A></FONT> 
  <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; &gt; This 
  </FONT><BR><FONT size=2>&gt; list is for NEW development of the application of 
  SIP Use </FONT><BR><FONT size=2>&gt; &gt; &gt; 
  sip-implementors@cs.columbia.edu for questions on current sip Use 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; sip@ietf.org for new developments of 
  core SIP</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
  --</FONT> <BR><FONT size=2>&gt; &gt; Gonzalo 
  Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; 
  +358&nbsp; 9 299 33 71</FONT> <BR><FONT size=2>&gt; &gt; Oy L M Ericsson 
  Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 35 
  35</FONT> <BR><FONT size=2>&gt; &gt; Telecom 
  R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 52</FONT> <BR><FONT size=2>&gt; 
  &gt; FIN-02420 Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Email :&nbsp; Gonzalo.Camarillo@ericsson.com</FONT> <BR><FONT size=2>&gt; &gt; 
  Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  <A target=_blank 
  href="http://www.hut.fi/~gonzalo">http://www.hut.fi/~gonzalo</A></FONT> 
  <BR><FONT size=2>&gt; &gt; 
  _______________________________________________</FONT> <BR><FONT size=2>&gt; 
  &gt; Sipping mailing list&nbsp; <A target=_blank 
  href="https://www1.ietf.org/mailman/listinfo/sipping">https://www1.ietf.org/mailman/listinfo/sipping</A></FONT> 
  <BR><FONT size=2>&gt; &gt; This list is for NEW development of the application 
  of SIP Use </FONT><BR><FONT size=2>&gt; &gt; sip-implementors@cs.columbia.edu 
  for questions on current sip Use </FONT><BR><FONT size=2>&gt; &gt; 
  sip@ietf.org for new developments of core SIP</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; -- </FONT><BR><FONT size=2>&gt; Gonzalo 
  Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; 
  +358&nbsp; 9 299 33 71</FONT> <BR><FONT size=2>&gt; Oy L M Ericsson 
  Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 35 
  35</FONT> <BR><FONT size=2>&gt; Telecom 
  R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 52</FONT> <BR><FONT size=2>&gt; 
  FIN-02420 Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email 
  :&nbsp; Gonzalo.Camarillo@ericsson.com</FONT> <BR><FONT size=2>&gt; 
  Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  <A target=_blank 
  href="http://www.hut.fi/~gonzalo">http://www.hut.fi/~gonzalo</A></FONT> 
  <BR><FONT size=2>&gt; _______________________________________________</FONT> 
  <BR><FONT size=2>&gt; Sipping mailing list&nbsp; <A target=_blank 
  href="https://www1.ietf.org/mailman/listinfo/sipping">https://www1.ietf.org/mailman/listinfo/sipping</A></FONT> 
  <BR><FONT size=2>&gt; This list is for NEW development of the application of 
  SIP</FONT> <BR><FONT size=2>&gt; Use sip-implementors@cs.columbia.edu for 
  questions on current </FONT><BR><FONT size=2>&gt; sip Use sip@ietf.org for new 
  developments of core SIP</FONT> <BR><FONT size=2>&gt; 
</FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E367.EA97C7EC--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 18:47:47 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06622
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 18:47:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25NwXh02987
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 18:58:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25NwXO02984
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 18:58:33 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06591
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 18:47:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25NvSO02863;
	Wed, 5 Mar 2003 18:57:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25NrcO02709
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 18:53:38 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06430
	for <sipping@ietf.org>; Wed, 5 Mar 2003 18:42:21 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h25Ne9C04479;
	Wed, 5 Mar 2003 23:40:09 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JR4WD>; Wed, 5 Mar 2003 18:40:14 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214EC3@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        Mark Watson
	 <mwatson@nortelnetworks.com>
Cc: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping
	 <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Wed, 5 Mar 2003 18:40:13 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


I don't think that the Alert-Info header proposal will really assuage the
stated problem. Mr. Marshall raised a 'null' Alert-Info proposal in the
previous discussion, and it was rejected then, as it should be now. Here's
the thread:

http://www1.ietf.org/mail-archive/working-groups/sipping/current/msg02545.ht
ml

Null Alert-Info wouldn't express anything more than just sending a 183 does
- a UAS should send a 183 when it knows it has some non-ringing in-band
media. Null Alert-Info certainly wouldn't give you any additional leverage
in cases where media arrives before signaling. I'm not sure what new
properties it would grant. The text already suggests a policy of:

        1.   Unless a 180 (Ringing) response is received, never generate
             local ringback.

... which essentially entails 'don't play local ringback if 183 is
received'. I'm not sure how it would be any better to recommend a similar
(and redundant) policy relating to Alert-Info.

As an aside, I do agree with Mr. Audet that we should discourage mixing
local ringback tones with received media.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: Wednesday, March 05, 2003 10:22 AM
> To: Mark Watson
> Cc: 'Ejzak, Richard P (Richard)'; sipping
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Mark,
> 
> many of your points have been discussed either in the draft or in the
> mailing list before. The MGC-MG decomposition problem is discussed in
> the draft, and the indication of the presence in-band media was
> discussed in the previous version of the draft.
> 
> My initial proposal was to include an SDP parameter that provided
> information about the intention of the sender. That is, the sender
> intended to send early media... that was seen as too complex (and I
> agree with that, by the way).
> 
> But using some type of *simpler* mechanism that only 
> indicates that the
> UAS does not want the UAC to generate local ringback (like 
> the mechanism
> proposed in this thread), would be sensible, IMO. 
> 
> How do people feel about using the header field below in a 
> 18x response
> to indicate that the UAS would like the UAC not to provide local
> ringback (as proposed previously in this thread)?
> 
> Alert-Info: <data:,>
> 
> To me, once we have defined Alert-Info, this is not an unreasonable
> thing to do with this header. Opinions?
> 
> Gonzalo
> 
> 
> Mark Watson wrote:
> > 
> > Gonzalo,
> > 
> > I would support this addition (or something like it - I 
> confess to not
> > having followed all the details of this thread).
> > 
> > This same problem has come up again and again over the last 
> two years.
> > The root issue is a distinction between explicit application layer
> > indications and implicit media layer indications. If the UAC is a
> > distributed system (e.g. Media Gateway and Media Gateway 
> Controller),
> > then the general model is that the MG is controlled by the MGC. The
> > MGC has only explicit app. layer indications to work from - 
> it cannot
> > take actions on the basis of receipt of not of media packets because
> > it does not see them.
> > 
> > Sure, the MG can report and 'RTP received' event and the 
> MGC can then
> > instruct it appropriately, but this takes time & I don't think it's
> > standardised.
> > 
> > So, there should be enough information *in the SIP 
> signalling* for the
> > UAC to take an intelligent decision on whether to play 
> media or local
> > ringing. I don't want to prescribe how it takes this 
> decision, but at
> > present there is information available to the UAS at the SIP layer
> > which is not communicated to the UAC (at the SIP layer) - namely the
> > availability of in-band media. This can only result in the 
> UAC taking
> > inappropriate decisions in some scenarios.
> > 
> > Perhaps we should not be telling the UAC to 'play local ringing' or
> > 'don't play local ringing', but if the UAS knows there is in-band
> > information, it should tell the UAC in SIP.
> > 
> > Regards...Mark
> > 
> > > -----Original Message-----
> > > From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com]
> > > Sent: 04 March 2003 19:15
> > > To: 'Gonzalo Camarillo'
> > > Cc: sipping
> > > Subject: RE: [Sipping] New version of the early media draft
> > >
> > >
> > > Gonzalo,
> > > Thanks for your response.  I understand and agree with your
> > > concerns about race conditions as well as the discussion of
> > > how to handle them.  But I do not want the UAS to blindly
> > > control when the UAC should apply local ringing.  I want the
> > > UAS to be able to indicate when the UAC should NOT apply
> > > local ringing.  There is a very important distinction here.
> > > According to your draft, when a UAC receives a 180 it should
> > > be prepared to generate local ringing, and it is a matter of
> > > local policy what the UAC should do when there is concurrent
> > > in-band media.  Gateway resources should be allocated to
> > > detect in-band media and decide whether or not to generate
> > > ringing.  But under some circumstances the UAS knows that
> > > call progress information is available in-band and the UAC
> > > does not need to bother to allocate extra resources to
> > > monitor the media flow and optionally inject ringing.  I
> > > believe it is important for a UAS to be able to indicate this
> > > situation to a UAC.  These are processing !
> > > resources that could be put to use elsewhere.  There are no
> > > race conditions in this situation - only the recognition that
> > > local ringing and packet detection are unnecessary.
> > >
> > > I stand by my original suggestion and continue to request a
> > > modest addition to your draft based on this general approach
> > > (my previous email indicates one possible detailed solution).
> > >  Please let me know if you see any further issues.
> > >
> > > Regards,
> > > Richard Ejzak
> > > Lucent Technologies
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > Sent: Tuesday, March 04, 2003 5:42 AM
> > > To: Ejzak, Richard P (Richard)
> > > Cc: sipping
> > > Subject: Re: [Sipping] New version of the early media draft
> > >
> > >
> > > Ejzak,
> > >
> > > the main problem with any SIP-layer mechanism that allows 
> the UAS to
> > 
> > > tell the UAC whether local ringback has to be generated or not is
> > race
> > > conditions. It really does not matter whether you use an 
> Alert-Info
> > > header field in a reponse, or a special status code, or a
> > > special body,
> > > or whatever to signal it. You always have race conditions.
> > >
> > > Let's say that the UAS tells the UAC to generate local
> > > ringback. After a
> > > while, the callee picks up. The UAS sends back a 200 OK and starts
> > > sending media. The 200 OK, for some reason, arrives much
> > > later than the
> > > first media packets... what is the UAC supposed to do in the
> > > mean time?
> > > Ignore the media? Play the media anyway?
> > >
> > > Another scenario. The UAC starts receiving media before a
> > provisional
> > > response is received... what does it have to do?
> > >
> > > The main point is that, since signalling and media are loosely
> > > synchronized, you will always have race conditions and you
> > > will have to
> > > make guesses about what to do during those race conditions anyway.
> > >
> > > Thanks,
> > >
> > > Gonzalo
> > >
> > >
> > >
> > > "Ejzak, Richard P (Richard)" wrote:
> > > >
> > > > Gonzalo,
> > > > It seems the single greatest difficulty with the gateway
> > > model (as you point out in your draft) is the difficulty of
> > > depending on the arrival of media packets to determine
> > > whether or not to generate local ringing.  I have previously
> > > (last summer) suggested a solution to this (use 180
> > > exclusively to indicate that local ringing should override
> > > any inband media and 183 otherwise) that is unacceptable
> > > since it does not satisfy the requirement that 180 be used to
> > > indicate alerting of the called party.
> > > >
> > > > Have you considered using the Alert-Info header in the
> > > following way? Since the real problem is that we would like
> > > to be able to discriminate between cases when 180 should
> > > cause local ringing and when 180 should not (since inband
> > > media is available), and it is the UAS that knows
> > > conclusively which case applies, let's agree on an encoding
> > > of the Alert-Info header that indicates that local ringing
> > > should not be applied.  The following line is a syntactically
> > > valid header:
> > > >
> > > > Alert-Info: <data:,>
> > > >
> > > > This header identifies the Alert-Info as the null string,
> > > which seems unambiguously and efficiently interpretable
> > > within a 180 response as "do not play local ringing even
> > > though the called party is being alerted."  If the UAC does
> > > not recognize it or chooses not to interpret it for security
> > > reasons, it can be safely ignored.
> > > >
> > > > This modest addition to your draft (or an equivalent
> > > mechanism) would make it unnecessary for the gateway model to
> > > depend on local policy or incoming media packet detection and
> > > is completely consistent with all of the constraints you have
> > > documented.
> > > >
> > > > Another approach may be to actually specify the rtp stream
> > > as the source of the alert info (although this would require
> > > the definition of a new URI scheme type).  It might look like:
> > > >
> > > > Alert-Info: <rtp:/12.34.56.78:90>
> > > >
> > > > where the Alert-Info specifies the address and port of the
> > > rtp stream.  I don't like this mechanism since it is
> > > redundant with SDP and prone to error.  It is also ambiguous
> > > in the event of any subsequent media change using UPDATE (Do
> > > I begin to generate local ringing if the rtp stream source
> > > address changes?  Or do I continue to listen to the address
> > > specified in the Alert-Info and ignore any UPDATEs?  No to both.)
> > > >
> > > > May I suggest including such a mechanism (preferably the
> > > first one) in your draft.
> > > >
> > > > Richard Ejzak
> > > > Lucent Technologies
> > > >
> > > > -----Original Message-----
> > > > From: Gonzalo Camarillo 
> [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > 
> > > > Sent: Monday, February 10, 2003 5:41 AM
> > > > To: sipping
> > > > Subject: [Sipping] New version of the early media draft
> > > >
> > > > Folks,
> > > >
> > > > I have just sumitted a new version of the early media
> > > draft. Until it
> > > > appears in the archives, you can fetch it from:
> > > >
> > > >
> > 
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s
> ipping-early-media-01.txt
> > 
> > >
> > > I have included all the (long and useful) discussions we 
> had in the
> > > mailing list. Therefore, the draft now keeps separate the 
> "gateway"
> > and
> > > the "application server" models. I have also removed the parts we
> > did
> > > not agree on.
> > >
> > > Feedback is, as usual, appreciated.
> > >
> > > Thanks,
> > >
> > > Gonzalo
> > > _______________________________________________
> > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > 
> > > This list is for NEW development of the application of SIP
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sip@ietf.org for new developments of core SIP
> > 
> > --
> > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > Telecom R&D               Fax   :  +358  9 299 30 52
> > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> > Finland                   http://www.hut.fi/~gonzalo
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> 
> -- 
> Gonzalo Camarillo         Phone :  +358  9 299 33 71
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> Telecom R&D               Fax   :  +358  9 299 30 52
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> Finland                   http://www.hut.fi/~gonzalo
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 19:50:58 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08575
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 19:50:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2611jA07514
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 20:01:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2611jO07511
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 20:01:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08566
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 19:50:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2610hO07461;
	Wed, 5 Mar 2003 20:00:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h260xFO07371
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 19:59:15 -0500
Received: from zrc2s0jx.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08519
	for <sipping@ietf.org>; Wed, 5 Mar 2003 19:47:56 -0500 (EST)
Received: from zsc3c028.us.nortel.com (zsc3c028.us.nortel.com [47.81.138.28])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h260nm020854;
	Wed, 5 Mar 2003 18:49:49 -0600 (CST)
Received: by zsc3c028.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1LW2L83S>; Wed, 5 Mar 2003 16:49:48 -0800
Message-ID: <2F1FC1DEA077D5119FAD00508BCFD6D20700CB6A@zsc3c030.us.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        "Mark Watson" <mwatson@nortelnetworks.com>
Cc: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'sipping'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Wed, 5 Mar 2003 16:49:49 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E37A.4A42D788"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E37A.4A42D788
Content-Type: text/plain

I agree with Jon's proposal of stating explicitly that 183 implies 
that local ringback should not be used. 

The null Alert-Info seems a little cludgy (and redundant) to me.

The way I am reading RFC3261, I see that Alert-Info can NOT be used
in 183 (only in INVITE or 180). This makes sense to me. Is this
true?

If this is correct, then the procedures seems consistent to me:
1  - 183 Progress. Implies NO locally generated alerting (i.e., it
     is NOT 180, and can not have Alert-Info). In-band media can be
     present.
2a - 180 with Alert-Info. You can play the Alert-Info (can potentially
     be overridden by in-band media based on local policy)
2b - 180 without Alert-Info. You can provide locally generated default
     treatment (can potentially be overridden by in-band media, based
     on local policy). The fact that no Alert-Info is present simply
     means that default treatment can be provided.

I really hope we can settle this thing once and for all...

> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz] 
> Sent: Wednesday, March 05, 2003 3:40 PM
> To: 'Gonzalo Camarillo'; Watson, Mark [MOP:EP10:EXCH]
> Cc: 'Ejzak, Richard P (Richard)'; sipping
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> 
> I don't think that the Alert-Info header proposal will really 
> assuage the stated problem. Mr. Marshall raised a 'null' 
> Alert-Info proposal in the previous discussion, and it was 
> rejected then, as it should be now. Here's the thread:
> 
> http://www1.ietf.org/mail-archive/working-groups/sipping/curre
> nt/msg02545.ht
> ml
> 
> Null Alert-Info wouldn't express anything more than just 
> sending a 183 does
> - a UAS should send a 183 when it knows it has some 
> non-ringing in-band media. Null Alert-Info certainly wouldn't 
> give you any additional leverage in cases where media arrives 
> before signaling. I'm not sure what new properties it would 
> grant. The text already suggests a policy of:
> 
>         1.   Unless a 180 (Ringing) response is received, 
> never generate
>              local ringback.
> 
> ... which essentially entails 'don't play local ringback if 
> 183 is received'. I'm not sure how it would be any better to 
> recommend a similar (and redundant) policy relating to Alert-Info.
> 
> As an aside, I do agree with Mr. Audet that we should 
> discourage mixing local ringback tones with received media.
> 
> Jon Peterson
> NeuStar, Inc.

------_=_NextPart_001_01C2E37A.4A42D788
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I agree with Jon's proposal of stating explicitly =
that 183 implies </FONT>
<BR><FONT SIZE=3D2>that local ringback should not be used. </FONT>
</P>

<P><FONT SIZE=3D2>The null Alert-Info seems a little cludgy (and =
redundant) to me.</FONT>
</P>

<P><FONT SIZE=3D2>The way I am reading RFC3261, I see that Alert-Info =
can NOT be used</FONT>
<BR><FONT SIZE=3D2>in 183 (only in INVITE or 180). This makes sense to =
me. Is this</FONT>
<BR><FONT SIZE=3D2>true?</FONT>
</P>

<P><FONT SIZE=3D2>If this is correct, then the procedures seems =
consistent to me:</FONT>
<BR><FONT SIZE=3D2>1&nbsp; - 183 Progress. Implies NO locally generated =
alerting (i.e., it</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; is NOT 180, and can not =
have Alert-Info). In-band media can be</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; present.</FONT>
<BR><FONT SIZE=3D2>2a - 180 with Alert-Info. You can play the =
Alert-Info (can potentially</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; be overridden by in-band =
media based on local policy)</FONT>
<BR><FONT SIZE=3D2>2b - 180 without Alert-Info. You can provide locally =
generated default</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; treatment (can potentially =
be overridden by in-band media, based</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; on local policy). The fact =
that no Alert-Info is present simply</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; means that default =
treatment can be provided.</FONT>
</P>

<P><FONT SIZE=3D2>I really hope we can settle this thing once and for =
all...</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Peterson, Jon [<A =
HREF=3D"mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz=
</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, March 05, 2003 3:40 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Gonzalo Camarillo'; Watson, Mark =
[MOP:EP10:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'Ejzak, Richard P (Richard)'; =
sipping</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I don't think that the Alert-Info header =
proposal will really </FONT>
<BR><FONT SIZE=3D2>&gt; assuage the stated problem. Mr. Marshall raised =
a 'null' </FONT>
<BR><FONT SIZE=3D2>&gt; Alert-Info proposal in the previous discussion, =
and it was </FONT>
<BR><FONT SIZE=3D2>&gt; rejected then, as it should be now. Here's the =
thread:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www1.ietf.org/mail-archive/working-groups/sipping/curre" =
TARGET=3D"_blank">http://www1.ietf.org/mail-archive/working-groups/sippi=
ng/curre</A></FONT>
<BR><FONT SIZE=3D2>&gt; nt/msg02545.ht</FONT>
<BR><FONT SIZE=3D2>&gt; ml</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Null Alert-Info wouldn't express anything more =
than just </FONT>
<BR><FONT SIZE=3D2>&gt; sending a 183 does</FONT>
<BR><FONT SIZE=3D2>&gt; - a UAS should send a 183 when it knows it has =
some </FONT>
<BR><FONT SIZE=3D2>&gt; non-ringing in-band media. Null Alert-Info =
certainly wouldn't </FONT>
<BR><FONT SIZE=3D2>&gt; give you any additional leverage in cases where =
media arrives </FONT>
<BR><FONT SIZE=3D2>&gt; before signaling. I'm not sure what new =
properties it would </FONT>
<BR><FONT SIZE=3D2>&gt; grant. The text already suggests a policy =
of:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1.&nbsp;&nbsp; Unless a 180 (Ringing) response is received, </FONT>
<BR><FONT SIZE=3D2>&gt; never generate</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; local ringback.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; ... which essentially entails 'don't play local =
ringback if </FONT>
<BR><FONT SIZE=3D2>&gt; 183 is received'. I'm not sure how it would be =
any better to </FONT>
<BR><FONT SIZE=3D2>&gt; recommend a similar (and redundant) policy =
relating to Alert-Info.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; As an aside, I do agree with Mr. Audet that we =
should </FONT>
<BR><FONT SIZE=3D2>&gt; discourage mixing local ringback tones with =
received media.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Jon Peterson</FONT>
<BR><FONT SIZE=3D2>&gt; NeuStar, Inc.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E37A.4A42D788--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar  5 21:44:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10658
	for <sipping-archive@odin.ietf.org>; Wed, 5 Mar 2003 21:44:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h262tJL14511
	for sipping-archive@odin.ietf.org; Wed, 5 Mar 2003 21:55:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h262tIO14508
	for <sipping-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 21:55:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10649
	for <sipping-web-archive@ietf.org>; Wed, 5 Mar 2003 21:43:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h262sTO14437;
	Wed, 5 Mar 2003 21:54:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h262r7O14388
	for <sipping@optimus.ietf.org>; Wed, 5 Mar 2003 21:53:07 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10588
	for <sipping@ietf.org>; Wed, 5 Mar 2003 21:41:47 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h262haC06508;
	Thu, 6 Mar 2003 02:43:36 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JRVS9>; Wed, 5 Mar 2003 21:43:41 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214EC5@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Francois Audet'" <audet@nortelnetworks.com>,
        "Peterson, Jon"
	 <jon.peterson@neustar.biz>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>,
        Mark Watson
	 <mwatson@nortelnetworks.com>
Cc: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'sipping'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Wed, 5 Mar 2003 21:43:40 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E38A.31F1D700"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E38A.31F1D700
Content-Type: text/plain;
	charset="iso-8859-1"

 
Just to be clear, I wasn't arguing for any changes to the existing text. I
was just saying that the current text describes (but does mandate) a local
policy which entails that 183 would not result in local ringback. I think
the existing text can stand.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Francois Audet [mailto:audet@nortelnetworks.com]
Sent: Wednesday, March 05, 2003 4:50 PM
To: 'Peterson, Jon'; 'Gonzalo Camarillo'; Mark Watson
Cc: 'Ejzak, Richard P (Richard)'; 'sipping'
Subject: RE: [Sipping] New version of the early media draft



I agree with Jon's proposal of stating explicitly that 183 implies 
that local ringback should not be used. 

The null Alert-Info seems a little cludgy (and redundant) to me. 

The way I am reading RFC3261, I see that Alert-Info can NOT be used 
in 183 (only in INVITE or 180). This makes sense to me. Is this 
true? 

If this is correct, then the procedures seems consistent to me: 
1  - 183 Progress. Implies NO locally generated alerting (i.e., it 
     is NOT 180, and can not have Alert-Info). In-band media can be 
     present. 
2a - 180 with Alert-Info. You can play the Alert-Info (can potentially 
     be overridden by in-band media based on local policy) 
2b - 180 without Alert-Info. You can provide locally generated default 
     treatment (can potentially be overridden by in-band media, based 
     on local policy). The fact that no Alert-Info is present simply 
     means that default treatment can be provided. 

I really hope we can settle this thing once and for all... 

> -----Original Message----- 
> From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> Sent: Wednesday, March 05, 2003 3:40 PM 
> To: 'Gonzalo Camarillo'; Watson, Mark [MOP:EP10:EXCH] 
> Cc: 'Ejzak, Richard P (Richard)'; sipping 
> Subject: RE: [Sipping] New version of the early media draft 
> 
> 
> 
> I don't think that the Alert-Info header proposal will really 
> assuage the stated problem. Mr. Marshall raised a 'null' 
> Alert-Info proposal in the previous discussion, and it was 
> rejected then, as it should be now. Here's the thread: 
> 
> http://www1.ietf.org/mail-archive/working-groups/sipping/curre
<http://www1.ietf.org/mail-archive/working-groups/sipping/curre>  
> nt/msg02545.ht 
> ml 
> 
> Null Alert-Info wouldn't express anything more than just 
> sending a 183 does 
> - a UAS should send a 183 when it knows it has some 
> non-ringing in-band media. Null Alert-Info certainly wouldn't 
> give you any additional leverage in cases where media arrives 
> before signaling. I'm not sure what new properties it would 
> grant. The text already suggests a policy of: 
> 
>         1.   Unless a 180 (Ringing) response is received, 
> never generate 
>              local ringback. 
> 
> ... which essentially entails 'don't play local ringback if 
> 183 is received'. I'm not sure how it would be any better to 
> recommend a similar (and redundant) policy relating to Alert-Info. 
> 
> As an aside, I do agree with Mr. Audet that we should 
> discourage mixing local ringback tones with received media. 
> 
> Jon Peterson 
> NeuStar, Inc. 


------_=_NextPart_001_01C2E38A.31F1D700
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=553064302-06032003>Just 
to be clear, I wasn't arguing for any changes to the existing text. I was just 
saying that the current text describes (but does mandate) a local policy which 
entails that 183 would not result in local ringback. I think the existing text 
can stand.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><SPAN class=553064302-06032003><FONT face=Arial color=#0000ff size=2>Jon 
Peterson</FONT></SPAN></DIV>
<DIV><SPAN class=553064302-06032003><FONT face=Arial color=#0000ff 
size=2>NeuStar, Inc.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Francois Audet 
  [mailto:audet@nortelnetworks.com]<BR><B>Sent:</B> Wednesday, March 05, 2003 
  4:50 PM<BR><B>To:</B> 'Peterson, Jon'; 'Gonzalo Camarillo'; Mark 
  Watson<BR><B>Cc:</B> 'Ejzak, Richard P (Richard)'; 
  'sipping'<BR><B>Subject:</B> RE: [Sipping] New version of the early media 
  draft<BR><BR></FONT></DIV>
  <P><FONT size=2>I agree with Jon's proposal of stating explicitly that 183 
  implies </FONT><BR><FONT size=2>that local ringback should not be used. 
  </FONT></P>
  <P><FONT size=2>The null Alert-Info seems a little cludgy (and redundant) to 
  me.</FONT> </P>
  <P><FONT size=2>The way I am reading RFC3261, I see that Alert-Info can NOT be 
  used</FONT> <BR><FONT size=2>in 183 (only in INVITE or 180). This makes sense 
  to me. Is this</FONT> <BR><FONT size=2>true?</FONT> </P>
  <P><FONT size=2>If this is correct, then the procedures seems consistent to 
  me:</FONT> <BR><FONT size=2>1&nbsp; - 183 Progress. Implies NO locally 
  generated alerting (i.e., it</FONT> <BR><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp; 
  is NOT 180, and can not have Alert-Info). In-band media can be</FONT> 
  <BR><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp; present.</FONT> <BR><FONT size=2>2a 
  - 180 with Alert-Info. You can play the Alert-Info (can potentially</FONT> 
  <BR><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp; be overridden by in-band media based 
  on local policy)</FONT> <BR><FONT size=2>2b - 180 without Alert-Info. You can 
  provide locally generated default</FONT> <BR><FONT 
  size=2>&nbsp;&nbsp;&nbsp;&nbsp; treatment (can potentially be overridden by 
  in-band media, based</FONT> <BR><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp; on local 
  policy). The fact that no Alert-Info is present simply</FONT> <BR><FONT 
  size=2>&nbsp;&nbsp;&nbsp;&nbsp; means that default treatment can be 
  provided.</FONT> </P>
  <P><FONT size=2>I really hope we can settle this thing once and for 
  all...</FONT> </P>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: Peterson, Jon [<A 
  href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>] 
  </FONT><BR><FONT size=2>&gt; Sent: Wednesday, March 05, 2003 3:40 PM</FONT> 
  <BR><FONT size=2>&gt; To: 'Gonzalo Camarillo'; Watson, Mark 
  [MOP:EP10:EXCH]</FONT> <BR><FONT size=2>&gt; Cc: 'Ejzak, Richard P (Richard)'; 
  sipping</FONT> <BR><FONT size=2>&gt; Subject: RE: [Sipping] New version of the 
  early media draft</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; I don't think that 
  the Alert-Info header proposal will really </FONT><BR><FONT size=2>&gt; 
  assuage the stated problem. Mr. Marshall raised a 'null' </FONT><BR><FONT 
  size=2>&gt; Alert-Info proposal in the previous discussion, and it was 
  </FONT><BR><FONT size=2>&gt; rejected then, as it should be now. Here's the 
  thread:</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; <A 
  target=_blank 
  href="http://www1.ietf.org/mail-archive/working-groups/sipping/curre">http://www1.ietf.org/mail-archive/working-groups/sipping/curre</A></FONT> 
  <BR><FONT size=2>&gt; nt/msg02545.ht</FONT> <BR><FONT size=2>&gt; ml</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Null Alert-Info wouldn't 
  express anything more than just </FONT><BR><FONT size=2>&gt; sending a 183 
  does</FONT> <BR><FONT size=2>&gt; - a UAS should send a 183 when it knows it 
  has some </FONT><BR><FONT size=2>&gt; non-ringing in-band media. Null 
  Alert-Info certainly wouldn't </FONT><BR><FONT size=2>&gt; give you any 
  additional leverage in cases where media arrives </FONT><BR><FONT size=2>&gt; 
  before signaling. I'm not sure what new properties it would </FONT><BR><FONT 
  size=2>&gt; grant. The text already suggests a policy of:</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1.&nbsp;&nbsp; 
  Unless a 180 (Ringing) response is received, </FONT><BR><FONT size=2>&gt; 
  never generate</FONT> <BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  local ringback.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; ... 
  which essentially entails 'don't play local ringback if </FONT><BR><FONT 
  size=2>&gt; 183 is received'. I'm not sure how it would be any better to 
  </FONT><BR><FONT size=2>&gt; recommend a similar (and redundant) policy 
  relating to Alert-Info.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; As an aside, I do agree with Mr. Audet that we should 
  </FONT><BR><FONT size=2>&gt; discourage mixing local ringback tones with 
  received media.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Jon 
  Peterson</FONT> <BR><FONT size=2>&gt; NeuStar, Inc.</FONT> 
</P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E38A.31F1D700--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 03:16:24 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27802
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 03:16:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h268RJh12134
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 03:27:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h268RIO12131
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 03:27:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27793
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 03:15:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h268QTO12103;
	Thu, 6 Mar 2003 03:26:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h268HVO11819
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 03:17:31 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27636
	for <sipping@ietf.org>; Thu, 6 Mar 2003 03:06:05 -0500 (EST)
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h26887B3001007;
	Thu, 6 Mar 2003 09:08:07 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id FDVMMVLL; Thu, 6 Mar 2003 09:08:07 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h26886lW013633;
	Thu, 6 Mar 2003 10:08:06 +0200 (EET)
Message-ID: <3E6701E6.834FE6B1@lmf.ericsson.se>
Date: Thu, 06 Mar 2003 10:08:06 +0200
X-Sybari-Trust: de993653 9ffcebbb a5ee123c 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Francois Audet <audet@nortelnetworks.com>
CC: "'sipping'" <sipping@ietf.org>
Subject: Re: [Sipping] New version of the early media draft
References: <2F1FC1DEA077D5119FAD00508BCFD6D206F5AF7D@zsc3c030.us.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Francois,

well, you are right that mixing them would not make a lot of sense... I
guess I will re-phrase that example in the next revision as you
suggested.

Thanks,

Gonzalo

Francois Audet wrote:
> 
> Agreed. I just think that mixing two ringing patterns may yield
> unpredictable
> results. It can be done, but I'm a bit sceptical that phone
> manufacturers will
> actually do this.
> 
> But, as you say, this is just a suggestion, so I don't have any real
> problem
> with the current draft.
> 
> > -----Original Message-----
> > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > Sent: Tuesday, March 04, 2003 3:21 AM
> > To: Audet, Francois [SC100:4K02:EXCH]
> > Cc: 'sipping'
> > Subject: Re: [Sipping] New version of the early media draft
> >
> >
> > Francois,
> >
> > Thanks for the feedback.
> >
> > About your suggestion, the paragraph you are referring to
> > does not recommend any particular behaviour. It only says
> > that one possible choice is mixing them. I do not think that
> > we need to list all possible things a gateway could do in
> > that case. I believe that the reader gets the idea by reading
> > the paragraph as it is (i.e., there are multiple behaviours
> > to choose from).

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 04:32:50 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29486
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 04:32:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h269hkO18409
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 04:43:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h269hkO18406
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 04:43:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29476
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 04:32:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h269cOO18122;
	Thu, 6 Mar 2003 04:38:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2699TO15913
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 04:09:29 -0500
Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28767
	for <sipping@ietf.org>; Thu, 6 Mar 2003 03:58:01 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 6 Mar 2003 01:00:04 -0800
Received: from 203.196.139.114 by lw8fd.law8.hotmail.msn.com with HTTP;
	Thu, 06 Mar 2003 09:00:03 GMT
X-Originating-IP: [203.196.139.114]
From: "banibrata dutta" <bdutta@hotmail.com>
To: rishik@mahindrabt.com, sipforum-discussion@lists.su.se, sipping@ietf.org
Date: Thu, 06 Mar 2003 09:00:03 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F3FJ3sl3xbYiMCIqtQv0000b22e@hotmail.com>
X-OriginalArrivalTime: 06 Mar 2003 09:00:04.0121 (UTC) FILETIME=[C6F7B890:01C2E3BE]
Subject: [Sipping] Re: [Sipforum-discussion] SIP Telephony Device Requirements,Conf iguration
 andData
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

short answer is yes. longer answer is it depends on the SIP device
in question. SIP devices, s.a. the CISCO, Pingtel phones, have no.
of common, and some differentiating "features". Call park, call hold,
call trasfer are some of the business-line features you'd find in
these phones. These features, are nothing but the application of
core-SIP or some SIP-extentions, in form of an application, much
like the traditional PSTN features and services, both IN & non-IN.

--

From: rishi <rishik@mahindrabt.com>
To: banibrata dutta <bdutta@hotmail.com>
CC: sipforum-discussion@lists.su.se, sipping@ietf.org
Subject: Re: [Sipforum-discussion] SIP Telephony Device Requirements,Conf 
iguration andData
Date: Thu, 06 Mar 2003 01:21:03 +0530

Hi folks,
query - Can SIP handle simultaneous session as in ...can we transfer a media 
to
another sip client and talk to someone else at the same time using the same
device?
please help
Regards
Rishi

banibrata dutta wrote:

 > you are absolutely right. SIP, brings the intelligent
 > for call-control right upto the user-agent, i.e. the
 > device used for making a SIP call, but that is just 1
 > of the several possibilities.
 >
 > in the PSTN world we have the Access-network & the
 > Core-network. For the Access-network too we do have
 > protocols s.a. V5, ISDN, apart from the traditional
 > tip/ring protocol.
 >
 > a "residential gateway" is a network-entity that can
 > allow the dumb-black-phones (i.e. non-SIP + analog phone)
 > to connect to the SIP network... somewhat similar in
 > spirit to the NT-1/NT-2 in ISDN n/ws.
 >
 > then there are the signalling gateways which can do
 > interworking between SIP - SS7, SIP - H323, H323 - SS7 etc.
 > infact you need such a gateway everything you make a
 > call that crosses SIP-VoIP network boundary into the PSTN
 > network boundary, and vice-versa.
 >
 > -bdutta.
 >
 > From: rishi <rishik@mahindrabt.com>
 > CC: sipforum-discussion@lists.su.se, sipping@ietf.org
 > Subject: Re: [Sipforum-discussion] SIP Telephony Device Requirements,Conf
 > iguration and Data
 > Date: Wed, 05 Mar 2003 03:48:46 +0530
 >
 > Hi folks,
 > Just got interested in SIP world,would like to know how SIP can be 
related
 > to SS7 as both being signalling protocols,but SIP sits even on the client
 > device where as SS7 is completely invisible to client,and what are the 
major
 > differences of SIP and SS7
 > can some one help me in this ??
 > regards
 > Rishi
 >
 > Henry Sinnreich wrote:
 >
 >  > Franz Edler writes:
 >  >
 >  > >"dual homed" SIP-UA with one "line" connected
 >  > > to the PSTN via V5 - SIP gateway and the other "lines" beeing
 >  > > free for all new services of the SIP world.
 >  >
 >  > Great minds think alike! :-) Some of us had actually the same
 >  > requirements. This may be a MAY...
 >  >
 >  > The authors are still collecting all comments and we plan to 
consolidate
 >  > them with our follow-up into one single reply, for consistency 
reasons.
 >  > Please stay tuned.
 >  >
 >  > Thanks, Henry
 >  >
 >  > I've stopped 2,514 spam messages. You can too!
 >  > Get your free, safe spam protection at
 >  > http://www.cloudmark.com/spamnetsig/
 >  >
 >  > > -----Original Message-----
 >  > > From: Edler Franz [mailto:franz.edler@uta.at]
 >  > > Sent: Friday, February 28, 2003 1:55 AM
 >  > > To: 'Eric Tremblay'; Henry Sinnreich; Jörgen Björkner;
 >  > > sipforum-discussion@lists.su.se
 >  > > Cc: sipping@ietf.org
 >  > > Subject: AW: [Sipforum-discussion] SIP Telephony Device
 >  > > Requirements, Conf iguration and Data
 >  > >
 >  > >
 >  > > Hi folks,
 >  > >
 >  > > just a comment on SIP-25:
 >  > >
 >  > > I am currently working on a PSTN - SIP migration concept
 >  > > avoiding to re-invent all fancy features of the PSTN and in
 >  > > particular to re-implement all legal/regulatory requirements
 >  > > (emergency call handling, legal intercept). The concept
 >  > > builds upon a "dual homed" SIP-UA with one "line" connected
 >  > > to the PSTN via V5 - SIP gateway and the other "lines" beeing
 >  > > free for all new services of the SIP world. Therefore the
 >  > > requirement of multiple identities on the SIP side and a
 >  > > static identitiy on the PSTN side is essential, but I agree,
 >  > > if you are focused on analog adapters only, this would mean
 >  > > an unnecessary burden. But I suggest to re-think the
 >  > > migration perspective.
 >  > >
 >  > > By the way, if anyone is interested in this "dual-homed" PSTN
 >  > > - SIP migration concept let me know. I am convienced that
 >  > > this means a good chance for a carrier to migrate towards SIP
 >  > > without heavy investments in re-inventing what is already existing.
 >  > >
 >  > > kind regards
 >  > > Franz
 >  > >
 >  > > ---------------------------------------------------------------
 >  > > Franz Edler
 >  > > Strategy & Business Development
 >  > >
 >  > > UTA Telekom AG
 >  > > Donau-City-Strasse 11
 >  > > A-1220 Wien
 >  > > T: + 43/1/9009-3310
 >  > > F: + 43/1/9009-93310
 >  > > M: + 43/699/1388 3310
 >  > > mailto:franz.edler@uta.at
 >  > > http://www.uta.at
 >  > > --------------------------------------------------------------
 >  > >
 >  > > > -----Ursprüngliche Nachricht-----
 >  > > > Von:        Eric Tremblay [SMTP:etremblay@mediatrix.com]
 >  > > > Gesendet am:        Mittwoch, 26. Februar 2003 17:41
 >  > > > An: Henry Sinnreich; Jörgen Björkner;
 >  > > sipforum-discussion@lists.su.se
 >  > > > Cc: sipping@ietf.org
 >  > > > Betreff:    RE: [Sipforum-discussion] SIP Telephony Device
 >  > > Requirements,
 >  > > > Configuration and Data
 >  > > >
 >  > > > Hi Henry,
 >  > > >
 >  > > > Here is a somewhat lengthy email with a few comments about the SIP
 >  > > > Telephony Device Requirements draft:
 >  > > >
 >  > > >
 >  > > >   SIP-25, Dynamic login/logout for user mobility: SIP devices MUST
 >  > > >   support user mobility.  SIP clients MUST store a static
 >  > > profile in
 >  > > >   non-volatile memory so that this information is available
 >  > > during the
 >  > > >   power up sequence.  SIP clients MUST allow a user to walk up to 
a
 >  > > >   client, login, and be able to send and receive calls with
 >  > > his profile
 >  > > >   information.
 >  > > >   For emergency numbers (e.g. 911) the client MUST send the
 >  > > credentials
 >  > > >   (username/password) of the static profile.
 >  > > >
 >  > > > [EricT]
 >  > > > We are developing analog adapters and don't remember
 >  > > receiving such a
 >  > > > request. I suggest either changing the MUST to SHOULD or
 >  > > adding some text
 >  > > > to specify that it is a MUST for devices with the proper
 >  > > interface to do
 >  > > > it and a SHOULD for devices with a limited interface. I
 >  > > know we could
 >  > > > possibly configure this through a web interface, but the
 >  > > point is that
 >  > > > there are a lot of vendore that currently just want to
 >  > > replace the wire,
 >  > > > not the phone and its interface...
 >  > > >
 >  > > >
 >  > > >
 >  > > >
 >  > >
 >
 > *********************************************************
 > Disclaimer
 >
 > This message (including any attachments) contains
 > confidential information intended for a specific
 > individual and purpose, and is protected by law.
 > If you are not the intended recipient, you should
 > delete this message and are hereby notified that
 > any disclosure, copying, or distribution of this
 > message, or the taking of any action based on it,
 > is strictly prohibited.
 >
 > *********************************************************
 > Visit us at http://www.mahindrabt.com
 >
 > _________________________________________________________________
 > Cricket World Cup 2003- News, Views and Match Reports.
 > http://server1.msn.co.in/msnspecials/worldcup03/

*********************************************************
Disclaimer

This message (including any attachments) contains
confidential information intended for a specific
individual and purpose, and is protected by law.
If you are not the intended recipient, you should
delete this message and are hereby notified that
any disclosure, copying, or distribution of this
message, or the taking of any action based on it,
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com


_________________________________________________________________
Cricket World Cup 2003- News, Views and Match Reports. 
http://server1.msn.co.in/msnspecials/worldcup03/

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 04:33:05 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29503
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 04:33:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h269i2h18431
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 04:44:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h269i2O18428
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 04:44:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29481
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 04:32:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h269cKO18101;
	Thu, 6 Mar 2003 04:38:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h267qnO10170
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 02:52:49 -0500
Received: from shardagate.mahindrabt.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27147
	for <sipping@ietf.org>; Thu, 6 Mar 2003 02:41:20 -0500 (EST)
Received: from thisdomain (mailscan.sharda.mahindrabt.com [10.5.0.97])
	by shardagate.mahindrabt.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id NAA11960
	for <sipping@ietf.org>; Thu, 6 Mar 2003 13:13:15 +0530
Received: from intranet.sharda.mahindrabt.com by mahindrabt.com ; Thu, 06 Mar 2003 13:00:45 +0530
Date: Thu, 06 Mar 2003 13:00:45 +0530
X-Originating-IP: 10.5.0.15
X-Auth-User: rishik@mahindrabt.com
Received: from mahindrabt.com ([10.5.4.51])
	by intranet.sharda.mahindrabt.com (8.9.3/8.9.3) with ESMTP id NAA08500;
	Thu, 6 Mar 2003 13:13:05 +0530
Message-ID: <3E665526.38F7E31C@mahindrabt.com>
Date: Thu, 06 Mar 2003 01:21:03 +0530
From: rishi <rishik@mahindrabt.com>
Organization: MBT
X-Mailer: Mozilla 4.74 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: banibrata dutta <bdutta@hotmail.com>
CC: sipforum-discussion@lists.su.se, sipping@ietf.org
References: <F81sg8Kyg8COSd3CMMk00002d59@hotmail.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sipping] Re: [Sipforum-discussion] SIP Telephony Device Requirements,Conf
 iguration andData
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi folks,
query - Can SIP handle simultaneous session as in ...can we transfer a media to
another sip client and talk to someone else at the same time using the same
device?
please help
Regards
Rishi

banibrata dutta wrote:

> you are absolutely right. SIP, brings the intelligent
> for call-control right upto the user-agent, i.e. the
> device used for making a SIP call, but that is just 1
> of the several possibilities.
>
> in the PSTN world we have the Access-network & the
> Core-network. For the Access-network too we do have
> protocols s.a. V5, ISDN, apart from the traditional
> tip/ring protocol.
>
> a "residential gateway" is a network-entity that can
> allow the dumb-black-phones (i.e. non-SIP + analog phone)
> to connect to the SIP network... somewhat similar in
> spirit to the NT-1/NT-2 in ISDN n/ws.
>
> then there are the signalling gateways which can do
> interworking between SIP - SS7, SIP - H323, H323 - SS7 etc.
> infact you need such a gateway everything you make a
> call that crosses SIP-VoIP network boundary into the PSTN
> network boundary, and vice-versa.
>
> -bdutta.
>
> From: rishi <rishik@mahindrabt.com>
> CC: sipforum-discussion@lists.su.se, sipping@ietf.org
> Subject: Re: [Sipforum-discussion] SIP Telephony Device Requirements,Conf
> iguration and Data
> Date: Wed, 05 Mar 2003 03:48:46 +0530
>
> Hi folks,
> Just got interested in SIP world,would like to know how SIP can be related
> to SS7 as both being signalling protocols,but SIP sits even on the client
> device where as SS7 is completely invisible to client,and what are the major
> differences of SIP and SS7
> can some one help me in this ??
> regards
> Rishi
>
> Henry Sinnreich wrote:
>
>  > Franz Edler writes:
>  >
>  > >"dual homed" SIP-UA with one "line" connected
>  > > to the PSTN via V5 - SIP gateway and the other "lines" beeing
>  > > free for all new services of the SIP world.
>  >
>  > Great minds think alike! :-) Some of us had actually the same
>  > requirements. This may be a MAY...
>  >
>  > The authors are still collecting all comments and we plan to consolidate
>  > them with our follow-up into one single reply, for consistency reasons.
>  > Please stay tuned.
>  >
>  > Thanks, Henry
>  >
>  > I've stopped 2,514 spam messages. You can too!
>  > Get your free, safe spam protection at
>  > http://www.cloudmark.com/spamnetsig/
>  >
>  > > -----Original Message-----
>  > > From: Edler Franz [mailto:franz.edler@uta.at]
>  > > Sent: Friday, February 28, 2003 1:55 AM
>  > > To: 'Eric Tremblay'; Henry Sinnreich; Jörgen Björkner;
>  > > sipforum-discussion@lists.su.se
>  > > Cc: sipping@ietf.org
>  > > Subject: AW: [Sipforum-discussion] SIP Telephony Device
>  > > Requirements, Conf iguration and Data
>  > >
>  > >
>  > > Hi folks,
>  > >
>  > > just a comment on SIP-25:
>  > >
>  > > I am currently working on a PSTN - SIP migration concept
>  > > avoiding to re-invent all fancy features of the PSTN and in
>  > > particular to re-implement all legal/regulatory requirements
>  > > (emergency call handling, legal intercept). The concept
>  > > builds upon a "dual homed" SIP-UA with one "line" connected
>  > > to the PSTN via V5 - SIP gateway and the other "lines" beeing
>  > > free for all new services of the SIP world. Therefore the
>  > > requirement of multiple identities on the SIP side and a
>  > > static identitiy on the PSTN side is essential, but I agree,
>  > > if you are focused on analog adapters only, this would mean
>  > > an unnecessary burden. But I suggest to re-think the
>  > > migration perspective.
>  > >
>  > > By the way, if anyone is interested in this "dual-homed" PSTN
>  > > - SIP migration concept let me know. I am convienced that
>  > > this means a good chance for a carrier to migrate towards SIP
>  > > without heavy investments in re-inventing what is already existing.
>  > >
>  > > kind regards
>  > > Franz
>  > >
>  > > ---------------------------------------------------------------
>  > > Franz Edler
>  > > Strategy & Business Development
>  > >
>  > > UTA Telekom AG
>  > > Donau-City-Strasse 11
>  > > A-1220 Wien
>  > > T: + 43/1/9009-3310
>  > > F: + 43/1/9009-93310
>  > > M: + 43/699/1388 3310
>  > > mailto:franz.edler@uta.at
>  > > http://www.uta.at
>  > > --------------------------------------------------------------
>  > >
>  > > > -----Ursprüngliche Nachricht-----
>  > > > Von:        Eric Tremblay [SMTP:etremblay@mediatrix.com]
>  > > > Gesendet am:        Mittwoch, 26. Februar 2003 17:41
>  > > > An: Henry Sinnreich; Jörgen Björkner;
>  > > sipforum-discussion@lists.su.se
>  > > > Cc: sipping@ietf.org
>  > > > Betreff:    RE: [Sipforum-discussion] SIP Telephony Device
>  > > Requirements,
>  > > > Configuration and Data
>  > > >
>  > > > Hi Henry,
>  > > >
>  > > > Here is a somewhat lengthy email with a few comments about the SIP
>  > > > Telephony Device Requirements draft:
>  > > >
>  > > >
>  > > >   SIP-25, Dynamic login/logout for user mobility: SIP devices MUST
>  > > >   support user mobility.  SIP clients MUST store a static
>  > > profile in
>  > > >   non-volatile memory so that this information is available
>  > > during the
>  > > >   power up sequence.  SIP clients MUST allow a user to walk up to a
>  > > >   client, login, and be able to send and receive calls with
>  > > his profile
>  > > >   information.
>  > > >   For emergency numbers (e.g. 911) the client MUST send the
>  > > credentials
>  > > >   (username/password) of the static profile.
>  > > >
>  > > > [EricT]
>  > > > We are developing analog adapters and don't remember
>  > > receiving such a
>  > > > request. I suggest either changing the MUST to SHOULD or
>  > > adding some text
>  > > > to specify that it is a MUST for devices with the proper
>  > > interface to do
>  > > > it and a SHOULD for devices with a limited interface. I
>  > > know we could
>  > > > possibly configure this through a web interface, but the
>  > > point is that
>  > > > there are a lot of vendore that currently just want to
>  > > replace the wire,
>  > > > not the phone and its interface...
>  > > >
>  > > >
>  > > >
>  > > >
>  > >
>
> *********************************************************
> Disclaimer
>
> This message (including any attachments) contains
> confidential information intended for a specific
> individual and purpose, and is protected by law.
> If you are not the intended recipient, you should
> delete this message and are hereby notified that
> any disclosure, copying, or distribution of this
> message, or the taking of any action based on it,
> is strictly prohibited.
>
> *********************************************************
> Visit us at http://www.mahindrabt.com
>
> _________________________________________________________________
> Cricket World Cup 2003- News, Views and Match Reports.
> http://server1.msn.co.in/msnspecials/worldcup03/

*********************************************************
Disclaimer

This message (including any attachments) contains 
confidential information intended for a specific 
individual and purpose, and is protected by law. 
If you are not the intended recipient, you should 
delete this message and are hereby notified that 
any disclosure, copying, or distribution of this
message, or the taking of any action based on it, 
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 06:47:14 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05487
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 06:47:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26BwEN28091
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 06:58:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26BwEO28088
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 06:58:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05470
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 06:46:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26BvSO27978;
	Thu, 6 Mar 2003 06:57:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26BeRO26644
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 06:40:27 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03400;
	Thu, 6 Mar 2003 06:28:57 -0500 (EST)
Message-Id: <200303061128.GAA03400@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 06 Mar 2003 06:28:57 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-dialog-package-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: An INVITE Inititiated Dialog Event Package for the 
                          Session Initiation Protocol (SIP
	Author(s)	: J. Rosenberg, H. Schulzrinne
	Filename	: draft-ietf-sipping-dialog-package-01.txt
	Pages		: 25
	Date		: 2003-3-5
	
This document defines a dialog event package for the SIP Events
architecture, along with a data format used in notifications for this
package. The dialog package allows users to subscribe to another
user, an receive notifications about the changes in state of INVITE
initiated dialogs that the user is involved in.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-dialog-package-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sipping-dialog-package-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-sipping-dialog-package-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:	<2003-3-5141219.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-dialog-package-01.txt

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

Content-Type: text/plain
Content-ID:	<2003-3-5141219.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 06:49:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05632
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 06:49:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26C0V028364
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 07:00:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26C0VO28361
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 07:00:31 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05602
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 06:49:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26BxnO28144;
	Thu, 6 Mar 2003 06:59:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26BeXO26651
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 06:40:33 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03422;
	Thu, 6 Mar 2003 06:29:03 -0500 (EST)
Message-Id: <200303061129.GAA03422@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 06 Mar 2003 06:29:03 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-realtimefax-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: SIP Support for Real-time Fax: Call Flow Examples And 
                          Best Current Practices
	Author(s)	: J. Mule, J. Li
	Filename	: draft-ietf-sipping-realtimefax-01.txt
	Pages		: 56
	Date		: 2003-3-5
	
The Session Initiation Protocol (SIP) allows the establishment of 
real-time Internet fax communications.  Real-time facsimile 
communications over IP may follow 2 modes of operation: T.38 fax 
relay as defined by the ITU-T T.38 recommendation or fax pass-
through.  
This document clarifies the options available to Internet telephony 
gateway vendors to handle real-time fax calls using SIP.  While our 
primary focus is to address the more reliable real-time T.38 Group 3 
fax mode, we briefly cover the fax pass-through mode to enable 
fallback operations and super G3 fax communications using SIP.  We 
also give examples of SIP call flows for real-time Internet fax 
gateways or SIP proxy redirect servers.  Elements in these call 
flows include SIP User Agents, SIP Proxy Servers, and Gateways to 
the PSTN (Public Switch Telephone Network). 
This document introduces best current practices for SIP T.38 fax and 
SIP fax pass-through sessions.  A session starts with audio 
capabilities, and, upon fax tone detection, T.38 fax capabilities 
are negotiated; upon successful negotiation, the session continues 
with fax capabilities and the media termination hosts exchange T.38 
Internet fax packets.  The T.38 fax call scenarios include various 
aspects of the call sequence: the detection of fax transmission, the 
usage of the T.38 session description attributes, the optional 
fallback into fax pass-through mode and the session termination. The 
fax pass-through call scenarios involve some specific SDP media 
attributes to enable proper fax transmission. 
Fax transmission can be detected by the receiving side, the emitting 
side or both (in the latter case, a 'glare' effect may appear).  
This document only covers the case when the fax transmission is 
detected by the receiving side: it is the most common practice and 
the other cases do not represent any particular challenges and are 
therefore left for future discussions).  Call flow diagrams and 
message details are shown.  A list of IANA defined SDP attribute 
names for T.38 is summarized in section 7.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-realtimefax-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sipping-realtimefax-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-sipping-realtimefax-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:	<2003-3-5141228.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-realtimefax-01.txt

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

Content-Type: text/plain
Content-ID:	<2003-3-5141228.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 06:58:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06567
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 06:58:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26C9fC30027
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 07:09:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26C9fO30024
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 07:09:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06504
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 06:58:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26C8vO29925;
	Thu, 6 Mar 2003 07:08:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26C6pO29045
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 07:06:51 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06274
	for <sipping@ietf.org>; Thu, 6 Mar 2003 06:55:19 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h26BvJwv011017;
	Thu, 6 Mar 2003 12:57:19 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5XH7VHZ; Thu, 6 Mar 2003 12:57:08 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h26Bv6lW028529;
	Thu, 6 Mar 2003 13:57:06 +0200 (EET)
Message-ID: <3E673791.B759475A@lmf.ericsson.se>
Date: Thu, 06 Mar 2003 13:57:05 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] New I-D on URI leasing
References: <3E49E4B5.8010608@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Jonathan,

I would add to Section 3 that the application server interaction work
(and thus, the early media work) also uses GRUUs. It would be part of
the already existing Section 3.2 (conferencing), but it is worthwhile
mentioning it anyway.

Gonzalo


Jonathan Rosenberg wrote:
> 
> Folks,
> 
> I've just submitted an I-D on the concept of "URI leasing". THis is my
> proposed technique for solving the "globally routable UA URI" problem.
> SPecifically, for cases like REFER, how do we construct a URI that
> routes to a specific UA instance in a domain? At the last ietf meeting,
> this issue came up in several contexts. I suggested a single document to
> explore the problem. The chairs asked for volunteers, and I said I'd
> write one, time permitting, if no one else stepped up. Since no one did,
> well, here it is.
> 
> Until it appears in the archives, you can pick it up at:
> http://www.jdrosen.net/papers/draft-rosenberg-sipping-lease-00.txt
> http://www.jdrosen.net/papers/draft-rosenberg-sipping-lease-00.html
> 
> Thanks,
> Jonathan R.
> --
> Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
> Chief Scientist                             First Floor
> dynamicsoft                                 East Hanover, NJ 07936
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 08:48:06 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14293
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 08:48:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26Dx8l05389
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 08:59:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26Dx8O05386
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 08:59:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14191
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 08:47:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26DwEO05327;
	Thu, 6 Mar 2003 08:58:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26DtXO05221
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 08:55:33 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14027
	for <sipping@ietf.org>; Thu, 6 Mar 2003 08:43:57 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h26Dk1wv010880;
	Thu, 6 Mar 2003 14:46:01 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5XH8SST; Thu, 6 Mar 2003 14:46:01 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h26Dk1lW005525;
	Thu, 6 Mar 2003 15:46:01 +0200 (EET)
Message-ID: <3E675117.F3C01A0A@lmf.ericsson.se>
Date: Thu, 06 Mar 2003 15:45:59 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Peterson, Jon" <jon.peterson@neustar.biz>
CC: Mark Watson <mwatson@nortelnetworks.com>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>
Subject: Re: [Sipping] New version of the early media draft
References: <15A2739B7DAA624D8091C65981D7DA8101214EC3@stntexch2.va.neustar.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

well, I can see which scenario he is after, but I agree that the
solution would not bring much value.

The scenario he is after is as follows; a gateway *knows* that the user
is being alerted and also *knows* that it will be sending in-band
ringing.

He is proposing a flag (i.e., null Altert-Info) for resolving that
situation.

We have two situations:
1) media packets arrive to the UAC before the 180.

2) the 180 arrives before the first media packets.

Situation 1) is not a problem, since the UAC will (most likely) not play
local ringback, since it is already receiving (and playing) media.

A null Alert Info would be helpful in Situation 2), but only to avoid
that the UAC plays local ringback during the instants (it is a race
condition) between the arrival of the 180 until the arrival of the first
media packets. A simpler solution would be to always wait for, say, a
second, before generating local ringback after reception of a 180 (if
during that second media is not received).

In fact, this is what my mobile (GSM) does today. I dial a number, and
when the terminal knows that the other user is being paged, it emits a
beep (it also displays a message on the screen). Ringback (in this case
remote ringback, but it really does not matter) starts a second or so
later. Millions of users (me included) find this behaviour acceptable,
so it would be acceptable as well for SIP-based systems.

If the only useful scenario for a null Alert-Info is a race condition of
this type, I agree that we should not adopt it.

Gonzalo



"Peterson, Jon" wrote:
> 
> I don't think that the Alert-Info header proposal will really assuage the
> stated problem. Mr. Marshall raised a 'null' Alert-Info proposal in the
> previous discussion, and it was rejected then, as it should be now. Here's
> the thread:
> 
> http://www1.ietf.org/mail-archive/working-groups/sipping/current/msg02545.ht
> ml
> 
> Null Alert-Info wouldn't express anything more than just sending a 183 does
> - a UAS should send a 183 when it knows it has some non-ringing in-band
> media. Null Alert-Info certainly wouldn't give you any additional leverage
> in cases where media arrives before signaling. I'm not sure what new
> properties it would grant. The text already suggests a policy of:
> 
>         1.   Unless a 180 (Ringing) response is received, never generate
>              local ringback.
> 
> ... which essentially entails 'don't play local ringback if 183 is
> received'. I'm not sure how it would be any better to recommend a similar
> (and redundant) policy relating to Alert-Info.
> 
> As an aside, I do agree with Mr. Audet that we should discourage mixing
> local ringback tones with received media.
> 
> Jon Peterson
> NeuStar, Inc.
> 
> > -----Original Message-----
> > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > Sent: Wednesday, March 05, 2003 10:22 AM
> > To: Mark Watson
> > Cc: 'Ejzak, Richard P (Richard)'; sipping
> > Subject: Re: [Sipping] New version of the early media draft
> >
> >
> > Mark,
> >
> > many of your points have been discussed either in the draft or in the
> > mailing list before. The MGC-MG decomposition problem is discussed in
> > the draft, and the indication of the presence in-band media was
> > discussed in the previous version of the draft.
> >
> > My initial proposal was to include an SDP parameter that provided
> > information about the intention of the sender. That is, the sender
> > intended to send early media... that was seen as too complex (and I
> > agree with that, by the way).
> >
> > But using some type of *simpler* mechanism that only
> > indicates that the
> > UAS does not want the UAC to generate local ringback (like
> > the mechanism
> > proposed in this thread), would be sensible, IMO.
> >
> > How do people feel about using the header field below in a
> > 18x response
> > to indicate that the UAS would like the UAC not to provide local
> > ringback (as proposed previously in this thread)?
> >
> > Alert-Info: <data:,>
> >
> > To me, once we have defined Alert-Info, this is not an unreasonable
> > thing to do with this header. Opinions?
> >
> > Gonzalo
> >
> >
> > Mark Watson wrote:
> > >
> > > Gonzalo,
> > >
> > > I would support this addition (or something like it - I
> > confess to not
> > > having followed all the details of this thread).
> > >
> > > This same problem has come up again and again over the last
> > two years.
> > > The root issue is a distinction between explicit application layer
> > > indications and implicit media layer indications. If the UAC is a
> > > distributed system (e.g. Media Gateway and Media Gateway
> > Controller),
> > > then the general model is that the MG is controlled by the MGC. The
> > > MGC has only explicit app. layer indications to work from -
> > it cannot
> > > take actions on the basis of receipt of not of media packets because
> > > it does not see them.
> > >
> > > Sure, the MG can report and 'RTP received' event and the
> > MGC can then
> > > instruct it appropriately, but this takes time & I don't think it's
> > > standardised.
> > >
> > > So, there should be enough information *in the SIP
> > signalling* for the
> > > UAC to take an intelligent decision on whether to play
> > media or local
> > > ringing. I don't want to prescribe how it takes this
> > decision, but at
> > > present there is information available to the UAS at the SIP layer
> > > which is not communicated to the UAC (at the SIP layer) - namely the
> > > availability of in-band media. This can only result in the
> > UAC taking
> > > inappropriate decisions in some scenarios.
> > >
> > > Perhaps we should not be telling the UAC to 'play local ringing' or
> > > 'don't play local ringing', but if the UAS knows there is in-band
> > > information, it should tell the UAC in SIP.
> > >
> > > Regards...Mark
> > >
> > > > -----Original Message-----
> > > > From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com]
> > > > Sent: 04 March 2003 19:15
> > > > To: 'Gonzalo Camarillo'
> > > > Cc: sipping
> > > > Subject: RE: [Sipping] New version of the early media draft
> > > >
> > > >
> > > > Gonzalo,
> > > > Thanks for your response.  I understand and agree with your
> > > > concerns about race conditions as well as the discussion of
> > > > how to handle them.  But I do not want the UAS to blindly
> > > > control when the UAC should apply local ringing.  I want the
> > > > UAS to be able to indicate when the UAC should NOT apply
> > > > local ringing.  There is a very important distinction here.
> > > > According to your draft, when a UAC receives a 180 it should
> > > > be prepared to generate local ringing, and it is a matter of
> > > > local policy what the UAC should do when there is concurrent
> > > > in-band media.  Gateway resources should be allocated to
> > > > detect in-band media and decide whether or not to generate
> > > > ringing.  But under some circumstances the UAS knows that
> > > > call progress information is available in-band and the UAC
> > > > does not need to bother to allocate extra resources to
> > > > monitor the media flow and optionally inject ringing.  I
> > > > believe it is important for a UAS to be able to indicate this
> > > > situation to a UAC.  These are processing !
> > > > resources that could be put to use elsewhere.  There are no
> > > > race conditions in this situation - only the recognition that
> > > > local ringing and packet detection are unnecessary.
> > > >
> > > > I stand by my original suggestion and continue to request a
> > > > modest addition to your draft based on this general approach
> > > > (my previous email indicates one possible detailed solution).
> > > >  Please let me know if you see any further issues.
> > > >
> > > > Regards,
> > > > Richard Ejzak
> > > > Lucent Technologies
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > > Sent: Tuesday, March 04, 2003 5:42 AM
> > > > To: Ejzak, Richard P (Richard)
> > > > Cc: sipping
> > > > Subject: Re: [Sipping] New version of the early media draft
> > > >
> > > >
> > > > Ejzak,
> > > >
> > > > the main problem with any SIP-layer mechanism that allows
> > the UAS to
> > >
> > > > tell the UAC whether local ringback has to be generated or not is
> > > race
> > > > conditions. It really does not matter whether you use an
> > Alert-Info
> > > > header field in a reponse, or a special status code, or a
> > > > special body,
> > > > or whatever to signal it. You always have race conditions.
> > > >
> > > > Let's say that the UAS tells the UAC to generate local
> > > > ringback. After a
> > > > while, the callee picks up. The UAS sends back a 200 OK and starts
> > > > sending media. The 200 OK, for some reason, arrives much
> > > > later than the
> > > > first media packets... what is the UAC supposed to do in the
> > > > mean time?
> > > > Ignore the media? Play the media anyway?
> > > >
> > > > Another scenario. The UAC starts receiving media before a
> > > provisional
> > > > response is received... what does it have to do?
> > > >
> > > > The main point is that, since signalling and media are loosely
> > > > synchronized, you will always have race conditions and you
> > > > will have to
> > > > make guesses about what to do during those race conditions anyway.
> > > >
> > > > Thanks,
> > > >
> > > > Gonzalo
> > > >
> > > >
> > > >
> > > > "Ejzak, Richard P (Richard)" wrote:
> > > > >
> > > > > Gonzalo,
> > > > > It seems the single greatest difficulty with the gateway
> > > > model (as you point out in your draft) is the difficulty of
> > > > depending on the arrival of media packets to determine
> > > > whether or not to generate local ringing.  I have previously
> > > > (last summer) suggested a solution to this (use 180
> > > > exclusively to indicate that local ringing should override
> > > > any inband media and 183 otherwise) that is unacceptable
> > > > since it does not satisfy the requirement that 180 be used to
> > > > indicate alerting of the called party.
> > > > >
> > > > > Have you considered using the Alert-Info header in the
> > > > following way? Since the real problem is that we would like
> > > > to be able to discriminate between cases when 180 should
> > > > cause local ringing and when 180 should not (since inband
> > > > media is available), and it is the UAS that knows
> > > > conclusively which case applies, let's agree on an encoding
> > > > of the Alert-Info header that indicates that local ringing
> > > > should not be applied.  The following line is a syntactically
> > > > valid header:
> > > > >
> > > > > Alert-Info: <data:,>
> > > > >
> > > > > This header identifies the Alert-Info as the null string,
> > > > which seems unambiguously and efficiently interpretable
> > > > within a 180 response as "do not play local ringing even
> > > > though the called party is being alerted."  If the UAC does
> > > > not recognize it or chooses not to interpret it for security
> > > > reasons, it can be safely ignored.
> > > > >
> > > > > This modest addition to your draft (or an equivalent
> > > > mechanism) would make it unnecessary for the gateway model to
> > > > depend on local policy or incoming media packet detection and
> > > > is completely consistent with all of the constraints you have
> > > > documented.
> > > > >
> > > > > Another approach may be to actually specify the rtp stream
> > > > as the source of the alert info (although this would require
> > > > the definition of a new URI scheme type).  It might look like:
> > > > >
> > > > > Alert-Info: <rtp:/12.34.56.78:90>
> > > > >
> > > > > where the Alert-Info specifies the address and port of the
> > > > rtp stream.  I don't like this mechanism since it is
> > > > redundant with SDP and prone to error.  It is also ambiguous
> > > > in the event of any subsequent media change using UPDATE (Do
> > > > I begin to generate local ringing if the rtp stream source
> > > > address changes?  Or do I continue to listen to the address
> > > > specified in the Alert-Info and ignore any UPDATEs?  No to both.)
> > > > >
> > > > > May I suggest including such a mechanism (preferably the
> > > > first one) in your draft.
> > > > >
> > > > > Richard Ejzak
> > > > > Lucent Technologies
> > > > >
> > > > > -----Original Message-----
> > > > > From: Gonzalo Camarillo
> > [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > >
> > > > > Sent: Monday, February 10, 2003 5:41 AM
> > > > > To: sipping
> > > > > Subject: [Sipping] New version of the early media draft
> > > > >
> > > > > Folks,
> > > > >
> > > > > I have just sumitted a new version of the early media
> > > > draft. Until it
> > > > > appears in the archives, you can fetch it from:
> > > > >
> > > > >
> > >
> > http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s
> > ipping-early-media-01.txt
> > >
> > > >
> > > > I have included all the (long and useful) discussions we
> > had in the
> > > > mailing list. Therefore, the draft now keeps separate the
> > "gateway"
> > > and
> > > > the "application server" models. I have also removed the parts we
> > > did
> > > > not agree on.
> > > >
> > > > Feedback is, as usual, appreciated.
> > > >
> > > > Thanks,
> > > >
> > > > Gonzalo
> > > > _______________________________________________
> > > > Sipping mailing list
> > https://www1.ietf.org/mailman/listinfo/sipping
> > >
> > > > This list is for NEW development of the application of SIP
> > > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > > Use sip@ietf.org for new developments of core SIP
> > >
> > > --
> > > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > > Telecom R&D               Fax   :  +358  9 299 30 52
> > > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> > > Finland                   http://www.hut.fi/~gonzalo
> > > _______________________________________________
> > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sip@ietf.org for new developments of core SIP
> >
> > --
> > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > Telecom R&D               Fax   :  +358  9 299 30 52
> > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> > Finland                   http://www.hut.fi/~gonzalo
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 10:29:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20300
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 10:29:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26Fe6U14597
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 10:40:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26Fe5O14594
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 10:40:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20283
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 10:28:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26FdBO14516;
	Thu, 6 Mar 2003 10:39:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26FaYO13631
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 10:36:34 -0500
Received: from acmepacket.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20163
	for <sipping@ietf.org>; Thu, 6 Mar 2003 10:25:00 -0500 (EST)
Received: from BPenfield [127.0.0.1] by acmepacket.com
  (SMTPD32-7.07) id A8C46302B8; Thu, 06 Mar 2003 10:27:00 -0500
Message-ID: <00a601c2e3f4$c2624260$2300000a@BPenfield>
From: "Bob Penfield" <bpenfield@acmepacket.com>
To: <vkenneally@cit.ie>, <sipping@ietf.org>
References: <NIEFLFDIBJCPCKAMIGBPOEGLCFAA.vkenneally@cit.ie>
Date: Thu, 6 Mar 2003 10:26:29 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: [Sip] Question on Basic Call flows document section 3.6
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The redirect (302) response (message F2) instructs User A to send the
request to UserB@chicago.com (in the Contact header). Because the Contact in
the redirect response has just the domain "chicago.com", RFC 3263 procedures
(as referenced in section 8.1.2 of RFC 3261) are then used to find the SIP
server for the chicago.com domain, which is ss3.chicago.com (the third proxy
in the list of Actors in section 1.3).

cheers,
(-:bob

Robert F. Penfield
Chief Software Architect
Acme Packet, Inc.
130 New Boston Street
Woburn, MA 01801
bpenfield@acmepacket.com

----- Original Message -----
From: "Valerie Kenneally" <vkenneally@cit.ie>
To: <sip@ietf.org>; <sipping@ietf.org>
Cc: <alan.johnston@wcom.com>; <sdonovan@dynamicsoft.com>;
<rsparks@dynamicsoft.com>; <ccunningham@dynamicsoft.com>;
<kevin.summers@sonusnet.com>
Sent: Tuesday, March 04, 2003 10:41 AM
Subject: [Sip] Question on Basic Call flows document section 3.6


> Hi All,
>
> In document at the below link
>
>
http://www.ietf.org/internet-drafts/draft-ietf-sipping-basic-call-flows-01.t
> xt
> section 3.6 "Session via Redirect and Proxy Servers with the SDP in ACK".
>
> I am wondering if someone can explain to me how the INVITE (F4) is
directed
> from User A to Proxy 3 without any Route header being included in the
> message.
>
> I have been trying to figure this out for a while and I'd really
appreciate
> any feedback asap
>
> Thanks in advance,
> Val
>
> ------------------------
> Val Kenneally,
> Post-Graduate,
> Electronic Eng. Dept.,
> CIT,
> Rossa Ave.,
> Bishopstown,
> Cork,
> Ireland.
> ------------------------
> Tel: +353 87 2273668
> Fax: +353 21 4326625
>
>
> -------------------Legal
Disclaimer---------------------------------------
>
> The above electronic mail transmission is confidential and intended only
for the person to whom it is addressed. Its contents may be protected by
legal and/or professional privilege. Should it be received by you in error
please contact the sender at the above quoted email address. Any
unauthorised form of reproduction of this message is strictly prohibited.
The Institute does not guarantee the security of any information
electronically transmitted and is not liable if the information contained in
this communication is not a proper and complete record of the message as
transmitted by the sender nor for any delay in its receipt.
>
> --------------------------------------------------------------------------
--------------
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 16:12:12 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12692
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 16:12:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26LNNM15294
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 16:23:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26LNNO15291
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 16:23:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12683
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 16:11:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26LLtO15200;
	Thu, 6 Mar 2003 16:21:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26LAvO14500
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 16:10:57 -0500
Received: from f1ee40-19.idc1.level3.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12267
	for <sipping@ietf.org>; Thu, 6 Mar 2003 15:59:16 -0500 (EST)
Received: from idc1exc0001.corp.global.level3.com (localhost [127.0.0.1])
	by f1ee40-19.idc1.level3.com (8.8.8+Sun/8.8.8) with SMTP id VAA20701
	for <sipping@ietf.org>; Thu, 6 Mar 2003 21:01:19 GMT
Received: from idc1exc0004.corp.global.level3.com ([10.1.6.220]) by idc1exc0001.corp.global.level3.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 6 Mar 2003 14:01:18 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6334.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] I-D ACTION:draft-ietf-sipping-realtimefax-01.txt
Date: Thu, 6 Mar 2003 14:01:18 -0700
Message-ID: <3DB099919328BA41905F651A6EF83976B4DC5C@idc1exc0004.corp.global.level3.com>
Thread-Topic: [Sipping] I-D ACTION:draft-ietf-sipping-realtimefax-01.txt
Thread-Index: AcLj3GM9HQ1e06ZzQLuYh9M2BD675gAQZagw
From: "Hearty, John" <John.Hearty@Level3.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 06 Mar 2003 21:01:18.0916 (UTC) FILETIME=[88C16840:01C2E423]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h26LAvO14501
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

A comment.  Section 5.3.2 starting at F11, the original stream is being muted by sending 0.0.0.0 in the c= line.  This is a depreciated way of doing hold, see RFC3264 section 8.4.  Shouldn't the sendonly/recvonly attributes be used?  Same for section 5.4.2.

John Hearty
Level3


> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Thursday, March 06, 2003 4:29 AM
> Cc: sipping@ietf.org
> Subject: [Sipping] I-D ACTION:draft-ietf-sipping-realtimefax-01.txt
> 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Session Initiation Proposal 
> Investigation Working Group of the IETF.
> 
> 	Title		: SIP Support for Real-time Fax: Call 
> Flow Examples And 
>                           Best Current Practices
> 	Author(s)	: J. Mule, J. Li
> 	Filename	: draft-ietf-sipping-realtimefax-01.txt
> 	Pages		: 56
> 	Date		: 2003-3-5
> 	
> The Session Initiation Protocol (SIP) allows the establishment of 
> real-time Internet fax communications.  Real-time facsimile 
> communications over IP may follow 2 modes of operation: T.38 fax 
> relay as defined by the ITU-T T.38 recommendation or fax pass-
> through.  
> This document clarifies the options available to Internet telephony 
> gateway vendors to handle real-time fax calls using SIP.  While our 
> primary focus is to address the more reliable real-time T.38 Group 3 
> fax mode, we briefly cover the fax pass-through mode to enable 
> fallback operations and super G3 fax communications using SIP.  We 
> also give examples of SIP call flows for real-time Internet fax 
> gateways or SIP proxy redirect servers.  Elements in these call 
> flows include SIP User Agents, SIP Proxy Servers, and Gateways to 
> the PSTN (Public Switch Telephone Network). 
> This document introduces best current practices for SIP T.38 fax and 
> SIP fax pass-through sessions.  A session starts with audio 
> capabilities, and, upon fax tone detection, T.38 fax capabilities 
> are negotiated; upon successful negotiation, the session continues 
> with fax capabilities and the media termination hosts exchange T.38 
> Internet fax packets.  The T.38 fax call scenarios include various 
> aspects of the call sequence: the detection of fax transmission, the 
> usage of the T.38 session description attributes, the optional 
> fallback into fax pass-through mode and the session termination. The 
> fax pass-through call scenarios involve some specific SDP media 
> attributes to enable proper fax transmission. 
> Fax transmission can be detected by the receiving side, the emitting 
> side or both (in the latter case, a 'glare' effect may appear).  
> This document only covers the case when the fax transmission is 
> detected by the receiving side: it is the most common practice and 
> the other cases do not represent any particular challenges and are 
> therefore left for future discussions).  Call flow diagrams and 
> message details are shown.  A list of IANA defined SDP attribute 
> names for T.38 is summarized in section 7.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-realtim
efax-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sipping-realtimefax-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-sipping-realtimefax-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.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 16:24:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13185
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 16:24:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26LZlh15982
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 16:35:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26LZlO15979
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 16:35:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13161
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 16:24:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26LYFO15895;
	Thu, 6 Mar 2003 16:34:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26LL4O15171
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 16:21:04 -0500
Received: from dgesmtp01.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12614
	for <sipping@ietf.org>; Thu, 6 Mar 2003 16:09:23 -0500 (EST)
Received: from pmismtp01.wcomnet.com ([166.38.62.36])
 by firewall.wcom.com (Iplanet MTA)
 with ESMTP id <0HBC00EHTIRJ2T@firewall.wcom.com> for sipping@ietf.org; Thu,
 06 Mar 2003 21:09:19 +0000 (GMT)
Received: from pmismtp01.wcomnet.com by pmismtp01.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HBC00L01IRJCK@pmismtp01.wcomnet.com>; Thu,
 06 Mar 2003 21:09:19 +0000 (GMT)
Received: from ajohnston.wcom.com ([166.50.106.241])
 by pmismtp01.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HBC00KJ8IRH9B@pmismtp01.wcomnet.com>; Thu,
 06 Mar 2003 21:09:19 +0000 (GMT)
Date: Thu, 06 Mar 2003 15:08:50 -0600
From: Alan Johnston <alan.johnston@wcom.com>
Subject: RE: [Sipping] Change of IP mid session and Contact header question
X-Sender: Alan.Johnston@pop.mcit.com
To: "Drage, Keith (Keith)" <drage@lucent.com>,
        "'vkenneally@cit.ie'" <vkenneally@cit.ie>, sipping@ietf.org
Message-id: <5.1.1.6.0.20030306135339.020e2030@pop.mcit.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset=us-ascii; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Hi Val,

What Keith describes is true for 3GPP, but not generally true for SIP.

For an RFC 3261 compliant user agent, if a user agent changes its IP 
address during a session for any reason (DHCP renewal failure, VPN failure 
and re-establishment, or due to mobility) and as a result the signaling or 
media packets need to be routed to a different IP address, then re-INVITE 
is the correct mechanism.  It does have the limitation that the routeset 
(set of proxies traversed) can not be changed with a re-INVITE, only the 
Contact URI.  So if a change of IP address requires a new proxy to be 
traversed, instead of a re-INVITE, the user agent should send a new INVITE 
(creating a new dialog with a new route set) with a Replaces header 
identifying the existing session.  A new REGISTER is required in order to 
receive new incoming calls, but has little to do with the current dialog.

This scenario is still likely when an endpoint wishes to switch a call 
between non-cooperating networks, such as a commercial wireless IP network 
and an enterprise or home 802.11 network.

Hope this helps.

Alan Johnston
WorldCom
sip:alan@digitalari.com

At 02:23 PM 3/5/2003 +0000, Drage, Keith (Keith) wrote:
>Apart from some author drafts using SIP for mobility itself, which are not 
>being progressed by the working group, this question is outside IETF 
>itself. IETF has been working with 3GPP and 3GPP2 on how to put SIP into a 
>mobile environment.
>
>In 3GPP release 5, not only does a new IP address necessitate the use of a 
>new INVITE, it also necessitates the use of a new registration as well.
>
>Normally mobile users retain their PDP context to the GGSN when moving, 
>and therefore retain their IP address, and therefore the issue should not 
>arise. Mobility is handled below the SIP layer.
>
>3GPP2 are using mobile IP instead of GPRS, and therefore the same 
>considerations apply.
>
>Keith
>
>Keith Drage
>Lucent Technologies
>Tel: +44 1793 776249
>Email: drage@lucent.com
>
> > -----Original Message-----
> > From: Valerie Kenneally [mailto:vkenneally@cit.ie]
> > Sent: 05 March 2003 11:52
> > To: sipping@ietf.org
> > Subject: [Sipping] Change of IP mid session and Contact
> > header question
> >
> >
> > Hi All,
> >
> >       I'm just trying to understand some SIP session
> > scenarios and various
> > features.  My question is best explained by example
> >
> > If a session is established using SIP between two endpoints
> > (in a mobile
> > network) and during the session one of these endpoints moves
> > such that it is
> > assigned a new ip, is it a MUST that this endpoint send a
> > RE-INVITE with new
> > Contact information to the other communicating entity?
> >
> > Thanks in advance,
> > Val Kenneally
> >
> >
> > -------------------Legal
> > Disclaimer---------------------------------------
> >
> > The above electronic mail transmission is confidential and
> > intended only for the person to whom it is addressed. Its
> > contents may be protected by legal and/or professional
> > privilege. Should it be received by you in error please
> > contact the sender at the above quoted email address. Any
> > unauthorised form of reproduction of this message is strictly
> > prohibited. The Institute does not guarantee the security of
> > any information electronically transmitted and is not liable
> > if the information contained in this communication is not a
> > proper and complete record of the message as transmitted by
> > the sender nor for any delay in its receipt.
> >
> > --------------------------------------------------------------
> > --------------------------
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 16:27:46 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13378
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 16:27:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26Lcvq17013
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 16:38:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26LcvO17008
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 16:38:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13341
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 16:27:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26LbKO16563;
	Thu, 6 Mar 2003 16:37:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26KlkO12635
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 15:47:46 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11599
	for <sipping@ietf.org>; Thu, 6 Mar 2003 15:36:05 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] Updated Version of MSCML
Date: Thu, 6 Mar 2003 15:40:19 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D097C2D@zoe.office.snowshore.com>
Thread-Topic: [Sipping] Updated Version of MSCML
Thread-Index: AcLNUQrjfXV8+zkCTqa0CaF/JZbEHgWzGZsA
From: "Eric Burger" <eburger@snowshore.com>
To: "Garland Sharratt" <gsharratt@convedia.com>
Cc: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h26KlkO12636
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Your eyes are better than mine.  The IPR notice is supposed to be on -01, too.  That might be a newbie xml-rfc goof.

That said, did you read the IPR disclosure?  If you had, you would have seen very liberal licensing terms.

We have received a lot of feedback and interest in MSCML.  This feedback has been both in public on the list and in private, from service providers, vendors, partners, and competitors.  Given our desire to promote standards in this area, we have revised our IPR licensing terms.

Our attorneys are currently doing a review of all of the IETF IPR disclosures.  The review is not complete yet, but it looks like SnowShore's revised disclosure statement is the ONLY royalty free license that does not ask other people to give away their *entire* portfolio.

The updated disclosure has been given to the Secretariat and should be posted shortly.  Until then, you can find it at 
<http://flyingfox.snowshore.com/i-d/IETF%20IPR%20draft-vandyke-mscml.txt>

> -----Original Message-----
> From: Garland Sharratt [mailto:gsharratt@convedia.com]
> Sent: Wednesday, February 05, 2003 2:59 PM
> To: Eric Burger
> Cc: Sipping@Ietf. Org
> Subject: RE: [Sipping] Updated Version of MSCML
> 
> 
> Eric:
> 
> I took a look at draft-vandyke-mscml-01 and saw no 
> substantive changes.
> 
> MSCML isn't perfect but my only real concern with it (both 01 
> and 00) is
> the fact that SnowShore has claimed IPR on it.  This doesn't 
> work for an
> interface that is supposed to be -- and otherwise likely would be --
> adopted by all call agent and media server vendors who need 
> its type of
> media server control.
> 
> I did notice that the following paragraph in 00 --
> 
>    "The IETF has been notified of intellectual property rights claimed
> in regard to some or all of the specification contained in this
> document.  For more information consult the online list of claimed
> rights."
> 
> -- has been removed in 01.  But the SnowShore notice on the 
> IETF Page of
> Intellectual Property Rights Notices is still present 
> ("SnowShore Patent
> Statement pertaining to draft-vandyke-mscml").
> 
> Is there any chance of getting MSCML released into the public 
> domain so
> that it can be widely and safely adopted by everyone?
> 
> Thanks,
> 
> Garland
> 
> 
> -----Original Message-----
> From: sipping-admin@ietf.org 
> [mailto:sipping-admin@ietf.org]On Behalf Of
> Eric Burger
> Sent: Monday, February 03, 2003 11:54
> To: Sipping (E-mail)
> Subject: [Sipping] Updated Version of MSCML
> 
> 
> Until it hits the archive:
> 
> http://flyingfox.snowshore.com/i-d/sip/draft-vandyke-mscml-01.html
> http://flyingfox.snowshore.com/i-d/sip/draft-vandyke-mscml-01.txt
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 16:35:27 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13797
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 16:35:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26Lkct17805
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 16:46:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26LkcO17802
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 16:46:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13756
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 16:34:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26LjFO17555;
	Thu, 6 Mar 2003 16:45:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26KMaO10444
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 15:22:36 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10549
	for <sipping@ietf.org>; Thu, 6 Mar 2003 15:10:54 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] New version of netann
Date: Thu, 6 Mar 2003 15:15:09 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D2DF82F@zoe.office.snowshore.com>
Thread-Topic: [Sipping] New version of netann
Thread-Index: AcLjXekAxxal0jCFT3aLdxyOdL6P7QAvrERg
From: "Eric Burger" <eburger@snowshore.com>
To: "Christer Holmberg" <christer.holmberg@lmf.ericsson.se>
Cc: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h26KMaO10445
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Inline

> Original Message From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > As it stands now, you would need multiple INVITEs.
> >
> > Otherwise, how would one correlate the play's with m-lines?
> 
> Well, you could define the play's as SDP attributes. Something like:
> 
> m=audio...
> a=play:"http://audio.example.net/allcircuitsbusy.g711";
> m=video...
> a=play:"http://video.example.net/allcircuitsbusy.mpeg4";
> 
> I don't know if this would work (I haven't had time to think so much
> about it) the way you've planned, though.

It might work, except error handling would be horrific.  A fetch error would have to be reported as an SDP error, for example.

> But, if we need multiple INVITEs, would it be possible to associate
> them? We would have to use different call identifiers etc (I hope you
> wouldn't want to use something similar to overlapping for this :)

Is this a real issue?


> Another question I have, is related to the media mode attributes.
> 
> Assume I send a re-INVITE during the session, to put the media
> "on-hold". Now, does this mean that the stream will be 
> "paused", or does
> it mean that I just won't receive it? Personally I would say that the
> second alternative is more according to the semantics, but in a
> streaming environment some may disagree...

I hadn't thought about it before, as we've never seen it happen.  I suppose it could happen, however.  I'm hesitant to standardize the behavior.  If we say "hold=pause session", then we're opening ourselves up to a major denial-of-service attack.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 17:08:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15332
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 17:08:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26MJEa21236
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 17:19:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26MJEO21233
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 17:19:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15306
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 17:07:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26MHBO21091;
	Thu, 6 Mar 2003 17:17:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26MG1O21021
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 17:16:01 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15220
	for <sipping@ietf.org>; Thu, 6 Mar 2003 17:04:18 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h26M6EC26063;
	Thu, 6 Mar 2003 22:06:14 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JR9BD>; Thu, 6 Mar 2003 17:06:21 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214EC8@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: Mark Watson <mwatson@nortelnetworks.com>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping
	 <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Thu, 6 Mar 2003 17:06:19 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Well,

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
[snip]
> 
> The scenario he is after is as follows; a gateway *knows* that the user
> is being alerted and also *knows* that it will be sending in-band
> ringing.
> 

If the gateway knows that it will be sending in-band ringing, my position is
that the gateway shouldn't be sending that media. It's just ring tone. The
UAC can generate that itself. Let's not waste the bandwidth sending ringing,
especially in forking cases, especially because the UAC might not even
render this provisional media (if it's a PC UAC, for example).

If media arrives at the UAC, it should override local ringtone, agreed. And
I have no problem with the idea that a UAC would delay local ringtone for a
short interval in order to see if any media is coming, even when 180 is
received. But we should not encourage gateways to send ringing media.

Jon Peterson
NeuStar, Inc. 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 17:40:23 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16169
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 17:40:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26MpaC23499
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 17:51:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26MpaO23496
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 17:51:36 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16158
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 17:39:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26MoRO23443;
	Thu, 6 Mar 2003 17:50:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26MnFO23381
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 17:49:15 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16132
	for <sipping@ietf.org>; Thu, 6 Mar 2003 17:37:31 -0500 (EST)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by auemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h26MdY319040
	for <sipping@ietf.org>; Thu, 6 Mar 2003 17:39:34 -0500 (EST)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2653.19)
	id <1H3RNDST>; Thu, 6 Mar 2003 16:39:33 -0600
Message-ID: <DBC3D7D0A071F743AE0767C9C6071EDA0482BBC6@il0015exch010u.ih.lucent.com>
From: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: Mark Watson <mwatson@nortelnetworks.com>, sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Thu, 6 Mar 2003 16:39:33 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Jon,
I must disagree with your blanket recommendation that the gateway not sent in-band ringing media.  This may be possible in some cases - and nothing we have suggested would prevent a gateway from using out-of-band indications.  But ringing is not the only in-band call progress information you may receive while trying to establish a call from SIP to ISUP.  The transition from alerting to other forms of in-band call progress information is not guaranteed to be clearly signaled by ISUP within an ACM or CPG (since every switch in the network can safely assume in-band call progress after a certain point in the call), and it is essential that this subsequent information (when it exists) be presented to the UAC/user.  And the notion of having the gateway intelligently filter what it thinks is ringing and detect a transition to other forms of call progress is not acceptable.

Regards,
Richard Ejzak
Lucent Technologies



-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: Thursday, March 06, 2003 4:06 PM
To: 'Gonzalo Camarillo'
Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping
Subject: RE: [Sipping] New version of the early media draft



Well,

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
[snip]
> 
> The scenario he is after is as follows; a gateway *knows* that the user
> is being alerted and also *knows* that it will be sending in-band
> ringing.
> 

If the gateway knows that it will be sending in-band ringing, my position is
that the gateway shouldn't be sending that media. It's just ring tone. The
UAC can generate that itself. Let's not waste the bandwidth sending ringing,
especially in forking cases, especially because the UAC might not even
render this provisional media (if it's a PC UAC, for example).

If media arrives at the UAC, it should override local ringtone, agreed. And
I have no problem with the idea that a UAC would delay local ringtone for a
short interval in order to see if any media is coming, even when 180 is
received. But we should not encourage gateways to send ringing media.

Jon Peterson
NeuStar, Inc. 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar  6 19:12:01 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20406
	for <sipping-archive@odin.ietf.org>; Thu, 6 Mar 2003 19:12:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h270NFj31100
	for sipping-archive@odin.ietf.org; Thu, 6 Mar 2003 19:23:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h270NFO31097
	for <sipping-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 19:23:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20393
	for <sipping-web-archive@ietf.org>; Thu, 6 Mar 2003 19:11:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h270LeO30979;
	Thu, 6 Mar 2003 19:21:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h270JSO30834
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 19:19:28 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20301
	for <sipping@ietf.org>; Thu, 6 Mar 2003 19:07:42 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2709JC27914;
	Fri, 7 Mar 2003 00:09:19 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JR976>; Thu, 6 Mar 2003 19:09:25 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214ECA@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "Peterson, Jon"
	 <jon.peterson@neustar.biz>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: Mark Watson <mwatson@nortelnetworks.com>, sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Thu, 6 Mar 2003 19:09:24 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Everything below is familiar ground, and I don't want to start rehearsing
these same arguments again. SIP has made a number of design decisions that
predispose it towards out-of-band status information. Sending in-band status
information in SIP is harmful - period. In-band media should be sent only
when the gateway does not know the status of the call, and thus cannot
communicate it out-of-band. Below, you basically argue that in cases where
the gateway does not know the status of the call, it has to send early
media. I agree. I said that in cases in which the gateway knows that the
early media is just ringtone, it should send 180. Clearly, if there's some
in-band transition in call state from ringtone to some other audible call
progress information, and the gateway isn't made aware of it, then the
gateway doesn't know the state of the call. Perhaps we might draw the
conclusion from your example that out-of-band call status indicators are
inherently unreliable, then - and surmise that it is impossible for the
gateway to know the state of the call. Or perhaps the likelihood of this
condition arising is sufficiently remote, the consequences of sending early
media sufficiently troublesome, that we might decide the in-band information
in these cases is not 'essential' enough to worry over. But I firmly believe
we should leave this to the conscience of the individual gateway
implementer. I don't think the early media draft needs to draw that
conclusion.

Mr. Camarillo's draft already maintains a very delicate balance of behavior
to accommodate SIP's needs, and I haven't heard anything in this yet that
should alter it.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com]
> Sent: Thursday, March 06, 2003 2:40 PM
> To: 'Peterson, Jon'; 'Gonzalo Camarillo'
> Cc: Mark Watson; sipping
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> Jon,
> I must disagree with your blanket recommendation that the 
> gateway not sent in-band ringing media.  This may be possible 
> in some cases - and nothing we have suggested would prevent a 
> gateway from using out-of-band indications.  But ringing is 
> not the only in-band call progress information you may 
> receive while trying to establish a call from SIP to ISUP.  
> The transition from alerting to other forms of in-band call 
> progress information is not guaranteed to be clearly signaled 
> by ISUP within an ACM or CPG (since every switch in the 
> network can safely assume in-band call progress after a 
> certain point in the call), and it is essential that this 
> subsequent information (when it exists) be presented to the 
> UAC/user.  And the notion of having the gateway intelligently 
> filter what it thinks is ringing and detect a transition to 
> other forms of call progress is not acceptable.
> 
> Regards,
> Richard Ejzak
> Lucent Technologies
> 
> 
> 
> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> Sent: Thursday, March 06, 2003 4:06 PM
> To: 'Gonzalo Camarillo'
> Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> 
> Well,
> 
> > -----Original Message-----
> > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> [snip]
> > 
> > The scenario he is after is as follows; a gateway *knows* 
> that the user
> > is being alerted and also *knows* that it will be sending in-band
> > ringing.
> > 
> 
> If the gateway knows that it will be sending in-band ringing, 
> my position is
> that the gateway shouldn't be sending that media. It's just 
> ring tone. The
> UAC can generate that itself. Let's not waste the bandwidth 
> sending ringing,
> especially in forking cases, especially because the UAC might not even
> render this provisional media (if it's a PC UAC, for example).
> 
> If media arrives at the UAC, it should override local 
> ringtone, agreed. And
> I have no problem with the idea that a UAC would delay local 
> ringtone for a
> short interval in order to see if any media is coming, even 
> when 180 is
> received. But we should not encourage gateways to send ringing media.
> 
> Jon Peterson
> NeuStar, Inc. 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 01:06:39 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00907
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 01:06:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h276I1307930
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 01:18:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h276I1O07927
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 01:18:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00885
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 01:06:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h276GbO07709;
	Fri, 7 Mar 2003 01:16:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h276EcO07601
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 01:14:38 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00803
	for <sipping@ietf.org>; Fri, 7 Mar 2003 01:02:45 -0500 (EST)
Received: from esealnt610.al.sw.ericsson.se (alteon-nat3.sw.ericsson.se [153.88.254.120])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2764mwx012916;
	Fri, 7 Mar 2003 07:04:48 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id FD4J3TXY; Fri, 7 Mar 2003 07:04:48 +0100
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.31.86])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2764llW020797;
	Fri, 7 Mar 2003 08:04:47 +0200 (EET)
Message-ID: <3E683681.4B2CD7D3@lmf.ericsson.se>
Date: Fri, 07 Mar 2003 08:04:49 +0200
X-Sybari-Trust: 936fa67c 9ffcebbb 7a95d2f4 00000138
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] New version of netann
References: <4A3384433CE2AB46A63468CB207E209D2DF82F@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi Eric,

> >>As it stands now, you would need multiple INVITEs.
> >>
> >>Otherwise, how would one correlate the play's with m-lines?
> >
> >Well, you could define the play's as SDP attributes. Something like:
> >
> >m=audio...
> >a=play:"http://audio.example.net/allcircuitsbusy.g711";
> >m=video...
> >a=play:"http://video.example.net/allcircuitsbusy.mpeg4";
> >
> >I don't know if this would work (I haven't had time to think so much
> >about it) the way you've planned, though.
>
> It might work, except error handling would be horrific.  A fetch error would have to be reported as an SDP error, for example.

Well, you could return 200 OK with an SDP, with the port set to zero for the specific stream. That's how we do it in "normal" SIP calls, so... Or, you could send 415 Unsupported Media Type.

> >But, if we need multiple INVITEs, would it be possible to associate
> >them? We would have to use different call identifiers etc (I hope you
> >wouldn't want to use something similar to overlapping for this :)
>
> Is this a real issue?

What? Being able to associate the INVITEs, or having to send multiple INVITEs? At least regarding the issue of multiple INVITEs, I think multimedia streams (including eg audio AND video) IS a real issue...

> >Another question I have, is related to the media mode attributes.
> >
> >Assume I send a re-INVITE during the session, to put the media
> >"on-hold". Now, does this mean that the stream will be
> >"paused", or does it mean that I just won't receive it? Personally I would say that the
> >second alternative is more according to the semantics, but in a
> >streaming environment some may disagree...
>
> I hadn't thought about it before, as we've never seen it happen.  I suppose it could happen, however.  I'm hesitant to standardize the behavior.  If we say "hold=pause session", then we're opening ourselves up to a major denial-of-service attack.

If it's supposed to work as it normally does, there is no need to standardize anything. But, in that case I guess it will not be able, with your current draft, to put media on hold. I guess it's not needed for announcements etc, but my understanding
is that the scope of your draft includes also real, established, streaming sessions.

Regards,

Christer Holmberg
Ericsson Finland


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 03:48:52 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14938
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 03:48:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2790IB30853
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 04:00:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2790HO30850
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 04:00:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14927
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 03:48:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h278xLO30746;
	Fri, 7 Mar 2003 03:59:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h278w2O30671
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 03:58:02 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14874
	for <sipping@ietf.org>; Fri, 7 Mar 2003 03:46:04 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h278m5B3003385;
	Fri, 7 Mar 2003 09:48:05 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5W97SHX; Fri, 7 Mar 2003 09:48:04 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h278m4lW001271;
	Fri, 7 Mar 2003 10:48:04 +0200 (EET)
Message-ID: <3E685CC3.25E602D3@lmf.ericsson.se>
Date: Fri, 07 Mar 2003 10:48:03 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Peterson, Jon" <jon.peterson@neustar.biz>
CC: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        Mark Watson <mwatson@nortelnetworks.com>, sipping <sipping@ietf.org>,
        Francois Audet <audet@nortelnetworks.com>
Subject: Re: [Sipping] New version of the early media draft
References: <15A2739B7DAA624D8091C65981D7DA8101214ECA@stntexch2.va.neustar.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

I agree with Jon that we should not encourage people to send in-band
ringing tones, but I also agree with Mark that this issue has
re-surfaced a number of times already. The message we want to get
through is that adding a SIP flag for resolving that issue offers little
or no value.

I am willing, if people agree, to add some text saying why it is not a
good idea to add a SIP-layer flag to 180 responses indicating that media
is coming.

What about a section along these lines:?

2.2.1 Problems with SIP-layer Indications in 180 Responses

As stated above, it is not an easy task for a UAC that receives a 180
(Ringing) response to decide whether it should generate local ringback
or it will be receiving early media. At first sight, it may seem that
adding a "there is media coming" indication to 180 (Ringing) responses
would facilitate the task of UACs. Upon reception of a 180 (Ringing)
response with such an indication, the UAC would not generate local
ringback. However, such an indication would offer little or no gain.

The only scenario where such an indication would be applicable is when
the UAS sends a 180 (Ringing) response and starts sending early media
right away. If the UAS intended to send early media at a later time,
instead of right away, a sensible local policy for the UAC could be to
generate local ringback in the meantime. Therefore, the "there is media
coming" indication would be useless.

Assuming, then, that the UAS sends the 180 (Ringing) response and the
first media packets in parallel towards the UAC, we have a race
condition. If the media packets arrive at the UAC before the 180
(Ringing) response, the "there is media coming" indication will not
provide any further information to the UAC.

The only situation where the UAC could benefit from that indication is
when the 180 (Ringing) response arrives before the first media packets.
The UAC could avoid generating local ringback for an instant before the
first media packets arrive. However, the same result can be achieved in
a much simpler way (without protocol extensions) by just having UACs
always delay the generation of local ringback for a short period of
time. The UAC can, for instance, generate a short beep upon reception of
the 180 (Ringing) response (this is already done by some
circuit-switched mobile terminals) and one second later start generating
local ringback if no media have been received during that period.

\motivation{Note that adding such an indication does not keep UACs from
implementing media arrival detection either, since they have to
implement it anyway to cover other scenarios, like the race condition
between the 200 OK for the INVITE and the first regular media packets).}


Opinions?

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 04:21:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15538
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 04:21:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h279XEG01259
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 04:33:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279XEO01255
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 04:33:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15497
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 04:21:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279WCO01086;
	Fri, 7 Mar 2003 04:32:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279VeO00991
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 04:31:40 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15470
	for <sipping@ietf.org>; Fri, 7 Mar 2003 04:19:43 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h279Li402415;
	Fri, 7 Mar 2003 04:21:44 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (europem01.nt.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h279LfL17474;
	Fri, 7 Mar 2003 09:21:41 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id G3M62F1G; Fri, 7 Mar 2003 09:21:42 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FS3957L8>; Fri, 7 Mar 2003 09:21:18 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C4A@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        "Peterson, Jon" <jon.peterson@neustar.biz>
Cc: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>,
        "Francois Audet" <audet@nortelnetworks.com>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 7 Mar 2003 09:21:15 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E48A.9421E7E8"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E48A.9421E7E8
Content-Type: text/plain;
	charset="iso-8859-1"

Gonzalo,

Your text does not recognise the desire to avoid reading semantics in to the
arrival of RTP packets, to cope with the MGC/MG scenario.

I still think this problem remains unsolved.

...Mark



> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: 07 March 2003 08:48
> To: Peterson, Jon
> Cc: 'Ejzak, Richard P (Richard)'; Watson, Mark 
> [MOP:EP10:EXCH]; sipping;
> Audet, Francois [SC100:4K02:EXCH]
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Folks,
> 
> I agree with Jon that we should not encourage people to send in-band
> ringing tones, but I also agree with Mark that this issue has
> re-surfaced a number of times already. The message we want to get
> through is that adding a SIP flag for resolving that issue 
> offers little
> or no value.
> 
> I am willing, if people agree, to add some text saying why it is not a
> good idea to add a SIP-layer flag to 180 responses indicating 
> that media
> is coming.
> 
> What about a section along these lines:?
> 
> 2.2.1 Problems with SIP-layer Indications in 180 Responses
> 
> As stated above, it is not an easy task for a UAC that receives a 180
> (Ringing) response to decide whether it should generate local ringback
> or it will be receiving early media. At first sight, it may seem that
> adding a "there is media coming" indication to 180 (Ringing) responses
> would facilitate the task of UACs. Upon reception of a 180 (Ringing)
> response with such an indication, the UAC would not generate local
> ringback. However, such an indication would offer little or no gain.
> 
> The only scenario where such an indication would be applicable is when
> the UAS sends a 180 (Ringing) response and starts sending early media
> right away. If the UAS intended to send early media at a later time,
> instead of right away, a sensible local policy for the UAC could be to
> generate local ringback in the meantime. Therefore, the 
> "there is media
> coming" indication would be useless.
> 
> Assuming, then, that the UAS sends the 180 (Ringing) response and the
> first media packets in parallel towards the UAC, we have a race
> condition. If the media packets arrive at the UAC before the 180
> (Ringing) response, the "there is media coming" indication will not
> provide any further information to the UAC.
> 
> The only situation where the UAC could benefit from that indication is
> when the 180 (Ringing) response arrives before the first 
> media packets.
> The UAC could avoid generating local ringback for an instant 
> before the
> first media packets arrive. However, the same result can be 
> achieved in
> a much simpler way (without protocol extensions) by just having UACs
> always delay the generation of local ringback for a short period of
> time. The UAC can, for instance, generate a short beep upon 
> reception of
> the 180 (Ringing) response (this is already done by some
> circuit-switched mobile terminals) and one second later start 
> generating
> local ringback if no media have been received during that period.
> 
> \motivation{Note that adding such an indication does not keep 
> UACs from
> implementing media arrival detection either, since they have to
> implement it anyway to cover other scenarios, like the race condition
> between the 200 OK for the INVITE and the first regular media 
> packets).}
> 
> 
> Opinions?
> 
> Gonzalo
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Gonzalo,</FONT>
</P>

<P><FONT SIZE=3D2>Your text does not recognise the desire to avoid =
reading semantics in to the arrival of RTP packets, to cope with the =
MGC/MG scenario.</FONT></P>

<P><FONT SIZE=3D2>I still think this problem remains unsolved.</FONT>
</P>

<P><FONT SIZE=3D2>...Mark</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 07 March 2003 08:48</FONT>
<BR><FONT SIZE=3D2>&gt; To: Peterson, Jon</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'Ejzak, Richard P (Richard)'; Watson, Mark =
</FONT>
<BR><FONT SIZE=3D2>&gt; [MOP:EP10:EXCH]; sipping;</FONT>
<BR><FONT SIZE=3D2>&gt; Audet, Francois [SC100:4K02:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Folks,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I agree with Jon that we should not encourage =
people to send in-band</FONT>
<BR><FONT SIZE=3D2>&gt; ringing tones, but I also agree with Mark that =
this issue has</FONT>
<BR><FONT SIZE=3D2>&gt; re-surfaced a number of times already. The =
message we want to get</FONT>
<BR><FONT SIZE=3D2>&gt; through is that adding a SIP flag for resolving =
that issue </FONT>
<BR><FONT SIZE=3D2>&gt; offers little</FONT>
<BR><FONT SIZE=3D2>&gt; or no value.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I am willing, if people agree, to add some text =
saying why it is not a</FONT>
<BR><FONT SIZE=3D2>&gt; good idea to add a SIP-layer flag to 180 =
responses indicating </FONT>
<BR><FONT SIZE=3D2>&gt; that media</FONT>
<BR><FONT SIZE=3D2>&gt; is coming.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; What about a section along these lines:?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 2.2.1 Problems with SIP-layer Indications in =
180 Responses</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; As stated above, it is not an easy task for a =
UAC that receives a 180</FONT>
<BR><FONT SIZE=3D2>&gt; (Ringing) response to decide whether it should =
generate local ringback</FONT>
<BR><FONT SIZE=3D2>&gt; or it will be receiving early media. At first =
sight, it may seem that</FONT>
<BR><FONT SIZE=3D2>&gt; adding a &quot;there is media coming&quot; =
indication to 180 (Ringing) responses</FONT>
<BR><FONT SIZE=3D2>&gt; would facilitate the task of UACs. Upon =
reception of a 180 (Ringing)</FONT>
<BR><FONT SIZE=3D2>&gt; response with such an indication, the UAC would =
not generate local</FONT>
<BR><FONT SIZE=3D2>&gt; ringback. However, such an indication would =
offer little or no gain.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The only scenario where such an indication =
would be applicable is when</FONT>
<BR><FONT SIZE=3D2>&gt; the UAS sends a 180 (Ringing) response and =
starts sending early media</FONT>
<BR><FONT SIZE=3D2>&gt; right away. If the UAS intended to send early =
media at a later time,</FONT>
<BR><FONT SIZE=3D2>&gt; instead of right away, a sensible local policy =
for the UAC could be to</FONT>
<BR><FONT SIZE=3D2>&gt; generate local ringback in the meantime. =
Therefore, the </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;there is media</FONT>
<BR><FONT SIZE=3D2>&gt; coming&quot; indication would be =
useless.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Assuming, then, that the UAS sends the 180 =
(Ringing) response and the</FONT>
<BR><FONT SIZE=3D2>&gt; first media packets in parallel towards the =
UAC, we have a race</FONT>
<BR><FONT SIZE=3D2>&gt; condition. If the media packets arrive at the =
UAC before the 180</FONT>
<BR><FONT SIZE=3D2>&gt; (Ringing) response, the &quot;there is media =
coming&quot; indication will not</FONT>
<BR><FONT SIZE=3D2>&gt; provide any further information to the =
UAC.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The only situation where the UAC could benefit =
from that indication is</FONT>
<BR><FONT SIZE=3D2>&gt; when the 180 (Ringing) response arrives before =
the first </FONT>
<BR><FONT SIZE=3D2>&gt; media packets.</FONT>
<BR><FONT SIZE=3D2>&gt; The UAC could avoid generating local ringback =
for an instant </FONT>
<BR><FONT SIZE=3D2>&gt; before the</FONT>
<BR><FONT SIZE=3D2>&gt; first media packets arrive. However, the same =
result can be </FONT>
<BR><FONT SIZE=3D2>&gt; achieved in</FONT>
<BR><FONT SIZE=3D2>&gt; a much simpler way (without protocol =
extensions) by just having UACs</FONT>
<BR><FONT SIZE=3D2>&gt; always delay the generation of local ringback =
for a short period of</FONT>
<BR><FONT SIZE=3D2>&gt; time. The UAC can, for instance, generate a =
short beep upon </FONT>
<BR><FONT SIZE=3D2>&gt; reception of</FONT>
<BR><FONT SIZE=3D2>&gt; the 180 (Ringing) response (this is already =
done by some</FONT>
<BR><FONT SIZE=3D2>&gt; circuit-switched mobile terminals) and one =
second later start </FONT>
<BR><FONT SIZE=3D2>&gt; generating</FONT>
<BR><FONT SIZE=3D2>&gt; local ringback if no media have been received =
during that period.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; \motivation{Note that adding such an indication =
does not keep </FONT>
<BR><FONT SIZE=3D2>&gt; UACs from</FONT>
<BR><FONT SIZE=3D2>&gt; implementing media arrival detection either, =
since they have to</FONT>
<BR><FONT SIZE=3D2>&gt; implement it anyway to cover other scenarios, =
like the race condition</FONT>
<BR><FONT SIZE=3D2>&gt; between the 200 OK for the INVITE and the first =
regular media </FONT>
<BR><FONT SIZE=3D2>&gt; packets).}</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Opinions?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E48A.9421E7E8--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 04:22:37 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15595
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 04:22:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h279Y2K01430
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 04:34:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279Y2O01427
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 04:34:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15559
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 04:21:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279W7O01035;
	Fri, 7 Mar 2003 04:32:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26HEqO24245
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 12:14:52 -0500
Received: from zrc2s0jx.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28725
	for <sipping@ietf.org>; Thu, 6 Mar 2003 12:03:10 -0500 (EST)
Received: from zsc3c028.us.nortel.com (zsc3c028.us.nortel.com [47.81.138.28])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h26H51o04528;
	Thu, 6 Mar 2003 11:05:01 -0600 (CST)
Received: by zsc3c028.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1LW2M9G8>; Thu, 6 Mar 2003 09:05:01 -0800
Message-ID: <2F1FC1DEA077D5119FAD00508BCFD6D20705951A@zsc3c030.us.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>
Cc: "Mark Watson" <mwatson@nortelnetworks.com>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Thu, 6 Mar 2003 09:04:52 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E402.80F13D5A"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E402.80F13D5A
Content-Type: text/plain

I agree with your analysis. 

Of course an alternative is for locally generated tones to override the
in-band
ringing. In the case of forking, I don't think we have much choice anyways.
But again,
this is a local policy.


> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se] 
> Sent: Thursday, March 06, 2003 5:46 AM
> To: Peterson, Jon
> Cc: Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P 
> (Richard)'; sipping
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Hi,
> 
> well, I can see which scenario he is after, but I agree that 
> the solution would not bring much value.
> 
> The scenario he is after is as follows; a gateway *knows* 
> that the user is being alerted and also *knows* that it will 
> be sending in-band ringing.
> 
> He is proposing a flag (i.e., null Altert-Info) for resolving 
> that situation.
> 
> We have two situations:
> 1) media packets arrive to the UAC before the 180.
> 
> 2) the 180 arrives before the first media packets.
> 
> Situation 1) is not a problem, since the UAC will (most 
> likely) not play local ringback, since it is already 
> receiving (and playing) media.
> 
> A null Alert Info would be helpful in Situation 2), but only 
> to avoid that the UAC plays local ringback during the 
> instants (it is a race
> condition) between the arrival of the 180 until the arrival 
> of the first media packets. A simpler solution would be to 
> always wait for, say, a second, before generating local 
> ringback after reception of a 180 (if during that second 
> media is not received).
> 
> In fact, this is what my mobile (GSM) does today. I dial a 
> number, and when the terminal knows that the other user is 
> being paged, it emits a beep (it also displays a message on 
> the screen). Ringback (in this case remote ringback, but it 
> really does not matter) starts a second or so later. Millions 
> of users (me included) find this behaviour acceptable, so it 
> would be acceptable as well for SIP-based systems.
> 
> If the only useful scenario for a null Alert-Info is a race 
> condition of this type, I agree that we should not adopt it.
> 
> Gonzalo
> 
> 
> 
> "Peterson, Jon" wrote:
> > 
> > I don't think that the Alert-Info header proposal will 
> really assuage 
> > the stated problem. Mr. Marshall raised a 'null' Alert-Info 
> proposal 
> > in the previous discussion, and it was rejected then, as it 
> should be 
> > now. Here's the thread:
> > 
> > 
> http://www1.ietf.org/mail-archive/working-groups/sipping/current/msg02
> > 545.ht
> > ml
> > 
> > Null Alert-Info wouldn't express anything more than just 
> sending a 183 
> > does
> > - a UAS should send a 183 when it knows it has some 
> non-ringing in-band
> > media. Null Alert-Info certainly wouldn't give you any 
> additional leverage
> > in cases where media arrives before signaling. I'm not sure what new
> > properties it would grant. The text already suggests a policy of:
> > 
> >         1.   Unless a 180 (Ringing) response is received, 
> never generate
> >              local ringback.
> > 
> > ... which essentially entails 'don't play local ringback if 183 is 
> > received'. I'm not sure how it would be any better to recommend a 
> > similar (and redundant) policy relating to Alert-Info.
> > 
> > As an aside, I do agree with Mr. Audet that we should discourage 
> > mixing local ringback tones with received media.
> > 
> > Jon Peterson
> > NeuStar, Inc.
> > 
> > > -----Original Message-----
> > > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > Sent: Wednesday, March 05, 2003 10:22 AM
> > > To: Mark Watson
> > > Cc: 'Ejzak, Richard P (Richard)'; sipping
> > > Subject: Re: [Sipping] New version of the early media draft
> > >
> > >
> > > Mark,
> > >
> > > many of your points have been discussed either in the draft or in 
> > > the mailing list before. The MGC-MG decomposition problem is 
> > > discussed in the draft, and the indication of the 
> presence in-band 
> > > media was discussed in the previous version of the draft.
> > >
> > > My initial proposal was to include an SDP parameter that provided 
> > > information about the intention of the sender. That is, 
> the sender 
> > > intended to send early media... that was seen as too 
> complex (and I 
> > > agree with that, by the way).
> > >
> > > But using some type of *simpler* mechanism that only 
> indicates that 
> > > the UAS does not want the UAC to generate local ringback (like
> > > the mechanism
> > > proposed in this thread), would be sensible, IMO.
> > >
> > > How do people feel about using the header field below in a 18x 
> > > response to indicate that the UAS would like the UAC not 
> to provide 
> > > local ringback (as proposed previously in this thread)?
> > >
> > > Alert-Info: <data:,>
> > >
> > > To me, once we have defined Alert-Info, this is not an 
> unreasonable 
> > > thing to do with this header. Opinions?
> > >
> > > Gonzalo
> > >
> > >
> > > Mark Watson wrote:
> > > >
> > > > Gonzalo,
> > > >
> > > > I would support this addition (or something like it - I
> > > confess to not
> > > > having followed all the details of this thread).
> > > >
> > > > This same problem has come up again and again over the last
> > > two years.
> > > > The root issue is a distinction between explicit 
> application layer 
> > > > indications and implicit media layer indications. If 
> the UAC is a 
> > > > distributed system (e.g. Media Gateway and Media Gateway
> > > Controller),
> > > > then the general model is that the MG is controlled by the MGC. 
> > > > The MGC has only explicit app. layer indications to work from -
> > > it cannot
> > > > take actions on the basis of receipt of not of media packets 
> > > > because it does not see them.
> > > >
> > > > Sure, the MG can report and 'RTP received' event and the
> > > MGC can then
> > > > instruct it appropriately, but this takes time & I don't think 
> > > > it's standardised.
> > > >
> > > > So, there should be enough information *in the SIP
> > > signalling* for the
> > > > UAC to take an intelligent decision on whether to play
> > > media or local
> > > > ringing. I don't want to prescribe how it takes this
> > > decision, but at
> > > > present there is information available to the UAS at 
> the SIP layer 
> > > > which is not communicated to the UAC (at the SIP layer) 
> - namely 
> > > > the availability of in-band media. This can only result in the
> > > UAC taking
> > > > inappropriate decisions in some scenarios.
> > > >
> > > > Perhaps we should not be telling the UAC to 'play local 
> ringing' 
> > > > or 'don't play local ringing', but if the UAS knows there is 
> > > > in-band information, it should tell the UAC in SIP.
> > > >
> > > > Regards...Mark
> > > >
> > > > > -----Original Message-----
> > > > > From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com]
> > > > > Sent: 04 March 2003 19:15
> > > > > To: 'Gonzalo Camarillo'
> > > > > Cc: sipping
> > > > > Subject: RE: [Sipping] New version of the early media draft
> > > > >
> > > > >
> > > > > Gonzalo,
> > > > > Thanks for your response.  I understand and agree with your 
> > > > > concerns about race conditions as well as the 
> discussion of how 
> > > > > to handle them.  But I do not want the UAS to blindly control 
> > > > > when the UAC should apply local ringing.  I want the 
> UAS to be 
> > > > > able to indicate when the UAC should NOT apply local 
> ringing.  
> > > > > There is a very important distinction here. According to your 
> > > > > draft, when a UAC receives a 180 it should be prepared to 
> > > > > generate local ringing, and it is a matter of local 
> policy what 
> > > > > the UAC should do when there is concurrent in-band media.  
> > > > > Gateway resources should be allocated to detect in-band media 
> > > > > and decide whether or not to generate ringing.  But 
> under some 
> > > > > circumstances the UAS knows that call progress information is 
> > > > > available in-band and the UAC does not need to bother to 
> > > > > allocate extra resources to monitor the media flow and 
> > > > > optionally inject ringing.  I believe it is important 
> for a UAS 
> > > > > to be able to indicate this situation to a UAC.  These are 
> > > > > processing ! resources that could be put to use elsewhere.  
> > > > > There are no race conditions in this situation - only the 
> > > > > recognition that local ringing and packet detection are 
> > > > > unnecessary.
> > > > >
> > > > > I stand by my original suggestion and continue to request a 
> > > > > modest addition to your draft based on this general 
> approach (my 
> > > > > previous email indicates one possible detailed solution).  
> > > > > Please let me know if you see any further issues.
> > > > >
> > > > > Regards,
> > > > > Richard Ejzak
> > > > > Lucent Technologies
> > > > >
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: Gonzalo Camarillo 
> > > > > [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > > > Sent: Tuesday, March 04, 2003 5:42 AM
> > > > > To: Ejzak, Richard P (Richard)
> > > > > Cc: sipping
> > > > > Subject: Re: [Sipping] New version of the early media draft
> > > > >
> > > > >
> > > > > Ejzak,
> > > > >
> > > > > the main problem with any SIP-layer mechanism that allows
> > > the UAS to
> > > >
> > > > > tell the UAC whether local ringback has to be 
> generated or not 
> > > > > is
> > > > race
> > > > > conditions. It really does not matter whether you use an
> > > Alert-Info
> > > > > header field in a reponse, or a special status code, or a 
> > > > > special body, or whatever to signal it. You always have race 
> > > > > conditions.
> > > > >
> > > > > Let's say that the UAS tells the UAC to generate 
> local ringback. 
> > > > > After a while, the callee picks up. The UAS sends 
> back a 200 OK 
> > > > > and starts sending media. The 200 OK, for some 
> reason, arrives 
> > > > > much later than the
> > > > > first media packets... what is the UAC supposed to do in the
> > > > > mean time?
> > > > > Ignore the media? Play the media anyway?
> > > > >
> > > > > Another scenario. The UAC starts receiving media before a
> > > > provisional
> > > > > response is received... what does it have to do?
> > > > >
> > > > > The main point is that, since signalling and media 
> are loosely 
> > > > > synchronized, you will always have race conditions 
> and you will 
> > > > > have to make guesses about what to do during those race 
> > > > > conditions anyway.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Gonzalo
> > > > >
> > > > >
> > > > >
> > > > > "Ejzak, Richard P (Richard)" wrote:
> > > > > >
> > > > > > Gonzalo,
> > > > > > It seems the single greatest difficulty with the gateway
> > > > > model (as you point out in your draft) is the difficulty of 
> > > > > depending on the arrival of media packets to 
> determine whether 
> > > > > or not to generate local ringing.  I have previously (last 
> > > > > summer) suggested a solution to this (use 180 exclusively to 
> > > > > indicate that local ringing should override any 
> inband media and 
> > > > > 183 otherwise) that is unacceptable since it does not satisfy 
> > > > > the requirement that 180 be used to indicate alerting of the 
> > > > > called party.
> > > > > >
> > > > > > Have you considered using the Alert-Info header in the
> > > > > following way? Since the real problem is that we 
> would like to 
> > > > > be able to discriminate between cases when 180 should cause 
> > > > > local ringing and when 180 should not (since inband media is 
> > > > > available), and it is the UAS that knows conclusively 
> which case 
> > > > > applies, let's agree on an encoding of the Alert-Info header 
> > > > > that indicates that local ringing should not be applied.  The 
> > > > > following line is a syntactically valid header:
> > > > > >
> > > > > > Alert-Info: <data:,>
> > > > > >
> > > > > > This header identifies the Alert-Info as the null string,
> > > > > which seems unambiguously and efficiently 
> interpretable within a 
> > > > > 180 response as "do not play local ringing even though the 
> > > > > called party is being alerted."  If the UAC does not 
> recognize 
> > > > > it or chooses not to interpret it for security 
> reasons, it can 
> > > > > be safely ignored.
> > > > > >
> > > > > > This modest addition to your draft (or an equivalent
> > > > > mechanism) would make it unnecessary for the gateway model to 
> > > > > depend on local policy or incoming media packet 
> detection and is 
> > > > > completely consistent with all of the constraints you have 
> > > > > documented.
> > > > > >
> > > > > > Another approach may be to actually specify the rtp stream
> > > > > as the source of the alert info (although this would 
> require the 
> > > > > definition of a new URI scheme type).  It might look like:
> > > > > >
> > > > > > Alert-Info: <rtp:/12.34.56.78:90>
> > > > > >
> > > > > > where the Alert-Info specifies the address and port of the
> > > > > rtp stream.  I don't like this mechanism since it is 
> redundant 
> > > > > with SDP and prone to error.  It is also ambiguous in 
> the event 
> > > > > of any subsequent media change using UPDATE (Do I begin to 
> > > > > generate local ringing if the rtp stream source 
> address changes?  
> > > > > Or do I continue to listen to the address specified in the 
> > > > > Alert-Info and ignore any UPDATEs?  No to both.)
> > > > > >
> > > > > > May I suggest including such a mechanism (preferably the
> > > > > first one) in your draft.
> > > > > >
> > > > > > Richard Ejzak
> > > > > > Lucent Technologies
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Gonzalo Camarillo
> > > [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > >
> > > > > > Sent: Monday, February 10, 2003 5:41 AM
> > > > > > To: sipping
> > > > > > Subject: [Sipping] New version of the early media draft
> > > > > >
> > > > > > Folks,
> > > > > >
> > > > > > I have just sumitted a new version of the early media
> > > > > draft. Until it
> > > > > > appears in the archives, you can fetch it from:
> > > > > >
> > > > > >
> > > >
> > > http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s
> > > ipping-early-media-01.txt
> > > >
> > > > >
> > > > > I have included all the (long and useful) discussions we
> > > had in the
> > > > > mailing list. Therefore, the draft now keeps separate the
> > > "gateway"
> > > > and
> > > > > the "application server" models. I have also removed 
> the parts 
> > > > > we
> > > > did
> > > > > not agree on.
> > > > >
> > > > > Feedback is, as usual, appreciated.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Gonzalo
> > > > > _______________________________________________
> > > > > Sipping mailing list
> > > https://www1.ietf.org/mailman/listinfo/sipping
> > > >
> > > > > This list is for NEW development of the application 
> of SIP Use 
> > > > > sip-implementors@cs.columbia.edu for questions on current sip 
> > > > > Use sip@ietf.org for new developments of core SIP
> > > >
> > > > --
> > > > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > > > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > > > Telecom R&D               Fax   :  +358  9 299 30 52
> > > > FIN-02420 Jorvas          Email :  
> Gonzalo.Camarillo@ericsson.com
> > > > Finland                   http://www.hut.fi/~gonzalo
> > > > _______________________________________________
> > > > Sipping mailing list  
> > > > https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the application of SIP
> > > > Use sip-implementors@cs.columbia.edu for questions on 
> current sip
> > > > Use sip@ietf.org for new developments of core SIP
> > >
> > > --
> > > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > > Telecom R&D               Fax   :  +358  9 299 30 52
> > > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> > > Finland                   http://www.hut.fi/~gonzalo
> > > _______________________________________________
> > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > > This list 
> is for NEW development of the application of SIP Use 
> > > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > > sip@ietf.org for new developments of core SIP
> > >
> 
> -- 
> Gonzalo Camarillo         Phone :  +358  9 299 33 71
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> Telecom R&D               Fax   :  +358  9 299 30 52
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> Finland                   http://www.hut.fi/~gonzalo
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 

------_=_NextPart_001_01C2E402.80F13D5A
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I agree with your analysis. </FONT>
</P>

<P><FONT SIZE=3D2>Of course an alternative is for locally generated =
tones to override the in-band</FONT>
<BR><FONT SIZE=3D2>ringing. In the case of forking, I don't think we =
have much choice anyways. But again,</FONT>
<BR><FONT SIZE=3D2>this is a local policy.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, March 06, 2003 5:46 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Peterson, Jon</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, =
Richard P </FONT>
<BR><FONT SIZE=3D2>&gt; (Richard)'; sipping</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; well, I can see which scenario he is after, but =
I agree that </FONT>
<BR><FONT SIZE=3D2>&gt; the solution would not bring much value.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The scenario he is after is as follows; a =
gateway *knows* </FONT>
<BR><FONT SIZE=3D2>&gt; that the user is being alerted and also *knows* =
that it will </FONT>
<BR><FONT SIZE=3D2>&gt; be sending in-band ringing.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; He is proposing a flag (i.e., null Altert-Info) =
for resolving </FONT>
<BR><FONT SIZE=3D2>&gt; that situation.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; We have two situations:</FONT>
<BR><FONT SIZE=3D2>&gt; 1) media packets arrive to the UAC before the =
180.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 2) the 180 arrives before the first media =
packets.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Situation 1) is not a problem, since the UAC =
will (most </FONT>
<BR><FONT SIZE=3D2>&gt; likely) not play local ringback, since it is =
already </FONT>
<BR><FONT SIZE=3D2>&gt; receiving (and playing) media.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; A null Alert Info would be helpful in Situation =
2), but only </FONT>
<BR><FONT SIZE=3D2>&gt; to avoid that the UAC plays local ringback =
during the </FONT>
<BR><FONT SIZE=3D2>&gt; instants (it is a race</FONT>
<BR><FONT SIZE=3D2>&gt; condition) between the arrival of the 180 until =
the arrival </FONT>
<BR><FONT SIZE=3D2>&gt; of the first media packets. A simpler solution =
would be to </FONT>
<BR><FONT SIZE=3D2>&gt; always wait for, say, a second, before =
generating local </FONT>
<BR><FONT SIZE=3D2>&gt; ringback after reception of a 180 (if during =
that second </FONT>
<BR><FONT SIZE=3D2>&gt; media is not received).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; In fact, this is what my mobile (GSM) does =
today. I dial a </FONT>
<BR><FONT SIZE=3D2>&gt; number, and when the terminal knows that the =
other user is </FONT>
<BR><FONT SIZE=3D2>&gt; being paged, it emits a beep (it also displays =
a message on </FONT>
<BR><FONT SIZE=3D2>&gt; the screen). Ringback (in this case remote =
ringback, but it </FONT>
<BR><FONT SIZE=3D2>&gt; really does not matter) starts a second or so =
later. Millions </FONT>
<BR><FONT SIZE=3D2>&gt; of users (me included) find this behaviour =
acceptable, so it </FONT>
<BR><FONT SIZE=3D2>&gt; would be acceptable as well for SIP-based =
systems.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; If the only useful scenario for a null =
Alert-Info is a race </FONT>
<BR><FONT SIZE=3D2>&gt; condition of this type, I agree that we should =
not adopt it.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;Peterson, Jon&quot; wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I don't think that the Alert-Info header =
proposal will </FONT>
<BR><FONT SIZE=3D2>&gt; really assuage </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the stated problem. Mr. Marshall raised a =
'null' Alert-Info </FONT>
<BR><FONT SIZE=3D2>&gt; proposal </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; in the previous discussion, and it was =
rejected then, as it </FONT>
<BR><FONT SIZE=3D2>&gt; should be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; now. Here's the thread:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www1.ietf.org/mail-archive/working-groups/sipping/current=
/msg02" =
TARGET=3D"_blank">http://www1.ietf.org/mail-archive/working-groups/sippi=
ng/current/msg02</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 545.ht</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ml</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Null Alert-Info wouldn't express anything =
more than just </FONT>
<BR><FONT SIZE=3D2>&gt; sending a 183 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; does</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; - a UAS should send a 183 when it knows it =
has some </FONT>
<BR><FONT SIZE=3D2>&gt; non-ringing in-band</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; media. Null Alert-Info certainly wouldn't =
give you any </FONT>
<BR><FONT SIZE=3D2>&gt; additional leverage</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; in cases where media arrives before =
signaling. I'm not sure what new</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; properties it would grant. The text =
already suggests a policy of:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1.&nbsp;&nbsp; =
Unless a 180 (Ringing) response is received, </FONT>
<BR><FONT SIZE=3D2>&gt; never generate</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; local ringback.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ... which essentially entails 'don't play =
local ringback if 183 is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; received'. I'm not sure how it would be =
any better to recommend a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; similar (and redundant) policy relating to =
Alert-Info.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; As an aside, I do agree with Mr. Audet =
that we should discourage </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; mixing local ringback tones with received =
media.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Jon Peterson</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; NeuStar, Inc.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sent: Wednesday, March 05, 2003 10:22 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; To: Mark Watson</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Cc: 'Ejzak, Richard P (Richard)'; =
sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Subject: Re: [Sipping] New version of =
the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Mark,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; many of your points have been =
discussed either in the draft or in </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the mailing list before. The MGC-MG =
decomposition problem is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; discussed in the draft, and the =
indication of the </FONT>
<BR><FONT SIZE=3D2>&gt; presence in-band </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; media was discussed in the previous =
version of the draft.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; My initial proposal was to include an =
SDP parameter that provided </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; information about the intention of =
the sender. That is, </FONT>
<BR><FONT SIZE=3D2>&gt; the sender </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; intended to send early media... that =
was seen as too </FONT>
<BR><FONT SIZE=3D2>&gt; complex (and I </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; agree with that, by the way).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; But using some type of *simpler* =
mechanism that only </FONT>
<BR><FONT SIZE=3D2>&gt; indicates that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the UAS does not want the UAC to =
generate local ringback (like</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the mechanism</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; proposed in this thread), would be =
sensible, IMO.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; How do people feel about using the =
header field below in a 18x </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; response to indicate that the UAS =
would like the UAC not </FONT>
<BR><FONT SIZE=3D2>&gt; to provide </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; local ringback (as proposed =
previously in this thread)?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Alert-Info: &lt;data:,&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; To me, once we have defined =
Alert-Info, this is not an </FONT>
<BR><FONT SIZE=3D2>&gt; unreasonable </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; thing to do with this header. =
Opinions?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Mark Watson wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; I would support this addition =
(or something like it - I</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; confess to not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; having followed all the details =
of this thread).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; This same problem has come up =
again and again over the last</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; two years.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; The root issue is a distinction =
between explicit </FONT>
<BR><FONT SIZE=3D2>&gt; application layer </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; indications and implicit media =
layer indications. If </FONT>
<BR><FONT SIZE=3D2>&gt; the UAC is a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; distributed system (e.g. Media =
Gateway and Media Gateway</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Controller),</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; then the general model is that =
the MG is controlled by the MGC. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; The MGC has only explicit app. =
layer indications to work from -</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; it cannot</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; take actions on the basis of =
receipt of not of media packets </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; because it does not see =
them.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Sure, the MG can report and 'RTP =
received' event and the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; MGC can then</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; instruct it appropriately, but =
this takes time &amp; I don't think </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; it's standardised.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; So, there should be enough =
information *in the SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; signalling* for the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; UAC to take an intelligent =
decision on whether to play</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; media or local</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; ringing. I don't want to =
prescribe how it takes this</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; decision, but at</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; present there is information =
available to the UAS at </FONT>
<BR><FONT SIZE=3D2>&gt; the SIP layer </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; which is not communicated to the =
UAC (at the SIP layer) </FONT>
<BR><FONT SIZE=3D2>&gt; - namely </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; the availability of in-band =
media. This can only result in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; UAC taking</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; inappropriate decisions in some =
scenarios.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Perhaps we should not be telling =
the UAC to 'play local </FONT>
<BR><FONT SIZE=3D2>&gt; ringing' </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; or 'don't play local ringing', =
but if the UAS knows there is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; in-band information, it should =
tell the UAC in SIP.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Regards...Mark</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; From: Ejzak, Richard P =
(Richard) [<A =
HREF=3D"mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Sent: 04 March 2003 =
19:15</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; To: 'Gonzalo =
Camarillo'</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Cc: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Subject: RE: [Sipping] New =
version of the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Thanks for your =
response.&nbsp; I understand and agree with your </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; concerns about race =
conditions as well as the </FONT>
<BR><FONT SIZE=3D2>&gt; discussion of how </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; to handle them.&nbsp; But I =
do not want the UAS to blindly control </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; when the UAC should apply =
local ringing.&nbsp; I want the </FONT>
<BR><FONT SIZE=3D2>&gt; UAS to be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; able to indicate when the =
UAC should NOT apply local </FONT>
<BR><FONT SIZE=3D2>&gt; ringing.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; There is a very important =
distinction here. According to your </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; draft, when a UAC receives =
a 180 it should be prepared to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; generate local ringing, and =
it is a matter of local </FONT>
<BR><FONT SIZE=3D2>&gt; policy what </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; the UAC should do when =
there is concurrent in-band media.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Gateway resources should be =
allocated to detect in-band media </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; and decide whether or not =
to generate ringing.&nbsp; But </FONT>
<BR><FONT SIZE=3D2>&gt; under some </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; circumstances the UAS knows =
that call progress information is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; available in-band and the =
UAC does not need to bother to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; allocate extra resources to =
monitor the media flow and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; optionally inject =
ringing.&nbsp; I believe it is important </FONT>
<BR><FONT SIZE=3D2>&gt; for a UAS </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; to be able to indicate this =
situation to a UAC.&nbsp; These are </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; processing ! resources that =
could be put to use elsewhere.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; There are no race =
conditions in this situation - only the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; recognition that local =
ringing and packet detection are </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; unnecessary.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; I stand by my original =
suggestion and continue to request a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; modest addition to your =
draft based on this general </FONT>
<BR><FONT SIZE=3D2>&gt; approach (my </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; previous email indicates =
one possible detailed solution).&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Please let me know if you =
see any further issues.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Regards,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Richard Ejzak</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Lucent Technologies</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; From: Gonzalo Camarillo =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Sent: Tuesday, March 04, =
2003 5:42 AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; To: Ejzak, Richard P =
(Richard)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Cc: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Subject: Re: [Sipping] New =
version of the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Ejzak,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; the main problem with any =
SIP-layer mechanism that allows</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the UAS to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; tell the UAC whether local =
ringback has to be </FONT>
<BR><FONT SIZE=3D2>&gt; generated or not </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; race</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; conditions. It really does =
not matter whether you use an</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Alert-Info</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; header field in a reponse, =
or a special status code, or a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; special body, or whatever =
to signal it. You always have race </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; conditions.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Let's say that the UAS =
tells the UAC to generate </FONT>
<BR><FONT SIZE=3D2>&gt; local ringback. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; After a while, the callee =
picks up. The UAS sends </FONT>
<BR><FONT SIZE=3D2>&gt; back a 200 OK </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; and starts sending media. =
The 200 OK, for some </FONT>
<BR><FONT SIZE=3D2>&gt; reason, arrives </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; much later than the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; first media packets... what =
is the UAC supposed to do in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; mean time?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Ignore the media? Play the =
media anyway?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Another scenario. The UAC =
starts receiving media before a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; provisional</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; response is received... =
what does it have to do?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; The main point is that, =
since signalling and media </FONT>
<BR><FONT SIZE=3D2>&gt; are loosely </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; synchronized, you will =
always have race conditions </FONT>
<BR><FONT SIZE=3D2>&gt; and you will </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; have to make guesses about =
what to do during those race </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; conditions anyway.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &quot;Ejzak, Richard P =
(Richard)&quot; wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; It seems the single =
greatest difficulty with the gateway</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; model (as you point out in =
your draft) is the difficulty of </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; depending on the arrival of =
media packets to </FONT>
<BR><FONT SIZE=3D2>&gt; determine whether </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; or not to generate local =
ringing.&nbsp; I have previously (last </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; summer) suggested a =
solution to this (use 180 exclusively to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; indicate that local ringing =
should override any </FONT>
<BR><FONT SIZE=3D2>&gt; inband media and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; 183 otherwise) that is =
unacceptable since it does not satisfy </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; the requirement that 180 be =
used to indicate alerting of the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; called party.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Have you considered =
using the Alert-Info header in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; following way? Since the =
real problem is that we </FONT>
<BR><FONT SIZE=3D2>&gt; would like to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; be able to discriminate =
between cases when 180 should cause </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; local ringing and when 180 =
should not (since inband media is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; available), and it is the =
UAS that knows conclusively </FONT>
<BR><FONT SIZE=3D2>&gt; which case </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; applies, let's agree on an =
encoding of the Alert-Info header </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; that indicates that local =
ringing should not be applied.&nbsp; The </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; following line is a =
syntactically valid header:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Alert-Info: =
&lt;data:,&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; This header identifies =
the Alert-Info as the null string,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; which seems unambiguously =
and efficiently </FONT>
<BR><FONT SIZE=3D2>&gt; interpretable within a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; 180 response as &quot;do =
not play local ringing even though the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; called party is being =
alerted.&quot;&nbsp; If the UAC does not </FONT>
<BR><FONT SIZE=3D2>&gt; recognize </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; it or chooses not to =
interpret it for security </FONT>
<BR><FONT SIZE=3D2>&gt; reasons, it can </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; be safely ignored.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; This modest addition =
to your draft (or an equivalent</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; mechanism) would make it =
unnecessary for the gateway model to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; depend on local policy or =
incoming media packet </FONT>
<BR><FONT SIZE=3D2>&gt; detection and is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; completely consistent with =
all of the constraints you have </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; documented.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Another approach may =
be to actually specify the rtp stream</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; as the source of the alert =
info (although this would </FONT>
<BR><FONT SIZE=3D2>&gt; require the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; definition of a new URI =
scheme type).&nbsp; It might look like:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Alert-Info: =
&lt;rtp:/12.34.56.78:90&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; where the Alert-Info =
specifies the address and port of the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; rtp stream.&nbsp; I don't =
like this mechanism since it is </FONT>
<BR><FONT SIZE=3D2>&gt; redundant </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; with SDP and prone to =
error.&nbsp; It is also ambiguous in </FONT>
<BR><FONT SIZE=3D2>&gt; the event </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; of any subsequent media =
change using UPDATE (Do I begin to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; generate local ringing if =
the rtp stream source </FONT>
<BR><FONT SIZE=3D2>&gt; address changes?&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Or do I continue to listen =
to the address specified in the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Alert-Info and ignore any =
UPDATEs?&nbsp; No to both.)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; May I suggest =
including such a mechanism (preferably the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; first one) in your =
draft.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Richard Ejzak</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Lucent =
Technologies</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; From: Gonzalo =
Camarillo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Sent: Monday, February =
10, 2003 5:41 AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; To: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Subject: [Sipping] New =
version of the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Folks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; I have just sumitted a =
new version of the early media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; draft. Until it</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; appears in the =
archives, you can fetch it from:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; <A =
HREF=3D"http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s" =
TARGET=3D"_blank">http://standards.ericsson.net/gonzalo/papers/draft-cam=
arillo-s</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ipping-early-media-01.txt</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; I have included all the =
(long and useful) discussions we</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; had in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; mailing list. Therefore, =
the draft now keeps separate the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &quot;gateway&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; the &quot;application =
server&quot; models. I have also removed </FONT>
<BR><FONT SIZE=3D2>&gt; the parts </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; we</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; did</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; not agree on.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Feedback is, as usual, =
appreciated.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Sipping mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; This list is for NEW =
development of the application </FONT>
<BR><FONT SIZE=3D2>&gt; of SIP Use </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
sip-implementors@cs.columbia.edu for questions on current sip </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Use sip@ietf.org for new =
developments of core SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; =
Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Sipping mailing list&nbsp; =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; This list is for NEW development =
of the application of SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Use =
sip-implementors@cs.columbia.edu for questions on </FONT>
<BR><FONT SIZE=3D2>&gt; current sip</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Use sip@ietf.org for new =
developments of core SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sipping mailing list&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; This list </FONT>
<BR><FONT SIZE=3D2>&gt; is for NEW development of the application of =
SIP Use </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; sip-implementors@cs.columbia.edu for =
questions on current sip Use </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; sip@ietf.org for new developments of =
core SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -- </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>&gt; Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>&gt; Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>&gt; FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT SIZE=3D2>&gt; =
Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Sipping mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; This list is for NEW development of the =
application of SIP</FONT>
<BR><FONT SIZE=3D2>&gt; Use sip-implementors@cs.columbia.edu for =
questions on current </FONT>
<BR><FONT SIZE=3D2>&gt; sip Use sip@ietf.org for new developments of =
core SIP</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E402.80F13D5A--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 04:22:42 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15609
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 04:22:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h279Y7201483
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 04:34:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279Y7O01480
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 04:34:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15564
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 04:22:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279W4O01014;
	Fri, 7 Mar 2003 04:32:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26FMPO12769
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 10:22:25 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19230
	for <sipping@ietf.org>; Thu, 6 Mar 2003 10:10:45 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h26FCi325360;
	Thu, 6 Mar 2003 10:12:45 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h26FCeX03461;
	Thu, 6 Mar 2003 15:12:41 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id FS3MX5DN; Thu, 6 Mar 2003 15:12:41 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FS3953FL>; Thu, 6 Mar 2003 15:11:24 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C3E@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        "Peterson, Jon" <jon.peterson@neustar.biz>
Cc: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping
	 <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Thu, 6 Mar 2003 15:11:20 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E3F2.A4967FB4"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E3F2.A4967FB4
Content-Type: text/plain;
	charset="iso-8859-1"

Ok, so I have now read the draft (sorry 'bout that short delay there). It is
very good, btw.

The problem is related to 180 only, and specifically the scenario described
by Gonzalo below. The draft does indeed include a good treatment of the
problem for decomposed MG/MGC arhicitecture but the only solution suggested
seems to be mixing local ringback with inband media. I tend to agree with
Francois and Mr. Peterson, that this is not a good idea.

What is needed, to my mind, is an indication at the SIP layer that in-band
media is/will be provided. This indication is there implicitly in a 183
(there is no other reason why you would send a 183), but not in 180.

I don't care whether it's Alert-Info or something else. Mr Peterson seemed
to object to Alert-Info - do you have an alternative suggestion ?

This requirement has re-surfaced every six months for at least the past two
years & my bet is that it will keep resurfacing until we address it.

Regards...Mark

PS: Minor nit in the first para of 2.1.1 - two occurances of UAS in the last
line should be UAC, I think.

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: 06 March 2003 13:46
> To: Peterson, Jon
> Cc: Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P 
> (Richard)'; sipping
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Hi,
> 
> well, I can see which scenario he is after, but I agree that the
> solution would not bring much value.
> 
> The scenario he is after is as follows; a gateway *knows* 
> that the user
> is being alerted and also *knows* that it will be sending in-band
> ringing.
> 
> He is proposing a flag (i.e., null Altert-Info) for resolving that
> situation.
> 
> We have two situations:
> 1) media packets arrive to the UAC before the 180.
> 
> 2) the 180 arrives before the first media packets.
> 
> Situation 1) is not a problem, since the UAC will (most 
> likely) not play
> local ringback, since it is already receiving (and playing) media.
> 
> A null Alert Info would be helpful in Situation 2), but only to avoid
> that the UAC plays local ringback during the instants (it is a race
> condition) between the arrival of the 180 until the arrival 
> of the first
> media packets. A simpler solution would be to always wait for, say, a
> second, before generating local ringback after reception of a 180 (if
> during that second media is not received).
> 
> In fact, this is what my mobile (GSM) does today. I dial a number, and
> when the terminal knows that the other user is being paged, it emits a
> beep (it also displays a message on the screen). Ringback (in 
> this case
> remote ringback, but it really does not matter) starts a second or so
> later. Millions of users (me included) find this behaviour acceptable,
> so it would be acceptable as well for SIP-based systems.
> 
> If the only useful scenario for a null Alert-Info is a race 
> condition of
> this type, I agree that we should not adopt it.
> 
> Gonzalo
> 
> 
> 
> "Peterson, Jon" wrote:
> > 
> > I don't think that the Alert-Info header proposal will 
> really assuage the
> > stated problem. Mr. Marshall raised a 'null' Alert-Info 
> proposal in the
> > previous discussion, and it was rejected then, as it should 
> be now. Here's
> > the thread:
> > 
> > 
> http://www1.ietf.org/mail-archive/working-groups/sipping/curre
> nt/msg02545.ht
> > ml
> > 
> > Null Alert-Info wouldn't express anything more than just 
> sending a 183 does
> > - a UAS should send a 183 when it knows it has some 
> non-ringing in-band
> > media. Null Alert-Info certainly wouldn't give you any 
> additional leverage
> > in cases where media arrives before signaling. I'm not sure what new
> > properties it would grant. The text already suggests a policy of:
> > 
> >         1.   Unless a 180 (Ringing) response is received, 
> never generate
> >              local ringback.
> > 
> > ... which essentially entails 'don't play local ringback if 183 is
> > received'. I'm not sure how it would be any better to 
> recommend a similar
> > (and redundant) policy relating to Alert-Info.
> > 
> > As an aside, I do agree with Mr. Audet that we should 
> discourage mixing
> > local ringback tones with received media.
> > 
> > Jon Peterson
> > NeuStar, Inc.
> > 
> > > -----Original Message-----
> > > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > Sent: Wednesday, March 05, 2003 10:22 AM
> > > To: Mark Watson
> > > Cc: 'Ejzak, Richard P (Richard)'; sipping
> > > Subject: Re: [Sipping] New version of the early media draft
> > >
> > >
> > > Mark,
> > >
> > > many of your points have been discussed either in the 
> draft or in the
> > > mailing list before. The MGC-MG decomposition problem is 
> discussed in
> > > the draft, and the indication of the presence in-band media was
> > > discussed in the previous version of the draft.
> > >
> > > My initial proposal was to include an SDP parameter that provided
> > > information about the intention of the sender. That is, the sender
> > > intended to send early media... that was seen as too 
> complex (and I
> > > agree with that, by the way).
> > >
> > > But using some type of *simpler* mechanism that only
> > > indicates that the
> > > UAS does not want the UAC to generate local ringback (like
> > > the mechanism
> > > proposed in this thread), would be sensible, IMO.
> > >
> > > How do people feel about using the header field below in a
> > > 18x response
> > > to indicate that the UAS would like the UAC not to provide local
> > > ringback (as proposed previously in this thread)?
> > >
> > > Alert-Info: <data:,>
> > >
> > > To me, once we have defined Alert-Info, this is not an 
> unreasonable
> > > thing to do with this header. Opinions?
> > >
> > > Gonzalo
> > >
> > >
> > > Mark Watson wrote:
> > > >
> > > > Gonzalo,
> > > >
> > > > I would support this addition (or something like it - I
> > > confess to not
> > > > having followed all the details of this thread).
> > > >
> > > > This same problem has come up again and again over the last
> > > two years.
> > > > The root issue is a distinction between explicit 
> application layer
> > > > indications and implicit media layer indications. If 
> the UAC is a
> > > > distributed system (e.g. Media Gateway and Media Gateway
> > > Controller),
> > > > then the general model is that the MG is controlled by 
> the MGC. The
> > > > MGC has only explicit app. layer indications to work from -
> > > it cannot
> > > > take actions on the basis of receipt of not of media 
> packets because
> > > > it does not see them.
> > > >
> > > > Sure, the MG can report and 'RTP received' event and the
> > > MGC can then
> > > > instruct it appropriately, but this takes time & I 
> don't think it's
> > > > standardised.
> > > >
> > > > So, there should be enough information *in the SIP
> > > signalling* for the
> > > > UAC to take an intelligent decision on whether to play
> > > media or local
> > > > ringing. I don't want to prescribe how it takes this
> > > decision, but at
> > > > present there is information available to the UAS at 
> the SIP layer
> > > > which is not communicated to the UAC (at the SIP layer) 
> - namely the
> > > > availability of in-band media. This can only result in the
> > > UAC taking
> > > > inappropriate decisions in some scenarios.
> > > >
> > > > Perhaps we should not be telling the UAC to 'play local 
> ringing' or
> > > > 'don't play local ringing', but if the UAS knows there 
> is in-band
> > > > information, it should tell the UAC in SIP.
> > > >
> > > > Regards...Mark
> > > >
> > > > > -----Original Message-----
> > > > > From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com]
> > > > > Sent: 04 March 2003 19:15
> > > > > To: 'Gonzalo Camarillo'
> > > > > Cc: sipping
> > > > > Subject: RE: [Sipping] New version of the early media draft
> > > > >
> > > > >
> > > > > Gonzalo,
> > > > > Thanks for your response.  I understand and agree with your
> > > > > concerns about race conditions as well as the discussion of
> > > > > how to handle them.  But I do not want the UAS to blindly
> > > > > control when the UAC should apply local ringing.  I want the
> > > > > UAS to be able to indicate when the UAC should NOT apply
> > > > > local ringing.  There is a very important distinction here.
> > > > > According to your draft, when a UAC receives a 180 it should
> > > > > be prepared to generate local ringing, and it is a matter of
> > > > > local policy what the UAC should do when there is concurrent
> > > > > in-band media.  Gateway resources should be allocated to
> > > > > detect in-band media and decide whether or not to generate
> > > > > ringing.  But under some circumstances the UAS knows that
> > > > > call progress information is available in-band and the UAC
> > > > > does not need to bother to allocate extra resources to
> > > > > monitor the media flow and optionally inject ringing.  I
> > > > > believe it is important for a UAS to be able to indicate this
> > > > > situation to a UAC.  These are processing !
> > > > > resources that could be put to use elsewhere.  There are no
> > > > > race conditions in this situation - only the recognition that
> > > > > local ringing and packet detection are unnecessary.
> > > > >
> > > > > I stand by my original suggestion and continue to request a
> > > > > modest addition to your draft based on this general approach
> > > > > (my previous email indicates one possible detailed solution).
> > > > >  Please let me know if you see any further issues.
> > > > >
> > > > > Regards,
> > > > > Richard Ejzak
> > > > > Lucent Technologies
> > > > >
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: Gonzalo Camarillo 
> [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > > > Sent: Tuesday, March 04, 2003 5:42 AM
> > > > > To: Ejzak, Richard P (Richard)
> > > > > Cc: sipping
> > > > > Subject: Re: [Sipping] New version of the early media draft
> > > > >
> > > > >
> > > > > Ejzak,
> > > > >
> > > > > the main problem with any SIP-layer mechanism that allows
> > > the UAS to
> > > >
> > > > > tell the UAC whether local ringback has to be 
> generated or not is
> > > > race
> > > > > conditions. It really does not matter whether you use an
> > > Alert-Info
> > > > > header field in a reponse, or a special status code, or a
> > > > > special body,
> > > > > or whatever to signal it. You always have race conditions.
> > > > >
> > > > > Let's say that the UAS tells the UAC to generate local
> > > > > ringback. After a
> > > > > while, the callee picks up. The UAS sends back a 200 
> OK and starts
> > > > > sending media. The 200 OK, for some reason, arrives much
> > > > > later than the
> > > > > first media packets... what is the UAC supposed to do in the
> > > > > mean time?
> > > > > Ignore the media? Play the media anyway?
> > > > >
> > > > > Another scenario. The UAC starts receiving media before a
> > > > provisional
> > > > > response is received... what does it have to do?
> > > > >
> > > > > The main point is that, since signalling and media are loosely
> > > > > synchronized, you will always have race conditions and you
> > > > > will have to
> > > > > make guesses about what to do during those race 
> conditions anyway.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Gonzalo
> > > > >
> > > > >
> > > > >
> > > > > "Ejzak, Richard P (Richard)" wrote:
> > > > > >
> > > > > > Gonzalo,
> > > > > > It seems the single greatest difficulty with the gateway
> > > > > model (as you point out in your draft) is the difficulty of
> > > > > depending on the arrival of media packets to determine
> > > > > whether or not to generate local ringing.  I have previously
> > > > > (last summer) suggested a solution to this (use 180
> > > > > exclusively to indicate that local ringing should override
> > > > > any inband media and 183 otherwise) that is unacceptable
> > > > > since it does not satisfy the requirement that 180 be used to
> > > > > indicate alerting of the called party.
> > > > > >
> > > > > > Have you considered using the Alert-Info header in the
> > > > > following way? Since the real problem is that we would like
> > > > > to be able to discriminate between cases when 180 should
> > > > > cause local ringing and when 180 should not (since inband
> > > > > media is available), and it is the UAS that knows
> > > > > conclusively which case applies, let's agree on an encoding
> > > > > of the Alert-Info header that indicates that local ringing
> > > > > should not be applied.  The following line is a syntactically
> > > > > valid header:
> > > > > >
> > > > > > Alert-Info: <data:,>
> > > > > >
> > > > > > This header identifies the Alert-Info as the null string,
> > > > > which seems unambiguously and efficiently interpretable
> > > > > within a 180 response as "do not play local ringing even
> > > > > though the called party is being alerted."  If the UAC does
> > > > > not recognize it or chooses not to interpret it for security
> > > > > reasons, it can be safely ignored.
> > > > > >
> > > > > > This modest addition to your draft (or an equivalent
> > > > > mechanism) would make it unnecessary for the gateway model to
> > > > > depend on local policy or incoming media packet detection and
> > > > > is completely consistent with all of the constraints you have
> > > > > documented.
> > > > > >
> > > > > > Another approach may be to actually specify the rtp stream
> > > > > as the source of the alert info (although this would require
> > > > > the definition of a new URI scheme type).  It might look like:
> > > > > >
> > > > > > Alert-Info: <rtp:/12.34.56.78:90>
> > > > > >
> > > > > > where the Alert-Info specifies the address and port of the
> > > > > rtp stream.  I don't like this mechanism since it is
> > > > > redundant with SDP and prone to error.  It is also ambiguous
> > > > > in the event of any subsequent media change using UPDATE (Do
> > > > > I begin to generate local ringing if the rtp stream source
> > > > > address changes?  Or do I continue to listen to the address
> > > > > specified in the Alert-Info and ignore any UPDATEs?  
> No to both.)
> > > > > >
> > > > > > May I suggest including such a mechanism (preferably the
> > > > > first one) in your draft.
> > > > > >
> > > > > > Richard Ejzak
> > > > > > Lucent Technologies
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Gonzalo Camarillo
> > > [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > >
> > > > > > Sent: Monday, February 10, 2003 5:41 AM
> > > > > > To: sipping
> > > > > > Subject: [Sipping] New version of the early media draft
> > > > > >
> > > > > > Folks,
> > > > > >
> > > > > > I have just sumitted a new version of the early media
> > > > > draft. Until it
> > > > > > appears in the archives, you can fetch it from:
> > > > > >
> > > > > >
> > > >
> > > http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s
> > > ipping-early-media-01.txt
> > > >
> > > > >
> > > > > I have included all the (long and useful) discussions we
> > > had in the
> > > > > mailing list. Therefore, the draft now keeps separate the
> > > "gateway"
> > > > and
> > > > > the "application server" models. I have also removed 
> the parts we
> > > > did
> > > > > not agree on.
> > > > >
> > > > > Feedback is, as usual, appreciated.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Gonzalo
> > > > > _______________________________________________
> > > > > Sipping mailing list
> > > https://www1.ietf.org/mailman/listinfo/sipping
> > > >
> > > > > This list is for NEW development of the application of SIP
> > > > > Use sip-implementors@cs.columbia.edu for questions on 
> current sip
> > > > > Use sip@ietf.org for new developments of core SIP
> > > >
> > > > --
> > > > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > > > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > > > Telecom R&D               Fax   :  +358  9 299 30 52
> > > > FIN-02420 Jorvas          Email :  
> Gonzalo.Camarillo@ericsson.com
> > > > Finland                   http://www.hut.fi/~gonzalo
> > > > _______________________________________________
> > > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the application of SIP
> > > > Use sip-implementors@cs.columbia.edu for questions on 
> current sip
> > > > Use sip@ietf.org for new developments of core SIP
> > >
> > > --
> > > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > > Telecom R&D               Fax   :  +358  9 299 30 52
> > > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> > > Finland                   http://www.hut.fi/~gonzalo
> > > _______________________________________________
> > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sip@ietf.org for new developments of core SIP
> > >
> 
> -- 
> Gonzalo Camarillo         Phone :  +358  9 299 33 71
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> Telecom R&D               Fax   :  +358  9 299 30 52
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> Finland                   http://www.hut.fi/~gonzalo
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Ok, so I have now read the draft (sorry 'bout that =
short delay there). It is very good, btw.</FONT>
</P>

<P><FONT SIZE=3D2>The problem is related to 180 only, and specifically =
the scenario described by Gonzalo below. The draft does indeed include =
a good treatment of the problem for decomposed MG/MGC arhicitecture but =
the only solution suggested seems to be mixing local ringback with =
inband media. I tend to agree with Francois and Mr. Peterson, that this =
is not a good idea.</FONT></P>

<P><FONT SIZE=3D2>What is needed, to my mind, is an indication at the =
SIP layer that in-band media is/will be provided. This indication is =
there implicitly in a 183 (there is no other reason why you would send =
a 183), but not in 180.</FONT></P>

<P><FONT SIZE=3D2>I don't care whether it's Alert-Info or something =
else. Mr Peterson seemed to object to Alert-Info - do you have an =
alternative suggestion ?</FONT></P>

<P><FONT SIZE=3D2>This requirement has re-surfaced every six months for =
at least the past two years &amp; my bet is that it will keep =
resurfacing until we address it.</FONT></P>

<P><FONT SIZE=3D2>Regards...Mark</FONT>
</P>

<P><FONT SIZE=3D2>PS: Minor nit in the first para of 2.1.1 - two =
occurances of UAS in the last line should be UAC, I think.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 06 March 2003 13:46</FONT>
<BR><FONT SIZE=3D2>&gt; To: Peterson, Jon</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, =
Richard P </FONT>
<BR><FONT SIZE=3D2>&gt; (Richard)'; sipping</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; well, I can see which scenario he is after, but =
I agree that the</FONT>
<BR><FONT SIZE=3D2>&gt; solution would not bring much value.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The scenario he is after is as follows; a =
gateway *knows* </FONT>
<BR><FONT SIZE=3D2>&gt; that the user</FONT>
<BR><FONT SIZE=3D2>&gt; is being alerted and also *knows* that it will =
be sending in-band</FONT>
<BR><FONT SIZE=3D2>&gt; ringing.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; He is proposing a flag (i.e., null Altert-Info) =
for resolving that</FONT>
<BR><FONT SIZE=3D2>&gt; situation.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; We have two situations:</FONT>
<BR><FONT SIZE=3D2>&gt; 1) media packets arrive to the UAC before the =
180.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 2) the 180 arrives before the first media =
packets.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Situation 1) is not a problem, since the UAC =
will (most </FONT>
<BR><FONT SIZE=3D2>&gt; likely) not play</FONT>
<BR><FONT SIZE=3D2>&gt; local ringback, since it is already receiving =
(and playing) media.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; A null Alert Info would be helpful in Situation =
2), but only to avoid</FONT>
<BR><FONT SIZE=3D2>&gt; that the UAC plays local ringback during the =
instants (it is a race</FONT>
<BR><FONT SIZE=3D2>&gt; condition) between the arrival of the 180 until =
the arrival </FONT>
<BR><FONT SIZE=3D2>&gt; of the first</FONT>
<BR><FONT SIZE=3D2>&gt; media packets. A simpler solution would be to =
always wait for, say, a</FONT>
<BR><FONT SIZE=3D2>&gt; second, before generating local ringback after =
reception of a 180 (if</FONT>
<BR><FONT SIZE=3D2>&gt; during that second media is not =
received).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; In fact, this is what my mobile (GSM) does =
today. I dial a number, and</FONT>
<BR><FONT SIZE=3D2>&gt; when the terminal knows that the other user is =
being paged, it emits a</FONT>
<BR><FONT SIZE=3D2>&gt; beep (it also displays a message on the =
screen). Ringback (in </FONT>
<BR><FONT SIZE=3D2>&gt; this case</FONT>
<BR><FONT SIZE=3D2>&gt; remote ringback, but it really does not matter) =
starts a second or so</FONT>
<BR><FONT SIZE=3D2>&gt; later. Millions of users (me included) find =
this behaviour acceptable,</FONT>
<BR><FONT SIZE=3D2>&gt; so it would be acceptable as well for SIP-based =
systems.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; If the only useful scenario for a null =
Alert-Info is a race </FONT>
<BR><FONT SIZE=3D2>&gt; condition of</FONT>
<BR><FONT SIZE=3D2>&gt; this type, I agree that we should not adopt =
it.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;Peterson, Jon&quot; wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I don't think that the Alert-Info header =
proposal will </FONT>
<BR><FONT SIZE=3D2>&gt; really assuage the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; stated problem. Mr. Marshall raised a =
'null' Alert-Info </FONT>
<BR><FONT SIZE=3D2>&gt; proposal in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; previous discussion, and it was rejected =
then, as it should </FONT>
<BR><FONT SIZE=3D2>&gt; be now. Here's</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the thread:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www1.ietf.org/mail-archive/working-groups/sipping/curre" =
TARGET=3D"_blank">http://www1.ietf.org/mail-archive/working-groups/sippi=
ng/curre</A></FONT>
<BR><FONT SIZE=3D2>&gt; nt/msg02545.ht</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ml</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Null Alert-Info wouldn't express anything =
more than just </FONT>
<BR><FONT SIZE=3D2>&gt; sending a 183 does</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; - a UAS should send a 183 when it knows it =
has some </FONT>
<BR><FONT SIZE=3D2>&gt; non-ringing in-band</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; media. Null Alert-Info certainly wouldn't =
give you any </FONT>
<BR><FONT SIZE=3D2>&gt; additional leverage</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; in cases where media arrives before =
signaling. I'm not sure what new</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; properties it would grant. The text =
already suggests a policy of:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1.&nbsp;&nbsp; =
Unless a 180 (Ringing) response is received, </FONT>
<BR><FONT SIZE=3D2>&gt; never generate</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; local ringback.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ... which essentially entails 'don't play =
local ringback if 183 is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; received'. I'm not sure how it would be =
any better to </FONT>
<BR><FONT SIZE=3D2>&gt; recommend a similar</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (and redundant) policy relating to =
Alert-Info.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; As an aside, I do agree with Mr. Audet =
that we should </FONT>
<BR><FONT SIZE=3D2>&gt; discourage mixing</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; local ringback tones with received =
media.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Jon Peterson</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; NeuStar, Inc.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sent: Wednesday, March 05, 2003 10:22 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; To: Mark Watson</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Cc: 'Ejzak, Richard P (Richard)'; =
sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Subject: Re: [Sipping] New version of =
the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Mark,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; many of your points have been =
discussed either in the </FONT>
<BR><FONT SIZE=3D2>&gt; draft or in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; mailing list before. The MGC-MG =
decomposition problem is </FONT>
<BR><FONT SIZE=3D2>&gt; discussed in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the draft, and the indication of the =
presence in-band media was</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; discussed in the previous version of =
the draft.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; My initial proposal was to include an =
SDP parameter that provided</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; information about the intention of =
the sender. That is, the sender</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; intended to send early media... that =
was seen as too </FONT>
<BR><FONT SIZE=3D2>&gt; complex (and I</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; agree with that, by the way).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; But using some type of *simpler* =
mechanism that only</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; indicates that the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; UAS does not want the UAC to generate =
local ringback (like</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the mechanism</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; proposed in this thread), would be =
sensible, IMO.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; How do people feel about using the =
header field below in a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; 18x response</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; to indicate that the UAS would like =
the UAC not to provide local</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ringback (as proposed previously in =
this thread)?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Alert-Info: &lt;data:,&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; To me, once we have defined =
Alert-Info, this is not an </FONT>
<BR><FONT SIZE=3D2>&gt; unreasonable</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; thing to do with this header. =
Opinions?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Mark Watson wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; I would support this addition =
(or something like it - I</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; confess to not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; having followed all the details =
of this thread).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; This same problem has come up =
again and again over the last</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; two years.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; The root issue is a distinction =
between explicit </FONT>
<BR><FONT SIZE=3D2>&gt; application layer</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; indications and implicit media =
layer indications. If </FONT>
<BR><FONT SIZE=3D2>&gt; the UAC is a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; distributed system (e.g. Media =
Gateway and Media Gateway</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Controller),</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; then the general model is that =
the MG is controlled by </FONT>
<BR><FONT SIZE=3D2>&gt; the MGC. The</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; MGC has only explicit app. layer =
indications to work from -</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; it cannot</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; take actions on the basis of =
receipt of not of media </FONT>
<BR><FONT SIZE=3D2>&gt; packets because</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; it does not see them.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Sure, the MG can report and 'RTP =
received' event and the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; MGC can then</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; instruct it appropriately, but =
this takes time &amp; I </FONT>
<BR><FONT SIZE=3D2>&gt; don't think it's</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; standardised.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; So, there should be enough =
information *in the SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; signalling* for the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; UAC to take an intelligent =
decision on whether to play</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; media or local</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; ringing. I don't want to =
prescribe how it takes this</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; decision, but at</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; present there is information =
available to the UAS at </FONT>
<BR><FONT SIZE=3D2>&gt; the SIP layer</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; which is not communicated to the =
UAC (at the SIP layer) </FONT>
<BR><FONT SIZE=3D2>&gt; - namely the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; availability of in-band media. =
This can only result in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; UAC taking</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; inappropriate decisions in some =
scenarios.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Perhaps we should not be telling =
the UAC to 'play local </FONT>
<BR><FONT SIZE=3D2>&gt; ringing' or</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; 'don't play local ringing', but =
if the UAS knows there </FONT>
<BR><FONT SIZE=3D2>&gt; is in-band</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; information, it should tell the =
UAC in SIP.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Regards...Mark</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; From: Ejzak, Richard P =
(Richard) [<A =
HREF=3D"mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Sent: 04 March 2003 =
19:15</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; To: 'Gonzalo =
Camarillo'</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Cc: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Subject: RE: [Sipping] New =
version of the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Thanks for your =
response.&nbsp; I understand and agree with your</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; concerns about race =
conditions as well as the discussion of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; how to handle them.&nbsp; =
But I do not want the UAS to blindly</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; control when the UAC should =
apply local ringing.&nbsp; I want the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; UAS to be able to indicate =
when the UAC should NOT apply</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; local ringing.&nbsp; There =
is a very important distinction here.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; According to your draft, =
when a UAC receives a 180 it should</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; be prepared to generate =
local ringing, and it is a matter of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; local policy what the UAC =
should do when there is concurrent</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; in-band media.&nbsp; =
Gateway resources should be allocated to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; detect in-band media and =
decide whether or not to generate</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; ringing.&nbsp; But under =
some circumstances the UAS knows that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; call progress information =
is available in-band and the UAC</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; does not need to bother to =
allocate extra resources to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; monitor the media flow and =
optionally inject ringing.&nbsp; I</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; believe it is important for =
a UAS to be able to indicate this</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; situation to a UAC.&nbsp; =
These are processing !</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; resources that could be put =
to use elsewhere.&nbsp; There are no</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; race conditions in this =
situation - only the recognition that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; local ringing and packet =
detection are unnecessary.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; I stand by my original =
suggestion and continue to request a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; modest addition to your =
draft based on this general approach</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; (my previous email =
indicates one possible detailed solution).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;&nbsp; Please let me know if =
you see any further issues.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Regards,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Richard Ejzak</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Lucent Technologies</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; From: Gonzalo Camarillo =
</FONT>
<BR><FONT SIZE=3D2>&gt; [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Sent: Tuesday, March 04, =
2003 5:42 AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; To: Ejzak, Richard P =
(Richard)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Cc: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Subject: Re: [Sipping] New =
version of the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Ejzak,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; the main problem with any =
SIP-layer mechanism that allows</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the UAS to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; tell the UAC whether local =
ringback has to be </FONT>
<BR><FONT SIZE=3D2>&gt; generated or not is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; race</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; conditions. It really does =
not matter whether you use an</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Alert-Info</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; header field in a reponse, =
or a special status code, or a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; special body,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; or whatever to signal it. =
You always have race conditions.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Let's say that the UAS =
tells the UAC to generate local</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; ringback. After a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; while, the callee picks up. =
The UAS sends back a 200 </FONT>
<BR><FONT SIZE=3D2>&gt; OK and starts</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; sending media. The 200 OK, =
for some reason, arrives much</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; later than the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; first media packets... what =
is the UAC supposed to do in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; mean time?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Ignore the media? Play the =
media anyway?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Another scenario. The UAC =
starts receiving media before a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; provisional</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; response is received... =
what does it have to do?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; The main point is that, =
since signalling and media are loosely</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; synchronized, you will =
always have race conditions and you</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; will have to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; make guesses about what to =
do during those race </FONT>
<BR><FONT SIZE=3D2>&gt; conditions anyway.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &quot;Ejzak, Richard P =
(Richard)&quot; wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; It seems the single =
greatest difficulty with the gateway</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; model (as you point out in =
your draft) is the difficulty of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; depending on the arrival of =
media packets to determine</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; whether or not to generate =
local ringing.&nbsp; I have previously</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; (last summer) suggested a =
solution to this (use 180</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; exclusively to indicate =
that local ringing should override</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; any inband media and 183 =
otherwise) that is unacceptable</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; since it does not satisfy =
the requirement that 180 be used to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; indicate alerting of the =
called party.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Have you considered =
using the Alert-Info header in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; following way? Since the =
real problem is that we would like</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; to be able to discriminate =
between cases when 180 should</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; cause local ringing and =
when 180 should not (since inband</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; media is available), and it =
is the UAS that knows</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; conclusively which case =
applies, let's agree on an encoding</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; of the Alert-Info header =
that indicates that local ringing</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; should not be =
applied.&nbsp; The following line is a syntactically</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; valid header:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Alert-Info: =
&lt;data:,&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; This header identifies =
the Alert-Info as the null string,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; which seems unambiguously =
and efficiently interpretable</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; within a 180 response as =
&quot;do not play local ringing even</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; though the called party is =
being alerted.&quot;&nbsp; If the UAC does</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; not recognize it or chooses =
not to interpret it for security</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; reasons, it can be safely =
ignored.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; This modest addition =
to your draft (or an equivalent</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; mechanism) would make it =
unnecessary for the gateway model to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; depend on local policy or =
incoming media packet detection and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; is completely consistent =
with all of the constraints you have</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; documented.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Another approach may =
be to actually specify the rtp stream</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; as the source of the alert =
info (although this would require</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; the definition of a new URI =
scheme type).&nbsp; It might look like:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Alert-Info: =
&lt;rtp:/12.34.56.78:90&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; where the Alert-Info =
specifies the address and port of the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; rtp stream.&nbsp; I don't =
like this mechanism since it is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; redundant with SDP and =
prone to error.&nbsp; It is also ambiguous</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; in the event of any =
subsequent media change using UPDATE (Do</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; I begin to generate local =
ringing if the rtp stream source</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; address changes?&nbsp; Or =
do I continue to listen to the address</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; specified in the Alert-Info =
and ignore any UPDATEs?&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; No to both.)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; May I suggest =
including such a mechanism (preferably the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; first one) in your =
draft.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Richard Ejzak</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Lucent =
Technologies</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; From: Gonzalo =
Camarillo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Sent: Monday, February =
10, 2003 5:41 AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; To: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Subject: [Sipping] New =
version of the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; Folks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; I have just sumitted a =
new version of the early media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; draft. Until it</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; appears in the =
archives, you can fetch it from:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; <A =
HREF=3D"http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s" =
TARGET=3D"_blank">http://standards.ericsson.net/gonzalo/papers/draft-cam=
arillo-s</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ipping-early-media-01.txt</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; I have included all the =
(long and useful) discussions we</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; had in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; mailing list. Therefore, =
the draft now keeps separate the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &quot;gateway&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; the &quot;application =
server&quot; models. I have also removed </FONT>
<BR><FONT SIZE=3D2>&gt; the parts we</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; did</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; not agree on.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Feedback is, as usual, =
appreciated.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Sipping mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; This list is for NEW =
development of the application of SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Use =
sip-implementors@cs.columbia.edu for questions on </FONT>
<BR><FONT SIZE=3D2>&gt; current sip</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Use sip@ietf.org for new =
developments of core SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; =
Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Sipping mailing list&nbsp; =
</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; This list is for NEW development =
of the application of SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Use =
sip-implementors@cs.columbia.edu for questions on </FONT>
<BR><FONT SIZE=3D2>&gt; current sip</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Use sip@ietf.org for new =
developments of core SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sipping mailing list&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; This list is for NEW development of =
the application of SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Use sip-implementors@cs.columbia.edu =
for questions on current sip</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Use sip@ietf.org for new developments =
of core SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -- </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>&gt; Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>&gt; Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>&gt; FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT SIZE=3D2>&gt; =
Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E3F2.A4967FB4--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 04:22:57 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15630
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 04:22:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h279YMN01505
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 04:34:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279YMO01502
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 04:34:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15573
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 04:22:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279W9O01056;
	Fri, 7 Mar 2003 04:32:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26K8cO09528
	for <sipping@optimus.ietf.org>; Thu, 6 Mar 2003 15:08:38 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09023
	for <sipping@ietf.org>; Thu, 6 Mar 2003 14:56:50 -0500 (EST)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by auemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h26Jwsm29300
	for <sipping@ietf.org>; Thu, 6 Mar 2003 14:58:54 -0500 (EST)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2653.19)
	id <1H3RMQ6T>; Thu, 6 Mar 2003 13:58:53 -0600
Message-ID: <DBC3D7D0A071F743AE0767C9C6071EDA0482BBC4@il0015exch010u.ih.lucent.com>
From: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>,
        "Peterson, Jon"
	 <jon.peterson@neustar.biz>
Cc: sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Thu, 6 Mar 2003 13:58:50 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E41A.CE775F4C"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E41A.CE775F4C
Content-Type: text/plain;
	charset="iso-8859-1"

I must agree with Mark that this problem will not go away without an agreed-upon solution.  And while some system configurations may work with the mechanisms currently available, other configurations will have problems.  The earlier thread referenced by Jon discusses the near-term adequacy of the SIP-ISUP text while pointing out that a full early media solution is still needed.  It seemed that Jon was also suggesting that a gateway UAS could send 183 after it became aware of subscriber alerting to solve the problem (I agree it would), but I definitely heard objections to this.  It seems to me that Gonzalo's draft is the right place to address this problem.  We have now had proposals to include either 183 (instead of 180), SDP, Reason-Phrase or Alert-Info (and probably others) which have all raised objections.
 
I have another proposal which is a variation of one made last summer.  What about including a special token in the Reason-Phrase of the 180 (instead of the 183, as proposed last year)?  Instead of "SIP/2.0 180 Ringing" let it say "SIP/2.0 180 Ringing In-Band" or a similar message.  3261 allows any text for Reason-Phrase.  Let's establish the convention that a gateway UAS should use this encoding of the Reason-Phrase to indicate that in-band progress information is available, and that the UAC may use (but is not required to use) this information to make decisions related to processing of media.  This is a meaningful message that can be displayed to a human at a UAC user interface.  This convention does not in any way limit the use of the Reason-Phrase by other SIP entities.
 
Yet another less attractive solution is to define a new header.
 
Comments?  Alternative suggestions?
 
Regards,
Richard Ejzak
Lucent Technologies
 

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Thursday, March 06, 2003 9:11 AM
To: 'Gonzalo Camarillo'; Peterson, Jon
Cc: 'Ejzak, Richard P (Richard)'; sipping
Subject: RE: [Sipping] New version of the early media draft



Ok, so I have now read the draft (sorry 'bout that short delay there). It is very good, btw. 

The problem is related to 180 only, and specifically the scenario described by Gonzalo below. The draft does indeed include a good treatment of the problem for decomposed MG/MGC arhicitecture but the only solution suggested seems to be mixing local ringback with inband media. I tend to agree with Francois and Mr. Peterson, that this is not a good idea.

What is needed, to my mind, is an indication at the SIP layer that in-band media is/will be provided. This indication is there implicitly in a 183 (there is no other reason why you would send a 183), but not in 180.

I don't care whether it's Alert-Info or something else. Mr Peterson seemed to object to Alert-Info - do you have an alternative suggestion ?

This requirement has re-surfaced every six months for at least the past two years & my bet is that it will keep resurfacing until we address it.

Regards...Mark 

PS: Minor nit in the first para of 2.1.1 - two occurances of UAS in the last line should be UAC, I think. 

> -----Original Message----- 
> From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se <mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> Sent: 06 March 2003 13:46 
> To: Peterson, Jon 
> Cc: Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P 
> (Richard)'; sipping 
> Subject: Re: [Sipping] New version of the early media draft 
> 
> 
> Hi, 
> 
> well, I can see which scenario he is after, but I agree that the 
> solution would not bring much value. 
> 
> The scenario he is after is as follows; a gateway *knows* 
> that the user 
> is being alerted and also *knows* that it will be sending in-band 
> ringing. 
> 
> He is proposing a flag (i.e., null Altert-Info) for resolving that 
> situation. 
> 
> We have two situations: 
> 1) media packets arrive to the UAC before the 180. 
> 
> 2) the 180 arrives before the first media packets. 
> 
> Situation 1) is not a problem, since the UAC will (most 
> likely) not play 
> local ringback, since it is already receiving (and playing) media. 
> 
> A null Alert Info would be helpful in Situation 2), but only to avoid 
> that the UAC plays local ringback during the instants (it is a race 
> condition) between the arrival of the 180 until the arrival 
> of the first 
> media packets. A simpler solution would be to always wait for, say, a 
> second, before generating local ringback after reception of a 180 (if 
> during that second media is not received). 
> 
> In fact, this is what my mobile (GSM) does today. I dial a number, and 
> when the terminal knows that the other user is being paged, it emits a 
> beep (it also displays a message on the screen). Ringback (in 
> this case 
> remote ringback, but it really does not matter) starts a second or so 
> later. Millions of users (me included) find this behaviour acceptable, 
> so it would be acceptable as well for SIP-based systems. 
> 
> If the only useful scenario for a null Alert-Info is a race 
> condition of 
> this type, I agree that we should not adopt it. 
> 
> Gonzalo 
> 
> 
> 
> "Peterson, Jon" wrote: 
> > 
> > I don't think that the Alert-Info header proposal will 
> really assuage the 
> > stated problem. Mr. Marshall raised a 'null' Alert-Info 
> proposal in the 
> > previous discussion, and it was rejected then, as it should 
> be now. Here's 
> > the thread: 
> > 
> > 
> http://www1.ietf.org/mail-archive/working-groups/sipping/curre <http://www1.ietf.org/mail-archive/working-groups/sipping/curre>  
> nt/msg02545.ht 
> > ml 
> > 
> > Null Alert-Info wouldn't express anything more than just 
> sending a 183 does 
> > - a UAS should send a 183 when it knows it has some 
> non-ringing in-band 
> > media. Null Alert-Info certainly wouldn't give you any 
> additional leverage 
> > in cases where media arrives before signaling. I'm not sure what new 
> > properties it would grant. The text already suggests a policy of: 
> > 
> >         1.   Unless a 180 (Ringing) response is received, 
> never generate 
> >              local ringback. 
> > 
> > ... which essentially entails 'don't play local ringback if 183 is 
> > received'. I'm not sure how it would be any better to 
> recommend a similar 
> > (and redundant) policy relating to Alert-Info. 
> > 
> > As an aside, I do agree with Mr. Audet that we should 
> discourage mixing 
> > local ringback tones with received media. 
> > 
> > Jon Peterson 
> > NeuStar, Inc. 
> > 
> > > -----Original Message----- 
> > > From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se <mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > > Sent: Wednesday, March 05, 2003 10:22 AM 
> > > To: Mark Watson 
> > > Cc: 'Ejzak, Richard P (Richard)'; sipping 
> > > Subject: Re: [Sipping] New version of the early media draft 
> > > 
> > > 
> > > Mark, 
> > > 
> > > many of your points have been discussed either in the 
> draft or in the 
> > > mailing list before. The MGC-MG decomposition problem is 
> discussed in 
> > > the draft, and the indication of the presence in-band media was 
> > > discussed in the previous version of the draft. 
> > > 
> > > My initial proposal was to include an SDP parameter that provided 
> > > information about the intention of the sender. That is, the sender 
> > > intended to send early media... that was seen as too 
> complex (and I 
> > > agree with that, by the way). 
> > > 
> > > But using some type of *simpler* mechanism that only 
> > > indicates that the 
> > > UAS does not want the UAC to generate local ringback (like 
> > > the mechanism 
> > > proposed in this thread), would be sensible, IMO. 
> > > 
> > > How do people feel about using the header field below in a 
> > > 18x response 
> > > to indicate that the UAS would like the UAC not to provide local 
> > > ringback (as proposed previously in this thread)? 
> > > 
> > > Alert-Info: <data:,> 
> > > 
> > > To me, once we have defined Alert-Info, this is not an 
> unreasonable 
> > > thing to do with this header. Opinions? 
> > > 
> > > Gonzalo 
> > > 
> > > 
> > > Mark Watson wrote: 
> > > > 
> > > > Gonzalo, 
> > > > 
> > > > I would support this addition (or something like it - I 
> > > confess to not 
> > > > having followed all the details of this thread). 
> > > > 
> > > > This same problem has come up again and again over the last 
> > > two years. 
> > > > The root issue is a distinction between explicit 
> application layer 
> > > > indications and implicit media layer indications. If 
> the UAC is a 
> > > > distributed system (e.g. Media Gateway and Media Gateway 
> > > Controller), 
> > > > then the general model is that the MG is controlled by 
> the MGC. The 
> > > > MGC has only explicit app. layer indications to work from - 
> > > it cannot 
> > > > take actions on the basis of receipt of not of media 
> packets because 
> > > > it does not see them. 
> > > > 
> > > > Sure, the MG can report and 'RTP received' event and the 
> > > MGC can then 
> > > > instruct it appropriately, but this takes time & I 
> don't think it's 
> > > > standardised. 
> > > > 
> > > > So, there should be enough information *in the SIP 
> > > signalling* for the 
> > > > UAC to take an intelligent decision on whether to play 
> > > media or local 
> > > > ringing. I don't want to prescribe how it takes this 
> > > decision, but at 
> > > > present there is information available to the UAS at 
> the SIP layer 
> > > > which is not communicated to the UAC (at the SIP layer) 
> - namely the 
> > > > availability of in-band media. This can only result in the 
> > > UAC taking 
> > > > inappropriate decisions in some scenarios. 
> > > > 
> > > > Perhaps we should not be telling the UAC to 'play local 
> ringing' or 
> > > > 'don't play local ringing', but if the UAS knows there 
> is in-band 
> > > > information, it should tell the UAC in SIP. 
> > > > 
> > > > Regards...Mark 
> > > > 
> > > > > -----Original Message----- 
> > > > > From: Ejzak, Richard P (Richard) [ mailto:ejzak@lucent.com <mailto:ejzak@lucent.com> ] 
> > > > > Sent: 04 March 2003 19:15 
> > > > > To: 'Gonzalo Camarillo' 
> > > > > Cc: sipping 
> > > > > Subject: RE: [Sipping] New version of the early media draft 
> > > > > 
> > > > > 
> > > > > Gonzalo, 
> > > > > Thanks for your response.  I understand and agree with your 
> > > > > concerns about race conditions as well as the discussion of 
> > > > > how to handle them.  But I do not want the UAS to blindly 
> > > > > control when the UAC should apply local ringing.  I want the 
> > > > > UAS to be able to indicate when the UAC should NOT apply 
> > > > > local ringing.  There is a very important distinction here. 
> > > > > According to your draft, when a UAC receives a 180 it should 
> > > > > be prepared to generate local ringing, and it is a matter of 
> > > > > local policy what the UAC should do when there is concurrent 
> > > > > in-band media.  Gateway resources should be allocated to 
> > > > > detect in-band media and decide whether or not to generate 
> > > > > ringing.  But under some circumstances the UAS knows that 
> > > > > call progress information is available in-band and the UAC 
> > > > > does not need to bother to allocate extra resources to 
> > > > > monitor the media flow and optionally inject ringing.  I 
> > > > > believe it is important for a UAS to be able to indicate this 
> > > > > situation to a UAC.  These are processing ! 
> > > > > resources that could be put to use elsewhere.  There are no 
> > > > > race conditions in this situation - only the recognition that 
> > > > > local ringing and packet detection are unnecessary. 
> > > > > 
> > > > > I stand by my original suggestion and continue to request a 
> > > > > modest addition to your draft based on this general approach 
> > > > > (my previous email indicates one possible detailed solution). 
> > > > >  Please let me know if you see any further issues. 
> > > > > 
> > > > > Regards, 
> > > > > Richard Ejzak 
> > > > > Lucent Technologies 
> > > > > 
> > > > > 
> > > > > 
> > > > > -----Original Message----- 
> > > > > From: Gonzalo Camarillo 
> [ mailto:Gonzalo.Camarillo@lmf.ericsson.se <mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > > > > Sent: Tuesday, March 04, 2003 5:42 AM 
> > > > > To: Ejzak, Richard P (Richard) 
> > > > > Cc: sipping 
> > > > > Subject: Re: [Sipping] New version of the early media draft 
> > > > > 
> > > > > 
> > > > > Ejzak, 
> > > > > 
> > > > > the main problem with any SIP-layer mechanism that allows 
> > > the UAS to 
> > > > 
> > > > > tell the UAC whether local ringback has to be 
> generated or not is 
> > > > race 
> > > > > conditions. It really does not matter whether you use an 
> > > Alert-Info 
> > > > > header field in a reponse, or a special status code, or a 
> > > > > special body, 
> > > > > or whatever to signal it. You always have race conditions. 
> > > > > 
> > > > > Let's say that the UAS tells the UAC to generate local 
> > > > > ringback. After a 
> > > > > while, the callee picks up. The UAS sends back a 200 
> OK and starts 
> > > > > sending media. The 200 OK, for some reason, arrives much 
> > > > > later than the 
> > > > > first media packets... what is the UAC supposed to do in the 
> > > > > mean time? 
> > > > > Ignore the media? Play the media anyway? 
> > > > > 
> > > > > Another scenario. The UAC starts receiving media before a 
> > > > provisional 
> > > > > response is received... what does it have to do? 
> > > > > 
> > > > > The main point is that, since signalling and media are loosely 
> > > > > synchronized, you will always have race conditions and you 
> > > > > will have to 
> > > > > make guesses about what to do during those race 
> conditions anyway. 
> > > > > 
> > > > > Thanks, 
> > > > > 
> > > > > Gonzalo 
> > > > > 
> > > > > 
> > > > > 
> > > > > "Ejzak, Richard P (Richard)" wrote: 
> > > > > > 
> > > > > > Gonzalo, 
> > > > > > It seems the single greatest difficulty with the gateway 
> > > > > model (as you point out in your draft) is the difficulty of 
> > > > > depending on the arrival of media packets to determine 
> > > > > whether or not to generate local ringing.  I have previously 
> > > > > (last summer) suggested a solution to this (use 180 
> > > > > exclusively to indicate that local ringing should override 
> > > > > any inband media and 183 otherwise) that is unacceptable 
> > > > > since it does not satisfy the requirement that 180 be used to 
> > > > > indicate alerting of the called party. 
> > > > > > 
> > > > > > Have you considered using the Alert-Info header in the 
> > > > > following way? Since the real problem is that we would like 
> > > > > to be able to discriminate between cases when 180 should 
> > > > > cause local ringing and when 180 should not (since inband 
> > > > > media is available), and it is the UAS that knows 
> > > > > conclusively which case applies, let's agree on an encoding 
> > > > > of the Alert-Info header that indicates that local ringing 
> > > > > should not be applied.  The following line is a syntactically 
> > > > > valid header: 
> > > > > > 
> > > > > > Alert-Info: <data:,> 
> > > > > > 
> > > > > > This header identifies the Alert-Info as the null string, 
> > > > > which seems unambiguously and efficiently interpretable 
> > > > > within a 180 response as "do not play local ringing even 
> > > > > though the called party is being alerted."  If the UAC does 
> > > > > not recognize it or chooses not to interpret it for security 
> > > > > reasons, it can be safely ignored. 
> > > > > > 
> > > > > > This modest addition to your draft (or an equivalent 
> > > > > mechanism) would make it unnecessary for the gateway model to 
> > > > > depend on local policy or incoming media packet detection and 
> > > > > is completely consistent with all of the constraints you have 
> > > > > documented. 
> > > > > > 
> > > > > > Another approach may be to actually specify the rtp stream 
> > > > > as the source of the alert info (although this would require 
> > > > > the definition of a new URI scheme type).  It might look like: 
> > > > > > 
> > > > > > Alert-Info: <rtp:/12.34.56.78:90> 
> > > > > > 
> > > > > > where the Alert-Info specifies the address and port of the 
> > > > > rtp stream.  I don't like this mechanism since it is 
> > > > > redundant with SDP and prone to error.  It is also ambiguous 
> > > > > in the event of any subsequent media change using UPDATE (Do 
> > > > > I begin to generate local ringing if the rtp stream source 
> > > > > address changes?  Or do I continue to listen to the address 
> > > > > specified in the Alert-Info and ignore any UPDATEs?  
> No to both.) 
> > > > > > 
> > > > > > May I suggest including such a mechanism (preferably the 
> > > > > first one) in your draft. 
> > > > > > 
> > > > > > Richard Ejzak 
> > > > > > Lucent Technologies 
> > > > > > 
> > > > > > -----Original Message----- 
> > > > > > From: Gonzalo Camarillo 
> > > [ mailto:Gonzalo.Camarillo@lmf.ericsson.se <mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > > > 
> > > > > > Sent: Monday, February 10, 2003 5:41 AM 
> > > > > > To: sipping 
> > > > > > Subject: [Sipping] New version of the early media draft 
> > > > > > 
> > > > > > Folks, 
> > > > > > 
> > > > > > I have just sumitted a new version of the early media 
> > > > > draft. Until it 
> > > > > > appears in the archives, you can fetch it from: 
> > > > > > 
> > > > > > 
> > > > 
> > > http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s <http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s>  
> > > ipping-early-media-01.txt 
> > > > 
> > > > > 
> > > > > I have included all the (long and useful) discussions we 
> > > had in the 
> > > > > mailing list. Therefore, the draft now keeps separate the 
> > > "gateway" 
> > > > and 
> > > > > the "application server" models. I have also removed 
> the parts we 
> > > > did 
> > > > > not agree on. 
> > > > > 
> > > > > Feedback is, as usual, appreciated. 
> > > > > 
> > > > > Thanks, 
> > > > > 
> > > > > Gonzalo 
> > > > > _______________________________________________ 
> > > > > Sipping mailing list 
> > > https://www1.ietf.org/mailman/listinfo/sipping <https://www1.ietf.org/mailman/listinfo/sipping>  
> > > > 
> > > > > This list is for NEW development of the application of SIP 
> > > > > Use sip-implementors@cs.columbia.edu for questions on 
> current sip 
> > > > > Use sip@ietf.org for new developments of core SIP 
> > > > 
> > > > -- 
> > > > Gonzalo Camarillo         Phone :  +358  9 299 33 71 
> > > > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35 
> > > > Telecom R&D               Fax   :  +358  9 299 30 52 
> > > > FIN-02420 Jorvas          Email :  
> Gonzalo.Camarillo@ericsson.com 
> > > > Finland                   http://www.hut.fi/~gonzalo <http://www.hut.fi/~gonzalo>  
> > > > _______________________________________________ 
> > > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping <https://www1.ietf.org/mailman/listinfo/sipping>  
> > > > This list is for NEW development of the application of SIP 
> > > > Use sip-implementors@cs.columbia.edu for questions on 
> current sip 
> > > > Use sip@ietf.org for new developments of core SIP 
> > > 
> > > -- 
> > > Gonzalo Camarillo         Phone :  +358  9 299 33 71 
> > > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35 
> > > Telecom R&D               Fax   :  +358  9 299 30 52 
> > > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com 
> > > Finland                   http://www.hut.fi/~gonzalo <http://www.hut.fi/~gonzalo>  
> > > _______________________________________________ 
> > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping <https://www1.ietf.org/mailman/listinfo/sipping>  
> > > This list is for NEW development of the application of SIP 
> > > Use sip-implementors@cs.columbia.edu for questions on current sip 
> > > Use sip@ietf.org for new developments of core SIP 
> > > 
> 
> -- 
> Gonzalo Camarillo         Phone :  +358  9 299 33 71 
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35 
> Telecom R&D               Fax   :  +358  9 299 30 52 
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com 
> Finland                   http://www.hut.fi/~gonzalo <http://www.hut.fi/~gonzalo>  
> 


------_=_NextPart_001_01C2E41A.CE775F4C
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.50.4922.900" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=461161816-06032003>I must 
agree with Mark that this problem will not go away without an agreed-upon 
solution.&nbsp; And while some system configurations may work with the 
mechanisms currently available, other configurations will have problems.&nbsp; 
The earlier thread referenced by Jon discusses the near-term adequacy of the 
SIP-ISUP text while pointing out that a full early media solution is still 
needed.&nbsp; It seemed that Jon was also suggesting that a gateway UAS could 
send 183 after it became aware of subscriber alerting to solve the problem (I 
agree it would), but I definitely heard objections to this.&nbsp; It seems to me 
that Gonzalo's draft is the right place to address this problem.&nbsp; We have 
now had proposals to include either 183 (instead of 180), SDP, Reason-Phrase or 
Alert-Info (and probably others) which have all raised 
objections.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=461161816-06032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=461161816-06032003>I have 
another proposal which is a variation of one made last summer.&nbsp; What about 
including a special token in the Reason-Phrase of the 180 (instead of the 183, 
as proposed last year)?&nbsp; Instead of "SIP/2.0 180 Ringing" let it say 
"SIP/2.0 180 Ringing In-Band" or a similar message.&nbsp; 3261 allows any text 
for Reason-Phrase.&nbsp; Let's establish the convention that a gateway UAS 
should use this encoding of the Reason-Phrase to indicate that in-band progress 
information is available, and that the UAC may use (but is not required to use) 
this information to make decisions related to processing of media.&nbsp; This is 
a meaningful message that can be displayed to a human at a UAC user 
interface.&nbsp; This convention does not in any way limit the use of the 
Reason-Phrase by other SIP entities.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=461161816-06032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=461161816-06032003>Yet 
another less attractive solution is to define a new header.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=461161816-06032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=461161816-06032003>Comments?&nbsp; Alternative 
suggestions?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=461161816-06032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=461161816-06032003>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=461161816-06032003>Richard Ejzak</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=461161816-06032003>Lucent 
Technologies</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=461161816-06032003></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
  [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Thursday, March 06, 2003 
  9:11 AM<BR><B>To:</B> 'Gonzalo Camarillo'; Peterson, Jon<BR><B>Cc:</B> 'Ejzak, 
  Richard P (Richard)'; sipping<BR><B>Subject:</B> RE: [Sipping] New version of 
  the early media draft<BR><BR></FONT></DIV>
  <P><FONT size=2>Ok, so I have now read the draft (sorry 'bout that short delay 
  there). It is very good, btw.</FONT> </P>
  <P><FONT size=2>The problem is related to 180 only, and specifically the 
  scenario described by Gonzalo below. The draft does indeed include a good 
  treatment of the problem for decomposed MG/MGC arhicitecture but the only 
  solution suggested seems to be mixing local ringback with inband media. I tend 
  to agree with Francois and Mr. Peterson, that this is not a good 
  idea.</FONT></P>
  <P><FONT size=2>What is needed, to my mind, is an indication at the SIP layer 
  that in-band media is/will be provided. This indication is there implicitly in 
  a 183 (there is no other reason why you would send a 183), but not in 
  180.</FONT></P>
  <P><FONT size=2>I don't care whether it's Alert-Info or something else. Mr 
  Peterson seemed to object to Alert-Info - do you have an alternative 
  suggestion ?</FONT></P>
  <P><FONT size=2>This requirement has re-surfaced every six months for at least 
  the past two years &amp; my bet is that it will keep resurfacing until we 
  address it.</FONT></P>
  <P><FONT size=2>Regards...Mark</FONT> </P>
  <P><FONT size=2>PS: Minor nit in the first para of 2.1.1 - two occurances of 
  UAS in the last line should be UAC, I think.</FONT> </P>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: Gonzalo Camarillo [<A 
  href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
  <BR><FONT size=2>&gt; Sent: 06 March 2003 13:46</FONT> <BR><FONT size=2>&gt; 
  To: Peterson, Jon</FONT> <BR><FONT size=2>&gt; Cc: Watson, Mark 
  [MOP:EP10:EXCH]; 'Ejzak, Richard P </FONT><BR><FONT size=2>&gt; (Richard)'; 
  sipping</FONT> <BR><FONT size=2>&gt; Subject: Re: [Sipping] New version of the 
  early media draft</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; Hi,</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; well, I can see which scenario he is after, but I agree that 
  the</FONT> <BR><FONT size=2>&gt; solution would not bring much value.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; The scenario he is after is 
  as follows; a gateway *knows* </FONT><BR><FONT size=2>&gt; that the 
  user</FONT> <BR><FONT size=2>&gt; is being alerted and also *knows* that it 
  will be sending in-band</FONT> <BR><FONT size=2>&gt; ringing.</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; He is proposing a flag (i.e., null 
  Altert-Info) for resolving that</FONT> <BR><FONT size=2>&gt; situation.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; We have two 
  situations:</FONT> <BR><FONT size=2>&gt; 1) media packets arrive to the UAC 
  before the 180.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 2) 
  the 180 arrives before the first media packets.</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; Situation 1) is not a problem, since the UAC will 
  (most </FONT><BR><FONT size=2>&gt; likely) not play</FONT> <BR><FONT 
  size=2>&gt; local ringback, since it is already receiving (and playing) 
  media.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; A null Alert 
  Info would be helpful in Situation 2), but only to avoid</FONT> <BR><FONT 
  size=2>&gt; that the UAC plays local ringback during the instants (it is a 
  race</FONT> <BR><FONT size=2>&gt; condition) between the arrival of the 180 
  until the arrival </FONT><BR><FONT size=2>&gt; of the first</FONT> <BR><FONT 
  size=2>&gt; media packets. A simpler solution would be to always wait for, 
  say, a</FONT> <BR><FONT size=2>&gt; second, before generating local ringback 
  after reception of a 180 (if</FONT> <BR><FONT size=2>&gt; during that second 
  media is not received).</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; In fact, this is what my mobile (GSM) does today. I dial a number, 
  and</FONT> <BR><FONT size=2>&gt; when the terminal knows that the other user 
  is being paged, it emits a</FONT> <BR><FONT size=2>&gt; beep (it also displays 
  a message on the screen). Ringback (in </FONT><BR><FONT size=2>&gt; this 
  case</FONT> <BR><FONT size=2>&gt; remote ringback, but it really does not 
  matter) starts a second or so</FONT> <BR><FONT size=2>&gt; later. Millions of 
  users (me included) find this behaviour acceptable,</FONT> <BR><FONT 
  size=2>&gt; so it would be acceptable as well for SIP-based systems.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; If the only useful scenario 
  for a null Alert-Info is a race </FONT><BR><FONT size=2>&gt; condition 
  of</FONT> <BR><FONT size=2>&gt; this type, I agree that we should not adopt 
  it.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Gonzalo</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; "Peterson, Jon" wrote:</FONT> 
  <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; I don't think 
  that the Alert-Info header proposal will </FONT><BR><FONT size=2>&gt; really 
  assuage the</FONT> <BR><FONT size=2>&gt; &gt; stated problem. Mr. Marshall 
  raised a 'null' Alert-Info </FONT><BR><FONT size=2>&gt; proposal in the</FONT> 
  <BR><FONT size=2>&gt; &gt; previous discussion, and it was rejected then, as 
  it should </FONT><BR><FONT size=2>&gt; be now. Here's</FONT> <BR><FONT 
  size=2>&gt; &gt; the thread:</FONT> <BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; <A 
  target=_blank 
  href="http://www1.ietf.org/mail-archive/working-groups/sipping/curre">http://www1.ietf.org/mail-archive/working-groups/sipping/curre</A></FONT> 
  <BR><FONT size=2>&gt; nt/msg02545.ht</FONT> <BR><FONT size=2>&gt; &gt; 
  ml</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Null 
  Alert-Info wouldn't express anything more than just </FONT><BR><FONT 
  size=2>&gt; sending a 183 does</FONT> <BR><FONT size=2>&gt; &gt; - a UAS 
  should send a 183 when it knows it has some </FONT><BR><FONT size=2>&gt; 
  non-ringing in-band</FONT> <BR><FONT size=2>&gt; &gt; media. Null Alert-Info 
  certainly wouldn't give you any </FONT><BR><FONT size=2>&gt; additional 
  leverage</FONT> <BR><FONT size=2>&gt; &gt; in cases where media arrives before 
  signaling. I'm not sure what new</FONT> <BR><FONT size=2>&gt; &gt; properties 
  it would grant. The text already suggests a policy of:</FONT> <BR><FONT 
  size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1.&nbsp;&nbsp; Unless a 
  180 (Ringing) response is received, </FONT><BR><FONT size=2>&gt; never 
  generate</FONT> <BR><FONT size=2>&gt; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  local ringback.</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
  &gt; ... which essentially entails 'don't play local ringback if 183 is</FONT> 
  <BR><FONT size=2>&gt; &gt; received'. I'm not sure how it would be any better 
  to </FONT><BR><FONT size=2>&gt; recommend a similar</FONT> <BR><FONT 
  size=2>&gt; &gt; (and redundant) policy relating to Alert-Info.</FONT> 
  <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; As an aside, I do 
  agree with Mr. Audet that we should </FONT><BR><FONT size=2>&gt; discourage 
  mixing</FONT> <BR><FONT size=2>&gt; &gt; local ringback tones with received 
  media.</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Jon 
  Peterson</FONT> <BR><FONT size=2>&gt; &gt; NeuStar, Inc.</FONT> <BR><FONT 
  size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; &gt; -----Original 
  Message-----</FONT> <BR><FONT size=2>&gt; &gt; &gt; From: Gonzalo Camarillo 
  [<A 
  href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; Sent: Wednesday, March 05, 2003 10:22 
  AM</FONT> <BR><FONT size=2>&gt; &gt; &gt; To: Mark Watson</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; Cc: 'Ejzak, Richard P (Richard)'; sipping</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; Subject: Re: [Sipping] New version of the 
  early media draft</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; Mark,</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; many of 
  your points have been discussed either in the </FONT><BR><FONT size=2>&gt; 
  draft or in the</FONT> <BR><FONT size=2>&gt; &gt; &gt; mailing list before. 
  The MGC-MG decomposition problem is </FONT><BR><FONT size=2>&gt; discussed 
  in</FONT> <BR><FONT size=2>&gt; &gt; &gt; the draft, and the indication of the 
  presence in-band media was</FONT> <BR><FONT size=2>&gt; &gt; &gt; discussed in 
  the previous version of the draft.</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; My initial proposal was to include 
  an SDP parameter that provided</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  information about the intention of the sender. That is, the sender</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; intended to send early media... that was seen 
  as too </FONT><BR><FONT size=2>&gt; complex (and I</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; agree with that, by the way).</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; But using some 
  type of *simpler* mechanism that only</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  indicates that the</FONT> <BR><FONT size=2>&gt; &gt; &gt; UAS does not want 
  the UAC to generate local ringback (like</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; the mechanism</FONT> <BR><FONT size=2>&gt; &gt; &gt; proposed in this 
  thread), would be sensible, IMO.</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; How do people feel about using the header 
  field below in a</FONT> <BR><FONT size=2>&gt; &gt; &gt; 18x response</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; to indicate that the UAS would like the UAC 
  not to provide local</FONT> <BR><FONT size=2>&gt; &gt; &gt; ringback (as 
  proposed previously in this thread)?</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; Alert-Info: &lt;data:,&gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; To me, 
  once we have defined Alert-Info, this is not an </FONT><BR><FONT size=2>&gt; 
  unreasonable</FONT> <BR><FONT size=2>&gt; &gt; &gt; thing to do with this 
  header. Opinions?</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; Gonzalo</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; Mark 
  Watson wrote:</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; Gonzalo,</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; I would support this addition 
  (or something like it - I</FONT> <BR><FONT size=2>&gt; &gt; &gt; confess to 
  not</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; having followed all the 
  details of this thread).</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; This same problem has come up again and 
  again over the last</FONT> <BR><FONT size=2>&gt; &gt; &gt; two years.</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; The root issue is a distinction between 
  explicit </FONT><BR><FONT size=2>&gt; application layer</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; indications and implicit media layer indications. 
  If </FONT><BR><FONT size=2>&gt; the UAC is a</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; distributed system (e.g. Media Gateway and Media Gateway</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; Controller),</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; then the general model is that the MG is controlled by 
  </FONT><BR><FONT size=2>&gt; the MGC. The</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; MGC has only explicit app. layer indications to work from -</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; it cannot</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; take actions on the basis of receipt of not of media 
  </FONT><BR><FONT size=2>&gt; packets because</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; it does not see them.</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; Sure, the MG can report and 
  'RTP received' event and the</FONT> <BR><FONT size=2>&gt; &gt; &gt; MGC can 
  then</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; instruct it appropriately, 
  but this takes time &amp; I </FONT><BR><FONT size=2>&gt; don't think 
  it's</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; standardised.</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; So, there should be enough information *in the SIP</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; signalling* for the</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; UAC to take an intelligent decision on whether to play</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; media or local</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; ringing. I don't want to prescribe how it takes this</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; decision, but at</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; present there is information available to the UAS at 
  </FONT><BR><FONT size=2>&gt; the SIP layer</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; which is not communicated to the UAC (at the SIP layer) 
  </FONT><BR><FONT size=2>&gt; - namely the</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; availability of in-band media. This can only result in the</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; UAC taking</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; inappropriate decisions in some scenarios.</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; Perhaps 
  we should not be telling the UAC to 'play local </FONT><BR><FONT size=2>&gt; 
  ringing' or</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 'don't play local 
  ringing', but if the UAS knows there </FONT><BR><FONT size=2>&gt; is 
  in-band</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; information, it should 
  tell the UAC in SIP.</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; Regards...Mark</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  -----Original Message-----</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  From: Ejzak, Richard P (Richard) [<A 
  href="mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; Sent: 04 March 2003 19:15</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; To: 'Gonzalo Camarillo'</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; Cc: sipping</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; &gt; Subject: RE: [Sipping] New version of the early media 
  draft</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt; Gonzalo,</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; Thanks for your 
  response.&nbsp; I understand and agree with your</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; &gt; concerns about race conditions as well as the discussion 
  of</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; how to handle them.&nbsp; 
  But I do not want the UAS to blindly</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt; control when the UAC should apply local ringing.&nbsp; I want 
  the</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; UAS to be able to 
  indicate when the UAC should NOT apply</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt; local ringing.&nbsp; There is a very important distinction 
  here.</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; According to your 
  draft, when a UAC receives a 180 it should</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; &gt; be prepared to generate local ringing, and it is a matter 
  of</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; local policy what the UAC 
  should do when there is concurrent</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt; in-band media.&nbsp; Gateway resources should be allocated to</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; detect in-band media and decide 
  whether or not to generate</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  ringing.&nbsp; But under some circumstances the UAS knows that</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; call progress information is 
  available in-band and the UAC</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  does not need to bother to allocate extra resources to</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; monitor the media flow and optionally inject 
  ringing.&nbsp; I</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; believe it 
  is important for a UAS to be able to indicate this</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; situation to a UAC.&nbsp; These are processing 
  !</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; resources that could be put 
  to use elsewhere.&nbsp; There are no</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt; race conditions in this situation - only the recognition that</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; local ringing and packet detection 
  are unnecessary.</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; I stand by my original suggestion 
  and continue to request a</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  modest addition to your draft based on this general approach</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; (my previous email indicates one possible 
  detailed solution).</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;&nbsp; 
  Please let me know if you see any further issues.</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  Regards,</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; Richard Ejzak</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; Lucent Technologies</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; -----Original Message-----</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; From: Gonzalo Camarillo </FONT><BR><FONT 
  size=2>&gt; [<A 
  href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; Sent: Tuesday, March 04, 2003 5:42 
  AM</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; To: Ejzak, Richard P 
  (Richard)</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; Cc: sipping</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; Subject: Re: [Sipping] New version 
  of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; Ejzak,</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; the main problem 
  with any SIP-layer mechanism that allows</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; the UAS to</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; tell the UAC whether local ringback has to be 
  </FONT><BR><FONT size=2>&gt; generated or not is</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; race</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  conditions. It really does not matter whether you use an</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; Alert-Info</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt; header field in a reponse, or a special status code, or a</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; special body,</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; or whatever to signal it. You always have race 
  conditions.</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; Let's say that the UAS tells the UAC to 
  generate local</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; ringback. 
  After a</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; while, the callee 
  picks up. The UAS sends back a 200 </FONT><BR><FONT size=2>&gt; OK and 
  starts</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; sending media. The 200 
  OK, for some reason, arrives much</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt; later than the</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; first 
  media packets... what is the UAC supposed to do in the</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; mean time?</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; &gt; Ignore the media? Play the media anyway?</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt; Another scenario. The UAC starts receiving media before a</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; provisional</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; &gt; response is received... what does it have to do?</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; &gt; The main point is that, since signalling and media are 
  loosely</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; synchronized, you 
  will always have race conditions and you</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; &gt; will have to</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  make guesses about what to do during those race </FONT><BR><FONT size=2>&gt; 
  conditions anyway.</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; Thanks,</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  Gonzalo</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; "Ejzak, Richard P 
  (Richard)" wrote:</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt; Gonzalo,</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; &gt; It seems the single greatest difficulty 
  with the gateway</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; model (as 
  you point out in your draft) is the difficulty of</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; &gt; depending on the arrival of media packets to 
  determine</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; whether or not to 
  generate local ringing.&nbsp; I have previously</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; &gt; (last summer) suggested a solution to this (use 180</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; exclusively to indicate that local 
  ringing should override</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; any 
  inband media and 183 otherwise) that is unacceptable</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; since it does not satisfy the requirement that 
  180 be used to</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; indicate 
  alerting of the called party.</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt; Have you considered 
  using the Alert-Info header in the</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt; following way? Since the real problem is that we would like</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; to be able to discriminate between 
  cases when 180 should</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; cause 
  local ringing and when 180 should not (since inband</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; media is available), and it is the UAS that 
  knows</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; conclusively which case 
  applies, let's agree on an encoding</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt; of the Alert-Info header that indicates that local ringing</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; should not be applied.&nbsp; The 
  following line is a syntactically</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt; valid header:</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt; Alert-Info: 
  &lt;data:,&gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt; This header identifies the 
  Alert-Info as the null string,</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt; which seems unambiguously and efficiently interpretable</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; within a 180 response as "do not play local 
  ringing even</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; though the 
  called party is being alerted."&nbsp; If the UAC does</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; not recognize it or chooses not to interpret 
  it for security</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; reasons, it 
  can be safely ignored.</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt; This modest 
  addition to your draft (or an equivalent</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; &gt; mechanism) would make it unnecessary for the gateway model 
  to</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; depend on local policy or 
  incoming media packet detection and</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt; is completely consistent with all of the constraints you have</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; documented.</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt; &gt; Another approach may be to actually specify the rtp 
  stream</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; as the source of the 
  alert info (although this would require</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt; the definition of a new URI scheme type).&nbsp; It might look 
  like:</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; &gt; Alert-Info: 
  &lt;rtp:/12.34.56.78:90&gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt; where the 
  Alert-Info specifies the address and port of the</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; &gt; rtp stream.&nbsp; I don't like this mechanism since it 
  is</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; redundant with SDP and 
  prone to error.&nbsp; It is also ambiguous</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; &gt; in the event of any subsequent media change using UPDATE 
  (Do</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; I begin to generate local 
  ringing if the rtp stream source</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt; address changes?&nbsp; Or do I continue to listen to the address</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; specified in the Alert-Info and 
  ignore any UPDATEs?&nbsp; </FONT><BR><FONT size=2>&gt; No to both.)</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; &gt; &gt; May I suggest including such a mechanism (preferably 
  the</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; first one) in your 
  draft.</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; &gt; Richard Ejzak</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; &gt; Lucent Technologies</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt; &gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; &gt; &gt; From: Gonzalo Camarillo</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; [<A 
  href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt; &gt; Sent: Monday, February 10, 2003 5:41 AM</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; &gt; To: sipping</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; &gt; &gt; Subject: [Sipping] New version of the early media 
  draft</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; &gt; Folks,</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt; I 
  have just sumitted a new version of the early media</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; draft. Until it</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; &gt; &gt; appears in the archives, you can fetch it 
  from:</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; <A target=_blank 
  href="http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s">http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s</A></FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; ipping-early-media-01.txt</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; I have included all the 
  (long and useful) discussions we</FONT> <BR><FONT size=2>&gt; &gt; &gt; had in 
  the</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; mailing list. Therefore, 
  the draft now keeps separate the</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  "gateway"</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; and</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; the "application server" models. I have also 
  removed </FONT><BR><FONT size=2>&gt; the parts we</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; did</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; not agree 
  on.</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; Feedback is, as usual, appreciated.</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; &gt; Thanks,</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; Gonzalo</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; &gt; _______________________________________________</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; Sipping mailing list</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; <A target=_blank 
  href="https://www1.ietf.org/mailman/listinfo/sipping">https://www1.ietf.org/mailman/listinfo/sipping</A></FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt; This list is for NEW development of the application of SIP</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; Use sip-implementors@cs.columbia.edu 
  for questions on </FONT><BR><FONT size=2>&gt; current sip</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; &gt; Use sip@ietf.org for new developments of core 
  SIP</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; --</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; Gonzalo 
  Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; 
  +358&nbsp; 9 299 33 71</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; Oy L M 
  Ericsson Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 
  702 35 35</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; Telecom 
  R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 52</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; FIN-02420 
  Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email :&nbsp; 
  </FONT><BR><FONT size=2>&gt; Gonzalo.Camarillo@ericsson.com</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; &gt; 
  Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  <A target=_blank 
  href="http://www.hut.fi/~gonzalo">http://www.hut.fi/~gonzalo</A></FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  _______________________________________________</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; &gt; Sipping mailing list&nbsp; </FONT><BR><FONT size=2>&gt; <A 
  target=_blank 
  href="https://www1.ietf.org/mailman/listinfo/sipping">https://www1.ietf.org/mailman/listinfo/sipping</A></FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; &gt; This list is for NEW development of the 
  application of SIP</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; Use 
  sip-implementors@cs.columbia.edu for questions on </FONT><BR><FONT size=2>&gt; 
  current sip</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; Use sip@ietf.org for 
  new developments of core SIP</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; --</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  Gonzalo Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone 
  :&nbsp; +358&nbsp; 9 299 33 71</FONT> <BR><FONT size=2>&gt; &gt; &gt; Oy L M 
  Ericsson Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 
  702 35 35</FONT> <BR><FONT size=2>&gt; &gt; &gt; Telecom 
  R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 52</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; FIN-02420 
  Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email :&nbsp; 
  Gonzalo.Camarillo@ericsson.com</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  <A target=_blank 
  href="http://www.hut.fi/~gonzalo">http://www.hut.fi/~gonzalo</A></FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; 
  _______________________________________________</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; Sipping mailing list&nbsp; </FONT><BR><FONT size=2>&gt; <A 
  target=_blank 
  href="https://www1.ietf.org/mailman/listinfo/sipping">https://www1.ietf.org/mailman/listinfo/sipping</A></FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; This list is for NEW development of the 
  application of SIP</FONT> <BR><FONT size=2>&gt; &gt; &gt; Use 
  sip-implementors@cs.columbia.edu for questions on current sip</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; Use sip@ietf.org for new developments of core SIP</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; -- </FONT><BR><FONT size=2>&gt; Gonzalo 
  Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; 
  +358&nbsp; 9 299 33 71</FONT> <BR><FONT size=2>&gt; Oy L M Ericsson 
  Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 35 
  35</FONT> <BR><FONT size=2>&gt; Telecom 
  R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 52</FONT> <BR><FONT size=2>&gt; 
  FIN-02420 Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email 
  :&nbsp; Gonzalo.Camarillo@ericsson.com</FONT> <BR><FONT size=2>&gt; 
  Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  <A target=_blank 
  href="http://www.hut.fi/~gonzalo">http://www.hut.fi/~gonzalo</A></FONT> 
  <BR><FONT size=2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E41A.CE775F4C--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 04:23:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15643
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 04:23:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h279YQS01523
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 04:34:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279YQO01519
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 04:34:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15590
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 04:22:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279TRO00826;
	Fri, 7 Mar 2003 04:29:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279SUO00753
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 04:28:30 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15428
	for <sipping@ietf.org>; Fri, 7 Mar 2003 04:16:32 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h279IW402031;
	Fri, 7 Mar 2003 04:18:33 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (europem01.nt.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h279ITL17083;
	Fri, 7 Mar 2003 09:18:30 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id G3M621XA; Fri, 7 Mar 2003 09:18:30 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FS3957G9>; Fri, 7 Mar 2003 09:17:26 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C49@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 7 Mar 2003 09:17:24 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E48A.5D4E3442"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E48A.5D4E3442
Content-Type: text/plain;
	charset="iso-8859-1"

Jon,

You have missed one very important point which is that in-band media during
alerting is not necessarily 'just ringtone'. It is quite common for the call
to be in the 'Alerting' state (and for this to be know to a SIP to ISUP
gateway), but for the in-band media to contain some useful information other
than 'just ringtone'.

For example, in the UK at least, if the called party has Call Waiting, then
the call of course goes straight in to the Alerting state, but the caller
will here a message along the lines 'Please wait while we try to connect
your call - the person you are calling knows you are waiting'.

A second example would be when the call terminates on a queueing system, and
the message played gives the caller some idea of how long they will need to
wait.

I absolutely agree that if the in-band media was 'just ringtone' there would
be no point. In particular I don't see any need to support the PSTN
'feeture' in which you always hear the ringtone of the destination country
(IMO this is a bug, not a feature!).

So, let's recognise that there are cases where *both* out-of-band and
in-band status indications are present. My view is that out-of-band
indications should always be propogated if available - so for the scenario
in question we MUST use 180, not 183. Now we need to indicate that in-band
status is also available - is this really so hard ????

...Mark

> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> Sent: 07 March 2003 00:09
> To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo'
> Cc: Watson, Mark [MOP:EP10:EXCH]; sipping
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> 
> Everything below is familiar ground, and I don't want to 
> start rehearsing
> these same arguments again. SIP has made a number of design 
> decisions that
> predispose it towards out-of-band status information. Sending 
> in-band status
> information in SIP is harmful - period. In-band media should 
> be sent only
> when the gateway does not know the status of the call, and thus cannot
> communicate it out-of-band. Below, you basically argue that 
> in cases where
> the gateway does not know the status of the call, it has to send early
> media. I agree. I said that in cases in which the gateway 
> knows that the
> early media is just ringtone, it should send 180. Clearly, if 
> there's some
> in-band transition in call state from ringtone to some other 
> audible call
> progress information, and the gateway isn't made aware of it, then the
> gateway doesn't know the state of the call. Perhaps we might draw the
> conclusion from your example that out-of-band call status 
> indicators are
> inherently unreliable, then - and surmise that it is 
> impossible for the
> gateway to know the state of the call. Or perhaps the 
> likelihood of this
> condition arising is sufficiently remote, the consequences of 
> sending early
> media sufficiently troublesome, that we might decide the 
> in-band information
> in these cases is not 'essential' enough to worry over. But I 
> firmly believe
> we should leave this to the conscience of the individual gateway
> implementer. I don't think the early media draft needs to draw that
> conclusion.
> 
> Mr. Camarillo's draft already maintains a very delicate 
> balance of behavior
> to accommodate SIP's needs, and I haven't heard anything in 
> this yet that
> should alter it.
> 
> Jon Peterson
> NeuStar, Inc.
> 
> > -----Original Message-----
> > From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com]
> > Sent: Thursday, March 06, 2003 2:40 PM
> > To: 'Peterson, Jon'; 'Gonzalo Camarillo'
> > Cc: Mark Watson; sipping
> > Subject: RE: [Sipping] New version of the early media draft
> > 
> > 
> > Jon,
> > I must disagree with your blanket recommendation that the 
> > gateway not sent in-band ringing media.  This may be possible 
> > in some cases - and nothing we have suggested would prevent a 
> > gateway from using out-of-band indications.  But ringing is 
> > not the only in-band call progress information you may 
> > receive while trying to establish a call from SIP to ISUP.  
> > The transition from alerting to other forms of in-band call 
> > progress information is not guaranteed to be clearly signaled 
> > by ISUP within an ACM or CPG (since every switch in the 
> > network can safely assume in-band call progress after a 
> > certain point in the call), and it is essential that this 
> > subsequent information (when it exists) be presented to the 
> > UAC/user.  And the notion of having the gateway intelligently 
> > filter what it thinks is ringing and detect a transition to 
> > other forms of call progress is not acceptable.
> > 
> > Regards,
> > Richard Ejzak
> > Lucent Technologies
> > 
> > 
> > 
> > -----Original Message-----
> > From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > Sent: Thursday, March 06, 2003 4:06 PM
> > To: 'Gonzalo Camarillo'
> > Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping
> > Subject: RE: [Sipping] New version of the early media draft
> > 
> > 
> > 
> > Well,
> > 
> > > -----Original Message-----
> > > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > [snip]
> > > 
> > > The scenario he is after is as follows; a gateway *knows* 
> > that the user
> > > is being alerted and also *knows* that it will be sending in-band
> > > ringing.
> > > 
> > 
> > If the gateway knows that it will be sending in-band ringing, 
> > my position is
> > that the gateway shouldn't be sending that media. It's just 
> > ring tone. The
> > UAC can generate that itself. Let's not waste the bandwidth 
> > sending ringing,
> > especially in forking cases, especially because the UAC 
> might not even
> > render this provisional media (if it's a PC UAC, for example).
> > 
> > If media arrives at the UAC, it should override local 
> > ringtone, agreed. And
> > I have no problem with the idea that a UAC would delay local 
> > ringtone for a
> > short interval in order to see if any media is coming, even 
> > when 180 is
> > received. But we should not encourage gateways to send 
> ringing media.
> > 
> > Jon Peterson
> > NeuStar, Inc. 
> > 
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Jon,</FONT>
</P>

<P><FONT SIZE=3D2>You have missed one very important point which is =
that in-band media during alerting is not necessarily 'just ringtone'. =
It is quite common for the call to be in the 'Alerting' state (and for =
this to be know to a SIP to ISUP gateway), but for the in-band media to =
contain some useful information other than 'just ringtone'.</FONT></P>

<P><FONT SIZE=3D2>For example, in the UK at least, if the called party =
has Call Waiting, then the call of course goes straight in to the =
Alerting state, but the caller will here a message along the lines =
'Please wait while we try to connect your call - the person you are =
calling knows you are waiting'.</FONT></P>

<P><FONT SIZE=3D2>A second example would be when the call terminates on =
a queueing system, and the message played gives the caller some idea of =
how long they will need to wait.</FONT></P>

<P><FONT SIZE=3D2>I absolutely agree that if the in-band media was =
'just ringtone' there would be no point. In particular I don't see any =
need to support the PSTN 'feeture' in which you always hear the =
ringtone of the destination country (IMO this is a bug, not a =
feature!).</FONT></P>

<P><FONT SIZE=3D2>So, let's recognise that there are cases where *both* =
out-of-band and in-band status indications are present. My view is that =
out-of-band indications should always be propogated if available - so =
for the scenario in question we MUST use 180, not 183. Now we need to =
indicate that in-band status is also available - is this really so hard =
????</FONT></P>

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

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Peterson, Jon [<A =
HREF=3D"mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz=
</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 07 March 2003 00:09</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Ejzak, Richard P (Richard)'; Peterson, =
Jon; 'Gonzalo Camarillo'</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Watson, Mark [MOP:EP10:EXCH]; =
sipping</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Everything below is familiar ground, and I =
don't want to </FONT>
<BR><FONT SIZE=3D2>&gt; start rehearsing</FONT>
<BR><FONT SIZE=3D2>&gt; these same arguments again. SIP has made a =
number of design </FONT>
<BR><FONT SIZE=3D2>&gt; decisions that</FONT>
<BR><FONT SIZE=3D2>&gt; predispose it towards out-of-band status =
information. Sending </FONT>
<BR><FONT SIZE=3D2>&gt; in-band status</FONT>
<BR><FONT SIZE=3D2>&gt; information in SIP is harmful - period. In-band =
media should </FONT>
<BR><FONT SIZE=3D2>&gt; be sent only</FONT>
<BR><FONT SIZE=3D2>&gt; when the gateway does not know the status of =
the call, and thus cannot</FONT>
<BR><FONT SIZE=3D2>&gt; communicate it out-of-band. Below, you =
basically argue that </FONT>
<BR><FONT SIZE=3D2>&gt; in cases where</FONT>
<BR><FONT SIZE=3D2>&gt; the gateway does not know the status of the =
call, it has to send early</FONT>
<BR><FONT SIZE=3D2>&gt; media. I agree. I said that in cases in which =
the gateway </FONT>
<BR><FONT SIZE=3D2>&gt; knows that the</FONT>
<BR><FONT SIZE=3D2>&gt; early media is just ringtone, it should send =
180. Clearly, if </FONT>
<BR><FONT SIZE=3D2>&gt; there's some</FONT>
<BR><FONT SIZE=3D2>&gt; in-band transition in call state from ringtone =
to some other </FONT>
<BR><FONT SIZE=3D2>&gt; audible call</FONT>
<BR><FONT SIZE=3D2>&gt; progress information, and the gateway isn't =
made aware of it, then the</FONT>
<BR><FONT SIZE=3D2>&gt; gateway doesn't know the state of the call. =
Perhaps we might draw the</FONT>
<BR><FONT SIZE=3D2>&gt; conclusion from your example that out-of-band =
call status </FONT>
<BR><FONT SIZE=3D2>&gt; indicators are</FONT>
<BR><FONT SIZE=3D2>&gt; inherently unreliable, then - and surmise that =
it is </FONT>
<BR><FONT SIZE=3D2>&gt; impossible for the</FONT>
<BR><FONT SIZE=3D2>&gt; gateway to know the state of the call. Or =
perhaps the </FONT>
<BR><FONT SIZE=3D2>&gt; likelihood of this</FONT>
<BR><FONT SIZE=3D2>&gt; condition arising is sufficiently remote, the =
consequences of </FONT>
<BR><FONT SIZE=3D2>&gt; sending early</FONT>
<BR><FONT SIZE=3D2>&gt; media sufficiently troublesome, that we might =
decide the </FONT>
<BR><FONT SIZE=3D2>&gt; in-band information</FONT>
<BR><FONT SIZE=3D2>&gt; in these cases is not 'essential' enough to =
worry over. But I </FONT>
<BR><FONT SIZE=3D2>&gt; firmly believe</FONT>
<BR><FONT SIZE=3D2>&gt; we should leave this to the conscience of the =
individual gateway</FONT>
<BR><FONT SIZE=3D2>&gt; implementer. I don't think the early media =
draft needs to draw that</FONT>
<BR><FONT SIZE=3D2>&gt; conclusion.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mr. Camarillo's draft already maintains a very =
delicate </FONT>
<BR><FONT SIZE=3D2>&gt; balance of behavior</FONT>
<BR><FONT SIZE=3D2>&gt; to accommodate SIP's needs, and I haven't heard =
anything in </FONT>
<BR><FONT SIZE=3D2>&gt; this yet that</FONT>
<BR><FONT SIZE=3D2>&gt; should alter it.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Jon Peterson</FONT>
<BR><FONT SIZE=3D2>&gt; NeuStar, Inc.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Ejzak, Richard P (Richard) [<A =
HREF=3D"mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Thursday, March 06, 2003 2:40 =
PM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: 'Peterson, Jon'; 'Gonzalo =
Camarillo'</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cc: Mark Watson; sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: RE: [Sipping] New version of the =
early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Jon,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I must disagree with your blanket =
recommendation that the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; gateway not sent in-band ringing =
media.&nbsp; This may be possible </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; in some cases - and nothing we have =
suggested would prevent a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; gateway from using out-of-band =
indications.&nbsp; But ringing is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; not the only in-band call progress =
information you may </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; receive while trying to establish a call =
from SIP to ISUP.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The transition from alerting to other =
forms of in-band call </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; progress information is not guaranteed to =
be clearly signaled </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; by ISUP within an ACM or CPG (since every =
switch in the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; network can safely assume in-band call =
progress after a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; certain point in the call), and it is =
essential that this </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; subsequent information (when it exists) be =
presented to the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; UAC/user.&nbsp; And the notion of having =
the gateway intelligently </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; filter what it thinks is ringing and =
detect a transition to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; other forms of call progress is not =
acceptable.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Regards,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Richard Ejzak</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Lucent Technologies</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Peterson, Jon [<A =
HREF=3D"mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz=
</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Thursday, March 06, 2003 4:06 =
PM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: 'Gonzalo Camarillo'</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cc: Mark Watson; 'Ejzak, Richard P =
(Richard)'; sipping</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: RE: [Sipping] New version of the =
early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Well,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; [snip]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The scenario he is after is as =
follows; a gateway *knows* </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that the user</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; is being alerted and also *knows* =
that it will be sending in-band</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ringing.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; If the gateway knows that it will be =
sending in-band ringing, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; my position is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that the gateway shouldn't be sending that =
media. It's just </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ring tone. The</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; UAC can generate that itself. Let's not =
waste the bandwidth </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; sending ringing,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; especially in forking cases, especially =
because the UAC </FONT>
<BR><FONT SIZE=3D2>&gt; might not even</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; render this provisional media (if it's a =
PC UAC, for example).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; If media arrives at the UAC, it should =
override local </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ringtone, agreed. And</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I have no problem with the idea that a UAC =
would delay local </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ringtone for a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; short interval in order to see if any =
media is coming, even </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; when 180 is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; received. But we should not encourage =
gateways to send </FONT>
<BR><FONT SIZE=3D2>&gt; ringing media.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Jon Peterson</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; NeuStar, Inc. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E48A.5D4E3442--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 04:29:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15976
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 04:29:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h279f6f02988
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 04:41:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279f6O02985
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 04:41:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15958
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 04:29:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279e5O02863;
	Fri, 7 Mar 2003 04:40:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279d9O02726
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 04:39:09 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15805
	for <sipping@ietf.org>; Fri, 7 Mar 2003 04:27:12 -0500 (EST)
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h279TFB3015156
	for <sipping@ietf.org>; Fri, 7 Mar 2003 10:29:15 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id FDVMYFG4; Fri, 7 Mar 2003 10:29:15 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h279TBlW003842
	for <sipping@ietf.org>; Fri, 7 Mar 2003 11:29:11 +0200 (EET)
Message-ID: <3E686666.BAA9CC48@lmf.ericsson.se>
Date: Fri, 07 Mar 2003 11:29:10 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Administrative: message length
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

any message longer than 40 KB has to be authorized by me before the
mailins list distributes it. Try to keep your quotes short.

Thanks,

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 04:30:43 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16019
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 04:30:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h279g7D03044
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 04:42:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279g7O03041
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 04:42:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16003
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 04:30:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279cJO02629;
	Fri, 7 Mar 2003 04:38:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h279b1O01733
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 04:37:01 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15708
	for <sipping@ietf.org>; Fri, 7 Mar 2003 04:25:04 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h279R7B3014551;
	Fri, 7 Mar 2003 10:27:07 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5X2F2MC; Fri, 7 Mar 2003 10:27:06 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h279R6lW003764;
	Fri, 7 Mar 2003 11:27:06 +0200 (EET)
Message-ID: <3E6865E9.C17EE6CD@lmf.ericsson.se>
Date: Fri, 07 Mar 2003 11:27:05 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Watson <mwatson@nortelnetworks.com>
CC: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>, Francois Audet <audet@nortelnetworks.com>
Subject: Re: [Sipping] New version of the early media draft
References: <A3C2399B2FACD411A54200508BE39C74054F7C4A@zwcwd00r.europe.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mark,

the text says that such a flag would not solve that issue, because you
have to implement media detection *anyway* for covering other scenarios
(motivational paragraph at the bottom).

> I still think this problem remains unsolved.

The point is that such a flag would not solve it either.

Gonzalo

Mark Watson wrote:
> 
> Gonzalo,
> 
> Your text does not recognise the desire to avoid reading semantics in
> to the arrival of RTP packets, to cope with the MGC/MG scenario.
> 
> I still think this problem remains unsolved.
> 
> ...Mark
> 
> > -----Original Message-----
> > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > Sent: 07 March 2003 08:48
> > To: Peterson, Jon
> > Cc: 'Ejzak, Richard P (Richard)'; Watson, Mark
> > [MOP:EP10:EXCH]; sipping;
> > Audet, Francois [SC100:4K02:EXCH]
> > Subject: Re: [Sipping] New version of the early media draft
> >
> >
> > Folks,
> >
> > I agree with Jon that we should not encourage people to send in-band
> 
> > ringing tones, but I also agree with Mark that this issue has
> > re-surfaced a number of times already. The message we want to get
> > through is that adding a SIP flag for resolving that issue
> > offers little
> > or no value.
> >
> > I am willing, if people agree, to add some text saying why it is not
> a
> > good idea to add a SIP-layer flag to 180 responses indicating
> > that media
> > is coming.
> >
> > What about a section along these lines:?
> >
> > 2.2.1 Problems with SIP-layer Indications in 180 Responses
> >
> > As stated above, it is not an easy task for a UAC that receives a
> 180
> > (Ringing) response to decide whether it should generate local
> ringback
> > or it will be receiving early media. At first sight, it may seem
> that
> > adding a "there is media coming" indication to 180 (Ringing)
> responses
> > would facilitate the task of UACs. Upon reception of a 180 (Ringing)
> 
> > response with such an indication, the UAC would not generate local
> > ringback. However, such an indication would offer little or no gain.
> 
> >
> > The only scenario where such an indication would be applicable is
> when
> > the UAS sends a 180 (Ringing) response and starts sending early
> media
> > right away. If the UAS intended to send early media at a later time,
> 
> > instead of right away, a sensible local policy for the UAC could be
> to
> > generate local ringback in the meantime. Therefore, the
> > "there is media
> > coming" indication would be useless.
> >
> > Assuming, then, that the UAS sends the 180 (Ringing) response and
> the
> > first media packets in parallel towards the UAC, we have a race
> > condition. If the media packets arrive at the UAC before the 180
> > (Ringing) response, the "there is media coming" indication will not
> > provide any further information to the UAC.
> >
> > The only situation where the UAC could benefit from that indication
> is
> > when the 180 (Ringing) response arrives before the first
> > media packets.
> > The UAC could avoid generating local ringback for an instant
> > before the
> > first media packets arrive. However, the same result can be
> > achieved in
> > a much simpler way (without protocol extensions) by just having UACs
> 
> > always delay the generation of local ringback for a short period of
> > time. The UAC can, for instance, generate a short beep upon
> > reception of
> > the 180 (Ringing) response (this is already done by some
> > circuit-switched mobile terminals) and one second later start
> > generating
> > local ringback if no media have been received during that period.
> >
> > \motivation{Note that adding such an indication does not keep
> > UACs from
> > implementing media arrival detection either, since they have to
> > implement it anyway to cover other scenarios, like the race
> condition
> > between the 200 OK for the INVITE and the first regular media
> > packets).}
> >
> >
> > Opinions?
> >
> > Gonzalo
> >

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 05:03:55 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17313
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 05:03:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27AFLj06381
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 05:15:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27AFLO06378
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 05:15:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17304
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 05:03:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27AELO06212;
	Fri, 7 Mar 2003 05:14:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27ADoO06161
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 05:13:50 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17227
	for <sipping@ietf.org>; Fri, 7 Mar 2003 05:01:51 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27A3q413006;
	Fri, 7 Mar 2003 05:03:53 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27A3nL28653;
	Fri, 7 Mar 2003 10:03:50 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id G357ZD94; Fri, 7 Mar 2003 10:03:35 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FS39591M>; Fri, 7 Mar 2003 10:02:36 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C4C@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>,
        "Francois Audet" <audet@nortelnetworks.com>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 7 Mar 2003 10:02:36 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E490.ADDBA312"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E490.ADDBA312
Content-Type: text/plain;
	charset="iso-8859-1"

Gonzalo,

The 200 OK vs RTP packet race condition is a smaller problem than correctly
deciding whether to play in-band media or local ringing. It doesn't
necessarily justify media detection at the MG anyway (or rather. the MG
taking 'autonomous' action on the basis of media detecion, which is the
problematic part) .

I don't think that cutting through the actual media just on the basis of
receipt of a media packet would be an acceptable solution in some (common)
business models anyway - they will want to wait for the 200 OK before
cutting through media. If that results in speech clipping then your RTT is
probably too long for acceptable speech quality anyway.

Also, as a general layering principle, I think it is bad to attach semantics
to the presence/absence of RTP packets - the expected state of the media
stream should be completely known to the endpoints based on the SIP/SDP
negotiations. This surely makes the system more robust and assists debugging
because it allows be to detect an error case where I am expecting to receive
media but do not.

I am confused by the resistance to solving this problem in the
straightforward way. The existance of in-band media seems a perfectly
reasonable thing to want to signal at the SIP layer. People seem quite happy
to give the 183 message this semantic, for the case where the call state is
unknown - why is it such a big deal to convey the *same information* at the
SIP layer for the case where the call state is known to be alerting ?? All I
want to do is atomically signal the equivalent of 180 *plus* 183.

...Mark 

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: 07 March 2003 09:27
> To: Watson, Mark [MOP:EP10:EXCH]
> Cc: Peterson, Jon; 'Ejzak, Richard P (Richard)'; sipping; Audet,
> Francois [SC100:4K02:EXCH]
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Mark,
> 
> the text says that such a flag would not solve that issue, because you
> have to implement media detection *anyway* for covering other 
> scenarios
> (motivational paragraph at the bottom).
> 
> > I still think this problem remains unsolved.
> 
> The point is that such a flag would not solve it either.
> 
> Gonzalo
> 
> Mark Watson wrote:
> > 
> > Gonzalo,
> > 
> > Your text does not recognise the desire to avoid reading 
> semantics in
> > to the arrival of RTP packets, to cope with the MGC/MG scenario.
> > 
> > I still think this problem remains unsolved.
> > 
> > ...Mark
> > 
> > > -----Original Message-----
> > > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > Sent: 07 March 2003 08:48
> > > To: Peterson, Jon
> > > Cc: 'Ejzak, Richard P (Richard)'; Watson, Mark
> > > [MOP:EP10:EXCH]; sipping;
> > > Audet, Francois [SC100:4K02:EXCH]
> > > Subject: Re: [Sipping] New version of the early media draft
> > >
> > >
> > > Folks,
> > >
> > > I agree with Jon that we should not encourage people to 
> send in-band
> > 
> > > ringing tones, but I also agree with Mark that this issue has
> > > re-surfaced a number of times already. The message we want to get
> > > through is that adding a SIP flag for resolving that issue
> > > offers little
> > > or no value.
> > >
> > > I am willing, if people agree, to add some text saying 
> why it is not
> > a
> > > good idea to add a SIP-layer flag to 180 responses indicating
> > > that media
> > > is coming.
> > >
> > > What about a section along these lines:?
> > >
> > > 2.2.1 Problems with SIP-layer Indications in 180 Responses
> > >
> > > As stated above, it is not an easy task for a UAC that receives a
> > 180
> > > (Ringing) response to decide whether it should generate local
> > ringback
> > > or it will be receiving early media. At first sight, it may seem
> > that
> > > adding a "there is media coming" indication to 180 (Ringing)
> > responses
> > > would facilitate the task of UACs. Upon reception of a 
> 180 (Ringing)
> > 
> > > response with such an indication, the UAC would not generate local
> > > ringback. However, such an indication would offer little 
> or no gain.
> > 
> > >
> > > The only scenario where such an indication would be applicable is
> > when
> > > the UAS sends a 180 (Ringing) response and starts sending early
> > media
> > > right away. If the UAS intended to send early media at a 
> later time,
> > 
> > > instead of right away, a sensible local policy for the 
> UAC could be
> > to
> > > generate local ringback in the meantime. Therefore, the
> > > "there is media
> > > coming" indication would be useless.
> > >
> > > Assuming, then, that the UAS sends the 180 (Ringing) response and
> > the
> > > first media packets in parallel towards the UAC, we have a race
> > > condition. If the media packets arrive at the UAC before the 180
> > > (Ringing) response, the "there is media coming" 
> indication will not
> > > provide any further information to the UAC.
> > >
> > > The only situation where the UAC could benefit from that 
> indication
> > is
> > > when the 180 (Ringing) response arrives before the first
> > > media packets.
> > > The UAC could avoid generating local ringback for an instant
> > > before the
> > > first media packets arrive. However, the same result can be
> > > achieved in
> > > a much simpler way (without protocol extensions) by just 
> having UACs
> > 
> > > always delay the generation of local ringback for a short 
> period of
> > > time. The UAC can, for instance, generate a short beep upon
> > > reception of
> > > the 180 (Ringing) response (this is already done by some
> > > circuit-switched mobile terminals) and one second later start
> > > generating
> > > local ringback if no media have been received during that period.
> > >
> > > \motivation{Note that adding such an indication does not keep
> > > UACs from
> > > implementing media arrival detection either, since they have to
> > > implement it anyway to cover other scenarios, like the race
> > condition
> > > between the 200 OK for the INVITE and the first regular media
> > > packets).}
> > >
> > >
> > > Opinions?
> > >
> > > Gonzalo
> > >
> 
> -- 
> Gonzalo Camarillo         Phone :  +358  9 299 33 71
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> Telecom R&D               Fax   :  +358  9 299 30 52
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> Finland                   http://www.hut.fi/~gonzalo
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Gonzalo,</FONT>
</P>

<P><FONT SIZE=3D2>The 200 OK vs RTP packet race condition is a smaller =
problem than correctly deciding whether to play in-band media or local =
ringing. It doesn't necessarily justify media detection at the MG =
anyway (or rather. the MG taking 'autonomous' action on the basis of =
media detecion, which is the problematic part) .</FONT></P>

<P><FONT SIZE=3D2>I don't think that cutting through the actual media =
just on the basis of receipt of a media packet would be an acceptable =
solution in some (common) business models anyway - they will want to =
wait for the 200 OK before cutting through media. If that results in =
speech clipping then your RTT is probably too long for acceptable =
speech quality anyway.</FONT></P>

<P><FONT SIZE=3D2>Also, as a general layering principle, I think it is =
bad to attach semantics to the presence/absence of RTP packets - the =
expected state of the media stream should be completely known to the =
endpoints based on the SIP/SDP negotiations. This surely makes the =
system more robust and assists debugging because it allows be to detect =
an error case where I am expecting to receive media but do =
not.</FONT></P>

<P><FONT SIZE=3D2>I am confused by the resistance to solving this =
problem in the straightforward way. The existance of in-band media =
seems a perfectly reasonable thing to want to signal at the SIP layer. =
People seem quite happy to give the 183 message this semantic, for the =
case where the call state is unknown - why is it such a big deal to =
convey the *same information* at the SIP layer for the case where the =
call state is known to be alerting ?? All I want to do is atomically =
signal the equivalent of 180 *plus* 183.</FONT></P>

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

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 07 March 2003 09:27</FONT>
<BR><FONT SIZE=3D2>&gt; To: Watson, Mark [MOP:EP10:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Peterson, Jon; 'Ejzak, Richard P =
(Richard)'; sipping; Audet,</FONT>
<BR><FONT SIZE=3D2>&gt; Francois [SC100:4K02:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; the text says that such a flag would not solve =
that issue, because you</FONT>
<BR><FONT SIZE=3D2>&gt; have to implement media detection *anyway* for =
covering other </FONT>
<BR><FONT SIZE=3D2>&gt; scenarios</FONT>
<BR><FONT SIZE=3D2>&gt; (motivational paragraph at the bottom).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I still think this problem remains =
unsolved.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The point is that such a flag would not solve =
it either.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark Watson wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Your text does not recognise the desire to =
avoid reading </FONT>
<BR><FONT SIZE=3D2>&gt; semantics in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to the arrival of RTP packets, to cope =
with the MGC/MG scenario.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I still think this problem remains =
unsolved.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ...Mark</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sent: 07 March 2003 08:48</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; To: Peterson, Jon</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Cc: 'Ejzak, Richard P (Richard)'; =
Watson, Mark</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; [MOP:EP10:EXCH]; sipping;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Audet, Francois =
[SC100:4K02:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Subject: Re: [Sipping] New version of =
the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Folks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; I agree with Jon that we should not =
encourage people to </FONT>
<BR><FONT SIZE=3D2>&gt; send in-band</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ringing tones, but I also agree with =
Mark that this issue has</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; re-surfaced a number of times =
already. The message we want to get</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; through is that adding a SIP flag for =
resolving that issue</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; offers little</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; or no value.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; I am willing, if people agree, to add =
some text saying </FONT>
<BR><FONT SIZE=3D2>&gt; why it is not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; good idea to add a SIP-layer flag to =
180 responses indicating</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; that media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; is coming.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; What about a section along these =
lines:?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; 2.2.1 Problems with SIP-layer =
Indications in 180 Responses</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; As stated above, it is not an easy =
task for a UAC that receives a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 180</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; (Ringing) response to decide whether =
it should generate local</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ringback</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; or it will be receiving early media. =
At first sight, it may seem</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; adding a &quot;there is media =
coming&quot; indication to 180 (Ringing)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; responses</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; would facilitate the task of UACs. =
Upon reception of a </FONT>
<BR><FONT SIZE=3D2>&gt; 180 (Ringing)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; response with such an indication, the =
UAC would not generate local</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ringback. However, such an indication =
would offer little </FONT>
<BR><FONT SIZE=3D2>&gt; or no gain.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The only scenario where such an =
indication would be applicable is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; when</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the UAS sends a 180 (Ringing) =
response and starts sending early</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; right away. If the UAS intended to =
send early media at a </FONT>
<BR><FONT SIZE=3D2>&gt; later time,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; instead of right away, a sensible =
local policy for the </FONT>
<BR><FONT SIZE=3D2>&gt; UAC could be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; generate local ringback in the =
meantime. Therefore, the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &quot;there is media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; coming&quot; indication would be =
useless.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Assuming, then, that the UAS sends =
the 180 (Ringing) response and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; first media packets in parallel =
towards the UAC, we have a race</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; condition. If the media packets =
arrive at the UAC before the 180</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; (Ringing) response, the &quot;there =
is media coming&quot; </FONT>
<BR><FONT SIZE=3D2>&gt; indication will not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; provide any further information to =
the UAC.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The only situation where the UAC =
could benefit from that </FONT>
<BR><FONT SIZE=3D2>&gt; indication</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; when the 180 (Ringing) response =
arrives before the first</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; media packets.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The UAC could avoid generating local =
ringback for an instant</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; before the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; first media packets arrive. However, =
the same result can be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; achieved in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; a much simpler way (without protocol =
extensions) by just </FONT>
<BR><FONT SIZE=3D2>&gt; having UACs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; always delay the generation of local =
ringback for a short </FONT>
<BR><FONT SIZE=3D2>&gt; period of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; time. The UAC can, for instance, =
generate a short beep upon</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; reception of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the 180 (Ringing) response (this is =
already done by some</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; circuit-switched mobile terminals) =
and one second later start</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; generating</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; local ringback if no media have been =
received during that period.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; \motivation{Note that adding such an =
indication does not keep</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; UACs from</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; implementing media arrival detection =
either, since they have to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; implement it anyway to cover other =
scenarios, like the race</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; condition</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; between the 200 OK for the INVITE and =
the first regular media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; packets).}</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Opinions?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -- </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>&gt; Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>&gt; Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>&gt; FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT SIZE=3D2>&gt; =
Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E490.ADDBA312--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 05:26:44 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18023
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 05:26:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27AcAT08677
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 05:38:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27AcAO08674
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 05:38:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18000
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 05:26:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27AbFO08219;
	Fri, 7 Mar 2003 05:37:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27AaiO07835
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 05:36:44 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17946
	for <sipping@ietf.org>; Fri, 7 Mar 2003 05:24:45 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h27AQnwv008834;
	Fri, 7 Mar 2003 11:26:49 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5X2F5SH; Fri, 7 Mar 2003 11:26:47 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h27AQklW007702;
	Fri, 7 Mar 2003 12:26:46 +0200 (EET)
Message-ID: <3E6873E4.C5CE3B72@lmf.ericsson.se>
Date: Fri, 07 Mar 2003 12:26:44 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Watson <mwatson@nortelnetworks.com>
CC: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>, Francois Audet <audet@nortelnetworks.com>
Subject: Re: [Sipping] New version of the early media draft
References: <A3C2399B2FACD411A54200508BE39C74054F7C4C@zwcwd00r.europe.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mark,

> The 200 OK vs RTP packet race condition is a smaller problem than
> correctly deciding whether to play in-band media or local ringing. It
> doesn't necessarily justify media detection at the MG anyway (or
> rather. the MG taking 'autonomous' action on the basis of media
> detecion, which is the problematic part) .
> 
> I don't think that cutting through the actual media just on the basis
> of receipt of a media packet would be an acceptable solution in some
> (common) business models anyway - they will want to wait for the 200
> OK before cutting through media. If that results in speech clipping
> then your RTT is probably too long for acceptable speech quality
> anyway.

The RTT for the media packets has *nothing* to do with the RTT for SIP
signalling. If I introduce ten proxies providing services around the
world for a call to another user in my ethernet, I will have a very long
SIP RTT, but a very short media RTT.

Therefore, your MG needs to implement media detection anyway to avoid
media clipping (200 OK-RTP race condition).

 
> Also, as a general layering principle, I think it is bad to attach
> semantics to the presence/absence of RTP packets - the expected state
> of the media stream should be completely known to the endpoints based
> on the SIP/SDP negotiations. This surely makes the system more robust
> and assists debugging because it allows be to detect an error case
> where I am expecting to receive media but do not.

The state of the media toold is given by the SDP. The media tools for a
sendrecv stream are "on". Some time ago, I proposed to introduce more
states into SDP (not only direction, but also intention of the sender),
and we finally concluded that it was a bad idea because of media
clipping and race conditions.

 
> I am confused by the resistance to solving this problem in the
> straightforward way.

I still have not heard a single proposal that solves this. If there is a
good solution, I will be more than happy to document it, but as I stated
before, having a SIP flag does not solve the problem.

> The existance of in-band media seems a perfectly
> reasonable thing to want to signal at the SIP layer. People seem quite
> happy to give the 183 message this semantic, for the case where the
> call state is unknown - why is it such a big deal to convey the *same
> information* at the SIP layer for the case where the call state is
> known to be alerting ?? All I want to do is atomically signal the
> equivalent of 180 *plus* 183.

Well, a 183 response does not imply that there will be media. Examples
of 183 responses without early media are preconditions and encapsulated
early ACMs.

And the reason why we do not have "there is media coming" indications in
neither response is because the value of a flag like that is close to
zero, per the previous analysis.

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 05:47:42 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18440
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 05:47:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27Ax9809940
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 05:59:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27Ax9O09937
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 05:59:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18422
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 05:47:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27AwDO09790;
	Fri, 7 Mar 2003 05:58:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27AvwO09739
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 05:57:58 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18382
	for <sipping@ietf.org>; Fri, 7 Mar 2003 05:45:59 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27Am0418228;
	Fri, 7 Mar 2003 05:48:01 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (europem01.nt.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27AlvL04478;
	Fri, 7 Mar 2003 10:47:58 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id G357ZKFR; Fri, 7 Mar 2003 10:47:57 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FS396ADQ>; Fri, 7 Mar 2003 10:46:49 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C4F@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>,
        "Francois Audet" <audet@nortelnetworks.com>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 7 Mar 2003 10:46:48 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E496.DAEFB4C8"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E496.DAEFB4C8
Content-Type: text/plain;
	charset="iso-8859-1"


> The RTT for the media packets has *nothing* to do with the RTT for SIP
> signalling. If I introduce ten proxies providing services around the
> world for a call to another user in my ethernet, I will have 
> a very long
> SIP RTT, but a very short media RTT.

Yes, ok, my mistake on the RTT.

> 
> Therefore, your MG needs to implement media detection anyway to avoid
> media clipping (200 OK-RTP race condition).
> 

Unless you are in an environment where you're sure the SIP RTT is low enough
for this not to be a problem.

Nevertheless, it is not the race conditions and speech clipping that I am
worried about (I'm happy to accept that this indicator does not solve those
problems.) In the case that the UAC is a decomposed MGC/MG, the MGC needs to
instruct the MG whether to play local media or whether to play in-band
media. The MG should not make this decision on its own. Early Media may well
not be allowed in all cases due to the call state, policy of the gateway &
only the MGC has all this information. The MGC needs some information at the
SIP layer in order to make this decision.

Reporting media detection from the MG to MGC is, I think, too kuldgy, too
slow & IMO puts the indication at the wrong layer. A further option would be
to keep the MG informed of 'what to do if you receive media packets', but
this is not supported (to my knowledge) in the MG/MGC signalling standards,
is overly complex and still puts the indication at the wrong layer.

An additional indicator in SIP/SDP in the 180 that in-band media is present
would provide a solution. I don't care how the indicator is coded in the SIP
message and we are on the SIPPING list anyway, so that discussion is out of
scope.

...Mark

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>&gt; The RTT for the media packets has *nothing* to =
do with the RTT for SIP</FONT>
<BR><FONT SIZE=3D2>&gt; signalling. If I introduce ten proxies =
providing services around the</FONT>
<BR><FONT SIZE=3D2>&gt; world for a call to another user in my =
ethernet, I will have </FONT>
<BR><FONT SIZE=3D2>&gt; a very long</FONT>
<BR><FONT SIZE=3D2>&gt; SIP RTT, but a very short media RTT.</FONT>
</P>

<P><FONT SIZE=3D2>Yes, ok, my mistake on the RTT.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Therefore, your MG needs to implement media =
detection anyway to avoid</FONT>
<BR><FONT SIZE=3D2>&gt; media clipping (200 OK-RTP race =
condition).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>Unless you are in an environment where you're sure =
the SIP RTT is low enough for this not to be a problem.</FONT>
</P>

<P><FONT SIZE=3D2>Nevertheless, it is not the race conditions and =
speech clipping that I am worried about (I'm happy to accept that this =
indicator does not solve those problems.) In the case that the UAC is a =
decomposed MGC/MG, the MGC needs to instruct the MG whether to play =
local media or whether to play in-band media. The MG should not make =
this decision on its own. Early Media may well not be allowed in all =
cases due to the call state, policy of the gateway &amp; only the MGC =
has all this information. The MGC needs some information at the SIP =
layer in order to make this decision.</FONT></P>

<P><FONT SIZE=3D2>Reporting media detection from the MG to MGC is, I =
think, too kuldgy, too slow &amp; IMO puts the indication at the wrong =
layer. A further option would be to keep the MG informed of 'what to do =
if you receive media packets', but this is not supported (to my =
knowledge) in the MG/MGC signalling standards, is overly complex and =
still puts the indication at the wrong layer.</FONT></P>

<P><FONT SIZE=3D2>An additional indicator in SIP/SDP in the 180 that =
in-band media is present would provide a solution. I don't care how the =
indicator is coded in the SIP message and we are on the SIPPING list =
anyway, so that discussion is out of scope.</FONT></P>

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

</BODY>
</HTML>
------_=_NextPart_001_01C2E496.DAEFB4C8--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 06:15:08 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19102
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 06:15:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27BQZ912769
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 06:26:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27BQZO12766
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 06:26:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19080
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 06:14:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27BPgO12662;
	Fri, 7 Mar 2003 06:25:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27BIAO12088
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 06:18:10 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18875
	for <sipping@ietf.org>; Fri, 7 Mar 2003 06:06:11 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h27B8EB3012404;
	Fri, 7 Mar 2003 12:08:14 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id F5W985ZP; Fri, 7 Mar 2003 12:08:13 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h27B88lW010450;
	Fri, 7 Mar 2003 13:08:08 +0200 (EET)
Message-ID: <3E687D97.4B35FB60@lmf.ericsson.se>
Date: Fri, 07 Mar 2003 13:08:07 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Watson <mwatson@nortelnetworks.com>
CC: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>, Francois Audet <audet@nortelnetworks.com>
Subject: Re: [Sipping] New version of the early media draft
References: <A3C2399B2FACD411A54200508BE39C74054F7C4F@zwcwd00r.europe.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mark,

If I understood your mail correctly, you acknowledge that when race
conditions are possible, a "there is media coming" does not solve
anything. But you believe that in environments where you are sure that
no race conditions will occur, such a flag would be useful.

However, we do not design SIP with that type of environments in mind.
Any SIP mechanism should work assuming that SIP-RTP race conditions
occur.

Maybe you are after a P-flag to use in close environments where SIP
signalling always beat RTP packets?

Gonzalo



Mark Watson wrote:
> 
> > The RTT for the media packets has *nothing* to do with the RTT for
> SIP
> > signalling. If I introduce ten proxies providing services around the
> 
> > world for a call to another user in my ethernet, I will have
> > a very long
> > SIP RTT, but a very short media RTT.
> 
> Yes, ok, my mistake on the RTT.
> 
> >
> > Therefore, your MG needs to implement media detection anyway to
> avoid
> > media clipping (200 OK-RTP race condition).
> >
> 
> Unless you are in an environment where you're sure the SIP RTT is low
> enough for this not to be a problem.
> 
> Nevertheless, it is not the race conditions and speech clipping that I
> am worried about (I'm happy to accept that this indicator does not
> solve those problems.) In the case that the UAC is a decomposed
> MGC/MG, the MGC needs to instruct the MG whether to play local media
> or whether to play in-band media. The MG should not make this decision
> on its own. Early Media may well not be allowed in all cases due to
> the call state, policy of the gateway & only the MGC has all this
> information. The MGC needs some information at the SIP layer in order
> to make this decision.
> 
> Reporting media detection from the MG to MGC is, I think, too kuldgy,
> too slow & IMO puts the indication at the wrong layer. A further
> option would be to keep the MG informed of 'what to do if you receive
> media packets', but this is not supported (to my knowledge) in the
> MG/MGC signalling standards, is overly complex and still puts the
> indication at the wrong layer.
> 
> An additional indicator in SIP/SDP in the 180 that in-band media is
> present would provide a solution. I don't care how the indicator is
> coded in the SIP message and we are on the SIPPING list anyway, so
> that discussion is out of scope.
> 
> ...Mark
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 06:25:07 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19431
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 06:25:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27BaZk13417
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 06:36:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27BaZO13414
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 06:36:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19420
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 06:24:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27BZ9O13359;
	Fri, 7 Mar 2003 06:35:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27BY2O13324
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 06:34:02 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19340
	for <sipping@ietf.org>; Fri, 7 Mar 2003 06:22:02 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27BO3428963;
	Fri, 7 Mar 2003 06:24:03 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27BO0L15690;
	Fri, 7 Mar 2003 11:24:00 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id G357ZPAG; Fri, 7 Mar 2003 11:24:00 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FS396BQ2>; Fri, 7 Mar 2003 11:23:05 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C51@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>,
        "Francois Audet" <audet@nortelnetworks.com>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 7 Mar 2003 11:23:03 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E49B.EB2DD64E"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E49B.EB2DD64E
Content-Type: text/plain;
	charset="iso-8859-1"


> Mark,
> 
> If I understood your mail correctly, you acknowledge that when race
> conditions are possible, a "there is media coming" does not solve
> anything.

No, I acknowledge it doesn't solve the race conditions.


> But you believe that in environments where you are sure that
> no race conditions will occur, such a flag would be useful.
> 

No, I am saying that the solution that you have proposed is not appropriate
for a decomposed Media Gateway/Media Gateway Controller case. I acknowledge
that the race condition problem still exists in that case (e.g. at answer),
but I still think the media detection solution is not appropriate. So,
perhaps the race condition problem remains unsolved in that case, but I am
not so concerned about that problem.


> However, we do not design SIP with that type of environments in mind.
> Any SIP mechanism should work assuming that SIP-RTP race conditions
> occur.
> 

Of course not, but surely we do design SIP in a way which can work on a
gateway designed according to other IETF standards for gateways
(specifically megaco) ?

Even if you do want to assume a monolithic SIP UA, then I still think it's
valuable to pay attention to the layering in the system. I still believe
it's more robust if the media stream state is known at the signalling layer.

> Maybe you are after a P-flag to use in close environments where SIP
> signalling always beat RTP packets?
> 

Not exactly. The SIP message does not need to beat the RTP packet anyway.
There are well-established standards which imply acceptable times within
which cut-through should occur at answer, for example.

> Gonzalo
> 
> 
> 
> Mark Watson wrote:
> > 
> > > The RTT for the media packets has *nothing* to do with the RTT for
> > SIP
> > > signalling. If I introduce ten proxies providing services 
> around the
> > 
> > > world for a call to another user in my ethernet, I will have
> > > a very long
> > > SIP RTT, but a very short media RTT.
> > 
> > Yes, ok, my mistake on the RTT.
> > 
> > >
> > > Therefore, your MG needs to implement media detection anyway to
> > avoid
> > > media clipping (200 OK-RTP race condition).
> > >
> > 
> > Unless you are in an environment where you're sure the SIP 
> RTT is low
> > enough for this not to be a problem.
> > 
> > Nevertheless, it is not the race conditions and speech 
> clipping that I
> > am worried about (I'm happy to accept that this indicator does not
> > solve those problems.) In the case that the UAC is a decomposed
> > MGC/MG, the MGC needs to instruct the MG whether to play local media
> > or whether to play in-band media. The MG should not make 
> this decision
> > on its own. Early Media may well not be allowed in all cases due to
> > the call state, policy of the gateway & only the MGC has all this
> > information. The MGC needs some information at the SIP 
> layer in order
> > to make this decision.
> > 
> > Reporting media detection from the MG to MGC is, I think, 
> too kuldgy,
> > too slow & IMO puts the indication at the wrong layer. A further
> > option would be to keep the MG informed of 'what to do if 
> you receive
> > media packets', but this is not supported (to my knowledge) in the
> > MG/MGC signalling standards, is overly complex and still puts the
> > indication at the wrong layer.
> > 
> > An additional indicator in SIP/SDP in the 180 that in-band media is
> > present would provide a solution. I don't care how the indicator is
> > coded in the SIP message and we are on the SIPPING list anyway, so
> > that discussion is out of scope.
> > 
> > ...Mark
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>&gt; Mark,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; If I understood your mail correctly, you =
acknowledge that when race</FONT>
<BR><FONT SIZE=3D2>&gt; conditions are possible, a &quot;there is media =
coming&quot; does not solve</FONT>
<BR><FONT SIZE=3D2>&gt; anything.</FONT>
</P>

<P><FONT SIZE=3D2>No, I acknowledge it doesn't solve the race =
conditions.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; But you believe that in environments where you =
are sure that</FONT>
<BR><FONT SIZE=3D2>&gt; no race conditions will occur, such a flag =
would be useful.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>No, I am saying that the solution that you have =
proposed is not appropriate for a decomposed Media Gateway/Media =
Gateway Controller case. I acknowledge that the race condition problem =
still exists in that case (e.g. at answer), but I still think the media =
detection solution is not appropriate. So, perhaps the race condition =
problem remains unsolved in that case, but I am not so concerned about =
that problem.</FONT></P>
<BR>

<P><FONT SIZE=3D2>&gt; However, we do not design SIP with that type of =
environments in mind.</FONT>
<BR><FONT SIZE=3D2>&gt; Any SIP mechanism should work assuming that =
SIP-RTP race conditions</FONT>
<BR><FONT SIZE=3D2>&gt; occur.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>Of course not, but surely we do design SIP in a way =
which can work on a gateway designed according to other IETF standards =
for gateways (specifically megaco) ?</FONT></P>

<P><FONT SIZE=3D2>Even if you do want to assume a monolithic SIP UA, =
then I still think it's valuable to pay attention to the layering in =
the system. I still believe it's more robust if the media stream state =
is known at the signalling layer.</FONT></P>

<P><FONT SIZE=3D2>&gt; Maybe you are after a P-flag to use in close =
environments where SIP</FONT>
<BR><FONT SIZE=3D2>&gt; signalling always beat RTP packets?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>Not exactly. The SIP message does not need to beat =
the RTP packet anyway. There are well-established standards which imply =
acceptable times within which cut-through should occur at answer, for =
example.</FONT></P>

<P><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark Watson wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The RTT for the media packets has =
*nothing* to do with the RTT for</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; signalling. If I introduce ten =
proxies providing services </FONT>
<BR><FONT SIZE=3D2>&gt; around the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; world for a call to another user in =
my ethernet, I will have</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; a very long</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; SIP RTT, but a very short media =
RTT.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Yes, ok, my mistake on the RTT.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Therefore, your MG needs to implement =
media detection anyway to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; avoid</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; media clipping (200 OK-RTP race =
condition).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Unless you are in an environment where =
you're sure the SIP </FONT>
<BR><FONT SIZE=3D2>&gt; RTT is low</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; enough for this not to be a =
problem.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Nevertheless, it is not the race =
conditions and speech </FONT>
<BR><FONT SIZE=3D2>&gt; clipping that I</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; am worried about (I'm happy to accept that =
this indicator does not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; solve those problems.) In the case that =
the UAC is a decomposed</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; MGC/MG, the MGC needs to instruct the MG =
whether to play local media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; or whether to play in-band media. The MG =
should not make </FONT>
<BR><FONT SIZE=3D2>&gt; this decision</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; on its own. Early Media may well not be =
allowed in all cases due to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the call state, policy of the gateway =
&amp; only the MGC has all this</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; information. The MGC needs some =
information at the SIP </FONT>
<BR><FONT SIZE=3D2>&gt; layer in order</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to make this decision.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Reporting media detection from the MG to =
MGC is, I think, </FONT>
<BR><FONT SIZE=3D2>&gt; too kuldgy,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; too slow &amp; IMO puts the indication at =
the wrong layer. A further</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; option would be to keep the MG informed of =
'what to do if </FONT>
<BR><FONT SIZE=3D2>&gt; you receive</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; media packets', but this is not supported =
(to my knowledge) in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; MG/MGC signalling standards, is overly =
complex and still puts the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; indication at the wrong layer.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; An additional indicator in SIP/SDP in the =
180 that in-band media is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; present would provide a solution. I don't =
care how the indicator is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; coded in the SIP message and we are on the =
SIPPING list anyway, so</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that discussion is out of scope.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ...Mark</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E49B.EB2DD64E--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 07:00:16 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22712
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 07:00:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27CBjE17109
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 07:11:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CBjO17106
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 07:11:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22500
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 06:59:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CAQO16916;
	Fri, 7 Mar 2003 07:10:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27C35O15603
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 07:03:05 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20763;
	Fri, 7 Mar 2003 06:51:06 -0500 (EST)
Message-Id: <200303071151.GAA20763@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 06:51:05 -0500
Subject: [Sipping] I-D ACTION:draft-levin-sipping-conferencing-requirements-03.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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


	Title		: High Level Requirements for Tightly Coupled SIP 
                          Conferencing
	Author(s)	: O. Levin, R. Even
	Filename	: draft-levin-sipping-conferencing-requirements-03.txt
	Pages		: 13
	Date		: 2003-3-6
	
This document examines a wide range of conferencing requirements for
tightly coupled SIP conferences. Separate documents will map the
requirements to existing protocol primitives, define new protocol
extensions, and introduce new protocols as needed. Together, these
documents will provide a guide for building interoperable SIP
conferencing applications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-levin-sipping-conferencing-requirements-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-levin-sipping-conferencing-requirements-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-levin-sipping-conferencing-requirements-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:	<2003-3-6124605.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-levin-sipping-conferencing-requirements-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-levin-sipping-conferencing-requirements-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-6124605.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 07:01:55 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23027
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 07:01:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27CDOX17172
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 07:13:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CDOO17169
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 07:13:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22926
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 07:01:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CBFO17021;
	Fri, 7 Mar 2003 07:11:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27C47O15643
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 07:04:07 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20984;
	Fri, 7 Mar 2003 06:52:07 -0500 (EST)
Message-Id: <200303071152.GAA20984@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 06:52:07 -0500
Subject: [Sipping] I-D ACTION:draft-culpepper-sipping-app-interact-reqs-03.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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


	Title		: Session Initiation Protocol Based Application 
                          Interaction Requirements
	Author(s)	: B. Culpepper, R. Fairlie-Cuninghame
	Filename	: draft-culpepper-sipping-app-interact-reqs-03.txt
	Pages		: 8
	Date		: 2003-3-6
	
This document defines the high level requirements for a framework 
and/or one or more mechanisms that support user interaction, via 
SIP-based user agents, with applications residing on remote network 
servers.  The requirements in this document address the overall 
features of such a system, without regard to its architecture. 
SIP currently supports media-based application interactions using 
methods such as speech, video and end-to-end telephony-related 
tones; however, it is desired that more general application 
interaction models are defined, especially those that are not 
restricted to the media plane.  In addition, it is desired that an 
application be able to present the user with application-specific 
user interfaces and information.  The user agent should also be able 
to generate activity indications back to an application to 
communicate actions on physical or logical user interfaces.  The 
document also defines a number of topic-related terms to assist in 
disambiguating discussions of the issues.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-culpepper-sipping-app-interact-reqs-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-culpepper-sipping-app-interact-reqs-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-culpepper-sipping-app-interact-reqs-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:	<2003-3-6124807.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-culpepper-sipping-app-interact-reqs-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-culpepper-sipping-app-interact-reqs-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-6124807.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 07:10:17 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23876
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 07:10:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27CLkH17856
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 07:21:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CLkO17853
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 07:21:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23844
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 07:09:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CL2O17783;
	Fri, 7 Mar 2003 07:21:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27C6WO15803
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 07:06:32 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21574;
	Fri, 7 Mar 2003 06:54:32 -0500 (EST)
Message-Id: <200303071154.GAA21574@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 06:54:32 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-3pcc-03.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Best Current Practices for Third Party Call Control in
                          the Session Initiation Protocol
	Author(s)	: J. Rosenberg, J. Peterson, H. Schulzrinne, 
                          G. Camarillo
	Filename	: draft-ietf-sipping-3pcc-03.txt
	Pages		: 29
	Date		: 2003-3-6
	
Third party call control refers to the ability of one entity to
create a call in which communications is actually between other
parties. Third party call control is possible using the mechanisms
specified within the Session Initiation Protocol (SIP). However,
there are several possible approaches, each with different benefits
and drawbacks. This document discusses best current practices for the
usage of the SIP for third party call control.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-3pcc-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sipping-3pcc-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-sipping-3pcc-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:	<2003-3-6125442.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-3pcc-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-3pcc-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-6125442.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 07:10:19 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23889
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 07:10:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27CLmd17872
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 07:21:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CLmO17869
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 07:21:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23848
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 07:09:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CL4O17803;
	Fri, 7 Mar 2003 07:21:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27C6aO15807
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 07:06:36 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21594;
	Fri, 7 Mar 2003 06:54:37 -0500 (EST)
Message-Id: <200303071154.GAA21594@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 06:54:37 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-service-examples-04.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Session Initiation Protocol Service Examples
	Author(s)	: A. Johnston, S. Donovan et al.
	Filename	: draft-ietf-sipping-service-examples-04.txt
	Pages		: 155
	Date		: 2003-3-6
	
This informational document gives examples of Session Initiation
Protocol (SIP) services.  This covers most features offered in
so-called Centrex offerings from local exchange carriers and PBX
(Private Branch Exchange) features.  Most of the services shown in
this document are implemented in the SIP User Agents, although some
require the assistance of a SIP Proxy.  Some require some extensions
to SIP including the REFER, SUBSCRIBE, and NOTIFY methods and the
Replaces and Join headers. These features are not intended to be an
exhaustive set, but rather show implementations of common features
likely to be implemented on SIP IP telephones in a business
environment.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sipping-service-examples-04.txt".

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


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

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

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

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

Content-Type: text/plain
Content-ID:	<2003-3-6125450.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-service-examples-04.txt

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

Content-Type: text/plain
Content-ID:	<2003-3-6125450.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 07:31:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26074
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 07:31:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27ChAk20512
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 07:43:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27ChAO20509
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 07:43:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26033
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 07:31:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CgUO20466;
	Fri, 7 Mar 2003 07:42:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CfTO20334
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 07:41:29 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25838
	for <sipping@ietf.org>; Fri, 7 Mar 2003 07:29:27 -0500 (EST)
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h27CVVB3004847;
	Fri, 7 Mar 2003 13:31:31 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id FDVMZ6XC; Fri, 7 Mar 2003 13:31:24 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h27CVIlW016243;
	Fri, 7 Mar 2003 14:31:18 +0200 (EET)
Message-ID: <3E689114.BBB29FB4@lmf.ericsson.se>
Date: Fri, 07 Mar 2003 14:31:16 +0200
X-Sybari-Trust: 6bc73aaf 9ffcebbb a5ee123c 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Watson <mwatson@nortelnetworks.com>
CC: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>, Francois Audet <audet@nortelnetworks.com>
Subject: Re: [Sipping] New version of the early media draft
References: <A3C2399B2FACD411A54200508BE39C74054F7C51@zwcwd00r.europe.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mark,

OK, now I think I understand you. You want to develop a flag to be used
by systems that do not care about media clipping (they are probably in a
controlled environment without race conditions) but care about not
having to perform media detection (because they are distributed;
MGC-MG).

One of the assumption when designing SIP was that systems cared about
media clipping... I do not think we can develop general extensions at
this point in time that cause media clipping in order to resolve things
like ringback generation.

You may want to create a document that defines a P-flag and says: if you
do not care about media clipping for some reason, use this flag to have
accurate information in the SIP layer about the presence of media.

I understand what you are after, but I do not think we have a *general*
mechanism that resolves it.

Gonzalo



Mark Watson wrote:
> 
> > Mark,
> >
> > If I understood your mail correctly, you acknowledge that when race
> > conditions are possible, a "there is media coming" does not solve
> > anything.
> 
> No, I acknowledge it doesn't solve the race conditions.
> 
> > But you believe that in environments where you are sure that
> > no race conditions will occur, such a flag would be useful.
> >
> 
> No, I am saying that the solution that you have proposed is not
> appropriate for a decomposed Media Gateway/Media Gateway Controller
> case. I acknowledge that the race condition problem still exists in
> that case (e.g. at answer), but I still think the media detection
> solution is not appropriate. So, perhaps the race condition problem
> remains unsolved in that case, but I am not so concerned about that
> problem.
> 
> > However, we do not design SIP with that type of environments in
> mind.
> > Any SIP mechanism should work assuming that SIP-RTP race conditions
> > occur.
> >
> 
> Of course not, but surely we do design SIP in a way which can work on
> a gateway designed according to other IETF standards for gateways
> (specifically megaco) ?
> 
> Even if you do want to assume a monolithic SIP UA, then I still think
> it's valuable to pay attention to the layering in the system. I still
> believe it's more robust if the media stream state is known at the
> signalling layer.
> 
> > Maybe you are after a P-flag to use in close environments where SIP
> > signalling always beat RTP packets?
> >
> 
> Not exactly. The SIP message does not need to beat the RTP packet
> anyway. There are well-established standards which imply acceptable
> times within which cut-through should occur at answer, for example.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 09:02:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02671
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 09:02:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27EDrL28452
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 09:13:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27EDqO28449
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 09:13:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02625
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 09:01:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27EBSO28298;
	Fri, 7 Mar 2003 09:11:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27EAlO28066
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 09:10:47 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02247
	for <sipping@ietf.org>; Fri, 7 Mar 2003 08:58:43 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27E0j402384;
	Fri, 7 Mar 2003 09:00:45 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27E0cL21283;
	Fri, 7 Mar 2003 14:00:38 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id G3575C9Y; Fri, 7 Mar 2003 14:00:38 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FS396HS8>; Fri, 7 Mar 2003 13:59:29 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C54@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>,
        "Francois Audet" <audet@nortelnetworks.com>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 7 Mar 2003 13:59:23 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E4B1.C1B1BB30"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E4B1.C1B1BB30
Content-Type: text/plain;
	charset="iso-8859-1"

Gonzalo,

I didn't say that media clipping was not a problem, or that I was concerned
only with systems which did not care about media clipping. I just said that
media clipping was not the problem I was addressing here.

The problem I am addressing here is how an MGC decides whether to instruct
it's MG to play local ringing or to play media.

Your argument seems to be something along the lines of:
1) Because of the media clipping problem, the MG will need to detect in-band
media, and 
2) this also provides a solution to the MGC/MG ringback problem, because
either
2a) the MG can override local ringback with the detected media, or
2b) the MG can report the detected media to the MGC, which can instruct the
MG to play it

I am saying that, **whether or not (1) is true**, (2) is not. We can argue
about whether or not (1) is true, are there other solutions to media
clipping etc., but that is not the issue.

Neither 2a not 2b provide an acceptable general solution to this problem =>
(2a) involves inappropriate autonomy for the MG and 2b is not supported in
the standards right now and IMO a little kludgy. Further, both 2a and 2b
seem to be inappropriate architecturally since they attach symantics to the
arrival of the RTP data.

Further, there is scope in the current specs for TDM gateways which send
backwards media right from the off, which may contain silence - do I need to
look inside the RTP packets to see if there is 'real' media there ?

So, I rather think it is *your* solution which is not general. Addition of a
functional indication of in-band media at the SIP layer would ensure we have
a solution to this problem in all cases.

Regards...Mark



> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: 07 March 2003 12:31
> To: Watson, Mark [MOP:EP10:EXCH]
> Cc: Peterson, Jon; 'Ejzak, Richard P (Richard)'; sipping; Audet,
> Francois [SC100:4K02:EXCH]
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Mark,
> 
> OK, now I think I understand you. You want to develop a flag 
> to be used
> by systems that do not care about media clipping (they are 
> probably in a
> controlled environment without race conditions) but care about not
> having to perform media detection (because they are distributed;
> MGC-MG).
> 
> One of the assumption when designing SIP was that systems cared about
> media clipping... I do not think we can develop general extensions at
> this point in time that cause media clipping in order to 
> resolve things
> like ringback generation.
> 
> You may want to create a document that defines a P-flag and 
> says: if you
> do not care about media clipping for some reason, use this 
> flag to have
> accurate information in the SIP layer about the presence of media.
> 
> I understand what you are after, but I do not think we have a 
> *general*
> mechanism that resolves it.
> 
> Gonzalo
> 
> 
> 
> Mark Watson wrote:
> > 
> > > Mark,
> > >
> > > If I understood your mail correctly, you acknowledge that 
> when race
> > > conditions are possible, a "there is media coming" does not solve
> > > anything.
> > 
> > No, I acknowledge it doesn't solve the race conditions.
> > 
> > > But you believe that in environments where you are sure that
> > > no race conditions will occur, such a flag would be useful.
> > >
> > 
> > No, I am saying that the solution that you have proposed is not
> > appropriate for a decomposed Media Gateway/Media Gateway Controller
> > case. I acknowledge that the race condition problem still exists in
> > that case (e.g. at answer), but I still think the media detection
> > solution is not appropriate. So, perhaps the race condition problem
> > remains unsolved in that case, but I am not so concerned about that
> > problem.
> > 
> > > However, we do not design SIP with that type of environments in
> > mind.
> > > Any SIP mechanism should work assuming that SIP-RTP race 
> conditions
> > > occur.
> > >
> > 
> > Of course not, but surely we do design SIP in a way which 
> can work on
> > a gateway designed according to other IETF standards for gateways
> > (specifically megaco) ?
> > 
> > Even if you do want to assume a monolithic SIP UA, then I 
> still think
> > it's valuable to pay attention to the layering in the 
> system. I still
> > believe it's more robust if the media stream state is known at the
> > signalling layer.
> > 
> > > Maybe you are after a P-flag to use in close environments 
> where SIP
> > > signalling always beat RTP packets?
> > >
> > 
> > Not exactly. The SIP message does not need to beat the RTP packet
> > anyway. There are well-established standards which imply acceptable
> > times within which cut-through should occur at answer, for example.
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Gonzalo,</FONT>
</P>

<P><FONT SIZE=3D2>I didn't say that media clipping was not a problem, =
or that I was concerned only with systems which did not care about =
media clipping. I just said that media clipping was not the problem I =
was addressing here.</FONT></P>

<P><FONT SIZE=3D2>The problem I am addressing here is how an MGC =
decides whether to instruct it's MG to play local ringing or to play =
media.</FONT></P>

<P><FONT SIZE=3D2>Your argument seems to be something along the lines =
of:</FONT>
<BR><FONT SIZE=3D2>1) Because of the media clipping problem, the MG =
will need to detect in-band media, and </FONT>
<BR><FONT SIZE=3D2>2) this also provides a solution to the MGC/MG =
ringback problem, because either</FONT>
<BR><FONT SIZE=3D2>2a) the MG can override local ringback with the =
detected media, or</FONT>
<BR><FONT SIZE=3D2>2b) the MG can report the detected media to the MGC, =
which can instruct the MG to play it</FONT>
</P>

<P><FONT SIZE=3D2>I am saying that, **whether or not (1) is true**, (2) =
is not. We can argue about whether or not (1) is true, are there other =
solutions to media clipping etc., but that is not the issue.</FONT></P>

<P><FONT SIZE=3D2>Neither 2a not 2b provide an acceptable general =
solution to this problem =3D&gt; (2a) involves inappropriate autonomy =
for the MG and 2b is not supported in the standards right now and IMO a =
little kludgy. Further, both 2a and 2b seem to be inappropriate =
architecturally since they attach symantics to the arrival of the RTP =
data.</FONT></P>

<P><FONT SIZE=3D2>Further, there is scope in the current specs for TDM =
gateways which send backwards media right from the off, which may =
contain silence - do I need to look inside the RTP packets to see if =
there is 'real' media there ?</FONT></P>

<P><FONT SIZE=3D2>So, I rather think it is *your* solution which is not =
general. Addition of a functional indication of in-band media at the =
SIP layer would ensure we have a solution to this problem in all =
cases.</FONT></P>

<P><FONT SIZE=3D2>Regards...Mark</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 07 March 2003 12:31</FONT>
<BR><FONT SIZE=3D2>&gt; To: Watson, Mark [MOP:EP10:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Peterson, Jon; 'Ejzak, Richard P =
(Richard)'; sipping; Audet,</FONT>
<BR><FONT SIZE=3D2>&gt; Francois [SC100:4K02:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; OK, now I think I understand you. You want to =
develop a flag </FONT>
<BR><FONT SIZE=3D2>&gt; to be used</FONT>
<BR><FONT SIZE=3D2>&gt; by systems that do not care about media =
clipping (they are </FONT>
<BR><FONT SIZE=3D2>&gt; probably in a</FONT>
<BR><FONT SIZE=3D2>&gt; controlled environment without race conditions) =
but care about not</FONT>
<BR><FONT SIZE=3D2>&gt; having to perform media detection (because they =
are distributed;</FONT>
<BR><FONT SIZE=3D2>&gt; MGC-MG).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; One of the assumption when designing SIP was =
that systems cared about</FONT>
<BR><FONT SIZE=3D2>&gt; media clipping... I do not think we can develop =
general extensions at</FONT>
<BR><FONT SIZE=3D2>&gt; this point in time that cause media clipping in =
order to </FONT>
<BR><FONT SIZE=3D2>&gt; resolve things</FONT>
<BR><FONT SIZE=3D2>&gt; like ringback generation.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; You may want to create a document that defines =
a P-flag and </FONT>
<BR><FONT SIZE=3D2>&gt; says: if you</FONT>
<BR><FONT SIZE=3D2>&gt; do not care about media clipping for some =
reason, use this </FONT>
<BR><FONT SIZE=3D2>&gt; flag to have</FONT>
<BR><FONT SIZE=3D2>&gt; accurate information in the SIP layer about the =
presence of media.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I understand what you are after, but I do not =
think we have a </FONT>
<BR><FONT SIZE=3D2>&gt; *general*</FONT>
<BR><FONT SIZE=3D2>&gt; mechanism that resolves it.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark Watson wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Mark,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; If I understood your mail correctly, =
you acknowledge that </FONT>
<BR><FONT SIZE=3D2>&gt; when race</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; conditions are possible, a =
&quot;there is media coming&quot; does not solve</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; anything.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; No, I acknowledge it doesn't solve the =
race conditions.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; But you believe that in environments =
where you are sure that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; no race conditions will occur, such a =
flag would be useful.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; No, I am saying that the solution that you =
have proposed is not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; appropriate for a decomposed Media =
Gateway/Media Gateway Controller</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; case. I acknowledge that the race =
condition problem still exists in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that case (e.g. at answer), but I still =
think the media detection</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; solution is not appropriate. So, perhaps =
the race condition problem</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; remains unsolved in that case, but I am =
not so concerned about that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; problem.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; However, we do not design SIP with =
that type of environments in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; mind.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Any SIP mechanism should work =
assuming that SIP-RTP race </FONT>
<BR><FONT SIZE=3D2>&gt; conditions</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; occur.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Of course not, but surely we do design SIP =
in a way which </FONT>
<BR><FONT SIZE=3D2>&gt; can work on</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; a gateway designed according to other IETF =
standards for gateways</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (specifically megaco) ?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Even if you do want to assume a monolithic =
SIP UA, then I </FONT>
<BR><FONT SIZE=3D2>&gt; still think</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; it's valuable to pay attention to the =
layering in the </FONT>
<BR><FONT SIZE=3D2>&gt; system. I still</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; believe it's more robust if the media =
stream state is known at the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; signalling layer.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Maybe you are after a P-flag to use =
in close environments </FONT>
<BR><FONT SIZE=3D2>&gt; where SIP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; signalling always beat RTP =
packets?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Not exactly. The SIP message does not need =
to beat the RTP packet</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; anyway. There are well-established =
standards which imply acceptable</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; times within which cut-through should =
occur at answer, for example.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E4B1.C1B1BB30--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 09:33:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04829
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 09:33:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27Ej9v31284
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 09:45:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27Ej9O31277
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 09:45:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04803
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 09:33:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27EiOO31215;
	Fri, 7 Mar 2003 09:44:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27Eh6O31179
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 09:43:06 -0500
Received: from imo-m01.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04722
	for <sipping@ietf.org>; Fri, 7 Mar 2003 09:31:02 -0500 (EST)
Received: from bertculpepper@netscape.net
	by imo-m01.mx.aol.com (mail_out_v34.21.) id l.1b1.5129310 (16226)
	 for <sipping@ietf.org>; Fri, 7 Mar 2003 09:32:47 -0500 (EST)
Received: from  netscape.net (159.252.8.67.cfl.rr.com [67.8.252.159]) by air-in02.mx.aol.com (v90_r2.5) with ESMTP id MAILININ22-0307093247; Fri, 07 Mar 2003 09:32:47 -0500
Message-ID: <3E68AE11.6080404@netscape.net>
Date: Fri, 07 Mar 2003 09:34:57 -0500
From: Bert Culpepper <bertculpepper@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: SIPPING List <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailer: Unknown (No Version)
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Changes in SIP Application Interaction Requirements I-D
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

draft-culpepper-sipping-app-interact-reqs-03.txt has the following changes:

- Editorial "fixes",
- Added use case text,
- Added requirement dealing with correlation of user indications
    to media streams,
- Added requirement dealing with suppression of other forms of
    transmitting user indications when requested.

Please post any issues/comments to the SIPPING list and authors.  The
I-D is available at
www.ietf.org/internet-drafts/draft-culpepper-sipping-app-interact-reqs-03.txt.

Thank you,
Bert


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 09:52:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06940
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 09:52:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27F44A32678
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 10:04:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27F44O32675
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 10:04:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06815
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 09:51:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27F2BO32558;
	Fri, 7 Mar 2003 10:02:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27F1xO32538
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 10:01:59 -0500
Received: from mgw-x4.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06411
	for <sipping@ietf.org>; Fri, 7 Mar 2003 09:49:54 -0500 (EST)
From: aki.niemi@nokia.com
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27EtLF27715
	for <sipping@ietf.org>; Fri, 7 Mar 2003 16:55:21 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60d5ce2d24ac158f23077@esvir03nok.nokia.com> for <sipping@ietf.org>;
 Fri, 7 Mar 2003 16:51:59 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 7 Mar 2003 16:51:58 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 7 Mar 2003 16:51:57 +0200
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD9019451A5@esebe013.ntc.nokia.com>
Thread-Topic: I-D ACTION:draft-niemi-sipping-event-throttle-reqs-01.txt
Thread-Index: AcLjQJ3q1PR1+vRdRuKZKidcOlLpPABdxUbg
To: <sipping@ietf.org>
X-OriginalArrivalTime: 07 Mar 2003 14:51:59.0221 (UTC) FILETIME=[1AF60A50:01C2E4B9]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h27F1xO32539
Subject: [Sipping] New version of the rate limiting requirements
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi All,

I recently submitted an update to the throttle requirements draft. It now includes a chapter discussing the model for event throttles, reusing the "quarantine" model introduced by the MWI work. 

I also cleaned up the requirements a bit to reflect the comments received on the list. Check also the "Open Issues" section, which conveniently tries to summarize the issues I think we might want to address next.

http://www.ietf.org/internet-drafts/draft-niemi-sipping-event-throttle-reqs-01.txt

Comments are welcome!

Cheers,
Aki
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 09:54:17 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07239
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 09:54:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27F5om00394
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 10:05:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27F5oO00391
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 10:05:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07128
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 09:53:42 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27F35O32624;
	Fri, 7 Mar 2003 10:03:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27F2tO32584
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 10:02:55 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06534
	for <sipping@ietf.org>; Fri, 7 Mar 2003 09:50:47 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27Eqp408126
	for <sipping@ietf.org>; Fri, 7 Mar 2003 09:52:51 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27EqnL27639
	for <sipping@ietf.org>; Fri, 7 Mar 2003 14:52:49 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id G3575K49; Fri, 7 Mar 2003 14:52:49 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FS396J9W>; Fri, 7 Mar 2003 14:51:40 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C58@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Fri, 7 Mar 2003 14:51:37 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E4B9.0DF6F008"
Subject: [Sipping] SIGCOMP and large binary content SIP messages
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E4B9.0DF6F008
Content-Type: text/plain;
	charset="iso-8859-1"

All,

We have had a couple of short threads on SIMPLE considering the implications
of including large binary content within SIP messages (using MIME) (by
large, I mean anything more than several times the size of a normal INVITE
and by binary, I mean arbitrary bytes, rather than text). An example would
be a JPEG or audio file. It's been suggested that a user might include one
of these as part of their presence information.

On the face of it, it seems that this might have implications for the
effectiveness of SIPCOMP, firstly because such data may not itself compress
well (compared to SIP headers and SDP), and secondly because of the impact
this might have on any dynamic dictionary.

There may be ways to design SIGCOMP compressors which can cope with this,
and if so it would be good to have some guidelines included in the SIGCOMP
documentation. This would stop people from naively designing SIGCOMP
compressors based on false assumptions about the nature of SIP messaging
(for example SIGCOMP has to date made the assumption that SIP messages are
ASCII encoded - RFC3322).

So, before raising this in ROCH, perhaps we need to discuss what those
assumptions about SIP messaging should be - i.e. to approximately define a
class of SIP messages for which app. designers can expect SIGCOMP to perform
well. Then if applications need to generate messages outside that class,
they can choose between (i) potentially poor SIGCOMP performance (which may
be acceptable in some cases) or (ii) using techniques like Content
Indirection to return their messages into the 'SIGCOMP friendly' class.

I know large content in SIP messages has been discussed before in various
contexts, but is there any chance we can come to a rough consensus on what a
'SIGCOMP-friendly' class of SIP messages should look like ?

Regards,

Mark Watson




-----Original Message-----
From: Watson, Mark [MOP:EP10:EXCH] 
Sent: 05 March 2003 10:33
To: 'mikko.lonnfors@nokia.com'; simple@ietf.org
Subject: RE: [Simple] I-D ACTION:draft-lonnfors-simple-partial-notify-00.t
xt


Mikko, All, 
The correct place to document such recommendations about SIGCOMP would be in
some ROCH documentation, perhaps the SIGCOMP User Guide ? I notice that
RFC3322 (Signalling Compression Requirements & Assumptions) already assumes
that the signalling messages are ASCII encoded, so if this is not the case I
think it's fairly urgent to get some discussion going.
Before we go to ROCH, though, we need to make some decision on what kind of
content we see being commonly included in SIP messages - i.e. what does
SIGCOMP have to deal with in addition to SIP Headers and SDP ??
To my mind this is a discussion for SIPPING - does anyone object to moving
this discussion there ? (Let's avoid creating a cross-posted thread if
possible - they're always a nightmare).
...Mark 



> -----Original Message----- 
> From: mikko.lonnfors@nokia.com [mailto:mikko.lonnfors@nokia.com] 
> Sent: 04 March 2003 10:03 
> To: Watson, Mark [MOP:EP10:EXCH]; simple@ietf.org 
> Subject: RE: [Simple] I-D 
> ACTION:draft-lonnfors-simple-partial-notify-00.txt 
> 
> 
> Hi mark, 
> 
> Inline inside <ML>: 
> 
> 
> All, 
> I am not convinced by the discussion on SIGCOMP which has 
> been introduced into this draft (Section 1.1). 
> Firstly, is this even the correct place to describe these issues ?? 
> 
> <ML> 
> Yes, you are right. To move discussion forward we needed to 
> place text somewhere and in this case only place we could 
> place it was the partial notification draft. 
> </ML> 
> 
>  If we really expect to see large binary content in SIP 
> messages, then we should document the impacts for SIGCOMP 
> somewhere more general - not buried in a presence partial 
> notifications discussion. 
> 
> <ML> 
> Yes 
> </ML> 
> 
> If we do not expect such content, we should document that 
> fact somewhere more general too. We need to make a decision 
> one way or the other because it has important implications 
> for the design of SIGCOMP compressors. 
> 
> <ML> 
> This is probably true. 
> </ML> 
> 
> Secondly, two of the solutions referred to involve the 
> SIGCOMP layer having knowledge of the content type, which is 
> a major architectural change. Presently, the SIGCOMP layer 
> does not parse SIP, MIME etc. 
> 
> <ML> 
> We have been talking about this issue with SIGCOMP author Z. 
> Liu (as at least I not an expert in this are) and these were 
> mentioned as possible solutions for this problem. I am also 
> not convinced that these two solutions are the best ones and 
> if other people feel same I am quite happy to drop them. 
> </ML> 
> 
> Thirdly, the last solution mentioned involves leaving 
> 'binary' content uncompressed, but this does not necessarily 
> mean that this content will not mess up the dynamic 
> dictionary. The compression scheme would need to detect 
> 'uncompressible' parts of the message and leave these out of 
> the dictionary. 
> 
> <ML> 
> As far as I know this should be quite easy thing to 
> accomplish for a SIGCOMP implementation. Of course it should 
> be specified (recommended) somewhere what is appropriate 
> threshold value for data which should be considered 'uncompressible'. 
> </ML> 
> 
> So, if we expect binary content in SIP, we should document 
> the impacts in SIGCOMP somewhere in the sip/sipping WGs. We 
> should decide whether we expect SIGCOMP to cope with such 
> binary content in an efficient way (i.e. if we think the same 
> content will be sent multiple times) or whether we are happy 
> for SIGCOMP to leave such content uncompressed (i.e. if we 
> think the same content will generally only be sent once). 
> 
> Finally, I think we concluded in the last discussion on this 
> that it was not appropriate to include in-line binary content 
> in the presence document itself due to encoding issues - 
> there is still some reference to this in the draft. Large 
> binary content would need to referenced from the presence 
> document, and we left it open whether this reference could be 
> to other MIME parts within the same SIP message. 
> 
> <ML> 
> Yes, this is our mistake. I also agree that large binary data 
> should not be in-line with other presence data. This will be 
> fixed in next version 
> </ML> 
> 
> Thanks for comments 
> - Mikko 
> 
> Regards, 
> Mark 
> > -----Original Message----- 
> > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
> > Sent: 24 February 2003 11:45 
> > Cc: simple@ietf.org 
> > Subject: [Simple] I-D 
> > ACTION:draft-lonnfors-simple-partial-notify-00.txt 
> > 
> > 
> > A New Internet-Draft is available from the on-line 
> > Internet-Drafts directories. 
> > 
> > 
> >       Title           : Partial Notification of Presence 
> Information 
> >       Author(s)       : J. Costa-Requena, E. Leppanen et al. 
> >       Filename        : draft-lonnfors-simple-partial-notify-00.txt 
> >       Pages           : 24 
> >       Date            : 2003-2-21 
> >       
> > A Presence service implemented using SIMPLE has some 
> constraints for 
> > delivering presence information to devices with low data processing 
> > capabilities, small display, and limited battery power. Other 
> > limitations can be caused by the interface between the terminal and 
> > the network, i.e. over radio links with high latency and low 
> > bandwidth. This memo presents a solution that aids in reducing the 
> > impact of those constrains and increasing efficiency, by 
> introducing 
> > a new MIME-type æpartial notificationsÆ and a Require header 
> > extension æpartial-notificationÆ. 
> > 
> > A URL for this Internet-Draft is: 
> > http://www.ietf.org/internet-drafts/draft-lonnfors-simple-part 
> > ial-notify-00.txt 
> > 
> > To remove yourself from the IETF Announcement list, send a 
> message to 
> > ietf-announce-request with the word unsubscribe in the body 
> > of the message. 
> > 
> > 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-lonnfors-simple-partial-notify-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-lonnfors-simple-partial-notify-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_001_01C2E4B9.0DF6F008
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>SIGCOMP and large binary content SIP messages</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>All,</FONT>
</P>

<P><FONT SIZE=3D2>We have had a couple of short threads on SIMPLE =
considering the implications of including large binary content within =
SIP messages (using MIME) (by large, I mean anything more than several =
times the size of a normal INVITE and by binary, I mean arbitrary =
bytes, rather than text). An example would be a JPEG or audio file. =
It's been suggested that a user might include one of these as part of =
their presence information.</FONT></P>

<P><FONT SIZE=3D2>On the face of it, it seems that this might have =
implications for the effectiveness of SIPCOMP, firstly because such =
data may not itself compress well (compared to SIP headers and SDP), =
and secondly because of the impact this might have on any dynamic =
dictionary.</FONT></P>

<P><FONT SIZE=3D2>There may be ways to design SIGCOMP compressors which =
can cope with this, and if so it would be good to have some guidelines =
included in the SIGCOMP documentation. This would stop people from =
naively designing SIGCOMP compressors based on false assumptions about =
the nature of SIP messaging (for example SIGCOMP has to date made the =
assumption that SIP messages are ASCII encoded - RFC3322).</FONT></P>

<P><FONT SIZE=3D2>So, before raising this in ROCH, perhaps we need to =
discuss what those assumptions about SIP messaging should be - i.e. to =
approximately define a class of SIP messages for which app. designers =
can expect SIGCOMP to perform well. Then if applications need to =
generate messages outside that class, they can choose between (i) =
potentially poor SIGCOMP performance (which may be acceptable in some =
cases) or (ii) using techniques like Content Indirection to return =
their messages into the 'SIGCOMP friendly' class.</FONT></P>

<P><FONT SIZE=3D2>I know large content in SIP messages has been =
discussed before in various contexts, but is there any chance we can =
come to a rough consensus on what a 'SIGCOMP-friendly' class of SIP =
messages should look like ?</FONT></P>

<P><FONT SIZE=3D2>Regards,</FONT>
</P>

<P><FONT SIZE=3D2>Mark Watson</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Watson, Mark [MOP:EP10:EXCH] </FONT>
<BR><FONT SIZE=3D2>Sent: 05 March 2003 10:33</FONT>
<BR><FONT SIZE=3D2>To: 'mikko.lonnfors@nokia.com'; =
simple@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Simple] I-D =
ACTION:draft-lonnfors-simple-partial-notify-00.t xt</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Mikko, All, </FONT>
<BR><FONT SIZE=3D2>The correct place to document such recommendations =
about SIGCOMP would be in some ROCH documentation, perhaps the SIGCOMP =
User Guide ? I notice that RFC3322 (Signalling Compression Requirements =
&amp; Assumptions) already assumes that the signalling messages are =
ASCII encoded, so if this is not the case I think it's fairly urgent to =
get some discussion going.</FONT></P>

<P><FONT SIZE=3D2>Before we go to ROCH, though, we need to make some =
decision on what kind of content we see being commonly included in SIP =
messages - i.e. what does SIGCOMP have to deal with in addition to SIP =
Headers and SDP ??</FONT></P>

<P><FONT SIZE=3D2>To my mind this is a discussion for SIPPING - does =
anyone object to moving this discussion there ? (Let's avoid creating a =
cross-posted thread if possible - they're always a =
nightmare).</FONT></P>

<P><FONT SIZE=3D2>...Mark </FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; From: mikko.lonnfors@nokia.com [<A =
HREF=3D"mailto:mikko.lonnfors@nokia.com">mailto:mikko.lonnfors@nokia.com=
</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 04 March 2003 10:03 </FONT>
<BR><FONT SIZE=3D2>&gt; To: Watson, Mark [MOP:EP10:EXCH]; =
simple@ietf.org </FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Simple] I-D </FONT>
<BR><FONT SIZE=3D2>&gt; =
ACTION:draft-lonnfors-simple-partial-notify-00.txt </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi mark, </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Inline inside &lt;ML&gt;: </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; All, </FONT>
<BR><FONT SIZE=3D2>&gt; I am not convinced by the discussion on SIGCOMP =
which has </FONT>
<BR><FONT SIZE=3D2>&gt; been introduced into this draft (Section 1.1). =
</FONT>
<BR><FONT SIZE=3D2>&gt; Firstly, is this even the correct place to =
describe these issues ?? </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Yes, you are right. To move discussion forward =
we needed to </FONT>
<BR><FONT SIZE=3D2>&gt; place text somewhere and in this case only =
place we could </FONT>
<BR><FONT SIZE=3D2>&gt; place it was the partial notification draft. =
</FONT>
<BR><FONT SIZE=3D2>&gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; If we really expect to see large binary =
content in SIP </FONT>
<BR><FONT SIZE=3D2>&gt; messages, then we should document the impacts =
for SIGCOMP </FONT>
<BR><FONT SIZE=3D2>&gt; somewhere more general - not buried in a =
presence partial </FONT>
<BR><FONT SIZE=3D2>&gt; notifications discussion. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Yes </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; If we do not expect such content, we should =
document that </FONT>
<BR><FONT SIZE=3D2>&gt; fact somewhere more general too. We need to =
make a decision </FONT>
<BR><FONT SIZE=3D2>&gt; one way or the other because it has important =
implications </FONT>
<BR><FONT SIZE=3D2>&gt; for the design of SIGCOMP compressors. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; This is probably true. </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Secondly, two of the solutions referred to =
involve the </FONT>
<BR><FONT SIZE=3D2>&gt; SIGCOMP layer having knowledge of the content =
type, which is </FONT>
<BR><FONT SIZE=3D2>&gt; a major architectural change. Presently, the =
SIGCOMP layer </FONT>
<BR><FONT SIZE=3D2>&gt; does not parse SIP, MIME etc. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; We have been talking about this issue with =
SIGCOMP author Z. </FONT>
<BR><FONT SIZE=3D2>&gt; Liu (as at least I not an expert in this are) =
and these were </FONT>
<BR><FONT SIZE=3D2>&gt; mentioned as possible solutions for this =
problem. I am also </FONT>
<BR><FONT SIZE=3D2>&gt; not convinced that these two solutions are the =
best ones and </FONT>
<BR><FONT SIZE=3D2>&gt; if other people feel same I am quite happy to =
drop them. </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thirdly, the last solution mentioned involves =
leaving </FONT>
<BR><FONT SIZE=3D2>&gt; 'binary' content uncompressed, but this does =
not necessarily </FONT>
<BR><FONT SIZE=3D2>&gt; mean that this content will not mess up the =
dynamic </FONT>
<BR><FONT SIZE=3D2>&gt; dictionary. The compression scheme would need =
to detect </FONT>
<BR><FONT SIZE=3D2>&gt; 'uncompressible' parts of the message and leave =
these out of </FONT>
<BR><FONT SIZE=3D2>&gt; the dictionary. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; As far as I know this should be quite easy =
thing to </FONT>
<BR><FONT SIZE=3D2>&gt; accomplish for a SIGCOMP implementation. Of =
course it should </FONT>
<BR><FONT SIZE=3D2>&gt; be specified (recommended) somewhere what is =
appropriate </FONT>
<BR><FONT SIZE=3D2>&gt; threshold value for data which should be =
considered 'uncompressible'. </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; So, if we expect binary content in SIP, we =
should document </FONT>
<BR><FONT SIZE=3D2>&gt; the impacts in SIGCOMP somewhere in the =
sip/sipping WGs. We </FONT>
<BR><FONT SIZE=3D2>&gt; should decide whether we expect SIGCOMP to cope =
with such </FONT>
<BR><FONT SIZE=3D2>&gt; binary content in an efficient way (i.e. if we =
think the same </FONT>
<BR><FONT SIZE=3D2>&gt; content will be sent multiple times) or whether =
we are happy </FONT>
<BR><FONT SIZE=3D2>&gt; for SIGCOMP to leave such content uncompressed =
(i.e. if we </FONT>
<BR><FONT SIZE=3D2>&gt; think the same content will generally only be =
sent once). </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Finally, I think we concluded in the last =
discussion on this </FONT>
<BR><FONT SIZE=3D2>&gt; that it was not appropriate to include in-line =
binary content </FONT>
<BR><FONT SIZE=3D2>&gt; in the presence document itself due to encoding =
issues - </FONT>
<BR><FONT SIZE=3D2>&gt; there is still some reference to this in the =
draft. Large </FONT>
<BR><FONT SIZE=3D2>&gt; binary content would need to referenced from =
the presence </FONT>
<BR><FONT SIZE=3D2>&gt; document, and we left it open whether this =
reference could be </FONT>
<BR><FONT SIZE=3D2>&gt; to other MIME parts within the same SIP =
message. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Yes, this is our mistake. I also agree that =
large binary data </FONT>
<BR><FONT SIZE=3D2>&gt; should not be in-line with other presence data. =
This will be </FONT>
<BR><FONT SIZE=3D2>&gt; fixed in next version </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks for comments </FONT>
<BR><FONT SIZE=3D2>&gt; - Mikko </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Regards, </FONT>
<BR><FONT SIZE=3D2>&gt; Mark </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Internet-Drafts@ietf.org [<A =
HREF=3D"mailto:Internet-Drafts@ietf.org">mailto:Internet-Drafts@ietf.org=
</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: 24 February 2003 11:45 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cc: simple@ietf.org </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: [Simple] I-D </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
ACTION:draft-lonnfors-simple-partial-notify-00.txt </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; A New Internet-Draft is available from the =
on-line </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Internet-Drafts directories. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
Partial Notification of Presence </FONT>
<BR><FONT SIZE=3D2>&gt; Information </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : J. Costa-Requena, E. =
Leppanen et al. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
draft-lonnfors-simple-partial-notify-00.txt </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 24 =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
: 2003-2-21 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; A Presence service implemented using =
SIMPLE has some </FONT>
<BR><FONT SIZE=3D2>&gt; constraints for </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; delivering presence information to devices =
with low data processing </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; capabilities, small display, and limited =
battery power. Other </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; limitations can be caused by the interface =
between the terminal and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the network, i.e. over radio links with =
high latency and low </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; bandwidth. This memo presents a solution =
that aids in reducing the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; impact of those constrains and increasing =
efficiency, by </FONT>
<BR><FONT SIZE=3D2>&gt; introducing </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; a new MIME-type =E6partial =
notifications=C6 and a Require header </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; extension =E6partial-notification=C6. =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; A URL for this Internet-Draft is: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-lonnfors-simple-part" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-lonnfors-sim=
ple-part</A> </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ial-notify-00.txt </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To remove yourself from the IETF =
Announcement list, send a </FONT>
<BR><FONT SIZE=3D2>&gt; message to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ietf-announce-request with the word =
unsubscribe in the body </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; of the message. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Internet-Drafts are also available by =
anonymous FTP. Login </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; with the username </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &quot;anonymous&quot; and a password of =
your e-mail address. After </FONT>
<BR><FONT SIZE=3D2>&gt; logging in, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; type &quot;cd internet-drafts&quot; and =
then </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;get draft-lonnfors-simple-partial-notify-00.txt&quot;. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; A list of Internet-Drafts directories can =
be found in </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"http://www.ietf.org/shadow.html" =
TARGET=3D"_blank">http://www.ietf.org/shadow.html</A> </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; or <A =
HREF=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" =
TARGET=3D"_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</A> </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Internet-Drafts can also be obtained by =
e-mail. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Send a message to: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
mailserv@ietf.org. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; In the body type: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;FILE </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
/internet-drafts/draft-lonnfors-simple-partial-notify-00.txt&quot;. =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; NOTE: The mail server at ietf.org can =
return the document in </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MIME-encoded form by using the &quot;mpack&quot; utility.&nbsp; To use =
this </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
feature, insert the command &quot;ENCODING mime&quot; before the =
&quot;FILE&quot; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
command.&nbsp; To decode the response(s), you will need </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;munpack&quot; or </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a =
MIME-compliant mail reader.&nbsp; Different MIME-compliant </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; mail readers </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
exhibit different behavior, especially when dealing with </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;multipart&quot; MIME messages (i.e. documents which have </FONT>
<BR><FONT SIZE=3D2>&gt; been split </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; up =
into multiple messages), so check your local </FONT>
<BR><FONT SIZE=3D2>&gt; documentation on </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to =
manipulate these messages. </FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Below is the data which will enable a MIME =
compliant mail reader </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; implementation to automatically retrieve =
the ASCII version of the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Internet-Draft. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E4B9.0DF6F008--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 10:04:42 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08189
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 10:04:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27FGGu02261
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 10:16:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27FGGO02258
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 10:16:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08122
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 10:04:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27FEhO02041;
	Fri, 7 Mar 2003 10:14:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27F6DO00434
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 10:06:13 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07199;
	Fri, 7 Mar 2003 09:54:09 -0500 (EST)
Message-Id: <200303071454.JAA07199@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 09:54:09 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-mwi-02.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: A Message Summary and Message Waiting 
			  Indication Event Package for the Session 
			  Initiation Protocol (SIP)
	Author(s)	: R. Mahy
	Filename	: draft-ietf-sipping-mwi-02.txt
	Pages		: 21
	Date		: 2003-3-6
	
This draft proposes a SIP event package to carry message waiting
status and message summaries from a messaging system to an interested
User Agent.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sipping-mwi-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-sipping-mwi-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:	<2003-3-6175211.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-mwi-02.txt

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

Content-Type: text/plain
Content-ID:	<2003-3-6175211.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 11:06:55 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12623
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 11:06:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27GISt08342
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 11:18:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27GISO08339
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 11:18:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12605
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 11:06:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27GHJO08268;
	Fri, 7 Mar 2003 11:17:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27GE1O08117
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 11:14:01 -0500
Received: from dgesmtp02.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12520
	for <sipping@ietf.org>; Fri, 7 Mar 2003 11:01:57 -0500 (EST)
Received: from pmismtp02.wcomnet.com ([166.38.62.37])
 by firewall.wcom.com (Iplanet MTA )
 with ESMTP id <0HBD002AFZ8C99@firewall.wcom.com> for sipping@ietf.org; Fri,
 07 Mar 2003 16:02:36 +0000 (GMT)
Received: from pmismtp02.wcomnet.com by pmismtp02.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HBD00001Z8BEV@pmismtp02.wcomnet.com> for sipping@ietf.org; Fri,
 07 Mar 2003 16:02:36 +0000 (GMT)
Received: from ajohnston.wcom.com ([166.50.138.136])
 by pmismtp02.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HBD0005MZ8A79@pmismtp02.wcomnet.com> for
 sipping@ietf.org; Fri, 07 Mar 2003 16:02:35 +0000 (GMT)
Date: Fri, 07 Mar 2003 10:01:30 -0600
From: Alan Johnston <alan.johnston@wcom.com>
X-Sender: Alan.Johnston@pop.mcit.com
To: sipping@ietf.org
Message-id: <5.1.1.6.0.20030307092804.01ed89d0@pop.mcit.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset=us-ascii; format=flowed
Subject: [Sipping] Conferencing Design Team Update
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

All,

The past few months have been very busy for the conferencing design team 
and I'm happy to report on the work.

Three Internet-Drafts have been updated recently:

-  "High Level Requirements for Tightly Coupled SIP Conferencing " 
(http://www.ietf.org/internet-drafts/draft-levin-sipping-conferencing-requirements-03.txt)

- "A Framework for Conferencing with the Session Initiation Protocol" 
(http://www.ietf.org/internet-drafts/draft-rosenberg-sipping-conferencing-framework-01.txt)

- "Session Initiation Protocol Call Control - Conferencing for User Agents" 
(http://www.ietf.org/internet-drafts/draft-johnston-sipping-cc-conferencing-01.txt)

These three documents outline the requirements, framework, and SIP call 
control operations for tightly coupled SIP conferences and now should now 
be aligned in terms of terminology and approach.

These documents have had significant review within the team and the team 
believes they are ready for consideration as working group items.

Newly submitted design team documents include:

  - "Requirements for Conference Policy Data" 
(http://www.ietf.org/internet-drafts/draft-koskelainen-sipping-conf-policy-req-00.txt)

  - "Conferencing Media Policy Requirements" 
(http://www.ietf.org/internet-drafts/draft-even-sipping-media-policy-requirements-00.txt)

  -  "Media Policy Manipulation in the Conference Policy Control Protocol" 
(http://www.ietf.org/internet-drafts/draft-mahy-sipping-media-policy-control-00.txt)

These documents are still in the early stages but are a good reflection of 
the direction being taken by the design team.  Feedback from the working 
group is most welcome on these drafts.

Other related documents that are not direct output of the design team but 
relate to conferencing include:

  - "A Session Initiation Protocol (SIP) Event Package for Conference 
State" 
(http://www.ietf.org/internet-drafts/draft-ietf-sipping-conference-package-00.txt)

  -  "Caller Preferences and Callee Capabilities for the Session Initiation 
Protocol (SIP)" 
(http://www.ietf.org/internet-drafts/draft-ietf-sip-callerprefs-08.txt) 
which contains the definition of the "isfocus" feature tag.

  - "Requirements for Floor 
Control" 
(http://www.ietf.org/internet-drafts/draft-koskelainen-mmusic-floor-req-01.txt)

  -  "Use of Session Initiation Protocol (SIP) and Simple Object Access 
Protocol (SOAP) for Conference Floor Control" 
(http://www.ietf.org/internet-drafts/draft-wu-sipping-floor-control-04.txt)

At IETF-56, we plan to discuss the status of the design team drafts and the 
open issues associated with this topic.

Thanks to the entire design team for their hard work on this topic.

To follow the progress of this work including working documents use: 
http://ee.wustl.edu/~alan/sip-conf

Thanks,
Alan Johnston
WorldCom
sip:alan@digitalari.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 11:40:43 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15386
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 11:40:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27GqHk11441
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 11:52:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27GqHO11438
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 11:52:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15309
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 11:40:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27GpNO11400;
	Fri, 7 Mar 2003 11:51:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27GocO11370
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 11:50:38 -0500
Received: from rtp-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15266
	for <sipping@ietf.org>; Fri, 7 Mar 2003 11:38:33 -0500 (EST)
Received: from cia.cisco.com (IDENT:mirapoint@cia.cisco.com [161.44.85.200])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h27GeYSc006655;
	Fri, 7 Mar 2003 11:40:35 -0500 (EST)
Received: from mhammer-w2k02.cisco.com (hrn2-dhcp-161-44-87-89.cisco.com [161.44.87.89])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABR03067;
	Fri, 7 Mar 2003 11:30:38 -0500 (EST)
Message-Id: <4.3.2.7.2.20030307113421.00b6c6d8@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 07 Mar 2003 11:40:14 -0500
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
From: Michael Hammer <mhammer@cisco.com>
Subject: Re: [Sipping] New version of the early media draft
Cc: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        Mark Watson <mwatson@nortelnetworks.com>, sipping <sipping@ietf.org>,
        Francois Audet <audet@nortelnetworks.com>
In-Reply-To: <3E685CC3.25E602D3@lmf.ericsson.se>
References: <15A2739B7DAA624D8091C65981D7DA8101214ECA@stntexch2.va.neustar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Gonzalo,

So the sequence is:

1) Receive 180, beep, wait 1 second,
    if media,    play media,
    if no media, play local ring-back.

2) While playing local ring-back,
    if media arrives, cut off local ring-back and play media.

Rationale for step 2:  Absent this, there is a race condition between 200 
OK and real media (versus in-band signals) leading to temporal clipping.

Mike

At 10:48 AM 3/7/2003 +0200, Gonzalo Camarillo wrote:
>Folks,
>
>I agree with Jon that we should not encourage people to send in-band
>ringing tones, but I also agree with Mark that this issue has
>re-surfaced a number of times already. The message we want to get
>through is that adding a SIP flag for resolving that issue offers little
>or no value.
>
>I am willing, if people agree, to add some text saying why it is not a
>good idea to add a SIP-layer flag to 180 responses indicating that media
>is coming.
>
>What about a section along these lines:?
>
>2.2.1 Problems with SIP-layer Indications in 180 Responses
>
>As stated above, it is not an easy task for a UAC that receives a 180
>(Ringing) response to decide whether it should generate local ringback
>or it will be receiving early media. At first sight, it may seem that
>adding a "there is media coming" indication to 180 (Ringing) responses
>would facilitate the task of UACs. Upon reception of a 180 (Ringing)
>response with such an indication, the UAC would not generate local
>ringback. However, such an indication would offer little or no gain.
>
>The only scenario where such an indication would be applicable is when
>the UAS sends a 180 (Ringing) response and starts sending early media
>right away. If the UAS intended to send early media at a later time,
>instead of right away, a sensible local policy for the UAC could be to
>generate local ringback in the meantime. Therefore, the "there is media
>coming" indication would be useless.
>
>Assuming, then, that the UAS sends the 180 (Ringing) response and the
>first media packets in parallel towards the UAC, we have a race
>condition. If the media packets arrive at the UAC before the 180
>(Ringing) response, the "there is media coming" indication will not
>provide any further information to the UAC.
>
>The only situation where the UAC could benefit from that indication is
>when the 180 (Ringing) response arrives before the first media packets.
>The UAC could avoid generating local ringback for an instant before the
>first media packets arrive. However, the same result can be achieved in
>a much simpler way (without protocol extensions) by just having UACs
>always delay the generation of local ringback for a short period of
>time. The UAC can, for instance, generate a short beep upon reception of
>the 180 (Ringing) response (this is already done by some
>circuit-switched mobile terminals) and one second later start generating
>local ringback if no media have been received during that period.
>
>\motivation{Note that adding such an indication does not keep UACs from
>implementing media arrival detection either, since they have to
>implement it anyway to cover other scenarios, like the race condition
>between the 200 OK for the INVITE and the first regular media packets).}
>
>
>Opinions?
>
>Gonzalo
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 12:07:21 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16991
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 12:07:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27HIuR14598
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 12:18:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27HIuO14593
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 12:18:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16925
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 12:06:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27HHcO14356;
	Fri, 7 Mar 2003 12:17:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27H1GO11965
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 12:01:16 -0500
Received: from rtp-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15855
	for <sipping@ietf.org>; Fri, 7 Mar 2003 11:49:10 -0500 (EST)
Received: from cia.cisco.com (IDENT:mirapoint@cia.cisco.com [161.44.85.200])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h27GpCSc008255;
	Fri, 7 Mar 2003 11:51:13 -0500 (EST)
Received: from mhammer-w2k02.cisco.com (hrn2-dhcp-161-44-87-89.cisco.com [161.44.87.89])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABR03170;
	Fri, 7 Mar 2003 11:41:12 -0500 (EST)
Message-Id: <4.3.2.7.2.20030307114533.00ba3d08@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 07 Mar 2003 11:51:07 -0500
To: "Mark Watson" <mwatson@nortelnetworks.com>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] New version of the early media draft
Cc: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>,
        "Francois Audet" <audet@nortelnetworks.com>
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7C4C@zwcwd00r.europe.n
 ortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Mark,

I understand the essence of your problem is not the signaling that RTP 
packets are flowing, but signaling the intent of the downstream switch to 
insert meaningful content into the RTP stream.

The 180 alone does not convey this signaling information.  Nor can this 
signaling information be inferred from the receipt of an RTP packet flow 
(absent the ability to detect all possible announcements/signals used 
around the world).

What you are saying is that this signaling information is presented at the 
IWF, but there is no signaling element to map it to.  Thus this feature 
must be terminated at the IWF.

Mike


At 10:02 AM 3/7/2003 +0000, Mark Watson wrote:

>Gonzalo,
>
>The 200 OK vs RTP packet race condition is a smaller problem than 
>correctly deciding whether to play in-band media or local ringing. It 
>doesn't necessarily justify media detection at the MG anyway (or rather. 
>the MG taking 'autonomous' action on the basis of media detecion, which is 
>the problematic part) .
>
>I don't think that cutting through the actual media just on the basis of 
>receipt of a media packet would be an acceptable solution in some (common) 
>business models anyway - they will want to wait for the 200 OK before 
>cutting through media. If that results in speech clipping then your RTT is 
>probably too long for acceptable speech quality anyway.
>
>Also, as a general layering principle, I think it is bad to attach 
>semantics to the presence/absence of RTP packets - the expected state of 
>the media stream should be completely known to the endpoints based on the 
>SIP/SDP negotiations. This surely makes the system more robust and assists 
>debugging because it allows be to detect an error case where I am 
>expecting to receive media but do not.
>
>I am confused by the resistance to solving this problem in the 
>straightforward way. The existance of in-band media seems a perfectly 
>reasonable thing to want to signal at the SIP layer. People seem quite 
>happy to give the 183 message this semantic, for the case where the call 
>state is unknown - why is it such a big deal to convey the *same 
>information* at the SIP layer for the case where the call state is known 
>to be alerting ?? All I want to do is atomically signal the equivalent of 
>180 *plus* 183.
>
>...Mark
>
> > -----Original Message-----
> > From: Gonzalo Camarillo 
> [<mailto:Gonzalo.Camarillo@lmf.ericsson.se>mailto:Gonzalo.Camarillo@lmf.ericsson.se] 
>
> > Sent: 07 March 2003 09:27
> > To: Watson, Mark [MOP:EP10:EXCH]
> > Cc: Peterson, Jon; 'Ejzak, Richard P (Richard)'; sipping; Audet,
> > Francois [SC100:4K02:EXCH]
> > Subject: Re: [Sipping] New version of the early media draft
> >
> >
> > Mark,
> >
> > the text says that such a flag would not solve that issue, because you
> > have to implement media detection *anyway* for covering other
> > scenarios
> > (motivational paragraph at the bottom).
> >
> > > I still think this problem remains unsolved.
> >
> > The point is that such a flag would not solve it either.
> >
> > Gonzalo
> >
> > Mark Watson wrote:
> > >
> > > Gonzalo,
> > >
> > > Your text does not recognise the desire to avoid reading
> > semantics in
> > > to the arrival of RTP packets, to cope with the MGC/MG scenario.
> > >
> > > I still think this problem remains unsolved.
> > >
> > > ...Mark
> > >
> > > > -----Original Message-----
> > > > From: Gonzalo Camarillo 
> [<mailto:Gonzalo.Camarillo@lmf.ericsson.se>mailto:Gonzalo.Camarillo@lmf.ericsson.se] 
>
> > > > Sent: 07 March 2003 08:48
> > > > To: Peterson, Jon
> > > > Cc: 'Ejzak, Richard P (Richard)'; Watson, Mark
> > > > [MOP:EP10:EXCH]; sipping;
> > > > Audet, Francois [SC100:4K02:EXCH]
> > > > Subject: Re: [Sipping] New version of the early media draft
> > > >
> > > >
> > > > Folks,
> > > >
> > > > I agree with Jon that we should not encourage people to
> > send in-band
> > >
> > > > ringing tones, but I also agree with Mark that this issue has
> > > > re-surfaced a number of times already. The message we want to get
> > > > through is that adding a SIP flag for resolving that issue
> > > > offers little
> > > > or no value.
> > > >
> > > > I am willing, if people agree, to add some text saying
> > why it is not
> > > a
> > > > good idea to add a SIP-layer flag to 180 responses indicating
> > > > that media
> > > > is coming.
> > > >
> > > > What about a section along these lines:?
> > > >
> > > > 2.2.1 Problems with SIP-layer Indications in 180 Responses
> > > >
> > > > As stated above, it is not an easy task for a UAC that receives a
> > > 180
> > > > (Ringing) response to decide whether it should generate local
> > > ringback
> > > > or it will be receiving early media. At first sight, it may seem
> > > that
> > > > adding a "there is media coming" indication to 180 (Ringing)
> > > responses
> > > > would facilitate the task of UACs. Upon reception of a
> > 180 (Ringing)
> > >
> > > > response with such an indication, the UAC would not generate local
> > > > ringback. However, such an indication would offer little
> > or no gain.
> > >
> > > >
> > > > The only scenario where such an indication would be applicable is
> > > when
> > > > the UAS sends a 180 (Ringing) response and starts sending early
> > > media
> > > > right away. If the UAS intended to send early media at a
> > later time,
> > >
> > > > instead of right away, a sensible local policy for the
> > UAC could be
> > > to
> > > > generate local ringback in the meantime. Therefore, the
> > > > "there is media
> > > > coming" indication would be useless.
> > > >
> > > > Assuming, then, that the UAS sends the 180 (Ringing) response and
> > > the
> > > > first media packets in parallel towards the UAC, we have a race
> > > > condition. If the media packets arrive at the UAC before the 180
> > > > (Ringing) response, the "there is media coming"
> > indication will not
> > > > provide any further information to the UAC.
> > > >
> > > > The only situation where the UAC could benefit from that
> > indication
> > > is
> > > > when the 180 (Ringing) response arrives before the first
> > > > media packets.
> > > > The UAC could avoid generating local ringback for an instant
> > > > before the
> > > > first media packets arrive. However, the same result can be
> > > > achieved in
> > > > a much simpler way (without protocol extensions) by just
> > having UACs
> > >
> > > > always delay the generation of local ringback for a short
> > period of
> > > > time. The UAC can, for instance, generate a short beep upon
> > > > reception of
> > > > the 180 (Ringing) response (this is already done by some
> > > > circuit-switched mobile terminals) and one second later start
> > > > generating
> > > > local ringback if no media have been received during that period.
> > > >
> > > > \motivation{Note that adding such an indication does not keep
> > > > UACs from
> > > > implementing media arrival detection either, since they have to
> > > > implement it anyway to cover other scenarios, like the race
> > > condition
> > > > between the 200 OK for the INVITE and the first regular media
> > > > packets).}
> > > >
> > > >
> > > > Opinions?
> > > >
> > > > Gonzalo
> > > >
> >
> > --
> > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > Telecom R&D               Fax   :  +358  9 299 30 52
> > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> > 
> Finland 
> <http://www.hut.fi/~gonzalo>http://www.hut.fi/~gonzalo
> >

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 12:22:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18266
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 12:22:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27HY3l16628
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 12:34:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27HY3O16625
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 12:34:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18239
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 12:21:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27HWCO16438;
	Fri, 7 Mar 2003 12:32:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27HVmO16351
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 12:31:48 -0500
Received: from rtp-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18076
	for <sipping@ietf.org>; Fri, 7 Mar 2003 12:19:41 -0500 (EST)
Received: from cia.cisco.com (IDENT:mirapoint@cia.cisco.com [161.44.85.200])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h27HLhSc012330;
	Fri, 7 Mar 2003 12:21:43 -0500 (EST)
Received: from mhammer-w2k02.cisco.com (hrn2-dhcp-161-44-87-89.cisco.com [161.44.87.89])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABR03473;
	Fri, 7 Mar 2003 12:11:46 -0500 (EST)
Message-Id: <4.3.2.7.2.20030307120836.04310390@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 07 Mar 2003 12:21:40 -0500
To: "Mark Watson" <mwatson@nortelnetworks.com>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] New version of the early media draft
Cc: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>,
        "Francois Audet" <audet@nortelnetworks.com>
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7C54@zwcwd00r.europe.n
 ortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Mark,

If the rule is to play media immediately upon receipt, then the need to 
signal that signaling content in the media is moot. The local ring-back 
would be over-ridden anyway.

What I am not so certain of is the opposite case when RTP is cut-through, 
but no in-band ringing is provided by the destination PSTN switch (is this 
normal; do we care?):

1) There is no ring-back (or maybe 1 ring), the user listens to dead air 
for some time, and eventually the person comes on line.  (This can happen 
in quick pickup cases.)

2) There is no ring-back (or maybe 1 ring), the user listens to dead air 
for some time (could be minutes) until an announcement or special tone 
comes, or the call is simply released.

Did I cover the proposed approach correctly?

Mike


At 01:59 PM 3/7/2003 +0000, Mark Watson wrote:

>Gonzalo,
>
>I didn't say that media clipping was not a problem, or that I was 
>concerned only with systems which did not care about media clipping. I 
>just said that media clipping was not the problem I was addressing here.
>
>The problem I am addressing here is how an MGC decides whether to instruct 
>it's MG to play local ringing or to play media.
>
>Your argument seems to be something along the lines of:
>1) Because of the media clipping problem, the MG will need to detect 
>in-band media, and
>2) this also provides a solution to the MGC/MG ringback problem, because 
>either
>2a) the MG can override local ringback with the detected media, or
>2b) the MG can report the detected media to the MGC, which can instruct 
>the MG to play it
>
>I am saying that, **whether or not (1) is true**, (2) is not. We can argue 
>about whether or not (1) is true, are there other solutions to media 
>clipping etc., but that is not the issue.
>
>Neither 2a not 2b provide an acceptable general solution to this problem 
>=> (2a) involves inappropriate autonomy for the MG and 2b is not supported 
>in the standards right now and IMO a little kludgy. Further, both 2a and 
>2b seem to be inappropriate architecturally since they attach symantics to 
>the arrival of the RTP data.
>
>Further, there is scope in the current specs for TDM gateways which send 
>backwards media right from the off, which may contain silence - do I need 
>to look inside the RTP packets to see if there is 'real' media there ?
>
>So, I rather think it is *your* solution which is not general. Addition of 
>a functional indication of in-band media at the SIP layer would ensure we 
>have a solution to this problem in all cases.
>
>Regards...Mark
>
>
> > -----Original Message-----
> > From: Gonzalo Camarillo 
> [<mailto:Gonzalo.Camarillo@lmf.ericsson.se>mailto:Gonzalo.Camarillo@lmf.ericsson.se] 
>
> > Sent: 07 March 2003 12:31
> > To: Watson, Mark [MOP:EP10:EXCH]
> > Cc: Peterson, Jon; 'Ejzak, Richard P (Richard)'; sipping; Audet,
> > Francois [SC100:4K02:EXCH]
> > Subject: Re: [Sipping] New version of the early media draft
> >
> >
> > Mark,
> >
> > OK, now I think I understand you. You want to develop a flag
> > to be used
> > by systems that do not care about media clipping (they are
> > probably in a
> > controlled environment without race conditions) but care about not
> > having to perform media detection (because they are distributed;
> > MGC-MG).
> >
> > One of the assumption when designing SIP was that systems cared about
> > media clipping... I do not think we can develop general extensions at
> > this point in time that cause media clipping in order to
> > resolve things
> > like ringback generation.
> >
> > You may want to create a document that defines a P-flag and
> > says: if you
> > do not care about media clipping for some reason, use this
> > flag to have
> > accurate information in the SIP layer about the presence of media.
> >
> > I understand what you are after, but I do not think we have a
> > *general*
> > mechanism that resolves it.
> >
> > Gonzalo
> >
> >
> >
> > Mark Watson wrote:
> > >
> > > > Mark,
> > > >
> > > > If I understood your mail correctly, you acknowledge that
> > when race
> > > > conditions are possible, a "there is media coming" does not solve
> > > > anything.
> > >
> > > No, I acknowledge it doesn't solve the race conditions.
> > >
> > > > But you believe that in environments where you are sure that
> > > > no race conditions will occur, such a flag would be useful.
> > > >
> > >
> > > No, I am saying that the solution that you have proposed is not
> > > appropriate for a decomposed Media Gateway/Media Gateway Controller
> > > case. I acknowledge that the race condition problem still exists in
> > > that case (e.g. at answer), but I still think the media detection
> > > solution is not appropriate. So, perhaps the race condition problem
> > > remains unsolved in that case, but I am not so concerned about that
> > > problem.
> > >
> > > > However, we do not design SIP with that type of environments in
> > > mind.
> > > > Any SIP mechanism should work assuming that SIP-RTP race
> > conditions
> > > > occur.
> > > >
> > >
> > > Of course not, but surely we do design SIP in a way which
> > can work on
> > > a gateway designed according to other IETF standards for gateways
> > > (specifically megaco) ?
> > >
> > > Even if you do want to assume a monolithic SIP UA, then I
> > still think
> > > it's valuable to pay attention to the layering in the
> > system. I still
> > > believe it's more robust if the media stream state is known at the
> > > signalling layer.
> > >
> > > > Maybe you are after a P-flag to use in close environments
> > where SIP
> > > > signalling always beat RTP packets?
> > > >
> > >
> > > Not exactly. The SIP message does not need to beat the RTP packet
> > > anyway. There are well-established standards which imply acceptable
> > > times within which cut-through should occur at answer, for example.
> >

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 12:23:39 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18332
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 12:23:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27HZF116795
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 12:35:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27HZEO16792
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 12:35:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18307
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 12:23:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27HY6O16652;
	Fri, 7 Mar 2003 12:34:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27HX1O16557
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 12:33:01 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18205
	for <sipping@ietf.org>; Fri, 7 Mar 2003 12:20:52 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27HMr408257;
	Fri, 7 Mar 2003 12:22:53 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27HMoL29139;
	Fri, 7 Mar 2003 17:22:50 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id G3575755; Fri, 7 Mar 2003 17:22:50 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FS3963X2>; Fri, 7 Mar 2003 17:22:50 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C5C@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Michael Hammer'" <mhammer@cisco.com>
Cc: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        sipping <sipping@ietf.org>,
        "Francois Audet" <audet@nortelnetworks.com>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 7 Mar 2003 17:22:41 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E4CD.961F4318"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E4CD.961F4318
Content-Type: text/plain;
	charset="iso-8859-1"

Mike wrote:


> Mark,
> 
> I understand the essence of your problem is not the signaling 
> that RTP 
> packets are flowing, but signaling the intent of the 
> downstream switch to 
> insert meaningful content into the RTP stream.
> 

Well, it's both, really. The 'intent to insert meaningful content' is the
clearest, but even if we knew that gateways didn't send 'meaningless'
content (i.e. that they *only* sent RTP with meaningful content), then I
still think that using the RTP packet itself as an indication is putting the
function at the wrong layer.

> The 180 alone does not convey this signaling information.  
> Nor can this 
> signaling information be inferred from the receipt of an RTP 
> packet flow 
> (absent the ability to detect all possible announcements/signals used 
> around the world).
> 
> What you are saying is that this signaling information is 
> presented at the 
> IWF, but there is no signaling element to map it to. 

Yes.

> Thus 
> this feature 
> must be terminated at the IWF.
> 

...or a new signalling element defined to carry it. I vote for a new
signalling element because I believe the information is useful to the UAC,
especially if the UAC is a decomposed gateway.

> Mike
> 
> 
> At 10:02 AM 3/7/2003 +0000, Mark Watson wrote:
> 
> >Gonzalo,
> >
> >The 200 OK vs RTP packet race condition is a smaller problem than 
> >correctly deciding whether to play in-band media or local 
> ringing. It 
> >doesn't necessarily justify media detection at the MG anyway 
> (or rather. 
> >the MG taking 'autonomous' action on the basis of media 
> detecion, which is 
> >the problematic part) .
> >
> >I don't think that cutting through the actual media just on 
> the basis of 
> >receipt of a media packet would be an acceptable solution in 
> some (common) 
> >business models anyway - they will want to wait for the 200 
> OK before 
> >cutting through media. If that results in speech clipping 
> then your RTT is 
> >probably too long for acceptable speech quality anyway.
> >
> >Also, as a general layering principle, I think it is bad to attach 
> >semantics to the presence/absence of RTP packets - the 
> expected state of 
> >the media stream should be completely known to the endpoints 
> based on the 
> >SIP/SDP negotiations. This surely makes the system more 
> robust and assists 
> >debugging because it allows be to detect an error case where I am 
> >expecting to receive media but do not.
> >
> >I am confused by the resistance to solving this problem in the 
> >straightforward way. The existance of in-band media seems a 
> perfectly 
> >reasonable thing to want to signal at the SIP layer. People 
> seem quite 
> >happy to give the 183 message this semantic, for the case 
> where the call 
> >state is unknown - why is it such a big deal to convey the *same 
> >information* at the SIP layer for the case where the call 
> state is known 
> >to be alerting ?? All I want to do is atomically signal the 
> equivalent of 
> >180 *plus* 183.
> >
> >...Mark
> >
> > > -----Original Message-----
> > > From: Gonzalo Camarillo 
> > 
> [<mailto:Gonzalo.Camarillo@lmf.ericsson.se>mailto:Gonzalo.Cama
> rillo@lmf.ericsson.se] 
> >
> > > Sent: 07 March 2003 09:27
> > > To: Watson, Mark [MOP:EP10:EXCH]
> > > Cc: Peterson, Jon; 'Ejzak, Richard P (Richard)'; sipping; Audet,
> > > Francois [SC100:4K02:EXCH]
> > > Subject: Re: [Sipping] New version of the early media draft
> > >
> > >
> > > Mark,
> > >
> > > the text says that such a flag would not solve that 
> issue, because you
> > > have to implement media detection *anyway* for covering other
> > > scenarios
> > > (motivational paragraph at the bottom).
> > >
> > > > I still think this problem remains unsolved.
> > >
> > > The point is that such a flag would not solve it either.
> > >
> > > Gonzalo
> > >
> > > Mark Watson wrote:
> > > >
> > > > Gonzalo,
> > > >
> > > > Your text does not recognise the desire to avoid reading
> > > semantics in
> > > > to the arrival of RTP packets, to cope with the MGC/MG scenario.
> > > >
> > > > I still think this problem remains unsolved.
> > > >
> > > > ...Mark
> > > >
> > > > > -----Original Message-----
> > > > > From: Gonzalo Camarillo 
> > 
> [<mailto:Gonzalo.Camarillo@lmf.ericsson.se>mailto:Gonzalo.Cama
> rillo@lmf.ericsson.se] 
> >
> > > > > Sent: 07 March 2003 08:48
> > > > > To: Peterson, Jon
> > > > > Cc: 'Ejzak, Richard P (Richard)'; Watson, Mark
> > > > > [MOP:EP10:EXCH]; sipping;
> > > > > Audet, Francois [SC100:4K02:EXCH]
> > > > > Subject: Re: [Sipping] New version of the early media draft
> > > > >
> > > > >
> > > > > Folks,
> > > > >
> > > > > I agree with Jon that we should not encourage people to
> > > send in-band
> > > >
> > > > > ringing tones, but I also agree with Mark that this issue has
> > > > > re-surfaced a number of times already. The message we 
> want to get
> > > > > through is that adding a SIP flag for resolving that issue
> > > > > offers little
> > > > > or no value.
> > > > >
> > > > > I am willing, if people agree, to add some text saying
> > > why it is not
> > > > a
> > > > > good idea to add a SIP-layer flag to 180 responses indicating
> > > > > that media
> > > > > is coming.
> > > > >
> > > > > What about a section along these lines:?
> > > > >
> > > > > 2.2.1 Problems with SIP-layer Indications in 180 Responses
> > > > >
> > > > > As stated above, it is not an easy task for a UAC 
> that receives a
> > > > 180
> > > > > (Ringing) response to decide whether it should generate local
> > > > ringback
> > > > > or it will be receiving early media. At first sight, 
> it may seem
> > > > that
> > > > > adding a "there is media coming" indication to 180 (Ringing)
> > > > responses
> > > > > would facilitate the task of UACs. Upon reception of a
> > > 180 (Ringing)
> > > >
> > > > > response with such an indication, the UAC would not 
> generate local
> > > > > ringback. However, such an indication would offer little
> > > or no gain.
> > > >
> > > > >
> > > > > The only scenario where such an indication would be 
> applicable is
> > > > when
> > > > > the UAS sends a 180 (Ringing) response and starts 
> sending early
> > > > media
> > > > > right away. If the UAS intended to send early media at a
> > > later time,
> > > >
> > > > > instead of right away, a sensible local policy for the
> > > UAC could be
> > > > to
> > > > > generate local ringback in the meantime. Therefore, the
> > > > > "there is media
> > > > > coming" indication would be useless.
> > > > >
> > > > > Assuming, then, that the UAS sends the 180 (Ringing) 
> response and
> > > > the
> > > > > first media packets in parallel towards the UAC, we 
> have a race
> > > > > condition. If the media packets arrive at the UAC 
> before the 180
> > > > > (Ringing) response, the "there is media coming"
> > > indication will not
> > > > > provide any further information to the UAC.
> > > > >
> > > > > The only situation where the UAC could benefit from that
> > > indication
> > > > is
> > > > > when the 180 (Ringing) response arrives before the first
> > > > > media packets.
> > > > > The UAC could avoid generating local ringback for an instant
> > > > > before the
> > > > > first media packets arrive. However, the same result can be
> > > > > achieved in
> > > > > a much simpler way (without protocol extensions) by just
> > > having UACs
> > > >
> > > > > always delay the generation of local ringback for a short
> > > period of
> > > > > time. The UAC can, for instance, generate a short beep upon
> > > > > reception of
> > > > > the 180 (Ringing) response (this is already done by some
> > > > > circuit-switched mobile terminals) and one second later start
> > > > > generating
> > > > > local ringback if no media have been received during 
> that period.
> > > > >
> > > > > \motivation{Note that adding such an indication does not keep
> > > > > UACs from
> > > > > implementing media arrival detection either, since 
> they have to
> > > > > implement it anyway to cover other scenarios, like the race
> > > > condition
> > > > > between the 200 OK for the INVITE and the first regular media
> > > > > packets).}
> > > > >
> > > > >
> > > > > Opinions?
> > > > >
> > > > > Gonzalo
> > > > >
> > >
> > > --
> > > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > > Telecom R&D               Fax   :  +358  9 299 30 52
> > > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> > > 
> > Finland 
> > <http://www.hut.fi/~gonzalo>http://www.hut.fi/~gonzalo
> > >
> 
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Mike wrote:</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; Mark,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I understand the essence of your problem is not =
the signaling </FONT>
<BR><FONT SIZE=3D2>&gt; that RTP </FONT>
<BR><FONT SIZE=3D2>&gt; packets are flowing, but signaling the intent =
of the </FONT>
<BR><FONT SIZE=3D2>&gt; downstream switch to </FONT>
<BR><FONT SIZE=3D2>&gt; insert meaningful content into the RTP =
stream.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>Well, it's both, really. The 'intent to insert =
meaningful content' is the clearest, but even if we knew that gateways =
didn't send 'meaningless' content (i.e. that they *only* sent RTP with =
meaningful content), then I still think that using the RTP packet =
itself as an indication is putting the function at the wrong =
layer.</FONT></P>

<P><FONT SIZE=3D2>&gt; The 180 alone does not convey this signaling =
information.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; Nor can this </FONT>
<BR><FONT SIZE=3D2>&gt; signaling information be inferred from the =
receipt of an RTP </FONT>
<BR><FONT SIZE=3D2>&gt; packet flow </FONT>
<BR><FONT SIZE=3D2>&gt; (absent the ability to detect all possible =
announcements/signals used </FONT>
<BR><FONT SIZE=3D2>&gt; around the world).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; What you are saying is that this signaling =
information is </FONT>
<BR><FONT SIZE=3D2>&gt; presented at the </FONT>
<BR><FONT SIZE=3D2>&gt; IWF, but there is no signaling element to map =
it to. </FONT>
</P>

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

<P><FONT SIZE=3D2>&gt; Thus </FONT>
<BR><FONT SIZE=3D2>&gt; this feature </FONT>
<BR><FONT SIZE=3D2>&gt; must be terminated at the IWF.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>...or a new signalling element defined to carry it. I =
vote for a new signalling element because I believe the information is =
useful to the UAC, especially if the UAC is a decomposed =
gateway.</FONT></P>

<P><FONT SIZE=3D2>&gt; Mike</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; At 10:02 AM 3/7/2003 +0000, Mark Watson =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;The 200 OK vs RTP packet race condition is =
a smaller problem than </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;correctly deciding whether to play in-band =
media or local </FONT>
<BR><FONT SIZE=3D2>&gt; ringing. It </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;doesn't necessarily justify media detection =
at the MG anyway </FONT>
<BR><FONT SIZE=3D2>&gt; (or rather. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;the MG taking 'autonomous' action on the =
basis of media </FONT>
<BR><FONT SIZE=3D2>&gt; detecion, which is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;the problematic part) .</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;I don't think that cutting through the =
actual media just on </FONT>
<BR><FONT SIZE=3D2>&gt; the basis of </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;receipt of a media packet would be an =
acceptable solution in </FONT>
<BR><FONT SIZE=3D2>&gt; some (common) </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;business models anyway - they will want to =
wait for the 200 </FONT>
<BR><FONT SIZE=3D2>&gt; OK before </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;cutting through media. If that results in =
speech clipping </FONT>
<BR><FONT SIZE=3D2>&gt; then your RTT is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;probably too long for acceptable speech =
quality anyway.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;Also, as a general layering principle, I =
think it is bad to attach </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;semantics to the presence/absence of RTP =
packets - the </FONT>
<BR><FONT SIZE=3D2>&gt; expected state of </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;the media stream should be completely known =
to the endpoints </FONT>
<BR><FONT SIZE=3D2>&gt; based on the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;SIP/SDP negotiations. This surely makes the =
system more </FONT>
<BR><FONT SIZE=3D2>&gt; robust and assists </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;debugging because it allows be to detect an =
error case where I am </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;expecting to receive media but do =
not.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;I am confused by the resistance to solving =
this problem in the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;straightforward way. The existance of =
in-band media seems a </FONT>
<BR><FONT SIZE=3D2>&gt; perfectly </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;reasonable thing to want to signal at the =
SIP layer. People </FONT>
<BR><FONT SIZE=3D2>&gt; seem quite </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;happy to give the 183 message this =
semantic, for the case </FONT>
<BR><FONT SIZE=3D2>&gt; where the call </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;state is unknown - why is it such a big =
deal to convey the *same </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;information* at the SIP layer for the case =
where the call </FONT>
<BR><FONT SIZE=3D2>&gt; state is known </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;to be alerting ?? All I want to do is =
atomically signal the </FONT>
<BR><FONT SIZE=3D2>&gt; equivalent of </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;180 *plus* 183.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;...Mark</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: Gonzalo Camarillo </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; [&lt;<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>&gt;<A =
HREF=3D"mailto:Gonzalo.Cama">mailto:Gonzalo.Cama</A></FONT>
<BR><FONT SIZE=3D2>&gt; rillo@lmf.ericsson.se] </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sent: 07 March 2003 09:27</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; To: Watson, Mark =
[MOP:EP10:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Cc: Peterson, Jon; 'Ejzak, Richard P =
(Richard)'; sipping; Audet,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Francois [SC100:4K02:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Subject: Re: [Sipping] New version of =
the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Mark,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the text says that such a flag would =
not solve that </FONT>
<BR><FONT SIZE=3D2>&gt; issue, because you</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; have to implement media detection =
*anyway* for covering other</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; scenarios</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; (motivational paragraph at the =
bottom).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; I still think this problem =
remains unsolved.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The point is that such a flag would =
not solve it either.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Mark Watson wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Your text does not recognise the =
desire to avoid reading</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; semantics in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; to the arrival of RTP packets, =
to cope with the MGC/MG scenario.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; I still think this problem =
remains unsolved.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; ...Mark</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; From: Gonzalo Camarillo =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; [&lt;<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>&gt;<A =
HREF=3D"mailto:Gonzalo.Cama">mailto:Gonzalo.Cama</A></FONT>
<BR><FONT SIZE=3D2>&gt; rillo@lmf.ericsson.se] </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Sent: 07 March 2003 =
08:48</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; To: Peterson, Jon</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Cc: 'Ejzak, Richard P =
(Richard)'; Watson, Mark</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; [MOP:EP10:EXCH]; =
sipping;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Audet, Francois =
[SC100:4K02:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Subject: Re: [Sipping] New =
version of the early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Folks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; I agree with Jon that we =
should not encourage people to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; send in-band</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; ringing tones, but I also =
agree with Mark that this issue has</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; re-surfaced a number of =
times already. The message we </FONT>
<BR><FONT SIZE=3D2>&gt; want to get</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; through is that adding a =
SIP flag for resolving that issue</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; offers little</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; or no value.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; I am willing, if people =
agree, to add some text saying</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; why it is not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; good idea to add a =
SIP-layer flag to 180 responses indicating</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; that media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; is coming.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; What about a section along =
these lines:?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; 2.2.1 Problems with =
SIP-layer Indications in 180 Responses</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; As stated above, it is not =
an easy task for a UAC </FONT>
<BR><FONT SIZE=3D2>&gt; that receives a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; 180</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; (Ringing) response to =
decide whether it should generate local</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; ringback</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; or it will be receiving =
early media. At first sight, </FONT>
<BR><FONT SIZE=3D2>&gt; it may seem</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; adding a &quot;there is =
media coming&quot; indication to 180 (Ringing)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; responses</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; would facilitate the task =
of UACs. Upon reception of a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; 180 (Ringing)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; response with such an =
indication, the UAC would not </FONT>
<BR><FONT SIZE=3D2>&gt; generate local</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; ringback. However, such an =
indication would offer little</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; or no gain.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; The only scenario where =
such an indication would be </FONT>
<BR><FONT SIZE=3D2>&gt; applicable is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; when</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; the UAS sends a 180 =
(Ringing) response and starts </FONT>
<BR><FONT SIZE=3D2>&gt; sending early</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; right away. If the UAS =
intended to send early media at a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; later time,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; instead of right away, a =
sensible local policy for the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; UAC could be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; generate local ringback in =
the meantime. Therefore, the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &quot;there is media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; coming&quot; indication =
would be useless.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Assuming, then, that the =
UAS sends the 180 (Ringing) </FONT>
<BR><FONT SIZE=3D2>&gt; response and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; first media packets in =
parallel towards the UAC, we </FONT>
<BR><FONT SIZE=3D2>&gt; have a race</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; condition. If the media =
packets arrive at the UAC </FONT>
<BR><FONT SIZE=3D2>&gt; before the 180</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; (Ringing) response, the =
&quot;there is media coming&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; indication will not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; provide any further =
information to the UAC.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; The only situation where =
the UAC could benefit from that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; indication</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; when the 180 (Ringing) =
response arrives before the first</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; media packets.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; The UAC could avoid =
generating local ringback for an instant</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; before the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; first media packets arrive. =
However, the same result can be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; achieved in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; a much simpler way (without =
protocol extensions) by just</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; having UACs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; always delay the generation =
of local ringback for a short</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; period of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; time. The UAC can, for =
instance, generate a short beep upon</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; reception of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; the 180 (Ringing) response =
(this is already done by some</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; circuit-switched mobile =
terminals) and one second later start</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; generating</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; local ringback if no media =
have been received during </FONT>
<BR><FONT SIZE=3D2>&gt; that period.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; \motivation{Note that =
adding such an indication does not keep</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; UACs from</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; implementing media arrival =
detection either, since </FONT>
<BR><FONT SIZE=3D2>&gt; they have to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; implement it anyway to =
cover other scenarios, like the race</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; condition</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; between the 200 OK for the =
INVITE and the first regular media</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; packets).}</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Opinions?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Finland </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;<A HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A>&gt;<A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E4CD.961F4318--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 13:06:15 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20686
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 13:06:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27IHpL22337
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 13:17:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27IHpO22334
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 13:17:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20637
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 13:05:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27IGoO22027;
	Fri, 7 Mar 2003 13:16:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27IDdO21597
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 13:13:39 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20289
	for <sipping@ietf.org>; Fri, 7 Mar 2003 13:01:30 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h27I3NC09254;
	Fri, 7 Mar 2003 18:03:24 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JS1Z3>; Fri, 7 Mar 2003 13:03:32 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214ED8@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 7 Mar 2003 13:03:29 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E4D3.DBF8E730"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E4D3.DBF8E730
Content-Type: text/plain;
	charset="iso-8859-1"

 
I'm not sure I missed that point, exactly. I said that if the gateway knows
that the early media is just ringtone, it should send a 180. You're just
citing another case below in which the early media is not ringtone. I can't
see how this contradicts what I said. If there's some other in-band status
information available, the gateway should be using 183.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Friday, March 07, 2003 1:17 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft



Jon, 

You have missed one very important point which is that in-band media during
alerting is not necessarily 'just ringtone'. It is quite common for the call
to be in the 'Alerting' state (and for this to be know to a SIP to ISUP
gateway), but for the in-band media to contain some useful information other
than 'just ringtone'.

For example, in the UK at least, if the called party has Call Waiting, then
the call of course goes straight in to the Alerting state, but the caller
will here a message along the lines 'Please wait while we try to connect
your call - the person you are calling knows you are waiting'.

A second example would be when the call terminates on a queueing system, and
the message played gives the caller some idea of how long they will need to
wait.

I absolutely agree that if the in-band media was 'just ringtone' there would
be no point. In particular I don't see any need to support the PSTN
'feeture' in which you always hear the ringtone of the destination country
(IMO this is a bug, not a feature!).

So, let's recognise that there are cases where *both* out-of-band and
in-band status indications are present. My view is that out-of-band
indications should always be propogated if available - so for the scenario
in question we MUST use 180, not 183. Now we need to indicate that in-band
status is also available - is this really so hard ????

...Mark 

> -----Original Message----- 
> From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> Sent: 07 March 2003 00:09 
> To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo' 
> Cc: Watson, Mark [MOP:EP10:EXCH]; sipping 
> Subject: RE: [Sipping] New version of the early media draft 
> 
> 
> 
> Everything below is familiar ground, and I don't want to 
> start rehearsing 
> these same arguments again. SIP has made a number of design 
> decisions that 
> predispose it towards out-of-band status information. Sending 
> in-band status 
> information in SIP is harmful - period. In-band media should 
> be sent only 
> when the gateway does not know the status of the call, and thus cannot 
> communicate it out-of-band. Below, you basically argue that 
> in cases where 
> the gateway does not know the status of the call, it has to send early 
> media. I agree. I said that in cases in which the gateway 
> knows that the 
> early media is just ringtone, it should send 180. Clearly, if 
> there's some 
> in-band transition in call state from ringtone to some other 
> audible call 
> progress information, and the gateway isn't made aware of it, then the 
> gateway doesn't know the state of the call. Perhaps we might draw the 
> conclusion from your example that out-of-band call status 
> indicators are 
> inherently unreliable, then - and surmise that it is 
> impossible for the 
> gateway to know the state of the call. Or perhaps the 
> likelihood of this 
> condition arising is sufficiently remote, the consequences of 
> sending early 
> media sufficiently troublesome, that we might decide the 
> in-band information 
> in these cases is not 'essential' enough to worry over. But I 
> firmly believe 
> we should leave this to the conscience of the individual gateway 
> implementer. I don't think the early media draft needs to draw that 
> conclusion. 
> 
> Mr. Camarillo's draft already maintains a very delicate 
> balance of behavior 
> to accommodate SIP's needs, and I haven't heard anything in 
> this yet that 
> should alter it. 
> 
> Jon Peterson 
> NeuStar, Inc. 
> 
> > -----Original Message----- 
> > From: Ejzak, Richard P (Richard) [ mailto:ejzak@lucent.com
<mailto:ejzak@lucent.com> ] 
> > Sent: Thursday, March 06, 2003 2:40 PM 
> > To: 'Peterson, Jon'; 'Gonzalo Camarillo' 
> > Cc: Mark Watson; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > Jon, 
> > I must disagree with your blanket recommendation that the 
> > gateway not sent in-band ringing media.  This may be possible 
> > in some cases - and nothing we have suggested would prevent a 
> > gateway from using out-of-band indications.  But ringing is 
> > not the only in-band call progress information you may 
> > receive while trying to establish a call from SIP to ISUP.  
> > The transition from alerting to other forms of in-band call 
> > progress information is not guaranteed to be clearly signaled 
> > by ISUP within an ACM or CPG (since every switch in the 
> > network can safely assume in-band call progress after a 
> > certain point in the call), and it is essential that this 
> > subsequent information (when it exists) be presented to the 
> > UAC/user.  And the notion of having the gateway intelligently 
> > filter what it thinks is ringing and detect a transition to 
> > other forms of call progress is not acceptable. 
> > 
> > Regards, 
> > Richard Ejzak 
> > Lucent Technologies 
> > 
> > 
> > 
> > -----Original Message----- 
> > From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> > Sent: Thursday, March 06, 2003 4:06 PM 
> > To: 'Gonzalo Camarillo' 
> > Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > 
> > Well, 
> > 
> > > -----Original Message----- 
> > > From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se
<mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > [snip] 
> > > 
> > > The scenario he is after is as follows; a gateway *knows* 
> > that the user 
> > > is being alerted and also *knows* that it will be sending in-band 
> > > ringing. 
> > > 
> > 
> > If the gateway knows that it will be sending in-band ringing, 
> > my position is 
> > that the gateway shouldn't be sending that media. It's just 
> > ring tone. The 
> > UAC can generate that itself. Let's not waste the bandwidth 
> > sending ringing, 
> > especially in forking cases, especially because the UAC 
> might not even 
> > render this provisional media (if it's a PC UAC, for example). 
> > 
> > If media arrives at the UAC, it should override local 
> > ringtone, agreed. And 
> > I have no problem with the idea that a UAC would delay local 
> > ringtone for a 
> > short interval in order to see if any media is coming, even 
> > when 180 is 
> > received. But we should not encourage gateways to send 
> ringing media. 
> > 
> > Jon Peterson 
> > NeuStar, Inc. 
> > 
> 


------_=_NextPart_001_01C2E4D3.DBF8E730
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff size=2>I'm 
not sure I missed that point, exactly. I said that if the gateway knows that the 
early media is just ringtone, it should send a 180. You're just citing another 
case below in which the early media is not ringtone. I can't see how this 
contradicts what I said. If there's some other in-band status information 
available, the gateway should be using 183.</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff size=2>Jon 
Peterson</FONT></SPAN></DIV>
<DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
size=2>NeuStar, Inc.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
  [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Friday, March 07, 2003 
  1:17 AM<BR><B>To:</B> 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo 
  Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] New version 
  of the early media draft<BR><BR></FONT></DIV>
  <P><FONT size=2>Jon,</FONT> </P>
  <P><FONT size=2>You have missed one very important point which is that in-band 
  media during alerting is not necessarily 'just ringtone'. It is quite common 
  for the call to be in the 'Alerting' state (and for this to be know to a SIP 
  to ISUP gateway), but for the in-band media to contain some useful information 
  other than 'just ringtone'.</FONT></P>
  <P><FONT size=2>For example, in the UK at least, if the called party has Call 
  Waiting, then the call of course goes straight in to the Alerting state, but 
  the caller will here a message along the lines 'Please wait while we try to 
  connect your call - the person you are calling knows you are 
  waiting'.</FONT></P>
  <P><FONT size=2>A second example would be when the call terminates on a 
  queueing system, and the message played gives the caller some idea of how long 
  they will need to wait.</FONT></P>
  <P><FONT size=2>I absolutely agree that if the in-band media was 'just 
  ringtone' there would be no point. In particular I don't see any need to 
  support the PSTN 'feeture' in which you always hear the ringtone of the 
  destination country (IMO this is a bug, not a feature!).</FONT></P>
  <P><FONT size=2>So, let's recognise that there are cases where *both* 
  out-of-band and in-band status indications are present. My view is that 
  out-of-band indications should always be propogated if available - so for the 
  scenario in question we MUST use 180, not 183. Now we need to indicate that 
  in-band status is also available - is this really so hard ????</FONT></P>
  <P><FONT size=2>...Mark</FONT> </P>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: Peterson, Jon [<A 
  href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
  <BR><FONT size=2>&gt; Sent: 07 March 2003 00:09</FONT> <BR><FONT size=2>&gt; 
  To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo'</FONT> 
  <BR><FONT size=2>&gt; Cc: Watson, Mark [MOP:EP10:EXCH]; sipping</FONT> 
  <BR><FONT size=2>&gt; Subject: RE: [Sipping] New version of the early media 
  draft</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Everything below is 
  familiar ground, and I don't want to </FONT><BR><FONT size=2>&gt; start 
  rehearsing</FONT> <BR><FONT size=2>&gt; these same arguments again. SIP has 
  made a number of design </FONT><BR><FONT size=2>&gt; decisions that</FONT> 
  <BR><FONT size=2>&gt; predispose it towards out-of-band status information. 
  Sending </FONT><BR><FONT size=2>&gt; in-band status</FONT> <BR><FONT 
  size=2>&gt; information in SIP is harmful - period. In-band media should 
  </FONT><BR><FONT size=2>&gt; be sent only</FONT> <BR><FONT size=2>&gt; when 
  the gateway does not know the status of the call, and thus cannot</FONT> 
  <BR><FONT size=2>&gt; communicate it out-of-band. Below, you basically argue 
  that </FONT><BR><FONT size=2>&gt; in cases where</FONT> <BR><FONT size=2>&gt; 
  the gateway does not know the status of the call, it has to send early</FONT> 
  <BR><FONT size=2>&gt; media. I agree. I said that in cases in which the 
  gateway </FONT><BR><FONT size=2>&gt; knows that the</FONT> <BR><FONT 
  size=2>&gt; early media is just ringtone, it should send 180. Clearly, if 
  </FONT><BR><FONT size=2>&gt; there's some</FONT> <BR><FONT size=2>&gt; in-band 
  transition in call state from ringtone to some other </FONT><BR><FONT 
  size=2>&gt; audible call</FONT> <BR><FONT size=2>&gt; progress information, 
  and the gateway isn't made aware of it, then the</FONT> <BR><FONT size=2>&gt; 
  gateway doesn't know the state of the call. Perhaps we might draw the</FONT> 
  <BR><FONT size=2>&gt; conclusion from your example that out-of-band call 
  status </FONT><BR><FONT size=2>&gt; indicators are</FONT> <BR><FONT 
  size=2>&gt; inherently unreliable, then - and surmise that it is 
  </FONT><BR><FONT size=2>&gt; impossible for the</FONT> <BR><FONT size=2>&gt; 
  gateway to know the state of the call. Or perhaps the </FONT><BR><FONT 
  size=2>&gt; likelihood of this</FONT> <BR><FONT size=2>&gt; condition arising 
  is sufficiently remote, the consequences of </FONT><BR><FONT size=2>&gt; 
  sending early</FONT> <BR><FONT size=2>&gt; media sufficiently troublesome, 
  that we might decide the </FONT><BR><FONT size=2>&gt; in-band 
  information</FONT> <BR><FONT size=2>&gt; in these cases is not 'essential' 
  enough to worry over. But I </FONT><BR><FONT size=2>&gt; firmly believe</FONT> 
  <BR><FONT size=2>&gt; we should leave this to the conscience of the individual 
  gateway</FONT> <BR><FONT size=2>&gt; implementer. I don't think the early 
  media draft needs to draw that</FONT> <BR><FONT size=2>&gt; conclusion.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Mr. Camarillo's draft 
  already maintains a very delicate </FONT><BR><FONT size=2>&gt; balance of 
  behavior</FONT> <BR><FONT size=2>&gt; to accommodate SIP's needs, and I 
  haven't heard anything in </FONT><BR><FONT size=2>&gt; this yet that</FONT> 
  <BR><FONT size=2>&gt; should alter it.</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; Jon Peterson</FONT> <BR><FONT size=2>&gt; 
  NeuStar, Inc.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; 
  -----Original Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: Ejzak, 
  Richard P (Richard) [<A 
  href="mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT> <BR><FONT 
  size=2>&gt; &gt; Sent: Thursday, March 06, 2003 2:40 PM</FONT> <BR><FONT 
  size=2>&gt; &gt; To: 'Peterson, Jon'; 'Gonzalo Camarillo'</FONT> <BR><FONT 
  size=2>&gt; &gt; Cc: Mark Watson; sipping</FONT> <BR><FONT size=2>&gt; &gt; 
  Subject: RE: [Sipping] New version of the early media draft</FONT> <BR><FONT 
  size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
  size=2>&gt; &gt; Jon,</FONT> <BR><FONT size=2>&gt; &gt; I must disagree with 
  your blanket recommendation that the </FONT><BR><FONT size=2>&gt; &gt; gateway 
  not sent in-band ringing media.&nbsp; This may be possible </FONT><BR><FONT 
  size=2>&gt; &gt; in some cases - and nothing we have suggested would prevent a 
  </FONT><BR><FONT size=2>&gt; &gt; gateway from using out-of-band 
  indications.&nbsp; But ringing is </FONT><BR><FONT size=2>&gt; &gt; not the 
  only in-band call progress information you may </FONT><BR><FONT size=2>&gt; 
  &gt; receive while trying to establish a call from SIP to ISUP.&nbsp; 
  </FONT><BR><FONT size=2>&gt; &gt; The transition from alerting to other forms 
  of in-band call </FONT><BR><FONT size=2>&gt; &gt; progress information is not 
  guaranteed to be clearly signaled </FONT><BR><FONT size=2>&gt; &gt; by ISUP 
  within an ACM or CPG (since every switch in the </FONT><BR><FONT size=2>&gt; 
  &gt; network can safely assume in-band call progress after a </FONT><BR><FONT 
  size=2>&gt; &gt; certain point in the call), and it is essential that this 
  </FONT><BR><FONT size=2>&gt; &gt; subsequent information (when it exists) be 
  presented to the </FONT><BR><FONT size=2>&gt; &gt; UAC/user.&nbsp; And the 
  notion of having the gateway intelligently </FONT><BR><FONT size=2>&gt; &gt; 
  filter what it thinks is ringing and detect a transition to </FONT><BR><FONT 
  size=2>&gt; &gt; other forms of call progress is not acceptable.</FONT> 
  <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Regards,</FONT> 
  <BR><FONT size=2>&gt; &gt; Richard Ejzak</FONT> <BR><FONT size=2>&gt; &gt; 
  Lucent Technologies</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
  size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
  size=2>&gt; &gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; &gt; 
  From: Peterson, Jon [<A 
  href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
  <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 4:06 PM</FONT> 
  <BR><FONT size=2>&gt; &gt; To: 'Gonzalo Camarillo'</FONT> <BR><FONT 
  size=2>&gt; &gt; Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping</FONT> 
  <BR><FONT size=2>&gt; &gt; Subject: RE: [Sipping] New version of the early 
  media draft</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
  &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
  Well,</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; &gt; 
  -----Original Message-----</FONT> <BR><FONT size=2>&gt; &gt; &gt; From: 
  Gonzalo Camarillo [<A 
  href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
  <BR><FONT size=2>&gt; &gt; [snip]</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; The scenario he is after is as follows; 
  a gateway *knows* </FONT><BR><FONT size=2>&gt; &gt; that the user</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; is being alerted and also *knows* that it will 
  be sending in-band</FONT> <BR><FONT size=2>&gt; &gt; &gt; ringing.</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; If the gateway knows that it will be sending 
  in-band ringing, </FONT><BR><FONT size=2>&gt; &gt; my position is</FONT> 
  <BR><FONT size=2>&gt; &gt; that the gateway shouldn't be sending that media. 
  It's just </FONT><BR><FONT size=2>&gt; &gt; ring tone. The</FONT> <BR><FONT 
  size=2>&gt; &gt; UAC can generate that itself. Let's not waste the bandwidth 
  </FONT><BR><FONT size=2>&gt; &gt; sending ringing,</FONT> <BR><FONT 
  size=2>&gt; &gt; especially in forking cases, especially because the UAC 
  </FONT><BR><FONT size=2>&gt; might not even</FONT> <BR><FONT size=2>&gt; &gt; 
  render this provisional media (if it's a PC UAC, for example).</FONT> 
  <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; If media arrives 
  at the UAC, it should override local </FONT><BR><FONT size=2>&gt; &gt; 
  ringtone, agreed. And</FONT> <BR><FONT size=2>&gt; &gt; I have no problem with 
  the idea that a UAC would delay local </FONT><BR><FONT size=2>&gt; &gt; 
  ringtone for a</FONT> <BR><FONT size=2>&gt; &gt; short interval in order to 
  see if any media is coming, even </FONT><BR><FONT size=2>&gt; &gt; when 180 
  is</FONT> <BR><FONT size=2>&gt; &gt; received. But we should not encourage 
  gateways to send </FONT><BR><FONT size=2>&gt; ringing media.</FONT> <BR><FONT 
  size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Jon Peterson</FONT> 
  <BR><FONT size=2>&gt; &gt; NeuStar, Inc. </FONT><BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E4D3.DBF8E730--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 13:52:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22734
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 13:52:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27J46n26607
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 14:04:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27J46O26602
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 14:04:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22686
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 13:51:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27J3SO26565;
	Fri, 7 Mar 2003 14:03:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27J2XO26504
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 14:02:33 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22577
	for <sipping@ietf.org>; Fri, 7 Mar 2003 13:50:24 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by auemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27IqSi29428
	for <sipping@ietf.org>; Fri, 7 Mar 2003 13:52:28 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <XNTCNPHT>; Fri, 7 Mar 2003 18:52:27 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EC4D@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'Alan Johnston'" <alan.johnston@wcom.com>,
        "Drage, Keith (Keith)"
	 <drage@lucent.com>,
        "'vkenneally@cit.ie'" <vkenneally@cit.ie>, sipping@ietf.org
Subject: RE: [Sipping] Change of IP mid session and Contact header questio
	n
Date: Fri, 7 Mar 2003 18:52:26 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

I tried to make clear in my original response that I was talking only about mobility in 3GPP, and also because 3GPP2 uses exactly the same specification in this area also about 3GPP2.

If I failed to do so, let me reiterate, for mobility using 3GPP and 3GPP2 standards, and using the IMS platform specified by those two bodies, there is no change of IP address caused by mobility, and therefore no need for any SIP procedures as a result.

Were you thinking of some other mobile network technology using IP and SIP, while I agree there are other standardised mobile technologies, they tend to be access technologies rather than network ones.


Keith

Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 

> -----Original Message-----
> From: Alan Johnston [mailto:alan.johnston@wcom.com]
> Sent: 06 March 2003 21:09
> To: Drage, Keith (Keith); 'vkenneally@cit.ie'; sipping@ietf.org
> Subject: RE: [Sipping] Change of IP mid session and Contact header
> question
> 
> 
> Hi Val,
> 
> What Keith describes is true for 3GPP, but not generally true for SIP.
> 
> For an RFC 3261 compliant user agent, if a user agent changes its IP 
> address during a session for any reason (DHCP renewal 
> failure, VPN failure 
> and re-establishment, or due to mobility) and as a result the 
> signaling or 
> media packets need to be routed to a different IP address, 
> then re-INVITE 
> is the correct mechanism.  It does have the limitation that 
> the routeset 
> (set of proxies traversed) can not be changed with a 
> re-INVITE, only the 
> Contact URI.  So if a change of IP address requires a new proxy to be 
> traversed, instead of a re-INVITE, the user agent should send 
> a new INVITE 
> (creating a new dialog with a new route set) with a Replaces header 
> identifying the existing session.  A new REGISTER is required 
> in order to 
> receive new incoming calls, but has little to do with the 
> current dialog.
> 
> This scenario is still likely when an endpoint wishes to 
> switch a call 
> between non-cooperating networks, such as a commercial 
> wireless IP network 
> and an enterprise or home 802.11 network.
> 
> Hope this helps.
> 
> Alan Johnston
> WorldCom
> sip:alan@digitalari.com
> 
> At 02:23 PM 3/5/2003 +0000, Drage, Keith (Keith) wrote:
> >Apart from some author drafts using SIP for mobility itself, 
> which are not 
> >being progressed by the working group, this question is outside IETF 
> >itself. IETF has been working with 3GPP and 3GPP2 on how to 
> put SIP into a 
> >mobile environment.
> >
> >In 3GPP release 5, not only does a new IP address 
> necessitate the use of a 
> >new INVITE, it also necessitates the use of a new 
> registration as well.
> >
> >Normally mobile users retain their PDP context to the GGSN 
> when moving, 
> >and therefore retain their IP address, and therefore the 
> issue should not 
> >arise. Mobility is handled below the SIP layer.
> >
> >3GPP2 are using mobile IP instead of GPRS, and therefore the same 
> >considerations apply.
> >
> >Keith
> >
> >Keith Drage
> >Lucent Technologies
> >Tel: +44 1793 776249
> >Email: drage@lucent.com
> >
> > > -----Original Message-----
> > > From: Valerie Kenneally [mailto:vkenneally@cit.ie]
> > > Sent: 05 March 2003 11:52
> > > To: sipping@ietf.org
> > > Subject: [Sipping] Change of IP mid session and Contact
> > > header question
> > >
> > >
> > > Hi All,
> > >
> > >       I'm just trying to understand some SIP session
> > > scenarios and various
> > > features.  My question is best explained by example
> > >
> > > If a session is established using SIP between two endpoints
> > > (in a mobile
> > > network) and during the session one of these endpoints moves
> > > such that it is
> > > assigned a new ip, is it a MUST that this endpoint send a
> > > RE-INVITE with new
> > > Contact information to the other communicating entity?
> > >
> > > Thanks in advance,
> > > Val Kenneally
> > >
> > >
> > > -------------------Legal
> > > Disclaimer---------------------------------------
> > >
> > > The above electronic mail transmission is confidential and
> > > intended only for the person to whom it is addressed. Its
> > > contents may be protected by legal and/or professional
> > > privilege. Should it be received by you in error please
> > > contact the sender at the above quoted email address. Any
> > > unauthorised form of reproduction of this message is strictly
> > > prohibited. The Institute does not guarantee the security of
> > > any information electronically transmitted and is not liable
> > > if the information contained in this communication is not a
> > > proper and complete record of the message as transmitted by
> > > the sender nor for any delay in its receipt.
> > >
> > > --------------------------------------------------------------
> > > --------------------------
> > >
> > > _______________________________________________
> > > Sipping mailing list  
https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 15:28:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27799
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 15:28:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27Kdgc05217
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 15:39:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KdgO05214
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 15:39:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27749
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 15:27:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27Kd6O05004;
	Fri, 7 Mar 2003 15:39:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KbCO04296
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 15:37:12 -0500
Received: from bdsl.greycouncil.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27651
	for <sipping@ietf.org>; Fri, 7 Mar 2003 15:25:01 -0500 (EST)
Received: from txdwillis (bdsl.66.12.12.254.gte.net [66.12.12.254])
	(authenticated bits=0)
	by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id h27KR649000954
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <sipping@ietf.org>; Fri, 7 Mar 2003 14:27:06 -0600
From: "Dean Willis" <dwillis@dynamicsoft.com>
To: <sipping@ietf.org>
Date: Fri, 7 Mar 2003 14:26:47 -0600
Message-ID: <00a701c2e4e7$e0bfce00$ee036e3f@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sipping] FW: SF Agenda Requests
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit




Ok, I think I have filed all the SIPPING agenda requests I've seen into the
requests tracking page at 

http://www.softarmor.com/sipping/meets/ietf56/requests.html

And of course general meeting info will be at

http://www.softarmor.com/sipping/meets/ietf56/

As usual.


If you have made a request, please check to make sure that it is listed
here. If it is not, get Gonzalo or I to fix it ASAP. Of course, if you NEED
to make a request, this is probably your last chance . . .

--
Dean


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 16:00:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02732
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 16:00:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27LCUo09538
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 16:12:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27LCUO09535
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 16:12:30 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02642
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 16:00:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27LAiO09055;
	Fri, 7 Mar 2003 16:10:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KoRO06012
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 15:50:27 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29853;
	Fri, 7 Mar 2003 15:38:16 -0500 (EST)
Message-Id: <200303072038.PAA29853@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 15:38:16 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-cc-framework-02.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: A Call Control and Multi-party usage framework 
			  for the Session Initiation Protocol (SIP)
	Author(s)	: R. Mahy et. al.
	Filename	: draft-ietf-sipping-cc-framework-02.txt
	Pages		: 43
	Date		: 2003-3-7
	
This document defines a framework and requirements for multi-party
usage of SIP.  To enable discussion of multi-party features and
applications we define an abstract call model for describing the
media relationships required by many of these.  The model and actions
described here are specifically chosen to be independent of the SIP
signaling and/or mixing approach chosen to actually setup the media
relationships.  In addition to its dialog manipulation aspect, this
framework includes requirements for communicating related information
and events such as conference and session state, and session history.
This framework also describes other goals which embody the spirit of
SIP applications as used on the Internet.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-cc-framework-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sipping-cc-framework-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-sipping-cc-framework-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:	<2003-3-7151846.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-cc-framework-02.txt

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

Content-Type: text/plain
Content-ID:	<2003-3-7151846.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 17:23:15 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09847
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 17:23:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27MYuM19666
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 17:34:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27MYuO19663
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 17:34:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09823
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 17:22:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27MXtO19606;
	Fri, 7 Mar 2003 17:33:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27MWLO19435
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 17:32:21 -0500
Received: from gateway.hns.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09665
	for <sipping@ietf.org>; Fri, 7 Mar 2003 17:20:09 -0500 (EST)
Received: from excore1.hns.com (excore1.hns.com [139.85.52.104])
	by gateway.hns.com (Switch-3.0.3/Switch-3.0.0) with ESMTP id h27MMBv6012154
	for <sipping@ietf.org>; Fri, 7 Mar 2003 17:22:12 -0500 (EST)
Received: from atlas (atlas.hns.com [139.85.177.110])
	by excore1.hns.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h27MM6814904
	for <sipping@ietf.org>; Fri, 7 Mar 2003 17:22:06 -0500 (EST)
To: sipping@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF3B9E74BB.7D71DCF6-ON85256CE2.0077C9DE@LocalDomain>
From: "Arjun Roychowdhury" <aroychow@hns.com>
Date: Fri, 7 Mar 2003 17:21:40 -0500
X-MIMETrack: Serialize by Router on Atlas/HNS(Release 5.0.10 |March 22, 2002) at 03/07/2003
 05:20:08 PM,
	Serialize complete at 03/07/2003 05:20:08 PM
Content-Type: text/plain; charset="us-ascii"
X-Filtered: Sendmail MIME Filter v1.0.8 excore1.hns.com h27MM6814904
Subject: [Sipping] CPCP and SIP {conferencing}
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Reading 
http://www.ietf.org/internet-drafts/draft-levin-sipping-conferencing-requirements-03.txt
and 
http://www.ietf.org/internet-drafts/draft-koskelainen-sipping-conf-policy-req-00.txt 
in conjunction, 

it seems both CPCP and SIP have similar requirements and the reqts listed 
in the above two drafts to a great
extent can mix with each other. This probably is a good  thing since that 
means SIP can meet many of CPCP's requirements.

But it does not clarify my confusion below:

In addition, framework-01, for each scenario lists a SIP way and a CPCP 
way

 Even though SIP may finally land up doing a lot of what is required by 
CPCP,  looking at the framework-01 diagram Figure 2, the interface between 
Participant and Focus is different from the interface between Participant 
and Conference Policy server.

However, when I read petri's, jonathan's and orit's drafts in conjunction, 
I see these two interfaces sparring in the same ring.

 I am somewhat confused. Where does the design team consider CPCP to stop 
(Participant - CPS) and SIP dialog to start (Participant to Focus) ?

regds
Arjun










_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 18:11:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13240
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 18:11:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27NNVi24303
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 18:23:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27NNVO24300
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 18:23:31 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13173
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 18:11:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27NMWO24197;
	Fri, 7 Mar 2003 18:22:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27NDrO23858
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 18:13:53 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12151
	for <sipping@ietf.org>; Fri, 7 Mar 2003 18:01:36 -0500 (EST)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by auemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27N3es24321
	for <sipping@ietf.org>; Fri, 7 Mar 2003 18:03:40 -0500 (EST)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2653.19)
	id <1H3RQSKF>; Fri, 7 Mar 2003 17:03:39 -0600
Message-ID: <DBC3D7D0A071F743AE0767C9C6071EDA0482BBD1@il0015exch010u.ih.lucent.com>
From: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Mark Watson'"
	 <mwatson@nortelnetworks.com>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 7 Mar 2003 17:03:37 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E4FD.C96FCC62"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E4FD.C96FCC62
Content-Type: text/plain;
	charset="iso-8859-1"

Jon,
You are assuming a model in which the UAS gateway call control entity has perfect knowledge of the content of the media stream.  This is frequently not true, particularly in a decomposed MGC/MG architecture.  There are two possible ways for it to gain this knowledge: 1) for the MG to monitor the media stream and analyze its contents and report the results to the MGC (an unacceptable solution); or 2) for the MGC to receive this information from the next hop via the call control protocol on that hop (ISUP/BICC/SIP).  But for case 2) to work, an MGC depends on the chain of switches all the way to the terminating switch to accurately signal this information (equivalent to 183 if it's not ringing tone; 180 if it is) in the backward direction.  One simple example of where this breaks down is when no COT is performed and there is a link failure (i.e. there is no in-band information even while alerting).  In effect, the in-band information tests the media path, providing immediate i!
nformation about the media path to the caller so the call can be abandoned if appropriate.  THIS IS NOT POSSIBLE without having a clear indication in the 180 from the UAS that there is supposed to be in-band progress information.  The current text would have the UAC inject local ringing in the absence of in-band media, while what we really want to do is play silence since there is no media path beyond the UAS anyway!  Many more examples are possible.  Alerting indication (180) does not necessarily mean there is in-band ringing when in-band information is present.  There may be announcements or various tones or nothing, depending on the state of the network.  There is no guarantee that a UAS gateway will have sufficient information to send a 183 if in-band call progress information changes during alerting.
 
In general, I support Mark's analysis of the situation and continue to request an in-band call progress indication for the 180 response.
 
If you are alternately saying that a UAS gateway that cannot guarantee that any in-band call progress information it may be sending is in the form of a ringing tone should send 183 rather than 180 after receiving "subscriber free" or "alerting" indications, then I can also accept this solution.  But then this new guideline must be clearly spelled out in either Gonzalo's draft or RFC 3398, preferably the latter, since a UAS gateway will rarely send 180 once in-band information is available.  I have seen some strong resistance to this in prior emails on this reflector.  We can't have it both ways.
 
Regards,
Richard Ejzak
Lucent Technologies

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: Friday, March 07, 2003 12:03 PM
To: 'Mark Watson'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


 
I'm not sure I missed that point, exactly. I said that if the gateway knows that the early media is just ringtone, it should send a 180. You're just citing another case below in which the early media is not ringtone. I can't see how this contradicts what I said. If there's some other in-band status information available, the gateway should be using 183.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Friday, March 07, 2003 1:17 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft



Jon, 

You have missed one very important point which is that in-band media during alerting is not necessarily 'just ringtone'. It is quite common for the call to be in the 'Alerting' state (and for this to be know to a SIP to ISUP gateway), but for the in-band media to contain some useful information other than 'just ringtone'.

For example, in the UK at least, if the called party has Call Waiting, then the call of course goes straight in to the Alerting state, but the caller will here a message along the lines 'Please wait while we try to connect your call - the person you are calling knows you are waiting'.

A second example would be when the call terminates on a queueing system, and the message played gives the caller some idea of how long they will need to wait.

I absolutely agree that if the in-band media was 'just ringtone' there would be no point. In particular I don't see any need to support the PSTN 'feeture' in which you always hear the ringtone of the destination country (IMO this is a bug, not a feature!).

So, let's recognise that there are cases where *both* out-of-band and in-band status indications are present. My view is that out-of-band indications should always be propogated if available - so for the scenario in question we MUST use 180, not 183. Now we need to indicate that in-band status is also available - is this really so hard ????

...Mark 

> -----Original Message----- 
> From: Peterson, Jon [ mailto:jon.peterson@neustar.biz <mailto:jon.peterson@neustar.biz> ] 
> Sent: 07 March 2003 00:09 
> To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo' 
> Cc: Watson, Mark [MOP:EP10:EXCH]; sipping 
> Subject: RE: [Sipping] New version of the early media draft 
> 
> 
> 
> Everything below is familiar ground, and I don't want to 
> start rehearsing 
> these same arguments again. SIP has made a number of design 
> decisions that 
> predispose it towards out-of-band status information. Sending 
> in-band status 
> information in SIP is harmful - period. In-band media should 
> be sent only 
> when the gateway does not know the status of the call, and thus cannot 
> communicate it out-of-band. Below, you basically argue that 
> in cases where 
> the gateway does not know the status of the call, it has to send early 
> media. I agree. I said that in cases in which the gateway 
> knows that the 
> early media is just ringtone, it should send 180. Clearly, if 
> there's some 
> in-band transition in call state from ringtone to some other 
> audible call 
> progress information, and the gateway isn't made aware of it, then the 
> gateway doesn't know the state of the call. Perhaps we might draw the 
> conclusion from your example that out-of-band call status 
> indicators are 
> inherently unreliable, then - and surmise that it is 
> impossible for the 
> gateway to know the state of the call. Or perhaps the 
> likelihood of this 
> condition arising is sufficiently remote, the consequences of 
> sending early 
> media sufficiently troublesome, that we might decide the 
> in-band information 
> in these cases is not 'essential' enough to worry over. But I 
> firmly believe 
> we should leave this to the conscience of the individual gateway 
> implementer. I don't think the early media draft needs to draw that 
> conclusion. 
> 
> Mr. Camarillo's draft already maintains a very delicate 
> balance of behavior 
> to accommodate SIP's needs, and I haven't heard anything in 
> this yet that 
> should alter it. 
> 
> Jon Peterson 
> NeuStar, Inc. 
> 
> > -----Original Message----- 
> > From: Ejzak, Richard P (Richard) [ mailto:ejzak@lucent.com <mailto:ejzak@lucent.com> ] 
> > Sent: Thursday, March 06, 2003 2:40 PM 
> > To: 'Peterson, Jon'; 'Gonzalo Camarillo' 
> > Cc: Mark Watson; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > Jon, 
> > I must disagree with your blanket recommendation that the 
> > gateway not sent in-band ringing media.  This may be possible 
> > in some cases - and nothing we have suggested would prevent a 
> > gateway from using out-of-band indications.  But ringing is 
> > not the only in-band call progress information you may 
> > receive while trying to establish a call from SIP to ISUP.  
> > The transition from alerting to other forms of in-band call 
> > progress information is not guaranteed to be clearly signaled 
> > by ISUP within an ACM or CPG (since every switch in the 
> > network can safely assume in-band call progress after a 
> > certain point in the call), and it is essential that this 
> > subsequent information (when it exists) be presented to the 
> > UAC/user.  And the notion of having the gateway intelligently 
> > filter what it thinks is ringing and detect a transition to 
> > other forms of call progress is not acceptable. 
> > 
> > Regards, 
> > Richard Ejzak 
> > Lucent Technologies 
> > 
> > 
> > 
> > -----Original Message----- 
> > From: Peterson, Jon [ mailto:jon.peterson@neustar.biz <mailto:jon.peterson@neustar.biz> ] 
> > Sent: Thursday, March 06, 2003 4:06 PM 
> > To: 'Gonzalo Camarillo' 
> > Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > 
> > Well, 
> > 
> > > -----Original Message----- 
> > > From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se <mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > [snip] 
> > > 
> > > The scenario he is after is as follows; a gateway *knows* 
> > that the user 
> > > is being alerted and also *knows* that it will be sending in-band 
> > > ringing. 
> > > 
> > 
> > If the gateway knows that it will be sending in-band ringing, 
> > my position is 
> > that the gateway shouldn't be sending that media. It's just 
> > ring tone. The 
> > UAC can generate that itself. Let's not waste the bandwidth 
> > sending ringing, 
> > especially in forking cases, especially because the UAC 
> might not even 
> > render this provisional media (if it's a PC UAC, for example). 
> > 
> > If media arrives at the UAC, it should override local 
> > ringtone, agreed. And 
> > I have no problem with the idea that a UAC would delay local 
> > ringtone for a 
> > short interval in order to see if any media is coming, even 
> > when 180 is 
> > received. But we should not encourage gateways to send 
> ringing media. 
> > 
> > Jon Peterson 
> > NeuStar, Inc. 
> > 
> 


------_=_NextPart_001_01C2E4FD.C96FCC62
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.50.4922.900" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=307152419-07032003>Jon,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=307152419-07032003>You 
are assuming a model in which the UAS gateway call control entity has perfect 
knowledge of the content of the media stream.&nbsp; This is frequently not true, 
particularly in a decomposed MGC/MG architecture.&nbsp; There are two possible 
ways for it to gain this knowledge: 1) for the MG to monitor the media stream 
and analyze its contents and report the results to the MGC (an unacceptable 
solution); or 2) for the MGC to receive this information from the next hop via 
the call control protocol on that hop (ISUP/BICC/SIP).&nbsp; But for case 2) to 
work, an MGC depends on the chain of switches all the way to the terminating 
switch to accurately signal this information (equivalent to 183 if it's not 
ringing tone; 180 if it is) in the backward direction.&nbsp; One simple example 
of where this breaks down is when no COT is performed and there is a link 
failure (i.e. there is no in-band information even while alerting).&nbsp; In 
effect, the in-band information tests the media path, providing immediate 
information&nbsp;about the media path&nbsp;to the caller so the call can be 
abandoned if appropriate.&nbsp; THIS IS NOT POSSIBLE without having a clear 
indication in the 180 from the UAS that there is supposed to be in-band progress 
information.&nbsp;&nbsp;The current text would have the UAC inject local ringing 
in the absence of in-band media, while what we really want to do is play silence 
since there is no media path beyond the UAS anyway!&nbsp; Many more examples are 
possible.&nbsp; Alerting indication (180) does not necessarily mean there is 
in-band ringing when in-band information is present.&nbsp; There may be 
announcements or various tones or nothing, depending on the state of the 
network.&nbsp; There is no guarantee that a UAS gateway will have sufficient 
information to send a 183 if in-band call progress information changes during 
alerting.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=307152419-07032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=307152419-07032003>In 
general, I support Mark's analysis of the situation and continue to request an 
in-band call progress indication for the 180 response.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=307152419-07032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=307152419-07032003>If you 
are alternately saying that a UAS gateway that cannot guarantee that any in-band 
call progress information it may be sending is in the form of a ringing 
tone&nbsp;should send 183 rather than 180 after receiving "subscriber free" or 
"alerting" indications, then I can also accept this solution.&nbsp; But then 
this new guideline must be clearly spelled out in either Gonzalo's draft or RFC 
3398, preferably the latter, since a UAS gateway will rarely send 180 once 
in-band information is available.&nbsp; I have seen some strong resistance to 
this in prior emails on this reflector.&nbsp; We can't have it both 
ways.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=307152419-07032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=307152419-07032003>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=307152419-07032003>Richard Ejzak</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=307152419-07032003>Lucent 
Technologies</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Peterson, Jon 
  [mailto:jon.peterson@neustar.biz]<BR><B>Sent:</B> Friday, March 07, 2003 12:03 
  PM<BR><B>To:</B> 'Mark Watson'; 'Ejzak, Richard P (Richard)'; 'Gonzalo 
  Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] New version 
  of the early media draft<BR><BR></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff size=2>I'm 
  not sure I missed that point, exactly. I said that if the gateway knows that 
  the early media is just ringtone, it should send a 180. You're just citing 
  another case below in which the early media is not ringtone. I can't see how 
  this contradicts what I said. If there's some other in-band status information 
  available, the gateway should be using 183.</FONT></SPAN></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff size=2>Jon 
  Peterson</FONT></SPAN></DIV>
  <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
  size=2>NeuStar, Inc.</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=ltr 
  style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
    <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
    size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
    [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Friday, March 07, 2003 
    1:17 AM<BR><B>To:</B> 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 
    'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] 
    New version of the early media draft<BR><BR></FONT></DIV>
    <P><FONT size=2>Jon,</FONT> </P>
    <P><FONT size=2>You have missed one very important point which is that 
    in-band media during alerting is not necessarily 'just ringtone'. It is 
    quite common for the call to be in the 'Alerting' state (and for this to be 
    know to a SIP to ISUP gateway), but for the in-band media to contain some 
    useful information other than 'just ringtone'.</FONT></P>
    <P><FONT size=2>For example, in the UK at least, if the called party has 
    Call Waiting, then the call of course goes straight in to the Alerting 
    state, but the caller will here a message along the lines 'Please wait while 
    we try to connect your call - the person you are calling knows you are 
    waiting'.</FONT></P>
    <P><FONT size=2>A second example would be when the call terminates on a 
    queueing system, and the message played gives the caller some idea of how 
    long they will need to wait.</FONT></P>
    <P><FONT size=2>I absolutely agree that if the in-band media was 'just 
    ringtone' there would be no point. In particular I don't see any need to 
    support the PSTN 'feeture' in which you always hear the ringtone of the 
    destination country (IMO this is a bug, not a feature!).</FONT></P>
    <P><FONT size=2>So, let's recognise that there are cases where *both* 
    out-of-band and in-band status indications are present. My view is that 
    out-of-band indications should always be propogated if available - so for 
    the scenario in question we MUST use 180, not 183. Now we need to indicate 
    that in-band status is also available - is this really so hard 
    ????</FONT></P>
    <P><FONT size=2>...Mark</FONT> </P>
    <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
    From: Peterson, Jon [<A 
    href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
    <BR><FONT size=2>&gt; Sent: 07 March 2003 00:09</FONT> <BR><FONT size=2>&gt; 
    To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo'</FONT> 
    <BR><FONT size=2>&gt; Cc: Watson, Mark [MOP:EP10:EXCH]; sipping</FONT> 
    <BR><FONT size=2>&gt; Subject: RE: [Sipping] New version of the early media 
    draft</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
    </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Everything below 
    is familiar ground, and I don't want to </FONT><BR><FONT size=2>&gt; start 
    rehearsing</FONT> <BR><FONT size=2>&gt; these same arguments again. SIP has 
    made a number of design </FONT><BR><FONT size=2>&gt; decisions that</FONT> 
    <BR><FONT size=2>&gt; predispose it towards out-of-band status information. 
    Sending </FONT><BR><FONT size=2>&gt; in-band status</FONT> <BR><FONT 
    size=2>&gt; information in SIP is harmful - period. In-band media should 
    </FONT><BR><FONT size=2>&gt; be sent only</FONT> <BR><FONT size=2>&gt; when 
    the gateway does not know the status of the call, and thus cannot</FONT> 
    <BR><FONT size=2>&gt; communicate it out-of-band. Below, you basically argue 
    that </FONT><BR><FONT size=2>&gt; in cases where</FONT> <BR><FONT 
    size=2>&gt; the gateway does not know the status of the call, it has to send 
    early</FONT> <BR><FONT size=2>&gt; media. I agree. I said that in cases in 
    which the gateway </FONT><BR><FONT size=2>&gt; knows that the</FONT> 
    <BR><FONT size=2>&gt; early media is just ringtone, it should send 180. 
    Clearly, if </FONT><BR><FONT size=2>&gt; there's some</FONT> <BR><FONT 
    size=2>&gt; in-band transition in call state from ringtone to some other 
    </FONT><BR><FONT size=2>&gt; audible call</FONT> <BR><FONT size=2>&gt; 
    progress information, and the gateway isn't made aware of it, then 
    the</FONT> <BR><FONT size=2>&gt; gateway doesn't know the state of the call. 
    Perhaps we might draw the</FONT> <BR><FONT size=2>&gt; conclusion from your 
    example that out-of-band call status </FONT><BR><FONT size=2>&gt; indicators 
    are</FONT> <BR><FONT size=2>&gt; inherently unreliable, then - and surmise 
    that it is </FONT><BR><FONT size=2>&gt; impossible for the</FONT> <BR><FONT 
    size=2>&gt; gateway to know the state of the call. Or perhaps the 
    </FONT><BR><FONT size=2>&gt; likelihood of this</FONT> <BR><FONT size=2>&gt; 
    condition arising is sufficiently remote, the consequences of 
    </FONT><BR><FONT size=2>&gt; sending early</FONT> <BR><FONT size=2>&gt; 
    media sufficiently troublesome, that we might decide the </FONT><BR><FONT 
    size=2>&gt; in-band information</FONT> <BR><FONT size=2>&gt; in these cases 
    is not 'essential' enough to worry over. But I </FONT><BR><FONT size=2>&gt; 
    firmly believe</FONT> <BR><FONT size=2>&gt; we should leave this to the 
    conscience of the individual gateway</FONT> <BR><FONT size=2>&gt; 
    implementer. I don't think the early media draft needs to draw that</FONT> 
    <BR><FONT size=2>&gt; conclusion.</FONT> <BR><FONT size=2>&gt; 
    </FONT><BR><FONT size=2>&gt; Mr. Camarillo's draft already maintains a very 
    delicate </FONT><BR><FONT size=2>&gt; balance of behavior</FONT> <BR><FONT 
    size=2>&gt; to accommodate SIP's needs, and I haven't heard anything in 
    </FONT><BR><FONT size=2>&gt; this yet that</FONT> <BR><FONT size=2>&gt; 
    should alter it.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
    Jon Peterson</FONT> <BR><FONT size=2>&gt; NeuStar, Inc.</FONT> <BR><FONT 
    size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; -----Original 
    Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: Ejzak, Richard P 
    (Richard) [<A 
    href="mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT> <BR><FONT 
    size=2>&gt; &gt; Sent: Thursday, March 06, 2003 2:40 PM</FONT> <BR><FONT 
    size=2>&gt; &gt; To: 'Peterson, Jon'; 'Gonzalo Camarillo'</FONT> <BR><FONT 
    size=2>&gt; &gt; Cc: Mark Watson; sipping</FONT> <BR><FONT size=2>&gt; &gt; 
    Subject: RE: [Sipping] New version of the early media draft</FONT> <BR><FONT 
    size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
    size=2>&gt; &gt; Jon,</FONT> <BR><FONT size=2>&gt; &gt; I must disagree with 
    your blanket recommendation that the </FONT><BR><FONT size=2>&gt; &gt; 
    gateway not sent in-band ringing media.&nbsp; This may be possible 
    </FONT><BR><FONT size=2>&gt; &gt; in some cases - and nothing we have 
    suggested would prevent a </FONT><BR><FONT size=2>&gt; &gt; gateway from 
    using out-of-band indications.&nbsp; But ringing is </FONT><BR><FONT 
    size=2>&gt; &gt; not the only in-band call progress information you may 
    </FONT><BR><FONT size=2>&gt; &gt; receive while trying to establish a call 
    from SIP to ISUP.&nbsp; </FONT><BR><FONT size=2>&gt; &gt; The transition 
    from alerting to other forms of in-band call </FONT><BR><FONT size=2>&gt; 
    &gt; progress information is not guaranteed to be clearly signaled 
    </FONT><BR><FONT size=2>&gt; &gt; by ISUP within an ACM or CPG (since every 
    switch in the </FONT><BR><FONT size=2>&gt; &gt; network can safely assume 
    in-band call progress after a </FONT><BR><FONT size=2>&gt; &gt; certain 
    point in the call), and it is essential that this </FONT><BR><FONT 
    size=2>&gt; &gt; subsequent information (when it exists) be presented to the 
    </FONT><BR><FONT size=2>&gt; &gt; UAC/user.&nbsp; And the notion of having 
    the gateway intelligently </FONT><BR><FONT size=2>&gt; &gt; filter what it 
    thinks is ringing and detect a transition to </FONT><BR><FONT size=2>&gt; 
    &gt; other forms of call progress is not acceptable.</FONT> <BR><FONT 
    size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Regards,</FONT> <BR><FONT 
    size=2>&gt; &gt; Richard Ejzak</FONT> <BR><FONT size=2>&gt; &gt; Lucent 
    Technologies</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
    &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
    -----Original Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: Peterson, 
    Jon [<A 
    href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
    <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 4:06 PM</FONT> 
    <BR><FONT size=2>&gt; &gt; To: 'Gonzalo Camarillo'</FONT> <BR><FONT 
    size=2>&gt; &gt; Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; 
    sipping</FONT> <BR><FONT size=2>&gt; &gt; Subject: RE: [Sipping] New version 
    of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
    size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
    size=2>&gt; &gt; Well,</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
    size=2>&gt; &gt; &gt; -----Original Message-----</FONT> <BR><FONT 
    size=2>&gt; &gt; &gt; From: Gonzalo Camarillo [<A 
    href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
    <BR><FONT size=2>&gt; &gt; [snip]</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
    </FONT><BR><FONT size=2>&gt; &gt; &gt; The scenario he is after is as 
    follows; a gateway *knows* </FONT><BR><FONT size=2>&gt; &gt; that the 
    user</FONT> <BR><FONT size=2>&gt; &gt; &gt; is being alerted and also 
    *knows* that it will be sending in-band</FONT> <BR><FONT size=2>&gt; &gt; 
    &gt; ringing.</FONT> <BR><FONT size=2>&gt; &gt; &gt; </FONT><BR><FONT 
    size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; If the gateway knows that 
    it will be sending in-band ringing, </FONT><BR><FONT size=2>&gt; &gt; my 
    position is</FONT> <BR><FONT size=2>&gt; &gt; that the gateway shouldn't be 
    sending that media. It's just </FONT><BR><FONT size=2>&gt; &gt; ring tone. 
    The</FONT> <BR><FONT size=2>&gt; &gt; UAC can generate that itself. Let's 
    not waste the bandwidth </FONT><BR><FONT size=2>&gt; &gt; sending 
    ringing,</FONT> <BR><FONT size=2>&gt; &gt; especially in forking cases, 
    especially because the UAC </FONT><BR><FONT size=2>&gt; might not 
    even</FONT> <BR><FONT size=2>&gt; &gt; render this provisional media (if 
    it's a PC UAC, for example).</FONT> <BR><FONT size=2>&gt; &gt; 
    </FONT><BR><FONT size=2>&gt; &gt; If media arrives at the UAC, it should 
    override local </FONT><BR><FONT size=2>&gt; &gt; ringtone, agreed. 
    And</FONT> <BR><FONT size=2>&gt; &gt; I have no problem with the idea that a 
    UAC would delay local </FONT><BR><FONT size=2>&gt; &gt; ringtone for 
    a</FONT> <BR><FONT size=2>&gt; &gt; short interval in order to see if any 
    media is coming, even </FONT><BR><FONT size=2>&gt; &gt; when 180 is</FONT> 
    <BR><FONT size=2>&gt; &gt; received. But we should not encourage gateways to 
    send </FONT><BR><FONT size=2>&gt; ringing media.</FONT> <BR><FONT 
    size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Jon Peterson</FONT> 
    <BR><FONT size=2>&gt; &gt; NeuStar, Inc. </FONT><BR><FONT size=2>&gt; &gt; 
    </FONT><BR><FONT size=2>&gt; </FONT></P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E4FD.C96FCC62--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 18:46:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15539
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 18:46:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27NwFo27668
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 18:58:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27NwFO27665
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 18:58:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15533
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 18:46:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27NvQO27579;
	Fri, 7 Mar 2003 18:57:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27Nu3O27432
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 18:56:03 -0500
Received: from ondar.cablelabs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15363
	for <sipping@ietf.org>; Fri, 7 Mar 2003 18:43:48 -0500 (EST)
Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20])
	by ondar.cablelabs.com (8.12.8/8.12.8) with ESMTP id h27NjpKg009293;
	Fri, 7 Mar 2003 16:45:51 -0700 (MST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [Sipping] I-D ACTION:draft-ietf-sipping-realtimefax-01.txt
Date: Fri, 7 Mar 2003 16:45:50 -0700
Message-ID: <E63E74E1F5391449BDFCAE1F352EC7DC0B9084@srvxchg.cablelabs.com>
Thread-Topic: [Sipping] I-D ACTION:draft-ietf-sipping-realtimefax-01.txt
thread-index: AcLj3GM9HQ1e06ZzQLuYh9M2BD675gAQZagwADi7kAA=
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: "Hearty, John" <John.Hearty@Level3.com>, <sipping@ietf.org>
X-Approved: ondar
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h27Nu3O27433
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

John,

Thanks for the comments. See below.

Jean-Francois.

> -----Original Message-----
> From: Hearty, John [mailto:John.Hearty@Level3.com] 
> Sent: Thursday, March 06, 2003 2:01 PM
> To: sipping@ietf.org
> Subject: RE: [Sipping] I-D 
> ACTION:draft-ietf-sipping-realtimefax-01.txt
> 
> 
> A comment.  Section 5.3.2 starting at F11, the original 
> stream is being muted by sending 0.0.0.0 in the c= line.  
> This is a depreciated way of doing hold, see RFC3264 section 
> 8.4.  Shouldn't the sendonly/recvonly attributes be used?  
The voice stream is muted but the real-time fax connection is up. I
understand the motivations of rfc3264 to be so that RTCP could still be
exchanged. Isn't the t38 media stream providing some kind of connection
control between the media endpoints? 
We could put the audio connection as inactive. Do we really have to add
the support for the offer/answer model here?
Comments?
Jean-Francois.


> Same for section 5.4.2.
> 
> John Hearty
> Level3
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 18:50:04 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15924
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 18:50:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2801lH28040
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 19:01:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2801lO28037
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 19:01:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15862
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 18:49:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28016O27932;
	Fri, 7 Mar 2003 19:01:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2800DO27872
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 19:00:13 -0500
Received: from zsc3s004.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15679
	for <sipping@ietf.org>; Fri, 7 Mar 2003 18:47:58 -0500 (EST)
Received: from zsc3c028.us.nortel.com (zsc3c028.us.nortel.com [47.81.138.28])
	by zsc3s004.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h27Nnk808567;
	Fri, 7 Mar 2003 15:49:47 -0800 (PST)
Received: by zsc3c028.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1LW2PYZR>; Fri, 7 Mar 2003 15:49:46 -0800
Message-ID: <2F1FC1DEA077D5119FAD00508BCFD6D207105044@zsc3c030.us.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "Mark Watson" <mwatson@nortelnetworks.com>,
        "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'sipping'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 7 Mar 2003 15:49:47 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E504.3BB41E08"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E504.3BB41E08
Content-Type: text/plain

> I am confused by the resistance to solving this problem in the
straightforward way. The 
> existance of in-band media seems a perfectly reasonable thing to want to
signal at the 
> SIP layer. People seem quite happy to give the 183 message this semantic,
for the case 
> where the call state is unknown - why is it such a big deal to convey the
*same
> information* at the SIP layer for the case where the call state is known
to be 
> alerting ?? All I want to do is atomically signal the equivalent of 180
*plus* 183.

Maybe the solution would be to define a 184 "Ringing, with in-band media".

Or we can argue for another 2 year... 

I'd prefer this approach to the one using the reason phrase in the 180.

------_=_NextPart_001_01C2E504.3BB41E08
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>&gt; I am confused by the resistance to solving this problem in the straightforward way. The </FONT>
<BR><FONT SIZE=2>&gt; existance of in-band media seems a perfectly reasonable thing to want to signal at the </FONT>
<BR><FONT SIZE=2>&gt; SIP layer. People seem quite happy to give the 183 message this semantic, for the case </FONT>
<BR><FONT SIZE=2>&gt; where the call state is unknown - why is it such a big deal to convey the *same</FONT>
<BR><FONT SIZE=2>&gt; information* at the SIP layer for the case where the call state is known to be </FONT>
<BR><FONT SIZE=2>&gt; alerting ?? All I want to do is atomically signal the equivalent of 180 *plus* 183.</FONT>
</P>

<P><FONT SIZE=2>Maybe the solution would be to define a 184 &quot;Ringing, with in-band media&quot;.</FONT>
</P>

<P><FONT SIZE=2>Or we can argue for another 2 year... </FONT>
</P>

<P><FONT SIZE=2>I'd prefer this approach to the one using the reason phrase in the 180.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E504.3BB41E08--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar  7 19:35:57 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19397
	for <sipping-archive@odin.ietf.org>; Fri, 7 Mar 2003 19:35:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h280lgP32754
	for sipping-archive@odin.ietf.org; Fri, 7 Mar 2003 19:47:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h280lgO32751
	for <sipping-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 19:47:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19319
	for <sipping-web-archive@ietf.org>; Fri, 7 Mar 2003 19:35:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h280l3O32702;
	Fri, 7 Mar 2003 19:47:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h280e0O31874
	for <sipping@optimus.ietf.org>; Fri, 7 Mar 2003 19:40:00 -0500
Received: from f1ee40-19.idc1.level3.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18503
	for <sipping@ietf.org>; Fri, 7 Mar 2003 19:27:44 -0500 (EST)
Received: from idc1exc0001.corp.global.level3.com (localhost [127.0.0.1])
	by f1ee40-19.idc1.level3.com (8.8.8+Sun/8.8.8) with SMTP id AAA11092;
	Sat, 8 Mar 2003 00:29:46 GMT
Received: from idc1exc0004.corp.global.level3.com ([10.1.6.220]) by idc1exc0001.corp.global.level3.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Fri, 7 Mar 2003 17:29:46 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6334.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] I-D ACTION:draft-ietf-sipping-realtimefax-01.txt
Date: Fri, 7 Mar 2003 17:29:45 -0700
Message-ID: <3DB099919328BA41905F651A6EF83976B4DC61@idc1exc0004.corp.global.level3.com>
Thread-Topic: [Sipping] I-D ACTION:draft-ietf-sipping-realtimefax-01.txt
Thread-Index: AcLj3GM9HQ1e06ZzQLuYh9M2BD675gAQZagwADi7kAAAAgDC4A==
From: "Hearty, John" <John.Hearty@Level3.com>
To: "Jean-Francois Mule" <jf.mule@cablelabs.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 08 Mar 2003 00:29:46.0401 (UTC) FILETIME=[D235E910:01C2E509]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h280e0O31875
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

I think the real address and an inactive attribute may be appropriate.  Any connection control going on for the T.38 stream is only relevant to that stream.  The original audio references a different stream.  I have no strong opinions on this, the 0.0.0.0 just jumped out to me as depreciated, you may want to be consistent with other flows involving audio as this first stream in this draft is.  If anyone implements this, they may have a need to continue receiving RTCP.  Opinions from other folks would be nice here.


> John,
> 
> Thanks for the comments. See below.
> 
> Jean-Francois.
> 
> > -----Original Message-----
> > From: Hearty, John [mailto:John.Hearty@Level3.com] 
> > Sent: Thursday, March 06, 2003 2:01 PM
> > To: sipping@ietf.org
> > Subject: RE: [Sipping] I-D 
> > ACTION:draft-ietf-sipping-realtimefax-01.txt
> > 
> > 
> > A comment.  Section 5.3.2 starting at F11, the original 
> > stream is being muted by sending 0.0.0.0 in the c= line.  
> > This is a depreciated way of doing hold, see RFC3264 section 
> > 8.4.  Shouldn't the sendonly/recvonly attributes be used?  
> The voice stream is muted but the real-time fax connection is up. I
> understand the motivations of rfc3264 to be so that RTCP 
> could still be
> exchanged. Isn't the t38 media stream providing some kind of 
> connection
> control between the media endpoints? 
> We could put the audio connection as inactive. Do we really 
> have to add
> the support for the offer/answer model here?
> Comments?
> Jean-Francois.
> 
> 
> > Same for section 5.4.2.
> > 
> > John Hearty
> > Level3
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sat Mar  8 04:05:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22120
	for <sipping-archive@odin.ietf.org>; Sat, 8 Mar 2003 04:05:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h289HRe18843
	for sipping-archive@odin.ietf.org; Sat, 8 Mar 2003 04:17:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h289HRO18840
	for <sipping-web-archive@optimus.ietf.org>; Sat, 8 Mar 2003 04:17:27 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22095
	for <sipping-web-archive@ietf.org>; Sat, 8 Mar 2003 04:05:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h289GNO18824;
	Sat, 8 Mar 2003 04:16:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h289EoO18780
	for <sipping@optimus.ietf.org>; Sat, 8 Mar 2003 04:14:50 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21897
	for <sipping@ietf.org>; Sat, 8 Mar 2003 04:02:22 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2894QB3009653;
	Sat, 8 Mar 2003 10:04:27 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id GPHZ63V1; Sat, 8 Mar 2003 10:04:26 +0100
Received: from lmf.ericsson.se (sealwa04-252.sw.ericsson.se [130.100.249.252])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2894MlW014109;
	Sat, 8 Mar 2003 11:04:23 +0200 (EET)
Message-ID: <3E69B21B.453FA7A0@lmf.ericsson.se>
Date: Sat, 08 Mar 2003 11:04:27 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Francois Audet <audet@nortelnetworks.com>
CC: Mark Watson <mwatson@nortelnetworks.com>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'sipping'" <sipping@ietf.org>
Subject: Re: [Sipping] New version of the early media draft
References: <2F1FC1DEA077D5119FAD00508BCFD6D207105044@zsc3c030.us.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

I was arguing that any MG will have to implement media arrival detection
anyway, because of the 200 OK-RTP race condition. Therefore, you MG MUST
implement media detection. What do you solve with a SIP provisional
response that tells you that media will be coming? I do not see the
value there. Could somebody explain the gains we get from that approach?

And regarding Mark's comment about placing the functionaloty in the
wrong place, a controller tells (using the media policies developed by
the conferencing design team) the mixer of a conference which
participant's voice should sound louder, which one should be discarded,
etc... you can see this as a media policy issue as well. The MGC sends a
media policy description to the MG:

1) if media comes, play it.

2) until media comes, play ringback tone. 

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sat Mar  8 15:02:13 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26039
	for <sipping-archive@odin.ietf.org>; Sat, 8 Mar 2003 15:02:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h28KELE32214
	for sipping-archive@odin.ietf.org; Sat, 8 Mar 2003 15:14:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28KELO32211
	for <sipping-web-archive@optimus.ietf.org>; Sat, 8 Mar 2003 15:14:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25969
	for <sipping-web-archive@ietf.org>; Sat, 8 Mar 2003 15:01:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28KCuO32070;
	Sat, 8 Mar 2003 15:12:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28K8wO31960
	for <sipping@optimus.ietf.org>; Sat, 8 Mar 2003 15:08:58 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24942
	for <sipping@ietf.org>; Sat, 8 Mar 2003 14:56:16 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h28Jw8C24721;
	Sat, 8 Mar 2003 19:58:08 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JSL24>; Sat, 8 Mar 2003 14:58:17 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214EDF@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'Mark Watson'"
	 <mwatson@nortelnetworks.com>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Sat, 8 Mar 2003 14:58:15 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E5AD.0EA65580"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E5AD.0EA65580
Content-Type: text/plain;
	charset="iso-8859-1"

Cases in which no interworking is encountered and ISUP fails to portray call
status are problematic, sure. Agreed that there are lazy PBXs that may not
use Q.931 correctly, which results in poor ISUP, and so on. But if ISUP lies
to you about call status, then that creates internal problems for the PSTN,
not just interworking with SIP. I'm sure you are aware that there are PSTN
cases in which ringing is not generated by the remote switch, in which
out-of-band signaling causes ringback to be generated elsewhere in the
network. These cases would seem to have problems when out-of-band ISUP
indicators are wrong.
 
I'm not sure that it's our job to design interworking cases around
non-standard usages of PSTN protocols, however. We could similarly say that
if a native SIP endpoint sent a 180 when the call is actually in a state
more indicative of 181, or something, that it would be problematic, but I
don't think we therefore need to say that SIP endpoints always need to
transmit in-band status info.
 
But this is all moot from my perspective - a new in-band indicator for SIP
won't make any of this any easier. You are correct, I am saying that a UAS
gateway should send 183 when it does not know the status of the call - that
is effectively the only in-band indicator that I think we need. But this
fact doesn't interact well with your lack of a 'guarantee' about whether or
not the out-of-band status is accurate, though. Presumably, you think that a
UAS gateway would be required to deliver in-band status info for every call,
because there is never any 'guarantee' that ISUP is correct. I don't think
we should recommend that a gateway always send in-band status information,
whether it would be sent with a 180 or 183. In-band status information, as
I've said before, is bad; how we indicate that there is in-band status info
is orthogonal to the real issue here.
 
Anyway, Gonzalo's draft is concerned with early media as a general
interworking phenomenon, I believe - it isn't just limited to ISUP. So I
agree that Gonzalo's draft is not the right place to recount the various
ISUP indicators and how a gateway UAS will treat them. You are correct that
RFC3398 is the right place for that specification. Currently, though, I
don't see a need to revise its existing text.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com]
Sent: Friday, March 07, 2003 3:04 PM
To: 'Peterson, Jon'; 'Mark Watson'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


Jon,
You are assuming a model in which the UAS gateway call control entity has
perfect knowledge of the content of the media stream.  This is frequently
not true, particularly in a decomposed MGC/MG architecture.  There are two
possible ways for it to gain this knowledge: 1) for the MG to monitor the
media stream and analyze its contents and report the results to the MGC (an
unacceptable solution); or 2) for the MGC to receive this information from
the next hop via the call control protocol on that hop (ISUP/BICC/SIP).  But
for case 2) to work, an MGC depends on the chain of switches all the way to
the terminating switch to accurately signal this information (equivalent to
183 if it's not ringing tone; 180 if it is) in the backward direction.  One
simple example of where this breaks down is when no COT is performed and
there is a link failure (i.e. there is no in-band information even while
alerting).  In effect, the in-band information tests the media path,
providing immediate information about the media path to the caller so the
call can be abandoned if appropriate.  THIS IS NOT POSSIBLE without having a
clear indication in the 180 from the UAS that there is supposed to be
in-band progress information.  The current text would have the UAC inject
local ringing in the absence of in-band media, while what we really want to
do is play silence since there is no media path beyond the UAS anyway!  Many
more examples are possible.  Alerting indication (180) does not necessarily
mean there is in-band ringing when in-band information is present.  There
may be announcements or various tones or nothing, depending on the state of
the network.  There is no guarantee that a UAS gateway will have sufficient
information to send a 183 if in-band call progress information changes
during alerting.
 
In general, I support Mark's analysis of the situation and continue to
request an in-band call progress indication for the 180 response.
 
If you are alternately saying that a UAS gateway that cannot guarantee that
any in-band call progress information it may be sending is in the form of a
ringing tone should send 183 rather than 180 after receiving "subscriber
free" or "alerting" indications, then I can also accept this solution.  But
then this new guideline must be clearly spelled out in either Gonzalo's
draft or RFC 3398, preferably the latter, since a UAS gateway will rarely
send 180 once in-band information is available.  I have seen some strong
resistance to this in prior emails on this reflector.  We can't have it both
ways.
 
Regards,
Richard Ejzak
Lucent Technologies

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: Friday, March 07, 2003 12:03 PM
To: 'Mark Watson'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


 
I'm not sure I missed that point, exactly. I said that if the gateway knows
that the early media is just ringtone, it should send a 180. You're just
citing another case below in which the early media is not ringtone. I can't
see how this contradicts what I said. If there's some other in-band status
information available, the gateway should be using 183.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Friday, March 07, 2003 1:17 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft



Jon, 

You have missed one very important point which is that in-band media during
alerting is not necessarily 'just ringtone'. It is quite common for the call
to be in the 'Alerting' state (and for this to be know to a SIP to ISUP
gateway), but for the in-band media to contain some useful information other
than 'just ringtone'.

For example, in the UK at least, if the called party has Call Waiting, then
the call of course goes straight in to the Alerting state, but the caller
will here a message along the lines 'Please wait while we try to connect
your call - the person you are calling knows you are waiting'.

A second example would be when the call terminates on a queueing system, and
the message played gives the caller some idea of how long they will need to
wait.

I absolutely agree that if the in-band media was 'just ringtone' there would
be no point. In particular I don't see any need to support the PSTN
'feeture' in which you always hear the ringtone of the destination country
(IMO this is a bug, not a feature!).

So, let's recognise that there are cases where *both* out-of-band and
in-band status indications are present. My view is that out-of-band
indications should always be propogated if available - so for the scenario
in question we MUST use 180, not 183. Now we need to indicate that in-band
status is also available - is this really so hard ????

...Mark 

> -----Original Message----- 
> From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> Sent: 07 March 2003 00:09 
> To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo' 
> Cc: Watson, Mark [MOP:EP10:EXCH]; sipping 
> Subject: RE: [Sipping] New version of the early media draft 
> 
> 
> 
> Everything below is familiar ground, and I don't want to 
> start rehearsing 
> these same arguments again. SIP has made a number of design 
> decisions that 
> predispose it towards out-of-band status information. Sending 
> in-band status 
> information in SIP is harmful - period. In-band media should 
> be sent only 
> when the gateway does not know the status of the call, and thus cannot 
> communicate it out-of-band. Below, you basically argue that 
> in cases where 
> the gateway does not know the status of the call, it has to send early 
> media. I agree. I said that in cases in which the gateway 
> knows that the 
> early media is just ringtone, it should send 180. Clearly, if 
> there's some 
> in-band transition in call state from ringtone to some other 
> audible call 
> progress information, and the gateway isn't made aware of it, then the 
> gateway doesn't know the state of the call. Perhaps we might draw the 
> conclusion from your example that out-of-band call status 
> indicators are 
> inherently unreliable, then - and surmise that it is 
> impossible for the 
> gateway to know the state of the call. Or perhaps the 
> likelihood of this 
> condition arising is sufficiently remote, the consequences of 
> sending early 
> media sufficiently troublesome, that we might decide the 
> in-band information 
> in these cases is not 'essential' enough to worry over. But I 
> firmly believe 
> we should leave this to the conscience of the individual gateway 
> implementer. I don't think the early media draft needs to draw that 
> conclusion. 
> 
> Mr. Camarillo's draft already maintains a very delicate 
> balance of behavior 
> to accommodate SIP's needs, and I haven't heard anything in 
> this yet that 
> should alter it. 
> 
> Jon Peterson 
> NeuStar, Inc. 
> 
> > -----Original Message----- 
> > From: Ejzak, Richard P (Richard) [ mailto:ejzak@lucent.com
<mailto:ejzak@lucent.com> ] 
> > Sent: Thursday, March 06, 2003 2:40 PM 
> > To: 'Peterson, Jon'; 'Gonzalo Camarillo' 
> > Cc: Mark Watson; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > Jon, 
> > I must disagree with your blanket recommendation that the 
> > gateway not sent in-band ringing media.  This may be possible 
> > in some cases - and nothing we have suggested would prevent a 
> > gateway from using out-of-band indications.  But ringing is 
> > not the only in-band call progress information you may 
> > receive while trying to establish a call from SIP to ISUP.  
> > The transition from alerting to other forms of in-band call 
> > progress information is not guaranteed to be clearly signaled 
> > by ISUP within an ACM or CPG (since every switch in the 
> > network can safely assume in-band call progress after a 
> > certain point in the call), and it is essential that this 
> > subsequent information (when it exists) be presented to the 
> > UAC/user.  And the notion of having the gateway intelligently 
> > filter what it thinks is ringing and detect a transition to 
> > other forms of call progress is not acceptable. 
> > 
> > Regards, 
> > Richard Ejzak 
> > Lucent Technologies 
> > 
> > 
> > 
> > -----Original Message----- 
> > From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> > Sent: Thursday, March 06, 2003 4:06 PM 
> > To: 'Gonzalo Camarillo' 
> > Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > 
> > Well, 
> > 
> > > -----Original Message----- 
> > > From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se
<mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > [snip] 
> > > 
> > > The scenario he is after is as follows; a gateway *knows* 
> > that the user 
> > > is being alerted and also *knows* that it will be sending in-band 
> > > ringing. 
> > > 
> > 
> > If the gateway knows that it will be sending in-band ringing, 
> > my position is 
> > that the gateway shouldn't be sending that media. It's just 
> > ring tone. The 
> > UAC can generate that itself. Let's not waste the bandwidth 
> > sending ringing, 
> > especially in forking cases, especially because the UAC 
> might not even 
> > render this provisional media (if it's a PC UAC, for example). 
> > 
> > If media arrives at the UAC, it should override local 
> > ringtone, agreed. And 
> > I have no problem with the idea that a UAC would delay local 
> > ringtone for a 
> > short interval in order to see if any media is coming, even 
> > when 180 is 
> > received. But we should not encourage gateways to send 
> ringing media. 
> > 
> > Jon Peterson 
> > NeuStar, Inc. 
> > 
> 


------_=_NextPart_001_01C2E5AD.0EA65580
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=220470723-07032003><SPAN 
class=220470723-07032003>Cases in which no interworking is encountered and ISUP 
fails to portray call status are problematic, sure. Agreed that there are lazy 
PBXs that may not use Q.931 correctly, which results in poor ISUP,&nbsp;and so 
on. <SPAN class=220470723-07032003><SPAN class=220470723-07032003>But if ISUP 
lies to you about call status, then that creates internal problems for the PSTN, 
not just interworking with SIP. I'm sure you are aware that there are PSTN cases 
in which ringing is not generated by the remote switch, in which out-of-band 
signaling causes ringback to be generated&nbsp;elsewhere in the network. These 
cases would seem to have problems when out-of-band ISUP indicators are 
wrong.</SPAN></SPAN></SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=220470723-07032003><SPAN 
class=220470723-07032003></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=220470723-07032003><SPAN 
class=220470723-07032003>I'm not sure that it's our job to design interworking 
cases around non-standard usages of PSTN protocols, however. We could similarly 
say that if a native SIP endpoint sent a 180 when the call is actually in a 
state more indicative of 181, or something, that it would be problematic, but I 
don't think we therefore need to say that SIP endpoints always need to transmit 
in-band status info.</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=220470723-07032003><SPAN 
class=220470723-07032003></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=220470723-07032003><SPAN 
class=220470723-07032003>But this is&nbsp;all moot from my perspective - a new 
in-band indicator for SIP&nbsp;won't make any of this any easier. <SPAN 
class=220470723-07032003>You are correct, I am saying that a UAS gateway should 
send 183 when it does not know the status of the call - that is effectively the 
only in-band indicator that I think we need. But this fact doesn't interact well 
with your lack of a 'guarantee' about whether or not the out-of-band status is 
accurate, though. Presumably, you think that a UAS gateway would be required to 
deliver in-band status info for every call, because there is never 
any&nbsp;'guarantee' that ISUP is correct. I don't think we should recommend 
that a gateway always send in-band status information, whether it would be sent 
with a 180 or 183. In-band status information, as I've said before,&nbsp;is bad; 
how we indicate that there is in-band status info is orthogonal to the real 
issue here.</SPAN></SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=220470723-07032003><SPAN 
class=220470723-07032003></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=220470723-07032003><SPAN 
class=220470723-07032003>Anyway, Gonzalo's draft is concerned with early media 
as a general interworking phenomenon, I believe - it isn't just limited to ISUP. 
So I agree that Gonzalo's draft is not the right place to recount the various 
ISUP indicators and how a gateway UAS will treat them. You are correct that 
RFC3398 is the right place for that specification. Currently, though, I don't 
see a need to revise its existing text.</SPAN></SPAN></FONT><FONT face=Arial 
color=#0000ff size=2><SPAN class=220470723-07032003><SPAN 
class=220470723-07032003></DIV></SPAN></SPAN></FONT>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><SPAN class=220470723-07032003><FONT face=Arial color=#0000ff size=2>Jon 
Peterson</FONT></SPAN></DIV>
<DIV><SPAN class=220470723-07032003><FONT face=Arial color=#0000ff 
size=2>NeuStar, Inc.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Ejzak, Richard P (Richard) 
  [mailto:ejzak@lucent.com]<BR><B>Sent:</B> Friday, March 07, 2003 3:04 
  PM<BR><B>To:</B> 'Peterson, Jon'; 'Mark Watson'; 'Gonzalo 
  Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] New version 
  of the early media draft<BR><BR></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=307152419-07032003>Jon,</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=307152419-07032003>You 
  are assuming a model in which the UAS gateway call control entity has perfect 
  knowledge of the content of the media stream.&nbsp; This is frequently not 
  true, particularly in a decomposed MGC/MG architecture.&nbsp; There are two 
  possible ways for it to gain this knowledge: 1) for the MG to monitor the 
  media stream and analyze its contents and report the results to the MGC (an 
  unacceptable solution); or 2) for the MGC to receive this information from the 
  next hop via the call control protocol on that hop (ISUP/BICC/SIP).&nbsp; But 
  for case 2) to work, an MGC depends on the chain of switches all the way to 
  the terminating switch to accurately signal this information (equivalent to 
  183 if it's not ringing tone; 180 if it is) in the backward direction.&nbsp; 
  One simple example of where this breaks down is when no COT is performed and 
  there is a link failure (i.e. there is no in-band information even while 
  alerting).&nbsp; In effect, the in-band information tests the media path, 
  providing immediate information&nbsp;about the media path&nbsp;to the caller 
  so the call can be abandoned if appropriate.&nbsp; THIS IS NOT POSSIBLE 
  without having a clear indication in the 180 from the UAS that there is 
  supposed to be in-band progress information.&nbsp;&nbsp;The current text would 
  have the UAC inject local ringing in the absence of in-band media, while what 
  we really want to do is play silence since there is no media path beyond the 
  UAS anyway!&nbsp; Many more examples are possible.&nbsp; Alerting indication 
  (180) does not necessarily mean there is in-band ringing when in-band 
  information is present.&nbsp; There may be announcements or various tones or 
  nothing, depending on the state of the network.&nbsp; There is no guarantee 
  that a UAS gateway will have sufficient information to send a 183 if in-band 
  call progress information changes during alerting.</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=307152419-07032003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=307152419-07032003>In 
  general, I support Mark's analysis of the situation and continue to request an 
  in-band call progress indication for the 180 response.</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=307152419-07032003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=307152419-07032003>If 
  you are alternately saying that a UAS gateway that cannot guarantee that any 
  in-band call progress information it may be sending is in the form of a 
  ringing tone&nbsp;should send 183 rather than 180 after receiving "subscriber 
  free" or "alerting" indications, then I can also accept this solution.&nbsp; 
  But then this new guideline must be clearly spelled out in either Gonzalo's 
  draft or RFC 3398, preferably the latter, since a UAS gateway will rarely send 
  180 once in-band information is available.&nbsp; I have seen some strong 
  resistance to this in prior emails on this reflector.&nbsp; We can't have it 
  both ways.</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=307152419-07032003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=307152419-07032003>Regards,</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=307152419-07032003>Richard Ejzak</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=307152419-07032003>Lucent Technologies</SPAN></FONT></DIV>
  <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
    <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
    size=2>-----Original Message-----<BR><B>From:</B> Peterson, Jon 
    [mailto:jon.peterson@neustar.biz]<BR><B>Sent:</B> Friday, March 07, 2003 
    12:03 PM<BR><B>To:</B> 'Mark Watson'; 'Ejzak, Richard P (Richard)'; 'Gonzalo 
    Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] New 
    version of the early media draft<BR><BR></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
    <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
    size=2>I'm not sure I missed that point, exactly. I said that if the gateway 
    knows that the early media is just ringtone, it should send a 180. You're 
    just citing another case below in which the early media is not ringtone. I 
    can't see how this contradicts what I said. If there's some other in-band 
    status information available, the gateway should be using 
    183.</FONT></SPAN></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
    <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
    size=2>Jon Peterson</FONT></SPAN></DIV>
    <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
    size=2>NeuStar, Inc.</FONT></SPAN></DIV>
    <BLOCKQUOTE dir=ltr 
    style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
      <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
      size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
      [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Friday, March 07, 2003 
      1:17 AM<BR><B>To:</B> 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 
      'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] 
      New version of the early media draft<BR><BR></FONT></DIV>
      <P><FONT size=2>Jon,</FONT> </P>
      <P><FONT size=2>You have missed one very important point which is that 
      in-band media during alerting is not necessarily 'just ringtone'. It is 
      quite common for the call to be in the 'Alerting' state (and for this to 
      be know to a SIP to ISUP gateway), but for the in-band media to contain 
      some useful information other than 'just ringtone'.</FONT></P>
      <P><FONT size=2>For example, in the UK at least, if the called party has 
      Call Waiting, then the call of course goes straight in to the Alerting 
      state, but the caller will here a message along the lines 'Please wait 
      while we try to connect your call - the person you are calling knows you 
      are waiting'.</FONT></P>
      <P><FONT size=2>A second example would be when the call terminates on a 
      queueing system, and the message played gives the caller some idea of how 
      long they will need to wait.</FONT></P>
      <P><FONT size=2>I absolutely agree that if the in-band media was 'just 
      ringtone' there would be no point. In particular I don't see any need to 
      support the PSTN 'feeture' in which you always hear the ringtone of the 
      destination country (IMO this is a bug, not a feature!).</FONT></P>
      <P><FONT size=2>So, let's recognise that there are cases where *both* 
      out-of-band and in-band status indications are present. My view is that 
      out-of-band indications should always be propogated if available - so for 
      the scenario in question we MUST use 180, not 183. Now we need to indicate 
      that in-band status is also available - is this really so hard 
      ????</FONT></P>
      <P><FONT size=2>...Mark</FONT> </P>
      <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT 
      size=2>&gt; From: Peterson, Jon [<A 
      href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
      <BR><FONT size=2>&gt; Sent: 07 March 2003 00:09</FONT> <BR><FONT 
      size=2>&gt; To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo 
      Camarillo'</FONT> <BR><FONT size=2>&gt; Cc: Watson, Mark [MOP:EP10:EXCH]; 
      sipping</FONT> <BR><FONT size=2>&gt; Subject: RE: [Sipping] New version of 
      the early media draft</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
      size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
      Everything below is familiar ground, and I don't want to </FONT><BR><FONT 
      size=2>&gt; start rehearsing</FONT> <BR><FONT size=2>&gt; these same 
      arguments again. SIP has made a number of design </FONT><BR><FONT 
      size=2>&gt; decisions that</FONT> <BR><FONT size=2>&gt; predispose it 
      towards out-of-band status information. Sending </FONT><BR><FONT 
      size=2>&gt; in-band status</FONT> <BR><FONT size=2>&gt; information in SIP 
      is harmful - period. In-band media should </FONT><BR><FONT size=2>&gt; be 
      sent only</FONT> <BR><FONT size=2>&gt; when the gateway does not know the 
      status of the call, and thus cannot</FONT> <BR><FONT size=2>&gt; 
      communicate it out-of-band. Below, you basically argue that 
      </FONT><BR><FONT size=2>&gt; in cases where</FONT> <BR><FONT size=2>&gt; 
      the gateway does not know the status of the call, it has to send 
      early</FONT> <BR><FONT size=2>&gt; media. I agree. I said that in cases in 
      which the gateway </FONT><BR><FONT size=2>&gt; knows that the</FONT> 
      <BR><FONT size=2>&gt; early media is just ringtone, it should send 180. 
      Clearly, if </FONT><BR><FONT size=2>&gt; there's some</FONT> <BR><FONT 
      size=2>&gt; in-band transition in call state from ringtone to some other 
      </FONT><BR><FONT size=2>&gt; audible call</FONT> <BR><FONT size=2>&gt; 
      progress information, and the gateway isn't made aware of it, then 
      the</FONT> <BR><FONT size=2>&gt; gateway doesn't know the state of the 
      call. Perhaps we might draw the</FONT> <BR><FONT size=2>&gt; conclusion 
      from your example that out-of-band call status </FONT><BR><FONT 
      size=2>&gt; indicators are</FONT> <BR><FONT size=2>&gt; inherently 
      unreliable, then - and surmise that it is </FONT><BR><FONT size=2>&gt; 
      impossible for the</FONT> <BR><FONT size=2>&gt; gateway to know the state 
      of the call. Or perhaps the </FONT><BR><FONT size=2>&gt; likelihood of 
      this</FONT> <BR><FONT size=2>&gt; condition arising is sufficiently 
      remote, the consequences of </FONT><BR><FONT size=2>&gt; sending 
      early</FONT> <BR><FONT size=2>&gt; media sufficiently troublesome, that we 
      might decide the </FONT><BR><FONT size=2>&gt; in-band information</FONT> 
      <BR><FONT size=2>&gt; in these cases is not 'essential' enough to worry 
      over. But I </FONT><BR><FONT size=2>&gt; firmly believe</FONT> <BR><FONT 
      size=2>&gt; we should leave this to the conscience of the individual 
      gateway</FONT> <BR><FONT size=2>&gt; implementer. I don't think the early 
      media draft needs to draw that</FONT> <BR><FONT size=2>&gt; 
      conclusion.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Mr. 
      Camarillo's draft already maintains a very delicate </FONT><BR><FONT 
      size=2>&gt; balance of behavior</FONT> <BR><FONT size=2>&gt; to 
      accommodate SIP's needs, and I haven't heard anything in </FONT><BR><FONT 
      size=2>&gt; this yet that</FONT> <BR><FONT size=2>&gt; should alter 
      it.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Jon 
      Peterson</FONT> <BR><FONT size=2>&gt; NeuStar, Inc.</FONT> <BR><FONT 
      size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; -----Original 
      Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: Ejzak, Richard P 
      (Richard) [<A 
      href="mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT> 
      <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 2:40 PM</FONT> 
      <BR><FONT size=2>&gt; &gt; To: 'Peterson, Jon'; 'Gonzalo Camarillo'</FONT> 
      <BR><FONT size=2>&gt; &gt; Cc: Mark Watson; sipping</FONT> <BR><FONT 
      size=2>&gt; &gt; Subject: RE: [Sipping] New version of the early media 
      draft</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; Jon,</FONT> <BR><FONT size=2>&gt; &gt; I 
      must disagree with your blanket recommendation that the </FONT><BR><FONT 
      size=2>&gt; &gt; gateway not sent in-band ringing media.&nbsp; This may be 
      possible </FONT><BR><FONT size=2>&gt; &gt; in some cases - and nothing we 
      have suggested would prevent a </FONT><BR><FONT size=2>&gt; &gt; gateway 
      from using out-of-band indications.&nbsp; But ringing is </FONT><BR><FONT 
      size=2>&gt; &gt; not the only in-band call progress information you may 
      </FONT><BR><FONT size=2>&gt; &gt; receive while trying to establish a call 
      from SIP to ISUP.&nbsp; </FONT><BR><FONT size=2>&gt; &gt; The transition 
      from alerting to other forms of in-band call </FONT><BR><FONT size=2>&gt; 
      &gt; progress information is not guaranteed to be clearly signaled 
      </FONT><BR><FONT size=2>&gt; &gt; by ISUP within an ACM or CPG (since 
      every switch in the </FONT><BR><FONT size=2>&gt; &gt; network can safely 
      assume in-band call progress after a </FONT><BR><FONT size=2>&gt; &gt; 
      certain point in the call), and it is essential that this </FONT><BR><FONT 
      size=2>&gt; &gt; subsequent information (when it exists) be presented to 
      the </FONT><BR><FONT size=2>&gt; &gt; UAC/user.&nbsp; And the notion of 
      having the gateway intelligently </FONT><BR><FONT size=2>&gt; &gt; filter 
      what it thinks is ringing and detect a transition to </FONT><BR><FONT 
      size=2>&gt; &gt; other forms of call progress is not acceptable.</FONT> 
      <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
      Regards,</FONT> <BR><FONT size=2>&gt; &gt; Richard Ejzak</FONT> <BR><FONT 
      size=2>&gt; &gt; Lucent Technologies</FONT> <BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; -----Original Message-----</FONT> 
      <BR><FONT size=2>&gt; &gt; From: Peterson, Jon [<A 
      href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
      <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 4:06 PM</FONT> 
      <BR><FONT size=2>&gt; &gt; To: 'Gonzalo Camarillo'</FONT> <BR><FONT 
      size=2>&gt; &gt; Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; 
      sipping</FONT> <BR><FONT size=2>&gt; &gt; Subject: RE: [Sipping] New 
      version of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; Well,</FONT> <BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; &gt; -----Original Message-----</FONT> 
      <BR><FONT size=2>&gt; &gt; &gt; From: Gonzalo Camarillo [<A 
      href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
      <BR><FONT size=2>&gt; &gt; [snip]</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; &gt; The scenario he is after is as 
      follows; a gateway *knows* </FONT><BR><FONT size=2>&gt; &gt; that the 
      user</FONT> <BR><FONT size=2>&gt; &gt; &gt; is being alerted and also 
      *knows* that it will be sending in-band</FONT> <BR><FONT size=2>&gt; &gt; 
      &gt; ringing.</FONT> <BR><FONT size=2>&gt; &gt; &gt; </FONT><BR><FONT 
      size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; If the gateway knows 
      that it will be sending in-band ringing, </FONT><BR><FONT size=2>&gt; &gt; 
      my position is</FONT> <BR><FONT size=2>&gt; &gt; that the gateway 
      shouldn't be sending that media. It's just </FONT><BR><FONT size=2>&gt; 
      &gt; ring tone. The</FONT> <BR><FONT size=2>&gt; &gt; UAC can generate 
      that itself. Let's not waste the bandwidth </FONT><BR><FONT size=2>&gt; 
      &gt; sending ringing,</FONT> <BR><FONT size=2>&gt; &gt; especially in 
      forking cases, especially because the UAC </FONT><BR><FONT size=2>&gt; 
      might not even</FONT> <BR><FONT size=2>&gt; &gt; render this provisional 
      media (if it's a PC UAC, for example).</FONT> <BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; If media arrives at the UAC, it should 
      override local </FONT><BR><FONT size=2>&gt; &gt; ringtone, agreed. 
      And</FONT> <BR><FONT size=2>&gt; &gt; I have no problem with the idea that 
      a UAC would delay local </FONT><BR><FONT size=2>&gt; &gt; ringtone for 
      a</FONT> <BR><FONT size=2>&gt; &gt; short interval in order to see if any 
      media is coming, even </FONT><BR><FONT size=2>&gt; &gt; when 180 is</FONT> 
      <BR><FONT size=2>&gt; &gt; received. But we should not encourage gateways 
      to send </FONT><BR><FONT size=2>&gt; ringing media.</FONT> <BR><FONT 
      size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Jon Peterson</FONT> 
      <BR><FONT size=2>&gt; &gt; NeuStar, Inc. </FONT><BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; 
</FONT></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E5AD.0EA65580--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sat Mar  8 16:24:25 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11973
	for <sipping-archive@odin.ietf.org>; Sat, 8 Mar 2003 16:24:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h28LaZ505916
	for sipping-archive@odin.ietf.org; Sat, 8 Mar 2003 16:36:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28LaZO05913
	for <sipping-web-archive@optimus.ietf.org>; Sat, 8 Mar 2003 16:36:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11895
	for <sipping-web-archive@ietf.org>; Sat, 8 Mar 2003 16:23:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28LZpO05875;
	Sat, 8 Mar 2003 16:35:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28LWwO05758
	for <sipping@optimus.ietf.org>; Sat, 8 Mar 2003 16:32:58 -0500
Received: from pmesmtp02.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11193
	for <sipping@ietf.org>; Sat, 8 Mar 2003 16:20:15 -0500 (EST)
Received: from dgismtp04.wcomnet.com ([166.38.58.144])
 by firewall.wcom.com (Iplanet MTA )
 with ESMTP id <0HBG00F8M8KJMQ@firewall.wcom.com> for sipping@ietf.org; Sat,
 08 Mar 2003 21:19:31 +0000 (GMT)
Received: from dgismtp04.wcomnet.com by dgismtp04.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HBG00L018KJOZ@dgismtp04.wcomnet.com>; Sat,
 08 Mar 2003 21:19:31 +0000 (GMT)
Received: from hsinnreich2 ([166.50.135.38])
 by dgismtp04.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HBG00I5D8K2P8@dgismtp04.wcomnet.com>; Sat,
 08 Mar 2003 21:19:30 +0000 (GMT)
Date: Sat, 08 Mar 2003 15:19:14 -0600
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sipping] New version of the early media draft
In-reply-to: 
 <DBC3D7D0A071F743AE0767C9C6071EDA0482BBD1@il0015exch010u.ih.lucent.com>
To: "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>
Cc: "'sipping'" <sipping@ietf.org>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Message-id: <001301c2e5b8$684f0ef0$268732a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>particularly in a decomposed MGC/MG architecture.

Why is this relevant to this working group?
 
It was shown to be an arguable decomposition anyway. Please see the
early I-D's on component servers. This working group has clearly
articulated the call control and component server architecture instead. 

I suggest we limit the discussion to the SIPPING WG architecture.

Thanks, Henry


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sat Mar  8 16:26:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12313
	for <sipping-archive@odin.ietf.org>; Sat, 8 Mar 2003 16:26:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h28LceS06900
	for sipping-archive@odin.ietf.org; Sat, 8 Mar 2003 16:38:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28LceO06897
	for <sipping-web-archive@optimus.ietf.org>; Sat, 8 Mar 2003 16:38:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12214
	for <sipping-web-archive@ietf.org>; Sat, 8 Mar 2003 16:25:57 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28Lc2O06770;
	Sat, 8 Mar 2003 16:38:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28LWxO05762
	for <sipping@optimus.ietf.org>; Sat, 8 Mar 2003 16:32:59 -0500
Received: from pmesmtp02.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11204
	for <sipping@ietf.org>; Sat, 8 Mar 2003 16:20:17 -0500 (EST)
Received: from dgismtp04.wcomnet.com ([166.38.58.144])
 by firewall.wcom.com (Iplanet MTA )
 with ESMTP id <0HBG00F938KPMQ@firewall.wcom.com> for sipping@ietf.org; Sat,
 08 Mar 2003 21:19:37 +0000 (GMT)
Received: from dgismtp04.wcomnet.com by dgismtp04.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HBG00L018KOP3@dgismtp04.wcomnet.com>; Sat,
 08 Mar 2003 21:19:37 +0000 (GMT)
Received: from hsinnreich2 ([166.50.135.38])
 by dgismtp04.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HBG00I5D8K2P8@dgismtp04.wcomnet.com>; Sat,
 08 Mar 2003 21:19:36 +0000 (GMT)
Date: Sat, 08 Mar 2003 15:19:14 -0600
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sipping] Updated Version of MSCML
In-reply-to: <4A3384433CE2AB46A63468CB207E209D097C2D@zoe.office.snowshore.com>
To: "'Eric Burger'" <eburger@snowshore.com>,
        "'Garland Sharratt'" <gsharratt@convedia.com>
Cc: "'Sipping (E-mail)'" <sipping@ietf.org>
Message-id: <001d01c2e5b8$6b9a9070$268732a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The only licensing terms I like is to hand over the IP to the ISOC, as
been done before.

Thanks, Henry


I've stopped 2,685 spam messages. You can too!
Get your free, safe spam protection at
http://www.cloudmark.com/spamnetsig/



> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of Eric Burger
> Sent: Thursday, March 06, 2003 2:40 PM
> To: Garland Sharratt
> Cc: Sipping (E-mail)
> Subject: RE: [Sipping] Updated Version of MSCML
> 
> 
> Your eyes are better than mine.  The IPR notice is supposed 
> to be on -01, too.  That might be a newbie xml-rfc goof.
> 
> That said, did you read the IPR disclosure?  If you had, you 
> would have seen very liberal licensing terms.
> 
> We have received a lot of feedback and interest in MSCML.  
> This feedback has been both in public on the list and in 
> private, from service providers, vendors, partners, and 
> competitors.  Given our desire to promote standards in this 
> area, we have revised our IPR licensing terms.
> 
> Our attorneys are currently doing a review of all of the IETF 
> IPR disclosures.  The review is not complete yet, but it 
> looks like SnowShore's revised disclosure statement is the 
> ONLY royalty free license that does not ask other people to 
> give away their *entire* portfolio.
> 
> The updated disclosure has been given to the Secretariat and 
> should be posted shortly.  Until then, you can find it at 
> <http://flyingfox.snowshore.com/i-d/IETF%20IPR%20draft-vandyke
> -mscml.txt>
> 
> > -----Original Message-----
> > From: Garland Sharratt [mailto:gsharratt@convedia.com]
> > Sent: Wednesday, February 05, 2003 2:59 PM
> > To: Eric Burger
> > Cc: Sipping@Ietf. Org
> > Subject: RE: [Sipping] Updated Version of MSCML
> > 
> > 
> > Eric:
> > 
> > I took a look at draft-vandyke-mscml-01 and saw no
> > substantive changes.
> > 
> > MSCML isn't perfect but my only real concern with it (both 01
> > and 00) is
> > the fact that SnowShore has claimed IPR on it.  This doesn't 
> > work for an
> > interface that is supposed to be -- and otherwise likely would be --
> > adopted by all call agent and media server vendors who need 
> > its type of
> > media server control.
> > 
> > I did notice that the following paragraph in 00 --
> > 
> >    "The IETF has been notified of intellectual property 
> rights claimed 
> > in regard to some or all of the specification contained in this 
> > document.  For more information consult the online list of claimed 
> > rights."
> > 
> > -- has been removed in 01.  But the SnowShore notice on the
> > IETF Page of
> > Intellectual Property Rights Notices is still present 
> > ("SnowShore Patent
> > Statement pertaining to draft-vandyke-mscml").
> > 
> > Is there any chance of getting MSCML released into the public
> > domain so
> > that it can be widely and safely adopted by everyone?
> > 
> > Thanks,
> > 
> > Garland
> > 
> > 
> > -----Original Message-----
> > From: sipping-admin@ietf.org
> > [mailto:sipping-admin@ietf.org]On Behalf Of
> > Eric Burger
> > Sent: Monday, February 03, 2003 11:54
> > To: Sipping (E-mail)
> > Subject: [Sipping] Updated Version of MSCML
> > 
> > 
> > Until it hits the archive:
> > 
> > http://flyingfox.snowshore.com/i-d/sip/draft-vandyke-mscml-01.html
> > http://flyingfox.snowshore.com/i-d/sip/draft-vandyke-mscml-01.txt
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sip@ietf.org for new developments of core SIP
> > 
> > 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sat Mar  8 19:18:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14657
	for <sipping-archive@odin.ietf.org>; Sat, 8 Mar 2003 19:18:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h290UFh17496
	for sipping-archive@odin.ietf.org; Sat, 8 Mar 2003 19:30:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h290UFO17493
	for <sipping-web-archive@optimus.ietf.org>; Sat, 8 Mar 2003 19:30:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14568
	for <sipping-web-archive@ietf.org>; Sat, 8 Mar 2003 19:17:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h290TWO17473;
	Sat, 8 Mar 2003 19:29:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h290Q0O17396
	for <sipping@optimus.ietf.org>; Sat, 8 Mar 2003 19:26:00 -0500
Received: from imo-r01.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13838
	for <sipping@ietf.org>; Sat, 8 Mar 2003 19:13:16 -0500 (EST)
Received: from bertculpepper@netscape.net
	by imo-r01.mx.aol.com (mail_out_v34.21.) id 7.1d.7dfaa55 (16214);
	Sat, 8 Mar 2003 19:14:59 -0500 (EST)
Received: from  netscape.net (159.252.8.67.cfl.rr.com [67.8.252.159]) by air-in01.mx.aol.com (v90_r2.5) with ESMTP id MAILININ12-0308191459; Sat, 08 Mar 2003 19:14:59 1900
Message-ID: <3E6A8809.1090909@netscape.net>
Date: Sat, 08 Mar 2003 19:17:13 -0500
From: Bert Culpepper <bertculpepper@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: SIPPING List <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailer: Unknown (No Version)
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Comments on updated KPML draft
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

A few issues came to mind on my reading of the revised KPML I-D.

Section 2 - Overview

The text at the end of this section discusses the inability for a user 
device to know that signaled digits are for KPML processing or the 
recipients of a media stream.  Therefore DTMF must be sent in the media 
stream in addition to be reported using KPML.  It seems to me that if a 
user device receives a KPML document for processing, it'll know based on 
the digit map what is meant for processing vs. sending in the media 
stream.  I realize processing key presses for digit map matching will 
delay the transmission when matches don't occur, however I expect this 
delay to be very small, resulting in no degradation of the user experience.

If a goal of KPML is to satisfy the requirements defined in Application 
Interaction Requirements I-D, then an attribute is needed to indicate 
suppression of reporting indications by any other means.  A default (if 
not present) for this attribute could result in DTMF being sent as 
described.

Section 4 - SIP Reporting

It's stated that the NOTIFY is sent to the Contact contained in an 
INVITE.  How does this support SIP proxy-based applications? 
draft-jennings-sip-app-info-00 allows proxies to add, delete, and read 
App-Info header values.  Or is the use of the NOTIFY method to be 
limited to the endpoints of a SIP session, and any other entity must use 
HTTP?

Another issue is that it's stated that a KPML session ends when a NOTIFY 
is sent, and further KPML sessions must be established with a reINVITE. 
  Why not allow a KPML document in the body of the 200 OK response to 
the NOTIFY as specified similarly for HTTP reporting?  This saves three 
messages between the application and user device.

According to RFC 3265, NOTIFY requests MUST contain an Event header. 
What would the value of this header be for KPML bodies?

Regards,
Bert

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 03:44:58 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22941
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 03:44:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2A8vpH23999
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 03:57:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A8voO23996
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 03:57:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22858
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 03:44:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A8ueO23958;
	Mon, 10 Mar 2003 03:56:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A8seO23899
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 03:54:40 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22314
	for <sipping@ietf.org>; Mon, 10 Mar 2003 03:41:16 -0500 (EST)
Received: from esealnt610.al.sw.ericsson.se (alteon-nat3.sw.ericsson.se [153.88.254.120])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2A8hMB3015480;
	Mon, 10 Mar 2003 09:43:22 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id FD4J8ZA9; Mon, 10 Mar 2003 09:43:21 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2A8hKlW020718;
	Mon, 10 Mar 2003 10:43:21 +0200 (EET)
Message-ID: <3E6C5027.DF4AB52C@lmf.ericsson.se>
Date: Mon, 10 Mar 2003 10:43:20 +0200
X-Sybari-Trust: 751dd506 9ffcebbb 7a95d2f4 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vkg@lucent.com, rajnishjain@lucent.com
CC: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Persistent Connections
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello,

What would be the difference between the persistent Via parameter
proposed in the draft below (Section 8.1) and the Alias Via parameter
proposed in the connection reuse draft? Does it solve the hint/forced
dilema in any way?

http://www.ietf.org/internet-drafts/draft-jain-sipping-persistent-conn-reqs-00.txt

Regarding the new transport token proposed in Section 8.3, the current
trend is not to define new transport tokens. That's why RFC 3486, for
instance, describes a SIP mechanism rather than a DNS based mechanism.

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 04:16:23 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28748
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 04:16:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2A9THn26455
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 04:29:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A9THO26452
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 04:29:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28645
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 04:15:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A9SPO26434;
	Mon, 10 Mar 2003 04:28:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A9RYO26405
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 04:27:34 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28368
	for <sipping@ietf.org>; Mon, 10 Mar 2003 04:14:07 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2A9G6418611;
	Mon, 10 Mar 2003 04:16:07 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2A9G3f01507;
	Mon, 10 Mar 2003 09:16:04 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GR67088T; Mon, 10 Mar 2003 09:16:03 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GR4VMLJ6>; Mon, 10 Mar 2003 09:14:55 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C5D@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Mon, 10 Mar 2003 09:14:54 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E6E5.2FFFDA92"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E6E5.2FFFDA92
Content-Type: text/plain;
	charset="iso-8859-1"

Jon,
 
If I use 183 then I lose the functional (out of band) indication that the
call is now in the Alerting state. So then, for example, a more advanced SIP
client may not provide the correct visual indication to the use ('ringing'
icon, or whatever).
 
We are talking about cases where the call state IS known to be 'Alerting',
so I think we must surely use 180, not 183. But there are useful in-band
tones AS WELL. In general a gateway would not know whether the in-band
information was boring ringtone, or something more interesting.
 
...Mark

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: 07 March 2003 18:03
To: Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P (Richard)'; 'Gonzalo
Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


 
I'm not sure I missed that point, exactly. I said that if the gateway knows
that the early media is just ringtone, it should send a 180. You're just
citing another case below in which the early media is not ringtone. I can't
see how this contradicts what I said. If there's some other in-band status
information available, the gateway should be using 183.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Friday, March 07, 2003 1:17 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft



Jon, 

You have missed one very important point which is that in-band media during
alerting is not necessarily 'just ringtone'. It is quite common for the call
to be in the 'Alerting' state (and for this to be know to a SIP to ISUP
gateway), but for the in-band media to contain some useful information other
than 'just ringtone'.

For example, in the UK at least, if the called party has Call Waiting, then
the call of course goes straight in to the Alerting state, but the caller
will here a message along the lines 'Please wait while we try to connect
your call - the person you are calling knows you are waiting'.

A second example would be when the call terminates on a queueing system, and
the message played gives the caller some idea of how long they will need to
wait.

I absolutely agree that if the in-band media was 'just ringtone' there would
be no point. In particular I don't see any need to support the PSTN
'feeture' in which you always hear the ringtone of the destination country
(IMO this is a bug, not a feature!).

So, let's recognise that there are cases where *both* out-of-band and
in-band status indications are present. My view is that out-of-band
indications should always be propogated if available - so for the scenario
in question we MUST use 180, not 183. Now we need to indicate that in-band
status is also available - is this really so hard ????

...Mark 

> -----Original Message----- 
> From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> Sent: 07 March 2003 00:09 
> To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo' 
> Cc: Watson, Mark [MOP:EP10:EXCH]; sipping 
> Subject: RE: [Sipping] New version of the early media draft 
> 
> 
> 
> Everything below is familiar ground, and I don't want to 
> start rehearsing 
> these same arguments again. SIP has made a number of design 
> decisions that 
> predispose it towards out-of-band status information. Sending 
> in-band status 
> information in SIP is harmful - period. In-band media should 
> be sent only 
> when the gateway does not know the status of the call, and thus cannot 
> communicate it out-of-band. Below, you basically argue that 
> in cases where 
> the gateway does not know the status of the call, it has to send early 
> media. I agree. I said that in cases in which the gateway 
> knows that the 
> early media is just ringtone, it should send 180. Clearly, if 
> there's some 
> in-band transition in call state from ringtone to some other 
> audible call 
> progress information, and the gateway isn't made aware of it, then the 
> gateway doesn't know the state of the call. Perhaps we might draw the 
> conclusion from your example that out-of-band call status 
> indicators are 
> inherently unreliable, then - and surmise that it is 
> impossible for the 
> gateway to know the state of the call. Or perhaps the 
> likelihood of this 
> condition arising is sufficiently remote, the consequences of 
> sending early 
> media sufficiently troublesome, that we might decide the 
> in-band information 
> in these cases is not 'essential' enough to worry over. But I 
> firmly believe 
> we should leave this to the conscience of the individual gateway 
> implementer. I don't think the early media draft needs to draw that 
> conclusion. 
> 
> Mr. Camarillo's draft already maintains a very delicate 
> balance of behavior 
> to accommodate SIP's needs, and I haven't heard anything in 
> this yet that 
> should alter it. 
> 
> Jon Peterson 
> NeuStar, Inc. 
> 
> > -----Original Message----- 
> > From: Ejzak, Richard P (Richard) [ mailto:ejzak@lucent.com
<mailto:ejzak@lucent.com> ] 
> > Sent: Thursday, March 06, 2003 2:40 PM 
> > To: 'Peterson, Jon'; 'Gonzalo Camarillo' 
> > Cc: Mark Watson; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > Jon, 
> > I must disagree with your blanket recommendation that the 
> > gateway not sent in-band ringing media.  This may be possible 
> > in some cases - and nothing we have suggested would prevent a 
> > gateway from using out-of-band indications.  But ringing is 
> > not the only in-band call progress information you may 
> > receive while trying to establish a call from SIP to ISUP.  
> > The transition from alerting to other forms of in-band call 
> > progress information is not guaranteed to be clearly signaled 
> > by ISUP within an ACM or CPG (since every switch in the 
> > network can safely assume in-band call progress after a 
> > certain point in the call), and it is essential that this 
> > subsequent information (when it exists) be presented to the 
> > UAC/user.  And the notion of having the gateway intelligently 
> > filter what it thinks is ringing and detect a transition to 
> > other forms of call progress is not acceptable. 
> > 
> > Regards, 
> > Richard Ejzak 
> > Lucent Technologies 
> > 
> > 
> > 
> > -----Original Message----- 
> > From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> > Sent: Thursday, March 06, 2003 4:06 PM 
> > To: 'Gonzalo Camarillo' 
> > Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > 
> > Well, 
> > 
> > > -----Original Message----- 
> > > From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se
<mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > [snip] 
> > > 
> > > The scenario he is after is as follows; a gateway *knows* 
> > that the user 
> > > is being alerted and also *knows* that it will be sending in-band 
> > > ringing. 
> > > 
> > 
> > If the gateway knows that it will be sending in-band ringing, 
> > my position is 
> > that the gateway shouldn't be sending that media. It's just 
> > ring tone. The 
> > UAC can generate that itself. Let's not waste the bandwidth 
> > sending ringing, 
> > especially in forking cases, especially because the UAC 
> might not even 
> > render this provisional media (if it's a PC UAC, for example). 
> > 
> > If media arrives at the UAC, it should override local 
> > ringtone, agreed. And 
> > I have no problem with the idea that a UAC would delay local 
> > ringtone for a 
> > short interval in order to see if any media is coming, even 
> > when 180 is 
> > received. But we should not encourage gateways to send 
> ringing media. 
> > 
> > Jon Peterson 
> > NeuStar, Inc. 
> > 
> 


------_=_NextPart_001_01C2E6E5.2FFFDA92
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.00.3504.2500" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=007171609-10032003>Jon,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=007171609-10032003>If I 
use 183 then I lose the functional (out of band) indication that the call is now 
in the Alerting state. So then, for example, a more advanced SIP client 
may&nbsp;not provide the correct visual indication to the use ('ringing' icon, 
or whatever).</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=007171609-10032003>We 
are talking about cases where the call state IS known to be 'Alerting', so I 
think we must surely use 180, not 183. But there are useful in-band tones AS 
WELL. In general a gateway would not know whether the in-band information was 
boring ringtone, or something more interesting.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=007171609-10032003>...Mark</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Peterson, Jon 
  [mailto:jon.peterson@neustar.biz]<BR><B>Sent:</B> 07 March 2003 
  18:03<BR><B>To:</B> Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P 
  (Richard)'; 'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: 
  [Sipping] New version of the early media draft<BR><BR></DIV></FONT>
  <DIV><FONT color=#0000ff face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=918445017-07032003><FONT color=#0000ff face=Arial size=2>I'm 
  not sure I missed that point, exactly. I said that if the gateway knows that 
  the early media is just ringtone, it should send a 180. You're just citing 
  another case below in which the early media is not ringtone. I can't see how 
  this contradicts what I said. If there's some other in-band status information 
  available, the gateway should be using 183.</FONT></SPAN></DIV>
  <DIV><FONT color=#0000ff face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=918445017-07032003><FONT color=#0000ff face=Arial size=2>Jon 
  Peterson</FONT></SPAN></DIV>
  <DIV><SPAN class=918445017-07032003><FONT color=#0000ff face=Arial 
  size=2>NeuStar, Inc.</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=ltr 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
    size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
    [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Friday, March 07, 2003 
    1:17 AM<BR><B>To:</B> 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 
    'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] 
    New version of the early media draft<BR><BR></FONT></DIV>
    <P><FONT size=2>Jon,</FONT> </P>
    <P><FONT size=2>You have missed one very important point which is that 
    in-band media during alerting is not necessarily 'just ringtone'. It is 
    quite common for the call to be in the 'Alerting' state (and for this to be 
    know to a SIP to ISUP gateway), but for the in-band media to contain some 
    useful information other than 'just ringtone'.</FONT></P>
    <P><FONT size=2>For example, in the UK at least, if the called party has 
    Call Waiting, then the call of course goes straight in to the Alerting 
    state, but the caller will here a message along the lines 'Please wait while 
    we try to connect your call - the person you are calling knows you are 
    waiting'.</FONT></P>
    <P><FONT size=2>A second example would be when the call terminates on a 
    queueing system, and the message played gives the caller some idea of how 
    long they will need to wait.</FONT></P>
    <P><FONT size=2>I absolutely agree that if the in-band media was 'just 
    ringtone' there would be no point. In particular I don't see any need to 
    support the PSTN 'feeture' in which you always hear the ringtone of the 
    destination country (IMO this is a bug, not a feature!).</FONT></P>
    <P><FONT size=2>So, let's recognise that there are cases where *both* 
    out-of-band and in-band status indications are present. My view is that 
    out-of-band indications should always be propogated if available - so for 
    the scenario in question we MUST use 180, not 183. Now we need to indicate 
    that in-band status is also available - is this really so hard 
    ????</FONT></P>
    <P><FONT size=2>...Mark</FONT> </P>
    <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
    From: Peterson, Jon [<A 
    href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
    <BR><FONT size=2>&gt; Sent: 07 March 2003 00:09</FONT> <BR><FONT size=2>&gt; 
    To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo'</FONT> 
    <BR><FONT size=2>&gt; Cc: Watson, Mark [MOP:EP10:EXCH]; sipping</FONT> 
    <BR><FONT size=2>&gt; Subject: RE: [Sipping] New version of the early media 
    draft</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
    </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Everything below 
    is familiar ground, and I don't want to </FONT><BR><FONT size=2>&gt; start 
    rehearsing</FONT> <BR><FONT size=2>&gt; these same arguments again. SIP has 
    made a number of design </FONT><BR><FONT size=2>&gt; decisions that</FONT> 
    <BR><FONT size=2>&gt; predispose it towards out-of-band status information. 
    Sending </FONT><BR><FONT size=2>&gt; in-band status</FONT> <BR><FONT 
    size=2>&gt; information in SIP is harmful - period. In-band media should 
    </FONT><BR><FONT size=2>&gt; be sent only</FONT> <BR><FONT size=2>&gt; when 
    the gateway does not know the status of the call, and thus cannot</FONT> 
    <BR><FONT size=2>&gt; communicate it out-of-band. Below, you basically argue 
    that </FONT><BR><FONT size=2>&gt; in cases where</FONT> <BR><FONT 
    size=2>&gt; the gateway does not know the status of the call, it has to send 
    early</FONT> <BR><FONT size=2>&gt; media. I agree. I said that in cases in 
    which the gateway </FONT><BR><FONT size=2>&gt; knows that the</FONT> 
    <BR><FONT size=2>&gt; early media is just ringtone, it should send 180. 
    Clearly, if </FONT><BR><FONT size=2>&gt; there's some</FONT> <BR><FONT 
    size=2>&gt; in-band transition in call state from ringtone to some other 
    </FONT><BR><FONT size=2>&gt; audible call</FONT> <BR><FONT size=2>&gt; 
    progress information, and the gateway isn't made aware of it, then 
    the</FONT> <BR><FONT size=2>&gt; gateway doesn't know the state of the call. 
    Perhaps we might draw the</FONT> <BR><FONT size=2>&gt; conclusion from your 
    example that out-of-band call status </FONT><BR><FONT size=2>&gt; indicators 
    are</FONT> <BR><FONT size=2>&gt; inherently unreliable, then - and surmise 
    that it is </FONT><BR><FONT size=2>&gt; impossible for the</FONT> <BR><FONT 
    size=2>&gt; gateway to know the state of the call. Or perhaps the 
    </FONT><BR><FONT size=2>&gt; likelihood of this</FONT> <BR><FONT size=2>&gt; 
    condition arising is sufficiently remote, the consequences of 
    </FONT><BR><FONT size=2>&gt; sending early</FONT> <BR><FONT size=2>&gt; 
    media sufficiently troublesome, that we might decide the </FONT><BR><FONT 
    size=2>&gt; in-band information</FONT> <BR><FONT size=2>&gt; in these cases 
    is not 'essential' enough to worry over. But I </FONT><BR><FONT size=2>&gt; 
    firmly believe</FONT> <BR><FONT size=2>&gt; we should leave this to the 
    conscience of the individual gateway</FONT> <BR><FONT size=2>&gt; 
    implementer. I don't think the early media draft needs to draw that</FONT> 
    <BR><FONT size=2>&gt; conclusion.</FONT> <BR><FONT size=2>&gt; 
    </FONT><BR><FONT size=2>&gt; Mr. Camarillo's draft already maintains a very 
    delicate </FONT><BR><FONT size=2>&gt; balance of behavior</FONT> <BR><FONT 
    size=2>&gt; to accommodate SIP's needs, and I haven't heard anything in 
    </FONT><BR><FONT size=2>&gt; this yet that</FONT> <BR><FONT size=2>&gt; 
    should alter it.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
    Jon Peterson</FONT> <BR><FONT size=2>&gt; NeuStar, Inc.</FONT> <BR><FONT 
    size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; -----Original 
    Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: Ejzak, Richard P 
    (Richard) [<A 
    href="mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT> <BR><FONT 
    size=2>&gt; &gt; Sent: Thursday, March 06, 2003 2:40 PM</FONT> <BR><FONT 
    size=2>&gt; &gt; To: 'Peterson, Jon'; 'Gonzalo Camarillo'</FONT> <BR><FONT 
    size=2>&gt; &gt; Cc: Mark Watson; sipping</FONT> <BR><FONT size=2>&gt; &gt; 
    Subject: RE: [Sipping] New version of the early media draft</FONT> <BR><FONT 
    size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
    size=2>&gt; &gt; Jon,</FONT> <BR><FONT size=2>&gt; &gt; I must disagree with 
    your blanket recommendation that the </FONT><BR><FONT size=2>&gt; &gt; 
    gateway not sent in-band ringing media.&nbsp; This may be possible 
    </FONT><BR><FONT size=2>&gt; &gt; in some cases - and nothing we have 
    suggested would prevent a </FONT><BR><FONT size=2>&gt; &gt; gateway from 
    using out-of-band indications.&nbsp; But ringing is </FONT><BR><FONT 
    size=2>&gt; &gt; not the only in-band call progress information you may 
    </FONT><BR><FONT size=2>&gt; &gt; receive while trying to establish a call 
    from SIP to ISUP.&nbsp; </FONT><BR><FONT size=2>&gt; &gt; The transition 
    from alerting to other forms of in-band call </FONT><BR><FONT size=2>&gt; 
    &gt; progress information is not guaranteed to be clearly signaled 
    </FONT><BR><FONT size=2>&gt; &gt; by ISUP within an ACM or CPG (since every 
    switch in the </FONT><BR><FONT size=2>&gt; &gt; network can safely assume 
    in-band call progress after a </FONT><BR><FONT size=2>&gt; &gt; certain 
    point in the call), and it is essential that this </FONT><BR><FONT 
    size=2>&gt; &gt; subsequent information (when it exists) be presented to the 
    </FONT><BR><FONT size=2>&gt; &gt; UAC/user.&nbsp; And the notion of having 
    the gateway intelligently </FONT><BR><FONT size=2>&gt; &gt; filter what it 
    thinks is ringing and detect a transition to </FONT><BR><FONT size=2>&gt; 
    &gt; other forms of call progress is not acceptable.</FONT> <BR><FONT 
    size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Regards,</FONT> <BR><FONT 
    size=2>&gt; &gt; Richard Ejzak</FONT> <BR><FONT size=2>&gt; &gt; Lucent 
    Technologies</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
    &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
    -----Original Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: Peterson, 
    Jon [<A 
    href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
    <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 4:06 PM</FONT> 
    <BR><FONT size=2>&gt; &gt; To: 'Gonzalo Camarillo'</FONT> <BR><FONT 
    size=2>&gt; &gt; Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; 
    sipping</FONT> <BR><FONT size=2>&gt; &gt; Subject: RE: [Sipping] New version 
    of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
    size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
    size=2>&gt; &gt; Well,</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
    size=2>&gt; &gt; &gt; -----Original Message-----</FONT> <BR><FONT 
    size=2>&gt; &gt; &gt; From: Gonzalo Camarillo [<A 
    href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
    <BR><FONT size=2>&gt; &gt; [snip]</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
    </FONT><BR><FONT size=2>&gt; &gt; &gt; The scenario he is after is as 
    follows; a gateway *knows* </FONT><BR><FONT size=2>&gt; &gt; that the 
    user</FONT> <BR><FONT size=2>&gt; &gt; &gt; is being alerted and also 
    *knows* that it will be sending in-band</FONT> <BR><FONT size=2>&gt; &gt; 
    &gt; ringing.</FONT> <BR><FONT size=2>&gt; &gt; &gt; </FONT><BR><FONT 
    size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; If the gateway knows that 
    it will be sending in-band ringing, </FONT><BR><FONT size=2>&gt; &gt; my 
    position is</FONT> <BR><FONT size=2>&gt; &gt; that the gateway shouldn't be 
    sending that media. It's just </FONT><BR><FONT size=2>&gt; &gt; ring tone. 
    The</FONT> <BR><FONT size=2>&gt; &gt; UAC can generate that itself. Let's 
    not waste the bandwidth </FONT><BR><FONT size=2>&gt; &gt; sending 
    ringing,</FONT> <BR><FONT size=2>&gt; &gt; especially in forking cases, 
    especially because the UAC </FONT><BR><FONT size=2>&gt; might not 
    even</FONT> <BR><FONT size=2>&gt; &gt; render this provisional media (if 
    it's a PC UAC, for example).</FONT> <BR><FONT size=2>&gt; &gt; 
    </FONT><BR><FONT size=2>&gt; &gt; If media arrives at the UAC, it should 
    override local </FONT><BR><FONT size=2>&gt; &gt; ringtone, agreed. 
    And</FONT> <BR><FONT size=2>&gt; &gt; I have no problem with the idea that a 
    UAC would delay local </FONT><BR><FONT size=2>&gt; &gt; ringtone for 
    a</FONT> <BR><FONT size=2>&gt; &gt; short interval in order to see if any 
    media is coming, even </FONT><BR><FONT size=2>&gt; &gt; when 180 is</FONT> 
    <BR><FONT size=2>&gt; &gt; received. But we should not encourage gateways to 
    send </FONT><BR><FONT size=2>&gt; ringing media.</FONT> <BR><FONT 
    size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Jon Peterson</FONT> 
    <BR><FONT size=2>&gt; &gt; NeuStar, Inc. </FONT><BR><FONT size=2>&gt; &gt; 
    </FONT><BR><FONT size=2>&gt; </FONT></P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E6E5.2FFFDA92--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 04:28:06 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01103
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 04:28:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2A9f0N27771
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 04:41:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A9f0O27768
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 04:41:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01004
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 04:27:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A9Y5O26679;
	Mon, 10 Mar 2003 04:34:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A9XUO26619
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 04:33:30 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29448
	for <sipping@ietf.org>; Mon, 10 Mar 2003 04:20:04 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2A9M8419392;
	Mon, 10 Mar 2003 04:22:08 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2A9M5f02423;
	Mon, 10 Mar 2003 09:22:06 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GR6709XW; Mon, 10 Mar 2003 09:22:05 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GR4VMLT1>; Mon, 10 Mar 2003 09:21:44 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C5E@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        "Francois Audet" <audet@nortelnetworks.com>
Cc: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'sipping'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Mon, 10 Mar 2003 09:21:41 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E6E6.0DF889B6"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E6E6.0DF889B6
Content-Type: text/plain;
	charset="iso-8859-1"

And how do I know whether the RTP packets contain actual useful media, or
whether some PSTN gateway is blindly copying silence from the G.711 TDM
stream into RTP ? Is it specified somewhere that PSTN gateways SHALL NOT do
this ?

...Mark

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: 08 March 2003 09:04
> To: Audet, Francois [SC100:4K02:EXCH]
> Cc: Watson, Mark [MOP:EP10:EXCH]; 'Peterson, Jon'; 'Ejzak, Richard P
> (Richard)'; 'sipping'
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Folks,
> 
> I was arguing that any MG will have to implement media 
> arrival detection
> anyway, because of the 200 OK-RTP race condition. Therefore, 
> you MG MUST
> implement media detection. What do you solve with a SIP provisional
> response that tells you that media will be coming? I do not see the
> value there. Could somebody explain the gains we get from 
> that approach?
> 
> And regarding Mark's comment about placing the functionaloty in the
> wrong place, a controller tells (using the media policies developed by
> the conferencing design team) the mixer of a conference which
> participant's voice should sound louder, which one should be 
> discarded,
> etc... you can see this as a media policy issue as well. The 
> MGC sends a
> media policy description to the MG:
> 
> 1) if media comes, play it.
> 
> 2) until media comes, play ringback tone. 
> 
> Gonzalo
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>And how do I know whether the RTP packets contain =
actual useful media, or whether some PSTN gateway is blindly copying =
silence from the G.711 TDM stream into RTP ? Is it specified somewhere =
that PSTN gateways SHALL NOT do this ?</FONT></P>

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

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 08 March 2003 09:04</FONT>
<BR><FONT SIZE=3D2>&gt; To: Audet, Francois [SC100:4K02:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Watson, Mark [MOP:EP10:EXCH]; 'Peterson, =
Jon'; 'Ejzak, Richard P</FONT>
<BR><FONT SIZE=3D2>&gt; (Richard)'; 'sipping'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Folks,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I was arguing that any MG will have to =
implement media </FONT>
<BR><FONT SIZE=3D2>&gt; arrival detection</FONT>
<BR><FONT SIZE=3D2>&gt; anyway, because of the 200 OK-RTP race =
condition. Therefore, </FONT>
<BR><FONT SIZE=3D2>&gt; you MG MUST</FONT>
<BR><FONT SIZE=3D2>&gt; implement media detection. What do you solve =
with a SIP provisional</FONT>
<BR><FONT SIZE=3D2>&gt; response that tells you that media will be =
coming? I do not see the</FONT>
<BR><FONT SIZE=3D2>&gt; value there. Could somebody explain the gains =
we get from </FONT>
<BR><FONT SIZE=3D2>&gt; that approach?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; And regarding Mark's comment about placing the =
functionaloty in the</FONT>
<BR><FONT SIZE=3D2>&gt; wrong place, a controller tells (using the =
media policies developed by</FONT>
<BR><FONT SIZE=3D2>&gt; the conferencing design team) the mixer of a =
conference which</FONT>
<BR><FONT SIZE=3D2>&gt; participant's voice should sound louder, which =
one should be </FONT>
<BR><FONT SIZE=3D2>&gt; discarded,</FONT>
<BR><FONT SIZE=3D2>&gt; etc... you can see this as a media policy issue =
as well. The </FONT>
<BR><FONT SIZE=3D2>&gt; MGC sends a</FONT>
<BR><FONT SIZE=3D2>&gt; media policy description to the MG:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 1) if media comes, play it.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 2) until media comes, play ringback tone. =
</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E6E6.0DF889B6--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 04:37:57 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02880
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 04:37:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2A9opG28365
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 04:50:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A9opO28362
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 04:50:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02792
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 04:37:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A9oBO28332;
	Mon, 10 Mar 2003 04:50:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2A9nCO28271
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 04:49:12 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02497
	for <sipping@ietf.org>; Mon, 10 Mar 2003 04:35:47 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2A9brB3004715;
	Mon, 10 Mar 2003 10:37:53 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id GPH5F2M1; Mon, 10 Mar 2003 10:37:53 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2A9bqlW024258;
	Mon, 10 Mar 2003 11:37:52 +0200 (EET)
Message-ID: <3E6C5CEF.773E39D3@lmf.ericsson.se>
Date: Mon, 10 Mar 2003 11:37:51 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Watson <mwatson@nortelnetworks.com>
CC: Francois Audet <audet@nortelnetworks.com>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'sipping'" <sipping@ietf.org>
Subject: Re: [Sipping] New version of the early media draft
References: <A3C2399B2FACD411A54200508BE39C74054F7C5E@zwcwd00r.europe.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mark,

what is the purpose of a gateway telling you to generate local ringback
and sending you silence at the same time?

Gonzalo

Mark Watson wrote:
> 
> And how do I know whether the RTP packets contain actual useful media,
> or whether some PSTN gateway is blindly copying silence from the G.711
> TDM stream into RTP ? Is it specified somewhere that PSTN gateways
> SHALL NOT do this ?
> 
> ...Mark
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 05:50:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15815
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 05:50:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AB2wa00371
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 06:02:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AB2wO00368
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 06:02:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15721
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 05:49:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AB1hO00328;
	Mon, 10 Mar 2003 06:01:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AB0fO32717
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 06:00:41 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15313
	for <sipping@ietf.org>; Mon, 10 Mar 2003 05:47:13 -0500 (EST)
Received: from znsgs01r.nortelnetworks.com (znsgs01r.nortelnetworks.com [47.137.129.92])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2AAnE407134;
	Mon, 10 Mar 2003 05:49:14 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2AAnBf21631;
	Mon, 10 Mar 2003 10:49:11 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GR68ALWN; Mon, 10 Mar 2003 10:49:11 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GR4VMPPL>; Mon, 10 Mar 2003 10:47:59 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C60@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: "Francois Audet" <audet@nortelnetworks.com>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Ejzak, Richard P (Richard)'" <ejzak@lucent.com>,
        "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Mon, 10 Mar 2003 10:47:59 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E6F2.8453FDAA"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E6F2.8453FDAA
Content-Type: text/plain;
	charset="iso-8859-1"

You've responded to my question with another question! I did not say it had
a purpose, I asked whether there was anything which specified a particular
behaviour.

As I understand things, it is quite common for the MG component of a PSTN
gateway to be rather dumb. It could be instructed to cut-through the
backwards media path immediately the INVITE->IAM is processed, in which case
it will just blindly pass through whatever is received from the PSTN side.

In the case that there is in fact no in-band ringing tone, it would be a
mistake for the UAC to play this media. The UAS (gateway) does in fact have
an indication of whether there is in-band media or not which is could
provide to the UAC with the proposed SIP extension. The UAC can then make a
more intelligent decision on playing the media or local ringback.

I don't think it would be ideal for PSTN gateways to work this way, but it
does not seem an unreasonable implementation given that in the majority of
cases where will be in-band ringing.

So, my question was whether it was *specified* that PSTN gateways will not
do this. If it is specified, then of course the media detection solution can
work in some environments, although I still do not think it is applicable in
all or the most robust solution.

...Mark

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: 10 March 2003 09:38
> To: Watson, Mark [MOP:EP10:EXCH]
> Cc: Audet, Francois [SC100:4K02:EXCH]; 'Peterson, Jon'; 
> 'Ejzak, Richard
> P (Richard)'; 'sipping'
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Mark,
> 
> what is the purpose of a gateway telling you to generate 
> local ringback
> and sending you silence at the same time?
> 
> Gonzalo
> 
> Mark Watson wrote:
> > 
> > And how do I know whether the RTP packets contain actual 
> useful media,
> > or whether some PSTN gateway is blindly copying silence 
> from the G.711
> > TDM stream into RTP ? Is it specified somewhere that PSTN gateways
> > SHALL NOT do this ?
> > 
> > ...Mark
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>You've responded to my question with another =
question! I did not say it had a purpose, I asked whether there was =
anything which specified a particular behaviour.</FONT></P>

<P><FONT SIZE=3D2>As I understand things, it is quite common for the MG =
component of a PSTN gateway to be rather dumb. It could be instructed =
to cut-through the backwards media path immediately the INVITE-&gt;IAM =
is processed, in which case it will just blindly pass through whatever =
is received from the PSTN side.</FONT></P>

<P><FONT SIZE=3D2>In the case that there is in fact no in-band ringing =
tone, it would be a mistake for the UAC to play this media. The UAS =
(gateway) does in fact have an indication of whether there is in-band =
media or not which is could provide to the UAC with the proposed SIP =
extension. The UAC can then make a more intelligent decision on playing =
the media or local ringback.</FONT></P>

<P><FONT SIZE=3D2>I don't think it would be ideal for PSTN gateways to =
work this way, but it does not seem an unreasonable implementation =
given that in the majority of cases where will be in-band =
ringing.</FONT></P>

<P><FONT SIZE=3D2>So, my question was whether it was *specified* that =
PSTN gateways will not do this. If it is specified, then of course the =
media detection solution can work in some environments, although I =
still do not think it is applicable in all or the most robust =
solution.</FONT></P>

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

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 10 March 2003 09:38</FONT>
<BR><FONT SIZE=3D2>&gt; To: Watson, Mark [MOP:EP10:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Audet, Francois [SC100:4K02:EXCH]; =
'Peterson, Jon'; </FONT>
<BR><FONT SIZE=3D2>&gt; 'Ejzak, Richard</FONT>
<BR><FONT SIZE=3D2>&gt; P (Richard)'; 'sipping'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; what is the purpose of a gateway telling you to =
generate </FONT>
<BR><FONT SIZE=3D2>&gt; local ringback</FONT>
<BR><FONT SIZE=3D2>&gt; and sending you silence at the same =
time?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark Watson wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; And how do I know whether the RTP packets =
contain actual </FONT>
<BR><FONT SIZE=3D2>&gt; useful media,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; or whether some PSTN gateway is blindly =
copying silence </FONT>
<BR><FONT SIZE=3D2>&gt; from the G.711</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; TDM stream into RTP ? Is it specified =
somewhere that PSTN gateways</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; SHALL NOT do this ?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ...Mark</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E6F2.8453FDAA--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 08:48:37 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19136
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 08:48:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AE1Zv12464
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 09:01:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AE1ZO12461
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 09:01:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19026
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 08:48:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AE0hO12402;
	Mon, 10 Mar 2003 09:00:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ADxPO12245
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 08:59:25 -0500
Received: from imo-r01.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18585
	for <sipping@ietf.org>; Mon, 10 Mar 2003 08:45:55 -0500 (EST)
Received: from bertculpepper@netscape.net
	by imo-r01.mx.aol.com (mail_out_v34.21.) id 7.1b6.51c8dc1 (16228);
	Mon, 10 Mar 2003 08:47:52 -0500 (EST)
Received: from  netscape.net (159.252.8.67.cfl.rr.com [67.8.252.159]) by air-in02.mx.aol.com (v90_r2.5) with ESMTP id MAILININ24-0310084752; Mon, 10 Mar 2003 08:47:52 -0500
Message-ID: <3E6C9812.3020809@netscape.net>
Date: Mon, 10 Mar 2003 08:50:10 -0500
From: Bert Culpepper <bertculpepper@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: Bert Culpepper <bertculpepper@netscape.net>
CC: Eric Burger <eburger@snowshore.com>, SIPPING List <sipping@ietf.org>
Subject: Re: [Sipping] Comments on updated KPML draft
References: <3E6A8809.1090909@netscape.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailer: Unknown (No Version)
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

A qualification below...

Bert Culpepper wrote:

 > A few issues came to mind on my reading of the revised KPML I-D.
 >
 > Section 2 - Overview
 >
 > The text at the end of this section discusses the inability for a user
 > device to know that signaled digits are for KPML processing or the
 > recipients of a media stream.  Therefore DTMF must be sent in the media
 > stream in addition to be reported using KPML.  It seems to me that if a
 > user device receives a KPML document for processing, it'll know based on
 > the digit map what is meant for processing vs. sending in the media
 > stream.  I realize processing key presses for digit map matching will
 > delay the transmission when matches don't occur, however I expect this
 > delay to be very small, resulting in no degradation of the user 
experience.

Reflecting on my weekend comments, the cases where it would be
OK to delay sending indications in the media stream are limited to very
short digit maps (a single digit practically speaking).  But for those
cases, long digits such as the "long pound", and when focus can be
determined by the user device, it'll be desirable to NOT to have the
indications duplicated in the media stream.

 >
 > If a goal of KPML is to satisfy the requirements defined in Application
 > Interaction Requirements I-D, then an attribute is needed to indicate
 > suppression of reporting indications by any other means.  A default (if
 > not present) for this attribute could result in DTMF being sent as
 > described.
 >
 > Section 4 - SIP Reporting
 >
 > It's stated that the NOTIFY is sent to the Contact contained in an
 > INVITE.  How does this support SIP proxy-based applications?
 > draft-jennings-sip-app-info-00 allows proxies to add, delete, and read
 > App-Info header values.  Or is the use of the NOTIFY method to be
 > limited to the endpoints of a SIP session, and any other entity must use
 > HTTP?
 >
 > Another issue is that it's stated that a KPML session ends when a NOTIFY
 > is sent, and further KPML sessions must be established with a reINVITE.
 >  Why not allow a KPML document in the body of the 200 OK response to the
 > NOTIFY as specified similarly for HTTP reporting?  This saves three
 > messages between the application and user device.
 >
 > According to RFC 3265, NOTIFY requests MUST contain an Event header.
 > What would the value of this header be for KPML bodies?
 >
 > Regards,
 > Bert
 >
 > _______________________________________________
 > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
 > This list is for NEW development of the application of SIP
 > Use sip-implementors@cs.columbia.edu for questions on current sip
 > Use sip@ietf.org for new developments of core SIP
 >



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 11:47:54 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02525
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 11:47:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AH0vb26448
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 12:00:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AH0vO26445
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 12:00:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02511
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 11:47:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AH0CO26358;
	Mon, 10 Mar 2003 12:00:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AGxMO26268
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 11:59:22 -0500
Received: from auemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02407
	for <sipping@ietf.org>; Mon, 10 Mar 2003 11:45:47 -0500 (EST)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by auemail2.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2AGls110118
	for <sipping@ietf.org>; Mon, 10 Mar 2003 11:47:54 -0500 (EST)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2653.19)
	id <1H3R4W6D>; Mon, 10 Mar 2003 10:47:53 -0600
Message-ID: <DBC3D7D0A071F743AE0767C9C6071EDA0482BBD3@il0015exch010u.ih.lucent.com>
From: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: Mark Watson <mwatson@nortelnetworks.com>,
        "'Peterson, Jon'"
	 <jon.peterson@neustar.biz>,
        "'sipping'" <sipping@ietf.org>,
        Francois Audet
	 <audet@nortelnetworks.com>
Subject: RE: [Sipping] New version of the early media draft
Date: Mon, 10 Mar 2003 10:47:39 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Gonzalo,
You ask about the gains from including an indication of in-band call progress information with a 180:

Scenario 1) 183 completes media negotiation, followed by 180.  If there is an in-band media indication in the 180 then the MGC has no need to update the MG with any ring tone instructions or media policy instructions upon receipt of 180, and the MGC does not need to tell the gateway when the period of potential ring tone injection is over (with receipt of 200 OK).  We do not risk the danger of injecting potentially inappropriate local ringtone.  If there is no in-band media indication in the 180 because there is no in-band media, then the media policy instructions could be made more explicit to continue injecting tones even in the presence of some noise (e.g. RTP comfort noise packets, silence packets, or brief periods of sound) since in-band information is not expected.  Any valid shift from local ringing to in-band information should be almost immediately followed by removal of the ringtone and policy instructions.  If they are not removed soon after shifting to in-band me!
dia, the shift was probably done in error.  If the media policy instructions need to handle both cases where there may or may not be in-band media, then how can one tell if the media packets are legitimate call progress information (since in-band call progress may be anything, including silence)?  A hair trigger (one or a small number of RTP packets) seems highly prone to error.  An explicit indication of in-band call progress information, on the other hand, is quite robust.

Scenario 2) 180 completes media negotiation.  The advantages are the same as scenario 1) except that the ringtone and policy instructions can be left out of the initial MG interaction.

Scenario 3) 180 completes media negotiation, followed by 183.  If the 180 included an indication of in-band media, then both the initial ringtone and policy instructions and the subsequent update to remove them (upon receipt of 183) become unnecessary.  If the 180 indicated no in-band media, then there is still the advantage of being able to institute a more intelligent media policy, as described in scenario 1).

Regards,
Richard Ejzak
Lucent Technologies

-----Original Message-----
From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
Sent: Saturday, March 08, 2003 3:04 AM
To: Francois Audet
Cc: Mark Watson; 'Peterson, Jon'; 'Ejzak, Richard P (Richard)';
'sipping'
Subject: Re: [Sipping] New version of the early media draft


Folks,

I was arguing that any MG will have to implement media arrival detection
anyway, because of the 200 OK-RTP race condition. Therefore, you MG MUST
implement media detection. What do you solve with a SIP provisional
response that tells you that media will be coming? I do not see the
value there. Could somebody explain the gains we get from that approach?

And regarding Mark's comment about placing the functionaloty in the
wrong place, a controller tells (using the media policies developed by
the conferencing design team) the mixer of a conference which
participant's voice should sound louder, which one should be discarded,
etc... you can see this as a media policy issue as well. The MGC sends a
media policy description to the MG:

1) if media comes, play it.

2) until media comes, play ringback tone. 

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 11:48:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02543
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 11:48:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AH1NZ26523
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 12:01:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AH1NO26520
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 12:01:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02522
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 11:47:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AH0EO26378;
	Mon, 10 Mar 2003 12:00:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AGxQO26272
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 11:59:26 -0500
Received: from hoemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02409
	for <sipping@ietf.org>; Mon, 10 Mar 2003 11:45:48 -0500 (EST)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by hoemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2AGls627868
	for <sipping@ietf.org>; Mon, 10 Mar 2003 11:47:54 -0500 (EST)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2653.19)
	id <1H3R4W6B>; Mon, 10 Mar 2003 10:47:53 -0600
Message-ID: <DBC3D7D0A071F743AE0767C9C6071EDA0482BBD4@il0015exch010u.ih.lucent.com>
From: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Mark Watson'"
	 <mwatson@nortelnetworks.com>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Mon, 10 Mar 2003 10:47:42 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E724.C4B497A6"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E724.C4B497A6
Content-Type: text/plain;
	charset="iso-8859-1"

Jon,
You point out that "there are PSTN cases in which ringing is not generated by the remote switch, in which out-of-band signaling causes ringback to be generated elsewhere in the network."  Agreed.  There are also PSTN cases in which a remote switch signals the presence of both in-band call progress information AND alerting where the in-band media is not ringing tone.  And there is no problem in this case since the remote switch is not asking for the generation of local ringing - it is asking to have in-band information cut through to the calling party while also signaling alerting out of band.  Nor is this an incorrect use of ISUP - that's why both indications are available.  No where in ISUP does it say that the only in-band call progress information allowed during alerting is ringing tone.
 
Both of these scenarios are common and important in the PSTN today.  What makes it important to support one but not the other?
 
After some more consideration, I also think that it is appropriate and important to include the resolution of this issue in Gonzalo's draft, since the draft already discusses the role of gateways and in-band media.
 
Regards,
Richard Ejzak
Lucent Technologies

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: Saturday, March 08, 2003 1:58 PM
To: 'Ejzak, Richard P (Richard)'; 'Mark Watson'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


Cases in which no interworking is encountered and ISUP fails to portray call status are problematic, sure. Agreed that there are lazy PBXs that may not use Q.931 correctly, which results in poor ISUP, and so on. But if ISUP lies to you about call status, then that creates internal problems for the PSTN, not just interworking with SIP. I'm sure you are aware that there are PSTN cases in which ringing is not generated by the remote switch, in which out-of-band signaling causes ringback to be generated elsewhere in the network. These cases would seem to have problems when out-of-band ISUP indicators are wrong.
 
I'm not sure that it's our job to design interworking cases around non-standard usages of PSTN protocols, however. We could similarly say that if a native SIP endpoint sent a 180 when the call is actually in a state more indicative of 181, or something, that it would be problematic, but I don't think we therefore need to say that SIP endpoints always need to transmit in-band status info.
 
But this is all moot from my perspective - a new in-band indicator for SIP won't make any of this any easier. You are correct, I am saying that a UAS gateway should send 183 when it does not know the status of the call - that is effectively the only in-band indicator that I think we need. But this fact doesn't interact well with your lack of a 'guarantee' about whether or not the out-of-band status is accurate, though. Presumably, you think that a UAS gateway would be required to deliver in-band status info for every call, because there is never any 'guarantee' that ISUP is correct. I don't think we should recommend that a gateway always send in-band status information, whether it would be sent with a 180 or 183. In-band status information, as I've said before, is bad; how we indicate that there is in-band status info is orthogonal to the real issue here.
 
Anyway, Gonzalo's draft is concerned with early media as a general interworking phenomenon, I believe - it isn't just limited to ISUP. So I agree that Gonzalo's draft is not the right place to recount the various ISUP indicators and how a gateway UAS will treat them. You are correct that RFC3398 is the right place for that specification. Currently, though, I don't see a need to revise its existing text.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com]
Sent: Friday, March 07, 2003 3:04 PM
To: 'Peterson, Jon'; 'Mark Watson'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


Jon,
You are assuming a model in which the UAS gateway call control entity has perfect knowledge of the content of the media stream.  This is frequently not true, particularly in a decomposed MGC/MG architecture.  There are two possible ways for it to gain this knowledge: 1) for the MG to monitor the media stream and analyze its contents and report the results to the MGC (an unacceptable solution); or 2) for the MGC to receive this information from the next hop via the call control protocol on that hop (ISUP/BICC/SIP).  But for case 2) to work, an MGC depends on the chain of switches all the way to the terminating switch to accurately signal this information (equivalent to 183 if it's not ringing tone; 180 if it is) in the backward direction.  One simple example of where this breaks down is when no COT is performed and there is a link failure (i.e. there is no in-band information even while alerting).  In effect, the in-band information tests the media path, providing immediate i!
nformation about the media path to the caller so the call can be abandoned if appropriate.  THIS IS NOT POSSIBLE without having a clear indication in the 180 from the UAS that there is supposed to be in-band progress information.  The current text would have the UAC inject local ringing in the absence of in-band media, while what we really want to do is play silence since there is no media path beyond the UAS anyway!  Many more examples are possible.  Alerting indication (180) does not necessarily mean there is in-band ringing when in-band information is present.  There may be announcements or various tones or nothing, depending on the state of the network.  There is no guarantee that a UAS gateway will have sufficient information to send a 183 if in-band call progress information changes during alerting.
 
In general, I support Mark's analysis of the situation and continue to request an in-band call progress indication for the 180 response.
 
If you are alternately saying that a UAS gateway that cannot guarantee that any in-band call progress information it may be sending is in the form of a ringing tone should send 183 rather than 180 after receiving "subscriber free" or "alerting" indications, then I can also accept this solution.  But then this new guideline must be clearly spelled out in either Gonzalo's draft or RFC 3398, preferably the latter, since a UAS gateway will rarely send 180 once in-band information is available.  I have seen some strong resistance to this in prior emails on this reflector.  We can't have it both ways.
 
Regards,
Richard Ejzak
Lucent Technologies

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: Friday, March 07, 2003 12:03 PM
To: 'Mark Watson'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


 
I'm not sure I missed that point, exactly. I said that if the gateway knows that the early media is just ringtone, it should send a 180. You're just citing another case below in which the early media is not ringtone. I can't see how this contradicts what I said. If there's some other in-band status information available, the gateway should be using 183.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Friday, March 07, 2003 1:17 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft



Jon, 

You have missed one very important point which is that in-band media during alerting is not necessarily 'just ringtone'. It is quite common for the call to be in the 'Alerting' state (and for this to be know to a SIP to ISUP gateway), but for the in-band media to contain some useful information other than 'just ringtone'.

For example, in the UK at least, if the called party has Call Waiting, then the call of course goes straight in to the Alerting state, but the caller will here a message along the lines 'Please wait while we try to connect your call - the person you are calling knows you are waiting'.

A second example would be when the call terminates on a queueing system, and the message played gives the caller some idea of how long they will need to wait.

I absolutely agree that if the in-band media was 'just ringtone' there would be no point. In particular I don't see any need to support the PSTN 'feeture' in which you always hear the ringtone of the destination country (IMO this is a bug, not a feature!).

So, let's recognise that there are cases where *both* out-of-band and in-band status indications are present. My view is that out-of-band indications should always be propogated if available - so for the scenario in question we MUST use 180, not 183. Now we need to indicate that in-band status is also available - is this really so hard ????

...Mark 

> -----Original Message----- 
> From: Peterson, Jon [ mailto:jon.peterson@neustar.biz <mailto:jon.peterson@neustar.biz> ] 
> Sent: 07 March 2003 00:09 
> To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo' 
> Cc: Watson, Mark [MOP:EP10:EXCH]; sipping 
> Subject: RE: [Sipping] New version of the early media draft 
> 
> 
> 
> Everything below is familiar ground, and I don't want to 
> start rehearsing 
> these same arguments again. SIP has made a number of design 
> decisions that 
> predispose it towards out-of-band status information. Sending 
> in-band status 
> information in SIP is harmful - period. In-band media should 
> be sent only 
> when the gateway does not know the status of the call, and thus cannot 
> communicate it out-of-band. Below, you basically argue that 
> in cases where 
> the gateway does not know the status of the call, it has to send early 
> media. I agree. I said that in cases in which the gateway 
> knows that the 
> early media is just ringtone, it should send 180. Clearly, if 
> there's some 
> in-band transition in call state from ringtone to some other 
> audible call 
> progress information, and the gateway isn't made aware of it, then the 
> gateway doesn't know the state of the call. Perhaps we might draw the 
> conclusion from your example that out-of-band call status 
> indicators are 
> inherently unreliable, then - and surmise that it is 
> impossible for the 
> gateway to know the state of the call. Or perhaps the 
> likelihood of this 
> condition arising is sufficiently remote, the consequences of 
> sending early 
> media sufficiently troublesome, that we might decide the 
> in-band information 
> in these cases is not 'essential' enough to worry over. But I 
> firmly believe 
> we should leave this to the conscience of the individual gateway 
> implementer. I don't think the early media draft needs to draw that 
> conclusion. 
> 
> Mr. Camarillo's draft already maintains a very delicate 
> balance of behavior 
> to accommodate SIP's needs, and I haven't heard anything in 
> this yet that 
> should alter it. 
> 
> Jon Peterson 
> NeuStar, Inc. 
> 
> > -----Original Message----- 
> > From: Ejzak, Richard P (Richard) [ mailto:ejzak@lucent.com <mailto:ejzak@lucent.com> ] 
> > Sent: Thursday, March 06, 2003 2:40 PM 
> > To: 'Peterson, Jon'; 'Gonzalo Camarillo' 
> > Cc: Mark Watson; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > Jon, 
> > I must disagree with your blanket recommendation that the 
> > gateway not sent in-band ringing media.  This may be possible 
> > in some cases - and nothing we have suggested would prevent a 
> > gateway from using out-of-band indications.  But ringing is 
> > not the only in-band call progress information you may 
> > receive while trying to establish a call from SIP to ISUP.  
> > The transition from alerting to other forms of in-band call 
> > progress information is not guaranteed to be clearly signaled 
> > by ISUP within an ACM or CPG (since every switch in the 
> > network can safely assume in-band call progress after a 
> > certain point in the call), and it is essential that this 
> > subsequent information (when it exists) be presented to the 
> > UAC/user.  And the notion of having the gateway intelligently 
> > filter what it thinks is ringing and detect a transition to 
> > other forms of call progress is not acceptable. 
> > 
> > Regards, 
> > Richard Ejzak 
> > Lucent Technologies 
> > 
> > 
> > 
> > -----Original Message----- 
> > From: Peterson, Jon [ mailto:jon.peterson@neustar.biz <mailto:jon.peterson@neustar.biz> ] 
> > Sent: Thursday, March 06, 2003 4:06 PM 
> > To: 'Gonzalo Camarillo' 
> > Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > 
> > Well, 
> > 
> > > -----Original Message----- 
> > > From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se <mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > [snip] 
> > > 
> > > The scenario he is after is as follows; a gateway *knows* 
> > that the user 
> > > is being alerted and also *knows* that it will be sending in-band 
> > > ringing. 
> > > 
> > 
> > If the gateway knows that it will be sending in-band ringing, 
> > my position is 
> > that the gateway shouldn't be sending that media. It's just 
> > ring tone. The 
> > UAC can generate that itself. Let's not waste the bandwidth 
> > sending ringing, 
> > especially in forking cases, especially because the UAC 
> might not even 
> > render this provisional media (if it's a PC UAC, for example). 
> > 
> > If media arrives at the UAC, it should override local 
> > ringtone, agreed. And 
> > I have no problem with the idea that a UAC would delay local 
> > ringtone for a 
> > short interval in order to see if any media is coming, even 
> > when 180 is 
> > received. But we should not encourage gateways to send 
> ringing media. 
> > 
> > Jon Peterson 
> > NeuStar, Inc. 
> > 
> 


------_=_NextPart_001_01C2E724.C4B497A6
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.50.4922.900" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=291223214-10032003>Jon,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=291223214-10032003>You&nbsp;point out that "there are PSTN cases in which 
ringing is not generated by the remote switch, in which out-of-band signaling 
causes ringback to be generated&nbsp;elsewhere in the network."&nbsp; 
Agreed.&nbsp; There are also PSTN cases in which a remote switch signals the 
presence of both in-band call progress information AND alerting where the 
in-band media is not ringing tone.&nbsp; And there is no problem in this case 
since the remote switch is not asking for the generation of local ringing - it 
is asking to have in-band information cut through to the calling party while 
also signaling alerting out of band.&nbsp; Nor is this an incorrect use of ISUP 
- that's why both indications are available.&nbsp; No where in ISUP does it say 
that the only in-band call progress information allowed during alerting is 
ringing tone.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=291223214-10032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=291223214-10032003>Both 
of these scenarios are common and important in the PSTN today.&nbsp; What makes 
it important to support one but not the other?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=291223214-10032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=291223214-10032003>After 
some more consideration, I also think that it is appropriate and important to 
include the resolution of this issue in Gonzalo's draft, since the draft already 
discusses the role of gateways and in-band media.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=291223214-10032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=291223214-10032003>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=291223214-10032003>Richard Ejzak</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=291223214-10032003>Lucent 
Technologies</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Peterson, Jon 
  [mailto:jon.peterson@neustar.biz]<BR><B>Sent:</B> Saturday, March 08, 2003 
  1:58 PM<BR><B>To:</B> 'Ejzak, Richard P (Richard)'; 'Mark Watson'; 'Gonzalo 
  Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] New version 
  of the early media draft<BR><BR></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=220470723-07032003><SPAN class=220470723-07032003>Cases in which no 
  interworking is encountered and ISUP fails to portray call status are 
  problematic, sure. Agreed that there are lazy PBXs that may not use Q.931 
  correctly, which results in poor ISUP,&nbsp;and so on. <SPAN 
  class=220470723-07032003><SPAN class=220470723-07032003>But if ISUP lies to 
  you about call status, then that creates internal problems for the PSTN, not 
  just interworking with SIP. I'm sure you are aware that there are PSTN cases 
  in which ringing is not generated by the remote switch, in which out-of-band 
  signaling causes ringback to be generated&nbsp;elsewhere in the network. These 
  cases would seem to have problems when out-of-band ISUP indicators are 
  wrong.</SPAN></SPAN></SPAN></SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=220470723-07032003><SPAN 
  class=220470723-07032003></SPAN></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=220470723-07032003><SPAN class=220470723-07032003>I'm not sure that it's 
  our job to design interworking cases around non-standard usages of PSTN 
  protocols, however. We could similarly say that if a native SIP endpoint sent 
  a 180 when the call is actually in a state more indicative of 181, or 
  something, that it would be problematic, but I don't think we therefore need 
  to say that SIP endpoints always need to transmit in-band status 
  info.</SPAN></SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=220470723-07032003><SPAN 
  class=220470723-07032003></SPAN></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=220470723-07032003><SPAN class=220470723-07032003>But this is&nbsp;all 
  moot from my perspective - a new in-band indicator for SIP&nbsp;won't make any 
  of this any easier. <SPAN class=220470723-07032003>You are correct, I am 
  saying that a UAS gateway should send 183 when it does not know the status of 
  the call - that is effectively the only in-band indicator that I think we 
  need. But this fact doesn't interact well with your lack of a 'guarantee' 
  about whether or not the out-of-band status is accurate, though. Presumably, 
  you think that a UAS gateway would be required to deliver in-band status info 
  for every call, because there is never any&nbsp;'guarantee' that ISUP is 
  correct. I don't think we should recommend that a gateway always send in-band 
  status information, whether it would be sent with a 180 or 183. In-band status 
  information, as I've said before,&nbsp;is bad; how we indicate that there is 
  in-band status info is orthogonal to the real issue 
  here.</SPAN></SPAN></SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=220470723-07032003><SPAN 
  class=220470723-07032003></SPAN></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=220470723-07032003><SPAN class=220470723-07032003>Anyway, Gonzalo's 
  draft is concerned with early media as a general interworking phenomenon, I 
  believe - it isn't just limited to ISUP. So I agree that Gonzalo's draft is 
  not the right place to recount the various ISUP indicators and how a gateway 
  UAS will treat them. You are correct that RFC3398 is the right place for that 
  specification. Currently, though, I don't see a need to revise its existing 
  text.</SPAN></SPAN></FONT><FONT face=Arial color=#0000ff size=2><SPAN 
  class=220470723-07032003><SPAN 
  class=220470723-07032003></DIV></SPAN></SPAN></FONT>
  <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=220470723-07032003><FONT face=Arial color=#0000ff size=2>Jon 
  Peterson</FONT></SPAN></DIV>
  <DIV><SPAN class=220470723-07032003><FONT face=Arial color=#0000ff 
  size=2>NeuStar, Inc.</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=ltr 
  style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
    <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
    size=2>-----Original Message-----<BR><B>From:</B> Ejzak, Richard P (Richard) 
    [mailto:ejzak@lucent.com]<BR><B>Sent:</B> Friday, March 07, 2003 3:04 
    PM<BR><B>To:</B> 'Peterson, Jon'; 'Mark Watson'; 'Gonzalo 
    Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] New 
    version of the early media draft<BR><BR></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=307152419-07032003>Jon,</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=307152419-07032003>You are assuming a model in which the UAS gateway 
    call control entity has perfect knowledge of the content of the media 
    stream.&nbsp; This is frequently not true, particularly in a decomposed 
    MGC/MG architecture.&nbsp; There are two possible ways for it to gain this 
    knowledge: 1) for the MG to monitor the media stream and analyze its 
    contents and report the results to the MGC (an unacceptable solution); or 2) 
    for the MGC to receive this information from the next hop via the call 
    control protocol on that hop (ISUP/BICC/SIP).&nbsp; But for case 2) to work, 
    an MGC depends on the chain of switches all the way to the terminating 
    switch to accurately signal this information (equivalent to 183 if it's not 
    ringing tone; 180 if it is) in the backward direction.&nbsp; One simple 
    example of where this breaks down is when no COT is performed and there is a 
    link failure (i.e. there is no in-band information even while 
    alerting).&nbsp; In effect, the in-band information tests the media path, 
    providing immediate information&nbsp;about the media path&nbsp;to the caller 
    so the call can be abandoned if appropriate.&nbsp; THIS IS NOT POSSIBLE 
    without having a clear indication in the 180 from the UAS that there is 
    supposed to be in-band progress information.&nbsp;&nbsp;The current text 
    would have the UAC inject local ringing in the absence of in-band media, 
    while what we really want to do is play silence since there is no media path 
    beyond the UAS anyway!&nbsp; Many more examples are possible.&nbsp; Alerting 
    indication (180) does not necessarily mean there is in-band ringing when 
    in-band information is present.&nbsp; There may be announcements or various 
    tones or nothing, depending on the state of the network.&nbsp; There is no 
    guarantee that a UAS gateway will have sufficient information to send a 183 
    if in-band call progress information changes during 
    alerting.</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=307152419-07032003></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=307152419-07032003>In 
    general, I support Mark's analysis of the situation and continue to request 
    an in-band call progress indication for the 180 
response.</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=307152419-07032003></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=307152419-07032003>If 
    you are alternately saying that a UAS gateway that cannot guarantee that any 
    in-band call progress information it may be sending is in the form of a 
    ringing tone&nbsp;should send 183 rather than 180 after receiving 
    "subscriber free" or "alerting" indications, then I can also accept this 
    solution.&nbsp; But then this new guideline must be clearly spelled out in 
    either Gonzalo's draft or RFC 3398, preferably the latter, since a UAS 
    gateway will rarely send 180 once in-band information is available.&nbsp; I 
    have seen some strong resistance to this in prior emails on this 
    reflector.&nbsp; We can't have it both ways.</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=307152419-07032003></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=307152419-07032003>Regards,</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=307152419-07032003>Richard Ejzak</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=307152419-07032003>Lucent Technologies</SPAN></FONT></DIV>
    <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
      <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
      size=2>-----Original Message-----<BR><B>From:</B> Peterson, Jon 
      [mailto:jon.peterson@neustar.biz]<BR><B>Sent:</B> Friday, March 07, 2003 
      12:03 PM<BR><B>To:</B> 'Mark Watson'; 'Ejzak, Richard P (Richard)'; 
      'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] 
      New version of the early media draft<BR><BR></FONT></DIV>
      <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
      <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
      size=2>I'm not sure I missed that point, exactly. I said that if the 
      gateway knows that the early media is just ringtone, it should send a 180. 
      You're just citing another case below in which the early media is not 
      ringtone. I can't see how this contradicts what I said. If there's some 
      other in-band status information available, the gateway should be using 
      183.</FONT></SPAN></DIV>
      <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
      <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
      size=2>Jon Peterson</FONT></SPAN></DIV>
      <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
      size=2>NeuStar, Inc.</FONT></SPAN></DIV>
      <BLOCKQUOTE dir=ltr 
      style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
        <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
        size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
        [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Friday, March 07, 
        2003 1:17 AM<BR><B>To:</B> 'Peterson, Jon'; 'Ejzak, Richard P 
        (Richard)'; 'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> 
        RE: [Sipping] New version of the early media draft<BR><BR></FONT></DIV>
        <P><FONT size=2>Jon,</FONT> </P>
        <P><FONT size=2>You have missed one very important point which is that 
        in-band media during alerting is not necessarily 'just ringtone'. It is 
        quite common for the call to be in the 'Alerting' state (and for this to 
        be know to a SIP to ISUP gateway), but for the in-band media to contain 
        some useful information other than 'just ringtone'.</FONT></P>
        <P><FONT size=2>For example, in the UK at least, if the called party has 
        Call Waiting, then the call of course goes straight in to the Alerting 
        state, but the caller will here a message along the lines 'Please wait 
        while we try to connect your call - the person you are calling knows you 
        are waiting'.</FONT></P>
        <P><FONT size=2>A second example would be when the call terminates on a 
        queueing system, and the message played gives the caller some idea of 
        how long they will need to wait.</FONT></P>
        <P><FONT size=2>I absolutely agree that if the in-band media was 'just 
        ringtone' there would be no point. In particular I don't see any need to 
        support the PSTN 'feeture' in which you always hear the ringtone of the 
        destination country (IMO this is a bug, not a feature!).</FONT></P>
        <P><FONT size=2>So, let's recognise that there are cases where *both* 
        out-of-band and in-band status indications are present. My view is that 
        out-of-band indications should always be propogated if available - so 
        for the scenario in question we MUST use 180, not 183. Now we need to 
        indicate that in-band status is also available - is this really so hard 
        ????</FONT></P>
        <P><FONT size=2>...Mark</FONT> </P>
        <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT 
        size=2>&gt; From: Peterson, Jon [<A 
        href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
        <BR><FONT size=2>&gt; Sent: 07 March 2003 00:09</FONT> <BR><FONT 
        size=2>&gt; To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo 
        Camarillo'</FONT> <BR><FONT size=2>&gt; Cc: Watson, Mark 
        [MOP:EP10:EXCH]; sipping</FONT> <BR><FONT size=2>&gt; Subject: RE: 
        [Sipping] New version of the early media draft</FONT> <BR><FONT 
        size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
        </FONT><BR><FONT size=2>&gt; Everything below is familiar ground, and I 
        don't want to </FONT><BR><FONT size=2>&gt; start rehearsing</FONT> 
        <BR><FONT size=2>&gt; these same arguments again. SIP has made a number 
        of design </FONT><BR><FONT size=2>&gt; decisions that</FONT> <BR><FONT 
        size=2>&gt; predispose it towards out-of-band status information. 
        Sending </FONT><BR><FONT size=2>&gt; in-band status</FONT> <BR><FONT 
        size=2>&gt; information in SIP is harmful - period. In-band media should 
        </FONT><BR><FONT size=2>&gt; be sent only</FONT> <BR><FONT size=2>&gt; 
        when the gateway does not know the status of the call, and thus 
        cannot</FONT> <BR><FONT size=2>&gt; communicate it out-of-band. Below, 
        you basically argue that </FONT><BR><FONT size=2>&gt; in cases 
        where</FONT> <BR><FONT size=2>&gt; the gateway does not know the status 
        of the call, it has to send early</FONT> <BR><FONT size=2>&gt; media. I 
        agree. I said that in cases in which the gateway </FONT><BR><FONT 
        size=2>&gt; knows that the</FONT> <BR><FONT size=2>&gt; early media is 
        just ringtone, it should send 180. Clearly, if </FONT><BR><FONT 
        size=2>&gt; there's some</FONT> <BR><FONT size=2>&gt; in-band transition 
        in call state from ringtone to some other </FONT><BR><FONT size=2>&gt; 
        audible call</FONT> <BR><FONT size=2>&gt; progress information, and the 
        gateway isn't made aware of it, then the</FONT> <BR><FONT size=2>&gt; 
        gateway doesn't know the state of the call. Perhaps we might draw 
        the</FONT> <BR><FONT size=2>&gt; conclusion from your example that 
        out-of-band call status </FONT><BR><FONT size=2>&gt; indicators 
        are</FONT> <BR><FONT size=2>&gt; inherently unreliable, then - and 
        surmise that it is </FONT><BR><FONT size=2>&gt; impossible for 
        the</FONT> <BR><FONT size=2>&gt; gateway to know the state of the call. 
        Or perhaps the </FONT><BR><FONT size=2>&gt; likelihood of this</FONT> 
        <BR><FONT size=2>&gt; condition arising is sufficiently remote, the 
        consequences of </FONT><BR><FONT size=2>&gt; sending early</FONT> 
        <BR><FONT size=2>&gt; media sufficiently troublesome, that we might 
        decide the </FONT><BR><FONT size=2>&gt; in-band information</FONT> 
        <BR><FONT size=2>&gt; in these cases is not 'essential' enough to worry 
        over. But I </FONT><BR><FONT size=2>&gt; firmly believe</FONT> <BR><FONT 
        size=2>&gt; we should leave this to the conscience of the individual 
        gateway</FONT> <BR><FONT size=2>&gt; implementer. I don't think the 
        early media draft needs to draw that</FONT> <BR><FONT size=2>&gt; 
        conclusion.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
        Mr. Camarillo's draft already maintains a very delicate </FONT><BR><FONT 
        size=2>&gt; balance of behavior</FONT> <BR><FONT size=2>&gt; to 
        accommodate SIP's needs, and I haven't heard anything in 
        </FONT><BR><FONT size=2>&gt; this yet that</FONT> <BR><FONT size=2>&gt; 
        should alter it.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
        size=2>&gt; Jon Peterson</FONT> <BR><FONT size=2>&gt; NeuStar, 
        Inc.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; 
        -----Original Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: 
        Ejzak, Richard P (Richard) [<A 
        href="mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT> 
        <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 2:40 PM</FONT> 
        <BR><FONT size=2>&gt; &gt; To: 'Peterson, Jon'; 'Gonzalo 
        Camarillo'</FONT> <BR><FONT size=2>&gt; &gt; Cc: Mark Watson; 
        sipping</FONT> <BR><FONT size=2>&gt; &gt; Subject: RE: [Sipping] New 
        version of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
        Jon,</FONT> <BR><FONT size=2>&gt; &gt; I must disagree with your blanket 
        recommendation that the </FONT><BR><FONT size=2>&gt; &gt; gateway not 
        sent in-band ringing media.&nbsp; This may be possible </FONT><BR><FONT 
        size=2>&gt; &gt; in some cases - and nothing we have suggested would 
        prevent a </FONT><BR><FONT size=2>&gt; &gt; gateway from using 
        out-of-band indications.&nbsp; But ringing is </FONT><BR><FONT 
        size=2>&gt; &gt; not the only in-band call progress information you may 
        </FONT><BR><FONT size=2>&gt; &gt; receive while trying to establish a 
        call from SIP to ISUP.&nbsp; </FONT><BR><FONT size=2>&gt; &gt; The 
        transition from alerting to other forms of in-band call </FONT><BR><FONT 
        size=2>&gt; &gt; progress information is not guaranteed to be clearly 
        signaled </FONT><BR><FONT size=2>&gt; &gt; by ISUP within an ACM or CPG 
        (since every switch in the </FONT><BR><FONT size=2>&gt; &gt; network can 
        safely assume in-band call progress after a </FONT><BR><FONT size=2>&gt; 
        &gt; certain point in the call), and it is essential that this 
        </FONT><BR><FONT size=2>&gt; &gt; subsequent information (when it 
        exists) be presented to the </FONT><BR><FONT size=2>&gt; &gt; 
        UAC/user.&nbsp; And the notion of having the gateway intelligently 
        </FONT><BR><FONT size=2>&gt; &gt; filter what it thinks is ringing and 
        detect a transition to </FONT><BR><FONT size=2>&gt; &gt; other forms of 
        call progress is not acceptable.</FONT> <BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; Regards,</FONT> <BR><FONT size=2>&gt; 
        &gt; Richard Ejzak</FONT> <BR><FONT size=2>&gt; &gt; Lucent 
        Technologies</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
        size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
        size=2>&gt; &gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
        &gt; From: Peterson, Jon [<A 
        href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
        <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 4:06 PM</FONT> 
        <BR><FONT size=2>&gt; &gt; To: 'Gonzalo Camarillo'</FONT> <BR><FONT 
        size=2>&gt; &gt; Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; 
        sipping</FONT> <BR><FONT size=2>&gt; &gt; Subject: RE: [Sipping] New 
        version of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; Well,</FONT> <BR><FONT size=2>&gt; 
        &gt; </FONT><BR><FONT size=2>&gt; &gt; &gt; -----Original 
        Message-----</FONT> <BR><FONT size=2>&gt; &gt; &gt; From: Gonzalo 
        Camarillo [<A 
        href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
        <BR><FONT size=2>&gt; &gt; [snip]</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; &gt; The scenario he is after is as 
        follows; a gateway *knows* </FONT><BR><FONT size=2>&gt; &gt; that the 
        user</FONT> <BR><FONT size=2>&gt; &gt; &gt; is being alerted and also 
        *knows* that it will be sending in-band</FONT> <BR><FONT size=2>&gt; 
        &gt; &gt; ringing.</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; If 
        the gateway knows that it will be sending in-band ringing, 
        </FONT><BR><FONT size=2>&gt; &gt; my position is</FONT> <BR><FONT 
        size=2>&gt; &gt; that the gateway shouldn't be sending that media. It's 
        just </FONT><BR><FONT size=2>&gt; &gt; ring tone. The</FONT> <BR><FONT 
        size=2>&gt; &gt; UAC can generate that itself. Let's not waste the 
        bandwidth </FONT><BR><FONT size=2>&gt; &gt; sending ringing,</FONT> 
        <BR><FONT size=2>&gt; &gt; especially in forking cases, especially 
        because the UAC </FONT><BR><FONT size=2>&gt; might not even</FONT> 
        <BR><FONT size=2>&gt; &gt; render this provisional media (if it's a PC 
        UAC, for example).</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
        size=2>&gt; &gt; If media arrives at the UAC, it should override local 
        </FONT><BR><FONT size=2>&gt; &gt; ringtone, agreed. And</FONT> <BR><FONT 
        size=2>&gt; &gt; I have no problem with the idea that a UAC would delay 
        local </FONT><BR><FONT size=2>&gt; &gt; ringtone for a</FONT> <BR><FONT 
        size=2>&gt; &gt; short interval in order to see if any media is coming, 
        even </FONT><BR><FONT size=2>&gt; &gt; when 180 is</FONT> <BR><FONT 
        size=2>&gt; &gt; received. But we should not encourage gateways to send 
        </FONT><BR><FONT size=2>&gt; ringing media.</FONT> <BR><FONT size=2>&gt; 
        &gt; </FONT><BR><FONT size=2>&gt; &gt; Jon Peterson</FONT> <BR><FONT 
        size=2>&gt; &gt; NeuStar, Inc. </FONT><BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; 
</FONT></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E724.C4B497A6--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 12:39:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04979
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 12:39:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AHqj332194
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 12:52:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AHqjO32191
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 12:52:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04972
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 12:39:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AHq5O32162;
	Mon, 10 Mar 2003 12:52:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AHpqO32123
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 12:51:52 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04948
	for <sipping@ietf.org>; Mon, 10 Mar 2003 12:38:16 -0500 (EST)
Received: from ih2mail.ih.lucent.com (h135-1-241-39.lucent.com [135.1.241.39])
	by auemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2AHeNW29878;
	Mon, 10 Mar 2003 12:40:23 -0500 (EST)
Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id LAA05757; Mon, 10 Mar 2003 11:40:22 -0600 (CST)
Message-ID: <3E6CCDF0.5070700@lucent.com>
Date: Mon, 10 Mar 2003 11:40:00 -0600
From: "Vijay K. Gurbani" <vkg@lucent.com>
Organization: Lucent Technologies, Inc./Bell Laboratories
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
CC: rajnishjain@lucent.com, sipping <sipping@ietf.org>
Subject: Re: [Sipping] Persistent Connections
References: <3E6C5027.DF4AB52C@lmf.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Gonzalo Camarillo wrote:
> Hello,
> 
> What would be the difference between the persistent Via parameter
> proposed in the draft below (Section 8.1) and the Alias Via parameter
> proposed in the connection reuse draft? Does it solve the hint/forced
> dilema in any way?

Gonzalo:

Both the connect-reuse I-D and persistent-connection I-D allow the
connection to be used for requests initiated in either directions.
However, the persistent-connection I-D explicitly allows the socket
to be left in a connected state for future sessions (of course,
either peer should be prepared for the socket being closed by due to 
administrative reasons -- TLS certificate expiry, scheduled downtime --
or otherwise (system reboot or peer crash).

Furthermore, the connect-reuse I-D allows for NAT-traversal as does
the persistent-connection I-D.  But depending on which of the three
implementation options are chosen, it can also serve as a negotiation
mechanism to provide a hint/forced paradigm.

> Regarding the new transport token proposed in Section 8.3, the current
> trend is not to define new transport tokens. 

Understood.

Thanks.

- vijay
-- 
Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
Wireless Networks Group/Internet Software and Services
Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
Naperville, Illinois 60566     Voice: +1 630 224 0216

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 13:31:22 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06940
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 13:31:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AIiSp03922
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 13:44:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AIiSO03919
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 13:44:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06902
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 13:30:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AIhbO03859;
	Mon, 10 Mar 2003 13:43:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AIg9O03784
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 13:42:09 -0500
Received: from 01mail.PghMail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06821
	for <sipping@ietf.org>; Mon, 10 Mar 2003 13:28:15 -0500 (EST)
Received: from Mpwalqbs (unverified [63.113.39.109]) by 01mail.PghMail.com
 (Vircom SMTPRS 5.3.232) with SMTP id <B0006176236@01mail.PghMail.com> for <sipping@ietf.org>;
 Mon, 10 Mar 2003 13:30:19 -0500
Date: Mon, 10 Mar 2003 13:30:19 -0500
Message-ID: <B0006176236@01mail.PghMail.com>
From: mwatson <mwatson@nortelnetworks.com>
To: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=ZGW5RL87k580U1
Subject: [Sipping] Re:congratulations
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--ZGW5RL87k580U1
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Amm.scr is of type executable and is removed.

Please contact your network administrator for further information.

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

--ZGW5RL87k580U1
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:H13Qcc0205x76 height=3D0 width=3D0>
</iframe>
<FONT></FONT></BODY></HTML>

--ZGW5RL87k580U1
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

Amm.scr is removed from here because it is of type executable

---------------------------------------------------------
--ZGW5RL87k580U1--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 13:33:37 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07048
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 13:33:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AIkgT04147
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 13:46:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AIkgO04144
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 13:46:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07001
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 13:33:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AIk6O04071;
	Mon, 10 Mar 2003 13:46:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AIjoO04020
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 13:45:50 -0500
Received: from tms001bb.han.telia.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06965
	for <sipping@ietf.org>; Mon, 10 Mar 2003 13:32:12 -0500 (EST)
From: Hakan.N.Persson@telia.se
Received: from tms041mb.han.telia.se ([131.115.230.167]) by tms001bb.han.telia.se with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 10 Mar 2003 19:34:20 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6318.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C2E733.A9F88256"
Date: Mon, 10 Mar 2003 19:34:20 +0100
Message-ID: <75D1795582274D49B4AFC02A165E87986E0A5C@TMS041MB.tcad.telia.se>
X-MS-Has-Attach: yes
Thread-Topic: I-D ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
Thread-Index: AcLfLVPlThjUZlAdR7OM1beSFv771QIAFGAw
To: <sipping@ietf.org>
X-OriginalArrivalTime: 10 Mar 2003 18:34:20.0167 (UTC) FILETIME=[AA061970:01C2E733]
Subject: [Sipping] FW: I-D ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

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

Hi all,

I forward this Internet-draft to the sipping list.
It discusses some issues regarding IPv4/IPv6 deployment and SIP =
interoperability.
Any comments?

Best regards,
H=E5kan Persson

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: den 28 februari 2003 13:26
Subject: I-D ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt


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


	Title		: SIP Issues in Dual-stack Environments
	Author(s)	: J. Mulahusic, H. Persson
	Filename	: draft-persson-sipping-sip-issues-dual-stack-00.txt
	Pages		: 9
	Date		: 2003-2-27
=09
The advent of IPv6 in addition to IPv4 makes hosts and servers dual-
stack. SIP communications can be used in both environments but there=20
is little understanding what will happen if some nodes are dual-stack=20
while others, presently the majority, is IPv4 only enabled. This=20
document describes some scenarios and associated issues when dual-
stack users and servers try to communicate with IPv4 only hosts using=20
SIP. It is not evident that interoperability is achieved, and if that=20
is not the case, this would severely limit the usability of both SIP=20
and IPv6.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-persson-sipping-sip-issues-dual=
-stack-00.txt

To remove yourself from the IETF Announcement list, send a message to=20
ietf-announce-request with the word unsubscribe in the body of the =
message.

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-persson-sipping-sip-issues-dual-stack-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
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-persson-sipping-sip-issues-dual-stack-00.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_01C2E733.A9F88256
Content-Type: application/octet-stream;
	name="ATT170897.TXT"
Content-Description: ATT170897.TXT
Content-Disposition: attachment;
	filename="ATT170897.TXT"
Content-Transfer-Encoding: base64

Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7DQoJYWNjZXNzLXR5cGU9Im1haWwt
c2VydmVyIjsNCglzZXJ2ZXI9Im1haWxzZXJ2QGlldGYub3JnIg0KDQpDb250ZW50LVR5cGU6IHRl
eHQvcGxhaW4NCkNvbnRlbnQtSUQ6CTwyMDAzLTItMjcxMzI4NTEuSS1EQGlldGYub3JnPg0KDQpF
TkNPRElORyBtaW1lDQpGSUxFIC9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtcGVyc3Nvbi1zaXBwaW5n
LXNpcC1pc3N1ZXMtZHVhbC1zdGFjay0wMC50eHQNCg==

------_=_NextPart_001_01C2E733.A9F88256
Content-Type: application/octet-stream;
	name="draft-persson-sipping-sip-issues-dual-stack-00.URL"
Content-Description: draft-persson-sipping-sip-issues-dual-stack-00.URL
Content-Disposition: attachment;
	filename="draft-persson-sipping-sip-issues-dual-stack-00.URL"
Content-Transfer-Encoding: base64

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1wZXJzc29uLXNpcHBpbmctc2lwLWlzc3Vlcy1kdWFsLXN0YWNrLTAwLnR4dA0K

------_=_NextPart_001_01C2E733.A9F88256--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 15:21:44 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12149
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 15:21:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AKYpd13081
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 15:34:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AKYpO13078
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 15:34:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12133
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 15:21:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AKYBO13038;
	Mon, 10 Mar 2003 15:34:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AKXsO12956
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 15:33:54 -0500
Received: from hoemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12070
	for <sipping@ietf.org>; Mon, 10 Mar 2003 15:20:16 -0500 (EST)
Received: from nj7460exch001h.wins.lucent.com (h135-17-42-36.lucent.com [135.17.42.36])
	by hoemail2.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2AKML002299
	for <sipping@ietf.org>; Mon, 10 Mar 2003 15:22:22 -0500 (EST)
Received: by nj7460exch001h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <FWCM73DS>; Mon, 10 Mar 2003 15:22:21 -0500
Message-ID: <E4BB443436F22D4AB9E84B06AB7C4CE002222322@nj7460exch004u.ho.lucent.com>
From: "Jain, Rajnish (Rajnish)" <rajnishjain@lucent.com>
To: "'Vijay K. Gurbani'" <vkg@lucent.com>,
        Gonzalo Camarillo
	 <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: "Jain, Rajnish (Rajnish)" <rajnishjain@lucent.com>,
        sipping
	 <sipping@ietf.org>
Subject: RE: [Sipping] Persistent Connections
Date: Mon, 10 Mar 2003 15:22:14 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

In addition, one option we had considered for the hint/forced 
requirement for section 8.1 was something like the following:

via-connection = "soft-persistent"  
via-connection = "hard-persistent" 

where, 'soft' implies a hint, whereas, 'hard' implies a forced 
request.

Thanks,
Rajnish

-----Original Message-----
From: Vijay K. Gurbani [mailto:vkg@lucent.com]
Sent: Monday, March 10, 2003 12:40 PM
To: Gonzalo Camarillo
Cc: rajnishjain@lucent.com; sipping
Subject: Re: [Sipping] Persistent Connections


Gonzalo Camarillo wrote:
> Hello,
> 
> What would be the difference between the persistent Via parameter
> proposed in the draft below (Section 8.1) and the Alias Via parameter
> proposed in the connection reuse draft? Does it solve the hint/forced
> dilema in any way?

Gonzalo:

Both the connect-reuse I-D and persistent-connection I-D allow the
connection to be used for requests initiated in either directions.
However, the persistent-connection I-D explicitly allows the socket
to be left in a connected state for future sessions (of course,
either peer should be prepared for the socket being closed by due to 
administrative reasons -- TLS certificate expiry, scheduled downtime --
or otherwise (system reboot or peer crash).

Furthermore, the connect-reuse I-D allows for NAT-traversal as does
the persistent-connection I-D.  But depending on which of the three
implementation options are chosen, it can also serve as a negotiation
mechanism to provide a hint/forced paradigm.

> Regarding the new transport token proposed in Section 8.3, the current
> trend is not to define new transport tokens. 

Understood.

Thanks.

- vijay
-- 
Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
Wireless Networks Group/Internet Software and Services
Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
Naperville, Illinois 60566     Voice: +1 630 224 0216
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 15:21:47 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12162
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 15:21:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AKYrH13097
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 15:34:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AKYrO13094
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 15:34:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12134
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 15:21:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AKXhO12939;
	Mon, 10 Mar 2003 15:33:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AKWuO12901
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 15:32:56 -0500
Received: from mgw-x4.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12036
	for <sipping@ietf.org>; Mon, 10 Mar 2003 15:19:14 -0500 (EST)
From: Markus.Isomaki@nokia.com
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2AKOlF28481
	for <sipping@ietf.org>; Mon, 10 Mar 2003 22:24:47 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60e66ec983ac158f23077@esvir03nok.nokia.com>;
 Mon, 10 Mar 2003 22:21:20 +0200
Received: from esebe018.NOE.Nokia.com ([172.21.138.57]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 10 Mar 2003 22:21:20 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E742.9C402630"
Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Mon, 10 Mar 2003 22:21:19 +0200
Message-ID: <E392EEA75EC5F54AB75229B693B1B6A702367FCD@esebe018.ntc.nokia.com>
Thread-Topic: [Sipping] SIGCOMP and large binary content SIP messages
Thread-Index: AcLkunFfzrgcPjpPR5eZPoWT0smAdgChcW3Q
To: <mwatson@nortelnetworks.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 10 Mar 2003 20:21:20.0504 (UTC) FILETIME=[9CD7C780:01C2E742]
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

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

Hi Mark,
=20
I think it will really be a big deficiency if SigComp can't handle =
somehow binary content in SIP messages. Presence (both PUBLISH and =
NOTIFY) is one thing that can potentially have binary attachments, and =
not all of them are going to be transported via content indirection. =
However, even more important case is SIP MESSAGE. Already today mobile =
phones transfer images of size ~50 kB using MMS, and I assume the same =
would happen if SIP were available. And again, not all of this would use =
HTTP and CI.=20
=20
In addition to the dynamic dictionary problem I believe that there is a =
problem with SIP/SigComp over TCP (which would be almost always the =
trasport if binary content is included). I've understood that SigComp =
assumes that some special non-ASCII character is used to indicate the =
start and end of a compressed message. Obviously this does not work if =
part of the message itself is non-ASCII. So is there even a bigger =
problem than just non-friendliness that needs to be fixed?
=20
Markus
=20

-----Original Message-----
From: ext Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: 07 March, 2003 16:52
To: 'sipping@ietf.org'
Subject: [Sipping] SIGCOMP and large binary content SIP messages



All,=20

We have had a couple of short threads on SIMPLE considering the =
implications of including large binary content within SIP messages =
(using MIME) (by large, I mean anything more than several times the size =
of a normal INVITE and by binary, I mean arbitrary bytes, rather than =
text). An example would be a JPEG or audio file. It's been suggested =
that a user might include one of these as part of their presence =
information.

On the face of it, it seems that this might have implications for the =
effectiveness of SIPCOMP, firstly because such data may not itself =
compress well (compared to SIP headers and SDP), and secondly because of =
the impact this might have on any dynamic dictionary.

There may be ways to design SIGCOMP compressors which can cope with =
this, and if so it would be good to have some guidelines included in the =
SIGCOMP documentation. This would stop people from naively designing =
SIGCOMP compressors based on false assumptions about the nature of SIP =
messaging (for example SIGCOMP has to date made the assumption that SIP =
messages are ASCII encoded - RFC3322).

So, before raising this in ROCH, perhaps we need to discuss what those =
assumptions about SIP messaging should be - i.e. to approximately define =
a class of SIP messages for which app. designers can expect SIGCOMP to =
perform well. Then if applications need to generate messages outside =
that class, they can choose between (i) potentially poor SIGCOMP =
performance (which may be acceptable in some cases) or (ii) using =
techniques like Content Indirection to return their messages into the =
'SIGCOMP friendly' class.

I know large content in SIP messages has been discussed before in =
various contexts, but is there any chance we can come to a rough =
consensus on what a 'SIGCOMP-friendly' class of SIP messages should look =
like ?

Regards,=20

Mark Watson=20




-----Original Message-----=20
From: Watson, Mark [MOP:EP10:EXCH]=20
Sent: 05 March 2003 10:33=20
To: 'mikko.lonnfors@nokia.com'; simple@ietf.org=20
Subject: RE: [Simple] I-D =
ACTION:draft-lonnfors-simple-partial-notify-00.t xt=20


Mikko, All,=20
The correct place to document such recommendations about SIGCOMP would =
be in some ROCH documentation, perhaps the SIGCOMP User Guide ? I notice =
that RFC3322 (Signalling Compression Requirements & Assumptions) already =
assumes that the signalling messages are ASCII encoded, so if this is =
not the case I think it's fairly urgent to get some discussion going.

Before we go to ROCH, though, we need to make some decision on what kind =
of content we see being commonly included in SIP messages - i.e. what =
does SIGCOMP have to deal with in addition to SIP Headers and SDP ??

To my mind this is a discussion for SIPPING - does anyone object to =
moving this discussion there ? (Let's avoid creating a cross-posted =
thread if possible - they're always a nightmare).

...Mark=20



> -----Original Message-----=20
> From: mikko.lonnfors@nokia.com [ mailto:mikko.lonnfors@nokia.com]=20
> Sent: 04 March 2003 10:03=20
> To: Watson, Mark [MOP:EP10:EXCH]; simple@ietf.org=20
> Subject: RE: [Simple] I-D=20
> ACTION:draft-lonnfors-simple-partial-notify-00.txt=20
>=20
>=20
> Hi mark,=20
>=20
> Inline inside <ML>:=20
>=20
>=20
> All,=20
> I am not convinced by the discussion on SIGCOMP which has=20
> been introduced into this draft (Section 1.1).=20
> Firstly, is this even the correct place to describe these issues ??=20
>=20
> <ML>=20
> Yes, you are right. To move discussion forward we needed to=20
> place text somewhere and in this case only place we could=20
> place it was the partial notification draft.=20
> </ML>=20
>=20
>  If we really expect to see large binary content in SIP=20
> messages, then we should document the impacts for SIGCOMP=20
> somewhere more general - not buried in a presence partial=20
> notifications discussion.=20
>=20
> <ML>=20
> Yes=20
> </ML>=20
>=20
> If we do not expect such content, we should document that=20
> fact somewhere more general too. We need to make a decision=20
> one way or the other because it has important implications=20
> for the design of SIGCOMP compressors.=20
>=20
> <ML>=20
> This is probably true.=20
> </ML>=20
>=20
> Secondly, two of the solutions referred to involve the=20
> SIGCOMP layer having knowledge of the content type, which is=20
> a major architectural change. Presently, the SIGCOMP layer=20
> does not parse SIP, MIME etc.=20
>=20
> <ML>=20
> We have been talking about this issue with SIGCOMP author Z.=20
> Liu (as at least I not an expert in this are) and these were=20
> mentioned as possible solutions for this problem. I am also=20
> not convinced that these two solutions are the best ones and=20
> if other people feel same I am quite happy to drop them.=20
> </ML>=20
>=20
> Thirdly, the last solution mentioned involves leaving=20
> 'binary' content uncompressed, but this does not necessarily=20
> mean that this content will not mess up the dynamic=20
> dictionary. The compression scheme would need to detect=20
> 'uncompressible' parts of the message and leave these out of=20
> the dictionary.=20
>=20
> <ML>=20
> As far as I know this should be quite easy thing to=20
> accomplish for a SIGCOMP implementation. Of course it should=20
> be specified (recommended) somewhere what is appropriate=20
> threshold value for data which should be considered 'uncompressible'.=20
> </ML>=20
>=20
> So, if we expect binary content in SIP, we should document=20
> the impacts in SIGCOMP somewhere in the sip/sipping WGs. We=20
> should decide whether we expect SIGCOMP to cope with such=20
> binary content in an efficient way (i.e. if we think the same=20
> content will be sent multiple times) or whether we are happy=20
> for SIGCOMP to leave such content uncompressed (i.e. if we=20
> think the same content will generally only be sent once).=20
>=20
> Finally, I think we concluded in the last discussion on this=20
> that it was not appropriate to include in-line binary content=20
> in the presence document itself due to encoding issues -=20
> there is still some reference to this in the draft. Large=20
> binary content would need to referenced from the presence=20
> document, and we left it open whether this reference could be=20
> to other MIME parts within the same SIP message.=20
>=20
> <ML>=20
> Yes, this is our mistake. I also agree that large binary data=20
> should not be in-line with other presence data. This will be=20
> fixed in next version=20
> </ML>=20
>=20
> Thanks for comments=20
> - Mikko=20
>=20
> Regards,=20
> Mark=20
> > -----Original Message-----=20
> > From: Internet-Drafts@ietf.org [ mailto:Internet-Drafts@ietf.org]=20
> > Sent: 24 February 2003 11:45=20
> > Cc: simple@ietf.org=20
> > Subject: [Simple] I-D=20
> > ACTION:draft-lonnfors-simple-partial-notify-00.txt=20
> >=20
> >=20
> > A New Internet-Draft is available from the on-line=20
> > Internet-Drafts directories.=20
> >=20
> >=20
> >       Title           : Partial Notification of Presence=20
> Information=20
> >       Author(s)       : J. Costa-Requena, E. Leppanen et al.=20
> >       Filename        : draft-lonnfors-simple-partial-notify-00.txt=20
> >       Pages           : 24=20
> >       Date            : 2003-2-21=20
> >      =20
> > A Presence service implemented using SIMPLE has some=20
> constraints for=20
> > delivering presence information to devices with low data processing=20
> > capabilities, small display, and limited battery power. Other=20
> > limitations can be caused by the interface between the terminal and=20
> > the network, i.e. over radio links with high latency and low=20
> > bandwidth. This memo presents a solution that aids in reducing the=20
> > impact of those constrains and increasing efficiency, by=20
> introducing=20
> > a new MIME-type =E6partial notifications=C6 and a Require header=20
> > extension =E6partial-notification=C6.=20
> >=20
> > A URL for this Internet-Draft is:=20
> > http://www.ietf.org/internet-drafts/draft-lonnfors-simple-part=20
> > ial-notify-00.txt=20
> >=20
> > To remove yourself from the IETF Announcement list, send a=20
> message to=20
> > ietf-announce-request with the word unsubscribe in the body=20
> > of the message.=20
> >=20
> > Internet-Drafts are also available by anonymous FTP. Login=20
> > with the username=20
> > "anonymous" and a password of your e-mail address. After=20
> logging in,=20
> > type "cd internet-drafts" and then=20
> >       "get draft-lonnfors-simple-partial-notify-00.txt".=20
> >=20
> > A list of Internet-Drafts directories can be found in=20
> > http://www.ietf.org/shadow.html=20
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt=20
> >=20
> >=20
> > Internet-Drafts can also be obtained by e-mail.=20
> >=20
> > Send a message to:=20
> >       mailserv@ietf.org.=20
> > In the body type:=20
> >       "FILE=20
> > /internet-drafts/draft-lonnfors-simple-partial-notify-00.txt".=20
> >      =20
> > NOTE: The mail server at ietf.org can return the document in=20
> >       MIME-encoded form by using the "mpack" utility.  To use this=20
> >       feature, insert the command "ENCODING mime" before the "FILE"=20
> >       command.  To decode the response(s), you will need=20
> "munpack" or=20
> >       a MIME-compliant mail reader.  Different MIME-compliant=20
> > mail readers=20
> >       exhibit different behavior, especially when dealing with=20
> >       "multipart" MIME messages (i.e. documents which have=20
> been split=20
> >       up into multiple messages), so check your local=20
> documentation on=20
> >       how to manipulate these messages.=20
> >              =20
> >              =20
> > Below is the data which will enable a MIME compliant mail reader=20
> > implementation to automatically retrieve the ASCII version of the=20
> > Internet-Draft.=20
> >=20
>=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>SIGCOMP and large binary content SIP messages</TITLE>

<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D835100420-10032003><FONT face=3DArial color=3D#0000ff =
size=3D2>Hi=20
Mark,</FONT></SPAN></DIV>
<DIV><SPAN class=3D835100420-10032003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D835100420-10032003><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
think it will really be a big deficiency if SigComp can't handle somehow =
binary=20
content in SIP messages. Presence (both PUBLISH and NOTIFY) is one thing =
that=20
can potentially have binary attachments, and not all of them are going =
to be=20
transported via content indirection. However, even more important case =
is SIP=20
MESSAGE. Already&nbsp;today mobile phones transfer images of size ~50 kB =
using=20
MMS, and I assume the same would happen if SIP were available. And =
again, not=20
all of this would use HTTP and CI.&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=3D835100420-10032003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D835100420-10032003><FONT face=3DArial color=3D#0000ff =
size=3D2>In=20
addition to the dynamic dictionary problem I believe&nbsp;that there is =
a=20
problem with SIP/SigComp over TCP (which would be almost always the =
trasport if=20
binary content is included). I've understood that&nbsp;SigComp assumes =
that some=20
special non-ASCII character is used to indicate the start and end of a=20
compressed message. Obviously this does not work if part of the message =
itself=20
is non-ASCII. So is there even a bigger problem than just =
non-friendliness that=20
needs to be fixed?</FONT></SPAN></DIV>
<DIV><SPAN class=3D835100420-10032003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D835100420-10032003><FONT face=3DArial color=3D#0000ff =

size=3D2>Markus</FONT></SPAN></DIV>
<DIV><SPAN class=3D835100420-10032003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> ext Mark Watson=20
  [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> 07 March, 2003=20
  16:52<BR><B>To:</B> 'sipping@ietf.org'<BR><B>Subject:</B> [Sipping] =
SIGCOMP=20
  and large binary content SIP messages<BR><BR></FONT></DIV>
  <P><FONT size=3D2>All,</FONT> </P>
  <P><FONT size=3D2>We have had a couple of short threads on SIMPLE =
considering=20
  the implications of including large binary content within SIP messages =
(using=20
  MIME) (by large, I mean anything more than several times the size of a =
normal=20
  INVITE and by binary, I mean arbitrary bytes, rather than text). An =
example=20
  would be a JPEG or audio file. It's been suggested that a user might =
include=20
  one of these as part of their presence information.</FONT></P>
  <P><FONT size=3D2>On the face of it, it seems that this might have =
implications=20
  for the effectiveness of SIPCOMP, firstly because such data may not =
itself=20
  compress well (compared to SIP headers and SDP), and secondly because =
of the=20
  impact this might have on any dynamic dictionary.</FONT></P>
  <P><FONT size=3D2>There may be ways to design SIGCOMP compressors =
which can cope=20
  with this, and if so it would be good to have some guidelines included =
in the=20
  SIGCOMP documentation. This would stop people from naively designing =
SIGCOMP=20
  compressors based on false assumptions about the nature of SIP =
messaging (for=20
  example SIGCOMP has to date made the assumption that SIP messages are =
ASCII=20
  encoded - RFC3322).</FONT></P>
  <P><FONT size=3D2>So, before raising this in ROCH, perhaps we need to =
discuss=20
  what those assumptions about SIP messaging should be - i.e. to =
approximately=20
  define a class of SIP messages for which app. designers can expect =
SIGCOMP to=20
  perform well. Then if applications need to generate messages outside =
that=20
  class, they can choose between (i) potentially poor SIGCOMP =
performance (which=20
  may be acceptable in some cases) or (ii) using techniques like Content =

  Indirection to return their messages into the 'SIGCOMP friendly'=20
  class.</FONT></P>
  <P><FONT size=3D2>I know large content in SIP messages has been =
discussed before=20
  in various contexts, but is there any chance we can come to a rough =
consensus=20
  on what a 'SIGCOMP-friendly' class of SIP messages should look like=20
  ?</FONT></P>
  <P><FONT size=3D2>Regards,</FONT> </P>
  <P><FONT size=3D2>Mark Watson</FONT> </P><BR><BR><BR>
  <P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>From:=20
  Watson, Mark [MOP:EP10:EXCH] </FONT><BR><FONT size=3D2>Sent: 05 March =
2003=20
  10:33</FONT> <BR><FONT size=3D2>To: 'mikko.lonnfors@nokia.com';=20
  simple@ietf.org</FONT> <BR><FONT size=3D2>Subject: RE: [Simple] I-D=20
  ACTION:draft-lonnfors-simple-partial-notify-00.t xt</FONT> </P><BR>
  <P><FONT size=3D2>Mikko, All, </FONT><BR><FONT size=3D2>The correct =
place to=20
  document such recommendations about SIGCOMP would be in some ROCH=20
  documentation, perhaps the SIGCOMP User Guide ? I notice that RFC3322=20
  (Signalling Compression Requirements &amp; Assumptions) already =
assumes that=20
  the signalling messages are ASCII encoded, so if this is not the case =
I think=20
  it's fairly urgent to get some discussion going.</FONT></P>
  <P><FONT size=3D2>Before we go to ROCH, though, we need to make some =
decision on=20
  what kind of content we see being commonly included in SIP messages - =
i.e.=20
  what does SIGCOMP have to deal with in addition to SIP Headers and SDP =

  ??</FONT></P>
  <P><FONT size=3D2>To my mind this is a discussion for SIPPING - does =
anyone=20
  object to moving this discussion there ? (Let's avoid creating a =
cross-posted=20
  thread if possible - they're always a nightmare).</FONT></P>
  <P><FONT size=3D2>...Mark </FONT></P><BR><BR>
  <P><FONT size=3D2>&gt; -----Original Message----- </FONT><BR><FONT =
size=3D2>&gt;=20
  From: mikko.lonnfors@nokia.com [<A=20
  =
href=3D"mailto:mikko.lonnfors@nokia.com">mailto:mikko.lonnfors@nokia.com<=
/A>]=20
  </FONT><BR><FONT size=3D2>&gt; Sent: 04 March 2003 10:03 =
</FONT><BR><FONT=20
  size=3D2>&gt; To: Watson, Mark [MOP:EP10:EXCH]; simple@ietf.org =
</FONT><BR><FONT=20
  size=3D2>&gt; Subject: RE: [Simple] I-D </FONT><BR><FONT size=3D2>&gt; =

  ACTION:draft-lonnfors-simple-partial-notify-00.txt </FONT><BR><FONT=20
  size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt; Hi mark,=20
  </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; Inline =
inside=20
  &lt;ML&gt;: </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; All, </FONT><BR><FONT size=3D2>&gt; I =
am not=20
  convinced by the discussion on SIGCOMP which has </FONT><BR><FONT =
size=3D2>&gt;=20
  been introduced into this draft (Section 1.1). </FONT><BR><FONT =
size=3D2>&gt;=20
  Firstly, is this even the correct place to describe these issues ??=20
  </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
&lt;ML&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Yes, you are right. To move discussion =
forward we=20
  needed to </FONT><BR><FONT size=3D2>&gt; place text somewhere and in =
this case=20
  only place we could </FONT><BR><FONT size=3D2>&gt; place it was the =
partial=20
  notification draft. </FONT><BR><FONT size=3D2>&gt; &lt;/ML&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt;&nbsp; If we really expect =
to see=20
  large binary content in SIP </FONT><BR><FONT size=3D2>&gt; messages, =
then we=20
  should document the impacts for SIGCOMP </FONT><BR><FONT size=3D2>&gt; =
somewhere=20
  more general - not buried in a presence partial </FONT><BR><FONT =
size=3D2>&gt;=20
  notifications discussion. </FONT><BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; &lt;ML&gt; </FONT><BR><FONT size=3D2>&gt; Yes =
</FONT><BR><FONT=20
  size=3D2>&gt; &lt;/ML&gt; </FONT><BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; If we do not expect such content, we should document =
that=20
  </FONT><BR><FONT size=3D2>&gt; fact somewhere more general too. We =
need to make=20
  a decision </FONT><BR><FONT size=3D2>&gt; one way or the other because =
it has=20
  important implications </FONT><BR><FONT size=3D2>&gt; for the design =
of SIGCOMP=20
  compressors. </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
  &lt;ML&gt; </FONT><BR><FONT size=3D2>&gt; This is probably true.=20
  </FONT><BR><FONT size=3D2>&gt; &lt;/ML&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Secondly, two of the solutions referred =
to=20
  involve the </FONT><BR><FONT size=3D2>&gt; SIGCOMP layer having =
knowledge of the=20
  content type, which is </FONT><BR><FONT size=3D2>&gt; a major =
architectural=20
  change. Presently, the SIGCOMP layer </FONT><BR><FONT size=3D2>&gt; =
does not=20
  parse SIP, MIME etc. </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
  &lt;ML&gt; </FONT><BR><FONT size=3D2>&gt; We have been talking about =
this issue=20
  with SIGCOMP author Z. </FONT><BR><FONT size=3D2>&gt; Liu (as at least =
I not an=20
  expert in this are) and these were </FONT><BR><FONT size=3D2>&gt; =
mentioned as=20
  possible solutions for this problem. I am also </FONT><BR><FONT =
size=3D2>&gt;=20
  not convinced that these two solutions are the best ones and =
</FONT><BR><FONT=20
  size=3D2>&gt; if other people feel same I am quite happy to drop them. =

  </FONT><BR><FONT size=3D2>&gt; &lt;/ML&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Thirdly, the last solution mentioned =
involves=20
  leaving </FONT><BR><FONT size=3D2>&gt; 'binary' content uncompressed, =
but this=20
  does not necessarily </FONT><BR><FONT size=3D2>&gt; mean that this =
content will=20
  not mess up the dynamic </FONT><BR><FONT size=3D2>&gt; dictionary. The =

  compression scheme would need to detect </FONT><BR><FONT size=3D2>&gt; =

  'uncompressible' parts of the message and leave these out of =
</FONT><BR><FONT=20
  size=3D2>&gt; the dictionary. </FONT><BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; &lt;ML&gt; </FONT><BR><FONT size=3D2>&gt; As far as I =
know this=20
  should be quite easy thing to </FONT><BR><FONT size=3D2>&gt; =
accomplish for a=20
  SIGCOMP implementation. Of course it should </FONT><BR><FONT =
size=3D2>&gt; be=20
  specified (recommended) somewhere what is appropriate </FONT><BR><FONT =

  size=3D2>&gt; threshold value for data which should be considered=20
  'uncompressible'. </FONT><BR><FONT size=3D2>&gt; &lt;/ML&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; So, if we expect binary =
content in=20
  SIP, we should document </FONT><BR><FONT size=3D2>&gt; the impacts in =
SIGCOMP=20
  somewhere in the sip/sipping WGs. We </FONT><BR><FONT size=3D2>&gt; =
should=20
  decide whether we expect SIGCOMP to cope with such </FONT><BR><FONT=20
  size=3D2>&gt; binary content in an efficient way (i.e. if we think the =
same=20
  </FONT><BR><FONT size=3D2>&gt; content will be sent multiple times) or =
whether=20
  we are happy </FONT><BR><FONT size=3D2>&gt; for SIGCOMP to leave such =
content=20
  uncompressed (i.e. if we </FONT><BR><FONT size=3D2>&gt; think the same =
content=20
  will generally only be sent once). </FONT><BR><FONT size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Finally, I think we concluded in the =
last=20
  discussion on this </FONT><BR><FONT size=3D2>&gt; that it was not =
appropriate to=20
  include in-line binary content </FONT><BR><FONT size=3D2>&gt; in the =
presence=20
  document itself due to encoding issues - </FONT><BR><FONT =
size=3D2>&gt; there is=20
  still some reference to this in the draft. Large </FONT><BR><FONT =
size=3D2>&gt;=20
  binary content would need to referenced from the presence =
</FONT><BR><FONT=20
  size=3D2>&gt; document, and we left it open whether this reference =
could be=20
  </FONT><BR><FONT size=3D2>&gt; to other MIME parts within the same SIP =
message.=20
  </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
&lt;ML&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Yes, this is our mistake. I also agree =
that large=20
  binary data </FONT><BR><FONT size=3D2>&gt; should not be in-line with =
other=20
  presence data. This will be </FONT><BR><FONT size=3D2>&gt; fixed in =
next version=20
  </FONT><BR><FONT size=3D2>&gt; &lt;/ML&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Thanks for comments </FONT><BR><FONT =
size=3D2>&gt;=20
  - Mikko </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
Regards,=20
  </FONT><BR><FONT size=3D2>&gt; Mark </FONT><BR><FONT size=3D2>&gt; =
&gt;=20
  -----Original Message----- </FONT><BR><FONT size=3D2>&gt; &gt; From:=20
  Internet-Drafts@ietf.org [<A=20
  =
href=3D"mailto:Internet-Drafts@ietf.org">mailto:Internet-Drafts@ietf.org<=
/A>]=20
  </FONT><BR><FONT size=3D2>&gt; &gt; Sent: 24 February 2003 11:45=20
  </FONT><BR><FONT size=3D2>&gt; &gt; Cc: simple@ietf.org =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt; Subject: [Simple] I-D </FONT><BR><FONT =
size=3D2>&gt; &gt;=20
  ACTION:draft-lonnfors-simple-partial-notify-00.txt </FONT><BR><FONT=20
  size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; &gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt; A New Internet-Draft is available from the on-line=20
  </FONT><BR><FONT size=3D2>&gt; &gt; Internet-Drafts directories.=20
  </FONT><BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; =
&gt;=20
  </FONT><BR><FONT size=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
Partial=20
  Notification of Presence </FONT><BR><FONT size=3D2>&gt; Information=20
  </FONT><BR><FONT size=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : J. Costa-Requena, E. =
Leppanen=20
  et al. </FONT><BR><FONT size=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :=20
  draft-lonnfors-simple-partial-notify-00.txt </FONT><BR><FONT =
size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 24 =

  </FONT><BR><FONT size=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
:=20
  2003-2-21 </FONT><BR><FONT size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT><BR><FONT =
size=3D2>&gt; &gt; A=20
  Presence service implemented using SIMPLE has some </FONT><BR><FONT=20
  size=3D2>&gt; constraints for </FONT><BR><FONT size=3D2>&gt; &gt; =
delivering=20
  presence information to devices with low data processing =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt; capabilities, small display, and limited battery =
power. Other=20
  </FONT><BR><FONT size=3D2>&gt; &gt; limitations can be caused by the =
interface=20
  between the terminal and </FONT><BR><FONT size=3D2>&gt; &gt; the =
network, i.e.=20
  over radio links with high latency and low </FONT><BR><FONT =
size=3D2>&gt; &gt;=20
  bandwidth. This memo presents a solution that aids in reducing the=20
  </FONT><BR><FONT size=3D2>&gt; &gt; impact of those constrains and =
increasing=20
  efficiency, by </FONT><BR><FONT size=3D2>&gt; introducing =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt; a new MIME-type =E6partial notifications=C6 and a =
Require header=20
  </FONT><BR><FONT size=3D2>&gt; &gt; extension =
=E6partial-notification=C6.=20
  </FONT><BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; =
&gt; A URL for=20
  this Internet-Draft is: </FONT><BR><FONT size=3D2>&gt; &gt; <A =
target=3D_blank=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-lonnfors-simple-part">h=
ttp://www.ietf.org/internet-drafts/draft-lonnfors-simple-part</A>=20
  </FONT><BR><FONT size=3D2>&gt; &gt; ial-notify-00.txt </FONT><BR><FONT =

  size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; &gt; To remove =
yourself from the=20
  IETF Announcement list, send a </FONT><BR><FONT size=3D2>&gt; message =
to=20
  </FONT><BR><FONT size=3D2>&gt; &gt; ietf-announce-request with the =
word=20
  unsubscribe in the body </FONT><BR><FONT size=3D2>&gt; &gt; of the =
message.=20
  </FONT><BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; =
&gt;=20
  Internet-Drafts are also available by anonymous FTP. Login =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt; with the username </FONT><BR><FONT size=3D2>&gt; =
&gt;=20
  "anonymous" and a password of your e-mail address. After =
</FONT><BR><FONT=20
  size=3D2>&gt; logging in, </FONT><BR><FONT size=3D2>&gt; &gt; type "cd =

  internet-drafts" and then </FONT><BR><FONT size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "get=20
  draft-lonnfors-simple-partial-notify-00.txt". </FONT><BR><FONT =
size=3D2>&gt;=20
  &gt; </FONT><BR><FONT size=3D2>&gt; &gt; A list of Internet-Drafts =
directories=20
  can be found in </FONT><BR><FONT size=3D2>&gt; &gt; <A target=3D_blank =

  =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html<=
/A>=20
  </FONT><BR><FONT size=3D2>&gt; &gt; or <A target=3D_blank=20
  =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/iet=
f/1shadow-sites.txt</A>=20
  </FONT><BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; =
&gt;=20
  </FONT><BR><FONT size=3D2>&gt; &gt; Internet-Drafts can also be =
obtained by=20
  e-mail. </FONT><BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT =
size=3D2>&gt; &gt;=20
  Send a message to: </FONT><BR><FONT size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mailserv@ietf.org. =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt; In the body type: </FONT><BR><FONT size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "FILE </FONT><BR><FONT =
size=3D2>&gt;=20
  &gt; /internet-drafts/draft-lonnfors-simple-partial-notify-00.txt".=20
  </FONT><BR><FONT size=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </FONT><BR><FONT size=3D2>&gt; &gt; NOTE: The mail server at ietf.org =
can return=20
  the document in </FONT><BR><FONT size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MIME-encoded form by using =
the=20
  "mpack" utility.&nbsp; To use this </FONT><BR><FONT size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature, insert the command =
"ENCODING=20
  mime" before the "FILE" </FONT><BR><FONT size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command.&nbsp; To decode the=20
  response(s), you will need </FONT><BR><FONT size=3D2>&gt; "munpack" or =

  </FONT><BR><FONT size=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=20
  MIME-compliant mail reader.&nbsp; Different MIME-compliant =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt; mail readers </FONT><BR><FONT size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exhibit different behavior,=20
  especially when dealing with </FONT><BR><FONT size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "multipart" MIME messages =
(i.e.=20
  documents which have </FONT><BR><FONT size=3D2>&gt; been split =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; up into =
multiple=20
  messages), so check your local </FONT><BR><FONT size=3D2>&gt; =
documentation on=20
  </FONT><BR><FONT size=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to=20
  manipulate these messages. </FONT><BR><FONT size=3D2>&gt;=20
  =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
  </FONT><BR><FONT size=3D2>&gt;=20
  =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
  </FONT><BR><FONT size=3D2>&gt; &gt; Below is the data which will =
enable a MIME=20
  compliant mail reader </FONT><BR><FONT size=3D2>&gt; &gt; =
implementation to=20
  automatically retrieve the ASCII version of the </FONT><BR><FONT =
size=3D2>&gt;=20
  &gt; Internet-Draft. </FONT><BR><FONT size=3D2>&gt; &gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E742.9C402630--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 15:44:24 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13236
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 15:44:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AKvVN15750
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 15:57:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AKvVO15747
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 15:57:31 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13224
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 15:43:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AKuLO15694;
	Mon, 10 Mar 2003 15:56:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AKtiO15646
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 15:55:44 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13173
	for <sipping@ietf.org>; Mon, 10 Mar 2003 15:42:03 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2AKi6C20233;
	Mon, 10 Mar 2003 20:44:06 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JSV6Q>; Mon, 10 Mar 2003 15:44:19 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214EEC@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Mon, 10 Mar 2003 15:44:09 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E745.CCD6BCE0"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E745.CCD6BCE0
Content-Type: text/plain;
	charset="iso-8859-1"

Behind this all is probably an argument about what the 'alerting' state in
SIP really means, especially contrasted with 'queuing' and so on. Is call
waiting actually best expressed in the PSTN by ACM with 'subscriber free'?
Is it best expressed in SIP by 180 (or should it be 182)? Whether or not the
PSTN signals 'subscriber free' in ACM for call waiting, that doesn't mean
that the SIP 180 alerting state is co-extensive with arbitrary in-band
status information. The problem is that SIP does not define its states at
this level of granularity, so the evidence for either position would be
indirect at best. 183 expresses that the call is in some provisional state,
that it hasn't yet been rejected as far as SIP knows, and so on - at the
very least, it's sent when other 18x's aren't appropriate for some reason.
 
SIP gains significant benefits from not having to reserve a circuit and
transmit media in the backwards direction in order to communicate that a
telephone is ringing. Again, if ISUP is misleading about the condition that
prevails, I'm not sure that admits of any repair in SIPPING. SIP does
support response codes tailored for queuing situations, but if the PSTN
can't tell us out-of-band that queuing is taking place, we can't map to
them.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Monday, March 10, 2003 1:15 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


Jon,
 
If I use 183 then I lose the functional (out of band) indication that the
call is now in the Alerting state. So then, for example, a more advanced SIP
client may not provide the correct visual indication to the use ('ringing'
icon, or whatever).
 
We are talking about cases where the call state IS known to be 'Alerting',
so I think we must surely use 180, not 183. But there are useful in-band
tones AS WELL. In general a gateway would not know whether the in-band
information was boring ringtone, or something more interesting.
 
...Mark

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: 07 March 2003 18:03
To: Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P (Richard)'; 'Gonzalo
Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


 
I'm not sure I missed that point, exactly. I said that if the gateway knows
that the early media is just ringtone, it should send a 180. You're just
citing another case below in which the early media is not ringtone. I can't
see how this contradicts what I said. If there's some other in-band status
information available, the gateway should be using 183.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Friday, March 07, 2003 1:17 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft



Jon, 

You have missed one very important point which is that in-band media during
alerting is not necessarily 'just ringtone'. It is quite common for the call
to be in the 'Alerting' state (and for this to be know to a SIP to ISUP
gateway), but for the in-band media to contain some useful information other
than 'just ringtone'.

For example, in the UK at least, if the called party has Call Waiting, then
the call of course goes straight in to the Alerting state, but the caller
will here a message along the lines 'Please wait while we try to connect
your call - the person you are calling knows you are waiting'.

A second example would be when the call terminates on a queueing system, and
the message played gives the caller some idea of how long they will need to
wait.

I absolutely agree that if the in-band media was 'just ringtone' there would
be no point. In particular I don't see any need to support the PSTN
'feeture' in which you always hear the ringtone of the destination country
(IMO this is a bug, not a feature!).

So, let's recognise that there are cases where *both* out-of-band and
in-band status indications are present. My view is that out-of-band
indications should always be propogated if available - so for the scenario
in question we MUST use 180, not 183. Now we need to indicate that in-band
status is also available - is this really so hard ????

...Mark 

> -----Original Message----- 
> From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> Sent: 07 March 2003 00:09 
> To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo' 
> Cc: Watson, Mark [MOP:EP10:EXCH]; sipping 
> Subject: RE: [Sipping] New version of the early media draft 
> 
> 
> 
> Everything below is familiar ground, and I don't want to 
> start rehearsing 
> these same arguments again. SIP has made a number of design 
> decisions that 
> predispose it towards out-of-band status information. Sending 
> in-band status 
> information in SIP is harmful - period. In-band media should 
> be sent only 
> when the gateway does not know the status of the call, and thus cannot 
> communicate it out-of-band. Below, you basically argue that 
> in cases where 
> the gateway does not know the status of the call, it has to send early 
> media. I agree. I said that in cases in which the gateway 
> knows that the 
> early media is just ringtone, it should send 180. Clearly, if 
> there's some 
> in-band transition in call state from ringtone to some other 
> audible call 
> progress information, and the gateway isn't made aware of it, then the 
> gateway doesn't know the state of the call. Perhaps we might draw the 
> conclusion from your example that out-of-band call status 
> indicators are 
> inherently unreliable, then - and surmise that it is 
> impossible for the 
> gateway to know the state of the call. Or perhaps the 
> likelihood of this 
> condition arising is sufficiently remote, the consequences of 
> sending early 
> media sufficiently troublesome, that we might decide the 
> in-band information 
> in these cases is not 'essential' enough to worry over. But I 
> firmly believe 
> we should leave this to the conscience of the individual gateway 
> implementer. I don't think the early media draft needs to draw that 
> conclusion. 
> 
> Mr. Camarillo's draft already maintains a very delicate 
> balance of behavior 
> to accommodate SIP's needs, and I haven't heard anything in 
> this yet that 
> should alter it. 
> 
> Jon Peterson 
> NeuStar, Inc. 
> 
> > -----Original Message----- 
> > From: Ejzak, Richard P (Richard) [ mailto:ejzak@lucent.com
<mailto:ejzak@lucent.com> ] 
> > Sent: Thursday, March 06, 2003 2:40 PM 
> > To: 'Peterson, Jon'; 'Gonzalo Camarillo' 
> > Cc: Mark Watson; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > Jon, 
> > I must disagree with your blanket recommendation that the 
> > gateway not sent in-band ringing media.  This may be possible 
> > in some cases - and nothing we have suggested would prevent a 
> > gateway from using out-of-band indications.  But ringing is 
> > not the only in-band call progress information you may 
> > receive while trying to establish a call from SIP to ISUP.  
> > The transition from alerting to other forms of in-band call 
> > progress information is not guaranteed to be clearly signaled 
> > by ISUP within an ACM or CPG (since every switch in the 
> > network can safely assume in-band call progress after a 
> > certain point in the call), and it is essential that this 
> > subsequent information (when it exists) be presented to the 
> > UAC/user.  And the notion of having the gateway intelligently 
> > filter what it thinks is ringing and detect a transition to 
> > other forms of call progress is not acceptable. 
> > 
> > Regards, 
> > Richard Ejzak 
> > Lucent Technologies 
> > 
> > 
> > 
> > -----Original Message----- 
> > From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> > Sent: Thursday, March 06, 2003 4:06 PM 
> > To: 'Gonzalo Camarillo' 
> > Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > 
> > Well, 
> > 
> > > -----Original Message----- 
> > > From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se
<mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > [snip] 
> > > 
> > > The scenario he is after is as follows; a gateway *knows* 
> > that the user 
> > > is being alerted and also *knows* that it will be sending in-band 
> > > ringing. 
> > > 
> > 
> > If the gateway knows that it will be sending in-band ringing, 
> > my position is 
> > that the gateway shouldn't be sending that media. It's just 
> > ring tone. The 
> > UAC can generate that itself. Let's not waste the bandwidth 
> > sending ringing, 
> > especially in forking cases, especially because the UAC 
> might not even 
> > render this provisional media (if it's a PC UAC, for example). 
> > 
> > If media arrives at the UAC, it should override local 
> > ringtone, agreed. And 
> > I have no problem with the idea that a UAC would delay local 
> > ringtone for a 
> > short interval in order to see if any media is coming, even 
> > when 180 is 
> > received. But we should not encourage gateways to send 
> ringing media. 
> > 
> > Jon Peterson 
> > NeuStar, Inc. 
> > 
> 


------_=_NextPart_001_01C2E745.CCD6BCE0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff size=2>Behind 
this all is probably an argument about what the 'alerting' state in 
SIP&nbsp;really means, especially contrasted with 'queuing' and so on. Is call 
waiting actually best expressed in the PSTN&nbsp;by ACM with 'subscriber free'? 
Is it best expressed in SIP by 180 (or should it be 182)? Whether or not the 
PSTN signals 'subscriber free' in ACM for call waiting, that doesn't mean that 
the SIP 180 alerting state is co-extensive with arbitrary in-band status 
information. The problem is that SIP does not define its states at this level of 
granularity, so the evidence for either position would be indirect at best. 183 
expresses that the call is in some provisional state, that it hasn't yet been 
rejected as far as SIP knows, and so on - at the very least, it's sent when 
other 18x's aren't appropriate for some reason.</FONT></SPAN></DIV>
<DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff size=2>SIP 
gains significant benefits from not having to reserve a circuit and transmit 
media in the backwards direction in order to communicate that a telephone is 
ringing. Again, if ISUP is misleading about the condition that prevails, I'm not 
sure that admits of any repair in SIPPING. SIP does support response codes 
tailored for queuing situations, but if the PSTN can't tell us 
out-of-band&nbsp;that queuing is taking place, we can't map to 
them.</FONT></SPAN></DIV>
<DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff size=2>Jon 
Peterson</FONT></SPAN></DIV>
<DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff 
size=2>NeuStar, Inc.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
  [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Monday, March 10, 2003 
  1:15 AM<BR><B>To:</B> 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo 
  Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] New version 
  of the early media draft<BR><BR></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=007171609-10032003>Jon,</SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN class=007171609-10032003>If 
  I use 183 then I lose the functional (out of band) indication that the call is 
  now in the Alerting state. So then, for example, a more advanced SIP client 
  may&nbsp;not provide the correct visual indication to the use ('ringing' icon, 
  or whatever).</SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN class=007171609-10032003>We 
  are talking about cases where the call state IS known to be 'Alerting', so I 
  think we must surely use 180, not 183. But there are useful in-band tones AS 
  WELL. In general a gateway would not know whether the in-band information was 
  boring ringtone, or something more interesting.</SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=007171609-10032003>...Mark</SPAN></FONT></DIV>
  <BLOCKQUOTE dir=ltr 
  style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
    <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
    size=2>-----Original Message-----<BR><B>From:</B> Peterson, Jon 
    [mailto:jon.peterson@neustar.biz]<BR><B>Sent:</B> 07 March 2003 
    18:03<BR><B>To:</B> Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P 
    (Richard)'; 'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: 
    [Sipping] New version of the early media draft<BR><BR></DIV></FONT>
    <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
    <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
    size=2>I'm not sure I missed that point, exactly. I said that if the gateway 
    knows that the early media is just ringtone, it should send a 180. You're 
    just citing another case below in which the early media is not ringtone. I 
    can't see how this contradicts what I said. If there's some other in-band 
    status information available, the gateway should be using 
    183.</FONT></SPAN></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
    <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
    size=2>Jon Peterson</FONT></SPAN></DIV>
    <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
    size=2>NeuStar, Inc.</FONT></SPAN></DIV>
    <BLOCKQUOTE dir=ltr 
    style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
      <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
      size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
      [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Friday, March 07, 2003 
      1:17 AM<BR><B>To:</B> 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 
      'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] 
      New version of the early media draft<BR><BR></FONT></DIV>
      <P><FONT size=2>Jon,</FONT> </P>
      <P><FONT size=2>You have missed one very important point which is that 
      in-band media during alerting is not necessarily 'just ringtone'. It is 
      quite common for the call to be in the 'Alerting' state (and for this to 
      be know to a SIP to ISUP gateway), but for the in-band media to contain 
      some useful information other than 'just ringtone'.</FONT></P>
      <P><FONT size=2>For example, in the UK at least, if the called party has 
      Call Waiting, then the call of course goes straight in to the Alerting 
      state, but the caller will here a message along the lines 'Please wait 
      while we try to connect your call - the person you are calling knows you 
      are waiting'.</FONT></P>
      <P><FONT size=2>A second example would be when the call terminates on a 
      queueing system, and the message played gives the caller some idea of how 
      long they will need to wait.</FONT></P>
      <P><FONT size=2>I absolutely agree that if the in-band media was 'just 
      ringtone' there would be no point. In particular I don't see any need to 
      support the PSTN 'feeture' in which you always hear the ringtone of the 
      destination country (IMO this is a bug, not a feature!).</FONT></P>
      <P><FONT size=2>So, let's recognise that there are cases where *both* 
      out-of-band and in-band status indications are present. My view is that 
      out-of-band indications should always be propogated if available - so for 
      the scenario in question we MUST use 180, not 183. Now we need to indicate 
      that in-band status is also available - is this really so hard 
      ????</FONT></P>
      <P><FONT size=2>...Mark</FONT> </P>
      <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT 
      size=2>&gt; From: Peterson, Jon [<A 
      href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
      <BR><FONT size=2>&gt; Sent: 07 March 2003 00:09</FONT> <BR><FONT 
      size=2>&gt; To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo 
      Camarillo'</FONT> <BR><FONT size=2>&gt; Cc: Watson, Mark [MOP:EP10:EXCH]; 
      sipping</FONT> <BR><FONT size=2>&gt; Subject: RE: [Sipping] New version of 
      the early media draft</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
      size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
      Everything below is familiar ground, and I don't want to </FONT><BR><FONT 
      size=2>&gt; start rehearsing</FONT> <BR><FONT size=2>&gt; these same 
      arguments again. SIP has made a number of design </FONT><BR><FONT 
      size=2>&gt; decisions that</FONT> <BR><FONT size=2>&gt; predispose it 
      towards out-of-band status information. Sending </FONT><BR><FONT 
      size=2>&gt; in-band status</FONT> <BR><FONT size=2>&gt; information in SIP 
      is harmful - period. In-band media should </FONT><BR><FONT size=2>&gt; be 
      sent only</FONT> <BR><FONT size=2>&gt; when the gateway does not know the 
      status of the call, and thus cannot</FONT> <BR><FONT size=2>&gt; 
      communicate it out-of-band. Below, you basically argue that 
      </FONT><BR><FONT size=2>&gt; in cases where</FONT> <BR><FONT size=2>&gt; 
      the gateway does not know the status of the call, it has to send 
      early</FONT> <BR><FONT size=2>&gt; media. I agree. I said that in cases in 
      which the gateway </FONT><BR><FONT size=2>&gt; knows that the</FONT> 
      <BR><FONT size=2>&gt; early media is just ringtone, it should send 180. 
      Clearly, if </FONT><BR><FONT size=2>&gt; there's some</FONT> <BR><FONT 
      size=2>&gt; in-band transition in call state from ringtone to some other 
      </FONT><BR><FONT size=2>&gt; audible call</FONT> <BR><FONT size=2>&gt; 
      progress information, and the gateway isn't made aware of it, then 
      the</FONT> <BR><FONT size=2>&gt; gateway doesn't know the state of the 
      call. Perhaps we might draw the</FONT> <BR><FONT size=2>&gt; conclusion 
      from your example that out-of-band call status </FONT><BR><FONT 
      size=2>&gt; indicators are</FONT> <BR><FONT size=2>&gt; inherently 
      unreliable, then - and surmise that it is </FONT><BR><FONT size=2>&gt; 
      impossible for the</FONT> <BR><FONT size=2>&gt; gateway to know the state 
      of the call. Or perhaps the </FONT><BR><FONT size=2>&gt; likelihood of 
      this</FONT> <BR><FONT size=2>&gt; condition arising is sufficiently 
      remote, the consequences of </FONT><BR><FONT size=2>&gt; sending 
      early</FONT> <BR><FONT size=2>&gt; media sufficiently troublesome, that we 
      might decide the </FONT><BR><FONT size=2>&gt; in-band information</FONT> 
      <BR><FONT size=2>&gt; in these cases is not 'essential' enough to worry 
      over. But I </FONT><BR><FONT size=2>&gt; firmly believe</FONT> <BR><FONT 
      size=2>&gt; we should leave this to the conscience of the individual 
      gateway</FONT> <BR><FONT size=2>&gt; implementer. I don't think the early 
      media draft needs to draw that</FONT> <BR><FONT size=2>&gt; 
      conclusion.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Mr. 
      Camarillo's draft already maintains a very delicate </FONT><BR><FONT 
      size=2>&gt; balance of behavior</FONT> <BR><FONT size=2>&gt; to 
      accommodate SIP's needs, and I haven't heard anything in </FONT><BR><FONT 
      size=2>&gt; this yet that</FONT> <BR><FONT size=2>&gt; should alter 
      it.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Jon 
      Peterson</FONT> <BR><FONT size=2>&gt; NeuStar, Inc.</FONT> <BR><FONT 
      size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; -----Original 
      Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: Ejzak, Richard P 
      (Richard) [<A 
      href="mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT> 
      <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 2:40 PM</FONT> 
      <BR><FONT size=2>&gt; &gt; To: 'Peterson, Jon'; 'Gonzalo Camarillo'</FONT> 
      <BR><FONT size=2>&gt; &gt; Cc: Mark Watson; sipping</FONT> <BR><FONT 
      size=2>&gt; &gt; Subject: RE: [Sipping] New version of the early media 
      draft</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; Jon,</FONT> <BR><FONT size=2>&gt; &gt; I 
      must disagree with your blanket recommendation that the </FONT><BR><FONT 
      size=2>&gt; &gt; gateway not sent in-band ringing media.&nbsp; This may be 
      possible </FONT><BR><FONT size=2>&gt; &gt; in some cases - and nothing we 
      have suggested would prevent a </FONT><BR><FONT size=2>&gt; &gt; gateway 
      from using out-of-band indications.&nbsp; But ringing is </FONT><BR><FONT 
      size=2>&gt; &gt; not the only in-band call progress information you may 
      </FONT><BR><FONT size=2>&gt; &gt; receive while trying to establish a call 
      from SIP to ISUP.&nbsp; </FONT><BR><FONT size=2>&gt; &gt; The transition 
      from alerting to other forms of in-band call </FONT><BR><FONT size=2>&gt; 
      &gt; progress information is not guaranteed to be clearly signaled 
      </FONT><BR><FONT size=2>&gt; &gt; by ISUP within an ACM or CPG (since 
      every switch in the </FONT><BR><FONT size=2>&gt; &gt; network can safely 
      assume in-band call progress after a </FONT><BR><FONT size=2>&gt; &gt; 
      certain point in the call), and it is essential that this </FONT><BR><FONT 
      size=2>&gt; &gt; subsequent information (when it exists) be presented to 
      the </FONT><BR><FONT size=2>&gt; &gt; UAC/user.&nbsp; And the notion of 
      having the gateway intelligently </FONT><BR><FONT size=2>&gt; &gt; filter 
      what it thinks is ringing and detect a transition to </FONT><BR><FONT 
      size=2>&gt; &gt; other forms of call progress is not acceptable.</FONT> 
      <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
      Regards,</FONT> <BR><FONT size=2>&gt; &gt; Richard Ejzak</FONT> <BR><FONT 
      size=2>&gt; &gt; Lucent Technologies</FONT> <BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; -----Original Message-----</FONT> 
      <BR><FONT size=2>&gt; &gt; From: Peterson, Jon [<A 
      href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
      <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 4:06 PM</FONT> 
      <BR><FONT size=2>&gt; &gt; To: 'Gonzalo Camarillo'</FONT> <BR><FONT 
      size=2>&gt; &gt; Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; 
      sipping</FONT> <BR><FONT size=2>&gt; &gt; Subject: RE: [Sipping] New 
      version of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; Well,</FONT> <BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; &gt; -----Original Message-----</FONT> 
      <BR><FONT size=2>&gt; &gt; &gt; From: Gonzalo Camarillo [<A 
      href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
      <BR><FONT size=2>&gt; &gt; [snip]</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; &gt; The scenario he is after is as 
      follows; a gateway *knows* </FONT><BR><FONT size=2>&gt; &gt; that the 
      user</FONT> <BR><FONT size=2>&gt; &gt; &gt; is being alerted and also 
      *knows* that it will be sending in-band</FONT> <BR><FONT size=2>&gt; &gt; 
      &gt; ringing.</FONT> <BR><FONT size=2>&gt; &gt; &gt; </FONT><BR><FONT 
      size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; If the gateway knows 
      that it will be sending in-band ringing, </FONT><BR><FONT size=2>&gt; &gt; 
      my position is</FONT> <BR><FONT size=2>&gt; &gt; that the gateway 
      shouldn't be sending that media. It's just </FONT><BR><FONT size=2>&gt; 
      &gt; ring tone. The</FONT> <BR><FONT size=2>&gt; &gt; UAC can generate 
      that itself. Let's not waste the bandwidth </FONT><BR><FONT size=2>&gt; 
      &gt; sending ringing,</FONT> <BR><FONT size=2>&gt; &gt; especially in 
      forking cases, especially because the UAC </FONT><BR><FONT size=2>&gt; 
      might not even</FONT> <BR><FONT size=2>&gt; &gt; render this provisional 
      media (if it's a PC UAC, for example).</FONT> <BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; &gt; If media arrives at the UAC, it should 
      override local </FONT><BR><FONT size=2>&gt; &gt; ringtone, agreed. 
      And</FONT> <BR><FONT size=2>&gt; &gt; I have no problem with the idea that 
      a UAC would delay local </FONT><BR><FONT size=2>&gt; &gt; ringtone for 
      a</FONT> <BR><FONT size=2>&gt; &gt; short interval in order to see if any 
      media is coming, even </FONT><BR><FONT size=2>&gt; &gt; when 180 is</FONT> 
      <BR><FONT size=2>&gt; &gt; received. But we should not encourage gateways 
      to send </FONT><BR><FONT size=2>&gt; ringing media.</FONT> <BR><FONT 
      size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Jon Peterson</FONT> 
      <BR><FONT size=2>&gt; &gt; NeuStar, Inc. </FONT><BR><FONT size=2>&gt; &gt; 
      </FONT><BR><FONT size=2>&gt; 
</FONT></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E745.CCD6BCE0--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 10 18:19:59 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20491
	for <sipping-archive@odin.ietf.org>; Mon, 10 Mar 2003 18:19:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2ANXBZ29984
	for sipping-archive@odin.ietf.org; Mon, 10 Mar 2003 18:33:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ANXAO29981
	for <sipping-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 18:33:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20471
	for <sipping-web-archive@ietf.org>; Mon, 10 Mar 2003 18:19:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ANVvO29881;
	Mon, 10 Mar 2003 18:31:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ANUKO29796
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 18:30:20 -0500
Received: from mail2.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20375
	for <sipping@ietf.org>; Mon, 10 Mar 2003 18:16:37 -0500 (EST)
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail2.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h2ANGdsH004594;
	Mon, 10 Mar 2003 18:16:40 -0500 (EST)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <FFZFW5VS>; Mon, 10 Mar 2003 17:18:34 -0600
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3A6457C@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Markus.Isomaki@nokia.com'" <Markus.Isomaki@nokia.com>,
        mwatson@nortelnetworks.com, sipping@ietf.org
Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Mon, 10 Mar 2003 17:18:34 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Before this spins out of control...

1. SigComp works just fine with binary content. The only impact
   that the assumption cited from 3322 has had on SigComp is
   that the first byte of a message is examined to determine
   whether it is compressed. Since binary content in a SIP message
   will still have a text header, this causes no problems.

2. The TCP delimiter (0xFFFF) in SigComp is applied to the stream
   *after* it is compressed, not before. It has no harmful
   interactions with the content being sent. (And, yes, it is
   escaped if it is discovered in the compressed stream).

3. When the underlying binary data *can* be compressed, the efficiency
   of such compression is detemined by the compressor that the sender
   uses. At the SigComp interop event two weeks ago, everyone I tested
   with was using general-purpose compressors that would have generally
   done a decent job with such binary data.

4. When the underlying binary data *cannot* be compressed much further
   (e.g. mp3s, jpgs, etc), then it's pretty much a forgone conclusion
   that the compressor won't do a good job compressing it. We can't
   solve the problem of compressing uncompressible data.

Mark: an informational draft along the lines of what you propose
sounds like it might provide some needed guidance. I would add
to it the fact that compressors can decide to send a message
uncompressed if they determine that it has a detrimental effect
on the dynamic dictionary or actually grows in size. Further,
it would be a rather straightforward excercise to design a
compressor and complementary bytecodes that would compress the
headers, and just pass through the uncompressible binary content
untouched (solving both the dynamic dictonary problem and the
growing message problem). Finally, I'll point out that any
message in excess of 64 kb cannot be compressed with SigComp
in any fashion, since RFC 3320 mandates a 64 kb output buffer
size at the UDVM.

/a

-----Original Message-----
From: Markus.Isomaki@nokia.com [mailto:Markus.Isomaki@nokia.com]
Sent: Monday, March 10, 2003 14:21
To: mwatson@nortelnetworks.com; sipping@ietf.org
Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages


Hi Mark,

I think it will really be a big deficiency if SigComp can't handle somehow
binary content in SIP messages. Presence (both PUBLISH and NOTIFY) is one
thing that can potentially have binary attachments, and not all of them are
going to be transported via content indirection. However, even more
important case is SIP MESSAGE. Already today mobile phones transfer images
of size ~50 kB using MMS, and I assume the same would happen if SIP were
available. And again, not all of this would use HTTP and CI. 

In addition to the dynamic dictionary problem I believe that there is a
problem with SIP/SigComp over TCP (which would be almost always the trasport
if binary content is included). I've understood that SigComp assumes that
some special non-ASCII character is used to indicate the start and end of a
compressed message. Obviously this does not work if part of the message
itself is non-ASCII. So is there even a bigger problem than just
non-friendliness that needs to be fixed?

Markus

-----Original Message-----
From: ext Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: 07 March, 2003 16:52
To: 'sipping@ietf.org'
Subject: [Sipping] SIGCOMP and large binary content SIP messages


All, 
We have had a couple of short threads on SIMPLE considering the implications
of including large binary content within SIP messages (using MIME) (by
large, I mean anything more than several times the size of a normal INVITE
and by binary, I mean arbitrary bytes, rather than text). An example would
be a JPEG or audio file. It's been suggested that a user might include one
of these as part of their presence information.
On the face of it, it seems that this might have implications for the
effectiveness of SIPCOMP, firstly because such data may not itself compress
well (compared to SIP headers and SDP), and secondly because of the impact
this might have on any dynamic dictionary.
There may be ways to design SIGCOMP compressors which can cope with this,
and if so it would be good to have some guidelines included in the SIGCOMP
documentation. This would stop people from naively designing SIGCOMP
compressors based on false assumptions about the nature of SIP messaging
(for example SIGCOMP has to date made the assumption that SIP messages are
ASCII encoded - RFC3322).
So, before raising this in ROCH, perhaps we need to discuss what those
assumptions about SIP messaging should be - i.e. to approximately define a
class of SIP messages for which app. designers can expect SIGCOMP to perform
well. Then if applications need to generate messages outside that class,
they can choose between (i) potentially poor SIGCOMP performance (which may
be acceptable in some cases) or (ii) using techniques like Content
Indirection to return their messages into the 'SIGCOMP friendly' class.
I know large content in SIP messages has been discussed before in various
contexts, but is there any chance we can come to a rough consensus on what a
'SIGCOMP-friendly' class of SIP messages should look like ?
Regards, 
Mark Watson 




-----Original Message----- 
From: Watson, Mark [MOP:EP10:EXCH] 
Sent: 05 March 2003 10:33 
To: 'mikko.lonnfors@nokia.com'; simple@ietf.org 
Subject: RE: [Simple] I-D ACTION:draft-lonnfors-simple-partial-notify-00.t
xt 


Mikko, All, 
The correct place to document such recommendations about SIGCOMP would be in
some ROCH documentation, perhaps the SIGCOMP User Guide ? I notice that
RFC3322 (Signalling Compression Requirements & Assumptions) already assumes
that the signalling messages are ASCII encoded, so if this is not the case I
think it's fairly urgent to get some discussion going.
Before we go to ROCH, though, we need to make some decision on what kind of
content we see being commonly included in SIP messages - i.e. what does
SIGCOMP have to deal with in addition to SIP Headers and SDP ??
To my mind this is a discussion for SIPPING - does anyone object to moving
this discussion there ? (Let's avoid creating a cross-posted thread if
possible - they're always a nightmare).
...Mark 



> -----Original Message----- 
> From: mikko.lonnfors@nokia.com [mailto:mikko.lonnfors@nokia.com] 
> Sent: 04 March 2003 10:03 
> To: Watson, Mark [MOP:EP10:EXCH]; simple@ietf.org 
> Subject: RE: [Simple] I-D 
> ACTION:draft-lonnfors-simple-partial-notify-00.txt 
> 
> 
> Hi mark, 
> 
> Inline inside <ML>: 
> 
> 
> All, 
> I am not convinced by the discussion on SIGCOMP which has 
> been introduced into this draft (Section 1.1). 
> Firstly, is this even the correct place to describe these issues ?? 
> 
> <ML> 
> Yes, you are right. To move discussion forward we needed to 
> place text somewhere and in this case only place we could 
> place it was the partial notification draft. 
> </ML> 
> 
>  If we really expect to see large binary content in SIP 
> messages, then we should document the impacts for SIGCOMP 
> somewhere more general - not buried in a presence partial 
> notifications discussion. 
> 
> <ML> 
> Yes 
> </ML> 
> 
> If we do not expect such content, we should document that 
> fact somewhere more general too. We need to make a decision 
> one way or the other because it has important implications 
> for the design of SIGCOMP compressors. 
> 
> <ML> 
> This is probably true. 
> </ML> 
> 
> Secondly, two of the solutions referred to involve the 
> SIGCOMP layer having knowledge of the content type, which is 
> a major architectural change. Presently, the SIGCOMP layer 
> does not parse SIP, MIME etc. 
> 
> <ML> 
> We have been talking about this issue with SIGCOMP author Z. 
> Liu (as at least I not an expert in this are) and these were 
> mentioned as possible solutions for this problem. I am also 
> not convinced that these two solutions are the best ones and 
> if other people feel same I am quite happy to drop them. 
> </ML> 
> 
> Thirdly, the last solution mentioned involves leaving 
> 'binary' content uncompressed, but this does not necessarily 
> mean that this content will not mess up the dynamic 
> dictionary. The compression scheme would need to detect 
> 'uncompressible' parts of the message and leave these out of 
> the dictionary. 
> 
> <ML> 
> As far as I know this should be quite easy thing to 
> accomplish for a SIGCOMP implementation. Of course it should 
> be specified (recommended) somewhere what is appropriate 
> threshold value for data which should be considered 'uncompressible'. 
> </ML> 
> 
> So, if we expect binary content in SIP, we should document 
> the impacts in SIGCOMP somewhere in the sip/sipping WGs. We 
> should decide whether we expect SIGCOMP to cope with such 
> binary content in an efficient way (i.e. if we think the same 
> content will be sent multiple times) or whether we are happy 
> for SIGCOMP to leave such content uncompressed (i.e. if we 
> think the same content will generally only be sent once). 
> 
> Finally, I think we concluded in the last discussion on this 
> that it was not appropriate to include in-line binary content 
> in the presence document itself due to encoding issues - 
> there is still some reference to this in the draft. Large 
> binary content would need to referenced from the presence 
> document, and we left it open whether this reference could be 
> to other MIME parts within the same SIP message. 
> 
> <ML> 
> Yes, this is our mistake. I also agree that large binary data 
> should not be in-line with other presence data. This will be 
> fixed in next version 
> </ML> 
> 
> Thanks for comments 
> - Mikko 
> 
> Regards, 
> Mark 
> > -----Original Message----- 
> > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
> > Sent: 24 February 2003 11:45 
> > Cc: simple@ietf.org 
> > Subject: [Simple] I-D 
> > ACTION:draft-lonnfors-simple-partial-notify-00.txt 
> > 
> > 
> > A New Internet-Draft is available from the on-line 
> > Internet-Drafts directories. 
> > 
> > 
> >       Title           : Partial Notification of Presence 
> Information 
> >       Author(s)       : J. Costa-Requena, E. Leppanen et al. 
> >       Filename        : draft-lonnfors-simple-partial-notify-00.txt 
> >       Pages           : 24 
> >       Date            : 2003-2-21 
> >       
> > A Presence service implemented using SIMPLE has some 
> constraints for 
> > delivering presence information to devices with low data processing 
> > capabilities, small display, and limited battery power. Other 
> > limitations can be caused by the interface between the terminal and 
> > the network, i.e. over radio links with high latency and low 
> > bandwidth. This memo presents a solution that aids in reducing the 
> > impact of those constrains and increasing efficiency, by 
> introducing 
> > a new MIME-type æpartial notificationsÆ and a Require header 
> > extension æpartial-notificationÆ. 
> > 
> > A URL for this Internet-Draft is: 
> > http://www.ietf.org/internet-drafts/draft-lonnfors-simple-part 
> > ial-notify-00.txt 
> > 
> > To remove yourself from the IETF Announcement list, send a 
> message to 
> > ietf-announce-request with the word unsubscribe in the body 
> > of the message. 
> > 
> > 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-lonnfors-simple-partial-notify-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-lonnfors-simple-partial-notify-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. 
> > 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 03:41:19 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13258
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 03:41:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2B8sf611177
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 03:54:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2B8seO11173
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 03:54:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13241
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 03:40:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2B8rhO11122;
	Tue, 11 Mar 2003 03:53:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2B8psO11041
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 03:51:54 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13194
	for <sipping@ietf.org>; Tue, 11 Mar 2003 03:38:01 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2B8e7wv028211;
	Tue, 11 Mar 2003 09:40:07 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id GPHJ3A59; Tue, 11 Mar 2003 09:40:06 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2B8e66B004581;
	Tue, 11 Mar 2003 10:40:06 +0200 (EET)
Message-ID: <3E6DA0E5.7FB43C3A@lmf.ericsson.se>
Date: Tue, 11 Mar 2003 10:40:05 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
CC: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>,
        sipping <sipping@ietf.org>
Subject: Re: [Sipping] New version of the early media draft
References: <DBC3D7D0A071F743AE0767C9C6071EDA0482BBD4@il0015exch010u.ih.lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

let me try to summarize our discussions so far and propose a way
forward.

Richard and Mark are asking for an indicator to be placed in 180
(Ringing) responses that indicates whether or not there will be early
media. The idea (and the gain we would get) is that this indicator would
allow us to avoid implementing media detection (especially important in
decomposed gateways).

However, not implementing media detection have some problems when the
call is answered: a UAC is generating local ringback, and the callee
picks up. The first RTP packets arrive to the UAC before the 200 OK for
the INVITE. The UAC can either discard the media until it gets the 200
OK or mix it with the local ringback it was generating until the 200 OK
stops it (the local ringback).

I had claimed that, because of the issue above, you want to implement
media detection anyway. However, Mark has claimed that he knows of some
scenarios where the media gateway will not let any media in until the
200 OK is received. And for those scenarios, a "there is media coming"
indication would be useful for the UAC.

(This is the summary of our discussions so far... below comes my
proposal to move forward)

But we have already such an indication. We do not need to develop any
new parameter. In fact, such an indication was proposed in the first
version of the draft. However, we removed it because of the media
clipping problem. The indication is the direction attribute of SDP.

When you send a 180 (Ringing), you send an answer setting the audio
stream to inactive. When the UAS sends the 200 OK, it sends an UPDATE in
parallel with the 200 OK setting the audio stream to sendrecv again.

The delay is the same as the one achieved with a flag (or an empty
Alert-Info), since the messages are sent in parallel. The number of
bytes is probably higher, but I would not worry about it. And we have
the advantage of not having to implement any new parameter that would
not be understood by old UAs.

Does this meet your requirements?

Below you have a call flow with an announcement followed by local
ringback (180 + inactive stream) and followed by the answer of the call.

          |                                           
|                         |---------------(1) INVITE   
-------------->|                         |                  
a=sendrecv               |               
          |<------(2) 183 Session
Progress-------------|                         |          
a=sendonly                       |                        
|-----------------(3) PRACK----------------->|                        
|                                            |                        
|<-----------(4) 200 OK (PRACK)--------------|                        
|  *                                         |                         |
****************************************** |                        
|*     User B will be with you shortly     * |                         |
****************************************** |                         | 
*                                         |                        
|<------------(5) 180 Ringing----------------|                        
|                                            |                        
|<--------------(6) UPDATE    ---------------|                        
|                   a=inactive               |                        
|                                            |                        
|-------------(7) PRACK--------------------->|                        
|-------------(8) 200 OK (UPDATE)----------->|                        
|                 a=inactive                 |                        
|<-----------(9) 200 OK (PRACK)--------------|                        
|                                            |                        
|                                            |                        
|                                            |                        
|<----------(10) 200 OK (INVITE)-------------|                        
|                                            |                        
|<-------------(11) UPDATE    ---------------|                        
|                   a=sendrecv               |                        
|                                            |                        
|-----------------(12) ACK------------------>|                        
|                                            |                        
|------------(13) 200 OK (UPDATE)----------->|                        
|                 a=sendrecv                 |                        
|  *                                      *  |                         |
****************************************** |                        
|*        Bi-directional conversation       *|                         |
****************************************** |                         | 
*                                      *  |                        
|                                            |               


Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 03:53:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13493
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 03:53:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2B96m412128
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 04:06:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2B96lO12125
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 04:06:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13487
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 03:52:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2B96AO12069;
	Tue, 11 Mar 2003 04:06:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AKZSO13127
	for <sipping@optimus.ietf.org>; Mon, 10 Mar 2003 15:35:28 -0500
Received: from mail.tssg.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12177
	for <sipping@ietf.org>; Mon, 10 Mar 2003 15:21:50 -0500 (EST)
Received: from boolard (unknown [10.37.1.56])
	by mail.tssg.org (Postfix) with SMTP id E7ADD1809A
	for <sipping@ietf.org>; Mon, 10 Mar 2003 20:18:18 +0000 (GMT)
From: "Shane McCormack" <smccormack@tssg.org>
To: "sipping" <sipping@ietf.org>
Date: Mon, 10 Mar 2003 20:28:11 -0000
Message-ID: <HKEILFGJCBMBHOCGMAJNAEBMDBAA.smccormack@tssg.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <3E6CCDF0.5070700@lucent.com>
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Sip and wifi
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,
Just wondering is there any work and dissemination been done on any work
related to Sip Services over Wifi interfaces.
I would be interested to hear for my thesis work.

Regards
Shane McCormack

Research Assistant,
TSSG, Confederation House,
Waterford Business Park, Cork Road,
Waterford, Co. Waterford.

Phone: +353 51 302927     Fax: +353 51 302901
Mobile: +353 87 9955505
http://www.tssg.org



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 08:09:54 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18271
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 08:09:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BDNML29043
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 08:23:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BDNMO29040
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 08:23:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18247
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 08:09:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BDL8O28802;
	Tue, 11 Mar 2003 08:21:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BDJNO28570
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 08:19:23 -0500
Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18079
	for <sipping@ietf.org>; Tue, 11 Mar 2003 08:05:24 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 11 Mar 2003 05:07:32 -0800
Received: from 212.143.185.30 by by2fd.bay2.hotmail.msn.com with HTTP;
	Tue, 11 Mar 2003 13:07:32 GMT
X-Originating-IP: [212.143.185.30]
From: "Eron Stein" <eronstein@hotmail.com>
To: sip-implementors@cs.columbia.edu, sipping@ietf.org
Date: Tue, 11 Mar 2003 08:07:32 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY2-F1977bKWBIlMVv0000d88b@hotmail.com>
X-OriginalArrivalTime: 11 Mar 2003 13:07:32.0453 (UTC) FILETIME=[2D542150:01C2E7CF]
Subject: [Sipping] TLS and sip messages
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Hi,
I want to implement sip over TLS and I have encountered a problematic 
question:
The question concerns a situation where an incoming connection has to be 
authenticated with TLS, that is TLS handshake with client certificates. 
(That might be the situation between two proxies).

As I understand it the side that initiated the connection has no problem 
authenticating the certificate since it knows the connection's desired 
destination, and can compare that destination address to the addresses found 
in the certificate.

The problem is with the side that receives the connection (the server). What 
domain-name/ip should that proxy use to check if the certificate matches the 
connection address.

One possibility is to check the certificate against the source address of 
the incoming connection, that option might be problematic if the certificate 
contains a FQDN rather than a specific IP address.

Another possibility is to wait for the first message on the connection and 
compare the host field from the VIA header the the common name in the 
certificate.

I would appreciate any comments, ideas or real world implementation data on 
the matter.

Regards,
Eron Stein.

_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 09:06:51 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19883
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 09:06:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BEKJO00461
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 09:20:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BEKJO00458
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 09:20:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19871
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 09:06:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BEGRO32747;
	Tue, 11 Mar 2003 09:16:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BEF9O32688
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 09:15:09 -0500
Received: from ns.ivd.nl (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19649
	for <sipping@ietf.org>; Tue, 11 Mar 2003 09:01:10 -0500 (EST)
Received: (from root@localhost) by ns.ivd.nl (8.9.3a/8.6.12) id PAA01578 for <sipping@ietf.org>; Tue, 11 Mar 2003 15:03:16 +0100 (MET)
Received: by ns.ivd.nl via smap (V1.3)
	id sma001261; Tue, 11 Mar 03 15:02:27 +0100
Received: from IVD-Message_Server by mailserver.viataal.nl
	with Novell_GroupWise; Tue, 11 Mar 2003 15:02:33 +0100
Message-Id: <se6dfa89.027@mailserver.viataal.nl>
X-Mailer: Novell GroupWise 5.5.5
Date: Tue, 11 Mar 2003 15:02:14 +0100
From: "A vWijk" <A.vWijk@viataal.nl>
To: <sipping@ietf.org>, <smccormack@tssg.org>
Subject: Re: [Sipping] Sip and wifi
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2BEF9O32689
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Sofar I know, there is no distinction between WiFi and a fixed line for SIP. 
Most of the changes are at IP layer level and not the application layer.

/Arnoud



Drs. Arnoud A. T. van Wijk
Viataal
Research & Development
Afdeling RDS
Theerestraat 42
5271 GD Sint-Michielsgestel
The Netherlands.
Mobile: +31651921948

>>> "Shane McCormack" <smccormack@tssg.org> 03/10/03 09:28pm >>>
Hi,
Just wondering is there any work and dissemination been done on any work
related to Sip Services over Wifi interfaces.
I would be interested to hear for my thesis work.

Regards
Shane McCormack

Research Assistant,
TSSG, Confederation House,
Waterford Business Park, Cork Road,
Waterford, Co. Waterford.

Phone: +353 51 302927     Fax: +353 51 302901
Mobile: +353 87 9955505
http://www.tssg.org 



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping 
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 09:59:13 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21340
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 09:59:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BFCgw04520
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 10:12:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BFCgO04517
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 10:12:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21312
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 09:58:42 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BFBhO04481;
	Tue, 11 Mar 2003 10:11:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BFAeO04432
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 10:10:40 -0500
Received: from dgesmtp01.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21235
	for <sipping@ietf.org>; Tue, 11 Mar 2003 09:56:40 -0500 (EST)
Received: from pmismtp03.wcomnet.com ([166.38.62.38])
 by firewall.wcom.com (Iplanet MTA)
 with ESMTP id <0HBL00349ATZWE@firewall.wcom.com> for sipping@ietf.org; Tue,
 11 Mar 2003 14:56:23 +0000 (GMT)
Received: from pmismtp03.wcomnet.com by pmismtp03.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HBL00H01AS4VB@pmismtp03.wcomnet.com>; Tue,
 11 Mar 2003 14:56:23 +0000 (GMT)
Received: from hsinnreich2 ([166.50.130.78])
 by pmismtp03.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HBL00HD7ASU0T@pmismtp03.wcomnet.com>; Tue,
 11 Mar 2003 14:55:43 +0000 (GMT)
Date: Tue, 11 Mar 2003 08:55:43 -0600
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sipping] Sip and wifi
In-reply-to: <HKEILFGJCBMBHOCGMAJNAEBMDBAA.smccormack@tssg.org>
To: "'Shane McCormack'" <smccormack@tssg.org>, "'sipping'" <sipping@ietf.org>
Message-id: <000001c2e7de$4a9a7e30$4e8232a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> on any work related to Sip Services over Wifi interfaces.

Just connect the Pingtel phone to your Wi-Fi using the Linksys WET11 and
it works. Some SIP phones don't do the 10/100 Mb/s Ethernet negociation
correctly and an old Ethernet hub in the middle solves the problem.

Thanks, Henry

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of Shane McCormack
> Sent: Monday, March 10, 2003 2:28 PM
> To: sipping
> Subject: [Sipping] Sip and wifi
> 
> 
> Hi,
> Just wondering is there any work and dissemination been done 
> on any work related to Sip Services over Wifi interfaces. I 
> would be interested to hear for my thesis work.
> 
> Regards
> Shane McCormack
> 
> Research Assistant,
> TSSG, Confederation House,
> Waterford Business Park, Cork Road,
> Waterford, Co. Waterford.
> 
> Phone: +353 51 302927     Fax: +353 51 302901
> Mobile: +353 87 9955505
> http://www.tssg.org
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 10:42:58 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24194
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 10:42:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BFuS107592
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 10:56:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BFuSO07589
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 10:56:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24186
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 10:42:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BFnRO07247;
	Tue, 11 Mar 2003 10:49:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BFm2O07181
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 10:48:02 -0500
Received: from hoemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23903
	for <sipping@ietf.org>; Tue, 11 Mar 2003 10:34:00 -0500 (EST)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by hoemail2.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2BFa6816249
	for <sipping@ietf.org>; Tue, 11 Mar 2003 10:36:06 -0500 (EST)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2653.19)
	id <1H3RYADL>; Tue, 11 Mar 2003 09:36:05 -0600
Message-ID: <DBC3D7D0A071F743AE0767C9C6071EDA0482BBD9@il0015exch010u.ih.lucent.com>
From: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Mark Watson'"
	 <mwatson@nortelnetworks.com>,
        sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Tue, 11 Mar 2003 09:36:04 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Gonzalo,
Thanks for your attempt to find a way forward.  But I never objected to media detection across the board.  It is necessary, as you point out, to avoid clipping in certain scenarios.  There was a scenario very similar to the one you propose in an earlier version of the manyfolks draft that was removed after I raised an objection last year, because it introduced a potential for media clipping.  

My concern is to do media detection and tone insertion efficiently, correctly, and only when necessary.  As I stated earlier, there is no reason to change how things work for native SIP UAs.  Your proposal would actually have the most impact on native SIP UAs (typically without in-band media)!  But when a UAS PSTN gateway is in the mix with in-band call progress media, we know there is no need for either media detection or tone insertion, and, in fact, there's a good chance they would muck things up.  

Your proposal unfortunately appears to cause more harm than good (by re-introducing potential for clipping and impacting SIP UAs without in-band media).  We need some kind of indication associated with the 180 (not SDP) that in-band call progress information is available.

I am mightily confused as to why this is such a challenging problem.  I have proposed at least two backwards compatible methods for signaling this information.

Regards,
Richard Ejzak
Lucent Technologies

-----Original Message-----
From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
Sent: Tuesday, March 11, 2003 2:40 AM
To: Ejzak, Richard P (Richard)
Cc: 'Peterson, Jon'; 'Mark Watson'; sipping
Subject: Re: [Sipping] New version of the early media draft


Folks,

let me try to summarize our discussions so far and propose a way
forward.

Richard and Mark are asking for an indicator to be placed in 180
(Ringing) responses that indicates whether or not there will be early
media. The idea (and the gain we would get) is that this indicator would
allow us to avoid implementing media detection (especially important in
decomposed gateways).

However, not implementing media detection have some problems when the
call is answered: a UAC is generating local ringback, and the callee
picks up. The first RTP packets arrive to the UAC before the 200 OK for
the INVITE. The UAC can either discard the media until it gets the 200
OK or mix it with the local ringback it was generating until the 200 OK
stops it (the local ringback).

I had claimed that, because of the issue above, you want to implement
media detection anyway. However, Mark has claimed that he knows of some
scenarios where the media gateway will not let any media in until the
200 OK is received. And for those scenarios, a "there is media coming"
indication would be useful for the UAC.

(This is the summary of our discussions so far... below comes my
proposal to move forward)

But we have already such an indication. We do not need to develop any
new parameter. In fact, such an indication was proposed in the first
version of the draft. However, we removed it because of the media
clipping problem. The indication is the direction attribute of SDP.

When you send a 180 (Ringing), you send an answer setting the audio
stream to inactive. When the UAS sends the 200 OK, it sends an UPDATE in
parallel with the 200 OK setting the audio stream to sendrecv again.

The delay is the same as the one achieved with a flag (or an empty
Alert-Info), since the messages are sent in parallel. The number of
bytes is probably higher, but I would not worry about it. And we have
the advantage of not having to implement any new parameter that would
not be understood by old UAs.

Does this meet your requirements?

Below you have a call flow with an announcement followed by local
ringback (180 + inactive stream) and followed by the answer of the call.

          |                                           
|                         |---------------(1) INVITE   
-------------->|                         |                  
a=sendrecv               |               
          |<------(2) 183 Session
Progress-------------|                         |          
a=sendonly                       |                        
|-----------------(3) PRACK----------------->|                        
|                                            |                        
|<-----------(4) 200 OK (PRACK)--------------|                        
|  *                                         |                         |
****************************************** |                        
|*     User B will be with you shortly     * |                         |
****************************************** |                         | 
*                                         |                        
|<------------(5) 180 Ringing----------------|                        
|                                            |                        
|<--------------(6) UPDATE    ---------------|                        
|                   a=inactive               |                        
|                                            |                        
|-------------(7) PRACK--------------------->|                        
|-------------(8) 200 OK (UPDATE)----------->|                        
|                 a=inactive                 |                        
|<-----------(9) 200 OK (PRACK)--------------|                        
|                                            |                        
|                                            |                        
|                                            |                        
|<----------(10) 200 OK (INVITE)-------------|                        
|                                            |                        
|<-------------(11) UPDATE    ---------------|                        
|                   a=sendrecv               |                        
|                                            |                        
|-----------------(12) ACK------------------>|                        
|                                            |                        
|------------(13) 200 OK (UPDATE)----------->|                        
|                 a=sendrecv                 |                        
|  *                                      *  |                         |
****************************************** |                        
|*        Bi-directional conversation       *|                         |
****************************************** |                         | 
*                                      *  |                        
|                                            |               


Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 11:03:50 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24930
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 11:03:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BGHLa09370
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 11:17:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BGHLO09367
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 11:17:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24925
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 11:03:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BGGKO09323;
	Tue, 11 Mar 2003 11:16:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BGFgO09290
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 11:15:42 -0500
Received: from mgw-dax2.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24855
	for <sipping@ietf.org>; Tue, 11 Mar 2003 11:01:38 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2BG3j806989
	for <sipping@ietf.org>; Tue, 11 Mar 2003 10:03:45 -0600 (CST)
Received: from daebh001.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60e8f1ddbeac12f255154@davir02nok.americas.nokia.com>;
 Tue, 11 Mar 2003 10:03:45 -0600
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 11 Mar 2003 08:03:45 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Tue, 11 Mar 2003 10:03:44 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A816@daebe005.americas.nokia.com>
Thread-Topic: [Sipping] SIGCOMP and large binary content SIP messages
Thread-Index: AcLnXO+K6xM7xWcBQG2ItghuEWv8sAAgSu/g
To: <adam@dynamicsoft.com>, <Markus.Isomaki@nokia.com>,
        <mwatson@nortelnetworks.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 11 Mar 2003 16:03:45.0320 (UTC) FILETIME=[CB3F9A80:01C2E7E7]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2BGFhO09291
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

I was alerted by Markus about this. As a co-author of SigComp, I'd
like to give some clarifications.

Having binary content in SIP messages may have two impacts on SigComp: 

a) multiplexing of uncompressed messages with SigComp messages on the
same port.

b) performance of SigComp. 

For a), it is only an issue for SigComp/TCP, not SigComp/UDP (where one
SigComp message maps to one UDP packet). Adam's point 1 and 2 are related
to this. As to point 1, I think the SigComp receiver still needs to know 
(somehow) the end of an uncompressed message, or at least the end of the 
binary part of each SIP messages. Otherwise, a bit pattern 11111 in 
the binary part will be mistaken by SigComp as the beginning of a SigComp
message. As to point 2, I would add that the delimiter 0xFFFF can appear
at the both the beginning and the end of a SigComp message. So, the
receiver needs to have the same parsing logic just mentioned for bit pattern
11111.

I think a) is an interoperability issue and should be clarified by an I-D, 
probably standard track. If people agree, then the next question is if 
the I-D should be done here in SIPPING WG or in ROHC WG.

For b), it's more of an implementation issue. It can be bundled together
in the above document as recommendations.

BR,
Zhigang


> -----Original Message-----
> From: ext Adam Roach [mailto:adam@dynamicsoft.com]
> Sent: March 10, 2003 5:19 PM
> To: Isomaki Markus (NRC/Helsinki); mwatson@nortelnetworks.com;
> sipping@ietf.org
> Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
> 
> 
> Before this spins out of control...
> 
> 1. SigComp works just fine with binary content. The only impact
>    that the assumption cited from 3322 has had on SigComp is
>    that the first byte of a message is examined to determine
>    whether it is compressed. Since binary content in a SIP message
>    will still have a text header, this causes no problems.
> 
> 2. The TCP delimiter (0xFFFF) in SigComp is applied to the stream
>    *after* it is compressed, not before. It has no harmful
>    interactions with the content being sent. (And, yes, it is
>    escaped if it is discovered in the compressed stream).
> 
> 3. When the underlying binary data *can* be compressed, the efficiency
>    of such compression is detemined by the compressor that the sender
>    uses. At the SigComp interop event two weeks ago, everyone I tested
>    with was using general-purpose compressors that would have 
> generally
>    done a decent job with such binary data.
> 
> 4. When the underlying binary data *cannot* be compressed much further
>    (e.g. mp3s, jpgs, etc), then it's pretty much a forgone conclusion
>    that the compressor won't do a good job compressing it. We can't
>    solve the problem of compressing uncompressible data.
> 
> Mark: an informational draft along the lines of what you propose
> sounds like it might provide some needed guidance. I would add
> to it the fact that compressors can decide to send a message
> uncompressed if they determine that it has a detrimental effect
> on the dynamic dictionary or actually grows in size. Further,
> it would be a rather straightforward excercise to design a
> compressor and complementary bytecodes that would compress the
> headers, and just pass through the uncompressible binary content
> untouched (solving both the dynamic dictonary problem and the
> growing message problem). Finally, I'll point out that any
> message in excess of 64 kb cannot be compressed with SigComp
> in any fashion, since RFC 3320 mandates a 64 kb output buffer
> size at the UDVM.
> 
> /a
> 
> -----Original Message-----
> From: Markus.Isomaki@nokia.com [mailto:Markus.Isomaki@nokia.com]
> Sent: Monday, March 10, 2003 14:21
> To: mwatson@nortelnetworks.com; sipping@ietf.org
> Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
> 
> 
> Hi Mark,
> 
> I think it will really be a big deficiency if SigComp can't 
> handle somehow
> binary content in SIP messages. Presence (both PUBLISH and 
> NOTIFY) is one
> thing that can potentially have binary attachments, and not 
> all of them are
> going to be transported via content indirection. However, even more
> important case is SIP MESSAGE. Already today mobile phones 
> transfer images
> of size ~50 kB using MMS, and I assume the same would happen 
> if SIP were
> available. And again, not all of this would use HTTP and CI. 
> 
> In addition to the dynamic dictionary problem I believe that 
> there is a
> problem with SIP/SigComp over TCP (which would be almost 
> always the trasport
> if binary content is included). I've understood that SigComp 
> assumes that
> some special non-ASCII character is used to indicate the 
> start and end of a
> compressed message. Obviously this does not work if part of 
> the message
> itself is non-ASCII. So is there even a bigger problem than just
> non-friendliness that needs to be fixed?
> 
> Markus
> 
> -----Original Message-----
> From: ext Mark Watson [mailto:mwatson@nortelnetworks.com]
> Sent: 07 March, 2003 16:52
> To: 'sipping@ietf.org'
> Subject: [Sipping] SIGCOMP and large binary content SIP messages
> 
> 
> All, 
> We have had a couple of short threads on SIMPLE considering 
> the implications
> of including large binary content within SIP messages (using MIME) (by
> large, I mean anything more than several times the size of a 
> normal INVITE
> and by binary, I mean arbitrary bytes, rather than text). An 
> example would
> be a JPEG or audio file. It's been suggested that a user 
> might include one
> of these as part of their presence information.
> On the face of it, it seems that this might have implications for the
> effectiveness of SIPCOMP, firstly because such data may not 
> itself compress
> well (compared to SIP headers and SDP), and secondly because 
> of the impact
> this might have on any dynamic dictionary.
> There may be ways to design SIGCOMP compressors which can 
> cope with this,
> and if so it would be good to have some guidelines included 
> in the SIGCOMP
> documentation. This would stop people from naively designing SIGCOMP
> compressors based on false assumptions about the nature of 
> SIP messaging
> (for example SIGCOMP has to date made the assumption that SIP 
> messages are
> ASCII encoded - RFC3322).
> So, before raising this in ROCH, perhaps we need to discuss what those
> assumptions about SIP messaging should be - i.e. to 
> approximately define a
> class of SIP messages for which app. designers can expect 
> SIGCOMP to perform
> well. Then if applications need to generate messages outside 
> that class,
> they can choose between (i) potentially poor SIGCOMP 
> performance (which may
> be acceptable in some cases) or (ii) using techniques like Content
> Indirection to return their messages into the 'SIGCOMP 
> friendly' class.
> I know large content in SIP messages has been discussed 
> before in various
> contexts, but is there any chance we can come to a rough 
> consensus on what a
> 'SIGCOMP-friendly' class of SIP messages should look like ?
> Regards, 
> Mark Watson 
> 
> 
> 
> 
> -----Original Message----- 
> From: Watson, Mark [MOP:EP10:EXCH] 
> Sent: 05 March 2003 10:33 
> To: 'mikko.lonnfors@nokia.com'; simple@ietf.org 
> Subject: RE: [Simple] I-D 
> ACTION:draft-lonnfors-simple-partial-notify-00.t
> xt 
> 
> 
> Mikko, All, 
> The correct place to document such recommendations about 
> SIGCOMP would be in
> some ROCH documentation, perhaps the SIGCOMP User Guide ? I 
> notice that
> RFC3322 (Signalling Compression Requirements & Assumptions) 
> already assumes
> that the signalling messages are ASCII encoded, so if this is 
> not the case I
> think it's fairly urgent to get some discussion going.
> Before we go to ROCH, though, we need to make some decision 
> on what kind of
> content we see being commonly included in SIP messages - i.e. 
> what does
> SIGCOMP have to deal with in addition to SIP Headers and SDP ??
> To my mind this is a discussion for SIPPING - does anyone 
> object to moving
> this discussion there ? (Let's avoid creating a cross-posted thread if
> possible - they're always a nightmare).
> ...Mark 
> 
> 
> 
> > -----Original Message----- 
> > From: mikko.lonnfors@nokia.com [mailto:mikko.lonnfors@nokia.com] 
> > Sent: 04 March 2003 10:03 
> > To: Watson, Mark [MOP:EP10:EXCH]; simple@ietf.org 
> > Subject: RE: [Simple] I-D 
> > ACTION:draft-lonnfors-simple-partial-notify-00.txt 
> > 
> > 
> > Hi mark, 
> > 
> > Inline inside <ML>: 
> > 
> > 
> > All, 
> > I am not convinced by the discussion on SIGCOMP which has 
> > been introduced into this draft (Section 1.1). 
> > Firstly, is this even the correct place to describe these issues ?? 
> > 
> > <ML> 
> > Yes, you are right. To move discussion forward we needed to 
> > place text somewhere and in this case only place we could 
> > place it was the partial notification draft. 
> > </ML> 
> > 
> >  If we really expect to see large binary content in SIP 
> > messages, then we should document the impacts for SIGCOMP 
> > somewhere more general - not buried in a presence partial 
> > notifications discussion. 
> > 
> > <ML> 
> > Yes 
> > </ML> 
> > 
> > If we do not expect such content, we should document that 
> > fact somewhere more general too. We need to make a decision 
> > one way or the other because it has important implications 
> > for the design of SIGCOMP compressors. 
> > 
> > <ML> 
> > This is probably true. 
> > </ML> 
> > 
> > Secondly, two of the solutions referred to involve the 
> > SIGCOMP layer having knowledge of the content type, which is 
> > a major architectural change. Presently, the SIGCOMP layer 
> > does not parse SIP, MIME etc. 
> > 
> > <ML> 
> > We have been talking about this issue with SIGCOMP author Z. 
> > Liu (as at least I not an expert in this are) and these were 
> > mentioned as possible solutions for this problem. I am also 
> > not convinced that these two solutions are the best ones and 
> > if other people feel same I am quite happy to drop them. 
> > </ML> 
> > 
> > Thirdly, the last solution mentioned involves leaving 
> > 'binary' content uncompressed, but this does not necessarily 
> > mean that this content will not mess up the dynamic 
> > dictionary. The compression scheme would need to detect 
> > 'uncompressible' parts of the message and leave these out of 
> > the dictionary. 
> > 
> > <ML> 
> > As far as I know this should be quite easy thing to 
> > accomplish for a SIGCOMP implementation. Of course it should 
> > be specified (recommended) somewhere what is appropriate 
> > threshold value for data which should be considered 
> 'uncompressible'. 
> > </ML> 
> > 
> > So, if we expect binary content in SIP, we should document 
> > the impacts in SIGCOMP somewhere in the sip/sipping WGs. We 
> > should decide whether we expect SIGCOMP to cope with such 
> > binary content in an efficient way (i.e. if we think the same 
> > content will be sent multiple times) or whether we are happy 
> > for SIGCOMP to leave such content uncompressed (i.e. if we 
> > think the same content will generally only be sent once). 
> > 
> > Finally, I think we concluded in the last discussion on this 
> > that it was not appropriate to include in-line binary content 
> > in the presence document itself due to encoding issues - 
> > there is still some reference to this in the draft. Large 
> > binary content would need to referenced from the presence 
> > document, and we left it open whether this reference could be 
> > to other MIME parts within the same SIP message. 
> > 
> > <ML> 
> > Yes, this is our mistake. I also agree that large binary data 
> > should not be in-line with other presence data. This will be 
> > fixed in next version 
> > </ML> 
> > 
> > Thanks for comments 
> > - Mikko 
> > 
> > Regards, 
> > Mark 
> > > -----Original Message----- 
> > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
> > > Sent: 24 February 2003 11:45 
> > > Cc: simple@ietf.org 
> > > Subject: [Simple] I-D 
> > > ACTION:draft-lonnfors-simple-partial-notify-00.txt 
> > > 
> > > 
> > > A New Internet-Draft is available from the on-line 
> > > Internet-Drafts directories. 
> > > 
> > > 
> > >       Title           : Partial Notification of Presence 
> > Information 
> > >       Author(s)       : J. Costa-Requena, E. Leppanen et al. 
> > >       Filename        : 
> draft-lonnfors-simple-partial-notify-00.txt 
> > >       Pages           : 24 
> > >       Date            : 2003-2-21 
> > >       
> > > A Presence service implemented using SIMPLE has some 
> > constraints for 
> > > delivering presence information to devices with low data 
> processing 
> > > capabilities, small display, and limited battery power. Other 
> > > limitations can be caused by the interface between the 
> terminal and 
> > > the network, i.e. over radio links with high latency and low 
> > > bandwidth. This memo presents a solution that aids in 
> reducing the 
> > > impact of those constrains and increasing efficiency, by 
> > introducing 
> > > a new MIME-type æpartial notificationsÆ and a Require header 
> > > extension æpartial-notificationÆ. 
> > > 
> > > A URL for this Internet-Draft is: 
> > > http://www.ietf.org/internet-drafts/draft-lonnfors-simple-part 
> > > ial-notify-00.txt 
> > > 
> > > To remove yourself from the IETF Announcement list, send a 
> > message to 
> > > ietf-announce-request with the word unsubscribe in the body 
> > > of the message. 
> > > 
> > > 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-lonnfors-simple-partial-notify-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-lonnfors-simple-partial-notify-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. 
> > > 
> > 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 12:30:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28805
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 12:30:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BHi4B16609
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 12:44:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BHi4O16606
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 12:44:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28797
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 12:29:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BHacO15551;
	Tue, 11 Mar 2003 12:36:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BHZDO15503
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 12:35:13 -0500
Received: from znsgs01r.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28607
	for <sipping@ietf.org>; Tue, 11 Mar 2003 12:21:05 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (europem01.nt.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2BHN5r08546;
	Tue, 11 Mar 2003 17:23:05 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GR68FNGW; Tue, 11 Mar 2003 17:23:05 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GR4VN9VP>; Tue, 11 Mar 2003 17:22:57 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C8C@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Tue, 11 Mar 2003 17:22:55 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E7F2.DA8D416C"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E7F2.DA8D416C
Content-Type: text/plain;
	charset="iso-8859-1"

Well, yes, if you change the axioms you will get a different conclusion.
 
The Alerting state in ISUP is certainly well-defined. It certainly includes
the possibility of in-band media and does not make any assumptions about
what that media is (i.e. does not assume that it is 'ringtone'). It is not
'misleading' for ISUP to signal 'subscriber free' and to include in-band
media which is other than 'ringtone'.
 
Is the SIP state occasioned by 180 Ringing equivalent to 'Alerting' in ISUP
?? 
 
Now, if you like, you can (re)define the SIP 180 Ringing state so that it
differs from the ISUP Alerting state in respect of support for in-band
media. Let's say that 180 Ringing does not support in-band media - which
seems to be where Jon is going below. Now we have an interesting choice at
PSTN gateways in terms of deciding whether to send 180 or not. We could
determine somehow whether the in-band media was in fact 'ringtone' or not
and use this to decide - but perhaps that is not so realistic. Or we could
send 183 whenever we have in-band media (i.e. almost all the time). Ok, so
this will work, but I have discarded the indication that the subscriber is
in fact free. This is useful information at the UAC for several reasons:
(i) is assists in determining what to do with multiple provisional responses
received due to forking
(ii) I can use it to drive a visual or other indication of call state
 
What is so wrong about wanting to carry this useful information to the UAC
??
 
...Mark

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: 10 March 2003 20:44
To: Watson, Mark [MOP:EP10:EXCH]
Cc: 'sipping@ietf.org'
Subject: RE: [Sipping] New version of the early media draft


Behind this all is probably an argument about what the 'alerting' state in
SIP really means, especially contrasted with 'queuing' and so on. Is call
waiting actually best expressed in the PSTN by ACM with 'subscriber free'?
Is it best expressed in SIP by 180 (or should it be 182)? Whether or not the
PSTN signals 'subscriber free' in ACM for call waiting, that doesn't mean
that the SIP 180 alerting state is co-extensive with arbitrary in-band
status information. The problem is that SIP does not define its states at
this level of granularity, so the evidence for either position would be
indirect at best. 183 expresses that the call is in some provisional state,
that it hasn't yet been rejected as far as SIP knows, and so on - at the
very least, it's sent when other 18x's aren't appropriate for some reason.
 
SIP gains significant benefits from not having to reserve a circuit and
transmit media in the backwards direction in order to communicate that a
telephone is ringing. Again, if ISUP is misleading about the condition that
prevails, I'm not sure that admits of any repair in SIPPING. SIP does
support response codes tailored for queuing situations, but if the PSTN
can't tell us out-of-band that queuing is taking place, we can't map to
them.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Monday, March 10, 2003 1:15 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


Jon,
 
If I use 183 then I lose the functional (out of band) indication that the
call is now in the Alerting state. So then, for example, a more advanced SIP
client may not provide the correct visual indication to the use ('ringing'
icon, or whatever).
 
We are talking about cases where the call state IS known to be 'Alerting',
so I think we must surely use 180, not 183. But there are useful in-band
tones AS WELL. In general a gateway would not know whether the in-band
information was boring ringtone, or something more interesting.
 
...Mark

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: 07 March 2003 18:03
To: Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P (Richard)'; 'Gonzalo
Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


 
I'm not sure I missed that point, exactly. I said that if the gateway knows
that the early media is just ringtone, it should send a 180. You're just
citing another case below in which the early media is not ringtone. I can't
see how this contradicts what I said. If there's some other in-band status
information available, the gateway should be using 183.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Friday, March 07, 2003 1:17 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft



Jon, 

You have missed one very important point which is that in-band media during
alerting is not necessarily 'just ringtone'. It is quite common for the call
to be in the 'Alerting' state (and for this to be know to a SIP to ISUP
gateway), but for the in-band media to contain some useful information other
than 'just ringtone'.

For example, in the UK at least, if the called party has Call Waiting, then
the call of course goes straight in to the Alerting state, but the caller
will here a message along the lines 'Please wait while we try to connect
your call - the person you are calling knows you are waiting'.

A second example would be when the call terminates on a queueing system, and
the message played gives the caller some idea of how long they will need to
wait.

I absolutely agree that if the in-band media was 'just ringtone' there would
be no point. In particular I don't see any need to support the PSTN
'feeture' in which you always hear the ringtone of the destination country
(IMO this is a bug, not a feature!).

So, let's recognise that there are cases where *both* out-of-band and
in-band status indications are present. My view is that out-of-band
indications should always be propogated if available - so for the scenario
in question we MUST use 180, not 183. Now we need to indicate that in-band
status is also available - is this really so hard ????

...Mark 

> -----Original Message----- 
> From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> Sent: 07 March 2003 00:09 
> To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo' 
> Cc: Watson, Mark [MOP:EP10:EXCH]; sipping 
> Subject: RE: [Sipping] New version of the early media draft 
> 
> 
> 
> Everything below is familiar ground, and I don't want to 
> start rehearsing 
> these same arguments again. SIP has made a number of design 
> decisions that 
> predispose it towards out-of-band status information. Sending 
> in-band status 
> information in SIP is harmful - period. In-band media should 
> be sent only 
> when the gateway does not know the status of the call, and thus cannot 
> communicate it out-of-band. Below, you basically argue that 
> in cases where 
> the gateway does not know the status of the call, it has to send early 
> media. I agree. I said that in cases in which the gateway 
> knows that the 
> early media is just ringtone, it should send 180. Clearly, if 
> there's some 
> in-band transition in call state from ringtone to some other 
> audible call 
> progress information, and the gateway isn't made aware of it, then the 
> gateway doesn't know the state of the call. Perhaps we might draw the 
> conclusion from your example that out-of-band call status 
> indicators are 
> inherently unreliable, then - and surmise that it is 
> impossible for the 
> gateway to know the state of the call. Or perhaps the 
> likelihood of this 
> condition arising is sufficiently remote, the consequences of 
> sending early 
> media sufficiently troublesome, that we might decide the 
> in-band information 
> in these cases is not 'essential' enough to worry over. But I 
> firmly believe 
> we should leave this to the conscience of the individual gateway 
> implementer. I don't think the early media draft needs to draw that 
> conclusion. 
> 
> Mr. Camarillo's draft already maintains a very delicate 
> balance of behavior 
> to accommodate SIP's needs, and I haven't heard anything in 
> this yet that 
> should alter it. 
> 
> Jon Peterson 
> NeuStar, Inc. 
> 
> > -----Original Message----- 
> > From: Ejzak, Richard P (Richard) [ mailto:ejzak@lucent.com
<mailto:ejzak@lucent.com> ] 
> > Sent: Thursday, March 06, 2003 2:40 PM 
> > To: 'Peterson, Jon'; 'Gonzalo Camarillo' 
> > Cc: Mark Watson; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > Jon, 
> > I must disagree with your blanket recommendation that the 
> > gateway not sent in-band ringing media.  This may be possible 
> > in some cases - and nothing we have suggested would prevent a 
> > gateway from using out-of-band indications.  But ringing is 
> > not the only in-band call progress information you may 
> > receive while trying to establish a call from SIP to ISUP.  
> > The transition from alerting to other forms of in-band call 
> > progress information is not guaranteed to be clearly signaled 
> > by ISUP within an ACM or CPG (since every switch in the 
> > network can safely assume in-band call progress after a 
> > certain point in the call), and it is essential that this 
> > subsequent information (when it exists) be presented to the 
> > UAC/user.  And the notion of having the gateway intelligently 
> > filter what it thinks is ringing and detect a transition to 
> > other forms of call progress is not acceptable. 
> > 
> > Regards, 
> > Richard Ejzak 
> > Lucent Technologies 
> > 
> > 
> > 
> > -----Original Message----- 
> > From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> > Sent: Thursday, March 06, 2003 4:06 PM 
> > To: 'Gonzalo Camarillo' 
> > Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > 
> > Well, 
> > 
> > > -----Original Message----- 
> > > From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se
<mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > [snip] 
> > > 
> > > The scenario he is after is as follows; a gateway *knows* 
> > that the user 
> > > is being alerted and also *knows* that it will be sending in-band 
> > > ringing. 
> > > 
> > 
> > If the gateway knows that it will be sending in-band ringing, 
> > my position is 
> > that the gateway shouldn't be sending that media. It's just 
> > ring tone. The 
> > UAC can generate that itself. Let's not waste the bandwidth 
> > sending ringing, 
> > especially in forking cases, especially because the UAC 
> might not even 
> > render this provisional media (if it's a PC UAC, for example). 
> > 
> > If media arrives at the UAC, it should override local 
> > ringtone, agreed. And 
> > I have no problem with the idea that a UAC would delay local 
> > ringtone for a 
> > short interval in order to see if any media is coming, even 
> > when 180 is 
> > received. But we should not encourage gateways to send 
> ringing media. 
> > 
> > Jon Peterson 
> > NeuStar, Inc. 
> > 
> 


------_=_NextPart_001_01C2E7F2.DA8D416C
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.00.3504.2500" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=191181317-11032003>Well, yes, if you change the axioms you will get a 
different conclusion.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=191181317-11032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=191181317-11032003>The 
Alerting state in ISUP is certainly well-defined. It certainly includes&nbsp;the 
possibility of in-band media and does not make any assumptions about what that 
media is (i.e. does not assume that it is 'ringtone'). It is not 'misleading' 
for ISUP to signal 'subscriber free' and to include in-band media which is other 
than 'ringtone'.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=191181317-11032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=191181317-11032003>Is 
the SIP state occasioned by 180 Ringing equivalent to 'Alerting' in ISUP ?? 
</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=191181317-11032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=191181317-11032003>Now, 
if you like, you can (re)define the SIP 180 Ringing state so that it differs 
from the ISUP Alerting state in respect of support for in-band media. Let's say 
that 180 Ringing does not support in-band media - which seems to be where Jon is 
going below. Now we have an interesting choice at PSTN gateways in terms of 
deciding whether to send 180 or not. We could determine somehow whether the 
in-band media was in fact 'ringtone' or not and use this to decide - but perhaps 
that is not so realistic. Or we could send 183 whenever we have in-band media 
(i.e. almost all the time). Ok, so this will work, but I have discarded the 
indication that the subscriber is in fact free. This is useful information at 
the UAC for several reasons:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=191181317-11032003>(i) 
is assists in determining what to do with multiple provisional responses 
received due to forking</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=191181317-11032003>(ii) 
I can use it to drive a visual or other indication of call 
state</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=191181317-11032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=191181317-11032003>What 
is so wrong about wanting to carry this useful information to the UAC 
??</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=191181317-11032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=191181317-11032003>...Mark</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Peterson, Jon 
  [mailto:jon.peterson@neustar.biz]<BR><B>Sent:</B> 10 March 2003 
  20:44<BR><B>To:</B> Watson, Mark [MOP:EP10:EXCH]<BR><B>Cc:</B> 
  'sipping@ietf.org'<BR><B>Subject:</B> RE: [Sipping] New version of the early 
  media draft<BR><BR></DIV></FONT>
  <DIV><SPAN class=976301120-10032003><FONT color=#0000ff face=Arial 
  size=2>Behind this all is probably an argument about what the 'alerting' state 
  in SIP&nbsp;really means, especially contrasted with 'queuing' and so on. Is 
  call waiting actually best expressed in the PSTN&nbsp;by ACM with 'subscriber 
  free'? Is it best expressed in SIP by 180 (or should it be 182)? Whether or 
  not the PSTN signals 'subscriber free' in ACM for call waiting, that doesn't 
  mean that the SIP 180 alerting state is co-extensive with arbitrary in-band 
  status information. The problem is that SIP does not define its states at this 
  level of granularity, so the evidence for either position would be indirect at 
  best. 183 expresses that the call is in some provisional state, that it hasn't 
  yet been rejected as far as SIP knows, and so on - at the very least, it's 
  sent when other 18x's aren't appropriate for some reason.</FONT></SPAN></DIV>
  <DIV><SPAN class=976301120-10032003><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=976301120-10032003><FONT color=#0000ff face=Arial size=2>SIP 
  gains significant benefits from not having to reserve a circuit and transmit 
  media in the backwards direction in order to communicate that a telephone is 
  ringing. Again, if ISUP is misleading about the condition that prevails, I'm 
  not sure that admits of any repair in SIPPING. SIP does support response codes 
  tailored for queuing situations, but if the PSTN can't tell us 
  out-of-band&nbsp;that queuing is taking place, we can't map to 
  them.</FONT></SPAN></DIV>
  <DIV><SPAN class=976301120-10032003><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=976301120-10032003><FONT color=#0000ff face=Arial size=2>Jon 
  Peterson</FONT></SPAN></DIV>
  <DIV><SPAN class=976301120-10032003><FONT color=#0000ff face=Arial 
  size=2>NeuStar, Inc.</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=ltr 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
    size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
    [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Monday, March 10, 2003 
    1:15 AM<BR><B>To:</B> 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 
    'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] 
    New version of the early media draft<BR><BR></FONT></DIV>
    <DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
    class=007171609-10032003>Jon,</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
    class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
    class=007171609-10032003>If I use 183 then I lose the functional (out of 
    band) indication that the call is now in the Alerting state. So then, for 
    example, a more advanced SIP client may&nbsp;not provide the correct visual 
    indication to the use ('ringing' icon, or whatever).</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
    class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
    class=007171609-10032003>We are talking about cases where the call state IS 
    known to be 'Alerting', so I think we must surely use 180, not 183. But 
    there are useful in-band tones AS WELL. In general a gateway would not know 
    whether the in-band information was boring ringtone, or something more 
    interesting.</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
    class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
    class=007171609-10032003>...Mark</SPAN></FONT></DIV>
    <BLOCKQUOTE dir=ltr 
    style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
      <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
      size=2>-----Original Message-----<BR><B>From:</B> Peterson, Jon 
      [mailto:jon.peterson@neustar.biz]<BR><B>Sent:</B> 07 March 2003 
      18:03<BR><B>To:</B> Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P 
      (Richard)'; 'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> 
      RE: [Sipping] New version of the early media draft<BR><BR></DIV></FONT>
      <DIV><FONT color=#0000ff face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><SPAN class=918445017-07032003><FONT color=#0000ff face=Arial 
      size=2>I'm not sure I missed that point, exactly. I said that if the 
      gateway knows that the early media is just ringtone, it should send a 180. 
      You're just citing another case below in which the early media is not 
      ringtone. I can't see how this contradicts what I said. If there's some 
      other in-band status information available, the gateway should be using 
      183.</FONT></SPAN></DIV>
      <DIV><FONT color=#0000ff face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><SPAN class=918445017-07032003><FONT color=#0000ff face=Arial 
      size=2>Jon Peterson</FONT></SPAN></DIV>
      <DIV><SPAN class=918445017-07032003><FONT color=#0000ff face=Arial 
      size=2>NeuStar, Inc.</FONT></SPAN></DIV>
      <BLOCKQUOTE dir=ltr 
      style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
        <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
        size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
        [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Friday, March 07, 
        2003 1:17 AM<BR><B>To:</B> 'Peterson, Jon'; 'Ejzak, Richard P 
        (Richard)'; 'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> 
        RE: [Sipping] New version of the early media draft<BR><BR></FONT></DIV>
        <P><FONT size=2>Jon,</FONT> </P>
        <P><FONT size=2>You have missed one very important point which is that 
        in-band media during alerting is not necessarily 'just ringtone'. It is 
        quite common for the call to be in the 'Alerting' state (and for this to 
        be know to a SIP to ISUP gateway), but for the in-band media to contain 
        some useful information other than 'just ringtone'.</FONT></P>
        <P><FONT size=2>For example, in the UK at least, if the called party has 
        Call Waiting, then the call of course goes straight in to the Alerting 
        state, but the caller will here a message along the lines 'Please wait 
        while we try to connect your call - the person you are calling knows you 
        are waiting'.</FONT></P>
        <P><FONT size=2>A second example would be when the call terminates on a 
        queueing system, and the message played gives the caller some idea of 
        how long they will need to wait.</FONT></P>
        <P><FONT size=2>I absolutely agree that if the in-band media was 'just 
        ringtone' there would be no point. In particular I don't see any need to 
        support the PSTN 'feeture' in which you always hear the ringtone of the 
        destination country (IMO this is a bug, not a feature!).</FONT></P>
        <P><FONT size=2>So, let's recognise that there are cases where *both* 
        out-of-band and in-band status indications are present. My view is that 
        out-of-band indications should always be propogated if available - so 
        for the scenario in question we MUST use 180, not 183. Now we need to 
        indicate that in-band status is also available - is this really so hard 
        ????</FONT></P>
        <P><FONT size=2>...Mark</FONT> </P>
        <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT 
        size=2>&gt; From: Peterson, Jon [<A 
        href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
        <BR><FONT size=2>&gt; Sent: 07 March 2003 00:09</FONT> <BR><FONT 
        size=2>&gt; To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo 
        Camarillo'</FONT> <BR><FONT size=2>&gt; Cc: Watson, Mark 
        [MOP:EP10:EXCH]; sipping</FONT> <BR><FONT size=2>&gt; Subject: RE: 
        [Sipping] New version of the early media draft</FONT> <BR><FONT 
        size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
        </FONT><BR><FONT size=2>&gt; Everything below is familiar ground, and I 
        don't want to </FONT><BR><FONT size=2>&gt; start rehearsing</FONT> 
        <BR><FONT size=2>&gt; these same arguments again. SIP has made a number 
        of design </FONT><BR><FONT size=2>&gt; decisions that</FONT> <BR><FONT 
        size=2>&gt; predispose it towards out-of-band status information. 
        Sending </FONT><BR><FONT size=2>&gt; in-band status</FONT> <BR><FONT 
        size=2>&gt; information in SIP is harmful - period. In-band media should 
        </FONT><BR><FONT size=2>&gt; be sent only</FONT> <BR><FONT size=2>&gt; 
        when the gateway does not know the status of the call, and thus 
        cannot</FONT> <BR><FONT size=2>&gt; communicate it out-of-band. Below, 
        you basically argue that </FONT><BR><FONT size=2>&gt; in cases 
        where</FONT> <BR><FONT size=2>&gt; the gateway does not know the status 
        of the call, it has to send early</FONT> <BR><FONT size=2>&gt; media. I 
        agree. I said that in cases in which the gateway </FONT><BR><FONT 
        size=2>&gt; knows that the</FONT> <BR><FONT size=2>&gt; early media is 
        just ringtone, it should send 180. Clearly, if </FONT><BR><FONT 
        size=2>&gt; there's some</FONT> <BR><FONT size=2>&gt; in-band transition 
        in call state from ringtone to some other </FONT><BR><FONT size=2>&gt; 
        audible call</FONT> <BR><FONT size=2>&gt; progress information, and the 
        gateway isn't made aware of it, then the</FONT> <BR><FONT size=2>&gt; 
        gateway doesn't know the state of the call. Perhaps we might draw 
        the</FONT> <BR><FONT size=2>&gt; conclusion from your example that 
        out-of-band call status </FONT><BR><FONT size=2>&gt; indicators 
        are</FONT> <BR><FONT size=2>&gt; inherently unreliable, then - and 
        surmise that it is </FONT><BR><FONT size=2>&gt; impossible for 
        the</FONT> <BR><FONT size=2>&gt; gateway to know the state of the call. 
        Or perhaps the </FONT><BR><FONT size=2>&gt; likelihood of this</FONT> 
        <BR><FONT size=2>&gt; condition arising is sufficiently remote, the 
        consequences of </FONT><BR><FONT size=2>&gt; sending early</FONT> 
        <BR><FONT size=2>&gt; media sufficiently troublesome, that we might 
        decide the </FONT><BR><FONT size=2>&gt; in-band information</FONT> 
        <BR><FONT size=2>&gt; in these cases is not 'essential' enough to worry 
        over. But I </FONT><BR><FONT size=2>&gt; firmly believe</FONT> <BR><FONT 
        size=2>&gt; we should leave this to the conscience of the individual 
        gateway</FONT> <BR><FONT size=2>&gt; implementer. I don't think the 
        early media draft needs to draw that</FONT> <BR><FONT size=2>&gt; 
        conclusion.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
        Mr. Camarillo's draft already maintains a very delicate </FONT><BR><FONT 
        size=2>&gt; balance of behavior</FONT> <BR><FONT size=2>&gt; to 
        accommodate SIP's needs, and I haven't heard anything in 
        </FONT><BR><FONT size=2>&gt; this yet that</FONT> <BR><FONT size=2>&gt; 
        should alter it.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
        size=2>&gt; Jon Peterson</FONT> <BR><FONT size=2>&gt; NeuStar, 
        Inc.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; 
        -----Original Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: 
        Ejzak, Richard P (Richard) [<A 
        href="mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT> 
        <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 2:40 PM</FONT> 
        <BR><FONT size=2>&gt; &gt; To: 'Peterson, Jon'; 'Gonzalo 
        Camarillo'</FONT> <BR><FONT size=2>&gt; &gt; Cc: Mark Watson; 
        sipping</FONT> <BR><FONT size=2>&gt; &gt; Subject: RE: [Sipping] New 
        version of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
        Jon,</FONT> <BR><FONT size=2>&gt; &gt; I must disagree with your blanket 
        recommendation that the </FONT><BR><FONT size=2>&gt; &gt; gateway not 
        sent in-band ringing media.&nbsp; This may be possible </FONT><BR><FONT 
        size=2>&gt; &gt; in some cases - and nothing we have suggested would 
        prevent a </FONT><BR><FONT size=2>&gt; &gt; gateway from using 
        out-of-band indications.&nbsp; But ringing is </FONT><BR><FONT 
        size=2>&gt; &gt; not the only in-band call progress information you may 
        </FONT><BR><FONT size=2>&gt; &gt; receive while trying to establish a 
        call from SIP to ISUP.&nbsp; </FONT><BR><FONT size=2>&gt; &gt; The 
        transition from alerting to other forms of in-band call </FONT><BR><FONT 
        size=2>&gt; &gt; progress information is not guaranteed to be clearly 
        signaled </FONT><BR><FONT size=2>&gt; &gt; by ISUP within an ACM or CPG 
        (since every switch in the </FONT><BR><FONT size=2>&gt; &gt; network can 
        safely assume in-band call progress after a </FONT><BR><FONT size=2>&gt; 
        &gt; certain point in the call), and it is essential that this 
        </FONT><BR><FONT size=2>&gt; &gt; subsequent information (when it 
        exists) be presented to the </FONT><BR><FONT size=2>&gt; &gt; 
        UAC/user.&nbsp; And the notion of having the gateway intelligently 
        </FONT><BR><FONT size=2>&gt; &gt; filter what it thinks is ringing and 
        detect a transition to </FONT><BR><FONT size=2>&gt; &gt; other forms of 
        call progress is not acceptable.</FONT> <BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; Regards,</FONT> <BR><FONT size=2>&gt; 
        &gt; Richard Ejzak</FONT> <BR><FONT size=2>&gt; &gt; Lucent 
        Technologies</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
        size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
        size=2>&gt; &gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
        &gt; From: Peterson, Jon [<A 
        href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
        <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 4:06 PM</FONT> 
        <BR><FONT size=2>&gt; &gt; To: 'Gonzalo Camarillo'</FONT> <BR><FONT 
        size=2>&gt; &gt; Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; 
        sipping</FONT> <BR><FONT size=2>&gt; &gt; Subject: RE: [Sipping] New 
        version of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; Well,</FONT> <BR><FONT size=2>&gt; 
        &gt; </FONT><BR><FONT size=2>&gt; &gt; &gt; -----Original 
        Message-----</FONT> <BR><FONT size=2>&gt; &gt; &gt; From: Gonzalo 
        Camarillo [<A 
        href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
        <BR><FONT size=2>&gt; &gt; [snip]</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; &gt; The scenario he is after is as 
        follows; a gateway *knows* </FONT><BR><FONT size=2>&gt; &gt; that the 
        user</FONT> <BR><FONT size=2>&gt; &gt; &gt; is being alerted and also 
        *knows* that it will be sending in-band</FONT> <BR><FONT size=2>&gt; 
        &gt; &gt; ringing.</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; If 
        the gateway knows that it will be sending in-band ringing, 
        </FONT><BR><FONT size=2>&gt; &gt; my position is</FONT> <BR><FONT 
        size=2>&gt; &gt; that the gateway shouldn't be sending that media. It's 
        just </FONT><BR><FONT size=2>&gt; &gt; ring tone. The</FONT> <BR><FONT 
        size=2>&gt; &gt; UAC can generate that itself. Let's not waste the 
        bandwidth </FONT><BR><FONT size=2>&gt; &gt; sending ringing,</FONT> 
        <BR><FONT size=2>&gt; &gt; especially in forking cases, especially 
        because the UAC </FONT><BR><FONT size=2>&gt; might not even</FONT> 
        <BR><FONT size=2>&gt; &gt; render this provisional media (if it's a PC 
        UAC, for example).</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
        size=2>&gt; &gt; If media arrives at the UAC, it should override local 
        </FONT><BR><FONT size=2>&gt; &gt; ringtone, agreed. And</FONT> <BR><FONT 
        size=2>&gt; &gt; I have no problem with the idea that a UAC would delay 
        local </FONT><BR><FONT size=2>&gt; &gt; ringtone for a</FONT> <BR><FONT 
        size=2>&gt; &gt; short interval in order to see if any media is coming, 
        even </FONT><BR><FONT size=2>&gt; &gt; when 180 is</FONT> <BR><FONT 
        size=2>&gt; &gt; received. But we should not encourage gateways to send 
        </FONT><BR><FONT size=2>&gt; ringing media.</FONT> <BR><FONT size=2>&gt; 
        &gt; </FONT><BR><FONT size=2>&gt; &gt; Jon Peterson</FONT> <BR><FONT 
        size=2>&gt; &gt; NeuStar, Inc. </FONT><BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; 
</FONT></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E7F2.DA8D416C--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 13:40:48 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01270
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 13:40:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BIsNc21509
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 13:54:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BIsNO21506
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 13:54:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01239
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 13:40:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BIoUO21263;
	Tue, 11 Mar 2003 13:50:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BIntO21189
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 13:49:55 -0500
Received: from mgw-x4.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00995
	for <sipping@ietf.org>; Tue, 11 Mar 2003 13:35:48 -0500 (EST)
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2BIfNF14653
	for <sipping@ietf.org>; Tue, 11 Mar 2003 20:41:23 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60eb367b77ac158f24077@esvir04nok.ntc.nokia.com>;
 Tue, 11 Mar 2003 20:37:56 +0200
Received: from mgw.research.nokia.com ([172.21.33.76]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 11 Mar 2003 20:37:56 +0200
Received: from localhost.localdomain (hed040-224.research.nokia.com [172.21.40.224])
	by mgw.research.nokia.com (8.9.3/8.9.3) with ESMTP id UAA15924;
	Tue, 11 Mar 2003 20:37:55 +0200 (EET)
Received: from localhost.localdomain (localhost [127.0.0.1])
	by localhost.localdomain (8.12.8/8.12.5) with ESMTP id h2BIbh9M007102;
	Tue, 11 Mar 2003 20:37:43 +0200
Received: (from ppessi@localhost)
	by localhost.localdomain (8.12.8/8.12.5/Submit) id h2BIbhn6007101;
	Tue, 11 Mar 2003 20:37:43 +0200
X-Authentication-Warning: localhost.localdomain: ppessi set sender to Pekka.Pessi@nokia.com using -f
To: Adam Roach <adam@dynamicsoft.com>
Cc: "'Markus.Isomaki@nokia.com'" <Markus.Isomaki@nokia.com>,
        mwatson@nortelnetworks.com, sipping@ietf.org
Subject: Re: [Sipping] SIGCOMP and large binary content SIP messages
X-face: #V(jdpv[lI!TNUU=2*oh:="#suS*ponXW"yr6G;~L}<xZn_2^0)V{jqdc4y}@2b]ffd}SY#
 :9||1pew85O,WjiYA"6C7bW^zt^+.{b#B{lEE+4$9lrXL(55g}dU>uZ\JfD\"IG#G{j`hZI;=DmT\H
 pfDMyJ`i=:M;BM3R.`[>P^ER8+]i
From: Pekka Pessi <Pekka.Pessi@nokia.com>
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3A6457C@dyn-tx-exch-001.dynamicsoft.com> (Adam
 Roach's message of "Mon, 10 Mar 2003 17:18:34 -0600")
References: <9BF66EBF6BEFD942915B4D4D45C051F3A6457C@dyn-tx-exch-001.dynamicsoft.com>
Date: Tue, 11 Mar 2003 20:37:43 +0200
Message-ID: <pv65qp3g20.fsf@nokia.com>
User-Agent: Gnus/5.09001 (Oort Gnus v0.10) XEmacs/21.4 (Honest Recruiter,
 i386-redhat-linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginalArrivalTime: 11 Mar 2003 18:37:56.0015 (UTC) FILETIME=[5517A3F0:01C2E7FD]
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Adam Roach <adam@dynamicsoft.com> writes:
>1. SigComp works just fine with binary content. The only impact
>   that the assumption cited from 3322 has had on SigComp is
>   that the first byte of a message is examined to determine
>   whether it is compressed. Since binary content in a SIP message
>   will still have a text header, this causes no problems.

	The problem is, as Zhigang said, determining the message
	boundaries within a single stream. If SigComp messages and
	uncompressed SIP messages are multiplexed within the same
	stream, decompressor dispatcher has to rely on application (SIP
	parser) to determine message boundaries. If the SIP message were
	nice ASCII or UTF-8, the decompressor dispatcher could do this
	by itself, but the SIP message body may contain "binary" data
	like HTML (which is Latin-1 by default).

....
>Finally, I'll point out that any
>message in excess of 64 kb cannot be compressed with SigComp
>in any fashion, since RFC 3320 mandates a 64 kb output buffer
>size at the UDVM.

	On the other hand, I'd like to point out that a SIP message can
	be sent as a several SigComp messages.

						Pekka
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 18:25:59 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18322
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 18:25:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BNdde11631
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 18:39:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNddO11628
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 18:39:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18302
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 18:25:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNcuO11609;
	Tue, 11 Mar 2003 18:38:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNbwO11540
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 18:37:58 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18278
	for <sipping@ietf.org>; Tue, 11 Mar 2003 18:23:47 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z05YP9>; Tue, 11 Mar 2003 18:24:03 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410D995BDC@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: sipping@ietf.org
Date: Tue, 11 Mar 2003 18:22:18 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

My personal (not representing any organization) comments on
draft-peterson-sipping-ieprep-00

Some of these comments address details rather than the overall sense, but I
think it is important to keep even the details straight.

Section 2-2 Signaling Encapsulation

"In the CSN, it is not possible to
      make an emergency call, for example, from France to the United
      States.  International ISUP gateways that bridge between different
      signaling systems will at best discard priority information."

Actually, it IS possible.  Every month over 3000 GETS (710...) calls are
placed from over 50 international locations.  They receive no priority until
they get to  US based switch, but most of them DO  receive priority
treatment within the US.  Granted, it is the "710" that is passing through
the international gateway, but that IS a "priority label" as well as a
dialed number, and is not "discarded by the international gateway".

"It's not clear that it would even be desirable for priority
      information to be retained when you cross network boundaries - if
      someone's a government official in Iraq, when they place a call to
      the United States, should they be afforded the status of a
      government official here?"

Just as with the ISUP "Precedence" parameter, the priority information
could/should indicate (or be mappable to) the context within which it
applies.

Also, the NCS is actively working within the ITU-T to set aside an
international CPC so calls may be recognized as emergency or priority at
international gateways.  The issue of determining which countries should
receive priority is recognized, and messy. 

"Some additional discussion is necessary to understand why signaling
   encapsulation is insufficient for CSN-IP-CSN architectures.  If this
   amounts only to the requirement described in Section 7, then
   signaling encapsulation may still provide some useful properties to
   the terminating gateway."

Signaling encapsulation definitely DOES provide "some useful properties".
But, as you noted above, it does not allow for making "different routing
decisions for some calls in the presence of a priority indicator".

Sec 2.3  ETS in existing SIP networks

"This points to a fundamental questions: Is ETS opt-in?"

Personally, I think it is reasonable to expect that ETS will be "opt-in" for
the most part, at least in terms of providing any kind of special services.
But I think it is also reasonable to hope that "transparent" networks will
pass the priority information (directly or encapsulated) even if they do not
DO anything with it.  Similarly, I want to make it as easy as possible for a
network to make the decision to opt-in.

"and even then,
   there is no guarantee that fully compliant implementations will be
   ubiquitously deployed, nor configured to behave appropriately in an
   ETS situation."

This is true, even in the current CSN, and has not precluded the
implementation of  a useful, near ubiquitous, service.

"...only networks that develop relationships with the
   relevant government agencies, and are given proper configuration
   information by those agencies, will do so."

True, but the hope is to make it as painless as possible for networks to
develop those relationships.

3.1 General Requirements

REQ-4 "The 'mapping of schemes' requirement could be taken to be
   strong or weak." 

 I had interpreted it as "weak", in some ways analogous to the ISUP
Precedence parameter.

REQ-7
(wrt MLPP in the CSN) "It's never unclear within a certain network
   how a given element will behave when presented with a prioritization
   indicator."

Unfortunately, this is not true.  The standards dictate what SHOULD happen,
but the actual implementation often does not reflect the standards.

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 19:41:40 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20776
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 19:41:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2C0tMS16838
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 19:55:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C0tMO16835
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 19:55:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20772
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 19:41:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C0sVO16793;
	Tue, 11 Mar 2003 19:54:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C0rvO16758
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 19:53:57 -0500
Received: from brazilnut.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20743
	for <sipping@ietf.org>; Tue, 11 Mar 2003 19:39:43 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(user=hgs10 mech=PLAIN bits=0)
	by brazilnut.cc.columbia.edu (8.12.8/8.12.8) with ESMTP id h2C0fmcZ008790
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 11 Mar 2003 19:41:49 -0500 (EST)
Message-ID: <3E6E8260.6010308@cs.columbia.edu>
Date: Tue, 11 Mar 2003 19:42:08 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] Comments on draft-peterson-sipping-ieprep-00
References: <CBED705A7FD2D311865500508B1089410D995BDC@chntex02.is.dyncorp.com>
In-Reply-To: <CBED705A7FD2D311865500508B1089410D995BDC@chntex02.is.dyncorp.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

To amplify what Janet wrote: I think Jon's draft misses the point that 
we want

- networks that don't want to play to at least not get in the way (i.e., 
not prevent delivery of services downstream)

- require minimal changes to end systems

- support non-ISUP originators (e.g., SIP soft-terminals)

It's a nice side benefit if 'joining' ETS is easy, but the primary 
consideration is that needs it work with standards-compliant SIP 
elements (in particular, proxies) that are unaware of it.

It should also have the "earliest possible" property, i.e., as the 
network becomes ETS-aware, suitable treatment gets applied closer to the 
caller.

Thus, success is not measured by whether we get 100% coverage or 
international coverage, but rather whether I can plug in a SIP terminal 
or use my laptop and get whatever service I can.

One could clearly model the SIP solution on the GETS system, by having a 
"gateway" with a specific SIP address (equivalent to the 710 number), 
which then prompts for another SIP address or tel URI. From scaling and 
architectural perspectives, this seems much worse.

The draft tries to make this clear by emphasizing the different network 
types.

Gunn, Janet wrote:
> My personal (not representing any organization) comments on
> draft-peterson-sipping-ieprep-00
> 
> Some of these comments address details rather than the overall sense, but I
> think it is important to keep even the details straight.
> 
> Section 2-2 Signaling Encapsulation
> 
> "In the CSN, it is not possible to
>       make an emergency call, for example, from France to the United
>       States.  International ISUP gateways that bridge between different
>       signaling systems will at best discard priority information."
> 
> Actually, it IS possible.  Every month over 3000 GETS (710...) calls are
> placed from over 50 international locations.  They receive no priority until
> they get to  US based switch, but most of them DO  receive priority
> treatment within the US.  Granted, it is the "710" that is passing through
> the international gateway, but that IS a "priority label" as well as a
> dialed number, and is not "discarded by the international gateway".
> 
> "It's not clear that it would even be desirable for priority
>       information to be retained when you cross network boundaries - if
>       someone's a government official in Iraq, when they place a call to
>       the United States, should they be afforded the status of a
>       government official here?"
> 
> Just as with the ISUP "Precedence" parameter, the priority information
> could/should indicate (or be mappable to) the context within which it
> applies.
> 
> Also, the NCS is actively working within the ITU-T to set aside an
> international CPC so calls may be recognized as emergency or priority at
> international gateways.  The issue of determining which countries should
> receive priority is recognized, and messy. 
> 
> "Some additional discussion is necessary to understand why signaling
>    encapsulation is insufficient for CSN-IP-CSN architectures.  If this
>    amounts only to the requirement described in Section 7, then
>    signaling encapsulation may still provide some useful properties to
>    the terminating gateway."
> 
> Signaling encapsulation definitely DOES provide "some useful properties".
> But, as you noted above, it does not allow for making "different routing
> decisions for some calls in the presence of a priority indicator".
> 
> Sec 2.3  ETS in existing SIP networks
> 
> "This points to a fundamental questions: Is ETS opt-in?"
> 
> Personally, I think it is reasonable to expect that ETS will be "opt-in" for
> the most part, at least in terms of providing any kind of special services.
> But I think it is also reasonable to hope that "transparent" networks will
> pass the priority information (directly or encapsulated) even if they do not
> DO anything with it.  Similarly, I want to make it as easy as possible for a
> network to make the decision to opt-in.
> 
> "and even then,
>    there is no guarantee that fully compliant implementations will be
>    ubiquitously deployed, nor configured to behave appropriately in an
>    ETS situation."
> 
> This is true, even in the current CSN, and has not precluded the
> implementation of  a useful, near ubiquitous, service.
> 
> "...only networks that develop relationships with the
>    relevant government agencies, and are given proper configuration
>    information by those agencies, will do so."
> 
> True, but the hope is to make it as painless as possible for networks to
> develop those relationships.
> 
> 3.1 General Requirements
> 
> REQ-4 "The 'mapping of schemes' requirement could be taken to be
>    strong or weak." 
> 
>  I had interpreted it as "weak", in some ways analogous to the ISUP
> Precedence parameter.
> 
> REQ-7
> (wrt MLPP in the CSN) "It's never unclear within a certain network
>    how a given element will behave when presented with a prioritization
>    indicator."
> 
> Unfortunately, this is not true.  The standards dictate what SHOULD happen,
> but the actual implementation often does not reflect the standards.
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 22:03:56 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24182
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 22:03:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2C3HeG26280
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 22:17:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C3HeO26277
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 22:17:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24140
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 22:03:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C3GqO26225;
	Tue, 11 Mar 2003 22:16:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C3FhO26175
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 22:15:43 -0500
Received: from mail2.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24087
	for <sipping@ietf.org>; Tue, 11 Mar 2003 22:01:28 -0500 (EST)
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail2.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h2C31XsH010838;
	Tue, 11 Mar 2003 22:01:34 -0500 (EST)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <FFZFW61M>; Tue, 11 Mar 2003 21:03:34 -0600
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3A64586@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>,
        Adam Roach
	 <adam@dynamicsoft.com>, Markus.Isomaki@nokia.com,
        mwatson@nortelnetworks.com, sipping@ietf.org
Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Tue, 11 Mar 2003 21:03:29 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

> -----Original Message-----
> From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> 
> Having binary content in SIP messages may have two impacts on 
> SigComp: 
> 
> a) multiplexing of uncompressed messages with SigComp messages on the
> same port.
...
> For a), it is only an issue for SigComp/TCP, not SigComp/UDP (where one
> SigComp message maps to one UDP packet). Adam's point 1 and 2 are related
> to this. As to point 1, I think the SigComp receiver still needs to know 
> (somehow) the end of an uncompressed message, or at least the end of the 
> binary part of each SIP messages. Otherwise, a bit pattern 11111 in 
> the binary part will be mistaken by SigComp as the beginning of a SigComp
> message. As to point 2, I would add that the delimiter 0xFFFF can appear
> at the both the beginning and the end of a SigComp message. So, the
> receiver needs to have the same parsing logic just mentioned for bit
pattern
> 11111.

This isn't any more of an issue than it is without SigComp. SIP
messages provide their own framing, and SigComp messages do the
same. They can be trivially mixed on the same stream:

1. Peek at the first byte waiting in the stream.

2. If it is 0xf8 or higher, the next message in the stream is
   a SigComp message. The message continues until a 0xFFFF is
   encountered in the stream.

3. Otherwise, the next message in the stream is a SIP message.
   Read the stream until a CR/LF/CR/LF is encountered. Parse
   the headers, and then read the number of bytes specified
   in the "Content-Length" header.

4. Return to step 1.

/a
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 11 22:14:16 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24472
	for <sipping-archive@odin.ietf.org>; Tue, 11 Mar 2003 22:14:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2C3S0F26836
	for sipping-archive@odin.ietf.org; Tue, 11 Mar 2003 22:28:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C3S0O26833
	for <sipping-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 22:28:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24448
	for <sipping-web-archive@ietf.org>; Tue, 11 Mar 2003 22:13:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C3R8O26759;
	Tue, 11 Mar 2003 22:27:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C3QPO26716
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 22:26:25 -0500
Received: from mail2.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24421
	for <sipping@ietf.org>; Tue, 11 Mar 2003 22:12:08 -0500 (EST)
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail2.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h2C3CEsH010879;
	Tue, 11 Mar 2003 22:12:14 -0500 (EST)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <FFZFW61R>; Tue, 11 Mar 2003 21:14:15 -0600
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3A64587@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        Adam Roach
	 <adam@dynamicsoft.com>,
        "'Markus.Isomaki@nokia.com'"
	 <Markus.Isomaki@nokia.com>,
        sipping@ietf.org
Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Tue, 11 Mar 2003 21:14:09 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

I will reiterate that compressors can decide to send a message
uncompressed if they determine that it has a detrimental effect
on the dynamic dictionary. They could also send them compressed,
but with an indication that the dynamic dictionary is not to
be updated. Finally, it would be a rather straightforward
excercise to design a compressor and complementary bytecodes
that would compress the headers, and just pass through any binary
content untouched (and without impact to the any dynamic dictionary).

As I said before, I think an informational document describing
the issues and techniques used to mitigate them would be useful.
I fully intended to stay out of this conversation until it was
implied that something was actually *broken* as opposed to merely
being sub-optimal when implemented thoughtlessly.

/a

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Tuesday, March 11, 2003 8:38
To: 'Adam Roach'; 'Markus.Isomaki@nokia.com'; sipping@ietf.org
Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages


Adam, 
I am not sure I agree with the statement 'SigComp works just fine with
binary content' - although I guess it depends what you mean by 'just fine'.
A very basic compression algorithm which replaces repeated text with a
reference back to a previous occurance, and which keeps a dynamic dictionary
of previous messages (within some reasonable size limit of a few k), will
really work very well with SIP headers & SDP. Throw some binary content in
and this blots out the dictionary, dramatically cutting performance for
subsequent SIP messages.
Ok, so it still 'works', in that nothing actually breaks, but it doesn't
work 'as well' as it should. This could be resolved if the compressor
designer had known to expect this kind of message i.e. if we document the
conditions under which we expect Sigcomp to perform well. 
Of course the inefficiency in compressing subsequent SIP messages probably
costs few extra bytes when compared to the size of the previous binary
content - you might argue that if you have enough bandwidth for the binary
content itself you shouldn't worry about some inefficienies in the
'aftermath' of this content.
However at least in a wireless context it is not just bandwidth which is a
problem but the transmission time for the messages - this may not be
important for a message containing some content (the user may expect this to
take some time to arrive), but it is important for session establishement
messaging.
Finally, I think different algorithms have a different 'run in' time before
they become really efficient (e.g. LZW-based algorithms will need to see a
good few messages before they build up a good codebook). If you tailor your
compression algorithm to SIP/SDP-type messaging then you can achieve high
compression much faster. For example it would be really useful if I knew
that the second occurance of a given SIP URI could always be replaced by a
reference in full. But you need to know what 'SIP/SDP-type messaging' looks
like to get this right.
...Mark 
> -----Original Message----- 
> From: Adam Roach [mailto:adam@dynamicsoft.com] 
> Sent: 10 March 2003 23:19 
> To: 'Markus.Isomaki@nokia.com'; Watson, Mark [MOP:EP10:EXCH]; 
> sipping@ietf.org 
> Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages 
> 
> 
> Before this spins out of control... 
> 
> 1. SigComp works just fine with binary content. The only impact 
>    that the assumption cited from 3322 has had on SigComp is 
>    that the first byte of a message is examined to determine 
>    whether it is compressed. Since binary content in a SIP message 
>    will still have a text header, this causes no problems. 
> 
> 2. The TCP delimiter (0xFFFF) in SigComp is applied to the stream 
>    *after* it is compressed, not before. It has no harmful 
>    interactions with the content being sent. (And, yes, it is 
>    escaped if it is discovered in the compressed stream). 
> 
> 3. When the underlying binary data *can* be compressed, the efficiency 
>    of such compression is detemined by the compressor that the sender 
>    uses. At the SigComp interop event two weeks ago, everyone I tested 
>    with was using general-purpose compressors that would have 
> generally 
>    done a decent job with such binary data. 
> 
> 4. When the underlying binary data *cannot* be compressed much further 
>    (e.g. mp3s, jpgs, etc), then it's pretty much a forgone conclusion 
>    that the compressor won't do a good job compressing it. We can't 
>    solve the problem of compressing uncompressible data. 
> 
> Mark: an informational draft along the lines of what you propose 
> sounds like it might provide some needed guidance. I would add 
> to it the fact that compressors can decide to send a message 
> uncompressed if they determine that it has a detrimental effect 
> on the dynamic dictionary or actually grows in size. Further, 
> it would be a rather straightforward excercise to design a 
> compressor and complementary bytecodes that would compress the 
> headers, and just pass through the uncompressible binary content 
> untouched (solving both the dynamic dictonary problem and the 
> growing message problem). Finally, I'll point out that any 
> message in excess of 64 kb cannot be compressed with SigComp 
> in any fashion, since RFC 3320 mandates a 64 kb output buffer 
> size at the UDVM. 
> 
> /a 
> 
> -----Original Message----- 
> From: Markus.Isomaki@nokia.com [mailto:Markus.Isomaki@nokia.com] 
> Sent: Monday, March 10, 2003 14:21 
> To: mwatson@nortelnetworks.com; sipping@ietf.org 
> Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages 
> 
> 
> Hi Mark, 
> 
> I think it will really be a big deficiency if SigComp can't 
> handle somehow 
> binary content in SIP messages. Presence (both PUBLISH and 
> NOTIFY) is one 
> thing that can potentially have binary attachments, and not 
> all of them are 
> going to be transported via content indirection. However, even more 
> important case is SIP MESSAGE. Already today mobile phones 
> transfer images 
> of size ~50 kB using MMS, and I assume the same would happen 
> if SIP were 
> available. And again, not all of this would use HTTP and CI. 
> 
> In addition to the dynamic dictionary problem I believe that 
> there is a 
> problem with SIP/SigComp over TCP (which would be almost 
> always the trasport 
> if binary content is included). I've understood that SigComp 
> assumes that 
> some special non-ASCII character is used to indicate the 
> start and end of a 
> compressed message. Obviously this does not work if part of 
> the message 
> itself is non-ASCII. So is there even a bigger problem than just 
> non-friendliness that needs to be fixed? 
> 
> Markus 
> 
> -----Original Message----- 
> From: ext Mark Watson [mailto:mwatson@nortelnetworks.com] 
> Sent: 07 March, 2003 16:52 
> To: 'sipping@ietf.org' 
> Subject: [Sipping] SIGCOMP and large binary content SIP messages 
> 
> 
> All, 
> We have had a couple of short threads on SIMPLE considering 
> the implications 
> of including large binary content within SIP messages (using MIME) (by 
> large, I mean anything more than several times the size of a 
> normal INVITE 
> and by binary, I mean arbitrary bytes, rather than text). An 
> example would 
> be a JPEG or audio file. It's been suggested that a user 
> might include one 
> of these as part of their presence information. 
> On the face of it, it seems that this might have implications for the 
> effectiveness of SIPCOMP, firstly because such data may not 
> itself compress 
> well (compared to SIP headers and SDP), and secondly because 
> of the impact 
> this might have on any dynamic dictionary. 
> There may be ways to design SIGCOMP compressors which can 
> cope with this, 
> and if so it would be good to have some guidelines included 
> in the SIGCOMP 
> documentation. This would stop people from naively designing SIGCOMP 
> compressors based on false assumptions about the nature of 
> SIP messaging 
> (for example SIGCOMP has to date made the assumption that SIP 
> messages are 
> ASCII encoded - RFC3322). 
> So, before raising this in ROCH, perhaps we need to discuss what those 
> assumptions about SIP messaging should be - i.e. to 
> approximately define a 
> class of SIP messages for which app. designers can expect 
> SIGCOMP to perform 
> well. Then if applications need to generate messages outside 
> that class, 
> they can choose between (i) potentially poor SIGCOMP 
> performance (which may 
> be acceptable in some cases) or (ii) using techniques like Content 
> Indirection to return their messages into the 'SIGCOMP 
> friendly' class. 
> I know large content in SIP messages has been discussed 
> before in various 
> contexts, but is there any chance we can come to a rough 
> consensus on what a 
> 'SIGCOMP-friendly' class of SIP messages should look like ? 
> Regards, 
> Mark Watson 
> 
> 
> 
> 
> -----Original Message----- 
> From: Watson, Mark [MOP:EP10:EXCH] 
> Sent: 05 March 2003 10:33 
> To: 'mikko.lonnfors@nokia.com'; simple@ietf.org 
> Subject: RE: [Simple] I-D 
> ACTION:draft-lonnfors-simple-partial-notify-00.t 
> xt 
> 
> 
> Mikko, All, 
> The correct place to document such recommendations about 
> SIGCOMP would be in 
> some ROCH documentation, perhaps the SIGCOMP User Guide ? I 
> notice that 
> RFC3322 (Signalling Compression Requirements & Assumptions) 
> already assumes 
> that the signalling messages are ASCII encoded, so if this is 
> not the case I 
> think it's fairly urgent to get some discussion going. 
> Before we go to ROCH, though, we need to make some decision 
> on what kind of 
> content we see being commonly included in SIP messages - i.e. 
> what does 
> SIGCOMP have to deal with in addition to SIP Headers and SDP ?? 
> To my mind this is a discussion for SIPPING - does anyone 
> object to moving 
> this discussion there ? (Let's avoid creating a cross-posted thread if 
> possible - they're always a nightmare). 
> ...Mark 
> 
> 
> 
> > -----Original Message----- 
> > From: mikko.lonnfors@nokia.com [mailto:mikko.lonnfors@nokia.com] 
> > Sent: 04 March 2003 10:03 
> > To: Watson, Mark [MOP:EP10:EXCH]; simple@ietf.org 
> > Subject: RE: [Simple] I-D 
> > ACTION:draft-lonnfors-simple-partial-notify-00.txt 
> > 
> > 
> > Hi mark, 
> > 
> > Inline inside <ML>: 
> > 
> > 
> > All, 
> > I am not convinced by the discussion on SIGCOMP which has 
> > been introduced into this draft (Section 1.1). 
> > Firstly, is this even the correct place to describe these issues ?? 
> > 
> > <ML> 
> > Yes, you are right. To move discussion forward we needed to 
> > place text somewhere and in this case only place we could 
> > place it was the partial notification draft. 
> > </ML> 
> > 
> >  If we really expect to see large binary content in SIP 
> > messages, then we should document the impacts for SIGCOMP 
> > somewhere more general - not buried in a presence partial 
> > notifications discussion. 
> > 
> > <ML> 
> > Yes 
> > </ML> 
> > 
> > If we do not expect such content, we should document that 
> > fact somewhere more general too. We need to make a decision 
> > one way or the other because it has important implications 
> > for the design of SIGCOMP compressors. 
> > 
> > <ML> 
> > This is probably true. 
> > </ML> 
> > 
> > Secondly, two of the solutions referred to involve the 
> > SIGCOMP layer having knowledge of the content type, which is 
> > a major architectural change. Presently, the SIGCOMP layer 
> > does not parse SIP, MIME etc. 
> > 
> > <ML> 
> > We have been talking about this issue with SIGCOMP author Z. 
> > Liu (as at least I not an expert in this are) and these were 
> > mentioned as possible solutions for this problem. I am also 
> > not convinced that these two solutions are the best ones and 
> > if other people feel same I am quite happy to drop them. 
> > </ML> 
> > 
> > Thirdly, the last solution mentioned involves leaving 
> > 'binary' content uncompressed, but this does not necessarily 
> > mean that this content will not mess up the dynamic 
> > dictionary. The compression scheme would need to detect 
> > 'uncompressible' parts of the message and leave these out of 
> > the dictionary. 
> > 
> > <ML> 
> > As far as I know this should be quite easy thing to 
> > accomplish for a SIGCOMP implementation. Of course it should 
> > be specified (recommended) somewhere what is appropriate 
> > threshold value for data which should be considered 
> 'uncompressible'. 
> > </ML> 
> > 
> > So, if we expect binary content in SIP, we should document 
> > the impacts in SIGCOMP somewhere in the sip/sipping WGs. We 
> > should decide whether we expect SIGCOMP to cope with such 
> > binary content in an efficient way (i.e. if we think the same 
> > content will be sent multiple times) or whether we are happy 
> > for SIGCOMP to leave such content uncompressed (i.e. if we 
> > think the same content will generally only be sent once). 
> > 
> > Finally, I think we concluded in the last discussion on this 
> > that it was not appropriate to include in-line binary content 
> > in the presence document itself due to encoding issues - 
> > there is still some reference to this in the draft. Large 
> > binary content would need to referenced from the presence 
> > document, and we left it open whether this reference could be 
> > to other MIME parts within the same SIP message. 
> > 
> > <ML> 
> > Yes, this is our mistake. I also agree that large binary data 
> > should not be in-line with other presence data. This will be 
> > fixed in next version 
> > </ML> 
> > 
> > Thanks for comments 
> > - Mikko 
> > 
> > Regards, 
> > Mark 
> > > -----Original Message----- 
> > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
> > > Sent: 24 February 2003 11:45 
> > > Cc: simple@ietf.org 
> > > Subject: [Simple] I-D 
> > > ACTION:draft-lonnfors-simple-partial-notify-00.txt 
> > > 
> > > 
> > > A New Internet-Draft is available from the on-line 
> > > Internet-Drafts directories. 
> > > 
> > > 
> > >       Title           : Partial Notification of Presence 
> > Information 
> > >       Author(s)       : J. Costa-Requena, E. Leppanen et al. 
> > >       Filename        : 
> draft-lonnfors-simple-partial-notify-00.txt 
> > >       Pages           : 24 
> > >       Date            : 2003-2-21 
> > >       
> > > A Presence service implemented using SIMPLE has some 
> > constraints for 
> > > delivering presence information to devices with low data 
> processing 
> > > capabilities, small display, and limited battery power. Other 
> > > limitations can be caused by the interface between the 
> terminal and 
> > > the network, i.e. over radio links with high latency and low 
> > > bandwidth. This memo presents a solution that aids in 
> reducing the 
> > > impact of those constrains and increasing efficiency, by 
> > introducing 
> > > a new MIME-type æpartial notificationsÆ and a Require header 
> > > extension æpartial-notificationÆ. 
> > > 
> > > A URL for this Internet-Draft is: 
> > > http://www.ietf.org/internet-drafts/draft-lonnfors-simple-part 
> > > ial-notify-00.txt 
> > > 
> > > To remove yourself from the IETF Announcement list, send a 
> > message to 
> > > ietf-announce-request with the word unsubscribe in the body 
> > > of the message. 
> > > 
> > > 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-lonnfors-simple-partial-notify-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-lonnfors-simple-partial-notify-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. 
> > > 
> > 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 12 02:10:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09553
	for <sipping-archive@odin.ietf.org>; Wed, 12 Mar 2003 02:10:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2C7Odj18970
	for sipping-archive@odin.ietf.org; Wed, 12 Mar 2003 02:24:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C7OdO18967
	for <sipping-web-archive@optimus.ietf.org>; Wed, 12 Mar 2003 02:24:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09214
	for <sipping-web-archive@ietf.org>; Wed, 12 Mar 2003 02:10:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C7NhO18925;
	Wed, 12 Mar 2003 02:23:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C7MjO18864
	for <sipping@optimus.ietf.org>; Wed, 12 Mar 2003 02:22:45 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07395
	for <sipping@ietf.org>; Wed, 12 Mar 2003 02:08:23 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2C7AWB3025731;
	Wed, 12 Mar 2003 08:10:32 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id GPH5WXSZ; Wed, 12 Mar 2003 08:10:31 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2C7AU6B013363;
	Wed, 12 Mar 2003 09:10:31 +0200 (EET)
Message-ID: <3E6EDD66.11563FAA@lmf.ericsson.se>
Date: Wed, 12 Mar 2003 09:10:30 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
CC: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>,
        sipping <sipping@ietf.org>
Subject: Re: [Sipping] New version of the early media draft
References: <DBC3D7D0A071F743AE0767C9C6071EDA0482BBD9@il0015exch010u.ih.lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Richard,

just to be clear, I am not proposing to change the draft. I am just
saying that using the SDP direction attribute seems to resolve Mark's
concerns.

> My concern is to do media detection and tone insertion efficiently, 
> correctly, and only when necessary.

I guess the crux of the issue is the part where you say "only when
necessary"... it is clear that such an indication would save you
performing media detection for 180 responses with the inband media flag.

My position is, as I said in this thread before, that if people
considered this as an important gain, I would not find it unreasonable
to standardize an empty Alert-Info header field.

However, others have expressed concerns about that...

Gonzalo

"Ejzak, Richard P (Richard)" wrote:
> 
> Gonzalo,
> Thanks for your attempt to find a way forward.  But I never objected to media detection across the board.  It is necessary, as you point out, to avoid clipping in certain scenarios.  There was a scenario very similar to the one you propose in an earlier version of the manyfolks draft that was removed after I raised an objection last year, because it introduced a potential for media clipping.
> 
> My concern is to do media detection and tone insertion efficiently, correctly, and only when necessary.  As I stated earlier, there is no reason to change how things work for native SIP UAs.  Your proposal would actually have the most impact on native SIP UAs (typically without in-band media)!  But when a UAS PSTN gateway is in the mix with in-band call progress media, we know there is no need for either media detection or tone insertion, and, in fact, there's a good chance they would muck things up.
> 
> Your proposal unfortunately appears to cause more harm than good (by re-introducing potential for clipping and impacting SIP UAs without in-band media).  We need some kind of indication associated with the 180 (not SDP) that in-band call progress information is available.
> 
> I am mightily confused as to why this is such a challenging problem.  I have proposed at least two backwards compatible methods for signaling this information.
> 
> Regards,
> Richard Ejzak
> Lucent Technologies
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 12 03:47:55 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26317
	for <sipping-archive@odin.ietf.org>; Wed, 12 Mar 2003 03:47:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2C91k325072
	for sipping-archive@odin.ietf.org; Wed, 12 Mar 2003 04:01:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C91kO25069
	for <sipping-web-archive@optimus.ietf.org>; Wed, 12 Mar 2003 04:01:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26311
	for <sipping-web-archive@ietf.org>; Wed, 12 Mar 2003 03:47:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C915O25057;
	Wed, 12 Mar 2003 04:01:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C8xwO24972
	for <sipping@optimus.ietf.org>; Wed, 12 Mar 2003 03:59:58 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26302
	for <sipping@ietf.org>; Wed, 12 Mar 2003 03:45:34 -0500 (EST)
Received: from esealnt610.al.sw.ericsson.se (alteon-nat3.sw.ericsson.se [153.88.254.120])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2C8lNB3026006;
	Wed, 12 Mar 2003 09:47:23 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id GZAK1CKA; Wed, 12 Mar 2003 09:47:22 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2C8lM6B019049;
	Wed, 12 Mar 2003 10:47:22 +0200 (EET)
Message-ID: <3E6EF41A.F30D12E4@lmf.ericsson.se>
Date: Wed, 12 Mar 2003 10:47:22 +0200
X-Sybari-Trust: 1dbd2c46 9ffcebbb 7a95d2f4 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
CC: Rohan Mahy <rohan@cisco.com>, Dean Willis <dean.willis@softarmor.com>,
        Jon Peterson <Jon.Peterson@neustar.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Draft Agenda, SIPPING WG
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

here you have our draft agenda:

http://www.softarmor.com/sipping/meets/ietf56/agenda.html

Please, give us feedback asap.

Thanks,

Gonzalo


Monday, March 17, 1930-2200 

1930 Agenda Bash 
1935 Status -- Chairs 
1945 Persistent Connection Management Requirements, Vijay K. Gurbani 
   draft-jain-sipping-persistent-conn-reqs-00.txt 
   draft-ietf-sipping-connect-reuse-reqs-00.txt 
2005 Role-based Authorization Requirements, Jon Peterson 
   draft-peterson-sipping-role-authz-00.txt 
2015 Service Examples, Alan Johnston 
   draft-ietf-sipping-service-examples-04.txt 
2025 Call Control -- Transfer, Allan Johnston 
   draft-ietf-sipping-cc-transfer-01.txt 
2035 Request History, Mary Barnes 
   draft-ietf-sipping-req-history-02.txt 
   draft-barnes-sipping-history-info-02.txt 
2055 Limiting Notifications Rate, Aki Niemi 
   draft-niemi-sipping-event-throttle-reqs-01.txt 
2105 Issues in Dual Stack Environments, Hakan N. Persson 
   draft-persson-sipping-sip-issues-dual-stack-00.txt 
2115 SIP Endpoint Service Charging Requirements, Wolfgang Beck 
   draft-beck-sipping-svc-charging-req-01.txt 
2125 SIP Network Address Translation, Jonathan Rosenberg 
   draft-ietf-sipping-nat-scenarios-00.txt 
   draft-rosenberg-sipping-ice-00.txt 
2135 Caller Preferences Use cases, Jonathan Rosenberg 
   draft-rosenberg-sipping-callerprefs-usecases-00.txt 
2145 URI Leasing, Jonathan Rosenberg 
   draft-rosenberg-sipping-lease-00.txt 
2200 Wrap 



Wednesday, March 19, 1530-1730 

1530 Agenda Bash 
1535 SIP Conferencing Design Team, Alan Johnston 
   Web Page for the Design Team 
1605 Application Server Interaction Design Team, Jonathan Rosenberg 
   Web Page for the Design Team 
1610 Transcoding Design Team, Gonzalo Camarillo 
   Web Page for the Design Team 
1615 Emergency Calls Design Team, Jon Peterson 
   Web Page for the Design Team 
1620 Considerations on the IPREP Requirements, Jon Peterson 
   draft-peterson-sipping-ieprep-00.txt 
1630 Session Policy Requiments, Jonathan Rosenberg 
   draft-rosenberg-sipping-session-policy-00.txt 
1640 Early Media, Gonzalo Camarillo 
   draft-camarillo-sipping-early-media-01.txt 
1650 SIP-AAA Requirements, Gonzalo Camarillo 
   draft-ietf-sipping-aaa-req-02.txt 
1700 Network Announcements, Eric Burger 
   draft-burger-sipping-netann-05.txt 
1710 Open Discussion 
1730 Wrap
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 12 04:00:05 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26537
	for <sipping-archive@odin.ietf.org>; Wed, 12 Mar 2003 04:00:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2C9Duv26648
	for sipping-archive@odin.ietf.org; Wed, 12 Mar 2003 04:13:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C9DuO26645
	for <sipping-web-archive@optimus.ietf.org>; Wed, 12 Mar 2003 04:13:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26502
	for <sipping-web-archive@ietf.org>; Wed, 12 Mar 2003 03:59:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C9D9O26603;
	Wed, 12 Mar 2003 04:13:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BFOuO05060
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 10:24:56 -0500
Received: from mail.tssg.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22492
	for <sipping@ietf.org>; Tue, 11 Mar 2003 10:10:55 -0500 (EST)
Received: from boolard (unknown [10.37.1.56])
	by mail.tssg.org (Postfix) with SMTP
	id 0751A1806B; Tue, 11 Mar 2003 15:07:25 +0000 (GMT)
From: "Shane McCormack" <smccormack@tssg.org>
To: "Henry Sinnreich" <Henry.Sinnreich@wcom.com>,
        "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] Sip and wifi
Date: Tue, 11 Mar 2003 15:17:18 -0000
Message-ID: <HKEILFGJCBMBHOCGMAJNOECHDBAA.smccormack@tssg.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <000001c2e7de$4a9a7e30$4e8232a6@hsinnreich2>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

what about mobile sip enabled devices roaming from one wifi "hotspot" to
another which are not from the same wireless access provider?
also
What mechanism is being used, mobile ip in the IP layer or sip based
mobility support as stated in Wedlunds and Shulzrinnes paper "Mobility
Support Using Sip"?
I am interested to hear some opinions on these matters as.

Regards
Shane McCormack

Research Assistant,
TSSG, Confederation House,
Waterford Business Park, Cork Road,
Waterford, Co. Waterford.

Phone: +353 51 302927     Fax: +353 51 302901
Mobile: +353 87 9955505
http://www.tssg.org <http://www.tssg.org/>
MSN: mccormackshane@hotmail.com <mailto:mccormackshane@hotmail.com>





-----Original Message-----
From: Henry Sinnreich [mailto:Henry.Sinnreich@wcom.com]
Sent: 11 March 2003 14:56
To: 'Shane McCormack'; 'sipping'
Subject: RE: [Sipping] Sip and wifi


*This message was transferred with a trial version of CommuniGate(tm) Pro*
> on any work related to Sip Services over Wifi interfaces.

Just connect the Pingtel phone to your Wi-Fi using the Linksys WET11 and
it works. Some SIP phones don't do the 10/100 Mb/s Ethernet negociation
correctly and an old Ethernet hub in the middle solves the problem.

Thanks, Henry

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]
> On Behalf Of Shane McCormack
> Sent: Monday, March 10, 2003 2:28 PM
> To: sipping
> Subject: [Sipping] Sip and wifi
>
>
> Hi,
> Just wondering is there any work and dissemination been done
> on any work related to Sip Services over Wifi interfaces. I
> would be interested to hear for my thesis work.
>
> Regards
> Shane McCormack
>
> Research Assistant,
> TSSG, Confederation House,
> Waterford Business Park, Cork Road,
> Waterford, Co. Waterford.
>
> Phone: +353 51 302927     Fax: +353 51 302901
> Mobile: +353 87 9955505
> http://www.tssg.org
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current
> sip Use sip@ietf.org for new developments of core SIP
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 12 04:00:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26573
	for <sipping-archive@odin.ietf.org>; Wed, 12 Mar 2003 04:00:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2C9EHe26725
	for sipping-archive@odin.ietf.org; Wed, 12 Mar 2003 04:14:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C9EHO26722
	for <sipping-web-archive@optimus.ietf.org>; Wed, 12 Mar 2003 04:14:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26511
	for <sipping-web-archive@ietf.org>; Wed, 12 Mar 2003 03:59:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C9D2O26583;
	Wed, 12 Mar 2003 04:13:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BEpbO02761
	for <sipping@optimus.ietf.org>; Tue, 11 Mar 2003 09:51:37 -0500
Received: from znsgs01r.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20740
	for <sipping@ietf.org>; Tue, 11 Mar 2003 09:37:32 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (europem01.nt.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2BEdMr17478;
	Tue, 11 Mar 2003 14:39:23 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GR681WHA; Tue, 11 Mar 2003 14:39:22 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GR4VNX6W>; Tue, 11 Mar 2003 14:38:17 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C88@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Adam Roach'" <adam@dynamicsoft.com>,
        "'Markus.Isomaki@nokia.com'"
	 <Markus.Isomaki@nokia.com>,
        sipping@ietf.org
Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Tue, 11 Mar 2003 14:38:14 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E7DB.D92CD6E6"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E7DB.D92CD6E6
Content-Type: text/plain;
	charset="iso-8859-1"

Adam,

I am not sure I agree with the statement 'SigComp works just fine with
binary content' - although I guess it depends what you mean by 'just fine'.

A very basic compression algorithm which replaces repeated text with a
reference back to a previous occurance, and which keeps a dynamic dictionary
of previous messages (within some reasonable size limit of a few k), will
really work very well with SIP headers & SDP. Throw some binary content in
and this blots out the dictionary, dramatically cutting performance for
subsequent SIP messages.

Ok, so it still 'works', in that nothing actually breaks, but it doesn't
work 'as well' as it should. This could be resolved if the compressor
designer had known to expect this kind of message i.e. if we document the
conditions under which we expect Sigcomp to perform well. 

Of course the inefficiency in compressing subsequent SIP messages probably
costs few extra bytes when compared to the size of the previous binary
content - you might argue that if you have enough bandwidth for the binary
content itself you shouldn't worry about some inefficienies in the
'aftermath' of this content.

However at least in a wireless context it is not just bandwidth which is a
problem but the transmission time for the messages - this may not be
important for a message containing some content (the user may expect this to
take some time to arrive), but it is important for session establishement
messaging.

Finally, I think different algorithms have a different 'run in' time before
they become really efficient (e.g. LZW-based algorithms will need to see a
good few messages before they build up a good codebook). If you tailor your
compression algorithm to SIP/SDP-type messaging then you can achieve high
compression much faster. For example it would be really useful if I knew
that the second occurance of a given SIP URI could always be replaced by a
reference in full. But you need to know what 'SIP/SDP-type messaging' looks
like to get this right.

...Mark

> -----Original Message-----
> From: Adam Roach [mailto:adam@dynamicsoft.com]
> Sent: 10 March 2003 23:19
> To: 'Markus.Isomaki@nokia.com'; Watson, Mark [MOP:EP10:EXCH];
> sipping@ietf.org
> Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
> 
> 
> Before this spins out of control...
> 
> 1. SigComp works just fine with binary content. The only impact
>    that the assumption cited from 3322 has had on SigComp is
>    that the first byte of a message is examined to determine
>    whether it is compressed. Since binary content in a SIP message
>    will still have a text header, this causes no problems.
> 
> 2. The TCP delimiter (0xFFFF) in SigComp is applied to the stream
>    *after* it is compressed, not before. It has no harmful
>    interactions with the content being sent. (And, yes, it is
>    escaped if it is discovered in the compressed stream).
> 
> 3. When the underlying binary data *can* be compressed, the efficiency
>    of such compression is detemined by the compressor that the sender
>    uses. At the SigComp interop event two weeks ago, everyone I tested
>    with was using general-purpose compressors that would have 
> generally
>    done a decent job with such binary data.
> 
> 4. When the underlying binary data *cannot* be compressed much further
>    (e.g. mp3s, jpgs, etc), then it's pretty much a forgone conclusion
>    that the compressor won't do a good job compressing it. We can't
>    solve the problem of compressing uncompressible data.
> 
> Mark: an informational draft along the lines of what you propose
> sounds like it might provide some needed guidance. I would add
> to it the fact that compressors can decide to send a message
> uncompressed if they determine that it has a detrimental effect
> on the dynamic dictionary or actually grows in size. Further,
> it would be a rather straightforward excercise to design a
> compressor and complementary bytecodes that would compress the
> headers, and just pass through the uncompressible binary content
> untouched (solving both the dynamic dictonary problem and the
> growing message problem). Finally, I'll point out that any
> message in excess of 64 kb cannot be compressed with SigComp
> in any fashion, since RFC 3320 mandates a 64 kb output buffer
> size at the UDVM.
> 
> /a
> 
> -----Original Message-----
> From: Markus.Isomaki@nokia.com [mailto:Markus.Isomaki@nokia.com]
> Sent: Monday, March 10, 2003 14:21
> To: mwatson@nortelnetworks.com; sipping@ietf.org
> Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
> 
> 
> Hi Mark,
> 
> I think it will really be a big deficiency if SigComp can't 
> handle somehow
> binary content in SIP messages. Presence (both PUBLISH and 
> NOTIFY) is one
> thing that can potentially have binary attachments, and not 
> all of them are
> going to be transported via content indirection. However, even more
> important case is SIP MESSAGE. Already today mobile phones 
> transfer images
> of size ~50 kB using MMS, and I assume the same would happen 
> if SIP were
> available. And again, not all of this would use HTTP and CI. 
> 
> In addition to the dynamic dictionary problem I believe that 
> there is a
> problem with SIP/SigComp over TCP (which would be almost 
> always the trasport
> if binary content is included). I've understood that SigComp 
> assumes that
> some special non-ASCII character is used to indicate the 
> start and end of a
> compressed message. Obviously this does not work if part of 
> the message
> itself is non-ASCII. So is there even a bigger problem than just
> non-friendliness that needs to be fixed?
> 
> Markus
> 
> -----Original Message-----
> From: ext Mark Watson [mailto:mwatson@nortelnetworks.com]
> Sent: 07 March, 2003 16:52
> To: 'sipping@ietf.org'
> Subject: [Sipping] SIGCOMP and large binary content SIP messages
> 
> 
> All, 
> We have had a couple of short threads on SIMPLE considering 
> the implications
> of including large binary content within SIP messages (using MIME) (by
> large, I mean anything more than several times the size of a 
> normal INVITE
> and by binary, I mean arbitrary bytes, rather than text). An 
> example would
> be a JPEG or audio file. It's been suggested that a user 
> might include one
> of these as part of their presence information.
> On the face of it, it seems that this might have implications for the
> effectiveness of SIPCOMP, firstly because such data may not 
> itself compress
> well (compared to SIP headers and SDP), and secondly because 
> of the impact
> this might have on any dynamic dictionary.
> There may be ways to design SIGCOMP compressors which can 
> cope with this,
> and if so it would be good to have some guidelines included 
> in the SIGCOMP
> documentation. This would stop people from naively designing SIGCOMP
> compressors based on false assumptions about the nature of 
> SIP messaging
> (for example SIGCOMP has to date made the assumption that SIP 
> messages are
> ASCII encoded - RFC3322).
> So, before raising this in ROCH, perhaps we need to discuss what those
> assumptions about SIP messaging should be - i.e. to 
> approximately define a
> class of SIP messages for which app. designers can expect 
> SIGCOMP to perform
> well. Then if applications need to generate messages outside 
> that class,
> they can choose between (i) potentially poor SIGCOMP 
> performance (which may
> be acceptable in some cases) or (ii) using techniques like Content
> Indirection to return their messages into the 'SIGCOMP 
> friendly' class.
> I know large content in SIP messages has been discussed 
> before in various
> contexts, but is there any chance we can come to a rough 
> consensus on what a
> 'SIGCOMP-friendly' class of SIP messages should look like ?
> Regards, 
> Mark Watson 
> 
> 
> 
> 
> -----Original Message----- 
> From: Watson, Mark [MOP:EP10:EXCH] 
> Sent: 05 March 2003 10:33 
> To: 'mikko.lonnfors@nokia.com'; simple@ietf.org 
> Subject: RE: [Simple] I-D 
> ACTION:draft-lonnfors-simple-partial-notify-00.t
> xt 
> 
> 
> Mikko, All, 
> The correct place to document such recommendations about 
> SIGCOMP would be in
> some ROCH documentation, perhaps the SIGCOMP User Guide ? I 
> notice that
> RFC3322 (Signalling Compression Requirements & Assumptions) 
> already assumes
> that the signalling messages are ASCII encoded, so if this is 
> not the case I
> think it's fairly urgent to get some discussion going.
> Before we go to ROCH, though, we need to make some decision 
> on what kind of
> content we see being commonly included in SIP messages - i.e. 
> what does
> SIGCOMP have to deal with in addition to SIP Headers and SDP ??
> To my mind this is a discussion for SIPPING - does anyone 
> object to moving
> this discussion there ? (Let's avoid creating a cross-posted thread if
> possible - they're always a nightmare).
> ...Mark 
> 
> 
> 
> > -----Original Message----- 
> > From: mikko.lonnfors@nokia.com [mailto:mikko.lonnfors@nokia.com] 
> > Sent: 04 March 2003 10:03 
> > To: Watson, Mark [MOP:EP10:EXCH]; simple@ietf.org 
> > Subject: RE: [Simple] I-D 
> > ACTION:draft-lonnfors-simple-partial-notify-00.txt 
> > 
> > 
> > Hi mark, 
> > 
> > Inline inside <ML>: 
> > 
> > 
> > All, 
> > I am not convinced by the discussion on SIGCOMP which has 
> > been introduced into this draft (Section 1.1). 
> > Firstly, is this even the correct place to describe these issues ?? 
> > 
> > <ML> 
> > Yes, you are right. To move discussion forward we needed to 
> > place text somewhere and in this case only place we could 
> > place it was the partial notification draft. 
> > </ML> 
> > 
> >  If we really expect to see large binary content in SIP 
> > messages, then we should document the impacts for SIGCOMP 
> > somewhere more general - not buried in a presence partial 
> > notifications discussion. 
> > 
> > <ML> 
> > Yes 
> > </ML> 
> > 
> > If we do not expect such content, we should document that 
> > fact somewhere more general too. We need to make a decision 
> > one way or the other because it has important implications 
> > for the design of SIGCOMP compressors. 
> > 
> > <ML> 
> > This is probably true. 
> > </ML> 
> > 
> > Secondly, two of the solutions referred to involve the 
> > SIGCOMP layer having knowledge of the content type, which is 
> > a major architectural change. Presently, the SIGCOMP layer 
> > does not parse SIP, MIME etc. 
> > 
> > <ML> 
> > We have been talking about this issue with SIGCOMP author Z. 
> > Liu (as at least I not an expert in this are) and these were 
> > mentioned as possible solutions for this problem. I am also 
> > not convinced that these two solutions are the best ones and 
> > if other people feel same I am quite happy to drop them. 
> > </ML> 
> > 
> > Thirdly, the last solution mentioned involves leaving 
> > 'binary' content uncompressed, but this does not necessarily 
> > mean that this content will not mess up the dynamic 
> > dictionary. The compression scheme would need to detect 
> > 'uncompressible' parts of the message and leave these out of 
> > the dictionary. 
> > 
> > <ML> 
> > As far as I know this should be quite easy thing to 
> > accomplish for a SIGCOMP implementation. Of course it should 
> > be specified (recommended) somewhere what is appropriate 
> > threshold value for data which should be considered 
> 'uncompressible'. 
> > </ML> 
> > 
> > So, if we expect binary content in SIP, we should document 
> > the impacts in SIGCOMP somewhere in the sip/sipping WGs. We 
> > should decide whether we expect SIGCOMP to cope with such 
> > binary content in an efficient way (i.e. if we think the same 
> > content will be sent multiple times) or whether we are happy 
> > for SIGCOMP to leave such content uncompressed (i.e. if we 
> > think the same content will generally only be sent once). 
> > 
> > Finally, I think we concluded in the last discussion on this 
> > that it was not appropriate to include in-line binary content 
> > in the presence document itself due to encoding issues - 
> > there is still some reference to this in the draft. Large 
> > binary content would need to referenced from the presence 
> > document, and we left it open whether this reference could be 
> > to other MIME parts within the same SIP message. 
> > 
> > <ML> 
> > Yes, this is our mistake. I also agree that large binary data 
> > should not be in-line with other presence data. This will be 
> > fixed in next version 
> > </ML> 
> > 
> > Thanks for comments 
> > - Mikko 
> > 
> > Regards, 
> > Mark 
> > > -----Original Message----- 
> > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
> > > Sent: 24 February 2003 11:45 
> > > Cc: simple@ietf.org 
> > > Subject: [Simple] I-D 
> > > ACTION:draft-lonnfors-simple-partial-notify-00.txt 
> > > 
> > > 
> > > A New Internet-Draft is available from the on-line 
> > > Internet-Drafts directories. 
> > > 
> > > 
> > >       Title           : Partial Notification of Presence 
> > Information 
> > >       Author(s)       : J. Costa-Requena, E. Leppanen et al. 
> > >       Filename        : 
> draft-lonnfors-simple-partial-notify-00.txt 
> > >       Pages           : 24 
> > >       Date            : 2003-2-21 
> > >       
> > > A Presence service implemented using SIMPLE has some 
> > constraints for 
> > > delivering presence information to devices with low data 
> processing 
> > > capabilities, small display, and limited battery power. Other 
> > > limitations can be caused by the interface between the 
> terminal and 
> > > the network, i.e. over radio links with high latency and low 
> > > bandwidth. This memo presents a solution that aids in 
> reducing the 
> > > impact of those constrains and increasing efficiency, by 
> > introducing 
> > > a new MIME-type æpartial notificationsÆ and a Require header 
> > > extension æpartial-notificationÆ. 
> > > 
> > > A URL for this Internet-Draft is: 
> > > http://www.ietf.org/internet-drafts/draft-lonnfors-simple-part 
> > > ial-notify-00.txt 
> > > 
> > > To remove yourself from the IETF Announcement list, send a 
> > message to 
> > > ietf-announce-request with the word unsubscribe in the body 
> > > of the message. 
> > > 
> > > 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-lonnfors-simple-partial-notify-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-lonnfors-simple-partial-notify-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_001_01C2E7DB.D92CD6E6
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>RE: [Sipping] SIGCOMP and large binary content SIP =
messages</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Adam,</FONT>
</P>

<P><FONT SIZE=3D2>I am not sure I agree with the statement 'SigComp =
works just fine with binary content' - although I guess it depends what =
you mean by 'just fine'.</FONT></P>

<P><FONT SIZE=3D2>A very basic compression algorithm which replaces =
repeated text with a reference back to a previous occurance, and which =
keeps a dynamic dictionary of previous messages (within some reasonable =
size limit of a few k), will really work very well with SIP headers =
&amp; SDP. Throw some binary content in and this blots out the =
dictionary, dramatically cutting performance for subsequent SIP =
messages.</FONT></P>

<P><FONT SIZE=3D2>Ok, so it still 'works', in that nothing actually =
breaks, but it doesn't work 'as well' as it should. This could be =
resolved if the compressor designer had known to expect this kind of =
message i.e. if we document the conditions under which we expect =
Sigcomp to perform well. </FONT></P>

<P><FONT SIZE=3D2>Of course the inefficiency in compressing subsequent =
SIP messages probably costs few extra bytes when compared to the size =
of the previous binary content - you might argue that if you have =
enough bandwidth for the binary content itself you shouldn't worry =
about some inefficienies in the 'aftermath' of this content.</FONT></P>

<P><FONT SIZE=3D2>However at least in a wireless context it is not just =
bandwidth which is a problem but the transmission time for the messages =
- this may not be important for a message containing some content (the =
user may expect this to take some time to arrive), but it is important =
for session establishement messaging.</FONT></P>

<P><FONT SIZE=3D2>Finally, I think different algorithms have a =
different 'run in' time before they become really efficient (e.g. =
LZW-based algorithms will need to see a good few messages before they =
build up a good codebook). If you tailor your compression algorithm to =
SIP/SDP-type messaging then you can achieve high compression much =
faster. For example it would be really useful if I knew that the second =
occurance of a given SIP URI could always be replaced by a reference in =
full. But you need to know what 'SIP/SDP-type messaging' looks like to =
get this right.</FONT></P>

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

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Adam Roach [<A =
HREF=3D"mailto:adam@dynamicsoft.com">mailto:adam@dynamicsoft.com</A>]</F=
ONT>
<BR><FONT SIZE=3D2>&gt; Sent: 10 March 2003 23:19</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Markus.Isomaki@nokia.com'; Watson, Mark =
[MOP:EP10:EXCH];</FONT>
<BR><FONT SIZE=3D2>&gt; sipping@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sipping] SIGCOMP and large binary =
content SIP messages</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Before this spins out of control...</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 1. SigComp works just fine with binary content. =
The only impact</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; that the assumption cited =
from 3322 has had on SigComp is</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; that the first byte of a =
message is examined to determine</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; whether it is compressed. =
Since binary content in a SIP message</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; will still have a text =
header, this causes no problems.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 2. The TCP delimiter (0xFFFF) in SigComp is =
applied to the stream</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; *after* it is compressed, not =
before. It has no harmful</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; interactions with the content =
being sent. (And, yes, it is</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; escaped if it is discovered =
in the compressed stream).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 3. When the underlying binary data *can* be =
compressed, the efficiency</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; of such compression is =
detemined by the compressor that the sender</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; uses. At the SigComp interop =
event two weeks ago, everyone I tested</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; with was using =
general-purpose compressors that would have </FONT>
<BR><FONT SIZE=3D2>&gt; generally</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; done a decent job with such =
binary data.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 4. When the underlying binary data *cannot* be =
compressed much further</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; (e.g. mp3s, jpgs, etc), then =
it's pretty much a forgone conclusion</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; that the compressor won't do =
a good job compressing it. We can't</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; solve the problem of =
compressing uncompressible data.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark: an informational draft along the lines of =
what you propose</FONT>
<BR><FONT SIZE=3D2>&gt; sounds like it might provide some needed =
guidance. I would add</FONT>
<BR><FONT SIZE=3D2>&gt; to it the fact that compressors can decide to =
send a message</FONT>
<BR><FONT SIZE=3D2>&gt; uncompressed if they determine that it has a =
detrimental effect</FONT>
<BR><FONT SIZE=3D2>&gt; on the dynamic dictionary or actually grows in =
size. Further,</FONT>
<BR><FONT SIZE=3D2>&gt; it would be a rather straightforward excercise =
to design a</FONT>
<BR><FONT SIZE=3D2>&gt; compressor and complementary bytecodes that =
would compress the</FONT>
<BR><FONT SIZE=3D2>&gt; headers, and just pass through the =
uncompressible binary content</FONT>
<BR><FONT SIZE=3D2>&gt; untouched (solving both the dynamic dictonary =
problem and the</FONT>
<BR><FONT SIZE=3D2>&gt; growing message problem). Finally, I'll point =
out that any</FONT>
<BR><FONT SIZE=3D2>&gt; message in excess of 64 kb cannot be compressed =
with SigComp</FONT>
<BR><FONT SIZE=3D2>&gt; in any fashion, since RFC 3320 mandates a 64 kb =
output buffer</FONT>
<BR><FONT SIZE=3D2>&gt; size at the UDVM.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; /a</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Markus.Isomaki@nokia.com [<A =
HREF=3D"mailto:Markus.Isomaki@nokia.com">mailto:Markus.Isomaki@nokia.com=
</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, March 10, 2003 14:21</FONT>
<BR><FONT SIZE=3D2>&gt; To: mwatson@nortelnetworks.com; =
sipping@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sipping] SIGCOMP and large binary =
content SIP messages</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi Mark,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I think it will really be a big deficiency if =
SigComp can't </FONT>
<BR><FONT SIZE=3D2>&gt; handle somehow</FONT>
<BR><FONT SIZE=3D2>&gt; binary content in SIP messages. Presence (both =
PUBLISH and </FONT>
<BR><FONT SIZE=3D2>&gt; NOTIFY) is one</FONT>
<BR><FONT SIZE=3D2>&gt; thing that can potentially have binary =
attachments, and not </FONT>
<BR><FONT SIZE=3D2>&gt; all of them are</FONT>
<BR><FONT SIZE=3D2>&gt; going to be transported via content =
indirection. However, even more</FONT>
<BR><FONT SIZE=3D2>&gt; important case is SIP MESSAGE. Already today =
mobile phones </FONT>
<BR><FONT SIZE=3D2>&gt; transfer images</FONT>
<BR><FONT SIZE=3D2>&gt; of size ~50 kB using MMS, and I assume the same =
would happen </FONT>
<BR><FONT SIZE=3D2>&gt; if SIP were</FONT>
<BR><FONT SIZE=3D2>&gt; available. And again, not all of this would use =
HTTP and CI. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; In addition to the dynamic dictionary problem I =
believe that </FONT>
<BR><FONT SIZE=3D2>&gt; there is a</FONT>
<BR><FONT SIZE=3D2>&gt; problem with SIP/SigComp over TCP (which would =
be almost </FONT>
<BR><FONT SIZE=3D2>&gt; always the trasport</FONT>
<BR><FONT SIZE=3D2>&gt; if binary content is included). I've understood =
that SigComp </FONT>
<BR><FONT SIZE=3D2>&gt; assumes that</FONT>
<BR><FONT SIZE=3D2>&gt; some special non-ASCII character is used to =
indicate the </FONT>
<BR><FONT SIZE=3D2>&gt; start and end of a</FONT>
<BR><FONT SIZE=3D2>&gt; compressed message. Obviously this does not =
work if part of </FONT>
<BR><FONT SIZE=3D2>&gt; the message</FONT>
<BR><FONT SIZE=3D2>&gt; itself is non-ASCII. So is there even a bigger =
problem than just</FONT>
<BR><FONT SIZE=3D2>&gt; non-friendliness that needs to be fixed?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Markus</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: ext Mark Watson [<A =
HREF=3D"mailto:mwatson@nortelnetworks.com">mailto:mwatson@nortelnetworks=
.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 07 March, 2003 16:52</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'sipping@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Sipping] SIGCOMP and large binary =
content SIP messages</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; All, </FONT>
<BR><FONT SIZE=3D2>&gt; We have had a couple of short threads on SIMPLE =
considering </FONT>
<BR><FONT SIZE=3D2>&gt; the implications</FONT>
<BR><FONT SIZE=3D2>&gt; of including large binary content within SIP =
messages (using MIME) (by</FONT>
<BR><FONT SIZE=3D2>&gt; large, I mean anything more than several times =
the size of a </FONT>
<BR><FONT SIZE=3D2>&gt; normal INVITE</FONT>
<BR><FONT SIZE=3D2>&gt; and by binary, I mean arbitrary bytes, rather =
than text). An </FONT>
<BR><FONT SIZE=3D2>&gt; example would</FONT>
<BR><FONT SIZE=3D2>&gt; be a JPEG or audio file. It's been suggested =
that a user </FONT>
<BR><FONT SIZE=3D2>&gt; might include one</FONT>
<BR><FONT SIZE=3D2>&gt; of these as part of their presence =
information.</FONT>
<BR><FONT SIZE=3D2>&gt; On the face of it, it seems that this might =
have implications for the</FONT>
<BR><FONT SIZE=3D2>&gt; effectiveness of SIPCOMP, firstly because such =
data may not </FONT>
<BR><FONT SIZE=3D2>&gt; itself compress</FONT>
<BR><FONT SIZE=3D2>&gt; well (compared to SIP headers and SDP), and =
secondly because </FONT>
<BR><FONT SIZE=3D2>&gt; of the impact</FONT>
<BR><FONT SIZE=3D2>&gt; this might have on any dynamic =
dictionary.</FONT>
<BR><FONT SIZE=3D2>&gt; There may be ways to design SIGCOMP compressors =
which can </FONT>
<BR><FONT SIZE=3D2>&gt; cope with this,</FONT>
<BR><FONT SIZE=3D2>&gt; and if so it would be good to have some =
guidelines included </FONT>
<BR><FONT SIZE=3D2>&gt; in the SIGCOMP</FONT>
<BR><FONT SIZE=3D2>&gt; documentation. This would stop people from =
naively designing SIGCOMP</FONT>
<BR><FONT SIZE=3D2>&gt; compressors based on false assumptions about =
the nature of </FONT>
<BR><FONT SIZE=3D2>&gt; SIP messaging</FONT>
<BR><FONT SIZE=3D2>&gt; (for example SIGCOMP has to date made the =
assumption that SIP </FONT>
<BR><FONT SIZE=3D2>&gt; messages are</FONT>
<BR><FONT SIZE=3D2>&gt; ASCII encoded - RFC3322).</FONT>
<BR><FONT SIZE=3D2>&gt; So, before raising this in ROCH, perhaps we =
need to discuss what those</FONT>
<BR><FONT SIZE=3D2>&gt; assumptions about SIP messaging should be - =
i.e. to </FONT>
<BR><FONT SIZE=3D2>&gt; approximately define a</FONT>
<BR><FONT SIZE=3D2>&gt; class of SIP messages for which app. designers =
can expect </FONT>
<BR><FONT SIZE=3D2>&gt; SIGCOMP to perform</FONT>
<BR><FONT SIZE=3D2>&gt; well. Then if applications need to generate =
messages outside </FONT>
<BR><FONT SIZE=3D2>&gt; that class,</FONT>
<BR><FONT SIZE=3D2>&gt; they can choose between (i) potentially poor =
SIGCOMP </FONT>
<BR><FONT SIZE=3D2>&gt; performance (which may</FONT>
<BR><FONT SIZE=3D2>&gt; be acceptable in some cases) or (ii) using =
techniques like Content</FONT>
<BR><FONT SIZE=3D2>&gt; Indirection to return their messages into the =
'SIGCOMP </FONT>
<BR><FONT SIZE=3D2>&gt; friendly' class.</FONT>
<BR><FONT SIZE=3D2>&gt; I know large content in SIP messages has been =
discussed </FONT>
<BR><FONT SIZE=3D2>&gt; before in various</FONT>
<BR><FONT SIZE=3D2>&gt; contexts, but is there any chance we can come =
to a rough </FONT>
<BR><FONT SIZE=3D2>&gt; consensus on what a</FONT>
<BR><FONT SIZE=3D2>&gt; 'SIGCOMP-friendly' class of SIP messages should =
look like ?</FONT>
<BR><FONT SIZE=3D2>&gt; Regards, </FONT>
<BR><FONT SIZE=3D2>&gt; Mark Watson </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; From: Watson, Mark [MOP:EP10:EXCH] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 05 March 2003 10:33 </FONT>
<BR><FONT SIZE=3D2>&gt; To: 'mikko.lonnfors@nokia.com'; simple@ietf.org =
</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Simple] I-D </FONT>
<BR><FONT SIZE=3D2>&gt; =
ACTION:draft-lonnfors-simple-partial-notify-00.t</FONT>
<BR><FONT SIZE=3D2>&gt; xt </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mikko, All, </FONT>
<BR><FONT SIZE=3D2>&gt; The correct place to document such =
recommendations about </FONT>
<BR><FONT SIZE=3D2>&gt; SIGCOMP would be in</FONT>
<BR><FONT SIZE=3D2>&gt; some ROCH documentation, perhaps the SIGCOMP =
User Guide ? I </FONT>
<BR><FONT SIZE=3D2>&gt; notice that</FONT>
<BR><FONT SIZE=3D2>&gt; RFC3322 (Signalling Compression Requirements =
&amp; Assumptions) </FONT>
<BR><FONT SIZE=3D2>&gt; already assumes</FONT>
<BR><FONT SIZE=3D2>&gt; that the signalling messages are ASCII encoded, =
so if this is </FONT>
<BR><FONT SIZE=3D2>&gt; not the case I</FONT>
<BR><FONT SIZE=3D2>&gt; think it's fairly urgent to get some discussion =
going.</FONT>
<BR><FONT SIZE=3D2>&gt; Before we go to ROCH, though, we need to make =
some decision </FONT>
<BR><FONT SIZE=3D2>&gt; on what kind of</FONT>
<BR><FONT SIZE=3D2>&gt; content we see being commonly included in SIP =
messages - i.e. </FONT>
<BR><FONT SIZE=3D2>&gt; what does</FONT>
<BR><FONT SIZE=3D2>&gt; SIGCOMP have to deal with in addition to SIP =
Headers and SDP ??</FONT>
<BR><FONT SIZE=3D2>&gt; To my mind this is a discussion for SIPPING - =
does anyone </FONT>
<BR><FONT SIZE=3D2>&gt; object to moving</FONT>
<BR><FONT SIZE=3D2>&gt; this discussion there ? (Let's avoid creating a =
cross-posted thread if</FONT>
<BR><FONT SIZE=3D2>&gt; possible - they're always a nightmare).</FONT>
<BR><FONT SIZE=3D2>&gt; ...Mark </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: mikko.lonnfors@nokia.com [<A =
HREF=3D"mailto:mikko.lonnfors@nokia.com">mailto:mikko.lonnfors@nokia.com=
</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: 04 March 2003 10:03 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: Watson, Mark [MOP:EP10:EXCH]; =
simple@ietf.org </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: RE: [Simple] I-D </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
ACTION:draft-lonnfors-simple-partial-notify-00.txt </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Hi mark, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Inline inside &lt;ML&gt;: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; All, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I am not convinced by the discussion on =
SIGCOMP which has </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; been introduced into this draft (Section =
1.1). </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Firstly, is this even the correct place to =
describe these issues ?? </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Yes, you are right. To move discussion =
forward we needed to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; place text somewhere and in this case only =
place we could </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; place it was the partial notification =
draft. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; If we really expect to see large =
binary content in SIP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; messages, then we should document the =
impacts for SIGCOMP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; somewhere more general - not buried in a =
presence partial </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; notifications discussion. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Yes </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; If we do not expect such content, we =
should document that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; fact somewhere more general too. We need =
to make a decision </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; one way or the other because it has =
important implications </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; for the design of SIGCOMP compressors. =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; This is probably true. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Secondly, two of the solutions referred to =
involve the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; SIGCOMP layer having knowledge of the =
content type, which is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; a major architectural change. Presently, =
the SIGCOMP layer </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; does not parse SIP, MIME etc. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; We have been talking about this issue with =
SIGCOMP author Z. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Liu (as at least I not an expert in this =
are) and these were </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; mentioned as possible solutions for this =
problem. I am also </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; not convinced that these two solutions are =
the best ones and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; if other people feel same I am quite happy =
to drop them. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Thirdly, the last solution mentioned =
involves leaving </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 'binary' content uncompressed, but this =
does not necessarily </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; mean that this content will not mess up =
the dynamic </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; dictionary. The compression scheme would =
need to detect </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 'uncompressible' parts of the message and =
leave these out of </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the dictionary. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; As far as I know this should be quite easy =
thing to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; accomplish for a SIGCOMP implementation. =
Of course it should </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; be specified (recommended) somewhere what =
is appropriate </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; threshold value for data which should be =
considered </FONT>
<BR><FONT SIZE=3D2>&gt; 'uncompressible'. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; So, if we expect binary content in SIP, we =
should document </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the impacts in SIGCOMP somewhere in the =
sip/sipping WGs. We </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; should decide whether we expect SIGCOMP to =
cope with such </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; binary content in an efficient way (i.e. =
if we think the same </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; content will be sent multiple times) or =
whether we are happy </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; for SIGCOMP to leave such content =
uncompressed (i.e. if we </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; think the same content will generally only =
be sent once). </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Finally, I think we concluded in the last =
discussion on this </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that it was not appropriate to include =
in-line binary content </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; in the presence document itself due to =
encoding issues - </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; there is still some reference to this in =
the draft. Large </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; binary content would need to referenced =
from the presence </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; document, and we left it open whether this =
reference could be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to other MIME parts within the same SIP =
message. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Yes, this is our mistake. I also agree =
that large binary data </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; should not be in-line with other presence =
data. This will be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; fixed in next version </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;/ML&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Thanks for comments </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; - Mikko </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Regards, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Mark </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: Internet-Drafts@ietf.org [<A =
HREF=3D"mailto:Internet-Drafts@ietf.org">mailto:Internet-Drafts@ietf.org=
</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sent: 24 February 2003 11:45 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Cc: simple@ietf.org </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Subject: [Simple] I-D </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
ACTION:draft-lonnfors-simple-partial-notify-00.txt </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; A New Internet-Draft is available =
from the on-line </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Internet-Drafts directories. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
Partial Notification of Presence </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Information </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : J. Costa-Requena, E. =
Leppanen et al. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : </FONT>
<BR><FONT SIZE=3D2>&gt; draft-lonnfors-simple-partial-notify-00.txt =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 24 =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
: 2003-2-21 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; A Presence service implemented using =
SIMPLE has some </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; constraints for </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; delivering presence information to =
devices with low data </FONT>
<BR><FONT SIZE=3D2>&gt; processing </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; capabilities, small display, and =
limited battery power. Other </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; limitations can be caused by the =
interface between the </FONT>
<BR><FONT SIZE=3D2>&gt; terminal and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the network, i.e. over radio links =
with high latency and low </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; bandwidth. This memo presents a =
solution that aids in </FONT>
<BR><FONT SIZE=3D2>&gt; reducing the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; impact of those constrains and =
increasing efficiency, by </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; introducing </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; a new MIME-type =E6partial =
notifications=C6 and a Require header </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; extension =E6partial-notification=C6. =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; A URL for this Internet-Draft is: =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-lonnfors-simple-part" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-lonnfors-sim=
ple-part</A> </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ial-notify-00.txt </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; To remove yourself from the IETF =
Announcement list, send a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; message to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ietf-announce-request with the word =
unsubscribe in the body </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; of the message. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Internet-Drafts are also available by =
anonymous FTP. Login </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; with the username </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &quot;anonymous&quot; and a password =
of your e-mail address. After </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; logging in, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; type &quot;cd internet-drafts&quot; =
and then </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;get draft-lonnfors-simple-partial-notify-00.txt&quot;. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; A list of Internet-Drafts directories =
can be found in </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; <A =
HREF=3D"http://www.ietf.org/shadow.html" =
TARGET=3D"_blank">http://www.ietf.org/shadow.html</A> </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; or <A =
HREF=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" =
TARGET=3D"_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</A> </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Internet-Drafts can also be obtained =
by e-mail. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Send a message to: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
mailserv@ietf.org. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; In the body type: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;FILE </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
/internet-drafts/draft-lonnfors-simple-partial-notify-00.txt&quot;. =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; NOTE: The mail server at ietf.org can =
return the document in </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MIME-encoded form by using the &quot;mpack&quot; utility.&nbsp; To =
</FONT>
<BR><FONT SIZE=3D2>&gt; use this </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
feature, insert the command &quot;ENCODING mime&quot; before </FONT>
<BR><FONT SIZE=3D2>&gt; the &quot;FILE&quot; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
command.&nbsp; To decode the response(s), you will need </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &quot;munpack&quot; or </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a =
MIME-compliant mail reader.&nbsp; Different MIME-compliant </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; mail readers </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
exhibit different behavior, especially when dealing with </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;multipart&quot; MIME messages (i.e. documents which have </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; been split </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
up into multiple messages), so check your local </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; documentation on </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
how to manipulate these messages. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Below is the data which will enable a =
MIME compliant mail reader </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; implementation to automatically =
retrieve the ASCII version of the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Internet-Draft. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E7DB.D92CD6E6--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 12 04:24:24 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27057
	for <sipping-archive@odin.ietf.org>; Wed, 12 Mar 2003 04:24:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2C9cFI28562
	for sipping-archive@odin.ietf.org; Wed, 12 Mar 2003 04:38:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C9cFO28559
	for <sipping-web-archive@optimus.ietf.org>; Wed, 12 Mar 2003 04:38:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27038
	for <sipping-web-archive@ietf.org>; Wed, 12 Mar 2003 04:23:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C9bLO28242;
	Wed, 12 Mar 2003 04:37:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2C9avO27568
	for <sipping@optimus.ietf.org>; Wed, 12 Mar 2003 04:36:57 -0500
Received: from znsgs01r.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26980
	for <sipping@ietf.org>; Wed, 12 Mar 2003 04:22:33 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2C9OUH14091;
	Wed, 12 Mar 2003 09:24:30 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GR68GSFQ; Wed, 12 Mar 2003 09:24:29 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GR4V32JJ>; Wed, 12 Mar 2003 09:24:20 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7C8F@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
Cc: "'Peterson, Jon'" <jon.peterson@neustar.biz>, sipping
	 <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Wed, 12 Mar 2003 09:24:18 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E879.28344EDE"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E879.28344EDE
Content-Type: text/plain;
	charset="iso-8859-1"

Gonzalo,

Regarding the SDP direction attribute, this is indeed the solution which was
mooted some time ago, but it is not documented clearly. I think if this is
the proposed resolution of this problem, it does need to be clearly
described & the Early Media draft would be an appropriate place.Then it can
be included in the SIP/ISUP interworking work which is ongoing in ITU-T and
3GPP.

If I understand correctly, you are saying that a UAS SHOULD put the media
'on hold' by setting a=inactive if there is no Early Media. If the media
stream is not 'on hold' then the UAC should assume there is media and play
it. 

This is ok with me, but it does seem to place a new requirement on all
existing UAS's.

I am confused about your position stated at the end of your mail, though. We
are on the sipping list, so the question of what protocol element might be
used if this requirement is agreed is out of scope here. So, are you saying
that you do not find the requirement unreasonable ? Can we agree on that
before jumping into solutions ?

...Mark

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: 12 March 2003 07:11
> To: Ejzak, Richard P (Richard)
> Cc: 'Peterson, Jon'; Watson, Mark [MOP:EP10:EXCH]; sipping
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Richard,
> 
> just to be clear, I am not proposing to change the draft. I am just
> saying that using the SDP direction attribute seems to resolve Mark's
> concerns.
> 
> > My concern is to do media detection and tone insertion efficiently, 
> > correctly, and only when necessary.
> 
> I guess the crux of the issue is the part where you say "only when
> necessary"... it is clear that such an indication would save you
> performing media detection for 180 responses with the inband 
> media flag.
> 
> My position is, as I said in this thread before, that if people
> considered this as an important gain, I would not find it unreasonable
> to standardize an empty Alert-Info header field.
> 
> However, others have expressed concerns about that...
> 
> Gonzalo
> 
> "Ejzak, Richard P (Richard)" wrote:
> > 
> > Gonzalo,
> > Thanks for your attempt to find a way forward.  But I never 
> objected to media detection across the board.  It is 
> necessary, as you point out, to avoid clipping in certain 
> scenarios.  There was a scenario very similar to the one you 
> propose in an earlier version of the manyfolks draft that was 
> removed after I raised an objection last year, because it 
> introduced a potential for media clipping.
> > 
> > My concern is to do media detection and tone insertion 
> efficiently, correctly, and only when necessary.  As I stated 
> earlier, there is no reason to change how things work for 
> native SIP UAs.  Your proposal would actually have the most 
> impact on native SIP UAs (typically without in-band media)!  
> But when a UAS PSTN gateway is in the mix with in-band call 
> progress media, we know there is no need for either media 
> detection or tone insertion, and, in fact, there's a good 
> chance they would muck things up.
> > 
> > Your proposal unfortunately appears to cause more harm than 
> good (by re-introducing potential for clipping and impacting 
> SIP UAs without in-band media).  We need some kind of 
> indication associated with the 180 (not SDP) that in-band 
> call progress information is available.
> > 
> > I am mightily confused as to why this is such a challenging 
> problem.  I have proposed at least two backwards compatible 
> methods for signaling this information.
> > 
> > Regards,
> > Richard Ejzak
> > Lucent Technologies
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Gonzalo,</FONT>
</P>

<P><FONT SIZE=3D2>Regarding the SDP direction attribute, this is indeed =
the solution which was mooted some time ago, but it is not documented =
clearly. I think if this is the proposed resolution of this problem, it =
does need to be clearly described &amp; the Early Media draft would be =
an appropriate place.Then it can be included in the SIP/ISUP =
interworking work which is ongoing in ITU-T and 3GPP.</FONT></P>

<P><FONT SIZE=3D2>If I understand correctly, you are saying that a UAS =
SHOULD put the media 'on hold' by setting a=3Dinactive if there is no =
Early Media. If the media stream is not 'on hold' then the UAC should =
assume there is media and play it. </FONT></P>

<P><FONT SIZE=3D2>This is ok with me, but it does seem to place a new =
requirement on all existing UAS's.</FONT>
</P>

<P><FONT SIZE=3D2>I am confused about your position stated at the end =
of your mail, though. We are on the sipping list, so the question of =
what protocol element might be used if this requirement is agreed is =
out of scope here. So, are you saying that you do not find the =
requirement unreasonable ? Can we agree on that before jumping into =
solutions ?</FONT></P>

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

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 12 March 2003 07:11</FONT>
<BR><FONT SIZE=3D2>&gt; To: Ejzak, Richard P (Richard)</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'Peterson, Jon'; Watson, Mark =
[MOP:EP10:EXCH]; sipping</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Richard,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; just to be clear, I am not proposing to change =
the draft. I am just</FONT>
<BR><FONT SIZE=3D2>&gt; saying that using the SDP direction attribute =
seems to resolve Mark's</FONT>
<BR><FONT SIZE=3D2>&gt; concerns.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; My concern is to do media detection and =
tone insertion efficiently, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; correctly, and only when necessary.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I guess the crux of the issue is the part where =
you say &quot;only when</FONT>
<BR><FONT SIZE=3D2>&gt; necessary&quot;... it is clear that such an =
indication would save you</FONT>
<BR><FONT SIZE=3D2>&gt; performing media detection for 180 responses =
with the inband </FONT>
<BR><FONT SIZE=3D2>&gt; media flag.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; My position is, as I said in this thread =
before, that if people</FONT>
<BR><FONT SIZE=3D2>&gt; considered this as an important gain, I would =
not find it unreasonable</FONT>
<BR><FONT SIZE=3D2>&gt; to standardize an empty Alert-Info header =
field.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; However, others have expressed concerns about =
that...</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;Ejzak, Richard P (Richard)&quot; =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Gonzalo,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Thanks for your attempt to find a way =
forward.&nbsp; But I never </FONT>
<BR><FONT SIZE=3D2>&gt; objected to media detection across the =
board.&nbsp; It is </FONT>
<BR><FONT SIZE=3D2>&gt; necessary, as you point out, to avoid clipping =
in certain </FONT>
<BR><FONT SIZE=3D2>&gt; scenarios.&nbsp; There was a scenario very =
similar to the one you </FONT>
<BR><FONT SIZE=3D2>&gt; propose in an earlier version of the manyfolks =
draft that was </FONT>
<BR><FONT SIZE=3D2>&gt; removed after I raised an objection last year, =
because it </FONT>
<BR><FONT SIZE=3D2>&gt; introduced a potential for media =
clipping.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; My concern is to do media detection and =
tone insertion </FONT>
<BR><FONT SIZE=3D2>&gt; efficiently, correctly, and only when =
necessary.&nbsp; As I stated </FONT>
<BR><FONT SIZE=3D2>&gt; earlier, there is no reason to change how =
things work for </FONT>
<BR><FONT SIZE=3D2>&gt; native SIP UAs.&nbsp; Your proposal would =
actually have the most </FONT>
<BR><FONT SIZE=3D2>&gt; impact on native SIP UAs (typically without =
in-band media)!&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; But when a UAS PSTN gateway is in the mix with =
in-band call </FONT>
<BR><FONT SIZE=3D2>&gt; progress media, we know there is no need for =
either media </FONT>
<BR><FONT SIZE=3D2>&gt; detection or tone insertion, and, in fact, =
there's a good </FONT>
<BR><FONT SIZE=3D2>&gt; chance they would muck things up.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Your proposal unfortunately appears to =
cause more harm than </FONT>
<BR><FONT SIZE=3D2>&gt; good (by re-introducing potential for clipping =
and impacting </FONT>
<BR><FONT SIZE=3D2>&gt; SIP UAs without in-band media).&nbsp; We need =
some kind of </FONT>
<BR><FONT SIZE=3D2>&gt; indication associated with the 180 (not SDP) =
that in-band </FONT>
<BR><FONT SIZE=3D2>&gt; call progress information is available.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I am mightily confused as to why this is =
such a challenging </FONT>
<BR><FONT SIZE=3D2>&gt; problem.&nbsp; I have proposed at least two =
backwards compatible </FONT>
<BR><FONT SIZE=3D2>&gt; methods for signaling this information.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Regards,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Richard Ejzak</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Lucent Technologies</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E879.28344EDE--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 12 11:26:11 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10168
	for <sipping-archive@odin.ietf.org>; Wed, 12 Mar 2003 11:26:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2CGeCG25586
	for sipping-archive@odin.ietf.org; Wed, 12 Mar 2003 11:40:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2CGeBO25583
	for <sipping-web-archive@optimus.ietf.org>; Wed, 12 Mar 2003 11:40:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10158
	for <sipping-web-archive@ietf.org>; Wed, 12 Mar 2003 11:25:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2CGdNO25524;
	Wed, 12 Mar 2003 11:39:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2CGcBO25482
	for <sipping@optimus.ietf.org>; Wed, 12 Mar 2003 11:38:11 -0500
Received: from mgw-dax2.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10109
	for <sipping@ietf.org>; Wed, 12 Mar 2003 11:23:38 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2CGPk822090
	for <sipping@ietf.org>; Wed, 12 Mar 2003 10:25:46 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60ee2c6034ac12f255154@davir02nok.americas.nokia.com>;
 Wed, 12 Mar 2003 10:25:46 -0600
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 12 Mar 2003 10:25:44 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Wed, 12 Mar 2003 10:25:44 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A819@daebe005.americas.nokia.com>
Thread-Topic: [Sipping] SIGCOMP and large binary content SIP messages
Thread-Index: AcLoRAe4CMxO1nt3SIyWmRswoP8p6gAasGTw
To: <adam@dynamicsoft.com>, <Markus.Isomaki@nokia.com>,
        <mwatson@nortelnetworks.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 12 Mar 2003 16:25:44.0820 (UTC) FILETIME=[08251340:01C2E8B4]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2CGcBO25485
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Yes, that is also what I had in mind for SIP. But my point is that
a SigComp receiver now needs to have some knowledge about application
message format and do parsing to determine the end of an uncompressed
message. This is something new (or at least unspecified) in RFC 3320 
and needs to be spelled out in a new (standard track) RFC. The document
will be short, but I think it's needed for interoperability.

I'll write up an I-D and submit it after IETF 56. But I'd like to know 
if folks in SIPPING think it should be done here or in ROHC.

Zhigang

> -----Original Message-----
> From: ext Adam Roach [mailto:adam@dynamicsoft.com]
> Sent: March 11, 2003 9:03 PM
> To: Liu Zhigang.C (NRC/Dallas); Adam Roach; Isomaki Markus
> (NRC/Helsinki); mwatson@nortelnetworks.com; sipping@ietf.org
> Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
> 
> 
> > -----Original Message-----
> > From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > 
> > Having binary content in SIP messages may have two impacts on 
> > SigComp: 
> > 
> > a) multiplexing of uncompressed messages with SigComp 
> messages on the
> > same port.
> ...
> > For a), it is only an issue for SigComp/TCP, not 
> SigComp/UDP (where one
> > SigComp message maps to one UDP packet). Adam's point 1 and 
> 2 are related
> > to this. As to point 1, I think the SigComp receiver still 
> needs to know 
> > (somehow) the end of an uncompressed message, or at least 
> the end of the 
> > binary part of each SIP messages. Otherwise, a bit pattern 11111 in 
> > the binary part will be mistaken by SigComp as the 
> beginning of a SigComp
> > message. As to point 2, I would add that the delimiter 
> 0xFFFF can appear
> > at the both the beginning and the end of a SigComp message. So, the
> > receiver needs to have the same parsing logic just mentioned for bit
> pattern
> > 11111.
> 
> This isn't any more of an issue than it is without SigComp. SIP
> messages provide their own framing, and SigComp messages do the
> same. They can be trivially mixed on the same stream:
> 
> 1. Peek at the first byte waiting in the stream.
> 
> 2. If it is 0xf8 or higher, the next message in the stream is
>    a SigComp message. The message continues until a 0xFFFF is
>    encountered in the stream.
> 
> 3. Otherwise, the next message in the stream is a SIP message.
>    Read the stream until a CR/LF/CR/LF is encountered. Parse
>    the headers, and then read the number of bytes specified
>    in the "Content-Length" header.
> 
> 4. Return to step 1.
> 
> /a
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 12 15:58:47 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22122
	for <sipping-archive@odin.ietf.org>; Wed, 12 Mar 2003 15:58:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2CLCsT14624
	for sipping-archive@odin.ietf.org; Wed, 12 Mar 2003 16:12:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2CLCsO14621
	for <sipping-web-archive@optimus.ietf.org>; Wed, 12 Mar 2003 16:12:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22039
	for <sipping-web-archive@ietf.org>; Wed, 12 Mar 2003 15:58:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2CLC9O14589;
	Wed, 12 Mar 2003 16:12:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2CLBRO14507
	for <sipping@optimus.ietf.org>; Wed, 12 Mar 2003 16:11:27 -0500
Received: from mail.aastra.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21938
	for <sipping@ietf.org>; Wed, 12 Mar 2003 15:56:49 -0500 (EST)
Received: by mail.aastra.com with Internet Mail Service (5.5.2653.19)
	id <1XVB0HCD>; Wed, 12 Mar 2003 15:48:21 -0500
Message-ID: <F924CEFBBF62D611A0C600D0B76ED037157981@cvxmail.ana.aastra.com>
From: Sumit Garg <sgarg@aastra.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Wed, 12 Mar 2003 15:48:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C2E8D8.B30897E0"
Subject: [Sipping] RFC 3398: REL cause
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_000_01C2E8D8.B30897E0
Content-Type: text/plain;
	charset="iso-8859-1"

Hi all,

According to the rfc 3398(SIP-ISUP mapping, section 7.1.3 and 7.2.2),for a
net to Phone call, when ACM timeout timer
 (T7- 20 - 30 s) expires, the ISUP leg  REL cause should be 102 (protocol
error, recovery on timer expiry) and corresponding SIP response should be
504 Server Timeout.
However, if one goes by Q.764 and table 1 of Q.850 the correct REL cause for
ISUP would be 31(normal unspecified)
and for the SIP leg it would then correspond to  480 (Temporarily
Unavailable). Apparently 102 is used mostly for
SUS-RES.

What should be the values used?


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Sumit Garg 
Aastra Telecom US
8 Federal Street 
Billerica, MA 01821 
978-436-4244
email: <<mailto:sgarg@aastra.com>> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 



------_=_NextPart_000_01C2E8D8.B30897E0
Content-Type: application/octet-stream;
	name="Sumit Garg.vcf"
Content-Disposition: attachment;
	filename="Sumit Garg.vcf"

BEGIN:VCARD
VERSION:2.1
N:Garg;Sumit
FN:Sumit Garg
ORG:Aastra Network Access
NOTE:Aastra CVX
TEL;WORK;VOICE:978-436-4244
ADR;WORK:;Boston;8 Federal Street;Billerica;MA;1821;USA
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Boston=0D=0A8 Federal Street=0D=0ABillerica, MA 1821=0D=0AUSA
EMAIL;PREF;INTERNET:sgarg@aastra.com
REV:20021122T160021Z
END:VCARD

------_=_NextPart_000_01C2E8D8.B30897E0
Content-Type: application/octet-stream;
	name="Sumit Garg.vcf"
Content-Disposition: attachment;
	filename="Sumit Garg.vcf"

BEGIN:VCARD
VERSION:2.1
N:Garg;Sumit
FN:Sumit Garg
ORG:Aastra Network Access
NOTE:Aastra CVX
TEL;WORK;VOICE:978-436-4244
ADR;WORK:;Boston;8 Federal Street;Billerica;MA;1821;USA
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Boston=0D=0A8 Federal Street=0D=0ABillerica, MA 1821=0D=0AUSA
EMAIL;PREF;INTERNET:sgarg@aastra.com
REV:20021122T160021Z
END:VCARD

------_=_NextPart_000_01C2E8D8.B30897E0--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 12 18:55:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00589
	for <sipping-archive@odin.ietf.org>; Wed, 12 Mar 2003 18:55:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2D09pT28632
	for sipping-archive@odin.ietf.org; Wed, 12 Mar 2003 19:09:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D09pO28629
	for <sipping-web-archive@optimus.ietf.org>; Wed, 12 Mar 2003 19:09:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00579
	for <sipping-web-archive@ietf.org>; Wed, 12 Mar 2003 18:55:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D08hO28559;
	Wed, 12 Mar 2003 19:08:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D07ZO28389
	for <sipping@optimus.ietf.org>; Wed, 12 Mar 2003 19:07:35 -0500
Received: from zrc2s0jx.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00514
	for <sipping@ietf.org>; Wed, 12 Mar 2003 18:52:51 -0500 (EST)
Received: from zsc3c028.us.nortel.com (zsc3c028.us.nortel.com [47.81.138.28])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2CNsqg20036;
	Wed, 12 Mar 2003 17:54:52 -0600 (CST)
Received: by zsc3c028.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1LW2WY6M>; Wed, 12 Mar 2003 15:54:51 -0800
Message-ID: <2F1FC1DEA077D5119FAD00508BCFD6D20728CCD6@zsc3c030.us.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "Mark Watson" <mwatson@nortelnetworks.com>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Wed, 12 Mar 2003 15:54:52 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E8F2.C610FF0C"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E8F2.C610FF0C
Content-Type: text/plain

It seems to me that Mark and Richard's requirement is not going away.

Why don't we just send a 180 with an SDP and a new header field
"No-Alert-Info"?

Alternatively we could change the syntax of Alert-Info to:

	Alert-Info = "Alert-Info" HCOLON ( alert-param *(COMMA alert-param)
) / "None"

So we'd have in 180 with SDP, an "Alert-Info: None" header field. "None"
would really
mean no alerting should be provided (only in-band early media only).

In my opinion both approaches would be consistent with 183 (which can not
have Alert-Info).
I don't have any preference one way or another.

-----Original Message-----
From: Watson, Mark [MOP:EP10:EXCH] 
Sent: Tuesday, March 11, 2003 09:23
To: 'Peterson, Jon'
Cc: 'sipping@ietf.org'
Subject: RE: [Sipping] New version of the early media draft


Well, yes, if you change the axioms you will get a different conclusion.

The Alerting state in ISUP is certainly well-defined. It certainly includes
the possibility of in-band media and does not make any assumptions about
what that media is (i.e. does not assume that it is 'ringtone'). It is not
'misleading' for ISUP to signal 'subscriber free' and to include in-band
media which is other than 'ringtone'.

Is the SIP state occasioned by 180 Ringing equivalent to 'Alerting' in ISUP
?? 

Now, if you like, you can (re)define the SIP 180 Ringing state so that it
differs from the ISUP Alerting state in respect of support for in-band
media. Let's say that 180 Ringing does not support in-band media - which
seems to be where Jon is going below. Now we have an interesting choice at
PSTN gateways in terms of deciding whether to send 180 or not. We could
determine somehow whether the in-band media was in fact 'ringtone' or not
and use this to decide - but perhaps that is not so realistic. Or we could
send 183 whenever we have in-band media (i.e. almost all the time). Ok, so
this will work, but I have discarded the indication that the subscriber is
in fact free. This is useful information at the UAC for several reasons:
(i) is assists in determining what to do with multiple provisional responses
received due to forking
(ii) I can use it to drive a visual or other indication of call state

What is so wrong about wanting to carry this useful information to the UAC
??

...Mark
-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: 10 March 2003 20:44
To: Watson, Mark [MOP:EP10:EXCH]
Cc: 'sipping@ietf.org'
Subject: RE: [Sipping] New version of the early media draft


Behind this all is probably an argument about what the 'alerting' state in
SIP really means, especially contrasted with 'queuing' and so on. Is call
waiting actually best expressed in the PSTN by ACM with 'subscriber free'?
Is it best expressed in SIP by 180 (or should it be 182)? Whether or not the
PSTN signals 'subscriber free' in ACM for call waiting, that doesn't mean
that the SIP 180 alerting state is co-extensive with arbitrary in-band
status information. The problem is that SIP does not define its states at
this level of granularity, so the evidence for either position would be
indirect at best. 183 expresses that the call is in some provisional state,
that it hasn't yet been rejected as far as SIP knows, and so on - at the
very least, it's sent when other 18x's aren't appropriate for some reason.

SIP gains significant benefits from not having to reserve a circuit and
transmit media in the backwards direction in order to communicate that a
telephone is ringing. Again, if ISUP is misleading about the condition that
prevails, I'm not sure that admits of any repair in SIPPING. SIP does
support response codes tailored for queuing situations, but if the PSTN
can't tell us out-of-band that queuing is taking place, we can't map to
them.

Jon Peterson
NeuStar, Inc.
-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Monday, March 10, 2003 1:15 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


Jon,

If I use 183 then I lose the functional (out of band) indication that the
call is now in the Alerting state. So then, for example, a more advanced SIP
client may not provide the correct visual indication to the use ('ringing'
icon, or whatever).

We are talking about cases where the call state IS known to be 'Alerting',
so I think we must surely use 180, not 183. But there are useful in-band
tones AS WELL. In general a gateway would not know whether the in-band
information was boring ringtone, or something more interesting.

...Mark
-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: 07 March 2003 18:03
To: Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P (Richard)'; 'Gonzalo
Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft



I'm not sure I missed that point, exactly. I said that if the gateway knows
that the early media is just ringtone, it should send a 180. You're just
citing another case below in which the early media is not ringtone. I can't
see how this contradicts what I said. If there's some other in-band status
information available, the gateway should be using 183.

Jon Peterson
NeuStar, Inc.
-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Friday, March 07, 2003 1:17 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


Jon, 
You have missed one very important point which is that in-band media during
alerting is not necessarily 'just ringtone'. It is quite common for the call
to be in the 'Alerting' state (and for this to be know to a SIP to ISUP
gateway), but for the in-band media to contain some useful information other
than 'just ringtone'.
For example, in the UK at least, if the called party has Call Waiting, then
the call of course goes straight in to the Alerting state, but the caller
will here a message along the lines 'Please wait while we try to connect
your call - the person you are calling knows you are waiting'.
A second example would be when the call terminates on a queueing system, and
the message played gives the caller some idea of how long they will need to
wait.
I absolutely agree that if the in-band media was 'just ringtone' there would
be no point. In particular I don't see any need to support the PSTN
'feeture' in which you always hear the ringtone of the destination country
(IMO this is a bug, not a feature!).
So, let's recognise that there are cases where *both* out-of-band and
in-band status indications are present. My view is that out-of-band
indications should always be propogated if available - so for the scenario
in question we MUST use 180, not 183. Now we need to indicate that in-band
status is also available - is this really so hard ????
...Mark 
> -----Original Message----- 
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz] 
> Sent: 07 March 2003 00:09 
> To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo' 
> Cc: Watson, Mark [MOP:EP10:EXCH]; sipping 
> Subject: RE: [Sipping] New version of the early media draft 
> 
> 
> 
> Everything below is familiar ground, and I don't want to 
> start rehearsing 
> these same arguments again. SIP has made a number of design 
> decisions that 
> predispose it towards out-of-band status information. Sending 
> in-band status 
> information in SIP is harmful - period. In-band media should 
> be sent only 
> when the gateway does not know the status of the call, and thus cannot 
> communicate it out-of-band. Below, you basically argue that 
> in cases where 
> the gateway does not know the status of the call, it has to send early 
> media. I agree. I said that in cases in which the gateway 
> knows that the 
> early media is just ringtone, it should send 180. Clearly, if 
> there's some 
> in-band transition in call state from ringtone to some other 
> audible call 
> progress information, and the gateway isn't made aware of it, then the 
> gateway doesn't know the state of the call. Perhaps we might draw the 
> conclusion from your example that out-of-band call status 
> indicators are 
> inherently unreliable, then - and surmise that it is 
> impossible for the 
> gateway to know the state of the call. Or perhaps the 
> likelihood of this 
> condition arising is sufficiently remote, the consequences of 
> sending early 
> media sufficiently troublesome, that we might decide the 
> in-band information 
> in these cases is not 'essential' enough to worry over. But I 
> firmly believe 
> we should leave this to the conscience of the individual gateway 
> implementer. I don't think the early media draft needs to draw that 
> conclusion. 
> 
> Mr. Camarillo's draft already maintains a very delicate 
> balance of behavior 
> to accommodate SIP's needs, and I haven't heard anything in 
> this yet that 
> should alter it. 
> 
> Jon Peterson 
> NeuStar, Inc. 
> 
> > -----Original Message----- 
> > From: Ejzak, Richard P (Richard) [mailto:ejzak@lucent.com] 
> > Sent: Thursday, March 06, 2003 2:40 PM 
> > To: 'Peterson, Jon'; 'Gonzalo Camarillo' 
> > Cc: Mark Watson; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > Jon, 
> > I must disagree with your blanket recommendation that the 
> > gateway not sent in-band ringing media.  This may be possible 
> > in some cases - and nothing we have suggested would prevent a 
> > gateway from using out-of-band indications.  But ringing is 
> > not the only in-band call progress information you may 
> > receive while trying to establish a call from SIP to ISUP.  
> > The transition from alerting to other forms of in-band call 
> > progress information is not guaranteed to be clearly signaled 
> > by ISUP within an ACM or CPG (since every switch in the 
> > network can safely assume in-band call progress after a 
> > certain point in the call), and it is essential that this 
> > subsequent information (when it exists) be presented to the 
> > UAC/user.  And the notion of having the gateway intelligently 
> > filter what it thinks is ringing and detect a transition to 
> > other forms of call progress is not acceptable. 
> > 
> > Regards, 
> > Richard Ejzak 
> > Lucent Technologies 
> > 
> > 
> > 
> > -----Original Message----- 
> > From: Peterson, Jon [mailto:jon.peterson@neustar.biz] 
> > Sent: Thursday, March 06, 2003 4:06 PM 
> > To: 'Gonzalo Camarillo' 
> > Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > 
> > Well, 
> > 
> > > -----Original Message----- 
> > > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se] 
> > [snip] 
> > > 
> > > The scenario he is after is as follows; a gateway *knows* 
> > that the user 
> > > is being alerted and also *knows* that it will be sending in-band 
> > > ringing. 
> > > 
> > 
> > If the gateway knows that it will be sending in-band ringing, 
> > my position is 
> > that the gateway shouldn't be sending that media. It's just 
> > ring tone. The 
> > UAC can generate that itself. Let's not waste the bandwidth 
> > sending ringing, 
> > especially in forking cases, especially because the UAC 
> might not even 
> > render this provisional media (if it's a PC UAC, for example). 
> > 
> > If media arrives at the UAC, it should override local 
> > ringtone, agreed. And 
> > I have no problem with the idea that a UAC would delay local 
> > ringtone for a 
> > short interval in order to see if any media is coming, even 
> > when 180 is 
> > received. But we should not encourage gateways to send 
> ringing media. 
> > 
> > Jon Peterson 
> > NeuStar, Inc. 
> > 
> 

------_=_NextPart_001_01C2E8F2.C610FF0C
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>It seems to me that Mark and Richard's requirement is =
not going away.</FONT>
</P>

<P><FONT SIZE=3D2>Why don't we just send a 180 with an SDP and a new =
header field &quot;No-Alert-Info&quot;?</FONT>
</P>

<P><FONT SIZE=3D2>Alternatively we could change the syntax of =
Alert-Info to:</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Alert-Info =
=3D &quot;Alert-Info&quot; HCOLON ( alert-param *(COMMA alert-param) ) =
/ &quot;None&quot;</FONT>
</P>

<P><FONT SIZE=3D2>So we'd have in 180 with SDP, an &quot;Alert-Info: =
None&quot; header field. &quot;None&quot; would really</FONT>
<BR><FONT SIZE=3D2>mean no alerting should be provided (only in-band =
early media only).</FONT>
</P>

<P><FONT SIZE=3D2>In my opinion both approaches would be consistent =
with 183 (which can not have Alert-Info).</FONT>
<BR><FONT SIZE=3D2>I don't have any preference one way or =
another.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Watson, Mark [MOP:EP10:EXCH] </FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, March 11, 2003 09:23</FONT>
<BR><FONT SIZE=3D2>To: 'Peterson, Jon'</FONT>
<BR><FONT SIZE=3D2>Cc: 'sipping@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Sipping] New version of the early =
media draft</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Well, yes, if you change the axioms you will get a =
different conclusion.</FONT>
</P>

<P><FONT SIZE=3D2>The Alerting state in ISUP is certainly well-defined. =
It certainly includes the possibility of in-band media and does not =
make any assumptions about what that media is (i.e. does not assume =
that it is 'ringtone'). It is not 'misleading' for ISUP to signal =
'subscriber free' and to include in-band media which is other than =
'ringtone'.</FONT></P>

<P><FONT SIZE=3D2>Is the SIP state occasioned by 180 Ringing equivalent =
to 'Alerting' in ISUP ?? </FONT>
</P>

<P><FONT SIZE=3D2>Now, if you like, you can (re)define the SIP 180 =
Ringing state so that it differs from the ISUP Alerting state in =
respect of support for in-band media. Let's say that 180 Ringing does =
not support in-band media - which seems to be where Jon is going below. =
Now we have an interesting choice at PSTN gateways in terms of deciding =
whether to send 180 or not. We could determine somehow whether the =
in-band media was in fact 'ringtone' or not and use this to decide - =
but perhaps that is not so realistic. Or we could send 183 whenever we =
have in-band media (i.e. almost all the time). Ok, so this will work, =
but I have discarded the indication that the subscriber is in fact =
free. This is useful information at the UAC for several =
reasons:</FONT></P>

<P><FONT SIZE=3D2>(i) is assists in determining what to do with =
multiple provisional responses received due to forking</FONT>
<BR><FONT SIZE=3D2>(ii) I can use it to drive a visual or other =
indication of call state</FONT>
</P>

<P><FONT SIZE=3D2>What is so wrong about wanting to carry this useful =
information to the UAC ??</FONT>
</P>

<P><FONT SIZE=3D2>...Mark</FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Peterson, Jon [<A =
HREF=3D"mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz=
</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: 10 March 2003 20:44</FONT>
<BR><FONT SIZE=3D2>To: Watson, Mark [MOP:EP10:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: 'sipping@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Sipping] New version of the early =
media draft</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Behind this all is probably an argument about what =
the 'alerting' state in SIP really means, especially contrasted with =
'queuing' and so on. Is call waiting actually best expressed in the =
PSTN by ACM with 'subscriber free'? Is it best expressed in SIP by 180 =
(or should it be 182)? Whether or not the PSTN signals 'subscriber =
free' in ACM for call waiting, that doesn't mean that the SIP 180 =
alerting state is co-extensive with arbitrary in-band status =
information. The problem is that SIP does not define its states at this =
level of granularity, so the evidence for either position would be =
indirect at best. 183 expresses that the call is in some provisional =
state, that it hasn't yet been rejected as far as SIP knows, and so on =
- at the very least, it's sent when other 18x's aren't appropriate for =
some reason.</FONT></P>

<P><FONT SIZE=3D2>SIP gains significant benefits from not having to =
reserve a circuit and transmit media in the backwards direction in =
order to communicate that a telephone is ringing. Again, if ISUP is =
misleading about the condition that prevails, I'm not sure that admits =
of any repair in SIPPING. SIP does support response codes tailored for =
queuing situations, but if the PSTN can't tell us out-of-band that =
queuing is taking place, we can't map to them.</FONT></P>

<P><FONT SIZE=3D2>Jon Peterson</FONT>
<BR><FONT SIZE=3D2>NeuStar, Inc.</FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Mark Watson [<A =
HREF=3D"mailto:mwatson@nortelnetworks.com">mailto:mwatson@nortelnetworks=
.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, March 10, 2003 1:15 AM</FONT>
<BR><FONT SIZE=3D2>To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; =
'Gonzalo Camarillo'</FONT>
<BR><FONT SIZE=3D2>Cc: sipping</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Sipping] New version of the early =
media draft</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Jon,</FONT>
</P>

<P><FONT SIZE=3D2>If I use 183 then I lose the functional (out of band) =
indication that the call is now in the Alerting state. So then, for =
example, a more advanced SIP client may not provide the correct visual =
indication to the use ('ringing' icon, or whatever).</FONT></P>

<P><FONT SIZE=3D2>We are talking about cases where the call state IS =
known to be 'Alerting', so I think we must surely use 180, not 183. But =
there are useful in-band tones AS WELL. In general a gateway would not =
know whether the in-band information was boring ringtone, or something =
more interesting.</FONT></P>

<P><FONT SIZE=3D2>...Mark</FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Peterson, Jon [<A =
HREF=3D"mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz=
</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: 07 March 2003 18:03</FONT>
<BR><FONT SIZE=3D2>To: Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P =
(Richard)'; 'Gonzalo Camarillo'</FONT>
<BR><FONT SIZE=3D2>Cc: sipping</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Sipping] New version of the early =
media draft</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>I'm not sure I missed that point, exactly. I said =
that if the gateway knows that the early media is just ringtone, it =
should send a 180. You're just citing another case below in which the =
early media is not ringtone. I can't see how this contradicts what I =
said. If there's some other in-band status information available, the =
gateway should be using 183.</FONT></P>

<P><FONT SIZE=3D2>Jon Peterson</FONT>
<BR><FONT SIZE=3D2>NeuStar, Inc.</FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Mark Watson [<A =
HREF=3D"mailto:mwatson@nortelnetworks.com">mailto:mwatson@nortelnetworks=
.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, March 07, 2003 1:17 AM</FONT>
<BR><FONT SIZE=3D2>To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; =
'Gonzalo Camarillo'</FONT>
<BR><FONT SIZE=3D2>Cc: sipping</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Sipping] New version of the early =
media draft</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Jon, </FONT>
<BR><FONT SIZE=3D2>You have missed one very important point which is =
that in-band media during alerting is not necessarily 'just ringtone'. =
It is quite common for the call to be in the 'Alerting' state (and for =
this to be know to a SIP to ISUP gateway), but for the in-band media to =
contain some useful information other than 'just ringtone'.</FONT></P>

<P><FONT SIZE=3D2>For example, in the UK at least, if the called party =
has Call Waiting, then the call of course goes straight in to the =
Alerting state, but the caller will here a message along the lines =
'Please wait while we try to connect your call - the person you are =
calling knows you are waiting'.</FONT></P>

<P><FONT SIZE=3D2>A second example would be when the call terminates on =
a queueing system, and the message played gives the caller some idea of =
how long they will need to wait.</FONT></P>

<P><FONT SIZE=3D2>I absolutely agree that if the in-band media was =
'just ringtone' there would be no point. In particular I don't see any =
need to support the PSTN 'feeture' in which you always hear the =
ringtone of the destination country (IMO this is a bug, not a =
feature!).</FONT></P>

<P><FONT SIZE=3D2>So, let's recognise that there are cases where *both* =
out-of-band and in-band status indications are present. My view is that =
out-of-band indications should always be propogated if available - so =
for the scenario in question we MUST use 180, not 183. Now we need to =
indicate that in-band status is also available - is this really so hard =
????</FONT></P>

<P><FONT SIZE=3D2>...Mark </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; From: Peterson, Jon [<A =
HREF=3D"mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz=
</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 07 March 2003 00:09 </FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Ejzak, Richard P (Richard)'; Peterson, =
Jon; 'Gonzalo Camarillo' </FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Watson, Mark [MOP:EP10:EXCH]; sipping =
</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sipping] New version of the early =
media draft </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Everything below is familiar ground, and I =
don't want to </FONT>
<BR><FONT SIZE=3D2>&gt; start rehearsing </FONT>
<BR><FONT SIZE=3D2>&gt; these same arguments again. SIP has made a =
number of design </FONT>
<BR><FONT SIZE=3D2>&gt; decisions that </FONT>
<BR><FONT SIZE=3D2>&gt; predispose it towards out-of-band status =
information. Sending </FONT>
<BR><FONT SIZE=3D2>&gt; in-band status </FONT>
<BR><FONT SIZE=3D2>&gt; information in SIP is harmful - period. In-band =
media should </FONT>
<BR><FONT SIZE=3D2>&gt; be sent only </FONT>
<BR><FONT SIZE=3D2>&gt; when the gateway does not know the status of =
the call, and thus cannot </FONT>
<BR><FONT SIZE=3D2>&gt; communicate it out-of-band. Below, you =
basically argue that </FONT>
<BR><FONT SIZE=3D2>&gt; in cases where </FONT>
<BR><FONT SIZE=3D2>&gt; the gateway does not know the status of the =
call, it has to send early </FONT>
<BR><FONT SIZE=3D2>&gt; media. I agree. I said that in cases in which =
the gateway </FONT>
<BR><FONT SIZE=3D2>&gt; knows that the </FONT>
<BR><FONT SIZE=3D2>&gt; early media is just ringtone, it should send =
180. Clearly, if </FONT>
<BR><FONT SIZE=3D2>&gt; there's some </FONT>
<BR><FONT SIZE=3D2>&gt; in-band transition in call state from ringtone =
to some other </FONT>
<BR><FONT SIZE=3D2>&gt; audible call </FONT>
<BR><FONT SIZE=3D2>&gt; progress information, and the gateway isn't =
made aware of it, then the </FONT>
<BR><FONT SIZE=3D2>&gt; gateway doesn't know the state of the call. =
Perhaps we might draw the </FONT>
<BR><FONT SIZE=3D2>&gt; conclusion from your example that out-of-band =
call status </FONT>
<BR><FONT SIZE=3D2>&gt; indicators are </FONT>
<BR><FONT SIZE=3D2>&gt; inherently unreliable, then - and surmise that =
it is </FONT>
<BR><FONT SIZE=3D2>&gt; impossible for the </FONT>
<BR><FONT SIZE=3D2>&gt; gateway to know the state of the call. Or =
perhaps the </FONT>
<BR><FONT SIZE=3D2>&gt; likelihood of this </FONT>
<BR><FONT SIZE=3D2>&gt; condition arising is sufficiently remote, the =
consequences of </FONT>
<BR><FONT SIZE=3D2>&gt; sending early </FONT>
<BR><FONT SIZE=3D2>&gt; media sufficiently troublesome, that we might =
decide the </FONT>
<BR><FONT SIZE=3D2>&gt; in-band information </FONT>
<BR><FONT SIZE=3D2>&gt; in these cases is not 'essential' enough to =
worry over. But I </FONT>
<BR><FONT SIZE=3D2>&gt; firmly believe </FONT>
<BR><FONT SIZE=3D2>&gt; we should leave this to the conscience of the =
individual gateway </FONT>
<BR><FONT SIZE=3D2>&gt; implementer. I don't think the early media =
draft needs to draw that </FONT>
<BR><FONT SIZE=3D2>&gt; conclusion. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mr. Camarillo's draft already maintains a very =
delicate </FONT>
<BR><FONT SIZE=3D2>&gt; balance of behavior </FONT>
<BR><FONT SIZE=3D2>&gt; to accommodate SIP's needs, and I haven't heard =
anything in </FONT>
<BR><FONT SIZE=3D2>&gt; this yet that </FONT>
<BR><FONT SIZE=3D2>&gt; should alter it. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Jon Peterson </FONT>
<BR><FONT SIZE=3D2>&gt; NeuStar, Inc. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Ejzak, Richard P (Richard) [<A =
HREF=3D"mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Thursday, March 06, 2003 2:40 PM =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: 'Peterson, Jon'; 'Gonzalo Camarillo' =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cc: Mark Watson; sipping </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: RE: [Sipping] New version of the =
early media draft </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Jon, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I must disagree with your blanket =
recommendation that the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; gateway not sent in-band ringing =
media.&nbsp; This may be possible </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; in some cases - and nothing we have =
suggested would prevent a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; gateway from using out-of-band =
indications.&nbsp; But ringing is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; not the only in-band call progress =
information you may </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; receive while trying to establish a call =
from SIP to ISUP.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The transition from alerting to other =
forms of in-band call </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; progress information is not guaranteed to =
be clearly signaled </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; by ISUP within an ACM or CPG (since every =
switch in the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; network can safely assume in-band call =
progress after a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; certain point in the call), and it is =
essential that this </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; subsequent information (when it exists) be =
presented to the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; UAC/user.&nbsp; And the notion of having =
the gateway intelligently </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; filter what it thinks is ringing and =
detect a transition to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; other forms of call progress is not =
acceptable. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Regards, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Richard Ejzak </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Lucent Technologies </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Peterson, Jon [<A =
HREF=3D"mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz=
</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Thursday, March 06, 2003 4:06 PM =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: 'Gonzalo Camarillo' </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cc: Mark Watson; 'Ejzak, Richard P =
(Richard)'; sipping </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: RE: [Sipping] New version of the =
early media draft </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Well, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camaril=
lo@lmf.ericsson.se</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; [snip] </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The scenario he is after is as =
follows; a gateway *knows* </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that the user </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; is being alerted and also *knows* =
that it will be sending in-band </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ringing. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; If the gateway knows that it will be =
sending in-band ringing, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; my position is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that the gateway shouldn't be sending that =
media. It's just </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ring tone. The </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; UAC can generate that itself. Let's not =
waste the bandwidth </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; sending ringing, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; especially in forking cases, especially =
because the UAC </FONT>
<BR><FONT SIZE=3D2>&gt; might not even </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; render this provisional media (if it's a =
PC UAC, for example). </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; If media arrives at the UAC, it should =
override local </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ringtone, agreed. And </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I have no problem with the idea that a UAC =
would delay local </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ringtone for a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; short interval in order to see if any =
media is coming, even </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; when 180 is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; received. But we should not encourage =
gateways to send </FONT>
<BR><FONT SIZE=3D2>&gt; ringing media. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Jon Peterson </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; NeuStar, Inc. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2E8F2.C610FF0C--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 00:35:27 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09054
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 00:35:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2D5nhL17233
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 00:49:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D5nhO17230
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 00:49:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09047
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 00:34:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D5mrO17213;
	Thu, 13 Mar 2003 00:48:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D5lkO17161
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 00:47:46 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09014
	for <sipping@ietf.org>; Thu, 13 Mar 2003 00:32:57 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2D5YrC09950;
	Thu, 13 Mar 2003 05:34:53 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JTMJA>; Thu, 13 Mar 2003 00:35:09 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F18@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'Gonzalo Camarillo'"
	 <Gonzalo.Camarillo@lmf.ericsson.se>,
        "Ejzak, Richard P (Richard)"
	 <ejzak@lucent.com>
Cc: sipping <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Thu, 13 Mar 2003 00:35:07 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E922.4E8B3120"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E922.4E8B3120
Content-Type: text/plain;
	charset="iso-8859-1"

inline.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Wednesday, March 12, 2003 1:24 AM
To: 'Gonzalo Camarillo'; Ejzak, Richard P (Richard)
Cc: 'Peterson, Jon'; sipping
Subject: RE: [Sipping] New version of the early media draft



Gonzalo, 

Regarding the SDP direction attribute, this is indeed the solution which was
mooted some time ago, but it is not documented clearly. I think if this is
the proposed resolution of this problem, it does need to be clearly
described & the Early Media draft would be an appropriate place.Then it can
be included in the SIP/ISUP interworking work which is ongoing in ITU-T and
3GPP. 

<JFP> The reason why it was mooted (if I recall) is that it seemed to change
the meaning of 'a=inactive'. The UAC has to be prepared to receive media
before 200 OK, in order to avoid clipping of post-answer media. Setting the
media stream inactive is supposed to tell the UAC that it doesn't need to
listen for media, or so the argument goes. I haven't heard that challenged
in this thread, anyway. </JFP>

If I understand correctly, you are saying that a UAS SHOULD put the media
'on hold' by setting a=inactive if there is no Early Media. If the media
stream is not 'on hold' then the UAC should assume there is media and play
it.  

<JFP> ... which seems to be redundant with sending the pre-answer media
itself, provided that the gateway UAS only sends media when the UAC needs to
render it (because the UAS is unable to communicate status out-of-band for
whatever reason). I'm still not clear why the UAC shouldn't play media, if
it's there. </JFP> 

This is ok with me, but it does seem to place a new requirement on all
existing UAS's. 

I am confused about your position stated at the end of your mail, though. We
are on the sipping list, so the question of what protocol element might be
used if this requirement is agreed is out of scope here. So, are you saying
that you do not find the requirement unreasonable ? Can we agree on that
before jumping into solutions ?

...Mark 

> -----Original Message----- 
> From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se
<mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> Sent: 12 March 2003 07:11 
> To: Ejzak, Richard P (Richard) 
> Cc: 'Peterson, Jon'; Watson, Mark [MOP:EP10:EXCH]; sipping 
> Subject: Re: [Sipping] New version of the early media draft 
> 
> 
> Richard, 
> 
> just to be clear, I am not proposing to change the draft. I am just 
> saying that using the SDP direction attribute seems to resolve Mark's 
> concerns. 
> 
> > My concern is to do media detection and tone insertion efficiently, 
> > correctly, and only when necessary. 
> 
> I guess the crux of the issue is the part where you say "only when 
> necessary"... it is clear that such an indication would save you 
> performing media detection for 180 responses with the inband 
> media flag. 
> 
> My position is, as I said in this thread before, that if people 
> considered this as an important gain, I would not find it unreasonable 
> to standardize an empty Alert-Info header field. 
> 
> However, others have expressed concerns about that... 
> 
> Gonzalo 
> 
> "Ejzak, Richard P (Richard)" wrote: 
> > 
> > Gonzalo, 
> > Thanks for your attempt to find a way forward.  But I never 
> objected to media detection across the board.  It is 
> necessary, as you point out, to avoid clipping in certain 
> scenarios.  There was a scenario very similar to the one you 
> propose in an earlier version of the manyfolks draft that was 
> removed after I raised an objection last year, because it 
> introduced a potential for media clipping. 
> > 
> > My concern is to do media detection and tone insertion 
> efficiently, correctly, and only when necessary.  As I stated 
> earlier, there is no reason to change how things work for 
> native SIP UAs.  Your proposal would actually have the most 
> impact on native SIP UAs (typically without in-band media)!  
> But when a UAS PSTN gateway is in the mix with in-band call 
> progress media, we know there is no need for either media 
> detection or tone insertion, and, in fact, there's a good 
> chance they would muck things up. 
> > 
> > Your proposal unfortunately appears to cause more harm than 
> good (by re-introducing potential for clipping and impacting 
> SIP UAs without in-band media).  We need some kind of 
> indication associated with the 180 (not SDP) that in-band 
> call progress information is available. 
> > 
> > I am mightily confused as to why this is such a challenging 
> problem.  I have proposed at least two backwards compatible 
> methods for signaling this information. 
> > 
> > Regards, 
> > Richard Ejzak 
> > Lucent Technologies 
> 


------_=_NextPart_001_01C2E922.4E8B3120
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=685595304-13032003><FONT face=Arial color=#0000ff 
size=2>inline.</FONT></SPAN></DIV>
<DIV><SPAN class=685595304-13032003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=685595304-13032003><FONT face=Arial color=#0000ff size=2>Jon 
Peterson</FONT></SPAN></DIV>
<DIV><SPAN class=685595304-13032003><FONT face=Arial color=#0000ff 
size=2>NeuStar, Inc.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
  [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Wednesday, March 12, 2003 
  1:24 AM<BR><B>To:</B> 'Gonzalo Camarillo'; Ejzak, Richard P 
  (Richard)<BR><B>Cc:</B> 'Peterson, Jon'; sipping<BR><B>Subject:</B> RE: 
  [Sipping] New version of the early media draft<BR><BR></FONT></DIV>
  <P><FONT size=2>Gonzalo,</FONT> </P>
  <P><FONT size=2>Regarding the SDP direction attribute, this is indeed the 
  solution which was mooted some time ago, but it is not documented clearly. I 
  think if this is the proposed resolution of this problem, it does need to be 
  clearly described &amp; the Early Media draft would be an appropriate 
  place.Then it can be included in the SIP/ISUP interworking work which is 
  ongoing in ITU-T and 3GPP.<SPAN class=685595304-13032003><FONT face=Arial 
  color=#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=2><SPAN class=685595304-13032003><FONT face=Arial 
  color=#0000ff>&lt;JFP&gt; The reason why it was mooted (if I recall) is that 
  it seemed to change the meaning of 'a=inactive'.&nbsp;The UAC has to be 
  prepared to&nbsp;receive media&nbsp;before 200 OK,&nbsp;in order to 
  avoid&nbsp;clipping of post-answer media. Setting the media stream inactive is 
  supposed to tell the UAC that it doesn't need to listen for media, or so the 
  argument goes. I haven't heard that challenged in this thread, anyway. 
  &lt;/JFP&gt;</FONT></SPAN></FONT></P>
  <P><FONT size=2>If I understand correctly, you are saying that a UAS SHOULD 
  put the media 'on hold' by setting a=inactive if there is no Early Media. If 
  the media stream is not 'on hold' then the UAC should assume there is media 
  and play it.&nbsp;<SPAN class=685595304-13032003><FONT face=Arial 
  color=#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=2><SPAN class=685595304-13032003><FONT face=Arial 
  color=#0000ff>&lt;JFP&gt;&nbsp;... which seems to be redundant with sending 
  the pre-answer&nbsp;media itself, provided that the gateway UAS only sends 
  media when the UAC needs to render it (because the UAS is unable to 
  communicate status out-of-band for whatever reason). I'm still not clear why 
  the UAC shouldn't play media, if it's there. 
  &lt;/JFP&gt;</FONT>&nbsp;</SPAN></FONT></P>
  <P><FONT size=2>This is ok with me, but it does seem to place a new 
  requirement on all existing UAS's.</FONT> </P>
  <P><FONT size=2>I am confused about your position stated at the end of your 
  mail, though. We are on the sipping list, so the question of what protocol 
  element might be used if this requirement is agreed is out of scope here. So, 
  are you saying that you do not find the requirement unreasonable ? Can we 
  agree on that before jumping into solutions ?</FONT></P>
  <P><FONT size=2>...Mark</FONT> </P>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: Gonzalo Camarillo [<A 
  href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
  <BR><FONT size=2>&gt; Sent: 12 March 2003 07:11</FONT> <BR><FONT size=2>&gt; 
  To: Ejzak, Richard P (Richard)</FONT> <BR><FONT size=2>&gt; Cc: 'Peterson, 
  Jon'; Watson, Mark [MOP:EP10:EXCH]; sipping</FONT> <BR><FONT size=2>&gt; 
  Subject: Re: [Sipping] New version of the early media draft</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  Richard,</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; just to be 
  clear, I am not proposing to change the draft. I am just</FONT> <BR><FONT 
  size=2>&gt; saying that using the SDP direction attribute seems to resolve 
  Mark's</FONT> <BR><FONT size=2>&gt; concerns.</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; &gt; My concern is to do media detection and tone 
  insertion efficiently, </FONT><BR><FONT size=2>&gt; &gt; correctly, and only 
  when necessary.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; I 
  guess the crux of the issue is the part where you say "only when</FONT> 
  <BR><FONT size=2>&gt; necessary"... it is clear that such an indication would 
  save you</FONT> <BR><FONT size=2>&gt; performing media detection for 180 
  responses with the inband </FONT><BR><FONT size=2>&gt; media flag.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; My position is, as I said 
  in this thread before, that if people</FONT> <BR><FONT size=2>&gt; considered 
  this as an important gain, I would not find it unreasonable</FONT> <BR><FONT 
  size=2>&gt; to standardize an empty Alert-Info header field.</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; However, others have expressed 
  concerns about that...</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; Gonzalo</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  "Ejzak, Richard P (Richard)" wrote:</FONT> <BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; Gonzalo,</FONT> <BR><FONT size=2>&gt; &gt; 
  Thanks for your attempt to find a way forward.&nbsp; But I never 
  </FONT><BR><FONT size=2>&gt; objected to media detection across the 
  board.&nbsp; It is </FONT><BR><FONT size=2>&gt; necessary, as you point out, 
  to avoid clipping in certain </FONT><BR><FONT size=2>&gt; scenarios.&nbsp; 
  There was a scenario very similar to the one you </FONT><BR><FONT size=2>&gt; 
  propose in an earlier version of the manyfolks draft that was </FONT><BR><FONT 
  size=2>&gt; removed after I raised an objection last year, because it 
  </FONT><BR><FONT size=2>&gt; introduced a potential for media clipping.</FONT> 
  <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; My concern is to 
  do media detection and tone insertion </FONT><BR><FONT size=2>&gt; 
  efficiently, correctly, and only when necessary.&nbsp; As I stated 
  </FONT><BR><FONT size=2>&gt; earlier, there is no reason to change how things 
  work for </FONT><BR><FONT size=2>&gt; native SIP UAs.&nbsp; Your proposal 
  would actually have the most </FONT><BR><FONT size=2>&gt; impact on native SIP 
  UAs (typically without in-band media)!&nbsp; </FONT><BR><FONT size=2>&gt; But 
  when a UAS PSTN gateway is in the mix with in-band call </FONT><BR><FONT 
  size=2>&gt; progress media, we know there is no need for either media 
  </FONT><BR><FONT size=2>&gt; detection or tone insertion, and, in fact, 
  there's a good </FONT><BR><FONT size=2>&gt; chance they would muck things 
  up.</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Your 
  proposal unfortunately appears to cause more harm than </FONT><BR><FONT 
  size=2>&gt; good (by re-introducing potential for clipping and impacting 
  </FONT><BR><FONT size=2>&gt; SIP UAs without in-band media).&nbsp; We need 
  some kind of </FONT><BR><FONT size=2>&gt; indication associated with the 180 
  (not SDP) that in-band </FONT><BR><FONT size=2>&gt; call progress information 
  is available.</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
  &gt; I am mightily confused as to why this is such a challenging 
  </FONT><BR><FONT size=2>&gt; problem.&nbsp; I have proposed at least two 
  backwards compatible </FONT><BR><FONT size=2>&gt; methods for signaling this 
  information.</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
  &gt; Regards,</FONT> <BR><FONT size=2>&gt; &gt; Richard Ejzak</FONT> <BR><FONT 
  size=2>&gt; &gt; Lucent Technologies</FONT> <BR><FONT size=2>&gt; 
</FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E922.4E8B3120--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 03:54:35 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24129
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 03:54:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2D98ul08338
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 04:08:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D98uO08335
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 04:08:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24117
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 03:53:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D97WO08103;
	Thu, 13 Mar 2003 04:07:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D560O14062
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 00:06:00 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07968
	for <sipping@ietf.org>; Wed, 12 Mar 2003 23:51:09 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2D4qEC09592;
	Thu, 13 Mar 2003 04:52:14 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JTMD9>; Wed, 12 Mar 2003 23:52:29 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F15@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Wed, 12 Mar 2003 23:52:29 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2E91C.5987E6F0"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2E91C.5987E6F0
Content-Type: text/plain;
	charset="iso-8859-1"

Let me see if I can put this is a slightly simpler light. Let's ignore what
SIP status code the gateway sends for a moment.
 
A gateway UAS needs to decide whether it's going to send pre-answer media
media or not. What I've heard you saying is that the indicators in ISUP
don't provide this information (presumably that the 'in-band status
indicator' in OBCI doesn't have to be present in order for the PSTN to send
in-band status, just sending 'subscriber free' in BCI is enough). All right,
let's grant that for a moment.
 
So how does the gateway decide whether or not it's going to send media? I've
heard that ISUP doesn't tell you this, and that in-band media detection at
the UAS gateway is unacceptable.
 
What's the point of proposing some indicator (regardless of where it
appears) that a gateway UAS can send to the UAC signifying pre-answer media
if the gateway has no deterministic way of figuring out whether or not it
should send media?
 
The value you ascribe to the UAC knowing that the state is 'alerting' while
still receiving in-band status information is also a little curious to me.
It might be useful in PSTN-SIP-PSTN cases for a UAC gateway to know that the
UAS gateway is in the PSTN state 'alerting', but of course that can be
accommodated with RFC3204. I'm not sure how great the value of communicating
the alerting state is for SIP in other cases, though, when in-band media
contains the real indication of the state of the call. It's not as if that
state information can replace the in-band status information, right?
 
The conclusion is, if there is a deterministic way for the UAS GW to know
the state of a call, we can provide a mapping for it with our existing
mechanics. If there's not, this whole discussion is moot, because then the
gateway never knows the state of the call, your recommendation would have to
be that you send 183 and media for every call that comes through the gateway
UAS. That would be a very ill-advised recommendation to make, in my
estimation.
 
Some more inline.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Tuesday, March 11, 2003 9:23 AM
To: 'Peterson, Jon'
Cc: 'sipping@ietf.org'
Subject: RE: [Sipping] New version of the early media draft


Well, yes, if you change the axioms you will get a different conclusion.
<JFP> My point was more that SIP has no axioms for this to start with - the
standard is more or less totally silent about this. </JFP>
 
The Alerting state in ISUP is certainly well-defined. It certainly includes
the possibility of in-band media and does not make any assumptions about
what that media is (i.e. does not assume that it is 'ringtone'). It is not
'misleading' for ISUP to signal 'subscriber free' and to include in-band
media which is other than 'ringtone'.
 
Is the SIP state occasioned by 180 Ringing equivalent to 'Alerting' in ISUP
??  
<JFP> Indeed, that is the question. I see no reason to think it is. For one
thing, ISUP can assume that a backwards media path exists - that circuit
reservations were made when the IAM was sent. SIP makes no such assumption.
That's at least one difference in state. </JFP> 
 
Now, if you like, you can (re)define the SIP 180 Ringing state so that it
differs from the ISUP Alerting state in respect of support for in-band
media. Let's say that 180 Ringing does not support in-band media - which
seems to be where Jon is going below.  Now we have an interesting choice at
PSTN gateways in terms of deciding whether to send 180 or not. We could
determine somehow whether the in-band media was in fact 'ringtone' or not
and use this to decide - but perhaps that is not so realistic. Or we could
send 183 whenever we have in-band media (i.e. almost all the time). Ok, so
this will work, but I have discarded the indication that the subscriber is
in fact free. This is useful information at the UAC for several reasons:
(i) is assists in determining what to do with multiple provisional responses
received due to forking 
<JFP> But if you need to play the in-band media anyway, its value is no
greater than that of 183. The UAC knows that it needs to render the media to
get the status information. </JFP>
(ii) I can use it to drive a visual or other indication of call state
<JFP> The whole point of the fact that there's in-band information is that
there's something that can't be summed up by the simple 'ringing' icon or
indicator. If there's a call waiting announcement, shouldn't the visual
display ideally read "your call is waiting" or something? </JFP>
 
<JFP> But here's the thing - in the sorts of use cases I'm hearing from you,
it's not at all clear to me that the subscriber is free. In a call-waiting
case, isn't the subscriber 'free' or being queued? The in-band status
information provided instead of ringtone effectively clobbers the indication
that the subscriber is free. How ISUP defines its states is somewhat
immaterial to this point - saying that you're in the 'alerting state,
subscriber free' when you're playing a announcement that says something
different seems inherently contradictory.
 
All of these arguments about what happens at gateway UASs are predicated on
the fact that the gateway has some way to determine the state of the call.
What I hear you saying is that there really isn't. So where are you getting
this information that you want to carry back to the UAS? </JFP>
 
What is so wrong about wanting to carry this useful information to the UAC
??
 
...Mark

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: 10 March 2003 20:44
To: Watson, Mark [MOP:EP10:EXCH]
Cc: 'sipping@ietf.org'
Subject: RE: [Sipping] New version of the early media draft


Behind this all is probably an argument about what the 'alerting' state in
SIP really means, especially contrasted with 'queuing' and so on. Is call
waiting actually best expressed in the PSTN by ACM with 'subscriber free'?
Is it best expressed in SIP by 180 (or should it be 182)? Whether or not the
PSTN signals 'subscriber free' in ACM for call waiting, that doesn't mean
that the SIP 180 alerting state is co-extensive with arbitrary in-band
status information. The problem is that SIP does not define its states at
this level of granularity, so the evidence for either position would be
indirect at best. 183 expresses that the call is in some provisional state,
that it hasn't yet been rejected as far as SIP knows, and so on - at the
very least, it's sent when other 18x's aren't appropriate for some reason.
 
SIP gains significant benefits from not having to reserve a circuit and
transmit media in the backwards direction in order to communicate that a
telephone is ringing. Again, if ISUP is misleading about the condition that
prevails, I'm not sure that admits of any repair in SIPPING. SIP does
support response codes tailored for queuing situations, but if the PSTN
can't tell us out-of-band that queuing is taking place, we can't map to
them.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Monday, March 10, 2003 1:15 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


Jon,
 
If I use 183 then I lose the functional (out of band) indication that the
call is now in the Alerting state. So then, for example, a more advanced SIP
client may not provide the correct visual indication to the use ('ringing'
icon, or whatever).
 
We are talking about cases where the call state IS known to be 'Alerting',
so I think we must surely use 180, not 183. But there are useful in-band
tones AS WELL. In general a gateway would not know whether the in-band
information was boring ringtone, or something more interesting.
 
...Mark

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: 07 March 2003 18:03
To: Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P (Richard)'; 'Gonzalo
Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft


 
I'm not sure I missed that point, exactly. I said that if the gateway knows
that the early media is just ringtone, it should send a 180. You're just
citing another case below in which the early media is not ringtone. I can't
see how this contradicts what I said. If there's some other in-band status
information available, the gateway should be using 183.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Friday, March 07, 2003 1:17 AM
To: 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 'Gonzalo Camarillo'
Cc: sipping
Subject: RE: [Sipping] New version of the early media draft



Jon, 

You have missed one very important point which is that in-band media during
alerting is not necessarily 'just ringtone'. It is quite common for the call
to be in the 'Alerting' state (and for this to be know to a SIP to ISUP
gateway), but for the in-band media to contain some useful information other
than 'just ringtone'.

For example, in the UK at least, if the called party has Call Waiting, then
the call of course goes straight in to the Alerting state, but the caller
will here a message along the lines 'Please wait while we try to connect
your call - the person you are calling knows you are waiting'.

A second example would be when the call terminates on a queueing system, and
the message played gives the caller some idea of how long they will need to
wait.

I absolutely agree that if the in-band media was 'just ringtone' there would
be no point. In particular I don't see any need to support the PSTN
'feeture' in which you always hear the ringtone of the destination country
(IMO this is a bug, not a feature!).

So, let's recognise that there are cases where *both* out-of-band and
in-band status indications are present. My view is that out-of-band
indications should always be propogated if available - so for the scenario
in question we MUST use 180, not 183. Now we need to indicate that in-band
status is also available - is this really so hard ????

...Mark 

> -----Original Message----- 
> From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> Sent: 07 March 2003 00:09 
> To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo Camarillo' 
> Cc: Watson, Mark [MOP:EP10:EXCH]; sipping 
> Subject: RE: [Sipping] New version of the early media draft 
> 
> 
> 
> Everything below is familiar ground, and I don't want to 
> start rehearsing 
> these same arguments again. SIP has made a number of design 
> decisions that 
> predispose it towards out-of-band status information. Sending 
> in-band status 
> information in SIP is harmful - period. In-band media should 
> be sent only 
> when the gateway does not know the status of the call, and thus cannot 
> communicate it out-of-band. Below, you basically argue that 
> in cases where 
> the gateway does not know the status of the call, it has to send early 
> media. I agree. I said that in cases in which the gateway 
> knows that the 
> early media is just ringtone, it should send 180. Clearly, if 
> there's some 
> in-band transition in call state from ringtone to some other 
> audible call 
> progress information, and the gateway isn't made aware of it, then the 
> gateway doesn't know the state of the call. Perhaps we might draw the 
> conclusion from your example that out-of-band call status 
> indicators are 
> inherently unreliable, then - and surmise that it is 
> impossible for the 
> gateway to know the state of the call. Or perhaps the 
> likelihood of this 
> condition arising is sufficiently remote, the consequences of 
> sending early 
> media sufficiently troublesome, that we might decide the 
> in-band information 
> in these cases is not 'essential' enough to worry over. But I 
> firmly believe 
> we should leave this to the conscience of the individual gateway 
> implementer. I don't think the early media draft needs to draw that 
> conclusion. 
> 
> Mr. Camarillo's draft already maintains a very delicate 
> balance of behavior 
> to accommodate SIP's needs, and I haven't heard anything in 
> this yet that 
> should alter it. 
> 
> Jon Peterson 
> NeuStar, Inc. 
> 
> > -----Original Message----- 
> > From: Ejzak, Richard P (Richard) [ mailto:ejzak@lucent.com
<mailto:ejzak@lucent.com> ] 
> > Sent: Thursday, March 06, 2003 2:40 PM 
> > To: 'Peterson, Jon'; 'Gonzalo Camarillo' 
> > Cc: Mark Watson; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > Jon, 
> > I must disagree with your blanket recommendation that the 
> > gateway not sent in-band ringing media.  This may be possible 
> > in some cases - and nothing we have suggested would prevent a 
> > gateway from using out-of-band indications.  But ringing is 
> > not the only in-band call progress information you may 
> > receive while trying to establish a call from SIP to ISUP.  
> > The transition from alerting to other forms of in-band call 
> > progress information is not guaranteed to be clearly signaled 
> > by ISUP within an ACM or CPG (since every switch in the 
> > network can safely assume in-band call progress after a 
> > certain point in the call), and it is essential that this 
> > subsequent information (when it exists) be presented to the 
> > UAC/user.  And the notion of having the gateway intelligently 
> > filter what it thinks is ringing and detect a transition to 
> > other forms of call progress is not acceptable. 
> > 
> > Regards, 
> > Richard Ejzak 
> > Lucent Technologies 
> > 
> > 
> > 
> > -----Original Message----- 
> > From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> > Sent: Thursday, March 06, 2003 4:06 PM 
> > To: 'Gonzalo Camarillo' 
> > Cc: Mark Watson; 'Ejzak, Richard P (Richard)'; sipping 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> > 
> > 
> > Well, 
> > 
> > > -----Original Message----- 
> > > From: Gonzalo Camarillo [ mailto:Gonzalo.Camarillo@lmf.ericsson.se
<mailto:Gonzalo.Camarillo@lmf.ericsson.se> ] 
> > [snip] 
> > > 
> > > The scenario he is after is as follows; a gateway *knows* 
> > that the user 
> > > is being alerted and also *knows* that it will be sending in-band 
> > > ringing. 
> > > 
> > 
> > If the gateway knows that it will be sending in-band ringing, 
> > my position is 
> > that the gateway shouldn't be sending that media. It's just 
> > ring tone. The 
> > UAC can generate that itself. Let's not waste the bandwidth 
> > sending ringing, 
> > especially in forking cases, especially because the UAC 
> might not even 
> > render this provisional media (if it's a PC UAC, for example). 
> > 
> > If media arrives at the UAC, it should override local 
> > ringtone, agreed. And 
> > I have no problem with the idea that a UAC would delay local 
> > ringtone for a 
> > short interval in order to see if any media is coming, even 
> > when 180 is 
> > received. But we should not encourage gateways to send 
> ringing media. 
> > 
> > Jon Peterson 
> > NeuStar, Inc. 
> > 
> 


------_=_NextPart_001_01C2E91C.5987E6F0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff size=2>Let me 
see if I can put this is a slightly simpler light. Let's ignore what 
SIP&nbsp;status code the gateway sends for a moment.</FONT></SPAN></DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff size=2>A 
gateway UAS needs to decide whether it's going to send pre-answer media media or 
not. What I've heard you saying is that the indicators in ISUP don't provide 
this information (presumably that the 'in-band status indicator'&nbsp;in OBCI 
doesn't have to be present in order for the PSTN to send in-band status, just 
sending 'subscriber free' in BCI is enough). All right, let's grant that for a 
moment.</FONT></SPAN></DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff size=2>So how 
does the gateway decide whether or not it's going to send media? I've heard that 
ISUP doesn't tell you this, and that in-band media detection at the 
UAS&nbsp;gateway is unacceptable.</FONT></SPAN></DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff size=2>What's 
the point of proposing some indicator (regardless of where it appears) that a 
gateway&nbsp;UAS can send to the UAC signifying pre-answer media&nbsp;if the 
gateway has no deterministic way of figuring out whether or not it&nbsp;should 
send media?</FONT></SPAN></DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff size=2>The 
value you ascribe to the UAC knowing that the state is 'alerting' while 
still&nbsp;receiving in-band status information&nbsp;is also a little curious to 
me. It might be useful in PSTN-SIP-PSTN cases for a UAC gateway to know 
that&nbsp;the UAS gateway is in the PSTN state 'alerting', but of course that 
can be accommodated with RFC3204. I'm not sure how great the value of 
communicating the alerting state is for SIP in other cases, though, when in-band 
media contains the real indication of the state of the call. It's not as if that 
state information can replace the in-band status information, 
right?</FONT></SPAN></DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff size=2>The 
conclusion is, if there is a deterministic way for the UAS GW to know the state 
of a call, we can provide a mapping for it with our existing mechanics. If 
there's not, this whole discussion is moot, because then the gateway never knows 
the state of the call, your recommendation would have to be that you send 183 
and media for every call that comes through the gateway UAS. That would be a 
very ill-advised recommendation to make, in my estimation.</FONT></SPAN></DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff size=2>Some 
more inline.</FONT></SPAN></DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff size=2>Jon 
Peterson</FONT></SPAN></DIV>
<DIV><SPAN class=241473419-11032003><FONT face=Arial color=#0000ff 
size=2>NeuStar, Inc.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
  [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Tuesday, March 11, 2003 
  9:23 AM<BR><B>To:</B> 'Peterson, Jon'<BR><B>Cc:</B> 
  'sipping@ietf.org'<BR><B>Subject:</B> RE: [Sipping] New version of the early 
  media draft<BR><BR></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003>Well, yes, if you change the axioms you will get a 
  different conclusion.</SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003><SPAN class=241473419-11032003>&lt;JFP&gt; My point 
  was more that SIP has no axioms for this to start with&nbsp;- the standard is 
  more or less totally silent about this. 
&lt;/JFP&gt;</SPAN></SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003>The Alerting state in ISUP is certainly well-defined. 
  It certainly includes&nbsp;the possibility of in-band media and does not make 
  any assumptions about what that media is (i.e. does not assume that it is 
  'ringtone'). It is not 'misleading' for ISUP to signal 'subscriber free' and 
  to include in-band media which is other than 'ringtone'.</SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Verdana size=1><SPAN class=191181317-11032003><FONT 
  color=#0000ff>Is the SIP state occasioned by 180 Ringing equivalent to 
  'Alerting' in ISUP ??&nbsp;<SPAN class=241473419-11032003><FONT face=Arial 
  size=2>&nbsp;</FONT></SPAN></FONT></SPAN></FONT></DIV>
  <DIV><SPAN class=191181317-11032003><FONT color=#0000ff><SPAN 
  class=241473419-11032003><FONT face=Verdana size=1>&lt;JFP&gt; Indeed, that is 
  the question.&nbsp;I see no reason to think it is. For one thing, ISUP can 
  assume that a backwards media path exists - that circuit reservations were 
  made when the IAM was sent. SIP makes no such assumption. That's at least one 
  difference in state. &lt;/JFP&gt;&nbsp;</FONT></SPAN></FONT></SPAN></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003>Now, if you like, you can (re)define the SIP 180 
  Ringing state so that it differs from the ISUP Alerting state in respect of 
  support for in-band media. Let's say that 180 Ringing does not support in-band 
  media - which seems to be where Jon is going below.&nbsp;</SPAN></FONT><FONT 
  face=Verdana color=#0000ff size=1><SPAN class=191181317-11032003><SPAN 
  class=241473419-11032003>&nbsp;</SPAN>Now we have an interesting choice at 
  PSTN gateways in terms of deciding whether to send 180 or not. We could 
  determine somehow whether the in-band media was in fact 'ringtone' or not and 
  use this to decide - but perhaps that is not so realistic. Or we could send 
  183 whenever we have in-band media (i.e. almost all the time). Ok, so this 
  will work, but I have discarded the indication that the subscriber is in fact 
  free. This is useful information at the UAC for several 
  reasons:</SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003>(i) is assists in determining what to do with 
  multiple provisional responses received due to forking<SPAN 
  class=241473419-11032003><FONT face=Arial color=#000000 
  size=2>&nbsp;</FONT></SPAN></SPAN></FONT></DIV>
  <DIV><SPAN class=191181317-11032003><SPAN class=241473419-11032003><FONT 
  color=#0000ff><FONT face=Verdana size=1>&lt;JFP&gt;&nbsp;But if you 
  need&nbsp;to play the in-band media anyway, its value is no greater than that 
  of 183.&nbsp;The UAC knows that it needs to render the media to get the status 
  information. &lt;/JFP&gt;</FONT></FONT></SPAN></SPAN></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003>(ii) I can use it to drive a visual or other 
  indication of call state</SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003><SPAN class=241473419-11032003>&lt;JFP&gt; The whole 
  point of the fact that there's in-band information is that there's something 
  that can't be summed up by the simple 'ringing' icon or indicator. If there's 
  a call waiting announcement, shouldn't the visual display ideally&nbsp;read 
  "your call is&nbsp;waiting" or 
  something?&nbsp;&lt;/JFP&gt;</SPAN></SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003><SPAN 
  class=241473419-11032003></SPAN></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003><SPAN class=241473419-11032003>&lt;JFP&gt; But here's 
  the thing - in the sorts of use cases I'm hearing from you, it's not at all 
  clear to me that the subscriber is free. In a call-waiting case, isn't the 
  subscriber 'free' or being queued? The in-band status information provided 
  instead of ringtone effectively clobbers the indication that the subscriber is 
  free. How ISUP defines its states is somewhat immaterial to this point - 
  saying that you're in the 'alerting state, subscriber free' when you're 
  playing a announcement that says something different seems inherently 
  contradictory.</SPAN></SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003><SPAN 
  class=241473419-11032003></SPAN></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003><SPAN class=241473419-11032003>All of these arguments 
  about what happens at gateway UASs are predicated on the fact that the gateway 
  has some way to determine the state of the call. What I hear you saying is 
  that there really isn't. So where are you getting this information that you 
  want to carry back to the UAS? &lt;/JFP&gt;</SPAN></SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003>What is so wrong about wanting to carry this useful 
  information to the UAC ??</SPAN></FONT></DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
  class=191181317-11032003>...Mark</SPAN></FONT></DIV>
  <BLOCKQUOTE dir=ltr 
  style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
    <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
    size=2>-----Original Message-----<BR><B>From:</B> Peterson, Jon 
    [mailto:jon.peterson@neustar.biz]<BR><B>Sent:</B> 10 March 2003 
    20:44<BR><B>To:</B> Watson, Mark [MOP:EP10:EXCH]<BR><B>Cc:</B> 
    'sipping@ietf.org'<BR><B>Subject:</B> RE: [Sipping] New version of the early 
    media draft<BR><BR></DIV></FONT>
    <DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff 
    size=2>Behind this all is probably an argument about what the 'alerting' 
    state in SIP&nbsp;really means, especially contrasted with 'queuing' and so 
    on. Is call waiting actually best expressed in the PSTN&nbsp;by ACM with 
    'subscriber free'? Is it best expressed in SIP by 180 (or should it be 182)? 
    Whether or not the PSTN signals 'subscriber free' in ACM for call waiting, 
    that doesn't mean that the SIP 180 alerting state is co-extensive with 
    arbitrary in-band status information. The problem is that SIP does not 
    define its states at this level of granularity, so the evidence for either 
    position would be indirect at best. 183 expresses that the call is in some 
    provisional state, that it hasn't yet been rejected as far as SIP knows, and 
    so on - at the very least, it's sent when other 18x's aren't appropriate for 
    some reason.</FONT></SPAN></DIV>
    <DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff 
    size=2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff 
    size=2>SIP gains significant benefits from not having to reserve a circuit 
    and transmit media in the backwards direction in order to communicate that a 
    telephone is ringing. Again, if ISUP is misleading about the condition that 
    prevails, I'm not sure that admits of any repair in SIPPING. SIP does 
    support response codes tailored for queuing situations, but if the PSTN 
    can't tell us out-of-band&nbsp;that queuing is taking place, we can't map to 
    them.</FONT></SPAN></DIV>
    <DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff 
    size=2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff 
    size=2>Jon Peterson</FONT></SPAN></DIV>
    <DIV><SPAN class=976301120-10032003><FONT face=Arial color=#0000ff 
    size=2>NeuStar, Inc.</FONT></SPAN></DIV>
    <BLOCKQUOTE dir=ltr 
    style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
      <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
      size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
      [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Monday, March 10, 2003 
      1:15 AM<BR><B>To:</B> 'Peterson, Jon'; 'Ejzak, Richard P (Richard)'; 
      'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> RE: [Sipping] 
      New version of the early media draft<BR><BR></FONT></DIV>
      <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
      class=007171609-10032003>Jon,</SPAN></FONT></DIV>
      <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
      class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
      class=007171609-10032003>If I use 183 then I lose the functional (out of 
      band) indication that the call is now in the Alerting state. So then, for 
      example, a more advanced SIP client may&nbsp;not provide the correct 
      visual indication to the use ('ringing' icon, or 
      whatever).</SPAN></FONT></DIV>
      <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
      class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
      class=007171609-10032003>We are talking about cases where the call state 
      IS known to be 'Alerting', so I think we must surely use 180, not 183. But 
      there are useful in-band tones AS WELL. In general a gateway would not 
      know whether the in-band information was boring ringtone, or something 
      more interesting.</SPAN></FONT></DIV>
      <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
      class=007171609-10032003></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=Verdana color=#0000ff size=1><SPAN 
      class=007171609-10032003>...Mark</SPAN></FONT></DIV>
      <BLOCKQUOTE dir=ltr 
      style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
        <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
        size=2>-----Original Message-----<BR><B>From:</B> Peterson, Jon 
        [mailto:jon.peterson@neustar.biz]<BR><B>Sent:</B> 07 March 2003 
        18:03<BR><B>To:</B> Watson, Mark [MOP:EP10:EXCH]; 'Ejzak, Richard P 
        (Richard)'; 'Gonzalo Camarillo'<BR><B>Cc:</B> sipping<BR><B>Subject:</B> 
        RE: [Sipping] New version of the early media draft<BR><BR></DIV></FONT>
        <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
        <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
        size=2>I'm not sure I missed that point, exactly. I said that if the 
        gateway knows that the early media is just ringtone, it should send a 
        180. You're just citing another case below in which the early media is 
        not ringtone. I can't see how this contradicts what I said. If there's 
        some other in-band status information available, the gateway should be 
        using 183.</FONT></SPAN></DIV>
        <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
        <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
        size=2>Jon Peterson</FONT></SPAN></DIV>
        <DIV><SPAN class=918445017-07032003><FONT face=Arial color=#0000ff 
        size=2>NeuStar, Inc.</FONT></SPAN></DIV>
        <BLOCKQUOTE dir=ltr 
        style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
          <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
          size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
          [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Friday, March 07, 
          2003 1:17 AM<BR><B>To:</B> 'Peterson, Jon'; 'Ejzak, Richard P 
          (Richard)'; 'Gonzalo Camarillo'<BR><B>Cc:</B> 
          sipping<BR><B>Subject:</B> RE: [Sipping] New version of the early 
          media draft<BR><BR></FONT></DIV>
          <P><FONT size=2>Jon,</FONT> </P>
          <P><FONT size=2>You have missed one very important point which is that 
          in-band media during alerting is not necessarily 'just ringtone'. It 
          is quite common for the call to be in the 'Alerting' state (and for 
          this to be know to a SIP to ISUP gateway), but for the in-band media 
          to contain some useful information other than 'just 
          ringtone'.</FONT></P>
          <P><FONT size=2>For example, in the UK at least, if the called party 
          has Call Waiting, then the call of course goes straight in to the 
          Alerting state, but the caller will here a message along the lines 
          'Please wait while we try to connect your call - the person you are 
          calling knows you are waiting'.</FONT></P>
          <P><FONT size=2>A second example would be when the call terminates on 
          a queueing system, and the message played gives the caller some idea 
          of how long they will need to wait.</FONT></P>
          <P><FONT size=2>I absolutely agree that if the in-band media was 'just 
          ringtone' there would be no point. In particular I don't see any need 
          to support the PSTN 'feeture' in which you always hear the ringtone of 
          the destination country (IMO this is a bug, not a 
feature!).</FONT></P>
          <P><FONT size=2>So, let's recognise that there are cases where *both* 
          out-of-band and in-band status indications are present. My view is 
          that out-of-band indications should always be propogated if available 
          - so for the scenario in question we MUST use 180, not 183. Now we 
          need to indicate that in-band status is also available - is this 
          really so hard ????</FONT></P>
          <P><FONT size=2>...Mark</FONT> </P>
          <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT 
          size=2>&gt; From: Peterson, Jon [<A 
          href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
          <BR><FONT size=2>&gt; Sent: 07 March 2003 00:09</FONT> <BR><FONT 
          size=2>&gt; To: 'Ejzak, Richard P (Richard)'; Peterson, Jon; 'Gonzalo 
          Camarillo'</FONT> <BR><FONT size=2>&gt; Cc: Watson, Mark 
          [MOP:EP10:EXCH]; sipping</FONT> <BR><FONT size=2>&gt; Subject: RE: 
          [Sipping] New version of the early media draft</FONT> <BR><FONT 
          size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
          </FONT><BR><FONT size=2>&gt; Everything below is familiar ground, and 
          I don't want to </FONT><BR><FONT size=2>&gt; start rehearsing</FONT> 
          <BR><FONT size=2>&gt; these same arguments again. SIP has made a 
          number of design </FONT><BR><FONT size=2>&gt; decisions that</FONT> 
          <BR><FONT size=2>&gt; predispose it towards out-of-band status 
          information. Sending </FONT><BR><FONT size=2>&gt; in-band 
          status</FONT> <BR><FONT size=2>&gt; information in SIP is harmful - 
          period. In-band media should </FONT><BR><FONT size=2>&gt; be sent 
          only</FONT> <BR><FONT size=2>&gt; when the gateway does not know the 
          status of the call, and thus cannot</FONT> <BR><FONT size=2>&gt; 
          communicate it out-of-band. Below, you basically argue that 
          </FONT><BR><FONT size=2>&gt; in cases where</FONT> <BR><FONT 
          size=2>&gt; the gateway does not know the status of the call, it has 
          to send early</FONT> <BR><FONT size=2>&gt; media. I agree. I said that 
          in cases in which the gateway </FONT><BR><FONT size=2>&gt; knows that 
          the</FONT> <BR><FONT size=2>&gt; early media is just ringtone, it 
          should send 180. Clearly, if </FONT><BR><FONT size=2>&gt; there's 
          some</FONT> <BR><FONT size=2>&gt; in-band transition in call state 
          from ringtone to some other </FONT><BR><FONT size=2>&gt; audible 
          call</FONT> <BR><FONT size=2>&gt; progress information, and the 
          gateway isn't made aware of it, then the</FONT> <BR><FONT size=2>&gt; 
          gateway doesn't know the state of the call. Perhaps we might draw 
          the</FONT> <BR><FONT size=2>&gt; conclusion from your example that 
          out-of-band call status </FONT><BR><FONT size=2>&gt; indicators 
          are</FONT> <BR><FONT size=2>&gt; inherently unreliable, then - and 
          surmise that it is </FONT><BR><FONT size=2>&gt; impossible for 
          the</FONT> <BR><FONT size=2>&gt; gateway to know the state of the 
          call. Or perhaps the </FONT><BR><FONT size=2>&gt; likelihood of 
          this</FONT> <BR><FONT size=2>&gt; condition arising is sufficiently 
          remote, the consequences of </FONT><BR><FONT size=2>&gt; sending 
          early</FONT> <BR><FONT size=2>&gt; media sufficiently troublesome, 
          that we might decide the </FONT><BR><FONT size=2>&gt; in-band 
          information</FONT> <BR><FONT size=2>&gt; in these cases is not 
          'essential' enough to worry over. But I </FONT><BR><FONT size=2>&gt; 
          firmly believe</FONT> <BR><FONT size=2>&gt; we should leave this to 
          the conscience of the individual gateway</FONT> <BR><FONT size=2>&gt; 
          implementer. I don't think the early media draft needs to draw 
          that</FONT> <BR><FONT size=2>&gt; conclusion.</FONT> <BR><FONT 
          size=2>&gt; </FONT><BR><FONT size=2>&gt; Mr. Camarillo's draft already 
          maintains a very delicate </FONT><BR><FONT size=2>&gt; balance of 
          behavior</FONT> <BR><FONT size=2>&gt; to accommodate SIP's needs, and 
          I haven't heard anything in </FONT><BR><FONT size=2>&gt; this yet 
          that</FONT> <BR><FONT size=2>&gt; should alter it.</FONT> <BR><FONT 
          size=2>&gt; </FONT><BR><FONT size=2>&gt; Jon Peterson</FONT> <BR><FONT 
          size=2>&gt; NeuStar, Inc.</FONT> <BR><FONT size=2>&gt; 
          </FONT><BR><FONT size=2>&gt; &gt; -----Original Message-----</FONT> 
          <BR><FONT size=2>&gt; &gt; From: Ejzak, Richard P (Richard) [<A 
          href="mailto:ejzak@lucent.com">mailto:ejzak@lucent.com</A>]</FONT> 
          <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 2:40 
          PM</FONT> <BR><FONT size=2>&gt; &gt; To: 'Peterson, Jon'; 'Gonzalo 
          Camarillo'</FONT> <BR><FONT size=2>&gt; &gt; Cc: Mark Watson; 
          sipping</FONT> <BR><FONT size=2>&gt; &gt; Subject: RE: [Sipping] New 
          version of the early media draft</FONT> <BR><FONT size=2>&gt; &gt; 
          </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
          Jon,</FONT> <BR><FONT size=2>&gt; &gt; I must disagree with your 
          blanket recommendation that the </FONT><BR><FONT size=2>&gt; &gt; 
          gateway not sent in-band ringing media.&nbsp; This may be possible 
          </FONT><BR><FONT size=2>&gt; &gt; in some cases - and nothing we have 
          suggested would prevent a </FONT><BR><FONT size=2>&gt; &gt; gateway 
          from using out-of-band indications.&nbsp; But ringing is 
          </FONT><BR><FONT size=2>&gt; &gt; not the only in-band call progress 
          information you may </FONT><BR><FONT size=2>&gt; &gt; receive while 
          trying to establish a call from SIP to ISUP.&nbsp; </FONT><BR><FONT 
          size=2>&gt; &gt; The transition from alerting to other forms of 
          in-band call </FONT><BR><FONT size=2>&gt; &gt; progress information is 
          not guaranteed to be clearly signaled </FONT><BR><FONT size=2>&gt; 
          &gt; by ISUP within an ACM or CPG (since every switch in the 
          </FONT><BR><FONT size=2>&gt; &gt; network can safely assume in-band 
          call progress after a </FONT><BR><FONT size=2>&gt; &gt; certain point 
          in the call), and it is essential that this </FONT><BR><FONT 
          size=2>&gt; &gt; subsequent information (when it exists) be presented 
          to the </FONT><BR><FONT size=2>&gt; &gt; UAC/user.&nbsp; And the 
          notion of having the gateway intelligently </FONT><BR><FONT 
          size=2>&gt; &gt; filter what it thinks is ringing and detect a 
          transition to </FONT><BR><FONT size=2>&gt; &gt; other forms of call 
          progress is not acceptable.</FONT> <BR><FONT size=2>&gt; &gt; 
          </FONT><BR><FONT size=2>&gt; &gt; Regards,</FONT> <BR><FONT 
          size=2>&gt; &gt; Richard Ejzak</FONT> <BR><FONT size=2>&gt; &gt; 
          Lucent Technologies</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
          size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
          size=2>&gt; &gt; -----Original Message-----</FONT> <BR><FONT 
          size=2>&gt; &gt; From: Peterson, Jon [<A 
          href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
          <BR><FONT size=2>&gt; &gt; Sent: Thursday, March 06, 2003 4:06 
          PM</FONT> <BR><FONT size=2>&gt; &gt; To: 'Gonzalo Camarillo'</FONT> 
          <BR><FONT size=2>&gt; &gt; Cc: Mark Watson; 'Ejzak, Richard P 
          (Richard)'; sipping</FONT> <BR><FONT size=2>&gt; &gt; Subject: RE: 
          [Sipping] New version of the early media draft</FONT> <BR><FONT 
          size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
          size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Well,</FONT> 
          <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; &gt; 
          -----Original Message-----</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
          From: Gonzalo Camarillo [<A 
          href="mailto:Gonzalo.Camarillo@lmf.ericsson.se">mailto:Gonzalo.Camarillo@lmf.ericsson.se</A>]</FONT> 
          <BR><FONT size=2>&gt; &gt; [snip]</FONT> <BR><FONT size=2>&gt; &gt; 
          &gt; </FONT><BR><FONT size=2>&gt; &gt; &gt; The scenario he is after 
          is as follows; a gateway *knows* </FONT><BR><FONT size=2>&gt; &gt; 
          that the user</FONT> <BR><FONT size=2>&gt; &gt; &gt; is being alerted 
          and also *knows* that it will be sending in-band</FONT> <BR><FONT 
          size=2>&gt; &gt; &gt; ringing.</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
          </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; If 
          the gateway knows that it will be sending in-band ringing, 
          </FONT><BR><FONT size=2>&gt; &gt; my position is</FONT> <BR><FONT 
          size=2>&gt; &gt; that the gateway shouldn't be sending that media. 
          It's just </FONT><BR><FONT size=2>&gt; &gt; ring tone. The</FONT> 
          <BR><FONT size=2>&gt; &gt; UAC can generate that itself. Let's not 
          waste the bandwidth </FONT><BR><FONT size=2>&gt; &gt; sending 
          ringing,</FONT> <BR><FONT size=2>&gt; &gt; especially in forking 
          cases, especially because the UAC </FONT><BR><FONT size=2>&gt; might 
          not even</FONT> <BR><FONT size=2>&gt; &gt; render this provisional 
          media (if it's a PC UAC, for example).</FONT> <BR><FONT size=2>&gt; 
          &gt; </FONT><BR><FONT size=2>&gt; &gt; If media arrives at the UAC, it 
          should override local </FONT><BR><FONT size=2>&gt; &gt; ringtone, 
          agreed. And</FONT> <BR><FONT size=2>&gt; &gt; I have no problem with 
          the idea that a UAC would delay local </FONT><BR><FONT size=2>&gt; 
          &gt; ringtone for a</FONT> <BR><FONT size=2>&gt; &gt; short interval 
          in order to see if any media is coming, even </FONT><BR><FONT 
          size=2>&gt; &gt; when 180 is</FONT> <BR><FONT size=2>&gt; &gt; 
          received. But we should not encourage gateways to send 
          </FONT><BR><FONT size=2>&gt; ringing media.</FONT> <BR><FONT 
          size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Jon Peterson</FONT> 
          <BR><FONT size=2>&gt; &gt; NeuStar, Inc. </FONT><BR><FONT size=2>&gt; 
          &gt; </FONT><BR><FONT size=2>&gt; 
    </FONT></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2E91C.5987E6F0--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 04:10:05 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24560
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 04:10:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2D9ORc09093
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 04:24:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D9ORO09090
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 04:24:27 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24555
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 04:09:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D9NhO09039;
	Thu, 13 Mar 2003 04:23:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D9MGO08981
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 04:22:16 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24497
	for <sipping@ietf.org>; Thu, 13 Mar 2003 04:07:22 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2D99RC12796;
	Thu, 13 Mar 2003 09:09:27 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JTNVB>; Thu, 13 Mar 2003 04:09:44 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F1A@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Gunn, Janet'" <Janet.Gunn@DynCorp.com>, sipping@ietf.org
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Date: Thu, 13 Mar 2003 04:09:42 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Some notes below.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Gunn, Janet [mailto:Janet.Gunn@DynCorp.com]
> Sent: Tuesday, March 11, 2003 3:22 PM
> To: sipping@ietf.org
> Subject: [Sipping] Comments on draft-peterson-sipping-ieprep-00
> 
> 
[snip]
> 
> Section 2-2 Signaling Encapsulation
> 
> "In the CSN, it is not possible to
>       make an emergency call, for example, from France to the United
>       States.  International ISUP gateways that bridge between different
>       signaling systems will at best discard priority information."
> 
> Actually, it IS possible.  Every month over 3000 GETS  (710...) calls are
> placed from over 50 international locations.  They receive no priority
until
> they get to  US based switch, but most of them DO  receive priority
> treatment within the US.  Granted, it is the "710" that is passing through
> the international gateway, but that IS a "priority label" as well as a
> dialed number, and is not "discarded by the international gateway".
> 

There's no question that if the dialed number contains all of your priority
information, then you can make these prioritized calls internationally
(provided the number is E.164-friendly). The degree to which 710 numbers
receive priority treatment outside the US, however, is a subject of concern,
and that was what my point here was intended to illustrate. I can expand on
the wording above, if it was unclear.

Moreover, the Requirements draft went to great pains, if I recall, to
illustrate that dialed numbers were not sufficient for communicating
priority information (REQ-10). As was pointed out, non-authorized users can
dial these numbers in droves as a sort of DoS attack.

> "It's not clear that it would even be desirable for priority
>       information to be retained when you cross network boundaries - if
>       someone's a government official in Iraq, when they place a call to
>       the United States, should they be afforded the status of a
>       government official here?"
> 
> Just as with the ISUP "Precedence" parameter, the priority information
> could/should indicate (or be mappable to) the context within which it
> applies.
> 

I don't remember that being a requirement, actually, unless it's implicit in
REQ-1 somehow. I can see how that might follow, but it could stand to be
more explicit in the draft. 

The "strong" reading of REQ-4 entails some sort of end-to-end priority for
the Internet that is expected to apply regardless of context. In this case,
one wonder how you do without the strong reading, given that the Internet
lacks the sort of administrative boundries that would ordinary delimit one
telephony context from another.

> Also, the NCS is actively working within the ITU-T to set aside an
> international CPC so calls may be recognized as emergency or priority at
> international gateways.  The issue of determining which countries should
> receive priority is recognized, and messy. 
> 

I can imagine. My comment above was only intended to speak to that
messiness, not as a characterization of ongoing standards work. The fact
that the Internet is, again, largely independent of geopolitical boundries
makes this still more complex in our problem space.

> "Some additional discussion is necessary to understand why signaling
>    encapsulation is insufficient for CSN-IP-CSN architectures.  If this
>    amounts only to the requirement described in Section 7, then
>    signaling encapsulation may still provide some useful properties to
>    the terminating gateway."
> 
> Signaling encapsulation definitely DOES provide "some useful properties".
> But, as you noted above, it does not allow for making "different routing
> decisions for some calls in the presence of a priority indicator".
> 

No disagreement that proxy servers are unable to route based on the content
of SIP MIME bodies. 

> Sec 2.3  ETS in existing SIP networks
> 
> "This points to a fundamental questions: Is ETS opt-in?"
> 
> Personally, I think it is reasonable to expect that ETS will be "opt-in"
for
> the most part, at least in terms of providing any kind of special
services.
> But I think it is also reasonable to hope that "transparent" networks will
> pass the priority information (directly or encapsulated) even if they do
not
> DO anything with it.  Similarly, I want to make it as easy as possible for
a
> network to make the decision to opt-in.
> 

One question I raise in my draft is how much value there is in having
intermittent priority treatment in the path of the call - which is really a
question about where congestion arises and how to effectively combat it.
Unfortunately, I think that congestion could conceivably appear anywhere in
the path of a call. While having some ETS-aware segments of a call path
improves the odds of completing prioritzed calls, it is very difficult to
anticipate how greatly the odds will be improved, and how successful the
overall system will be in practical emergencies.

Clearly, opting in will involve at the least having special implementations
of network elements and having configurations dictated by the agency
responsible for administering ETS. It may be easy to make the decision to
opt in, but it will not be trivial to bear out. I would strongly maintain
that it will be impossible to force everyone to opt in (it's very unlikely
that my private LAN and its SIP devices will develop a relationship with the
relevant gov't agencies).

> "and even then,
>    there is no guarantee that fully compliant implementations will be
>    ubiquitously deployed, nor configured to behave appropriately in an
>    ETS situation."
> 
> This is true, even in the current CSN, and has not precluded the
> implementation of  a useful, near ubiquitous, service.
> 

The PSTN admits of far greater centralization that the Internet and its
services.

Unless there were a regulatory push that essentially made SIP's core
architecture illegal (by legislating the oversight of monolithic service
providers similar to the current LEC community), it is unlikely that ETS
would ever enjoy near-ubiquitous SIP deployment, in my opinion.

> "...only networks that develop relationships with the
>    relevant government agencies, and are given proper configuration
>    information by those agencies, will do so."
> 
> True, but the hope is to make it as painless as possible for networks to
> develop those relationships.
> 
> 3.1 General Requirements
> 
> REQ-4 "The 'mapping of schemes' requirement could be taken to be
>    strong or weak." 
> 
>  I had interpreted it as "weak", in some ways analogous to the ISUP
> Precedence parameter.
> 

Okay. I think that is more plausible than the strong interpretation.

> REQ-7
> (wrt MLPP in the CSN) "It's never unclear within a certain network
>    how a given element will behave when presented with a prioritization
>    indicator."
> 
> Unfortunately, this is not true.  The standards dictate what SHOULD
happen,
> but the actual implementation often does not reflect the standards.
> 

We in the standards business flatter ourselves too much sometimes that our
standards will be implemented. But the best we can do is to mandate common
behavior and hope that the desire for interoperability will lead to its
implementation. The behavior of particular elements in the standard should
be deterministic - we can't mitigate the risk that implementers will opt for
non-compliance. For the standard to disregard deterministic behavior of
elements seems to invite interoperability failures that might not happen
otherwise.

> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 04:27:35 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25034
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 04:27:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2D9fwb10675
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 04:41:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D9fwO10672
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 04:41:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25028
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 04:27:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D9fIO10641;
	Thu, 13 Mar 2003 04:41:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2D9etO10593
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 04:40:55 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24936
	for <sipping@ietf.org>; Thu, 13 Mar 2003 04:26:01 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2D9RxC12942;
	Thu, 13 Mar 2003 09:27:59 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JTNW0>; Thu, 13 Mar 2003 04:28:16 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F1B@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Henning Schulzrinne'" <hgs@cs.columbia.edu>,
        "Gunn, Janet"
	 <Janet.Gunn@DynCorp.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Date: Thu, 13 Mar 2003 04:28:15 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Well, I hope my draft doesn't miss those points - it was intended to try to
draw them out a bit. I agree that the three 'wants' that you identify below
are all desirable; what the draft questions is whether they are consistent
with the other requirements (in the case of the 2nd want) and whether they
are ultimately achievable.

Especially on the first want, the issue of partial ETS coverage is one that
I think really requires further examination. The system is clearly intended
to increase the chances of call completion, but I think some further
analysis of the effects of partial ETS coverage is required before we can
seriously assess the value added by the ETS concept for SIP. Universal
adoption seems profoundly unlikely to me, so in my mind the important cases
are partial coverage. No doubt it is true that the closer ETS is to the
caller, the better off you are.

Agreed that modeling a SIP prioritization system on GETS is probably
ill-advised.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> Sent: Tuesday, March 11, 2003 4:42 PM
> To: Gunn, Janet
> Cc: sipping@ietf.org
> Subject: Re: [Sipping] Comments on draft-peterson-sipping-ieprep-00
> 
> 
> To amplify what Janet wrote: I think Jon's draft misses the point that 
> we want
> 
> - networks that don't want to play to at least not get in the way (i.e., 
> not prevent delivery of services downstream)
> 
> - require minimal changes to end systems
> 
> - support non-ISUP originators (e.g., SIP soft-terminals)
> 
> It's a nice side benefit if 'joining' ETS is easy, but the primary 
> consideration is that needs it work with standards-compliant SIP 
> elements (in particular, proxies) that are unaware of it.
> 
> It should also have the "earliest possible" property, i.e., as the 
> network becomes ETS-aware, suitable treatment gets applied closer to the 
> caller.
> 
> Thus, success is not measured by whether we get 100% coverage or 
> international coverage, but rather whether I can plug in a SIP terminal 
> or use my laptop and get whatever service I can.
> 
> One could clearly model the SIP solution on the GETS system, by having a 
> "gateway" with a specific SIP address (equivalent to the 710 number), 
> which then prompts for another SIP address or tel URI. From scaling and 
> architectural perspectives, this seems much worse.
> 
> The draft tries to make this clear by emphasizing the different network 
> types.
> 
> Gunn, Janet wrote:
> > My personal (not representing any organization) comments on
> > draft-peterson-sipping-ieprep-00
> > 
> > Some of these comments address details rather than the 
> overall sense, but I
> > think it is important to keep even the details straight.
> > 
> > Section 2-2 Signaling Encapsulation
> > 
> > "In the CSN, it is not possible to
> >       make an emergency call, for example, from France to the United
> >       States.  International ISUP gateways that bridge 
> between different
> >       signaling systems will at best discard priority information."
> > 
> > Actually, it IS possible.  Every month over 3000 GETS 
> (710...) calls are
> > placed from over 50 international locations.  They receive 
> no priority until
> > they get to  US based switch, but most of them DO  receive priority
> > treatment within the US.  Granted, it is the "710" that is 
> passing through
> > the international gateway, but that IS a "priority label" 
> as well as a
> > dialed number, and is not "discarded by the international gateway".
> > 
> > "It's not clear that it would even be desirable for priority
> >       information to be retained when you cross network 
> boundaries - if
> >       someone's a government official in Iraq, when they 
> place a call to
> >       the United States, should they be afforded the status of a
> >       government official here?"
> > 
> > Just as with the ISUP "Precedence" parameter, the priority 
> information
> > could/should indicate (or be mappable to) the context 
> within which it
> > applies.
> > 
> > Also, the NCS is actively working within the ITU-T to set aside an
> > international CPC so calls may be recognized as emergency 
> or priority at
> > international gateways.  The issue of determining which 
> countries should
> > receive priority is recognized, and messy. 
> > 
> > "Some additional discussion is necessary to understand why signaling
> >    encapsulation is insufficient for CSN-IP-CSN 
> architectures.  If this
> >    amounts only to the requirement described in Section 7, then
> >    signaling encapsulation may still provide some useful 
> properties to
> >    the terminating gateway."
> > 
> > Signaling encapsulation definitely DOES provide "some 
> useful properties".
> > But, as you noted above, it does not allow for making 
> "different routing
> > decisions for some calls in the presence of a priority indicator".
> > 
> > Sec 2.3  ETS in existing SIP networks
> > 
> > "This points to a fundamental questions: Is ETS opt-in?"
> > 
> > Personally, I think it is reasonable to expect that ETS 
> will be "opt-in" for
> > the most part, at least in terms of providing any kind of 
> special services.
> > But I think it is also reasonable to hope that 
> "transparent" networks will
> > pass the priority information (directly or encapsulated) 
> even if they do not
> > DO anything with it.  Similarly, I want to make it as easy 
> as possible for a
> > network to make the decision to opt-in.
> > 
> > "and even then,
> >    there is no guarantee that fully compliant 
> implementations will be
> >    ubiquitously deployed, nor configured to behave 
> appropriately in an
> >    ETS situation."
> > 
> > This is true, even in the current CSN, and has not precluded the
> > implementation of  a useful, near ubiquitous, service.
> > 
> > "...only networks that develop relationships with the
> >    relevant government agencies, and are given proper configuration
> >    information by those agencies, will do so."
> > 
> > True, but the hope is to make it as painless as possible 
> for networks to
> > develop those relationships.
> > 
> > 3.1 General Requirements
> > 
> > REQ-4 "The 'mapping of schemes' requirement could be taken to be
> >    strong or weak." 
> > 
> >  I had interpreted it as "weak", in some ways analogous to the ISUP
> > Precedence parameter.
> > 
> > REQ-7
> > (wrt MLPP in the CSN) "It's never unclear within a certain network
> >    how a given element will behave when presented with a 
> prioritization
> >    indicator."
> > 
> > Unfortunately, this is not true.  The standards dictate 
> what SHOULD happen,
> > but the actual implementation often does not reflect the standards.
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 06:37:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27154
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 06:37:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DBptj18732
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 06:51:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DBptO18729
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 06:51:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27119
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 06:36:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DBoKO18665;
	Thu, 13 Mar 2003 06:50:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DBmqO18611
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 06:48:52 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27062
	for <sipping@ietf.org>; Thu, 13 Mar 2003 06:33:56 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2DBZxB3012723;
	Thu, 13 Mar 2003 12:35:59 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id GPHJ978B; Thu, 13 Mar 2003 12:35:59 +0100
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2DBZw6B014886;
	Thu, 13 Mar 2003 13:35:58 +0200 (EET)
Message-ID: <3E706D1C.460BE98E@lmf.ericsson.se>
Date: Thu, 13 Mar 2003 13:35:56 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: zhigang.c.liu@nokia.com
CC: adam@dynamicsoft.com, Markus.Isomaki@nokia.com, mwatson@nortelnetworks.com,
        sipping@ietf.org
Subject: Re: [Sipping] SIGCOMP and large binary content SIP messages
References: <DE0842B293FC4847992F9EDF8D72E1ED24A819@daebe005.americas.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Zhigang,

you can submit that draft to ROHC. SIPPING can review it afterwards.
IMO, the competence needed to generate this draft can be found more
easily in ROHC than in SIPPING.

Besides, you could use SigComp to compress RTSP messages, for instance
And RTSP is not handle by SIPPING either.

Gonzalo

zhigang.c.liu@nokia.com wrote:
> 
> Yes, that is also what I had in mind for SIP. But my point is that
> a SigComp receiver now needs to have some knowledge about application
> message format and do parsing to determine the end of an uncompressed
> message. This is something new (or at least unspecified) in RFC 3320
> and needs to be spelled out in a new (standard track) RFC. The document
> will be short, but I think it's needed for interoperability.
> 
> I'll write up an I-D and submit it after IETF 56. But I'd like to know
> if folks in SIPPING think it should be done here or in ROHC.
> 
> Zhigang
> 
> > -----Original Message-----
> > From: ext Adam Roach [mailto:adam@dynamicsoft.com]
> > Sent: March 11, 2003 9:03 PM
> > To: Liu Zhigang.C (NRC/Dallas); Adam Roach; Isomaki Markus
> > (NRC/Helsinki); mwatson@nortelnetworks.com; sipping@ietf.org
> > Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
> >
> >
> > > -----Original Message-----
> > > From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > >
> > > Having binary content in SIP messages may have two impacts on
> > > SigComp:
> > >
> > > a) multiplexing of uncompressed messages with SigComp
> > messages on the
> > > same port.
> > ...
> > > For a), it is only an issue for SigComp/TCP, not
> > SigComp/UDP (where one
> > > SigComp message maps to one UDP packet). Adam's point 1 and
> > 2 are related
> > > to this. As to point 1, I think the SigComp receiver still
> > needs to know
> > > (somehow) the end of an uncompressed message, or at least
> > the end of the
> > > binary part of each SIP messages. Otherwise, a bit pattern 11111 in
> > > the binary part will be mistaken by SigComp as the
> > beginning of a SigComp
> > > message. As to point 2, I would add that the delimiter
> > 0xFFFF can appear
> > > at the both the beginning and the end of a SigComp message. So, the
> > > receiver needs to have the same parsing logic just mentioned for bit
> > pattern
> > > 11111.
> >
> > This isn't any more of an issue than it is without SigComp. SIP
> > messages provide their own framing, and SigComp messages do the
> > same. They can be trivially mixed on the same stream:
> >
> > 1. Peek at the first byte waiting in the stream.
> >
> > 2. If it is 0xf8 or higher, the next message in the stream is
> >    a SigComp message. The message continues until a 0xFFFF is
> >    encountered in the stream.
> >
> > 3. Otherwise, the next message in the stream is a SIP message.
> >    Read the stream until a CR/LF/CR/LF is encountered. Parse
> >    the headers, and then read the number of bytes specified
> >    in the "Content-Length" header.
> >
> > 4. Return to step 1.
> >
> > /a
> >
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 07:53:45 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28738
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 07:53:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DD8A224625
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 08:08:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DD8AO24622
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 08:08:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28732
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 07:53:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DD5vO23658;
	Thu, 13 Mar 2003 08:05:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DD3aO23492
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 08:03:36 -0500
Received: from mail1.telekom.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28560
	for <sipping@ietf.org>; Thu, 13 Mar 2003 07:48:38 -0500 (EST)
Received: from g8pbr.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Thu, 13 Mar 2003 13:50:47 +0100
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <G43BC5KP>; Thu, 13 Mar 2003 13:50:47 +0100
Message-Id: <953B9B08F98DD61183F8000347AE66011ACC75@G8PPV.blf01.telekom.de>
From: "Jesske, R" <R.Jesske@telekom.de>
To: sgarg@aastra.com, sipping@ietf.org
Subject: AW: [Sipping] RFC 3398: REL cause
Date: Thu, 13 Mar 2003 13:50:44 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2DD3fO23498
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,
both is not correct. (From my point of view)

Because T7 will be started when the latest address message is sent. (See Q.764)

Expiry of T7 is caused due to the fact that no ACM is received (from the destination) because in the destination (normal case) address information is missing.

In Q.699 Table 23(DSS1-ISUP mapping) this case interworking unit is described as following:
Determination that the called number information received is incomplete, after an IAM message has already been sent 
--> therefore REL with Cause 28 is send in forward and Backward direction.

And Q.850 says:

Cause No. 28 - Invalid number format (address incomplete)
This cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete.
NOTE - This condition may be determined:
-	immediately after reception of an end of pulsing (ST) signal; or
-	on time-out after the last received digit.

If this scenario should also apply also for the SIP-ISUP interworking Q.699 could be taken as reference, because Q.764 doesn't point to this fact in the interworking case:
Therefore on the ISUP leg Cause 28 shall be sent and on the SIP leg 484 should be sent, as it is stated in the cause code mapping.

For completeness: In normal cases ISUP Timer T35 will normally expire before T7 will, therefore normally a REL with Cause 28 will be received from the destination. 

Best Regards

Roland



> -----Ursprüngliche Nachricht-----
> Von: Sumit Garg [mailto:sgarg@aastra.com]
> Gesendet: Mittwoch, 12. März 2003 21:48
> An: 'sipping@ietf.org'
> Betreff: [Sipping] RFC 3398: REL cause
> 
> 
> Hi all,
> 
> According to the rfc 3398(SIP-ISUP mapping, section 7.1.3 and 
> 7.2.2),for a
> net to Phone call, when ACM timeout timer
>  (T7- 20 - 30 s) expires, the ISUP leg  REL cause should be 
> 102 (protocol
> error, recovery on timer expiry) and corresponding SIP 
> response should be
> 504 Server Timeout.
> However, if one goes by Q.764 and table 1 of Q.850 the 
> correct REL cause for
> ISUP would be 31(normal unspecified)
> and for the SIP leg it would then correspond to  480 (Temporarily
> Unavailable). Apparently 102 is used mostly for
> SUS-RES.
> 
> What should be the values used?
> 
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> Sumit Garg 
> Aastra Telecom US
> 8 Federal Street 
> Billerica, MA 01821 
> 978-436-4244
> email: <<mailto:sgarg@aastra.com>> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> 
> 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 08:29:46 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29869
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 08:29:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DDiDB27757
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 08:44:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DDiDO27754
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 08:44:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29850
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 08:29:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DDhNO27671;
	Thu, 13 Mar 2003 08:43:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DDgOO27610
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 08:42:24 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29795
	for <sipping@ietf.org>; Thu, 13 Mar 2003 08:27:26 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for sipping@ietf.org; Thu, 13 Mar 2003 08:28:13 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2003031308291708121
 ; Thu, 13 Mar 2003 08:29:17 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <FSPL430P>; Thu, 13 Mar 2003 08:28:57 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77D5E@mcl-its-exs01.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'jon.peterson@neustar.biz'" <jon.peterson@neustar.biz>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>,
        "'hgs@cs.columbia.edu'" <hgs@cs.columbia.edu>
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Date: Thu, 13 Mar 2003 08:29:15 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Jon said:

>The system is clearly intended
>to increase the chances of call completion, but I think some further
>analysis of the effects of partial ETS coverage is required before we can
>seriously assess the value added by the ETS concept for SIP. 

I agree this is important.  Please consider the following.

Suppose there are Internet Telephony Service Providers (or cable operators
offering telephony services) that are willing to modify gateways to the PSTN
to provide preferential access for authorized users.  The idea would be in
times of gateway congestion, authorized users might have advantage in
obtaining resources.  If the providers run stateful proxies, those proxies
could also favor authorized users.  To receive preferential treatment,
authorized users must be customers of these particular providers.  Isn't
this partial ETS coverage potentially useful?

If some government wanted to create a priority scheme over its own priviate
network (e.g., MLPP/Assured Service over government owned network) then is
that reasonable?

Some people from the NGN PSTN camp are thinking about priviate packet
networks for telephony.  They envision trading traffic with their peers in a
manner mirroring their current methods.  (For example, see 
http://www.msforum.org/techinfo/reports/MSF-TR-QoS-001-FINAL.pdf )
Suppose the majority of ETS locations used a handful of providers and those
providers traded traffic as in the MSF report augmented with ETS support.
Given the assumed architecture, would this partial ETS coverage be
potentially useful?  

Is this the type of analysis you seek for partial ETS coverage?  

Kimberly


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 08:43:38 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00251
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 08:43:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DDw5Z28405
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 08:58:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DDw5O28402
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 08:58:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00241
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 08:43:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DDvJO28354;
	Thu, 13 Mar 2003 08:57:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DDuOO28314
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 08:56:24 -0500
Received: from mail.aastra.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00174
	for <sipping@ietf.org>; Thu, 13 Mar 2003 08:41:26 -0500 (EST)
Received: by mail.aastra.com with Internet Mail Service (5.5.2653.19)
	id <1XVB0JHF>; Thu, 13 Mar 2003 08:32:56 -0500
Message-ID: <F924CEFBBF62D611A0C600D0B76ED037157982@cvxmail.ana.aastra.com>
From: Sumit Garg <sgarg@aastra.com>
To: sipping@ietf.org
Subject: RE: [Sipping] RFC 3398: REL cause
Date: Thu, 13 Mar 2003 08:32:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C2E965.099A48B0"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

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

Hi,
I don't quite agree with that.
I believe that if the Address Information was found to be incomplete at =
the
Destn exchng
then the Originating exchange would have recd. a REL with Cause 28 (Due =
to
T35 expiry on the Destn).

Any intermediate/Destn exchng would be generating REL with cause 28 =
only if
they don't
 have information to route the msg.

A timeout would occur on Intermediate/Originating exchng only in =
abnormal
cases like
 hardware failure etc; in this case the address info supplied would =
have
been correct for that exchng (otherwise T35
should have expired and not T7 and we would have got REL cause 28);=20

Thus, I believe REL cause 28 on T7 expiry would again be wrong.

My only issue with 102 is that, this is not the RELEASE cause generated =
in
the scenario in a pure ISUP
network. If we consider a large network with multiple intermediate SS7
exchanges between the destn
and the SS7-SIP gateway; ACM timeout on any one of them would be =
conveyed to
the gateway as 31 and hence
translate to 480.=20
 Thus, I fail to understand why the gateway should behave any =
differently
and convey different release
causes to the SS7 and SIP world. It would be more logical if it just =
sent 31
and 480.

-Sumit



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=20
Sumit Garg=20
Aastra Telecom US
8 Federal Street=20
Billerica, MA 01821=20
978-436-4244
email: <<mailto:sgarg@aastra.com>>=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=20



-----Original Message-----
From: Jesske, R [mailto:R.Jesske@telekom.de]
Sent: Thursday, March 13, 2003 7:51 AM
To: sgarg@aastra.com; sipping@ietf.org
Subject: AW: [Sipping] RFC 3398: REL cause


Hi,
both is not correct. (From my point of view)

Because T7 will be started when the latest address message is sent. =
(See
Q.764)

Expiry of T7 is caused due to the fact that no ACM is received (from =
the
destination) because in the destination (normal case) address =
information is
missing.

In Q.699 Table 23(DSS1-ISUP mapping) this case interworking unit is
described as following:
Determination that the called number information received is =
incomplete,
after an IAM message has already been sent=20
--> therefore REL with Cause 28 is send in forward and Backward =
direction.

And Q.850 says:

Cause No. 28 - Invalid number format (address incomplete)
This cause indicates that the called party cannot be reached because =
the
called party number is not in a valid format or is not complete.
NOTE - This condition may be determined:
-	immediately after reception of an end of pulsing (ST) signal; or
-	on time-out after the last received digit.

If this scenario should also apply also for the SIP-ISUP interworking =
Q.699
could be taken as reference, because Q.764 doesn't point to this fact =
in the
interworking case:
Therefore on the ISUP leg Cause 28 shall be sent and on the SIP leg 484
should be sent, as it is stated in the cause code mapping.

For completeness: In normal cases ISUP Timer T35 will normally expire =
before
T7 will, therefore normally a REL with Cause 28 will be received from =
the
destination.=20

Best Regards

Roland



> -----Urspr=FCngliche Nachricht-----
> Von: Sumit Garg [mailto:sgarg@aastra.com]
> Gesendet: Mittwoch, 12. M=E4rz 2003 21:48
> An: 'sipping@ietf.org'
> Betreff: [Sipping] RFC 3398: REL cause
>=20
>=20
> Hi all,
>=20
> According to the rfc 3398(SIP-ISUP mapping, section 7.1.3 and=20
> 7.2.2),for a
> net to Phone call, when ACM timeout timer
>  (T7- 20 - 30 s) expires, the ISUP leg  REL cause should be=20
> 102 (protocol
> error, recovery on timer expiry) and corresponding SIP=20
> response should be
> 504 Server Timeout.
> However, if one goes by Q.764 and table 1 of Q.850 the=20
> correct REL cause for
> ISUP would be 31(normal unspecified)
> and for the SIP leg it would then correspond to  480 (Temporarily
> Unavailable). Apparently 102 is used mostly for
> SUS-RES.
>=20
> What should be the values used?
>=20
>=20
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=20
> Sumit Garg=20
> Aastra Telecom US
> 8 Federal Street=20
> Billerica, MA 01821=20
> 978-436-4244
> email: <<mailto:sgarg@aastra.com>>=20
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=20
>=20
>=20
>=20


------_=_NextPart_000_01C2E965.099A48B0
Content-Type: application/octet-stream;
	name="Sumit Garg.vcf"
Content-Disposition: attachment;
	filename="Sumit Garg.vcf"

BEGIN:VCARD
VERSION:2.1
N:Garg;Sumit
FN:Sumit Garg
ORG:Aastra Network Access
NOTE:Aastra CVX
TEL;WORK;VOICE:978-436-4244
ADR;WORK:;Boston;8 Federal Street;Billerica;MA;1821;USA
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Boston=0D=0A8 Federal Street=0D=0ABillerica, MA 1821=0D=0AUSA
EMAIL;PREF;INTERNET:sgarg@aastra.com
REV:20021122T160021Z
END:VCARD

------_=_NextPart_000_01C2E965.099A48B0--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 09:01:46 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00773
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 09:01:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DEGE430044
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 09:16:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DEGEO30041
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 09:16:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00753
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 09:01:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DEFXO30012;
	Thu, 13 Mar 2003 09:15:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DECUO29877
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 09:12:30 -0500
Received: from acmepacket.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00612
	for <sipping@ietf.org>; Thu, 13 Mar 2003 08:57:31 -0500 (EST)
Received: from BPenfield [127.0.0.1] by acmepacket.com
  (SMTPD32-7.14) id AECC81410238; Thu, 13 Mar 2003 08:59:40 -0500
Message-ID: <002801c2e968$c271e570$2300000a@BPenfield>
From: "Bob Penfield" <bpenfield@acmepacket.com>
To: "Peterson, Jon" <jon.peterson@neustar.biz>
Cc: <sipping@ietf.org>
References: <15A2739B7DAA624D8091C65981D7DA8101214F15@stntexch2.va.neustar.com>
Subject: Re: [Sipping] New version of the early media draft
Date: Thu, 13 Mar 2003 08:59:26 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I have been watching this discussion with great interest, but I have to say
that I agree pretty much with what Jon is saying. It seems to me there are a
few simple rules to follow:

1) If the UAS does not want the UAC to play media, then the UAS should not
send media. I still cannot figure out why a UAS would send media if it does
not want it played.

2) If the UAC receives media, it should play it. This becomes very important
if the call ends up at some announcement server (or the American Airlines
IVR system) that is playing media that the caller needs to hear.

I do however think that Alerting in the PSTN does equate to 180 in SIP. 180
should only be sent by the UAS when the called party is being alerted
(whether the UAS sends media or not). When there is no media, I as the user
of the UAC would want the "rendering" of a "ringing" indication to be
accurate. Also, not all UACs have a human user. If the UAS does not know
that it is ringing, it should not lie to the UAC and say it is. I'm not
saying it has to be absolute. If the UAS "believes" it is ringing it can
send 180.

cheers,
(-:bob

Robert F. Penfield
Chief Software Architect
Acme Packet, Inc.
130 New Boston Street
Woburn, MA 01801
bpenfield@acmepacket.com

----- Original Message -----
From: "Peterson, Jon" <jon.peterson@neustar.biz>


> Let me see if I can put this is a slightly simpler light. Let's ignore
what
> SIP status code the gateway sends for a moment.
>
> A gateway UAS needs to decide whether it's going to send pre-answer media
> media or not. What I've heard you saying is that the indicators in ISUP
> don't provide this information (presumably that the 'in-band status
> indicator' in OBCI doesn't have to be present in order for the PSTN to
send
> in-band status, just sending 'subscriber free' in BCI is enough). All
right,
> let's grant that for a moment.
>
> So how does the gateway decide whether or not it's going to send media?
I've
> heard that ISUP doesn't tell you this, and that in-band media detection at
> the UAS gateway is unacceptable.
>
> What's the point of proposing some indicator (regardless of where it
> appears) that a gateway UAS can send to the UAC signifying pre-answer
media
> if the gateway has no deterministic way of figuring out whether or not it
> should send media?
>
> The value you ascribe to the UAC knowing that the state is 'alerting'
while
> still receiving in-band status information is also a little curious to me.
> It might be useful in PSTN-SIP-PSTN cases for a UAC gateway to know that
the
> UAS gateway is in the PSTN state 'alerting', but of course that can be
> accommodated with RFC3204. I'm not sure how great the value of
communicating
> the alerting state is for SIP in other cases, though, when in-band media
> contains the real indication of the state of the call. It's not as if that
> state information can replace the in-band status information, right?
>
> The conclusion is, if there is a deterministic way for the UAS GW to know
> the state of a call, we can provide a mapping for it with our existing
> mechanics. If there's not, this whole discussion is moot, because then the
> gateway never knows the state of the call, your recommendation would have
to
> be that you send 183 and media for every call that comes through the
gateway
> UAS. That would be a very ill-advised recommendation to make, in my
> estimation.
>
> Some more inline.
>
> Jon Peterson
> NeuStar, Inc.
>
<previous messages trimmed, please consult the archive>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 09:06:15 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00867
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 09:06:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DEKhl30285
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 09:20:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DEKhO30282
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 09:20:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00848
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 09:05:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DEK5O30256;
	Thu, 13 Mar 2003 09:20:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DEJsO30184
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 09:19:54 -0500
Received: from mailgate.siemenscomms.co.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00820
	for <sipping@ietf.org>; Thu, 13 Mar 2003 09:04:55 -0500 (EST)
Received: from CONVERSION-DAEMON.siemenscomms.co.uk by siemenscomms.co.uk
 (PMDF V6.0-24 #45905) id <0HBO00701XV2HH@siemenscomms.co.uk> for
 sipping@ietf.org; Thu, 13 Mar 2003 14:06:38 +0000 (GMT)
Received: from beex10.siemenscomms.co.uk ([137.223.246.252])
 by siemenscomms.co.uk (PMDF V6.0-24 #45905)
 with ESMTP id <0HBO0075FXV2F0@siemenscomms.co.uk>; Thu,
 13 Mar 2003 14:06:38 +0000 (GMT)
Received: by beex10.siemenscomms.co.uk with Internet Mail Service (5.5.2650.21)
	id <G2S4J6L7>; Thu, 13 Mar 2003 14:07:03 +0000
Content-return: allowed
Date: Thu, 13 Mar 2003 14:07:13 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sipping] New version of the early media draft
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Message-id: <DE9048A49FFFE547BBC42F855DC8CC3740C1FB@beex53.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Jon,
 
You wrote:
 
<snip>
Let me see if I can put this is a slightly simpler light. Let's ignore what
SIP status code the gateway sends for a moment.
 
A gateway UAS needs to decide whether it's going to send pre-answer media
media or not. What I've heard you saying is that the indicators in ISUP
don't provide this information (presumably that the 'in-band status
indicator' in OBCI doesn't have to be present in order for the PSTN to send
in-band status, just sending 'subscriber free' in BCI is enough). All right,
let's grant that for a moment.
 
So how does the gateway decide whether or not it's going to send media? I've
heard that ISUP doesn't tell you this, and that in-band media detection at
the UAS gateway is unacceptable.
 
What's the point of proposing some indicator (regardless of where it
appears) that a gateway UAS can send to the UAC signifying pre-answer media
if the gateway has no deterministic way of figuring out whether or not it
should send media? 
</snip>
 
From a QSIG perspective (I believe ISUP is similar) the gateway DOES have a
way of figuring out whether it should send media. There is an explicit
indicator in QSIG that says that in-band media is present. Also there is an
explicit QSIG message that indicates that an alerting state has been
reached. The indication of in-band media can be sent with or without
indication of the alerting state. Therefore there are basically 3 things
that the gateway has the capability of signalling, if SIP allows it to:
 
1. Alerting - no media - 180 satisfies this
2. No state change (not alerting) - media present - 183 satisfies this
3. Alerting - media present - ????
 
The third possibility does not have a satisfactory solution. At present the
qsig2sip draft uses 180 for this and relies on the UAC detecting early media
and playing it in preference to local media. However, this is not very
satisfactory, for reasons that Mark Watson has given. An additional
indicator to include in 180 to say that in-band media is present would be
helpful.
 
John Elwell ( john.elwell@siemens.com <mailto:john.elwell@siemens.com> )
 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 09:31:50 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01829
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 09:31:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DEkI932428
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 09:46:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DEkIO32425
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 09:46:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01815
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 09:31:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DEjWO32348;
	Thu, 13 Mar 2003 09:45:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DEipO32271
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 09:44:51 -0500
Received: from pmesmtp01.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01698
	for <sipping@ietf.org>; Thu, 13 Mar 2003 09:29:51 -0500 (EST)
Received: from dgismtp01.wcomnet.com ([166.38.58.141])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HBO00GJ0YZCRF@firewall.wcom.com> for sipping@ietf.org; Thu,
 13 Mar 2003 14:30:49 +0000 (GMT)
Received: from dgismtp01.wcomnet.com by dgismtp01.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HBO00C01YY6GK@dgismtp01.wcomnet.com>; Thu,
 13 Mar 2003 14:30:48 +0000 (GMT)
Received: from hsinnreich2 ([166.50.97.30])
 by dgismtp01.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HBO006NJY562B@dgismtp01.wcomnet.com>; Thu,
 13 Mar 2003 14:30:12 +0000 (GMT)
Date: Thu, 13 Mar 2003 08:30:12 -0600
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
In-reply-to: 
 <B8030EB94AF1D51196D70002A589D64207E77D5E@mcl-its-exs01.mail.saic.com>
To: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>,
        jon.peterson@neustar.biz
Cc: sipping@ietf.org, hgs@cs.columbia.edu
Message-id: <000b01c2e96d$0f4c2230$1e6132a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>Some people from the NGN PSTN camp are thinking about 
>priviate packet networks for telephony.

We could actually each of us have our own network and not communicate
with anyone :-)

Henry

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of King, Kimberly S.
> Sent: Thursday, March 13, 2003 7:29 AM
> To: 'jon.peterson@neustar.biz'
> Cc: 'sipping@ietf.org'; 'hgs@cs.columbia.edu'
> Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
> 
> 
> Jon said:
> 
> >The system is clearly intended
> >to increase the chances of call completion, but I think some further 
> >analysis of the effects of partial ETS coverage is required 
> before we 
> >can seriously assess the value added by the ETS concept for SIP.
> 
> I agree this is important.  Please consider the following.
> 
> Suppose there are Internet Telephony Service Providers (or 
> cable operators offering telephony services) that are willing 
> to modify gateways to the PSTN to provide preferential access 
> for authorized users.  The idea would be in times of gateway 
> congestion, authorized users might have advantage in 
> obtaining resources.  If the providers run stateful proxies, 
> those proxies could also favor authorized users.  To receive 
> preferential treatment, authorized users must be customers of 
> these particular providers.  Isn't this partial ETS coverage 
> potentially useful?
> 
> If some government wanted to create a priority scheme over 
> its own priviate network (e.g., MLPP/Assured Service over 
> government owned network) then is that reasonable?
> 
> Some people from the NGN PSTN camp are thinking about 
> priviate packet networks for telephony.  They envision 
> trading traffic with their peers in a manner mirroring their 
> current methods.  (For example, see 
> http://www.msforum.org/techinfo/reports/MSF-TR-QoS-001-FINAL.p
> df ) Suppose the majority of ETS locations used a handful of 
> providers and those providers traded traffic as in the MSF 
> report augmented with ETS support. Given the assumed 
> architecture, would this partial ETS coverage be potentially useful?  
> 
> Is this the type of analysis you seek for partial ETS coverage?  
> 
> Kimberly
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 09:35:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02025
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 09:35:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DEoHf32691
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 09:50:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DEoHO32688
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 09:50:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01983
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 09:35:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DEnBO32603;
	Thu, 13 Mar 2003 09:49:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DEkjO32463
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 09:46:45 -0500
Received: from marionberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01827
	for <sipping@ietf.org>; Thu, 13 Mar 2003 09:31:45 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(user=hgs10 mech=PLAIN bits=0)
	by marionberry.cc.columbia.edu (8.12.8/8.12.8) with ESMTP id h2DEXsNI024878
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 13 Mar 2003 09:33:55 -0500 (EST)
Message-ID: <3E7096DD.2080808@cs.columbia.edu>
Date: Thu, 13 Mar 2003 09:34:05 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "King, Kimberly S." <KIMBERLY.S.KING@saic.com>
CC: "'jon.peterson@neustar.biz'" <jon.peterson@neustar.biz>,
        "'sipping@ietf.org'" <sipping@ietf.org>
Subject: Re: [Sipping] Comments on draft-peterson-sipping-ieprep-00
References: <B8030EB94AF1D51196D70002A589D64207E77D5E@mcl-its-exs01.mail.saic.com>
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77D5E@mcl-its-exs01.mail.saic.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Since partial coverage seems to be the crux of the matter, let me try to 
add a few words. We should probably be careful to distinguish three 
types of 'partial coverage', as their likely effect on ETS will differ.

(1) UAS as PSTN gateways

First, we can have partial coverage in PSTN gateways. Clearly, if all my 
calls are routed to a non-ETS gateway, then all the indications in the 
world, however done, are pointless. Until all or almost all gateways 
support ETS, deployments may need to force call routing and avoid the 
use of default gateway discovery (i.e., tel URIs.). Since I can discover 
gateway support, a smart end system could try default routing first and 
if that fails, use source routing to reach a known entry point.

This offers a transition mechanism that improves as deployment improves. 
(This is somewhat similar to the need to dial 1010xxx to reach a 
710-aware carrier in the GETS system.)

(2) UAS as SIP devices, but not gateways

Some people have pointed out that it would be useful to have SIP 
endpoints, such as IP phones or ACD systems, handle ETS calls 
differently, from flashing an orange light to bypassing the call queue. 
Again, while universal coverage is nice, the alternative of not 
indicating ETS is no better. After all, existing ETS systems also have 
the problem that phone end systems may not know that the call is an ETS 
call and are still useful.

(3) Partial coverage in proxies

This matters in two ways, depending on how proxies use the RP 
indication. If it's used for routing, the need depends on issue (1). You 
could either have lots of RP-aware proxies and relatively few 
specialized gateways or the converse. (If all gateways are RP-aware, 
proxy routing isn't all that important.)

Proxies could use RP for prioritized call handling to deal with 
signaling overload.

I think in all cases, the issue is increased *probability* of call 
completion. I can't see how partial deployment could be worse than no 
deployment, particularly if the most-likely-to-be-scarce resources are 
enabled first. My guess is that those scarce resources are the 
gateways/PSTN circuits, where we have a reasonable chance of making this 
work. This would not require international cooperation - indeed, as long 
as the Internet side stays up, this may make calls from abroad into a 
national ETS system far more likely to work. I think that type of 
international usage is the more likely one (officials traveling abroad, 
etc.).

Clearly, the access links from the SIP endpoint to the gateway could be 
congested, but the experts in IEPREP tell us that the Internet never 
gets congested, so this is nothing to be concerned about. (In any event, 
it's not the concern of the mechanism under discussion here.)

Henning

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 10:45:08 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06077
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 10:45:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DFxcV06146
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 10:59:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DFxcO06143
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 10:59:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06071
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 10:44:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DFwUO06091;
	Thu, 13 Mar 2003 10:58:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DFw0O06063
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 10:58:00 -0500
Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05958
	for <sipping@ietf.org>; Thu, 13 Mar 2003 10:42:58 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by ihemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2DFj7f18133
	for <sipping@ietf.org>; Thu, 13 Mar 2003 10:45:08 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <XNTCRYLW>; Thu, 13 Mar 2003 15:45:06 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EC62@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'Sumit Garg'" <sgarg@aastra.com>, sipping@ietf.org
Subject: RE: [Sipping] RFC 3398: REL cause
Date: Thu, 13 Mar 2003 15:45:04 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

I had some problem trying to identify the problem that is trying to be solved here, and that is because it is out of scope.

The text in section 7.2.2 of RFC 3398, that states

"A REL message with cause value 102 (protocol error,
   recovery on timer expiry) SHOULD be sent to the PSTN. "

is a purely ISUP / BICC protocol procedure and nothing to do with any interworking. Interworking documents should not attempt to rewrite the protocols on either side of the interworking point. Therefore this sentence SHOULD be deleted from any future version of RFC 3398. Can the authors please note this in the appropriate bug list.

Looking at the BICC specification, I cannot actually see a point where it specifies a cause value to be included in the ISUP REL message, and therefore presumably it is up to the implementor to choose an appropriate one. 

I would believe that #28 would be inappropriate, but that belief is irrelevant to this list, as this is an ISUP response to an ISUP timer expiry.

For 7.1.3, I guess these are more informative, although I would have preferred a different terminology to "MG Releases PSTN Trunk" which implies to me that the trunk is released as part of interworking, when it is a purely ISUP / BICC protocol action that is causing this.


Keith

Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 

> -----Original Message-----
> From: Sumit Garg [mailto:sgarg@aastra.com]
> Sent: 13 March 2003 13:33
> To: sipping@ietf.org
> Subject: RE: [Sipping] RFC 3398: REL cause
> 
> 
> Hi,
> I don't quite agree with that.
> I believe that if the Address Information was found to be 
> incomplete at the
> Destn exchng
> then the Originating exchange would have recd. a REL with 
> Cause 28 (Due to
> T35 expiry on the Destn).
> 
> Any intermediate/Destn exchng would be generating REL with 
> cause 28 only if
> they don't
>  have information to route the msg.
> 
> A timeout would occur on Intermediate/Originating exchng only 
> in abnormal
> cases like
>  hardware failure etc; in this case the address info supplied 
> would have
> been correct for that exchng (otherwise T35
> should have expired and not T7 and we would have got REL cause 28); 
> 
> Thus, I believe REL cause 28 on T7 expiry would again be wrong.
> 
> My only issue with 102 is that, this is not the RELEASE cause 
> generated in
> the scenario in a pure ISUP
> network. If we consider a large network with multiple intermediate SS7
> exchanges between the destn
> and the SS7-SIP gateway; ACM timeout on any one of them would 
> be conveyed to
> the gateway as 31 and hence
> translate to 480. 
>  Thus, I fail to understand why the gateway should behave any 
> differently
> and convey different release
> causes to the SS7 and SIP world. It would be more logical if 
> it just sent 31
> and 480.
> 
> -Sumit
> 
> 
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> Sumit Garg 
> Aastra Telecom US
> 8 Federal Street 
> Billerica, MA 01821 
> 978-436-4244
> email: <<mailto:sgarg@aastra.com>> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> 
> 
> 
> -----Original Message-----
> From: Jesske, R [mailto:R.Jesske@telekom.de]
> Sent: Thursday, March 13, 2003 7:51 AM
> To: sgarg@aastra.com; sipping@ietf.org
> Subject: AW: [Sipping] RFC 3398: REL cause
> 
> 
> Hi,
> both is not correct. (From my point of view)
> 
> Because T7 will be started when the latest address message is 
> sent. (See
> Q.764)
> 
> Expiry of T7 is caused due to the fact that no ACM is 
> received (from the
> destination) because in the destination (normal case) address 
> information is
> missing.
> 
> In Q.699 Table 23(DSS1-ISUP mapping) this case interworking unit is
> described as following:
> Determination that the called number information received is 
> incomplete,
> after an IAM message has already been sent 
> --> therefore REL with Cause 28 is send in forward and 
> Backward direction.
> 
> And Q.850 says:
> 
> Cause No. 28 - Invalid number format (address incomplete)
> This cause indicates that the called party cannot be reached 
> because the
> called party number is not in a valid format or is not complete.
> NOTE - This condition may be determined:
> -	immediately after reception of an end of pulsing (ST) signal; or
> -	on time-out after the last received digit.
> 
> If this scenario should also apply also for the SIP-ISUP 
> interworking Q.699
> could be taken as reference, because Q.764 doesn't point to 
> this fact in the
> interworking case:
> Therefore on the ISUP leg Cause 28 shall be sent and on the 
> SIP leg 484
> should be sent, as it is stated in the cause code mapping.
> 
> For completeness: In normal cases ISUP Timer T35 will 
> normally expire before
> T7 will, therefore normally a REL with Cause 28 will be 
> received from the
> destination. 
> 
> Best Regards
> 
> Roland
> 
> 
> 
> > -----Ursprüngliche Nachricht-----
> > Von: Sumit Garg [mailto:sgarg@aastra.com]
> > Gesendet: Mittwoch, 12. März 2003 21:48
> > An: 'sipping@ietf.org'
> > Betreff: [Sipping] RFC 3398: REL cause
> > 
> > 
> > Hi all,
> > 
> > According to the rfc 3398(SIP-ISUP mapping, section 7.1.3 and 
> > 7.2.2),for a
> > net to Phone call, when ACM timeout timer
> >  (T7- 20 - 30 s) expires, the ISUP leg  REL cause should be 
> > 102 (protocol
> > error, recovery on timer expiry) and corresponding SIP 
> > response should be
> > 504 Server Timeout.
> > However, if one goes by Q.764 and table 1 of Q.850 the 
> > correct REL cause for
> > ISUP would be 31(normal unspecified)
> > and for the SIP leg it would then correspond to  480 (Temporarily
> > Unavailable). Apparently 102 is used mostly for
> > SUS-RES.
> > 
> > What should be the values used?
> > 
> > 
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> > Sumit Garg 
> > Aastra Telecom US
> > 8 Federal Street 
> > Billerica, MA 01821 
> > 978-436-4244
> > email: <<mailto:sgarg@aastra.com>> 
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> > 
> > 
> > 
> 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 10:54:19 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06419
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 10:54:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DG8n307412
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 11:08:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DG8nO07409
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 11:08:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06393
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 10:53:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DG87O07345;
	Thu, 13 Mar 2003 11:08:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DG7bO07193
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 11:07:37 -0500
Received: from mgw-dax1.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06356;
	Thu, 13 Mar 2003 10:52:35 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax1.ext.nokia.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2DFsla11330;
	Thu, 13 Mar 2003 09:54:47 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60f3362a52ac12f254079@davir01nok.americas.nokia.com>;
 Thu, 13 Mar 2003 09:54:33 -0600
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 13 Mar 2003 09:54:33 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Thu, 13 Mar 2003 09:54:31 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED0133E0CB@daebe005.americas.nokia.com>
Thread-Topic: [Sipping] SIGCOMP and large binary content SIP messages
Thread-Index: AcLpVL875wZKKes8SNWZDhb0yP7KAQAIsPiA
To: <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: <adam@dynamicsoft.com>, <Markus.Isomaki@nokia.com>,
        <mwatson@nortelnetworks.com>, <sipping@ietf.org>, <rohc@ietf.org>
X-OriginalArrivalTime: 13 Mar 2003 15:54:33.0304 (UTC) FILETIME=[D70C2580:01C2E978]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2DG7bO07198
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

I agree. How to handling binary content is a generic issue for any
application messages. What I have in mind is to give generic 
descriptions/requirements (mainly on the SigComp receiver parsing part),
then touch on SIP (perhaps RTSP too) as a particular example.

Unless someone objects, I'll submit it in ROHC.

Zhigang


> -----Original Message-----
> From: ext Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: March 13, 2003 5:36 AM
> To: Liu Zhigang.C (NRC/Dallas)
> Cc: adam@dynamicsoft.com; Isomaki Markus (NRC/Helsinki);
> mwatson@nortelnetworks.com; sipping@ietf.org
> Subject: Re: [Sipping] SIGCOMP and large binary content SIP messages
> 
> 
> Zhigang,
> 
> you can submit that draft to ROHC. SIPPING can review it afterwards.
> IMO, the competence needed to generate this draft can be found more
> easily in ROHC than in SIPPING.
> 
> Besides, you could use SigComp to compress RTSP messages, for instance
> And RTSP is not handle by SIPPING either.
> 
> Gonzalo
> 
> zhigang.c.liu@nokia.com wrote:
> > 
> > Yes, that is also what I had in mind for SIP. But my point is that
> > a SigComp receiver now needs to have some knowledge about 
> application
> > message format and do parsing to determine the end of an 
> uncompressed
> > message. This is something new (or at least unspecified) in RFC 3320
> > and needs to be spelled out in a new (standard track) RFC. 
> The document
> > will be short, but I think it's needed for interoperability.
> > 
> > I'll write up an I-D and submit it after IETF 56. But I'd 
> like to know
> > if folks in SIPPING think it should be done here or in ROHC.
> > 
> > Zhigang
> > 
> > > -----Original Message-----
> > > From: ext Adam Roach [mailto:adam@dynamicsoft.com]
> > > Sent: March 11, 2003 9:03 PM
> > > To: Liu Zhigang.C (NRC/Dallas); Adam Roach; Isomaki Markus
> > > (NRC/Helsinki); mwatson@nortelnetworks.com; sipping@ietf.org
> > > Subject: RE: [Sipping] SIGCOMP and large binary content 
> SIP messages
> > >
> > >
> > > > -----Original Message-----
> > > > From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > > >
> > > > Having binary content in SIP messages may have two impacts on
> > > > SigComp:
> > > >
> > > > a) multiplexing of uncompressed messages with SigComp
> > > messages on the
> > > > same port.
> > > ...
> > > > For a), it is only an issue for SigComp/TCP, not
> > > SigComp/UDP (where one
> > > > SigComp message maps to one UDP packet). Adam's point 1 and
> > > 2 are related
> > > > to this. As to point 1, I think the SigComp receiver still
> > > needs to know
> > > > (somehow) the end of an uncompressed message, or at least
> > > the end of the
> > > > binary part of each SIP messages. Otherwise, a bit 
> pattern 11111 in
> > > > the binary part will be mistaken by SigComp as the
> > > beginning of a SigComp
> > > > message. As to point 2, I would add that the delimiter
> > > 0xFFFF can appear
> > > > at the both the beginning and the end of a SigComp 
> message. So, the
> > > > receiver needs to have the same parsing logic just 
> mentioned for bit
> > > pattern
> > > > 11111.
> > >
> > > This isn't any more of an issue than it is without SigComp. SIP
> > > messages provide their own framing, and SigComp messages do the
> > > same. They can be trivially mixed on the same stream:
> > >
> > > 1. Peek at the first byte waiting in the stream.
> > >
> > > 2. If it is 0xf8 or higher, the next message in the stream is
> > >    a SigComp message. The message continues until a 0xFFFF is
> > >    encountered in the stream.
> > >
> > > 3. Otherwise, the next message in the stream is a SIP message.
> > >    Read the stream until a CR/LF/CR/LF is encountered. Parse
> > >    the headers, and then read the number of bytes specified
> > >    in the "Content-Length" header.
> > >
> > > 4. Return to step 1.
> > >
> > > /a
> > >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> 
> -- 
> Gonzalo Camarillo         Phone :  +358  9 299 33 71
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> Telecom R&D               Fax   :  +358  9 299 30 52
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> Finland                   http://www.hut.fi/~gonzalo
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 10:55:16 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06488
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 10:55:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DG9lm07474
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 11:09:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DG9lO07471
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 11:09:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06464
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 10:54:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DG95O07441;
	Thu, 13 Mar 2003 11:09:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DG8VO07404
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 11:08:31 -0500
Received: from mail.aastra.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06389
	for <sipping@ietf.org>; Thu, 13 Mar 2003 10:53:29 -0500 (EST)
Received: by mail.aastra.com with Internet Mail Service (5.5.2653.19)
	id <1XVB0J7X>; Thu, 13 Mar 2003 10:45:00 -0500
Message-ID: <F924CEFBBF62D611A0C600D0B76ED037157983@cvxmail.ana.aastra.com>
From: Sumit Garg <sgarg@aastra.com>
To: "'Drage, Keith (Keith)'" <drage@lucent.com>, sipping@ietf.org
Subject: RE: [Sipping] RFC 3398: REL cause
Date: Thu, 13 Mar 2003 10:44:52 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C2E977.7CA344D0"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_000_01C2E977.7CA344D0
Content-Type: text/plain;
	charset="iso-8859-1"


I totally agree with you on that. RFC 3398 should try to change ISUP
protocol.
Q.764 does not mention any specific Release cause but the one indicated by
Q.850 (Table 1)
seems to be 31.

The text in section 7.2.2 of RFC 3398, that states

"A REL message with cause value 102 (protocol error,
   recovery on timer expiry) SHOULD be sent to the PSTN. "

thus, caused the confusion.
All will be well if it were removed from the next version.

-Sumit
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Sumit Garg 
Aastra Telecom US
8 Federal Street 
Billerica, MA 01821 
978-436-4244
email: <<mailto:sgarg@aastra.com>> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 



-----Original Message-----
From: Drage, Keith (Keith) [mailto:drage@lucent.com]
Sent: Thursday, March 13, 2003 10:45 AM
To: 'Sumit Garg'; sipping@ietf.org
Subject: RE: [Sipping] RFC 3398: REL cause


I had some problem trying to identify the problem that is trying to be
solved here, and that is because it is out of scope.

The text in section 7.2.2 of RFC 3398, that states

"A REL message with cause value 102 (protocol error,
   recovery on timer expiry) SHOULD be sent to the PSTN. "

is a purely ISUP / BICC protocol procedure and nothing to do with any
interworking. Interworking documents should not attempt to rewrite the
protocols on either side of the interworking point. Therefore this sentence
SHOULD be deleted from any future version of RFC 3398. Can the authors
please note this in the appropriate bug list.

Looking at the BICC specification, I cannot actually see a point where it
specifies a cause value to be included in the ISUP REL message, and
therefore presumably it is up to the implementor to choose an appropriate
one. 

I would believe that #28 would be inappropriate, but that belief is
irrelevant to this list, as this is an ISUP response to an ISUP timer
expiry.

For 7.1.3, I guess these are more informative, although I would have
preferred a different terminology to "MG Releases PSTN Trunk" which implies
to me that the trunk is released as part of interworking, when it is a
purely ISUP / BICC protocol action that is causing this.


Keith

Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 

> -----Original Message-----
> From: Sumit Garg [mailto:sgarg@aastra.com]
> Sent: 13 March 2003 13:33
> To: sipping@ietf.org
> Subject: RE: [Sipping] RFC 3398: REL cause
> 
> 
> Hi,
> I don't quite agree with that.
> I believe that if the Address Information was found to be 
> incomplete at the
> Destn exchng
> then the Originating exchange would have recd. a REL with 
> Cause 28 (Due to
> T35 expiry on the Destn).
> 
> Any intermediate/Destn exchng would be generating REL with 
> cause 28 only if
> they don't
>  have information to route the msg.
> 
> A timeout would occur on Intermediate/Originating exchng only 
> in abnormal
> cases like
>  hardware failure etc; in this case the address info supplied 
> would have
> been correct for that exchng (otherwise T35
> should have expired and not T7 and we would have got REL cause 28); 
> 
> Thus, I believe REL cause 28 on T7 expiry would again be wrong.
> 
> My only issue with 102 is that, this is not the RELEASE cause 
> generated in
> the scenario in a pure ISUP
> network. If we consider a large network with multiple intermediate SS7
> exchanges between the destn
> and the SS7-SIP gateway; ACM timeout on any one of them would 
> be conveyed to
> the gateway as 31 and hence
> translate to 480. 
>  Thus, I fail to understand why the gateway should behave any 
> differently
> and convey different release
> causes to the SS7 and SIP world. It would be more logical if 
> it just sent 31
> and 480.
> 
> -Sumit
> 
> 
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> Sumit Garg 
> Aastra Telecom US
> 8 Federal Street 
> Billerica, MA 01821 
> 978-436-4244
> email: <<mailto:sgarg@aastra.com>> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> 
> 
> 
> -----Original Message-----
> From: Jesske, R [mailto:R.Jesske@telekom.de]
> Sent: Thursday, March 13, 2003 7:51 AM
> To: sgarg@aastra.com; sipping@ietf.org
> Subject: AW: [Sipping] RFC 3398: REL cause
> 
> 
> Hi,
> both is not correct. (From my point of view)
> 
> Because T7 will be started when the latest address message is 
> sent. (See
> Q.764)
> 
> Expiry of T7 is caused due to the fact that no ACM is 
> received (from the
> destination) because in the destination (normal case) address 
> information is
> missing.
> 
> In Q.699 Table 23(DSS1-ISUP mapping) this case interworking unit is
> described as following:
> Determination that the called number information received is 
> incomplete,
> after an IAM message has already been sent 
> --> therefore REL with Cause 28 is send in forward and 
> Backward direction.
> 
> And Q.850 says:
> 
> Cause No. 28 - Invalid number format (address incomplete)
> This cause indicates that the called party cannot be reached 
> because the
> called party number is not in a valid format or is not complete.
> NOTE - This condition may be determined:
> -	immediately after reception of an end of pulsing (ST) signal; or
> -	on time-out after the last received digit.
> 
> If this scenario should also apply also for the SIP-ISUP 
> interworking Q.699
> could be taken as reference, because Q.764 doesn't point to 
> this fact in the
> interworking case:
> Therefore on the ISUP leg Cause 28 shall be sent and on the 
> SIP leg 484
> should be sent, as it is stated in the cause code mapping.
> 
> For completeness: In normal cases ISUP Timer T35 will 
> normally expire before
> T7 will, therefore normally a REL with Cause 28 will be 
> received from the
> destination. 
> 
> Best Regards
> 
> Roland
> 
> 
> 
> > -----Ursprüngliche Nachricht-----
> > Von: Sumit Garg [mailto:sgarg@aastra.com]
> > Gesendet: Mittwoch, 12. März 2003 21:48
> > An: 'sipping@ietf.org'
> > Betreff: [Sipping] RFC 3398: REL cause
> > 
> > 
> > Hi all,
> > 
> > According to the rfc 3398(SIP-ISUP mapping, section 7.1.3 and 
> > 7.2.2),for a
> > net to Phone call, when ACM timeout timer
> >  (T7- 20 - 30 s) expires, the ISUP leg  REL cause should be 
> > 102 (protocol
> > error, recovery on timer expiry) and corresponding SIP 
> > response should be
> > 504 Server Timeout.
> > However, if one goes by Q.764 and table 1 of Q.850 the 
> > correct REL cause for
> > ISUP would be 31(normal unspecified)
> > and for the SIP leg it would then correspond to  480 (Temporarily
> > Unavailable). Apparently 102 is used mostly for
> > SUS-RES.
> > 
> > What should be the values used?
> > 
> > 
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> > Sumit Garg 
> > Aastra Telecom US
> > 8 Federal Street 
> > Billerica, MA 01821 
> > 978-436-4244
> > email: <<mailto:sgarg@aastra.com>> 
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> > 
> > 
> > 
> 
> 


------_=_NextPart_000_01C2E977.7CA344D0
Content-Type: application/octet-stream;
	name="Sumit Garg.vcf"
Content-Disposition: attachment;
	filename="Sumit Garg.vcf"

BEGIN:VCARD
VERSION:2.1
N:Garg;Sumit
FN:Sumit Garg
ORG:Aastra Network Access
NOTE:Aastra CVX
TEL;WORK;VOICE:978-436-4244
ADR;WORK:;Boston;8 Federal Street;Billerica;MA;1821;USA
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Boston=0D=0A8 Federal Street=0D=0ABillerica, MA 1821=0D=0AUSA
EMAIL;PREF;INTERNET:sgarg@aastra.com
REV:20021122T160021Z
END:VCARD

------_=_NextPart_000_01C2E977.7CA344D0--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 12:18:46 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09377
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 12:18:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DHXGg13597
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 12:33:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DHXGO13594
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 12:33:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09372
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 12:18:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DHWRO13581;
	Thu, 13 Mar 2003 12:32:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DHVmO13516
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 12:31:48 -0500
Received: from smail3.alcatel.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09335
	for <sipping@ietf.org>; Thu, 13 Mar 2003 12:16:46 -0500 (EST)
From: Pascal.Jalet@alcatel.fr
Received: from frmail21.netfr.alcatel.fr (frmail21.netfr.alcatel.fr [155.132.182.151])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id h2DHItqj014208
	for <sipping@ietf.org>; Thu, 13 Mar 2003 18:18:55 +0100
To: <sipping@ietf.org>
Date: Thu, 13 Mar 2003 18:18:52 +0100
Message-ID: <OF958F23BE.38396BEA-ONC1256CE8.005D3C5C@netfr.alcatel.fr>
X-MIMETrack: Serialize by Router on FRMAIL21/FR/ALCATEL(Release 5.0.8 |June 18, 2001) at
 03/13/2003 18:18:54
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Virus-Scanned: by amavisd-new
Subject: [Sipping] Proxy behavior with request URI parameters
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Dear sipping members,

What must be a proxy behaviour when it receives a SIP request
with request-URI parameters that it doesn't undertstand.
In RFC 3261, It is said that "SIP elements MUST silently ignore
any uri-parameters that they do not understand".

Does it mean:
    that the proxy removes the uri-parameters when constructing the
   forwarded request.
    that  the proxy copies  transparently the unknown uri-parameters in the
   request-URI of the
forwarded request.

thanks for your help

Pascal


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 12:42:34 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10148
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 12:42:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DHv6W15618
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 12:57:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DHv5O15615
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 12:57:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10129
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 12:42:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DHuHO15561;
	Thu, 13 Mar 2003 12:56:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DHteO15515
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 12:55:40 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10085
	for <sipping@ietf.org>; Thu, 13 Mar 2003 12:40:37 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2DHgjC21872;
	Thu, 13 Mar 2003 17:42:45 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JTRNL>; Thu, 13 Mar 2003 12:43:02 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F1D@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Drage, Keith (Keith)'" <drage@lucent.com>,
        "'Sumit Garg'"
	 <sgarg@aastra.com>, sipping@ietf.org
Subject: RE: [Sipping] RFC 3398: REL cause
Date: Thu, 13 Mar 2003 12:43:01 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Some notes below.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Drage, Keith (Keith) [mailto:drage@lucent.com]
> Sent: Thursday, March 13, 2003 7:45 AM
> To: 'Sumit Garg'; sipping@ietf.org
> Subject: RE: [Sipping] RFC 3398: REL cause
> 
> 
> I had some problem trying to identify the problem that is 
> trying to be solved here, and that is because it is out of scope.
> 
> The text in section 7.2.2 of RFC 3398, that states
> 
> "A REL message with cause value 102 (protocol error,
>    recovery on timer expiry) SHOULD be sent to the PSTN. "
> 
> is a purely ISUP / BICC protocol procedure and nothing to do 
> with any interworking. Interworking documents should not 
> attempt to rewrite the protocols on either side of the 
> interworking point. Therefore this sentence SHOULD be deleted 
> from any future version of RFC 3398. Can the authors please 
> note this in the appropriate bug list.
> 

You are quite correct on this matter, Mr. Drage.

> Looking at the BICC specification, I cannot actually see a 
> point where it specifies a cause value to be included in the 
> ISUP REL message, and therefore presumably it is up to the 
> implementor to choose an appropriate one. 
> 
> I would believe that #28 would be inappropriate, but that 
> belief is irrelevant to this list, as this is an ISUP 
> response to an ISUP timer expiry.
> 

Agreed both that #28 is bad and that this is largely irrelevant to SIP-ISUP
interworking. Well, if literally nothing is specified for this case in the
relevant ITU-T specs, then it couldn't hurt for us to make a suggestion, but
making a normative one is inappropriate.

> For 7.1.3, I guess these are more informative, although I 
> would have preferred a different terminology to "MG Releases 
> PSTN Trunk" which implies to me that the trunk is released as 
> part of interworking, when it is a purely ISUP / BICC 
> protocol action that is causing this.
> 

7.1.3 is useful in so far as it's nice to know that 504 is sent in the
backwards direction in this instance, and so on.

One more note below.

> 
> Keith

> > -----Original Message-----
> > From: Sumit Garg [mailto:sgarg@aastra.com]


> > It would be more logical if it just sent 31
> > and 480.
> > 
> > -Sumit
> > 
> > 

I'm not sure #31 is so great for this either. But leaving that aside, 480
represents a radically different condition in SIP networks (which is very
close to cause #19). It would not be appropriate to send a 480 response
here.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 12:53:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10559
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 12:53:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DI7wv16969
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 13:07:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DI7wO16966
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 13:07:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10544
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 12:52:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DI7CO16484;
	Thu, 13 Mar 2003 13:07:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DI6VO16097
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 13:06:31 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10450
	for <sipping@ietf.org>; Thu, 13 Mar 2003 12:51:28 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2DHrVC22120;
	Thu, 13 Mar 2003 17:53:31 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JTRQM>; Thu, 13 Mar 2003 12:53:49 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F1F@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Elwell, John'" <john.elwell@siemens.com>,
        "'Mark Watson'"
	 <mwatson@nortelnetworks.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Thu, 13 Mar 2003 12:53:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


More can be found below.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens.com]
> Sent: Thursday, March 13, 2003 6:07 AM
> To: 'Peterson, Jon'; 'Mark Watson'
> Cc: 'sipping@ietf.org'
> Subject: RE: [Sipping] New version of the early media draft
> 
[snip]
>  
> From a QSIG perspective (I believe ISUP is similar) the gateway DOES have
a
> way of figuring out whether it should send media. There is an explicit
> indicator in QSIG that says that in-band media is present. Also there is
an
> explicit QSIG message that indicates that an alerting state has been
> reached. The indication of in-band media can be sent with or without
> indication of the alerting state. 

Yes, those indicators exist in ISUP, and they are decoupled from the BCI,
which indicates 'subscriber free' when the user is being alerted. What I've
been hearing in this thread is that these in-band media indicators are not
used reliably. That is, that some ISUP endpoints 'assume' that a media path
has been established by the ACM, and send early media without indicating so
in ISUP. That would complicate things a bit.

> Therefore there are basically 3 things
> that the gateway has the capability of signalling, if SIP 
> allows it to:
>  
> 1. Alerting - no media - 180 satisfies this
> 2. No state change (not alerting) - media present - 183 satisfies this
> 3. Alerting - media present - ????
>  
> The third possibility does not have a satisfactory solution. At present
the
> qsig2sip draft uses 180 for this and relies on the UAC detecting early
media
> and playing it in preference to local media. However, this is not very
> satisfactory, for reasons that Mark Watson has given. An additional
> indicator to include in 180 to say that in-band media is present would be
> helpful.
>  

Yes, well, obviously I think media detection is an adequate solution, and it
is necessary for reasons other than detecting early media - it is also used
to detect and render post-answer media before 200 OK, as Gonzalo has pointed
out. The MGC composition issues, thus far, have not appeared persuasive to
me.

But moreover you are reinforcing Mark's suggesting that the 'Alerting' state
means something specific in SIP, which it doesn't. Even if it did, there
wouldn't be a need to play in-band media during the 'Alerting' state if this
in-band media did not somehow qualify or supplement the information that the
state is 'alerting'. The in-band early media provides status information -
otherwise, there'd be no point in sending it or rendering it. That in-band
media characterizes the true state of the call, not the SIP status code.
That's why I think 183 is adequate for this.

> John Elwell ( john.elwell@siemens.com 
> <mailto:john.elwell@siemens.com> )
>  
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 13:04:14 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10838
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 13:04:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DIIkH17379
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 13:18:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DIIkO17376
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 13:18:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10831
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 13:03:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DII7O17339;
	Thu, 13 Mar 2003 13:18:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DIHLO17299
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 13:17:21 -0500
Received: from auemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10781
	for <sipping@ietf.org>; Thu, 13 Mar 2003 13:02:18 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by auemail2.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2DI4Q311758
	for <sipping@ietf.org>; Thu, 13 Mar 2003 13:04:26 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <XNTCR8Z8>; Thu, 13 Mar 2003 18:04:25 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EC64@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Sumit Garg'"
	 <sgarg@aastra.com>, sipping@ietf.org
Subject: RE: [Sipping] RFC 3398: REL cause
Date: Thu, 13 Mar 2003 18:04:23 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

See below with some additional fairly minor comments.

Keith

Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 

> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> Sent: 13 March 2003 17:43
> To: 'Drage, Keith (Keith)'; 'Sumit Garg'; sipping@ietf.org
> Subject: RE: [Sipping] RFC 3398: REL cause
> 
> 
> 
> Some notes below.
> 
> Jon Peterson
> NeuStar, Inc.

<snipped>

> > Looking at the BICC specification, I cannot actually see a 
> > point where it specifies a cause value to be included in the 
> > ISUP REL message, and therefore presumably it is up to the 
> > implementor to choose an appropriate one. 
> > 
> > I would believe that #28 would be inappropriate, but that 
> > belief is irrelevant to this list, as this is an ISUP 
> > response to an ISUP timer expiry.
> > 
> 
> Agreed both that #28 is bad and that this is largely 
> irrelevant to SIP-ISUP
> interworking. Well, if literally nothing is specified for 
> this case in the
> relevant ITU-T specs, then it couldn't hurt for us to make a 
> suggestion, but
> making a normative one is inappropriate.
> 
I would disagree with making even a suggestion in the IETF document. My understanding of ISUP / BICC and DSS1 is that if the cause code is not specified for the specific release instance, then an appropriate cause should be chosen by the implementor. Making even a suggestion in an IETF document may imply to some implementors that they should absolutely follow this.

If it is considered that a specification or suggestion is needed (and I dont really think it is), then the appropriate contribution should be made to ITU-T SG11 to change Q.1701.4 (I am unsure whether Q.764 is currently being maintained).

And certainly just deleting the sentence is the easiest fix to agree.

> > For 7.1.3, I guess these are more informative, although I 
> > would have preferred a different terminology to "MG Releases 
> > PSTN Trunk" which implies to me that the trunk is released as 
> > part of interworking, when it is a purely ISUP / BICC 
> > protocol action that is causing this.
> > 
> 
> 7.1.3 is useful in so far as it's nice to know that 504 is sent in the
> backwards direction in this instance, and so on.
> 
Yes, I guess I would not delete it, but in the future we may want to consider making it slightly more general, something along the lines of "ISUP protocol error in MGC, e.g. T7 expiry". I assume 504 would apply in all these sort of cases.

<rest snipped>
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 13:17:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11423
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 13:17:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DIVwQ18209
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 13:31:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DIVwO18206
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 13:31:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11411
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 13:16:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DIV9O18139;
	Thu, 13 Mar 2003 13:31:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DIULO18080
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 13:30:21 -0500
Received: from auemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11307
	for <sipping@ietf.org>; Thu, 13 Mar 2003 13:15:17 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by auemail2.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2DIHPV23172
	for <sipping@ietf.org>; Thu, 13 Mar 2003 13:17:26 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <XNTCR9DY>; Thu, 13 Mar 2003 18:17:25 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EC65@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Elwell, John'"
	 <john.elwell@siemens.com>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Thu, 13 Mar 2003 18:17:23 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

I would agree with John and Mark from that from the ISDN side (be it ISUP, BICC, DSS1 or QSIG, we are talking about 3 cases. I tried to draft some definitions of that before John's mail came in and I ended up with the following:

"The PSTN/ISDN ringing state, arrived at by sending a ringing type message, can be used for more that the simple case of the call being delivered to the end user with ringing in-band. It is also used in the following cases:

i)    cases where there is a need to present information to the user (normally from the service provider) without charging commencing. This case does not carry any special indication in the PSTN signalling, as the backward media path is assumed to be in place once the ringing state is entered.

ii)    cases where the status of the destination is unknown, but there is a need to move out of one of the call set up states due to timer expiry problems. This situation frequently occurs when interworking with less capable signalling systems. I believe there are PBX signalling systems that do not contain an equivalent of a ringing signal at all, and certaining there are still a large amount of none ISUP signalling systems around int he public network (e.g. R2). Normally in this case, it would be expected that some indication of interworking is available at the PSTN side, and this case can be distinguished by that indication, although there have been examples of interworking with R2 in the past, where such an indication was not provided.

Both these cases are represented in the standards for PSTN signalling, and can therefore be assumed to be correct operation in the PSTN.

Combining the normal SIP cases and the PSTN interworking cases, there are three things we need to signal:

1)    The call has been delivered to the end user terminal and the user is being informed of the presence of the request. No media being delivered in-band. This can only be a SIP only case, unless the media path is being inspected to see if it really contains media. This would appear to be the case currently recommended for 180 (Ringing).

2)    The call may have been delivered to the end user, with the user being informed of the presence of the request (it has certainly been delivered somewhere), however the precise nature of the situation is indicated by in-band information. This is the normal SIP interworking case with the PSTN. In this case I would suggest that the UAC should at least consider overriding any local generated tone with the contents of the media packets.

3)    The status is not known, but may be indicated by in-band information. This is the SIP interworking case with the PSTN where one of the interworking progress indicators has been delivered from the remote end."

The issue under discussion is how we represent the last two cases. I support both Mark and John in saying that we do need to distinguish all three to the end user, no matter how we do it.

As regards the early-media draft, I would propose putting some of the general text above in the general section. We then have the discussion of the two models, and the solution of each of the three cases needs to be presented for both models.

Currently the discussion seems to have focussed only on the solutions for the gateway model.

regards

Keith

Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 

> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> Sent: 13 March 2003 17:54
> To: 'Elwell, John'; 'Mark Watson'
> Cc: 'sipping@ietf.org'
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> 
> More can be found below.
> 
> Jon Peterson
> NeuStar, Inc.
> 
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens.com]
> > Sent: Thursday, March 13, 2003 6:07 AM
> > To: 'Peterson, Jon'; 'Mark Watson'
> > Cc: 'sipping@ietf.org'
> > Subject: RE: [Sipping] New version of the early media draft
> > 
> [snip]
> >  
> > From a QSIG perspective (I believe ISUP is similar) the 
> gateway DOES have
> a
> > way of figuring out whether it should send media. There is 
> an explicit
> > indicator in QSIG that says that in-band media is present. 
> Also there is
> an
> > explicit QSIG message that indicates that an alerting state has been
> > reached. The indication of in-band media can be sent with or without
> > indication of the alerting state. 
> 
> Yes, those indicators exist in ISUP, and they are decoupled 
> from the BCI,
> which indicates 'subscriber free' when the user is being 
> alerted. What I've
> been hearing in this thread is that these in-band media 
> indicators are not
> used reliably. That is, that some ISUP endpoints 'assume' 
> that a media path
> has been established by the ACM, and send early media without 
> indicating so
> in ISUP. That would complicate things a bit.
> 
> > Therefore there are basically 3 things
> > that the gateway has the capability of signalling, if SIP 
> > allows it to:
> >  
> > 1. Alerting - no media - 180 satisfies this
> > 2. No state change (not alerting) - media present - 183 
> satisfies this
> > 3. Alerting - media present - ????
> >  
> > The third possibility does not have a satisfactory 
> solution. At present
> the
> > qsig2sip draft uses 180 for this and relies on the UAC 
> detecting early
> media
> > and playing it in preference to local media. However, this 
> is not very
> > satisfactory, for reasons that Mark Watson has given. An additional
> > indicator to include in 180 to say that in-band media is 
> present would be
> > helpful.
> >  
> 
> Yes, well, obviously I think media detection is an adequate 
> solution, and it
> is necessary for reasons other than detecting early media - 
> it is also used
> to detect and render post-answer media before 200 OK, as 
> Gonzalo has pointed
> out. The MGC composition issues, thus far, have not appeared 
> persuasive to
> me.
> 
> But moreover you are reinforcing Mark's suggesting that the 
> 'Alerting' state
> means something specific in SIP, which it doesn't. Even if it 
> did, there
> wouldn't be a need to play in-band media during the 
> 'Alerting' state if this
> in-band media did not somehow qualify or supplement the 
> information that the
> state is 'alerting'. The in-band early media provides status 
> information -
> otherwise, there'd be no point in sending it or rendering it. 
> That in-band
> media characterizes the true state of the call, not the SIP 
> status code.
> That's why I think 183 is adequate for this.
> 
> > John Elwell ( john.elwell@siemens.com 
> > <mailto:john.elwell@siemens.com> )
> >  
> > 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 13:44:25 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12342
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 13:44:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DIwwk20278
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 13:58:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DIwwO20275
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 13:58:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12330
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 13:43:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DIw2O20243;
	Thu, 13 Mar 2003 13:58:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DIvHO20197
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 13:57:17 -0500
Received: from mail.aastra.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12275
	for <sipping@ietf.org>; Thu, 13 Mar 2003 13:42:12 -0500 (EST)
Received: by mail.aastra.com with Internet Mail Service (5.5.2653.19)
	id <1XVB0KXC>; Thu, 13 Mar 2003 13:33:42 -0500
Message-ID: <F924CEFBBF62D611A0C600D0B76ED037157984@cvxmail.ana.aastra.com>
From: Sumit Garg <sgarg@aastra.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Drage, Keith (Keith)'"
	 <drage@lucent.com>,
        Sumit Garg <sgarg@aastra.com>, sipping@ietf.org
Subject: RE: [Sipping] RFC 3398: REL cause
Date: Thu, 13 Mar 2003 13:33:33 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C2E98F.0D832990"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_000_01C2E98F.0D832990
Content-Type: text/plain;
	charset="iso-8859-1"

Some notes at the end:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sumit Garg
Aastra Telecom US
8 Federal Street
Billerica, MA 01821
978-436-4244
email: <<mailto:sgarg@aastra.com>>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: Thursday, March 13, 2003 12:43 PM
To: 'Drage, Keith (Keith)'; 'Sumit Garg'; sipping@ietf.org
Subject: RE: [Sipping] RFC 3398: REL cause



Some notes below.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Drage, Keith (Keith) [mailto:drage@lucent.com]
> Sent: Thursday, March 13, 2003 7:45 AM
> To: 'Sumit Garg'; sipping@ietf.org
> Subject: RE: [Sipping] RFC 3398: REL cause
>
>
> I had some problem trying to identify the problem that is
> trying to be solved here, and that is because it is out of scope.
>
> The text in section 7.2.2 of RFC 3398, that states
>
> "A REL message with cause value 102 (protocol error,
>    recovery on timer expiry) SHOULD be sent to the PSTN. "
>
> is a purely ISUP / BICC protocol procedure and nothing to do
> with any interworking. Interworking documents should not
> attempt to rewrite the protocols on either side of the
> interworking point. Therefore this sentence SHOULD be deleted
> from any future version of RFC 3398. Can the authors please
> note this in the appropriate bug list.
>

>You are quite correct on this matter, Mr. Drage.

> Looking at the BICC specification, I cannot actually see a
> point where it specifies a cause value to be included in the
> ISUP REL message, and therefore presumably it is up to the
> implementor to choose an appropriate one.
>
> I would believe that #28 would be inappropriate, but that
> belief is irrelevant to this list, as this is an ISUP
> response to an ISUP timer expiry.


>Agreed both that #28 is bad and that this is largely irrelevant to SIP-ISUP
>interworking. Well, if literally nothing is specified for this case in the
>relevant ITU-T specs, then it couldn't hurt for us to make a suggestion,
but
>making a normative one is inappropriate.

> For 7.1.3, I guess these are more informative, although I
> would have preferred a different terminology to "MG Releases
> PSTN Trunk" which implies to me that the trunk is released as
> part of interworking, when it is a purely ISUP / BICC
> protocol action that is causing this.
>

>7.1.3 is useful in so far as it's nice to know that 504 is sent in the
>backwards direction in this instance, and so on.

>One more note below.

>
> Keith

> > -----Original Message-----
> > From: Sumit Garg [mailto:sgarg@aastra.com]


> > It would be more logical if it just sent 31
> > and 480.
> >
> > -Sumit
> >
> >

>I'm not sure #31 is so great for this either. But leaving that aside, 480
>represents a radically different condition in SIP networks (which is very
>close to cause #19). It would not be appropriate to send a 480 response
>here.
-------------

I am pasting the section of table 1 from Q.850 which defines the Causes to
be used.
Cause
Value    No        Definition                  Diagnostics  Application

 1111    31         Normal, unspecified                        DSS1,ISUP


References       Location           Remarks
Q.931		     RLN                Call  information failure

2.1.1/Q.764      TN, INTL, RLN      indicating the failure
2.1.2/Q.764                          of a call due to the
 2.8.1/Q.764                         lapse of a timeout  
2.8.2/Q.764                          or a fault not covered
 2.9.3/Q.764                         by specific causes
2.9.6/Q.764                          (examples: expiry of timers
2.9.8.2/Q.764                        Q.764 not covered by
2.9.8.3/Q.764                        specific causes, release of
2.1.8/Q.764                          interconnected circuit, etc.)
 2.2.4/Q.764

Thus for the ISUP side the most likely cause would be 31.
So I mapped this 31 as per RFC3398 to get 480 as the SIP release cause;
 which per se is not all that bad...
It would just cause the request to be made again (I hope) after some
time..and then
we would hopefully not have an ACM timeout. 
504 for sure is better; but consider a case where the ACM timeout occurs
on a switch between the SS7-SIP gateway and the destination. The Gateway
would still
recv 31 and map it to 480 evoking the behaviour which is closer to Release
Cause 19 ;-)

So would it really matter if the gateway itself sent the release cause of
480 instead
of 504 on timeout??

I totally agree that the RFC should not make any suggestion towards the
causes to be
be used on the protocols being interworked. That should be done only in
their respective
specs/RFCs.

--Sumit





------_=_NextPart_000_01C2E98F.0D832990
Content-Type: application/octet-stream;
	name="Sumit Garg.vcf"
Content-Disposition: attachment;
	filename="Sumit Garg.vcf"

BEGIN:VCARD
VERSION:2.1
N:Garg;Sumit
FN:Sumit Garg
ORG:Aastra Network Access
NOTE:Aastra CVX
TEL;WORK;VOICE:978-436-4244
ADR;WORK:;Boston;8 Federal Street;Billerica;MA;1821;USA
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Boston=0D=0A8 Federal Street=0D=0ABillerica, MA 1821=0D=0AUSA
EMAIL;PREF;INTERNET:sgarg@aastra.com
REV:20021122T160021Z
END:VCARD

------_=_NextPart_000_01C2E98F.0D832990--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 13:48:24 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12465
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 13:48:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DJ2vU20549
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 14:02:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DJ2vO20546
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 14:02:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12436
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 13:47:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DIvIO20207;
	Thu, 13 Mar 2003 13:57:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DIutO20179
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 13:56:55 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12259
	for <sipping@ietf.org>; Thu, 13 Mar 2003 13:41:51 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2DIh8C23375;
	Thu, 13 Mar 2003 18:43:08 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JTSAG>; Thu, 13 Mar 2003 13:43:26 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F21@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>,
        "'hgs@cs.columbia.edu'"
	 <hgs@cs.columbia.edu>
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Date: Thu, 13 Mar 2003 13:43:24 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


> From: King, Kimberly S. [mailto:KIMBERLY.S.KING@saic.com]
> 
[snip]
> 
> Suppose there are Internet Telephony Service Providers (or cable operators
> offering telephony services) that are willing to modify gateways to the
PSTN
> to provide preferential access for authorized users.  The idea would be in
> times of gateway congestion, authorized users might have advantage in
> obtaining resources.  If the providers run stateful proxies, those proxies
> could also favor authorized users.  To receive preferential treatment,
> authorized users must be customers of these particular providers.  Isn't
> this partial ETS coverage potentially useful?
> 

This is useful for combatting gateway congestion, yes. If the reality is
that congestion is more likely to arise in other parts of the system (like,
the access links), then alleviating congestion at gateways is unlikely to
increase the overall odds of call completion significantly. If odds are that
you will never be able to get to the gateways, then managing gateway
congestion will make little difference; we need to know if the interposition
of one administrative domain that does not support ETS in a call's path
crushes the odds that calls will complete reliably in emergencies. This is
the sort of analysis that needs to be done. 

I agree that managing gateway congestion by routing prioritized calls to
reserved emergency gateways is realistic. But if it turns out that this is
the only aspect of managing prioritization that is actually realistic, then
that tells us something about the mechanism (for one thing, that all SIP
calls whose priority can be managed would have telephone numbers in their
Request-URI). This could have significant ramifications for the ongoing
design work.

> If some government wanted to create a priority scheme over its own
priviate
> network (e.g., MLPP/Assured Service over government owned network) then is
> that reasonable?
> 

On totally private networks, I find the whole ETS SIP concept entirely
plausible. I would note that the "I" in "IEPREP" is for Internet, though. I
have always understood that to be the capital-"I" Internet, as in RFC3271.

> Some people from the NGN PSTN camp are thinking about priviate packet
> networks for telephony.  They envision trading traffic with their peers in
a
> manner mirroring their current methods.  (For example, see 
> http://www.msforum.org/techinfo/reports/MSF-TR-QoS-001-FINAL.pdf )
> Suppose the majority of ETS locations used a handful of providers and
those
> providers traded traffic as in the MSF report augmented with ETS support.
> Given the assumed architecture, would this partial ETS coverage be
> potentially useful?  
> 

This concept of 'partial' is slightly different than the one I was
suggesting for further analysis. I think this 'partial ETS coverage'
suggests partial deployment of ETS in the world, but in deployments such
that, within controlled environments, it is possible to have ETS support
end-to-end. The 'partial' ETS I'm concerned with is the specific effects of
partial support of ETS in a particular call path (which is, among other
things, the motivation for wanting ETS to propagate through unaware networks
- unaware networks would constitute a segment of the call path in which ETS
is not supported).

And again, private packet networks are not the native environment for SIP -
nor would I have thought that they were the only meaningful customer of
IEPREP. The MSF architecture specified by the document referenced above
relies on numerous assumptions that are not general Internet tenets. That
much said, these private networks are not harmful to the Internet, they are
potentially useful, and so on. However, I don't think any ETS system that
relied exclusively on the traversal such networks would be a general
solution for Internet emergency preparedness. 

Jon Peterson
NeuStar, Inc.

> Is this the type of analysis you seek for partial ETS coverage?  
> 
> Kimberly
> 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 14:09:53 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13269
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 14:09:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DJOQe22570
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 14:24:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DJOQO22567
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 14:24:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13241
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 14:09:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DJN9O22468;
	Thu, 13 Mar 2003 14:23:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DJMPO22420
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 14:22:25 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13173
	for <sipping@ietf.org>; Thu, 13 Mar 2003 14:07:20 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2DJ9LC24009;
	Thu, 13 Mar 2003 19:09:21 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JTS2J>; Thu, 13 Mar 2003 14:09:38 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F22@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Drage, Keith (Keith)'" <drage@lucent.com>,
        "'Elwell, John'"
	 <john.elwell@siemens.com>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Thu, 13 Mar 2003 14:09:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Some notes below.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Drage, Keith (Keith) [mailto:drage@lucent.com]
> Sent: Thursday, March 13, 2003 10:17 AM
> To: 'Peterson, Jon'; 'Elwell, John'; 'Mark Watson'
> Cc: 'sipping@ietf.org'
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
[snip]
>
> 2)    The call may have been delivered to the end user, with 
> the user being informed of the presence of the request (it 
> has certainly been delivered somewhere), however the precise 
> nature of the situation is indicated by in-band information. 
> This is the normal SIP interworking case with the PSTN. In 
> this case I would suggest that the UAC should at least 
> consider overriding any local generated tone with the 
> contents of the media packets.
> 
> 3)    The status is not known, but may be indicated by 
> in-band information. This is the SIP interworking case with 
> the PSTN where one of the interworking progress indicators 
> has been delivered from the remote end."
> 
> The issue under discussion is how we represent the last two 
> cases. I support both Mark and John in saying that we do need 
> to distinguish all three to the end user, no matter how we do it.
> 

What's the need to distinguish between 2 and 3? Both are sending in-band
media to the UAC which it should use, right? In both cases, the UAC nees to
listen to the media to learn the "precise nature of the situation." What
should the UAC do differently because condition 2 prevails, as opposed to
condition 3?

If the UAC receives media, it should be playing it. I don't think it's a
matter, as you describe in 2, that a UAC should merely consider playing it.
Given that, 2 and 3 seem to be identical. Making the UAC responsible for
deciding whether or not to play the media seems like the wrong model to me.
The gateway, which actually inspects and understands PSTN signaling, should
decide whether or not delivering media to the UAC is necessary.

> As regards the early-media draft, I would propose putting 
> some of the general text above in the general section. We 
> then have the discussion of the two models, and the solution 
> of each of the three cases needs to be presented for both models.
> 
> Currently the discussion seems to have focussed only on the 
> solutions for the gateway model.
> 
> regards
> 
> Keith
> 
> Keith Drage
> Lucent Technologies
> Tel: +44 1793 776249
> Email: drage@lucent.com 
> 
> > -----Original Message-----
> > From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > Sent: 13 March 2003 17:54
> > To: 'Elwell, John'; 'Mark Watson'
> > Cc: 'sipping@ietf.org'
> > Subject: RE: [Sipping] New version of the early media draft
> > 
> > 
> > 
> > More can be found below.
> > 
> > Jon Peterson
> > NeuStar, Inc.
> > 
> > > -----Original Message-----
> > > From: Elwell, John [mailto:john.elwell@siemens.com]
> > > Sent: Thursday, March 13, 2003 6:07 AM
> > > To: 'Peterson, Jon'; 'Mark Watson'
> > > Cc: 'sipping@ietf.org'
> > > Subject: RE: [Sipping] New version of the early media draft
> > > 
> > [snip]
> > >  
> > > From a QSIG perspective (I believe ISUP is similar) the 
> > gateway DOES have
> > a
> > > way of figuring out whether it should send media. There is 
> > an explicit
> > > indicator in QSIG that says that in-band media is present. 
> > Also there is
> > an
> > > explicit QSIG message that indicates that an alerting 
> state has been
> > > reached. The indication of in-band media can be sent with 
> or without
> > > indication of the alerting state. 
> > 
> > Yes, those indicators exist in ISUP, and they are decoupled 
> > from the BCI,
> > which indicates 'subscriber free' when the user is being 
> > alerted. What I've
> > been hearing in this thread is that these in-band media 
> > indicators are not
> > used reliably. That is, that some ISUP endpoints 'assume' 
> > that a media path
> > has been established by the ACM, and send early media without 
> > indicating so
> > in ISUP. That would complicate things a bit.
> > 
> > > Therefore there are basically 3 things
> > > that the gateway has the capability of signalling, if SIP 
> > > allows it to:
> > >  
> > > 1. Alerting - no media - 180 satisfies this
> > > 2. No state change (not alerting) - media present - 183 
> > satisfies this
> > > 3. Alerting - media present - ????
> > >  
> > > The third possibility does not have a satisfactory 
> > solution. At present
> > the
> > > qsig2sip draft uses 180 for this and relies on the UAC 
> > detecting early
> > media
> > > and playing it in preference to local media. However, this 
> > is not very
> > > satisfactory, for reasons that Mark Watson has given. An 
> additional
> > > indicator to include in 180 to say that in-band media is 
> > present would be
> > > helpful.
> > >  
> > 
> > Yes, well, obviously I think media detection is an adequate 
> > solution, and it
> > is necessary for reasons other than detecting early media - 
> > it is also used
> > to detect and render post-answer media before 200 OK, as 
> > Gonzalo has pointed
> > out. The MGC composition issues, thus far, have not appeared 
> > persuasive to
> > me.
> > 
> > But moreover you are reinforcing Mark's suggesting that the 
> > 'Alerting' state
> > means something specific in SIP, which it doesn't. Even if it 
> > did, there
> > wouldn't be a need to play in-band media during the 
> > 'Alerting' state if this
> > in-band media did not somehow qualify or supplement the 
> > information that the
> > state is 'alerting'. The in-band early media provides status 
> > information -
> > otherwise, there'd be no point in sending it or rendering it. 
> > That in-band
> > media characterizes the true state of the call, not the SIP 
> > status code.
> > That's why I think 183 is adequate for this.
> > 
> > > John Elwell ( john.elwell@siemens.com 
> > > <mailto:john.elwell@siemens.com> )
> > >  
> > > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> > 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 14:55:39 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15270
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 14:55:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DKADp27008
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 15:10:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DKADO27005
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 15:10:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15249
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 14:55:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DK9VO26934;
	Thu, 13 Mar 2003 15:09:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DK8BO26875
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 15:08:11 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15154
	for <sipping@ietf.org>; Thu, 13 Mar 2003 14:53:05 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z059BT>; Thu, 13 Mar 2003 14:53:21 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410D995BE7@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'King, Kimberly  S.'"
	 <KIMBERLY.S.KING@saic.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>,
        "'hgs@cs.columbia.edu'"
	 <hgs@cs.columbia.edu>
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Date: Thu, 13 Mar 2003 14:51:27 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Not "the only meaningful customer", but certainly "one of the meaningful
customers".

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> 
[snip]

And again, private packet networks are not the native environment for SIP -
nor would I have thought that they were the only meaningful customer of
IEPREP. The MSF architecture specified by the document referenced above
relies on numerous assumptions that are not general Internet tenets. That
much said, these private networks are not harmful to the Internet, they are
potentially useful, and so on. However, I don't think any ETS system that
relied exclusively on the traversal such networks would be a general
solution for Internet emergency preparedness. 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 15:01:15 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15462
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 15:01:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DKFoK27275
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 15:15:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DKFoO27272
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 15:15:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15443
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 15:00:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DKF4O27213;
	Thu, 13 Mar 2003 15:15:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DKEdO27178
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 15:14:39 -0500
Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15385
	for <sipping@ietf.org>; Thu, 13 Mar 2003 14:59:33 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by ihemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2DK1gY24028
	for <sipping@ietf.org>; Thu, 13 Mar 2003 15:01:42 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <XNTCR0W3>; Thu, 13 Mar 2003 20:01:41 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EC68@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Elwell, John'"
	 <john.elwell@siemens.com>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Thu, 13 Mar 2003 20:01:39 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

See below

regards

Keith

Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 

> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> Sent: 13 March 2003 19:10
> To: 'Drage, Keith (Keith)'; 'Elwell, John'; 'Mark Watson'
> Cc: 'sipping@ietf.org'
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> 
> Some notes below.
> 
> Jon Peterson
> NeuStar, Inc.
> 
> > -----Original Message-----
> > From: Drage, Keith (Keith) [mailto:drage@lucent.com]
> > Sent: Thursday, March 13, 2003 10:17 AM
> > To: 'Peterson, Jon'; 'Elwell, John'; 'Mark Watson'
> > Cc: 'sipping@ietf.org'
> > Subject: RE: [Sipping] New version of the early media draft
> > 
> > 
> [snip]
> >
> > 2)    The call may have been delivered to the end user, with 
> > the user being informed of the presence of the request (it 
> > has certainly been delivered somewhere), however the precise 
> > nature of the situation is indicated by in-band information. 
> > This is the normal SIP interworking case with the PSTN. In 
> > this case I would suggest that the UAC should at least 
> > consider overriding any local generated tone with the 
> > contents of the media packets.
> > 
> > 3)    The status is not known, but may be indicated by 
> > in-band information. This is the SIP interworking case with 
> > the PSTN where one of the interworking progress indicators 
> > has been delivered from the remote end."
> > 
> > The issue under discussion is how we represent the last two 
> > cases. I support both Mark and John in saying that we do need 
> > to distinguish all three to the end user, no matter how we do it.
> > 
> 
> What's the need to distinguish between 2 and 3? Both are 
> sending in-band
> media to the UAC which it should use, right? In both cases, 
> the UAC nees to
> listen to the media to learn the "precise nature of the 
> situation." What
> should the UAC do differently because condition 2 prevails, 
> as opposed to
> condition 3?
> 
I believe the distinction is that in case 2) it is appropriate to write "ringing" or "call delivered" or "waiting answer" or such like on the display of the UAC, or whatever additional indications are given to the user over and above the in-band tones/announcements. In case 3 it is not.

Given the number of different non-standard ring tones out there, the user may actually be relying on this extra information to know that the tone he is listening to is actually the ring tone he thinks it is, and not so other variety of busy tone. In one case he can terminate the call immediately, and in the other case he should cannot.

I think the issue here is that the user is essentially dialling a PSTN user in both these cases, and therefore it is reasonable to present to the user at the UAC the indications that he would expect to get back from the PSTN. 

In terms of the solution, presenting 183 in both cases 2 and 3 without some additional indication is misleading. Furthermore the tone/announcement in this case could well assume that the signalling level distinction available in the ISUP has been made available to the end user.

There is also the case of providing appropriate level of signalling to support the SHOULD discussed below.

> If the UAC receives media, it should be playing it. I don't 
> think it's a
> matter, as you describe in 2, that a UAC should merely 
> consider playing it.
> Given that, 2 and 3 seem to be identical. Making the UAC 
> responsible for
> deciding whether or not to play the media seems like the 
> wrong model to me.
> The gateway, which actually inspects and understands PSTN 
> signaling, should
> decide whether or not delivering media to the UAC is necessary.
> 
As far as the UAC is concerned, in general I agree that if the UAC receives media, it should be playing it. I consider it unsafe to write a MUST here, and would default to a SHOULD, as there may be specific user interface considerations that make it incorrect or inappropriate.

I think it is also an assumption that all gateways can actually look at the in-band media and reliably detect what has been indicated. Any specification for early media must deal with both the cases, i.e. where the media gateway controller is not doing media detection, and that where it is. 

By the way, I suspect that this would need to be somewhat more sophisticated that just looking at the media stream at when the indication arrives; the nature of in-band information can change over time, and thus the nature of any appropriate indication to be given. There is also the problem of distinguishing noice (generated from transmission of the PSTN path over 20 miles of barbed wire) versus real signal.

Note also that while ITU-T specifies characteristics of these tones, PSTN equipment has a lifetime that tends to exceed the lifetime of a harmonised ITU specification of these tones. In practice there are 57 different varieties of all these tones out there, and there are laws of nature that state that the first ones you find in the field are the odd ones.


<snipped>
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 15:30:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17912
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 15:30:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DKisd29734
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 15:44:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DKisO29731
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 15:44:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17884
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 15:29:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DKiCO29668;
	Thu, 13 Mar 2003 15:44:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DKhVO29634
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 15:43:31 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17849
	for <sipping@ietf.org>; Thu, 13 Mar 2003 15:28:24 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by auemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2DKUXp16555
	for <sipping@ietf.org>; Thu, 13 Mar 2003 15:30:33 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <XNTCSADV>; Thu, 13 Mar 2003 20:30:32 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EC69@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>,
        "'Gonzalo.Camarillo@lmf.ericsson.se'" <Gonzalo.Camarillo@lmf.ericsson.se>
Date: Thu, 13 Mar 2003 20:30:30 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] Some comments on draft-camarillo-sipping-early-media-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Some fairly minor comments that need to be applied to this document if it progresses with the current text in any of these areas.

A question over and above these comments - is the intent of this work to result in a standards track document or an information document? Which of those will affect whether some of the standard clauses are needed or not.

regards

Keith

Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 

1)	General. Can we stop using the term ringback tone, as these is not a standard definition elsewhere and certainly in the PBX world means something entirely different. I would suggest an appropriate term is "ringing tone" and the appropriate reference for definition of that term ITU-T Recomendation E.182 "Application of tones and recorded announcements in telephone services" and the technical characteristics of such a tone is defined in ITU-T Recommendation E.180, "Technical characteristics of tones for the telephone service".

2)	Section 1, 3rd (last) paragraph, suggest reference back to section 12 of RFC 3261 for the term "early dialog", maybe as part of a new definitions clause if you do not wish to do it in the text itself.

3)	Section 2, 3rd paragraph. "early" appears in quotation marks here, but not elsewhere. Lack of consistency.

4)	Section 2.1. This is a long piece of text for which we discover at the end that this section (including 2.1.1) that it is describing a problem that is outside the scope of the document. Perhaps we could try to develop a shorter way of getting to that conclusion.

5)	Section 2.1, 6th paragraph (just before the end of page 4) - I did not understand the distinction being made by the phrase "and the caller starts speaking as well" to the rest of the sentence. Can you explain further.

6)	Section 2.2, 2nd paragraph. Two uses of the word "supposed" in "is supposed to generate" and "is supposed to play". I think this is too strong a word for something that is entirely up to the design of the implementation as being described. I would substitute something like "can generate" and "can play".

7)	Section 2.2, 4th paragraph, top of page 7, text "With this in mind, a UAC should develop...". Is this meant to be "SHOULD", i.e. one of the RFC 2119 terms.

8)	Section 2.2, 4th paragraph, numbered list items 2) and 3) include word "response" after "(Ringing)".

9)	Section 2.2, 5th paragraph through to end of section. Here we have a paragraph (no indent) starting  "Note, however..." followed by an indented one starting "Note that..." followed by one (no indent) starting "Note that...". I am confused by the relative status of these paragraphs to each other and to the rest of the text.

10)	Section 3, 1st paragraph, not a comment that requires fixing, but we have a dependency to the Join draft which will need to be finished before or at the same time as this draft.

11)	Section 3, 1st paragraph, Amend final sentence to read "... by sending a new INVITE request to the URI it received in the Join header field."
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 16:02:40 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18996
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 16:02:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DLHHD32009
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 16:17:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DLHGO32006
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 16:17:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18962
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 16:02:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DLGNO31981;
	Thu, 13 Mar 2003 16:16:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DLFIO31928
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 16:15:18 -0500
Received: from dewberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18881
	for <sipping@ietf.org>; Thu, 13 Mar 2003 16:00:10 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(user=hgs10 mech=PLAIN bits=0)
	by dewberry.cc.columbia.edu (8.12.8/8.12.8) with ESMTP id h2DL2JjC018352
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 13 Mar 2003 16:02:20 -0500 (EST)
Message-ID: <3E70F1E5.7020903@cs.columbia.edu>
Date: Thu, 13 Mar 2003 16:02:29 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Peterson, Jon" <jon.peterson@neustar.biz>
CC: "'King, Kimberly S.'" <KIMBERLY.S.KING@saic.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>
Subject: Re: [Sipping] Comments on draft-peterson-sipping-ieprep-00
References: <15A2739B7DAA624D8091C65981D7DA8101214F21@stntexch2.va.neustar.com>
In-Reply-To: <15A2739B7DAA624D8091C65981D7DA8101214F21@stntexch2.va.neustar.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

At least my impression from the IEPREP discussion was that access link 
congestion is an important factor, but that it is a separable concern. 
For that, indications and reservations at the IP layer seem like the 
more appropriate consideration, which seem pretty far afield from SIP 
territory.


> This is useful for combatting gateway congestion, yes. If the reality is
> that congestion is more likely to arise in other parts of the system (like,
> the access links), then alleviating congestion at gateways is unlikely to
> increase the overall odds of call completion significantly. If odds are that
> you will never be able to get to the gateways, then managing gateway
> congestion will make little difference; we need to know if the interposition
> of one administrative domain that does not support ETS in a call's path
> crushes the odds that calls will complete reliably in emergencies. This is
> the sort of analysis that needs to be done. 

I just don't see you we can "analyze" this, since there is no real data 
on access link congestion in the places where people would like to place 
ETS calls. At least on 9/11 (and, I believe, during most disasters where 
ETS was used, such as the various earthquakes in CA), Internet traffic 
volume wasn't significantly higher than usual, but all such past events 
took place in an environment where few people used the Internet for 
real-time communications.

How do you propose to arrive at an analysis?

> 
> I agree that managing gateway congestion by routing prioritized calls to
> reserved emergency gateways is realistic. But if it turns out that this is
> the only aspect of managing prioritization that is actually realistic, then
> that tells us something about the mechanism (for one thing, that all SIP
> calls whose priority can be managed would have telephone numbers in their
> Request-URI). This could have significant ramifications for the ongoing
> design work.

They might have phone numbers before they hit the gateway, but they may 
well have 'regular' SIP URIs at the origin, translated by some proxy or 
B2BUA.



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 16:21:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19616
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 16:21:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DLa3U00523
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 16:36:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DLa2O00520
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 16:36:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19593
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 16:20:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DLZAO00481;
	Thu, 13 Mar 2003 16:35:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DLYcO00445
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 16:34:38 -0500
Received: from pmesmtp02.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19545
	for <sipping@ietf.org>; Thu, 13 Mar 2003 16:19:29 -0500 (EST)
Received: from pmismtp01.wcomnet.com ([166.38.62.36])
 by firewall.wcom.com (Iplanet MTA )
 with ESMTP id <0HBP00137HUIHM@firewall.wcom.com> for sipping@ietf.org; Thu,
 13 Mar 2003 21:18:18 +0000 (GMT)
Received: from pmismtp01.wcomnet.com by pmismtp01.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HBP00I01HPB9Q@pmismtp01.wcomnet.com>; Thu,
 13 Mar 2003 21:18:18 +0000 (GMT)
Received: from ajohnston.wcom.com ([166.50.126.191])
 by pmismtp01.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HBP00I3CHTTNY@pmismtp01.wcomnet.com>; Thu,
 13 Mar 2003 21:17:55 +0000 (GMT)
Date: Thu, 13 Mar 2003 15:17:53 -0600
From: Alan Johnston <alan.johnston@wcom.com>
Subject: Re: [Sipping] Some comments on
 draft-camarillo-sipping-early-media-01.txt
X-Sender: Alan.Johnston@pop.mcit.com
To: "Drage, Keith (Keith)" <drage@lucent.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>,
        "'Gonzalo.Camarillo@lmf.ericsson.se'" <Gonzalo.Camarillo@lmf.ericsson.se>
Message-id: <5.1.1.6.0.20030313150038.024d36f0@pop.mcit.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset=us-ascii; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

At 08:30 PM 3/13/2003 +0000, Drage, Keith (Keith) wrote:

<snip>

>10)     Section 3, 1st paragraph, not a comment that requires fixing, but 
>we have a dependency to the Join draft which will need to be finished 
>before or at the same time as this draft.
>
>11)     Section 3, 1st paragraph, Amend final sentence to read "... by 
>sending a new INVITE request to the URI it received in the Join header field."

This entire section is quite confusing.  I think that Gonzalo does not mean 
to reference the Join header field - it has no application in this 
example.  I think he means to reference the To-Join header field proposed 
by Jonathan in the original call package 
(http://www.softarmor.com/sipping/drafts/morgue/draft-rosenberg-sip-call-package-00.txt). 


Also, the reference 5 cited in this section is the Application Interaction 
Framework which again has no bearing on this idea of separate dialogs for 
regular and early media.  Perhaps the Application Component Architecture 
document was the intended reference?

Thanks,
Alan Johnston
WorldCom
sip:alan@digitalari.com

>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 18:59:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25909
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 18:59:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2E0EFL12183
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 19:14:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2E0EFO12180
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 19:14:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25894
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 18:59:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2E0CmO12085;
	Thu, 13 Mar 2003 19:12:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2E09GO11925
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 19:09:16 -0500
Received: from dgesmtp02.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25772
	for <sipping@ietf.org>; Thu, 13 Mar 2003 18:54:02 -0500 (EST)
Received: from dgismtp02.wcomnet.com ([166.38.58.142])
 by firewall.wcom.com (Iplanet MTA )
 with ESMTP id <0HBP004A4P5OU3@firewall.wcom.com> for sipping@ietf.org; Thu,
 13 Mar 2003 23:56:12 +0000 (GMT)
Received: from dgismtp02.wcomnet.com by dgismtp02.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HBP00J01P4ERO@dgismtp02.wcomnet.com>; Thu,
 13 Mar 2003 23:56:12 +0000 (GMT)
Received: from hsinnreich2 ([166.50.97.37])
 by dgismtp02.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HBP00GGWP4LNJ@dgismtp02.wcomnet.com>; Thu,
 13 Mar 2003 23:55:37 +0000 (GMT)
Date: Thu, 13 Mar 2003 17:55:33 -0600
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
To: gonzalo.camarillo@ericsson.com, Rohan Mahy <rohan@cisco.com>,
        dean.willis@softarmor.com, sipping@ietf.org
Cc: "'Steven Lass'" <Steven.Lass@wcom.com>,
        "'Daniel G. Petrie'" <dpetrie@pingtel.com>,
        "'Christian Stredicke'" <stredicke@snom.de>
Message-id: <005e01c2e74c$0c3bc690$677432a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=iso-8859-1
Importance: High
X-Priority: 1 (Highest)
X-MSMail-priority: High
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2E09HO11926
Subject: [Sipping] Comments on SIP Telephony Device Requirements, Configuration and Data
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

The draft 

http://www.ietf.org/internet-drafts/draft-sinnreich-sipdev-req-00.txt

 has received comments kindly provided by Denise Caballero-McCan(Cisco),
Yaron Scheffer (Personeta), Sanjoy Sen(Nortel), Ed Elleson (Lboard),
Jiri Kuthan (iptel), Jean Brierre (WorldCom), Adrian Louis
(Profile-ICT), Brian Rosen (Marconi), Gunnar Hellström (Omnitor AB),
Eric Tremblay (Mediatrix), Franz Edler (UTA Telekom AG), Banibrata Dutta
and Subir Saha (Hughes). There were also e-mails on the SIP Forum list
on SIP devices. 

The authors propose to edit version 01 based on these comments, in time
for the 57 IETF; with the objective of issuing an informational RFC on
BCP for SIP devices. The BCP will reflect the implementation and user
experience from a large number of SIP phones and PC clients deployed.

Thanks, Henry

Henry Sinnreich
WorldCom
400 International Parkway
Richardson, Texas 75081
USA
 
____________________________________________

- In Sec. 4, I would expect DHCP to be a MUST protocol. Also, please
specify for some of the protocols (HTTP, DNS) whether client support,
server support or both are required.
- Sec. 5.3.1: the DNS A record implies manual configuration of the
server's DNS name (FQDN). It is also confusing that you recommend DNS
support, and then go on to mention "magic" IP addresses for the server.
- Emergency URL: just "sos", without the "sip:" and "@domain"
ornamentation, is probably more useful to lay users. I suppose many
phones would translate the URL automatically. Can it be made a MUST?
- Sec. 6.5.1, ILBR Codec: the referenced document is missing, or
expired.
- Sec. 8, Services: support in the devices does not imply support in the
proxies, so it is not a sufficient condition for deploying these
services. Based on the experience with IN, I believe services should NOT
be standardized. But this section should mention this distinction.
- Sec. 10, Security: use of SIP REFER opens up a number of large
security issues. Please mention them in this section. Although REFER
nominally requires positive user action at the UA, this is not the case
with current implementations. Thus, disabling REFER through
configuration should probably be a SHOULD - at least.


1. Section 4 under MUST support..  Given that there is little market
demand 
for TCP on our hard Phone clients I think this should be changed to 
may.   Adding TCP support will eat into valuable memory that can be
better 
used for features such as WEB Browsing, etc.

2. Section 4 - Does NTP mean _ Network Timing Protocol?

3. Section 5.3.1 - Not clear to me why Manual configuration needs to be
by 
a web Browser.. I think this should read... SIP devices must support
manual 
configuration, this configuration may be my means of a web browser.

4. Section 6.4 - I think this is a product differentiator and should not
be 
a must... for example, why should we have to support audio mixing for 
conference calls in a low end residential phone or the ATA device if the

market does not demand it.

5. Section 9.1 -  This seems a little two specific... buttons for 
initiating call set ups may be labeled dial, talk, etc... in addition
you 
may have voice activated calling... perhaps this section is better 
re-written to say that a mechanism to "Correct mistakes" should be 
supported...and a mechanism by which the user can initiate the call set
up 
should be provided...

6. Section 9.1.3. This is a little confusing..earlier in the document it

says that either 911 or sos calling should be supported, but this
section 
sounds like you need to support both which could be very confusing to a 
"panicked' user...

7. Section 11 - I think defining SNMP as should in most cases, including

high-end devices, is over kill.. in addition... high end-devices is a 
nebulous term... you could fix this by use may instead of should.


Requirements for SIP device/service configuration process:

OP-Req) The client SHOULD be able to perform remote operations on
configuration data, e.g., - upload, insert, modify, fetch, search. This
list of operations is not exhaustive.

ERR-Req) Adequate error codes MUST be supported for various types of
transaction failures as a result of performing these operations - such
as, 'server failure', 'authentication required', 'search failed' etc.
This list of error codes is not exhaustive.

CAP-Req) It SHOULD be possible for the client to provide its device and
service capability/preference information to the configuration server in
an extensible and flexible manner. This may be required by the server to
determine the appropriate provisioning data for the client depending on
the device capabilities. Examples of such information include vendor
name, device type, video enabled, supported protocols for download of
provisioning data etc. 

MULT-Req) It MUST be possible to request for different configuration
profiles associated with a single device. For example, different users
hosted on a SIP device may have different profiles.

DIS-Req) Disconnected operations MUST be supported. This implies the
need to track changes in configuration data.

REL-Req) Reliable transport of a large amount of data MUST be supported.

EFFC-Req) Means for efficient transport of large amount of configuration
and capability information SHOULD be supported. This is particularly
important for low bandwidth wireless links.

AUTH-Req) The client MUST be able to perform remote operations on
configuration data securely. The framework MUST support adequate access
control of user profiles through proper authentication of clients
attempting to perform operations on provisioning information. The
provisioning server SHOULD be authenticated by the client.

PRIV-Req) The framework MUST support adequate confidentiality of
configuration data of the user.

EXT-Req) The protocol MUST be easily extensible

EASE-Req) Text based protocol encoding is preferable for ease of
interpretation, implementation and extensibility.


The immediate need that prompts me to request that such a document be
agreed to and advanced by the sippiing wg is that we at our company have
experienced problems on our own internal sip network due to problems
with the SIP registration behavior of certain end user devices.  

Here is the problem we have noticed:  

If a group of sip end devices loses connectivity with their SIP
registrar, due to, for example, an enterprise taking their firewall out
of service for several hours to do an upgrade over the weekend, we find
that certain end devices do not continue to try to register after
network connectivity to the registrar has been restored.  These devices
follow the sip spec in timing out their registration attempts, which is
fine.  However, at an application level, these devices should
re-initiate the registration process after, say, an hour, and every hour
thereafter, to see if network connectivity to the registrar has been
restored.  Without this application level behavior, what we have found
is that when people come in to use their phones after a network outage,
they find that they cannot receive phone calls unless they reboot their
phones.  Not all devices have this problem, but a sufficient number of
devices do, that it would be valuable to describe in a BCP what the
expected end device behavior should be for functions like this.  

Please consider this a vote in favor of working on and advancing a BCP
on appropriate end user sip device behavior. 


You may want to add some BCP recommendations. Particularly, I would like
to see a push on phone vendors "Do, really do implement SRV fail-over,
so that if a primary server fails, a backup server will be used".
Otherwise, service reliability is threatened.


Integrated Switch/Hub SIP devices designed for wired Ethernet SHOULD
have an uplink port such that another IP device, such as a personal
computer, MAY share the network connection. SIP clients MUST prioritize
the transmission of RTP traffic over the shared network connection. 

comment 1: 
Wish you would remove the Hub reference since this is a shared collision
domain concept which I do not recommend for sip client that has real
time requirements sharing this shared Ethernet environment with a host
device that may also have real time data on the same hub. Switch is the
only way to go since ethernet HUB collisions between 2 devices can
effect throughput

"IP Requirements IP-1: SIP telephony devices MUST be able to acquire an
IP address by: Automatic IP address configuration using DHCP, or Manual
IP address entry from the device. "

Comment 2 
Why did you not reference RFC3361 DHCP option for sip
ftp://ftp.rfc-editor.org/in-notes/rfc3361.txt this a great MAY RFC to
support for sip clients to learn SIP proxy servers

Comment 3 
No mention was made of support for Visual and Hearing Impaired Special
Equipment or even RFC3351 ftp://ftp.rfc-editor.org/in-notes/rfc3351.txt

Comment 4 
You mention management but only for provisioning, why can we not have
SNMP v3 support for network LAN statistics, SIP traffic stats or even
RTCP info on the SIP phone.


> it would be interesting to see if SIP phone manufacturers think this
is
>OK for any type of SIP device, or only for certain devices, such as SIP
>telephony adaptors that support key sets. I believe it makes sense only

>for latter. Opinions?

I agree!  SNMP v3 support for network LAN statistics etc. might just
about make sense for SIP telphony adaptors, but it is unlikely that you
would convince SIP telephone manufacturers of the need for such support
in their products.


I think it makes sense for any network device.  I'm not sure how far I
would go, but our network management systems want to know the devices
that are out there, and have the basic info any device gives you.

Certainly we've been asked by customers for tools that network
management can use to determine what is happening when users say "I got
a call, but I couldn't hear them".  We've offered syslogs and they got
amused.  

I'll admit that my "sipphone" engineers think this is silly.
My customers beg to differ.

I think the only thing there is to discuss is:
	How much info is available
	Are there alarms/traps

And, of course, it MUST be SNMPv3


SIP-xx, analogue text support: SIP adapter devices (for analog phone
lines)
  MUST support conversion between real time text transmission using RFC
2793 [y]
  and text telephones according to ITU-T V.18 [x] allowing alternating
use of
  text and voice. SIP clients MUST fallback to G.711 if RFC2793
connection fails.


SIP-zz, digital text support: SIP telephone devices MUST support
  real time text conversation using RFC 2793 [y] for the text stream.
  It MUST be possible to use text simultaneously with voice.



---------------------------------------------
In 4.11 Ringer Behaviour  : add the section below for the purpose of
deaf, hearing impaired, deaf-blind people and people in the garden and
noisy
locations:

SIP Telephony devices MUST provide an external interface to
an external alerting system.



Add to References
-----------------
[y] G. Hellstrom: "RTP Payload for Text Conversation.", RFC 2793, IETF,
May 2000. [z] ITU-T Recommendation V.18 "Operational and interworking
requirements for DCEs operating in the text telephone mode", November
2000 with amendment November 2002.


  SIP-2, DNS SRV: SIP clients MUST t support RFC2782 [3] and MAY 
  support the SIP service examples [4] for basic PBX-like or Centrex-
  like functions.  SIP clients MUST support DNS SRV for locating a SIP 
  Server. When making a SRV query, the client MUST t use the DNS 
  additional information in the response that contains the IP addresses 
  for the A records. 
     
  If the DNS additional information is not present, the client MUST 
  make DNS A record queries to resolve the hostnames.

[EricT]
I suggest referencing RFC 3263 (Locating SIP Servers) in the above
section. I don't know what services are being referred to when saying
"and MAY support the SIP service examples [4] for basic PBX-like or
Centrex-like functions.".  This section is about DNS SRV, but I found
nothing in the latest SIP Services Examples draft about DNS SRV...


  SIP-3, Do Not Disturb: SIP clients MUST be able to set the state of 
  the client as Do Not Disturb.  Clients MUST respond to new INVITES 
  with a ô486 Busy Hereö.  Clients MUST respond to re-INVITES on 
  existing call legs as normal behavior [4]. 

[EricT]
I suggest rewording to something like "It must be possible for the SIP
device user to configure the device state to Do Not Disturb. ...", as it
is generally the user that sets the DND state ;)

  SIP-4, call hold resume: SIP clients MUST be able to place a call on 
  hold/resume [4].

[EricT]
Should it focus on the usage of RFC 3264, with the use of a=sendonly
instead of c=0.0.0.0? Also with a focus that the answer does not
automatically comes with a "held" sdp? I suggest adding something like
"SIP clients MUST follow RFC 3264 when placing a call on hold. More
specifically, the a=sendonly attribute MUST be used. The SDP answer of
SIP clients that are being placed on hold MUST NOT contain "held" SDP,
unless the user session was originally on hold."

  SIP-7, message waiting indicator: SIP clients MUST support SIP 
  message waiting  and an indicator for integration with voicemail 
  platforms [5]. 

[EricT]
This is kind of hard, since there is not RFC yet for this and different
vendor/integrators are using different draft versions which sometimes do
not interoperate.  Should maybe add a note to this effect... Maybe
something like "No RFC exist yet for this service. SIP clients MUST
implement this service in its RFC form when it becomes available."

  SIP-9, transfer: SIP devices MUST support REFER and NOTIFY as 
  required to support the transfer [6].  SIP clients MAY support 
  escaped headers in the Refer-To: header.

[EricT]
Same problem as SIP-7...  I suggest upgrading the "MAY support escaped
headers..." to MUST, as not supporting this has impact on attended call
transfer.


  SIP-11, attended call transfer: SIP devices MUST support attended 
  call transfer [3], [4].  SIP clients MAY support escaped headers in 
  the Refer-To: header. 

[EricT]
Reference [3] makes no sense here ;) Should probably be [6]. 

  SIP-12, music on hold: SIP devices MUST support music on hold [4]. 

[EricT]
Not sure why this service is a MUST? Maybe in enterprise environments,
but what about homes?


  SIP-15: DTMF RTP payload: SIP clients MUST be able to send DTMF 
  specified by RFC2833 [7].   
   
  Payload type negotiation MUST comply with RFC 3264 [8]. 
   
  Payload type MUST remain constant throughout the session.  For 
  example, if an endpoint decides to renegotiate codecs or put the call 
  on hold, the payload type for the re-invite MUST be the same as 
  initial payload type. 

[EricT]
Should probably refer to RFC 3388. Maybe add "SIP devices SHOULD support
Flow Identification (FID) as defined in RFC 3388."

  SIP-20, reason phrase display: If the ôReason Phraseö of a response 
  message is displayed, the client MUST use ôReason Phraseö in the 
  response packet.  The client MUST not use an internal ôStatus Codeö 
  table. 
   
  Another SIP device MAY respond with ô403 Forbiddenö, or various other 
  messages. 

[EricT]
I am not sure about the above two MUST. Something tells me that the
client could rely on an internal table if there was a problem with
language negotiation...  I don't know what the last sentence means???
"Another SIP device MAY ..." It makes no sense to me...

  SIP-25, Dynamic login/logout for user mobility: SIP devices MUST 
  support user mobility.  SIP clients MUST store a static profile in 
  non-volatile memory so that this information is available during the 
  power up sequence.  SIP clients MUST allow a user to walk up to a 
  client, login, and be able to send and receive calls with his profile 
  information. 
  For emergency numbers (e.g. 911) the client MUST send the credentials 
  (username/password) of the static profile. 

[EricT]
We are developing analog adapters and don't remember receiving such a
request. I suggest either changing the MUST to SHOULD or adding some
text to specify that it is a MUST for devices with the proper interface
to do it and a SHOULD for devices with a limited interface. I know we
could possibly configure this through a web interface, but the point is
that there are a lot of vendore that currently just want to replace the
wire, not the phone and its interface...

  App-5, SIMPLE Integration: SIP devices MUST provide a ôbuddy-
  list/addressbookö and use SIP extensions to leverage presence [21]. 

[EricT]
This also does not applies well to black phones applications. I suggest
changing this to "MAY".


  FW/NAT-2, NAT capable configuration: SIP devices MUST be able to 
  operate behind a static NAT/PAT (Network Address Translation/Port 
  Address Translation) device using the STUN protocol [x22].  SIP 
  clients MUST be able to populate SIP messages with the public, 
  external address of the NAT/PAT device and use specific port ranges 
  for RTP. 
   
  FW/NAT-3, UPnP capable configuration 
  SIP devices MUST be able to operate with a UPnP 
  (http://www.upnp.org/) firewall device. 

[EricT]
I suggest using a MUST on only one of these, and a MAY on the other. I
am not fully aware of all details about these two protocols, but I think
a device could very well work behind a firewall by using only one
mechanism. I think the draft should clearly state which mechanism is
preferred.

As a last point, I suggest splitting this draft into two or more drafts.
One about generic requirements for SIP devices, and one (or more) about
the configuration mechanism along with the data that can be configured.
The first draft could refer the second one.  The draft, as it is right
now, defines basic requirements, then some configuration framework and
its requirement, and then data (and data representation). I don't think
those mix well. Focusing would probably make the documents easier to
maintain ;)


SIP-8, local dial plan:
  I'm unhappy with requiring a local dialing plan.
  Many of my customers wish to force all calls through the
    local proxy

SIP-13, client-based conferencing: 
  I don't know what the sentence "SIP devices MUST be able to 
  support handset based conferencing" means.  I understand the
  next sentence.  Are you proposing that each handset follow
  the SIP conferencing requirements?  If not, what, exactly,
  is the requirement?

SIP-15: DTMF RTP payload
  I'm confused why this is a MUST.  If the device only supports
  G.711 or better (i.e. no low bandwidth, highly compressed) codecs,
  why is it a requirement to generate 2833?

SIP-22 through SIP-26, multi-line support
  I'm having problems with the terminology.  "Multiline" to me
  means the ability to handle more than one call at a time (all but
  one on hold).  Here you mean "multiple users on the same UA"
  I think the requirements are okay (at MAY), but we need
  a new term that really means multiple users registered at one UA.

  I'll note that there is a possible problem with our basic standards.
  To allow multiple users at the same UA, the UA, the registrar and
  the incoming proxy all have to support such a thing.  There is no
  way for the UA to know if that is possible.

SIP-24, multi-line call waiting indicator
  I don't understand "If call waiting is set for an identity, the 
  client MUST respond with "486 Busy Here" when an incoming call 
  to that identity is received and the client has an existing 
  call with any of the identities"

  Are you disallowing the possibility of more than one waiting
  call for an identity?  How else do I understand "call waiting
  is set"?

SIP-25, Dynamic login/logout 
  I disagree with the architecture assumption made here.  I think
  emergency calls should NOT depend on any kind of authentication.
  Thus, I think it should not be necessary to register before
  making an emergency call, and thus there is no need for a default
  identity.  

  Specifically, if your proposal was implemented, and, for whatever
  reason, authentication failed, and a user could not make an emergency
  call, I think someone is in DEEP doo-doo.

  I think we need some convention for identity (ie what is in the From)
  to aid law enforcement in tracking malicious calls to emergency
  centers, but, please, don't depend on authentication.  As far as I
  know, emergency centers would rather get some "anonymous" calls than
  miss a call because someone configured something wrong.

SIPsec-2 password protection
  I dislike this requirement.  I think the problems it generates
outweigh
  the security it provides.  Specifically, to make this work, you have
  to put a default password in the device, so you can get in the first
  time, and you need some kind of a reset function when people forget
  the settings.  The former almost always gets left in this state, which
  opens up a huge attack, the latter always eventually gets known, and
  exploited.

  Our systems have VERY limited configuration done at the terminal -
  basically, just how you get an IP address.  Everything else we store
  on a server and download.  This works well for us, and putting a
password
  on the IP settings is just not justified.

SIPsec-4, INVITE user portion acceptance
  You don't have the corresponding output requirements - SIP devices
must
  have a setting that forces all outbound messages to a specific proxy.
  This is a clear requirement for many operators.

International-1, language support
  I have a very minor problem with "The setting for this header MUST 
  be provisioned".  My problem is that it could be interpreted as
  disallowing a separate language preference for each user who is
  registered when multi-user support is provided.  We certainly would
  not provision the PHONE with language.  We would have a user profile
  setting for this.

App-2, hold ring-back
  Do you expect the phone to send any SIP message when it starts to
  ring?  Maybe you should say what you expect.

App-5, SIMPLE Integration
  I think this is not well specified.  SIMPLE has so many possible
  variations, I don't see what we say.  I also think there is no
  "address book" spec yet, and specifically, an address book may
  have many more addresses in it than you get presence for.

Web-1
  I object to this requirement.  We provide a very nice
  UI on our device to specify things like ring tones and forwarding
  preferences.  It happens that we also have a web UI that can do this,
  but we really don't need it.  I'll note that the wording is
  awkward.  The first sentence says "SIP devices MUST support a web
server",
  while the second sentence says "Web pages ... MAY be [in]
..centralized 
  web servers"  The latter is more correct than the former.

Web-2
  Object in that not all such settings make sense to be remotely
settable.
  Forwarding behavior may be, ringtones may not be, at least with
respect
  to a user.

FW/NAT-1, outbound proxy support
  I think this is too tightly specified.  Specifically, I think the
  device needs to accept an outbound proxy.  It must be configurable
  to always use this proxy, and for each user, there must be a full
  uri that may or may not be in the same domain as the outbound proxy.
  There is no need to explicitly know the domain; you need to know the
  URI.  It may be that your implementation affixes a registration name
  to a default domain.  Ours doesn't.  We authenticate with a username
  and then return an AOR.  I think that is quite reasonable.

  That means the first MUST (default domain) can go away.

Int-1: (buttons)
  I would not want this to be interpreted as requiring any specific
  hard buttons.  Any/all of these could be in some soft UI.

Int-3 
  There are several paragraphs after the first one in Int-3 that I
  can't make any sense of.  Is some of it supposed to be an Int-4?
  
  The fragment "End user options..." is not a sentence.

Lines-1 This requirement gets confused with the prior multi-line
  section above.  Consolidation and terminology change is needed.

Section 3
  First of all, at least at the moment, there is no SIP mechanism to
  do any of this, and I suspect it won't be a sip mechanism that
  does it, although it could be a form of PUBLISH.  So, I think 
  using terms like "User Agent" is incorrect.  Perhaps use Profile 
  Server and Profile Client.

  There are several cases where the word "may" became "MAY"
  inappropriately.  

  I also think there are "device profiles" that are associated with
  a particular UA, "user profiles" that are associated with a particular
  user, and a hybrid, where there is a profile for a particular
  user at a particular device.  These need names, we need a name
  for any of them, and the text has to be edited to use the
  correct one of these.

  I have some problems with:
    Change Notification is the means by which the profile server tells 
    the user agent that profiles of interest have changed.  Typically, 
    the intention would be for the user agent to get those changes or
the 
    updated profiles.  

  My problem is that this is a database, the terminal may change it,
  or an external web accessed page may change it.  In the former, the
  device has to inform the database that it is changed.  In the latter,
  the database has to inform the device that it is changed.  Both of
  these are change notifications.

OpenExt-1: and OpenExt-2: are the same.
  I think extensibility of the data object is more important than
  "intelligence" at the server, whatever that means.

ENR-5:
  Also is needed to support multiple users on the same UA.

CN-3: 
  Could we have some justification for this?  I'm not objecting
  to a MAY, I want the device to MAY support a scheduled change.

SEC-n
  I have some problems with authentication, because I envision this
  to be close to the first thing you do after you have an IP address.
  The device is either provisioned with, or learns the profile
  server from DHCP.  It contacts it first, before any registration,
  ....  You don't have a lot to authenticate either end with, except
  the aforementioned password which I think is worse than nothing.
  
Section 4
  I am confused over what this intended to be.  Are we talking about
  settings that are made manually at the device, not covered by
  a device profile described in Section 3?  I personally think we should
  be minimizing such things.  Right now, ideally, I think you learn
  the profile server from DHCP and get everything from that except the
  IP address/mask stuff that you also get from DHCP.  It's a tossup
  whether you learn the sip proxy from DHCP or the profile server.
  You certainly shouldn't be having a "Session Timer" setting that
  doesn't come from the device profile.

  Also has the confusion on the term "line"

  There is a typo in the chapter number in the first sentence.

Network-2
  We should be clear whether we intend this wording to imply you have
  more than one setting, or whether there is one setting and it is
  applied to both media and signalling.  I think there are potentially
  many settings, one for each media type and one for signalling.

Dial-1: Dial Plan. 
  I object.  We SHOULD recommend a "Dial" button and not rely on
  a dial plan.  A dial plan should at best be a MAY.

Regional-4: 
  I recognize that some sites will not support DHCP.  DHCP should
  be the preferred way to find the time server.  The text should say
  that.  If you don't have DHCP, it has to be provisioned, and thus
  we need this in the list, I just think its use should be discouraged.
  
Phonebook-1:
  The text seems to not allow a phonebook to be stored on the profile
  server.  It should allow that.  The problem is the word "stored".

PhoneServers-1:
  I don't understand why you would encourage phonebooks to be stored
  in someplace other than the profile server.  I can see some difficulty
  in storing history there, although we would do it that way.

4.11 Ringer Behavior  
   
  The text "These devices SHOULD ignore all line related settings 
  that do no affect the default outbound line settings they receive"
  has a typo, and it confuses how "default" should work.  They are
  line settings.  There is a default line.  It should state something
  like "... all line settings other than the default line's settings"

  The last paragraph of this section should be deleted.  It doesn't
  help, and it ignores the most common choice of ringtone selection
  by caller.

4.12 User Related Settings
  This text is very confusing to me.  I'm certainly agreeable to
supporting
  multiple users registered at a UA.  I'm interested in supporting
  multiple call appearances per user (or per UA if you prefer, they are
  the same as long as you don't restrict one user to a SINGLE
appearance)

  The picture you seem to have is a physical or UI button per line,
  and you want to assign a user to a line.  Okay, if that's what you
  want as long as I can assign more than one line to one user.

  Our system works a bit differently but the effect is the same with
  regard to allowing multiple users registered at one UA, and multiple
  call appearances per user.

  The only thing I can make out of this text is that you want to be
  able to have some prior configuration that has some default
association
  between a line button and a user.  While we wouldn't do that, I
understand
  that such a facility may be useful for some vendors.  The text is far
  from clear about that, if indeed that is what you meant.

  Roaming means that a user walks up to a phone and does something that
  causes him to be registered.  In your picture, it causes one or more
  line buttons to be associated with him.  That isn't a configuration
  mechanism, that's a run time dynamic assignment mechanism. Registering
  on a UA may cause a new user profile to be downloaded, I get that,
  but this section is on device configuration, as best I can figure out,
  and this text doesn't make much sense to me here.

4.13 Line Related Settings 
  
  Another very confusing section for me.  My problem is that I don't see
  a 1to1 correspondence between a "line" and an address of record.
  The whole "line" concept is POTS specific.  There are users and there
  are call appearances.  You can have one or more users, and each user
  can have zero or more call appearances.  Each user has an AoR, but
  you can have more than one active call at this AoR at a particular
  device.  

  It could be that if you changed "line" to "registered user", the text
  could make some sense, but it might need more work than that.
  You clearly don't have a separate registration if a user has more
  than one "line" in your sense of "line"; The first call to the user's
  AoR would show up on his first "line", the second would show at his
  second "line".  There doesn't have to be any knowledge of this in
  anything except the device.  There doesn't have to be a URI for each
  line.

4.16 through 4.20
  These are, or should at least have the option to be, PER USER
settings,
  not per device settings.  I'm having a little conflicting views
  problems, because we implement these things in the proxy server
  not the device, but we're having some problems with the idea of 
  "ring once then forward".  Generally, we think that forwarding
  behavior is best done at the server since you have to do it anyway
  when the user is not logged in.  On the other hand, not all servers
  will do that, and so maybe requiring the phone to be able to do
  it may be necessary.

I did not review sections 5 and higher.


just a comment on SIP-25:

I am currently working on a PSTN - SIP migration concept avoiding to
re-invent all fancy features of the PSTN and in particular to
re-implement all legal/regulatory requirements (emergency call handling,
legal intercept). The concept builds upon a "dual homed" SIP-UA with one
"line" connected to the PSTN via V5 - SIP gateway and the other "lines"
beeing free for all new services of the SIP world. Therefore the
requirement of multiple identities on the SIP side and a static
identitiy on the PSTN side is essential, but I agree, if you are focused
on analog adapters only, this would mean an unnecessary burden. But I
suggest to re-think the migration perspective.

By the way, if anyone is interested in this "dual-homed" PSTN - SIP
migration concept let me know. I am convienced that this means a good
chance for a carrier to migrate towards SIP without heavy investments in
re-inventing what is already existing.


>Can SIP handle simultaneous session as in ...can we transfer a media to

>another sip client and talk to someone else at the same time using the 
>same device?

short answer is yes. longer answer is it depends on the SIP device in
question. SIP devices, s.a. the CISCO, Pingtel phones, have no. of
common, and some differentiating "features". Call park, call hold, call
trasfer are some of the business-line features you'd find in these
phones. These features, are nothing but the application of core-SIP or
some SIP-extentions, in form of an application, much like the
traditional PSTN features and services, both IN & non-IN.

--

From: rishi <rishik@mahindrabt.com>
To: banibrata dutta <bdutta@hotmail.com>
CC: sipforum-discussion@lists.su.se, sipping@ietf.org
Subject: Re: [Sipforum-discussion] SIP Telephony Device
Requirements,Conf 
iguration andData
Date: Thu, 06 Mar 2003 01:21:03 +0530

Hi folks,
query - Can SIP handle simultaneous session as in ...can we transfer a
media 
to
another sip client and talk to someone else at the same time using the
same device?


Hello Everybody:
Now that the list has got reasonable members, I would like to start the
activities under this working group. To start with, we should brainstrom
on what we can do in this area. My guess is that the Draft authored by
Henry Sinnreich et. al.  [
http://www.ietf.org/internet-drafts/draft-sinnreich-sipdev-req-00.txt]
is a good starting point for our discussions. Also we should follow
similar activity started in H323 forum and elsewhere. Lets start...

_________________________________

Thanks, Henry 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 13 21:06:53 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29094
	for <sipping-archive@odin.ietf.org>; Thu, 13 Mar 2003 21:06:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2E2LZb20576
	for sipping-archive@odin.ietf.org; Thu, 13 Mar 2003 21:21:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2E2LZO20573
	for <sipping-web-archive@optimus.ietf.org>; Thu, 13 Mar 2003 21:21:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29089
	for <sipping-web-archive@ietf.org>; Thu, 13 Mar 2003 21:06:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2E2KJO20459;
	Thu, 13 Mar 2003 21:20:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2E2BqO20080
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 21:11:52 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28910
	for <sipping@ietf.org>; Thu, 13 Mar 2003 20:56:39 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for sipping@ietf.org; Thu, 13 Mar 2003 20:57:30 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2003031320583428268
 ; Thu, 13 Mar 2003 20:58:34 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <FSPLMCYK>; Thu, 13 Mar 2003 21:00:42 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77D65@mcl-its-exs01.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Peterson, Jon '" <jon.peterson@neustar.biz>,
        "''King, Kimberly  S.' '" <KIMBERLY.S.KING@saic.com>
Cc: "''sipping@ietf.org' '" <sipping@ietf.org>,
        "''hgs@cs.columbia.edu' '" <hgs@cs.columbia.edu>
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Date: Thu, 13 Mar 2003 20:58:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Jon said:

>If the reality is
>that congestion is more likely to arise in other parts of the system
>(like, the access links), then alleviating congestion at gateways is
unlikely
>to increase the overall odds of call completion significantly. If odds are
>that you will never be able to get to the gateways, then managing gateway
>congestion will make little difference; we need to know if the
>interposition of one administrative domain that does not support ETS in a
call's path
>crushes the odds that calls will complete reliably in emergencies. This
>is the sort of analysis that needs to be done. 

Okay, the ideas I'm about to present represent my personal thoughts. 

Why should ETS need to justify the absence of congestion in the access links
or other parts of the network (thereby proving optional preferential
treatment is justified) when the default system operates without respect to
transport congestion?  We are just trying to increase our odds with the
default system.  Why not have transport congestion issues, where
appropriate, handled independently?

For example, there are Internet Telephony Service Providers (ITSPs) today
that are selling VoIP using SIP where the ITSP has no control over access
links or any administrative domains over which the packets flow.  If
transport layer congestion occurs then perhaps some signaling packets get
dropped or voice quality is reduced.  If gateway congestion occurs then no
ports are available and I'm assuming some SIP VoIP sessions are given a fast
busy or re-routed to an alternate gateway.  I take as an assumption that if
a provider spent the money on gateway resources by investing in many
connections to the PSTN (these are $$$) that they were smart enough to
ensure, given reasonable traffic assumptions, that signaling isn't going to
be dropped very often (at least near the gateway) and that on-going call
quality can be maintained fairly well.  This represents the standard network
offering that I'll assume works well enough even when the gateway is full. 

Suppose we want to do better than the default service offering by allowing a
preferential access to gateway resources during times of gateway congestion.
Examine the scenario of an ETS supporting fully loaded gateway.  In this
case, the total traffic is the same as the maximum traffic load that could
be supported.  If the call quality was sufficient before, it should be
sufficient now too.  All that has changed is the proportion of ETS sessions
is possibly greater.  I'm aware this is different than GETS, but GETS
provides a good model.  It doesn't "fix" the PSTN under all circumstances;
it just uses the default network to increase the probability of success.
Why shouldn't the SIP ETS provided by an ITSP adhere to the same "take the
default offering and increase the probability of success"?  

>I agree that managing gateway congestion by routing prioritized calls to
>reserved emergency gateways is realistic. But if it turns out that this
>is the only aspect of managing prioritization that is actually realistic,
>then that tells us something about the mechanism (for one thing, that all
SIP
>calls whose priority can be managed would have telephone numbers in
>their Request-URI). This could have significant ramifications for the
ongoing
>design work.

I agree with you that if gateways are the only issue then this could affect
the design.  However, are there not media or application servers that might
also provide such preferential access?  

>On totally private networks, I find the whole ETS SIP concept entirely
>plausible. I would note that the "I" in "IEPREP" is for Internet,
>though. I
>have always understood that to be the capital-"I" Internet, as in
>RFC3271.

This is a good point.  I believe many in ieprep have interest in developing
standards for IP networks (both those that are part of the Internet and
those that are not).    

Kimberly
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 01:29:34 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05632
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 01:29:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2E6iLK06066
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 01:44:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2E6iLO06063
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 01:44:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05621
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 01:29:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2E6hSO06007;
	Fri, 14 Mar 2003 01:43:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2E6fYO05919
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 01:41:34 -0500
Received: from mail1.telekom.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05506
	for <sipping@ietf.org>; Fri, 14 Mar 2003 01:26:14 -0500 (EST)
Received: from g8pbr.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Fri, 14 Mar 2003 07:28:23 +0100
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <G43BDRDW>; Fri, 14 Mar 2003 07:28:23 +0100
Message-Id: <953B9B08F98DD61183F8000347AE66011ACC77@G8PPV.blf01.telekom.de>
From: "Jesske, R" <R.Jesske@telekom.de>
To: sgarg@aastra.com, jon.peterson@neustar.biz, drage@lucent.com,
        sipping@ietf.org
Subject: AW: [Sipping] RFC 3398: REL cause
Date: Fri, 14 Mar 2003 07:28:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2E6fYO05920
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

HI,
I can agree that this is not stated within Q.764, Q.1902 and in the Q.1912.SIP draft (the ITU SIP-ISUP/BICC interworking). Also I can agree that this is not an IETF matter how to release a call on ISUP side.

The only hint with regard to this issue is the Q.699 as I stated earlier. 

In Q.699 Table 23(DSS1-ISUP mapping) the interworking is described as following:
Determination that the called number information received is incomplete, after an IAM message has already been sent 
--> therefore REL with Cause 28 is send in forward and Backward direction.


        DSS1                       IWU                      PSTN
        1|---------SETUP----------->|                          |
         |                          |                          |
         |                          |------------IAM---------->|2
         |                          |<=========Audio===========|
         |                          |    *** T7 Expires ***    |
         |                          |                          |
        4|<----------REL------------|------------REL---------->|3
         |         Cause 28         |          Cause 28        |


The only indication where I know that this fackt will be indicated to the Interworking unit is the expiry of T7.

The other cause as proposed by Sumit (31) is more common and could be also valid.

Due to the fact that this is a ITU issue, this will be discussed at the next ITU Meeting in Paris (April). 

Best Regards 

Roland



> -----Ursprüngliche Nachricht-----
> Von: Sumit Garg [mailto:sgarg@aastra.com]
> Gesendet: Donnerstag, 13. März 2003 19:34
> An: 'Peterson, Jon'; 'Drage, Keith (Keith)'; Sumit Garg;
> sipping@ietf.org
> Betreff: RE: [Sipping] RFC 3398: REL cause
> 
> 
> Some notes at the end:
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Sumit Garg
> Aastra Telecom US
> 8 Federal Street
> Billerica, MA 01821
> 978-436-4244
> email: <<mailto:sgarg@aastra.com>>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> 
> 
> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> Sent: Thursday, March 13, 2003 12:43 PM
> To: 'Drage, Keith (Keith)'; 'Sumit Garg'; sipping@ietf.org
> Subject: RE: [Sipping] RFC 3398: REL cause
> 
> 
> 
> Some notes below.
> 
> Jon Peterson
> NeuStar, Inc.
> 
> > -----Original Message-----
> > From: Drage, Keith (Keith) [mailto:drage@lucent.com]
> > Sent: Thursday, March 13, 2003 7:45 AM
> > To: 'Sumit Garg'; sipping@ietf.org
> > Subject: RE: [Sipping] RFC 3398: REL cause
> >
> >
> > I had some problem trying to identify the problem that is
> > trying to be solved here, and that is because it is out of scope.
> >
> > The text in section 7.2.2 of RFC 3398, that states
> >
> > "A REL message with cause value 102 (protocol error,
> >    recovery on timer expiry) SHOULD be sent to the PSTN. "
> >
> > is a purely ISUP / BICC protocol procedure and nothing to do
> > with any interworking. Interworking documents should not
> > attempt to rewrite the protocols on either side of the
> > interworking point. Therefore this sentence SHOULD be deleted
> > from any future version of RFC 3398. Can the authors please
> > note this in the appropriate bug list.
> >
> 
> >You are quite correct on this matter, Mr. Drage.
> 
> > Looking at the BICC specification, I cannot actually see a
> > point where it specifies a cause value to be included in the
> > ISUP REL message, and therefore presumably it is up to the
> > implementor to choose an appropriate one.
> >
> > I would believe that #28 would be inappropriate, but that
> > belief is irrelevant to this list, as this is an ISUP
> > response to an ISUP timer expiry.
> 
> 
> >Agreed both that #28 is bad and that this is largely 
> irrelevant to SIP-ISUP
> >interworking. Well, if literally nothing is specified for 
> this case in the
> >relevant ITU-T specs, then it couldn't hurt for us to make a 
> suggestion,
> but
> >making a normative one is inappropriate.
> 
> > For 7.1.3, I guess these are more informative, although I
> > would have preferred a different terminology to "MG Releases
> > PSTN Trunk" which implies to me that the trunk is released as
> > part of interworking, when it is a purely ISUP / BICC
> > protocol action that is causing this.
> >
> 
> >7.1.3 is useful in so far as it's nice to know that 504 is 
> sent in the
> >backwards direction in this instance, and so on.
> 
> >One more note below.
> 
> >
> > Keith
> 
> > > -----Original Message-----
> > > From: Sumit Garg [mailto:sgarg@aastra.com]
> 
> 
> > > It would be more logical if it just sent 31
> > > and 480.
> > >
> > > -Sumit
> > >
> > >
> 
> >I'm not sure #31 is so great for this either. But leaving 
> that aside, 480
> >represents a radically different condition in SIP networks 
> (which is very
> >close to cause #19). It would not be appropriate to send a 
> 480 response
> >here.
> -------------
> 
> I am pasting the section of table 1 from Q.850 which defines 
> the Causes to
> be used.
> Cause
> Value    No        Definition                  Diagnostics  
> Application
> 
>  1111    31         Normal, unspecified                       
>  DSS1,ISUP
> 
> 
> References       Location           Remarks
> Q.931		     RLN                Call  information failure
> 
> 2.1.1/Q.764      TN, INTL, RLN      indicating the failure
> 2.1.2/Q.764                          of a call due to the
>  2.8.1/Q.764                         lapse of a timeout  
> 2.8.2/Q.764                          or a fault not covered
>  2.9.3/Q.764                         by specific causes
> 2.9.6/Q.764                          (examples: expiry of timers
> 2.9.8.2/Q.764                        Q.764 not covered by
> 2.9.8.3/Q.764                        specific causes, release of
> 2.1.8/Q.764                          interconnected circuit, etc.)
>  2.2.4/Q.764
> 
> Thus for the ISUP side the most likely cause would be 31.
> So I mapped this 31 as per RFC3398 to get 480 as the SIP 
> release cause;
>  which per se is not all that bad...
> It would just cause the request to be made again (I hope) after some
> time..and then
> we would hopefully not have an ACM timeout. 
> 504 for sure is better; but consider a case where the ACM 
> timeout occurs
> on a switch between the SS7-SIP gateway and the destination. 
> The Gateway
> would still
> recv 31 and map it to 480 evoking the behaviour which is 
> closer to Release
> Cause 19 ;-)
> 
> So would it really matter if the gateway itself sent the 
> release cause of
> 480 instead
> of 504 on timeout??
> 
> I totally agree that the RFC should not make any suggestion 
> towards the
> causes to be
> be used on the protocols being interworked. That should be 
> done only in
> their respective
> specs/RFCs.
> 
> --Sumit
> 
> 
> 
> 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 05:48:37 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21461
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 05:48:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EB3T800506
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 06:03:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EB3TO00503
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 06:03:29 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21452
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 05:48:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EB2hO00485;
	Fri, 14 Mar 2003 06:02:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EB1cO00431
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 06:01:38 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21393
	for <sipping@ietf.org>; Fri, 14 Mar 2003 05:46:12 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2EAmCC03339;
	Fri, 14 Mar 2003 10:48:12 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JTXG9>; Fri, 14 Mar 2003 05:48:30 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F2B@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Henning Schulzrinne'" <hgs@cs.columbia.edu>,
        "King, Kimberly S."
	 <KIMBERLY.S.KING@saic.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Date: Fri, 14 Mar 2003 05:48:29 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


inline.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> Sent: Thursday, March 13, 2003 6:34 AM
> To: King, Kimberly S.
> Cc: 'jon.peterson@neustar.biz'; 'sipping@ietf.org'
> Subject: Re: [Sipping] Comments on draft-peterson-sipping-ieprep-00
> 
> 
> Since partial coverage seems to be the crux of the matter, let me try to 
> add a few words. We should probably be careful to distinguish three 
> types of 'partial coverage', as their likely effect on ETS will differ.
> 

I think this is the sort of analysis that's required, yes. I've added some
notes inline, but basically just expanding on what you have below.

> (1) UAS as PSTN gateways
> 
> First, we can have partial coverage in PSTN gateways. Clearly, if all my 
> calls are routed to a non-ETS gateway, then all the indications in the 
> world, however done, are pointless. Until all or almost all gateways 
> support ETS, deployments may need to force call routing and avoid the 
> use of default gateway discovery (i.e., tel URIs.). Since I can discover 
> gateway support, a smart end system could try default routing first and 
> if that fails, use source routing to reach a known entry point.
> 

Let me make sure I understand. So UACs would either throw out a tel URL, and
let proxies (presumably the default outbound) route it as they will, or UACs
would form some sort of sip:tel@gateway URI (if that's what you mean by
'source routing') or perhaps the URI of a particular proxy that fronts for a
farm of such ETS-compliant gateways. The latter addresses the possibility
that the UAC's local proxy will not be ETS-capable (and hence this is an
important partial coverage case). To mitigate that, users are informed of
one or more known-capable URI which can be called when the proxy
infrastructure doesn't support ETS. That seems reasonable, though somewhat
intensive on the user's memory. Not really more intensive, I suppose, than
carrying around GETS numbers.

Presumably, the discovery capability (in REQ-14) can let the UAC know if the
proxy supported ETS, rather than just determining if the gateway supported
ETS. There's also some question of whether or not the UAC needs to place a
call to learn if the proxy supports ETS (I suppose something like OPTIONS
Proxy-Require would be in order). In any event, it would definitely be
better to detect this condition at the proxy in these partial deployment
cases, and it would be best if the UAC didn't have to place a call to do so.

Another important aspect of gateway priority management seems to be the
'context' in which prioritization is asserted. Even if we assume that all
gateways support ETS, it isn't that case that all gateways would respect all
contexts (i.e. that an Iraqi general would receive priority in the United
States). The concept is certainly noted by the requirements (REQ-14), but it
seems like another potential cause of partial coverage for any given call.

> This offers a transition mechanism that improves as deployment improves. 
> (This is somewhat similar to the need to dial 1010xxx to reach a 
> 710-aware carrier in the GETS system.)
> 

A system which has no effect on congestion in the LEC, but is better than
nothing.

> (2) UAS as SIP devices, but not gateways
> 
> Some people have pointed out that it would be useful to have SIP 
> endpoints, such as IP phones or ACD systems, handle ETS calls 
> differently, from flashing an orange light to bypassing the call queue. 
> Again, while universal coverage is nice, the alternative of not 
> indicating ETS is no better. After all, existing ETS systems also have 
> the problem that phone end systems may not know that the call is an ETS 
> call and are still useful.
> 

Agreed, I'm not particularly concerned about prioritized calls to SIP UAs
that don't support ETS. It is hard for me to see, though, how much benefit
these mechanisms really provide in the SIP-to-SIP cases. There is virtually
no behavior required of the UAC, proxy, or UAS in this case - while it may
be no worse than unprioritized SIP calls, it's hard to see how it's better.

I think it is also worth considering the case in which the UAC is a SIP
device that does not support ETS. In that case, while it is no doubt
possible to place calls to proxies and gateways that support ETS, the UAC
would presumably be unable to discover whether or not the priority mechanism
is supported. Depending on the authentication methods accepted by the proxy
(and the nature of the mechanism, I suppose), a user agent could also prove
that it requires prioritization and rely on the proxy to add some sort of
prioritization indicator on the UA's behalf (though I'm still unsure how to
read REQ-4 on this subject - it seems to suggest that ETS UAs should support
some special authentication methods).

> (3) Partial coverage in proxies
> 
> This matters in two ways, depending on how proxies use the RP 
> indication. If it's used for routing, the need depends on issue (1). You 
> could either have lots of RP-aware proxies and relatively few 
> specialized gateways or the converse. (If all gateways are RP-aware, 
> proxy routing isn't all that important.)
> 

Like gateway support, I assume proxy support of ETS is also specific to a
particular context, with the same ramifications for partial coverage.

If the only prioritization function that proxies provide is ETS gateway
discovery, then it is worth noting that proxy support for ETS is useless
unless the proxy knows of an appropriate gateway.

Another proxy case that's worth examining is one in which the UAC must go
through some local outbound proxy that doesn't support ETS, and the effects
of that. Does the source-routing requirement extend to this case? I suppose
pre-loaded Route headers could be used to traverse proxies that might
otherwise route a call for a tel URL to a local gateway (perhaps especially
for emergency numbers). I gather that REQ-3 is partly intended to cover
something like this case.

> Proxies could use RP for prioritized call handling to deal with 
> signaling overload.
> 

This idea does concern me a little. If you've gone through the processing of
the message to the point that you're extracting an RP header (to take that
one mechanism as an example), then you've already expended a significant
amount of the energy that a proxy puts into the processing of an entire
request. But moreover, it seems to be this sort of grey area - neither in
scope nor out of scope of the requirements.

> I think in all cases, the issue is increased *probability* of call 
> completion. I can't see how partial deployment could be worse than no 
> deployment, particularly if the most-likely-to-be-scarce resources are 
> enabled first. My guess is that those scarce resources are the 
> gateways/PSTN circuits, where we have a reasonable chance of making this 
> work. 

Agreed that partial deployment of ETS will be no worse than no deployment
(provided that security issues are all handled well - if the system is
exploitable, it could be quite a bit worse). I also agree that the scarcity
of gateway resources is one of the paramount concerns.

> This would not require international cooperation - indeed, as long 
> as the Internet side stays up, this may make calls from abroad into a 
> national ETS system far more likely to work. I think that type of 
> international usage is the more likely one (officials traveling abroad, 
> etc.).
> 
> Clearly, the access links from the SIP endpoint to the gateway could be 
> congested, but the experts in IEPREP tell us that the Internet never 
> gets congested, so this is nothing to be concerned about. (In any event, 
> it's not the concern of the mechanism under discussion here.)
> 

Well, I was just citing the access links as one example - the partial
coverage cases described above are just as important, and seem more like
they should be in the scope of this work.

> Henning
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 05:52:17 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21519
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 05:52:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EB7Bt00871
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 06:07:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EB7BO00868
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 06:07:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21511
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 05:51:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EB64O00612;
	Fri, 14 Mar 2003 06:06:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EB5dO00575
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 06:05:39 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21477
	for <sipping@ietf.org>; Fri, 14 Mar 2003 05:50:14 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2EAqGC03350;
	Fri, 14 Mar 2003 10:52:16 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JTXHB>; Fri, 14 Mar 2003 05:52:34 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F2C@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Drage, Keith (Keith)'" <drage@lucent.com>,
        "'Elwell, John'"
	 <john.elwell@siemens.com>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 14 Mar 2003 05:52:33 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Below.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Drage, Keith (Keith) [mailto:drage@lucent.com]
> Sent: Thursday, March 13, 2003 12:02 PM
> To: 'Peterson, Jon'; 'Elwell, John'; 'Mark Watson'
> Cc: 'sipping@ietf.org'
> Subject: RE: [Sipping] New version of the early media draft
> 
[snip]
> > What
> > should the UAC do differently because condition 2 prevails, as opposed
to
> > condition 3?
> > 
> I believe the distinction is that in case 2) it is 
> appropriate to write "ringing" or "call delivered" or 
> "waiting answer" or such like on the display of the UAC, or 
> whatever additional indications are given to the user over 
> and above the in-band tones/announcements. In case 3 it is not.
> 

Once a SIP endpoint has gotten a provisional response from a PSTN gateway,
then from SIP's perspective the call has been delivered - we're essentially
interworking with a network that (we must conclude from this thread) is
unable to express its status out-of-band. The value of a visual display that
says "alerting" when the in-band media is saying something different (like
"queuing") is really questionable.

So what's the difference between what you show the user and what you tell
them? Many users have both working eyes and ears, I agree, but that doesn't
mean they'll benefit from seeing a visual display when what they need to
understand the state of the call isto hear the in-band media. Some UACs will
not support the visual display, just as some would not ordinarily play
in-band pre-answer media.

> Given the number of different non-standard ring tones out 
> there, the user may actually be relying on this extra 
> information to know that the tone he is listening to is 
> actually the ring tone he thinks it is, and not so other 
> variety of busy tone. In one case he can terminate the call 
> immediately, and in the other case he should cannot.
> 

Well, that's the first slightly credible argument I've heard on this point,
but I still don't find it satisfactory. If the tone were actually a busy
tone, the user wouldn't be hearing it - they'd be looking at a 486 response
code. This just speaks to the degree to which the PSTN in-band user
signaling paradigm is ingrained in this conversation, though. We need to
avoid using in-band status information in SIP at all, to the degree that we
can.

> I think the issue here is that the user is essentially 
> dialling a PSTN user in both these cases, and therefore it is 
> reasonable to present to the user at the UAC the indications 
> that he would expect to get back from the PSTN. 
> 

A PSTN user gets back an indication that the remote side is being alerted,
other than the in-band media? I don't see that displayed on my phone.

> In terms of the solution, presenting 183 in both cases 2 and 
> 3 without some additional indication is misleading. 
> Furthermore the tone/announcement in this case could well 
> assume that the signalling level distinction available in the 
> ISUP has been made available to the end user.
> 

It's the PSTN that is misleading, I think, not how we choose to map the
status codes. This is just like ISUP interworking with legacy CAS networks.
We could say that sending ACM is 'misleading' is ISUP-CAS interworking
cases, because in truth there may be a busy signal on the line. It's not
ISUP's fault, though - that's the only way it can contend with the CAS
network.

> There is also the case of providing appropriate level of 
> signalling to support the SHOULD discussed below.
> 
> > If the UAC receives media, it should be playing it. I don't think it's a
> > matter, as you describe in 2, that a UAC should merely consider playing
it.
> > Given that, 2 and 3 seem to be identical. Making the UAC responsible for
> > deciding whether or not to play the media seems like the wrong model to
me.
> > The gateway, which actually inspects and understands PSTN signaling,
should
> > decide whether or not delivering media to the UAC is necessary.
> > 
> As far as the UAC is concerned, in general I agree that if 
> the UAC receives media, it should be playing it. I consider 
> it unsafe to write a MUST here, and would default to a 
> SHOULD, as there may be specific user interface 
> considerations that make it incorrect or inappropriate.
> 

User interface considerations or UAC gateway operator policies, a more
likely case. If media arrives at a non-gateway UAC, and the UAC doesn't play
it for some reason, the UAC should be telling its user "pre-answer media is
arriving and it's trying to tell you something, but I don't know what"

> I think it is also an assumption that all gateways can 
> actually look at the in-band media and reliably detect what 
> has been indicated. Any specification for early media must 
> deal with both the cases, i.e. where the media gateway 
> controller is not doing media detection, and that where it is. 
> 

I have in no way suggested that in-band media can be mined by applications
for status information - just that it needs to be passed to the user. By
media detection, here, I'm just talking about detecting the condition that
some RTP has arrived, not inspecting the media programmatically to determine
its contents.

When you send an INVITE, you need to be prepared to start receiving media
immediately. This is essentially a requirement for the sort of media
detection I'm describing.

> By the way, I suspect that this would need to be somewhat 
> more sophisticated that just looking at the media stream at 
> when the indication arrives; the nature of in-band 
> information can change over time, and thus the nature of any 
> appropriate indication to be given. There is also the problem 
> of distinguishing noice (generated from transmission of the 
> PSTN path over 20 miles of barbed wire) versus real signal.
> 

Agreed that gateways are not in a position to understand what the media is.
My contention is only that if there is media, it has to be played for the
user.

> Note also that while ITU-T specifies characteristics of these 
> tones, PSTN equipment has a lifetime that tends to exceed the 
> lifetime of a harmonised ITU specification of these tones. In 
> practice there are 57 different varieties of all these tones 
> out there, and there are laws of nature that state that the 
> first ones you find in the field are the odd ones.
> 
> 
> <snipped>
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 06:03:12 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22069
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 06:03:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EBI6t01845
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 06:18:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EBI5O01842
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 06:18:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21995
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 06:02:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EBGAO01758;
	Fri, 14 Mar 2003 06:16:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EBF8O01710
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 06:15:08 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21689
	for <sipping@ietf.org>; Fri, 14 Mar 2003 05:59:43 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2EB1rC03435;
	Fri, 14 Mar 2003 11:01:53 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JTX2L>; Fri, 14 Mar 2003 06:02:12 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F2D@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>
Cc: "''sipping@ietf.org' '" <sipping@ietf.org>,
        "''hgs@cs.columbia.edu' '"
	 <hgs@cs.columbia.edu>
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Date: Fri, 14 Mar 2003 06:02:10 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Some notes inline.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: King, Kimberly S. [mailto:KIMBERLY.S.KING@saic.com]
> Sent: Thursday, March 13, 2003 5:59 PM
> To: 'Peterson, Jon '; ''King, Kimberly S.' '
> Cc: ''sipping@ietf.org' '; ''hgs@cs.columbia.edu' '
> Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
> 
[snip]
> 
> Okay, the ideas I'm about to present represent my personal thoughts. 
> 
> Why should ETS need to justify the absence of congestion in the access
links
> or other parts of the network (thereby proving optional preferential
> treatment is justified) when the default system operates without respect
to
> transport congestion?  We are just trying to increase our odds with the
> default system.  Why not have transport congestion issues, where
> appropriate, handled independently?
> 

Well, I didn't mean to pick on transport congestion - I was just trying to
illustrate a case in which part of the network didn't support ETS and it had
deleterious effects. There are clearly other aspects of partial coverage
that are worthy of analysis (some of which I just talked about in another
mail).

[snip]
> 
> I agree with you that if gateways are the only issue then this could
affect
> the design.  However, are there not media or application servers that
might
> also provide such preferential access?  
> 

That's a good point, yes. I wouldn't ordinarily think application servers
are constrained resources, but media servers tend to have ports, just like
gateways. I suppose that an emergency call could constitute listening to
some sort of announcements or leaving a message, which could entail a media
server, but I hadn't really given the matter much thought. On initial
reflection, I imagine that it would be more difficult to enable media
servers to handle prioritization than it would be for gateways... or at
least, given how diverse media servers are, it would be difficult to
generalize this emergency behavior into useful guidelines.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 06:11:52 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22198
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 06:11:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EBQkq02154
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 06:26:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EBQkO02151
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 06:26:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22187
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 06:11:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EBP9O02103;
	Fri, 14 Mar 2003 06:25:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EBOTO02064
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 06:24:29 -0500
Received: from smail3.alcatel.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22138
	for <sipping@ietf.org>; Fri, 14 Mar 2003 06:09:03 -0500 (EST)
From: Pascal.Jalet@alcatel.fr
Received: from frmail21.netfr.alcatel.fr (frmail21.netfr.alcatel.fr [155.132.182.151])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id h2EBBEqj003278;
	Fri, 14 Mar 2003 12:11:14 +0100
To: <sipping@ietf.org>, "Eric Burger" <eburger@snowshore.com>
Date: Fri, 14 Mar 2003 12:11:12 +0100
Message-ID: <OFB439489B.59944C9B-ONC1256CE9.00361671@netfr.alcatel.fr>
X-MIMETrack: Serialize by Router on FRMAIL21/FR/ALCATEL(Release 5.0.8 |June 18, 2001) at
 03/14/2003 12:11:14
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Virus-Scanned: by amavisd-new
Subject: [Sipping] URI parameters and draft-burger-sipping-netann-05
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Eric , Dear SIPPING members,
In the network model on which is based  the draft-burger-sipping-netann-05,
do you make the assumption that the proxy that requires announcement
playing
to the media server  is the "last hop" proxy?

In case , not, we have the risk that  the proxies that are on the path to
the media server,
may change or remove the uri parameters that describes the annoucemement.

I say so,because  in RFC 3261, It is not guarantied that a proxy copies
"transparently"
the URI parameters in the forwarded request (am I right?)

So I have a more general question. Should announcement description be
included in uri parameters?
shouldn't user part be a better place for this?

Thanks for your help

Pascal

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 07:00:58 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23225
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 07:00:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2ECFpd05581
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 07:15:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ECFpO05578
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 07:15:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23206
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 07:00:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ECDUO05448;
	Fri, 14 Mar 2003 07:13:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ECBeO05357
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 07:11:40 -0500
Received: from znsgs01r.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23086
	for <sipping@ietf.org>; Fri, 14 Mar 2003 06:56:12 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (europem01.nt.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2EBw7n26496;
	Fri, 14 Mar 2003 11:58:07 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GR68NLJX; Fri, 14 Mar 2003 11:58:07 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GR4VQGPT>; Fri, 14 Mar 2003 11:57:06 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7CB5@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'Drage, Keith (Keith)'"
	 <drage@lucent.com>,
        "'Elwell, John'" <john.elwell@siemens.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 14 Mar 2003 11:57:06 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2EA20.D5BF3EEE"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2EA20.D5BF3EEE
Content-Type: text/plain;
	charset="iso-8859-1"

Jon,

You claimed that Keith's case 2 and case 3 were identical, but I do not see
how this can be.

In both cases, in-band media is available.

In case 2, it is known that the called user is being informed of the
presence of the request (at least if they are physically present, they are),
in case 3 this is now known. I do not see how any definition of identical
can be applied to these two cases.

A different claim would be that *for the purposes of the UAC* these cases
are identical, because all the UAC does in both cases is play the media.

But I think you are making too many assumptions about what the UAC may or
may not be able to use this information for. As a general rule, I would err
on the side of providing this information to the UAC, if only to assist in
future scenarios that we haven't yet thought of.

In terms of specific examples:
1) Keith mentioned that some ringing tones around the world are not
dissimilar from busy tones elsewhere in the world. It is entirely possible
for the user on a SIP terminal to end up hearing remotely generated busy
tone and you give an example of CAS interworking yourself - this would be
case 3. The additional indication available in Case 2 may give the user
additional confidence that what they are hearing really is a ring-tone.

2) In a forking case, the UAC may have early media arriving from multiple
sources. There is very little the UAC itself can tell about the call state
of these multiple calls - the media needs to be presented to a human user
for interpretation. I think in this case any additional information that the
UAC can be provided with about call state will be helpful. The user may also
find these indications useful in deciding which of several forks to listen
to first.

I think that whenever we have an indication that the user is being alerted
we should pass this to the UAC, using a 180 message. 183 should only be used
if we have no information. Indeed, this is what is specified in the ISUP
interworking work.

The problem remains of distinguishing at the SIP layer between 180 with no
media and 180 with media.

...Mark

> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> Sent: 14 March 2003 10:53
> To: 'Drage, Keith (Keith)'; 'Elwell, John'; Watson, Mark 
> [MOP:EP10:EXCH]
> Cc: 'sipping@ietf.org'
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> 
> Below.
> 
> Jon Peterson
> NeuStar, Inc.
> 
> > -----Original Message-----
> > From: Drage, Keith (Keith) [mailto:drage@lucent.com]
> > Sent: Thursday, March 13, 2003 12:02 PM
> > To: 'Peterson, Jon'; 'Elwell, John'; 'Mark Watson'
> > Cc: 'sipping@ietf.org'
> > Subject: RE: [Sipping] New version of the early media draft
> > 
> [snip]
> > > What
> > > should the UAC do differently because condition 2 
> prevails, as opposed
> to
> > > condition 3?
> > > 
> > I believe the distinction is that in case 2) it is 
> > appropriate to write "ringing" or "call delivered" or 
> > "waiting answer" or such like on the display of the UAC, or 
> > whatever additional indications are given to the user over 
> > and above the in-band tones/announcements. In case 3 it is not.
> > 
> 
> Once a SIP endpoint has gotten a provisional response from a 
> PSTN gateway,
> then from SIP's perspective the call has been delivered - 
> we're essentially
> interworking with a network that (we must conclude from this 
> thread) is
> unable to express its status out-of-band. The value of a 
> visual display that
> says "alerting" when the in-band media is saying something 
> different (like
> "queuing") is really questionable.
> 
> So what's the difference between what you show the user and 
> what you tell
> them? Many users have both working eyes and ears, I agree, 
> but that doesn't
> mean they'll benefit from seeing a visual display when what 
> they need to
> understand the state of the call isto hear the in-band media. 
> Some UACs will
> not support the visual display, just as some would not ordinarily play
> in-band pre-answer media.
> 
> > Given the number of different non-standard ring tones out 
> > there, the user may actually be relying on this extra 
> > information to know that the tone he is listening to is 
> > actually the ring tone he thinks it is, and not so other 
> > variety of busy tone. In one case he can terminate the call 
> > immediately, and in the other case he should cannot.
> > 
> 
> Well, that's the first slightly credible argument I've heard 
> on this point,
> but I still don't find it satisfactory. If the tone were 
> actually a busy
> tone, the user wouldn't be hearing it - they'd be looking at 
> a 486 response
> code. This just speaks to the degree to which the PSTN in-band user
> signaling paradigm is ingrained in this conversation, though. 
> We need to
> avoid using in-band status information in SIP at all, to the 
> degree that we
> can.
> 
> > I think the issue here is that the user is essentially 
> > dialling a PSTN user in both these cases, and therefore it is 
> > reasonable to present to the user at the UAC the indications 
> > that he would expect to get back from the PSTN. 
> > 
> 
> A PSTN user gets back an indication that the remote side is 
> being alerted,
> other than the in-band media? I don't see that displayed on my phone.
> 
> > In terms of the solution, presenting 183 in both cases 2 and 
> > 3 without some additional indication is misleading. 
> > Furthermore the tone/announcement in this case could well 
> > assume that the signalling level distinction available in the 
> > ISUP has been made available to the end user.
> > 
> 
> It's the PSTN that is misleading, I think, not how we choose 
> to map the
> status codes. This is just like ISUP interworking with legacy 
> CAS networks.
> We could say that sending ACM is 'misleading' is ISUP-CAS interworking
> cases, because in truth there may be a busy signal on the 
> line. It's not
> ISUP's fault, though - that's the only way it can contend with the CAS
> network.
> 
> > There is also the case of providing appropriate level of 
> > signalling to support the SHOULD discussed below.
> > 
> > > If the UAC receives media, it should be playing it. I 
> don't think it's a
> > > matter, as you describe in 2, that a UAC should merely 
> consider playing
> it.
> > > Given that, 2 and 3 seem to be identical. Making the UAC 
> responsible for
> > > deciding whether or not to play the media seems like the 
> wrong model to
> me.
> > > The gateway, which actually inspects and understands PSTN 
> signaling,
> should
> > > decide whether or not delivering media to the UAC is necessary.
> > > 
> > As far as the UAC is concerned, in general I agree that if 
> > the UAC receives media, it should be playing it. I consider 
> > it unsafe to write a MUST here, and would default to a 
> > SHOULD, as there may be specific user interface 
> > considerations that make it incorrect or inappropriate.
> > 
> 
> User interface considerations or UAC gateway operator policies, a more
> likely case. If media arrives at a non-gateway UAC, and the 
> UAC doesn't play
> it for some reason, the UAC should be telling its user 
> "pre-answer media is
> arriving and it's trying to tell you something, but I don't know what"
> 
> > I think it is also an assumption that all gateways can 
> > actually look at the in-band media and reliably detect what 
> > has been indicated. Any specification for early media must 
> > deal with both the cases, i.e. where the media gateway 
> > controller is not doing media detection, and that where it is. 
> > 
> 
> I have in no way suggested that in-band media can be mined by 
> applications
> for status information - just that it needs to be passed to 
> the user. By
> media detection, here, I'm just talking about detecting the 
> condition that
> some RTP has arrived, not inspecting the media 
> programmatically to determine
> its contents.
> 
> When you send an INVITE, you need to be prepared to start 
> receiving media
> immediately. This is essentially a requirement for the sort of media
> detection I'm describing.
> 
> > By the way, I suspect that this would need to be somewhat 
> > more sophisticated that just looking at the media stream at 
> > when the indication arrives; the nature of in-band 
> > information can change over time, and thus the nature of any 
> > appropriate indication to be given. There is also the problem 
> > of distinguishing noice (generated from transmission of the 
> > PSTN path over 20 miles of barbed wire) versus real signal.
> > 
> 
> Agreed that gateways are not in a position to understand what 
> the media is.
> My contention is only that if there is media, it has to be 
> played for the
> user.
> 
> > Note also that while ITU-T specifies characteristics of these 
> > tones, PSTN equipment has a lifetime that tends to exceed the 
> > lifetime of a harmonised ITU specification of these tones. In 
> > practice there are 57 different varieties of all these tones 
> > out there, and there are laws of nature that state that the 
> > first ones you find in the field are the odd ones.
> > 
> > 
> > <snipped>
> > 
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Jon,</FONT>
</P>

<P><FONT SIZE=3D2>You claimed that Keith's case 2 and case 3 were =
identical, but I do not see how this can be.</FONT>
</P>

<P><FONT SIZE=3D2>In both cases, in-band media is available.</FONT>
</P>

<P><FONT SIZE=3D2>In case 2, it is known that the called user is being =
informed of the presence of the request (at least if they are =
physically present, they are), in case 3 this is now known. I do not =
see how any definition of identical can be applied to these two =
cases.</FONT></P>

<P><FONT SIZE=3D2>A different claim would be that *for the purposes of =
the UAC* these cases are identical, because all the UAC does in both =
cases is play the media.</FONT></P>

<P><FONT SIZE=3D2>But I think you are making too many assumptions about =
what the UAC may or may not be able to use this information for. As a =
general rule, I would err on the side of providing this information to =
the UAC, if only to assist in future scenarios that we haven't yet =
thought of.</FONT></P>

<P><FONT SIZE=3D2>In terms of specific examples:</FONT>
<BR><FONT SIZE=3D2>1) Keith mentioned that some ringing tones around =
the world are not dissimilar from busy tones elsewhere in the world. It =
is entirely possible for the user on a SIP terminal to end up hearing =
remotely generated busy tone and you give an example of CAS =
interworking yourself - this would be case 3. The additional indication =
available in Case 2 may give the user additional confidence that what =
they are hearing really is a ring-tone.</FONT></P>

<P><FONT SIZE=3D2>2) In a forking case, the UAC may have early media =
arriving from multiple sources. There is very little the UAC itself can =
tell about the call state of these multiple calls - the media needs to =
be presented to a human user for interpretation. I think in this case =
any additional information that the UAC can be provided with about call =
state will be helpful. The user may also find these indications useful =
in deciding which of several forks to listen to first.</FONT></P>

<P><FONT SIZE=3D2>I think that whenever we have an indication that the =
user is being alerted we should pass this to the UAC, using a 180 =
message. 183 should only be used if we have no information. Indeed, =
this is what is specified in the ISUP interworking work.</FONT></P>

<P><FONT SIZE=3D2>The problem remains of distinguishing at the SIP =
layer between 180 with no media and 180 with media.</FONT>
</P>

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

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Peterson, Jon [<A =
HREF=3D"mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz=
</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 14 March 2003 10:53</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Drage, Keith (Keith)'; 'Elwell, John'; =
Watson, Mark </FONT>
<BR><FONT SIZE=3D2>&gt; [MOP:EP10:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'sipping@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Below.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Jon Peterson</FONT>
<BR><FONT SIZE=3D2>&gt; NeuStar, Inc.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Drage, Keith (Keith) [<A =
HREF=3D"mailto:drage@lucent.com">mailto:drage@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Thursday, March 13, 2003 12:02 =
PM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: 'Peterson, Jon'; 'Elwell, John'; 'Mark =
Watson'</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cc: 'sipping@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: RE: [Sipping] New version of the =
early media draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; [snip]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; What</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; should the UAC do differently because =
condition 2 </FONT>
<BR><FONT SIZE=3D2>&gt; prevails, as opposed</FONT>
<BR><FONT SIZE=3D2>&gt; to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; condition 3?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I believe the distinction is that in case =
2) it is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; appropriate to write &quot;ringing&quot; =
or &quot;call delivered&quot; or </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &quot;waiting answer&quot; or such like on =
the display of the UAC, or </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; whatever additional indications are given =
to the user over </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; and above the in-band tones/announcements. =
In case 3 it is not.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Once a SIP endpoint has gotten a provisional =
response from a </FONT>
<BR><FONT SIZE=3D2>&gt; PSTN gateway,</FONT>
<BR><FONT SIZE=3D2>&gt; then from SIP's perspective the call has been =
delivered - </FONT>
<BR><FONT SIZE=3D2>&gt; we're essentially</FONT>
<BR><FONT SIZE=3D2>&gt; interworking with a network that (we must =
conclude from this </FONT>
<BR><FONT SIZE=3D2>&gt; thread) is</FONT>
<BR><FONT SIZE=3D2>&gt; unable to express its status out-of-band. The =
value of a </FONT>
<BR><FONT SIZE=3D2>&gt; visual display that</FONT>
<BR><FONT SIZE=3D2>&gt; says &quot;alerting&quot; when the in-band =
media is saying something </FONT>
<BR><FONT SIZE=3D2>&gt; different (like</FONT>
<BR><FONT SIZE=3D2>&gt; &quot;queuing&quot;) is really =
questionable.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; So what's the difference between what you show =
the user and </FONT>
<BR><FONT SIZE=3D2>&gt; what you tell</FONT>
<BR><FONT SIZE=3D2>&gt; them? Many users have both working eyes and =
ears, I agree, </FONT>
<BR><FONT SIZE=3D2>&gt; but that doesn't</FONT>
<BR><FONT SIZE=3D2>&gt; mean they'll benefit from seeing a visual =
display when what </FONT>
<BR><FONT SIZE=3D2>&gt; they need to</FONT>
<BR><FONT SIZE=3D2>&gt; understand the state of the call isto hear the =
in-band media. </FONT>
<BR><FONT SIZE=3D2>&gt; Some UACs will</FONT>
<BR><FONT SIZE=3D2>&gt; not support the visual display, just as some =
would not ordinarily play</FONT>
<BR><FONT SIZE=3D2>&gt; in-band pre-answer media.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Given the number of different non-standard =
ring tones out </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; there, the user may actually be relying on =
this extra </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; information to know that the tone he is =
listening to is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; actually the ring tone he thinks it is, =
and not so other </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; variety of busy tone. In one case he can =
terminate the call </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; immediately, and in the other case he =
should cannot.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Well, that's the first slightly credible =
argument I've heard </FONT>
<BR><FONT SIZE=3D2>&gt; on this point,</FONT>
<BR><FONT SIZE=3D2>&gt; but I still don't find it satisfactory. If the =
tone were </FONT>
<BR><FONT SIZE=3D2>&gt; actually a busy</FONT>
<BR><FONT SIZE=3D2>&gt; tone, the user wouldn't be hearing it - they'd =
be looking at </FONT>
<BR><FONT SIZE=3D2>&gt; a 486 response</FONT>
<BR><FONT SIZE=3D2>&gt; code. This just speaks to the degree to which =
the PSTN in-band user</FONT>
<BR><FONT SIZE=3D2>&gt; signaling paradigm is ingrained in this =
conversation, though. </FONT>
<BR><FONT SIZE=3D2>&gt; We need to</FONT>
<BR><FONT SIZE=3D2>&gt; avoid using in-band status information in SIP =
at all, to the </FONT>
<BR><FONT SIZE=3D2>&gt; degree that we</FONT>
<BR><FONT SIZE=3D2>&gt; can.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I think the issue here is that the user is =
essentially </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; dialling a PSTN user in both these cases, =
and therefore it is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; reasonable to present to the user at the =
UAC the indications </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that he would expect to get back from the =
PSTN. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; A PSTN user gets back an indication that the =
remote side is </FONT>
<BR><FONT SIZE=3D2>&gt; being alerted,</FONT>
<BR><FONT SIZE=3D2>&gt; other than the in-band media? I don't see that =
displayed on my phone.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; In terms of the solution, presenting 183 =
in both cases 2 and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 3 without some additional indication is =
misleading. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Furthermore the tone/announcement in this =
case could well </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; assume that the signalling level =
distinction available in the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ISUP has been made available to the end =
user.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; It's the PSTN that is misleading, I think, not =
how we choose </FONT>
<BR><FONT SIZE=3D2>&gt; to map the</FONT>
<BR><FONT SIZE=3D2>&gt; status codes. This is just like ISUP =
interworking with legacy </FONT>
<BR><FONT SIZE=3D2>&gt; CAS networks.</FONT>
<BR><FONT SIZE=3D2>&gt; We could say that sending ACM is 'misleading' =
is ISUP-CAS interworking</FONT>
<BR><FONT SIZE=3D2>&gt; cases, because in truth there may be a busy =
signal on the </FONT>
<BR><FONT SIZE=3D2>&gt; line. It's not</FONT>
<BR><FONT SIZE=3D2>&gt; ISUP's fault, though - that's the only way it =
can contend with the CAS</FONT>
<BR><FONT SIZE=3D2>&gt; network.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; There is also the case of providing =
appropriate level of </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; signalling to support the SHOULD discussed =
below.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; If the UAC receives media, it should =
be playing it. I </FONT>
<BR><FONT SIZE=3D2>&gt; don't think it's a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; matter, as you describe in 2, that a =
UAC should merely </FONT>
<BR><FONT SIZE=3D2>&gt; consider playing</FONT>
<BR><FONT SIZE=3D2>&gt; it.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Given that, 2 and 3 seem to be =
identical. Making the UAC </FONT>
<BR><FONT SIZE=3D2>&gt; responsible for</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; deciding whether or not to play the =
media seems like the </FONT>
<BR><FONT SIZE=3D2>&gt; wrong model to</FONT>
<BR><FONT SIZE=3D2>&gt; me.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The gateway, which actually inspects =
and understands PSTN </FONT>
<BR><FONT SIZE=3D2>&gt; signaling,</FONT>
<BR><FONT SIZE=3D2>&gt; should</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; decide whether or not delivering =
media to the UAC is necessary.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; As far as the UAC is concerned, in general =
I agree that if </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the UAC receives media, it should be =
playing it. I consider </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; it unsafe to write a MUST here, and would =
default to a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; SHOULD, as there may be specific user =
interface </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; considerations that make it incorrect or =
inappropriate.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; User interface considerations or UAC gateway =
operator policies, a more</FONT>
<BR><FONT SIZE=3D2>&gt; likely case. If media arrives at a non-gateway =
UAC, and the </FONT>
<BR><FONT SIZE=3D2>&gt; UAC doesn't play</FONT>
<BR><FONT SIZE=3D2>&gt; it for some reason, the UAC should be telling =
its user </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;pre-answer media is</FONT>
<BR><FONT SIZE=3D2>&gt; arriving and it's trying to tell you something, =
but I don't know what&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I think it is also an assumption that all =
gateways can </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; actually look at the in-band media and =
reliably detect what </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; has been indicated. Any specification for =
early media must </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; deal with both the cases, i.e. where the =
media gateway </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; controller is not doing media detection, =
and that where it is. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I have in no way suggested that in-band media =
can be mined by </FONT>
<BR><FONT SIZE=3D2>&gt; applications</FONT>
<BR><FONT SIZE=3D2>&gt; for status information - just that it needs to =
be passed to </FONT>
<BR><FONT SIZE=3D2>&gt; the user. By</FONT>
<BR><FONT SIZE=3D2>&gt; media detection, here, I'm just talking about =
detecting the </FONT>
<BR><FONT SIZE=3D2>&gt; condition that</FONT>
<BR><FONT SIZE=3D2>&gt; some RTP has arrived, not inspecting the media =
</FONT>
<BR><FONT SIZE=3D2>&gt; programmatically to determine</FONT>
<BR><FONT SIZE=3D2>&gt; its contents.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; When you send an INVITE, you need to be =
prepared to start </FONT>
<BR><FONT SIZE=3D2>&gt; receiving media</FONT>
<BR><FONT SIZE=3D2>&gt; immediately. This is essentially a requirement =
for the sort of media</FONT>
<BR><FONT SIZE=3D2>&gt; detection I'm describing.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; By the way, I suspect that this would need =
to be somewhat </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; more sophisticated that just looking at =
the media stream at </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; when the indication arrives; the nature of =
in-band </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; information can change over time, and thus =
the nature of any </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; appropriate indication to be given. There =
is also the problem </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; of distinguishing noice (generated from =
transmission of the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; PSTN path over 20 miles of barbed wire) =
versus real signal.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Agreed that gateways are not in a position to =
understand what </FONT>
<BR><FONT SIZE=3D2>&gt; the media is.</FONT>
<BR><FONT SIZE=3D2>&gt; My contention is only that if there is media, =
it has to be </FONT>
<BR><FONT SIZE=3D2>&gt; played for the</FONT>
<BR><FONT SIZE=3D2>&gt; user.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Note also that while ITU-T specifies =
characteristics of these </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; tones, PSTN equipment has a lifetime that =
tends to exceed the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; lifetime of a harmonised ITU specification =
of these tones. In </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; practice there are 57 different varieties =
of all these tones </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; out there, and there are laws of nature =
that state that the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; first ones you find in the field are the =
odd ones.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;snipped&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2EA20.D5BF3EEE--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 09:08:52 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25723
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 09:08:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EENnP13126
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 09:23:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EENnO13123
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 09:23:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25708
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 09:08:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EELfO13067;
	Fri, 14 Mar 2003 09:21:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EEKRO13028
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 09:20:27 -0500
Received: from mta06-svc.ntlworld.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25545
	for <sipping@ietf.org>; Fri, 14 Mar 2003 09:04:59 -0500 (EST)
Received: from winxp ([213.107.1.165]) by mta06-svc.ntlworld.com
          (InterMail vM.4.01.03.37 201-229-121-137-20020806) with SMTP
          id <20030314140709.PVCS20605.mta06-svc.ntlworld.com@winxp>;
          Fri, 14 Mar 2003 14:07:09 +0000
Message-ID: <000e01c2ea33$016b8310$a5016bd5@winxp>
From: "James Undery" <james.undery@ntlworld.com>
To: <Pascal.Jalet@alcatel.fr>, <sipping@ietf.org>,
        "Eric Burger" <eburger@snowshore.com>
References: <OFB439489B.59944C9B-ONC1256CE9.00361671@netfr.alcatel.fr>
Subject: Re: [Sipping] URI parameters and draft-burger-sipping-netann-05
Date: Fri, 14 Mar 2003 14:07:10 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Comment inline
----- Original Message -----
From: <Pascal.Jalet@alcatel.fr>
To: <sipping@ietf.org>; "Eric Burger" <eburger@snowshore.com>
Sent: Friday, March 14, 2003 11:11 AM
Subject: [Sipping] URI parameters and draft-burger-sipping-netann-05


> Eric , Dear SIPPING members,
> In the network model on which is based  the
draft-burger-sipping-netann-05,
> do you make the assumption that the proxy that requires announcement
> playing
> to the media server  is the "last hop" proxy?
>
> In case , not, we have the risk that  the proxies that are on the path to
> the media server,
> may change or remove the uri parameters that describes the annoucemement.
>
> I say so,because  in RFC 3261, It is not guarantied that a proxy copies
> "transparently"
> the URI parameters in the forwarded request (am I right?)

No you are wrong, RFC3261 states that a proxy that isn't responsible (i.e.
knows the location server) for the domain/IP of the request URI shouldn't
change the request URI this includes parameters that it doesn't know about.
As the request URI should be targeted at the media server (or else how will
it get there) intermediate proxies should not change or strip parameters.

> So I have a more general question. Should announcement description be
> included in uri parameters?
> shouldn't user part be a better place for this?

In order to work with RFC 2543 or misbehaving proxies this may seem a better
idea, but it seriously impacts how a location service would work with
multiple media servers and just seems philosophically wrong. IIRC this was
the subject of much debate when this draft was first presented.

James

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 10:10:35 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28079
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 10:10:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EFPX017098
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 10:25:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFPXO17095
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 10:25:33 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28015
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 10:10:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFNgO16929;
	Fri, 14 Mar 2003 10:23:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFJtO16731
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 10:19:55 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27203
	for <sipping@ietf.org>; Fri, 14 Mar 2003 10:04:26 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Digit suppression (was [Sipping] Comments on updated KPML draft)
Date: Fri, 14 Mar 2003 10:08:49 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D2488E1@zoe.office.snowshore.com>
Thread-Topic: [Sipping] Comments on updated KPML draft
Thread-Index: AcLnC/nOjaSNle08T7+22C5MTwo57wCxpuwQ
From: "Eric Burger" <eburger@snowshore.com>
To: "Bert Culpepper" <bertculpepper@netscape.net>
Cc: "SIPPING List" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2EFJuO16732
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

On the one hand, it is trivially easy to add a "suppress=yes" parameter to the digit map tag.  However, I am still VERY concerned about the local/remote digit processing.  For review, here is the example from the draft:

<quote>
NOTE: If KPML did not have this behavior, then a user device executing KPML could easily break called applications. For example, take a personal assistant that uses "*9" for attention. If the user presses the "*" key, KPML will hold the digit, looking for the "9". What if the user just enters a "*" key, possibly because they accessed an IVR system that looks for "*"? In this case, the "*" would get held by the user device, because it is looking for the "*9" pattern. The user would probably press the "*" key again, hoping that the called IVR system just did not hear the key press. At that point, the user device would send both "*" entries, as "**" does not match "*9". However, that would not have the effect the user intended when they pressed "*". 
</quote>

Does this issue ever go away?



> Original Message From: Bert Culpepper [mailto:bertculpepper@netscape.net]
[snip]
>  > The text at the end of this section discusses the 
> inability for a user
>  > device to know that signaled digits are for KPML processing or the
>  > recipients of a media stream.  Therefore DTMF must be sent 
> in the media
>  > stream in addition to be reported using KPML.  It seems to 
> me that if a
>  > user device receives a KPML document for processing, it'll 
> know based on
>  > the digit map what is meant for processing vs. sending in the media
>  > stream.  I realize processing key presses for digit map 
> matching will
>  > delay the transmission when matches don't occur, however I 
> expect this
>  > delay to be very small, resulting in no degradation of the user 
> experience.
> 
> Reflecting on my weekend comments, the cases where it would be
> OK to delay sending indications in the media stream are 
> limited to very
> short digit maps (a single digit practically speaking).  But for those
> cases, long digits such as the "long pound", and when focus can be
> determined by the user device, it'll be desirable to NOT to have the
> indications duplicated in the media stream.
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 10:10:43 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28102
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 10:10:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EFPf417115
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 10:25:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFPfO17112
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 10:25:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28034
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 10:10:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFNiO16950;
	Fri, 14 Mar 2003 10:23:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFJuO16735
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 10:19:56 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27205
	for <sipping@ietf.org>; Fri, 14 Mar 2003 10:04:27 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Use of NOTIFY in KPML (was [SIPPING] Comments on updated KPML draft)
Date: Fri, 14 Mar 2003 10:08:49 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D2488E2@zoe.office.snowshore.com>
Thread-Topic: Comments on updated KPML draft
Thread-Index: AcLl0UfpXqvJYiK6Suuy9q3FP7k1igEAjtug
From: "Eric Burger" <eburger@snowshore.com>
To: "Bert Culpepper" <bertculpepper@netscape.net>
Cc: "SIPPING List" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2EFJuO16736
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Inline.

> -----Original Message From: Bert Culpepper [mailto:bertculpepper@netscape.net]
[snip]
> Section 4 - SIP Reporting
> 
> It's stated that the NOTIFY is sent to the Contact contained in an 
> INVITE.  How does this support SIP proxy-based applications? 
> draft-jennings-sip-app-info-00 allows proxies to add, delete, 
> and read 
> App-Info header values.  Or is the use of the NOTIFY method to be 
> limited to the endpoints of a SIP session, and any other 
> entity must use 
> HTTP?

Good point.  I was looking for a mechanism that makes third-party DDOS attacks harder.  Do you have an alternative mechanism for specifying who gets the notification?

> Another issue is that it's stated that a KPML session ends 
> when a NOTIFY 
> is sent, and further KPML sessions must be established with a 
> reINVITE. 
>   Why not allow a KPML document in the body of the 200 OK response to 
> the NOTIFY as specified similarly for HTTP reporting?  This 
> saves three 
> messages between the application and user device.

I don't have a problem with that.  However, I can hear a chorus of objection.  Principally, if you fetch a document, execute it, return a result, and that results in a new document, why aren't you using HTTP?


> According to RFC 3265, NOTIFY requests MUST contain an Event header. 
> What would the value of this header be for KPML bodies?
Whoops.  That would be kpml.  Something for the next draft.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 10:10:45 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28119
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 10:10:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EFPiC17131
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 10:25:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFPiO17128
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 10:25:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28040
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 10:10:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFNbO16899;
	Fri, 14 Mar 2003 10:23:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFJtO16727
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 10:19:55 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27199
	for <sipping@ietf.org>; Fri, 14 Mar 2003 10:04:25 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] New version of netann
Date: Fri, 14 Mar 2003 10:08:47 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D2488D9@zoe.office.snowshore.com>
Thread-Topic: [Sipping] New version of netann
Thread-Index: AcLkb8bPeDJc5Xk/TyS+46tvRjjTGgFUq0Lg
From: "Eric Burger" <eburger@snowshore.com>
To: "Christer Holmberg" <christer.holmberg@lmf.ericsson.se>
Cc: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2EFJtO16728
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Inline.

> Original Message From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
[snip]
> > >Well, you could define the play's as SDP attributes. 
> Something like:
> > >
> > >m=audio...
> > >a=play:"http://audio.example.net/allcircuitsbusy.g711";
> > >m=video...
> > >a=play:"http://video.example.net/allcircuitsbusy.mpeg4";
> > >
> > >I don't know if this would work (I haven't had time to 
> think so much
> > >about it) the way you've planned, though.
> >
> > It might work, except error handling would be horrific.  A 
> fetch error would have to be reported as an SDP error, for example.
> 
> Well, you could return 200 OK with an SDP, with the port set 
> to zero for the specific stream. That's how we do it in 
> "normal" SIP calls, so... Or, you could send 415 Unsupported 
> Media Type.

The problem is, is the 415 because the fetch failed or because I don't support G.mumble?  Yes, one might be able to work it out from the parameters given in the 415, but that sounds like a lot of machinery.

> 
> > >But, if we need multiple INVITEs, would it be possible to associate
> > >them? We would have to use different call identifiers etc 
> (I hope you
> > >wouldn't want to use something similar to overlapping for this :)
> >
> > Is this a real issue?
> 
> What? Being able to associate the INVITEs, or having to send 
> multiple INVITEs? At least regarding the issue of multiple 
> INVITEs, I think multimedia streams (including eg audio AND 
> video) IS a real issue...

The unfortunate thing is, I think I agree with you.  Does anyone have a thought on how to do this?  My initial thinking is I don't want the URI to play in the SDP, because that is a signaling thing, not a media thing.  However, I don't see a nice way of correlating what to play over which stream, without something like a stream ID in the SDP that gets referenced in SIP.

> > >Another question I have, is related to the media mode attributes.
> > >
> > >Assume I send a re-INVITE during the session, to put the media
> > >"on-hold". Now, does this mean that the stream will be
> > >"paused", or does it mean that I just won't receive it? 
> Personally I would say that the
> > >second alternative is more according to the semantics, but in a
> > >streaming environment some may disagree...
> >
> > I hadn't thought about it before, as we've never seen it 
> happen.  I suppose it could happen, however.  I'm hesitant to 
> standardize the behavior.  If we say "hold=pause session", 
> then we're opening ourselves up to a major denial-of-service attack.
> 
> If it's supposed to work as it normally does, there is no 
> need to standardize anything. But, in that case I guess it 
> will not be able, with your current draft, to put media on 
> hold. I guess it's not needed for announcements etc, but my 
> understanding
> is that the scope of your draft includes also real, 
> established, streaming sessions.

I think the thing to do is say that putting announcement media on hold may have unpredictable results.  The PSTN emulation behaviour would be to virtually continue play out, and then resume from the time index of the re-re-INVITE bringing us off hold.  The *easy* thing to do is suspend playing.

The scope of the draft w.r.t. annc, ivr, and dialog is announcements or interactive sessions.  The only service where "established" sessions might be an issue is conf.  However, for conf the semantics are clear and straightforward.

Thinking of my comment above concerning putting an annc on hold, it doesn't really follow for ivr and dialog services.  Vote time: should we suspend ivr and dialog sessions on receipt of hold, or should we time-forward them?
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 10:24:57 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29018
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 10:24:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EFduC18561
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 10:39:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFduO18558
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 10:39:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29011
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 10:24:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFZeO17589;
	Fri, 14 Mar 2003 10:35:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFWmO17410
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 10:32:48 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28813
	for <sipping@ietf.org>; Fri, 14 Mar 2003 10:17:18 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z05009>; Fri, 14 Mar 2003 10:17:35 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410D995BEB@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>,
        "'Peterson, Jon '"
	 <jon.peterson@neustar.biz>
Cc: "''sipping@ietf.org' '" <sipping@ietf.org>,
        "''hgs@cs.columbia.edu' '"
	 <hgs@cs.columbia.edu>
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Date: Fri, 14 Mar 2003 10:15:49 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

I agree.

It makes much more sense (in a private IP network) to rely on standards that
are accepted in the public (Big "I") Internet, than to rely on proprietary
approaches and have future interoperability problems.

-----Original Message-----
From: King, Kimberly S. [mailto:KIMBERLY.S.KING@saic.com]

Jon said:

snip

>On totally private networks, I find the whole ETS SIP concept entirely
>plausible. I would note that the "I" in "IEPREP" is for Internet,
>though. I
>have always understood that to be the capital-"I" Internet, as in
>RFC3271.

This is a good point.  I believe many in ieprep have interest in developing
standards for IP networks (both those that are part of the Internet and
those that are not).    

Kimberly
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 12:13:10 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02992
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 12:13:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EHSB726418
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 12:28:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EHSBO26415
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 12:28:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02985
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 12:12:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EHQiO26353;
	Fri, 14 Mar 2003 12:26:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EHPMO26295
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 12:25:22 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02921
	for <sipping@ietf.org>; Fri, 14 Mar 2003 12:09:49 -0500 (EST)
Received: from zcard307.ca.nortel.com (zcard307.ca.nortel.com [47.129.242.67])
	by zcars04e.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2EHBkC18835;
	Fri, 14 Mar 2003 12:11:47 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GDFBYDAW; Fri, 14 Mar 2003 12:11:47 -0500
Received: from nortelnetworks.com (acart1fn.ca.nortel.com [47.129.129.163]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id G7ZYWF3V; Fri, 14 Mar 2003 12:11:47 -0500
Message-ID: <3E720D51.40809@nortelnetworks.com>
Date: Fri, 14 Mar 2003 12:11:45 -0500
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030131
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: sipping@ietf.org, Bert Culpepper <bertculpepper@netscape.net>
Subject: Re: Digit suppression (was [Sipping] Comments on updated KPML draft)
References: <4A3384433CE2AB46A63468CB207E209D2488E1@zoe.office.snowshore.com>
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D2488E1@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

This one is easy to answer.  Pattern match when you have alternatives like "*" and 
"*9" has to use timers to make the distinction.

Eric Burger wrote:
> On the one hand, it is trivially easy to add a "suppress=yes" parameter to the digit map tag.  However, I am still VERY concerned about the local/remote digit processing.  For review, here is the example from the draft:
> 
> <quote>
> NOTE: If KPML did not have this behavior, then a user device executing KPML could easily break called applications. For example, take a personal assistant that uses "*9" for attention. If the user presses the "*" key, KPML will hold the digit, looking for the "9". What if the user just enters a "*" key, possibly because they accessed an IVR system that looks for "*"? In this case, the "*" would get held by the user device, because it is looking for the "*9" pattern. The user would probably press the "*" key again, hoping that the called IVR system just did not hear the key press. At that point, the user device would send both "*" entries, as "**" does not match "*9". However, that would not have the effect the user intended when they pressed "*". 
> </quote>
> 
> Does this issue ever go away?
> 
> 
> 
> 
>>Original Message From: Bert Culpepper [mailto:bertculpepper@netscape.net]
> 
> [snip]
> 
>> > The text at the end of this section discusses the 
>>inability for a user
>> > device to know that signaled digits are for KPML processing or the
>> > recipients of a media stream.  Therefore DTMF must be sent 
>>in the media
>> > stream in addition to be reported using KPML.  It seems to 
>>me that if a
>> > user device receives a KPML document for processing, it'll 
>>know based on
>> > the digit map what is meant for processing vs. sending in the media
>> > stream.  I realize processing key presses for digit map 
>>matching will
>> > delay the transmission when matches don't occur, however I 
>>expect this
>> > delay to be very small, resulting in no degradation of the user 
>>experience.
>>
>>Reflecting on my weekend comments, the cases where it would be
>>OK to delay sending indications in the media stream are 
>>limited to very
>>short digit maps (a single digit practically speaking).  But for those
>>cases, long digits such as the "long pound", and when focus can be
>>determined by the user device, it'll be desirable to NOT to have the
>>indications duplicated in the media stream.
>>
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 12:48:14 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03785
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 12:48:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EI3F728620
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 13:03:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EI3EO28617
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 13:03:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03771
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 12:47:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EI2QO28569;
	Fri, 14 Mar 2003 13:02:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EI1PO28516
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 13:01:25 -0500
Received: from marionberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03749
	for <sipping@ietf.org>; Fri, 14 Mar 2003 12:45:53 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(user=hgs10 mech=PLAIN bits=0)
	by marionberry.cc.columbia.edu (8.12.8/8.12.8) with ESMTP id h2EHm2QK018412
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 14 Mar 2003 12:48:03 -0500 (EST)
Message-ID: <3E7215D7.8090301@cs.columbia.edu>
Date: Fri, 14 Mar 2003 12:48:07 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Peterson, Jon" <jon.peterson@neustar.biz>
CC: "'King, Kimberly S.'" <KIMBERLY.S.KING@saic.com>,
        "''sipping@ietf.org' '" <sipping@ietf.org>
Subject: Re: [Sipping] Comments on draft-peterson-sipping-ieprep-00
References: <15A2739B7DAA624D8091C65981D7DA8101214F2D@stntexch2.va.neustar.com>
In-Reply-To: <15A2739B7DAA624D8091C65981D7DA8101214F2D@stntexch2.va.neustar.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> least, given how diverse media servers are, it would be difficult to
> generalize this emergency behavior into useful guidelines.

We don't need to specify precisely what happens - again, "increased 
probability". For example, depending on the size of the server, one 
server may just have two queues (hi/lo priority), another may preempt 
some existing lower-priority session. This is within the scope of end 
system behavior, just as much as deciding precisely how (say) a UI 
renders the Priority header or rings.

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 14:10:52 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08902
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 14:10:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EJPsG01860
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 14:25:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EJPsO01857
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 14:25:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08875
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 14:10:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EJMbO01717;
	Fri, 14 Mar 2003 14:22:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EJL8O01660
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 14:21:08 -0500
Received: from cerbrus.convedia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08574
	for <sipping@ietf.org>; Fri, 14 Mar 2003 14:05:34 -0500 (EST)
Received: from ladon.convedia.com (ladon [192.168.208.15])
	by cerbrus.convedia.com (8.9.3+Sun/8.9.3) with ESMTP id LAA07305;
	Fri, 14 Mar 2003 11:05:09 -0800 (PST)
Received: from convedia.com (egret.convedia.com [192.168.208.147])
	by ladon.convedia.com (8.9.3+Sun/8.9.3) with ESMTP id LAA02075;
	Fri, 14 Mar 2003 11:07:42 -0800 (PST)
Message-ID: <3E7228B4.20201@convedia.com>
Date: Fri, 14 Mar 2003 11:08:36 -0800
From: Tim Melanchuk <timm@convedia.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: Christer Holmberg <christer.holmberg@lmf.ericsson.se>,
        "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] New version of netann
References: <4A3384433CE2AB46A63468CB207E209D2488D9@zoe.office.snowshore.com>
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D2488D9@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

at the end...

Eric Burger wrote:
> Inline.
> 
>>Original Message From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> 
[snip]
>>>>Another question I have, is related to the media mode attributes.
>>>>
>>>>Assume I send a re-INVITE during the session, to put the media
>>>>"on-hold". Now, does this mean that the stream will be
>>>>"paused", or does it mean that I just won't receive it? 
>>
>>Personally I would say that the
>>
>>>>second alternative is more according to the semantics, but in a
>>>>streaming environment some may disagree...
>>>
>>>I hadn't thought about it before, as we've never seen it 
>>
>>happen.  I suppose it could happen, however.  I'm hesitant to 
>>standardize the behavior.  If we say "hold=pause session", 
>>then we're opening ourselves up to a major denial-of-service attack.
>>
>>If it's supposed to work as it normally does, there is no 
>>need to standardize anything. But, in that case I guess it 
>>will not be able, with your current draft, to put media on 
>>hold. I guess it's not needed for announcements etc, but my 
>>understanding
>>is that the scope of your draft includes also real, 
>>established, streaming sessions.
> 
> 
> I think the thing to do is say that putting announcement media on hold may have unpredictable results.  The PSTN emulation behaviour would be to virtually continue play out, and then resume from the time index of the re-re-INVITE bringing us off hold.  The *easy* thing to do is suspend playing.
> 
> The scope of the draft w.r.t. annc, ivr, and dialog is announcements or interactive sessions.  The only service where "established" sessions might be an issue is conf.  However, for conf the semantics are clear and straightforward.
> 
> Thinking of my comment above concerning putting an annc on hold, it doesn't really follow for ivr and dialog services.  Vote time: should we suspend ivr and dialog sessions on receipt of hold, or should we time-forward them?

i believe that all should time-forward. services such as ivr
and dialog involve bi-directional interactions. each direction
can be independently put on hold. requesting that one direction
be put on hold, should not influence the stream in the opposite
direction. for example, if a user requests that the stream from
a media server be put on hold, it does not mean that they will
not send to the media server, only that the media server should
not send.

since transitions from a=sendrecv to a=sendonly or a=recevonly
should not pause an ivr or dialog service, i don't think that
a=inactive should be special cased to pause the service.

then, since hold would not affect the conf, ivr, or dialog
services, it would not be consistent to have it affect the
ann service.


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 14:14:44 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09249
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 14:14:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EJTlo02105
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 14:29:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EJTkO02102
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 14:29:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09204
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 14:14:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EJSOO02050;
	Fri, 14 Mar 2003 14:28:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EJQ8O01892
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 14:26:08 -0500
Received: from rtp-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08890
	for <sipping@ietf.org>; Fri, 14 Mar 2003 14:10:33 -0500 (EST)
Received: from cia.cisco.com (IDENT:mirapoint@cia.cisco.com [161.44.85.200])
	by rtp-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h2EJCavD026958;
	Fri, 14 Mar 2003 14:12:36 -0500 (EST)
Received: from mhammer-w2k02.cisco.com (hrn2-dhcp-161-44-87-89.cisco.com [161.44.87.89])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABR66425;
	Fri, 14 Mar 2003 14:02:39 -0500 (EST)
Message-Id: <4.3.2.7.2.20030314135155.00b9aa48@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 14 Mar 2003 14:12:20 -0500
To: "Peterson, Jon" <jon.peterson@neustar.biz>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Cc: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>,
        "''sipping@ietf.org' '" <sipping@ietf.org>,
        "''hgs@cs.columbia.edu' '" <hgs@cs.columbia.edu>
In-Reply-To: <15A2739B7DAA624D8091C65981D7DA8101214F2D@stntexch2.va.neus
 tar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Jon,

In a couple places you use the term "call path".  Could you clarify what 
you are referring to here?

I gathered from the original draft (that your draft critiques), that you 
are focusing on the SIP signaling only and not the media path taken?  Or is 
this a more general reference to the sequence of networks one must traverse 
to get to the endpoint or PSTN GW?

Also, I am curious about how tightly or loosely coupled the media path and 
signaling path are, given that it may not be just proxy or PSTN GW 
resources that may be congested, but the media path resources, in light of 
possible QoS usage.

I can appreciate that the target of the SIP INVITE can be diverted to an 
appropriate ETS-aware endpoint through (at the earliest recognition of a 
ETS priority header) possibly ETS-aware proxies.  But, does that ensure 
that an ETS media path finds ETS-aware networks that might set aside media 
resources and avoid ETS-unaware congested networks?

Also, has anyone given thought to how to route around countries that are 
antagonistic towards another country's perceived "emergency"?  I gather 
this is behind some of the anonymity requirements, but suspect this may 
come down to local policy implementation.  (Spare me the Internet does not 
recognize national boundaries rhetoric.)

Mike


At 06:02 AM 3/14/2003 -0500, Peterson, Jon wrote:

>Some notes inline.
>
>Jon Peterson
>NeuStar, Inc.
>
> > -----Original Message-----
> > From: King, Kimberly S. [mailto:KIMBERLY.S.KING@saic.com]
> > Sent: Thursday, March 13, 2003 5:59 PM
> > To: 'Peterson, Jon '; ''King, Kimberly S.' '
> > Cc: ''sipping@ietf.org' '; ''hgs@cs.columbia.edu' '
> > Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
> >
>[snip]
> >
> > Okay, the ideas I'm about to present represent my personal thoughts.
> >
> > Why should ETS need to justify the absence of congestion in the access
>links
> > or other parts of the network (thereby proving optional preferential
> > treatment is justified) when the default system operates without respect
>to
> > transport congestion?  We are just trying to increase our odds with the
> > default system.  Why not have transport congestion issues, where
> > appropriate, handled independently?
> >
>
>Well, I didn't mean to pick on transport congestion - I was just trying to
>illustrate a case in which part of the network didn't support ETS and it had
>deleterious effects. There are clearly other aspects of partial coverage
>that are worthy of analysis (some of which I just talked about in another
>mail).
>
>[snip]
> >
> > I agree with you that if gateways are the only issue then this could
>affect
> > the design.  However, are there not media or application servers that
>might
> > also provide such preferential access?
> >
>
>That's a good point, yes. I wouldn't ordinarily think application servers
>are constrained resources, but media servers tend to have ports, just like
>gateways. I suppose that an emergency call could constitute listening to
>some sort of announcements or leaving a message, which could entail a media
>server, but I hadn't really given the matter much thought. On initial
>reflection, I imagine that it would be more difficult to enable media
>servers to handle prioritization than it would be for gateways... or at
>least, given how diverse media servers are, it would be difficult to
>generalize this emergency behavior into useful guidelines.
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 15:07:51 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11682
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 15:07:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EKMr406451
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 15:22:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EKMrO06448
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 15:22:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11630
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 15:07:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EKM6O06434;
	Fri, 14 Mar 2003 15:22:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EKLcO06387
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 15:21:38 -0500
Received: from rtp-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11494
	for <sipping@ietf.org>; Fri, 14 Mar 2003 15:06:03 -0500 (EST)
Received: from cia.cisco.com (IDENT:mirapoint@cia.cisco.com [161.44.85.200])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h2EK8CSc009943;
	Fri, 14 Mar 2003 15:08:12 -0500 (EST)
Received: from mhammer-w2k02.cisco.com (dhcp-64-100-224-75.cisco.com [64.100.224.75])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABR67154;
	Fri, 14 Mar 2003 14:58:16 -0500 (EST)
Message-Id: <4.3.2.7.2.20030314150507.03f4ceb0@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 14 Mar 2003 15:08:08 -0500
To: "Peterson, Jon" <jon.peterson@neustar.biz>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] New version of the early media draft
Cc: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>
In-Reply-To: <15A2739B7DAA624D8091C65981D7DA8101214F15@stntexch2.va.neus
 tar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Jon,

I think I heard someone before say that they wanted to display a visual 
icon to indicate alerting, while playing the in-band media, but not have 
that over-written with locally injected ringing.

So, it may not be a case of signal alerting OR play inband media, but doing 
both.

What is the objection to providing signaling to indicate alerting state 
along with an indicator that locally injected audio should be suppressed?

Mike


At 11:52 PM 3/12/2003 -0500, Peterson, Jon wrote:
>I'm not sure how great the value of communicating the alerting state is 
>for SIP in other cases, though, when in-band media contains the real 
>indication of the state of the call. It's not as if that state information 
>can replace the in-band status information, right?

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 15:20:15 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12998
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 15:20:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EKZJd07076
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 15:35:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EKZJO07073
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 15:35:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12954
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 15:19:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EKYHO06922;
	Fri, 14 Mar 2003 15:34:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EKVcO06795
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 15:31:38 -0500
Received: from rtp-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12729
	for <sipping@ietf.org>; Fri, 14 Mar 2003 15:16:02 -0500 (EST)
Received: from cia.cisco.com (IDENT:mirapoint@cia.cisco.com [161.44.85.200])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h2EKIASc011656;
	Fri, 14 Mar 2003 15:18:10 -0500 (EST)
Received: from mhammer-w2k02.cisco.com (dhcp-64-100-224-75.cisco.com [64.100.224.75])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABR67261;
	Fri, 14 Mar 2003 15:08:15 -0500 (EST)
Message-Id: <4.3.2.7.2.20030314151158.03fd33c0@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 14 Mar 2003 15:18:08 -0500
To: "Bob Penfield" <bpenfield@acmepacket.com>
From: Michael Hammer <mhammer@cisco.com>
Subject: Re: [Sipping] New version of the early media draft
Cc: "Peterson, Jon" <jon.peterson@neustar.biz>, <sipping@ietf.org>
In-Reply-To: <002801c2e968$c271e570$2300000a@BPenfield>
References: <15A2739B7DAA624D8091C65981D7DA8101214F15@stntexch2.va.neustar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

At 08:59 AM 3/13/2003 -0500, Bob Penfield wrote:
>2) If the UAC receives media, it should play it.

Do you include in the term "media":

1) RTP stream with silence as input at the PSTN GW, or
2) RTP stream with actual audio carried

I agree you play if 2), not sure about that for 1) as this may be merely 
early setup to avoid clipping.

If ISUP in-band indication is meant to identify 2) or if that is always 
known to be the case, then the way is clear.  But, as already mentioned, 
the ISUP indicator may not be present and the PSTN GW may not be detecting 
audio, thus the non-determinism.

Mike

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 15:50:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13966
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 15:50:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EL5sh09180
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 16:05:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EL5rO09177
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 16:05:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13943
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 15:50:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EL59O09150;
	Fri, 14 Mar 2003 16:05:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EL46O09115
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 16:04:06 -0500
Received: from rtp-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13877
	for <sipping@ietf.org>; Fri, 14 Mar 2003 15:48:30 -0500 (EST)
Received: from cia.cisco.com (IDENT:mirapoint@cia.cisco.com [161.44.85.200])
	by rtp-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h2EKodvD005288;
	Fri, 14 Mar 2003 15:50:40 -0500 (EST)
Received: from mhammer-w2k02.cisco.com (hrn2-dhcp-161-44-87-89.cisco.com [161.44.87.89])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABR67679;
	Fri, 14 Mar 2003 15:40:43 -0500 (EST)
Message-Id: <4.3.2.7.2.20030314154737.00b430b0@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 14 Mar 2003 15:50:37 -0500
To: "Peterson, Jon" <jon.peterson@neustar.biz>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] New version of the early media draft
Cc: "'Drage, Keith (Keith)'" <drage@lucent.com>,
        "'Elwell, John'" <john.elwell@siemens.com>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>
In-Reply-To: <15A2739B7DAA624D8091C65981D7DA8101214F2C@stntexch2.va.neus
 tar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Jon,

Doesn't the possibility of deaf users preclude the use of 183 from being 
used, as has been suggested, since they won't hear the locally injected 
ringback or the inband media?

Mike


At 05:52 AM 3/14/2003 -0500, Peterson, Jon wrote:

>Below.
>
>Jon Peterson
>NeuStar, Inc.

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 16:00:58 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14134
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 16:00:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2ELG3J10296
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 16:16:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ELG3O10293
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 16:16:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14119
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 16:00:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ELF5O10254;
	Fri, 14 Mar 2003 16:15:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ELEbO10218
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 16:14:37 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14059
	for <sipping@ietf.org>; Fri, 14 Mar 2003 15:58:57 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2EL0uC15664;
	Fri, 14 Mar 2003 21:00:56 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JT7GT>; Fri, 14 Mar 2003 16:01:14 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F34@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'Drage, Keith (Keith)'"
	 <drage@lucent.com>,
        "'Elwell, John'" <john.elwell@siemens.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 14 Mar 2003 16:01:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2EA6C.D8D265B0"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2EA6C.D8D265B0
Content-Type: text/plain;
	charset="iso-8859-1"

inline.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Friday, March 14, 2003 3:57 AM
To: 'Peterson, Jon'; 'Drage, Keith (Keith)'; 'Elwell, John'
Cc: 'sipping@ietf.org'
Subject: RE: [Sipping] New version of the early media draft



Jon, 

You claimed that Keith's case 2 and case 3 were identical, but I do not see
how this can be. 

In both cases, in-band media is available. 

In case 2, it is known that the called user is being informed of the
presence of the request (at least if they are physically present, they are),
in case 3 this is now known. I do not see how any definition of identical
can be applied to these two cases.

A different claim would be that *for the purposes of the UAC* these cases
are identical, because all the UAC does in both cases is play the media. 

<JFP> This is what I meant, yes. I hoped that would have been clear from the
context of the remainder of the paragraph in which my assertion appeared.
</JFP>

But I think you are making too many assumptions about what the UAC may or
may not be able to use this information for. As a general rule, I would err
on the side of providing this information to the UAC, if only to assist in
future scenarios that we haven't yet thought of. 

<JFP> True, I'm much more interested in getting people to recognize that
this is a pseudoproblem than in speculating about ways we could exploit
these signaling mechanics down the road. </JFP> 

In terms of specific examples: 
1) Keith mentioned that some ringing tones around the world are not
dissimilar from busy tones elsewhere in the world. It is entirely possible
for the user on a SIP terminal to end up hearing remotely generated busy
tone and you give an example of CAS interworking yourself - this would be
case 3. The additional indication available in Case 2 may give the user
additional confidence that what they are hearing really is a ring-tone. 

<JFP> If you're not looking at a 486, you're not going to be looking at a
display that says "busy" either, right? In the CAS case, the gateway is
unable to ascertain status. So Case 3 is a wash either way. In Case 2, when
you could have a visual indicator telling you the difference between busy
and ringing, it would be much better if you just got the out-of-band
signaling than if you got the tones - largely because of your reason 2,
forking.

2) In a forking case, the UAC may have early media arriving from multiple
sources. There is very little the UAC itself can tell about the call state
of these multiple calls - the media needs to be presented to a human user
for interpretation. I think in this case any additional information that the
UAC can be provided with about call state will be helpful. The user may also
find these indications useful in deciding which of several forks to listen
to first. 

<JFP> In forking cases, it is categorically better to receive out-of-band
status information than in-band status information - this is one of my
primary motivators for avoiding in-band pre-answer status info. I would
greatly prefer it if we were interworking with a signaling protocol that is
capable of expressing its status out-of-band - but since we're apparently
not, we're not left with any option but to send the media. From a forking
composition perspective, I don't see any appreciable difference between
listening to ringtone, listening to dead air, or listening to any other
pre-answer media condition. All are equally likely not to be the branch that
is about to be answered. 

Look at it this way - if your position is that when the user sees 'alerting'
on their display for a particular branch, they therefore know that they
don't need to listen to the media that's being sent, this really begs the
question of why we're sending the media at all. But it's not safe to fail to
listen to media from any branch of a fork that is giving back a provisional
status. It would be radically preferable if media were only sent from (ISUP
'subscriber free') branches when an answer arose; otherwise the UAC's access
links could be swamped with early media that will never lead to a call, and
it will be impossible for the user to listen to any of the branches. Sending
180 with media is anathema to forking if this media is not necessary - and I
mean that in the strong sense 'necessary', as opposed to 'nice' or
'potentially useful for something we think up next year'. </JFP>

I think that whenever we have an indication that the user is being alerted
we should pass this to the UAC, using a 180 message. 183 should only be used
if we have no information. Indeed, this is what is specified in the ISUP
interworking work. 

<JFP> Yes, I agree, if the user is just being alerted, a 180 should be sent
- but not any media. If on the other hand some other condition prevails that
is only expressed in-band, we need to send that media. 'Alerting' doesn't
carry the full of sense of the state of the call; if it did, there would be
no need for in-band media. </JFP>

The problem remains of distinguishing at the SIP layer between 180 with no
media and 180 with media.  

<JFP> I don't think you've successfully made the case that the UAC does not
need to do media detection anyway, to handle cases in which post-answer
media arrives before 200 OK. If for some reason that wasn't true, then
perhaps you could argue that media detection is too hard in decomposed
architectures for us to require it on the grounds of early media cases. But
given that there is a pre-existing requirement for all UAs to do this sort
of media detection, I don't think there's any need for SIP layer
disambiguation of this. 

But all this is indicative of separable though related issues:

1) Whether or not we recommend that gateway UASs send media when they
receive an ACM coded 'subscriber free' without an indication of in-band
status information;

2) Whether or not gateway UASs send 183 in all cases where pre-answer media
is to be sent; and

3) Whether or not the UAC needs to detect media regardless of the
provisional status of the call.

As you might guess, I would prefer the answers 1) don't send media, 2) send
183, 3) always detect. 

</JFP>.

...Mark 

> -----Original Message----- 
> From: Peterson, Jon [ mailto:jon.peterson@neustar.biz
<mailto:jon.peterson@neustar.biz> ] 
> Sent: 14 March 2003 10:53 
> To: 'Drage, Keith (Keith)'; 'Elwell, John'; Watson, Mark 
> [MOP:EP10:EXCH] 
> Cc: 'sipping@ietf.org' 
> Subject: RE: [Sipping] New version of the early media draft 
> 
> 
> 
> Below. 
> 
> Jon Peterson 
> NeuStar, Inc. 
> 
> > -----Original Message----- 
> > From: Drage, Keith (Keith) [ mailto:drage@lucent.com
<mailto:drage@lucent.com> ] 
> > Sent: Thursday, March 13, 2003 12:02 PM 
> > To: 'Peterson, Jon'; 'Elwell, John'; 'Mark Watson' 
> > Cc: 'sipping@ietf.org' 
> > Subject: RE: [Sipping] New version of the early media draft 
> > 
> [snip] 
> > > What 
> > > should the UAC do differently because condition 2 
> prevails, as opposed 
> to 
> > > condition 3? 
> > > 
> > I believe the distinction is that in case 2) it is 
> > appropriate to write "ringing" or "call delivered" or 
> > "waiting answer" or such like on the display of the UAC, or 
> > whatever additional indications are given to the user over 
> > and above the in-band tones/announcements. In case 3 it is not. 
> > 
> 
> Once a SIP endpoint has gotten a provisional response from a 
> PSTN gateway, 
> then from SIP's perspective the call has been delivered - 
> we're essentially 
> interworking with a network that (we must conclude from this 
> thread) is 
> unable to express its status out-of-band. The value of a 
> visual display that 
> says "alerting" when the in-band media is saying something 
> different (like 
> "queuing") is really questionable. 
> 
> So what's the difference between what you show the user and 
> what you tell 
> them? Many users have both working eyes and ears, I agree, 
> but that doesn't 
> mean they'll benefit from seeing a visual display when what 
> they need to 
> understand the state of the call isto hear the in-band media. 
> Some UACs will 
> not support the visual display, just as some would not ordinarily play 
> in-band pre-answer media. 
> 
> > Given the number of different non-standard ring tones out 
> > there, the user may actually be relying on this extra 
> > information to know that the tone he is listening to is 
> > actually the ring tone he thinks it is, and not so other 
> > variety of busy tone. In one case he can terminate the call 
> > immediately, and in the other case he should cannot. 
> > 
> 
> Well, that's the first slightly credible argument I've heard 
> on this point, 
> but I still don't find it satisfactory. If the tone were 
> actually a busy 
> tone, the user wouldn't be hearing it - they'd be looking at 
> a 486 response 
> code. This just speaks to the degree to which the PSTN in-band user 
> signaling paradigm is ingrained in this conversation, though. 
> We need to 
> avoid using in-band status information in SIP at all, to the 
> degree that we 
> can. 
> 
> > I think the issue here is that the user is essentially 
> > dialling a PSTN user in both these cases, and therefore it is 
> > reasonable to present to the user at the UAC the indications 
> > that he would expect to get back from the PSTN. 
> > 
> 
> A PSTN user gets back an indication that the remote side is 
> being alerted, 
> other than the in-band media? I don't see that displayed on my phone. 
> 
> > In terms of the solution, presenting 183 in both cases 2 and 
> > 3 without some additional indication is misleading. 
> > Furthermore the tone/announcement in this case could well 
> > assume that the signalling level distinction available in the 
> > ISUP has been made available to the end user. 
> > 
> 
> It's the PSTN that is misleading, I think, not how we choose 
> to map the 
> status codes. This is just like ISUP interworking with legacy 
> CAS networks. 
> We could say that sending ACM is 'misleading' is ISUP-CAS interworking 
> cases, because in truth there may be a busy signal on the 
> line. It's not 
> ISUP's fault, though - that's the only way it can contend with the CAS 
> network. 
> 
> > There is also the case of providing appropriate level of 
> > signalling to support the SHOULD discussed below. 
> > 
> > > If the UAC receives media, it should be playing it. I 
> don't think it's a 
> > > matter, as you describe in 2, that a UAC should merely 
> consider playing 
> it. 
> > > Given that, 2 and 3 seem to be identical. Making the UAC 
> responsible for 
> > > deciding whether or not to play the media seems like the 
> wrong model to 
> me. 
> > > The gateway, which actually inspects and understands PSTN 
> signaling, 
> should 
> > > decide whether or not delivering media to the UAC is necessary. 
> > > 
> > As far as the UAC is concerned, in general I agree that if 
> > the UAC receives media, it should be playing it. I consider 
> > it unsafe to write a MUST here, and would default to a 
> > SHOULD, as there may be specific user interface 
> > considerations that make it incorrect or inappropriate. 
> > 
> 
> User interface considerations or UAC gateway operator policies, a more 
> likely case. If media arrives at a non-gateway UAC, and the 
> UAC doesn't play 
> it for some reason, the UAC should be telling its user 
> "pre-answer media is 
> arriving and it's trying to tell you something, but I don't know what" 
> 
> > I think it is also an assumption that all gateways can 
> > actually look at the in-band media and reliably detect what 
> > has been indicated. Any specification for early media must 
> > deal with both the cases, i.e. where the media gateway 
> > controller is not doing media detection, and that where it is. 
> > 
> 
> I have in no way suggested that in-band media can be mined by 
> applications 
> for status information - just that it needs to be passed to 
> the user. By 
> media detection, here, I'm just talking about detecting the 
> condition that 
> some RTP has arrived, not inspecting the media 
> programmatically to determine 
> its contents. 
> 
> When you send an INVITE, you need to be prepared to start 
> receiving media 
> immediately. This is essentially a requirement for the sort of media 
> detection I'm describing. 
> 
> > By the way, I suspect that this would need to be somewhat 
> > more sophisticated that just looking at the media stream at 
> > when the indication arrives; the nature of in-band 
> > information can change over time, and thus the nature of any 
> > appropriate indication to be given. There is also the problem 
> > of distinguishing noice (generated from transmission of the 
> > PSTN path over 20 miles of barbed wire) versus real signal. 
> > 
> 
> Agreed that gateways are not in a position to understand what 
> the media is. 
> My contention is only that if there is media, it has to be 
> played for the 
> user. 
> 
> > Note also that while ITU-T specifies characteristics of these 
> > tones, PSTN equipment has a lifetime that tends to exceed the 
> > lifetime of a harmonised ITU specification of these tones. In 
> > practice there are 57 different varieties of all these tones 
> > out there, and there are laws of nature that state that the 
> > first ones you find in the field are the odd ones. 
> > 
> > 
> > <snipped> 
> > 
> 


------_=_NextPart_001_01C2EA6C.D8D265B0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>

<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=498142417-14032003><FONT face=Arial color=#0000ff 
size=2>inline.</FONT></SPAN></DIV>
<DIV><SPAN class=498142417-14032003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=498142417-14032003><FONT face=Arial color=#0000ff size=2>Jon 
Peterson</FONT></SPAN></DIV>
<DIV><SPAN class=498142417-14032003><FONT face=Arial color=#0000ff 
size=2>NeuStar, Inc.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
  [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Friday, March 14, 2003 
  3:57 AM<BR><B>To:</B> 'Peterson, Jon'; 'Drage, Keith (Keith)'; 'Elwell, 
  John'<BR><B>Cc:</B> 'sipping@ietf.org'<BR><B>Subject:</B> RE: [Sipping] New 
  version of the early media draft<BR><BR></FONT></DIV>
  <P><FONT size=2>Jon,</FONT> </P>
  <P><FONT size=2>You claimed that Keith's case 2 and case 3 were identical, but 
  I do not see how this can be.</FONT> </P>
  <P><FONT size=2>In both cases, in-band media is available.</FONT> </P>
  <P><FONT size=2>In case 2, it is known that the called user is being informed 
  of the presence of the request (at least if they are physically present, they 
  are), in case 3 this is now known. I do not see how any definition of 
  identical can be applied to these two cases.</FONT></P>
  <P><FONT size=2>A different claim would be that *for the purposes of the UAC* 
  these cases are identical, because all the UAC does in both cases is play the 
  media.<SPAN class=498142417-14032003><FONT face=Arial 
  color=#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=2><SPAN class=498142417-14032003><FONT face=Arial 
  color=#0000ff>&lt;JFP&gt; This is what I meant, yes. I hoped that would have 
  been clear from the context of the remainder of the paragraph in which my 
  assertion appeared. &lt;/JFP&gt;</FONT></SPAN></FONT></P>
  <P><FONT size=2>But I think you are making too many assumptions about what the 
  UAC may or may not be able to use this information for. As a general rule, I 
  would err on the side of providing this information to the UAC, if only to 
  assist in future scenarios that we haven't yet thought of.<SPAN 
  class=498142417-14032003><FONT face=Arial 
  color=#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=2><SPAN class=498142417-14032003><FONT face=Arial 
  color=#0000ff>&lt;JFP&gt; True, I'm much more interested 
  in&nbsp;getting&nbsp;people to recognize that&nbsp;this is 
  a&nbsp;pseudoproblem than in&nbsp;speculating about ways&nbsp;we could exploit 
  these&nbsp;signaling mechanics down the 
  road.&nbsp;&lt;/JFP&gt;</FONT>&nbsp;</SPAN></FONT></P>
  <P><FONT size=2>In terms of specific examples:</FONT> <BR><FONT size=2>1) 
  Keith mentioned that some ringing tones around the world are not dissimilar 
  from busy tones elsewhere in the world. It is entirely possible for the user 
  on a SIP terminal to end up hearing remotely generated busy tone and you give 
  an example of CAS interworking yourself - this would be case 3. The additional 
  indication available in Case 2 may give the user additional confidence that 
  what they are hearing really is a ring-tone.<SPAN 
  class=498142417-14032003><FONT face=Arial 
  color=#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=2><SPAN class=498142417-14032003><FONT face=Arial 
  color=#0000ff>&lt;JFP&gt; If you're not looking at a 486, you're not going to 
  be looking at a display that says "busy" either, right? In the CAS case, the 
  gateway is unable to ascertain status. So Case 3 is a wash either way. In Case 
  2, when you could have a visual indicator telling you the difference between 
  busy and ringing, it would be much better if you just got the out-of-band 
  signaling than if you got the tones - largely because of your reason 2, 
  forking.</FONT></SPAN></FONT></P>
  <P><FONT size=2>2) In a forking case, the UAC may have early media arriving 
  from multiple sources. There is very little the UAC itself can tell about the 
  call state of these multiple calls - the media needs to be presented to a 
  human user for interpretation. I think in this case any additional information 
  that the UAC can be provided with about call state will be helpful. The user 
  may also find these indications useful in deciding which of several forks to 
  listen to first.<SPAN class=498142417-14032003><FONT face=Arial 
  color=#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=2><SPAN class=498142417-14032003><FONT face=Arial 
  color=#0000ff>&lt;JFP&gt; In forking cases, it is categorically better to 
  receive out-of-band status information than in-band</FONT>&nbsp;<FONT 
  face=Arial color=#0000ff>status information - this is one of my primary 
  motivators for avoiding in-band pre-answer status info. I would greatly prefer 
  it if we were interworking with a signaling protocol that is capable of 
  expressing its status out-of-band - but since we're apparently not, we're not 
  left with any option but to send the media. From a forking composition 
  perspective, I don't see any appreciable difference between listening to 
  ringtone, listening to dead air, or listening to any other pre-answer media 
  condition. All are equally likely not to be the branch that is about to be 
  answered. </FONT></SPAN></FONT></P>
  <P><FONT size=2><SPAN class=498142417-14032003><FONT face=Arial 
  color=#0000ff>Look at it this way - if your position is that when the user 
  sees 'alerting' on their display for a particular branch, they therefore know 
  that they don't need to listen to the media that's being sent, this really 
  begs the question of why we're sending the media at all. But it's not safe to 
  fail to listen to media from&nbsp;any branch of a fork that is giving back a 
  provisional status. It would be radically preferable if media were only sent 
  from (ISUP 'subscriber free') branches when an answer arose; otherwise the 
  UAC's access links could be swamped with early media that will never lead to a 
  call, and it will be impossible for the user to listen to any of the branches. 
  Sending 180 with media is anathema to forking if this media is not necessary - 
  and I mean that in the strong sense 'necessary', as opposed to 'nice' or 
  'potentially useful for something we think up next year'. 
  &lt;/JFP&gt;</FONT></SPAN></FONT></P>
  <P><FONT size=2>I think that whenever we have an indication that the user is 
  being alerted we should pass this to the UAC, using a 180 message. 183 should 
  only be used if we have no information. Indeed, this is what is specified in 
  the ISUP interworking work.<SPAN class=498142417-14032003><FONT face=Arial 
  color=#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=2><SPAN class=498142417-14032003><FONT face=Arial 
  color=#0000ff>&lt;JFP&gt; Yes, I agree, if the user is just being alerted, a 
  180 should be sent - but not any media. If on the other hand some other 
  condition prevails that is only expressed in-band, we need to send that 
  media.</FONT>&nbsp;<FONT face=Arial color=#0000ff>'Alerting' doesn't carry the 
  full of sense of the state of the call; if it did, there would be no need for 
  in-band media. </FONT></SPAN></FONT><FONT size=2><SPAN 
  class=498142417-14032003><FONT face=Arial 
  color=#0000ff>&lt;/JFP&gt;</FONT></SPAN></FONT></P>
  <P><FONT size=2>The problem remains of distinguishing at the SIP layer between 
  180 with no media and 180 with media.</FONT>&nbsp;<SPAN 
  class=498142417-14032003><FONT face=Arial color=#0000ff 
  size=2>&nbsp;</FONT></SPAN></P>
  <P><SPAN class=498142417-14032003><FONT face=Arial color=#0000ff 
  size=2>&lt;JFP&gt; I don't&nbsp;think you've successfully made the case that 
  the&nbsp;UAC does not need to do media detection anyway, to handle cases in 
  which post-answer media arrives before 200 OK. If for some reason that wasn't 
  true, then&nbsp;perhaps you could argue&nbsp;that media detection is too hard 
  in decomposed architectures for us to require&nbsp;it on the grounds of early 
  media cases.&nbsp;But given that there is a pre-existing requirement for all 
  UAs to do this sort of media detection, I don't think there's any need for SIP 
  layer disambiguation of this. </FONT></SPAN></P>
  <P><SPAN class=498142417-14032003><FONT face=Arial color=#0000ff size=2>But 
  all&nbsp;this is indicative of separable though 
  related&nbsp;issues:</FONT></SPAN></P>
  <P><SPAN class=498142417-14032003><FONT face=Arial color=#0000ff size=2>1) 
  Whether or not we recommend that gateway UASs send media when they receive an 
  ACM coded 'subscriber free' without an indication of in-band status 
  information;</FONT></SPAN></P>
  <P><SPAN class=498142417-14032003><FONT face=Arial color=#0000ff size=2>2) 
  Whether or&nbsp;not gateway UASs send 183 in all cases where pre-answer media 
  is to be sent; and</FONT></SPAN></P>
  <P><SPAN class=498142417-14032003><FONT face=Arial color=#0000ff size=2>3) 
  Whether or not the UAC needs to detect media regardless of the provisional 
  status of the call.</FONT></SPAN></P>
  <P><SPAN class=498142417-14032003><FONT face=Arial color=#0000ff size=2>As you 
  might guess, I would prefer the answers 1) don't send media, 2) send 183, 3) 
  always detect. </FONT></SPAN></P>
  <P><SPAN class=498142417-14032003><FONT face=Arial color=#0000ff 
  size=2>&lt;/JFP&gt;.</FONT></SPAN></P>
  <P><FONT size=2>...Mark</FONT> </P>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: Peterson, Jon [<A 
  href="mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz</A>]</FONT> 
  <BR><FONT size=2>&gt; Sent: 14 March 2003 10:53</FONT> <BR><FONT size=2>&gt; 
  To: 'Drage, Keith (Keith)'; 'Elwell, John'; Watson, Mark </FONT><BR><FONT 
  size=2>&gt; [MOP:EP10:EXCH]</FONT> <BR><FONT size=2>&gt; Cc: 
  'sipping@ietf.org'</FONT> <BR><FONT size=2>&gt; Subject: RE: [Sipping] New 
  version of the early media draft</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  Below.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Jon 
  Peterson</FONT> <BR><FONT size=2>&gt; NeuStar, Inc.</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; -----Original 
  Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: Drage, Keith (Keith) [<A 
  href="mailto:drage@lucent.com">mailto:drage@lucent.com</A>]</FONT> <BR><FONT 
  size=2>&gt; &gt; Sent: Thursday, March 13, 2003 12:02 PM</FONT> <BR><FONT 
  size=2>&gt; &gt; To: 'Peterson, Jon'; 'Elwell, John'; 'Mark Watson'</FONT> 
  <BR><FONT size=2>&gt; &gt; Cc: 'sipping@ietf.org'</FONT> <BR><FONT size=2>&gt; 
  &gt; Subject: RE: [Sipping] New version of the early media draft</FONT> 
  <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; [snip]</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; What</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  should the UAC do differently because condition 2 </FONT><BR><FONT size=2>&gt; 
  prevails, as opposed</FONT> <BR><FONT size=2>&gt; to</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; condition 3?</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; I believe the distinction is that in case 2) 
  it is </FONT><BR><FONT size=2>&gt; &gt; appropriate to write "ringing" or 
  "call delivered" or </FONT><BR><FONT size=2>&gt; &gt; "waiting answer" or such 
  like on the display of the UAC, or </FONT><BR><FONT size=2>&gt; &gt; whatever 
  additional indications are given to the user over </FONT><BR><FONT size=2>&gt; 
  &gt; and above the in-band tones/announcements. In case 3 it is not.</FONT> 
  <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; Once a SIP endpoint has gotten a provisional response from a 
  </FONT><BR><FONT size=2>&gt; PSTN gateway,</FONT> <BR><FONT size=2>&gt; then 
  from SIP's perspective the call has been delivered - </FONT><BR><FONT 
  size=2>&gt; we're essentially</FONT> <BR><FONT size=2>&gt; interworking with a 
  network that (we must conclude from this </FONT><BR><FONT size=2>&gt; thread) 
  is</FONT> <BR><FONT size=2>&gt; unable to express its status out-of-band. The 
  value of a </FONT><BR><FONT size=2>&gt; visual display that</FONT> <BR><FONT 
  size=2>&gt; says "alerting" when the in-band media is saying something 
  </FONT><BR><FONT size=2>&gt; different (like</FONT> <BR><FONT size=2>&gt; 
  "queuing") is really questionable.</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; So what's the difference between what you show 
  the user and </FONT><BR><FONT size=2>&gt; what you tell</FONT> <BR><FONT 
  size=2>&gt; them? Many users have both working eyes and ears, I agree, 
  </FONT><BR><FONT size=2>&gt; but that doesn't</FONT> <BR><FONT size=2>&gt; 
  mean they'll benefit from seeing a visual display when what </FONT><BR><FONT 
  size=2>&gt; they need to</FONT> <BR><FONT size=2>&gt; understand the state of 
  the call isto hear the in-band media. </FONT><BR><FONT size=2>&gt; Some UACs 
  will</FONT> <BR><FONT size=2>&gt; not support the visual display, just as some 
  would not ordinarily play</FONT> <BR><FONT size=2>&gt; in-band pre-answer 
  media.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; Given 
  the number of different non-standard ring tones out </FONT><BR><FONT 
  size=2>&gt; &gt; there, the user may actually be relying on this extra 
  </FONT><BR><FONT size=2>&gt; &gt; information to know that the tone he is 
  listening to is </FONT><BR><FONT size=2>&gt; &gt; actually the ring tone he 
  thinks it is, and not so other </FONT><BR><FONT size=2>&gt; &gt; variety of 
  busy tone. In one case he can terminate the call </FONT><BR><FONT size=2>&gt; 
  &gt; immediately, and in the other case he should cannot.</FONT> <BR><FONT 
  size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  Well, that's the first slightly credible argument I've heard </FONT><BR><FONT 
  size=2>&gt; on this point,</FONT> <BR><FONT size=2>&gt; but I still don't find 
  it satisfactory. If the tone were </FONT><BR><FONT size=2>&gt; actually a 
  busy</FONT> <BR><FONT size=2>&gt; tone, the user wouldn't be hearing it - 
  they'd be looking at </FONT><BR><FONT size=2>&gt; a 486 response</FONT> 
  <BR><FONT size=2>&gt; code. This just speaks to the degree to which the PSTN 
  in-band user</FONT> <BR><FONT size=2>&gt; signaling paradigm is ingrained in 
  this conversation, though. </FONT><BR><FONT size=2>&gt; We need to</FONT> 
  <BR><FONT size=2>&gt; avoid using in-band status information in SIP at all, to 
  the </FONT><BR><FONT size=2>&gt; degree that we</FONT> <BR><FONT size=2>&gt; 
  can.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; I think 
  the issue here is that the user is essentially </FONT><BR><FONT size=2>&gt; 
  &gt; dialling a PSTN user in both these cases, and therefore it is 
  </FONT><BR><FONT size=2>&gt; &gt; reasonable to present to the user at the UAC 
  the indications </FONT><BR><FONT size=2>&gt; &gt; that he would expect to get 
  back from the PSTN. </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; A PSTN user gets back an indication 
  that the remote side is </FONT><BR><FONT size=2>&gt; being alerted,</FONT> 
  <BR><FONT size=2>&gt; other than the in-band media? I don't see that displayed 
  on my phone.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; In 
  terms of the solution, presenting 183 in both cases 2 and </FONT><BR><FONT 
  size=2>&gt; &gt; 3 without some additional indication is misleading. 
  </FONT><BR><FONT size=2>&gt; &gt; Furthermore the tone/announcement in this 
  case could well </FONT><BR><FONT size=2>&gt; &gt; assume that the signalling 
  level distinction available in the </FONT><BR><FONT size=2>&gt; &gt; ISUP has 
  been made available to the end user.</FONT> <BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; It's the PSTN that 
  is misleading, I think, not how we choose </FONT><BR><FONT size=2>&gt; to map 
  the</FONT> <BR><FONT size=2>&gt; status codes. This is just like ISUP 
  interworking with legacy </FONT><BR><FONT size=2>&gt; CAS networks.</FONT> 
  <BR><FONT size=2>&gt; We could say that sending ACM is 'misleading' is 
  ISUP-CAS interworking</FONT> <BR><FONT size=2>&gt; cases, because in truth 
  there may be a busy signal on the </FONT><BR><FONT size=2>&gt; line. It's 
  not</FONT> <BR><FONT size=2>&gt; ISUP's fault, though - that's the only way it 
  can contend with the CAS</FONT> <BR><FONT size=2>&gt; network.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; There is also the case 
  of providing appropriate level of </FONT><BR><FONT size=2>&gt; &gt; signalling 
  to support the SHOULD discussed below.</FONT> <BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; If the UAC receives media, it should be 
  playing it. I </FONT><BR><FONT size=2>&gt; don't think it's a</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; matter, as you describe in 2, that a UAC should merely 
  </FONT><BR><FONT size=2>&gt; consider playing</FONT> <BR><FONT size=2>&gt; 
  it.</FONT> <BR><FONT size=2>&gt; &gt; &gt; Given that, 2 and 3 seem to be 
  identical. Making the UAC </FONT><BR><FONT size=2>&gt; responsible for</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt; deciding whether or not to play the media 
  seems like the </FONT><BR><FONT size=2>&gt; wrong model to</FONT> <BR><FONT 
  size=2>&gt; me.</FONT> <BR><FONT size=2>&gt; &gt; &gt; The gateway, which 
  actually inspects and understands PSTN </FONT><BR><FONT size=2>&gt; 
  signaling,</FONT> <BR><FONT size=2>&gt; should</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; decide whether or not delivering media to the UAC is 
  necessary.</FONT> <BR><FONT size=2>&gt; &gt; &gt; </FONT><BR><FONT size=2>&gt; 
  &gt; As far as the UAC is concerned, in general I agree that if 
  </FONT><BR><FONT size=2>&gt; &gt; the UAC receives media, it should be playing 
  it. I consider </FONT><BR><FONT size=2>&gt; &gt; it unsafe to write a MUST 
  here, and would default to a </FONT><BR><FONT size=2>&gt; &gt; SHOULD, as 
  there may be specific user interface </FONT><BR><FONT size=2>&gt; &gt; 
  considerations that make it incorrect or inappropriate.</FONT> <BR><FONT 
  size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  User interface considerations or UAC gateway operator policies, a more</FONT> 
  <BR><FONT size=2>&gt; likely case. If media arrives at a non-gateway UAC, and 
  the </FONT><BR><FONT size=2>&gt; UAC doesn't play</FONT> <BR><FONT size=2>&gt; 
  it for some reason, the UAC should be telling its user </FONT><BR><FONT 
  size=2>&gt; "pre-answer media is</FONT> <BR><FONT size=2>&gt; arriving and 
  it's trying to tell you something, but I don't know what"</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; I think it is also an assumption 
  that all gateways can </FONT><BR><FONT size=2>&gt; &gt; actually look at the 
  in-band media and reliably detect what </FONT><BR><FONT size=2>&gt; &gt; has 
  been indicated. Any specification for early media must </FONT><BR><FONT 
  size=2>&gt; &gt; deal with both the cases, i.e. where the media gateway 
  </FONT><BR><FONT size=2>&gt; &gt; controller is not doing media detection, and 
  that where it is. </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; I have in no way suggested that 
  in-band media can be mined by </FONT><BR><FONT size=2>&gt; applications</FONT> 
  <BR><FONT size=2>&gt; for status information - just that it needs to be passed 
  to </FONT><BR><FONT size=2>&gt; the user. By</FONT> <BR><FONT size=2>&gt; 
  media detection, here, I'm just talking about detecting the </FONT><BR><FONT 
  size=2>&gt; condition that</FONT> <BR><FONT size=2>&gt; some RTP has arrived, 
  not inspecting the media </FONT><BR><FONT size=2>&gt; programmatically to 
  determine</FONT> <BR><FONT size=2>&gt; its contents.</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; When you send an INVITE, you need to 
  be prepared to start </FONT><BR><FONT size=2>&gt; receiving media</FONT> 
  <BR><FONT size=2>&gt; immediately. This is essentially a requirement for the 
  sort of media</FONT> <BR><FONT size=2>&gt; detection I'm describing.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; By the way, I suspect 
  that this would need to be somewhat </FONT><BR><FONT size=2>&gt; &gt; more 
  sophisticated that just looking at the media stream at </FONT><BR><FONT 
  size=2>&gt; &gt; when the indication arrives; the nature of in-band 
  </FONT><BR><FONT size=2>&gt; &gt; information can change over time, and thus 
  the nature of any </FONT><BR><FONT size=2>&gt; &gt; appropriate indication to 
  be given. There is also the problem </FONT><BR><FONT size=2>&gt; &gt; of 
  distinguishing noice (generated from transmission of the </FONT><BR><FONT 
  size=2>&gt; &gt; PSTN path over 20 miles of barbed wire) versus real 
  signal.</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; Agreed that gateways are not in a position to 
  understand what </FONT><BR><FONT size=2>&gt; the media is.</FONT> <BR><FONT 
  size=2>&gt; My contention is only that if there is media, it has to be 
  </FONT><BR><FONT size=2>&gt; played for the</FONT> <BR><FONT size=2>&gt; 
  user.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; Note also 
  that while ITU-T specifies characteristics of these </FONT><BR><FONT 
  size=2>&gt; &gt; tones, PSTN equipment has a lifetime that tends to exceed the 
  </FONT><BR><FONT size=2>&gt; &gt; lifetime of a harmonised ITU specification 
  of these tones. In </FONT><BR><FONT size=2>&gt; &gt; practice there are 57 
  different varieties of all these tones </FONT><BR><FONT size=2>&gt; &gt; out 
  there, and there are laws of nature that state that the </FONT><BR><FONT 
  size=2>&gt; &gt; first ones you find in the field are the odd ones.</FONT> 
  <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
  size=2>&gt; &gt; &lt;snipped&gt;</FONT> <BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2EA6C.D8D265B0--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 16:14:10 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14701
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 16:14:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2ELTGG10997
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 16:29:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ELTGO10994
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 16:29:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14685
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 16:13:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ELSXO10930;
	Fri, 14 Mar 2003 16:28:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ELRSO10844
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 16:27:28 -0500
Received: from rtp-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14608
	for <sipping@ietf.org>; Fri, 14 Mar 2003 16:11:51 -0500 (EST)
Received: from cia.cisco.com (IDENT:mirapoint@cia.cisco.com [161.44.85.200])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h2ELDwSc020371;
	Fri, 14 Mar 2003 16:13:59 -0500 (EST)
Received: from mhammer-w2k02.cisco.com (hrn2-dhcp-161-44-87-89.cisco.com [161.44.87.89])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABR67998;
	Fri, 14 Mar 2003 16:04:02 -0500 (EST)
Message-Id: <4.3.2.7.2.20030314161140.03fb4e28@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 14 Mar 2003 16:13:53 -0500
To: Pascal.Jalet@alcatel.fr
From: Michael Hammer <mhammer@cisco.com>
Subject: Re: [Sipping] Proxy behavior with request URI parameters
Cc: <sipping@ietf.org>
In-Reply-To: <OF958F23BE.38396BEA-ONC1256CE8.005D3C5C@netfr.alcatel.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Pascal,

My understanding has always been that for forward compatibility reasons, 
the parameters get passed forward, else an older proxy would tend to break 
any new SIP parameters defined later.

Mike


At 06:18 PM 3/13/2003 +0100, Pascal.Jalet@alcatel.fr wrote:
>Dear sipping members,
>
>What must be a proxy behaviour when it receives a SIP request
>with request-URI parameters that it doesn't undertstand.
>In RFC 3261, It is said that "SIP elements MUST silently ignore
>any uri-parameters that they do not understand".
>
>Does it mean:
>     that the proxy removes the uri-parameters when constructing the
>    forwarded request.
>     that  the proxy copies  transparently the unknown uri-parameters in the
>    request-URI of the
>forwarded request.
>
>thanks for your help
>
>Pascal
>
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 16:29:04 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15137
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 16:29:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2ELiAq12390
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 16:44:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ELiAO12387
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 16:44:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15099
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 16:28:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ELbEO11655;
	Fri, 14 Mar 2003 16:37:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2ELaGO11226
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 16:36:16 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14873
	for <sipping@ietf.org>; Fri, 14 Mar 2003 16:20:39 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2ELMdC16171;
	Fri, 14 Mar 2003 21:22:39 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JT7NM>; Fri, 14 Mar 2003 16:22:58 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F37@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Michael Hammer'" <mhammer@cisco.com>
Cc: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 14 Mar 2003 16:22:58 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Just as a summary, the argument has been that the motivations below are
orthogonal to the presence of some indicator in SIP that tells the UAC to
suppress locally-generated ringing. If the gateway UAS sends pre-answer
media, the UAC should play it (with the caveat the UAS SHOULD NOT send media
if it can portray the status of the call out-of-band). There is no need for
any indicator here; the UAS gateway can express its preference for the use
of media by sending RTP or not. The ensuing contentions focused on whether
or not the UAC could be expected to detect the presence of RTP - I've argued
that it can. In short, the argument is that this indicator adds nothing to
SIP that we don't have already.

Mr. Camarillo also suggested that a UAC could delay generating local
ringback by a second or so after receiving a 180 to wait for UAS media to
arrive. I have a hard time seeing why this doesn't do the trick.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Michael Hammer [mailto:mhammer@cisco.com]
> Sent: Friday, March 14, 2003 12:08 PM
> To: Peterson, Jon
> Cc: 'Mark Watson'; 'sipping@ietf.org'
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> Jon,
> 
> I think I heard someone before say that they wanted to 
> display a visual 
> icon to indicate alerting, while playing the in-band media, 
> but not have 
> that over-written with locally injected ringing.
> 
> So, it may not be a case of signal alerting OR play inband 
> media, but doing 
> both.
> 
> What is the objection to providing signaling to indicate 
> alerting state 
> along with an indicator that locally injected audio should be 
> suppressed?
> 
> Mike
> 
> 
> At 11:52 PM 3/12/2003 -0500, Peterson, Jon wrote:
> >I'm not sure how great the value of communicating the 
> alerting state is 
> >for SIP in other cases, though, when in-band media contains the real 
> >indication of the state of the call. It's not as if that 
> state information 
> >can replace the in-band status information, right?
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 16:53:56 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16048
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 16:53:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EM92e15064
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 17:09:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EM92O15061
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 17:09:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16031
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 16:53:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EM58O14073;
	Fri, 14 Mar 2003 17:05:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EM4EO14025
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 17:04:14 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15876
	for <sipping@ietf.org>; Fri, 14 Mar 2003 16:48:37 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2ELoVC16849;
	Fri, 14 Mar 2003 21:50:31 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JT7VX>; Fri, 14 Mar 2003 16:50:50 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA8101214F39@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Michael Hammer'" <mhammer@cisco.com>
Cc: "'Drage, Keith (Keith)'" <drage@lucent.com>,
        "'Elwell, John'"
	 <john.elwell@siemens.com>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Fri, 14 Mar 2003 16:50:49 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

They are proverbially out of luck in the CAS interworking case, no? Again,
it's not our fault that ISUP doesn't present its status accurately
out-of-band.

Anyway, this is speaking to a pair of separable issues. Whether or not we
send pre-answer media with a 180 is separable from whether or not we need
some SIP-layer indication that we are doing so. Personally, I think we're in
a bad position to deal with cases where ISUP provides valuable in-band
information but doesn't tell us so in the encoding of an ACM, and I don't
think it is reasonable for us to always send pre-answer media on receipt of
ACM. But this is a separate issue. 

If we send 180, and subsequently send media, we could very well be deceiving
a deaf user (or a user whose UA simply doesn't render pre-answer media) into
thinking that 'alerting' tells the whole story. But if 'alerting' told the
whole story, there'd be no need to send any pre-answer media to accompany
it. This is the paradox I keep hearing - people want to see an indicator
that says "alerting" and play early media, but they simultaneously
acknowledge that the reason they want the early media is because it
qualifies the alerting state in some fashion.  How valuable is the
"alerting" state at the UAC, then?

I would be more sympathetic to this view if the 'alerting' state had some
specific semantics at the UAC pointed out in RFC3261 that differentiated
'180 received' from '183 received' or other provisional states - but it
doesn't. There's nothing magical about receiving a 180 response. It's been
suggested that this is valuable for forking composition, but in my
estimation, if there's in-band media associated with a provisional branch of
a fork, you need to evaluate that media, not the status code (again,
otherwise, why send the media at all?). Some sort of 180 indicator that
suppresses local ringback doesn't help you either way with any of these
problems.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Michael Hammer [mailto:mhammer@cisco.com]
> Sent: Friday, March 14, 2003 12:51 PM
> To: Peterson, Jon
> Cc: 'Drage, Keith (Keith)'; 'Elwell, John'; 'Mark Watson';
> 'sipping@ietf.org'
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> Jon,
> 
> Doesn't the possibility of deaf users preclude the use of 183 
> from being 
> used, as has been suggested, since they won't hear the 
> locally injected 
> ringback or the inband media?
> 
> Mike
> 
> 
> At 05:52 AM 3/14/2003 -0500, Peterson, Jon wrote:
> 
> >Below.
> >
> >Jon Peterson
> >NeuStar, Inc.
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 17:21:15 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16747
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 17:21:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2EMaMO16296
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 17:36:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EMaMO16293
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 17:36:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16710
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 17:20:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EMZbO16234;
	Fri, 14 Mar 2003 17:35:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EMYhO16163
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 17:34:44 -0500
Received: from rtp-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16682
	for <sipping@ietf.org>; Fri, 14 Mar 2003 17:19:04 -0500 (EST)
Received: from cia.cisco.com (IDENT:mirapoint@cia.cisco.com [161.44.85.200])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h2EML9Sc000464;
	Fri, 14 Mar 2003 17:21:09 -0500 (EST)
Received: from mhammer-w2k02.cisco.com (dhcp-64-100-224-75.cisco.com [64.100.224.75])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABR68771;
	Fri, 14 Mar 2003 17:11:13 -0500 (EST)
Message-Id: <4.3.2.7.2.20030314170944.00b5ed58@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 14 Mar 2003 17:20:31 -0500
To: "Peterson, Jon" <jon.peterson@neustar.biz>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] New version of the early media draft
Cc: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>
In-Reply-To: <15A2739B7DAA624D8091C65981D7DA8101214F37@stntexch2.va.neus
 tar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Jon,

Just noting the implications.

You equate the receipt of RTP of any kind with the presence of meaningful 
audio to listen to.  (Caveat that as being any RTP except silence 
suppression RTP.)

Your current approach places the burden on the GW to determine if there is 
meaningful audio and to suppress RTP until something meaningful is 
detected.  The GW could also use the "in-band media" indication (if it is 
present in the OBCI) to make the decision to send RTP.

Else, if the GW simply cuts-through and the end-switch doesn't provide 
tones or announcements, the Camarillo suggestion would lead to no ringing 
injected and the user listening to dead air, but, perhaps a visual 
indication.  At least he gets the same experience as the deaf person. :)

Mike


At 04:22 PM 3/14/2003 -0500, Peterson, Jon wrote:
>Just as a summary, the argument has been that the motivations below are
>orthogonal to the presence of some indicator in SIP that tells the UAC to
>suppress locally-generated ringing. If the gateway UAS sends pre-answer
>media, the UAC should play it (with the caveat the UAS SHOULD NOT send media
>if it can portray the status of the call out-of-band). There is no need for
>any indicator here; the UAS gateway can express its preference for the use
>of media by sending RTP or not. The ensuing contentions focused on whether
>or not the UAC could be expected to detect the presence of RTP - I've argued
>that it can. In short, the argument is that this indicator adds nothing to
>SIP that we don't have already.
>
>Mr. Camarillo also suggested that a UAC could delay generating local
>ringback by a second or so after receiving a 180 to wait for UAS media to
>arrive. I have a hard time seeing why this doesn't do the trick.
>
>Jon Peterson
>NeuStar, Inc.
>
> > -----Original Message-----
> > From: Michael Hammer [mailto:mhammer@cisco.com]
> > Sent: Friday, March 14, 2003 12:08 PM
> > To: Peterson, Jon
> > Cc: 'Mark Watson'; 'sipping@ietf.org'
> > Subject: RE: [Sipping] New version of the early media draft
> >
> >
> > Jon,
> >
> > I think I heard someone before say that they wanted to
> > display a visual
> > icon to indicate alerting, while playing the in-band media,
> > but not have
> > that over-written with locally injected ringing.
> >
> > So, it may not be a case of signal alerting OR play inband
> > media, but doing
> > both.
> >
> > What is the objection to providing signaling to indicate
> > alerting state
> > along with an indicator that locally injected audio should be
> > suppressed?
> >
> > Mike
> >
> >
> > At 11:52 PM 3/12/2003 -0500, Peterson, Jon wrote:
> > >I'm not sure how great the value of communicating the
> > alerting state is
> > >for SIP in other cases, though, when in-band media contains the real
> > >indication of the state of the call. It's not as if that
> > state information
> > >can replace the in-band status information, right?
> >

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 18:56:22 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20070
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 18:56:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2F0BUv22179
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 19:11:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2F0BUO22176
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 19:11:30 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19988
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 18:55:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2F0AcO22125;
	Fri, 14 Mar 2003 19:10:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2F07IO21728
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 19:07:18 -0500
Received: from imo-r01.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19958
	for <sipping@ietf.org>; Fri, 14 Mar 2003 18:51:37 -0500 (EST)
Received: from bertculpepper@netscape.net
	by imo-r01.mx.aol.com (mail_out_v34.21.) id 7.1c.7e373e4 (16239);
	Fri, 14 Mar 2003 18:53:35 -0500 (EST)
Received: from  netscape.net (159.252.8.67.cfl.rr.com [67.8.252.159]) by air-in03.mx.aol.com (v92.17) with ESMTP id MAILININ33-3f6f3e726b7eb4; Fri, 14 Mar 2003 18:53:35 -0500
Message-ID: <3E726B8B.60906@netscape.net>
Date: Fri, 14 Mar 2003 18:53:47 -0500
From: Bert Culpepper <bertculpepper@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: SIPPING List <sipping@ietf.org>
Subject: Re: Use of NOTIFY in KPML (was [SIPPING] Comments on updated KPML draft)
References: <4A3384433CE2AB46A63468CB207E209D2488E2@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailer: Unknown (No Version)
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Comments inline...

Eric Burger wrote:

> Inline.
> 
> 
>>-----Original Message From: Bert Culpepper [mailto:bertculpepper@netscape.net]
>>
> [snip]
> 
>>Section 4 - SIP Reporting
>>
>>It's stated that the NOTIFY is sent to the Contact contained in an 
>>INVITE.  How does this support SIP proxy-based applications? 
>>draft-jennings-sip-app-info-00 allows proxies to add, delete, 
>>and read 
>>App-Info header values.  Or is the use of the NOTIFY method to be 
>>limited to the endpoints of a SIP session, and any other 
>>entity must use 
>>HTTP?
>>
> 
> Good point.  I was looking for a mechanism that makes third-party DDOS attacks harder.  Do you have an alternative mechanism for specifying who gets the notification?


I won't pretend to be knowledgeable in the area of DOS attacks (of any 
kind).  But was it considered that hosts appearing in Via and/or 
Record-Route headers can be trusted (can be authorized and/or 
authenticated if needed)?


> 
> 
>>Another issue is that it's stated that a KPML session ends 
>>when a NOTIFY 
>>is sent, and further KPML sessions must be established with a 
>>reINVITE. 
>>  Why not allow a KPML document in the body of the 200 OK response to 
>>the NOTIFY as specified similarly for HTTP reporting?  This 
>>saves three 
>>messages between the application and user device.
>>
> 
> I don't have a problem with that.  However, I can hear a chorus of objection.  Principally, if you fetch a document, execute it, return a result, and that results in a new document, why aren't you using HTTP?


My quick answer of not using HTTP is the fact that a SIP mechanism is 
now defined :)  Not knowing the motivation behind this addition I can't 
speak more to this point.  However, having to send a reINVITE if an 
entity (specifically a SIP proxy) wishes to "continue" the KPML session 
(or start a HTML/HTTP session) requires more SIP UA functionality in the 
entity than otherwise required.  I'll admit, I don't have any use cases 
in mind at the moment.  But I don't understand this limitation, perhaps 
some explanatory text motivating the defined behavior is enough.


> 
> 
> 
>>According to RFC 3265, NOTIFY requests MUST contain an Event header. 
>>What would the value of this header be for KPML bodies?
>>
> Whoops.  That would be kpml.  Something for the next draft.
> 
> 

I suspect this may be a sensitive subject, but a few words about an 
implicit subscription be established on receipt of the corresponding 
KPML document, what values to put in the Subsciption-State header 
(depending on the outcome of the above issue), etc. are also in order. 
In short, how to construct a "well-formed" NOTIFY request.

Regards,
Bert

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 14 20:03:58 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21665
	for <sipping-archive@odin.ietf.org>; Fri, 14 Mar 2003 20:03:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2F1J7r26224
	for sipping-archive@odin.ietf.org; Fri, 14 Mar 2003 20:19:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2F1J7O26221
	for <sipping-web-archive@optimus.ietf.org>; Fri, 14 Mar 2003 20:19:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21659
	for <sipping-web-archive@ietf.org>; Fri, 14 Mar 2003 20:03:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2F1IMO26170;
	Fri, 14 Mar 2003 20:18:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2F1FAO26093
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 20:15:10 -0500
Received: from imo-m01.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21546
	for <sipping@ietf.org>; Fri, 14 Mar 2003 19:59:29 -0500 (EST)
Received: from bertculpepper@netscape.net
	by imo-m01.mx.aol.com (mail_out_v34.21.) id d.e7.7b67c4a (22680);
	Fri, 14 Mar 2003 20:01:21 -0500 (EST)
Received: from  netscape.net (159.252.8.67.cfl.rr.com [67.8.252.159]) by air-in04.mx.aol.com (v92.17) with ESMTP id MAILININ41-58983e727b606c; Fri, 14 Mar 2003 20:01:21 -0500
Message-ID: <3E727B6D.8000907@netscape.net>
Date: Fri, 14 Mar 2003 20:01:33 -0500
From: Bert Culpepper <bertculpepper@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: Tom Taylor <taylor@nortelnetworks.com>
CC: Eric Burger <eburger@snowshore.com>, sipping@ietf.org
Subject: Re: Digit suppression (was [Sipping] Comments on updated KPML draft)
References: <4A3384433CE2AB46A63468CB207E209D2488E1@zoe.office.snowshore.com> <3E720D51.40809@nortelnetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailer: Unknown (No Version)
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Right, when the pattern exceeds a single digit we have timing issues, 
and the issue as Eric describes in the I-D is present.

Suppression can only be used in limited cases IMHO.  Steve F's proposal 
(in his message) seems reasonable.  Suppression only occurs after focus 
is determined.

I'm not sure if it's practical to try and handle suppression at any 
point in the digit map (i.e., not sending the "long pound" in the media 
stream).  This would require focus determination to be attempted prior 
to sending the indication in the media stream.  This is probably too 
much to expect a user device to support.  However, I'm neutral on this 
aspect.

Regards,
Bert

Tom Taylor wrote:

> This one is easy to answer.  Pattern match when you have alternatives 
> like "*" and "*9" has to use timers to make the distinction.
> 
> Eric Burger wrote:
> 
>> On the one hand, it is trivially easy to add a "suppress=yes" 
>> parameter to the digit map tag.  However, I am still VERY concerned 
>> about the local/remote digit processing.  For review, here is the 
>> example from the draft:
>>
>> <quote>
>> NOTE: If KPML did not have this behavior, then a user device executing 
>> KPML could easily break called applications. For example, take a 
>> personal assistant that uses "*9" for attention. If the user presses 
>> the "*" key, KPML will hold the digit, looking for the "9". What if 
>> the user just enters a "*" key, possibly because they accessed an IVR 
>> system that looks for "*"? In this case, the "*" would get held by the 
>> user device, because it is looking for the "*9" pattern. The user 
>> would probably press the "*" key again, hoping that the called IVR 
>> system just did not hear the key press. At that point, the user device 
>> would send both "*" entries, as "**" does not match "*9". However, 
>> that would not have the effect the user intended when they pressed 
>> "*". </quote>
>>
>> Does this issue ever go away?
>>
>>
>>
>>
>>> Original Message From: Bert Culpepper 
>>> [mailto:bertculpepper@netscape.net]
>>
>>
>> [snip]
>>
>>> > The text at the end of this section discusses the inability for a user
>>> > device to know that signaled digits are for KPML processing or the
>>> > recipients of a media stream.  Therefore DTMF must be sent in the 
>>> media
>>> > stream in addition to be reported using KPML.  It seems to me that 
>>> if a
>>> > user device receives a KPML document for processing, it'll know 
>>> based on
>>> > the digit map what is meant for processing vs. sending in the media
>>> > stream.  I realize processing key presses for digit map matching will
>>> > delay the transmission when matches don't occur, however I expect this
>>> > delay to be very small, resulting in no degradation of the user 
>>> experience.
>>>
>>> Reflecting on my weekend comments, the cases where it would be
>>> OK to delay sending indications in the media stream are limited to very
>>> short digit maps (a single digit practically speaking).  But for those
>>> cases, long digits such as the "long pound", and when focus can be
>>> determined by the user device, it'll be desirable to NOT to have the
>>> indications duplicated in the media stream.
>>>
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sip@ietf.org for new developments of core SIP
>>
> 
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sat Mar 15 16:30:50 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26649
	for <sipping-archive@odin.ietf.org>; Sat, 15 Mar 2003 16:30:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2FLkPc02714
	for sipping-archive@odin.ietf.org; Sat, 15 Mar 2003 16:46:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2FLkOO02711
	for <sipping-web-archive@optimus.ietf.org>; Sat, 15 Mar 2003 16:46:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26634
	for <sipping-web-archive@ietf.org>; Sat, 15 Mar 2003 16:30:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2FLjEO02629;
	Sat, 15 Mar 2003 16:45:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2FLh0O02547
	for <sipping@optimus.ietf.org>; Sat, 15 Mar 2003 16:43:00 -0500
Received: from marionberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26599
	for <sipping@ietf.org>; Sat, 15 Mar 2003 16:26:54 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(user=hgs10 mech=PLAIN bits=0)
	by marionberry.cc.columbia.edu (8.12.8/8.12.8) with ESMTP id h2FLT1QK020815
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 15 Mar 2003 16:29:02 -0500 (EST)
Message-ID: <3E739B2F.6060001@cs.columbia.edu>
Date: Sat, 15 Mar 2003 16:29:19 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Hammer <mhammer@cisco.com>
CC: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'King, Kimberly S.'" <KIMBERLY.S.KING@saic.com>,
        "''sipping@ietf.org' '" <sipping@ietf.org>
Subject: Re: [Sipping] Comments on draft-peterson-sipping-ieprep-00
References: <4.3.2.7.2.20030314135155.00b9aa48@cia.cisco.com>
In-Reply-To: <4.3.2.7.2.20030314135155.00b9aa48@cia.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> Also, has anyone given thought to how to route around countries that are 
> antagonistic towards another country's perceived "emergency"?  I gather 
> this is behind some of the anonymity requirements, but suspect this may 
> come down to local policy implementation.  (Spare me the Internet does 
> not recognize national boundaries rhetoric.)

It's your choice: you can use tel: and hope/test that the receiving 
gateway is ETS-capable. Or you can use sip:12345@your-favorite-ets-provider.

If you don't trust the SIP nodes along the way to not mess with the ETS 
indicator (Resource-Priority, in our draft), you need to stick it in an 
S/MIME body, but then lose the ability for proxies to help you out.

These are all operational choices, whose advisability will probably 
change as SIP elements become ETS-aware, may depend on how much you know 
about the network, etc.

The goal here, I think, is to make sure that any mechanism works as well 
as can be expected in most circumstances, does not interfere with normal 
SIP operation of the ETS-unaware and works better as more elements 
become ETS-aware. (I think the last sentence is pretty much true for any 
SIP extension that is optional-to-support.)

Henning

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sat Mar 15 16:52:17 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27070
	for <sipping-archive@odin.ietf.org>; Sat, 15 Mar 2003 16:52:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2FM7q604548
	for sipping-archive@odin.ietf.org; Sat, 15 Mar 2003 17:07:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2FM7qO04545
	for <sipping-web-archive@optimus.ietf.org>; Sat, 15 Mar 2003 17:07:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27062
	for <sipping-web-archive@ietf.org>; Sat, 15 Mar 2003 16:51:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2FM7AO04125;
	Sat, 15 Mar 2003 17:07:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2FM6RO03750
	for <sipping@optimus.ietf.org>; Sat, 15 Mar 2003 17:06:27 -0500
Received: from marionberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27056
	for <sipping@ietf.org>; Sat, 15 Mar 2003 16:50:20 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(user=hgs10 mech=PLAIN bits=0)
	by marionberry.cc.columbia.edu (8.12.8/8.12.8) with ESMTP id h2FLqVQK027021
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 15 Mar 2003 16:52:31 -0500 (EST)
Message-ID: <3E73A0B1.9000906@cs.columbia.edu>
Date: Sat, 15 Mar 2003 16:52:49 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Peterson, Jon" <jon.peterson@neustar.biz>
CC: "King, Kimberly S." <KIMBERLY.S.KING@saic.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>
Subject: Re: [Sipping] Comments on draft-peterson-sipping-ieprep-00
References: <15A2739B7DAA624D8091C65981D7DA8101214F2B@stntexch2.va.neustar.com>
In-Reply-To: <15A2739B7DAA624D8091C65981D7DA8101214F2B@stntexch2.va.neustar.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>>First, we can have partial coverage in PSTN gateways. Clearly, if all my 
>>calls are routed to a non-ETS gateway, then all the indications in the 
>>world, however done, are pointless. Until all or almost all gateways 
>>support ETS, deployments may need to force call routing and avoid the 
>>use of default gateway discovery (i.e., tel URIs.). Since I can discover 
>>gateway support, a smart end system could try default routing first and 
>>if that fails, use source routing to reach a known entry point.
>>
> 
> 
> Let me make sure I understand. So UACs would either throw out a tel URL, and
> let proxies (presumably the default outbound) route it as they will, or UACs
> would form some sort of sip:tel@gateway URI (if that's what you mean by
> 'source routing') or perhaps the URI of a particular proxy that fronts for a
> farm of such ETS-compliant gateways. The latter addresses the possibility
> that the UAC's local proxy will not be ETS-capable (and hence this is an
> important partial coverage case). To mitigate that, users are informed of
> one or more known-capable URI which can be called when the proxy
> infrastructure doesn't support ETS. That seems reasonable, though somewhat
> intensive on the user's memory. Not really more intensive, I suppose, than
> carrying around GETS numbers.

If the UA is owned by the ETS-person, the UA can presumably do this all 
automatically, without the need for the user to remember anything. For 
the official-in-hotelroom scenario, clearly some manual typing is required.


> 
> Presumably, the discovery capability (in REQ-14) can let the UAC know if the
> proxy supported ETS, rather than just determining if the gateway supported
> ETS. There's also some question of whether or not the UAC needs to place a
> call to learn if the proxy supports ETS (I suppose something like OPTIONS
> Proxy-Require would be in order). In any event, it would definitely be

Yes.

> better to detect this condition at the proxy in these partial deployment
> cases, and it would be best if the UAC didn't have to place a call to do so.

That's why we propose to use OPTIONS, with an optional *Require.

> 
> Another important aspect of gateway priority management seems to be the
> 'context' in which prioritization is asserted. Even if we assume that all
> gateways support ETS, it isn't that case that all gateways would respect all
> contexts (i.e. that an Iraqi general would receive priority in the United
> States). The concept is certainly noted by the requirements (REQ-14), but it
> seems like another potential cause of partial coverage for any given call.

If the Iraqui general wants to call in for unconditional surrender, I'm 
sure that an ETS code could be arranged :-)

While in theory the number of ETS schemes is unbounded, in practice the 
number is likely to be rather small, at least for each country.

After all, after half a century of this in the telecom field (MLPP, GETS 
and such), we still have only a few variants of this. The bigger issue 
is authorization - even if somebody uses the right ETS scheme, they may 
not be recognized as a suitable person to use it. That's probably ok in 
practice since I see little practical need for "roaming" arrangements 
where official-from-country-A needs to place a call for termination 
within country B while country B is having an emergency.

> A system which has no effect on congestion in the LEC, but is better than
> nothing.

You solve the problems you can solve...

> 
> 
> Agreed, I'm not particularly concerned about prioritized calls to SIP UAs
> that don't support ETS. It is hard for me to see, though, how much benefit
> these mechanisms really provide in the SIP-to-SIP cases. There is virtually
> no behavior required of the UAC, proxy, or UAS in this case - while it may
> be no worse than unprioritized SIP calls, it's hard to see how it's better.

The scenarios may be a bit far-fetched, but I can picture ACDs fronting 
emergency coordination centers and similar resources making good use of 
this. You want citizens to be able to call these, but if an official 
needs to get through to an operator, it's helpful if they can.

> 
> I think it is also worth considering the case in which the UAC is a SIP
> device that does not support ETS. In that case, while it is no doubt
> possible to place calls to proxies and gateways that support ETS, the UAC
> would presumably be unable to discover whether or not the priority mechanism
> is supported. Depending on the authentication methods accepted by the proxy
> (and the nature of the mechanism, I suppose), a user agent could also prove
> that it requires prioritization and rely on the proxy to add some sort of
> prioritization indicator on the UA's behalf (though I'm still unsure how to
> read REQ-4 on this subject - it seems to suggest that ETS UAs should support
> some special authentication methods).

Yes, proxies could add this indication, although this is a bit dicey 
since the identity of a caller does not imply that the call deserves 
special treatment.

Do you mean SEC-4?


> Like gateway support, I assume proxy support of ETS is also specific to a
> particular context, with the same ramifications for partial coverage.

Sure.

> 
> If the only prioritization function that proxies provide is ETS gateway
> discovery, then it is worth noting that proxy support for ETS is useless
> unless the proxy knows of an appropriate gateway.

Again, it's no worse than having no indication.

> 
> Another proxy case that's worth examining is one in which the UAC must go
> through some local outbound proxy that doesn't support ETS, and the effects
> of that. Does the source-routing requirement extend to this case? I suppose
> pre-loaded Route headers could be used to traverse proxies that might
> otherwise route a call for a tel URL to a local gateway (perhaps especially
> for emergency numbers). I gather that REQ-3 is partly intended to cover
> something like this case.

Do you mean REQ-3 'invisible to IP layer'?

> 
> 
>>Proxies could use RP for prioritized call handling to deal with 
>>signaling overload.
>>
> 
> 
> This idea does concern me a little. If you've gone through the processing of
> the message to the point that you're extracting an RP header (to take that
> one mechanism as an example), then you've already expended a significant
> amount of the energy that a proxy puts into the processing of an entire
> request. But moreover, it seems to be this sort of grey area - neither in
> scope nor out of scope of the requirements.

This is a local choice, depending on how much post-parsing processing 
you do. If you have lots of scripts running, AAA, logging and such, 
having two queues (RP, rest) can help. At least from our implementation 
experience, parsing is a small fraction of the resources expended on a 
request.

> Agreed that partial deployment of ETS will be no worse than no deployment
> (provided that security issues are all handled well - if the system is
> exploitable, it could be quite a bit worse). I also agree that the scarcity
> of gateway resources is one of the paramount concerns.

Any such system needs to limit the high-priority set-aside to some safe 
number so that even compromise does not significantly degrade the system 
below the non-enabled state. After all, the volume of ETS calls is 
usually only a tiny fraction of the total system capacity, so if you set 
aside, say, 10% of the capacity for ETS, you can limit the worst-case 
exposure.

I think we all agree on the security issues; the requirements documents 
is not shy about those...


> Well, I was just citing the access links as one example - the partial
> coverage cases described above are just as important, and seem more like
> they should be in the scope of this work.

The goal of this work is modest; it tries to do the things that are 
likely to be implementable and known to be required (based on 
operational experience). Things like non-gw UAS or proxy behavior 
modification are gravy.

> 
> 
>>Henning
>>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sun Mar 16 10:39:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27936
	for <sipping-archive@odin.ietf.org>; Sun, 16 Mar 2003 10:39:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2GFtGg05882
	for sipping-archive@odin.ietf.org; Sun, 16 Mar 2003 10:55:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2GFtGO05879
	for <sipping-web-archive@optimus.ietf.org>; Sun, 16 Mar 2003 10:55:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27886
	for <sipping-web-archive@ietf.org>; Sun, 16 Mar 2003 10:38:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2GFrvO05786;
	Sun, 16 Mar 2003 10:53:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2GFpYO05730
	for <sipping@optimus.ietf.org>; Sun, 16 Mar 2003 10:51:34 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27790
	for <sipping@ietf.org>; Sun, 16 Mar 2003 10:35:06 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2GFb9wv017152;
	Sun, 16 Mar 2003 16:37:10 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id GPHKQ07V; Sun, 16 Mar 2003 16:37:09 +0100
Received: from lmf.ericsson.se (rmt160194.am.ericsson.se [138.85.160.194])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2GFb56B021199;
	Sun, 16 Mar 2003 17:37:07 +0200 (EET)
Message-ID: <3E749A34.72E8B8C7@lmf.ericsson.se>
Date: Sun, 16 Mar 2003 17:37:24 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
CC: Rohan Mahy <rohan@cisco.com>, Dean Willis <dean.willis@softarmor.com>,
        Jon Peterson <Jon.Peterson@neustar.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Early media ad-hoc meeting
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

we will be organizing an ad-hoc meeting to discuss open issues related
to early media. We will be focusing on whether or not there is a need
for a SIP-level flag to signal that there is media coming in 180
responses.

All of you who are interested, please approach me at the end of
tomorrow's (Monday) SIPPING meeting.

Thanks,

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sun Mar 16 11:19:53 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28606
	for <sipping-archive@odin.ietf.org>; Sun, 16 Mar 2003 11:19:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2GGZpg07587
	for sipping-archive@odin.ietf.org; Sun, 16 Mar 2003 11:35:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2GGZpO07584
	for <sipping-web-archive@optimus.ietf.org>; Sun, 16 Mar 2003 11:35:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28587
	for <sipping-web-archive@ietf.org>; Sun, 16 Mar 2003 11:19:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2GGYiO07467;
	Sun, 16 Mar 2003 11:34:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DG61O06481
	for <sipping@optimus.ietf.org>; Thu, 13 Mar 2003 11:06:01 -0500
Received: from mail.tssg.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06261
	for <sipping@ietf.org>; Thu, 13 Mar 2003 10:50:58 -0500 (EST)
Received: from boolard (unknown [10.37.1.56])
	by mail.tssg.org (Postfix) with SMTP id DECE91806B
	for <sipping@ietf.org>; Thu, 13 Mar 2003 15:47:31 +0000 (GMT)
From: "Shane McCormack" <smccormack@tssg.org>
To: <sipping@ietf.org>
Date: Thu, 13 Mar 2003 15:57:28 -0000
Message-ID: <HKEILFGJCBMBHOCGMAJNEEEMDBAA.smccormack@tssg.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <3E7096DD.2080808@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Spatial Location
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,
I have been looking at the documents relating to SIP for Emergency services
having the ability to return a users spatial geographical location.
Is their any work been done in this area currently or any documentation
regarding how it applies to a sip service. Is their a provision for an Even
Notification for spatial geographical location?

Regards
ShaneShane McCormack

Research Assistant,
TSSG, Confederation House,
Waterford Business Park, Cork Road,
Waterford, Co. Waterford.

Phone: +353 51 302927     Fax: +353 51 302901
Mobile: +353 87 9955505
http://www.tssg.org <http://www.tssg.org/>
MSN: mccormackshane@hotmail.com <mailto:mccormackshane@hotmail.com>




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sun Mar 16 11:19:55 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28619
	for <sipping-archive@odin.ietf.org>; Sun, 16 Mar 2003 11:19:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2GGZrU07603
	for sipping-archive@odin.ietf.org; Sun, 16 Mar 2003 11:35:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2GGZqO07600
	for <sipping-web-archive@optimus.ietf.org>; Sun, 16 Mar 2003 11:35:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28590
	for <sipping-web-archive@ietf.org>; Sun, 16 Mar 2003 11:19:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2GGYlO07500;
	Sun, 16 Mar 2003 11:34:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EGGoO21528
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 11:16:51 -0500
Received: from kcmso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00502
	for <sipping@ietf.org>; Fri, 14 Mar 2003 11:01:19 -0500 (EST)
Received: from maillennium.att.com ([135.25.114.99])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h2EG3SFl014225
	for <sipping@ietf.org>; Fri, 14 Mar 2003 10:03:28 -0600 (CST)
Received: from fisherlatitude (unknown[135.210.35.100](misconfigured sender))
          by maillennium.att.com (mailgw1) with SMTP
          id <20030314160238gw100nj1u5e>; Fri, 14 Mar 2003 16:02:40 +0000
From: "Steve Fisher" <sfisher1@att.com>
To: "'Eric Burger'" <eburger@snowshore.com>,
        "'Bert Culpepper'" <bertculpepper@netscape.net>
Cc: "'SIPPING List'" <sipping@ietf.org>
Subject: RE: Digit suppression (was [Sipping] Comments on updated KPML draft)
Date: Fri, 14 Mar 2003 11:02:38 -0500
Message-ID: <000001c2ea43$26702f70$6423d287@fisherlatitude>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D2488E1@zoe.office.snowshore.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Eric,

I know we've been having this discussion forever, but it still seems to
me that AT&T's Transfer Connect service serves as a good model for how
this can work (we've been working on similar services for end users that
leverage SIP's ability to make "media transfer" far more efficient than
was possible in the PSTN, and so this is more than an academic exercise
for us). 

In Transfer Connect there is an "agent" listening for tones. Until it
hears "*8", it passes them through. Once it hears "*8", though, it
assumes that the transfer connect application has the focus, and
suppresses the next 10 digits. I'm sure most of us in the US have heard
the effect of this service when we call a toll-free number, get an IVR
system, and are then transferred to a live agent -- we hear the "*8",
but do not hear the next 10 tones (I suspect we can all agree that even
those 2 tones are annoying -- 12 would be intolerable!).

Thus, in this model there is one set of tones that is used to determine
the focus, and then another set that provides the actual data for that
application. It seems to me that this model could apply to KPML, using
something like the following:

Add an additional attribute to the <regex> tag named, say, "suppress",
as in the following example:

<regex value="E8"
	suppress="10" 
	href="sip:" /> 

This would be equivalent to the following tag:

<regex value="E8XXXXXXXXXX" href="sip:" />
	
except that the UA may, at its discretion (I do think support for
"suppress" should be optional), suppress the 10 digits following the
"*8" from the audio path. In this case the application server is
providing a hint to the UA that if it sees a "*8" then this application
wants the focus, and that the next 10 digits should only be sent to this
application (via SIP NOTIFY), and not to any other application,
including an application that may be on the other end of the media
stream.

Of course, another application may also have "*8" as part of its <regex>
tag, and in this case the UA should probably ignore the "suppress"
attribute. Alternatively, the UA could NOTIFY both applications, but
still suppress the tones.

Is this reasonable?

Thanks!
Steve Fisher
Division Manager
AT&T Labs

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
Of Eric Burger
Sent: Friday, March 14, 2003 10:09 AM
To: Bert Culpepper
Cc: SIPPING List
Subject: Digit suppression (was [Sipping] Comments on updated KPML
draft)


On the one hand, it is trivially easy to add a "suppress=yes" parameter
to the digit map tag.  However, I am still VERY concerned about the
local/remote digit processing.  For review, here is the example from the
draft:

<quote>
NOTE: If KPML did not have this behavior, then a user device executing
KPML could easily break called applications. For example, take a
personal assistant that uses "*9" for attention. If the user presses the
"*" key, KPML will hold the digit, looking for the "9". What if the user
just enters a "*" key, possibly because they accessed an IVR system that
looks for "*"? In this case, the "*" would get held by the user device,
because it is looking for the "*9" pattern. The user would probably
press the "*" key again, hoping that the called IVR system just did not
hear the key press. At that point, the user device would send both "*"
entries, as "**" does not match "*9". However, that would not have the
effect the user intended when they pressed "*". 
</quote>

Does this issue ever go away?



> Original Message From: Bert Culpepper 
> [mailto:bertculpepper@netscape.net]
[snip]
>  > The text at the end of this section discusses the
> inability for a user
>  > device to know that signaled digits are for KPML processing or the
>  > recipients of a media stream.  Therefore DTMF must be sent 
> in the media
>  > stream in addition to be reported using KPML.  It seems to 
> me that if a
>  > user device receives a KPML document for processing, it'll 
> know based on
>  > the digit map what is meant for processing vs. sending in the media
>  > stream.  I realize processing key presses for digit map 
> matching will
>  > delay the transmission when matches don't occur, however I 
> expect this
>  > delay to be very small, resulting in no degradation of the user 
> experience.
> 
> Reflecting on my weekend comments, the cases where it would be OK to 
> delay sending indications in the media stream are limited to very
> short digit maps (a single digit practically speaking).  But for those
> cases, long digits such as the "long pound", and when focus can be
> determined by the user device, it'll be desirable to NOT to have the
> indications duplicated in the media stream.
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip Use
sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sun Mar 16 11:20:14 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28635
	for <sipping-archive@odin.ietf.org>; Sun, 16 Mar 2003 11:20:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2GGaCM07626
	for sipping-archive@odin.ietf.org; Sun, 16 Mar 2003 11:36:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2GGaCO07623
	for <sipping-web-archive@optimus.ietf.org>; Sun, 16 Mar 2003 11:36:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28601
	for <sipping-web-archive@ietf.org>; Sun, 16 Mar 2003 11:19:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2GGYqO07525;
	Sun, 16 Mar 2003 11:34:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EGIDO21638
	for <sipping@optimus.ietf.org>; Fri, 14 Mar 2003 11:18:13 -0500
Received: from kcmso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00573
	for <sipping@ietf.org>; Fri, 14 Mar 2003 11:02:41 -0500 (EST)
Received: from maillennium.att.com ([135.25.114.99])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h2EG4qFl015014
	for <sipping@ietf.org>; Fri, 14 Mar 2003 10:04:52 -0600 (CST)
Received: from fisherlatitude (unknown[135.210.35.100](misconfigured sender))
          by maillennium.att.com (mailgw1) with SMTP
          id <20030314160402gw100nj04qe>; Fri, 14 Mar 2003 16:04:04 +0000
From: "Steve Fisher" <sfisher1@att.com>
To: "'Eric Burger'" <eburger@snowshore.com>,
        "'Bert Culpepper'" <bertculpepper@netscape.net>
Cc: "'SIPPING List'" <sipping@ietf.org>
Subject: RE: Digit suppression (was [Sipping] Comments on updated KPML draft)
Date: Fri, 14 Mar 2003 11:04:06 -0500
Message-ID: <000101c2ea43$58661a30$6423d287@fisherlatitude>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D2488E1@zoe.office.snowshore.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Eric,

I know we've been having this discussion forever, but it still seems to
me that AT&T's Transfer Connect service serves as a good model for how
this can work (we've been working on similar services for end users that
leverage SIP's ability to make "media transfer" far more efficient than
was possible in the PSTN, and so this is more than an academic exercise
for us). 

In Transfer Connect there is an "agent" listening for tones. Until it
hears "*8", it passes them through. Once it hears "*8", though, it
assumes that the transfer connect application has the focus, and
suppresses the next 10 digits. I'm sure most of us in the US have heard
the effect of this service when we call a toll-free number, get an IVR
system, and are then transferred to a live agent -- we hear the "*8",
but do not hear the next 10 tones (I suspect we can all agree that even
those 2 tones are annoying -- 12 would be intolerable!).

Thus, in this model there is one set of tones that is used to determine
the focus, and then another set that provides the actual data for that
application. It seems to me that this model could apply to KPML, using
something like the following:

Add an additional attribute to the <regex> tag named, say, "suppress",
as in the following example:

<regex value="E8"
	suppress="10" 
	href="sip:" /> 

This would be equivalent to the following tag:

<regex value="E8XXXXXXXXXX" href="sip:" />
	
except that the UA may, at its discretion (I do think support for
"suppress" should be optional), suppress the 10 digits following the
"*8" from the audio path. In this case the application server is
providing a hint to the UA that if it sees a "*8" then this application
wants the focus, and that the next 10 digits should only be sent to this
application (via SIP NOTIFY), and not to any other application,
including an application that may be on the other end of the media
stream. Note that in this model there is no "holding" of digits that
produced the bad behavior you cite in your example. The UA knows, for
each digit, whether to suppress it or not.

Of course, another application may also have "*8" as part of its <regex>
tag, and in this case the UA should probably ignore the "suppress"
attribute. Alternatively, the UA could NOTIFY both applications, but
still suppress the tones.

Is this reasonable?

Thanks!
Steve Fisher
Division Manager
AT&T Labs

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
Of Eric Burger
Sent: Friday, March 14, 2003 10:09 AM
To: Bert Culpepper
Cc: SIPPING List
Subject: Digit suppression (was [Sipping] Comments on updated KPML
draft)


On the one hand, it is trivially easy to add a "suppress=yes" parameter
to the digit map tag.  However, I am still VERY concerned about the
local/remote digit processing.  For review, here is the example from the
draft:

<quote>
NOTE: If KPML did not have this behavior, then a user device executing
KPML could easily break called applications. For example, take a
personal assistant that uses "*9" for attention. If the user presses the
"*" key, KPML will hold the digit, looking for the "9". What if the user
just enters a "*" key, possibly because they accessed an IVR system that
looks for "*"? In this case, the "*" would get held by the user device,
because it is looking for the "*9" pattern. The user would probably
press the "*" key again, hoping that the called IVR system just did not
hear the key press. At that point, the user device would send both "*"
entries, as "**" does not match "*9". However, that would not have the
effect the user intended when they pressed "*". 
</quote>

Does this issue ever go away?



> Original Message From: Bert Culpepper
> [mailto:bertculpepper@netscape.net]
[snip]
>  > The text at the end of this section discusses the inability for a 
> user  > device to know that signaled digits are for KPML processing or

> the  > recipients of a media stream.  Therefore DTMF must be sent
> in the media
>  > stream in addition to be reported using KPML.  It seems to 
> me that if a
>  > user device receives a KPML document for processing, it'll 
> know based on
>  > the digit map what is meant for processing vs. sending in the media
>  > stream.  I realize processing key presses for digit map 
> matching will
>  > delay the transmission when matches don't occur, however I 
> expect this
>  > delay to be very small, resulting in no degradation of the user 
> experience.
> 
> Reflecting on my weekend comments, the cases where it would be OK to
> delay sending indications in the media stream are limited to very
> short digit maps (a single digit practically speaking).  But for those
> cases, long digits such as the "long pound", and when focus can be
> determined by the user device, it'll be desirable to NOT to have the
> indications duplicated in the media stream.
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip Use
sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sun Mar 16 20:18:51 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14858
	for <sipping-archive@odin.ietf.org>; Sun, 16 Mar 2003 20:18:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2H1Z1E07510
	for sipping-archive@odin.ietf.org; Sun, 16 Mar 2003 20:35:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2H1Z1O07507
	for <sipping-web-archive@optimus.ietf.org>; Sun, 16 Mar 2003 20:35:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14846
	for <sipping-web-archive@ietf.org>; Sun, 16 Mar 2003 20:18:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2H1XBO07421;
	Sun, 16 Mar 2003 20:33:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2H1U5O07344
	for <sipping@optimus.ietf.org>; Sun, 16 Mar 2003 20:30:05 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14674
	for <sipping@ietf.org>; Sun, 16 Mar 2003 20:13:25 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Sun, 16 Mar 2003 20:17:49 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D2488FB@zoe.office.snowshore.com>
Thread-Topic: Proposal for Digit Suppression
Thread-Index: AcLsFwstck0RV/w0TuWvKdQAoqcpLg==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2H1U5O07345
Subject: [Sipping] Proposal for Digit Suppression
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

OK, I'm convinced.  I'm willing to put out a chain saw.  If you are in a well-defined, controlled environment (e.g., Steve Fisher's example), then one can quickly cut down a big tree.  However, if you are not in a well-defined environment, you can quickly cut off your own foot.

I don't see inter-digit timing working out (Tom's suggestion, <http://www1.ietf.org/mail-archive/working-groups/sipping/current/msg04172.html>), as it will always be wrong and will still most likely result in the ** behaviour described in the draft for the general case.

Rather than suppressing on match, how about suppressing anything that starts the match?  Would that have problems in the controlled environments?  E.g., the *T would also get suppressed, and * alone or *[~T] would get buffered and timed out?
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 04:00:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07405
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 04:00:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2H9Gae15954
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 04:16:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2H9GZO15951
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 04:16:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07373
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 03:59:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2H9FdO15916;
	Mon, 17 Mar 2003 04:15:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2H9ETO15853
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 04:14:29 -0500
Received: from bdsl.greycouncil.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07321
	for <sipping@ietf.org>; Mon, 17 Mar 2003 03:57:40 -0500 (EST)
Received: from txdwillis (h-66-166-232-219.SNVACAID.covad.net [66.166.232.219])
	(authenticated bits=0)
	by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id h2H8xn49010807
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Mon, 17 Mar 2003 02:59:52 -0600
From: "Dean Willis" <dean.willis@softarmor.com>
To: "'Shane McCormack'" <smccormack@tssg.org>, <sipping@ietf.org>
Subject: RE: [Sipping] Spatial Location
Date: Mon, 17 Mar 2003 02:59:49 -0600
Message-ID: <002001c2ec63$926eaf40$2200000a@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <HKEILFGJCBMBHOCGMAJNEEEMDBAA.smccormack@tssg.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2H9ETO15854
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Shane asked:
>Is their any work been done in 
> this area currently or any documentation regarding how it 
> applies to a sip service. Is their a provision for an Even 
> Notification for spatial geographical location?

I believe we're waiting on output from geopriv.

Once this happens, it would seem obvious that one could include geoloc
(perhaps indirectly) in one's presence document, for which we have a
subscription/notficication mechanism fairly well worked out. This is
actually happening in the SIMPLE working group, not SIPPING.

There have also been discussions from time to time of doing an event package
specifically for geoloc transmission, another for informing mobile terminals
of location related information, like "The game is on in the pub across the
street", and several other sorts of things. As far as I know, none of these
have really "set up" yet.

--
Dean

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 04:59:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09036
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 04:59:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HAG8r20740
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 05:16:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HAG8O20737
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 05:16:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09024
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 04:59:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HAFMO20703;
	Mon, 17 Mar 2003 05:15:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HAEHO20642
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 05:14:17 -0500
Received: from mail3.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09005
	for <sipping@ietf.org>; Mon, 17 Mar 2003 04:57:27 -0500 (EST)
Received: from dynamicsoft.com (dyn-tx-app-004.dfw.dynamicsoft.com [63.110.3.2])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h2H9xfJD018835;
	Mon, 17 Mar 2003 04:59:42 -0500 (EST)
Message-ID: <3E759C83.5070605@dynamicsoft.com>
Date: Mon, 17 Mar 2003 04:59:31 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Steve Fisher <sfisher1@att.com>
CC: "'Eric Burger'" <eburger@snowshore.com>,
        "'Bert Culpepper'" <bertculpepper@netscape.net>,
        "'SIPPING List'" <sipping@ietf.org>
Subject: Re: Digit suppression (was [Sipping] Comments on updated KPML draft)
References: <000001c2ea43$26702f70$6423d287@fisherlatitude>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I think I would be comfortable with a suppression mechanism if we place 
some constraints on it:

1.  it only suppressed when there were no ambguities in the digit map. 
That is, if after pressing a digit sequence, only one pattern across all 
KPMLs matched, and that pattern expressed a suppression, you would 
suppress from the media stream.

2. the text is clear that this can interfere with the operation of other 
applications listening on the media stream. You should only do 
suppression when you are using "focus detection" digit maps of 
sufficient length to be certain of this (i.e., not * or #).


Now, you can still run into trouble when the media stream terminates on 
a gateway or application server that is looking for dtmf patterns but 
not using KPML. But with the above caveats perhaps we can make that case 
an infrequent one.

-Jonathan R.


Steve Fisher wrote:
> Eric,
> 
> I know we've been having this discussion forever, but it still seems to
> me that AT&T's Transfer Connect service serves as a good model for how
> this can work (we've been working on similar services for end users that
> leverage SIP's ability to make "media transfer" far more efficient than
> was possible in the PSTN, and so this is more than an academic exercise
> for us). 
> 
> In Transfer Connect there is an "agent" listening for tones. Until it
> hears "*8", it passes them through. Once it hears "*8", though, it
> assumes that the transfer connect application has the focus, and
> suppresses the next 10 digits. I'm sure most of us in the US have heard
> the effect of this service when we call a toll-free number, get an IVR
> system, and are then transferred to a live agent -- we hear the "*8",
> but do not hear the next 10 tones (I suspect we can all agree that even
> those 2 tones are annoying -- 12 would be intolerable!).
> 
> Thus, in this model there is one set of tones that is used to determine
> the focus, and then another set that provides the actual data for that
> application. It seems to me that this model could apply to KPML, using
> something like the following:
> 
> Add an additional attribute to the <regex> tag named, say, "suppress",
> as in the following example:
> 
> <regex value="E8"
> 	suppress="10" 
> 	href="sip:" /> 
> 
> This would be equivalent to the following tag:
> 
> <regex value="E8XXXXXXXXXX" href="sip:" />
> 	
> except that the UA may, at its discretion (I do think support for
> "suppress" should be optional), suppress the 10 digits following the
> "*8" from the audio path. In this case the application server is
> providing a hint to the UA that if it sees a "*8" then this application
> wants the focus, and that the next 10 digits should only be sent to this
> application (via SIP NOTIFY), and not to any other application,
> including an application that may be on the other end of the media
> stream.
> 
> Of course, another application may also have "*8" as part of its <regex>
> tag, and in this case the UA should probably ignore the "suppress"
> attribute. Alternatively, the UA could NOTIFY both applications, but
> still suppress the tones.
> 
> Is this reasonable?
> 
> Thanks!
> Steve Fisher
> Division Manager
> AT&T Labs
> 
> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
> Of Eric Burger
> Sent: Friday, March 14, 2003 10:09 AM
> To: Bert Culpepper
> Cc: SIPPING List
> Subject: Digit suppression (was [Sipping] Comments on updated KPML
> draft)
> 
> 
> On the one hand, it is trivially easy to add a "suppress=yes" parameter
> to the digit map tag.  However, I am still VERY concerned about the
> local/remote digit processing.  For review, here is the example from the
> draft:
> 
> <quote>
> NOTE: If KPML did not have this behavior, then a user device executing
> KPML could easily break called applications. For example, take a
> personal assistant that uses "*9" for attention. If the user presses the
> "*" key, KPML will hold the digit, looking for the "9". What if the user
> just enters a "*" key, possibly because they accessed an IVR system that
> looks for "*"? In this case, the "*" would get held by the user device,
> because it is looking for the "*9" pattern. The user would probably
> press the "*" key again, hoping that the called IVR system just did not
> hear the key press. At that point, the user device would send both "*"
> entries, as "**" does not match "*9". However, that would not have the
> effect the user intended when they pressed "*". 
> </quote>
> 
> Does this issue ever go away?
> 
> 
> 
> 
>>Original Message From: Bert Culpepper 
>>[mailto:bertculpepper@netscape.net]
> 
> [snip]
> 
>> > The text at the end of this section discusses the
>>inability for a user
>> > device to know that signaled digits are for KPML processing or the
>> > recipients of a media stream.  Therefore DTMF must be sent 
>>in the media
>> > stream in addition to be reported using KPML.  It seems to 
>>me that if a
>> > user device receives a KPML document for processing, it'll 
>>know based on
>> > the digit map what is meant for processing vs. sending in the media
>> > stream.  I realize processing key presses for digit map 
>>matching will
>> > delay the transmission when matches don't occur, however I 
>>expect this
>> > delay to be very small, resulting in no degradation of the user 
>>experience.
>>
>>Reflecting on my weekend comments, the cases where it would be OK to 
>>delay sending indications in the media stream are limited to very
>>short digit maps (a single digit practically speaking).  But for those
>>cases, long digits such as the "long pound", and when focus can be
>>determined by the user device, it'll be desirable to NOT to have the
>>indications duplicated in the media stream.
>>
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip Use
> sip@ietf.org for new developments of core SIP
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 05:05:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09169
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 05:05:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HALq020937
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 05:21:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HALpO20934
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 05:21:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09161
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 05:05:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HALBO20907;
	Mon, 17 Mar 2003 05:21:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HAKOO20880
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 05:20:24 -0500
Received: from mail3.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09124
	for <sipping@ietf.org>; Mon, 17 Mar 2003 05:03:34 -0500 (EST)
Received: from dynamicsoft.com (dyn-tx-app-004.dfw.dynamicsoft.com [63.110.3.2])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h2HA5oJD018856;
	Mon, 17 Mar 2003 05:05:50 -0500 (EST)
Message-ID: <3E759DF4.3090409@dynamicsoft.com>
Date: Mon, 17 Mar 2003 05:05:40 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bert Culpepper <bertculpepper@netscape.net>
CC: Eric Burger <eburger@snowshore.com>, SIPPING List <sipping@ietf.org>
Subject: Re: Use of NOTIFY in KPML (was [SIPPING] Comments on updated KPML
 draft)
References: <4A3384433CE2AB46A63468CB207E209D2488E2@zoe.office.snowshore.com> <3E726B8B.60906@netscape.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

inline.

Bert Culpepper wrote:

>>> Another issue is that it's stated that a KPML session ends when a 
>>> NOTIFY is sent, and further KPML sessions must be established with a 
>>> reINVITE.  Why not allow a KPML document in the body of the 200 OK 
>>> response to the NOTIFY as specified similarly for HTTP reporting?  
>>> This saves three messages between the application and user device.
>>>
>>
>> I don't have a problem with that.  However, I can hear a chorus of 
>> objection.  Principally, if you fetch a document, execute it, return a 
>> result, and that results in a new document, why aren't you using HTTP?
> 
> 
> 
> My quick answer of not using HTTP is the fact that a SIP mechanism is 
> now defined :)  Not knowing the motivation behind this addition I can't 
> speak more to this point. 

I would like to be clear that there is still not design team consensus 
on this point.


  However, having to send a reINVITE if an
> entity (specifically a SIP proxy) wishes to "continue" the KPML session 
> (or start a HTML/HTTP session) requires more SIP UA functionality in the 
> entity than otherwise required.  I'll admit, I don't have any use cases 
> in mind at the moment.  But I don't understand this limitation, perhaps 
> some explanatory text motivating the defined behavior is enough.

I think the bigger meta-issue is what a KPML "session" means. KPML 
provides no means for prompting. Thus, in most applications I can think 
of, you have a single KPML, collect a digit, and use that to kick off a 
real dialog, using VoiceXML or something like that. The KPML draft 
offers one other use case for KPML where there are multiple documents 
without prompting, by using VoiceXML in a server, and collecting digits 
via KPML. I think it is worth considering whether this should be in 
scope or not. The only benefit to this above rfc2833 is the possibility 
of "immediate barge", which is a fringe feature, to be certain. I am 
looking for places to cut back scope of this work so as to move it along 
faster, and this looked like one opportunity.

What kind of applications did people REALLY have in mind for this, and 
were those applications needing anything more than a single KPML 
document before a real dialog is carried out?


-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 10:25:53 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17048
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 10:25:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HFgI808817
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 10:42:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HFgIO08814
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 10:42:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17029
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 10:25:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HFcLO08572;
	Mon, 17 Mar 2003 10:38:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HFbNO08253
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 10:37:23 -0500
Received: from brazilnut.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16850
	for <sipping@ietf.org>; Mon, 17 Mar 2003 10:20:26 -0500 (EST)
Received: from cs.columbia.edu (ca-71-247.wired.ietf56.ietf.org [130.129.71.247])
	(user=hgs10 mech=PLAIN bits=0)
	by brazilnut.cc.columbia.edu (8.12.8/8.12.8) with ESMTP id h2HFMa2O009654
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Mon, 17 Mar 2003 10:22:38 -0500 (EST)
Message-ID: <3E75E789.8090200@cs.columbia.edu>
Date: Mon, 17 Mar 2003 10:19:37 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
CC: "'Shane McCormack'" <smccormack@tssg.org>, sipping@ietf.org
Subject: Re: [Sipping] Spatial Location
References: <002001c2ec63$926eaf40$2200000a@txdwillis>
In-Reply-To: <002001c2ec63$926eaf40$2200000a@txdwillis>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Dean Willis wrote:
> Shane asked:
> 
>>Is their any work been done in 
>>this area currently or any documentation regarding how it 
>>applies to a sip service. Is their a provision for an Even 
>>Notification for spatial geographical location?
> 
> 
> I believe we're waiting on output from geopriv.
> 
> Once this happens, it would seem obvious that one could include geoloc
> (perhaps indirectly) in one's presence document, for which we have a
> subscription/notficication mechanism fairly well worked out. This is
> actually happening in the SIMPLE working group, not SIPPING.

It is not clear to me that this is the most robust approach, as you 
would then have to, during an emergency call,
- upload your location
- tell the emergency call center what your presence address is
- get the credentials (and address) for the ECC
- either add them to the access list or explicitly allow access, via the 
usual "Foo wants to subscribe to your presence, click Yes or No" button.
- the ECC then has to subscribe and get the notification



> 
> There have also been discussions from time to time of doing an event package
> specifically for geoloc transmission, another for informing mobile terminals
> of location related information, like "The game is on in the pub across the
> street", and several other sorts of things. As far as I know, none of these
> have really "set up" yet.
> 
> --
> Dean
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 11:35:16 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19400
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 11:35:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HGphr13514
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 11:51:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HGphO13511
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 11:51:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19371
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 11:34:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HGoZO13463;
	Mon, 17 Mar 2003 11:50:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HGlLO13319
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 11:47:21 -0500
Received: from bdsl.greycouncil.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19129
	for <sipping@ietf.org>; Mon, 17 Mar 2003 11:30:22 -0500 (EST)
Received: from txdwillis (h-66-166-232-219.SNVACAID.covad.net [66.166.232.219])
	(authenticated bits=0)
	by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id h2HGWF49013544
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Mon, 17 Mar 2003 10:32:16 -0600
From: "Dean Willis" <dean.willis@softarmor.com>
To: "'Henning Schulzrinne'" <hgs@cs.columbia.edu>
Cc: "'Shane McCormack'" <smccormack@tssg.org>, <sipping@ietf.org>
Subject: RE: [Sipping] Spatial Location
Date: Mon, 17 Mar 2003 10:32:13 -0600
Message-ID: <002f01c2eca2$c58c7990$2200000a@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <3E75E789.8090200@cs.columbia.edu>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2HGlLO13320
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> Dean Willis wrote:
> > Shane asked:
> > 
> >>Is their any work been done in
> >>this area currently or any documentation regarding how it 
> >>applies to a sip service. Is their a provision for an Even 
> >>Notification for spatial geographical location?
> > 
> > 
> > I believe we're waiting on output from geopriv.
> > 
> > Once this happens, it would seem obvious that one could 
> include geoloc 
> > (perhaps indirectly) in one's presence document, for which 
> we have a 
> > subscription/notficication mechanism fairly well worked 
> out. This is 
> > actually happening in the SIMPLE working group, not SIPPING.

And Henning said: 
> It is not clear to me that this is the most robust approach, as you 
> would then have to, during an emergency call,
> - upload your location
> - tell the emergency call center what your presence address is
> - get the credentials (and address) for the ECC
> - either add them to the access list or explicitly allow 
> access, via the 
> usual "Foo wants to subscribe to your presence, click Yes or 
> No" button.
> - the ECC then has to subscribe and get the notification

Admittedly, emergency services are a different question than adding location
to presence. Very different requirements. These requirements weren't clear
to me from Shane's question. Do we have a rigorous statement of the
requirements somewhere?

Presuming that the requirement is something like "Provide location
information within the dialog associated with an emergency call such that
location information is available to the PSAP when the dialog is requested"
or some such, then the answer probably looks more like "Put a geoloc body
into the SIP INVITE request using multipart MIME", which we still can't do
without geopriv and formats. But that is stating the answer before knowing
the problem, I think.

--
dean

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 12:19:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21150
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 12:19:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HHZwB17261
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 12:35:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHZvO17258
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 12:35:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21136
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 12:18:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHZAO17205;
	Mon, 17 Mar 2003 12:35:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHYEO17142
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 12:34:14 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21048
	for <sipping@ietf.org>; Mon, 17 Mar 2003 12:17:15 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z061HH>; Mon, 17 Mar 2003 12:17:36 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410D995BF1@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Henning Schulzrinne'" <hgs@cs.columbia.edu>,
        "Peterson, Jon"
	 <jon.peterson@neustar.biz>
Cc: "King, Kimberly S." <KIMBERLY.S.KING@saic.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Date: Mon, 17 Mar 2003 12:15:40 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Alternatively, I would phrase it as setting aside 90% of the capacity for
NON-ETS traffic. 

-----Original Message-----
From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
Major snip

> Agreed that partial deployment of ETS will be no worse than no deployment
> (provided that security issues are all handled well - if the system is
> exploitable, it could be quite a bit worse). I also agree that the
scarcity
> of gateway resources is one of the paramount concerns.

Any such system needs to limit the high-priority set-aside to some safe 
number so that even compromise does not significantly degrade the system 
below the non-enabled state. After all, the volume of ETS calls is 
usually only a tiny fraction of the total system capacity, so if you set 
aside, say, 10% of the capacity for ETS, you can limit the worst-case 
exposure.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 12:26:33 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21429
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 12:26:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HHh2p18489
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 12:43:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHh2O18486
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 12:43:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21403
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 12:26:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHgGO18399;
	Mon, 17 Mar 2003 12:42:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHfQO18335
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 12:41:26 -0500
Received: from dewberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21312
	for <sipping@ietf.org>; Mon, 17 Mar 2003 12:24:27 -0500 (EST)
Received: from cs.columbia.edu (wl-134-224.wireless.ietf56.ietf.org [130.129.134.224])
	(user=hgs10 mech=PLAIN bits=0)
	by dewberry.cc.columbia.edu (8.12.8/8.12.8) with ESMTP id h2HHQbGg002273
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Mon, 17 Mar 2003 12:26:39 -0500 (EST)
Message-ID: <3E76049B.3040207@cs.columbia.edu>
Date: Mon, 17 Mar 2003 12:23:39 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
CC: "'Shane McCormack'" <smccormack@tssg.org>, sipping@ietf.org
Subject: Re: [Sipping] Spatial Location
References: <002f01c2eca2$c58c7990$2200000a@txdwillis>
In-Reply-To: <002f01c2eca2$c58c7990$2200000a@txdwillis>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

draft-schulzrinne-sipping-emergency-req-01 is one view of the problem 
space (it does cover more than the geographic location issue).

> 
> Admittedly, emergency services are a different question than adding location
> to presence. Very different requirements. These requirements weren't clear
> to me from Shane's question. Do we have a rigorous statement of the
> requirements somewhere?
> 
> Presuming that the requirement is something like "Provide location
> information within the dialog associated with an emergency call such that
> location information is available to the PSAP when the dialog is requested"
> or some such, then the answer probably looks more like "Put a geoloc body
> into the SIP INVITE request using multipart MIME", which we still can't do
> without geopriv and formats. But that is stating the answer before knowing
> the problem, I think.
> 
> --
> dean

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 12:33:25 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21753
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 12:33:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HHnsS18875
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 12:49:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHnsO18872
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 12:49:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21743
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 12:32:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHn7O18825;
	Mon, 17 Mar 2003 12:49:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHmcO18749
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 12:48:38 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21661
	for <sipping@ietf.org>; Mon, 17 Mar 2003 12:31:38 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z061J1>; Mon, 17 Mar 2003 12:31:59 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410D995BF2@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Henning Schulzrinne'" <hgs@cs.columbia.edu>,
        "Peterson, Jon"
	 <jon.peterson@neustar.biz>
Cc: "King, Kimberly S." <KIMBERLY.S.KING@saic.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] Comments on draft-peterson-sipping-ieprep-00
Date: Mon, 17 Mar 2003 12:30:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This analogy (snipped bit included "(This is somewhat similar to the need to
dial 1010xxx to reach a 
> 710-aware carrier in the GETS system.)") actually is (in my opinion) very
important.  

The FIRST objective is to be able to pass the priority/ETS information to
the pieces that know what to do with it.  We don't want to LOSE the
priority/ETS information, just because the path goes through non-ETS-aware
devices

The SECOND objective is to DO SOMETHING based on the priority/ETS
information where possible (and that objective is, itself, prioritized in
terms of "where it will do the most good").

-----Original Message-----
From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]

Major snip

> A system which has no effect on congestion in the LEC, but is better than
> nothing.

You solve the problems you can solve...
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 12:37:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21876
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 12:37:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HHsHH19138
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 12:54:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHsHO19135
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 12:54:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21867
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 12:37:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHrHO19104;
	Mon, 17 Mar 2003 12:53:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HHqYO19040
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 12:52:34 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21831
	for <sipping@ietf.org>; Mon, 17 Mar 2003 12:35:34 -0500 (EST)
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2HHbCB3022792;
	Mon, 17 Mar 2003 18:37:12 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id FDVP170C; Mon, 17 Mar 2003 18:37:12 +0100
Received: from lmf.ericsson.se (vrrch2-177136.am.ericsson.se [138.85.177.136])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2HHbA6B010959;
	Mon, 17 Mar 2003 19:37:11 +0200 (EET)
Message-ID: <3E7607E0.C6DC48E0@lmf.ericsson.se>
Date: Mon, 17 Mar 2003 19:37:36 +0200
X-Sybari-Trust: 904e732d 9ffcebbb a5ee123c 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
CC: Dean Willis <dean.willis@softarmor.com>, Rohan Mahy <rohan@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Final agenda
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

this is the final SIPPING agenda. We have re-shuffled some slots and
added a last minute request.

http://www.softarmor.com/sipping/meets/ietf56/agenda.html

Regards,

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 16:31:15 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02364
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 16:31:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HLlno05085
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 16:47:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HLlnO05082
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 16:47:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02346
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 16:30:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HLkdO04969;
	Mon, 17 Mar 2003 16:46:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HLjOO04900
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 16:45:24 -0500
Received: from hoemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02202
	for <sipping@ietf.org>; Mon, 17 Mar 2003 16:28:19 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by hoemail2.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2HLUVs17602
	for <sipping@ietf.org>; Mon, 17 Mar 2003 16:30:31 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <XNTC4GS0>; Mon, 17 Mar 2003 21:30:30 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB007EAB7F6@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: sipping@ietf.org
Cc: schulzrinne@cs.columbia.edu
Date: Mon, 17 Mar 2003 21:30:28 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] Comments on draft-schulzrinne-sipping-emergency-req-00
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

a)	Section 3 definitions. I am unsure of the need to distinguish between "Basic emergency service" and "Enhanced emergency service". What I understood for emergency calls was that ideally all information available (i.e. carried in the normal call signalling) about the caller should be delivered. If the information was unavailable, the call should still be delivered.

b)	Section 4, M2: "Call setup delay: The call setup delay MUST NOT be no larger than for existing analog trunks." translates as "Call setup delay: The call setup delay MUST NOT be smaller than for existing analog trunks ..., which is obviously not the meaning.

c)	Section 4, M3: Why not just refer here to the transfer of standard E164 addresses. E.164 specifies a maximum length for these addresses.

d)	Section 4, M4 and M5 specify the need for certain additional services. There should also be requirements to be able to override other services so that that service is not imposed. For example, if there is a SIP version of the closed user group service ever invented, then it would be inappropriate for the network of the ECC to allow this to be used on an emergency call. However, I would suggest this is expressed generally, rather than in a service specific manner.

e)	Section 5.1, A2: We have discussed before that there are really two levels of requirements here. The first level concerns those numbers that are used somewhere for emergency calling purposes, but that are not used elsewhere in the world for any other purposes. These should always be emergency calls. The second level concerns numbers that are used elsewhere for emergency calls, and do not conflict with local usage for some other purpose, or represent local usage for some other purpose in the terminal owners normal home environment. Where the service provider provides a device for insertion in the terminal, or where this information can be downloaded to the terminal, these can also be made by the terminal as emergency calls. Such calls should be specifically tagged as emergency calls, and presumably made using the emergency SIP URL rather than using the normal emergency digits.

f)	Additionally to the above, if the transport mechanism provides specific indications for emergency calls, e.g. to allow special routeing or special QoS, then those should be used where a call is identified as an emergency call. E.g. 3GPP is likely to define special characteristics of a PDP context that is solely used for emergency calls. Primarily this is expected to have a routeing impact.

g)	Section 6, S1: The term "unauthenticated emergency calls" is not correct as it implies that the user has to authenticate with the ECC in order to make an emergency call. Prefer "...allow an unauthencicated user to call the emergency call centre."

regards

Keith


Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 16:37:23 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02929
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 16:37:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HLruO05494
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 16:53:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HLruO05491
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 16:53:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02890
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 16:36:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HLr5O05415;
	Mon, 17 Mar 2003 16:53:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2H2GvO10383
	for <sipping@optimus.ietf.org>; Sun, 16 Mar 2003 21:16:57 -0500
Received: from kcmso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15795
	for <sipping@ietf.org>; Sun, 16 Mar 2003 21:00:15 -0500 (EST)
Received: from maillennium.att.com ([135.25.114.99])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h2H22SFl006612
	for <sipping@ietf.org>; Sun, 16 Mar 2003 20:02:28 -0600 (CST)
Received: from fisherlatitude (unknown[135.210.0.33](misconfigured sender))
          by maillennium.att.com (mailgw1) with SMTP
          id <20030317020135gw100niu8re>; Mon, 17 Mar 2003 02:01:39 +0000
From: "Steve Fisher" <sfisher1@att.com>
To: "'Eric Burger'" <eburger@snowshore.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
Subject: RE: [Sipping] Proposal for Digit Suppression
Date: Sun, 16 Mar 2003 21:01:37 -0500
Message-ID: <000101c2ec29$285c0a10$2100d287@fisherlatitude>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D2488FB@zoe.office.snowshore.com>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

If I understand your suggestion correctly, my preference would be
"suppress on match", i.e. only suppress after a set of digits has been
pressed to indicate that the app should have the focus. I would think
that buffering "*" would also result in the ** behavior described in the
draft, wouldn't it? Even in controlled environments, callers are
frequently still talking to automated systems that prompt for keypresses
such as "*".

Steve Fisher
Division Manager
AT&T Labs

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
Of Eric Burger
Sent: Sunday, March 16, 2003 8:18 PM
To: Sipping (E-mail)
Subject: [Sipping] Proposal for Digit Suppression


OK, I'm convinced.  I'm willing to put out a chain saw.  If you are in a
well-defined, controlled environment (e.g., Steve Fisher's example),
then one can quickly cut down a big tree.  However, if you are not in a
well-defined environment, you can quickly cut off your own foot.

I don't see inter-digit timing working out (Tom's suggestion,
<http://www1.ietf.org/mail-archive/working-groups/sipping/current/msg041
72.html>), as it will always be wrong and will still most likely result
in the ** behaviour described in the draft for the general case.

Rather than suppressing on match, how about suppressing anything that
starts the match?  Would that have problems in the controlled
environments?  E.g., the *T would also get suppressed, and * alone or
*[~T] would get buffered and timed out?
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip Use
sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 16:37:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02955
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 16:37:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HLs2v05531
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 16:54:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HLs2O05528
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 16:54:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02900
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 16:36:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HLr7O05435;
	Mon, 17 Mar 2003 16:53:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HI48O19721
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 13:04:08 -0500
Received: from kcmso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22200
	for <sipping@ietf.org>; Mon, 17 Mar 2003 12:47:07 -0500 (EST)
Received: from maillennium.att.com ([135.25.114.99])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h2HHnJFl014839
	for <sipping@ietf.org>; Mon, 17 Mar 2003 11:49:19 -0600 (CST)
Received: from fisherlatitude (unknown[135.210.128.146](misconfigured sender))
          by maillennium.att.com (mailgw1) with SMTP
          id <20030317174827gw100niuqde>; Mon, 17 Mar 2003 17:48:28 +0000
From: "Steve Fisher" <sfisher1@att.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>
Cc: "'SIPPING List'" <sipping@ietf.org>
Subject: RE: Use of NOTIFY in KPML (was [SIPPING] Comments on updated KPML draft)
Date: Mon, 17 Mar 2003 12:48:31 -0500
Message-ID: <000001c2ecad$6dd7ed00$9280d287@fisherlatitude>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0001_01C2EC83.8501E500"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
In-Reply-To: <3E759DF4.3090409@dynamicsoft.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0001_01C2EC83.8501E500
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Jonathan,
 
For all of the applications that we have in mind, the digits interpreted
by the KPML document would either move the "far" end of the call to a
media server, thus removing the need for the KPML document (at least for
awhile), or would move the caller from one device to another, which
would result in a new INVITE for the new device anyway. Thus, for our
apps, having to issue a reINVITE to set a new KPML document would be
fine. 
 
We are also very eager to move this work along, as it's quite critical
for many of the services we hope to roll out.
 
Steve

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
Of Jonathan Rosenberg
Sent: Monday, March 17, 2003 5:06 AM
To: Bert Culpepper
Cc: Eric Burger; SIPPING List
Subject: Re: Use of NOTIFY in KPML (was [SIPPING] Comments on updated
KPML draft)


inline.

Bert Culpepper wrote:

>>> Another issue is that it's stated that a KPML session ends when a
>>> NOTIFY is sent, and further KPML sessions must be established with a

>>> reINVITE. Why not allow a KPML document in the body of the 200 OK 
>>> response to the NOTIFY as specified similarly for HTTP reporting? 
>>> This saves three messages between the application and user device.
>>>
>>
>> I don't have a problem with that. However, I can hear a chorus of
>> objection. Principally, if you fetch a document, execute it, return a

>> result, and that results in a new document, why aren't you using
HTTP?
> 
> 
> 
> My quick answer of not using HTTP is the fact that a SIP mechanism is
> now defined :) Not knowing the motivation behind this addition I can't

> speak more to this point. 

I would like to be clear that there is still not design team consensus 
on this point.


However, having to send a reINVITE if an
> entity (specifically a SIP proxy) wishes to "continue" the KPML 
> session
> (or start a HTML/HTTP session) requires more SIP UA functionality in
the 
> entity than otherwise required. I'll admit, I don't have any use cases

> in mind at the moment. But I don't understand this limitation, perhaps

> some explanatory text motivating the defined behavior is enough.

I think the bigger meta-issue is what a KPML "session" means. KPML 
provides no means for prompting. Thus, in most applications I can think 
of, you have a single KPML, collect a digit, and use that to kick off a 
real dialog, using VoiceXML or something like that. The KPML draft 
offers one other use case for KPML where there are multiple documents 
without prompting, by using VoiceXML in a server, and collecting digits 
via KPML. I think it is worth considering whether this should be in 
scope or not. The only benefit to this above rfc2833 is the possibility 
of "immediate barge", which is a fringe feature, to be certain. I am 
looking for places to cut back scope of this work so as to move it along

faster, and this looked like one opportunity.

What kind of applications did people REALLY have in mind for this, and 
were those applications needing anything more than a single KPML 
document before a real dialog is carried out?


-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
jdrosen@dynamicsoft.com FAX: (973) 952-5050 <tel:+19739525050> 
http://www.jdrosen.net PHONE: (973) 952-5000 <tel:+19739525000> 
http://www.dynamicsoft.com

_______________________________________________
Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip Use
sip@ietf.org for new developments of core SIP



------=_NextPart_000_0001_01C2EC83.8501E500
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- This message has been modified by the AT&T Click-to-Dial Add-In =
--><HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D438593617-17032003>Jonathan,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D438593617-17032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D438593617-17032003>For=20
all of the applications that we have in mind, the digits interpreted by =
the KPML=20
document would either move the "far" end of the call to a media server, =
thus=20
removing the need for the KPML document (at least for awhile), or would =
move the=20
caller from one device to another, which would result in a new INVITE =
for the=20
new device anyway. Thus, for our apps, having to issue a reINVITE to set =
a new=20
KPML document would be fine. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D438593617-17032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D438593617-17032003>We are=20
also very eager to move this work along, as it's quite critical for many =
of the=20
services we hope to roll out.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D438593617-17032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D438593617-17032003>Steve</SPAN></FONT></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] <B>On Behalf Of =

  </B>Jonathan Rosenberg<BR><B>Sent:</B> Monday, March 17, 2003 5:06=20
  AM<BR><B>To:</B> Bert Culpepper<BR><B>Cc:</B> Eric Burger; SIPPING=20
  List<BR><B>Subject:</B> Re: Use of NOTIFY in KPML (was [SIPPING] =
Comments on=20
  updated KPML draft)<BR><BR></FONT></DIV><TT>inline.<BR><BR>Bert =
Culpepper=20
  wrote:<BR><BR>&gt;&gt;&gt; Another issue is that it's stated that a =
KPML=20
  session ends when a<BR>&gt;&gt;&gt; NOTIFY is sent, and further KPML =
sessions=20
  must be established with a <BR>&gt;&gt;&gt; reINVITE. Why not allow a =
KPML=20
  document in the body of the 200 OK <BR>&gt;&gt;&gt; response to the =
NOTIFY as=20
  specified similarly for HTTP reporting? <BR>&gt;&gt;&gt; This saves =
three=20
  messages between the application and user=20
  device.<BR>&gt;&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt; I don't have a problem =
with=20
  that. However, I can hear a chorus of<BR>&gt;&gt; objection. =
Principally, if=20
  you fetch a document, execute it, return a <BR>&gt;&gt; result, and =
that=20
  results in a new document, why aren't you using HTTP?<BR>&gt; <BR>&gt; =

  <BR>&gt; <BR>&gt; My quick answer of not using HTTP is the fact that a =
SIP=20
  mechanism is<BR>&gt; now defined :) Not knowing the motivation behind =
this=20
  addition I can't <BR>&gt; speak more to this point. <BR><BR>I would =
like to be=20
  clear that there is still not design team consensus <BR>on this=20
  point.<BR><BR><BR>However, having to send a reINVITE if an<BR>&gt; =
entity=20
  (specifically a SIP proxy) wishes to "continue" the KPML <BR>&gt;=20
  session<BR>&gt; (or start a HTML/HTTP session) requires more SIP UA=20
  functionality in the <BR>&gt; entity than otherwise required. I'll =
admit, I=20
  don't have any use cases <BR>&gt; in mind at the moment. But I don't=20
  understand this limitation, perhaps <BR>&gt; some explanatory text =
motivating=20
  the defined behavior is enough.<BR><BR>I think the bigger meta-issue =
is what a=20
  KPML "session" means. KPML <BR>provides no means for prompting. Thus, =
in most=20
  applications I can think <BR>of, you have a single KPML, collect a =
digit, and=20
  use that to kick off a <BR>real dialog, using VoiceXML or something =
like that.=20
  The KPML draft <BR>offers one other use case for KPML where there are =
multiple=20
  documents <BR>without prompting, by using VoiceXML in a server, and =
collecting=20
  digits <BR>via KPML. I think it is worth considering whether this =
should be in=20
  <BR>scope or not. The only benefit to this above rfc2833 is the =
possibility=20
  <BR>of "immediate barge", which is a fringe feature, to be certain. I =
am=20
  <BR>looking for places to cut back scope of this work so as to move it =
along=20
  <BR>faster, and this looked like one opportunity.<BR><BR>What kind of=20
  applications did people REALLY have in mind for this, and <BR>were =
those=20
  applications needing anything more than a single KPML <BR>document =
before a=20
  real dialog is carried out?<BR><BR><BR>-Jonathan R.<BR><BR><BR>-- =
<BR>Jonathan=20
  D. Rosenberg, Ph.D. 72 Eagle Rock Ave.<BR>Chief Scientist First=20
  Floor<BR>dynamicsoft East Hanover, NJ 07936<BR><A=20
  href=3D"mailto:jdrosen@dynamicsoft.com">jdrosen@dynamicsoft.com</A> =
FAX: <A=20
  href=3D"tel:+19739525050">(973) 952-5050</A><BR><A=20
  href=3D"http://www.jdrosen.net">http://www.jdrosen.net</A> PHONE: <A=20
  href=3D"tel:+19739525000">(973) 952-5000</A><BR><A=20
  =
href=3D"http://www.dynamicsoft.com">http://www.dynamicsoft.com</A><BR><BR=
>_______________________________________________<BR>Sipping=20
  mailing list <A=20
  =
href=3D"https://www1.ietf.org/mailman/listinfo/sipping">https://www1.ietf=
.org/mailman/listinfo/sipping</A><BR>This=20
  list is for NEW development of the application of SIP<BR>Use <A=20
  =
href=3D"mailto:sip-implementors@cs.columbia.edu">sip-implementors@cs.colu=
mbia.edu</A>=20
  for questions on current sip Use <A=20
  href=3D"mailto:sip@ietf.org">sip@ietf.org</A> for new developments of =
core=20
  SIP<BR></BLOCKQUOTE></TT></BODY></HTML>

------=_NextPart_000_0001_01C2EC83.8501E500--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 17:28:39 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04912
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 17:28:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HMjEC10249
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 17:45:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HMjEO10246
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 17:45:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04897
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 17:28:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HMiSO10214;
	Mon, 17 Mar 2003 17:44:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HMhWO10165
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 17:43:32 -0500
Received: from mail.aastra.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04864
	for <sipping@ietf.org>; Mon, 17 Mar 2003 17:26:26 -0500 (EST)
Received: by mail.aastra.com with Internet Mail Service (5.5.2653.19)
	id <1XVB0V1Q>; Mon, 17 Mar 2003 17:17:49 -0500
Message-ID: <F924CEFBBF62D611A0C600D0B76ED037157988@cvxmail.ana.aastra.com>
From: Sumit Garg <sgarg@aastra.com>
To: "Peterson, Jon" <jon.peterson@neustar.biz>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Mon, 17 Mar 2003 17:17:40 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C2ECD3.06384200"
Subject: [Sipping] RFC3398: Section 11.1 Reset messages
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_000_01C2ECD3.06384200
Content-Type: text/plain;
	charset="iso-8859-1"

Hi all,
Section 11.1 of RFC3398 says:
"
11.1 Reset messages

   Upon reception of an RSC message for a circuit currently being used
   by the gateway for a call, the call MUST be released immediately
   (this typically results from a serious maintenance condition).  RSC
   MUST be answered with an RLC after resetting the circuit in the
   gateway.  Group reset (GRS) messages which target a range of circuits
   are answered with a Circuit Group Reset ACK Message (GRA) after
   resetting all the circuits affected by the message.

   The gateways SHOULD behave as if a REL had been received in order to
   release the dialog on the SIP side.  A BYE or a CANCEL are sent
   depending of the status of the call.  See the procedures in Section
   10."

I have some confusion regarding the second paragraph.
Shouldn't it have just the first line.
The second line of the paragraph is incomplete and misleading.
It does not take into consideration the RSC on a circuit for
a Net to Phone call case before the call has been setup.

I think it should say "A BYE, CANCEL or Final Response (say 5xx) are sent
   depending of the status of the call."

-Sumit

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Sumit Garg 
Aastra Telecom US
8 Federal Street 
Billerica, MA 01821 
978-436-4244
email: <<mailto:sgarg@aastra.com>> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
 <<Sumit Garg.vcf>> 

------_=_NextPart_000_01C2ECD3.06384200
Content-Type: application/octet-stream;
	name="Sumit Garg.vcf"
Content-Disposition: attachment;
	filename="Sumit Garg.vcf"

BEGIN:VCARD
VERSION:2.1
N:Garg;Sumit
FN:Sumit Garg
ORG:Aastra Network Access
NOTE:Aastra CVX
TEL;WORK;VOICE:978-436-4244
ADR;WORK:;Boston;8 Federal Street;Billerica;MA;1821;USA
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Boston=0D=0A8 Federal Street=0D=0ABillerica, MA 1821=0D=0AUSA
EMAIL;PREF;INTERNET:sgarg@aastra.com
REV:20021122T160021Z
END:VCARD

------_=_NextPart_000_01C2ECD3.06384200--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 17:46:54 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05438
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 17:46:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HN3Sa11101
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 18:03:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HN3SO11098
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 18:03:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05399
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 17:46:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HN2TO11030;
	Mon, 17 Mar 2003 18:02:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HMxTO10796
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 17:59:29 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05243
	for <sipping@ietf.org>; Mon, 17 Mar 2003 17:42:23 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z06FRZ>; Mon, 17 Mar 2003 17:42:43 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410D995BF7@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        sipping
	 <sipping@ietf.org>
Cc: Dean Willis <dean.willis@softarmor.com>, Rohan Mahy <rohan@cisco.com>
Subject: RE: [Sipping] Final agenda
Date: Mon, 17 Mar 2003 17:40:47 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This is a very unfortunate change.  

I know at least one person who specifically scheduled his plans on the basis
that  
2150 Considerations on the IPREP Requirements, Jon Peterson 
   draft-peterson-sipping-ieprep-00.txt 
would be held on Wednesday, after the ieprep session.   

Now it has been changed to tonight. As he is juggling this conference with
the CTIA conference, it is too late to change his plans.

I expect there are others who are interested in the ieprep issues who also
made their plans on the basis of the previously published agenda, putting it
on the same day as ieprep.

I hope there is a way to change the agenda, so that the people who are most
interested in this document will be able to attend.

-----Original Message-----
From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
Sent: Monday, March 17, 2003 12:38 PM
To: sipping
Cc: Dean Willis; Rohan Mahy
Subject: [Sipping] Final agenda


Folks,

this is the final SIPPING agenda. We have re-shuffled some slots and
added a last minute request.

http://www.softarmor.com/sipping/meets/ietf56/agenda.html

Regards,

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 18:25:16 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07702
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 18:25:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HNfqp14584
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 18:41:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HNfpO14581
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 18:41:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07692
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 18:24:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HNfFO14556;
	Mon, 17 Mar 2003 18:41:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HNePO14487
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 18:40:25 -0500
Received: from NREXCH.netrake.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07624
	for <sipping@ietf.org>; Mon, 17 Mar 2003 18:23:18 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Date: Mon, 17 Mar 2003 17:26:16 -0600
Message-ID: <7E06D3212981524CA10D2A114937C41401357205@nrexch.netrake.net>
Thread-Topic: b2bua description
Thread-Index: AcLs3Jt2M74rdDLXQGOUGacHNc9Tgg==
From: "Jasson Casey" <jasson@netrake.com>
To: <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h2HNePO14488
Subject: [Sipping] b2bua description
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Its seems the concept of a B2BUA has been discussed a bit on the list; however, is anyone working on putting thoughts to paper? It seems that there are several scenarios where having a more detailed description of use would be benificial concerning this topic.
 
thanks,
 
-jasson
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 18:43:35 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08372
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 18:43:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2I00Br15524
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 19:00:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I00BO15521
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 19:00:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08361
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 18:43:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HNxTO15429;
	Mon, 17 Mar 2003 18:59:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HNwOO15340
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 18:58:24 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08295
	for <sipping@ietf.org>; Mon, 17 Mar 2003 18:41:16 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2HNhLwv015581;
	Tue, 18 Mar 2003 00:43:21 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id GPH7FTCD; Tue, 18 Mar 2003 00:43:21 +0100
Received: from lmf.ericsson.se (vrrch2-177148.am.ericsson.se [138.85.177.148])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2HNhJ6B028688;
	Tue, 18 Mar 2003 01:43:20 +0200 (EET)
Message-ID: <3E765DAC.234ECF63@lmf.ericsson.se>
Date: Tue, 18 Mar 2003 01:43:40 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
CC: sipping <sipping@ietf.org>, Dean Willis <dean.willis@softarmor.com>,
        Rohan Mahy <rohan@cisco.com>
Subject: Re: [Sipping] Final agenda
References: <CBED705A7FD2D311865500508B1089410D995BF7@chntex02.is.dyncorp.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Fixed. The IPREP presentation will be given on Wednesday, as originally
planned.

Thanks for the note.

Gonzalo

"Gunn, Janet" wrote:
> 
> This is a very unfortunate change.
> 
> I know at least one person who specifically scheduled his plans on the basis
> that
> 2150 Considerations on the IPREP Requirements, Jon Peterson
>    draft-peterson-sipping-ieprep-00.txt
> would be held on Wednesday, after the ieprep session.
> 
> Now it has been changed to tonight. As he is juggling this conference with
> the CTIA conference, it is too late to change his plans.
> 
> I expect there are others who are interested in the ieprep issues who also
> made their plans on the basis of the previously published agenda, putting it
> on the same day as ieprep.
> 
> I hope there is a way to change the agenda, so that the people who are most
> interested in this document will be able to attend.
> 
> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: Monday, March 17, 2003 12:38 PM
> To: sipping
> Cc: Dean Willis; Rohan Mahy
> Subject: [Sipping] Final agenda
> 
> Folks,
> 
> this is the final SIPPING agenda. We have re-shuffled some slots and
> added a last minute request.
> 
> http://www.softarmor.com/sipping/meets/ietf56/agenda.html
> 
> Regards,
> 
> Gonzalo
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 17 19:01:24 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09009
	for <sipping-archive@odin.ietf.org>; Mon, 17 Mar 2003 19:01:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2I0I0V17341
	for sipping-archive@odin.ietf.org; Mon, 17 Mar 2003 19:18:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I0I0O17338
	for <sipping-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 19:18:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08961
	for <sipping-web-archive@ietf.org>; Mon, 17 Mar 2003 19:00:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I0HHO17306;
	Mon, 17 Mar 2003 19:17:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I0GYO17249
	for <sipping@optimus.ietf.org>; Mon, 17 Mar 2003 19:16:34 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08906
	for <sipping@ietf.org>; Mon, 17 Mar 2003 18:59:26 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z06F4W>; Mon, 17 Mar 2003 18:59:47 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410D995BFB@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: sipping <sipping@ietf.org>, Dean Willis <dean.willis@softarmor.com>,
        Rohan Mahy <rohan@cisco.com>
Subject: RE: [Sipping] Final agenda
Date: Mon, 17 Mar 2003 18:57:57 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Thanks

-----Original Message-----
From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
Sent: Monday, March 17, 2003 6:44 PM
To: Gunn, Janet
Cc: sipping; Dean Willis; Rohan Mahy
Subject: Re: [Sipping] Final agenda


Fixed. The IPREP presentation will be given on Wednesday, as originally
planned.

Thanks for the note.

Gonzalo

"Gunn, Janet" wrote:
> 
> This is a very unfortunate change.
> 
> I know at least one person who specifically scheduled his plans on the
basis
> that
> 2150 Considerations on the IPREP Requirements, Jon Peterson
>    draft-peterson-sipping-ieprep-00.txt
> would be held on Wednesday, after the ieprep session.
> 
> Now it has been changed to tonight. As he is juggling this conference with
> the CTIA conference, it is too late to change his plans.
> 
> I expect there are others who are interested in the ieprep issues who also
> made their plans on the basis of the previously published agenda, putting
it
> on the same day as ieprep.
> 
> I hope there is a way to change the agenda, so that the people who are
most
> interested in this document will be able to attend.
> 
> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: Monday, March 17, 2003 12:38 PM
> To: sipping
> Cc: Dean Willis; Rohan Mahy
> Subject: [Sipping] Final agenda
> 
> Folks,
> 
> this is the final SIPPING agenda. We have re-shuffled some slots and
> added a last minute request.
> 
> http://www.softarmor.com/sipping/meets/ietf56/agenda.html
> 
> Regards,
> 
> Gonzalo
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 18 02:52:22 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03735
	for <sipping-archive@odin.ietf.org>; Tue, 18 Mar 2003 02:52:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2I899S27552
	for sipping-archive@odin.ietf.org; Tue, 18 Mar 2003 03:09:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I899O27549
	for <sipping-web-archive@optimus.ietf.org>; Tue, 18 Mar 2003 03:09:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03730
	for <sipping-web-archive@ietf.org>; Tue, 18 Mar 2003 02:51:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I88OO27517;
	Tue, 18 Mar 2003 03:08:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I86tO26703
	for <sipping@optimus.ietf.org>; Tue, 18 Mar 2003 03:06:55 -0500
Received: from smail3.alcatel.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03702
	for <sipping@ietf.org>; Tue, 18 Mar 2003 02:49:37 -0500 (EST)
From: Juan-Carlos.Rojas@alcatel.fr
Received: from frmail25.netfr.alcatel.fr (frmail25.netfr.alcatel.fr [155.132.182.155])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id h2I7poqj032528;
	Tue, 18 Mar 2003 08:51:50 +0100
Subject: Re: [Sipping] b2bua description
To: "Jasson Casey" <jasson@netrake.com>
Cc: <sipping@ietf.org>
Date: Tue, 18 Mar 2003 08:51:48 +0100
Message-ID: <OFA80D744B.AFD57070-ONC1256CED.002AFFC0@netfr.alcatel.fr>
X-MIMETrack: Serialize by Router on FRMAIL25/FR/ALCATEL(Release 5.0.11  |July 24, 2002) at
 03/18/2003 08:51:50
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Virus-Scanned: by amavisd-new
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Hi,
I don't know if anybody is writing something; moreover, I do not know what
was (more or less) the result of the previous debate.
What is sure is that the debate showed that there is a lot of confusion
about this subject.
Best regards
Juan Carlos





"Jasson Casey" <jasson@netrake.com>@ietf.org on 03/18/2003 12:26:16 AM

Sent by:    sipping-admin@ietf.org


To:    <sipping@ietf.org>
cc:
Subject:    [Sipping] b2bua description


Its seems the concept of a B2BUA has been discussed a bit on the list;
however, is anyone working on putting thoughts to paper? It seems that
there are several scenarios where having a more detailed description of use
would be benificial concerning this topic.

thanks,

-jasson
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
 Use sip@ietf.org for new developments of core SIP




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 18 16:52:51 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02019
	for <sipping-archive@odin.ietf.org>; Tue, 18 Mar 2003 16:52:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2IM9tW24003
	for sipping-archive@odin.ietf.org; Tue, 18 Mar 2003 17:09:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2IM9tO24000
	for <sipping-web-archive@optimus.ietf.org>; Tue, 18 Mar 2003 17:09:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02016
	for <sipping-web-archive@ietf.org>; Tue, 18 Mar 2003 16:52:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2IM94O23965;
	Tue, 18 Mar 2003 17:09:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2IM6UO23104
	for <sipping@optimus.ietf.org>; Tue, 18 Mar 2003 17:06:30 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01901
	for <sipping@ietf.org>; Tue, 18 Mar 2003 16:48:54 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2ILp5HQ013207;
	Tue, 18 Mar 2003 22:51:05 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id GPHLCWX7; Tue, 18 Mar 2003 22:50:58 +0100
Received: from lmf.ericsson.se (vrrch1-177055.am.ericsson.se [138.85.177.55])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2ILou6B009244;
	Tue, 18 Mar 2003 23:50:57 +0200 (EET)
Message-ID: <3E77951B.A5FA06C2@lmf.ericsson.se>
Date: Tue, 18 Mar 2003 23:52:27 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] New version of netann
References: <4A3384433CE2AB46A63468CB207E209D2488D9@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi Eric,

> >>>Well, you could define the play's as SDP attributes.
> >>>Something like:
> >>>
> >>>m=audio...
> >>>a=play:"http://audio.example.net/allcircuitsbusy.g711";
> >>>m=video...
> >>>a=play:"http://video.example.net/allcircuitsbusy.mpeg4";
> >>>
> >>>I don't know if this would work (I haven't had time to
> >>>think so much about it) the way you've planned, though.
> >>
> >>It might work, except error handling would be horrific.  A
> >>fetch error would have to be reported as an SDP error, for example.
> >
> >Well, you could return 200 OK with an SDP, with the port set
> >to zero for the specific stream. That's how we do it in
> >"normal" SIP calls, so... Or, you could send 415 Unsupported
> >Media Type.
>
> The problem is, is the 415 because the fetch failed or because I don't support G.mumble?  Yes, one might be able to work it out from the parameters given in the 415, but that sounds like a lot of machinery.

[CHH] Well, 200 OK (or a reliable 18x provisional response) with the port set to zero for streams not accepted, is another option. Then, the client can make a decission if it wants to continue with the announcement or not.

> >>>But, if we need multiple INVITEs, would it be possible to associate
> >>>them? We would have to use different call identifiers etc
> >>>(I hope you wouldn't want to use something similar to overlapping for this :)
> >>
> >>Is this a real issue?
> >
> >What? Being able to associate the INVITEs, or having to send
> >multiple INVITEs? At least regarding the issue of multiple
> >INVITEs, I think multimedia streams (including eg audio AND
> >video) IS a real issue...
>
> The unfortunate thing is, I think I agree with you.  Does anyone have a thought on how to do this?  My initial thinking is I don't want the URI to play in the SDP, because that is a signaling thing, not a media thing.

[CHH] These specific URIs defines "media objects", and not a location (like the Request-URI), so one could argue they are related to the media.

Regards,

Christer Holmberg
Ericsson Finland


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 18 18:18:17 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05712
	for <sipping-archive@odin.ietf.org>; Tue, 18 Mar 2003 18:18:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2INZLJ29249
	for sipping-archive@odin.ietf.org; Tue, 18 Mar 2003 18:35:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2INZLO29246
	for <sipping-web-archive@optimus.ietf.org>; Tue, 18 Mar 2003 18:35:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05702
	for <sipping-web-archive@ietf.org>; Tue, 18 Mar 2003 18:17:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2INYXO29205;
	Tue, 18 Mar 2003 18:34:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2INXBO29172
	for <sipping@optimus.ietf.org>; Tue, 18 Mar 2003 18:33:11 -0500
Received: from elmer.LEAPSTONE.COM (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05493
	for <sipping@ietf.org>; Tue, 18 Mar 2003 18:15:36 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Date: Tue, 18 Mar 2003 18:18:42 -0500
Message-ID: <59A835EDCDDBEB46BC75402F4604D5520107AA16@elmer>
Thread-Topic: Use of NOTIFY in KPML (was [SIPPING] Comments on updated KPML draft)
Thread-Index: AcLqhtMLN/g1PNvxTja/iASXKHJSDwDHFGbm
From: "Dusan Mudric" <dmudric@LEAPSTONE.com>
To: <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h2INXBO29173
Subject: [Sipping] event types for SUBSCRIBE and NOTIFY
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hello,
 
Are there standard event types defied for SUBSCRIBE and NOTIFY? Can you give me pointers please?
 
Dusan Mudric
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 18 19:44:09 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09133
	for <sipping-archive@odin.ietf.org>; Tue, 18 Mar 2003 19:44:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2J11Fh03023
	for sipping-archive@odin.ietf.org; Tue, 18 Mar 2003 20:01:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J11FO03020
	for <sipping-web-archive@optimus.ietf.org>; Tue, 18 Mar 2003 20:01:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09049
	for <sipping-web-archive@ietf.org>; Tue, 18 Mar 2003 19:43:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J10RO02918;
	Tue, 18 Mar 2003 20:00:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J0xaO02855
	for <sipping@optimus.ietf.org>; Tue, 18 Mar 2003 19:59:36 -0500
Received: from mail4.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08932
	for <sipping@ietf.org>; Tue, 18 Mar 2003 19:41:57 -0500 (EST)
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h2J0i7Yk007376;
	Tue, 18 Mar 2003 19:44:07 -0500 (EST)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <G9J73LHH>; Tue, 18 Mar 2003 18:44:11 -0600
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3A645AF@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Dusan Mudric'" <dmudric@leapstone.com>, sipping@ietf.org
Subject: RE: [Sipping] event types for SUBSCRIBE and NOTIFY
Date: Tue, 18 Mar 2003 18:44:10 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="utf-8"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

The IANA registry for defined event types is at:

http://www.iana.org/assignments/sip-events

/a

> -----Original Message-----
> From: Dusan Mudric [mailto:dmudric@leapstone.com]
> Sent: Tuesday, March 18, 2003 17:19
> To: sipping@ietf.org
> Subject: [Sipping] event types for SUBSCRIBE and NOTIFY
> 
> 
> Hello,
>  
> Are there standard event types defied for SUBSCRIBE and 
> NOTIFY? Can you give me pointers please?
>  
> Dusan Mudric
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 18 22:30:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14016
	for <sipping-archive@odin.ietf.org>; Tue, 18 Mar 2003 22:30:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2J3lba14618
	for sipping-archive@odin.ietf.org; Tue, 18 Mar 2003 22:47:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J3lbO14615
	for <sipping-web-archive@optimus.ietf.org>; Tue, 18 Mar 2003 22:47:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14006
	for <sipping-web-archive@ietf.org>; Tue, 18 Mar 2003 22:29:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J3kkO14586;
	Tue, 18 Mar 2003 22:46:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J3jXO14538
	for <sipping@optimus.ietf.org>; Tue, 18 Mar 2003 22:45:33 -0500
Received: from mgw-x1.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13981
	for <sipping@ietf.org>; Tue, 18 Mar 2003 22:27:50 -0500 (EST)
From: aki.niemi@nokia.com
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.5/Switch-2.2.5) with ESMTP id h2J3SdM10048
	for <sipping@ietf.org>; Wed, 19 Mar 2003 05:28:39 +0200 (EET)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T61112a2b33ac158f252d7@esvir05nok.ntc.nokia.com>;
 Wed, 19 Mar 2003 05:30:03 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 19 Mar 2003 05:30:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] FW: I-D ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
Date: Wed, 19 Mar 2003 05:30:01 +0200
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD9019451C4@esebe013.ntc.nokia.com>
Thread-Topic: I-D ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
Thread-Index: AcLfLVPlThjUZlAdR7OM1beSFv771QIAFGAwAaYMZSA=
To: <Hakan.N.Persson@telia.se>, <sipping@ietf.org>
X-OriginalArrivalTime: 19 Mar 2003 03:30:02.0722 (UTC) FILETIME=[D3C8C420:01C2EDC7]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2J3jXO14539
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

A couple of comments to the draft.

First, it seems to omit record-routing. A dual-stack proxy really only provides for IPv6/IPv4 transition if it record-routes and thus assures that all requests after the initial INVITE also transition using the same dual-stack proxy. A dual-stack proxy that record-routes will make sure that the two endpoints never end up with contacts of different IP-versions and thus no way of communicating directly.

Secondly, none of this helps with transitioning of media. That's actually a lot bigger problem.

There are a couple of documents that discuss some transition scenarios for SIP in v6ops:
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-3gpp-cases-02.txt
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-3gpp-analysis-02.txt

Cheers,
Aki
 

 > -----Original Message-----
 > From: ext Hakan.N.Persson@telia.se [mailto:Hakan.N.Persson@telia.se]
 > Sent: 10 March, 2003 20:34
 > To: sipping@ietf.org
 > Subject: [Sipping] FW: I-D
 > ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
 > 
 > 
 > Hi all,
 > 
 > I forward this Internet-draft to the sipping list.
 > It discusses some issues regarding IPv4/IPv6 deployment and 
 > SIP interoperability.
 > Any comments?
 > 
 > Best regards,
 > Håkan Persson
 > 
 > -----Original Message-----
 > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
 > Sent: den 28 februari 2003 13:26
 > Subject: I-D 
 > ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
 > 
 > 
 > A New Internet-Draft is available from the on-line 
 > Internet-Drafts directories.
 > 
 > 
 > 	Title		: SIP Issues in Dual-stack Environments
 > 	Author(s)	: J. Mulahusic, H. Persson
 > 	Filename	: 
 > draft-persson-sipping-sip-issues-dual-stack-00.txt
 > 	Pages		: 9
 > 	Date		: 2003-2-27
 > 	
 > The advent of IPv6 in addition to IPv4 makes hosts and servers dual-
 > stack. SIP communications can be used in both environments but there 
 > is little understanding what will happen if some nodes are 
 > dual-stack 
 > while others, presently the majority, is IPv4 only enabled. This 
 > document describes some scenarios and associated issues when dual-
 > stack users and servers try to communicate with IPv4 only 
 > hosts using 
 > SIP. It is not evident that interoperability is achieved, 
 > and if that 
 > is not the case, this would severely limit the usability of both SIP 
 > and IPv6.
 > 
 > A URL for this Internet-Draft is:
 > http://www.ietf.org/internet-drafts/draft-persson-sipping-sip
-issues-dual-stack-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-persson-sipping-sip-issues-dual-stack-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-persson-sipping-sip-issues-dual-stack-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.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 19 08:20:06 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20400
	for <sipping-archive@odin.ietf.org>; Wed, 19 Mar 2003 08:20:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2JDbRJ28734
	for sipping-archive@odin.ietf.org; Wed, 19 Mar 2003 08:37:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JDbRO28731
	for <sipping-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 08:37:27 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20397
	for <sipping-web-archive@ietf.org>; Wed, 19 Mar 2003 08:19:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JDaDO27925;
	Wed, 19 Mar 2003 08:36:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JDYDO27845
	for <sipping@optimus.ietf.org>; Wed, 19 Mar 2003 08:34:13 -0500
Received: from mail3.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20293
	for <sipping@ietf.org>; Wed, 19 Mar 2003 08:15:00 -0500 (EST)
Received: from dynamicsoft.com (dyn-tx-app-004.dfw.dynamicsoft.com [63.110.3.2])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h2J5DOBd000819;
	Wed, 19 Mar 2003 00:14:40 -0500 (EST)
Message-ID: <3E77FC6C.3070602@dynamicsoft.com>
Date: Wed, 19 Mar 2003 00:13:16 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Juan-Carlos.Rojas@alcatel.fr
CC: Jasson Casey <jasson@netrake.com>, sipping@ietf.org
Subject: Re: [Sipping] b2bua description
References: <OFA80D744B.AFD57070-ONC1256CED.002AFFC0@netfr.alcatel.fr>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

As I recall, the conclusion was that there is not much value in 
describing a b2bua for the sake of a b2bua. Rather, the use was in 
describing specific problems for which a b2bua was posited as a 
solution, and show what one would do in such a scenario.

-Jonathan R.

Juan-Carlos.Rojas@alcatel.fr wrote:
> Hi,
> I don't know if anybody is writing something; moreover, I do not know what
> was (more or less) the result of the previous debate.
> What is sure is that the debate showed that there is a lot of confusion
> about this subject.
> Best regards
> Juan Carlos
> 
> 
> 
> 
> 
> "Jasson Casey" <jasson@netrake.com>@ietf.org on 03/18/2003 12:26:16 AM
> 
> Sent by:    sipping-admin@ietf.org
> 
> 
> To:    <sipping@ietf.org>
> cc:
> Subject:    [Sipping] b2bua description
> 
> 
> Its seems the concept of a B2BUA has been discussed a bit on the list;
> however, is anyone working on putting thoughts to paper? It seems that
> there are several scenarios where having a more detailed description of use
> would be benificial concerning this topic.
> 
> thanks,
> 
> -jasson
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
>  Use sip@ietf.org for new developments of core SIP
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 19 15:58:43 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07615
	for <sipping-archive@odin.ietf.org>; Wed, 19 Mar 2003 15:58:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2JLGDX04248
	for sipping-archive@odin.ietf.org; Wed, 19 Mar 2003 16:16:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JLGDO04245
	for <sipping-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 16:16:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07579
	for <sipping-web-archive@ietf.org>; Wed, 19 Mar 2003 15:58:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JLFVO04138;
	Wed, 19 Mar 2003 16:15:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JLCdO03976
	for <sipping@optimus.ietf.org>; Wed, 19 Mar 2003 16:12:39 -0500
Received: from dyn-tx-arch-crash.dfw.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07473;
	Wed, 19 Mar 2003 15:54:36 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id h2JKuo924748;
	Wed, 19 Mar 2003 14:56:50 -0600
From: Robert Sparks <rsparks@dynamicsoft.com>
Reply-To: sip@ietf.org
To: sip@ietf.org, simple@ietf.org, sipping@ietf.org
Content-Type: text/plain
Message-Id: <1048107377.1063.49.camel@RjS.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 19 Mar 2003 12:56:18 -0800
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] [Fwd: RE: SIP WG bugzilla instance]
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

All -

I apologize now for violating the no-crosspost policy, but
this spans all the groups. Please, please, reply _ONLY_ to
sip@ietf.org (which is what should happen if you hit your
reply button if I've built this message correctly).

If you have any opinions, positive or negative, about our
use of bugzilla for issue tracking and whether other groups
should follow the model, now would be a good time to comment.

Thanks!

RjS

-----Forwarded Message-----

> From: john.loughney@nokia.com
> To: rsparks@dynamicsoft.com, wgchairs@ietf.org
> Subject: RE: SIP WG bugzilla instance
> Date: 19 Mar 2003 22:46:52 +0200
> 
> Robert,
> 
> Any comments on how the WG & WG Chairs like it?
> 
> John
> 
> > At the session on improving working group chair training
> > (and chair effectiveness), tools came up. The SIP related
> > working groups have been effectively using a bugzilla variant
> > to track document issues and help drive open issues to
> > conclusion.
> > 
> > It's available at http://www.sipwg.org (or http://bugs.sipit.net).
> > 
> > One point to bring forth at the beginning - we use this as
> > a tracking tool, not an alternative venue for list discussion.
> > Document/issue owners are able to make changes to a bug -
> > people ask the owner to add things to the tracking tool on
> > the appropriate list. The chairs make sure that the owners
> > accurately capture threads on the tracking tool.
> > 
> > RjS
> > 
> > 
> > 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 19 16:42:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10550
	for <sipping-archive@odin.ietf.org>; Wed, 19 Mar 2003 16:42:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2JLxxp09351
	for sipping-archive@odin.ietf.org; Wed, 19 Mar 2003 16:59:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JLxwO09348
	for <sipping-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 16:59:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10418
	for <sipping-web-archive@ietf.org>; Wed, 19 Mar 2003 16:41:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JLx8O09314;
	Wed, 19 Mar 2003 16:59:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JLwQO09263
	for <sipping@optimus.ietf.org>; Wed, 19 Mar 2003 16:58:26 -0500
Received: from mail3.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10373
	for <sipping@ietf.org>; Wed, 19 Mar 2003 16:40:21 -0500 (EST)
Received: from dynamicsoft.com (dyn-tx-app-004.dfw.dynamicsoft.com [63.110.3.2])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h2JLfqBd001509;
	Wed, 19 Mar 2003 16:42:37 -0500 (EST)
Message-ID: <3E78E41B.7050407@dynamicsoft.com>
Date: Wed, 19 Mar 2003 16:41:47 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: aki.niemi@nokia.com
CC: Hakan.N.Persson@telia.se, sipping@ietf.org
Subject: Re: [Sipping] FW: I-D ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
References: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD9019451C4@esebe013.ntc.nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

I have the same comment as Aki.

In the sip space, this is the same problem as tcp/udp conversion, 
sip/sips and so on. In all cases, we are using record routing, with 
differeing URIs on each side, as a means to solve it. I believe that 
will work here.

Now, as Aki says, the harder problem is the media. Alas, I have a 
solution for that. It is ICE:

http://www.ietf.org/internet-drafts/draft-rosenberg-sipping-ice-00.txt

With ICE, a dual stack host would put both its IPv4 and IPv6 addresses 
in the SDP, using the ALT SDP mechanism:

http://www.ietf.org/internet-drafts/draft-camarillo-mmusic-alt-00.txt

Now, this reaches the UAS. According to the ICE draft, the UAS will use 
STUN to verify connectivity over those addresses it can reach. So, if 
its v4 only, it would verify connectivity to v4, and in its answer, list 
its v4 address only. The caller would verify its connectivity to that v4 
address, and then communications take place.

ICE, as written, explicitly prefers v6 addresses over v4. The result is 
that ICE will end up using v6 when both ends are dual stack and both are 
connected to a global v6 network. If, for some reason, both ends are v6 
but the v6 networks are not connected,  ICE will fall back to a global 
v4 address.

I believe ICE will also work with a 6to4 nat, although I have to work 
through the flows to be sure.

I mentioned ICE as being useful for v6 transition during sipping. I 
encourage folks who are interested in this problem to take a look at the 
draft.

Thanks,
Jonathan R.

aki.niemi@nokia.com wrote:
> Hi,
> 
> A couple of comments to the draft.
> 
> First, it seems to omit record-routing. A dual-stack proxy really only provides for IPv6/IPv4 transition if it record-routes and thus assures that all requests after the initial INVITE also transition using the same dual-stack proxy. A dual-stack proxy that record-routes will make sure that the two endpoints never end up with contacts of different IP-versions and thus no way of communicating directly.
> 
> Secondly, none of this helps with transitioning of media. That's actually a lot bigger problem.
> 
> There are a couple of documents that discuss some transition scenarios for SIP in v6ops:
> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-3gpp-cases-02.txt
> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-3gpp-analysis-02.txt
> 
> Cheers,
> Aki
>  
> 
>  > -----Original Message-----
>  > From: ext Hakan.N.Persson@telia.se [mailto:Hakan.N.Persson@telia.se]
>  > Sent: 10 March, 2003 20:34
>  > To: sipping@ietf.org
>  > Subject: [Sipping] FW: I-D
>  > ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
>  > 
>  > 
>  > Hi all,
>  > 
>  > I forward this Internet-draft to the sipping list.
>  > It discusses some issues regarding IPv4/IPv6 deployment and 
>  > SIP interoperability.
>  > Any comments?
>  > 
>  > Best regards,
>  > Håkan Persson
>  > 
>  > -----Original Message-----
>  > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>  > Sent: den 28 februari 2003 13:26
>  > Subject: I-D 
>  > ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
>  > 
>  > 
>  > A New Internet-Draft is available from the on-line 
>  > Internet-Drafts directories.
>  > 
>  > 
>  > 	Title		: SIP Issues in Dual-stack Environments
>  > 	Author(s)	: J. Mulahusic, H. Persson
>  > 	Filename	: 
>  > draft-persson-sipping-sip-issues-dual-stack-00.txt
>  > 	Pages		: 9
>  > 	Date		: 2003-2-27
>  > 	
>  > The advent of IPv6 in addition to IPv4 makes hosts and servers dual-
>  > stack. SIP communications can be used in both environments but there 
>  > is little understanding what will happen if some nodes are 
>  > dual-stack 
>  > while others, presently the majority, is IPv4 only enabled. This 
>  > document describes some scenarios and associated issues when dual-
>  > stack users and servers try to communicate with IPv4 only 
>  > hosts using 
>  > SIP. It is not evident that interoperability is achieved, 
>  > and if that 
>  > is not the case, this would severely limit the usability of both SIP 
>  > and IPv6.
>  > 
>  > A URL for this Internet-Draft is:
>  > http://www.ietf.org/internet-drafts/draft-persson-sipping-sip
> -issues-dual-stack-00.txt
> 
> To remove yourself from the IETF Announcement list, send a message to 
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> 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-persson-sipping-sip-issues-dual-stack-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-persson-sipping-sip-issues-dual-stack-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.
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 19 18:18:25 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15262
	for <sipping-archive@odin.ietf.org>; Wed, 19 Mar 2003 18:18:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2JNa0117688
	for sipping-archive@odin.ietf.org; Wed, 19 Mar 2003 18:36:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JNa0O17685
	for <sipping-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 18:36:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15238
	for <sipping-web-archive@ietf.org>; Wed, 19 Mar 2003 18:17:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JNZGO17665;
	Wed, 19 Mar 2003 18:35:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JNYWO17603
	for <sipping@optimus.ietf.org>; Wed, 19 Mar 2003 18:34:32 -0500
Received: from tms002bb.han.telia.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15185
	for <sipping@ietf.org>; Wed, 19 Mar 2003 18:16:25 -0500 (EST)
From: Jasminko.W.Mulahusic@telia.se
Received: from tms031mb.han.telia.se ([131.115.230.162]) by tms002bb.han.telia.se with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 20 Mar 2003 00:18:40 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6318.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] FW: I-D ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
Date: Thu, 20 Mar 2003 00:18:40 +0100
Message-ID: <7B64D9FB62EB42449683BA51E9AB2AE807E169@TMS031MB.tcad.telia.se>
Thread-Topic: [Sipping] FW: I-D ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
Thread-Index: AcLuYOXq0FyswM1OQnqsY3ECF9vzQwABb+sg
To: <jdrosen@dynamicsoft.com>, <aki.niemi@nokia.com>
Cc: <Hakan.N.Persson@telia.se>, <sipping@ietf.org>
X-OriginalArrivalTime: 19 Mar 2003 23:18:40.0859 (UTC) FILETIME=[E0B4DAB0:01C2EE6D]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2JNYWO17604
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



> -----Original Message-----
> From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com] 
> Sent: den 19 mars 2003 22:42
> 
> I have the same comment as Aki.
> 
> In the sip space, this is the same problem as tcp/udp conversion, 
> sip/sips and so on. In all cases, we are using record routing, with 
> differeing URIs on each side, as a means to solve it. I believe that 
> will work here.
> 
> Now, as Aki says, the harder problem is the media. Alas, I have a 
> solution for that. It is ICE:
> 
> http://www.ietf.org/internet-drafts/draft-rosenberg-sipping-ice-00.txt
> 
> With ICE, a dual stack host would put both its IPv4 and IPv6 

ok. that seems to be solving problem with sdp.

but, who (which proxy) is going to rewrite/change the contact-header field in the initial INVITE?

thanx
jasminko
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 19 19:04:43 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16859
	for <sipping-archive@odin.ietf.org>; Wed, 19 Mar 2003 19:04:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2K0MKG21799
	for sipping-archive@odin.ietf.org; Wed, 19 Mar 2003 19:22:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K0MKO21796
	for <sipping-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 19:22:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16825
	for <sipping-web-archive@ietf.org>; Wed, 19 Mar 2003 19:04:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K0LaO21763;
	Wed, 19 Mar 2003 19:21:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K0KSO21693
	for <sipping@optimus.ietf.org>; Wed, 19 Mar 2003 19:20:28 -0500
Received: from mail3.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16758
	for <sipping@ietf.org>; Wed, 19 Mar 2003 19:02:21 -0500 (EST)
Received: from dynamicsoft.com (dyn-tx-app-004.dfw.dynamicsoft.com [63.110.3.2])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h2K04dBd001678;
	Wed, 19 Mar 2003 19:04:40 -0500 (EST)
Message-ID: <3E790593.6050803@dynamicsoft.com>
Date: Wed, 19 Mar 2003 19:04:35 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jasminko.W.Mulahusic@telia.se
CC: aki.niemi@nokia.com, Hakan.N.Persson@telia.se, sipping@ietf.org
Subject: Re: [Sipping] FW: I-D ACTION:draft-persson-sipping-sip-issues-dual-stack-00.txt
References: <7B64D9FB62EB42449683BA51E9AB2AE807E169@TMS031MB.tcad.telia.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The UA sets its contact header. It needs to make sure it is set to use 
the same IP version as the proxy it is sending the request to. This may 
require the proxy to change the contact header after it does the DNS 
resolution, and finding, for example, that there are only AAAA records, 
and no A records.

-Jonathan R.

Jasminko.W.Mulahusic@telia.se wrote:
> 
>>-----Original Message-----
>>From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com] 
>>Sent: den 19 mars 2003 22:42
>>
>>I have the same comment as Aki.
>>
>>In the sip space, this is the same problem as tcp/udp conversion, 
>>sip/sips and so on. In all cases, we are using record routing, with 
>>differeing URIs on each side, as a means to solve it. I believe that 
>>will work here.
>>
>>Now, as Aki says, the harder problem is the media. Alas, I have a 
>>solution for that. It is ICE:
>>
>>http://www.ietf.org/internet-drafts/draft-rosenberg-sipping-ice-00.txt
>>
>>With ICE, a dual stack host would put both its IPv4 and IPv6 
> 
> 
> ok. that seems to be solving problem with sdp.
> 
> but, who (which proxy) is going to rewrite/change the contact-header field in the initial INVITE?
> 
> thanx
> jasminko
> 

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 14:05:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29673
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 14:05:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KJNOO16810
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 14:23:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJNOO16807
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 14:23:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29664
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 14:04:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJMZO16790;
	Thu, 20 Mar 2003 14:22:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJLpO16717
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 14:21:51 -0500
Received: from bdsl.greycouncil.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29611
	for <sipping@ietf.org>; Thu, 20 Mar 2003 14:03:22 -0500 (EST)
Received: from txdwillis (wl-133-122.wireless.ietf56.ietf.org [130.129.133.122])
	(authenticated bits=0)
	by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id h2KJ5X49008218
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <sipping@ietf.org>; Thu, 20 Mar 2003 13:05:36 -0600
From: "Dean Willis" <dean.willis@softarmor.com>
To: <sipping@ietf.org>
Date: Thu, 20 Mar 2003 11:05:20 -0800
Message-ID: <006301c2ef13$a9ab0610$7a858182@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Raw notes from SIPPING meetings posted
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


I have posted the raw notes I received for SIPPING at:

http://www.softarmor.com/sipping/meets/ietf56/notes/


We'll use these to develop the draft minutes.

You may wish to scan and see if there is anything that you're interested in
that may have been misreported or misrepresented.

--
Dean

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 14:41:01 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01530
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 14:41:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KJwxj19658
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 14:58:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJwxO19655
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 14:58:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01480
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 14:40:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJwGO19505;
	Thu, 20 Mar 2003 14:58:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJvsO19402
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 14:57:54 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01424
	for <sipping@ietf.org>; Thu, 20 Mar 2003 14:39:25 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 20 Mar 2003 14:43:50 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D248969@zoe.office.snowshore.com>
Thread-Topic: netann Issue #3: Multiple Media Streams
Thread-Index: AcLu/Yqd/AcfG147RCKjsvw7NYoQyA==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2KJvsO19403
Subject: [Sipping] netann Issue #3: Multiple Media Streams
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Problem: The UAC is a multimedia terminal, and the request is to play multiple simultaneous streams.  How can we do that given that the netann draft only specifies a single play URI?


WHAT THIS PROBLEM IS NOT:
It is not "how do I send multiple streams to a device?"  Standard SDP deals with that.

It is not "how do I negotiate media capabilities of a device?" or "what if the UAC doesn't do video?"  Standard offer/answer deals with that.


Options:

1. Have multiple play= attributes, somehow correlated to m=lines in the SDP, pointing to the appropriate media source.

2. Add a=lines to the SDP associated with the appropriate m=lines, indicating the media to play, like the a:control lines of RTSP.

3. Only allow simplex or compound objects that are described by a single URI.


Discussion:
Option 1 assumes there is a mapping between SDP-layer information and SIP information.  This breaks down pretty quickly if the offer is offering multiple codecs for a given media type.  

Option 2 is asking the proxy to modify the SDP as it passes through the proxy.  This is a direct violation of the RFC3261 proxy rules.

Option 3 means that one could not play media from different sources in a single netann session.


Proposal:
Since a proper mapping of media types to source URI inherently creates multiple sessions (which, by the way, is exactly how RTSP operates), Option 2 is explicitly out of scope for netann.

Option 1 is a non-starter.  One may consider marking the media types with fid's or sid's.  However, the originating UAC is unaware that the request may terminate to a media server.  Thus the UAC has no reason to mark media types in the SDP.

Our proposal is to do Option 3.  If you can fetch a multimedia object from a single URI (as specified in the play= parameter), a multimedia media server will negotiate and map the appropriate media types using implementation dependent rules.  If one wants to play media from different sources, you are welcome to construct a B2BUA that establishes multiple netann (or other) sessions with the appropriate SDP.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 14:41:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01543
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 14:41:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KJx0f19678
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 14:59:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJx0O19675
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 14:59:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01484
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 14:40:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJwAO19464;
	Thu, 20 Mar 2003 14:58:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJvrO19394
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 14:57:53 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01419
	for <sipping@ietf.org>; Thu, 20 Mar 2003 14:39:23 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 20 Mar 2003 14:43:49 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D248967@zoe.office.snowshore.com>
Thread-Topic: netann Open Issue #1: Media on Hold
Thread-Index: AcLu9hAzguKjnHY0QHSdQ8G22MDLUw==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2KJvrO19395
Subject: [Sipping] netann Open Issue #1: Media on Hold
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Problem:
What does the media server do when the UAC issues a 'hold' (see RFC3264)?  The options are:
	Do not send media, but have time move forward;
	Suspend playing media;
	Make a choice based on how the media was put on hold
	Let the UAC signal behavior

Note that hold is not an issue for early media: it is not possible to put early media on hold.  Also note that the semantics for putting a conference leg on hold is already well defined.


For VoiceXML, Dean had an excellent suggestion of throwing an exception: let the application decide what to do.  However, it will take about a year to standardize that behavior through the W3C.

There were rumblings of not specifying behavior for announcements.  I really don't want to do that because that approach will create different user experiences for the same activity, based on implementation.

An issue with suspending media is it is possible to have a session on hold indefinitely, whereas most announcements are bounded in time.  For example, an announcement could have duration=30000, which would normally disconnect the session after 30 seconds.

Letting the UAC signal behavior is unrealistic as the UAC probably does not know that it is calling a media server.



Here is the updated proposal:

Dialog service: Implementation dependent; suggest throwing an exception.
Announcement service: Suspend playout; implementation dependent timeout (if any) after which media server sends a BYE.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 14:41:03 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01557
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 14:41:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KJx2s19694
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 14:59:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJx2O19691
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 14:59:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01488
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 14:40:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJwNO19565;
	Thu, 20 Mar 2003 14:58:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJvvO19414
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 14:57:57 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01433
	for <sipping@ietf.org>; Thu, 20 Mar 2003 14:39:28 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 20 Mar 2003 14:43:51 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D24896C@zoe.office.snowshore.com>
Thread-Topic: conf: comments on draft-evan-sipping-conference-scenarios-00
Thread-Index: AcLvE+DqkWL8iZ4IR46SuinxMVbVuA==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2KJvvO19415
Subject: [Sipping] conf: comments on draft-evan-sipping-conference-scenarios-00
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Section 1:
Why is the "special member" the one that initiates the conference?  Moderation, ownership, and the person that happened to hit the bridge first are three distinct concepts.  Pick a term, like Moderator, Owner, or Special Member, and be sure it gets into the conferencing framework document.  I would strongly suggest NOT using Conference Initiator.


Section 3.3:
I don't get this section at all.  A participant in a SIP-based conference will be gatewayed into the SIP signaling realm.  From the point of view of a focus, the *gateway* is the SIP end point.  There is nothing special, nor any special treatment, about the device on the other side of the gateway.


Section 3.4:
Same comment as for Section 1 on Initiator vs. Moderator.  Here the draft is clearly talking about the moderator.


Section 3.5:
Authentication - Is the proposal to use digest authentication with a password?  Is the proposal to use an IVR system to collect a password?  Those are two very different cases with very different protocol implications.

Control "the member may be able to manage" - Which member?  Do you really mean an arbitrary conference participant?  I didn't think so.  In addition, letting a first participant mute an arbitrary second participant in their mix is a really neat trick.  Does anyone do that in the real world?  Likewise, most conferencing services allow the participant to mute *their* stream, not *other* streams.  Muting other streams is usually left to the moderator, for obvious reasons.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 14:41:04 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01570
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 14:41:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KJx3m19710
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 14:59:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJx3O19707
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 14:59:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01492
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 14:40:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJwQO19585;
	Thu, 20 Mar 2003 14:58:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJvwO19418
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 14:57:58 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01436
	for <sipping@ietf.org>; Thu, 20 Mar 2003 14:39:28 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 20 Mar 2003 14:43:52 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D24896D@zoe.office.snowshore.com>
Thread-Topic: conf: comments on draft-wu-sipping-floor-control-04
Thread-Index: AcLvFKVv2gyzoJ9QS9qUGX6GoOyI8w==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2KJvwO19419
Subject: [Sipping] conf: comments on draft-wu-sipping-floor-control-04
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

In general, this draft has gotten really good.

I have a general comment about time.  There are a number of operations based on the client submitting a timestamp.  I would offer that client timestamps are irrelevant.  If I want to always jump the queue when I make a request, I will quickly learn to set my clock behind 10 minutes to make sure I'm always at the top of the queue.  My suggestion would be that all timestamps are generated by the server.  Yes, it means that if someone is on a slow link, their request might get pushed behind someone on a fast link.  I would simply state that and move on.

In the same vein, expirations should be delta times, not absolute stop times.

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 14:41:06 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01586
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 14:41:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KJx5W19727
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 14:59:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJx5O19724
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 14:59:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01496
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 14:40:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJwIO19525;
	Thu, 20 Mar 2003 14:58:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJvtO19406
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 14:57:55 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01426
	for <sipping@ietf.org>; Thu, 20 Mar 2003 14:39:25 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 20 Mar 2003 14:43:51 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D24896A@zoe.office.snowshore.com>
Thread-Topic: conf: comments on draft-mahy-sipping-media-policy-control-00
Thread-Index: AcLvEOUcw/9aATYJS46WMTsNmRIjwA==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2KJvtO19407
Subject: [Sipping] conf: comments on draft-mahy-sipping-media-policy-control-00
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Section 2.1:
The operations described in the last paragraph (XML schema, queriable collections, methods, etc) sounds like SOAP in terms of model and operation.  Should one simply say that?

Section 2.2:
MUST support at least one standard collection:  everyone supporting a different standard collection doesn't help anyone.  Either chose a single MUST IMPLEMENT or drop the requirement.  The requirement has no value, otherwise.

The behavior described for building sidebars, etc. is overly complex.  The idea of simple building blocks is good.  The idea of arbitrarily complex connection models with arbitrarily complex behavior is bad.  The ability to *create* arbitrarily complex models from simple building blocks is best.

Looking at some of the operations of CPCP, like creating and deleting conferences, sounds a lot like... SIP.  Is the idea that most of CPCP can be SIP, or is the idea that we will create something that does exactly what SIP does, only it does the other stuff, too?


Section 3:
The statement that all connections have an input source and an output source doesn't mesh with hold or mute.  Is there going to be an explicit "hold tank"?  This sounds more and more like H.248...


Section 3.1:
I would strongly suggest looking at the CCXML work in the VBWG at the W3C.  That group has been looking at signaling transactions for about a year now.


Section 5:
I can buy that layout and floor controls are within the scope of CPCP.  However, I would offer that IVR operations are way out of scope (text2speech and speech2text).  There already are lots of IVR languages and protocols out there that work just fine.  Moreover, are we getting into a little SciFi with speech2gesture and speech2signlanguage?

Section 5.1.1:
What is the use case for picking the n-th loudest speaker?  That is a rather expensive operation.  The loudest speaker or the m loudest speakers makes sense.


Section 5.1.3:
What is the use case for the n-mixer?  People spent a LOT of time figuring out the n-1 mixer.  An n-mixer is a bug...


Section 5.1.5:
Is gain control per input leg, per output leg, per arbitrary in-out combination?  The first two are relatively easy.  The last one is particularly nasty and expensive.


Section 5.2.2:
I don't get "... the first input connection to all streams connected to the ou[t]put connector that match the input stream."

For that matter I don't get the use case for any of the topology manipulation blocks or how they would be used.  A deployable use case would be VERY helpful here.


Section 7:
The XML Schema reference is:
Thompson, H., Beech, D., Maloney, M. and N. Mendelsohn, "XML Schema Part 1: Structures", W3C REC REC-xmlschema-1-20010502, May 2001.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 14:41:09 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01600
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 14:41:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KJx7919753
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 14:59:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJx7O19750
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 14:59:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01500
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 14:40:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJwSO19606;
	Thu, 20 Mar 2003 14:58:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJvxO19422
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 14:57:59 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01438
	for <sipping@ietf.org>; Thu, 20 Mar 2003 14:39:29 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 20 Mar 2003 14:43:52 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D24896E@zoe.office.snowshore.com>
Thread-Topic: conf: comments on draft-ietf-sipping-conference-package-00
Thread-Index: AcLvFe60D1UY0q5uR/OkoZB3u12YcQ==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2KJvxO19423
Subject: [Sipping] conf: comments on draft-ietf-sipping-conference-package-00
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

What about side-bars?  That's neither anchor (well, it *might* be), nor receiving-all.  That said, offering this information has SERIOUS privacy implications.  For example, I'm not sure Alice wants you to know she is talking to Bob behind your back...

The same goes for mute.  When company A is presenting to company B over a muted speaker phone, I'm not sure company B wants Company A to know that company B is talking amongst themselves during the presentation.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 14:41:12 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01613
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 14:41:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KJxBR19777
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 14:59:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJxBO19774
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 14:59:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01504
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 14:40:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJwKO19545;
	Thu, 20 Mar 2003 14:58:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJvvO19410
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 14:57:57 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01430
	for <sipping@ietf.org>; Thu, 20 Mar 2003 14:39:26 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 20 Mar 2003 14:43:51 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D24896B@zoe.office.snowshore.com>
Thread-Topic: conf: comments on draft-evan-sipping-media-policy-requirements-00
Thread-Index: AcLvEr5o+0G7KpygR46gCgXWVFk6bw==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2KJvvO19411
Subject: [Sipping] conf: comments on draft-evan-sipping-media-policy-requirements-00
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Requirements in general:
I don't get the subject of the requirements.  Is the subject (in the grammatical sense) CPCP (protocol capabilities), the identified party (the participant or mixer), or something else?

For example in REQ-GP1, is the *participant* the party that MUST be able to specify its own topology?  Here's a nasty result: a company hosts an earnings announcement conference call.  Two analysts create a sidebar and get private communications service paid for by the host.  I don't think the participant MUST be able to specify topology, at all.  Alternately, is the *protocol* the party that MUST be ABLE to specify topologies?

Likewise, in REQ-GP3, does this say that the *protocol* MUST allow the SPECIFICATION of the number of streams, or does this say that the *mixer* must support dynamic active talker sizing?

REQ-GP4 is unrealistic and over the top..


The Security Considerations is VERY light.  It essentially says, "bad things can happen, but we're not going to do anything about it."


I don't understand any of Section 8.  It desperately needs examples.  I'm still not convinced of the need for arbitrarily complex, *participant-driven* topology description and manipulation.


Section 8.1:
What on Earth is LastLoudest?  What is the "audio mix set before the current one"?  Over what time period?  Is this continuous?  How often does it get updated?

Does Not(Qualifier) result in a set?  E.g., in a conference with more than 2 participants, Not(LastLoudest) results in more than one stream.


Section 8.3:
What is the use case for LoudestSpeaker(N), where N != 1?  I would offer that if the use case is, "I will construct a mix of the three loudest talkers by doing 
Mix(LoudestSpeaker(1),LoudestSpeaker(2),LoudestSpeaker(3))", you will have exactly zero implementations.  That is very hard to do.  Moreover, I don't know anyone that is interested in, "Please play for me the 6th loudest speaker."

I would STRONGLY suggest against using numerical table numbers to describe VideoLayout.  That's begging for mistakes an non-interoperable implementations.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 14:41:14 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01626
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 14:41:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KJxCI19793
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 14:59:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJxCO19790
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 14:59:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01507
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 14:40:42 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJwEO19485;
	Thu, 20 Mar 2003 14:58:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJvsO19398
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 14:57:54 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01421
	for <sipping@ietf.org>; Thu, 20 Mar 2003 14:39:24 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 20 Mar 2003 14:43:49 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D248968@zoe.office.snowshore.com>
Thread-Topic: netann Issue #2: Result Code for Early Media Termination
Thread-Index: AcLu/YTzL+6Zs0+ISu+I/V2ilryklQ==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2KJvsO19399
Subject: [Sipping] netann Issue #2: Result Code for Early Media Termination
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Problem: How does the media server signal that it has completed an early media announcement?

Prior drafts had the media server send a 487 REQUEST TERMINATED result code.  However, RFC3261 reserves that result code as a response to a request sent after the UAS has processed a BYE or CANCEL from the UAC.

The behavior netann seeks is identical in every way to a user that rejects a *particular* connection attempt.  That is, the rejection must not imply the user is not there, will not be there later, or that there is a failure at the media server.  We cannot have a proxy server optimize attempts by thinking that the annc user is not available and thus should not make follow-on connection attempts.

Options are:

410 GONE - Doesn't work because this implies a permanent condition; "annc" clearly is still at the media server.

480 TEMPORARILY UNAVAILABLE - looks identical to a user rejecting a call, e.g., Do-Not-Disturb.  Implies that another attempt to the same user (annc) may succeed.

486 BUSY HERE - also a good choice: identical to a user rejecting a call, AND lets the UAC play local busy tone after the announcement finishes.  If the user misses the announcement, they will still get meaningful call progress.  Note that 486 was the result code used in -00.  It was changed to 487 in -01 because some people felt that 486 might indicate something about the original target of the request that was not true.

487 REQUEST TERMINATED - we were trying to capture the idea of a request that had some treatment but was ultimately canceled.  Thus there was a virtual CANCEL from the UAC after the announcement played.  Even though any 4xx response should terminate a session, there is a non-conforming SIP phone that ignores 487's on dialogs where the phone did not send a CANCEL or BYE.

600 BUSY EVERYWHERE - a good choice: not only does it look like the user rejecting a call and the UAC playing local busy as in 486, but it stops forking proxies from continuing a search at locations other than the one that resulted in an announcement.  The only problem is, this might be seen as a bug, not a feature.

603 DECLINE - this would be an excellent choice, except for one possible problem.  6xx responses are 'definitive'. My concern is a zealous proxy might 'optimize' a 6xx response and hold-off further attempts to a given request-URI.  In fact, that is the correct action if there is a Retry-After header.  If the media server could return 603 with a Retry-After: 0, then there would not be a problem.  However, zero is not a valid Retry-After value.  Although it is not conforming behavior, if a proxy uses a non-zero default Retry-After value, future announcement requests will be blocked for a period of time.

4xx or 6xx new code - we could "say what we mean" and create a new response code.  The semantics of this code are "the user rejected the call."  However, given that this is identical to 480 or 603, why would we not simply use 480 or 603?



Proposal:
Use 480, because we do not want to break meaningful forking proxies.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 14:42:15 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01734
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 14:42:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KK0EK19965
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 15:00:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KK0EO19962
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 15:00:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01670
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 14:41:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJxGO19838;
	Thu, 20 Mar 2003 14:59:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJw0O19431
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 14:58:00 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01442
	for <sipping@ietf.org>; Thu, 20 Mar 2003 14:39:30 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 20 Mar 2003 14:43:53 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D248970@zoe.office.snowshore.com>
Thread-Topic: conf: comments on draft-koselainen-mmusic-floor-req-01
Thread-Index: AcLvF6RhgI64ZIwFQiKioblbLwKB+w==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2KJw0O19433
Subject: [Sipping] conf: comments on draft-koselainen-mmusic-floor-req-01
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

[Posted to SIPPING because that is the home of the Conference Design Team.  If it should go to MMUSIC, tell me.]

General observation: it would help to harmonize the terminology with the conference framework document.



Section 5:
Can the distinction between mandatory and optional be whether the policy is in effect or is ignored?


REQ-16:
I agree that the chair MUST know who has the floor and who has requested the floor.  I disagree that participants MUST know who has the floor.  A floor control framework certainly MUST have the CAPABILITY to let participant know who has the floor.  However, the only MUST for the participant is whether or not the participant has the floor.

Likewise I strongly disagree that participants MUST know who has requested the floor.  Again, the MUST is that the protocol needs the CAPABILITY to let the participant know who has made floor requests.  Likewise the protocol may indicate that someone else has requested the floor.  However, the divulging of the identities of other participants MUST consider their privacy needs.


REQ-17:
Again, this makes sense for the chair, but doesn't make sense for participants.


REQ-18:
What is the value of this requirement?
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 15:27:03 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01628
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 14:41:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KJxCu19809
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 14:59:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJxCO19799
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 14:59:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01510
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 14:40:42 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJwVO19628;
	Thu, 20 Mar 2003 14:58:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KJvxO19426
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 14:57:59 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01440
	for <sipping@ietf.org>; Thu, 20 Mar 2003 14:39:30 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 20 Mar 2003 14:43:52 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D24896F@zoe.office.snowshore.com>
Thread-Topic: conf: comments on draft-johnston-sipping-cc-conferencing-01
Thread-Index: AcLvFplDySJbL6wlTFqBj+MQapgDOQ==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2KJvxO19427
Subject: [Sipping] conf: comments on draft-johnston-sipping-cc-conferencing-01
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Sections 2.2 and 2.3:
Can one have a MUST with an UNLESS?  Doesn't that make the MUST into a SHOULD?

Section 4.1:
Why MUST the conference URI be reserved prior to use?  Who reserves it?

Section 4.10:
I would offer stronger language about authorization here.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 16:04:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06555
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 16:04:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KLM3O27906
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 16:22:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KLM3O27903
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 16:22:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06549
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 16:03:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KLLMO27855;
	Thu, 20 Mar 2003 16:21:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KLKJO27749
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 16:20:20 -0500
Received: from dewberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06498
	for <sipping@ietf.org>; Thu, 20 Mar 2003 16:01:47 -0500 (EST)
Received: from cs.columbia.edu (wl-134-224.wireless.ietf56.ietf.org [130.129.134.224])
	(user=hgs10 mech=PLAIN bits=0)
	by dewberry.cc.columbia.edu (8.12.8/8.12.8) with ESMTP id h2KL40WV002920
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 20 Mar 2003 16:04:02 -0500 (EST)
Message-ID: <3E7A2C0C.7020100@cs.columbia.edu>
Date: Thu, 20 Mar 2003 16:01:00 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>,
        Xiaotao Wu <xiaotaow@cs.columbia.edu>
Subject: Re: [Sipping] conf: comments on draft-wu-sipping-floor-control-04
References: <4A3384433CE2AB46A63468CB207E209D24896D@zoe.office.snowshore.com>
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D24896D@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Good suggestions; we'll incorporate those.

Eric Burger wrote:
> In general, this draft has gotten really good.
> 
> I have a general comment about time.  There are a number of
> operations based on the client submitting a timestamp.  I would offer
> that client timestamps are irrelevant.  If I want to always jump the
> queue when I make a request, I will quickly learn to set my clock
> behind 10 minutes to make sure I'm always at the top of the queue.
> My suggestion would be that all timestamps are generated by the
> server.  Yes, it means that if someone is on a slow link, their
> request might get pushed behind someone on a fast link.  I would
> simply state that and move on.
> 
> In the same vein, expirations should be delta times, not absolute
> stop times.

These probably offer less of an incentive to "cheat", but might as well 
be consistent.


> 
> _______________________________________________ Sipping mailing list
> https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW
> development of the application of SIP Use
> sip-implementors@cs.columbia.edu for questions on current sip Use
> sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 20 17:42:07 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10772
	for <sipping-archive@odin.ietf.org>; Thu, 20 Mar 2003 17:42:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2KN0AH03704
	for sipping-archive@odin.ietf.org; Thu, 20 Mar 2003 18:00:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KN0AO03701
	for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 18:00:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10710
	for <sipping-web-archive@ietf.org>; Thu, 20 Mar 2003 17:41:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KMxTO03636;
	Thu, 20 Mar 2003 17:59:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KMe6O02736
	for <sipping@optimus.ietf.org>; Thu, 20 Mar 2003 17:40:06 -0500
Received: from cerbrus.convedia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10261
	for <sipping@ietf.org>; Thu, 20 Mar 2003 17:21:32 -0500 (EST)
Received: from ladon.convedia.com (ladon [192.168.208.15])
	by cerbrus.convedia.com (8.9.3+Sun/8.9.3) with ESMTP id OAA11618;
	Thu, 20 Mar 2003 14:21:12 -0800 (PST)
Received: from convedia.com ([192.168.209.16])
	by ladon.convedia.com (8.9.3+Sun/8.9.3) with ESMTP id OAA22473;
	Thu, 20 Mar 2003 14:23:46 -0800 (PST)
Message-ID: <3E7A3FA5.6010701@convedia.com>
Date: Thu, 20 Mar 2003 14:24:37 -0800
From: Tim Melanchuk <timm@convedia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] netann Open Issue #1: Media on Hold
References: <4A3384433CE2AB46A63468CB207E209D248967@zoe.office.snowshore.com>
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D248967@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

why do we need different behaviour for each type of service?

- conf: time moves forward (no choice)
- dialog: implementation dependent
- ann: pause the stream

we do need to handle having a dialog (in the sip sense) created
on hold for some 3pcc scenarios and should not start playing
until it is taken off hold.

however i don't see a big difference between an announcemnt
"timing out" based upon some implementation dependent timeout,
or simply having it time forward.


Eric Burger wrote:
> Problem:
> What does the media server do when the UAC issues a 'hold' (see RFC3264)?  The options are:
> 	Do not send media, but have time move forward;
> 	Suspend playing media;
> 	Make a choice based on how the media was put on hold
> 	Let the UAC signal behavior
> 
> Note that hold is not an issue for early media: it is not possible to put early media on hold.  Also note that the semantics for putting a conference leg on hold is already well defined.
> 
> 
> For VoiceXML, Dean had an excellent suggestion of throwing an exception: let the application decide what to do.  However, it will take about a year to standardize that behavior through the W3C.
> 
> There were rumblings of not specifying behavior for announcements.  I really don't want to do that because that approach will create different user experiences for the same activity, based on implementation.
> 
> An issue with suspending media is it is possible to have a session on hold indefinitely, whereas most announcements are bounded in time.  For example, an announcement could have duration=30000, which would normally disconnect the session after 30 seconds.
> 
> Letting the UAC signal behavior is unrealistic as the UAC probably does not know that it is calling a media server.
> 
> 
> 
> Here is the updated proposal:
> 
> Dialog service: Implementation dependent; suggest throwing an exception.
> Announcement service: Suspend playout; implementation dependent timeout (if any) after which media server sends a BYE.
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 21 01:29:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23631
	for <sipping-archive@odin.ietf.org>; Fri, 21 Mar 2003 01:29:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2L6liW01682
	for sipping-archive@odin.ietf.org; Fri, 21 Mar 2003 01:47:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2L6lhO01677
	for <sipping-web-archive@optimus.ietf.org>; Fri, 21 Mar 2003 01:47:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23627
	for <sipping-web-archive@ietf.org>; Fri, 21 Mar 2003 01:28:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2L6kTO01629;
	Fri, 21 Mar 2003 01:46:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2L6jmO01586
	for <sipping@optimus.ietf.org>; Fri, 21 Mar 2003 01:45:48 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23597
	for <sipping@ietf.org>; Fri, 21 Mar 2003 01:27:04 -0500 (EST)
Subject: RE: [Sipping] netann Open Issue #1: Media on Hold
Date: Fri, 21 Mar 2003 01:31:32 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D24897A@zoe.office.snowshore.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Thread-Topic: [Sipping] netann Open Issue #1: Media on Hold
Thread-Index: AcLvL7a9/LOvSqIJS6y7FsYgjGPvogAQKY7w
content-class: urn:content-classes:message
From: "Eric Burger" <eburger@snowshore.com>
To: "Tim Melanchuk" <timm@convedia.com>
Cc: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2L6jmO01587
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

The difference is, "we can do better than the PSTN."

Timing out is just a bow to reality.

> -----Original Message-----
> From: Tim Melanchuk [mailto:timm@convedia.com]
> Sent: Thursday, March 20, 2003 5:25 PM
> To: Eric Burger
> Cc: Sipping (E-mail)
> Subject: Re: [Sipping] netann Open Issue #1: Media on Hold
> 
> 
> why do we need different behaviour for each type of service?
> 
> - conf: time moves forward (no choice)
> - dialog: implementation dependent
> - ann: pause the stream
> 
> we do need to handle having a dialog (in the sip sense) created
> on hold for some 3pcc scenarios and should not start playing
> until it is taken off hold.
> 
> however i don't see a big difference between an announcemnt
> "timing out" based upon some implementation dependent timeout,
> or simply having it time forward.
> 
> 
> Eric Burger wrote:
> > Problem:
> > What does the media server do when the UAC issues a 'hold' 
> (see RFC3264)?  The options are:
> > 	Do not send media, but have time move forward;
> > 	Suspend playing media;
> > 	Make a choice based on how the media was put on hold
> > 	Let the UAC signal behavior
> > 
> > Note that hold is not an issue for early media: it is not 
> possible to put early media on hold.  Also note that the 
> semantics for putting a conference leg on hold is already 
> well defined.
> > 
> > 
> > For VoiceXML, Dean had an excellent suggestion of throwing 
> an exception: let the application decide what to do.  
> However, it will take about a year to standardize that 
> behavior through the W3C.
> > 
> > There were rumblings of not specifying behavior for 
> announcements.  I really don't want to do that because that 
> approach will create different user experiences for the same 
> activity, based on implementation.
> > 
> > An issue with suspending media is it is possible to have a 
> session on hold indefinitely, whereas most announcements are 
> bounded in time.  For example, an announcement could have 
> duration=30000, which would normally disconnect the session 
> after 30 seconds.
> > 
> > Letting the UAC signal behavior is unrealistic as the UAC 
> probably does not know that it is calling a media server.
> > 
> > 
> > 
> > Here is the updated proposal:
> > 
> > Dialog service: Implementation dependent; suggest throwing 
> an exception.
> > Announcement service: Suspend playout; implementation 
> dependent timeout (if any) after which media server sends a BYE.
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> > 
> > 
> 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 21 21:21:45 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05627
	for <sipping-archive@odin.ietf.org>; Fri, 21 Mar 2003 21:21:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2M2eNZ28567
	for sipping-archive@odin.ietf.org; Fri, 21 Mar 2003 21:40:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2M2eNO28564
	for <sipping-web-archive@optimus.ietf.org>; Fri, 21 Mar 2003 21:40:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05613
	for <sipping-web-archive@ietf.org>; Fri, 21 Mar 2003 21:21:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2M2dUO28456;
	Fri, 21 Mar 2003 21:39:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2M2bvO28369
	for <sipping@optimus.ietf.org>; Fri, 21 Mar 2003 21:37:57 -0500
Received: from 01mail.PghMail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05516
	for <sipping@ietf.org>; Fri, 21 Mar 2003 21:18:46 -0500 (EST)
Received: from Akllsxnet (unverified [63.113.39.155]) by 01mail.PghMail.com
 (Vircom SMTPRS 5.3.232) with SMTP id <B0006492928@01mail.PghMail.com> for <sipping@ietf.org>;
 Fri, 21 Mar 2003 21:21:03 -0500
Date: Fri, 21 Mar 2003 21:21:03 -0500
Message-ID: <B0006492928@01mail.PghMail.com>
From: mwatson <mwatson@nortelnetworks.com>
To: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=TL1Z8Q85QBH5eWK5u6r7K18o
Subject: [Sipping] A  humour game
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--TL1Z8Q85QBH5eWK5u6r7K18o
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

picacu.exe is of type executable and is removed.

Please contact your network administrator for further information.

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

--TL1Z8Q85QBH5eWK5u6r7K18o
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>This is a  humour game<br>
This game is my first work.<br>
You're the first player.<br>
I expect you would enjoy it.</FONT></BODY></HTML>

--TL1Z8Q85QBH5eWK5u6r7K18o
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

picacu.exe is removed from here because it is of type executable

---------------------------------------------------------
--TL1Z8Q85QBH5eWK5u6r7K18o

Content-Type: application/octet-stream;
	name=448146_101[1].jpg
Content-Transfer-Encoding: base64
Content-ID: <Qd40i33E7B>

/9j/4AAQSkZJRgABAAEAlgCWAAD//gAfTEVBRCBUZWNobm9sb2dpZXMgSW5jLiBWMS4wMQD/
2wCEABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19i
Z2hnPk1xeXBkeFxlZ2MBERISGBUYLxoaL2NCOEJjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2Nj
Y2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY//EAaIAAAEFAQEBAQEBAAAAAAAAAAABAgMEBQYH
CAkKCwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoLEAACAQMDAgQDBQUEBAAAAX0BAgMA
BBEFEiExQQYTUWEHInEUMoGRoQgjQrHBFVLR8CQzYnKCCQoWFxgZGiUmJygpKjQ1Njc4OTpD
REVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoOEhYaHiImKkpOUlZaXmJmaoqOkpaan
qKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4eLj5OXm5+jp6vHy8/T19vf4+foRAAIB
AgQEAwQHBQQEAAECdwABAgMRBAUhMQYSQVEHYXETIjKBCBRCkaGxwQkjM1LwFWJy0QoWJDTh
JfEXGBkaJicoKSo1Njc4OTpDREVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoKDhIWG
h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uLj5OXm
5+jp6vLz9PX29/j5+v/AABEIAG4ApQMBEQACEQEDEQH/2gAMAwEAAhEDEQA/AJG+JG3/AJhX
/kx/9jQK4p+I4AH/ABKj/wCBH/2NAXAfEcE/8gr/AMmP/saAuTw+Op5pxCmiyNIRkIJiWxjO
cbadgudJpV9cXsRkntFgGTtxJvzyR6D0z9CPwGrDuX6QBQAUAFABQAUAFABQAUAFADXkVBzQ
K43zhjPAHfJxTsFxFmyGJUjBx1pBceHBOO9Ax2aADNAHg/JHzDGOc0EjsNt3Bfl9ccGgBULB
tzYoA6fRfE66TkLp1u25FBZcxs2BwSec9+g70wOg0/xHqesTKtnZeWgPzNngDOM7j1wD0x2z
04p2A60VIwpALQAUAFABQAUAFACUABOBmmBXuJF2NnPyjnB/SmkIz3uQkM5MbMYQxDNhGdVH
UDuO2fy61QE73BS4WBpVTK5AI4OMAjP4j06iiwiaFwzFix5Y8kjB+lSxlncMcUgE3e1MDwxN
2CcgcdD1qRkiyBg2eh4oAci8MyAkAZJxTES+ZJkg5BHUHI/z3pgdJBrupxMqW1vZ2rEqoEMA
DHdjPy5JPTnjgjB5xTA7bSbG5t1M1/cm5unADMOFXHZRx/LmkM0aQC0DCgAoAKAEoEFACOSF
ODg9s0AVRJ+8aOTOO2P8/jTEVrrDkmIo00Q+45x9D/n1700BjaldpassrFmjfKHCDcy7lY9x
xtB4HIznjNMCfzGL24RE2eWxZPMATkg4PHPQk9eAfXBANSCPymWMKBH0BDH+X4flQxF0YGcU
gFoGeHgDJK9D2IzUDHmEYGFK/wAjQBq6RrAsUa2mt0ubNzuMT8EE4yQwGew9qaYHVeVoniFo
ofN8q7ZSQsG4rwWPJKjnk9aq4jYsdD03SfLnCbpo1P71ySx9Tjp39KQzT+0oGC88jOccUWAm
ByMikAtAATQAxZlLbT8r4ztPWgB4OaACgAoAKAKl+haLKtgZAYZxn05HTBwcj0piM1riO4tJ
RCTcSgMVYIcEdiAe4zyBg5HbIFMDjYNTlN+PNkV4lUpuYbguNvzgMf8AZB5+gHSlcZu6MURY
7rCJJcPtCo7KF3AtwDx0OAMcEkcg8UhG/BcxQpJ1jRM/KwwcAZ7/AI0CHmRpZh5DggZBJ+7k
YH49e3pjIoAuAEdT+lIZ4Wm5iQo/GoGSDAwr5BHp2oAnWGSaVUt42lLf3QScjk00Bv6XoErI
k9xDcwLG7CTHAKbSRjJyeQQfUEVSQjqrG2itLNoLX94CSQZMMWHOO3OCcYx7U7DJYj5jKy7W
CsE2kZJPORjPpg9f50CNS2ZhtLsTxjJPH/16TGWs1Ihc0DIsK0zggHhTyPc0APRdoxuJA6Zo
AdQAhNAhM0wIp5FUbWJ+b04P4e9AHL+L2T7LFPBGDJGwTz24ZARnAJ5yc/kDTGcU2/eH3kPn
OV65qQN3w1Im6ON4yyh1WSRhuEec7Rgc4bPJ9apMDpoojchFDP5TL88bAAk8bhx16H29sYzR
JsoQ0eOmOMVIDZJyrYUZI600gPET8owB9azKHBsqQTgY7igB8ErwsrxMVZGzuU4IPr9aAPQ9
M1FrjRkivmDTZ2MMH7mBgN781aYWGPc4eNgz/KxYjOOp6H8OM/ywKdxk/wButvMif96pG7dG
qr8zE5J/p/h3QWHnxEkW7ZGxfBAVjnHoTj9alyQKLZDB4qnD5lhDJnJCkZAx0B47+tTzFchd
TxKzcJaB+M/LKcn8Nufyqk0ybW3IBr9w14lxHar5RTDJjJfuDux0H9T+D0CxM3iSXacWJVux
LHH8qNAsVW8S3yttMdurehVs/wDoVNWCwq+Ir84DJAP+AN/jRoKwf8JFf5wIoif9xv8AGgLF
e61vUJsBlWPHTbGT+hzQFjGlH2qQPKrkgYyVKcfl7mgZGbKFRz5f4zDP86WgDI7RoN00MkTb
cDLuvy5GMdccjd1oA3dD1p5nllnRQGckldwLOx+7gDBOBxjk8CqTJZ0kU++Lzk3FXIK4B5Hr
QIRpnRip2n/fOB+HSmB5C5XzcZUj1HesbGlxAqnGPu5+b1HvQFixLZvGxdGWSMcsU5x71PMr
2CzNCFWjiKRSTIGbDNkL09s570nOwKNxHmlCmIS5KHqwyTnPtmrU7q4WJLOTzsrdsyx4wAgx
uJx74x3/AM8S5jSNQyaXA21nkViOQWHv7/5xUq72HcRrjTCpKo7gtyFZiCfw7/40O+zHcjur
hPL2W8XlYbIcNlsY689OePXimpdAsZVxPdW5iMdzNtePdgSHC/MRgc+1aaEite3gIQSzHPOf
NNFkTcdMkzXTJNO7BUUjJJPK5xn8TRsUlcV7eUYMbNjHQsP60RkuoST6Ft7WNiMPIozxhuD9
TSlJW0FGL6jPsKuNonAx67iT+QJNTGSvqNx7E62lvHtWSSPhAeVbPTr09c1pzRJ5JEE1paG4
Z1kRkxkKA/p7rjrScojUJEZs4jACWSPa2ZHOduO2cZ7K3b8KmLKkitp189teR3GSxTop5DKc
5HIPqex6mtEZnY2t08pE6KyxMMouTz+Geh6//qFWtSTZYrIAcjP+z/8AqoA8gt0ElwAxAUdc
nFYt2RaL8Fvbjcm4ls9/SsXJlqxahMQOAWIOOint+dQ7lDZWiWM75XVmJJyMk+/T1zTV2LQf
F5DQyuc7g6nc5JbgHmqUmlYXmRm4jWRsZGQck5OP/rUrN6sdwk8m4IdpNuE29zz2qoycRPUd
50EOIhGpQgcnkH/ORSd3qGiLAMcmGBZiRgH0/rUptMohuUDrCu3b5Sbep5yxP9a2i7oTRpC2
gEMRjfzGOARt27TWqRkV5pDJeyELgoQgIbHA47/T9aiRpHYAxUFQNwHbPT8jWbLSLCB1RZEy
pByTuA4/T2pDG73y7jaATgnGen86QWFUAkhjuzwWHGPb2/GgBzxhUUHOfvKcZX6gdD+eaAGy
rGNOuI3GQzqdpbHAD8n2ziriyZHOgrHckiNX2sf4jg/iMGtLmTR0+janCLBIvLghaB4juQbc
5YKTkk54yD9e/QWmTYl1zUtTEkKWZnhiCEho8jdk989CMdKcnYEjB1SK3s9QlSKNViJ+VQ+4
4HB557g8VhOLuVHYrNcRhfLiYpxggAEH61movdlD4XCQlUdgQM4IHPH/ANYUPzBDlTrJlhEM
45GTnOOuD/8AqpX7DGTeZDhsmWFxnBG39PwFNWYtiIMsh3GHaeeFwB2703fuNNEuXL4jTLHg
Krkt+H+TQtRCtKYmeKeKSOQfwy5BH4dabiwuOi3AEI42/eYZ4H4/lUvXcaJWuEEG/wC6c4O3
HH+fanBNMGxRcXDKRHdZUYIUDpW3MTyofF5hLmSQZblgBknv/WobLirE8DIr4Od38PqOPUc1
JZM5Vzu3nGOcgEZ/z9akY9VkMmSp3D0P61Si3sS5JCtbOVQAFSpzlUyT+JquRke0QkqTAsUt
yfTAxij2bD2iGqrXFjdblCEwkDcQMOXUcnP1pJWuVfY5uL55FXOMnmrINSzC2MjSMXkym0gf
Ke3Of8/rTTsDWhY8Q3M2oyQ/ZYGiSPP3JM7s45P5f5zTcxcvcyZpGuLiSUhsyMXPHqSakVxg
TueOOueaLAKsQC4yduOAT2osAqgKwIZgRznJ/nSsO48Y+6ST1P3j+NKyAaI13Yxx6Z5xTsFx
TEvTjaTkg+o/rTAescf8MYyO4xQAYVD91R7henSlYVwEUZUnaCPanYYDYpXHHzdemOPX8KAL
UU2CfMUDJ5OevH/1qho0Uh+zfKdqFs9OM80iiwGItw/l7sgHAIwfrxSA1NHYTeZvh8plxleu
K1pmVRmn5a+grUyAxrjpRYDAdT9skiRQqksWPc4y/wD7LWLXvM3WyZzUMeGEj7SvoMc0ybl0
T5DAhiPTNArjvtfGcAD/AGmHNFg5ikM/5FAhCfmCgc5x60AA3AZXJ9vSkFiQdMs3bIyelA7C
bvceuaAsOIZTn27etAgDYxkH+tMYpLBd3AA7Hp/n/GkBIDhgOTn0pgDEI2AMgd16UALHllfb
gbBlvpnH8yKAJ7WznupNsEbtk8sqlgo9TgH+VFrhsby+FdQiKmRIp1OWbypdrnjplhgfl+VH
KPnG6p4fu7F/9Gge4g4wV5YexA5PTrUuPYqM11IdLu4bV5POO3cFIKxk56+mc9RzV09Nyaiv
saLaraBeGkbnoIm/wrTmRnysf9vtWH+u/wDHG/wo5kHKzCu5Jo7qaS2USK4YAn0K4PUj1OKy
eruaLaxShjjgRybaUzKRiVvmVRnsnc8dyRz070xNXNLTb3SbeGVRp32mdvm/fIuDjPQAHbz2
H9BTViWmdfYSwywCaW2itpHUExlQWUY4Bx7dP5CqEeUjdnlifbisyhQXTpnnrz0pDHBCxBbP
Ht0oCwEHsevb0oAcpPODy3vQFxrLztBJJOOO9AEiBkYcYxg4GKA2YpP95gCaAuMwSTjp7nmg
CTd8uX9eMdjQA5Cm0sxyAp/yeaAHRyldjJ8pQggg8g5657U7gdFpniu/SSKOdo2iLAM8o5QE
/h+tNMGju4pFljV0ZWRhlWByCPrVEGPqfh60uw7xqYJydwdCcZ916c98YJpNJjTsc9e6dNYS
7JfnXqJAMAjP8/ak0WmQhRRYY7aDQIVRtPGPypgSpkbtjvGT1KMQT+VUSPTzUXELRRDP3ow0
Zb67GXP4+v1poVjiFBI59cVkMeCVxgD3oGB5bqevbjikAnIJBbc31wKYhxG0kAnI446EUhiM
cEhgMjjg0AOA4POCOcHA47mgBzgoxUsMqc9uT357igLCEAZIyeefU0CFKlQqF0Tpk46ZHc/W
mMVVOyQkqRg7cEY/+v8ASkOwqKVfaVI4PJPB6/rx0oCw8syfJKSPQ8kfTNAWNfSfEt5pypD5
kUsWB8jt0GegI6cfgPSmpCaOotvGWlzsEkMsJI6soK/oTV3RNjaYRXMBGQ8Ui4yDwwI9RTEc
nqmnNYT/ACbmhIyrH+RpWLTKYIpDJFpgPAwB7DvTEO4/u0xGgPAOlD/lvefi6n/2Ws7AKvgL
S1GBc3uP+ui//E0WAT/hAdKxjz7vj/aT/wCJosAv/CB6XnIuL0e29cf+g0WAVvAmls2ftF6P
YSL/APE0WAcPA+mcZmuiPQsnP/jvtRYrmY0+A9LP/Le8H0dP/iaLCuJ/wgOlf897vPrvT/4m
iwhR4E0wAf6Recf7af8AxNFgFbwJpbKAZ7vI4Db1z/6DSsO4f8INpn/Pe7PGOWX0/wB2iwXD
/hBdM248+8xnP31/+Jp2BsJPA2nSJsa5vCP99f8A4miwXIv+FfaUM4ub0A/7af8AxNOwhR4A
0sf8vN7/AN9r/wDE0AatloKWEaR29/eiNW3BWZCPcfd6UXAtXmmw3sBhmZypOeMf4U7gUB4Y
sh/y1n/Nf8KQXHDw1Zj/AJbXH/fQ/wAKAuOHh20H/LWf/vof4U7gH/CO2n/PWf8A76H+FFwP
/9=9
--TL1Z8Q85QBH5eWK5u6r7K18o--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sun Mar 23 07:00:04 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00548
	for <sipping-archive@odin.ietf.org>; Sun, 23 Mar 2003 07:00:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2NCJMc01014
	for sipping-archive@odin.ietf.org; Sun, 23 Mar 2003 07:19:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2NCJMO01011
	for <sipping-web-archive@optimus.ietf.org>; Sun, 23 Mar 2003 07:19:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00529
	for <sipping-web-archive@ietf.org>; Sun, 23 Mar 2003 06:59:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2NCIIO00995;
	Sun, 23 Mar 2003 07:18:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2NCG8O00930
	for <sipping@optimus.ietf.org>; Sun, 23 Mar 2003 07:16:08 -0500
Received: from accord-ntsrv3.polycom.co.il (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00500
	for <sipping@ietf.org>; Sun, 23 Mar 2003 06:56:18 -0500 (EST)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2656.59)
	id <G8D0MKAH>; Sun, 23 Mar 2003 13:58:12 +0200
Message-ID: <C550397C3B6AEB418E62170D9E349CE2136FCE@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Eric Burger'" <eburger@snowshore.com>,
        "Sipping (E-mail)"
	 <sipping@ietf.org>
Subject: RE: [Sipping] conf: comments on draft-even-sipping-media-policy-r
	equirements-00
Date: Sun, 23 Mar 2003 13:58:11 +0200
X-Mailer: Internet Mail Service (5.5.2656.59)
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Eric,
Thanks for the comments.
I appreciate the feedback since part of it was written based on my
understanding of multimedia conferencing and the remarks will help me to
have it clearer in the next revision. I agree that section 8 needs to be
better written.
My other responses are in line

Roni

> -----Original Message-----
> From: Eric Burger [mailto:eburger@snowshore.com]
> Sent: Thursday, March 20, 2003 9:44 PM
> To: Sipping (E-mail)
> Subject: [Sipping] conf: comments on 
> draft-even-sipping-media-policy-requirements-00
> 
> 
> Requirements in general:
> I don't get the subject of the requirements.  Is the subject 
> (in the grammatical sense) CPCP (protocol capabilities), the 
> identified party (the participant or mixer), or something else?

I agree that it should be more clear. In general the texts says "All the
requirements are based on having a privilege mechanism that
   authorizes users to access and manipulate the media policy data." 
The requirements are for the Media Policy which is part of CPCP. The
requirements can be seen also from the participant size since being able to
manipulate the media policy is subject to privilege level (one of which can
be that the participant cannot do any manipulations or even be aware that
they exist)

> 
> For example in REQ-GP1, is the *participant* the party that 
> MUST be able to specify its own topology?  Here's a nasty 
> result: a company hosts an earnings announcement conference 
> call.  Two analysts create a sidebar and get private 
> communications service paid for by the host.  I don't think 
> the participant MUST be able to specify topology, at all.  
> Alternately, is the *protocol* the party that MUST be ABLE to 
> specify topologies?
I can change the text, but again it is implied by the general sentence. 

> 
> Likewise, in REQ-GP3, does this say that the *protocol* MUST 
> allow the SPECIFICATION of the number of streams, or does 
> this say that the *mixer* must support dynamic active talker sizing?

I meant the protocol. 
> 
> REQ-GP4 is unrealistic and over the top.
I disagree, there are products that can send each participant a different
video stream by switching and even mix different layouts.

> 
> 
> The Security Considerations is VERY light.  It essentially 
> says, "bad things can happen, but we're not going to do 
> anything about it."
>
The media policy are just the data manipulations, the CPCP which is
addressed in other document is the actual transport and the security section
is more a security requirement for the CPCP.
 
> 
> I don't understand any of Section 8.  It desperately needs 
> examples.  I'm still not convinced of the need for 
> arbitrarily complex, *participant-driven* topology 
> description and manipulation.
> 
> 
> Section 8.1:
> What on Earth is LastLoudest?  What is the "audio mix set 
> before the current one"?  Over what time period?  Is this 
> continuous?  How often does it get updated?
The Lastloudest is the loudest speaker in the previous mix, this operation
is to buffer the loudest speaker when a new speaker becomes the loudest. It
is used for example in video conferencing to create a conference that is
showing to every one the loudest speaker and the loudest speaker will see
the previous loudest speaker. As for the rate of change of active speaker,
the conferencing bridges are using some parameters that specify the minimum
time that some has to be loudest before becoming the loudest speaker (also
known as cough delay - so that clearing your throat will not cause a
switch), the other parameter is minimum time that active speaker is viewed
before a switch can occur.

> 
> Does Not(Qualifier) result in a set?  E.g., in a conference 
> with more than 2 participants, Not(LastLoudest) results in 
> more than one stream.
> 
That is true, but in the example we had 4 input streams that were the result
from the mixer. three of them had the loudest speaker as a contributor and
only one did not. I will clarify the text
> 
> Section 8.3:
> What is the use case for LoudestSpeaker(N), where N != 1?  I 
> would offer that if the use case is, "I will construct a mix 
> of the three loudest talkers by doing 
An example is Not (LoudestSpeaker(2)) - will select the stream that does not
include the second loudest speaker as a contributing source.

> Mix(LoudestSpeaker(1),LoudestSpeaker(2),LoudestSpeaker(3))", 
> you will have exactly zero implementations.  That is very 
> hard to do.  Moreover, I don't know anyone that is interested 
> in, "Please play for me the 6th loudest speaker."

This is more important for video. If I am using a tiled display I want the
video of  loudest speaker in sub-window1, the video from the second loudest
speaker in sub window 2 and so on.
> 
> I would STRONGLY suggest against using numerical table 
> numbers to describe VideoLayout.  That's begging for mistakes 
> an non-interoperable implementations.
I have no problem there - by using mime types for layout I still think that
we will need to explain and draw the actual layout.

> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sun Mar 23 08:59:43 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02033
	for <sipping-archive@odin.ietf.org>; Sun, 23 Mar 2003 08:59:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2NEJ4406634
	for sipping-archive@odin.ietf.org; Sun, 23 Mar 2003 09:19:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2NEJ3O06631
	for <sipping-web-archive@optimus.ietf.org>; Sun, 23 Mar 2003 09:19:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02027
	for <sipping-web-archive@ietf.org>; Sun, 23 Mar 2003 08:59:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2NEIIO06596;
	Sun, 23 Mar 2003 09:18:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2NEHmO06569
	for <sipping@optimus.ietf.org>; Sun, 23 Mar 2003 09:17:48 -0500
Received: from accord-ntsrv3.polycom.co.il (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02015
	for <sipping@ietf.org>; Sun, 23 Mar 2003 08:57:55 -0500 (EST)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2656.59)
	id <G8D0MKNP>; Sun, 23 Mar 2003 15:59:49 +0200
Message-ID: <C550397C3B6AEB418E62170D9E349CE2136FD0@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Eric Burger'" <eburger@snowshore.com>,
        "Sipping (E-mail)"
	 <sipping@ietf.org>
Subject: RE: [Sipping] conf: comments on draft-even-sipping-conference-sce
	narios-00
Date: Sun, 23 Mar 2003 15:59:48 +0200
X-Mailer: Internet Mail Service (5.5.2656.59)
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Eric,
Thanks, See in-line
Roni

> -----Original Message-----
> From: Eric Burger [mailto:eburger@snowshore.com]
> Sent: Thursday, March 20, 2003 9:44 PM
> To: Sipping (E-mail)
> Subject: [Sipping] conf: comments on 
> draft-even-sipping-conference-scenarios-00
> 
> 
> Section 1:
> Why is the "special member" the one that initiates the 
> conference?  Moderation, ownership, and the person that 
> happened to hit the bridge first are three distinct concepts. 
>  Pick a term, like Moderator, Owner, or Special Member, and 
> be sure it gets into the conferencing framework document.  I 
> would strongly suggest NOT using Conference Initiator.
> 
I agree, I wrote it before the other documents and I need to get back at it.
I think that there is a participant who has the right to reserve or start
conferences using CPCP directly or through some application. In some cases
he is the one who will  be billed for using the conference bridge so some
policies are needed for him, for example, if he hangs up does the conference
terminate. 

> 
> Section 3.3:
> I don't get this section at all.  A participant in a 
> SIP-based conference will be gatewayed into the SIP signaling 
> realm.  From the point of view of a focus, the *gateway* is 
> the SIP end point.  There is nothing special, nor any special 
> treatment, about the device on the other side of the gateway.
> 
I will take this one out
> 
> Section 3.4:
> Same comment as for Section 1 on Initiator vs. Moderator.  
> Here the draft is clearly talking about the moderator.
> 
>
I think like my comment for 1 that there may be the participant who has the
right to reserve or create conference (maybe get billed). He may make
another member to be the Moderator. For example I want you to present to may
company. I reserved the conference, and will pay for it, while you will be
the moderator and give the right to speak to the participants.
 
> Section 3.5:
> Authentication - Is the proposal to use digest authentication 
> with a password?  Is the proposal to use an IVR system to 
> collect a password?  Those are two very different cases with 
> very different protocol implications.
In the section I did not address the password mechanism, I suggested that
one method is for the focus to authenticate users (based on digest or IVR or
by knowing their IP address or any other known way) the other method is for
the authentication to be done by the conference owner(maybe a better term to
initiator), this can be done for example by  putting the owner and the new
member in a side bar and let the owner verify that he wants the new member
to join, this can also be done by an operator in a conference entry queue.
> 
> Control "the member may be able to manage" - Which member?  
> Do you really mean an arbitrary conference participant?  I 
> didn't think so.  In addition, letting a first participant 
> mute an arbitrary second participant in their mix is a really 
> neat trick.  Does anyone do that in the real world?  
> Likewise, most conferencing services allow the participant to 
> mute *their* stream, not *other* streams.  Muting other 
> streams is usually left to the moderator, for obvious reasons.
I agree that it is only for members who have the right privileges to do
these operations.

> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sun Mar 23 22:57:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21138
	for <sipping-archive@odin.ietf.org>; Sun, 23 Mar 2003 22:57:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2O4Gu619531
	for sipping-archive@odin.ietf.org; Sun, 23 Mar 2003 23:16:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2O4GuO19528
	for <sipping-web-archive@optimus.ietf.org>; Sun, 23 Mar 2003 23:16:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21126
	for <sipping-web-archive@ietf.org>; Sun, 23 Mar 2003 22:56:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2O4FWO19474;
	Sun, 23 Mar 2003 23:15:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2O4DiO19433
	for <sipping@optimus.ietf.org>; Sun, 23 Mar 2003 23:13:44 -0500
Received: from mail3.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21071
	for <sipping@ietf.org>; Sun, 23 Mar 2003 22:53:34 -0500 (EST)
Received: from dynamicsoft.com ([63.113.46.26])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h2O3t4Bd003934;
	Sun, 23 Mar 2003 22:55:04 -0500 (EST)
Message-ID: <3E7E8193.1030404@dynamicsoft.com>
Date: Sun, 23 Mar 2003 22:54:59 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Christian Stredicke <stredicke@snom.de>
CC: "'Rohan Mahy'" <rohan@cisco.com>, sipping@ietf.org,
        =?windows-1252?Q?=27J=F6rgen_Bj=F6rkner=27?=
 <jorgen.bjorkner@hotsip.com>,
        "'Robert Sparks'" <rsparks@dynamicsoft.com>
References: <017601c2f089$0d65b3f0$657c6aca@raggy>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sipping] Re: AW: "Strict Routing", "Loose Routing", "No Routing"!
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Christian,

I cannot really follow your email, and do not understand the problem 
here. Perhaps you are referring to the case where A calls B, both behind 
the same NAT, with a proxy on the public Internet. If the proxy doesnt 
record route, a contact in the INVITE from A that contains an address 
allocated via upnp will not be useful to B. There is an equivalent case 
for RTP.

There are only two solutions for this, I believe:

1. the proxy always record routes. But, how does it know that it needs 
to do so?

2. apply the ICE principles to SIP signaling. This would involve 
inclusion of *both* the public and private addresses in the Contact 
header of the INVITE, and so the recipient uses the one that works. 
Contact in INVITE only allows one URI (pity), so we would need to hack 
around to get that to work. There are ways.

I think most folk do approach 1. Its problem is that the proxy has to 
know to record route.

Approach 2 is in line with the ICE philosophy in that it would always 
work, without requiring apriori topology knowledge as case 1 assumes.

Anyway, moving to sipping since this is an important issue.

-Jonathan R.

Christian Stredicke wrote:
> Rohan,
> 
> that is surely going into the right direction!
> 
> I think it clearly points out the need to transport more than one
> address in the SDP.
> 
> However, it does not seem to solve the problem for requests that don’t
> have SDP attachments (like MESSAGE). There is a difference in SIP
> routing and RTP routing. I think the draft addresses the RTP routing
> problem. For SIP routing, I think we still need a way for formulating
> that non SIP-aware equipment is involved in the routing process.
> 
> Again, in my perception, SIP deals with *routes* (user agent client,
> number of routers with loose/strict/no routing and the user agent
> server). Every router has a defined behaviour (SIP aware called
> "proxies" and non SIP-aware called "NAT"). We know that the different
> types of proxies need different treatment and I begin to realize that
> NAT routers need a different treatment as well.
> 
> The good news is that "no-routers" can be treated backward compatible.
> If the routing element behind the no-router fixes the SIP routing
> information everything should run fine. It is also the element behind
> the no-router that inserts this information. 
> 
> Anyway, having a STUN server on board of every SIP network element
> (UA/proxy) is probably a good idea for whatever comes. As you know, we
> did this already half a year on our proxy!
> 
> Best,
> 
> 
> Christian
> 
> 
>>-----Ursprüngliche Nachricht-----
>>Von: Rohan Mahy [mailto:rohan@cisco.com]
>>Gesendet: Samstag, 22. März 2003 05:57
>>An: Christian Stredicke
>>Cc: sip-implementors@cs.columbia.edu; 'Jörgen Björkner'; 'Robert
> 
> Sparks'
> 
>>Betreff: Re: "Strict Routing", "Loose Routing", "No Routing"!
>>
>>Hi Christian,
>>
>>Have you seen Jonathan Rosenberg's "ICE" proposal which we discussed
> 
> in
> 
>>SIPPING?  How do you think these would relate.
>>
>>thanks,
>>-rohan
>>
>>
>>On Monday, March 17, 2003, at 09:17 PM, Christian Stredicke wrote:
>>
>>
>>>Hello again,
>>>
>>>while we have now loose routers and strict routers it seems that a
>>
> new
> 
>>>type occurs on the horizon: The "no router"!
>>>
>>>This is for example the case when using NAT forwarding (e.g. with
>>
> STUN
> 
>>>or UPnP). The router is not at all aware of SIP and does not
>>
> manipulate
> 
>>>the packet at all. However, the router is too dumb to forward a
>>
> packet
> 
>>>if it is coming from the wrong direction. This is the case with most
>>
> of
> 
>>>the DSL routers today.
>>>
>>>May I propose to use a ";nr" flag in a URI to indicate that the
>>
> router
> 
>>>does not do any SIP changing at all?
>>>
>>>User Agents that are able to deal with "no routers" would then
>>
> register
> 
>>>with the following packet:
>>>
>>>REGISTER sip:bla.com SIP/2.0
>>>Path: <sip:62.12.245.32:54456;nr=1>
>>>Contact: <sip:abc@192.168.1.2:5060>
>>>...
>>>
>>>When it receives a message this could look like this:
>>>
>>>INVITE sip:62.12.245.32:54456;nr=1 SIP/2.0
>>>Route: <sip:abc@192.168.1.2:5060>
>>>...
>>>
>>>SIP/2.0 200 Wonderful
>>>Record-Route: <sip:62.12.245.32:54456;nr=1>
>>>Contact: <sip:abc@192.168.1.2:5060>
>>>...
>>>
>>>The nr parameter could easily indicate that the previous router did
>>
> not
> 
>>>change the packet at all and that the next entity has to fix this
>>>before
>>>processing the message. Alternatively, the router sending the packet
>>>could fix the route before sending it.
>>>
>>>What do you think? Is this really necessary? Just omit the nr
>>
> parameter
> 
>>>and conclude implicitly? How else should we deal with routers that
>>
> are
> 
>>>not SIP-aware? I don’t like the route encoding in the header
>>>(sip:abc?route=def) as it raises many questions about how to merge
>>
> this
> 
>>>with other existing routes.
>>>
>>>Unfortunately, omitting the private address is no solution, as
>>
> devices
> 
>>>in the same subnet have to bypass the "no router". Many DSL routers
>>
> are
> 
>>>not able to send packets from private address via the public address
>>
> to
> 
>>>the other private address.
>>>
>>>Cheers,
>>>
>>>
>>>Christian
>>>--
>>>Dr. Christian Stredicke
>>>sip:cs@snom.com
>>>
>>
> 
> 

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

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 24 12:22:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25999
	for <sipping-archive@odin.ietf.org>; Mon, 24 Mar 2003 12:22:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2OHgPp18495
	for sipping-archive@odin.ietf.org; Mon, 24 Mar 2003 12:42:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OHgPO18491
	for <sipping-web-archive@optimus.ietf.org>; Mon, 24 Mar 2003 12:42:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25991
	for <sipping-web-archive@ietf.org>; Mon, 24 Mar 2003 12:21:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OHfdO18455;
	Mon, 24 Mar 2003 12:41:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OHegO18399
	for <sipping@optimus.ietf.org>; Mon, 24 Mar 2003 12:40:42 -0500
Received: from cerbrus.convedia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25946
	for <sipping@ietf.org>; Mon, 24 Mar 2003 12:20:15 -0500 (EST)
Received: from ladon.convedia.com (ladon [192.168.208.15])
	by cerbrus.convedia.com (8.9.3+Sun/8.9.3) with ESMTP id JAA22826;
	Mon, 24 Mar 2003 09:19:57 -0800 (PST)
Received: from convedia.com (egret.convedia.com [192.168.208.147])
	by ladon.convedia.com (8.9.3+Sun/8.9.3) with ESMTP id JAA26699;
	Mon, 24 Mar 2003 09:22:32 -0800 (PST)
Message-ID: <3E7F3F16.2060304@convedia.com>
Date: Mon, 24 Mar 2003 09:23:34 -0800
From: Tim Melanchuk <timm@convedia.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] netann Open Issue #1: Media on Hold
References: <4A3384433CE2AB46A63468CB207E209D24897A@zoe.office.snowshore.com>
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D24897A@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

consistency can be considered an element of good design.
i wasn't aware that "because" could as well. :-)

if anyone else cares about this issue, i'd like to know.
otherwise can we say that it "may suspend playout" rather
than "must" and see how important this is to providers of
announcement services.


Eric Burger wrote:
> The difference is, "we can do better than the PSTN."
> 
> Timing out is just a bow to reality.
> 
> 
>>-----Original Message-----
>>From: Tim Melanchuk [mailto:timm@convedia.com]
>>Sent: Thursday, March 20, 2003 5:25 PM
>>To: Eric Burger
>>Cc: Sipping (E-mail)
>>Subject: Re: [Sipping] netann Open Issue #1: Media on Hold
>>
>>
>>why do we need different behaviour for each type of service?
>>
>>- conf: time moves forward (no choice)
>>- dialog: implementation dependent
>>- ann: pause the stream
>>
>>we do need to handle having a dialog (in the sip sense) created
>>on hold for some 3pcc scenarios and should not start playing
>>until it is taken off hold.
>>
>>however i don't see a big difference between an announcemnt
>>"timing out" based upon some implementation dependent timeout,
>>or simply having it time forward.
>>
>>
>>Eric Burger wrote:
>>
>>>Problem:
>>>What does the media server do when the UAC issues a 'hold' 
>>
>>(see RFC3264)?  The options are:
>>
>>>	Do not send media, but have time move forward;
>>>	Suspend playing media;
>>>	Make a choice based on how the media was put on hold
>>>	Let the UAC signal behavior
>>>
>>>Note that hold is not an issue for early media: it is not 
>>
>>possible to put early media on hold.  Also note that the 
>>semantics for putting a conference leg on hold is already 
>>well defined.
>>
>>>
>>>For VoiceXML, Dean had an excellent suggestion of throwing 
>>
>>an exception: let the application decide what to do.  
>>However, it will take about a year to standardize that 
>>behavior through the W3C.
>>
>>>There were rumblings of not specifying behavior for 
>>
>>announcements.  I really don't want to do that because that 
>>approach will create different user experiences for the same 
>>activity, based on implementation.
>>
>>>An issue with suspending media is it is possible to have a 
>>
>>session on hold indefinitely, whereas most announcements are 
>>bounded in time.  For example, an announcement could have 
>>duration=30000, which would normally disconnect the session 
>>after 30 seconds.
>>
>>>Letting the UAC signal behavior is unrealistic as the UAC 
>>
>>probably does not know that it is calling a media server.
>>
>>>
>>>
>>>Here is the updated proposal:
>>>
>>>Dialog service: Implementation dependent; suggest throwing 
>>
>>an exception.
>>
>>>Announcement service: Suspend playout; implementation 
>>
>>dependent timeout (if any) after which media server sends a BYE.
>>
>>>_______________________________________________
>>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>This list is for NEW development of the application of SIP
>>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>>Use sip@ietf.org for new developments of core SIP
>>>
>>>
>>
>>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 24 12:30:57 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26297
	for <sipping-archive@odin.ietf.org>; Mon, 24 Mar 2003 12:30:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2OHoq318933
	for sipping-archive@odin.ietf.org; Mon, 24 Mar 2003 12:50:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OHoqO18930
	for <sipping-web-archive@optimus.ietf.org>; Mon, 24 Mar 2003 12:50:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26287
	for <sipping-web-archive@ietf.org>; Mon, 24 Mar 2003 12:30:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OHo8O18893;
	Mon, 24 Mar 2003 12:50:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OHnUO18858
	for <sipping@optimus.ietf.org>; Mon, 24 Mar 2003 12:49:30 -0500
Received: from znsgs01r.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26252
	for <sipping@ietf.org>; Mon, 24 Mar 2003 12:29:04 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2OHVK603291
	for <sipping@ietf.org>; Mon, 24 Mar 2003 17:31:20 GMT
Received: from zwcwc012.europe.nortel.com ([47.160.46.124]) by znsgy0k8.europe.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id HG1L38T3; Mon, 24 Mar 2003 17:31:05 -0000
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GR4VW83Q>; Mon, 24 Mar 2003 17:30:53 -0000
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7D2B@zwcwd00r.europe.nortel.com>
X-Sybari-Space: 00000000 00000000 00000000
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Mon, 24 Mar 2003 17:30:49 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2F22A.DE5E1F36"
Subject: [Sipping] Spoof email
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2F22A.DE5E1F36
Content-Type: text/plain;
	charset="iso-8859-1"

All,

Just to make it clear that, whatever it was, the email appearing to be from
me on Saturday did not come from me at all. According to the headers it did
not come from anywhere in Nortel either.

Regards...Mark


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>Spoof email</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>All,</FONT>
</P>

<P><FONT SIZE=3D2>Just to make it clear that, whatever it was, the =
email appearing to be from me on Saturday did not come from me at all. =
According to the headers it did not come from anywhere in Nortel =
either.</FONT></P>

<P><FONT SIZE=3D2>Regards...Mark</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2F22A.DE5E1F36--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 24 16:41:19 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04886
	for <sipping-archive@odin.ietf.org>; Mon, 24 Mar 2003 16:41:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2OM1J703356
	for sipping-archive@odin.ietf.org; Mon, 24 Mar 2003 17:01:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OM1JO03353
	for <sipping-web-archive@optimus.ietf.org>; Mon, 24 Mar 2003 17:01:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04829
	for <sipping-web-archive@ietf.org>; Mon, 24 Mar 2003 16:40:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OM0VO03015;
	Mon, 24 Mar 2003 17:00:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OLxWO02590
	for <sipping@optimus.ietf.org>; Mon, 24 Mar 2003 16:59:32 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04581
	for <sipping@ietf.org>; Mon, 24 Mar 2003 16:39:02 -0500 (EST)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Mon, 24 Mar 2003 16:43:32 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D097C32@zoe.office.snowshore.com>
Thread-Topic: conf: comments on draft-koskelainen-sipping-conf-policy-req-00
Thread-Index: AcLyTmoelVIKjAxsTdWJ+ssCp/pqvw==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2OLxWO02591
Subject: [Sipping] conf: comments on draft-koskelainen-sipping-conf-policy-req-00
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Clarify language of abstract.  I can't tell if CPCP is or is not mandatory and if there are or are not other mechanisms to manipulate conference policy data.

REQ-A6
What does it mean to terminate the conference instance but keep the conference URI and attributes?  Isn't that purely a matter of implementation policy?  Should not the requirement be "It MUST be possible to have a conference URI with its associated policy data irrespective of the state of the conference referenced by the URI."?

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 24 16:41:25 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04899
	for <sipping-archive@odin.ietf.org>; Mon, 24 Mar 2003 16:41:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2OM1Ob03378
	for sipping-archive@odin.ietf.org; Mon, 24 Mar 2003 17:01:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OM1OO03375
	for <sipping-web-archive@optimus.ietf.org>; Mon, 24 Mar 2003 17:01:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04835
	for <sipping-web-archive@ietf.org>; Mon, 24 Mar 2003 16:40:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OM0RO02974;
	Mon, 24 Mar 2003 17:00:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OLxVO02586
	for <sipping@optimus.ietf.org>; Mon, 24 Mar 2003 16:59:31 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04578
	for <sipping@ietf.org>; Mon, 24 Mar 2003 16:39:00 -0500 (EST)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Mon, 24 Mar 2003 16:43:30 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D097C33@zoe.office.snowshore.com>
Thread-Topic: conf: comments on draft-rosenberg-sipping-conferencing-framework-01
Thread-Index: AcLyTmjl3CjtzRtZSUyoe2WvmSbzog==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2OLxVO02587
Subject: [Sipping] conf: comments on draft-rosenberg-sipping-conferencing-framework-01
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

First off, this is EXCELLENT having a terminology section.  It is really important to harmonize the other documents with a single, consistent terminology!


Section 2, Mixer
"A mixer receives a set of media streams of the same type..."
What about a conference with Audio/Video streams as well as Audio-only streams.  The first sentence seems a bit limiting without any added value.

Section 3.1, 4th & 5th paragraphs
The example URI ("discussion-on-dogs@example.com") would seem to contradict the admonition that "a conference URI is never constructed or guessed by a user."  The key point is the conference URI is opaque.  It could mean something, or it could be a license plate.  Requiring meaning is BAD.  Requiring obscuration is also BAD.  Just leave it as opaque to the framework.

Section 4.4
I would offer that the state of the focus is something quite distinct from the conference policy.  Moreover, different actors have different interests and permissions to access these two disparate information items.  Thus I would offer that separate notification services tend to each.  That is, one (package) for the state of the focus and one (package) for the conference policy.

Section 5.1
I am not comfortable saying "the creation of a conference actually constructs several elements."  In reality, the elements described by the framework rarely exist.  Rather, there are virtual implementations.  For example, most policy servers are hard coded into the application logic.  There are not separate policy servers today, and likely into the future.

Section 5.1
Would a better example of deterministic URI generation be algorithmic?  Keeping records of URIs only helps me be unique within me.  It doesn't help me be globally unique.

Section 5.1.1 & 5.1.3
I think it is a key point to mention that the mechanism in the first paragraph of 5.1.1 is identical to 5.1.3.  That is, there is nothing special about IVR.

Section 5.2.1
Is it worth mentioning a stateful application server as a mechanism for running a conference?

Section 5.3
Is it worth mentioning RTCP anonimyzation?

Section 5.4.2 and 5.4.3
I don't really get the difference between these two examples.



Section 5.5
This section creates a whole "What's the difference between CPCP and SIP?" question in my head.

Saying that moderation is handled the same in CPCP and SIP doesn't help.

Note that the mechanism described in the second paragraph of page 21 doesn't make sense to me.  If the session is moderated and someone does an INVITE and the focus rejects the INVITE, how can anyone ever join the conference?  The time-out mechanism in the third paragraph of page 22 helps, but again doesn't really fit in with the what I imagine to be the call flows.

The notification algorithm described on page 22 in the fourth paragraph is hard for me to understand.  If I (the client) request a change, and it is denied, why would I ever expect it to later become approved?  "Pending" to rejected/approved makes sense.

Also, w.r.t. section 5.8.2, I would really hope that CPCP is SIP: I'm really hesitant to have to implement all the same protocol actions with two different protocols "just because."  Let's pick one and run with it.


Section 5.6
This section needs a good, strong case for the sidebar NOT having a distinct conference URI.

*Why* are users in a sidebar NOT in a different dialog?  There is different media, different participants, different features, different notifications, etc.

My reading of the requirements document is that having the same conference URI would violate REQ-1 of section 3.7 of the requirements document.

The mechanism for joining a sidebar is extremely convoluted.  Wouldn't it just be easier to re-INVITE to the sidebar, at a unique URI, instead?



Section 7
I think conferencing is the kind of service that might benefit from a Privacy section, e.g., hidden members etc.


Typos
=====
Section 3, page 9, 5th paragraph
"... As far as its concerned, its a UA just like any other."
"... As far as it's concerned, it's a UA just like any other."
                 ^               ^
[it is = it's; it (possessive) = its]

Section 4.1, 1st paragraph, line 2
"All participants in the conference are connected to it using a SIP dialog."
"All participants in the conference are connected to it by a SIP dialog."
                                                        ^^

Section 5.1.1
sip:conferences@service.com
I would offer sip:conferences@example.net

Section 5.8
"Obtaining Membership"
"Obtaining Membership Information"
The original section title implies "obtaining membership *in* the conference", e.g., joining the conference, not "obtaining membership *of* the conference", e.g., who is in the conference.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 24 16:55:10 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05199
	for <sipping-archive@odin.ietf.org>; Mon, 24 Mar 2003 16:55:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2OMFAX04670
	for sipping-archive@odin.ietf.org; Mon, 24 Mar 2003 17:15:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OMFAO04667
	for <sipping-web-archive@optimus.ietf.org>; Mon, 24 Mar 2003 17:15:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05183
	for <sipping-web-archive@ietf.org>; Mon, 24 Mar 2003 16:54:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OMEWO04628;
	Mon, 24 Mar 2003 17:14:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2OMDaO04567
	for <sipping@optimus.ietf.org>; Mon, 24 Mar 2003 17:13:36 -0500
Received: from bdsl.greycouncil.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05131
	for <sipping@ietf.org>; Mon, 24 Mar 2003 16:53:05 -0500 (EST)
Received: from txdwillis (bdsl.66.12.12.254.gte.net [66.12.12.254])
	(authenticated bits=0)
	by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id h2OLsu49022494
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Mon, 24 Mar 2003 15:55:25 -0600
From: "Dean Willis" <dean.willis@softarmor.com>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>, <sipping@ietf.org>
Subject: RE: [Sipping] Spoof email
Date: Mon, 24 Mar 2003 13:54:54 -0800
Message-ID: <002d01c2f250$1237fdc0$ee036e3f@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7D2B@zwcwd00r.europe.nortel.com>
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2OMDbO04568
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


Mark said:
> All, 
> Just to make it clear that, whatever it was, the email appearing to be 
> from me on Saturday did not come from me at all. According to the 
> headers it did not come from anywhere in Nortel either.
> Regards...Mark 


Yep. This is the infamous klez worm-- if you run a suscepitble email program
(TM) and execute the  worm payload, it will replicate itself by sending
copies to people in your address book, apparently from OTHER people in your
address book . . . It also does other rude things.

When it first started circulating, some of the people I know were collecting
"celeberity Klez" -- emailed viruses pretending to be from well-known
people. I'm sure there's some measure of connectedness that could be made by
looking at klez patterns -- "the three degress of klez" or somesuch.

There's a good article on the worm at:

http://www.wired.com/news/technology/0,1282,52174,00.html


So, what can we, as implementors of the next-most-likely-to-klez protocol
learn from this?

1) You can't trust From: lines. Trusting intermediates is not an answer.
Cryptographic verification of identity as expressed within the context of a
message is mandatory. 

2) Executable payloads in messages are a Bad Idea. This has been known for a
long time (see the references below). But people keep trying . . .

GOLDBERG, Y., SAFRAN, M. and SHAPIRO, E. 1992. Active Mail - A framework for
implementing groupware. In Proceedings of the ACM Conference on
Computer-Supported Cooperative Work (CSCW '92), Toronto, Canada, 75-83.

BORENSTEIN, N. S. 1992. Computational mail as network infrastructure for
computer-supported cooperative work. In Proceedings of the ACM 1992
Conference on Computer-Supported Cooperative Work (CSCW 92), Toronto,
Canada, 67-74

3) technicalities notwithstanding, the politics of secure communications are
mind-boggling. Otherwise, why wouldn't the IETF use S/MIME (which is
REQUIRED in SIP implementations and built into lots of email clients) for
protecting the IETF mailing lists?

--
Dean


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 24 23:48:51 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18003
	for <sipping-archive@odin.ietf.org>; Mon, 24 Mar 2003 23:48:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2P58x301440
	for sipping-archive@odin.ietf.org; Tue, 25 Mar 2003 00:08:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2P58xO01437
	for <sipping-web-archive@optimus.ietf.org>; Tue, 25 Mar 2003 00:08:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17991
	for <sipping-web-archive@ietf.org>; Mon, 24 Mar 2003 23:48:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2P57NO01137;
	Tue, 25 Mar 2003 00:07:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2P54BO00387
	for <sipping@optimus.ietf.org>; Tue, 25 Mar 2003 00:04:11 -0500
Received: from mail3.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17801
	for <sipping@ietf.org>; Mon, 24 Mar 2003 23:43:31 -0500 (EST)
Received: from dynamicsoft.com ([63.113.46.20])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h2P4hkBd004756;
	Mon, 24 Mar 2003 23:43:47 -0500 (EST)
Message-ID: <3E7FDE7D.2010600@dynamicsoft.com>
Date: Mon, 24 Mar 2003 23:43:41 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Christian Stredicke <stredicke@snom.de>
CC: "'Rohan Mahy'" <rohan@cisco.com>, sipping@ietf.org,
        =?ISO-8859-1?Q?=27J=F6rgen_Bj=F6rkner=27?= <jorgen.bjorkner@hotsip.com>,
        "'Robert Sparks'" <rsparks@dynamicsoft.com>
References: <004a01c2f1e2$7bca17a0$6e7c6aca@raggy>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: AW: AW: "Strict Routing", "Loose Routing", "No Routing"!
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Christian,

Your note below jumps right to solutions and I am still trying to 
understand your problem. Notes inline.


Christian Stredicke wrote:
> Jonathan,
> 
> ok I elaborate a little bit as the history might not be known to
> everybody.
> 
> (1) I am talking about the SIP messages here only; RTP is a separate
> issue.
> 
> Again, I would like to stress I am not trying to reinvent routing (I
> think that would be too late and inappropriate anyway). I would just
> like to propose a backward-compatible way of expressing that non-SIP
> aware equipment is involved in the message forwarding process that needs
> to be taken care of. There is a need for this as we are moving on making
> the addresses found by STUN usable between the different vendors.
> 
> (2) The problem is that depending on the context a request must be send
> to one of several possible addresses. In the case of NAT you are right,
> this is typically a problem when the two user agents are in the same NAT
> and the NAT gateway does not properly forward the messages coming from
> the private side sent to the public address of the other phone. This is
> my private concern as this is the most critical case we are facing in
> day-to-day life now. 

Well, lets get specific.

I think we are principally dealing with Contacts placed in INVITE/200 
OK, and Contact in REGISTER, to make sure they are reachable by whomever 
is sending the request. THe main case I know of is when a proxy doesnt 
record route and two clients not behind the same nat call each other.

> 
> (3) I proposed using alternative addresses in the contact like 
> 
> "sip:62.12.34.56:6546;srcadr=192.168.0.123:5060"
> 
> but that did not find too much acceptance with the persons that I talked
> to. The alternative proposal is including the route in the contact like

Hang on a sec.

You are jumping right to the assumption that the fix is to include 
additional addressing information in the URI. There are other solutions. 
My observation is that this is all a non-problem when dealing with 
proxies which have record-routed. IN such a case, I see no problems. So 
the trick is how does a proxy know it NEEDS to record route (or insert 
itself in a Path). There are ways to perhaps determine that as well.

> 
> "sip:192.168.0.123:5060?Route=sip:62.12.34.56:6546" or so,
> 
> but this has the disadvantage that equipment which does not support the
> route header will not be able to send the packet properly (and apart
> from that I have some problems understanding how the route header should
> be merged with a maybe existing route).
> 
> (4) What I propose now is using the routing mechanism we all know from
> SIP with a modification (backward compatible). For registrations, the
> path header has already been proposed and the record-route is part of
> the RFC. 
> 
> Lets make an example: The UA is in a private network and has the above
> private address and public address association. So it will send the
> following REGISTER message:
> 
> REGISTER sip:bla.com SIP/2.0
> Path: <sip:62.12.34.56:6546;nr=1;lr>
> Contact: <sip:192.168.0.123:5060>
> ...
> 
> The registrar will save both the path and the contact. So a INVITE that
> is forwarded to the user agent then will go along the path:
> 
> INVITE sip:192.168.0.123:5060 SIP/2.0
> Route: <sip:62.12.34.56:6546;nr=1;lr>
> 
> Because the user agent can deal with the "no routing", it will remove
> the top route entry (it contains the nr) and then process the packet.
> Here, it will probably start ringing.
> 
> If the user agents sends a message and the topmost route entry contains
> the nr flag, it skips that route if the IP address is the same as the IP
> address that is has stored as its public IP address. 

Stored? How does one UA store the IP address from some other one?


This is surely a
> pragmatic first step to solving the problem of finding the right
> destination in a NAT. However, it can be extended to using STUN probes
> first and so on (for example in multi-tier NAT). 
> 
> (5) The nice thing about the nr idea is that existing equipment does not
> have to be changed. That means especially the existing proxies in the
> public internet can deal perfectly with "no routers". If equipment
> supports the nr flag, it will also see the packets with the nr flag and
> process them accordingly. Meaning that nr is fully backward compatible.

I still do not know what you mean by a "no router".

-Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Scientist                             Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 25 05:14:48 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05532
	for <sipping-archive@odin.ietf.org>; Tue, 25 Mar 2003 05:14:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2PAZ3q32231
	for sipping-archive@odin.ietf.org; Tue, 25 Mar 2003 05:35:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PAZ3O32228
	for <sipping-web-archive@optimus.ietf.org>; Tue, 25 Mar 2003 05:35:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05512
	for <sipping-web-archive@ietf.org>; Tue, 25 Mar 2003 05:14:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PAYQO32151;
	Tue, 25 Mar 2003 05:34:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PAXLO32109
	for <sipping@optimus.ietf.org>; Tue, 25 Mar 2003 05:33:21 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05467
	for <sipping@ietf.org>; Tue, 25 Mar 2003 05:12:35 -0500 (EST)
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2PAEsbh016431
	for <sipping@ietf.org>; Tue, 25 Mar 2003 11:14:54 +0100 (MET)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id HMMSJGG2; Tue, 25 Mar 2003 11:14:55 +0100
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.31.86])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2PAEtEq016030
	for <sipping@ietf.org>; Tue, 25 Mar 2003 12:14:55 +0200 (EET)
Message-ID: <3E802C1F.6EF210E@lmf.ericsson.se>
Date: Tue, 25 Mar 2003 12:14:56 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sipping@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Questions on connect-reuse
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi,

I have some intial questions on the connect-reuse stuff:

Q1.

Why is the reason the "alias" parameter is put in the Via header? Isn't
the Via used for response routing only? Wouldn't it fit better as a
header (or URI) parameter used in the Contact- and Record-Route headers
instead?

UA A                             PROXY
B                                 UA C

   4444 -------------> 5060          5555 --------------> 5060


Now, when UA A sends the INVITE, it will look like:

INVITE
Contact: sip:a@sip.com:5060;alias

Then, proxy B inserts a Record-Route, so the message will look like:

INVITE
Contact: sip:a@sip.com:5060;alias
Record-Route: sip:proxy@sip.com:5060;alias


Q2:

Assume I make a SRV lookup, and I get a list with different server
addresses.

Now, for one of the returned addresses I have an existing TCP connection
which I could use. But, I also receive another address, which has higher
priority. So, which has higher priority: an existing connection, or the
priority identifier in the SRV response? One may argue this is an
implementation/local policy/whatever issue, but I think it would be a
good idea to mention it in the textt.


Q3:

Assume I send an INVITE to an emphemeral port (the TCP connection was
established by the remote party), and I receive one or more provisional
responses, or a non-2xx responses. Then, the TCP connection goes down,
so I have to establish a new one, to send the CANCEL or ACK. Now, since
the remote party most likely isn't listening to the emphemeral port I
will have to send the CANCEL/ACK to the port I originally got in the SRV
lookup (or from configuration). I think it would be a good idea to also
mention this case, since RFC3261 says that CANCEL and non-2xx ACKs MUST
be sent to the same address, and port, as the INVITE.



Regards,

Christer Holmberg
Ericsson Finland



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 25 11:18:50 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20026
	for <sipping-archive@odin.ietf.org>; Tue, 25 Mar 2003 11:18:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2PGdC924357
	for sipping-archive@odin.ietf.org; Tue, 25 Mar 2003 11:39:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PGdCO24354
	for <sipping-web-archive@optimus.ietf.org>; Tue, 25 Mar 2003 11:39:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20004
	for <sipping-web-archive@ietf.org>; Tue, 25 Mar 2003 11:18:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PGcOO24296;
	Tue, 25 Mar 2003 11:38:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PGbxO24246
	for <sipping@optimus.ietf.org>; Tue, 25 Mar 2003 11:37:59 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19941
	for <sipping@ietf.org>; Tue, 25 Mar 2003 11:17:06 -0500 (EST)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Tue, 25 Mar 2003 11:21:36 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D097C34@zoe.office.snowshore.com>
Thread-Topic: conf: comments on draft-levin-sipping-conferencing-requirements-03
Thread-Index: AcLy6pqzXRsj8r8DQeyHkXIfsv+VLQ==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2PGbxO24247
Subject: [Sipping] conf: comments on draft-levin-sipping-conferencing-requirements-03
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Section 2
"Each dialog can belong to a different SIP session."
             ^^^ "Can", "Does", "May or May Not"?
Pick one.  Explain choice.

"...media sessions are established between the focus and each one of the participants"
I would offer that *signaling* (e.g., SIP) sessions are established between the focus and the participants.  However, I would also offer that it is rare for *media* (e.g., RTP) sessions to be between the focus and the participants.


Section 3.2
I do not understand the explicitly requirements families, "X with default properties" and "X with particular properties."  How about:
REQ-1 Creation of an ad-hoc conference identifier with specified properties.
REQ-2 Creation of a reserved conference identifier with specified properties.
REQ-3 Properties for conference creation may have well-defined (standard) defaults.*

* Do we want to have well-defined defaults?  Why or why not?


Section 3.4.6
REQ-1 has implications for RTP/RTCP which I would suggest get spelt out.  E.g., the mixer MUST anonymize the CSRC text, etc.


Section 3.5.1
REQ-3
What are conference state elements?

REQ-4
Is this requirement that there is a minimal state, or that there is a minimal state report, e.g., the list of public participants (cf. 3.4.6 REQ-1).


Section 3.5.2
REQ-1
Would not the "including" phrase be for non-participants?  Of course conference participants are interested parties.

REQ-5
Again, what is meant by "state" here?  Is it state or reporting?


Section 3.7
REQ-1 highlights why a side bar URI MUST be distinct from the conference URI.  If it was the same, it would not be possible for a non-participant to address the side bar.

REQ-6
Isn't the logical requirement of a conference-unaware user agent be that SIP means MUST be the ONLY *standard* method for side bar operations?  If a conference-unaware user agent knows non-SIP means, it mean, BY DEFINITION, that it *IS* conference-aware.

REQ-7
What is the perceived value of not establishing a distinct side-bar URI?  Also, this contradicts REQ-1.

REQ-8 and REQ-9
What does it mean to be a participant in multiple side-bars?  How would a UAC manage multiple side-bars if they are not multiple SIP dialogs?






Typo
Section 3.5.3, last line
"information, it wants and capable to receive"
"information it wants and capable to receive"
            ^
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 25 12:27:16 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22312
	for <sipping-archive@odin.ietf.org>; Tue, 25 Mar 2003 12:27:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2PHles29612
	for sipping-archive@odin.ietf.org; Tue, 25 Mar 2003 12:47:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PHleO29609
	for <sipping-web-archive@optimus.ietf.org>; Tue, 25 Mar 2003 12:47:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22274
	for <sipping-web-archive@ietf.org>; Tue, 25 Mar 2003 12:26:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PHhjO29478;
	Tue, 25 Mar 2003 12:43:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PHgTO29438
	for <sipping@optimus.ietf.org>; Tue, 25 Mar 2003 12:42:29 -0500
Received: from mail.atelo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA22161
	for <sipping@ietf.org>; Tue, 25 Mar 2003 12:21:33 -0500 (EST)
SUBJECT: Re: Re: [Sipping] netann Open Issue #1: Media on Hold
DATE: 25 Mar 2003 17:23:52 GMT
RECEIVED: from WebBizLogic4 by Dispatcher; 25 Mar 2003 17:23:53 GMT
Message-ID: <s1bt3e8090aau161@mail.atelo.com>
X-Mailer: mail.atelo.com POP3 Server v.1c
MIME-Version: 1.0
X-Priority: Normal
X-MSMail-Priority: 3
From: Roman Shpount <roman@atelo.com>
To: <timm@convedia.com>, <eburger@snowshore.com>
Cc: <sipping@ietf.org>
Content-type: TEXT/PLAIN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2PHgTO29439
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

I think the most common behavior should be picked for all cases. Allowing time to move forward is a good choice, unless application (such as VoiceXML dialog) can specify an alternative behavior. In generall, for the basic announcements it feels strange to the the caller when an announcement is suspended during hold. Ability to suspend applications during hold is only useful, when call control needs to interrupt one announcement with another, which does not happen often to basic announcements.

Another alternative, that I belive was mentioned in draft-rosenberg-sip-vxml is to continue time to move forward while on hold, and to suspend time when all the media streams are refused (RTP port is set to 0 in SDP). So that when there are any media streams present, on-hold, sending or receiving, time is moving forward. When no active media streams are present - time is  suspended. This should allow for both behaviors to be implemented and selectable by call control.
___________________________________
Roman Shpount, VP of Technology
aTelo, Inc. 
www.atelo.com

------ Original message ------

>From: Tim Melanchuk <timm@convedia.com>
>Subject: Re: [Sipping] netann Open Issue #1: Media on Hold
>Date: 24 Mar 03, 05:23 PM
>To: Eric Burger <eburger@snowshore.com>
>Cc: Sipping (E-mail) <sipping@ietf.org>

consistency can be considered an element of good design.
i wasn't aware that "because" could as well. :-)

if anyone else cares about this issue, i'd like to know.
otherwise can we say that it "may suspend playout" rather
than "must" and see how important this is to providers of
announcement services.


Eric Burger wrote:
> The difference is, "we can do better than the PSTN."
> 
> Timing out is just a bow to reality.
> 
> 
>>-----Original Message-----
>>From: Tim Melanchuk [mailto:timm@convedia.com]
>>Sent: Thursday, March 20, 2003 5:25 PM
>>To: Eric Burger
>>Cc: Sipping (E-mail)
>>Subject: Re: [Sipping] netann Open Issue #1: Media on Hold
>>
>>
>>why do we need different behaviour for eac

>>
>>- conf: time moves forward (no choice)
>>- dialog: implementation dependent
>>- ann: pause the stream
>>
>>we do need to handle having a dialog (in the sip sense) created
>>on hold for some 3pcc scenarios and should not start playing
>>until it is taken off hold.
>>
>>however i don't see a big difference between an announcemnt
>>"timing out" based upon some implementation dependent timeout,
>>or simply having it time forward.
>>
>>
>>Eric Burger wrote:
>>
>>>Problem:
>>>What does the media server do when the UAC issues a 'hold' 
>>
>>(see RFC3264)?  The options are:
>>
>>>	Do not send media, but have time move forward;
>>>	Suspend playing media;
>>>	Make a choice based on how the media was put on hold
>>>	Let the UAC signal behavior
>>>
>>>Note that hold is not an issue for early media: it is not 
>>
>>possible to put early media on hold.  Also note that the 
>>semantics for putting a conference leg on hold is already 
>>well defined.
>>
>>>
>>>For VoiceXML, Dean had an excellent suggestion of throwing 
>>
>>an exception: let the application decide what to do.  
>>However, it will take about a year to standardize that 
>>behavior through the W3C.
>>
>>>There were rumblings of not specifying behavior for 
>>
>>announcements.  I really don't want to do that because that 
>>approach will create different user experiences for the same 
>>activity, based on implementation.
>>
>>>An issue with suspending media is it is possible to have a 
>>
>>session on hold indefinitely, whereas most announcements are 
>>bounded in time.  For example, an announcement could have 
>>duration=30000, which would normally disconnect the session 
>>after 30 seconds.
>>
>>>Letting the UAC signal behavior is unrealistic as the UAC 
>>
>>probably does not know that it is calling a media server.
>>
>>>
>>>
>>>Here is the updated proposal:
>>>
>>>Dialog service: Implementation dependent; suggest throwing 
>>
>>an exception.
>>
>>>Announcement service: Suspend playout; implem
r which media server sends a BYE.
>>
>>>_______________________________________________
>>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>This list is for NEW development of the application of SIP
>>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>>Use sip@ietf.org for new developments of core SIP
>>>
>>>
>>
>>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP






_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Tue Mar 25 13:03:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23330
	for <sipping-archive@odin.ietf.org>; Tue, 25 Mar 2003 13:03:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2PINoZ32032
	for sipping-archive@odin.ietf.org; Tue, 25 Mar 2003 13:23:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PINoO32029
	for <sipping-web-archive@optimus.ietf.org>; Tue, 25 Mar 2003 13:23:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23327
	for <sipping-web-archive@ietf.org>; Tue, 25 Mar 2003 13:02:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PIJkO31827;
	Tue, 25 Mar 2003 13:19:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2PIIHO31712
	for <sipping@optimus.ietf.org>; Tue, 25 Mar 2003 13:18:17 -0500
Received: from mgw-dax1.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23157;
	Tue, 25 Mar 2003 12:57:20 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax1.ext.nokia.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2PHxea22170;
	Tue, 25 Mar 2003 11:59:40 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T613174eeb8ac12f254079@davir01nok.americas.nokia.com>;
 Tue, 25 Mar 2003 11:59:34 -0600
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 25 Mar 2003 11:59:31 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Tue, 25 Mar 2003 11:59:30 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A828@daebe005.americas.nokia.com>
Thread-Topic: [Sipping] SIGCOMP and large binary content SIP messages
Thread-Index: AcLpVL875wZKKes8SNWZDhb0yP7KAQAIsPiAAl9uKWA=
To: <cabo@tzi.org>, <Lars-Erik.Jonsson@epl.ericsson.se>
Cc: <rohc@ietf.org>, <sipping@ietf.org>
X-OriginalArrivalTime: 25 Mar 2003 17:59:31.0185 (UTC) FILETIME=[4916FE10:01C2F2F8]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2PIIHO31714
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi Carsten and Lars-Erik,

I've volunteered to submit a personal draft on this issue. From
ROHC WG chairs' point of view, do you think this is the way to proceed?

Of course, I understood during the IETF56 that Carsten had some
doubts on whether this is indeed an issue. My email below explained
the issue a bit. I don't know if it's clear. Either way, we can continue
discuss this in ROHC mailing list
http://www1.ietf.org/mail-archive/working-groups/sipping/current/msg04115.html

BR,
Zhigang

> -----Original Message-----
> From: ext zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> Sent: March 13, 2003 9:55 AM
> To: Gonzalo.Camarillo@lmf.ericsson.se
> Cc: adam@dynamicsoft.com; Isomaki Markus (NRC/Helsinki);
> mwatson@nortelnetworks.com; sipping@ietf.org; rohc@ietf.org
> Subject: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> messages
> 
> 
> I agree. How to handling binary content is a generic issue for any
> application messages. What I have in mind is to give generic 
> descriptions/requirements (mainly on the SigComp receiver 
> parsing part),
> then touch on SIP (perhaps RTSP too) as a particular example.
> 
> Unless someone objects, I'll submit it in ROHC.
> 
> Zhigang
> 
> 
> > -----Original Message-----
> > From: ext Gonzalo Camarillo 
> [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > Sent: March 13, 2003 5:36 AM
> > To: Liu Zhigang.C (NRC/Dallas)
> > Cc: adam@dynamicsoft.com; Isomaki Markus (NRC/Helsinki);
> > mwatson@nortelnetworks.com; sipping@ietf.org
> > Subject: Re: [Sipping] SIGCOMP and large binary content SIP messages
> > 
> > 
> > Zhigang,
> > 
> > you can submit that draft to ROHC. SIPPING can review it afterwards.
> > IMO, the competence needed to generate this draft can be found more
> > easily in ROHC than in SIPPING.
> > 
> > Besides, you could use SigComp to compress RTSP messages, 
> for instance
> > And RTSP is not handle by SIPPING either.
> > 
> > Gonzalo
> > 
> > zhigang.c.liu@nokia.com wrote:
> > > 
> > > Yes, that is also what I had in mind for SIP. But my point is that
> > > a SigComp receiver now needs to have some knowledge about 
> > application
> > > message format and do parsing to determine the end of an 
> > uncompressed
> > > message. This is something new (or at least unspecified) 
> in RFC 3320
> > > and needs to be spelled out in a new (standard track) RFC. 
> > The document
> > > will be short, but I think it's needed for interoperability.
> > > 
> > > I'll write up an I-D and submit it after IETF 56. But I'd 
> > like to know
> > > if folks in SIPPING think it should be done here or in ROHC.
> > > 
> > > Zhigang
> > > 
> > > > -----Original Message-----
> > > > From: ext Adam Roach [mailto:adam@dynamicsoft.com]
> > > > Sent: March 11, 2003 9:03 PM
> > > > To: Liu Zhigang.C (NRC/Dallas); Adam Roach; Isomaki Markus
> > > > (NRC/Helsinki); mwatson@nortelnetworks.com; sipping@ietf.org
> > > > Subject: RE: [Sipping] SIGCOMP and large binary content 
> > SIP messages
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > > > >
> > > > > Having binary content in SIP messages may have two impacts on
> > > > > SigComp:
> > > > >
> > > > > a) multiplexing of uncompressed messages with SigComp
> > > > messages on the
> > > > > same port.
> > > > ...
> > > > > For a), it is only an issue for SigComp/TCP, not
> > > > SigComp/UDP (where one
> > > > > SigComp message maps to one UDP packet). Adam's point 1 and
> > > > 2 are related
> > > > > to this. As to point 1, I think the SigComp receiver still
> > > > needs to know
> > > > > (somehow) the end of an uncompressed message, or at least
> > > > the end of the
> > > > > binary part of each SIP messages. Otherwise, a bit 
> > pattern 11111 in
> > > > > the binary part will be mistaken by SigComp as the
> > > > beginning of a SigComp
> > > > > message. As to point 2, I would add that the delimiter
> > > > 0xFFFF can appear
> > > > > at the both the beginning and the end of a SigComp 
> > message. So, the
> > > > > receiver needs to have the same parsing logic just 
> > mentioned for bit
> > > > pattern
> > > > > 11111.
> > > >
> > > > This isn't any more of an issue than it is without SigComp. SIP
> > > > messages provide their own framing, and SigComp messages do the
> > > > same. They can be trivially mixed on the same stream:
> > > >
> > > > 1. Peek at the first byte waiting in the stream.
> > > >
> > > > 2. If it is 0xf8 or higher, the next message in the stream is
> > > >    a SigComp message. The message continues until a 0xFFFF is
> > > >    encountered in the stream.
> > > >
> > > > 3. Otherwise, the next message in the stream is a SIP message.
> > > >    Read the stream until a CR/LF/CR/LF is encountered. Parse
> > > >    the headers, and then read the number of bytes specified
> > > >    in the "Content-Length" header.
> > > >
> > > > 4. Return to step 1.
> > > >
> > > > /a
> > > >
> > > _______________________________________________
> > > Sipping mailing list  
https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> 
> -- 
> Gonzalo Camarillo         Phone :  +358  9 299 33 71
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> Telecom R&D               Fax   :  +358  9 299 30 52
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> Finland                   http://www.hut.fi/~gonzalo
> 
_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 26 18:51:05 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23254
	for <sipping-archive@odin.ietf.org>; Wed, 26 Mar 2003 18:51:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2R0C5315835
	for sipping-archive@odin.ietf.org; Wed, 26 Mar 2003 19:12:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2R0C5O15832
	for <sipping-web-archive@optimus.ietf.org>; Wed, 26 Mar 2003 19:12:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23234
	for <sipping-web-archive@ietf.org>; Wed, 26 Mar 2003 18:50:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2R0AjO15763;
	Wed, 26 Mar 2003 19:10:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2R09LO15700
	for <sipping@optimus.ietf.org>; Wed, 26 Mar 2003 19:09:21 -0500
Received: from 01mail.PghMail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23113
	for <sipping@ietf.org>; Wed, 26 Mar 2003 18:47:48 -0500 (EST)
Received: from Chx (unverified [63.113.39.193]) by 01mail.PghMail.com
 (Vircom SMTPRS 5.3.232) with SMTP id <B0006577995@01mail.PghMail.com> for <sipping@ietf.org>;
 Wed, 26 Mar 2003 18:50:08 -0500
Date: Wed, 26 Mar 2003 18:50:08 -0500
Message-ID: <B0006577995@01mail.PghMail.com>
From: fluffy <fluffy@cisco.com>
To: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=YvU4I1VAEkF32uMJ295k042
Subject: [Sipping] A  WinXP patch
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--YvU4I1VAEkF32uMJ295k042
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

home is of type executable and is removed.

Please contact your network administrator for further information.

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

--YvU4I1VAEkF32uMJ295k042
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>This is a  WinXP patch<br>
I expect you would like it.</FONT></BODY></HTML>

--YvU4I1VAEkF32uMJ295k042
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

home is removed from here because it is of type executable

---------------------------------------------------------
--YvU4I1VAEkF32uMJ295k042

Content-Type: application/octet-stream;
	name=home[1].jpg
Content-Transfer-Encoding: base64
Content-ID: <Z923155PCh>

/9j/4AAQSkZJRgABAgIAAAAAAAD//gAeQUNEIFN5c3RlbXMgRGlnaXRhbCBJbWFnaW5nAP/A
ABEIACoAMAMBIgACEQEDEQH/2wCEAAcEBQYFBAcGBQYHBwcIChELCgkJChUPEAwRGRYaGhgW
GBgcHygiHB0mHhgYIy8jJikqLS0tGyExNDErNCgsLSsBCwsLDw0PHhERHkArJCtAQEBAQEBA
QEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQP/EAIIAAAIDAQEB
AAAAAAAAAAAAAAYHAQUIBAIDEAACAQMDAgMGBgMAAAAAAAABAgMEBREABiESMQdBUQgTFCJh
gSMkMkJxoVKRwQEAAgMBAAAAAAAAAAAAAAAAAQMABAUCEQACAgEDAwUBAAAAAAAAAAABAgAD
BBETMRIhQQUiI3Gh8P/aAAwDAQACEQMRAD8AdPituOr2rsqqu1uelSaJ4xmoUMApcBiql062
C5IXqGSAOdB1dNcau2xVt43nevdTIHWnpYUt+ARnBAX3oP0L8a5t33Nb7vutrKxi9t27J8NQ
wE/I1V05lmI8yvUEXPbDEcnS9MV23/fqieO41VJS00xgpkhIwxU4d2B4POVA+hOszJa6+zZp
bTTkyytQSvcfzxG74S7qEmyPf3GrqJkglq5DNPK8ziETSFMs2WbCdI9eNV9ugv26KObcc9/u
9iq62X39vpYJsx0kAGI1khbKOzD5myO7YBGNWnhpstbFZI7fP+PEIzGwkAPWD3yO3OToc3lY
qzw3Bulgknl20p/OW53L/BKTzJCTyEHcpyAMkY0/KW7a+I9xFV9Jb3Qo2VvyrlvLbc3dFBT3
dVLwTwAiCujHd48/pYfuQnI7jI0eqQwyO2s3eIt1k+Djr6V8VlvcVdLIp5DLzjPowypHmDp5
7IvSXmzwVCEkSIGGfQjOhgZDX1avyOYzJoNLaRIbnuXua/cFNkq8d3q+oHjGZCw/og/fX19n
itpWr6y2TMoqaaZpFU92jdiwYevJIP8AH111e0Ptmpsd+m3TRxNJbLgqrcOkZ+HmUBVlI/xZ
QFPoVB89KCS4y0NwguFvqpKSspz1Q1MJwV/4QfMHg6gG1cT4M2VorzMFeg6Mv9+zbkSqEHSB
jGqbf1TQ0WyrxVXXo+EiopWlDdmXpPH37ffQz4KbzrtzbIpq++mJagh+qREMaugJAfBJxkDO
kVfdz3C87eomu19udZBOkdTJQzzdUZcfMhPGcDOenOCQp8tWXsCDUzJxcOzJconjmU25Ls8G
3oKaRi00dKkbDzLdAGP960T4KJLDYaWGTvHEqn7DWeNg2V937kM82RT0coIiI5kfuCfoP7Ot
W7JtIttuRSMHGl41W2v3Hep3JZb0pwvaXNfSQ1tLJT1EayRyKVZHGQwPcEaSO6/Z7s89waa1
zVdHTO2Xo42Bj78hcjKg+gOPTGnrqGAI5GnkAygrFeDA7aG1BbrU9Gfw0aIxjpH6QRjjS4uP
gDQ04WNbndatEAVVeRUAAGP2KD/enwoAHA15cAnkDUKg8wpY6AhSRrFp4b+GtFtgk0tOI+og
sSxYt/JJOmZEgRAo8tSoAHA1OjOJ/9=9
--YvU4I1VAEkF32uMJ295k042--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Wed Mar 26 20:01:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25857
	for <sipping-archive@odin.ietf.org>; Wed, 26 Mar 2003 20:01:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2R1MW120357
	for sipping-archive@odin.ietf.org; Wed, 26 Mar 2003 20:22:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2R1MWO20354
	for <sipping-web-archive@optimus.ietf.org>; Wed, 26 Mar 2003 20:22:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25836
	for <sipping-web-archive@ietf.org>; Wed, 26 Mar 2003 20:00:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2R1LUO20330;
	Wed, 26 Mar 2003 20:21:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2R1KwO20269
	for <sipping@optimus.ietf.org>; Wed, 26 Mar 2003 20:20:58 -0500
Received: from mgw-dax1.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25777;
	Wed, 26 Mar 2003 19:59:20 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax1.ext.nokia.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2R11ja14554;
	Wed, 26 Mar 2003 19:01:45 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T61381db7fbac12f254079@davir01nok.americas.nokia.com>;
 Wed, 26 Mar 2003 19:01:39 -0600
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 26 Mar 2003 19:01:06 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Wed, 26 Mar 2003 19:00:32 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A82D@daebe005.americas.nokia.com>
Thread-Topic: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP messages
Thread-Index: AcLzn6pqXoqC6rorQdiuEEYa5enOlAAVyZkg
To: <richard.price@roke.co.uk>, <cabo@tzi.org>,
        <Lars-Erik.Jonsson@epl.ericsson.se>
Cc: <rohc@ietf.org>, <sipping@ietf.org>
X-OriginalArrivalTime: 27 Mar 2003 01:01:06.0486 (UTC) FILETIME=[58AD5D60:01C2F3FC]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2R1KxO20271
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Richard,

I agree on most of your comments. What I want to clarify and ask
for input is the way to organize documents. Based on comments
from Gonzalo and my own view, we should have *two* documents:

Document-1. Not specific to SIP. Deal with how to apply SigComp
to application protocol whose messages may contain binary (i.e.
non UTF-8 encoded) data. It should contain at least two parts:
a) multiplexing between uncompressed and SigComp messages on
the same TCP port, and b) performance implication. Part a) should
be normative and b) should be just recommendations.

Document-2. SIP Specific. Deal with issues on how to apply SigComp 
to SIP, e.g. default DMS, compartment mapping/management, how to
deal with binary data in SIP messages, etc.

If we agree on the two documents approach, I think Document-1 should
be ROHC WG document as it is not SIP specific. As to document-2, I
tend to agree with you that it should be done in SIPPING WG. But
I really don't have strong feeling, as long as it is done. 

During the ROHC meeting in IETF-56, I've volunteered to be the editor
of document-2. I see you've made many good points here. So, here is 
my proposal. I'll write a skeleton draft with TOC, fill in some sections
that looks obvious to me (e.g. DMS, binary content, and perhaps 
compartment mapping) and then send to you so you can change and fill with 
other issues you pointed out below. I'll try to do that in the next 2~3 weeks.
Hopefully, people will agree which WG to home the document by then. :-)

BR,
Zhigang

> -----Original Message-----
> From: ext Price, Richard [mailto:richard.price@roke.co.uk]
> Sent: March 26, 2003 7:58 AM
> To: Liu Zhigang.C (NRC/Dallas); cabo@tzi.org;
> Lars-Erik.Jonsson@epl.ericsson.se
> Cc: rohc@ietf.org; sipping@ietf.org
> Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> messages
> 
> 
> Hi,
> 
> I think that the issue with SigComp and large binary
> content SIP messages is part of a more general issue -
> namely that before using SigComp to compress a particular
> application we need to standardise the following:
> 
> 1. Mechanism for SigComp discovery
> 2. Resources offered by SigComp
> 3. How to delimit messages
> 4. When to save state
> 
> Currently the SIPPING WG has provided RFCs for 1 and 2,
> but not for 3 and 4. It would be useful to get a draft
> out for these ASAP, as it would clarify several issues on
> how to get SigComp working with SIP (including the issue
> with large binary content SIP messages).
> 
> > Unless someone objects, I'll submit it in ROHC.
> 
> I think that any WG draft should be a product of the
> SIPPING WG, because the proposed solution for delimiting
> SigComp messages will need to take into account the
> behaviour of SIP itself (or we won't be able to multiplex
> SigComp and SIP messages on the same port). However, it
> would be good to get the ROHC WG involved in generating
> the draft as well!
> 
> Regards,
> 
> Richard
> 
> P.S. For anyone who's interested, the mechanisms that
> particular applications need to provide before they can
> use SigComp are as follows...
> 
> ------------------------------------------------------
> 
> 1. Mechanism for SigComp discovery
> 
>    - How does the application know when to use SigComp?
> 
> For SIP this issue is already sorted (RFC 3486).
> 
> ------------------------------------------------------
> 
> 2. Resources offered by SigComp
> 
>    - Does the application need to offer more than the
>      minimum amount of resources?
> 
>    - Does the application need any extra state (e.g.
>      a static dictionary)?
> 
> For SIP we've already got a static dictionary (RFC 3485).
> However, we haven't currently discussed how much memory
> should be provided in a SigComp implementation for SIP.
> If we don't specify a value then SigComp defaults to the
> minimum possible (2K), which is rather tight for some of
> the more generously sized SIP messages!
> 
> ------------------------------------------------------
> 
> 3. How to delimit messages
> 
>    - How does the application distinguish between
>      SigComp messages and uncompressed messages?
> 
>    - Is the application allowed to use "continuous mode"?
> 
> This is the issue that's been raised for large binary
> content SIP messages. If we want to send a mix of
> uncompressed and SigComp messages within the same TCP
> connection, how do we delimit the end of one message and
> the start of another?
> 
> A related issue is how to handle very large SIP messages
> (> 64K). SigComp is able to compress large SIP messages
> by using "continuous mode", where the message boundaries
> are ignored completely and the application data is just
> transmitted as a stream. However, this mode of operation
> raises some additional security issues, so it's up to the
> SIPPING WG to decide whether or not to use it in SigComp
> for SIP.
> 
> ------------------------------------------------------
> 
> 4. When to save state
> 
>    - How much security is needed in order to save state?
> 
>    - Which messages belong to each state "compartment"?
> 
>    - How long should the application keep state?
> 
> This is quite an important issue that doesn't seem to
> have been discussed in the SIPPING WG. It's up to the
> application whether or not to let SigComp save state,
> and for interoperability it's important to have at
> least a general idea of how long to keep saved state,
> when to reject state due to insufficient security etc.
> 
> ------------------------------------------------------
> 
> > -----Original Message-----
> > From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > Sent: Tuesday, March 25, 2003 6:00 PM
> > To: cabo@tzi.org; Lars-Erik.Jonsson@epl.ericsson.se
> > Cc: rohc@ietf.org; sipping@ietf.org
> > Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary 
> content SIP
> > messages
> > 
> > 
> > Hi Carsten and Lars-Erik,
> > 
> > I've volunteered to submit a personal draft on this issue. From
> > ROHC WG chairs' point of view, do you think this is the way 
> > to proceed?
> > 
> > Of course, I understood during the IETF56 that Carsten had some
> > doubts on whether this is indeed an issue. My email below explained
> > the issue a bit. I don't know if it's clear. Either way, we 
> > can continue discuss this in ROHC mailing list
> > 
> http://www1.ietf.org/mail-archive/working-groups/sipping/curre
> nt/msg04115.html
> > 
> > BR,
> > Zhigang
> > 
> > > -----Original Message-----
> > > From: ext zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > > Sent: March 13, 2003 9:55 AM
> > > To: Gonzalo.Camarillo@lmf.ericsson.se
> > > Cc: adam@dynamicsoft.com; Isomaki Markus (NRC/Helsinki);
> > > mwatson@nortelnetworks.com; sipping@ietf.org; rohc@ietf.org
> > > Subject: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> > > messages
> > > 
> > > 
> > > I agree. How to handling binary content is a generic issue for any
> > > application messages. What I have in mind is to give generic 
> > > descriptions/requirements (mainly on the SigComp receiver 
> parsing part),
> > > then touch on SIP (perhaps RTSP too) as a particular example.
> > > 
> > > Unless someone objects, I'll submit it in ROHC.
> > > 
> > > Zhigang
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: ext Gonzalo Camarillo 
> [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > > Sent: March 13, 2003 5:36 AM
> > > > To: Liu Zhigang.C (NRC/Dallas)
> > > > Cc: adam@dynamicsoft.com; Isomaki Markus (NRC/Helsinki);
> > > > mwatson@nortelnetworks.com; sipping@ietf.org
> > > > Subject: Re: [Sipping] SIGCOMP and large binary content 
> SIP messages
> > > > 
> > > > 
> > > > Zhigang,
> > > > 
> > > > you can submit that draft to ROHC. SIPPING can review 
> it afterwards.
> > > > IMO, the competence needed to generate this draft can 
> be found more
> > > > easily in ROHC than in SIPPING.
> > > > 
> > > > Besides, you could use SigComp to compress RTSP 
> messages, for instance
> > > > And RTSP is not handle by SIPPING either.
> > > > 
> > > > Gonzalo
> > > > 
> > > > zhigang.c.liu@nokia.com wrote:
> > > > > 
> > > > > Yes, that is also what I had in mind for SIP. But my 
> point is that
> > > > > a SigComp receiver now needs to have some knowledge 
> about application
> > > > > message format and do parsing to determine the end of 
> an uncompressed
> > > > > message. This is something new (or at least 
> unspecified) in RFC 3320
> > > > > and needs to be spelled out in a new (standard track) 
> RFC. The document
> > > > > will be short, but I think it's needed for interoperability.
> > > > > 
> > > > > I'll write up an I-D and submit it after IETF 56. But 
> I'd like to know
> > > > > if folks in SIPPING think it should be done here or in ROHC.
> > > > > 
> > > > > Zhigang
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: ext Adam Roach [mailto:adam@dynamicsoft.com]
> > > > > > Sent: March 11, 2003 9:03 PM
> > > > > > To: Liu Zhigang.C (NRC/Dallas); Adam Roach; Isomaki Markus
> > > > > > (NRC/Helsinki); mwatson@nortelnetworks.com; sipping@ietf.org
> > > > > > Subject: RE: [Sipping] SIGCOMP and large binary 
> content SIP messages
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: zhigang.c.liu@nokia.com 
> [mailto:zhigang.c.liu@nokia.com]
> > > > > > >
> > > > > > > Having binary content in SIP messages may have 
> two impacts on
> > > > > > > SigComp:
> > > > > > >
> > > > > > > a) multiplexing of uncompressed messages with 
> SigComp messages on the
> > > > > > > same port.
> > > > > > ...
> > > > > > > For a), it is only an issue for SigComp/TCP, not 
> SigComp/UDP (where one
> > > > > > > SigComp message maps to one UDP packet). Adam's 
> point 1 and 2 are related
> > > > > > > to this. As to point 1, I think the SigComp 
> receiver still needs to know
> > > > > > > (somehow) the end of an uncompressed message, or 
> at least the end of the
> > > > > > > binary part of each SIP messages. Otherwise, a 
> bit pattern 11111 in
> > > > > > > the binary part will be mistaken by SigComp as 
> the beginning of a SigComp
> > > > > > > message. As to point 2, I would add that the 
> delimiter 0xFFFF can appear
> > > > > > > at the both the beginning and the end of a 
> SigComp message. So, the
> > > > > > > receiver needs to have the same parsing logic 
> just mentioned for bit pattern
> > > > > > > 11111.
> > > > > >
> > > > > > This isn't any more of an issue than it is without 
> SigComp. SIP
> > > > > > messages provide their own framing, and SigComp 
> messages do the
> > > > > > same. They can be trivially mixed on the same stream:
> > > > > >
> > > > > > 1. Peek at the first byte waiting in the stream.
> > > > > >
> > > > > > 2. If it is 0xf8 or higher, the next message in the 
> stream is
> > > > > >    a SigComp message. The message continues until a 
> 0xFFFF is
> > > > > >    encountered in the stream.
> > > > > >
> > > > > > 3. Otherwise, the next message in the stream is a 
> SIP message.
> > > > > >    Read the stream until a CR/LF/CR/LF is encountered. Parse
> > > > > >    the headers, and then read the number of bytes specified
> > > > > >    in the "Content-Length" header.
> > > > > >
> > > > > > 4. Return to step 1.
> > > > > >
> > > > > > /a
> > > > > >
> > > > > _______________________________________________
> > > > > Sipping mailing list 
> https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the application of SIP
> > > > Use sip-implementors@cs.columbia.edu for questions on 
> current sip
> > > > Use sip@ietf.org for new developments of core SIP
> > > 
> > > -- 
> > > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > > Telecom R&D               Fax   :  +358  9 299 30 52
> > > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> > > Finland                   http://www.hut.fi/~gonzalo
> > > 
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> > 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 27 07:33:34 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25013
	for <sipping-archive@odin.ietf.org>; Thu, 27 Mar 2003 07:33:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2RCso713260
	for sipping-archive@odin.ietf.org; Thu, 27 Mar 2003 07:54:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RCsoO13257
	for <sipping-web-archive@optimus.ietf.org>; Thu, 27 Mar 2003 07:54:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25001
	for <sipping-web-archive@ietf.org>; Thu, 27 Mar 2003 07:33:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RCs5O13200;
	Thu, 27 Mar 2003 07:54:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RCq4O13088
	for <sipping@optimus.ietf.org>; Thu, 27 Mar 2003 07:52:04 -0500
Received: from mgw-x4.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24881
	for <sipping@ietf.org>; Thu, 27 Mar 2003 07:30:16 -0500 (EST)
From: aki.niemi@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.5/Switch-2.2.5) with ESMTP id h2RCaQX17018
	for <sipping@ietf.org>; Thu, 27 Mar 2003 14:36:26 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T613c4dc806ac158f24078@esvir04nok.ntc.nokia.com> for <sipping@ietf.org>;
 Thu, 27 Mar 2003 14:32:38 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 27 Mar 2003 14:32:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 27 Mar 2003 14:32:35 +0200
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD9019451E1@esebe013.ntc.nokia.com>
Thread-Topic: Comments to draft-ietf-sipping-aaa-reqs-02 WGLC
Thread-Index: AcL0XOW6qg9CgjCkTquMJdnjeOwzgw==
To: <sipping@ietf.org>
X-OriginalArrivalTime: 27 Mar 2003 12:32:36.0028 (UTC) FILETIME=[F25F0FC0:01C2F45C]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2RCq4O13089
Subject: [Sipping] Comments to draft-ietf-sipping-aaa-reqs-02 WGLC
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

Here are a few comments/suggestions:

- Ch 1.1 on Terminology
	* Accounting has a very nice definition in RFC 2975, suggestion is
	  to use that, or the one from Diameter base protocol.
	* Home AAA server definition is confusing.
	* Online/offline accounting definitions might also benefit from RFC 2975
	  definition on real time accounting.
	* The last four definitions could also be copied from RFC 3261

- Ch 2, first paragraph; the motivational text doesn't seem really assuring and
	begs the question "If a requirement isn't intended to be supported, why
	list it?" Perhaps just say that different deployment scenarios may have
	a different set of requirements, e.g., a subset of the requirements listed
	in the chapter.

- Ch 2.1.5., I think I understand what is meant here, but the sentence could
	be clearer about what it means for a SIP entity to "have" a user. Does it imply
	an administration type relationship, like say a registrar or a presence agent?

- Ch 2.2.2, This should probably be split into two separate requirements. I think
	the first sentence is about authentication between the SIP server and 
	AAA server, whereas the latter talks about authentication schemes
	supported by the SIP-AAA interface. I.e., authentication between the UA and
	the SIP server.

- Ch 2.3.1, The note about CANCEL below the requirment may well be true, but the 
	last sentence contradicts with requirement 2.2.1. After all, if the CANCEL 
	can't be authenticated, there's no way to determine that the sender is the
	one who originally generated the request to be cancelled.

- Ch 2.3.3, Seems that Req 2.3.2 already at least partly covers this requirement.
	Also, may I suggest that the user profile example be separated
	from the text describing the requirement, perhaps as a note or a separate
	paragraph.

- Ch 2.3.4, similar to de-authorization, there should also be a requirement about
	re-authorization. This would be useful in tasks that require refreshes, such
	as registrations and subscriptions.

- Ch 2.4, first paragraph; I think much of the motivational text could well be 
	omitted if the term "accounting" had been properly defined in Ch 1.1.

- Ch 2.4.1, This seems like a good thing, but it's hard to really understand what
	is required. Is it that accounting information is granular? I can imagine this
	to be useful not only in session duration but also in other services. 

- Ch 2.4.2 and 2.4.3, I don't quite understand the meaning of  "direct bearing on".
	I'm sure there's a better term to describe the relationship. Perhaps "link" or
	"correlation"?

- Ch 2.4.5, I believe this is a general requirement, and not only relevant to
	charging.

- Ch 2.4.6, This requirement again talks about charging when I don't think it
	needs to.

- Ch 2.4.10, Suggestion is to separate the example from the requirement text. 
	Also, the example seems to also talk about authorization based on real-time
	accounting data - perhaps a requirement for the Authorization section?

Cheers,
Aki 
  
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 27 10:21:24 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02911
	for <sipping-archive@odin.ietf.org>; Thu, 27 Mar 2003 10:21:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2RFgie25423
	for sipping-archive@odin.ietf.org; Thu, 27 Mar 2003 10:42:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RFgiO25420
	for <sipping-web-archive@optimus.ietf.org>; Thu, 27 Mar 2003 10:42:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02883
	for <sipping-web-archive@ietf.org>; Thu, 27 Mar 2003 10:20:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RFfCO25329;
	Thu, 27 Mar 2003 10:41:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RFdjO25149
	for <sipping@optimus.ietf.org>; Thu, 27 Mar 2003 10:39:45 -0500
Received: from dyn-tx-arch-crash.dfw.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02764;
	Thu, 27 Mar 2003 10:17:53 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id h2RFKB927303;
	Thu, 27 Mar 2003 09:20:11 -0600
From: Robert Sparks <rsparks@dynamicsoft.com>
To: sip@ietf.org, sipping@ietf.org, impp@iastate.edu
Content-Type: text/plain
Message-Id: <1048778410.917.24.camel@RjS.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 27 Mar 2003 09:20:11 -0600
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] [Fwd: [Simple] Call for availability: Interim meeting]
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

All -

Ted Hardie (our new Apps Area AD) asked that I repeat this
request on SIP, SIPPING, and IMPP.

If you haven't already responded and plan to attend this
SIMPLE WG interim meeting, please send a private message
to me as soon as possible.

RjS

-----Forwarded Message-----

> From: Robert Sparks <rsparks@dynamicsoft.com>
> To: simple@ietf.org
> Subject: [Simple] Call for availability: Interim meeting
> Date: 26 Mar 2003 08:50:08 -0600
> 
> Folks -
> 
> As mentioned at our meeting in IETF56 we are going to hold an
> interim meeting between now and IETF57. We're planning
> a two day session, but need to choose the actual dates. 
> Location will depend on the dates, but will probably be in
> eastern Canada.
> 
> If, and _only_ if, you are definitely planning to attend
> please reply to me PRIVATELY by Friday with your availability 
> between May 12 and June 13. We'll find a date that accomodates as
> many responders as possible. 
> 
> Thanks,
> 
> RjS
> 
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www1.ietf.org/mailman/listinfo/simple

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 27 14:19:54 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13870
	for <sipping-archive@odin.ietf.org>; Thu, 27 Mar 2003 14:19:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2RJfJ113395
	for sipping-archive@odin.ietf.org; Thu, 27 Mar 2003 14:41:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RJfJO13392
	for <sipping-web-archive@optimus.ietf.org>; Thu, 27 Mar 2003 14:41:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13860
	for <sipping-web-archive@ietf.org>; Thu, 27 Mar 2003 14:19:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RJb8O12508;
	Thu, 27 Mar 2003 14:37:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RJUPO11981
	for <sipping@optimus.ietf.org>; Thu, 27 Mar 2003 14:30:25 -0500
Received: from sj-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13306
	for <sipping@ietf.org>; Thu, 27 Mar 2003 14:08:29 -0500 (EST)
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h2RJ9u9a029713
	for <sipping@ietf.org>; Thu, 27 Mar 2003 11:09:58 -0800 (PST)
Received: from CJ650 (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with SMTP id ACR52989;
	Thu, 27 Mar 2003 11:09:55 -0800 (PST)
From: "Cullen Jennings" <fluffy@cisco.com>
To: <sipping@ietf.org>
Subject: Apology for RE: [Sipping] A  WinXP patch
Date: Thu, 27 Mar 2003 11:12:20 -0800
Message-ID: <MFEJKLHKCMNFOPKPHMBPCENMCDAA.fluffy@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0045_01C2F451.BC5683F0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <B0006577995@01mail.PghMail.com>
Importance: Normal
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

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

I did not sent any patches - certainly not to XP :-) Cullen (the guy with
the fluffy hair)
  -----Original Message-----
  From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
fluffy
  Sent: Wednesday, March 26, 2003 3:50 PM
  To: sipping@ietf.org
  Subject: [Sipping] A WinXP patch


  This is a WinXP patch
  I expect you would like it.

------=_NextPart_000_0045_01C2F451.BC5683F0
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.2715.400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D639260419-27032003>I did=20
not sent any patches - certainly not to XP :-) Cullen (the guy with the =
fluffy=20
hair) </SPAN></FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
sipping-admin@ietf.org=20
  [mailto:sipping-admin@ietf.org]<B>On Behalf Of =
</B>fluffy<BR><B>Sent:</B>=20
  Wednesday, March 26, 2003 3:50 PM<BR><B>To:</B>=20
  sipping@ietf.org<BR><B>Subject:</B> [Sipping] A WinXP=20
  patch<BR><BR></FONT></DIV><FONT size=3D+0>This is a WinXP patch<BR>I =
expect you=20
  would like it.</FONT> </BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0045_01C2F451.BC5683F0--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 27 20:55:25 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01053
	for <sipping-archive@odin.ietf.org>; Thu, 27 Mar 2003 20:55:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2S2Gvo12331
	for sipping-archive@odin.ietf.org; Thu, 27 Mar 2003 21:16:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S2GvO12328
	for <sipping-web-archive@optimus.ietf.org>; Thu, 27 Mar 2003 21:16:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01001
	for <sipping-web-archive@ietf.org>; Thu, 27 Mar 2003 20:54:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S2G6O12268;
	Thu, 27 Mar 2003 21:16:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S2BDO11986
	for <sipping@optimus.ietf.org>; Thu, 27 Mar 2003 21:11:13 -0500
Received: from mgw-dax2.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00708;
	Thu, 27 Mar 2003 20:49:04 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax2.ext.nokia.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2S1p4s22945;
	Thu, 27 Mar 2003 19:51:14 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T613d713059ac12f25703c@davir04nok.americas.nokia.com>;
 Thu, 27 Mar 2003 19:50:55 -0600
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 27 Mar 2003 19:50:30 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Thu, 27 Mar 2003 19:50:29 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A830@daebe005.americas.nokia.com>
Thread-Topic: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP messages
Thread-Index: AcL0Oh0S9278a4G2TwGrlMF2MA/VLAAjOLXA
To: <Lars-Erik.Jonsson@epl.ericsson.se>
Cc: <rohc@ietf.org>, <sipping@ietf.org>
X-OriginalArrivalTime: 28 Mar 2003 01:50:30.0476 (UTC) FILETIME=[69C418C0:01C2F4CC]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2S2BDO11988
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Lars-Erik,

IMO, binary content in application message is a general issue for
SigComp multiplexing. It's not specific to SIP. I already explained 
this in rohc and sipping mailing list. But here is a simple example. 

Let's say endpoint A already knows endpoint B supports SigComp on TCP 
port number 5000. A sends, on port 5000, uncompressed message 1 followed 
by message 2 compressed using SigComp. From RFC 3320, message 2 starts
with bit pattern 11111. So, if message 1 has no binary content, endpoint
B can easily detect the beginning of message 2 (i.e. end of message 1)
by detecting 11111. However, if message 1 contains binary content,
that means the (uncompressed) binary part may contain byte 11111xxx.
This "mimicking" will make endpoint B mistakenly think a new SigComp
message starts at that byte. Obviously, things will be messed up
from that point.

This is what I referred to as the multiplexing issue. I hope I explained
it better this time for you. 

Anyway, I'll submit a personal draft to help the discussion, although the 
above example should make it obvious already.

Zhigang


> -----Original Message-----
> From: ext Lars-Erik Jonsson (EAB)
> [mailto:Lars-Erik.Jonsson@epl.ericsson.se]
> Sent: March 27, 2003 2:18 AM
> To: Liu Zhigang.C (NRC/Dallas)
> Cc: rohc@ietf.org
> Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> messages
> 
> 
> Zhigang,
> 
> > My question is the handling of binary content in application 
> > messages. In my view, this is a generic issue although it started
> > with SIP. My thought was to have a *separate* document that
> > addresses this issue (and perhaps other generic SigComp "bugs" if
> > we find out).
> 
> First of all, it is not yet clear to me that this is a general issue,
> at least I have not been able to see consensus on that. Secondly, if
> we have general unclear issues with SigComp, those would go into the
> Implementer's guide at this point.
> 
> Currently, I therefore think we can and should avoid having even more
> documents.  However, you can always provide input by writing a draft,
> that is up to you.
> 
> Regarding the SigComp&SIP document, it does not matter much
> in which WG it is "hosted", as long as it is written and well 
> reviewed 
> by people from both sides.
> 
> 
> Rgds,
> /L-E 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Thu Mar 27 22:05:45 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02393
	for <sipping-archive@odin.ietf.org>; Thu, 27 Mar 2003 22:05:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2S3RKT16855
	for sipping-archive@odin.ietf.org; Thu, 27 Mar 2003 22:27:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S3RKO16852
	for <sipping-web-archive@optimus.ietf.org>; Thu, 27 Mar 2003 22:27:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02371
	for <sipping-web-archive@ietf.org>; Thu, 27 Mar 2003 22:05:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S3QTO16831;
	Thu, 27 Mar 2003 22:26:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S3PCO16781
	for <sipping@optimus.ietf.org>; Thu, 27 Mar 2003 22:25:12 -0500
Received: from mtiwmhc13.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02347
	for <sipping@ietf.org>; Thu, 27 Mar 2003 22:03:06 -0500 (EST)
Received: from fasthome.ieee.org (186.chicago-15rh15rt.il.dial-access.att.net[12.84.124.186])
          by mtiwmhc13.worldnet.att.net (mtiwmhc13) with SMTP
          id <2003032803052611300k4bane>; Fri, 28 Mar 2003 03:05:26 +0000
Message-Id: <4.3.2.7.2.20030327203149.00ce5c80@postoffice.worldnet.att.net>
X-Sender: a.varney@postoffice.worldnet.att.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 27 Mar 2003 21:04:56 -0600
To: "Peterson, Jon" <jon.peterson@neustar.biz>, sipping@ietf.org
From: Al Varney <varney@ieee.org>
Subject: RE: [Sipping] New version of the early media draft
In-Reply-To: <15A2739B7DAA624D8091C65981D7DA8101214F39@stntexch2.va.neus
 tar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

I haven't seen any "results" from the Early-Media Ad-Hoc (if it was held), 
so I'll toss out something I would have stated had I been there....

At 04:50 PM 3/14/03 -0500, Peterson, Jon wrote:
>They are proverbially out of luck in the CAS interworking case, no? Again,
>it's not our fault that ISUP doesn't present its status accurately
>out-of-band.

    Absolutely true.  Even more so for MF or DP trunks off a SIP 
gateway.  You can't fix the past, but you do have to worry about embedded base.

>Anyway, this is speaking to a pair of separable issues. Whether or not we
>send pre-answer media with a 180 is separable from whether or not we need
>some SIP-layer indication that we are doing so. Personally, I think we're in
>a bad position to deal with cases where ISUP provides valuable in-band
>information but doesn't tell us so in the encoding of an ACM, and I don't
>think it is reasonable for us to always send pre-answer media on receipt of
>ACM. But this is a separate issue.
>
>If we send 180, and subsequently send media, we could very well be deceiving
>a deaf user (or a user whose UA simply doesn't render pre-answer media) into
>thinking that 'alerting' tells the whole story. But if 'alerting' told the
>whole story, there'd be no need to send any pre-answer media to accompany
>it. This is the paradox I keep hearing - people want to see an indicator
>that says "alerting" and play early media, but they simultaneously
>acknowledge that the reason they want the early media is because it
>qualifies the alerting state in some fashion.  How valuable is the
>"alerting" state at the UAC, then?

    OK -- so folks want "alerting" and early media (as in ISUP), 
particularly for cases when interworking with the old PSTN.  Then why add a 
SIP-early-media indicator to 180?  Instead, why not add an "alerting" 
indicator to 183 -- which maps rather well to ISUP ACM practice (ACM always 
implies in-band media in the backward direction, and it sometimes indicates 
'user free'/alerting).  It also maps to/from ISDN in an obvious manner.

    This leaves 180 untarnished as an explicit "alerting and no intended 
early media" indicator, and local ringback could always be generated.  Any 
pre-200 media could be assumed to have gotten ahead of SIP messaging, and 
it could be cut through to the caller either immediately or after a short 
delay.

    Adding a new indicator to 183 for "user being alerted" is backward 
compatible, since RTP media would be there even if the new indicator was 
ignored.  And for cases where the indicator WAS recognized, a display or 
forking treatment similar to that for 180 could be used.  Some UA could 
even generate local ringback if it really, really wanted to do so.

    The major advantage would be better compatibility with SIP-ISUP 
gateways for interworking, and the preservation of 180 for cases where 
SIP-aware signaling was used end-to-end.  Or where gateways that could 
distinguish true alerting cases (a gateway with directly-connected lines, 
for example, always knows the true alerting state of a terminal).  Over 
time, SIP-to-SIP calls would all tend to use 180, and the old PSTN behavior 
would be contained within 183 handling (where it already has to exist).

    (While adding indicators to 183, would it also be useful to have a "SIP 
not used all-the-way" indicator that indicates interworking to non-SIP 
protocols?   Or would a UA always behave the same for gateways sending 183 
and called-UAs sending 183?)

    View this as a comment thrown out into a late-night Ad-Hoc session.

Al Varney

>I would be more sympathetic to this view if the 'alerting' state had some
>specific semantics at the UAC pointed out in RFC3261 that differentiated
>'180 received' from '183 received' or other provisional states - but it
>doesn't. There's nothing magical about receiving a 180 response. It's been
>suggested that this is valuable for forking composition, but in my
>estimation, if there's in-band media associated with a provisional branch of
>a fork, you need to evaluate that media, not the status code (again,
>otherwise, why send the media at all?). Some sort of 180 indicator that
>suppresses local ringback doesn't help you either way with any of these
>problems.
>
>Jon Peterson
>NeuStar, Inc.
>
> > -----Original Message-----
> > From: Michael Hammer [mailto:mhammer@cisco.com]
> > Sent: Friday, March 14, 2003 12:51 PM
> > To: Peterson, Jon
> > Cc: 'Drage, Keith (Keith)'; 'Elwell, John'; 'Mark Watson';
> > 'sipping@ietf.org'
> > Subject: RE: [Sipping] New version of the early media draft
> >
> >
> > Jon,
> >
> > Doesn't the possibility of deaf users preclude the use of 183
> > from being
> > used, as has been suggested, since they won't hear the
> > locally injected
> > ringback or the inband media?
> >
> > Mike
> >
> >
> > At 05:52 AM 3/14/2003 -0500, Peterson, Jon wrote:
> >
> > >Below.
> > >
> > >Jon Peterson
> > >NeuStar, Inc.
> >
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 28 02:36:46 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19716
	for <sipping-archive@odin.ietf.org>; Fri, 28 Mar 2003 02:36:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2S7wQp12700
	for sipping-archive@odin.ietf.org; Fri, 28 Mar 2003 02:58:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S7wQO12697
	for <sipping-web-archive@optimus.ietf.org>; Fri, 28 Mar 2003 02:58:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19706
	for <sipping-web-archive@ietf.org>; Fri, 28 Mar 2003 02:36:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S7viO12671;
	Fri, 28 Mar 2003 02:57:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S7u8O12554
	for <sipping@optimus.ietf.org>; Fri, 28 Mar 2003 02:56:08 -0500
Received: from mgw-x1.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19591;
	Fri, 28 Mar 2003 02:33:57 -0500 (EST)
From: hisham.khartabil@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.5/Switch-2.2.5) with ESMTP id h2S7YoU27852;
	Fri, 28 Mar 2003 09:34:50 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T614064b1c5ac158f21082@esvir01nok.ntc.nokia.com>;
 Fri, 28 Mar 2003 09:36:08 +0200
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 28 Mar 2003 09:36:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Fri, 28 Mar 2003 09:36:09 +0200
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7FE744F@esebe019.ntc.nokia.com>
Thread-Topic: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP messages
Thread-Index: AcL0Oh0S9278a4G2TwGrlMF2MA/VLAAjOLXAAA0mRMA=
To: <zhigang.c.liu@nokia.com>, <Lars-Erik.Jonsson@epl.ericsson.se>
Cc: <rohc@ietf.org>, <sipping@ietf.org>
X-OriginalArrivalTime: 28 Mar 2003 07:36:10.0995 (UTC) FILETIME=[B4142430:01C2F4FC]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2S7u8O12556
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

SIP has this header called content-length that tells how long the body of a sip message is regardless of its binary of UTF-8 contents.

The SIP parser will read the content-length value and then take that many octets from whatever follows the sip headers as body. If the body has binary with pattern 11111, the parser doesn't care and doesn't even look in the body.

Any protocol that wants to make use of sigcomp should fix its own problems.

Regards,
Hisham

> -----Original Message-----
> From: ext zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> Sent: Friday, March 28, 2003 3:50 AM
> To: Lars-Erik.Jonsson@epl.ericsson.se
> Cc: rohc@ietf.org; sipping@ietf.org
> Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> messages
> 
> 
> Lars-Erik,
> 
> IMO, binary content in application message is a general issue for
> SigComp multiplexing. It's not specific to SIP. I already explained 
> this in rohc and sipping mailing list. But here is a simple example. 
> 
> Let's say endpoint A already knows endpoint B supports SigComp on TCP 
> port number 5000. A sends, on port 5000, uncompressed message 
> 1 followed 
> by message 2 compressed using SigComp. From RFC 3320, message 2 starts
> with bit pattern 11111. So, if message 1 has no binary 
> content, endpoint
> B can easily detect the beginning of message 2 (i.e. end of message 1)
> by detecting 11111. However, if message 1 contains binary content,
> that means the (uncompressed) binary part may contain byte 11111xxx.
> This "mimicking" will make endpoint B mistakenly think a new SigComp
> message starts at that byte. Obviously, things will be messed up
> from that point.
> 
> This is what I referred to as the multiplexing issue. I hope 
> I explained
> it better this time for you. 
> 
> Anyway, I'll submit a personal draft to help the discussion, 
> although the 
> above example should make it obvious already.
> 
> Zhigang
> 
> 
> > -----Original Message-----
> > From: ext Lars-Erik Jonsson (EAB)
> > [mailto:Lars-Erik.Jonsson@epl.ericsson.se]
> > Sent: March 27, 2003 2:18 AM
> > To: Liu Zhigang.C (NRC/Dallas)
> > Cc: rohc@ietf.org
> > Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary 
> content SIP
> > messages
> > 
> > 
> > Zhigang,
> > 
> > > My question is the handling of binary content in application 
> > > messages. In my view, this is a generic issue although it started
> > > with SIP. My thought was to have a *separate* document that
> > > addresses this issue (and perhaps other generic SigComp "bugs" if
> > > we find out).
> > 
> > First of all, it is not yet clear to me that this is a 
> general issue,
> > at least I have not been able to see consensus on that. Secondly, if
> > we have general unclear issues with SigComp, those would go into the
> > Implementer's guide at this point.
> > 
> > Currently, I therefore think we can and should avoid having 
> even more
> > documents.  However, you can always provide input by 
> writing a draft,
> > that is up to you.
> > 
> > Regarding the SigComp&SIP document, it does not matter much
> > in which WG it is "hosted", as long as it is written and well 
> > reviewed 
> > by people from both sides.
> > 
> > 
> > Rgds,
> > /L-E 
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> > 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 28 03:30:40 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20728
	for <sipping-archive@odin.ietf.org>; Fri, 28 Mar 2003 03:30:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2S8qKS16830
	for sipping-archive@odin.ietf.org; Fri, 28 Mar 2003 03:52:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S8qJO16827
	for <sipping-web-archive@optimus.ietf.org>; Fri, 28 Mar 2003 03:52:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20705
	for <sipping-web-archive@ietf.org>; Fri, 28 Mar 2003 03:30:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S8pSO16683;
	Fri, 28 Mar 2003 03:51:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S8ofO16612
	for <sipping@optimus.ietf.org>; Fri, 28 Mar 2003 03:50:41 -0500
Received: from hss.hns.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20663;
	Fri, 28 Mar 2003 03:28:27 -0500 (EST)
From: mgovind@hss.hns.com
Received: from sampark.hss.hns.com (sampark [139.85.229.22])
	by hss.hns.com (8.11.6/8.11.2) with SMTP id h2S7sNa12840;
	Fri, 28 Mar 2003 13:24:24 +0530
Received: by sampark.hss.hns.com(Lotus SMTP MTA Internal build v4.6.2  (651.2 6-10-1998))  id 65256CF7.002EA97F ; Fri, 28 Mar 2003 13:59:40 +0530
X-Lotus-FromDomain: HSSBLR
To: hisham.khartabil@nokia.com
cc: zhigang.c.liu@nokia.com, Lars-Erik.Jonsson@epl.ericsson.se, rohc@ietf.org,
        sipping@ietf.org
Message-ID: <65256CF7.002EA920.00@sampark.hss.hns.com>
Date: Fri, 28 Mar 2003 13:59:25 +0530
Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
	 messages
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>



HI,
I have some doubts.
Content length will come into picture only after decompression and parsing
of  the incomming message.
But if the parsing or decompression fails , what will happen to the
subsequent messages in the stream.

Regards
mahesh







hisham.khartabil@nokia.com on 03/28/2003 01:06:09 PM

To:   zhigang.c.liu@nokia.com, Lars-Erik.Jonsson@epl.ericsson.se
cc:   rohc@ietf.org, sipping@ietf.org (bcc: Mahesh Govind/HSSBLR)

Subject:  RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
      messages




SIP has this header called content-length that tells how long the body of a
sip message is regardless of its binary of UTF-8 contents.

The SIP parser will read the content-length value and then take that many
octets from whatever follows the sip headers as body. If the body has
binary with pattern 11111, the parser doesn't care and doesn't even look in
the body.

Any protocol that wants to make use of sigcomp should fix its own problems.

Regards,
Hisham

> -----Original Message-----
> From: ext zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> Sent: Friday, March 28, 2003 3:50 AM
> To: Lars-Erik.Jonsson@epl.ericsson.se
> Cc: rohc@ietf.org; sipping@ietf.org
> Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> messages
>
>
> Lars-Erik,
>
> IMO, binary content in application message is a general issue for
> SigComp multiplexing. It's not specific to SIP. I already explained
> this in rohc and sipping mailing list. But here is a simple example.
>
> Let's say endpoint A already knows endpoint B supports SigComp on TCP
> port number 5000. A sends, on port 5000, uncompressed message
> 1 followed
> by message 2 compressed using SigComp. From RFC 3320, message 2 starts
> with bit pattern 11111. So, if message 1 has no binary
> content, endpoint
> B can easily detect the beginning of message 2 (i.e. end of message 1)
> by detecting 11111. However, if message 1 contains binary content,
> that means the (uncompressed) binary part may contain byte 11111xxx.
> This "mimicking" will make endpoint B mistakenly think a new SigComp
> message starts at that byte. Obviously, things will be messed up
> from that point.
>
> This is what I referred to as the multiplexing issue. I hope
> I explained
> it better this time for you.
>
> Anyway, I'll submit a personal draft to help the discussion,
> although the
> above example should make it obvious already.
>
> Zhigang
>
>
> > -----Original Message-----
> > From: ext Lars-Erik Jonsson (EAB)
> > [mailto:Lars-Erik.Jonsson@epl.ericsson.se]
> > Sent: March 27, 2003 2:18 AM
> > To: Liu Zhigang.C (NRC/Dallas)
> > Cc: rohc@ietf.org
> > Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary
> content SIP
> > messages
> >
> >
> > Zhigang,
> >
> > > My question is the handling of binary content in application
> > > messages. In my view, this is a generic issue although it started
> > > with SIP. My thought was to have a *separate* document that
> > > addresses this issue (and perhaps other generic SigComp "bugs" if
> > > we find out).
> >
> > First of all, it is not yet clear to me that this is a
> general issue,
> > at least I have not been able to see consensus on that. Secondly, if
> > we have general unclear issues with SigComp, those would go into the
> > Implementer's guide at this point.
> >
> > Currently, I therefore think we can and should avoid having
> even more
> > documents.  However, you can always provide input by
> writing a draft,
> > that is up to you.
> >
> > Regarding the SigComp&SIP document, it does not matter much
> > in which WG it is "hosted", as long as it is written and well
> > reviewed
> > by people from both sides.
> >
> >
> > Rgds,
> > /L-E
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> >
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 28 17:55:45 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22951
	for <sipping-archive@odin.ietf.org>; Fri, 28 Mar 2003 17:55:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2SNHhI16600
	for sipping-archive@odin.ietf.org; Fri, 28 Mar 2003 18:17:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SNHhO16597
	for <sipping-web-archive@optimus.ietf.org>; Fri, 28 Mar 2003 18:17:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22922
	for <sipping-web-archive@ietf.org>; Fri, 28 Mar 2003 17:55:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SNGsO16462;
	Fri, 28 Mar 2003 18:16:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2O99SO15676
	for <sipping@optimus.ietf.org>; Mon, 24 Mar 2003 04:09:28 -0500
Received: from www.unitedinfo.com.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA07725
	for <sipping@ietf.org>; Mon, 24 Mar 2003 03:49:11 -0500 (EST)
Received: (qmail 23122 invoked from network); 24 Mar 2003 08:49:23 -0000
Received: from unknown (HELO raggy) (202.106.124.99)
  by 0 with SMTP; 24 Mar 2003 08:49:23 -0000
From: "Christian Stredicke" <stredicke@snom.de>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>
Cc: "'Rohan Mahy'" <rohan@cisco.com>, <sipping@ietf.org>,
        "=?iso-8859-1?Q?'J=F6rgen_Bj=F6rkner'?=" <jorgen.bjorkner@hotsip.com>,
        "'Robert Sparks'" <rsparks@dynamicsoft.com>
Date: Mon, 24 Mar 2003 16:48:46 +0800
Organization: snom technology AG
Message-ID: <004a01c2f1e2$7bca17a0$6e7c6aca@raggy>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <3E7E8193.1030404@dynamicsoft.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2O99SO15677
Subject: [Sipping] AW: AW: "Strict Routing", "Loose Routing", "No Routing"!
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Jonathan,

ok I elaborate a little bit as the history might not be known to
everybody.

(1) I am talking about the SIP messages here only; RTP is a separate
issue.

Again, I would like to stress I am not trying to reinvent routing (I
think that would be too late and inappropriate anyway). I would just
like to propose a backward-compatible way of expressing that non-SIP
aware equipment is involved in the message forwarding process that needs
to be taken care of. There is a need for this as we are moving on making
the addresses found by STUN usable between the different vendors.

(2) The problem is that depending on the context a request must be send
to one of several possible addresses. In the case of NAT you are right,
this is typically a problem when the two user agents are in the same NAT
and the NAT gateway does not properly forward the messages coming from
the private side sent to the public address of the other phone. This is
my private concern as this is the most critical case we are facing in
day-to-day life now. 

(3) I proposed using alternative addresses in the contact like 

"sip:62.12.34.56:6546;srcadr=192.168.0.123:5060"

but that did not find too much acceptance with the persons that I talked
to. The alternative proposal is including the route in the contact like

"sip:192.168.0.123:5060?Route=sip:62.12.34.56:6546" or so,

but this has the disadvantage that equipment which does not support the
route header will not be able to send the packet properly (and apart
from that I have some problems understanding how the route header should
be merged with a maybe existing route).

(4) What I propose now is using the routing mechanism we all know from
SIP with a modification (backward compatible). For registrations, the
path header has already been proposed and the record-route is part of
the RFC. 

Lets make an example: The UA is in a private network and has the above
private address and public address association. So it will send the
following REGISTER message:

REGISTER sip:bla.com SIP/2.0
Path: <sip:62.12.34.56:6546;nr=1;lr>
Contact: <sip:192.168.0.123:5060>
...

The registrar will save both the path and the contact. So a INVITE that
is forwarded to the user agent then will go along the path:

INVITE sip:192.168.0.123:5060 SIP/2.0
Route: <sip:62.12.34.56:6546;nr=1;lr>

Because the user agent can deal with the "no routing", it will remove
the top route entry (it contains the nr) and then process the packet.
Here, it will probably start ringing.

If the user agents sends a message and the topmost route entry contains
the nr flag, it skips that route if the IP address is the same as the IP
address that is has stored as its public IP address. This is surely a
pragmatic first step to solving the problem of finding the right
destination in a NAT. However, it can be extended to using STUN probes
first and so on (for example in multi-tier NAT). 

(5) The nice thing about the nr idea is that existing equipment does not
have to be changed. That means especially the existing proxies in the
public internet can deal perfectly with "no routers". If equipment
supports the nr flag, it will also see the packets with the nr flag and
process them accordingly. Meaning that nr is fully backward compatible.


I hope this clarifies the idea a little bit more.


Christian
--
Dr.-Ing. Christian Stredicke
sip:cs@snom.com
 

> -----Ursprüngliche Nachricht-----
> Von: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
> Gesendet: Montag, 24. März 2003 11:55
> An: Christian Stredicke
> Cc: 'Rohan Mahy'; sipping@ietf.org; 'Jörgen Björkner'; 'Robert Sparks'
> Betreff: Re: AW: "Strict Routing", "Loose Routing", "No Routing"!
> 
> Christian,
> 
> I cannot really follow your email, and do not understand the problem
> here. Perhaps you are referring to the case where A calls B, both
behind
> the same NAT, with a proxy on the public Internet. If the proxy doesnt
> record route, a contact in the INVITE from A that contains an address
> allocated via upnp will not be useful to B. There is an equivalent
case
> for RTP.
> 
> There are only two solutions for this, I believe:
> 
> 1. the proxy always record routes. But, how does it know that it needs
> to do so?
> 
> 2. apply the ICE principles to SIP signaling. This would involve
> inclusion of *both* the public and private addresses in the Contact
> header of the INVITE, and so the recipient uses the one that works.
> Contact in INVITE only allows one URI (pity), so we would need to hack
> around to get that to work. There are ways.
> 
> I think most folk do approach 1. Its problem is that the proxy has to
> know to record route.
> 
> Approach 2 is in line with the ICE philosophy in that it would always
> work, without requiring apriori topology knowledge as case 1 assumes.
> 
> Anyway, moving to sipping since this is an important issue.
> 
> -Jonathan R.
> 
> Christian Stredicke wrote:
> > Rohan,
> >
> > that is surely going into the right direction!
> >
> > I think it clearly points out the need to transport more than one
> > address in the SDP.
> >
> > However, it does not seem to solve the problem for requests that
don’t
> > have SDP attachments (like MESSAGE). There is a difference in SIP
> > routing and RTP routing. I think the draft addresses the RTP routing
> > problem. For SIP routing, I think we still need a way for
formulating
> > that non SIP-aware equipment is involved in the routing process.
> >
> > Again, in my perception, SIP deals with *routes* (user agent client,
> > number of routers with loose/strict/no routing and the user agent
> > server). Every router has a defined behaviour (SIP aware called
> > "proxies" and non SIP-aware called "NAT"). We know that the
different
> > types of proxies need different treatment and I begin to realize
that
> > NAT routers need a different treatment as well.
> >
> > The good news is that "no-routers" can be treated backward
compatible.
> > If the routing element behind the no-router fixes the SIP routing
> > information everything should run fine. It is also the element
behind
> > the no-router that inserts this information.
> >
> > Anyway, having a STUN server on board of every SIP network element
> > (UA/proxy) is probably a good idea for whatever comes. As you know,
we
> > did this already half a year on our proxy!
> >
> > Best,
> >
> >
> > Christian
> >
> >
> >>-----Ursprüngliche Nachricht-----
> >>Von: Rohan Mahy [mailto:rohan@cisco.com]
> >>Gesendet: Samstag, 22. März 2003 05:57
> >>An: Christian Stredicke
> >>Cc: sip-implementors@cs.columbia.edu; 'Jörgen Björkner'; 'Robert
> >
> > Sparks'
> >
> >>Betreff: Re: "Strict Routing", "Loose Routing", "No Routing"!
> >>
> >>Hi Christian,
> >>
> >>Have you seen Jonathan Rosenberg's "ICE" proposal which we discussed
> >
> > in
> >
> >>SIPPING?  How do you think these would relate.
> >>
> >>thanks,
> >>-rohan
> >>
> >>
> >>On Monday, March 17, 2003, at 09:17 PM, Christian Stredicke wrote:
> >>
> >>
> >>>Hello again,
> >>>
> >>>while we have now loose routers and strict routers it seems that a
> >>
> > new
> >
> >>>type occurs on the horizon: The "no router"!
> >>>
> >>>This is for example the case when using NAT forwarding (e.g. with
> >>
> > STUN
> >
> >>>or UPnP). The router is not at all aware of SIP and does not
> >>
> > manipulate
> >
> >>>the packet at all. However, the router is too dumb to forward a
> >>
> > packet
> >
> >>>if it is coming from the wrong direction. This is the case with
most
> >>
> > of
> >
> >>>the DSL routers today.
> >>>
> >>>May I propose to use a ";nr" flag in a URI to indicate that the
> >>
> > router
> >
> >>>does not do any SIP changing at all?
> >>>
> >>>User Agents that are able to deal with "no routers" would then
> >>
> > register
> >
> >>>with the following packet:
> >>>
> >>>REGISTER sip:bla.com SIP/2.0
> >>>Path: <sip:62.12.245.32:54456;nr=1>
> >>>Contact: <sip:abc@192.168.1.2:5060>
> >>>...
> >>>
> >>>When it receives a message this could look like this:
> >>>
> >>>INVITE sip:62.12.245.32:54456;nr=1 SIP/2.0
> >>>Route: <sip:abc@192.168.1.2:5060>
> >>>...
> >>>
> >>>SIP/2.0 200 Wonderful
> >>>Record-Route: <sip:62.12.245.32:54456;nr=1>
> >>>Contact: <sip:abc@192.168.1.2:5060>
> >>>...
> >>>
> >>>The nr parameter could easily indicate that the previous router did
> >>
> > not
> >
> >>>change the packet at all and that the next entity has to fix this
> >>>before
> >>>processing the message. Alternatively, the router sending the
packet
> >>>could fix the route before sending it.
> >>>
> >>>What do you think? Is this really necessary? Just omit the nr
> >>
> > parameter
> >
> >>>and conclude implicitly? How else should we deal with routers that
> >>
> > are
> >
> >>>not SIP-aware? I don’t like the route encoding in the header
> >>>(sip:abc?route=def) as it raises many questions about how to merge
> >>
> > this
> >
> >>>with other existing routes.
> >>>
> >>>Unfortunately, omitting the private address is no solution, as
> >>
> > devices
> >
> >>>in the same subnet have to bypass the "no router". Many DSL routers
> >>
> > are
> >
> >>>not able to send packets from private address via the public
address
> >>
> > to
> >
> >>>the other private address.
> >>>
> >>>Cheers,
> >>>
> >>>
> >>>Christian
> >>>--
> >>>Dr. Christian Stredicke
> >>>sip:cs@snom.com
> >>>
> >>
> >
> >
> 
> --
> Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
> Chief Scientist                             Parsippany, NJ 07054-2711
> dynamicsoft
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 28 17:55:46 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22965
	for <sipping-archive@odin.ietf.org>; Fri, 28 Mar 2003 17:55:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2SNHjJ16620
	for sipping-archive@odin.ietf.org; Fri, 28 Mar 2003 18:17:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SNHjO16617
	for <sipping-web-archive@optimus.ietf.org>; Fri, 28 Mar 2003 18:17:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22925
	for <sipping-web-archive@ietf.org>; Fri, 28 Mar 2003 17:55:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SNH5O16533;
	Fri, 28 Mar 2003 18:17:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2S7i2O11730
	for <sipping@optimus.ietf.org>; Fri, 28 Mar 2003 02:44:02 -0500
Received: from mgw-x1.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19193;
	Fri, 28 Mar 2003 02:21:49 -0500 (EST)
From: Robert.Sugar@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.5/Switch-2.2.5) with ESMTP id h2S7MgU16360;
	Fri, 28 Mar 2003 09:22:43 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T614059b525ac158f21082@esvir01nok.ntc.nokia.com>;
 Fri, 28 Mar 2003 09:24:08 +0200
Received: from esebe016.NOE.Nokia.com ([172.21.138.55]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 28 Mar 2003 09:24:10 +0200
Received: from buebe002.NOE.Nokia.com ([10.211.0.51]) by esebe016.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 28 Mar 2003 09:24:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP messages
Date: Fri, 28 Mar 2003 08:24:09 +0100
Message-ID: <21B200DF0688CC45ACF38F49D227983206386D@buebe002.europe.nokia.com>
Thread-Topic: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP messages
Thread-Index: AcL0Oh0S9278a4G2TwGrlMF2MA/VLAAjOLXAAAxkv+A=
To: <zhigang.c.liu@nokia.com>
Cc: <rohc@ietf.org>, <sipping@ietf.org>
X-OriginalArrivalTime: 28 Mar 2003 07:24:10.0735 (UTC) FILETIME=[06C52FF0:01C2F4FB]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2S7i2O11731
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi Zhigang,

 I don't think it is a problem with SigComp multiplexing, but more like a SIP internal issue. What if there is a TCP stream of SIP messages and the Content-Length header is missing or false? They will screw up the same way with or without SigComp. During normal functioning both SIP and SigComp provide their own flow separation mechanism and they work just fine.
 As for other applications the requirement is that the messages must not start with 11111xxx and the end of the messages must be detected. If that is assured binary content is not a problem anymore. Besides, whatever pattern you choose to distinguish SigComp it might appear in application messages <evil> for example if we attach a Sigcomp message as application/octet stream </evil>. Only the possibility for screwing up will be lower.

Best Regards,
Robert

> -----Original Message-----
> From: ext zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> Sent: March 28,2003 2:50
> To: Lars-Erik.Jonsson@epl.ericsson.se
> Cc: rohc@ietf.org; sipping@ietf.org
> Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> messages
> 
> 
> Lars-Erik,
> 
> IMO, binary content in application message is a general issue for
> SigComp multiplexing. It's not specific to SIP. I already explained 
> this in rohc and sipping mailing list. But here is a simple example. 
> 
> Let's say endpoint A already knows endpoint B supports SigComp on TCP 
> port number 5000. A sends, on port 5000, uncompressed message 
> 1 followed 
> by message 2 compressed using SigComp. From RFC 3320, message 2 starts
> with bit pattern 11111. So, if message 1 has no binary 
> content, endpoint
> B can easily detect the beginning of message 2 (i.e. end of message 1)
> by detecting 11111. However, if message 1 contains binary content,
> that means the (uncompressed) binary part may contain byte 11111xxx.
> This "mimicking" will make endpoint B mistakenly think a new SigComp
> message starts at that byte. Obviously, things will be messed up
> from that point.
> 
> This is what I referred to as the multiplexing issue. I hope 
> I explained
> it better this time for you. 
> 
> Anyway, I'll submit a personal draft to help the discussion, 
> although the 
> above example should make it obvious already.
> 
> Zhigang
> 
> 
> > -----Original Message-----
> > From: ext Lars-Erik Jonsson (EAB)
> > [mailto:Lars-Erik.Jonsson@epl.ericsson.se]
> > Sent: March 27, 2003 2:18 AM
> > To: Liu Zhigang.C (NRC/Dallas)
> > Cc: rohc@ietf.org
> > Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary 
> content SIP
> > messages
> > 
> > 
> > Zhigang,
> > 
> > > My question is the handling of binary content in application 
> > > messages. In my view, this is a generic issue although it started
> > > with SIP. My thought was to have a *separate* document that
> > > addresses this issue (and perhaps other generic SigComp "bugs" if
> > > we find out).
> > 
> > First of all, it is not yet clear to me that this is a 
> general issue,
> > at least I have not been able to see consensus on that. Secondly, if
> > we have general unclear issues with SigComp, those would go into the
> > Implementer's guide at this point.
> > 
> > Currently, I therefore think we can and should avoid having 
> even more
> > documents.  However, you can always provide input by 
> writing a draft,
> > that is up to you.
> > 
> > Regarding the SigComp&SIP document, it does not matter much
> > in which WG it is "hosted", as long as it is written and well 
> > reviewed 
> > by people from both sides.
> > 
> > 
> > Rgds,
> > /L-E 
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> > 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 28 17:55:59 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22985
	for <sipping-archive@odin.ietf.org>; Fri, 28 Mar 2003 17:55:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2SNHw216690
	for sipping-archive@odin.ietf.org; Fri, 28 Mar 2003 18:17:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SNHwO16687
	for <sipping-web-archive@optimus.ietf.org>; Fri, 28 Mar 2003 18:17:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22932
	for <sipping-web-archive@ietf.org>; Fri, 28 Mar 2003 17:55:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SNH3O16513;
	Fri, 28 Mar 2003 18:17:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RBNpO07367
	for <sipping@optimus.ietf.org>; Thu, 27 Mar 2003 06:23:51 -0500
Received: from rsys002a.roke.co.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22972;
	Thu, 27 Mar 2003 06:02:04 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <HSB1W7PX>; Thu, 27 Mar 2003 11:04:24 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED41804A0F209@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>, cabo@tzi.org,
        Lars-Erik.Jonsson@epl.ericsson.se
Cc: rohc@ietf.org, sipping@ietf.org
Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP mes
	sages
Date: Thu, 27 Mar 2003 11:04:14 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

> I agree on most of your comments. What I want to clarify and ask
> for input is the way to organize documents. Based on comments
> from Gonzalo and my own view, we should have *two* documents:
> 
> Document-1. Not specific to SIP. Deal with how to apply SigComp
> to application protocol whose messages may contain binary (i.e.
> non UTF-8 encoded) data. It should contain at least two parts:
> a) multiplexing between uncompressed and SigComp messages on
> the same TCP port, and b) performance implication. Part a) should
> be normative and b) should be just recommendations.

Hi,

Regarding point a), I don't see how this can be done without
talking about specific protocols. Adam already made a proposal for
how to do the multiplexing in the case of SIP, which is as follows:

1. Peek at the first byte waiting in the stream.

2. If it is 0xf8 or higher, the next message in the stream is
   a SigComp message. The message continues until a 0xFFFF is
   encountered in the stream.

3. Otherwise, the next message in the stream is a SIP message.
   Read the stream until a CR/LF/CR/LF is encountered. Parse
   the headers, and then read the number of bytes specified
   in the "Content-Length" header.

4. Return to step 1.

However, the above mechanism works only for SIP - different
multiplexing mechanisms would be needed when using SigComp to
compress different protocols.

Regarding point b), it might be good to have some recommendations
on how to implement an efficient compressor for messages with
binary content. A suitable home for these would be the SigComp
User Guide, which already talks about the various different
compressors that can be used in conjunction with SigComp.

> Document-2. SIP Specific. Deal with issues on how to apply SigComp 
> to SIP, e.g. default DMS, compartment mapping/management, how to
> deal with binary data in SIP messages, etc.
> 
> If we agree on the two documents approach, I think Document-1 should
> be ROHC WG document as it is not SIP specific. As to document-2, I
> tend to agree with you that it should be done in SIPPING WG. But
> I really don't have strong feeling, as long as it is done. 
> 
> During the ROHC meeting in IETF-56, I've volunteered to be the editor
> of document-2. I see you've made many good points here. So, here is 
> my proposal. I'll write a skeleton draft with TOC, fill in some sections
> that looks obvious to me (e.g. DMS, binary content, and perhaps 
> compartment mapping) and then send to you so you can change and fill with 
> other issues you pointed out below. I'll try to do that in the next 2~3 weeks.
> Hopefully, people will agree which WG to home the document by then. :-)

Sounds ok to me. Of course, we'll need more mailing-list discussion
on some of the open issues - how much memory should be provided by
each SigComp endpoint and so on.

Regards,

Richard

> BR,
> Zhigang
> 
> > -----Original Message-----
> > From: ext Price, Richard [mailto:richard.price@roke.co.uk]
> > Sent: March 26, 2003 7:58 AM
> > To: Liu Zhigang.C (NRC/Dallas); cabo@tzi.org;
> > Lars-Erik.Jonsson@epl.ericsson.se
> > Cc: rohc@ietf.org; sipping@ietf.org
> > Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> > messages
> > 
> > 
> > Hi,
> > 
> > I think that the issue with SigComp and large binary
> > content SIP messages is part of a more general issue -
> > namely that before using SigComp to compress a particular
> > application we need to standardise the following:
> > 
> > 1. Mechanism for SigComp discovery
> > 2. Resources offered by SigComp
> > 3. How to delimit messages
> > 4. When to save state
> > 
> > Currently the SIPPING WG has provided RFCs for 1 and 2,
> > but not for 3 and 4. It would be useful to get a draft
> > out for these ASAP, as it would clarify several issues on
> > how to get SigComp working with SIP (including the issue
> > with large binary content SIP messages).
> > 
> > > Unless someone objects, I'll submit it in ROHC.
> > 
> > I think that any WG draft should be a product of the
> > SIPPING WG, because the proposed solution for delimiting
> > SigComp messages will need to take into account the
> > behaviour of SIP itself (or we won't be able to multiplex
> > SigComp and SIP messages on the same port). However, it
> > would be good to get the ROHC WG involved in generating
> > the draft as well!
> > 
> > Regards,
> > 
> > Richard
> > 
> > P.S. For anyone who's interested, the mechanisms that
> > particular applications need to provide before they can
> > use SigComp are as follows...
> > 
> > ------------------------------------------------------
> > 
> > 1. Mechanism for SigComp discovery
> > 
> >    - How does the application know when to use SigComp?
> > 
> > For SIP this issue is already sorted (RFC 3486).
> > 
> > ------------------------------------------------------
> > 
> > 2. Resources offered by SigComp
> > 
> >    - Does the application need to offer more than the
> >      minimum amount of resources?
> > 
> >    - Does the application need any extra state (e.g.
> >      a static dictionary)?
> > 
> > For SIP we've already got a static dictionary (RFC 3485).
> > However, we haven't currently discussed how much memory
> > should be provided in a SigComp implementation for SIP.
> > If we don't specify a value then SigComp defaults to the
> > minimum possible (2K), which is rather tight for some of
> > the more generously sized SIP messages!
> > 
> > ------------------------------------------------------
> > 
> > 3. How to delimit messages
> > 
> >    - How does the application distinguish between
> >      SigComp messages and uncompressed messages?
> > 
> >    - Is the application allowed to use "continuous mode"?
> > 
> > This is the issue that's been raised for large binary
> > content SIP messages. If we want to send a mix of
> > uncompressed and SigComp messages within the same TCP
> > connection, how do we delimit the end of one message and
> > the start of another?
> > 
> > A related issue is how to handle very large SIP messages
> > (> 64K). SigComp is able to compress large SIP messages
> > by using "continuous mode", where the message boundaries
> > are ignored completely and the application data is just
> > transmitted as a stream. However, this mode of operation
> > raises some additional security issues, so it's up to the
> > SIPPING WG to decide whether or not to use it in SigComp
> > for SIP.
> > 
> > ------------------------------------------------------
> > 
> > 4. When to save state
> > 
> >    - How much security is needed in order to save state?
> > 
> >    - Which messages belong to each state "compartment"?
> > 
> >    - How long should the application keep state?
> > 
> > This is quite an important issue that doesn't seem to
> > have been discussed in the SIPPING WG. It's up to the
> > application whether or not to let SigComp save state,
> > and for interoperability it's important to have at
> > least a general idea of how long to keep saved state,
> > when to reject state due to insufficient security etc.
> > 
> > ------------------------------------------------------
> > 
> > > -----Original Message-----
> > > From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > > Sent: Tuesday, March 25, 2003 6:00 PM
> > > To: cabo@tzi.org; Lars-Erik.Jonsson@epl.ericsson.se
> > > Cc: rohc@ietf.org; sipping@ietf.org
> > > Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> > > messages
> > > 
> > > 
> > > Hi Carsten and Lars-Erik,
> > > 
> > > I've volunteered to submit a personal draft on this issue. From
> > > ROHC WG chairs' point of view, do you think this is the way 
> > > to proceed?
> > > 
> > > Of course, I understood during the IETF56 that Carsten had some
> > > doubts on whether this is indeed an issue. My email below explained
> > > the issue a bit. I don't know if it's clear. Either way, we 
> > > can continue discuss this in ROHC mailing list
> > > 
> > http://www1.ietf.org/mail-archive/working-groups/sipping/current/msg04115.html
> > > 
> > > BR,
> > > Zhigang
> > > 
> > > > -----Original Message-----
> > > > From: ext zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > > > Sent: March 13, 2003 9:55 AM
> > > > To: Gonzalo.Camarillo@lmf.ericsson.se
> > > > Cc: adam@dynamicsoft.com; Isomaki Markus (NRC/Helsinki);
> > > > mwatson@nortelnetworks.com; sipping@ietf.org; rohc@ietf.org
> > > > Subject: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> > > > messages
> > > > 
> > > > 
> > > > I agree. How to handling binary content is a generic issue for any
> > > > application messages. What I have in mind is to give generic 
> > > > descriptions/requirements (mainly on the SigComp receiver parsing part),
> > > > then touch on SIP (perhaps RTSP too) as a particular example.
> > > > 
> > > > Unless someone objects, I'll submit it in ROHC.
> > > > 
> > > > Zhigang
> > > > 
> > > > 
> > > > > -----Original Message-----
> > > > > From: ext Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > > > Sent: March 13, 2003 5:36 AM
> > > > > To: Liu Zhigang.C (NRC/Dallas)
> > > > > Cc: adam@dynamicsoft.com; Isomaki Markus (NRC/Helsinki);
> > > > > mwatson@nortelnetworks.com; sipping@ietf.org
> > > > > Subject: Re: [Sipping] SIGCOMP and large binary content SIP messages
> > > > > 
> > > > > 
> > > > > Zhigang,
> > > > > 
> > > > > you can submit that draft to ROHC. SIPPING can review it afterwards.
> > > > > IMO, the competence needed to generate this draft can be found more
> > > > > easily in ROHC than in SIPPING.
> > > > > 
> > > > > Besides, you could use SigComp to compress RTSP messages, for instance
> > > > > And RTSP is not handle by SIPPING either.
> > > > > 
> > > > > Gonzalo
> > > > > 
> > > > > zhigang.c.liu@nokia.com wrote:
> > > > > > 
> > > > > > Yes, that is also what I had in mind for SIP. But my point is that
> > > > > > a SigComp receiver now needs to have some knowledge about application
> > > > > > message format and do parsing to determine the end of an uncompressed
> > > > > > message. This is something new (or at least unspecified) in RFC 3320
> > > > > > and needs to be spelled out in a new (standard track) RFC. The document
> > > > > > will be short, but I think it's needed for interoperability.
> > > > > > 
> > > > > > I'll write up an I-D and submit it after IETF 56. But I'd like to know
> > > > > > if folks in SIPPING think it should be done here or in ROHC.
> > > > > > 
> > > > > > Zhigang
> > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: ext Adam Roach [mailto:adam@dynamicsoft.com]
> > > > > > > Sent: March 11, 2003 9:03 PM
> > > > > > > To: Liu Zhigang.C (NRC/Dallas); Adam Roach; Isomaki Markus
> > > > > > > (NRC/Helsinki); mwatson@nortelnetworks.com; sipping@ietf.org
> > > > > > > Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > > > > > > >
> > > > > > > > Having binary content in SIP messages may have two impacts on
> > > > > > > > SigComp:
> > > > > > > >
> > > > > > > > a) multiplexing of uncompressed messages with SigComp messages on the
> > > > > > > > same port.
> > > > > > > ...
> > > > > > > > For a), it is only an issue for SigComp/TCP, not SigComp/UDP (where one
> > > > > > > > SigComp message maps to one UDP packet). Adam's point 1 and 2 are related
> > > > > > > > to this. As to point 1, I think the SigComp receiver still needs to know
> > > > > > > > (somehow) the end of an uncompressed message, or at least the end of the
> > > > > > > > binary part of each SIP messages. Otherwise, a bit pattern 11111 in
> > > > > > > > the binary part will be mistaken by SigComp as the beginning of a SigComp
> > > > > > > > message. As to point 2, I would add that the delimiter 0xFFFF can appear
> > > > > > > > at the both the beginning and the end of a SigComp message. So, the
> > > > > > > > receiver needs to have the same parsing logic just mentioned for bit pattern
> > > > > > > > 11111.
> > > > > > >
> > > > > > > This isn't any more of an issue than it is without SigComp. SIP
> > > > > > > messages provide their own framing, and SigComp messages do the
> > > > > > > same. They can be trivially mixed on the same stream:
> > > > > > >
> > > > > > > 1. Peek at the first byte waiting in the stream.
> > > > > > >
> > > > > > > 2. If it is 0xf8 or higher, the next message in the stream is
> > > > > > >    a SigComp message. The message continues until a 0xFFFF is
> > > > > > >    encountered in the stream.
> > > > > > >
> > > > > > > 3. Otherwise, the next message in the stream is a SIP message.
> > > > > > >    Read the stream until a CR/LF/CR/LF is encountered. Parse
> > > > > > >    the headers, and then read the number of bytes specified
> > > > > > >    in the "Content-Length" header.
> > > > > > >
> > > > > > > 4. Return to step 1.
> > > > > > >
> > > > > > > /a
> > > > > > >
> > > > > > _______________________________________________
> > > > > > Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping
> > > > > This list is for NEW development of the application of SIP
> > > > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > > > Use sip@ietf.org for new developments of core SIP
> > > > 
> > > > -- 
> > > > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > > > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > > > Telecom R&D               Fax   :  +358  9 299 30 52
> > > > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> > > > Finland                   http://www.hut.fi/~gonzalo
> > > > 
> > > _______________________________________________
> > > Rohc mailing list
> > > Rohc@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/rohc
> > > _______________________________________________
> > > Rohc mailing list
> > > Rohc@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/rohc
> > > 
> > 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 28 17:56:03 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22999
	for <sipping-archive@odin.ietf.org>; Fri, 28 Mar 2003 17:56:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2SNI2E16732
	for sipping-archive@odin.ietf.org; Fri, 28 Mar 2003 18:18:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SNI2O16729
	for <sipping-web-archive@optimus.ietf.org>; Fri, 28 Mar 2003 18:18:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22941
	for <sipping-web-archive@ietf.org>; Fri, 28 Mar 2003 17:55:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SNH0O16489;
	Fri, 28 Mar 2003 18:17:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2QEGaO31739
	for <sipping@optimus.ietf.org>; Wed, 26 Mar 2003 09:16:36 -0500
Received: from rsys002a.roke.co.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26268;
	Wed, 26 Mar 2003 08:55:13 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <HSB1W58P>; Wed, 26 Mar 2003 13:57:33 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED41804A0F206@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>, cabo@tzi.org,
        Lars-Erik.Jonsson@epl.ericsson.se
Cc: rohc@ietf.org, sipping@ietf.org
Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP mes
	sages
Date: Wed, 26 Mar 2003 13:57:32 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Hi,

I think that the issue with SigComp and large binary
content SIP messages is part of a more general issue -
namely that before using SigComp to compress a particular
application we need to standardise the following:

1. Mechanism for SigComp discovery
2. Resources offered by SigComp
3. How to delimit messages
4. When to save state

Currently the SIPPING WG has provided RFCs for 1 and 2,
but not for 3 and 4. It would be useful to get a draft
out for these ASAP, as it would clarify several issues on
how to get SigComp working with SIP (including the issue
with large binary content SIP messages).

> Unless someone objects, I'll submit it in ROHC.

I think that any WG draft should be a product of the
SIPPING WG, because the proposed solution for delimiting
SigComp messages will need to take into account the
behaviour of SIP itself (or we won't be able to multiplex
SigComp and SIP messages on the same port). However, it
would be good to get the ROHC WG involved in generating
the draft as well!

Regards,

Richard

P.S. For anyone who's interested, the mechanisms that
particular applications need to provide before they can
use SigComp are as follows...

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

1. Mechanism for SigComp discovery

   - How does the application know when to use SigComp?

For SIP this issue is already sorted (RFC 3486).

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

2. Resources offered by SigComp

   - Does the application need to offer more than the
     minimum amount of resources?

   - Does the application need any extra state (e.g.
     a static dictionary)?

For SIP we've already got a static dictionary (RFC 3485).
However, we haven't currently discussed how much memory
should be provided in a SigComp implementation for SIP.
If we don't specify a value then SigComp defaults to the
minimum possible (2K), which is rather tight for some of
the more generously sized SIP messages!

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

3. How to delimit messages

   - How does the application distinguish between
     SigComp messages and uncompressed messages?

   - Is the application allowed to use "continuous mode"?

This is the issue that's been raised for large binary
content SIP messages. If we want to send a mix of
uncompressed and SigComp messages within the same TCP
connection, how do we delimit the end of one message and
the start of another?

A related issue is how to handle very large SIP messages
(> 64K). SigComp is able to compress large SIP messages
by using "continuous mode", where the message boundaries
are ignored completely and the application data is just
transmitted as a stream. However, this mode of operation
raises some additional security issues, so it's up to the
SIPPING WG to decide whether or not to use it in SigComp
for SIP.

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

4. When to save state

   - How much security is needed in order to save state?

   - Which messages belong to each state "compartment"?

   - How long should the application keep state?

This is quite an important issue that doesn't seem to
have been discussed in the SIPPING WG. It's up to the
application whether or not to let SigComp save state,
and for interoperability it's important to have at
least a general idea of how long to keep saved state,
when to reject state due to insufficient security etc.

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

> -----Original Message-----
> From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> Sent: Tuesday, March 25, 2003 6:00 PM
> To: cabo@tzi.org; Lars-Erik.Jonsson@epl.ericsson.se
> Cc: rohc@ietf.org; sipping@ietf.org
> Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> messages
> 
> 
> Hi Carsten and Lars-Erik,
> 
> I've volunteered to submit a personal draft on this issue. From
> ROHC WG chairs' point of view, do you think this is the way 
> to proceed?
> 
> Of course, I understood during the IETF56 that Carsten had some
> doubts on whether this is indeed an issue. My email below explained
> the issue a bit. I don't know if it's clear. Either way, we 
> can continue discuss this in ROHC mailing list
> http://www1.ietf.org/mail-archive/working-groups/sipping/current/msg04115.html
> 
> BR,
> Zhigang
> 
> > -----Original Message-----
> > From: ext zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > Sent: March 13, 2003 9:55 AM
> > To: Gonzalo.Camarillo@lmf.ericsson.se
> > Cc: adam@dynamicsoft.com; Isomaki Markus (NRC/Helsinki);
> > mwatson@nortelnetworks.com; sipping@ietf.org; rohc@ietf.org
> > Subject: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> > messages
> > 
> > 
> > I agree. How to handling binary content is a generic issue for any
> > application messages. What I have in mind is to give generic 
> > descriptions/requirements (mainly on the SigComp receiver parsing part),
> > then touch on SIP (perhaps RTSP too) as a particular example.
> > 
> > Unless someone objects, I'll submit it in ROHC.
> > 
> > Zhigang
> > 
> > 
> > > -----Original Message-----
> > > From: ext Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > > Sent: March 13, 2003 5:36 AM
> > > To: Liu Zhigang.C (NRC/Dallas)
> > > Cc: adam@dynamicsoft.com; Isomaki Markus (NRC/Helsinki);
> > > mwatson@nortelnetworks.com; sipping@ietf.org
> > > Subject: Re: [Sipping] SIGCOMP and large binary content SIP messages
> > > 
> > > 
> > > Zhigang,
> > > 
> > > you can submit that draft to ROHC. SIPPING can review it afterwards.
> > > IMO, the competence needed to generate this draft can be found more
> > > easily in ROHC than in SIPPING.
> > > 
> > > Besides, you could use SigComp to compress RTSP messages, for instance
> > > And RTSP is not handle by SIPPING either.
> > > 
> > > Gonzalo
> > > 
> > > zhigang.c.liu@nokia.com wrote:
> > > > 
> > > > Yes, that is also what I had in mind for SIP. But my point is that
> > > > a SigComp receiver now needs to have some knowledge about application
> > > > message format and do parsing to determine the end of an uncompressed
> > > > message. This is something new (or at least unspecified) in RFC 3320
> > > > and needs to be spelled out in a new (standard track) RFC. The document
> > > > will be short, but I think it's needed for interoperability.
> > > > 
> > > > I'll write up an I-D and submit it after IETF 56. But I'd like to know
> > > > if folks in SIPPING think it should be done here or in ROHC.
> > > > 
> > > > Zhigang
> > > > 
> > > > > -----Original Message-----
> > > > > From: ext Adam Roach [mailto:adam@dynamicsoft.com]
> > > > > Sent: March 11, 2003 9:03 PM
> > > > > To: Liu Zhigang.C (NRC/Dallas); Adam Roach; Isomaki Markus
> > > > > (NRC/Helsinki); mwatson@nortelnetworks.com; sipping@ietf.org
> > > > > Subject: RE: [Sipping] SIGCOMP and large binary content SIP messages
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > > > > >
> > > > > > Having binary content in SIP messages may have two impacts on
> > > > > > SigComp:
> > > > > >
> > > > > > a) multiplexing of uncompressed messages with SigComp messages on the
> > > > > > same port.
> > > > > ...
> > > > > > For a), it is only an issue for SigComp/TCP, not SigComp/UDP (where one
> > > > > > SigComp message maps to one UDP packet). Adam's point 1 and 2 are related
> > > > > > to this. As to point 1, I think the SigComp receiver still needs to know
> > > > > > (somehow) the end of an uncompressed message, or at least the end of the
> > > > > > binary part of each SIP messages. Otherwise, a bit pattern 11111 in
> > > > > > the binary part will be mistaken by SigComp as the beginning of a SigComp
> > > > > > message. As to point 2, I would add that the delimiter 0xFFFF can appear
> > > > > > at the both the beginning and the end of a SigComp message. So, the
> > > > > > receiver needs to have the same parsing logic just mentioned for bit pattern
> > > > > > 11111.
> > > > >
> > > > > This isn't any more of an issue than it is without SigComp. SIP
> > > > > messages provide their own framing, and SigComp messages do the
> > > > > same. They can be trivially mixed on the same stream:
> > > > >
> > > > > 1. Peek at the first byte waiting in the stream.
> > > > >
> > > > > 2. If it is 0xf8 or higher, the next message in the stream is
> > > > >    a SigComp message. The message continues until a 0xFFFF is
> > > > >    encountered in the stream.
> > > > >
> > > > > 3. Otherwise, the next message in the stream is a SIP message.
> > > > >    Read the stream until a CR/LF/CR/LF is encountered. Parse
> > > > >    the headers, and then read the number of bytes specified
> > > > >    in the "Content-Length" header.
> > > > >
> > > > > 4. Return to step 1.
> > > > >
> > > > > /a
> > > > >
> > > > _______________________________________________
> > > > Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sip@ietf.org for new developments of core SIP
> > 
> > -- 
> > Gonzalo Camarillo         Phone :  +358  9 299 33 71
> > Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> > Telecom R&D               Fax   :  +358  9 299 30 52
> > FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> > Finland                   http://www.hut.fi/~gonzalo
> > 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Fri Mar 28 20:04:24 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27299
	for <sipping-archive@odin.ietf.org>; Fri, 28 Mar 2003 20:04:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2T1QNM24479
	for sipping-archive@odin.ietf.org; Fri, 28 Mar 2003 20:26:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2T1QNO24476
	for <sipping-web-archive@optimus.ietf.org>; Fri, 28 Mar 2003 20:26:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27291
	for <sipping-web-archive@ietf.org>; Fri, 28 Mar 2003 20:03:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2T1PVO24421;
	Fri, 28 Mar 2003 20:25:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2T1NoO24355
	for <sipping@optimus.ietf.org>; Fri, 28 Mar 2003 20:23:50 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27238
	for <sipping@ietf.org>; Fri, 28 Mar 2003 20:01:18 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by auemail1.firewall.lucent.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2T13cT06056
	for <sipping@ietf.org>; Fri, 28 Mar 2003 20:03:39 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <XNTC80P4>; Sat, 29 Mar 2003 01:03:37 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00806948B@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: Al Varney <varney@ieee.org>, "Peterson, Jon"
	 <jon.peterson@neustar.biz>,
        sipping@ietf.org
Subject: RE: [Sipping] New version of the early media draft
Date: Sat, 29 Mar 2003 01:03:35 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

For information, I think pretty well all the proponents of needing to distinguish three different cases of information provision do not really care how the coding distinguishes those three cases. 

The main person who keeps returning the discussion to particular encodings is Jon Peterson, who consistently argues that there are not three cases.

And yes we do need to agree codings at the end, but one step at a time.

Keith

Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 

> -----Original Message-----
> From: Al Varney [mailto:varney@ieee.org]
> Sent: 28 March 2003 03:05
> To: Peterson, Jon; sipping@ietf.org
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> I haven't seen any "results" from the Early-Media Ad-Hoc (if 
> it was held), 
> so I'll toss out something I would have stated had I been there....
> 
> At 04:50 PM 3/14/03 -0500, Peterson, Jon wrote:
> >They are proverbially out of luck in the CAS interworking 
> case, no? Again,
> >it's not our fault that ISUP doesn't present its status accurately
> >out-of-band.
> 
>     Absolutely true.  Even more so for MF or DP trunks off a SIP 
> gateway.  You can't fix the past, but you do have to worry 
> about embedded base.
> 
> >Anyway, this is speaking to a pair of separable issues. 
> Whether or not we
> >send pre-answer media with a 180 is separable from whether 
> or not we need
> >some SIP-layer indication that we are doing so. Personally, 
> I think we're in
> >a bad position to deal with cases where ISUP provides 
> valuable in-band
> >information but doesn't tell us so in the encoding of an 
> ACM, and I don't
> >think it is reasonable for us to always send pre-answer 
> media on receipt of
> >ACM. But this is a separate issue.
> >
> >If we send 180, and subsequently send media, we could very 
> well be deceiving
> >a deaf user (or a user whose UA simply doesn't render 
> pre-answer media) into
> >thinking that 'alerting' tells the whole story. But if 
> 'alerting' told the
> >whole story, there'd be no need to send any pre-answer media 
> to accompany
> >it. This is the paradox I keep hearing - people want to see 
> an indicator
> >that says "alerting" and play early media, but they simultaneously
> >acknowledge that the reason they want the early media is because it
> >qualifies the alerting state in some fashion.  How valuable is the
> >"alerting" state at the UAC, then?
> 
>     OK -- so folks want "alerting" and early media (as in ISUP), 
> particularly for cases when interworking with the old PSTN.  
> Then why add a 
> SIP-early-media indicator to 180?  Instead, why not add an "alerting" 
> indicator to 183 -- which maps rather well to ISUP ACM 
> practice (ACM always 
> implies in-band media in the backward direction, and it 
> sometimes indicates 
> 'user free'/alerting).  It also maps to/from ISDN in an 
> obvious manner.
> 
>     This leaves 180 untarnished as an explicit "alerting and 
> no intended 
> early media" indicator, and local ringback could always be 
> generated.  Any 
> pre-200 media could be assumed to have gotten ahead of SIP 
> messaging, and 
> it could be cut through to the caller either immediately or 
> after a short 
> delay.
> 
>     Adding a new indicator to 183 for "user being alerted" is 
> backward 
> compatible, since RTP media would be there even if the new 
> indicator was 
> ignored.  And for cases where the indicator WAS recognized, a 
> display or 
> forking treatment similar to that for 180 could be used.  
> Some UA could 
> even generate local ringback if it really, really wanted to do so.
> 
>     The major advantage would be better compatibility with SIP-ISUP 
> gateways for interworking, and the preservation of 180 for 
> cases where 
> SIP-aware signaling was used end-to-end.  Or where gateways 
> that could 
> distinguish true alerting cases (a gateway with 
> directly-connected lines, 
> for example, always knows the true alerting state of a 
> terminal).  Over 
> time, SIP-to-SIP calls would all tend to use 180, and the old 
> PSTN behavior 
> would be contained within 183 handling (where it already has 
> to exist).
> 
>     (While adding indicators to 183, would it also be useful 
> to have a "SIP 
> not used all-the-way" indicator that indicates interworking 
> to non-SIP 
> protocols?   Or would a UA always behave the same for 
> gateways sending 183 
> and called-UAs sending 183?)
> 
>     View this as a comment thrown out into a late-night 
> Ad-Hoc session.
> 
> Al Varney
> 
> >I would be more sympathetic to this view if the 'alerting' 
> state had some
> >specific semantics at the UAC pointed out in RFC3261 that 
> differentiated
> >'180 received' from '183 received' or other provisional 
> states - but it
> >doesn't. There's nothing magical about receiving a 180 
> response. It's been
> >suggested that this is valuable for forking composition, but in my
> >estimation, if there's in-band media associated with a 
> provisional branch of
> >a fork, you need to evaluate that media, not the status code (again,
> >otherwise, why send the media at all?). Some sort of 180 
> indicator that
> >suppresses local ringback doesn't help you either way with 
> any of these
> >problems.
> >
> >Jon Peterson
> >NeuStar, Inc.
> >
> > > -----Original Message-----
> > > From: Michael Hammer [mailto:mhammer@cisco.com]
> > > Sent: Friday, March 14, 2003 12:51 PM
> > > To: Peterson, Jon
> > > Cc: 'Drage, Keith (Keith)'; 'Elwell, John'; 'Mark Watson';
> > > 'sipping@ietf.org'
> > > Subject: RE: [Sipping] New version of the early media draft
> > >
> > >
> > > Jon,
> > >
> > > Doesn't the possibility of deaf users preclude the use of 183
> > > from being
> > > used, as has been suggested, since they won't hear the
> > > locally injected
> > > ringback or the inband media?
> > >
> > > Mike
> > >
> > >
> > > At 05:52 AM 3/14/2003 -0500, Peterson, Jon wrote:
> > >
> > > >Below.
> > > >
> > > >Jon Peterson
> > > >NeuStar, Inc.
> > >
> >_______________________________________________
> >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >This list is for NEW development of the application of SIP
> >Use sip-implementors@cs.columbia.edu for questions on current sip
> >Use sip@ietf.org for new developments of core SIP
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sat Mar 29 01:49:48 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03367
	for <sipping-archive@odin.ietf.org>; Sat, 29 Mar 2003 01:49:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2T7Btl20666
	for sipping-archive@odin.ietf.org; Sat, 29 Mar 2003 02:11:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2T7BtO20663
	for <sipping-web-archive@optimus.ietf.org>; Sat, 29 Mar 2003 02:11:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03357
	for <sipping-web-archive@ietf.org>; Sat, 29 Mar 2003 01:49:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2T7B4O20169;
	Sat, 29 Mar 2003 02:11:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2T772O14299
	for <sipping@optimus.ietf.org>; Sat, 29 Mar 2003 02:07:02 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03206
	for <sipping@ietf.org>; Sat, 29 Mar 2003 01:44:24 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2T6keC08767;
	Sat, 29 Mar 2003 06:46:40 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JW0SX>; Sat, 29 Mar 2003 01:47:22 -0500
Message-ID: <0449D80A0E9B614A83FA9031B07E8D3B257940@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Drage, Keith (Keith)'" <drage@lucent.com>, Al Varney
	 <varney@ieee.org>,
        sipping@ietf.org
Subject: RE: [Sipping] New version of the early media draft
Date: Sat, 29 Mar 2003 01:47:14 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Yes, well, I agree the issue of how we encode things in SIP is secondary to
the issue of what we hope the encodings will accomplish. I have been trying
to flush out the requirement for this encoding for some time now.

It is clear that a UAS can send a 180, and then send RTP, right? UACs need
to accept that sequence to prevent post-answer media clipping. If there's
some mysterious property that will be provided to a SIP UAC by virtue of
receiving the 180 and then receiving RTP, nothing is preventing a UAS from
sending just that. On an unrelated point, I also happen to think that
sending early media in SIP is generally bad, and we should avoid it as often
as possible, but that's not material to this issue - clearly, early media
must be sent in some cases, and we need to decide what we do then.

My concern is that some provisional response parameter (be it in 180 or 183)
stating that media will or will not be sent is pointless given that the UAS
can just send media with any 18x. Arguments that decomposed UACs will be
more responsive to SIP-layer indications than to the receipt of RTP seem
misguided to me in light of the fact that the UAC must be prepared to
receive and appropriately handle RTP with or without any forewarning (even
granting the questionable assumption that a SIP-layer indication would
actually arrive before the RTP itself). I am totally unsympathetic to
arguments that MGCP or Megaco-based MGC UACs are unable to be SIP-compliant
in this respect, and that we should therefore install new behavior in SIP to
compensate for their inadequacy.

Another problem is the idea that SIP has some special 'alerting' state
comparable to that of ISUP, and that if 180 is not received, this 'alerting'
state will not be reached. I'm not sure what UAC behavior the advocates of
this position imagine will result from 180 that will not result from 183. If
anyone can substantiate this for me, preferably with some citation from
RFC3261, that would go a long way towards putting this issue to rest.

Personally, I would be happy to compromise on the details of this encoding
if I understood why people want it in the first place.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Drage, Keith (Keith) [mailto:drage@lucent.com]
> Sent: Friday, March 28, 2003 5:04 PM
> To: Al Varney; Peterson, Jon; sipping@ietf.org
> Subject: RE: [Sipping] New version of the early media draft
> 
> 
> For information, I think pretty well all the proponents of 
> needing to distinguish three different cases of information 
> provision do not really care how the coding distinguishes 
> those three cases. 
> 
> The main person who keeps returning the discussion to 
> particular encodings is Jon Peterson, who consistently argues 
> that there are not three cases.
> 
> And yes we do need to agree codings at the end, but one step 
> at a time.
> 
> Keith
> 
> Keith Drage
> Lucent Technologies
> Tel: +44 1793 776249
> Email: drage@lucent.com 
> 
> > -----Original Message-----
> > From: Al Varney [mailto:varney@ieee.org]
> > Sent: 28 March 2003 03:05
> > To: Peterson, Jon; sipping@ietf.org
> > Subject: RE: [Sipping] New version of the early media draft
> > 
> > 
> > I haven't seen any "results" from the Early-Media Ad-Hoc (if 
> > it was held), 
> > so I'll toss out something I would have stated had I been there....
> > 
> > At 04:50 PM 3/14/03 -0500, Peterson, Jon wrote:
> > >They are proverbially out of luck in the CAS interworking 
> > case, no? Again,
> > >it's not our fault that ISUP doesn't present its status accurately
> > >out-of-band.
> > 
> >     Absolutely true.  Even more so for MF or DP trunks off a SIP 
> > gateway.  You can't fix the past, but you do have to worry 
> > about embedded base.
> > 
> > >Anyway, this is speaking to a pair of separable issues. 
> > Whether or not we
> > >send pre-answer media with a 180 is separable from whether 
> > or not we need
> > >some SIP-layer indication that we are doing so. Personally, 
> > I think we're in
> > >a bad position to deal with cases where ISUP provides 
> > valuable in-band
> > >information but doesn't tell us so in the encoding of an 
> > ACM, and I don't
> > >think it is reasonable for us to always send pre-answer 
> > media on receipt of
> > >ACM. But this is a separate issue.
> > >
> > >If we send 180, and subsequently send media, we could very 
> > well be deceiving
> > >a deaf user (or a user whose UA simply doesn't render 
> > pre-answer media) into
> > >thinking that 'alerting' tells the whole story. But if 
> > 'alerting' told the
> > >whole story, there'd be no need to send any pre-answer media 
> > to accompany
> > >it. This is the paradox I keep hearing - people want to see 
> > an indicator
> > >that says "alerting" and play early media, but they simultaneously
> > >acknowledge that the reason they want the early media is because it
> > >qualifies the alerting state in some fashion.  How valuable is the
> > >"alerting" state at the UAC, then?
> > 
> >     OK -- so folks want "alerting" and early media (as in ISUP), 
> > particularly for cases when interworking with the old PSTN.  
> > Then why add a 
> > SIP-early-media indicator to 180?  Instead, why not add an 
> "alerting" 
> > indicator to 183 -- which maps rather well to ISUP ACM 
> > practice (ACM always 
> > implies in-band media in the backward direction, and it 
> > sometimes indicates 
> > 'user free'/alerting).  It also maps to/from ISDN in an 
> > obvious manner.
> > 
> >     This leaves 180 untarnished as an explicit "alerting and 
> > no intended 
> > early media" indicator, and local ringback could always be 
> > generated.  Any 
> > pre-200 media could be assumed to have gotten ahead of SIP 
> > messaging, and 
> > it could be cut through to the caller either immediately or 
> > after a short 
> > delay.
> > 
> >     Adding a new indicator to 183 for "user being alerted" is 
> > backward 
> > compatible, since RTP media would be there even if the new 
> > indicator was 
> > ignored.  And for cases where the indicator WAS recognized, a 
> > display or 
> > forking treatment similar to that for 180 could be used.  
> > Some UA could 
> > even generate local ringback if it really, really wanted to do so.
> > 
> >     The major advantage would be better compatibility with SIP-ISUP 
> > gateways for interworking, and the preservation of 180 for 
> > cases where 
> > SIP-aware signaling was used end-to-end.  Or where gateways 
> > that could 
> > distinguish true alerting cases (a gateway with 
> > directly-connected lines, 
> > for example, always knows the true alerting state of a 
> > terminal).  Over 
> > time, SIP-to-SIP calls would all tend to use 180, and the old 
> > PSTN behavior 
> > would be contained within 183 handling (where it already has 
> > to exist).
> > 
> >     (While adding indicators to 183, would it also be useful 
> > to have a "SIP 
> > not used all-the-way" indicator that indicates interworking 
> > to non-SIP 
> > protocols?   Or would a UA always behave the same for 
> > gateways sending 183 
> > and called-UAs sending 183?)
> > 
> >     View this as a comment thrown out into a late-night 
> > Ad-Hoc session.
> > 
> > Al Varney
> > 
> > >I would be more sympathetic to this view if the 'alerting' 
> > state had some
> > >specific semantics at the UAC pointed out in RFC3261 that 
> > differentiated
> > >'180 received' from '183 received' or other provisional 
> > states - but it
> > >doesn't. There's nothing magical about receiving a 180 
> > response. It's been
> > >suggested that this is valuable for forking composition, but in my
> > >estimation, if there's in-band media associated with a 
> > provisional branch of
> > >a fork, you need to evaluate that media, not the status 
> code (again,
> > >otherwise, why send the media at all?). Some sort of 180 
> > indicator that
> > >suppresses local ringback doesn't help you either way with 
> > any of these
> > >problems.
> > >
> > >Jon Peterson
> > >NeuStar, Inc.
> > >
> > > > -----Original Message-----
> > > > From: Michael Hammer [mailto:mhammer@cisco.com]
> > > > Sent: Friday, March 14, 2003 12:51 PM
> > > > To: Peterson, Jon
> > > > Cc: 'Drage, Keith (Keith)'; 'Elwell, John'; 'Mark Watson';
> > > > 'sipping@ietf.org'
> > > > Subject: RE: [Sipping] New version of the early media draft
> > > >
> > > >
> > > > Jon,
> > > >
> > > > Doesn't the possibility of deaf users preclude the use of 183
> > > > from being
> > > > used, as has been suggested, since they won't hear the
> > > > locally injected
> > > > ringback or the inband media?
> > > >
> > > > Mike
> > > >
> > > >
> > > > At 05:52 AM 3/14/2003 -0500, Peterson, Jon wrote:
> > > >
> > > > >Below.
> > > > >
> > > > >Jon Peterson
> > > > >NeuStar, Inc.
> > > >
> > >_______________________________________________
> > >Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > >This list is for NEW development of the application of SIP
> > >Use sip-implementors@cs.columbia.edu for questions on current sip
> > >Use sip@ietf.org for new developments of core SIP
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> > 
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sat Mar 29 10:43:38 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24163
	for <sipping-archive@odin.ietf.org>; Sat, 29 Mar 2003 10:43:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2TG5vU16611
	for sipping-archive@odin.ietf.org; Sat, 29 Mar 2003 11:05:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2TG5vO16608
	for <sipping-web-archive@optimus.ietf.org>; Sat, 29 Mar 2003 11:05:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24148
	for <sipping-web-archive@ietf.org>; Sat, 29 Mar 2003 10:43:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2TG5CO16594;
	Sat, 29 Mar 2003 11:05:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2TG3TO16522
	for <sipping@optimus.ietf.org>; Sat, 29 Mar 2003 11:03:29 -0500
Received: from acmepacket.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24083
	for <sipping@ietf.org>; Sat, 29 Mar 2003 10:40:40 -0500 (EST)
Received: from BPenfield [127.0.0.1] by acmepacket.com
  (SMTPD32-7.14) id AF0754640302; Sat, 29 Mar 2003 10:43:03 -0500
Message-ID: <000e01c2f609$d5730a20$2300000a@BPenfield>
From: "Bob Penfield" <bpenfield@acmepacket.com>
To: <sipping@ietf.org>
References: <0449D80A0E9B614A83FA9031B07E8D3B257940@stntexch2.va.neustar.com>
Subject: Re: [Sipping] New version of the early media draft
Date: Sat, 29 Mar 2003 10:42:41 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Peterson, Jon" <jon.peterson@neustar.biz>
<snip>
>
> Another problem is the idea that SIP has some special 'alerting' state
> comparable to that of ISUP, and that if 180 is not received, this
'alerting'
> state will not be reached. I'm not sure what UAC behavior the advocates of
> this position imagine will result from 180 that will not result from 183.
If
> anyone can substantiate this for me, preferably with some citation from
> RFC3261, that would go a long way towards putting this issue to rest.
>

Even the RFC 3261 definition of 180 uses the term "alert".
180 is not the same as 183 and UAs (e.g. SIP Phones) do treat them
differently in order to provide the best user experience.

RFC 3261 defines 180 as:

    The UA receiving the INVITE is trying to alert the user.
    This response MAY be used to initiate local ringback.

where 183 is defined as:

   The 183 (Session Progress) response is used to convey information
   about the progress of the call that is not otherwise classified.

I'm not saying that 180 means exactly the same thing as alerting in ISUP,
but when the UAC receives a 180, it can reasonably believe that the call has
progressed to the point that it can render "Ringing" to the user whether
that is by displaying something on a screen (with or without inband media),
flash a light, or playing local ringback in the absence of inband media. No
such assumption can be made when a 183 response is received.

Regardless of the type of UAS or interworking protocol, if a UAS can
determine that the call has reached a state where it (or an endpoint at the
other side of the non-SIP network) is "trying to alert the user", it should
send 180. The response codes 180, 181, and 182 do have specific meaning in
SIP and whenever a reasonable mapping from states in a interworking protocol
can be made, they should be.

BTW, I do support your position that no additional indication of the
presence or absence of early media is required in SIP signaling. If UAC
receives media, it should play it.

cheers,
(-:bob



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Sun Mar 30 11:56:07 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00887
	for <sipping-archive@odin.ietf.org>; Sun, 30 Mar 2003 11:56:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2UHIvX15935
	for sipping-archive@odin.ietf.org; Sun, 30 Mar 2003 12:18:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2UHIvO15932
	for <sipping-web-archive@optimus.ietf.org>; Sun, 30 Mar 2003 12:18:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00879
	for <sipping-web-archive@ietf.org>; Sun, 30 Mar 2003 11:55:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2UHHwO15889;
	Sun, 30 Mar 2003 12:17:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2UHGuO15865
	for <sipping@optimus.ietf.org>; Sun, 30 Mar 2003 12:16:56 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00863
	for <sipping@ietf.org>; Sun, 30 Mar 2003 11:53:35 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2UGtvUE027428;
	Sun, 30 Mar 2003 18:55:57 +0200 (MEST)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id HK1WB26F; Sun, 30 Mar 2003 18:55:57 +0200
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.106.10])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2UGtvpn014119;
	Sun, 30 Mar 2003 19:55:57 +0300 (EET DST)
Message-ID: <3E87219B.861C0AD6@lmf.ericsson.se>
Date: Sun, 30 Mar 2003 19:55:55 +0300
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Bob Penfield <bpenfield@acmepacket.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] New version of the early media draft
References: <0449D80A0E9B614A83FA9031B07E8D3B257940@stntexch2.va.neustar.com> <000e01c2f609$d5730a20$2300000a@BPenfield>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi,

The spec currently says that "a UAC shall be able to receive media as soon as
the INVITE is sent".

Now, there may be reasons why a UAC is not able to do that. For example, it may
need the remote SDP before I starts accepting media. We have to remember that
SIP does not specify a specific bearer (unlike H.323, which uses RTP), so one
could argue the SIP spec should not contain these kind of statements in the
first place. After all, SIP is a pure signalling protocol.

But, going back to the early media discussion, my question is: should it also
include the offer/answer aspect? Now we only talk about the meaning of 180 etc,
assuming there is no need to consider the actual media part, since the UAC shall
be able to receive media at all time...

Regards,

Christer Holmberg
Ericsson Finland














Bob Penfield wrote:

> ----- Original Message -----
> From: "Peterson, Jon" <jon.peterson@neustar.biz>
> <snip>
> >
> > Another problem is the idea that SIP has some special 'alerting' state
> > comparable to that of ISUP, and that if 180 is not received, this
> 'alerting'
> > state will not be reached. I'm not sure what UAC behavior the advocates of
> > this position imagine will result from 180 that will not result from 183.
> If
> > anyone can substantiate this for me, preferably with some citation from
> > RFC3261, that would go a long way towards putting this issue to rest.
> >
>
> Even the RFC 3261 definition of 180 uses the term "alert".
> 180 is not the same as 183 and UAs (e.g. SIP Phones) do treat them
> differently in order to provide the best user experience.
>
> RFC 3261 defines 180 as:
>
>     The UA receiving the INVITE is trying to alert the user.
>     This response MAY be used to initiate local ringback.
>
> where 183 is defined as:
>
>    The 183 (Session Progress) response is used to convey information
>    about the progress of the call that is not otherwise classified.
>
> I'm not saying that 180 means exactly the same thing as alerting in ISUP,
> but when the UAC receives a 180, it can reasonably believe that the call has
> progressed to the point that it can render "Ringing" to the user whether
> that is by displaying something on a screen (with or without inband media),
> flash a light, or playing local ringback in the absence of inband media. No
> such assumption can be made when a 183 response is received.
>
> Regardless of the type of UAS or interworking protocol, if a UAS can
> determine that the call has reached a state where it (or an endpoint at the
> other side of the non-SIP network) is "trying to alert the user", it should
> send 180. The response codes 180, 181, and 182 do have specific meaning in
> SIP and whenever a reasonable mapping from states in a interworking protocol
> can be made, they should be.
>
> BTW, I do support your position that no additional indication of the
> presence or absence of early media is required in SIP signaling. If UAC
> receives media, it should play it.
>
> cheers,
> (-:bob
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 02:33:00 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28175
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 02:33:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2V7u8613442
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 02:56:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2V7u8O13439
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 02:56:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28169
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 02:32:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2V7tQO13396;
	Mon, 31 Mar 2003 02:55:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2V7qVO13230
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 02:52:31 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28102
	for <sipping@ietf.org>; Mon, 31 Mar 2003 02:28:52 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2V7VGrs004410;
	Mon, 31 Mar 2003 09:31:16 +0200 (MEST)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id HKFZB7VH; Mon, 31 Mar 2003 09:31:17 +0200
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2V7VHpn024503;
	Mon, 31 Mar 2003 10:31:17 +0300 (EET DST)
Message-ID: <3E87EEC4.1F974505@lmf.ericsson.se>
Date: Mon, 31 Mar 2003 10:31:17 +0300
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sipping@ietf.org
CC: Jon Peterson <Jon.Peterson@neustar.com>,
        Mark Watson <mwatson@nortelnetworks.com>
References: <0449D80A0E9B614A83FA9031B07E8D3B257940@stntexch2.va.neustar.com> <000e01c2f609$d5730a20$2300000a@BPenfield>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Early media; a summary after the IETF
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

here you have a summary of what happened in the IETF regarding early
media.

We planned to have an ad-hoc meeting, but since we managed to get more
meeting time than expected for this issue and some of the persons
involved in the mailing list discussions were not available for an
ad-hoc meeting (some of them were not even in San Francisco), we did not
finally have the ad-hoc.

Regarding the discussions during the second SIPPING session, the main
input was slide number 3 of

http://www.softarmor.com/sipping/meets/ietf56/slides/Gonzalo-sipping-early-media.ppt

That slide does not discuss the encoding issue. It focuses on the
requirements or the gains that adding a SIP "there is media coming" (or
"don't generate local ringback") indication would bring.

The conclusion of that slide is that a message with "generate local
ringback until media arrives" should be provided by the protocol (e.g.,
MGCP or H.248) between the MG and the MGC **REGARDLESS** of whether or
not we create a "there is media coming" flag.

Therefore, assuming that the MG is in accept-media state as soon as the
INVITE is sent, the only gain that a "there is media coming" would bring
would be saving one message from the MGC to the MG every time a 180 with
a flag is received. The gain is zero for 180 responses without the flag.

The question is: are people after this optimization (saving of one
message in some circumstances) or there is somebody with something else
in mind?


In any event, the conclusion of the meeting was that I will be gathering
use cases where a "there is media coming" flag would be useful. Please,
send any use case you have in mind and I will compile them in a
document. We hope that such a document help us figure out which
requirement is missing.

We also may organize a conference call in some weeks to further discuss
the issue, if needed.

Thanks,

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 05:31:00 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00993
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 05:31:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2VAsBd24711
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 05:54:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VAsAO24708
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 05:54:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00988
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 05:30:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VArOO24681;
	Mon, 31 Mar 2003 05:53:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VAqeO24653
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 05:52:40 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00948
	for <sipping@ietf.org>; Mon, 31 Mar 2003 05:28:58 -0500 (EST)
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2VAVMrs027951;
	Mon, 31 Mar 2003 12:31:22 +0200 (MEST)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id 2AG4KC7L; Mon, 31 Mar 2003 12:31:22 +0200
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2VAVMpn006600;
	Mon, 31 Mar 2003 13:31:22 +0300 (EET DST)
Message-ID: <3E8818F9.16D027B@lmf.ericsson.se>
Date: Mon, 31 Mar 2003 13:31:21 +0300
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] netann Open Issue #1: Media on Hold
References: <4A3384433CE2AB46A63468CB207E209D248967@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Eric,

> Note that hold is not an issue for early media: it is not possible to put early media on hold.

Why is it different for early media than for regular media? You can put
any type of media on hold... what did you have in mind?

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 05:33:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01055
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 05:33:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2VAulR24835
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 05:56:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VAulO24832
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 05:56:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01051
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 05:33:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VAu6O24791;
	Mon, 31 Mar 2003 05:56:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VAtkO24766
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 05:55:46 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01030
	for <sipping@ietf.org>; Mon, 31 Mar 2003 05:32:04 -0500 (EST)
Received: from esealnt610.al.sw.ericsson.se (alteon-nat3.sw.ericsson.se [153.88.254.120])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2VAYSrs028927;
	Mon, 31 Mar 2003 12:34:28 +0200 (MEST)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id 2AGQZZ4J; Mon, 31 Mar 2003 12:34:28 +0200
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2VAYSpn006699;
	Mon, 31 Mar 2003 13:34:29 +0300 (EET DST)
Message-ID: <3E8819B3.608F3890@lmf.ericsson.se>
Date: Mon, 31 Mar 2003 13:34:27 +0300
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] netann Issue #3: Multiple Media Streams
References: <4A3384433CE2AB46A63468CB207E209D248969@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Eric,

> Option 3 means that one could not play media from different sources in a single netann session.

8< [snip] 8<

> Our proposal is to do Option 3.

Yes, applying the KISS rule here sounds sensible.

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 05:46:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01255
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 05:46:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2VB9lM26030
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 06:09:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VB9lO26027
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 06:09:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01249
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 05:46:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VB89O25979;
	Mon, 31 Mar 2003 06:08:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VB77O25397
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 06:07:07 -0500
Received: from albatross.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01221
	for <sipping@ietf.org>; Mon, 31 Mar 2003 05:43:24 -0500 (EST)
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by albatross.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2VAjmUE024753;
	Mon, 31 Mar 2003 12:45:48 +0200 (MEST)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id 2AG4KG8P; Mon, 31 Mar 2003 12:45:49 +0200
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2VAjnpn007594;
	Mon, 31 Mar 2003 13:45:49 +0300 (EET DST)
Message-ID: <3E881C5C.CC87EE06@lmf.ericsson.se>
Date: Mon, 31 Mar 2003 13:45:48 +0300
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] netann Issue #2: Result Code for Early Media Termination
References: <4A3384433CE2AB46A63468CB207E209D248968@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Eric,

the issue here is that you are using the INVITE request in a very
peculiar way. Typically, the purpose of an INVITE is to establish a
session. That's why, when the session is established, you send a 200 OK
(the purpose of the INVITE - session establishment - went OK).

However, you are proposing to send an INVITE whose purpose is not
establishing a session. Its purpose is to do something in the media
stream, and then send back a status code saying that the purpose of the
INVITE (not establishing a session, but playing an early announcement)
went OK.

On one hand, you would want to send a 200 OK (the announcement was
played)... but on the other hand, you cannot (there was no session
established).

Thus, you are looking for a status code that means "OK" for this
particular scenario...

In any event, since you say in the draft that an INVITE that triggers an
announcement has an implicit CANCEL associated to it, 487 sounds like
the most appropriate status code.

Besides, I would assume that this status code will seldom reach the UAC.
The proxy (application server) will typically provide the UAC a more
meaningful status code to the UAC (e.g., Busy) upone reception of the
487 from the media server.

Gonzalo



Eric Burger wrote:
> 
> Problem: How does the media server signal that it has completed an early media announcement?
> 
> Prior drafts had the media server send a 487 REQUEST TERMINATED result code.  However, RFC3261 reserves that result code as a response to a request sent after the UAS has processed a BYE or CANCEL from the UAC.
> 
> The behavior netann seeks is identical in every way to a user that rejects a *particular* connection attempt.  That is, the rejection must not imply the user is not there, will not be there later, or that there is a failure at the media server.  We cannot have a proxy server optimize attempts by thinking that the annc user is not available and thus should not make follow-on connection attempts.
> 
> Options are:
> 
> 410 GONE - Doesn't work because this implies a permanent condition; "annc" clearly is still at the media server.
> 
> 480 TEMPORARILY UNAVAILABLE - looks identical to a user rejecting a call, e.g., Do-Not-Disturb.  Implies that another attempt to the same user (annc) may succeed.
> 
> 486 BUSY HERE - also a good choice: identical to a user rejecting a call, AND lets the UAC play local busy tone after the announcement finishes.  If the user misses the announcement, they will still get meaningful call progress.  Note that 486 was the result code used in -00.  It was changed to 487 in -01 because some people felt that 486 might indicate something about the original target of the request that was not true.
> 
> 487 REQUEST TERMINATED - we were trying to capture the idea of a request that had some treatment but was ultimately canceled.  Thus there was a virtual CANCEL from the UAC after the announcement played.  Even though any 4xx response should terminate a session, there is a non-conforming SIP phone that ignores 487's on dialogs where the phone did not send a CANCEL or BYE.
> 
> 600 BUSY EVERYWHERE - a good choice: not only does it look like the user rejecting a call and the UAC playing local busy as in 486, but it stops forking proxies from continuing a search at locations other than the one that resulted in an announcement.  The only problem is, this might be seen as a bug, not a feature.
> 
> 603 DECLINE - this would be an excellent choice, except for one possible problem.  6xx responses are 'definitive'. My concern is a zealous proxy might 'optimize' a 6xx response and hold-off further attempts to a given request-URI.  In fact, that is the correct action if there is a Retry-After header.  If the media server could return 603 with a Retry-After: 0, then there would not be a problem.  However, zero is not a valid Retry-After value.  Although it is not conforming behavior, if a proxy uses a non-zero default Retry-After value, future announcement requests will be blocked for a period of time.
> 
> 4xx or 6xx new code - we could "say what we mean" and create a new response code.  The semantics of this code are "the user rejected the call."  However, given that this is identical to 480 or 603, why would we not simply use 480 or 603?
> 
> Proposal:
> Use 480, because we do not want to break meaningful forking proxies.
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 06:04:23 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01683
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 06:04:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2VBRYX26719
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 06:27:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VBRYO26716
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 06:27:34 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01631
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 06:03:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VBQSO26674;
	Mon, 31 Mar 2003 06:26:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VBPeO26630
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 06:25:40 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01568
	for <sipping@ietf.org>; Mon, 31 Mar 2003 06:01:58 -0500 (EST)
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2VB4Mrs007898;
	Mon, 31 Mar 2003 13:04:22 +0200 (MEST)
Received: from hendrix.lmf.ericsson.se ([131.160.11.8]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id 2AG6FYAC; Mon, 31 Mar 2003 13:04:22 +0200
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.19])
	by hendrix.lmf.ericsson.se (8.12.8/8.12.8/lmf-2.1-jcs) with ESMTP id h2VB4Mpn008649;
	Mon, 31 Mar 2003 14:04:22 +0300 (EET DST)
Message-ID: <3E8820B5.CB7A29DA@lmf.ericsson.se>
Date: Mon, 31 Mar 2003 14:04:21 +0300
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Comments on netan
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Eric,

Here you have some comments on the netann draft:

http://www.ietf.org/internet-drafts/draft-burger-sipping-netann-05.txt

Abstract: I would clarify in the abstract that the media server speaks
SIP as well. Reading it for the first time is not clear... maybe you can
clarify it in the Introduction as well.

Section 2: the draft says:

"For per-service security, the media server MAY use any of the
   security protocols described in RFC3261 [2].

   The media server MAY issue 401 challenges for authentication."

This two statements are a consequence of having the application server
and the media server speak SIP. Therefore, you should not introduce any
normative behaviour in the draft.

You may want to add a note without normative language saying what you
say in those two paragraphs, though.

The draft says:
"Per RFC3261 [2], the service indicator is case insensitive."

The user part of a SIP URI is case-sensitive; quoting RFC 3261, top of
page 154.

"o  Comparison of the userinfo of SIP and SIPS URIs is case-
         sensitive.  This includes userinfo containing passwords or
         formatted as telephone-subscribers.  Comparison of all other
         components of the URI is case-insensitive unless explicitly
         defined otherwise.
"

Why does the draft say that the service indicator is case-insensitive?

Section 3: In the second paragraph, I would say up front that in SIP,
this is called "early media". You refer to early media leter in the
draft, so this is a good place to explain what it is.

Further down in Section 3, the draft says:
"To support the
   appropriate paradigm, the media server issues a 100 TRYING response,
   followed immediately by a 183 SESSION PROGRESS response with SDP."

If you are sending a 183 "immediately", you do not need to send the 100
Trying.

The same comment at the bottom of page 9, where you also send a "100
TRYING followed by a 183 SESSION PROGRESS".

The last sentence of Section 3.2.1 says "the proxy then issues a
BYE...". I would say that the "proxy *proxies* the BYE to... 

Having a proxy "issue" a request makes it look like a B2BUA, right?

Section 3.3.2: 200 OK for the PRACK is missing.


Regarding the 409 vs. 487 reponses issue, I already sent a reply to your
mail saying that, if you follow the paradigm you propose, a 487 response
seems to be more appropriate. However, as I suggested in that note, I do
not like that paradigm. When a UAC send a request, it can fork to reach
the user at several locations (UASs). Any of those UASs will send back
status codes reflecting the status of the user (e.g., busy). However,
now you are sending this request to a media server that will send back a
response that has nothing to do with the status of that user. 

I believe that it would be more appropriate for the applications server
to behave as a B2BUA. That is, the SIP dialog with the UAC is not the
same as the SIP dialog with the media server. To me, this would be a
better way of implementing the a vertical interface you propose between
the application server and the media server.

Regards,

Gonzalo
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 10:02:52 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08435
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 10:02:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2VFQ9S10346
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 10:26:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VFQ9O10343
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 10:26:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08408
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 10:02:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VFPIO10298;
	Mon, 31 Mar 2003 10:25:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VFOfO10251
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 10:24:41 -0500
Received: from zcars04f.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08334
	for <sipping@ietf.org>; Mon, 31 Mar 2003 10:00:52 -0500 (EST)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h2VF38722845;
	Mon, 31 Mar 2003 10:03:08 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GDF40K3L; Mon, 31 Mar 2003 10:03:09 -0500
Received: from nortelnetworks.com (acart1d8.ca.nortel.com [47.129.129.84]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id G7ZYWLC4; Mon, 31 Mar 2003 10:03:08 -0500
Message-ID: <3E8858AB.80401@nortelnetworks.com>
Date: Mon, 31 Mar 2003 10:03:07 -0500
X-Sybari-Space: 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
CC: sipping@ietf.org, Jon Peterson <Jon.Peterson@neustar.com>,
        "Mark Watson" <mwatson@nortelnetworks.com>
Subject: Re: [Sipping] Early media; a summary after the IETF
References: <0449D80A0E9B614A83FA9031B07E8D3B257940@stntexch2.va.neustar.com> <000e01c2f609$d5730a20$2300000a@BPenfield> <3E87EEC4.1F974505@lmf.ericsson.se>
In-Reply-To: <3E87EEC4.1F974505@lmf.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Your charts do not reflect an important difference between MGCP and Megaco/H.248. 
In MGCP, it is possible to tell the MG to automatically terminate application of 
ringing tone upon detection of incoming media.  In Megaco/H.248, the media event is 
detected on one termination, but the ringing tone is being applied to another.  This 
means that the MG has to report media detection to the MGC, and then the MGC has to 
request that ringing tone application be stopped.  It has occurred to me upon 
reflection that there might be a way around this, but for the moment that is the case.

Gonzalo Camarillo wrote:
> Folks,
> 
> here you have a summary of what happened in the IETF regarding early
> media.
> 
> We planned to have an ad-hoc meeting, but since we managed to get more
> meeting time than expected for this issue and some of the persons
> involved in the mailing list discussions were not available for an
> ad-hoc meeting (some of them were not even in San Francisco), we did not
> finally have the ad-hoc.
> 
> Regarding the discussions during the second SIPPING session, the main
> input was slide number 3 of
> 
> http://www.softarmor.com/sipping/meets/ietf56/slides/Gonzalo-sipping-early-media.ppt
> 
> That slide does not discuss the encoding issue. It focuses on the
> requirements or the gains that adding a SIP "there is media coming" (or
> "don't generate local ringback") indication would bring.
> 
> The conclusion of that slide is that a message with "generate local
> ringback until media arrives" should be provided by the protocol (e.g.,
> MGCP or H.248) between the MG and the MGC **REGARDLESS** of whether or
> not we create a "there is media coming" flag.
> 
> Therefore, assuming that the MG is in accept-media state as soon as the
> INVITE is sent, the only gain that a "there is media coming" would bring
> would be saving one message from the MGC to the MG every time a 180 with
> a flag is received. The gain is zero for 180 responses without the flag.
> 
> The question is: are people after this optimization (saving of one
> message in some circumstances) or there is somebody with something else
> in mind?
> 
> 
> In any event, the conclusion of the meeting was that I will be gathering
> use cases where a "there is media coming" flag would be useful. Please,
> send any use case you have in mind and I will compile them in a
> document. We hope that such a document help us figure out which
> requirement is missing.
> 
> We also may organize a conference call in some weeks to further discuss
> the issue, if needed.
> 
> Thanks,
> 
> Gonzalo
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 10:45:00 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11792
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 10:45:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2VG8JM14480
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 11:08:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VG8JO14476
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 11:08:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11778
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 10:44:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VG7UO14268;
	Mon, 31 Mar 2003 11:07:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VG6dO13602
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 11:06:39 -0500
Received: from rtp-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11664
	for <sipping@ietf.org>; Mon, 31 Mar 2003 10:42:48 -0500 (EST)
Received: from cia.cisco.com (IDENT:mirapoint@cia.cisco.com [161.44.85.200])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h2VFjBiH014063;
	Mon, 31 Mar 2003 10:45:12 -0500 (EST)
Received: from mhammer-w2k02.cisco.com (hrn2-dhcp-161-44-87-251.cisco.com [161.44.87.251])
	by cia.cisco.com (Mirapoint)
	with ESMTP id ABT20089;
	Mon, 31 Mar 2003 10:35:17 -0500 (EST)
Message-Id: <4.3.2.7.2.20030331102308.00b54d28@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 31 Mar 2003 10:45:09 -0500
To: "Bob Penfield" <bpenfield@acmepacket.com>
From: Michael Hammer <mhammer@cisco.com>
Subject: Re: [Sipping] New version of the early media draft
Cc: <sipping@ietf.org>
In-Reply-To: <000e01c2f609$d5730a20$2300000a@BPenfield>
References: <0449D80A0E9B614A83FA9031B07E8D3B257940@stntexch2.va.neustar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Bob and Jon,

The only problem with this approach is that you have blurred the line 
between signaling and bearer.  If 180 means alerting, then the UAC should 
provide alerting until the 200 OK or some other signaling removes the UAC 
from that state.  But, you have the bearer stream removing the UAC from the 
alerting state based on the receipt of RTP.

If you follow that approach, it should be clarified that not just any RTP, 
but RTP with some meaningful media would be of value.  But, this puts the 
burden on the UAC to determine whether highly ambiguous media means 
something or is just noise or silence.

A 180 meaning alerting with a suppression indication to supersede local 
alerting with inband alerting, or a 183 with an explicit indication of "do 
local alerting" would be a clear SIGNALING mechanism.

The only responses I recall getting to the following scenario is "GWs 
shouldn't do that" and "in MOST cases the destination EO will supply 
ringing inband anyway":

A GW responds with 180 and backward cut-through of RTP playing dead air.
The UAC plays the dead air because it got there before the 180 (and to 
avoid clipping).
This could go on for several seconds or however long it takes the UAS to 
pick up.

But, if this were to occur, I guess that is OK for the SIP UAC user.  This 
seems to be a minor case, so don't worry about it.

Mike


At 10:42 AM 3/29/2003 -0500, Bob Penfield wrote:

>----- Original Message -----
>From: "Peterson, Jon" <jon.peterson@neustar.biz>
><snip>
> >
> > Another problem is the idea that SIP has some special 'alerting' state
> > comparable to that of ISUP, and that if 180 is not received, this
>'alerting'
> > state will not be reached. I'm not sure what UAC behavior the advocates of
> > this position imagine will result from 180 that will not result from 183.
>If
> > anyone can substantiate this for me, preferably with some citation from
> > RFC3261, that would go a long way towards putting this issue to rest.
> >
>
>Even the RFC 3261 definition of 180 uses the term "alert".
>180 is not the same as 183 and UAs (e.g. SIP Phones) do treat them
>differently in order to provide the best user experience.
>
>RFC 3261 defines 180 as:
>
>     The UA receiving the INVITE is trying to alert the user.
>     This response MAY be used to initiate local ringback.
>
>where 183 is defined as:
>
>    The 183 (Session Progress) response is used to convey information
>    about the progress of the call that is not otherwise classified.
>
>I'm not saying that 180 means exactly the same thing as alerting in ISUP,
>but when the UAC receives a 180, it can reasonably believe that the call has
>progressed to the point that it can render "Ringing" to the user whether
>that is by displaying something on a screen (with or without inband media),
>flash a light, or playing local ringback in the absence of inband media. No
>such assumption can be made when a 183 response is received.
>
>Regardless of the type of UAS or interworking protocol, if a UAS can
>determine that the call has reached a state where it (or an endpoint at the
>other side of the non-SIP network) is "trying to alert the user", it should
>send 180. The response codes 180, 181, and 182 do have specific meaning in
>SIP and whenever a reasonable mapping from states in a interworking protocol
>can be made, they should be.
>
>BTW, I do support your position that no additional indication of the
>presence or absence of early media is required in SIP signaling. If UAC
>receives media, it should play it.
>
>cheers,
>(-:bob
>
>
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 11:22:43 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12897
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 11:22:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2VGk2917178
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 11:46:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VGk2O17175
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 11:46:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12869
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 11:22:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VGj5O17065;
	Mon, 31 Mar 2003 11:45:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VGgBO16955
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 11:42:11 -0500
Received: from sj-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12771
	for <sipping@ietf.org>; Mon, 31 Mar 2003 11:18:19 -0500 (EST)
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h2VGKfOV008028;
	Mon, 31 Mar 2003 08:20:42 -0800 (PST)
Received: from CJ650 (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with SMTP id ACT76485;
	Mon, 31 Mar 2003 08:20:40 -0800 (PST)
From: "Cullen Jennings" <fluffy@cisco.com>
To: "Al Varney" <varney@ieee.org>, <sipping@ietf.org>
Subject: RE: [Sipping] New version of the early media draft
Date: Mon, 31 Mar 2003 08:23:07 -0800
Message-ID: <MFEJKLHKCMNFOPKPHMBPGEOBCDAA.fluffy@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <4.3.2.7.2.20030327203149.00ce5c80@postoffice.worldnet.att.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Robert posted the minutes on the SIP list with the subject "Non-Invite adhoc
minutes and action plan" - lets keep the discussion on that thread.



> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
> Al Varney
> Sent: Thursday, March 27, 2003 7:05 PM
> To: Peterson, Jon; sipping@ietf.org
> Subject: RE: [Sipping] New version of the early media draft
>
>
> I haven't seen any "results" from the Early-Media Ad-Hoc (if it
> was held),
> so I'll toss out something I would have stated had I been there....
>
> At 04:50 PM 3/14/03 -0500, Peterson, Jon wrote:
> >They are proverbially out of luck in the CAS interworking case,
> no? Again,
> >it's not our fault that ISUP doesn't present its status accurately
> >out-of-band.
>
>     Absolutely true.  Even more so for MF or DP trunks off a SIP
> gateway.  You can't fix the past, but you do have to worry about
> embedded base.
>
> >Anyway, this is speaking to a pair of separable issues. Whether or not we
> >send pre-answer media with a 180 is separable from whether or not we need
> >some SIP-layer indication that we are doing so. Personally, I
> think we're in
> >a bad position to deal with cases where ISUP provides valuable in-band
> >information but doesn't tell us so in the encoding of an ACM, and I don't
> >think it is reasonable for us to always send pre-answer media on
> receipt of
> >ACM. But this is a separate issue.
> >
> >If we send 180, and subsequently send media, we could very well
> be deceiving
> >a deaf user (or a user whose UA simply doesn't render pre-answer
> media) into
> >thinking that 'alerting' tells the whole story. But if
> 'alerting' told the
> >whole story, there'd be no need to send any pre-answer media to accompany
> >it. This is the paradox I keep hearing - people want to see an indicator
> >that says "alerting" and play early media, but they simultaneously
> >acknowledge that the reason they want the early media is because it
> >qualifies the alerting state in some fashion.  How valuable is the
> >"alerting" state at the UAC, then?
>
>     OK -- so folks want "alerting" and early media (as in ISUP),
> particularly for cases when interworking with the old PSTN.  Then
> why add a
> SIP-early-media indicator to 180?  Instead, why not add an "alerting"
> indicator to 183 -- which maps rather well to ISUP ACM practice
> (ACM always
> implies in-band media in the backward direction, and it sometimes
> indicates
> 'user free'/alerting).  It also maps to/from ISDN in an obvious manner.
>
>     This leaves 180 untarnished as an explicit "alerting and no intended
> early media" indicator, and local ringback could always be
> generated.  Any
> pre-200 media could be assumed to have gotten ahead of SIP messaging, and
> it could be cut through to the caller either immediately or after a short
> delay.
>
>     Adding a new indicator to 183 for "user being alerted" is backward
> compatible, since RTP media would be there even if the new indicator was
> ignored.  And for cases where the indicator WAS recognized, a display or
> forking treatment similar to that for 180 could be used.  Some UA could
> even generate local ringback if it really, really wanted to do so.
>
>     The major advantage would be better compatibility with SIP-ISUP
> gateways for interworking, and the preservation of 180 for cases where
> SIP-aware signaling was used end-to-end.  Or where gateways that could
> distinguish true alerting cases (a gateway with directly-connected lines,
> for example, always knows the true alerting state of a terminal).  Over
> time, SIP-to-SIP calls would all tend to use 180, and the old
> PSTN behavior
> would be contained within 183 handling (where it already has to exist).
>
>     (While adding indicators to 183, would it also be useful to
> have a "SIP
> not used all-the-way" indicator that indicates interworking to non-SIP
> protocols?   Or would a UA always behave the same for gateways
> sending 183
> and called-UAs sending 183?)
>
>     View this as a comment thrown out into a late-night Ad-Hoc session.
>
> Al Varney
>
> >I would be more sympathetic to this view if the 'alerting' state had some
> >specific semantics at the UAC pointed out in RFC3261 that differentiated
> >'180 received' from '183 received' or other provisional states - but it
> >doesn't. There's nothing magical about receiving a 180 response.
> It's been
> >suggested that this is valuable for forking composition, but in my
> >estimation, if there's in-band media associated with a
> provisional branch of
> >a fork, you need to evaluate that media, not the status code (again,
> >otherwise, why send the media at all?). Some sort of 180 indicator that
> >suppresses local ringback doesn't help you either way with any of these
> >problems.
> >
> >Jon Peterson
> >NeuStar, Inc.
> >
> > > -----Original Message-----
> > > From: Michael Hammer [mailto:mhammer@cisco.com]
> > > Sent: Friday, March 14, 2003 12:51 PM
> > > To: Peterson, Jon
> > > Cc: 'Drage, Keith (Keith)'; 'Elwell, John'; 'Mark Watson';
> > > 'sipping@ietf.org'
> > > Subject: RE: [Sipping] New version of the early media draft
> > >
> > >
> > > Jon,
> > >
> > > Doesn't the possibility of deaf users preclude the use of 183
> > > from being
> > > used, as has been suggested, since they won't hear the
> > > locally injected
> > > ringback or the inband media?
> > >
> > > Mike
> > >
> > >
> > > At 05:52 AM 3/14/2003 -0500, Peterson, Jon wrote:
> > >
> > > >Below.
> > > >
> > > >Jon Peterson
> > > >NeuStar, Inc.
> > >
> >_______________________________________________
> >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >This list is for NEW development of the application of SIP
> >Use sip-implementors@cs.columbia.edu for questions on current sip
> >Use sip@ietf.org for new developments of core SIP
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 11:23:05 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12914
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 11:23:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2VGkOC17205
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 11:46:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VGkOO17202
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 11:46:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12876
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 11:22:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VGjAO17114;
	Mon, 31 Mar 2003 11:45:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VGiDO17012
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 11:44:13 -0500
Received: from sj-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12820
	for <sipping@ietf.org>; Mon, 31 Mar 2003 11:20:20 -0500 (EST)
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h2VGLsOV009873;
	Mon, 31 Mar 2003 08:21:56 -0800 (PST)
Received: from CJ650 (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with SMTP id ACT76483;
	Mon, 31 Mar 2003 08:20:39 -0800 (PST)
From: "Cullen Jennings" <fluffy@cisco.com>
To: "Christian Stredicke" <stredicke@snom.de>
Cc: <sipping@ietf.org>
Subject: RE: [Sipping] AW: AW: "Strict Routing", "Loose Routing", "No Routing"!
Date: Mon, 31 Mar 2003 08:23:06 -0800
Message-ID: <MFEJKLHKCMNFOPKPHMBPEEOBCDAA.fluffy@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <004a01c2f1e2$7bca17a0$6e7c6aca@raggy>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 8bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


Consider the case where there are three NATs calls A B and C. Both A and B
are behind C. This is typical where C is a ISP and A and B are home nats.
Two phones behind A and B both think their pubic address is the address on
the outside of C.

I'm not sure I understand what you are proposing but I suspect it might not
work in this case.

Cullen

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
> Christian Stredicke
> Sent: Monday, March 24, 2003 12:49 AM
> To: 'Jonathan Rosenberg'
> Cc: 'Rohan Mahy'; sipping@ietf.org; 'Jörgen Björkner'; 'Robert Sparks'
> Subject: [Sipping] AW: AW: "Strict Routing", "Loose Routing", "No
> Routing"!
>
>
> Jonathan,
>
> ok I elaborate a little bit as the history might not be known to
> everybody.
>
> (1) I am talking about the SIP messages here only; RTP is a separate
> issue.
>
> Again, I would like to stress I am not trying to reinvent routing (I
> think that would be too late and inappropriate anyway). I would just
> like to propose a backward-compatible way of expressing that non-SIP
> aware equipment is involved in the message forwarding process that needs
> to be taken care of. There is a need for this as we are moving on making
> the addresses found by STUN usable between the different vendors.
>
> (2) The problem is that depending on the context a request must be send
> to one of several possible addresses. In the case of NAT you are right,
> this is typically a problem when the two user agents are in the same NAT
> and the NAT gateway does not properly forward the messages coming from
> the private side sent to the public address of the other phone. This is
> my private concern as this is the most critical case we are facing in
> day-to-day life now.
>
> (3) I proposed using alternative addresses in the contact like
>
> "sip:62.12.34.56:6546;srcadr=192.168.0.123:5060"
>
> but that did not find too much acceptance with the persons that I talked
> to. The alternative proposal is including the route in the contact like
>
> "sip:192.168.0.123:5060?Route=sip:62.12.34.56:6546" or so,
>
> but this has the disadvantage that equipment which does not support the
> route header will not be able to send the packet properly (and apart
> from that I have some problems understanding how the route header should
> be merged with a maybe existing route).
>
> (4) What I propose now is using the routing mechanism we all know from
> SIP with a modification (backward compatible). For registrations, the
> path header has already been proposed and the record-route is part of
> the RFC.
>
> Lets make an example: The UA is in a private network and has the above
> private address and public address association. So it will send the
> following REGISTER message:
>
> REGISTER sip:bla.com SIP/2.0
> Path: <sip:62.12.34.56:6546;nr=1;lr>
> Contact: <sip:192.168.0.123:5060>
> ...
>
> The registrar will save both the path and the contact. So a INVITE that
> is forwarded to the user agent then will go along the path:
>
> INVITE sip:192.168.0.123:5060 SIP/2.0
> Route: <sip:62.12.34.56:6546;nr=1;lr>
>
> Because the user agent can deal with the "no routing", it will remove
> the top route entry (it contains the nr) and then process the packet.
> Here, it will probably start ringing.
>
> If the user agents sends a message and the topmost route entry contains
> the nr flag, it skips that route if the IP address is the same as the IP
> address that is has stored as its public IP address. This is surely a
> pragmatic first step to solving the problem of finding the right
> destination in a NAT. However, it can be extended to using STUN probes
> first and so on (for example in multi-tier NAT).
>
> (5) The nice thing about the nr idea is that existing equipment does not
> have to be changed. That means especially the existing proxies in the
> public internet can deal perfectly with "no routers". If equipment
> supports the nr flag, it will also see the packets with the nr flag and
> process them accordingly. Meaning that nr is fully backward compatible.
>
>
> I hope this clarifies the idea a little bit more.
>
>
> Christian
> --
> Dr.-Ing. Christian Stredicke
> sip:cs@snom.com
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
> > Gesendet: Montag, 24. März 2003 11:55
> > An: Christian Stredicke
> > Cc: 'Rohan Mahy'; sipping@ietf.org; 'Jörgen Björkner'; 'Robert Sparks'
> > Betreff: Re: AW: "Strict Routing", "Loose Routing", "No Routing"!
> >
> > Christian,
> >
> > I cannot really follow your email, and do not understand the problem
> > here. Perhaps you are referring to the case where A calls B, both
> behind
> > the same NAT, with a proxy on the public Internet. If the proxy doesnt
> > record route, a contact in the INVITE from A that contains an address
> > allocated via upnp will not be useful to B. There is an equivalent
> case
> > for RTP.
> >
> > There are only two solutions for this, I believe:
> >
> > 1. the proxy always record routes. But, how does it know that it needs
> > to do so?
> >
> > 2. apply the ICE principles to SIP signaling. This would involve
> > inclusion of *both* the public and private addresses in the Contact
> > header of the INVITE, and so the recipient uses the one that works.
> > Contact in INVITE only allows one URI (pity), so we would need to hack
> > around to get that to work. There are ways.
> >
> > I think most folk do approach 1. Its problem is that the proxy has to
> > know to record route.
> >
> > Approach 2 is in line with the ICE philosophy in that it would always
> > work, without requiring apriori topology knowledge as case 1 assumes.
> >
> > Anyway, moving to sipping since this is an important issue.
> >
> > -Jonathan R.
> >
> > Christian Stredicke wrote:
> > > Rohan,
> > >
> > > that is surely going into the right direction!
> > >
> > > I think it clearly points out the need to transport more than one
> > > address in the SDP.
> > >
> > > However, it does not seem to solve the problem for requests that
> don’t
> > > have SDP attachments (like MESSAGE). There is a difference in SIP
> > > routing and RTP routing. I think the draft addresses the RTP routing
> > > problem. For SIP routing, I think we still need a way for
> formulating
> > > that non SIP-aware equipment is involved in the routing process.
> > >
> > > Again, in my perception, SIP deals with *routes* (user agent client,
> > > number of routers with loose/strict/no routing and the user agent
> > > server). Every router has a defined behaviour (SIP aware called
> > > "proxies" and non SIP-aware called "NAT"). We know that the
> different
> > > types of proxies need different treatment and I begin to realize
> that
> > > NAT routers need a different treatment as well.
> > >
> > > The good news is that "no-routers" can be treated backward
> compatible.
> > > If the routing element behind the no-router fixes the SIP routing
> > > information everything should run fine. It is also the element
> behind
> > > the no-router that inserts this information.
> > >
> > > Anyway, having a STUN server on board of every SIP network element
> > > (UA/proxy) is probably a good idea for whatever comes. As you know,
> we
> > > did this already half a year on our proxy!
> > >
> > > Best,
> > >
> > >
> > > Christian
> > >
> > >
> > >>-----Ursprüngliche Nachricht-----
> > >>Von: Rohan Mahy [mailto:rohan@cisco.com]
> > >>Gesendet: Samstag, 22. März 2003 05:57
> > >>An: Christian Stredicke
> > >>Cc: sip-implementors@cs.columbia.edu; 'Jörgen Björkner'; 'Robert
> > >
> > > Sparks'
> > >
> > >>Betreff: Re: "Strict Routing", "Loose Routing", "No Routing"!
> > >>
> > >>Hi Christian,
> > >>
> > >>Have you seen Jonathan Rosenberg's "ICE" proposal which we discussed
> > >
> > > in
> > >
> > >>SIPPING?  How do you think these would relate.
> > >>
> > >>thanks,
> > >>-rohan
> > >>
> > >>
> > >>On Monday, March 17, 2003, at 09:17 PM, Christian Stredicke wrote:
> > >>
> > >>
> > >>>Hello again,
> > >>>
> > >>>while we have now loose routers and strict routers it seems that a
> > >>
> > > new
> > >
> > >>>type occurs on the horizon: The "no router"!
> > >>>
> > >>>This is for example the case when using NAT forwarding (e.g. with
> > >>
> > > STUN
> > >
> > >>>or UPnP). The router is not at all aware of SIP and does not
> > >>
> > > manipulate
> > >
> > >>>the packet at all. However, the router is too dumb to forward a
> > >>
> > > packet
> > >
> > >>>if it is coming from the wrong direction. This is the case with
> most
> > >>
> > > of
> > >
> > >>>the DSL routers today.
> > >>>
> > >>>May I propose to use a ";nr" flag in a URI to indicate that the
> > >>
> > > router
> > >
> > >>>does not do any SIP changing at all?
> > >>>
> > >>>User Agents that are able to deal with "no routers" would then
> > >>
> > > register
> > >
> > >>>with the following packet:
> > >>>
> > >>>REGISTER sip:bla.com SIP/2.0
> > >>>Path: <sip:62.12.245.32:54456;nr=1>
> > >>>Contact: <sip:abc@192.168.1.2:5060>
> > >>>...
> > >>>
> > >>>When it receives a message this could look like this:
> > >>>
> > >>>INVITE sip:62.12.245.32:54456;nr=1 SIP/2.0
> > >>>Route: <sip:abc@192.168.1.2:5060>
> > >>>...
> > >>>
> > >>>SIP/2.0 200 Wonderful
> > >>>Record-Route: <sip:62.12.245.32:54456;nr=1>
> > >>>Contact: <sip:abc@192.168.1.2:5060>
> > >>>...
> > >>>
> > >>>The nr parameter could easily indicate that the previous router did
> > >>
> > > not
> > >
> > >>>change the packet at all and that the next entity has to fix this
> > >>>before
> > >>>processing the message. Alternatively, the router sending the
> packet
> > >>>could fix the route before sending it.
> > >>>
> > >>>What do you think? Is this really necessary? Just omit the nr
> > >>
> > > parameter
> > >
> > >>>and conclude implicitly? How else should we deal with routers that
> > >>
> > > are
> > >
> > >>>not SIP-aware? I don’t like the route encoding in the header
> > >>>(sip:abc?route=def) as it raises many questions about how to merge
> > >>
> > > this
> > >
> > >>>with other existing routes.
> > >>>
> > >>>Unfortunately, omitting the private address is no solution, as
> > >>
> > > devices
> > >
> > >>>in the same subnet have to bypass the "no router". Many DSL routers
> > >>
> > > are
> > >
> > >>>not able to send packets from private address via the public
> address
> > >>
> > > to
> > >
> > >>>the other private address.
> > >>>
> > >>>Cheers,
> > >>>
> > >>>
> > >>>Christian
> > >>>--
> > >>>Dr. Christian Stredicke
> > >>>sip:cs@snom.com
> > >>>
> > >>
> > >
> > >
> >
> > --
> > Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
> > Chief Scientist                             Parsippany, NJ 07054-2711
> > dynamicsoft
> > jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> > http://www.jdrosen.net                      PHONE: (973) 952-5000
> > http://www.dynamicsoft.com
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 14:15:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19683
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 14:15:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2VJcms11097
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 14:38:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VJcmK11094
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 14:38:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19667
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 14:14:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VJc0K11065;
	Mon, 31 Mar 2003 14:38:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VJRoK09881
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 14:27:50 -0500
Received: from bdsl.greycouncil.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19379
	for <sipping@ietf.org>; Mon, 31 Mar 2003 14:03:57 -0500 (EST)
Received: from txdwillis (bdsl.66.12.12.254.gte.net [66.12.12.254])
	(authenticated bits=0)
	by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id h2VJ6COg011972
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Mon, 31 Mar 2003 13:06:15 -0600
From: "Dean Willis" <dean.willis@softarmor.com>
To: "'Cullen Jennings'" <fluffy@cisco.com>, <sipping@ietf.org>
Subject: RE: Apology for RE: [Sipping] A  WinXP patch
Date: Mon, 31 Mar 2003 13:05:46 -0600
Message-ID: <000d01c2f7b8$8b3143e0$fe0c0c42@txdwillis>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C2F786.4096D3E0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <MFEJKLHKCMNFOPKPHMBPCENMCDAA.fluffy@cisco.com>
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C2F786.4096D3E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

network asserted From:?
 
haha
 
--
Dean

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf Of
Cullen Jennings
Sent: Thursday, March 27, 2003 1:12 PM
To: sipping@ietf.org
Subject: Apology for RE: [Sipping] A WinXP patch


I did not sent any patches - certainly not to XP :-) Cullen (the guy with
the fluffy hair) 

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
fluffy
Sent: Wednesday, March 26, 2003 3:50 PM
To: sipping@ietf.org
Subject: [Sipping] A WinXP patch


This is a WinXP patch
I expect you would like it. 


------=_NextPart_000_000E_01C2F786.4096D3E0
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=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D633240519-31032003><FONT face=3DArial color=3D#0000ff =

size=3D2>network asserted From:?</FONT></SPAN></DIV>
<DIV><SPAN class=3D633240519-31032003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633240519-31032003><FONT face=3DArial color=3D#0000ff =

size=3D2>haha</FONT></SPAN></DIV>
<DIV><SPAN class=3D633240519-31032003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633240519-31032003><FONT face=3DArial color=3D#0000ff =

size=3D2>--<BR>Dean</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] <B>On Behalf Of =

  </B>Cullen Jennings<BR><B>Sent:</B> Thursday, March 27, 2003 1:12=20
  PM<BR><B>To:</B> sipping@ietf.org<BR><B>Subject:</B> Apology for RE: =
[Sipping]=20
  A WinXP patch<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D639260419-27032003>I=20
  did not sent any patches - certainly not to XP :-) Cullen (the guy =
with the=20
  fluffy hair) </SPAN></FONT></DIV>
  <BLOCKQUOTE=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> =
sipping-admin@ietf.org=20
    [mailto:sipping-admin@ietf.org]<B>On Behalf Of =
</B>fluffy<BR><B>Sent:</B>=20
    Wednesday, March 26, 2003 3:50 PM<BR><B>To:</B>=20
    sipping@ietf.org<BR><B>Subject:</B> [Sipping] A WinXP=20
    patch<BR><BR></FONT></DIV><FONT size=3D+0>This is a WinXP patch<BR>I =
expect=20
    you would like it.</FONT> </BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000E_01C2F786.4096D3E0--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 15:19:54 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22789
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 15:19:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2VKhIH15489
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 15:43:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VKhIK15485
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 15:43:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22781
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 15:19:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VKftK15406;
	Mon, 31 Mar 2003 15:41:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VKXrK14323
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 15:33:53 -0500
Received: from willow.neustar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22022
	for <sipping@ietf.org>; Mon, 31 Mar 2003 15:09:57 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h2VKCHC07058;
	Mon, 31 Mar 2003 20:12:17 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <ZH2JXKNS>; Mon, 31 Mar 2003 15:13:01 -0500
Message-ID: <0449D80A0E9B614A83FA9031B07E8D3B257943@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Michael Hammer'" <mhammer@cisco.com>,
        Bob Penfield
	 <bpenfield@acmepacket.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] New version of the early media draft
Date: Mon, 31 Mar 2003 15:13:00 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Well, I would argue that we haven't blurred the line in our approach - we're
just repeating what RFC3261 tells you to do. Based on the "you must be
prepared to receive media" after INVITE text and the "MAY generate local
ringback" after 180 text, it would seem that the alerting state entails that
you MAY generate local ringback unless you receive media. The blurring, if
any, occurred there. I don't really consider it blurring, though, because
sending an INVITE at all essentially signals at the application layer "I can
be sent media now". No response mechanic seems to be required to supplement
that application-layer indication. 

And actually, I'm not sure that the distinction between 'meaningful' RTP and
silence is actually a requirement. Earlier in this thread, in fact, somebody
expressed that when silence is sent over RTP, silence is what the UAC should
render (i.e. that playing local ringback over silence could in some cases be
the wrong behavior). I would second Gonzalo's call for use cases related to
these scenarios. Since (as many in this thread have argued) it is impossible
for a gateway UAS to know whether or not there is valuable information
in-band, it isn't clear when it would be appropriate for the UAS gateway to
say that the RTP it is sending is 'meaningful', anyway.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Michael Hammer [mailto:mhammer@cisco.com]
> Sent: Monday, March 31, 2003 7:45 AM
> To: Bob Penfield
> Cc: sipping@ietf.org
> Subject: Re: [Sipping] New version of the early media draft
> 
> 
> Bob and Jon,
> 
> The only problem with this approach is that you have blurred the line 
> between signaling and bearer.  If 180 means alerting, then 
> the UAC should 
> provide alerting until the 200 OK or some other signaling 
> removes the UAC 
> from that state.  But, you have the bearer stream removing 
> the UAC from the 
> alerting state based on the receipt of RTP.
> 
> If you follow that approach, it should be clarified that not 
> just any RTP, 
> but RTP with some meaningful media would be of value.  But, 
> this puts the 
> burden on the UAC to determine whether highly ambiguous media means 
> something or is just noise or silence.
> 
> A 180 meaning alerting with a suppression indication to 
> supersede local 
> alerting with inband alerting, or a 183 with an explicit 
> indication of "do 
> local alerting" would be a clear SIGNALING mechanism.
> 
> The only responses I recall getting to the following scenario is "GWs 
> shouldn't do that" and "in MOST cases the destination EO will supply 
> ringing inband anyway":
> 
> A GW responds with 180 and backward cut-through of RTP 
> playing dead air.
> The UAC plays the dead air because it got there before the 
> 180 (and to 
> avoid clipping).
> This could go on for several seconds or however long it takes 
> the UAS to 
> pick up.
> 
> But, if this were to occur, I guess that is OK for the SIP 
> UAC user.  This 
> seems to be a minor case, so don't worry about it.
> 
> Mike
> 
> 
> At 10:42 AM 3/29/2003 -0500, Bob Penfield wrote:
> 
> >----- Original Message -----
> >From: "Peterson, Jon" <jon.peterson@neustar.biz>
> ><snip>
> > >
> > > Another problem is the idea that SIP has some special 
> 'alerting' state
> > > comparable to that of ISUP, and that if 180 is not received, this
> >'alerting'
> > > state will not be reached. I'm not sure what UAC behavior 
> the advocates of
> > > this position imagine will result from 180 that will not 
> result from 183.
> >If
> > > anyone can substantiate this for me, preferably with some 
> citation from
> > > RFC3261, that would go a long way towards putting this 
> issue to rest.
> > >
> >
> >Even the RFC 3261 definition of 180 uses the term "alert".
> >180 is not the same as 183 and UAs (e.g. SIP Phones) do treat them
> >differently in order to provide the best user experience.
> >
> >RFC 3261 defines 180 as:
> >
> >     The UA receiving the INVITE is trying to alert the user.
> >     This response MAY be used to initiate local ringback.
> >
> >where 183 is defined as:
> >
> >    The 183 (Session Progress) response is used to convey information
> >    about the progress of the call that is not otherwise classified.
> >
> >I'm not saying that 180 means exactly the same thing as 
> alerting in ISUP,
> >but when the UAC receives a 180, it can reasonably believe 
> that the call has
> >progressed to the point that it can render "Ringing" to the 
> user whether
> >that is by displaying something on a screen (with or without 
> inband media),
> >flash a light, or playing local ringback in the absence of 
> inband media. No
> >such assumption can be made when a 183 response is received.
> >
> >Regardless of the type of UAS or interworking protocol, if a UAS can
> >determine that the call has reached a state where it (or an 
> endpoint at the
> >other side of the non-SIP network) is "trying to alert the 
> user", it should
> >send 180. The response codes 180, 181, and 182 do have 
> specific meaning in
> >SIP and whenever a reasonable mapping from states in a 
> interworking protocol
> >can be made, they should be.
> >
> >BTW, I do support your position that no additional indication of the
> >presence or absence of early media is required in SIP 
> signaling. If UAC
> >receives media, it should play it.
> >
> >cheers,
> >(-:bob
> >
> >
> >
> >_______________________________________________
> >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >This list is for NEW development of the application of SIP
> >Use sip-implementors@cs.columbia.edu for questions on current sip
> >Use sip@ietf.org for new developments of core SIP
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From mailnull@www1.ietf.org  Mon Mar 31 20:56:08 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06745
	for <sipping-archive@odin.ietf.org>; Mon, 31 Mar 2003 20:56:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h312Jco05408
	for sipping-archive@odin.ietf.org; Mon, 31 Mar 2003 21:19:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h312JcK05405
	for <sipping-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 21:19:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06739
	for <sipping-web-archive@ietf.org>; Mon, 31 Mar 2003 20:55:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h312HsK05316;
	Mon, 31 Mar 2003 21:17:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h312GUK05274
	for <sipping@optimus.ietf.org>; Mon, 31 Mar 2003 21:16:30 -0500
Received: from zrc2s0jx.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06695
	for <sipping@ietf.org>; Mon, 31 Mar 2003 20:52:26 -0500 (EST)
Received: from zsc3c028.us.nortel.com (zsc3c028.us.nortel.com [47.81.138.28])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h311smL28490;
	Mon, 31 Mar 2003 19:54:48 -0600 (CST)
Received: by zsc3c028.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <HK7DDT2P>; Mon, 31 Mar 2003 17:54:48 -0800
Message-ID: <2F1FC1DEA077D5119FAD00508BCFD6D20787D68D@zsc3c030.us.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Bob Penfield'" <bpenfield@acmepacket.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>
Cc: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        "'Jon PETERSON (Jon.Peterson@neustar.com)'" <Jon.Peterson@neustar.com>,
        "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Subject: RE: [Sipping] New version of the early media draft
Date: Mon, 31 Mar 2003 17:54:48 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2F7F1.AD1142A6"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2F7F1.AD1142A6
Content-Type: text/plain;
	charset="ISO-8859-1"



> -----Original Message-----
> From: Bob Penfield [mailto:bpenfield@acmepacket.com] 
> Sent: Saturday, March 29, 2003 07:43
> To: sipping@ietf.org
> Subject: Re: [Sipping] New version of the early media draft
>
> BTW, I do support your position that no additional indication 
> of the presence or absence of early media is required in SIP 
> signaling. If UAC receives media, it should play it.


This is actually the biggest problem I personnally have with the assumptions
on early
media. 

I do not think that this rule of "play media when you receive it" is
implementable
generally, but only in a few very selected cases.

There are a number of scenarios that I think are problematic:

1 - 180 with SDP

If a 180 is sent with an SDP (for the purpose of telling the far end what
codec is picked), the called UA the shouldn't be sending silence in
RTP because, according to the current rules, the calling UA would stop the
locally generated ringing to play the silence packet. (Doing some heavy duty
DSP parsing to detect if the media is silence or not seems hardly efficient,
nor reliable).

A side effect of this is that if there is a NAT/Firewall involved, it is
quite
possible that the binding will expire and the address in the SDP will be
invalid
or the media will be blocked upon answer. 

If an indication was present to indicate if the in-band media was meant to
be
replacing the locally generated tone, we wouldn't have this problem (i.e.,
one
could send packets in-band to keep the binding alive).
 

2 - Sequential calling

In a sequential calling scenario such as call call forwarding no answer
(section 2.8
of the SIP services examples Internet Draft). Suppose the following:

   Alice            Proxy         User B1             User B2
          |                |              |                   |
          |    INVITE F1   |              |                   |
          |--------------->|   INVITE F2  |                   |
          |(100 Trying) F3 |------------->|                   |
          |<---------------|183 ProgressF4|                   |  SDP is
included with 183
          | 183 Progress F5|<-------------|                   |
          |<---------------|              |                   |
          |   Both way RTP Established    |                   |
In-band   |<=============================>|                   |
ringing   |                 Request Timeout                   |
          |                |              |                   |
          |                |   CANCEL F6  |                   |
          |                |------------->|                   |
          |                |   200 OK F7  |                   |
          |                |<-------------|                   |
          |                |     487 F8   |                   |
          |                |<-------------|                   |
          |                |     ACK F9   |                   |
          |                |------------->|                   |
          |                |              |    INVITE F10     |
          |                |--------------------------------->|
          |                |              | 180 Ringing F11   |
          | 180 Ringing F12|<---------------------------------|
          |<---------------|              |                   |

The problem with this scenario is that presumably, upon receipt of 180,
the UA needs to figure out somehow that it should be playing the locally 
generated alerting. This would imply that upon receipt of the 180, the
calling
UA would start a timer and wait until it expires to play the locally
generate
tone. Since ringing is composed of tone-silence-tone, the timer will have to
be
relatively long. While the UA can detect that the 180 is a different dialog
than
the 183, it can not know for sure that the first dialog had been cancelled
because it could be forking: it has to rely on the media.

While this is technically feasible, it imposes a big unecessary burden on
the client, especially if it is a thin client. On a "decomposed"
architecture
(like a stimulus MGCP phone), it makes for pretty nasty signalling, if
possible 
at all.

PS: I'm not saying that the in-band media is necessarily useful in this
scenario. I'm
just pointing out the difficulties of the "play media when received" mantra.

3 - Forking

As expected, this is the worst.

   Alice            Proxy         User B1             User B2
          |                |              |                   |
          |    INVITE F1   |              |                   |
          |--------------->|   INVITE F2  |                   |
          |(100 Trying) F3 |------------->|                   |
          |<---------------|183 ProgressF4|                   |  SDP is
included with 183
          | 183 Progress F5|<-------------|                   |
          |<---------------|              |                   |
          |   Both way RTP Established    |                   |
In-band   |<=============================>|                   |
ringing   |                |              |                   |
          |                |              |    INVITE F10     |
          |                |--------------------------------->|
          |                |              | 180 Ringing F11   |
Locally   | 180 Ringing F12|<---------------------------------|
generated |<---------------|              |      200 OK F13   |
ringing   |                |<---------------------------------|

There are of course multiple permutations, such as 2 183s, 2 180s, 1 183
followed
by a 180, or 1 180 followed by a 183. And then there might be more than 2
UAs being 
forked-to, so the problem can be really bad.

There is no way to associate a specific RTP stream with a specific dialog.
The current
draft hints that one UA could randomly play one stream and mute the others
(which will be
very troublesome if the other UA doesn't support UPDATE). This is not
satisfactory and
would result in garbage being played to the user. For this reason, I believe
that the only 
reasonable approach in this scenario is to let the 180 override the 183s (if
there is
a 180) and ignore all media. This will of course result that there might be
some level of
clipping on answer (I have yet to see a network where this is a problem). If
there is no
180, one could play one of the random stream (although I don't think it is
particulary 
useful), or play some default "progress" tone that would indicate to the
user that the
call is forked.

One of the reason I think the 180 indication is more useful than the
183-with-in-band-
media is that if the in-band from the 183 is saying "This number has been
disconnected,
please hangup" and then a 200 OK comes back (for the 180) wich connects the
call, the user 
will be very disoriented (realistically, he will probably have hung-up
anyways). The other
way around (playing the local ringback) will at least keep the user on-line
in case somebody
does answer. The point is that since we can't associate a particular media
stream with
the SIP signalling, we can't just "play the media" when there is multiple
dialogs.

Many people seem to think that "this is forking, it is trouble, don't use
it, bla bla bla".
Unfortunately, it is extremely useful. Also, it happens all the time today
when parallel 
calling is done (different names exists for it, including "multiple
appearances", or 
"parallel hunt groups"). If SIP can not properly ring multiple agents in a
pool in parallel, 
it won't be terribly useful.

The only alternative is to wait for the 200 OK to connect media. Despite the
claims of
this introducing clipping on answer, I haven't seen this to be a problem on
existing VoIP 
systems (i.e., the time it takes the human to answer is longer than the
interval during 
which there could be clipping).  

One added difficulty is that from the calling UA's perspective, we can't
distinguish easily 
between case 2 and 3.

---------

My conclusion is that when there are multiple dialogs, we can not honor
media at the 
calling UA and have to rely on the SIP provisional responses exclusively.
This goes against
the "play media as soon as you receive it" principle.

Also, since parallel calling (i.e., forking) is extremely common in call
centers and
within enterprises, it greatly limits the applicability of early media, or
indeed ringing
2 phones in a private residence. My personal opinion is that it is really
limited to TDM 
gateway interworking, and only when there is no forking involved or multiple
dialog 
involved.

Again, I don't believe that the "in-band alerting" indication necessarily
solves this (although
it does help in a few cases). I'm just pointing out that the play in-band
RTP even if 180 is 
received is not generally a good idea. The reason I am sending this email in
the context
of this discussion on the in-band ringing indication is that this idea that
playing in-band
media automatically helps keeps on re-surfacing.


François Audet

------_=_NextPart_001_01C2F7F1.AD1142A6
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>RE: [Sipping] New version of the early media draft</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Bob Penfield [<A =
HREF=3D"mailto:bpenfield@acmepacket.com">mailto:bpenfield@acmepacket.com=
</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Saturday, March 29, 2003 07:43</FONT>
<BR><FONT SIZE=3D2>&gt; To: sipping@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] New version of the early =
media draft</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; BTW, I do support your position that no =
additional indication </FONT>
<BR><FONT SIZE=3D2>&gt; of the presence or absence of early media is =
required in SIP </FONT>
<BR><FONT SIZE=3D2>&gt; signaling. If UAC receives media, it should =
play it.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>This is actually the biggest problem I personnally =
have with the assumptions on early</FONT>
<BR><FONT SIZE=3D2>media. </FONT>
</P>

<P><FONT SIZE=3D2>I do not think that this rule of &quot;play media =
when you receive it&quot; is implementable</FONT>
<BR><FONT SIZE=3D2>generally, but only in a few very selected =
cases.</FONT>
</P>

<P><FONT SIZE=3D2>There are a number of scenarios that I think are =
problematic:</FONT>
</P>

<P><FONT SIZE=3D2>1 - 180 with SDP</FONT>
</P>

<P><FONT SIZE=3D2>If a 180 is sent with an SDP (for the purpose of =
telling the far end what</FONT>
<BR><FONT SIZE=3D2>codec is picked), the called UA the shouldn't be =
sending silence in</FONT>
<BR><FONT SIZE=3D2>RTP because, according to the current rules, the =
calling UA would stop the</FONT>
<BR><FONT SIZE=3D2>locally generated ringing to play the silence =
packet. (Doing some heavy duty</FONT>
<BR><FONT SIZE=3D2>DSP parsing to detect if the media is silence or not =
seems hardly efficient,</FONT>
<BR><FONT SIZE=3D2>nor reliable).</FONT>
</P>

<P><FONT SIZE=3D2>A side effect of this is that if there is a =
NAT/Firewall involved, it is quite</FONT>
<BR><FONT SIZE=3D2>possible that the binding will expire and the =
address in the SDP will be invalid</FONT>
<BR><FONT SIZE=3D2>or the media will be blocked upon answer. </FONT>
</P>

<P><FONT SIZE=3D2>If an indication was present to indicate if the =
in-band media was meant to be</FONT>
<BR><FONT SIZE=3D2>replacing the locally generated tone, we wouldn't =
have this problem (i.e., one</FONT>
<BR><FONT SIZE=3D2>could send packets in-band to keep the binding =
alive).</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>2 - Sequential calling</FONT>
</P>

<P><FONT SIZE=3D2>In a sequential calling scenario such as call call =
forwarding no answer (section 2.8</FONT>
<BR><FONT SIZE=3D2>of the SIP services examples Internet Draft). =
Suppose the following:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; =
Alice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Proxy&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; User =
B1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; User B2</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp; INVITE F1&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------&gt;|&nbsp;&nbsp; INVITE F2&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |(100 =
Trying) F3 =
|-------------&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&lt;---------------|183 =
ProgressF4|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; SDP is included =
with 183</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 183 =
Progress =
F5|&lt;-------------|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&lt;---------------|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp; Both way RTP Established&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>In-band&nbsp;&nbsp; =
|&lt;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>ringing&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; Request =
Timeout&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; CANCEL F6&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|-------------&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; 200 OK F7&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|&lt;-------------|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; 487 F8&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|&lt;-------------|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; ACK F9&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|-------------&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; |&nbsp;&nbsp;&nbsp; INVITE F10&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |---------------------------------&gt;|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; | 180 Ringing F11&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 180 =
Ringing F12|&lt;---------------------------------|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&lt;---------------|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
</P>

<P><FONT SIZE=3D2>The problem with this scenario is that presumably, =
upon receipt of 180,</FONT>
<BR><FONT SIZE=3D2>the UA needs to figure out somehow that it should be =
playing the locally </FONT>
<BR><FONT SIZE=3D2>generated alerting. This would imply that upon =
receipt of the 180, the calling</FONT>
<BR><FONT SIZE=3D2>UA would start a timer and wait until it expires to =
play the locally generate</FONT>
<BR><FONT SIZE=3D2>tone. Since ringing is composed of =
tone-silence-tone, the timer will have to be</FONT>
<BR><FONT SIZE=3D2>relatively long. While the UA can detect that the =
180 is a different dialog than</FONT>
<BR><FONT SIZE=3D2>the 183, it can not know for sure that the first =
dialog had been cancelled</FONT>
<BR><FONT SIZE=3D2>because it could be forking: it has to rely on the =
media.</FONT>
</P>

<P><FONT SIZE=3D2>While this is technically feasible, it imposes a big =
unecessary burden on</FONT>
<BR><FONT SIZE=3D2>the client, especially if it is a thin client. On a =
&quot;decomposed&quot; architecture</FONT>
<BR><FONT SIZE=3D2>(like a stimulus MGCP phone), it makes for pretty =
nasty signalling, if possible </FONT>
<BR><FONT SIZE=3D2>at all.</FONT>
</P>

<P><FONT SIZE=3D2>PS: I'm not saying that the in-band media is =
necessarily useful in this scenario. I'm</FONT>
<BR><FONT SIZE=3D2>just pointing out the difficulties of the &quot;play =
media when received&quot; mantra.</FONT>
</P>

<P><FONT SIZE=3D2>3 - Forking</FONT>
</P>

<P><FONT SIZE=3D2>As expected, this is the worst.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; =
Alice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Proxy&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; User =
B1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; User B2</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp; INVITE F1&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|---------------&gt;|&nbsp;&nbsp; INVITE F2&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |(100 =
Trying) F3 =
|-------------&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&lt;---------------|183 =
ProgressF4|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; SDP is included =
with 183</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 183 =
Progress =
F5|&lt;-------------|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&lt;---------------|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp; Both way RTP Established&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>In-band&nbsp;&nbsp; =
|&lt;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>ringing&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; |&nbsp;&nbsp;&nbsp; INVITE F10&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |---------------------------------&gt;|</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; | 180 Ringing F11&nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>Locally&nbsp;&nbsp; | 180 Ringing =
F12|&lt;---------------------------------|</FONT>
<BR><FONT SIZE=3D2>generated =
|&lt;---------------|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 200 OK =
F13&nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>ringing&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |&lt;---------------------------------|</FONT>
</P>

<P><FONT SIZE=3D2>There are of course multiple permutations, such as 2 =
183s, 2 180s, 1 183 followed</FONT>
<BR><FONT SIZE=3D2>by a 180, or 1 180 followed by a 183. And then there =
might be more than 2 UAs being </FONT>
<BR><FONT SIZE=3D2>forked-to, so the problem can be really bad.</FONT>
</P>

<P><FONT SIZE=3D2>There is no way to associate a specific RTP stream =
with a specific dialog. The current</FONT>
<BR><FONT SIZE=3D2>draft hints that one UA could randomly play one =
stream and mute the others (which will be</FONT>
<BR><FONT SIZE=3D2>very troublesome if the other UA doesn't support =
UPDATE). This is not satisfactory and</FONT>
<BR><FONT SIZE=3D2>would result in garbage being played to the user. =
For this reason, I believe that the only </FONT>
<BR><FONT SIZE=3D2>reasonable approach in this scenario is to let the =
180 override the 183s (if there is</FONT>
<BR><FONT SIZE=3D2>a 180) and ignore all media. This will of course =
result that there might be some level of</FONT>
<BR><FONT SIZE=3D2>clipping on answer (I have yet to see a network =
where this is a problem). If there is no</FONT>
<BR><FONT SIZE=3D2>180, one could play one of the random stream =
(although I don't think it is particulary </FONT>
<BR><FONT SIZE=3D2>useful), or play some default &quot;progress&quot; =
tone that would indicate to the user that the</FONT>
<BR><FONT SIZE=3D2>call is forked.</FONT>
</P>

<P><FONT SIZE=3D2>One of the reason I think the 180 indication is more =
useful than the 183-with-in-band-</FONT>
<BR><FONT SIZE=3D2>media is that if the in-band from the 183 is saying =
&quot;This number has been disconnected,</FONT>
<BR><FONT SIZE=3D2>please hangup&quot; and then a 200 OK comes back =
(for the 180) wich connects the call, the user </FONT>
<BR><FONT SIZE=3D2>will be very disoriented (realistically, he will =
probably have hung-up anyways). The other</FONT>
<BR><FONT SIZE=3D2>way around (playing the local ringback) will at =
least keep the user on-line in case somebody</FONT>
<BR><FONT SIZE=3D2>does answer. The point is that since we can't =
associate a particular media stream with</FONT>
<BR><FONT SIZE=3D2>the SIP signalling, we can't just &quot;play the =
media&quot; when there is multiple dialogs.</FONT>
</P>

<P><FONT SIZE=3D2>Many people seem to think that &quot;this is forking, =
it is trouble, don't use it, bla bla bla&quot;.</FONT>
<BR><FONT SIZE=3D2>Unfortunately, it is extremely useful. Also, it =
happens all the time today when parallel </FONT>
<BR><FONT SIZE=3D2>calling is done (different names exists for it, =
including &quot;multiple appearances&quot;, or </FONT>
<BR><FONT SIZE=3D2>&quot;parallel hunt groups&quot;). If SIP can not =
properly ring multiple agents in a pool in parallel, </FONT>
<BR><FONT SIZE=3D2>it won't be terribly useful.</FONT>
</P>

<P><FONT SIZE=3D2>The only alternative is to wait for the 200 OK to =
connect media. Despite the claims of</FONT>
<BR><FONT SIZE=3D2>this introducing clipping on answer, I haven't seen =
this to be a problem on existing VoIP </FONT>
<BR><FONT SIZE=3D2>systems (i.e., the time it takes the human to answer =
is longer than the interval during </FONT>
<BR><FONT SIZE=3D2>which there could be clipping).&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2>One added difficulty is that from the calling UA's =
perspective, we can't distinguish easily </FONT>
<BR><FONT SIZE=3D2>between case 2 and 3.</FONT>
</P>

<P><FONT SIZE=3D2>---------</FONT>
</P>

<P><FONT SIZE=3D2>My conclusion is that when there are multiple =
dialogs, we can not honor media at the </FONT>
<BR><FONT SIZE=3D2>calling UA and have to rely on the SIP provisional =
responses exclusively. This goes against</FONT>
<BR><FONT SIZE=3D2>the &quot;play media as soon as you receive it&quot; =
principle.</FONT>
</P>

<P><FONT SIZE=3D2>Also, since parallel calling (i.e., forking) is =
extremely common in call centers and</FONT>
<BR><FONT SIZE=3D2>within enterprises, it greatly limits the =
applicability of early media, or indeed ringing</FONT>
<BR><FONT SIZE=3D2>2 phones in a private residence. My personal opinion =
is that it is really limited to TDM </FONT>
<BR><FONT SIZE=3D2>gateway interworking, and only when there is no =
forking involved or multiple dialog </FONT>
<BR><FONT SIZE=3D2>involved.</FONT>
</P>

<P><FONT SIZE=3D2>Again, I don't believe that the &quot;in-band =
alerting&quot; indication necessarily solves this (although</FONT>
<BR><FONT SIZE=3D2>it does help in a few cases). I'm just pointing out =
that the play in-band RTP even if 180 is </FONT>
<BR><FONT SIZE=3D2>received is not generally a good idea. The reason I =
am sending this email in the context</FONT>
<BR><FONT SIZE=3D2>of this discussion on the in-band ringing indication =
is that this idea that playing in-band</FONT>
<BR><FONT SIZE=3D2>media automatically helps keeps on =
re-surfacing.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Fran=E7ois Audet</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2F7F1.AD1142A6--
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



