From sipping-bounces@ietf.org Tue Jan 02 13:53:46 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H1okf-0004wN-7h; Tue, 02 Jan 2007 13:52:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H1okd-0004wH-RJ
	for sipping@ietf.org; Tue, 02 Jan 2007 13:52:43 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H1okc-0001U5-GB
	for sipping@ietf.org; Tue, 02 Jan 2007 13:52:43 -0500
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-4.cisco.com with ESMTP; 02 Jan 2007 10:52:42 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l02IqfE7028305; 
	Tue, 2 Jan 2007 10:52:41 -0800
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l02Iq9Up009582;
	Tue, 2 Jan 2007 10:52:41 -0800 (PST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 Jan 2007 13:52:37 -0500
Received: from [10.86.242.124] ([10.86.242.124]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 Jan 2007 13:52:37 -0500
Message-ID: <459AA9F4.5040302@cisco.com>
Date: Tue, 02 Jan 2007 13:52:36 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: CHADLI Youssef RD-CORE-ISS <youssef.chadli@orange-ftgroup.com>
Subject: Re: [SIPPING] draft-sawada-sipping-sip-offeranswer-01.txt: SDP answer
	in unreliable SIP response
References: <2AF8FF7D89242541B12E7A47F6ECB4BE04D1E536@ftrdmel3.rd.francetelecom.fr>
In-Reply-To: <2AF8FF7D89242541B12E7A47F6ECB4BE04D1E536@ftrdmel3.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Jan 2007 18:52:37.0236 (UTC)
	FILETIME=[2BC50B40:01C72E9F]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2045; t=1167763961;
	x=1168627961; c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[SIPPING]=20draft-sawada-sipping-sip-offeranswer-01.t
	xt=3A=20SDP=20answer=0A=20=20in=20unreliable=20SIP=20response
	|Sender:=20; bh=LxiXPNuzxUtaHOm8fJAY5pFzuLd2vJfjjWLEezc+2Es=;
	b=pd8kc5dpH3nDL0V3p4P/lPWCN99yIO9sLeavXLAKJ3jfVfBT4wGVBvaiUYfZdZhIWCRhXbTZ
	IvEC601T/llN/fmX+UgfaST3hbUi3IDymEB5j+PiRsbFiadDNJuSNud6;
Authentication-Results: sj-dkim-6; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim6002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: Takuya Sawada <tu-sawada@kddi.com>, sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



CHADLI Youssef RD-CORE-ISS wrote:
> Hi
> 
> There is a contradiction with RFC3261 regarding the handling of  SDP
> answer in unreliable provisional SIP responses:
> 
> Draft draft-sawada-sipping-sip-offeranswer-01.tx states: Session
> description in an unreliable response that precedes a reliable response
> can be considered a "preview" of the session description that will be
> coming, and hence may be treated like an offer or an answer until the
> actual one arrives. (section 2.1)
> 
> However, RFC 3261 states:  If the initial offer is in an INVITE, the
> answer MUST be in a reliable non-failure message from UAS back to UAC
> which is correlated to that INVITE. For this specification, that is only
> the final 2xx response to that INVITE. That same exact answer MAY also
> be placed in any provisional responses sent prior to the answer. The UAC
> MUST treat the first session description it receives as the answer, and
> MUST ignore any session descriptions in subsequent responses to the
> initial INVITE.(section 13.2.1)
> 
> Is there any justification for that change ?

It isn't intended as change - just a clarification. The point is that 
the actual offer or answer has not yet been sent, which is important for 
knowing when a subsequent offer or answer may be sent. But meanwhile, 
the content of the sdp is a preview of what the offer or answer will be, 
and that may be used, for instance to begin transmitting or receiving 
early media.

This is intended to pull together implications from a variety of drafts 
and RFCs, together with implications of those that have proven to be 
non-obvious.

	Paul

> Moreover, the treatment stated in RFC 3261 seems to be more logical. In
> fact, given that the SDP answer in unreliable provisional responses and
> the one in the 200 OK response must be the same, there is no reason to
> wait for the SDP in the 200 OK in case an SDP is received in an
> unreliable provisional SIP response. 
> 
> Thanks & Regards,
> Youssef
> 
>  
> 

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



From sipping-bounces@ietf.org Tue Jan 02 13:56:24 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H1oo0-0007lw-Vd; Tue, 02 Jan 2007 13:56:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H1onz-0007ln-EM
	for sipping@ietf.org; Tue, 02 Jan 2007 13:56:11 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H1ony-0001qJ-4y
	for sipping@ietf.org; Tue, 02 Jan 2007 13:56:11 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 02 Jan 2007 10:56:09 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l02Iu9dF027652; 
	Tue, 2 Jan 2007 10:56:09 -0800
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l02ItoUN010924;
	Tue, 2 Jan 2007 10:56:09 -0800 (PST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 Jan 2007 13:55:59 -0500
Received: from [10.86.242.124] ([10.86.242.124]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 Jan 2007 13:55:58 -0500
Message-ID: <459AAABE.8020004@cisco.com>
Date: Tue, 02 Jan 2007 13:55:58 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: CHADLI Youssef RD-CORE-ISS <youssef.chadli@orange-ftgroup.com>
Subject: Re: [Sipping] SDP offer in unreliable SIP response/
	draft-sawada-sipping-sip-offeranswer-01.txt
References: <2AF8FF7D89242541B12E7A47F6ECB4BE04D1E53C@ftrdmel3.rd.francetelecom.fr>
In-Reply-To: <2AF8FF7D89242541B12E7A47F6ECB4BE04D1E53C@ftrdmel3.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Jan 2007 18:55:59.0044 (UTC)
	FILETIME=[A40E8040:01C72E9F]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=632; t=1167764169;
	x=1168628169; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20SDP=20offer=20in=20unreliable=20SIP=20res
	ponse/=20draft-sawada-sipping-sip-offeranswer-01.txt
	|Sender:=20; bh=lQ10F9xcFcDp+on8S+5gq4MAFA8MlYP7yhBTtU/OZvA=;
	b=fZ2TGn4wBVj9+uWfUM5QurdpscJgWnDm7Y5zdIHRgteewxHQ17ws3UOXWkRnbgYQ198KNpOG
	dXSdOTACNKL7a3KqBYvXpVA/L6hoDm/KE8e17Ty5dLJr33P/CmVN/lBq;
Authentication-Results: sj-dkim-7; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Takuya Sawada <tu-sawada@kddi.com>, sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



CHADLI Youssef RD-CORE-ISS wrote:
> 
> Hi,
> 
> When the INVITE request is received without SDP offer, in section 2.1.2 
> of the draft,  it is said that the UAS may include its SDP offer in the 
> sent provisional unreliable SIP response. This possibility is not 
> mentioned in RFC 3261. Is there any reason to diverge from RFC 3261 
> regarding this point ?

It may not be stated explicitly, but it is implicitly permitted because 
there is nothing that prevents it and and SDP body is permitted in 1xx 
responses, without restriction to reliable provisional responses (that 
aren't included in 3261.)

	Paul

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



From sipping-bounces@ietf.org Tue Jan 02 14:01:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H1otC-0002O8-Kg; Tue, 02 Jan 2007 14:01:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H1otA-0002O1-Tw
	for sipping@ietf.org; Tue, 02 Jan 2007 14:01:32 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H1ot9-00030d-Jl
	for sipping@ietf.org; Tue, 02 Jan 2007 14:01:32 -0500
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-5.cisco.com with ESMTP; 02 Jan 2007 11:01:31 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l02J1VhQ006427; 
	Tue, 2 Jan 2007 11:01:31 -0800
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l02J1IUJ014175;
	Tue, 2 Jan 2007 11:01:23 -0800 (PST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 Jan 2007 14:01:21 -0500
Received: from [10.86.242.124] ([10.86.242.124]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 Jan 2007 14:01:20 -0500
Message-ID: <459AABFF.8000404@cisco.com>
Date: Tue, 02 Jan 2007 14:01:19 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: CHADLI Youssef RD-CORE-ISS <youssef.chadli@orange-ftgroup.com>
Subject: Re: [Sipping]
	I-DACTION:draft-loreto-sipping-dialog-correlation-00.txt/
	use of same-session header with KMPL
References: <2AF8FF7D89242541B12E7A47F6ECB4BE04D1E542@ftrdmel3.rd.francetelecom.fr>
In-Reply-To: <2AF8FF7D89242541B12E7A47F6ECB4BE04D1E542@ftrdmel3.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Jan 2007 19:01:20.0903 (UTC)
	FILETIME=[63E64970:01C72EA0]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1584; t=1167764491;
	x=1168628491; c=relaxed/relaxed; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20I-DACTION=3Adraft-loreto-sipping-dialog-c
	orrelation-00.txt/=0A=20use=20of=20same-session=20header=20with=20KMPL
	|Sender:=20; bh=zwG0Uqxz4TqJsQOw0FbzJbT6M+Y9odSjjicRmubRu4E=;
	b=JAMVGq3Xn5d8BEiluvX5D3rOh0Y6H5SX6ETqA8qTRf1dM1YEGLEUXdgvPK805UHUz4M/SzyP
	nkOVAmOYuDOHaPs1ntqynPl7+hrNM4NDsj6d7GaIGrJfMpmb8xIoGELh;
Authentication-Results: sj-dkim-8; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim8002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: fluffy@cisco.com, adam@estacado.net, adam@nostrum.com,
	ravishankar.shiroor@wipro.com, roni.even@polycom.co.il,
	Gonzalo.Camarillo@ericsson.com, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

It seems to me that if the B2BUA is going to stick its ugly nose into 
this, then it has the obligation to figure out the mess it has made and 
fix it. That should be part of the work in B2BUA-"proxying" the 
SUBSCRIBE, without any extra hints from the subscriber.

	Paul

CHADLI Youssef RD-CORE-ISS wrote:
>  
> Hi,
> 
> KPML allows to correlate the KPML requests with an existing SIP dialog.
> This correlation is done by indicating the dialog identifiers within the
> KMPL request included in SUBSCRIBE. However, if a B2BUA entity is
> located between the tow UA, the dialog identifiers received by the
> notifier UA will not match any known SIP dialog . Here is an
> illustration of this problem:
> 
>    UA1					    B2BUA
> UA2
> 
>     | -----INVITE dialog D1 ------------- | -------INVITE dialog
> D2--------------  | 
>     |							|
> |	
>     | <-----SUBSCRIBE dialog D4 ----------| -------- SUBSCRIBE dialog
> D3-------    |  
>     |        KPML request (D2)	      |		KPML request (D2)
> |	
>     |							|
> |
>    
> UA2 receives a KPML request indicating D2 which it does not know.	
> It is assumed that the B2BUA does not inderstand KPML, for exemple a SIP
> ALG performing NAT.      
> 
> The use of  the Same-Session header can resolve this problem : UA2
> inserts the Same-Session header in the SUBSCRIBE request set to D2, then
> the B2BUA entity modifies this header and sets it to D1 before
> forwarding the request to UA1. Consequently, UA2 knows that KPML request
> is correlated with the media session corresponding to dialog D1. 
> Do you see any problem for doing that ?
> 
> Regards,
> 
> Youssef  
> 

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



From sipping-bounces@ietf.org Tue Jan 02 23:10:15 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H1xR1-0003yl-CD; Tue, 02 Jan 2007 23:09:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H1xQz-0003yX-S2
	for sipping@ietf.org; Tue, 02 Jan 2007 23:09:01 -0500
Received: from hoemail2.lucent.com ([192.11.226.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H1xQx-0001Xp-HW
	for sipping@ietf.org; Tue, 02 Jan 2007 23:09:01 -0500
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail2.lucent.com (8.13.8/IER-o) with ESMTP id l0348m44019119;
	Tue, 2 Jan 2007 22:08:48 -0600 (CST)
Received: from [127.0.0.1] ([135.104.20.69])
	by homail.ho.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l0348mW02551; Tue, 2 Jan 2007 23:08:48 -0500 (EST)
Message-ID: <459B2C4D.8000701@bell-labs.com>
Date: Tue, 02 Jan 2007 23:08:45 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Darshan Bildikar <dbildikar@ipunity.com>
References: <EXCHANGEVMMxB6rbe3g00001461@exchangevm.ipunity.com>
In-Reply-To: <EXCHANGEVMMxB6rbe3g00001461@exchangevm.ipunity.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 192.11.226.42
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: 'sipping' <sipping@ietf.org>
Subject: [Sipping] Re: Queries and comments on
	draft-hilt-sipping-overload-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Darshan Bildikar wrote:
> 1) How does this document relate to
> "draft-rosenberg-sipping-overload-reqs-01"? Does it take into cognisance the
> requirements defined in this document? 
> 
Yes, it should.

> 2) It is envisioned that overload information is exchanged through a header
> in response messages. Why not a more EXPLICIT mechanism like
> SUBSCRIBE/NOTIFY? Define an event package for overload and define a body
> that can be used to indicate a rich set of overload parameters to the
> upstream entity. 
> 
Using SUBSCRIBE/NOTIFY would require a proxy to subscribe to a 
downstream neighbor when (or before) sending requests to this neighbor 
to inquire the current load status. This would cause some messaging 
overhead, in particular, for proxies that talk to many downstream 
neighbors. The nice property of using a response header is that it is 
very light-weight and it automatically provides feedback from the 
downstream entities a proxy is currently talking to.

What did you have in mind for the rich set of overload parameters?

> 3) The draft talks about overload w.r.t certain resources. If a sub/not
> mechanism was used, it would allow overload control to be more "fine
> grained". For example, the SUBSCRIBE message would indicate what resource
> the requester is wants the overload throttling and statistics for. 
> 
Overload control is used when a SIP entity is unable to handle all 
incoming messages because it ran out of resources it needs for 
processing messages. To an upstream neighbor, it really does not matter 
which resource on the downstream element is the bottleneck. What matters 
is that the downstream element can't process all messages and, thus, the 
load has to be reduced. As long as the downstream element has enough 
capacity to return a meaningful response (e.g. 488 if a PSTN gateway 
runs out of trunk lines) it should do so.

> A use case that I can think of 
> 
> I have two applications on my box; CRBT and video conferencing. I might be
> fast running out of ports for video conferencing but might still be able to
> do CRBT at 100%. I should be able to control the load based on the REQUEST
> URI. 

I don't think this is a valid example for the use of overload control. 
If the box is still able to do CRBT, it should also be able to reject 
the additional requests for video conferencing.

> I'm thinking that the SUBSCRIBE shall indicate, "Give me overload statistics
> as if I were sending you this REQUEST URI". I'm assuming that a request URI
> maps to a "resource" but there could be a better way this could be done. 
> 
> This mechanism would help throttling based on SIP method, URI, host, port
> etc and will be able to support REQ 18 defined in
> draft-rosenberg-sipping-overload-reqs-01". 
> 
> Two things that I haven't really thought through.
> 
> 1) Throttling based on codecs and media lines would be useful. For example,
> I can support audio right now, but NOT video. 
> 2) Is it possible to make this mechanism more generic? It is after all a
> throttling mechanism and could be applied to domains OTHER than overload
> control. For example, Tele voting applications where an application server
> indicates filtering to a switch i.e. "Notify every 100'th INVITE to me"
> 
I don't think that the scope of overload control should be extended into 
these domains. Overload control specifically helps devices to deal with 
signaling overload. If a device is still able to return a SIP response 
it is not in signaling overload and should create a response with the 
appropriate response code.

Volker




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



From sipping-bounces@ietf.org Tue Jan 02 23:36:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H1xrQ-0004Op-JF; Tue, 02 Jan 2007 23:36:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H1xrP-0004Nd-Ce
	for sipping@ietf.org; Tue, 02 Jan 2007 23:36:19 -0500
Received: from corp2.ipunity.com ([65.106.79.133] helo=exchangevm.ipunity.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H1xrM-0007th-TV
	for sipping@ietf.org; Tue, 02 Jan 2007 23:36:19 -0500
Received: from BLRPC6 ([10.253.253.150]) by exchangevm.ipunity.com with
	Microsoft SMTPSVC(5.0.2195.6713); Tue, 2 Jan 2007 20:30:06 -0800
From: "Darshan Bildikar" <dbildikar@ipunity.com>
To: "'Volker Hilt'" <volkerh@bell-labs.com>
Date: Wed, 3 Jan 2007 10:05:04 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: Accu7dudMj0KwuuITOeralEcpLseRwAAAqpA
In-Reply-To: <459B2C4D.8000701@bell-labs.com>
Message-ID: <EXCHANGEVMjWC5qNpIx00001bb1@exchangevm.ipunity.com>
X-OriginalArrivalTime: 03 Jan 2007 04:30:06.0549 (UTC)
	FILETIME=[D85EA050:01C72EEF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: 'sipping' <sipping@ietf.org>
Subject: [Sipping] RE: Queries and comments on
	draft-hilt-sipping-overload-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hello Volker,

Thank you for the response. 

My responses inline marked by <Darshan>

BR
Darshan

-----Original Message-----
From: Volker Hilt [mailto:volkerh@bell-labs.com] 
Sent: Wednesday, January 03, 2007 9:39 AM
To: Darshan Bildikar
Cc: 'sipping'
Subject: Re: Queries and comments on draft-hilt-sipping-overload-00.txt

Darshan Bildikar wrote:
> 1) How does this document relate to
> "draft-rosenberg-sipping-overload-reqs-01"? Does it take into cognisance
the
> requirements defined in this document? 
> 
Yes, it should.

> 2) It is envisioned that overload information is exchanged through a
header
> in response messages. Why not a more EXPLICIT mechanism like
> SUBSCRIBE/NOTIFY? Define an event package for overload and define a body
> that can be used to indicate a rich set of overload parameters to the
> upstream entity. 
> 
Using SUBSCRIBE/NOTIFY would require a proxy to subscribe to a 
downstream neighbor when (or before) sending requests to this neighbor 
to inquire the current load status. This would cause some messaging 
overhead, in particular, for proxies that talk to many downstream 
neighbors. The nice property of using a response header is that it is 
very light-weight and it automatically provides feedback from the 
downstream entities a proxy is currently talking to.

<Darshan 1> Say a downstream entity has indicated that it is loaded at 100%.
This would result in the upstream proxy NOT forwarding it ANY requests. How
does the proxy determine when to send the next request then? It would never
know EXACTLY when the downstream element becomes available. A sub/not
mechanism allows the downstream element to indicate to an upstream element,
load status at discrete points of time instead of waiting for a request
which might never come!

Also, I don't agree that this would cause a messaging overhead. It's just
one more SIP dialog per downstream element. Even with your approach an
upstream element still needs to maintain some kind of "STATE" about the load
of each downstream element. We only avoid the SIP messaging. 

What did you have in mind for the rich set of overload parameters?
<Darshan> By rich set, I only meant overload PER resource instance on the
SIP downstream entity. 

> 3) The draft talks about overload w.r.t certain resources. If a sub/not
> mechanism was used, it would allow overload control to be more "fine
> grained". For example, the SUBSCRIBE message would indicate what resource
> the requester is wants the overload throttling and statistics for. 
> 
Overload control is used when a SIP entity is unable to handle all 
incoming messages because it ran out of resources it needs for 
processing messages. To an upstream neighbor, it really does not matter 
which resource on the downstream element is the bottleneck. What matters 
is that the downstream element can't process all messages and, thus, the 
load has to be reduced. As long as the downstream element has enough 
capacity to return a meaningful response (e.g. 488 if a PSTN gateway 
runs out of trunk lines) it should do so.

<Darshan 2> While I do agree with you, I think it's a useful feature to be
able to throttle specific traffic. There is definitely a use case for it.
Why should I waste time on generating 488 responses when I KNOW that I wont
be able to process certain requests beyond a limit. If I am able to indicate
load to an upstream entity for a specific resource, I would be able to run
my system much more efficiently. Ideally I SHOULD be able to throttle my
traffic in order to spend resources processing request I KNOW I can handle
and not reject. 

It would also allow me to partition resources on my box beautifully as I
would be able to control requests I receive for a particular resource. (I'm
thinking more from the point of view of an AS running services).

> A use case that I can think of 
> 
> I have two applications on my box; CRBT and video conferencing. I might be
> fast running out of ports for video conferencing but might still be able
to
> do CRBT at 100%. I should be able to control the load based on the REQUEST
> URI. 

I don't think this is a valid example for the use of overload control. 
If the box is still able to do CRBT, it should also be able to reject 
the additional requests for video conferencing.

<Darshan> See previous response

> I'm thinking that the SUBSCRIBE shall indicate, "Give me overload
statistics
> as if I were sending you this REQUEST URI". I'm assuming that a request
URI
> maps to a "resource" but there could be a better way this could be done. 
> 
> This mechanism would help throttling based on SIP method, URI, host, port
> etc and will be able to support REQ 18 defined in
> draft-rosenberg-sipping-overload-reqs-01". 
> 
> Two things that I haven't really thought through.
> 
> 1) Throttling based on codecs and media lines would be useful. For
example,
> I can support audio right now, but NOT video. 
> 2) Is it possible to make this mechanism more generic? It is after all a
> throttling mechanism and could be applied to domains OTHER than overload
> control. For example, Tele voting applications where an application server
> indicates filtering to a switch i.e. "Notify every 100'th INVITE to me"
> 
I don't think that the scope of overload control should be extended into 
these domains. Overload control specifically helps devices to deal with 
signaling overload. If a device is still able to return a SIP response 
it is not in signaling overload and should create a response with the 
appropriate response code.

<Darshan 3> As I said I haven't really thought this through. My only point
being that we should try and "generify" wherever possible. If someone
decides to implement SIP mechanism for tele voting/throttling applications,
they would find that what they want to do is already ALMOST done in
overload. 

Volker


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



From sipping-bounces@ietf.org Wed Jan 03 08:54:24 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H26YD-0001qE-LM; Wed, 03 Jan 2007 08:53:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H26YC-0001q6-Gm
	for sipping@ietf.org; Wed, 03 Jan 2007 08:53:04 -0500
Received: from amer-mta08.csc.com ([20.137.52.152])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H26YA-00029h-25
	for sipping@ietf.org; Wed, 03 Jan 2007 08:53:04 -0500
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245])
	by amer-mta08.csc.com (Switch-3.1.6/Switch-3.1.0) with ESMTP id
	l03DqxBj021927; Wed, 3 Jan 2007 08:53:00 -0500 (EST)
In-Reply-To: <EXCHANGEVMjWC5qNpIx00001bb1@exchangevm.ipunity.com>
Subject: Re: [Sipping] RE: Queries and comments
	on	draft-hilt-sipping-overload-00.txt
To: "Darshan Bildikar" <dbildikar@ipunity.com>
X-Mailer: Lotus Notes 652HF83 November 04, 2004
Message-ID: <OFEFCE9F52.7C42739D-ON85257258.004B6B94-85257258.004C4058@csc.com>
From: Janet P Gunn <jgunn6@csc.com>
Date: Wed, 3 Jan 2007 08:52:52 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 7.0.2|September
	26, 2006) at 01/03/2007 08:51:44 AM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff
Cc: 'Volker Hilt' <volkerh@bell-labs.com>, 'sipping' <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



I think it is important to focus on overload of the ability to PROCESS SIP
messages.  In particular, the focus should be on the situation where, if
the SIP messages keep coming, the box will crash (usually preceded by
unproductive thrashing).

As such, the mechanism and messaging must be as "lightweight" as possible,
in order to avoid making the machine congestion worse.

The other kinds of resource specific overload mechanisms you discuss sound
very useful.  But I don't think it is a good idea to try to overload them
on THIS effort.

Janet


"Darshan Bildikar" <dbildikar@ipunity.com> wrote on 01/02/2007 11:35:04 PM:

> Hello Volker,
>
> Thank you for the response.
>
> My responses inline marked by <Darshan>
>
> BR
> Darshan
>
> -----Original Message-----
> From: Volker Hilt [mailto:volkerh@bell-labs.com]
> Sent: Wednesday, January 03, 2007 9:39 AM
> To: Darshan Bildikar
> Cc: 'sipping'
> Subject: Re: Queries and comments on draft-hilt-sipping-overload-00.txt
>
> Darshan Bildikar wrote:
> > 1) How does this document relate to
> > "draft-rosenberg-sipping-overload-reqs-01"? Does it take into
cognisance
> the
> > requirements defined in this document?
> >
> Yes, it should.
>
> > 2) It is envisioned that overload information is exchanged through a
> header
> > in response messages. Why not a more EXPLICIT mechanism like
> > SUBSCRIBE/NOTIFY? Define an event package for overload and define a
body
> > that can be used to indicate a rich set of overload parameters to the
> > upstream entity.
> >
> Using SUBSCRIBE/NOTIFY would require a proxy to subscribe to a
> downstream neighbor when (or before) sending requests to this neighbor
> to inquire the current load status. This would cause some messaging
> overhead, in particular, for proxies that talk to many downstream
> neighbors. The nice property of using a response header is that it is
> very light-weight and it automatically provides feedback from the
> downstream entities a proxy is currently talking to.
>
> <Darshan 1> Say a downstream entity has indicated that it is loaded at
100%.
> This would result in the upstream proxy NOT forwarding it ANY requests.
How
> does the proxy determine when to send the next request then? It would
never
> know EXACTLY when the downstream element becomes available. A sub/not
> mechanism allows the downstream element to indicate to an upstream
element,
> load status at discrete points of time instead of waiting for a request
> which might never come!
>
> Also, I don't agree that this would cause a messaging overhead. It's just
> one more SIP dialog per downstream element. Even with your approach an
> upstream element still needs to maintain some kind of "STATE" about the
load
> of each downstream element. We only avoid the SIP messaging.
>
> What did you have in mind for the rich set of overload parameters?
> <Darshan> By rich set, I only meant overload PER resource instance on the
> SIP downstream entity.
>
> > 3) The draft talks about overload w.r.t certain resources. If a sub/not
> > mechanism was used, it would allow overload control to be more "fine
> > grained". For example, the SUBSCRIBE message would indicate what
resource
> > the requester is wants the overload throttling and statistics for.
> >
> Overload control is used when a SIP entity is unable to handle all
> incoming messages because it ran out of resources it needs for
> processing messages. To an upstream neighbor, it really does not matter
> which resource on the downstream element is the bottleneck. What matters
> is that the downstream element can't process all messages and, thus, the
> load has to be reduced. As long as the downstream element has enough
> capacity to return a meaningful response (e.g. 488 if a PSTN gateway
> runs out of trunk lines) it should do so.
>
> <Darshan 2> While I do agree with you, I think it's a useful feature to
be
> able to throttle specific traffic. There is definitely a use case for it.
> Why should I waste time on generating 488 responses when I KNOW that I
wont
> be able to process certain requests beyond a limit. If I am able to
indicate
> load to an upstream entity for a specific resource, I would be able to
run
> my system much more efficiently. Ideally I SHOULD be able to throttle my
> traffic in order to spend resources processing request I KNOW I can
handle
> and not reject.
>
> It would also allow me to partition resources on my box beautifully as I
> would be able to control requests I receive for a particular resource.
(I'm
> thinking more from the point of view of an AS running services).
>
> > A use case that I can think of
> >
> > I have two applications on my box; CRBT and video conferencing. I might
be
> > fast running out of ports for video conferencing but might still be
able
> to
> > do CRBT at 100%. I should be able to control the load based on the
REQUEST
> > URI.
>
> I don't think this is a valid example for the use of overload control.
> If the box is still able to do CRBT, it should also be able to reject
> the additional requests for video conferencing.
>
> <Darshan> See previous response
>
> > I'm thinking that the SUBSCRIBE shall indicate, "Give me overload
> statistics
> > as if I were sending you this REQUEST URI". I'm assuming that a request
> URI
> > maps to a "resource" but there could be a better way this could be
done.
> >
> > This mechanism would help throttling based on SIP method, URI, host,
port
> > etc and will be able to support REQ 18 defined in
> > draft-rosenberg-sipping-overload-reqs-01".
> >
> > Two things that I haven't really thought through.
> >
> > 1) Throttling based on codecs and media lines would be useful. For
> example,
> > I can support audio right now, but NOT video.
> > 2) Is it possible to make this mechanism more generic? It is after all
a
> > throttling mechanism and could be applied to domains OTHER than
overload
> > control. For example, Tele voting applications where an application
server
> > indicates filtering to a switch i.e. "Notify every 100'th INVITE to me"
> >
> I don't think that the scope of overload control should be extended into
> these domains. Overload control specifically helps devices to deal with
> signaling overload. If a device is still able to return a SIP response
> it is not in signaling overload and should create a response with the
> appropriate response code.
>
> <Darshan 3> As I said I haven't really thought this through. My only
point
> being that we should try and "generify" wherever possible. If someone
> decides to implement SIP mechanism for tele voting/throttling
applications,
> they would find that what they want to do is already ALMOST done in
> overload.
>
> Volker
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org Wed Jan 03 10:43:07 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H28GJ-0005Ls-4y; Wed, 03 Jan 2007 10:42:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H28GH-0005Lm-Q7
	for sipping@ietf.org; Wed, 03 Jan 2007 10:42:41 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H28GG-0005Hc-57
	for sipping@ietf.org; Wed, 03 Jan 2007 10:42:41 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 03 Jan 2007 07:42:38 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l03FgctS022544; 
	Wed, 3 Jan 2007 07:42:38 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l03FgGJ3003306;
	Wed, 3 Jan 2007 07:42:38 -0800 (PST)
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 3 Jan 2007 10:42:36 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: Queries and
	commentson	draft-hilt-sipping-overload-00.txt
Date: Wed, 3 Jan 2007 10:42:35 -0500
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E3026B632D@xmb-rtp-20b.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] RE: Queries and
	commentson	draft-hilt-sipping-overload-00.txt
Thread-Index: AccvPuBD2qRZ2puhROSG1Ijik/jjIwADnSAQ
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Janet P Gunn" <jgunn6@csc.com>, "Darshan Bildikar" <dbildikar@ipunity.com>
X-OriginalArrivalTime: 03 Jan 2007 15:42:36.0097 (UTC)
	FILETIME=[CA930B10:01C72F4D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8804; t=1167838958;
	x=1168702958; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mhammer@cisco.com;
	z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20RE=3A=20Queries=20and=20commentson=09draf
	t-hilt-sipping-overload-00.txt |Sender:=20;
	bh=hejzqXRlyisI+swZumx3ALqWdvNSvQcUQZTVJDwbGBY=;
	b=nOhmByVrGWrH2wWfKqq6p2ILGomTLr9CSL8VGe0+2dFvXukGFCi8Cg0B5uYfqCeJjLcVc/On
	R109i1JtP7tcELBg1XTkMrQG4lK+71E6F82B8l86XSJxHXTsrwgC1JM3;
Authentication-Results: sj-dkim-7; header.From=mhammer@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32029c790f79bd4a84a26bd2915c54b9
Cc: Volker Hilt <volkerh@bell-labs.com>, sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Janet and others,

Just out of curiosity, do you assume that SIP is the ONLY protocol
operating on a particular platform?

If not, then do you assume that each protocol has its own oveload
control mechanism and that each will independently determine when the
machine is overloaded?

Mike


> -----Original Message-----
> From: Janet P Gunn [mailto:jgunn6@csc.com]=20
> Sent: Wednesday, January 03, 2007 8:53 AM
> To: Darshan Bildikar
> Cc: 'Volker Hilt'; 'sipping'
> Subject: Re: [Sipping] RE: Queries and commentson=20
> draft-hilt-sipping-overload-00.txt
>=20
>=20
>=20
> I think it is important to focus on overload of the ability=20
> to PROCESS SIP messages.  In particular, the focus should be=20
> on the situation where, if the SIP messages keep coming, the=20
> box will crash (usually preceded by unproductive thrashing).
>=20
> As such, the mechanism and messaging must be as "lightweight"=20
> as possible, in order to avoid making the machine congestion worse.
>=20
> The other kinds of resource specific overload mechanisms you=20
> discuss sound very useful.  But I don't think it is a good=20
> idea to try to overload them on THIS effort.
>=20
> Janet
>=20
>=20
> "Darshan Bildikar" <dbildikar@ipunity.com> wrote on=20
> 01/02/2007 11:35:04 PM:
>=20
> > Hello Volker,
> >
> > Thank you for the response.
> >
> > My responses inline marked by <Darshan>
> >
> > BR
> > Darshan
> >
> > -----Original Message-----
> > From: Volker Hilt [mailto:volkerh@bell-labs.com]
> > Sent: Wednesday, January 03, 2007 9:39 AM
> > To: Darshan Bildikar
> > Cc: 'sipping'
> > Subject: Re: Queries and comments on=20
> > draft-hilt-sipping-overload-00.txt
> >
> > Darshan Bildikar wrote:
> > > 1) How does this document relate to
> > > "draft-rosenberg-sipping-overload-reqs-01"? Does it take into
> cognisance
> > the
> > > requirements defined in this document?
> > >
> > Yes, it should.
> >
> > > 2) It is envisioned that overload information is=20
> exchanged through a
> > header
> > > in response messages. Why not a more EXPLICIT mechanism like=20
> > > SUBSCRIBE/NOTIFY? Define an event package for overload=20
> and define a
> body
> > > that can be used to indicate a rich set of overload parameters to=20
> > > the upstream entity.
> > >
> > Using SUBSCRIBE/NOTIFY would require a proxy to subscribe to a=20
> > downstream neighbor when (or before) sending requests to=20
> this neighbor=20
> > to inquire the current load status. This would cause some messaging=20
> > overhead, in particular, for proxies that talk to many downstream=20
> > neighbors. The nice property of using a response header is=20
> that it is=20
> > very light-weight and it automatically provides feedback from the=20
> > downstream entities a proxy is currently talking to.
> >
> > <Darshan 1> Say a downstream entity has indicated that it=20
> is loaded at
> 100%.
> > This would result in the upstream proxy NOT forwarding it=20
> ANY requests.
> How
> > does the proxy determine when to send the next request=20
> then? It would
> never
> > know EXACTLY when the downstream element becomes available.=20
> A sub/not=20
> > mechanism allows the downstream element to indicate to an upstream
> element,
> > load status at discrete points of time instead of waiting for a=20
> > request which might never come!
> >
> > Also, I don't agree that this would cause a messaging=20
> overhead. It's=20
> > just one more SIP dialog per downstream element. Even with your=20
> > approach an upstream element still needs to maintain some kind of=20
> > "STATE" about the
> load
> > of each downstream element. We only avoid the SIP messaging.
> >
> > What did you have in mind for the rich set of overload parameters?
> > <Darshan> By rich set, I only meant overload PER resource=20
> instance on=20
> > the SIP downstream entity.
> >
> > > 3) The draft talks about overload w.r.t certain resources. If a=20
> > > sub/not mechanism was used, it would allow overload control to be=20
> > > more "fine grained". For example, the SUBSCRIBE message would=20
> > > indicate what
> resource
> > > the requester is wants the overload throttling and statistics for.
> > >
> > Overload control is used when a SIP entity is unable to handle all=20
> > incoming messages because it ran out of resources it needs for=20
> > processing messages. To an upstream neighbor, it really does not=20
> > matter which resource on the downstream element is the bottleneck.=20
> > What matters is that the downstream element can't process=20
> all messages=20
> > and, thus, the load has to be reduced. As long as the downstream=20
> > element has enough capacity to return a meaningful response=20
> (e.g. 488=20
> > if a PSTN gateway runs out of trunk lines) it should do so.
> >
> > <Darshan 2> While I do agree with you, I think it's a=20
> useful feature=20
> > to
> be
> > able to throttle specific traffic. There is definitely a=20
> use case for it.
> > Why should I waste time on generating 488 responses when I=20
> KNOW that I
> wont
> > be able to process certain requests beyond a limit. If I am able to
> indicate
> > load to an upstream entity for a specific resource, I would=20
> be able to
> run
> > my system much more efficiently. Ideally I SHOULD be able=20
> to throttle=20
> > my traffic in order to spend resources processing request I=20
> KNOW I can
> handle
> > and not reject.
> >
> > It would also allow me to partition resources on my box=20
> beautifully as=20
> > I would be able to control requests I receive for a=20
> particular resource.
> (I'm
> > thinking more from the point of view of an AS running services).
> >
> > > A use case that I can think of
> > >
> > > I have two applications on my box; CRBT and video conferencing. I=20
> > > might
> be
> > > fast running out of ports for video conferencing but=20
> might still be
> able
> > to
> > > do CRBT at 100%. I should be able to control the load based on the
> REQUEST
> > > URI.
> >
> > I don't think this is a valid example for the use of=20
> overload control.
> > If the box is still able to do CRBT, it should also be able=20
> to reject=20
> > the additional requests for video conferencing.
> >
> > <Darshan> See previous response
> >
> > > I'm thinking that the SUBSCRIBE shall indicate, "Give me overload
> > statistics
> > > as if I were sending you this REQUEST URI". I'm assuming that a=20
> > > request
> > URI
> > > maps to a "resource" but there could be a better way this could be
> done.
> > >
> > > This mechanism would help throttling based on SIP method,=20
> URI, host,
> port
> > > etc and will be able to support REQ 18 defined in=20
> > > draft-rosenberg-sipping-overload-reqs-01".
> > >
> > > Two things that I haven't really thought through.
> > >
> > > 1) Throttling based on codecs and media lines would be useful. For
> > example,
> > > I can support audio right now, but NOT video.
> > > 2) Is it possible to make this mechanism more generic? It=20
> is after=20
> > > all
> a
> > > throttling mechanism and could be applied to domains OTHER than
> overload
> > > control. For example, Tele voting applications where an=20
> application
> server
> > > indicates filtering to a switch i.e. "Notify every 100'th=20
> INVITE to me"
> > >
> > I don't think that the scope of overload control should be extended=20
> > into these domains. Overload control specifically helps devices to=20
> > deal with signaling overload. If a device is still able to return a=20
> > SIP response it is not in signaling overload and should create a=20
> > response with the appropriate response code.
> >
> > <Darshan 3> As I said I haven't really thought this through. My only
> point
> > being that we should try and "generify" wherever possible.=20
> If someone=20
> > decides to implement SIP mechanism for tele voting/throttling
> applications,
> > they would find that what they want to do is already ALMOST done in=20
> > overload.
> >
> > Volker
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP=20
> Use sip-implementors@cs.columbia.edu for questions on current=20
> sip Use sip@ietf.org for new developments of core SIP
>=20

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



From sipping-bounces@ietf.org Wed Jan 03 11:19:19 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H28oB-0003bx-6H; Wed, 03 Jan 2007 11:17:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H28o8-0003bn-VZ
	for sipping@ietf.org; Wed, 03 Jan 2007 11:17:40 -0500
Received: from hoemail2.lucent.com ([192.11.226.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H28o7-0006IR-3V
	for sipping@ietf.org; Wed, 03 Jan 2007 11:17:40 -0500
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail2.lucent.com (8.13.8/IER-o) with ESMTP id l03GHaGO011050;
	Wed, 3 Jan 2007 10:17:36 -0600 (CST)
Received: from [135.180.240.247] (volker-hopc2.dnrc.bell-labs.com
	[135.180.240.247])
	by homail.ho.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l03GHaW19453; Wed, 3 Jan 2007 11:17:36 -0500 (EST)
Message-ID: <459BD720.4050500@bell-labs.com>
Date: Wed, 03 Jan 2007 11:17:36 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Darshan Bildikar <dbildikar@ipunity.com>
References: <EXCHANGEVMjWC5qNpIx00001bb1@exchangevm.ipunity.com>
In-Reply-To: <EXCHANGEVMjWC5qNpIx00001bb1@exchangevm.ipunity.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 192.11.226.42
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: 'sipping' <sipping@ietf.org>
Subject: [Sipping] Re: Queries and comments on
	draft-hilt-sipping-overload-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

> Darshan Bildikar wrote:
>> 2) It is envisioned that overload information is exchanged through a
> header
>> in response messages. Why not a more EXPLICIT mechanism like
>> SUBSCRIBE/NOTIFY? Define an event package for overload and define a body
>> that can be used to indicate a rich set of overload parameters to the
>> upstream entity. 
>>
> Using SUBSCRIBE/NOTIFY would require a proxy to subscribe to a 
> downstream neighbor when (or before) sending requests to this neighbor 
> to inquire the current load status. This would cause some messaging 
> overhead, in particular, for proxies that talk to many downstream 
> neighbors. The nice property of using a response header is that it is 
> very light-weight and it automatically provides feedback from the 
> downstream entities a proxy is currently talking to.
> 
> <Darshan 1> Say a downstream entity has indicated that it is loaded at 100%.
> This would result in the upstream proxy NOT forwarding it ANY requests. How
> does the proxy determine when to send the next request then? It would never
> know EXACTLY when the downstream element becomes available. A sub/not
> mechanism allows the downstream element to indicate to an upstream element,
> load status at discrete points of time instead of waiting for a request
> which might never come!
> 
Usually a proxy will not entirely stop sending messages to a downstream 
neighbor. Instead, overload control should slowly regulate the request 
rate to a lower level that is acceptable to the downstream proxy. So 
even in an overload situation, the upstream proxy would still send some 
requests and therefore receive responses that contain the load status. 
Even in very extreme overload where a proxy entirely stops to forward 
requests, it can still occasionally forward a request to probe the 
current load status.

> Also, I don't agree that this would cause a messaging overhead. It's just
> one more SIP dialog per downstream element. Even with your approach an
> upstream element still needs to maintain some kind of "STATE" about the load
> of each downstream element. We only avoid the SIP messaging.
> 
I think the messaging overhead is key here. Avoiding SIP messaging is 
important for a mechanism that deals with messaging overload. SUB/NOT 
also requires both parties to maintain dialog state but that might not 
be that significant (it still could pose a problem if memory is the 
bottleneck on the downstream entity). I agree that even with a header, 
load state needs to be kept in the upstream proxy (the draft talks about 
this in detail).

>> 3) The draft talks about overload w.r.t certain resources. If a sub/not
>> mechanism was used, it would allow overload control to be more "fine
>> grained". For example, the SUBSCRIBE message would indicate what resource
>> the requester is wants the overload throttling and statistics for. 
>>
> Overload control is used when a SIP entity is unable to handle all 
> incoming messages because it ran out of resources it needs for 
> processing messages. To an upstream neighbor, it really does not matter 
> which resource on the downstream element is the bottleneck. What matters 
> is that the downstream element can't process all messages and, thus, the 
> load has to be reduced. As long as the downstream element has enough 
> capacity to return a meaningful response (e.g. 488 if a PSTN gateway 
> runs out of trunk lines) it should do so.
> 
> <Darshan 2> While I do agree with you, I think it's a useful feature to be
> able to throttle specific traffic. There is definitely a use case for it.
> Why should I waste time on generating 488 responses when I KNOW that I wont
> be able to process certain requests beyond a limit. If I am able to indicate
> load to an upstream entity for a specific resource, I would be able to run
> my system much more efficiently. Ideally I SHOULD be able to throttle my
> traffic in order to spend resources processing request I KNOW I can handle
> and not reject. 
> 
I'm not yet fully convinced that the benefits of rejecting a message one 
hop earlier for the cases you describe really justify the complexity 
needed for this. What would be achieved is that a request is forwarded 
one hop less to a device that could still produce a meaningful response.

But apart from this, I think we should try to keep overload control as 
simple as possible and make it effective in dealing with signaling overload.

>> Two things that I haven't really thought through.
>>
>> 1) Throttling based on codecs and media lines would be useful. For
> example,
>> I can support audio right now, but NOT video. 
>> 2) Is it possible to make this mechanism more generic? It is after all a
>> throttling mechanism and could be applied to domains OTHER than overload
>> control. For example, Tele voting applications where an application server
>> indicates filtering to a switch i.e. "Notify every 100'th INVITE to me"
>>
> I don't think that the scope of overload control should be extended into 
> these domains. Overload control specifically helps devices to deal with 
> signaling overload. If a device is still able to return a SIP response 
> it is not in signaling overload and should create a response with the 
> appropriate response code.
> 
> <Darshan 3> As I said I haven't really thought this through. My only point
> being that we should try and "generify" wherever possible. If someone
> decides to implement SIP mechanism for tele voting/throttling applications,
> they would find that what they want to do is already ALMOST done in
> overload. 
> 
The tele voting/throttling is interesting since it requires to set up 
throttles for a specific target at a specific point in time. So it is 
effectively an overload control that is known a priori.

I'm not sure how this relates to the reactive overload control mechanism 
that we are talking about here. The load feedback would not be needed 
for a priory throttles. However, the procedures to throttle may be 
similar. My gut feeling is that it is a separate mechanism that needs to 
be able to work along with overload control.

Thanks,

Volker


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



From sipping-bounces@ietf.org Wed Jan 03 12:10:59 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H29cz-00073n-TX; Wed, 03 Jan 2007 12:10:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H29cy-00073h-I1
	for sipping@ietf.org; Wed, 03 Jan 2007 12:10:12 -0500
Received: from amer-mta08.csc.com ([20.137.52.152])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H29cw-0001OG-7X
	for sipping@ietf.org; Wed, 03 Jan 2007 12:10:12 -0500
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245])
	by amer-mta08.csc.com (Switch-3.1.6/Switch-3.1.0) with ESMTP id
	l03HA3HR020427; Wed, 3 Jan 2007 12:10:08 -0500 (EST)
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E3026B632D@xmb-rtp-20b.amer.cisco.com>
Subject: RE: [Sipping] RE: Queries and
	commentson	draft-hilt-sipping-overload-00.txt
To: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-Mailer: Lotus Notes 652HF83 November 04, 2004
Message-ID: <OF81F7E74F.0F0771D4-ON85257258.005D44BF-85257258.005E4EA5@csc.com>
From: Janet P Gunn <jgunn6@csc.com>
Date: Wed, 3 Jan 2007 12:10:05 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 7.0.2|September
	26, 2006) at 01/03/2007 12:08:52 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: sipping <sipping@ietf.org>, Volker Hilt <volkerh@bell-labs.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Mike,

Good point..

Obviously everything is simplest if we are only dealing with one protocol.

If the box is serving multiple protocols, I would assume that
detecting/identifying overload applies to the machine, not the protocol
(e.g , cpu usage, internal queue length, time in  queue).

SIP can, of course, only address signalling the overload to other boxes
that "talk" SIP.  Obviously, if that "other box" is sending both SIP
messages and other-protocol-messages to the overloaded box, it would be
nice/ sensible if the "other box" throttled all messages (SIP or otherwise)
to the overloaded box.  But I don't think SIP can specify that.

If the overloaded box talks to some boxes that "talk" SIP, and some that
don't, there is always the possibility that the SIP boxes will cut back,
and the others won't, leaving the overloaded box STILL overloaded, but with
non-SIP work.  Obviously this wouldn't be a good idea.  I don't think we
can necessarily assume it away, but I don't think we can "solve" it with a
SIP document.

Janet



"Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on 01/03/2007
10:42:35 AM:

> Janet and others,
>
> Just out of curiosity, do you assume that SIP is the ONLY protocol
> operating on a particular platform?
>
> If not, then do you assume that each protocol has its own oveload
> control mechanism and that each will independently determine when the
> machine is overloaded?
>
> Mike
>
>
> > -----Original Message-----
> > From: Janet P Gunn [mailto:jgunn6@csc.com]
> > Sent: Wednesday, January 03, 2007 8:53 AM
> > To: Darshan Bildikar
> > Cc: 'Volker Hilt'; 'sipping'
> > Subject: Re: [Sipping] RE: Queries and commentson
> > draft-hilt-sipping-overload-00.txt
> >
> >
> >
> > I think it is important to focus on overload of the ability
> > to PROCESS SIP messages.  In particular, the focus should be
> > on the situation where, if the SIP messages keep coming, the
> > box will crash (usually preceded by unproductive thrashing).
> >
> > As such, the mechanism and messaging must be as "lightweight"
> > as possible, in order to avoid making the machine congestion worse.
> >
> > The other kinds of resource specific overload mechanisms you
> > discuss sound very useful.  But I don't think it is a good
> > idea to try to overload them on THIS effort.
> >
> > Janet
> >
> >


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



From sipping-bounces@ietf.org Wed Jan 03 13:54:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2BFC-0006CV-Sm; Wed, 03 Jan 2007 13:53:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2BFB-00069J-NR
	for sipping@ietf.org; Wed, 03 Jan 2007 13:53:45 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2BFA-0001Yj-8R
	for sipping@ietf.org; Wed, 03 Jan 2007 13:53:45 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 03 Jan 2007 10:53:44 -0800
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l03Irh82021606; 
	Wed, 3 Jan 2007 10:53:43 -0800
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l03IrJm5019882;
	Wed, 3 Jan 2007 10:53:39 -0800 (PST)
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 3 Jan 2007 13:53:37 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: Queries and
	commentson	draft-hilt-sipping-overload-00.txt
Date: Wed, 3 Jan 2007 13:53:36 -0500
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E3026B6456@xmb-rtp-20b.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] RE: Queries and
	commentson	draft-hilt-sipping-overload-00.txt
Thread-Index: AccvWhHCYqH/i39mTEKiV4kr+7NLPQAB4cXg
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Janet P Gunn" <jgunn6@csc.com>
X-OriginalArrivalTime: 03 Jan 2007 18:53:37.0136 (UTC)
	FILETIME=[79E2CF00:01C72F68]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3535; t=1167850423;
	x=1168714423; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mhammer@cisco.com;
	z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20RE=3A=20Queries=20and=20commentson=09draf
	t-hilt-sipping-overload-00.txt |Sender:=20;
	bh=VGrOjlluLcYiMuQ/slF0PXzm7OWbKZZaHoYxjOAjgLI=;
	b=sWMQybW4TbCqmxYGuPBVvWK+oC1/dzMztI5K/EzSeGP3MW8eY1l/FRBGwNA1FWxLLb379/2p
	7SzTGdPe0LxVoPYQ1s5GhO0zN4tR3+8w2IgRNeOkMfBSxFcdmC61BeA/;
Authentication-Results: sj-dkim-7; header.From=mhammer@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: sipping <sipping@ietf.org>, Volker Hilt <volkerh@bell-labs.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Janet,

I know it would be simpler to ignore anything not SIP, but in fact SIP
is designed to set up all sorts of sessions defined in SDP that SIP is
blissfully unaware of, since the nature of the media is an SDP issue not
a SIP issue.

Similarly, the Event framework enables reporting of "events" in the SIP
Notifies without any constraints (as far as I can tell) of what can be
defined as an event.  The structure of an event is whatever event can be
defined in XML.

This is a case where thinking could go outside the SIP box, if one were
so inclinded.

Mike


> -----Original Message-----
> From: Janet P Gunn [mailto:jgunn6@csc.com]=20
> Sent: Wednesday, January 03, 2007 12:10 PM
> To: Michael Hammer (mhammer)
> Cc: Darshan Bildikar; sipping; Volker Hilt
> Subject: RE: [Sipping] RE: Queries and commentson=20
> draft-hilt-sipping-overload-00.txt
>=20
> Mike,
>=20
> Good point..
>=20
> Obviously everything is simplest if we are only dealing with=20
> one protocol.
>=20
> If the box is serving multiple protocols, I would assume that=20
> detecting/identifying overload applies to the machine, not=20
> the protocol (e.g , cpu usage, internal queue length, time in  queue).
>=20
> SIP can, of course, only address signalling the overload to=20
> other boxes that "talk" SIP.  Obviously, if that "other box"=20
> is sending both SIP messages and other-protocol-messages to=20
> the overloaded box, it would be nice/ sensible if the "other=20
> box" throttled all messages (SIP or otherwise) to the=20
> overloaded box.  But I don't think SIP can specify that.
>=20
> If the overloaded box talks to some boxes that "talk" SIP,=20
> and some that don't, there is always the possibility that the=20
> SIP boxes will cut back, and the others won't, leaving the=20
> overloaded box STILL overloaded, but with non-SIP work. =20
> Obviously this wouldn't be a good idea.  I don't think we can=20
> necessarily assume it away, but I don't think we can "solve"=20
> it with a SIP document.
>=20
> Janet
>=20
>=20
>=20
> "Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on 01/03/2007
> 10:42:35 AM:
>=20
> > Janet and others,
> >
> > Just out of curiosity, do you assume that SIP is the ONLY protocol=20
> > operating on a particular platform?
> >
> > If not, then do you assume that each protocol has its own oveload=20
> > control mechanism and that each will independently=20
> determine when the=20
> > machine is overloaded?
> >
> > Mike
> >
> >
> > > -----Original Message-----
> > > From: Janet P Gunn [mailto:jgunn6@csc.com]
> > > Sent: Wednesday, January 03, 2007 8:53 AM
> > > To: Darshan Bildikar
> > > Cc: 'Volker Hilt'; 'sipping'
> > > Subject: Re: [Sipping] RE: Queries and commentson=20
> > > draft-hilt-sipping-overload-00.txt
> > >
> > >
> > >
> > > I think it is important to focus on overload of the ability to=20
> > > PROCESS SIP messages.  In particular, the focus should be on the=20
> > > situation where, if the SIP messages keep coming, the box=20
> will crash=20
> > > (usually preceded by unproductive thrashing).
> > >
> > > As such, the mechanism and messaging must be as "lightweight"
> > > as possible, in order to avoid making the machine=20
> congestion worse.
> > >
> > > The other kinds of resource specific overload mechanisms=20
> you discuss=20
> > > sound very useful.  But I don't think it is a good idea to try to=20
> > > overload them on THIS effort.
> > >
> > > Janet
> > >
> > >
>=20

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



From sipping-bounces@ietf.org Wed Jan 03 14:03:54 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2BOn-0001l3-Hw; Wed, 03 Jan 2007 14:03:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2BOl-0001kx-MM
	for sipping@ietf.org; Wed, 03 Jan 2007 14:03:39 -0500
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2BOj-0002uy-7X
	for sipping@ietf.org; Wed, 03 Jan 2007 14:03:39 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	l03Iu3115777; Wed, 3 Jan 2007 13:56:03 -0500 (EST)
Received: from [47.130.25.95] ([47.130.25.95] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 3 Jan 2007 14:03:55 -0500
Message-ID: <459BFDF5.4030007@nortel.com>
Date: Wed, 03 Jan 2007 14:03:17 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Janet P Gunn <jgunn6@csc.com>
Subject: Re: [Sipping] RE: Queries
	and	commentson	draft-hilt-sipping-overload-00.txt
References: <OF81F7E74F.0F0771D4-ON85257258.005D44BF-85257258.005E4EA5@csc.com>
In-Reply-To: <OF81F7E74F.0F0771D4-ON85257258.005D44BF-85257258.005E4EA5@csc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Jan 2007 19:03:55.0328 (UTC)
	FILETIME=[EA5B6C00:01C72F69]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: Volker Hilt <volkerh@bell-labs.com>, sipping <sipping@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

One of the proposals going around TISPAN was for a separate overload 
control protocol, for exactly the reason you point out: that you may 
need to control for overload from multiple application protocols on the 
same box. Another argument, applying even to single-protocol boxes, was 
that this would be more effective than defining new overload 
capabilities in a multiplicity of protocols.

I'm neutral on this argument, but if it seems to make sense, it puts the 
topic outside the scope of SIPPING.

Janet P Gunn wrote:
> Mike,
> 
> Good point..
> 
> Obviously everything is simplest if we are only dealing with one protocol.
> 
> If the box is serving multiple protocols, I would assume that
> detecting/identifying overload applies to the machine, not the protocol
> (e.g , cpu usage, internal queue length, time in  queue).
> 
> SIP can, of course, only address signalling the overload to other boxes
> that "talk" SIP.  Obviously, if that "other box" is sending both SIP
> messages and other-protocol-messages to the overloaded box, it would be
> nice/ sensible if the "other box" throttled all messages (SIP or otherwise)
> to the overloaded box.  But I don't think SIP can specify that.
> 
> If the overloaded box talks to some boxes that "talk" SIP, and some that
> don't, there is always the possibility that the SIP boxes will cut back,
> and the others won't, leaving the overloaded box STILL overloaded, but with
> non-SIP work.  Obviously this wouldn't be a good idea.  I don't think we
> can necessarily assume it away, but I don't think we can "solve" it with a
> SIP document.
> 
> Janet
> 
> 
> 
> "Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on 01/03/2007
> 10:42:35 AM:
> 
>> Janet and others,
>>
>> Just out of curiosity, do you assume that SIP is the ONLY protocol
>> operating on a particular platform?
>>
>> If not, then do you assume that each protocol has its own oveload
>> control mechanism and that each will independently determine when the
>> machine is overloaded?
>>
>> Mike
>>
>>
>>> -----Original Message-----
>>> From: Janet P Gunn [mailto:jgunn6@csc.com]
>>> Sent: Wednesday, January 03, 2007 8:53 AM
>>> To: Darshan Bildikar
>>> Cc: 'Volker Hilt'; 'sipping'
>>> Subject: Re: [Sipping] RE: Queries and commentson
>>> draft-hilt-sipping-overload-00.txt
>>>
>>>
>>>
>>> I think it is important to focus on overload of the ability
>>> to PROCESS SIP messages.  In particular, the focus should be
>>> on the situation where, if the SIP messages keep coming, the
>>> box will crash (usually preceded by unproductive thrashing).
>>>
>>> As such, the mechanism and messaging must be as "lightweight"
>>> as possible, in order to avoid making the machine congestion worse.
>>>
>>> The other kinds of resource specific overload mechanisms you
>>> discuss sound very useful.  But I don't think it is a good
>>> idea to try to overload them on THIS effort.
>>>
>>> Janet
>>>
>>>
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org Wed Jan 03 16:08:56 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2DLq-0001mb-Sz; Wed, 03 Jan 2007 16:08:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2DLp-0001mE-0c
	for sipping@ietf.org; Wed, 03 Jan 2007 16:08:45 -0500
Received: from hoemail2.lucent.com ([192.11.226.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2DLn-0008Us-Md
	for sipping@ietf.org; Wed, 03 Jan 2007 16:08:44 -0500
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail2.lucent.com (8.13.8/IER-o) with ESMTP id l03L8aqA013989;
	Wed, 3 Jan 2007 15:08:36 -0600 (CST)
Received: from [135.180.240.247] (volker-hopc2.dnrc.bell-labs.com
	[135.180.240.247])
	by homail.ho.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l03L8aW22155; Wed, 3 Jan 2007 16:08:36 -0500 (EST)
Message-ID: <459C1B54.3070100@bell-labs.com>
Date: Wed, 03 Jan 2007 16:08:36 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortel.com>
Subject: Re: [Sipping] RE: Queries and commentson
	draft-hilt-sipping-overload-00.txt
References: <OF81F7E74F.0F0771D4-ON85257258.005D44BF-85257258.005E4EA5@csc.com>
	<459BFDF5.4030007@nortel.com>
In-Reply-To: <459BFDF5.4030007@nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 192.11.226.42
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: sipping <sipping@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Tom-PT Taylor wrote:
> One of the proposals going around TISPAN was for a separate overload 
> control protocol, for exactly the reason you point out: that you may 
> need to control for overload from multiple application protocols on the 
> same box. Another argument, applying even to single-protocol boxes, was 
> that this would be more effective than defining new overload 
> capabilities in a multiplicity of protocols.
> 
A downside is that all SIP boxes need to implement the protocol stack of 
the stand-alone protocol for this to work well. Also, the stand-alone 
protocol stack would have to have hooks into all other protocols to 
actually facilitate the throttling (what if it doesn't?). E.g. it would 
have to have a way to instruct the SIP protocol stack on the upstream 
entity to reject a certain fraction/rate of messages. During operation, 
the protocol would have to exchange some kind of messages (maybe similar 
to SUB/NOT) which again contribute to messaging traffic. A mechanism 
directly built into SIP does not have these problems and seems to be 
simpler and easier to deploy.

Volker



> Janet P Gunn wrote:
>> Mike,
>>
>> Good point..
>>
>> Obviously everything is simplest if we are only dealing with one 
>> protocol.
>>
>> If the box is serving multiple protocols, I would assume that
>> detecting/identifying overload applies to the machine, not the protocol
>> (e.g , cpu usage, internal queue length, time in  queue).
>>
>> SIP can, of course, only address signalling the overload to other boxes
>> that "talk" SIP.  Obviously, if that "other box" is sending both SIP
>> messages and other-protocol-messages to the overloaded box, it would be
>> nice/ sensible if the "other box" throttled all messages (SIP or 
>> otherwise)
>> to the overloaded box.  But I don't think SIP can specify that.
>>
>> If the overloaded box talks to some boxes that "talk" SIP, and some that
>> don't, there is always the possibility that the SIP boxes will cut back,
>> and the others won't, leaving the overloaded box STILL overloaded, but 
>> with
>> non-SIP work.  Obviously this wouldn't be a good idea.  I don't think we
>> can necessarily assume it away, but I don't think we can "solve" it 
>> with a
>> SIP document.
>>
>> Janet
>>
>>
>>
>> "Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on 01/03/2007
>> 10:42:35 AM:
>>
>>> Janet and others,
>>>
>>> Just out of curiosity, do you assume that SIP is the ONLY protocol
>>> operating on a particular platform?
>>>
>>> If not, then do you assume that each protocol has its own oveload
>>> control mechanism and that each will independently determine when the
>>> machine is overloaded?
>>>
>>> Mike
>>>
>>>
>>>> -----Original Message-----
>>>> From: Janet P Gunn [mailto:jgunn6@csc.com]
>>>> Sent: Wednesday, January 03, 2007 8:53 AM
>>>> To: Darshan Bildikar
>>>> Cc: 'Volker Hilt'; 'sipping'
>>>> Subject: Re: [Sipping] RE: Queries and commentson
>>>> draft-hilt-sipping-overload-00.txt
>>>>
>>>>
>>>>
>>>> I think it is important to focus on overload of the ability
>>>> to PROCESS SIP messages.  In particular, the focus should be
>>>> on the situation where, if the SIP messages keep coming, the
>>>> box will crash (usually preceded by unproductive thrashing).
>>>>
>>>> As such, the mechanism and messaging must be as "lightweight"
>>>> as possible, in order to avoid making the machine congestion worse.
>>>>
>>>> The other kinds of resource specific overload mechanisms you
>>>> discuss sound very useful.  But I don't think it is a good
>>>> idea to try to overload them on THIS effort.
>>>>
>>>> Janet
>>>>
>>>>
>>
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the 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 sipping-bounces@ietf.org Wed Jan 03 16:18:59 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2DVW-0004Rg-2L; Wed, 03 Jan 2007 16:18:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2DVU-0004Qx-A5
	for sipping@ietf.org; Wed, 03 Jan 2007 16:18:44 -0500
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2DVK-0001hp-AO
	for sipping@ietf.org; Wed, 03 Jan 2007 16:18:44 -0500
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l03LIRfi024980; 
	Wed, 3 Jan 2007 15:18:27 -0600 (CST)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90])
	by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l03LIHu03510; Wed, 3 Jan 2007 15:18:22 -0600 (CST)
Message-ID: <459C1D99.2010504@alcatel-lucent.com>
Date: Wed, 03 Jan 2007 15:18:17 -0600
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>, Jonathan Rosenberg <jdrosen@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60fbf3dbcaca652b6d10036f0630412
Cc: SIPPING LIST <sipping@ietf.org>, Mary Barnes <mary.barnes@nortel.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: [Sipping] WGLC review of draft-ietf-sipping-spam-03
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Draft: draft-ietf-sipping-spam-03
Reviewer:  Vijay K. Gurbani <vkg@alcatel-lucent.com>
Review Date: Jan 3, 2007
Review Deadline:  Dec 31, 2006
Status: WGLC

Review Summary:
This draft is on the right track but has open issues, described in
the review.

Draft Summary: This is an excellent survey on spam in general, and
SIP-related spam in particular.  It ties in nicely the various
extensions to SIP (consent, identity, presence, etc.) to solve a
particular problem, namely preventing SIP spam.  In my opinion, the
sooner it gets to RFC status, the better it would be for the SIP
user community.

Issues needing discussion listed below, followed by some nits.

Issues needing discussion:

* S2.1, paragraph "This number (9 deliveries ... will be more
   effective."  I am not sure how you are characterizing the first
   sentence in that paragraph.  Certainly, a SMTP server (probably the
   closest equivalent to a SIP proxy) would be able to, and probably
   already does deliver 9 or more messages a second.  For some existing
   analysis on SMTP server performance, see [1,2], which describes
   systems that can handle anywhere from 52 to 5000 messages/second.

   If however, the 9 deliveries per second refers to the MUA (closest to
   a SIP UA), then I would agree that it is hard to pin down how many
   messages per second an individual receives.  For instance, sending a
   message to an enterprise reflector usually always elicits "On
   vacation" responses, and many times such responses are in numbers
   greater than 9 messages arriving per second.

* S2.2, s/which only allow spam to be/which only allow IM to be
   I think you meant that the *IM* will be delivered only if the sender
   is on a white list, not that the *spam* will be delivered only if the
   sender is on a white list.

* In S3.1, the third paragraph is redundant; it restates what the
   first sentence of the second paragraph alread said.  I would suggest
   taking it out completely, and modifying the first sentence of the
   second paragraph as follows:

   OLD:
   Unfortunately, this type of spam filtering is almost completely
   useless for call spam.

   NEW:
   Unfortunately, this type of spam filtering, while successful for email
   spam, is completely useless for call spam.

* In S3.1, to be complete, you should also add a blurb on whether or not
   content filtering helps for presence spam (since you mention that it
   does not help for call spam and may help for IM spam.)
   I would suggest the addition of the following paragraph at the end
   of the section:

     Content filtering will not help for presence spam because by
     definition, a request subscribing for the presence of a user will
     be devoid of any content.

* In S3.2, you may want to change spammer@domain.com and spammer.com.
   domain.com is registered to someone in Vancouver, WA, and
   spammer.com is a registered to someone in Houston, TX.
   Suggest using spammer@spam.example.com for spammer@domain.com
   and spam.example.com for spammer.com.

   spammers.com also appears in S5.

* In S3.3, it is worth discussing that in addition to Turing tests,
   the "introduction problem" can also be solved by tagged addresses,
   of which the Tagged Message Delivery Agent (TDMA,
   http://tmda.net/index.html) is a good example.  Using tagged
   addresses, you can limit an email address by temporal interval
   (i.e., valid only for 5 days) or sender-specific addresses.  I
   do think they are worth discussing (for email, they work well;
   they have limited utility in call spam, but could be used for
   IM spam and presence spam.)  I will leave it upto you to determine
   whether a new sub-section should be added in Section 3 to discuss
   tagged addresses, or you can discuss them as part of S3.7 "Limited
   Use Addresses".

* In S3.4, first complete paragraph on page 11: it is stated in the
   last sentence that "Fortunately, traditional content-based filtering
   can be applied to this type of information."  I presume the phrase
   "this type of information" refers to the SIP address
   "sip:please-buy-my-product-at-this-website@spam.example.com".  If
   so, then this is not content, but a header; more specifically,
   a From header.  Would white- or black-lists not be a better match
   then content-based filtering in this case?

* In S3.5, I don't think I agree with your assertion that "Reputation
   systems have not enjoyed much success outside of the instant messaging
   space." (third paragraph in that section.)  Certainly, in the business
   space occupied by eBay and Amazon, reputation is very intrinsic and
   an important contributor to the smooth functioning of the enterprise.
   Since eBay and Amazon have authority over their namespace, they can
   warn other users of identity mining (eBay, for instance, displays a
   special icon if you have recently changed your identity.)  Likewise,
   anyone who has bought a used book or CD through Amazon first scans
   the reputation of the seller before pressing the "1-click" button.

   My suggestion would be to begin the third paragraph using text
   suggested below:

   OLD:
   Reputation systems have not enjoyed much success outside of the
   instant messaging space.  This is in part because few other
   communications systems admit of the same degree of centralization and
   monolithic control.

   NEW:
   Reputation systems have been successful in communication systems
   where centralization of resources (user identities, authentication,
   etc.) and monolithic control dominate.

* S3.8, page 15, it is stated at the top of the page that "Automata
   cannot easily perform the image recognition needed to extract the
   word or number sequence, but a human user usually can."  Note that
   there exist programs (called CAPTCHAs) that can acheive with 93%
   correct recognition rate of visual puzzles (see
   http://www.captcha.net, and [3]).

* S3.8, of the two problems with the voice Turing tests mentioned
   towards the end of the section, the first one appears to *not* be
   a problem.  Yes, voice Turing test would need to be language
   specific, but as you note, SIP already has provisions to help here.
   Even if it did not, the experience is no different than what happens
   now when A calls B, and is instead redirected to B's voicemail
   which prompts him to enter "1" for A, "2" for A's wife and so on.
   If A is in the US, and B is in Lisbon, the instructions are rendered
   in Portugese.  A swears a bit, and hangs up, vowing to call B
   at a later time.

   The second problem -- cheap labor -- is indeed a problem.

* In S3.9, there is no mention of Cullen's hashcash draft?  Is that
   effort dead?

* In S3.9, one disadvantage of Payments At Risk scheme is the
   discrepancy of currency value between the sender and recipient.
   If the sender is in a third world country (albeit being financed by a
   spamming corporation in a first world country) and the receiver is
   in a first world country, then the sender really does not care about
   not getting his money refunded.  The benefactor funding the
   sender is able to use the currency valuation of his host country
   to conduct spam.  The sender deposits the payment in his local
   currency, the exchange value of which is much lower when compared to
   that of his benefactor's country.

* Isn't S3.13 similar to VoIP peering?  If domains establish a
   peering relationship, then they could optionally add spamming fines
   to the service level agreement.  In fact, the Circle of Trust
   idea of S3.12 is a simpler case of what is described in S3.13.
   Suggestion: remove S3.12, or subsume it in S3.13.

* The last statement of S3.13 is a strongly worded opinion of the
   authors.  While in and of itself, this is perfectly okay, I feel
   that standards documents ought to be a bit more impartial (okay,
   beat me here if you want.)  Instead, I would suggest that the last
   two sentences of S3.13 be reworded as follows to convey the authors
   distate in an objective manner:

   OLD:
   However, it puts back into SIP much of the complexity and monopolistic
   structures that SIP promised to eliminate.  As such, it is a solution
   that the authors find distasteful and contrary to the SIP design
   and architecture.

   NEW:
   However, centralized architectures as these are deliberately eschewed
   because they put back into SIP much of the complexity and mono-
   polistic structures that the protocol promises to eliminate.

* In S6, I would suggest that the three core recommendations be given
   labels; something like:

     1.  Enforce SIP Identity
     ...

     2.  Leverage White Lists
     ...

     3.  Provide a Solution for the Introduction Problem
     ...

   Implicitly, the last paragraph contains the fourth recommendation:

     4.  Do Not Ignore Spam
     ...

* There is no IANA Consideration section (I realize that this is an
   Informational track RFC, so an IANA Consideration section may not
   be required.  I do not remember if the IESG requires such a
   section in all drafts, even Informationals.)

References
[1] Wyman Miles, "A High-Availability High-Performance E-Mail Cluster,"
  Proceedings of the 30th annual ACM SIGUCCS conference on User services,
  pp. 84-88, November 20-23, 2002.
[2] Yasushi Saito, Brian N. Bershad, and Henry M. Levy, "Manageability,
  availability, and performance in porcupine: a highly scalable, cluster-
  based mail service," ACM Transactions on Computer Systems (TOCS), pp.
  298-332, 18(3), August 2000.
[3] Luis von Ahn, Manuel Blum, and John Langford, "Telling Humans and
  Computers Apart Automatically," Communications of the ACM, pp. 57-60,
  47(2), February 2004.

Nits
* S2.1, page 6,
   s/addresses, in that, in concert/addresses, such that in concert/

* S3.4, page 11,
   s/but to make the permission is extremely limited/but to ensure
   that the permission is extremely limited

* S3.5, first paragraph, second sentence:
   s/and they attempt/and A attempts to/

* S3.5, first paragraph, third sentence:
   s/from A, a reputation score/from A, and along with the consent, a
   reputation score/

* S3.5, regarding "reputation mafias" in the fourth paragraph, I am
   curious: is there any published reference?  It seems that such a
   mafia would neccessarily be a large, distributed, self-organizing
   system that shares a common goal, although the victims change over
   time.

* S3.8, last paragraph:
   s/turing tests/Turing tests

* In S3.9, I am not sure what the last sentence of the section
   is supposed to convey.  Any research is subject to patent and IP
   constraints, I suppose; SIP spam is no exception.  Best to simply take
   that sentence out.

* S3.10, first paragraph:
   s/A sends to user B/A sends email to user B/

* S3.10, third paragraph:
   s/for small transactions, for transaction as small as one cent./
   for small transactions, as small as one cent.

* S3.11, second sentence of second parargraph: I am not sure I
   can parse what it says.  Maybe you would consider, instead,
   to simply say:

       Whether they are, or are not effective remains to be seen.

* S 3.11, last sentence of the section: suggest rewrite as follows:

   OLD:
   For example, Habeas <http://www.habeas.com> inserts material in the
   header that, if a spammer inserted it without an appropriate license,
   allegedly causes the spammer to be violating US copyright and
   trademark laws, possibly reciprocal laws, and similar laws in many
   countries.

   NEW:
   For example, Habeas <http://www.habeas.com> inserts material in the
   header that, if it was inserted by a spammer without an appropriate
   license, would allegedly causes the spammer to violate US copyright
   and trademark laws, possibly reciprocal laws, and similar laws in
   many countries.

* S4.1, expand MTA and MUA on their first use.

* Reference 24, the terminating comma should appear before Third
   Annual Workshop...

Thank you.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs

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



From sipping-bounces@ietf.org Wed Jan 03 18:43:42 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2Fkp-0007ny-7N; Wed, 03 Jan 2007 18:42:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2Fko-0007ns-GE
	for sipping@ietf.org; Wed, 03 Jan 2007 18:42:42 -0500
Received: from exprod6og51.obsmtp.com ([64.18.1.183])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H2Fkl-00028z-SE
	for sipping@ietf.org; Wed, 03 Jan 2007 18:42:42 -0500
Received: from source ([192.150.11.134]) by exprod6ob51.postini.com
	([64.18.5.12]) with SMTP; Wed, 03 Jan 2007 15:42:35 PST
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l03NdMvV016389; Wed, 3 Jan 2007 15:39:22 -0800 (PST)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l03Ng3PR014751; Wed, 3 Jan 2007 15:42:25 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 3 Jan 2007 15:42:24 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: Queries and
	commentsondraft-hilt-sipping-overload-00.txt
Date: Wed, 3 Jan 2007 15:42:11 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D22141491@namail5.corp.adobe.com>
In-Reply-To: <459C1B54.3070100@bell-labs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] RE: Queries and
	commentsondraft-hilt-sipping-overload-00.txt
Thread-Index: Accve3DNtEEYyv7nRxS4HM/0C9IZxwAFOtNw
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Volker Hilt" <volkerh@bell-labs.com>, "Tom-PT Taylor" <taylor@nortel.com>
X-OriginalArrivalTime: 03 Jan 2007 23:42:24.0884 (UTC)
	FILETIME=[D2075340:01C72F90]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: sipping <sipping@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Volker is 100% correct and I would only like to add that a little more
bandwidth (think of all the multimedia and animated web commercials
flowing) and modern processors are far cheaper and more effective in
avoiding overload in the first place.

Sanity check: VoIP traffic is so small, that it is hard to detect on the
net :-)

Thanks, Henry

-----Original Message-----
From: Volker Hilt [mailto:volkerh@bell-labs.com]=20
Sent: Wednesday, January 03, 2007 3:09 PM
To: Tom-PT Taylor
Cc: sipping; Michael Hammer (mhammer)
Subject: Re: [Sipping] RE: Queries and
commentsondraft-hilt-sipping-overload-00.txt

Tom-PT Taylor wrote:
> One of the proposals going around TISPAN was for a separate overload=20
> control protocol, for exactly the reason you point out: that you may=20
> need to control for overload from multiple application protocols on
the=20
> same box. Another argument, applying even to single-protocol boxes,
was=20
> that this would be more effective than defining new overload=20
> capabilities in a multiplicity of protocols.
>=20
A downside is that all SIP boxes need to implement the protocol stack of

the stand-alone protocol for this to work well. Also, the stand-alone=20
protocol stack would have to have hooks into all other protocols to=20
actually facilitate the throttling (what if it doesn't?). E.g. it would=20
have to have a way to instruct the SIP protocol stack on the upstream=20
entity to reject a certain fraction/rate of messages. During operation,=20
the protocol would have to exchange some kind of messages (maybe similar

to SUB/NOT) which again contribute to messaging traffic. A mechanism=20
directly built into SIP does not have these problems and seems to be=20
simpler and easier to deploy.

Volker



> Janet P Gunn wrote:
>> Mike,
>>
>> Good point..
>>
>> Obviously everything is simplest if we are only dealing with one=20
>> protocol.
>>
>> If the box is serving multiple protocols, I would assume that
>> detecting/identifying overload applies to the machine, not the
protocol
>> (e.g , cpu usage, internal queue length, time in  queue).
>>
>> SIP can, of course, only address signalling the overload to other
boxes
>> that "talk" SIP.  Obviously, if that "other box" is sending both SIP
>> messages and other-protocol-messages to the overloaded box, it would
be
>> nice/ sensible if the "other box" throttled all messages (SIP or=20
>> otherwise)
>> to the overloaded box.  But I don't think SIP can specify that.
>>
>> If the overloaded box talks to some boxes that "talk" SIP, and some
that
>> don't, there is always the possibility that the SIP boxes will cut
back,
>> and the others won't, leaving the overloaded box STILL overloaded,
but=20
>> with
>> non-SIP work.  Obviously this wouldn't be a good idea.  I don't think
we
>> can necessarily assume it away, but I don't think we can "solve" it=20
>> with a
>> SIP document.
>>
>> Janet
>>
>>
>>
>> "Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on 01/03/2007
>> 10:42:35 AM:
>>
>>> Janet and others,
>>>
>>> Just out of curiosity, do you assume that SIP is the ONLY protocol
>>> operating on a particular platform?
>>>
>>> If not, then do you assume that each protocol has its own oveload
>>> control mechanism and that each will independently determine when
the
>>> machine is overloaded?
>>>
>>> Mike
>>>
>>>
>>>> -----Original Message-----
>>>> From: Janet P Gunn [mailto:jgunn6@csc.com]
>>>> Sent: Wednesday, January 03, 2007 8:53 AM
>>>> To: Darshan Bildikar
>>>> Cc: 'Volker Hilt'; 'sipping'
>>>> Subject: Re: [Sipping] RE: Queries and commentson
>>>> draft-hilt-sipping-overload-00.txt
>>>>
>>>>
>>>>
>>>> I think it is important to focus on overload of the ability
>>>> to PROCESS SIP messages.  In particular, the focus should be
>>>> on the situation where, if the SIP messages keep coming, the
>>>> box will crash (usually preceded by unproductive thrashing).
>>>>
>>>> As such, the mechanism and messaging must be as "lightweight"
>>>> as possible, in order to avoid making the machine congestion worse.
>>>>
>>>> The other kinds of resource specific overload mechanisms you
>>>> discuss sound very useful.  But I don't think it is a good
>>>> idea to try to overload them on THIS effort.
>>>>
>>>> Janet
>>>>
>>>>
>>
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the 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 sipping-bounces@ietf.org Wed Jan 03 23:33:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2KGs-00077t-5Y; Wed, 03 Jan 2007 23:32:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2KGq-00077o-4O
	for sipping@ietf.org; Wed, 03 Jan 2007 23:32:04 -0500
Received: from corp2.ipunity.com ([65.106.79.133] helo=exchangevm.ipunity.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2KGp-0000ko-J8
	for sipping@ietf.org; Wed, 03 Jan 2007 23:32:04 -0500
Received: from BLRPC6 ([10.253.253.150]) by exchangevm.ipunity.com with
	Microsoft SMTPSVC(5.0.2195.6713); Wed, 3 Jan 2007 20:26:54 -0800
From: "Darshan Bildikar" <dbildikar@ipunity.com>
To: "'Volker Hilt'" <volkerh@bell-labs.com>
Date: Thu, 4 Jan 2007 10:01:55 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AccvU3hG3YXPFfxzTK2ceg9NSmT7ygAYoYJg
In-Reply-To: <459BD720.4050500@bell-labs.com>
Message-ID: <EXCHANGEVMGbQtF8tBY00001d3a@exchangevm.ipunity.com>
X-OriginalArrivalTime: 04 Jan 2007 04:26:54.0841 (UTC)
	FILETIME=[90840E90:01C72FB8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: 'sipping' <sipping@ietf.org>
Subject: [Sipping] RE: Queries and comments on
	draft-hilt-sipping-overload-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

My last response on this!

Marked by <Darshan>

-----Original Message-----
From: Volker Hilt [mailto:volkerh@bell-labs.com] 
Sent: Wednesday, January 03, 2007 9:48 PM
To: Darshan Bildikar
Cc: 'sipping'
Subject: Re: Queries and comments on draft-hilt-sipping-overload-00.txt

> Darshan Bildikar wrote:
>> 2) It is envisioned that overload information is exchanged through a
> header
>> in response messages. Why not a more EXPLICIT mechanism like
>> SUBSCRIBE/NOTIFY? Define an event package for overload and define a body
>> that can be used to indicate a rich set of overload parameters to the
>> upstream entity. 
>>
> Using SUBSCRIBE/NOTIFY would require a proxy to subscribe to a 
> downstream neighbor when (or before) sending requests to this neighbor 
> to inquire the current load status. This would cause some messaging 
> overhead, in particular, for proxies that talk to many downstream 
> neighbors. The nice property of using a response header is that it is 
> very light-weight and it automatically provides feedback from the 
> downstream entities a proxy is currently talking to.
> 
> <Darshan 1> Say a downstream entity has indicated that it is loaded at
100%.
> This would result in the upstream proxy NOT forwarding it ANY requests.
How
> does the proxy determine when to send the next request then? It would
never
> know EXACTLY when the downstream element becomes available. A sub/not
> mechanism allows the downstream element to indicate to an upstream
element,
> load status at discrete points of time instead of waiting for a request
> which might never come!
> 
Usually a proxy will not entirely stop sending messages to a downstream 
neighbor. Instead, overload control should slowly regulate the request 
rate to a lower level that is acceptable to the downstream proxy. So 
even in an overload situation, the upstream proxy would still send some 
requests and therefore receive responses that contain the load status. 
Even in very extreme overload where a proxy entirely stops to forward 
requests, it can still occasionally forward a request to probe the 
current load status.

<Darshan> With all due respect, "some requests" and "occasionally" sound
very ambiguous. This should probably be better defined in the draft.
(Recommended timers etc)

> Also, I don't agree that this would cause a messaging overhead. It's just
> one more SIP dialog per downstream element. Even with your approach an
> upstream element still needs to maintain some kind of "STATE" about the
load
> of each downstream element. We only avoid the SIP messaging.
> 
I think the messaging overhead is key here. Avoiding SIP messaging is 
important for a mechanism that deals with messaging overload. SUB/NOT 
also requires both parties to maintain dialog state but that might not 
be that significant (it still could pose a problem if memory is the 
bottleneck on the downstream entity). I agree that even with a header, 
load state needs to be kept in the upstream proxy (the draft talks about 
this in detail).

<Darshan> I agree that the header approach might seem simpler to implement.
However, in my mind a SUB/NOT mechanism seems much more straightforward and
explicit. We agree to disagree here. 

>> 3) The draft talks about overload w.r.t certain resources. If a sub/not
>> mechanism was used, it would allow overload control to be more "fine
>> grained". For example, the SUBSCRIBE message would indicate what resource
>> the requester is wants the overload throttling and statistics for. 
>>
> Overload control is used when a SIP entity is unable to handle all 
> incoming messages because it ran out of resources it needs for 
> processing messages. To an upstream neighbor, it really does not matter 
> which resource on the downstream element is the bottleneck. What matters 
> is that the downstream element can't process all messages and, thus, the 
> load has to be reduced. As long as the downstream element has enough 
> capacity to return a meaningful response (e.g. 488 if a PSTN gateway 
> runs out of trunk lines) it should do so.
> 
> <Darshan 2> While I do agree with you, I think it's a useful feature to be
> able to throttle specific traffic. There is definitely a use case for it.
> Why should I waste time on generating 488 responses when I KNOW that I
wont
> be able to process certain requests beyond a limit. If I am able to
indicate
> load to an upstream entity for a specific resource, I would be able to run
> my system much more efficiently. Ideally I SHOULD be able to throttle my
> traffic in order to spend resources processing request I KNOW I can handle
> and not reject. 
> 
I'm not yet fully convinced that the benefits of rejecting a message one 
hop earlier for the cases you describe really justify the complexity 
needed for this. What would be achieved is that a request is forwarded 
one hop less to a device that could still produce a meaningful response.

<Darshan> Sorry if I don't seem to get the big picture. I'm thinking more
from the point of view of my box that runs multiple applications and
protocol stacks. Also when I have hosted applications I might have well
defined SLA's with my customers. For example, I promise customer 1 that run
CRBT at 20 CPS (calls per second) and customer 2 to run conferencing at 5
CPS. I need a mechanism that ENSURES that I don't get requests at > 20 CPS
for my app. And I don't want to spend computing resources on rejecting
requests that I cannot process. 

But apart from this, I think we should try to keep overload control as 
simple as possible and make it effective in dealing with signaling overload.


<Darshan> Do look at these requirements in
"draft-rosenberg-sipping-overload-reqs". They state:-

"The specification for the overload mechanism should give guidance on which
message types might be desirable to process over others during times of
overload, based on SIP-specific considerations.  For example, it may be more
beneficial to process a SUBSCRIBE refresh with Expires of zero than a
SUBSCRIBE refresh with a non-zero expiration, since the former reduces the
overall amount of load on the element, or to process re-INVITEs over new
INVITEs."

"The overload mechanism should be unambiguous about whether a load
indication applies to a specific IP address, host, or URI, so that an
upstream element can determine the load of the entity to which a request is
to be sent."

These two requirements can clearly not be satisfied with your approach. A
SUB/NOT mechanism is probably what is needed. You can take a call on how you
want to achieve this. 

>> Two things that I haven't really thought through.
>>
>> 1) Throttling based on codecs and media lines would be useful. For
> example,
>> I can support audio right now, but NOT video. 
>> 2) Is it possible to make this mechanism more generic? It is after all a
>> throttling mechanism and could be applied to domains OTHER than overload
>> control. For example, Tele voting applications where an application
server
>> indicates filtering to a switch i.e. "Notify every 100'th INVITE to me"
>>
> I don't think that the scope of overload control should be extended into 
> these domains. Overload control specifically helps devices to deal with 
> signaling overload. If a device is still able to return a SIP response 
> it is not in signaling overload and should create a response with the 
> appropriate response code.
> 
> <Darshan 3> As I said I haven't really thought this through. My only point
> being that we should try and "generify" wherever possible. If someone
> decides to implement SIP mechanism for tele voting/throttling
applications,
> they would find that what they want to do is already ALMOST done in
> overload. 
> 
The tele voting/throttling is interesting since it requires to set up 
throttles for a specific target at a specific point in time. So it is 
effectively an overload control that is known a priori.

I'm not sure how this relates to the reactive overload control mechanism 
that we are talking about here. The load feedback would not be needed 
for a priory throttles. However, the procedures to throttle may be 
similar. My gut feeling is that it is a separate mechanism that needs to 
be able to work along with overload control.

<Darshan> Fair enough. I appreciate the fact that overload needs to be as
simple as possible. I guess we cross this bridge when we come to it!

Thanks,

Volker



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



From sipping-bounces@ietf.org Thu Jan 04 12:00:27 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2VwG-0002Ax-U8; Thu, 04 Jan 2007 11:59:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2VwF-0002As-O2
	for sipping@ietf.org; Thu, 04 Jan 2007 11:59:35 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2VwE-0006dn-Aw
	for sipping@ietf.org; Thu, 04 Jan 2007 11:59:35 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 04 Jan 2007 08:59:34 -0800
X-IronPort-AV: i="4.12,239,1165219200"; 
	d="scan'208"; a="50000624:sNHT57365644"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l04GxYHm018541; 
	Thu, 4 Jan 2007 11:59:34 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l04GxX7f028754; 
	Thu, 4 Jan 2007 11:59:33 -0500 (EST)
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 4 Jan 2007 11:59:33 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: Queries and
	commentsondraft-hilt-sipping-overload-00.txt
Date: Thu, 4 Jan 2007 11:59:32 -0500
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E3026B679B@xmb-rtp-20b.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] RE: Queries and
	commentsondraft-hilt-sipping-overload-00.txt
Thread-Index: Accve3DNtEEYyv7nRxS4HM/0C9IZxwAFOtNwACQlLLA=
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Henry Sinnreich" <hsinnrei@adobe.com>,
	"Volker Hilt" <volkerh@bell-labs.com>, "Tom-PT Taylor" <taylor@nortel.com>
X-OriginalArrivalTime: 04 Jan 2007 16:59:33.0762 (UTC)
	FILETIME=[B5548E20:01C73021]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=6104; t=1167929974;
	x=1168793974; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mhammer@cisco.com;
	z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20RE=3A=20Queries=20and=20commentsondraft-h
	ilt-sipping-overload-00.txt |Sender:=20
	|To:=20=22Henry=20Sinnreich=22=20<hsinnrei@adobe.com>,
	=0A=20=20=20=20=20=
	20=20=20=22Volker=20Hilt=22=20<volkerh@bell-labs.com>,
	=0A=20=20=20=20=20=2
	0=20=20=22Tom-PT=20Taylor=22=20<taylor@nortel.com>;
	bh=EWz5qSqPAEvW/5oWRe9x1ZkbjKD1aUpuubBEGJa6ETY=;
	b=cY6bjUwmOtBuYkjsLotD4zxmc76jgCsYI5q5ss3ZUG20oTudvVnXjbwCqQwf8pkYfL8CCRi6
	U5zsUR0O6bGQjX5//pq++MlrDfy0oXsZ/FeeaoX8eEJJqR7LiWIBBsox;
Authentication-Results: rtp-dkim-2; header.From=mhammer@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Henry,

This has nothing to do with router congestion and everything to do with
overload of end host node supporting VoIP application, which is more
akin to an unintentional DDOS.

And yes, one can always throw more hosts at the problem, but
over-provisioning may not always be the most cost-effective use of
resources.

Hope that restores your sanity. :)

Mike


> -----Original Message-----
> From: Henry Sinnreich [mailto:hsinnrei@adobe.com]=20
> Sent: Wednesday, January 03, 2007 6:42 PM
> To: Volker Hilt; Tom-PT Taylor
> Cc: sipping; Michael Hammer (mhammer)
> Subject: RE: [Sipping] RE: Queries and=20
> commentsondraft-hilt-sipping-overload-00.txt
>=20
> Volker is 100% correct and I would only like to add that a=20
> little more bandwidth (think of all the multimedia and=20
> animated web commercials
> flowing) and modern processors are far cheaper and more=20
> effective in avoiding overload in the first place.
>=20
> Sanity check: VoIP traffic is so small, that it is hard to=20
> detect on the net :-)
>=20
> Thanks, Henry
>=20
> -----Original Message-----
> From: Volker Hilt [mailto:volkerh@bell-labs.com]
> Sent: Wednesday, January 03, 2007 3:09 PM
> To: Tom-PT Taylor
> Cc: sipping; Michael Hammer (mhammer)
> Subject: Re: [Sipping] RE: Queries and
> commentsondraft-hilt-sipping-overload-00.txt
>=20
> Tom-PT Taylor wrote:
> > One of the proposals going around TISPAN was for a separate=20
> overload=20
> > control protocol, for exactly the reason you point out:=20
> that you may=20
> > need to control for overload from multiple application protocols on
> the=20
> > same box. Another argument, applying even to single-protocol boxes,
> was=20
> > that this would be more effective than defining new overload=20
> > capabilities in a multiplicity of protocols.
> >=20
> A downside is that all SIP boxes need to implement the=20
> protocol stack of
>=20
> the stand-alone protocol for this to work well. Also, the=20
> stand-alone protocol stack would have to have hooks into all=20
> other protocols to actually facilitate the throttling (what=20
> if it doesn't?). E.g. it would have to have a way to instruct=20
> the SIP protocol stack on the upstream entity to reject a=20
> certain fraction/rate of messages. During operation, the=20
> protocol would have to exchange some kind of messages (maybe similar
>=20
> to SUB/NOT) which again contribute to messaging traffic. A=20
> mechanism directly built into SIP does not have these=20
> problems and seems to be simpler and easier to deploy.
>=20
> Volker
>=20
>=20
>=20
> > Janet P Gunn wrote:
> >> Mike,
> >>
> >> Good point..
> >>
> >> Obviously everything is simplest if we are only dealing with one=20
> >> protocol.
> >>
> >> If the box is serving multiple protocols, I would assume that=20
> >> detecting/identifying overload applies to the machine, not the
> protocol
> >> (e.g , cpu usage, internal queue length, time in  queue).
> >>
> >> SIP can, of course, only address signalling the overload to other
> boxes
> >> that "talk" SIP.  Obviously, if that "other box" is=20
> sending both SIP=20
> >> messages and other-protocol-messages to the overloaded=20
> box, it would
> be
> >> nice/ sensible if the "other box" throttled all messages (SIP or
> >> otherwise)
> >> to the overloaded box.  But I don't think SIP can specify that.
> >>
> >> If the overloaded box talks to some boxes that "talk" SIP, and some
> that
> >> don't, there is always the possibility that the SIP boxes will cut
> back,
> >> and the others won't, leaving the overloaded box STILL overloaded,
> but=20
> >> with
> >> non-SIP work.  Obviously this wouldn't be a good idea.  I=20
> don't think
> we
> >> can necessarily assume it away, but I don't think we can=20
> "solve" it=20
> >> with a SIP document.
> >>
> >> Janet
> >>
> >>
> >>
> >> "Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on=20
> 01/03/2007
> >> 10:42:35 AM:
> >>
> >>> Janet and others,
> >>>
> >>> Just out of curiosity, do you assume that SIP is the ONLY=20
> protocol=20
> >>> operating on a particular platform?
> >>>
> >>> If not, then do you assume that each protocol has its own oveload=20
> >>> control mechanism and that each will independently determine when
> the
> >>> machine is overloaded?
> >>>
> >>> Mike
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Janet P Gunn [mailto:jgunn6@csc.com]
> >>>> Sent: Wednesday, January 03, 2007 8:53 AM
> >>>> To: Darshan Bildikar
> >>>> Cc: 'Volker Hilt'; 'sipping'
> >>>> Subject: Re: [Sipping] RE: Queries and commentson=20
> >>>> draft-hilt-sipping-overload-00.txt
> >>>>
> >>>>
> >>>>
> >>>> I think it is important to focus on overload of the ability to=20
> >>>> PROCESS SIP messages.  In particular, the focus should be on the=20
> >>>> situation where, if the SIP messages keep coming, the box will=20
> >>>> crash (usually preceded by unproductive thrashing).
> >>>>
> >>>> As such, the mechanism and messaging must be as "lightweight"
> >>>> as possible, in order to avoid making the machine=20
> congestion worse.
> >>>>
> >>>> The other kinds of resource specific overload mechanisms you=20
> >>>> discuss sound very useful.  But I don't think it is a=20
> good idea to=20
> >>>> try to overload them on THIS effort.
> >>>>
> >>>> Janet
> >>>>
> >>>>
> >>
> >>
> >> _______________________________________________
> >> Sipping mailing list =20
> https://www1.ietf.org/mailman/listinfo/sipping
> >> This list is for NEW development of the application of SIP Use=20
> >> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> >> sip@ietf.org for new developments of core SIP
> >>
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP=20
> Use sip-implementors@cs.columbia.edu for questions on current=20
> sip Use sip@ietf.org for new developments of core SIP
>=20

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



From sipping-bounces@ietf.org Thu Jan 04 22:05:34 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2fNJ-0003Wx-47; Thu, 04 Jan 2007 22:04:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2fNH-0003Wa-5g
	for sipping@ietf.org; Thu, 04 Jan 2007 22:04:07 -0500
Received: from exprod6og54.obsmtp.com ([64.18.1.189])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H2fNG-00023x-IS
	for sipping@ietf.org; Thu, 04 Jan 2007 22:04:07 -0500
Received: from source ([192.150.20.142]) by exprod6ob54.postini.com
	([64.18.5.12]) with SMTP; Thu, 04 Jan 2007 19:03:32 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l0533dIY010467; Thu, 4 Jan 2007 19:03:44 -0800 (PST)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	l0533FeC029161; Thu, 4 Jan 2007 19:03:16 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 4 Jan 2007 19:03:15 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: Queries and
	commentsondraft-hilt-sipping-overload-00.txt
Date: Thu, 4 Jan 2007 19:03:13 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D221414A1@namail5.corp.adobe.com>
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E3026B679B@xmb-rtp-20b.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] RE: Queries and
	commentsondraft-hilt-sipping-overload-00.txt
Thread-Index: Accve3DNtEEYyv7nRxS4HM/0C9IZxwAFOtNwACQlLLAAFK7oIA==
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	"Volker Hilt" <volkerh@bell-labs.com>, "Tom-PT Taylor" <taylor@nortel.com>
X-OriginalArrivalTime: 05 Jan 2007 03:03:15.0957 (UTC)
	FILETIME=[0B70E250:01C73076]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Mike,

> overload of end host node supporting VoIP application

Maybe we pull out our laptops (end host node) at the IETF meeting and
you can show me how a VoIP application can overload it. Unless you have
an antique PC with collectors' value :-)

The same applies to SIP phones. DDOS is a security issue.

> over-provisioning may not always be the most cost-effective use of
> resources.

A comparison between the cost of over-provisioning and the cost of
complexity would indeed be very interesting for VoIP before plunging
into the SIP overload work.

> Hope that restores your sanity. :)

Not quite.

Maybe we have a misunderstanding and you refer to the endless collection
of SIP feature servers in VoIP networks, in which case I am in full
agreement. The correct alternative to this is to place the features in
the end host nodes (SIP UA) and use SIP as it is defined in RFC 3261:=20
A discovery and rendezvous protocol (with as little state in the proxy
as possible).

Let the flames come...

Henry

-----Original Message-----
From: Michael Hammer (mhammer) [mailto:mhammer@cisco.com]=20
Sent: Thursday, January 04, 2007 11:00 AM
To: Henry Sinnreich; Volker Hilt; Tom-PT Taylor
Cc: sipping
Subject: RE: [Sipping] RE: Queries and
commentsondraft-hilt-sipping-overload-00.txt

Henry,

This has nothing to do with router congestion and everything to do with
overload of end host node supporting VoIP application, which is more
akin to an unintentional DDOS.

And yes, one can always throw more hosts at the problem, but
over-provisioning may not always be the most cost-effective use of
resources.

Hope that restores your sanity. :)

Mike


> -----Original Message-----
> From: Henry Sinnreich [mailto:hsinnrei@adobe.com]=20
> Sent: Wednesday, January 03, 2007 6:42 PM
> To: Volker Hilt; Tom-PT Taylor
> Cc: sipping; Michael Hammer (mhammer)
> Subject: RE: [Sipping] RE: Queries and=20
> commentsondraft-hilt-sipping-overload-00.txt
>=20
> Volker is 100% correct and I would only like to add that a=20
> little more bandwidth (think of all the multimedia and=20
> animated web commercials
> flowing) and modern processors are far cheaper and more=20
> effective in avoiding overload in the first place.
>=20
> Sanity check: VoIP traffic is so small, that it is hard to=20
> detect on the net :-)
>=20
> Thanks, Henry
>=20
> -----Original Message-----
> From: Volker Hilt [mailto:volkerh@bell-labs.com]
> Sent: Wednesday, January 03, 2007 3:09 PM
> To: Tom-PT Taylor
> Cc: sipping; Michael Hammer (mhammer)
> Subject: Re: [Sipping] RE: Queries and
> commentsondraft-hilt-sipping-overload-00.txt
>=20
> Tom-PT Taylor wrote:
> > One of the proposals going around TISPAN was for a separate=20
> overload=20
> > control protocol, for exactly the reason you point out:=20
> that you may=20
> > need to control for overload from multiple application protocols on
> the=20
> > same box. Another argument, applying even to single-protocol boxes,
> was=20
> > that this would be more effective than defining new overload=20
> > capabilities in a multiplicity of protocols.
> >=20
> A downside is that all SIP boxes need to implement the=20
> protocol stack of
>=20
> the stand-alone protocol for this to work well. Also, the=20
> stand-alone protocol stack would have to have hooks into all=20
> other protocols to actually facilitate the throttling (what=20
> if it doesn't?). E.g. it would have to have a way to instruct=20
> the SIP protocol stack on the upstream entity to reject a=20
> certain fraction/rate of messages. During operation, the=20
> protocol would have to exchange some kind of messages (maybe similar
>=20
> to SUB/NOT) which again contribute to messaging traffic. A=20
> mechanism directly built into SIP does not have these=20
> problems and seems to be simpler and easier to deploy.
>=20
> Volker
>=20
>=20
>=20
> > Janet P Gunn wrote:
> >> Mike,
> >>
> >> Good point..
> >>
> >> Obviously everything is simplest if we are only dealing with one=20
> >> protocol.
> >>
> >> If the box is serving multiple protocols, I would assume that=20
> >> detecting/identifying overload applies to the machine, not the
> protocol
> >> (e.g , cpu usage, internal queue length, time in  queue).
> >>
> >> SIP can, of course, only address signalling the overload to other
> boxes
> >> that "talk" SIP.  Obviously, if that "other box" is=20
> sending both SIP=20
> >> messages and other-protocol-messages to the overloaded=20
> box, it would
> be
> >> nice/ sensible if the "other box" throttled all messages (SIP or
> >> otherwise)
> >> to the overloaded box.  But I don't think SIP can specify that.
> >>
> >> If the overloaded box talks to some boxes that "talk" SIP, and some
> that
> >> don't, there is always the possibility that the SIP boxes will cut
> back,
> >> and the others won't, leaving the overloaded box STILL overloaded,
> but=20
> >> with
> >> non-SIP work.  Obviously this wouldn't be a good idea.  I=20
> don't think
> we
> >> can necessarily assume it away, but I don't think we can=20
> "solve" it=20
> >> with a SIP document.
> >>
> >> Janet
> >>
> >>
> >>
> >> "Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on=20
> 01/03/2007
> >> 10:42:35 AM:
> >>
> >>> Janet and others,
> >>>
> >>> Just out of curiosity, do you assume that SIP is the ONLY=20
> protocol=20
> >>> operating on a particular platform?
> >>>
> >>> If not, then do you assume that each protocol has its own oveload=20
> >>> control mechanism and that each will independently determine when
> the
> >>> machine is overloaded?
> >>>
> >>> Mike
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Janet P Gunn [mailto:jgunn6@csc.com]
> >>>> Sent: Wednesday, January 03, 2007 8:53 AM
> >>>> To: Darshan Bildikar
> >>>> Cc: 'Volker Hilt'; 'sipping'
> >>>> Subject: Re: [Sipping] RE: Queries and commentson=20
> >>>> draft-hilt-sipping-overload-00.txt
> >>>>
> >>>>
> >>>>
> >>>> I think it is important to focus on overload of the ability to=20
> >>>> PROCESS SIP messages.  In particular, the focus should be on the=20
> >>>> situation where, if the SIP messages keep coming, the box will=20
> >>>> crash (usually preceded by unproductive thrashing).
> >>>>
> >>>> As such, the mechanism and messaging must be as "lightweight"
> >>>> as possible, in order to avoid making the machine=20
> congestion worse.
> >>>>
> >>>> The other kinds of resource specific overload mechanisms you=20
> >>>> discuss sound very useful.  But I don't think it is a=20
> good idea to=20
> >>>> try to overload them on THIS effort.
> >>>>
> >>>> Janet
> >>>>
> >>>>
> >>
> >>
> >> _______________________________________________
> >> Sipping mailing list =20
> https://www1.ietf.org/mailman/listinfo/sipping
> >> This list is for NEW development of the application of SIP Use=20
> >> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> >> sip@ietf.org for new developments of core SIP
> >>
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP=20
> Use sip-implementors@cs.columbia.edu for questions on current=20
> sip Use sip@ietf.org for new developments of core SIP
>=20

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



From sipping-bounces@ietf.org Fri Jan 05 09:47:36 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2qLU-0002DG-OI; Fri, 05 Jan 2007 09:47:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2qLT-0002D5-Pe
	for sipping@ietf.org; Fri, 05 Jan 2007 09:46:59 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2qLT-00075H-AC
	for sipping@ietf.org; Fri, 05 Jan 2007 09:46:59 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 05 Jan 2007 09:46:59 -0500
X-IronPort-AV: i="4.12,243,1165208400"; 
	d="scan'208"; a="110944962:sNHT74231856"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l05Ekx4c004926; 
	Fri, 5 Jan 2007 09:46:59 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l05Ekw7f009227; 
	Fri, 5 Jan 2007 09:46:58 -0500 (EST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 5 Jan 2007 09:46:58 -0500
Received: from [10.86.242.124] ([10.86.242.124]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 5 Jan 2007 09:46:57 -0500
Message-ID: <459E64E0.8000603@cisco.com>
Date: Fri, 05 Jan 2007 09:46:56 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Henry Sinnreich <hsinnrei@adobe.com>
Subject: Re: [Sipping] RE: Queries
	and	commentsondraft-hilt-sipping-overload-00.txt
References: <24CCCC428EFEA2469BF046DB3C7A8D221414A1@namail5.corp.adobe.com>
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D221414A1@namail5.corp.adobe.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Jan 2007 14:46:57.0502 (UTC)
	FILETIME=[59715FE0:01C730D8]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8728; t=1168008419;
	x=1168872419; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20RE=3A=20Queries=20and=09commentsondraft-h
	ilt-sipping-overload-00.txt |Sender:=20
	|To:=20Henry=20Sinnreich=20<hsinnrei@adobe.com>;
	bh=6sKTLxFLJyAtnKsbCVJxurdSsXbbeXz2LENOrF1krXc=;
	b=T3Gh++tK6ZKNkixDqcwQ0h9DgPrmJeuLUR3oiBwpyoheKxo3NS2d+cfVC+IE742QSAwd7cpa
	D80ibsxAG+tEjO5YN6lB5Xa4jdZN2/twomW/gTsKZrdTj6Qwu80E6KCC;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f0b5a4216bfa030ed8a6f68d1833f8ae
Cc: Volker Hilt <volkerh@bell-labs.com>, sipping <sipping@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	Tom-PT Taylor <taylor@nortel.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Henry,

I agree with you that many features that are being provided in the 
network could be provided in the endpoints, and that doing so would 
eliminate some potential failure points. But there are some services 
that just don't work very well that way. For instance voicemail service 
for devices that aren't permanently connected to the network.

I suppose we could assume that every user should have his own voicemail 
server sitting in his home, permanently connected and powered. That may 
work for some people, but others may want to outsource that. In a way 
this is analogous to network based services for doing file system 
backups - every user could have their own, but its not an operational 
model that works for everyone.

Also, there is bound to be some centralization when the customer is a 
business. For instance a call center.

So I think there will remain important targets for DOS attacks.

	Paul

Henry Sinnreich wrote:
> Mike,
> 
>> overload of end host node supporting VoIP application
> 
> Maybe we pull out our laptops (end host node) at the IETF meeting and
> you can show me how a VoIP application can overload it. Unless you have
> an antique PC with collectors' value :-)
> 
> The same applies to SIP phones. DDOS is a security issue.
> 
>> over-provisioning may not always be the most cost-effective use of
>> resources.
> 
> A comparison between the cost of over-provisioning and the cost of
> complexity would indeed be very interesting for VoIP before plunging
> into the SIP overload work.
> 
>> Hope that restores your sanity. :)
> 
> Not quite.
> 
> Maybe we have a misunderstanding and you refer to the endless collection
> of SIP feature servers in VoIP networks, in which case I am in full
> agreement. The correct alternative to this is to place the features in
> the end host nodes (SIP UA) and use SIP as it is defined in RFC 3261: 
> A discovery and rendezvous protocol (with as little state in the proxy
> as possible).
> 
> Let the flames come...
> 
> Henry
> 
> -----Original Message-----
> From: Michael Hammer (mhammer) [mailto:mhammer@cisco.com] 
> Sent: Thursday, January 04, 2007 11:00 AM
> To: Henry Sinnreich; Volker Hilt; Tom-PT Taylor
> Cc: sipping
> Subject: RE: [Sipping] RE: Queries and
> commentsondraft-hilt-sipping-overload-00.txt
> 
> Henry,
> 
> This has nothing to do with router congestion and everything to do with
> overload of end host node supporting VoIP application, which is more
> akin to an unintentional DDOS.
> 
> And yes, one can always throw more hosts at the problem, but
> over-provisioning may not always be the most cost-effective use of
> resources.
> 
> Hope that restores your sanity. :)
> 
> Mike
> 
> 
>> -----Original Message-----
>> From: Henry Sinnreich [mailto:hsinnrei@adobe.com] 
>> Sent: Wednesday, January 03, 2007 6:42 PM
>> To: Volker Hilt; Tom-PT Taylor
>> Cc: sipping; Michael Hammer (mhammer)
>> Subject: RE: [Sipping] RE: Queries and 
>> commentsondraft-hilt-sipping-overload-00.txt
>>
>> Volker is 100% correct and I would only like to add that a 
>> little more bandwidth (think of all the multimedia and 
>> animated web commercials
>> flowing) and modern processors are far cheaper and more 
>> effective in avoiding overload in the first place.
>>
>> Sanity check: VoIP traffic is so small, that it is hard to 
>> detect on the net :-)
>>
>> Thanks, Henry
>>
>> -----Original Message-----
>> From: Volker Hilt [mailto:volkerh@bell-labs.com]
>> Sent: Wednesday, January 03, 2007 3:09 PM
>> To: Tom-PT Taylor
>> Cc: sipping; Michael Hammer (mhammer)
>> Subject: Re: [Sipping] RE: Queries and
>> commentsondraft-hilt-sipping-overload-00.txt
>>
>> Tom-PT Taylor wrote:
>>> One of the proposals going around TISPAN was for a separate 
>> overload 
>>> control protocol, for exactly the reason you point out: 
>> that you may 
>>> need to control for overload from multiple application protocols on
>> the 
>>> same box. Another argument, applying even to single-protocol boxes,
>> was 
>>> that this would be more effective than defining new overload 
>>> capabilities in a multiplicity of protocols.
>>>
>> A downside is that all SIP boxes need to implement the 
>> protocol stack of
>>
>> the stand-alone protocol for this to work well. Also, the 
>> stand-alone protocol stack would have to have hooks into all 
>> other protocols to actually facilitate the throttling (what 
>> if it doesn't?). E.g. it would have to have a way to instruct 
>> the SIP protocol stack on the upstream entity to reject a 
>> certain fraction/rate of messages. During operation, the 
>> protocol would have to exchange some kind of messages (maybe similar
>>
>> to SUB/NOT) which again contribute to messaging traffic. A 
>> mechanism directly built into SIP does not have these 
>> problems and seems to be simpler and easier to deploy.
>>
>> Volker
>>
>>
>>
>>> Janet P Gunn wrote:
>>>> Mike,
>>>>
>>>> Good point..
>>>>
>>>> Obviously everything is simplest if we are only dealing with one 
>>>> protocol.
>>>>
>>>> If the box is serving multiple protocols, I would assume that 
>>>> detecting/identifying overload applies to the machine, not the
>> protocol
>>>> (e.g , cpu usage, internal queue length, time in  queue).
>>>>
>>>> SIP can, of course, only address signalling the overload to other
>> boxes
>>>> that "talk" SIP.  Obviously, if that "other box" is 
>> sending both SIP 
>>>> messages and other-protocol-messages to the overloaded 
>> box, it would
>> be
>>>> nice/ sensible if the "other box" throttled all messages (SIP or
>>>> otherwise)
>>>> to the overloaded box.  But I don't think SIP can specify that.
>>>>
>>>> If the overloaded box talks to some boxes that "talk" SIP, and some
>> that
>>>> don't, there is always the possibility that the SIP boxes will cut
>> back,
>>>> and the others won't, leaving the overloaded box STILL overloaded,
>> but 
>>>> with
>>>> non-SIP work.  Obviously this wouldn't be a good idea.  I 
>> don't think
>> we
>>>> can necessarily assume it away, but I don't think we can 
>> "solve" it 
>>>> with a SIP document.
>>>>
>>>> Janet
>>>>
>>>>
>>>>
>>>> "Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on 
>> 01/03/2007
>>>> 10:42:35 AM:
>>>>
>>>>> Janet and others,
>>>>>
>>>>> Just out of curiosity, do you assume that SIP is the ONLY 
>> protocol 
>>>>> operating on a particular platform?
>>>>>
>>>>> If not, then do you assume that each protocol has its own oveload 
>>>>> control mechanism and that each will independently determine when
>> the
>>>>> machine is overloaded?
>>>>>
>>>>> Mike
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Janet P Gunn [mailto:jgunn6@csc.com]
>>>>>> Sent: Wednesday, January 03, 2007 8:53 AM
>>>>>> To: Darshan Bildikar
>>>>>> Cc: 'Volker Hilt'; 'sipping'
>>>>>> Subject: Re: [Sipping] RE: Queries and commentson 
>>>>>> draft-hilt-sipping-overload-00.txt
>>>>>>
>>>>>>
>>>>>>
>>>>>> I think it is important to focus on overload of the ability to 
>>>>>> PROCESS SIP messages.  In particular, the focus should be on the 
>>>>>> situation where, if the SIP messages keep coming, the box will 
>>>>>> crash (usually preceded by unproductive thrashing).
>>>>>>
>>>>>> As such, the mechanism and messaging must be as "lightweight"
>>>>>> as possible, in order to avoid making the machine 
>> congestion worse.
>>>>>> The other kinds of resource specific overload mechanisms you 
>>>>>> discuss sound very useful.  But I don't think it is a 
>> good idea to 
>>>>>> try to overload them on THIS effort.
>>>>>>
>>>>>> Janet
>>>>>>
>>>>>>
>>>>
>>>> _______________________________________________
>>>> Sipping mailing list  
>> https://www1.ietf.org/mailman/listinfo/sipping
>>>> This list is for NEW development of the 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 sipping-bounces@ietf.org Fri Jan 05 10:13:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2qlB-0007UX-Tl; Fri, 05 Jan 2007 10:13:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2qlA-0007RT-7X
	for sipping@ietf.org; Fri, 05 Jan 2007 10:13:32 -0500
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2ql8-00057w-K1
	for sipping@ietf.org; Fri, 05 Jan 2007 10:13:32 -0500
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail1.lucent.com (8.13.8/IER-o) with ESMTP id l05FDPai015180;
	Fri, 5 Jan 2007 09:13:30 -0600 (CST)
Received: from [127.0.0.1] ([135.104.20.68])
	by homail.ho.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l05FDPW05374; Fri, 5 Jan 2007 10:13:25 -0500 (EST)
Message-ID: <459E6B11.7090709@bell-labs.com>
Date: Fri, 05 Jan 2007 10:13:21 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Darshan Bildikar <dbildikar@ipunity.com>
References: <EXCHANGEVMGbQtF8tBY00001d3a@exchangevm.ipunity.com>
In-Reply-To: <EXCHANGEVMGbQtF8tBY00001d3a@exchangevm.ipunity.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 192.11.226.41
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: 'sipping' <sipping@ietf.org>
Subject: [Sipping] Re: Queries and comments on
	draft-hilt-sipping-overload-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Darshan Bildikar wrote:
> Usually a proxy will not entirely stop sending messages to a downstream 
> neighbor. Instead, overload control should slowly regulate the request 
> rate to a lower level that is acceptable to the downstream proxy. So 
> even in an overload situation, the upstream proxy would still send some 
> requests and therefore receive responses that contain the load status. 
> Even in very extreme overload where a proxy entirely stops to forward 
> requests, it can still occasionally forward a request to probe the 
> current load status.
> 
> <Darshan> With all due respect, "some requests" and "occasionally" sound
> very ambiguous. This should probably be better defined in the draft.
> (Recommended timers etc)
> 
Yes, you are right, the draft needs to be more specific there.

> <Darshan> Do look at these requirements in
> "draft-rosenberg-sipping-overload-reqs". They state:-
> 
> "The specification for the overload mechanism should give guidance on which
> message types might be desirable to process over others during times of
> overload, based on SIP-specific considerations.  For example, it may be more
> beneficial to process a SUBSCRIBE refresh with Expires of zero than a
> SUBSCRIBE refresh with a non-zero expiration, since the former reduces the
> overall amount of load on the element, or to process re-INVITEs over new
> INVITEs."
> 
> "The overload mechanism should be unambiguous about whether a load
> indication applies to a specific IP address, host, or URI, so that an
> upstream element can determine the load of the entity to which a request is
> to be sent."
> 
> These two requirements can clearly not be satisfied with your approach. A
> SUB/NOT mechanism is probably what is needed. You can take a call on how you
> want to achieve this. 

The header mechanism does satisfy the above two requirements. The 
overload control specification can (and already does to some extent) 
give guidance on which message types should be processed over others in 
an upstream entity that has received a overload indication.

The header should also not be ambiguous about the element to which a 
load indication applies. This is determined by the address that is put 
into the Load header. I agree with you that better explanations are 
needed in the draft (remember that it still is a -00 draft).

Volker


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



From sipping-bounces@ietf.org Fri Jan 05 17:48:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2xqO-0004TY-QH; Fri, 05 Jan 2007 17:47:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2xqN-0004TS-0X
	for sipping@ietf.org; Fri, 05 Jan 2007 17:47:23 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2xqM-0006qF-He
	for sipping@ietf.org; Fri, 05 Jan 2007 17:47:22 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 05 Jan 2007 17:47:22 -0500
X-IronPort-AV: i="4.13,155,1167627600"; 
	d="scan'208"; a="110991693:sNHT62208920"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l05MlMVG019125; 
	Fri, 5 Jan 2007 17:47:22 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l05MlL7f004022; 
	Fri, 5 Jan 2007 17:47:22 -0500 (EST)
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 5 Jan 2007 17:47:21 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: Queries and
	commentsondraft-hilt-sipping-overload-00.txt
Date: Fri, 5 Jan 2007 17:47:20 -0500
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E3026B6CFE@xmb-rtp-20b.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] RE: Queries and
	commentsondraft-hilt-sipping-overload-00.txt
Thread-Index: Accve3DNtEEYyv7nRxS4HM/0C9IZxwAFOtNwACQlLLAAFK7oIAApWRKw
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Henry Sinnreich" <hsinnrei@adobe.com>,
	"Volker Hilt" <volkerh@bell-labs.com>, "Tom-PT Taylor" <taylor@nortel.com>
X-OriginalArrivalTime: 05 Jan 2007 22:47:21.0924 (UTC)
	FILETIME=[76232040:01C7311B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=9056; t=1168037242;
	x=1168901242; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mhammer@cisco.com;
	z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20RE=3A=20Queries=20and=20commentsondraft-h
	ilt-sipping-overload-00.txt |Sender:=20
	|To:=20=22Henry=20Sinnreich=22=20<hsinnrei@adobe.com>,
	=0A=20=20=20=20=20=
	20=20=20=22Volker=20Hilt=22=20<volkerh@bell-labs.com>,
	=0A=20=20=20=20=20=2
	0=20=20=22Tom-PT=20Taylor=22=20<taylor@nortel.com>;
	bh=x4mXdV6XIVMwLQJccGUyQdMGRdN4MwMOOxwp7+QiCVk=;
	b=i9VENg44b1sgokv1fSLNspostC9YnqkN/3LzyZCSsQFubB9dq57J8eOUijmWqmmq72telLRv
	x9kUdx4yS2MxMu3BvMVOpO5TlMh5ulSkK3EbRDbWL6h6CxV8UNk8iy1z;
Authentication-Results: rtp-dkim-2; header.From=mhammer@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Henry,

No flames, the difference is a matter of context or assumptions about
the envisioned architecture that might result in overload or not.  You
were thinking in terms of the original P2P vision of SIP.  I was
thinking in terms of the IMS variety where the question of how many
INVITEs/second does it take to bring down a SIP proxy, especially if UDP
is used and re-transmissions start to compound the problem till no
useful work gets done, or worse it crashes.

You have a logical conclusion about the approach to avoid the problem to
begin with, given some of the architectural design choices you make,
based on certain factors that have no value for you.

Did you mean incremental complexity over what has already been
introduced? :)

Mike

> -----Original Message-----
> From: Henry Sinnreich [mailto:hsinnrei@adobe.com]=20
> Sent: Thursday, January 04, 2007 10:03 PM
> To: Michael Hammer (mhammer); Volker Hilt; Tom-PT Taylor
> Cc: sipping
> Subject: RE: [Sipping] RE: Queries and=20
> commentsondraft-hilt-sipping-overload-00.txt
>=20
> Mike,
>=20
> > overload of end host node supporting VoIP application
>=20
> Maybe we pull out our laptops (end host node) at the IETF=20
> meeting and you can show me how a VoIP application can=20
> overload it. Unless you have an antique PC with collectors' value :-)
>=20
> The same applies to SIP phones. DDOS is a security issue.
>=20
> > over-provisioning may not always be the most cost-effective use of=20
> > resources.
>=20
> A comparison between the cost of over-provisioning and the=20
> cost of complexity would indeed be very interesting for VoIP=20
> before plunging into the SIP overload work.
>=20
> > Hope that restores your sanity. :)
>=20
> Not quite.
>=20
> Maybe we have a misunderstanding and you refer to the endless=20
> collection of SIP feature servers in VoIP networks, in which=20
> case I am in full agreement. The correct alternative to this=20
> is to place the features in the end host nodes (SIP UA) and=20
> use SIP as it is defined in RFC 3261:=20
> A discovery and rendezvous protocol (with as little state in=20
> the proxy as possible).
>=20
> Let the flames come...
>=20
> Henry
>=20
> -----Original Message-----
> From: Michael Hammer (mhammer) [mailto:mhammer@cisco.com]
> Sent: Thursday, January 04, 2007 11:00 AM
> To: Henry Sinnreich; Volker Hilt; Tom-PT Taylor
> Cc: sipping
> Subject: RE: [Sipping] RE: Queries and
> commentsondraft-hilt-sipping-overload-00.txt
>=20
> Henry,
>=20
> This has nothing to do with router congestion and everything=20
> to do with overload of end host node supporting VoIP=20
> application, which is more akin to an unintentional DDOS.
>=20
> And yes, one can always throw more hosts at the problem, but=20
> over-provisioning may not always be the most cost-effective=20
> use of resources.
>=20
> Hope that restores your sanity. :)
>=20
> Mike
>=20
>=20
> > -----Original Message-----
> > From: Henry Sinnreich [mailto:hsinnrei@adobe.com]
> > Sent: Wednesday, January 03, 2007 6:42 PM
> > To: Volker Hilt; Tom-PT Taylor
> > Cc: sipping; Michael Hammer (mhammer)
> > Subject: RE: [Sipping] RE: Queries and=20
> > commentsondraft-hilt-sipping-overload-00.txt
> >=20
> > Volker is 100% correct and I would only like to add that a=20
> little more=20
> > bandwidth (think of all the multimedia and animated web commercials
> > flowing) and modern processors are far cheaper and more=20
> effective in=20
> > avoiding overload in the first place.
> >=20
> > Sanity check: VoIP traffic is so small, that it is hard to=20
> detect on=20
> > the net :-)
> >=20
> > Thanks, Henry
> >=20
> > -----Original Message-----
> > From: Volker Hilt [mailto:volkerh@bell-labs.com]
> > Sent: Wednesday, January 03, 2007 3:09 PM
> > To: Tom-PT Taylor
> > Cc: sipping; Michael Hammer (mhammer)
> > Subject: Re: [Sipping] RE: Queries and=20
> > commentsondraft-hilt-sipping-overload-00.txt
> >=20
> > Tom-PT Taylor wrote:
> > > One of the proposals going around TISPAN was for a separate
> > overload
> > > control protocol, for exactly the reason you point out:=20
> > that you may
> > > need to control for overload from multiple application=20
> protocols on
> > the
> > > same box. Another argument, applying even to=20
> single-protocol boxes,
> > was
> > > that this would be more effective than defining new overload=20
> > > capabilities in a multiplicity of protocols.
> > >=20
> > A downside is that all SIP boxes need to implement the=20
> protocol stack=20
> > of
> >=20
> > the stand-alone protocol for this to work well. Also, the=20
> stand-alone=20
> > protocol stack would have to have hooks into all other protocols to=20
> > actually facilitate the throttling (what if it doesn't?). E.g. it=20
> > would have to have a way to instruct the SIP protocol stack on the=20
> > upstream entity to reject a certain fraction/rate of=20
> messages. During=20
> > operation, the protocol would have to exchange some kind of=20
> messages=20
> > (maybe similar
> >=20
> > to SUB/NOT) which again contribute to messaging traffic. A=20
> mechanism=20
> > directly built into SIP does not have these problems and=20
> seems to be=20
> > simpler and easier to deploy.
> >=20
> > Volker
> >=20
> >=20
> >=20
> > > Janet P Gunn wrote:
> > >> Mike,
> > >>
> > >> Good point..
> > >>
> > >> Obviously everything is simplest if we are only dealing with one=20
> > >> protocol.
> > >>
> > >> If the box is serving multiple protocols, I would assume that=20
> > >> detecting/identifying overload applies to the machine, not the
> > protocol
> > >> (e.g , cpu usage, internal queue length, time in  queue).
> > >>
> > >> SIP can, of course, only address signalling the overload to other
> > boxes
> > >> that "talk" SIP.  Obviously, if that "other box" is
> > sending both SIP
> > >> messages and other-protocol-messages to the overloaded
> > box, it would
> > be
> > >> nice/ sensible if the "other box" throttled all messages (SIP or
> > >> otherwise)
> > >> to the overloaded box.  But I don't think SIP can specify that.
> > >>
> > >> If the overloaded box talks to some boxes that "talk"=20
> SIP, and some
> > that
> > >> don't, there is always the possibility that the SIP=20
> boxes will cut
> > back,
> > >> and the others won't, leaving the overloaded box STILL=20
> overloaded,
> > but
> > >> with
> > >> non-SIP work.  Obviously this wouldn't be a good idea.  I
> > don't think
> > we
> > >> can necessarily assume it away, but I don't think we can
> > "solve" it
> > >> with a SIP document.
> > >>
> > >> Janet
> > >>
> > >>
> > >>
> > >> "Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on
> > 01/03/2007
> > >> 10:42:35 AM:
> > >>
> > >>> Janet and others,
> > >>>
> > >>> Just out of curiosity, do you assume that SIP is the ONLY
> > protocol
> > >>> operating on a particular platform?
> > >>>
> > >>> If not, then do you assume that each protocol has its=20
> own oveload=20
> > >>> control mechanism and that each will independently=20
> determine when
> > the
> > >>> machine is overloaded?
> > >>>
> > >>> Mike
> > >>>
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: Janet P Gunn [mailto:jgunn6@csc.com]
> > >>>> Sent: Wednesday, January 03, 2007 8:53 AM
> > >>>> To: Darshan Bildikar
> > >>>> Cc: 'Volker Hilt'; 'sipping'
> > >>>> Subject: Re: [Sipping] RE: Queries and commentson=20
> > >>>> draft-hilt-sipping-overload-00.txt
> > >>>>
> > >>>>
> > >>>>
> > >>>> I think it is important to focus on overload of the ability to=20
> > >>>> PROCESS SIP messages.  In particular, the focus should=20
> be on the=20
> > >>>> situation where, if the SIP messages keep coming, the box will=20
> > >>>> crash (usually preceded by unproductive thrashing).
> > >>>>
> > >>>> As such, the mechanism and messaging must be as "lightweight"
> > >>>> as possible, in order to avoid making the machine
> > congestion worse.
> > >>>>
> > >>>> The other kinds of resource specific overload mechanisms you=20
> > >>>> discuss sound very useful.  But I don't think it is a
> > good idea to
> > >>>> try to overload them on THIS effort.
> > >>>>
> > >>>> Janet
> > >>>>
> > >>>>
> > >>
> > >>
> > >> _______________________________________________
> > >> Sipping mailing list
> > https://www1.ietf.org/mailman/listinfo/sipping
> > >> This list is for NEW development of the application of SIP Use=20
> > >> sip-implementors@cs.columbia.edu for questions on=20
> current sip Use=20
> > >> sip@ietf.org for new developments of core SIP
> > >>
> >=20
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
> >=20
>=20

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



From sipping-bounces@ietf.org Fri Jan 05 18:21:36 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2yNS-0001vO-O4; Fri, 05 Jan 2007 18:21:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2yNP-0001uk-Vh
	for sipping@ietf.org; Fri, 05 Jan 2007 18:21:32 -0500
Received: from exprod6og51.obsmtp.com ([64.18.1.183])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H2yNN-0007Sr-Q6
	for sipping@ietf.org; Fri, 05 Jan 2007 18:21:31 -0500
Received: from source ([192.150.11.134]) by exprod6ob51.postini.com
	([64.18.5.12]) with SMTP; Fri, 05 Jan 2007 15:21:27 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com
	[192.150.20.198] (may be forged))
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l05NIJvV013493; Fri, 5 Jan 2007 15:18:20 -0800 (PST)
Received: from fe2.corp.adobe.com (fe2.corp.adobe.com [10.8.192.72])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	l05NLLeC010319; Fri, 5 Jan 2007 15:21:22 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe2.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 5 Jan 2007 15:21:21 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: Queries
	and	commentsondraft-hilt-sipping-overload-00.txt
Date: Fri, 5 Jan 2007 15:21:21 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D221414B0@namail5.corp.adobe.com>
In-Reply-To: <459E64E0.8000603@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] RE: Queries
	and	commentsondraft-hilt-sipping-overload-00.txt
Thread-Index: Accw2GxtmqksmxN6RnS1QTp5n9UEfQAQuNaQ
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 05 Jan 2007 23:21:21.0887 (UTC)
	FILETIME=[360CC6F0:01C73120]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2d133cc328f58695161c98bb4f4dc213
Cc: Volker Hilt <volkerh@bell-labs.com>, sipping <sipping@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	Tom-PT Taylor <taylor@nortel.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Mike,

>But there are some services=20
>that just don't work very well that way. For instance voicemail service

>for devices that aren't permanently connected to the network.

Actually, voice mail is an excellent example, since VM can be more
reliable provided in endpoints in a distributed P2P SIP network. See
section 5.1 here

http://portal.acm.org/citation.cfm?id=3D1065999=20

The prototype for this system has been implemented and is reported
elsewhere in a tech report from Columbia University.=20

Skype has voice mail as well, most likely not in data centers full of
servers for their 120 million users, but rather in their p2p network.=20
BTW: Does anyone here have more info on this?

> Also, there is bound to be some centralization when the customer is a=20
> business. For instance a call center.

This is another good example. A call center agent workstation can be
implemented as a peer in P2P as well.

This discussion is really not about VM and call centers, but about
services in the network (AKA the mutation of the IN) versus the "dumb
network" with the applications in the endpoints.

I can't help remembering what happened to the IN vs. the "dumb network",

but I guess this is not a topic for this list.=20

Coming back to overload for SIP, P2P is the better approach, since it
seems to be scalable without any overload problems.

A break during the upcoming P2P SIP WG meeting (let's hope) is good
opportunity to discuss this, or maybe even on the list at
p2p-sip@cs.columbia.edu after the P2P SIP WG gets started.

Thanks, Henry

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
Sent: Friday, January 05, 2007 8:47 AM
To: Henry Sinnreich
Cc: Michael Hammer (mhammer); Volker Hilt; Tom-PT Taylor; sipping
Subject: Re: [Sipping] RE: Queries and
commentsondraft-hilt-sipping-overload-00.txt

Henry,

I agree with you that many features that are being provided in the=20
network could be provided in the endpoints, and that doing so would=20
eliminate some potential failure points. But there are some services=20
that just don't work very well that way. For instance voicemail service=20
for devices that aren't permanently connected to the network.

I suppose we could assume that every user should have his own voicemail=20
server sitting in his home, permanently connected and powered. That may=20
work for some people, but others may want to outsource that. In a way=20
this is analogous to network based services for doing file system=20
backups - every user could have their own, but its not an operational=20
model that works for everyone.

Also, there is bound to be some centralization when the customer is a=20
business. For instance a call center.

So I think there will remain important targets for DOS attacks.

	Paul

Henry Sinnreich wrote:
> Mike,
>=20
>> overload of end host node supporting VoIP application
>=20
> Maybe we pull out our laptops (end host node) at the IETF meeting and
> you can show me how a VoIP application can overload it. Unless you
have
> an antique PC with collectors' value :-)
>=20
> The same applies to SIP phones. DDOS is a security issue.
>=20
>> over-provisioning may not always be the most cost-effective use of
>> resources.
>=20
> A comparison between the cost of over-provisioning and the cost of
> complexity would indeed be very interesting for VoIP before plunging
> into the SIP overload work.
>=20
>> Hope that restores your sanity. :)
>=20
> Not quite.
>=20
> Maybe we have a misunderstanding and you refer to the endless
collection
> of SIP feature servers in VoIP networks, in which case I am in full
> agreement. The correct alternative to this is to place the features in
> the end host nodes (SIP UA) and use SIP as it is defined in RFC 3261:=20
> A discovery and rendezvous protocol (with as little state in the proxy
> as possible).
>=20
> Let the flames come...
>=20
> Henry
>=20
> -----Original Message-----
> From: Michael Hammer (mhammer) [mailto:mhammer@cisco.com]=20
> Sent: Thursday, January 04, 2007 11:00 AM
> To: Henry Sinnreich; Volker Hilt; Tom-PT Taylor
> Cc: sipping
> Subject: RE: [Sipping] RE: Queries and
> commentsondraft-hilt-sipping-overload-00.txt
>=20
> Henry,
>=20
> This has nothing to do with router congestion and everything to do
with
> overload of end host node supporting VoIP application, which is more
> akin to an unintentional DDOS.
>=20
> And yes, one can always throw more hosts at the problem, but
> over-provisioning may not always be the most cost-effective use of
> resources.
>=20
> Hope that restores your sanity. :)
>=20
> Mike
>=20
>=20
>> -----Original Message-----
>> From: Henry Sinnreich [mailto:hsinnrei@adobe.com]=20
>> Sent: Wednesday, January 03, 2007 6:42 PM
>> To: Volker Hilt; Tom-PT Taylor
>> Cc: sipping; Michael Hammer (mhammer)
>> Subject: RE: [Sipping] RE: Queries and=20
>> commentsondraft-hilt-sipping-overload-00.txt
>>
>> Volker is 100% correct and I would only like to add that a=20
>> little more bandwidth (think of all the multimedia and=20
>> animated web commercials
>> flowing) and modern processors are far cheaper and more=20
>> effective in avoiding overload in the first place.
>>
>> Sanity check: VoIP traffic is so small, that it is hard to=20
>> detect on the net :-)
>>
>> Thanks, Henry
>>
>> -----Original Message-----
>> From: Volker Hilt [mailto:volkerh@bell-labs.com]
>> Sent: Wednesday, January 03, 2007 3:09 PM
>> To: Tom-PT Taylor
>> Cc: sipping; Michael Hammer (mhammer)
>> Subject: Re: [Sipping] RE: Queries and
>> commentsondraft-hilt-sipping-overload-00.txt
>>
>> Tom-PT Taylor wrote:
>>> One of the proposals going around TISPAN was for a separate=20
>> overload=20
>>> control protocol, for exactly the reason you point out:=20
>> that you may=20
>>> need to control for overload from multiple application protocols on
>> the=20
>>> same box. Another argument, applying even to single-protocol boxes,
>> was=20
>>> that this would be more effective than defining new overload=20
>>> capabilities in a multiplicity of protocols.
>>>
>> A downside is that all SIP boxes need to implement the=20
>> protocol stack of
>>
>> the stand-alone protocol for this to work well. Also, the=20
>> stand-alone protocol stack would have to have hooks into all=20
>> other protocols to actually facilitate the throttling (what=20
>> if it doesn't?). E.g. it would have to have a way to instruct=20
>> the SIP protocol stack on the upstream entity to reject a=20
>> certain fraction/rate of messages. During operation, the=20
>> protocol would have to exchange some kind of messages (maybe similar
>>
>> to SUB/NOT) which again contribute to messaging traffic. A=20
>> mechanism directly built into SIP does not have these=20
>> problems and seems to be simpler and easier to deploy.
>>
>> Volker
>>
>>
>>
>>> Janet P Gunn wrote:
>>>> Mike,
>>>>
>>>> Good point..
>>>>
>>>> Obviously everything is simplest if we are only dealing with one=20
>>>> protocol.
>>>>
>>>> If the box is serving multiple protocols, I would assume that=20
>>>> detecting/identifying overload applies to the machine, not the
>> protocol
>>>> (e.g , cpu usage, internal queue length, time in  queue).
>>>>
>>>> SIP can, of course, only address signalling the overload to other
>> boxes
>>>> that "talk" SIP.  Obviously, if that "other box" is=20
>> sending both SIP=20
>>>> messages and other-protocol-messages to the overloaded=20
>> box, it would
>> be
>>>> nice/ sensible if the "other box" throttled all messages (SIP or
>>>> otherwise)
>>>> to the overloaded box.  But I don't think SIP can specify that.
>>>>
>>>> If the overloaded box talks to some boxes that "talk" SIP, and some
>> that
>>>> don't, there is always the possibility that the SIP boxes will cut
>> back,
>>>> and the others won't, leaving the overloaded box STILL overloaded,
>> but=20
>>>> with
>>>> non-SIP work.  Obviously this wouldn't be a good idea.  I=20
>> don't think
>> we
>>>> can necessarily assume it away, but I don't think we can=20
>> "solve" it=20
>>>> with a SIP document.
>>>>
>>>> Janet
>>>>
>>>>
>>>>
>>>> "Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on=20
>> 01/03/2007
>>>> 10:42:35 AM:
>>>>
>>>>> Janet and others,
>>>>>
>>>>> Just out of curiosity, do you assume that SIP is the ONLY=20
>> protocol=20
>>>>> operating on a particular platform?
>>>>>
>>>>> If not, then do you assume that each protocol has its own oveload=20
>>>>> control mechanism and that each will independently determine when
>> the
>>>>> machine is overloaded?
>>>>>
>>>>> Mike
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Janet P Gunn [mailto:jgunn6@csc.com]
>>>>>> Sent: Wednesday, January 03, 2007 8:53 AM
>>>>>> To: Darshan Bildikar
>>>>>> Cc: 'Volker Hilt'; 'sipping'
>>>>>> Subject: Re: [Sipping] RE: Queries and commentson=20
>>>>>> draft-hilt-sipping-overload-00.txt
>>>>>>
>>>>>>
>>>>>>
>>>>>> I think it is important to focus on overload of the ability to=20
>>>>>> PROCESS SIP messages.  In particular, the focus should be on the=20
>>>>>> situation where, if the SIP messages keep coming, the box will=20
>>>>>> crash (usually preceded by unproductive thrashing).
>>>>>>
>>>>>> As such, the mechanism and messaging must be as "lightweight"
>>>>>> as possible, in order to avoid making the machine=20
>> congestion worse.
>>>>>> The other kinds of resource specific overload mechanisms you=20
>>>>>> discuss sound very useful.  But I don't think it is a=20
>> good idea to=20
>>>>>> try to overload them on THIS effort.
>>>>>>
>>>>>> Janet
>>>>>>
>>>>>>
>>>>
>>>> _______________________________________________
>>>> Sipping mailing list =20
>> https://www1.ietf.org/mailman/listinfo/sipping
>>>> This list is for NEW development of the application of SIP Use=20
>>>> sip-implementors@cs.columbia.edu for questions on current sip Use=20
>>>> 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=20
>> Use sip-implementors@cs.columbia.edu for questions on current=20
>> sip Use sip@ietf.org for new developments of core SIP
>>
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20

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



From sipping-bounces@ietf.org Fri Jan 05 18:29:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2yUs-0005Rj-0O; Fri, 05 Jan 2007 18:29:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2yUr-0005Re-B6
	for sipping@ietf.org; Fri, 05 Jan 2007 18:29:13 -0500
Received: from exprod6og56.obsmtp.com ([64.18.1.208])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H2yUq-0001C7-MK
	for sipping@ietf.org; Fri, 05 Jan 2007 18:29:13 -0500
Received: from source ([192.150.11.134]) by exprod6ob56.postini.com
	([64.18.5.12]) with SMTP; Fri, 05 Jan 2007 15:29:08 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com
	[192.150.20.198] (may be forged))
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l05NQ3vV014276; Fri, 5 Jan 2007 15:26:03 -0800 (PST)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	l05NS8ec010817; Fri, 5 Jan 2007 15:29:06 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 5 Jan 2007 15:29:05 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: Queries and
	commentsondraft-hilt-sipping-overload-00.txt
Date: Fri, 5 Jan 2007 15:27:40 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D221414B3@namail5.corp.adobe.com>
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E3026B6CFE@xmb-rtp-20b.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] RE: Queries and
	commentsondraft-hilt-sipping-overload-00.txt
Thread-Index: Accve3DNtEEYyv7nRxS4HM/0C9IZxwAFOtNwACQlLLAAFK7oIAApWRKwAAHU+/A=
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	"Volker Hilt" <volkerh@bell-labs.com>, "Tom-PT Taylor" <taylor@nortel.com>
X-OriginalArrivalTime: 05 Jan 2007 23:29:05.0536 (UTC)
	FILETIME=[4A680000:01C73121]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fe105289edd72640d9f392da880eefa2
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Michael,

> I was thinking in terms of the IMS variety

I have no idea how IMS can be really scalable and robust, especially in
a multi-vendor environment.

Following the latest I-Ds about SIP routing in such networks, the best I
can say is "it is work in progress" after all these years.

There are also no operational reports on IMS networks that have even
remotely the size of Skype.

Henry

-----Original Message-----
From: Michael Hammer (mhammer) [mailto:mhammer@cisco.com]=20
Sent: Friday, January 05, 2007 4:47 PM
To: Henry Sinnreich; Volker Hilt; Tom-PT Taylor
Cc: sipping
Subject: RE: [Sipping] RE: Queries and
commentsondraft-hilt-sipping-overload-00.txt

Henry,

No flames, the difference is a matter of context or assumptions about
the envisioned architecture that might result in overload or not.  You
were thinking in terms of the original P2P vision of SIP.  I was
thinking in terms of the IMS variety where the question of how many
INVITEs/second does it take to bring down a SIP proxy, especially if UDP
is used and re-transmissions start to compound the problem till no
useful work gets done, or worse it crashes.

You have a logical conclusion about the approach to avoid the problem to
begin with, given some of the architectural design choices you make,
based on certain factors that have no value for you.

Did you mean incremental complexity over what has already been
introduced? :)

Mike

> -----Original Message-----
> From: Henry Sinnreich [mailto:hsinnrei@adobe.com]=20
> Sent: Thursday, January 04, 2007 10:03 PM
> To: Michael Hammer (mhammer); Volker Hilt; Tom-PT Taylor
> Cc: sipping
> Subject: RE: [Sipping] RE: Queries and=20
> commentsondraft-hilt-sipping-overload-00.txt
>=20
> Mike,
>=20
> > overload of end host node supporting VoIP application
>=20
> Maybe we pull out our laptops (end host node) at the IETF=20
> meeting and you can show me how a VoIP application can=20
> overload it. Unless you have an antique PC with collectors' value :-)
>=20
> The same applies to SIP phones. DDOS is a security issue.
>=20
> > over-provisioning may not always be the most cost-effective use of=20
> > resources.
>=20
> A comparison between the cost of over-provisioning and the=20
> cost of complexity would indeed be very interesting for VoIP=20
> before plunging into the SIP overload work.
>=20
> > Hope that restores your sanity. :)
>=20
> Not quite.
>=20
> Maybe we have a misunderstanding and you refer to the endless=20
> collection of SIP feature servers in VoIP networks, in which=20
> case I am in full agreement. The correct alternative to this=20
> is to place the features in the end host nodes (SIP UA) and=20
> use SIP as it is defined in RFC 3261:=20
> A discovery and rendezvous protocol (with as little state in=20
> the proxy as possible).
>=20
> Let the flames come...
>=20
> Henry
>=20
> -----Original Message-----
> From: Michael Hammer (mhammer) [mailto:mhammer@cisco.com]
> Sent: Thursday, January 04, 2007 11:00 AM
> To: Henry Sinnreich; Volker Hilt; Tom-PT Taylor
> Cc: sipping
> Subject: RE: [Sipping] RE: Queries and
> commentsondraft-hilt-sipping-overload-00.txt
>=20
> Henry,
>=20
> This has nothing to do with router congestion and everything=20
> to do with overload of end host node supporting VoIP=20
> application, which is more akin to an unintentional DDOS.
>=20
> And yes, one can always throw more hosts at the problem, but=20
> over-provisioning may not always be the most cost-effective=20
> use of resources.
>=20
> Hope that restores your sanity. :)
>=20
> Mike
>=20
>=20
> > -----Original Message-----
> > From: Henry Sinnreich [mailto:hsinnrei@adobe.com]
> > Sent: Wednesday, January 03, 2007 6:42 PM
> > To: Volker Hilt; Tom-PT Taylor
> > Cc: sipping; Michael Hammer (mhammer)
> > Subject: RE: [Sipping] RE: Queries and=20
> > commentsondraft-hilt-sipping-overload-00.txt
> >=20
> > Volker is 100% correct and I would only like to add that a=20
> little more=20
> > bandwidth (think of all the multimedia and animated web commercials
> > flowing) and modern processors are far cheaper and more=20
> effective in=20
> > avoiding overload in the first place.
> >=20
> > Sanity check: VoIP traffic is so small, that it is hard to=20
> detect on=20
> > the net :-)
> >=20
> > Thanks, Henry
> >=20
> > -----Original Message-----
> > From: Volker Hilt [mailto:volkerh@bell-labs.com]
> > Sent: Wednesday, January 03, 2007 3:09 PM
> > To: Tom-PT Taylor
> > Cc: sipping; Michael Hammer (mhammer)
> > Subject: Re: [Sipping] RE: Queries and=20
> > commentsondraft-hilt-sipping-overload-00.txt
> >=20
> > Tom-PT Taylor wrote:
> > > One of the proposals going around TISPAN was for a separate
> > overload
> > > control protocol, for exactly the reason you point out:=20
> > that you may
> > > need to control for overload from multiple application=20
> protocols on
> > the
> > > same box. Another argument, applying even to=20
> single-protocol boxes,
> > was
> > > that this would be more effective than defining new overload=20
> > > capabilities in a multiplicity of protocols.
> > >=20
> > A downside is that all SIP boxes need to implement the=20
> protocol stack=20
> > of
> >=20
> > the stand-alone protocol for this to work well. Also, the=20
> stand-alone=20
> > protocol stack would have to have hooks into all other protocols to=20
> > actually facilitate the throttling (what if it doesn't?). E.g. it=20
> > would have to have a way to instruct the SIP protocol stack on the=20
> > upstream entity to reject a certain fraction/rate of=20
> messages. During=20
> > operation, the protocol would have to exchange some kind of=20
> messages=20
> > (maybe similar
> >=20
> > to SUB/NOT) which again contribute to messaging traffic. A=20
> mechanism=20
> > directly built into SIP does not have these problems and=20
> seems to be=20
> > simpler and easier to deploy.
> >=20
> > Volker
> >=20
> >=20
> >=20
> > > Janet P Gunn wrote:
> > >> Mike,
> > >>
> > >> Good point..
> > >>
> > >> Obviously everything is simplest if we are only dealing with one=20
> > >> protocol.
> > >>
> > >> If the box is serving multiple protocols, I would assume that=20
> > >> detecting/identifying overload applies to the machine, not the
> > protocol
> > >> (e.g , cpu usage, internal queue length, time in  queue).
> > >>
> > >> SIP can, of course, only address signalling the overload to other
> > boxes
> > >> that "talk" SIP.  Obviously, if that "other box" is
> > sending both SIP
> > >> messages and other-protocol-messages to the overloaded
> > box, it would
> > be
> > >> nice/ sensible if the "other box" throttled all messages (SIP or
> > >> otherwise)
> > >> to the overloaded box.  But I don't think SIP can specify that.
> > >>
> > >> If the overloaded box talks to some boxes that "talk"=20
> SIP, and some
> > that
> > >> don't, there is always the possibility that the SIP=20
> boxes will cut
> > back,
> > >> and the others won't, leaving the overloaded box STILL=20
> overloaded,
> > but
> > >> with
> > >> non-SIP work.  Obviously this wouldn't be a good idea.  I
> > don't think
> > we
> > >> can necessarily assume it away, but I don't think we can
> > "solve" it
> > >> with a SIP document.
> > >>
> > >> Janet
> > >>
> > >>
> > >>
> > >> "Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on
> > 01/03/2007
> > >> 10:42:35 AM:
> > >>
> > >>> Janet and others,
> > >>>
> > >>> Just out of curiosity, do you assume that SIP is the ONLY
> > protocol
> > >>> operating on a particular platform?
> > >>>
> > >>> If not, then do you assume that each protocol has its=20
> own oveload=20
> > >>> control mechanism and that each will independently=20
> determine when
> > the
> > >>> machine is overloaded?
> > >>>
> > >>> Mike
> > >>>
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: Janet P Gunn [mailto:jgunn6@csc.com]
> > >>>> Sent: Wednesday, January 03, 2007 8:53 AM
> > >>>> To: Darshan Bildikar
> > >>>> Cc: 'Volker Hilt'; 'sipping'
> > >>>> Subject: Re: [Sipping] RE: Queries and commentson=20
> > >>>> draft-hilt-sipping-overload-00.txt
> > >>>>
> > >>>>
> > >>>>
> > >>>> I think it is important to focus on overload of the ability to=20
> > >>>> PROCESS SIP messages.  In particular, the focus should=20
> be on the=20
> > >>>> situation where, if the SIP messages keep coming, the box will=20
> > >>>> crash (usually preceded by unproductive thrashing).
> > >>>>
> > >>>> As such, the mechanism and messaging must be as "lightweight"
> > >>>> as possible, in order to avoid making the machine
> > congestion worse.
> > >>>>
> > >>>> The other kinds of resource specific overload mechanisms you=20
> > >>>> discuss sound very useful.  But I don't think it is a
> > good idea to
> > >>>> try to overload them on THIS effort.
> > >>>>
> > >>>> Janet
> > >>>>
> > >>>>
> > >>
> > >>
> > >> _______________________________________________
> > >> Sipping mailing list
> > https://www1.ietf.org/mailman/listinfo/sipping
> > >> This list is for NEW development of the application of SIP Use=20
> > >> sip-implementors@cs.columbia.edu for questions on=20
> current sip Use=20
> > >> sip@ietf.org for new developments of core SIP
> > >>
> >=20
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
> >=20
>=20

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



From sipping-bounces@ietf.org Mon Jan 08 10:01:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H3vyg-0004In-P1; Mon, 08 Jan 2007 09:59:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H3vyf-0004IW-AB
	for sipping@ietf.org; Mon, 08 Jan 2007 09:59:57 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H3vyY-0007HX-W9
	for sipping@ietf.org; Mon, 08 Jan 2007 09:59:57 -0500
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-5.cisco.com with ESMTP; 08 Jan 2007 06:59:50 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id l08Exorv026792; 
	Mon, 8 Jan 2007 06:59:50 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l08Ex9JP022700;
	Mon, 8 Jan 2007 06:59:47 -0800 (PST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 8 Jan 2007 09:59:39 -0500
Received: from [10.86.242.10] ([10.86.242.10]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 8 Jan 2007 09:59:38 -0500
Message-ID: <45A25C5A.1040705@cisco.com>
Date: Mon, 08 Jan 2007 09:59:38 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Henry Sinnreich <hsinnrei@adobe.com>
Subject: Re: [Sipping] RE: Queries
	and	commentsondraft-hilt-sipping-overload-00.txt
References: <24CCCC428EFEA2469BF046DB3C7A8D221414B0@namail5.corp.adobe.com>
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D221414B0@namail5.corp.adobe.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Jan 2007 14:59:38.0897 (UTC)
	FILETIME=[9E824810:01C73335]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=12180; t=1168268390;
	x=1169132390; c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20RE=3A=20Queries=20and=09commentsondraft-h
	ilt-sipping-overload-00.txt |Sender:=20;
	bh=2+CQOV152q+lkm4RgB4bjCeQUkjGLI/XjJ5dvBVKDF0=;
	b=ccSpEItH04dPma/BYn2PGTUhweTUQVtrvTRB3X07CiY9dFAqqogR8XBVWOKsvD+FMgurCwPw
	f+SFAk7vl9ppc665sWVzCUPGqxkGl37v/2bQG212YGjZpsJGsgC4ajxG;
Authentication-Results: sj-dkim-5; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim5002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 65215b440f7ab00ca9514de4a7a89926
Cc: Volker Hilt <volkerh@bell-labs.com>, sipping <sipping@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	Tom-PT Taylor <taylor@nortel.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Henry,

I can't access the ACM article because I don't have an ACM online 
subscription.

I do understand that there have been proposals for P2P VM 
implementations, where some peer does the work for you. Frankly I just 
don't see how that can be robust, trustworthy, scale sufficiently, *and* 
not present DOS potentials.

I *do* think VM could, to some extent, be addressed using something 
comparable to the home answering machine - a user owned/operated VM 
server. For many that could be a good solution. But not for all. Some 
just won't have a suitable permanent network connection that can host 
such a server. Others won't want to be bothered with the management. 
Certainly in business deployments there has been a tendency to 
centralize such things.

Note that a VM server isn't necessarily a "network service" - it can be 
viewed as simply an alternative endpoint at an edge.

Nor is implementing VM in a P2P network necessarily a solution to DOS. 
The P2P network just becomes the DOS target. Bad guys trying to do 
damage will still try. The details of how that affects the targets may 
vary, but will still most likely be unpleasant and difficult to deal with.

	Paul

Henry Sinnreich wrote:
> Mike,
> 
>> But there are some services 
>> that just don't work very well that way. For instance voicemail service
> 
>> for devices that aren't permanently connected to the network.
> 
> Actually, voice mail is an excellent example, since VM can be more
> reliable provided in endpoints in a distributed P2P SIP network. See
> section 5.1 here
> 
> http://portal.acm.org/citation.cfm?id=1065999 
> 
> The prototype for this system has been implemented and is reported
> elsewhere in a tech report from Columbia University. 
> 
> Skype has voice mail as well, most likely not in data centers full of
> servers for their 120 million users, but rather in their p2p network. 
> BTW: Does anyone here have more info on this?
> 
>> Also, there is bound to be some centralization when the customer is a 
>> business. For instance a call center.
> 
> This is another good example. A call center agent workstation can be
> implemented as a peer in P2P as well.
> 
> This discussion is really not about VM and call centers, but about
> services in the network (AKA the mutation of the IN) versus the "dumb
> network" with the applications in the endpoints.
> 
> I can't help remembering what happened to the IN vs. the "dumb network",
> 
> but I guess this is not a topic for this list. 
> 
> Coming back to overload for SIP, P2P is the better approach, since it
> seems to be scalable without any overload problems.
> 
> A break during the upcoming P2P SIP WG meeting (let's hope) is good
> opportunity to discuss this, or maybe even on the list at
> p2p-sip@cs.columbia.edu after the P2P SIP WG gets started.
> 
> Thanks, Henry
> 
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: Friday, January 05, 2007 8:47 AM
> To: Henry Sinnreich
> Cc: Michael Hammer (mhammer); Volker Hilt; Tom-PT Taylor; sipping
> Subject: Re: [Sipping] RE: Queries and
> commentsondraft-hilt-sipping-overload-00.txt
> 
> Henry,
> 
> I agree with you that many features that are being provided in the 
> network could be provided in the endpoints, and that doing so would 
> eliminate some potential failure points. But there are some services 
> that just don't work very well that way. For instance voicemail service 
> for devices that aren't permanently connected to the network.
> 
> I suppose we could assume that every user should have his own voicemail 
> server sitting in his home, permanently connected and powered. That may 
> work for some people, but others may want to outsource that. In a way 
> this is analogous to network based services for doing file system 
> backups - every user could have their own, but its not an operational 
> model that works for everyone.
> 
> Also, there is bound to be some centralization when the customer is a 
> business. For instance a call center.
> 
> So I think there will remain important targets for DOS attacks.
> 
> 	Paul
> 
> Henry Sinnreich wrote:
>> Mike,
>>
>>> overload of end host node supporting VoIP application
>> Maybe we pull out our laptops (end host node) at the IETF meeting and
>> you can show me how a VoIP application can overload it. Unless you
> have
>> an antique PC with collectors' value :-)
>>
>> The same applies to SIP phones. DDOS is a security issue.
>>
>>> over-provisioning may not always be the most cost-effective use of
>>> resources.
>> A comparison between the cost of over-provisioning and the cost of
>> complexity would indeed be very interesting for VoIP before plunging
>> into the SIP overload work.
>>
>>> Hope that restores your sanity. :)
>> Not quite.
>>
>> Maybe we have a misunderstanding and you refer to the endless
> collection
>> of SIP feature servers in VoIP networks, in which case I am in full
>> agreement. The correct alternative to this is to place the features in
>> the end host nodes (SIP UA) and use SIP as it is defined in RFC 3261: 
>> A discovery and rendezvous protocol (with as little state in the proxy
>> as possible).
>>
>> Let the flames come...
>>
>> Henry
>>
>> -----Original Message-----
>> From: Michael Hammer (mhammer) [mailto:mhammer@cisco.com] 
>> Sent: Thursday, January 04, 2007 11:00 AM
>> To: Henry Sinnreich; Volker Hilt; Tom-PT Taylor
>> Cc: sipping
>> Subject: RE: [Sipping] RE: Queries and
>> commentsondraft-hilt-sipping-overload-00.txt
>>
>> Henry,
>>
>> This has nothing to do with router congestion and everything to do
> with
>> overload of end host node supporting VoIP application, which is more
>> akin to an unintentional DDOS.
>>
>> And yes, one can always throw more hosts at the problem, but
>> over-provisioning may not always be the most cost-effective use of
>> resources.
>>
>> Hope that restores your sanity. :)
>>
>> Mike
>>
>>
>>> -----Original Message-----
>>> From: Henry Sinnreich [mailto:hsinnrei@adobe.com] 
>>> Sent: Wednesday, January 03, 2007 6:42 PM
>>> To: Volker Hilt; Tom-PT Taylor
>>> Cc: sipping; Michael Hammer (mhammer)
>>> Subject: RE: [Sipping] RE: Queries and 
>>> commentsondraft-hilt-sipping-overload-00.txt
>>>
>>> Volker is 100% correct and I would only like to add that a 
>>> little more bandwidth (think of all the multimedia and 
>>> animated web commercials
>>> flowing) and modern processors are far cheaper and more 
>>> effective in avoiding overload in the first place.
>>>
>>> Sanity check: VoIP traffic is so small, that it is hard to 
>>> detect on the net :-)
>>>
>>> Thanks, Henry
>>>
>>> -----Original Message-----
>>> From: Volker Hilt [mailto:volkerh@bell-labs.com]
>>> Sent: Wednesday, January 03, 2007 3:09 PM
>>> To: Tom-PT Taylor
>>> Cc: sipping; Michael Hammer (mhammer)
>>> Subject: Re: [Sipping] RE: Queries and
>>> commentsondraft-hilt-sipping-overload-00.txt
>>>
>>> Tom-PT Taylor wrote:
>>>> One of the proposals going around TISPAN was for a separate 
>>> overload 
>>>> control protocol, for exactly the reason you point out: 
>>> that you may 
>>>> need to control for overload from multiple application protocols on
>>> the 
>>>> same box. Another argument, applying even to single-protocol boxes,
>>> was 
>>>> that this would be more effective than defining new overload 
>>>> capabilities in a multiplicity of protocols.
>>>>
>>> A downside is that all SIP boxes need to implement the 
>>> protocol stack of
>>>
>>> the stand-alone protocol for this to work well. Also, the 
>>> stand-alone protocol stack would have to have hooks into all 
>>> other protocols to actually facilitate the throttling (what 
>>> if it doesn't?). E.g. it would have to have a way to instruct 
>>> the SIP protocol stack on the upstream entity to reject a 
>>> certain fraction/rate of messages. During operation, the 
>>> protocol would have to exchange some kind of messages (maybe similar
>>>
>>> to SUB/NOT) which again contribute to messaging traffic. A 
>>> mechanism directly built into SIP does not have these 
>>> problems and seems to be simpler and easier to deploy.
>>>
>>> Volker
>>>
>>>
>>>
>>>> Janet P Gunn wrote:
>>>>> Mike,
>>>>>
>>>>> Good point..
>>>>>
>>>>> Obviously everything is simplest if we are only dealing with one 
>>>>> protocol.
>>>>>
>>>>> If the box is serving multiple protocols, I would assume that 
>>>>> detecting/identifying overload applies to the machine, not the
>>> protocol
>>>>> (e.g , cpu usage, internal queue length, time in  queue).
>>>>>
>>>>> SIP can, of course, only address signalling the overload to other
>>> boxes
>>>>> that "talk" SIP.  Obviously, if that "other box" is 
>>> sending both SIP 
>>>>> messages and other-protocol-messages to the overloaded 
>>> box, it would
>>> be
>>>>> nice/ sensible if the "other box" throttled all messages (SIP or
>>>>> otherwise)
>>>>> to the overloaded box.  But I don't think SIP can specify that.
>>>>>
>>>>> If the overloaded box talks to some boxes that "talk" SIP, and some
>>> that
>>>>> don't, there is always the possibility that the SIP boxes will cut
>>> back,
>>>>> and the others won't, leaving the overloaded box STILL overloaded,
>>> but 
>>>>> with
>>>>> non-SIP work.  Obviously this wouldn't be a good idea.  I 
>>> don't think
>>> we
>>>>> can necessarily assume it away, but I don't think we can 
>>> "solve" it 
>>>>> with a SIP document.
>>>>>
>>>>> Janet
>>>>>
>>>>>
>>>>>
>>>>> "Michael Hammer \(mhammer\)" <mhammer@cisco.com> wrote on 
>>> 01/03/2007
>>>>> 10:42:35 AM:
>>>>>
>>>>>> Janet and others,
>>>>>>
>>>>>> Just out of curiosity, do you assume that SIP is the ONLY 
>>> protocol 
>>>>>> operating on a particular platform?
>>>>>>
>>>>>> If not, then do you assume that each protocol has its own oveload 
>>>>>> control mechanism and that each will independently determine when
>>> the
>>>>>> machine is overloaded?
>>>>>>
>>>>>> Mike
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Janet P Gunn [mailto:jgunn6@csc.com]
>>>>>>> Sent: Wednesday, January 03, 2007 8:53 AM
>>>>>>> To: Darshan Bildikar
>>>>>>> Cc: 'Volker Hilt'; 'sipping'
>>>>>>> Subject: Re: [Sipping] RE: Queries and commentson 
>>>>>>> draft-hilt-sipping-overload-00.txt
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I think it is important to focus on overload of the ability to 
>>>>>>> PROCESS SIP messages.  In particular, the focus should be on the 
>>>>>>> situation where, if the SIP messages keep coming, the box will 
>>>>>>> crash (usually preceded by unproductive thrashing).
>>>>>>>
>>>>>>> As such, the mechanism and messaging must be as "lightweight"
>>>>>>> as possible, in order to avoid making the machine 
>>> congestion worse.
>>>>>>> The other kinds of resource specific overload mechanisms you 
>>>>>>> discuss sound very useful.  But I don't think it is a 
>>> good idea to 
>>>>>>> try to overload them on THIS effort.
>>>>>>>
>>>>>>> Janet
>>>>>>>
>>>>>>>
>>>>> _______________________________________________
>>>>> Sipping mailing list  
>>> https://www1.ietf.org/mailman/listinfo/sipping
>>>>> This list is for NEW development of the 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 sipping-bounces@ietf.org Mon Jan 08 10:39:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H3wb6-00049I-Mk; Mon, 08 Jan 2007 10:39:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H3wb4-00049D-BO
	for sipping@ietf.org; Mon, 08 Jan 2007 10:39:38 -0500
Received: from sccrmhc15.comcast.net ([63.240.77.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H3wb3-0003Ql-5X
	for sipping@ietf.org; Mon, 08 Jan 2007 10:39:38 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (sccrmhc15) with ESMTP
	id <2007010815393101500505b9e>; Mon, 8 Jan 2007 15:39:36 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l08FdVbM001802
	for <sipping@ietf.org>; Mon, 8 Jan 2007 10:39:31 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l08FdVRk001798;
	Mon, 8 Jan 2007 10:39:31 -0500
Date: Mon, 8 Jan 2007 10:39:31 -0500
Message-Id: <200701081539.l08FdVRk001798@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: [Sipping] Overload error codes
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

While we're at it, I think we need to define another error code.  503
means "this element is overloaded" and is supposed to have hop-by-hop
semantics.  In particular, a proxy that receives a 503 from downstream
should not send a 503 upstream, for fear of preventing upstream
elements from sending it any further traffic.

But we need a way of signalling to a UAC that its request failed due
to overload *somewhere*, much like the "reorder" signal in the PSTN.

This becomes increasingly important as proxy systems get more
sophisticated and start incorporating "failover" processing -- a
request sent on one path that has overloaded should be sent to a
failover path, but most other failures should not be.

Dale

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



From sipping-bounces@ietf.org Mon Jan 08 10:50:12 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H3wlC-0001gV-0C; Mon, 08 Jan 2007 10:50:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H3wlA-0001dp-Qa
	for sipping@ietf.org; Mon, 08 Jan 2007 10:50:04 -0500
Received: from wx-out-0506.google.com ([66.249.82.228])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H3wl8-0006SH-Fr
	for sipping@ietf.org; Mon, 08 Jan 2007 10:50:04 -0500
Received: by wx-out-0506.google.com with SMTP id h31so75575wxd
	for <sipping@ietf.org>; Mon, 08 Jan 2007 07:50:02 -0800 (PST)
Received: by 10.70.113.16 with SMTP id l16mr33488747wxc.1168271402275;
	Mon, 08 Jan 2007 07:50:02 -0800 (PST)
Received: by 10.70.40.9 with HTTP; Mon, 8 Jan 2007 07:50:02 -0800 (PST)
Message-ID: <db25d5be0701080750l37cf93b5vbe55e4a4578feaf9@mail.gmail.com>
Date: Mon, 8 Jan 2007 10:50:02 -0500
From: "Michael Slavitch" <slavitch@gmail.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
Subject: Fwd: [Sipping] RE: Queries and
	commentsondraft-hilt-sipping-overload-00.txt
In-Reply-To: <db25d5be0701080746v5d010cb1g37494696d17e198b@mail.gmail.com>
MIME-Version: 1.0
References: <24CCCC428EFEA2469BF046DB3C7A8D221414B0@namail5.corp.adobe.com>
	<45A25C5A.1040705@cisco.com>
	<db25d5be0701080746v5d010cb1g37494696d17e198b@mail.gmail.com>
X-Google-Sender-Auth: 12c53ac8564eb1dd
X-Spam-Score: 0.3 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Volker Hilt <volkerh@bell-labs.com>, sipping <sipping@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	Tom-PT Taylor <taylor@nortel.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-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-Type: multipart/mixed; boundary="===============2044787478=="
Errors-To: sipping-bounces@ietf.org

--===============2044787478==
Content-Type: multipart/alternative; 
	boundary="----=_Part_55086_19499760.1168271402139"

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

Paul wrote:

"Others won't want to be bothered with the management. Certainly in business
deployments there has been a tendency to centralize such things. Note that a
VM server isn't necessarily a "network service" - it can be viewed as simply
an alternative endpoint at an edge."

Centralization of administration, not centralization of service.  The
service can be anywhere as long as they operate under centralized control.
Centralization of administration and central servers are very different
animals.  Voice mail is but a message containing audio (and now in some
cases video or documents such as FAX).

Email servers are now trivial parts of  IT systems even for very small
businesses such as Microsoft Small Business Server and similar offerings
from IBM and RedHat.  Voice mail and unified communications are going that
way through automation.  Even in the client-server realm the amount of
effort needed to maintain a voice mail server is becoming low and getting
lower.

The DNS MX record is likely  the best implemented application-specific
extension of DNS and is well used for receipt redundancy in email systems,
which are a mish-mash of central servers (of the Yahoo/Gmail variety),
business systems that hide behind NAT tunnels,  some home systems and user
agents using IMAP or POP.

A little messy but the mail does get through with little central
co-ordination in the core as DNS MX records are not centralized as long as
the domain server is allowed to exist.  Centralized email in the core is a
recent arrival.  Most email until now was edge server based.

But what if the server is not needed because there are redundant user
agents?  There is no MX record equivalent for user agents in DNS and I doubt
there ever will be.  However there is such a thing in the land of P2P.

P2P messaging (voice, text, media),  technically identical to IM, eliminates
the need for servers except as archives and backups.

Redundancy becomes a 'so-what' in that circumstance.

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

<span class="gmail_quote"><br><br></span><span class="q">Paul wrote:<br><br>&quot;Others won&#39;t want to be bothered with the management. Certainly in business deployments there has been a tendency to centralize such things. Note that a VM server isn&#39;t necessarily a &quot;network service&quot; - it can be viewed as simply an alternative endpoint at an edge.&quot;
<br><br></span>Centralization of administration, not centralization of service.&nbsp; The service can be anywhere as long as they operate under centralized control. Centralization of administration and central servers are very different animals.&nbsp; Voice mail is but a message containing audio (and now in some cases video or documents such as FAX).&nbsp; 
<br><br>Email servers
are now trivial parts of&nbsp; IT systems even for very small businesses
such as Microsoft Small Business Server and similar offerings from IBM
and RedHat.&nbsp; Voice mail and unified communications are going that way
through automation.&nbsp; Even in the client-server realm the amount of
effort needed to maintain a voice mail server is becoming low and
getting lower.<br>

<br>The DNS MX record is likely&nbsp; the best implemented application-specific extension of DNS and is well used for receipt redundancy in email systems, which are a mish-mash of central servers (of the Yahoo/Gmail variety), business systems that hide behind NAT tunnels,&nbsp; some home systems and user agents using IMAP or POP.&nbsp; 
<br><br>A little messy but the mail does get through with little central co-ordination in the core as DNS MX records are not centralized as long as the domain server is allowed to exist.&nbsp; Centralized email in the core is a recent arrival.&nbsp; Most email until now was edge server based.&nbsp; 
<br><br>But what if the server is not needed because there are redundant user agents?&nbsp; There is no MX record equivalent for user agents in DNS and I doubt there ever will be.&nbsp; However there is such a thing in the land of P2P.&nbsp; 
<br><br>P2P messaging (voice, text, media),&nbsp; technically identical to IM, eliminates the need for servers except as archives and backups.&nbsp;&nbsp; <br><br>Redundancy becomes a &#39;so-what&#39; in that circumstance. <br><br>


------=_Part_55086_19499760.1168271402139--


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

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




From sipping-bounces@ietf.org Mon Jan 08 11:22:28 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H3xG1-0000XR-Ew; Mon, 08 Jan 2007 11:21:57 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H3xFz-0000XE-Tw
	for sipping@ietf.org; Mon, 08 Jan 2007 11:21:55 -0500
Received: from outbound.cantata.com ([208.236.123.102])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H3xFy-0007FQ-8l
	for sipping@ietf.org; Mon, 08 Jan 2007 11:21:55 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Overload error codes
Date: Mon, 8 Jan 2007 11:21:48 -0500
Message-ID: <AACB65FB607E074997DD8E482426D6F1E4C451@MA01EXCH01.Cantata.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Overload error codes
Thread-Index: AcczO0f7UQ8Rx679TLy0FstTF92NRwABQCoA
From: "Kiyanda, Bernard" <bkiyanda@cantata.com>
To: <Dale.Worley@comcast.net>,
	<sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I agree that an overloading response code would make for a clear =
transaction completion. In the case of a proxy "failing over" to some =
server/load balancing list and still unsuccessfully completing the =
transaction (e.g. mix of overload rsp and 5xx), would the proxy response =
to the initiating UA remain a 503 rsp?

Bernard

-----Original Message-----
From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]
Sent: Monday, January 08, 2007 10:40 AM
To: sipping@ietf.org
Subject: [Sipping] Overload error codes


While we're at it, I think we need to define another error code.  503
means "this element is overloaded" and is supposed to have hop-by-hop
semantics.  In particular, a proxy that receives a 503 from downstream
should not send a 503 upstream, for fear of preventing upstream
elements from sending it any further traffic.

But we need a way of signalling to a UAC that its request failed due
to overload *somewhere*, much like the "reorder" signal in the PSTN.

This becomes increasingly important as proxy systems get more
sophisticated and start incorporating "failover" processing -- a
request sent on one path that has overloaded should be sent to a
failover path, but most other failures should not be.

Dale

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org Mon Jan 08 11:43:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H3xaC-0008W1-PD; Mon, 08 Jan 2007 11:42:48 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H3xaA-0008Vs-Nx
	for sipping@ietf.org; Mon, 08 Jan 2007 11:42:46 -0500
Received: from amer-mta08.csc.com ([20.137.52.152])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H3xa8-000150-8O
	for sipping@ietf.org; Mon, 08 Jan 2007 11:42:46 -0500
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245])
	by amer-mta08.csc.com (Switch-3.1.6/Switch-3.1.0) with ESMTP id
	l08Gegx8012832
	for <sipping@ietf.org>; Mon, 8 Jan 2007 11:42:41 -0500 (EST)
In-Reply-To: <AACB65FB607E074997DD8E482426D6F1E4C451@MA01EXCH01.Cantata.com>
Subject: RE: [Sipping] Overload error codes
To: "Kiyanda, Bernard" <bkiyanda@cantata.com>
X-Mailer: Lotus Notes 652HF83 November 04, 2004
Message-ID: <OF5D52DDB8.E030AC4E-ON8525725D.005B9E87-8525725D.005BAAA6@csc.com>
From: Janet P Gunn <jgunn6@csc.com>
Date: Mon, 8 Jan 2007 11:41:15 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 7.0.2|September
	26, 2006) at 01/08/2007 11:41:33 AM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Isn't that where we started this discussion?

Janet


"Kiyanda, Bernard" <bkiyanda@cantata.com> wrote on 01/08/2007 11:21:48 AM:

> I agree that an overloading response code would make for a clear
> transaction completion. In the case of a proxy "failing over" to
> some server/load balancing list and still unsuccessfully completing
> the transaction (e.g. mix of overload rsp and 5xx), would the proxy
> response to the initiating UA remain a 503 rsp?
>
> Bernard
>
> -----Original Message-----
> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]
> Sent: Monday, January 08, 2007 10:40 AM
> To: sipping@ietf.org
> Subject: [Sipping] Overload error codes
>
>
> While we're at it, I think we need to define another error code.  503
> means "this element is overloaded" and is supposed to have hop-by-hop
> semantics.  In particular, a proxy that receives a 503 from downstream
> should not send a 503 upstream, for fear of preventing upstream
> elements from sending it any further traffic.
>
> But we need a way of signalling to a UAC that its request failed due
> to overload *somewhere*, much like the "reorder" signal in the PSTN.
>
> This becomes increasingly important as proxy systems get more
> sophisticated and start incorporating "failover" processing -- a
> request sent on one path that has overloaded should be sent to a
> failover path, but most other failures should not be.
>
> Dale
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org Mon Jan 08 12:51:53 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H3yeG-0007mu-Fm; Mon, 08 Jan 2007 12:51:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H3yeE-0007jl-6C
	for sipping@ietf.org; Mon, 08 Jan 2007 12:51:02 -0500
Received: from rwcrmhc14.comcast.net ([204.127.192.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H3ye9-0005z4-A7
	for sipping@ietf.org; Mon, 08 Jan 2007 12:51:02 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc14) with ESMTP
	id <20070108175050m1400feou2e>; Mon, 8 Jan 2007 17:50:56 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l08HonbM011471
	for <sipping@ietf.org>; Mon, 8 Jan 2007 12:50:49 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l08HonOG011467;
	Mon, 8 Jan 2007 12:50:49 -0500
Date: Mon, 8 Jan 2007 12:50:49 -0500
Message-Id: <200701081750.l08HonOG011467@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <AACB65FB607E074997DD8E482426D6F1E4C451@MA01EXCH01.Cantata.com>
	(bkiyanda@cantata.com)
Subject: Re: [Sipping] Overload error codes
References: <AACB65FB607E074997DD8E482426D6F1E4C451@MA01EXCH01.Cantata.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Kiyanda, Bernard" <bkiyanda@cantata.com>

   I agree that an overloading response code would make for a clear
   transaction completion. In the case of a proxy "failing over" to
   some server/load balancing list and still unsuccessfully completing
   the transaction (e.g. mix of overload rsp and 5xx), would the proxy
   response to the initiating UA remain a 503 rsp?

The discussion shows that by default the answer is no.  But I think
that in some special cases, such as when *all possible* downstream
paths from the proxy are overloaded, a 503 response upstream would be
reasonable, as all possible incoming traffic is affected.  This sort
of situation would be rare in servers on the wider Internet, but in
some closed systems, it might be a reasonable response.

Dale

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



From sipping-bounces@ietf.org Mon Jan 08 12:54:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H3yhG-0000dV-Ka; Mon, 08 Jan 2007 12:54:10 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H3yhE-0000ck-Fv
	for sipping@ietf.org; Mon, 08 Jan 2007 12:54:08 -0500
Received: from sccrmhc11.comcast.net ([204.127.200.81])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H3yhB-0007XD-73
	for sipping@ietf.org; Mon, 08 Jan 2007 12:54:08 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (sccrmhc11) with ESMTP
	id <2007010817540401100pmalae>; Mon, 8 Jan 2007 17:54:04 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l08Hs4bM011739
	for <sipping@ietf.org>; Mon, 8 Jan 2007 12:54:04 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l08Hs3Bg011735;
	Mon, 8 Jan 2007 12:54:04 -0500
Date: Mon, 8 Jan 2007 12:54:04 -0500
Message-Id: <200701081754.l08Hs3Bg011735@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <OF5D52DDB8.E030AC4E-ON8525725D.005B9E87-8525725D.005BAAA6@csc.com>
	(jgunn6@csc.com)
Subject: Re: [Sipping] Overload error codes
References: <OF5D52DDB8.E030AC4E-ON8525725D.005B9E87-8525725D.005BAAA6@csc.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: Janet P Gunn <jgunn6@csc.com>

   Isn't that where we started this discussion?

That might be, but I haven't seen a resolution to the response code
problem.

If an element adopts a more sophisticated overload control system, I
can envision that it might never return 503's, as it is careful to use
responses and signalling that more clearly describe its condition.
But in any case where load control or overloading is possible, we need
a "request could not be completed due to overload" response at the
end-to-end level, and RFC 3261 makes it clear that 503 is not that.

Dale

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



From sipping-bounces@ietf.org Mon Jan 08 16:16:14 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H41qN-0002sh-78; Mon, 08 Jan 2007 16:15:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H41qM-0002sZ-47
	for sipping@ietf.org; Mon, 08 Jan 2007 16:15:46 -0500
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H41qJ-0001aw-RY
	for sipping@ietf.org; Mon, 08 Jan 2007 16:15:46 -0500
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail1.lucent.com (8.13.8/IER-o) with ESMTP id l08LFgqr007366;
	Mon, 8 Jan 2007 15:15:42 -0600 (CST)
Received: from [135.180.240.247] (volker-hopc2.dnrc.bell-labs.com
	[135.180.240.247])
	by homail.ho.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l08LFgW29504; Mon, 8 Jan 2007 16:15:42 -0500 (EST)
Message-ID: <45A2B47E.9040106@bell-labs.com>
Date: Mon, 08 Jan 2007 16:15:42 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dale.Worley@comcast.net
Subject: Re: [Sipping] Overload error codes
References: <OF5D52DDB8.E030AC4E-ON8525725D.005B9E87-8525725D.005BAAA6@csc.com>
	<200701081754.l08Hs3Bg011735@dragon.ariadne.com>
In-Reply-To: <200701081754.l08Hs3Bg011735@dragon.ariadne.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 192.11.226.41
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

If a proxy that has received a 503 response is not overloaded and knows 
it can still service requests, it should not forward the 503. Instead it 
will typically create a 500 response for the request. A problem with 
this is that a proxy that is further upstream usually does not know that 
the 500 was created because of a 503 (or any other overload indication 
to be defined) by a downstream proxy. This information might be helpful 
if the upstream proxy has an alternative path it can try to reach the 
target.

This problem seems to apply in general to all cases in which a proxy 
generates an error and not the final recipient. In all those cases, 
there might be an alternative path to the target. Since there are 
different reasons why a proxy could fail besides overload, I'm not sure 
if this is really a problem that is specific to overload control or if 
this is another issue.

Volker




Dale.Worley@comcast.net wrote:
>    From: Janet P Gunn <jgunn6@csc.com>
> 
>    Isn't that where we started this discussion?
> 
> That might be, but I haven't seen a resolution to the response code
> problem.
> 
> If an element adopts a more sophisticated overload control system, I
> can envision that it might never return 503's, as it is careful to use
> responses and signalling that more clearly describe its condition.
> But in any case where load control or overloading is possible, we need
> a "request could not be completed due to overload" response at the
> end-to-end level, and RFC 3261 makes it clear that 503 is not that.
> 
> Dale
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org Mon Jan 08 17:28:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H42yN-0002th-9S; Mon, 08 Jan 2007 17:28:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H42yM-0002tc-Sh
	for sipping@ietf.org; Mon, 08 Jan 2007 17:28:06 -0500
Received: from alnrmhc11.comcast.net ([204.127.225.91])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H42yL-000592-MA
	for sipping@ietf.org; Mon, 08 Jan 2007 17:28:06 -0500
Received: from dragon.ariadne.com (failure[24.34.79.42])
	by comcast.net (alnrmhc11) with ESMTP
	id <20070108222722b1100k29rqe>; Mon, 8 Jan 2007 22:28:02 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l08MQfbM031569
	for <sipping@ietf.org>; Mon, 8 Jan 2007 17:26:41 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l08MQf8h031565;
	Mon, 8 Jan 2007 17:26:41 -0500
Date: Mon, 8 Jan 2007 17:26:41 -0500
Message-Id: <200701082226.l08MQf8h031565@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <45A2B47E.9040106@bell-labs.com> (volkerh@bell-labs.com)
Subject: Re: [Sipping] Overload error codes
References: <OF5D52DDB8.E030AC4E-ON8525725D.005B9E87-8525725D.005BAAA6@csc.com>
	<200701081754.l08Hs3Bg011735@dragon.ariadne.com>
	<45A2B47E.9040106@bell-labs.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: Volker Hilt <volkerh@bell-labs.com>

   This problem seems to apply in general to all cases in which a proxy 
   generates an error and not the final recipient. In all those cases, 
   there might be an alternative path to the target. Since there are 
   different reasons why a proxy could fail besides overload, I'm not sure 
   if this is really a problem that is specific to overload control or if 
   this is another issue.

Yes, that's true.  But most failure responses we now have can be
classified as "coming from the UA" vs. "coming from intermediate
systems".  E.g., 486 vs. 404.  Since we're now discussing overload,
I'd like to get its response codes clearly classified.

Dale

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



From sipping-bounces@ietf.org Tue Jan 09 10:58:12 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4JLX-0007FK-1g; Tue, 09 Jan 2007 10:57:07 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4JLV-0007DA-4x
	for sipping@ietf.org; Tue, 09 Jan 2007 10:57:05 -0500
Received: from dnsmx1pya.telcordia.com ([128.96.20.31])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H4JLS-00045a-Ec
	for sipping@ietf.org; Tue, 09 Jan 2007 10:57:05 -0500
Received: from rrc-dte-ieg01.cc.telcordia.com (rrc-dte-ieg01.cc.telcordia.com
	[128.96.20.22])
	by dnsmx1pya.telcordia.com (8.11.7+Sun/8.9.3) with SMTP id l09FuhJ21273
	for <sipping@ietf.org>; Tue, 9 Jan 2007 10:56:44 -0500 (EST)
Received: from rrc-dte-exbh01.dte.telcordia.com ([128.96.150.31])
	by rrc-dte-ieg01.cc.telcordia.com (SMSSMTP 4.1.9.35) with SMTP id
	M2007010910565906622
	for <sipping@ietf.org>; Tue, 09 Jan 2007 10:56:59 -0500
Received: from rrc-dte-exs01.dte.telcordia.com ([128.96.150.34]) by
	rrc-dte-exbh01.dte.telcordia.com with Microsoft SMTPSVC(6.0.3790.0); 
	Tue, 9 Jan 2007 10:53:21 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 9 Jan 2007 10:55:18 -0500
Message-ID: <A09345776B6C7A4985573569C0F3004313B4855B@rrc-dte-exs01.dte.telcordia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: seeking comments on
	draft-haluska-sipping-directory-assistance-01.txt
Thread-Index: Acc0Bo94pXjnx/X7T+GzCKNyfRNeXQ==
From: "Haluska, John J" <jhaluska@telcordia.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 09 Jan 2007 15:53:21.0891 (UTC)
	FILETIME=[49F9E330:01C73406]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cdeeb24e6b743a852c396a4af0e53c8f
Subject: [Sipping] seeking comments on
	draft-haluska-sipping-directory-assistance-01.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-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-Type: multipart/mixed; boundary="===============1278287105=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1278287105==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C73406.81E2FCFC"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C73406.81E2FCFC
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hello all,=20

=20

=20

I am seeking comments on
draft-haluska-sipping-directory-assistance-01.txt. Specifically,

=20

=20

1. Assuming that the providers involved agree, does it seem reasonable
to specify the use of the domain-name format of P-Asserted-Identity, in
order to determine the identity of the home provider? This seems to make
sense, especially given the fact that SBCs can break SIP Identity, as
pointed out in the recent identity coexistence draft.

=20

2. Does it seem reasonable to maintain a list of values for "via"
headers expected from providers from which the Operator and Information
Services Provider (OISP)  would expect to receive calls, to identify the
provider who is sending the call to the OISP? These would be providers
with whom the OISP has a pre existing relationship.

=20

3. For identifying the caller's terminal capabilities and
characteristics, we plan to specify  the use of RFC 3840 (indicating UA
capabilities in SIP) when it is supported - it is not in the current
revision of the draft. Where it is not supported, the session either
needs to do without this information, or some lookup (e.g. HSS in am IMS
environment) could be done.

=20

4. We plan to reduce the scope - it will not normatively define an
architecture (it will still describe one for the purposes of discussion)
and concentrate more on identifying existing SIP mechanisms for
conveying the required information, and will include additional call
flows.=20

=20

Any comments are greatly appreciated.

=20

Thanks

=20

John Haluska

=20

=20

=20


------_=_NextPart_001_01C73406.81E2FCFC
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

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

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I am seeking comments on
draft-haluska-sipping-directory-assistance-01.txt. =
Specifically,<o:p></o:p></span></font></p>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>1. Assuming that the providers involved agree, does =
it seem
reasonable to specify the use of the domain-name format of =
P-Asserted-Identity,
in order to determine the identity of the home provider? This seems to =
make
sense, especially given the fact that SBCs can break SIP Identity, as =
pointed
out in the recent identity coexistence =
draft.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>2. Does it seem reasonable to maintain a list of =
values for
&#8220;via&#8221; headers expected from providers from which the =
Operator and
Information Services Provider (OISP) &nbsp;would expect to receive =
calls, to
identify the provider who is sending the call to the OISP? These would =
be
providers with whom the OISP has a pre existing =
relationship.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>3. For identifying the caller&#8217;s terminal =
capabilities
and characteristics, we plan to specify &nbsp;the use of RFC 3840 =
(indicating
UA capabilities in SIP) when it is supported &#8211; it is not in the =
current
revision of the draft. Where it is not supported, the session either =
needs to
do without this information, or some lookup (e.g. HSS in am IMS =
environment)
could be done.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>4. We plan to reduce the scope &#8211; it will not
normatively define an architecture (it will still describe one for the =
purposes
of discussion) and concentrate more on identifying existing SIP =
mechanisms for
conveying the required information, and will include additional call =
flows. <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Any comments are greatly =
appreciated.<o:p></o:p></span></font></p>

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

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

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

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

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

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

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

</div>

</body>

</html>

------_=_NextPart_001_01C73406.81E2FCFC--


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

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




From sipping-bounces@ietf.org Tue Jan 09 11:38:01 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4Jz5-0000B3-1b; Tue, 09 Jan 2007 11:37:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4Jz2-000088-Po
	for sipping@ietf.org; Tue, 09 Jan 2007 11:37:56 -0500
Received: from sccrmhc15.comcast.net ([204.127.200.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4Jz1-0001ab-Jh
	for sipping@ietf.org; Tue, 09 Jan 2007 11:37:56 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (sccrmhc15) with ESMTP
	id <20070109163732015004v9lae>; Tue, 9 Jan 2007 16:37:55 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l09GbWbM014155;
	Tue, 9 Jan 2007 11:37:32 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l09GbVah014151;
	Tue, 9 Jan 2007 11:37:31 -0500
Date: Tue, 9 Jan 2007 11:37:31 -0500
Message-Id: <200701091637.l09GbVah014151@dragon.ariadne.com>
From: Dale Worley <worley@dworley.hsd1.ma.comcast.net>
To: sipping@ietf.org
In-reply-to: <459C1D99.2010504@alcatel-lucent.com> (vkg@alcatel-lucent.com)
Subject: Re: [Sipping] WGLC review of draft-ietf-sipping-spam-03
References: <459C1D99.2010504@alcatel-lucent.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: fluffy@cisco.com, mary.barnes@nortel.com, Gonzalo.Camarillo@ericsson.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I was reading this draft and noticed the following nit:

Section 3.8, page 15:

   In the case of voice, there are problems with the Turing test
   described above.  First, it is language specific.  The application
   could be made to run in different languages, if the caller indicates
   their supported languages.  This is possible in SIP, using the
   Accept-Language header field, but this is not widely used at the
   moment.

As far as I can tell, the Accept-Language header applies only to
"reason phrases" and the like in the SIP message, and not to the audio
content of the session.  See RFC 3261, section 20.3:

   20.3 Accept-Language

   The Accept-Language header field is used in requests to indicate the
   preferred languages for reason phrases, session descriptions, or
   status responses carried as message bodies in the response.  If no
   Accept-Language header field is present, the server SHOULD assume all
   languages are acceptable to the client.

Dale

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



From sipping-bounces@ietf.org Tue Jan 09 11:52:46 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4KCi-0005Eh-Pm; Tue, 09 Jan 2007 11:52:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4KCg-0005Cv-NA
	for sipping@ietf.org; Tue, 09 Jan 2007 11:52:02 -0500
Received: from alnrmhc11.comcast.net ([204.127.225.91])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4KCd-0005up-PG
	for sipping@ietf.org; Tue, 09 Jan 2007 11:52:02 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (alnrmhc11) with ESMTP
	id <20070109165144b1100k4v7de>; Tue, 9 Jan 2007 16:51:59 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l09GpibM015192;
	Tue, 9 Jan 2007 11:51:44 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l09GphBG015188;
	Tue, 9 Jan 2007 11:51:43 -0500
Date: Tue, 9 Jan 2007 11:51:43 -0500
Message-Id: <200701091651.l09GphBG015188@dragon.ariadne.com>
From: Dale Worley <worley@dworley.hsd1.ma.comcast.net>
To: sipping@ietf.org
In-reply-to: <459C1D99.2010504@alcatel-lucent.com> (vkg@alcatel-lucent.com)
Subject: Re: [Sipping] WGLC review of draft-ietf-sipping-spam-03
References: <459C1D99.2010504@alcatel-lucent.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: fluffy@cisco.com, mary.barnes@nortel.com, Gonzalo.Camarillo@ericsson.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>

   * In S3.9, one disadvantage of Payments At Risk scheme is the
      discrepancy of currency value between the sender and recipient.
      If the sender is in a third world country (albeit being financed by a
      spamming corporation in a first world country) and the receiver is
      in a first world country, then the sender really does not care about
      not getting his money refunded.  The benefactor funding the
      sender is able to use the currency valuation of his host country
      to conduct spam.  The sender deposits the payment in his local
      currency, the exchange value of which is much lower when compared to
      that of his benefactor's country.

This isn't exactly true -- if the recipient demands USD 1.00 as a
payment at risk, the currency at the location of the sender is not
important.  But the economic disparities between countries are
important, since (nominal) income levels vary between countries by a
factor of 100, and a sender in a poor country may not be willing to
risk the payment for a recipient in a rich country, even if the
message is legitimate.

This is mitigated by the fact that introductions are relatively
uncommon, and people at greatly different income levels tend to be in
different social circles.  For business purposes, a payment of even
USD 1.00 is not such a problem, as even businesses in poor countries
have ways of mobilizing money.

But perhaps I am exaggerating the problem -- cell phone use seems to
cost around USD 0.05 per minute around the world, and even in the
poorest countries, people can pay that much for calls they consider
important.  And a payment of 50,000 microcents per spam is 250 times
the facilities cost of 215 microcents per spam.

Dale

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



From sipping-bounces@ietf.org Tue Jan 09 15:45:02 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4Npd-0005t6-Oi; Tue, 09 Jan 2007 15:44:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4Npc-0005sK-A6
	for sipping@ietf.org; Tue, 09 Jan 2007 15:44:28 -0500
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4NpQ-0003pi-9x
	for sipping@ietf.org; Tue, 09 Jan 2007 15:44:18 -0500
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l09Ki5Q24098; Tue, 9 Jan 2007 15:44:05 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 9 Jan 2007 14:43:08 -0600
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB0AB3DFFD@zrc2hxm1.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Updated SIPPING WG document status - 9 Jan 2007
Thread-Index: Acc0LsUHqxhZNJBQSkyCzPYGmY4qLw==
From: "Mary Barnes" <mary.barnes@nortel.com>
To: <sipping@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
Cc: gonzalo.camarillo@ericsson.com
Subject: [Sipping] Updated SIPPING WG document status - 9 Jan 2007
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-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-Type: multipart/mixed; boundary="===============0028380996=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0028380996==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7342E.C538F7C9"

This is a multi-part message in MIME format.

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

Hi all,=20

I've updated the spreadsheets with the recent reviews:
http://www.softarmor.com/sipping/process/review_procedure.html (root
directory for reviews)

http://www.softarmor.com/sipping/process/wg-review/sipping-rt.html
(sorted by Review due date)
http://www.softarmor.com/sipping/process/wg-review/sipping-rt-rev-due.ht
ml
(sorted by revision due date)
http://www.softarmor.com/sipping/process/wg-review/sipping-rt-wglc.html
(sorted by WGLC dates)
http://www.softarmor.com/sipping/process/wg-review/sipping-rt-editor.htm
l
(sorted by document editor)


Docs planned for WGLC during January 2007:
-------------------------------------------
WGLC of the following 2 documents coordinated with WGLC of
draft-ietf-sip-policy-framework:
-  draft-ietf-sipping-policy-package-03 (originally targetted for WGLC
08 Jan - 28 Jan 2007)
-  draft-ietf-sipping-media-policy-dataset-03 (originally targetted for
WGLC 08 Jan - 28 Jan 2007)


Docs having completed WGLC during December 2006:
------------------------------------------------
The highlights of the other documents that have recently completed WGLC
since the last update are:
- draft-ietf-sipping-sbc-00  (WGLC ended 20 Dec) (Revision/re-review
required)
- draft-ietf-sipping-spam-03 (WGLC ended 31 Dec) (Revision/re-review
required)


Docs planned for WGLC between now and IETF-68:
------------------------------------------------
-  draft-ietf-sipping-ipv6-torture-tests-00 (WGLC 29 Jan - 16 Feb 2007)
-  draft-ietf-sipping-cc-framework-07 (WGLC 5 Feb - 26 Feb 2007)
-  draft-ietf-sipping-nat-scenarios-05 (WGLC 8 Mar - 29 March 2007)


Other important document timelines:
-----------------------------------
- draft-ietf-sipping-config-fw-10 (Initial revamped version from design
team due around 22 Jan 2007)
- draft-ietf-sipping-config-fw-11 (Updated version based on WG feedback
due around 5 March 2007)

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

As always, if you're interested in being an offical reviewer for a
particular
document, please contact the chairs.  For folks that aren't official=20
reviewers, your comments are always welcome and of course, the schedule=20
doesn't preclude discussion or review of other relevant documents at
anytime.  =20

Regards,
Mary
SIPPING WG co-chair


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.14">
<TITLE>Updated SIPPING WG document status - 9 Jan 2007</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

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

<P><FONT SIZE=3D2 FACE=3D"Courier New">I've updated the spreadsheets =
with the recent reviews:</FONT>

<BR><A =
HREF=3D"http://www.softarmor.com/sipping/process/review_procedure.html"><=
U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">http://www.softarmor.com/sipping/process/review_procedure.html</FONT=
></U></A><FONT SIZE=3D2 FACE=3D"Courier New"> (root</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">directory for reviews)</FONT>
</P>

<P><A =
HREF=3D"http://www.softarmor.com/sipping/process/wg-review/sipping-rt.htm=
l"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">http://www.softarmor.com/sipping/process/wg-review/sipping-rt.html</=
FONT></U></A>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">(sorted by Review due =
date)</FONT>

<BR><A =
HREF=3D"http://www.softarmor.com/sipping/process/wg-review/sipping-rt-rev=
-due.html"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">http://www.softarmor.com/sipping/process/wg-review/sipping-rt-rev-du=
e.html</FONT></U></A>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">(sorted by revision due =
date)</FONT>

<BR><A =
HREF=3D"http://www.softarmor.com/sipping/process/wg-review/sipping-rt-wgl=
c.html"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">http://www.softarmor.com/sipping/process/wg-review/sipping-rt-wglc.h=
tml</FONT></U></A>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">(sorted by WGLC dates)</FONT>

<BR><A =
HREF=3D"http://www.softarmor.com/sipping/process/wg-review/sipping-rt-edi=
tor.html"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">http://www.softarmor.com/sipping/process/wg-review/sipping-rt-editor=
.html</FONT></U></A>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">(sorted by document =
editor)</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Docs planned for WGLC during =
January 2007:</FONT>

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

<BR><FONT SIZE=3D2 FACE=3D"Courier New">WGLC of the following 2 =
documents coordinated with WGLC of =
draft-ietf-sip-policy-framework:</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">-&nbsp; =
draft-ietf-sipping-policy-package-03 (originally targetted for WGLC 08 =
Jan - 28 Jan 2007)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">-&nbsp; =
draft-ietf-sipping-media-policy-dataset-03 (originally targetted for =
WGLC 08 Jan - 28 Jan 2007)</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Docs having completed WGLC during =
December 2006:</FONT>

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

<BR><FONT SIZE=3D2 FACE=3D"Courier New">The highlights of the other =
documents that have recently completed WGLC since the last update =
are:</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">- =
draft-ietf-sipping-sbc-00&nbsp; (WGLC ended 20 Dec) (Revision/re-review =
required)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">- draft-ietf-sipping-spam-03 =
(WGLC ended 31 Dec) (Revision/re-review required)</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Docs planned for WGLC between now =
and IETF-68:</FONT>

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

<BR><FONT SIZE=3D2 FACE=3D"Courier New">-&nbsp; =
draft-ietf-sipping-ipv6-torture-tests-00 (WGLC 29 Jan - 16 Feb =
2007)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">-&nbsp; =
draft-ietf-sipping-cc-framework-07 (WGLC 5 Feb - 26 Feb 2007)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">-&nbsp; =
draft-ietf-sipping-nat-scenarios-05 (WGLC 8 Mar - 29 March 2007)</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Other important document =
timelines:</FONT>

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

<BR><FONT SIZE=3D2 FACE=3D"Courier New">- =
draft-ietf-sipping-config-fw-10 (Initial revamped version from design =
team due around 22 Jan 2007)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">- =
draft-ietf-sipping-config-fw-11 (Updated version based on WG feedback =
due around 5 March 2007)</FONT>
</P>

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

<P><FONT SIZE=3D2 FACE=3D"Courier New">As always, if you're interested =
in being an offical reviewer for a particular</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">document, please contact the =
chairs.&nbsp; For folks that aren't official </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">reviewers, your comments are =
always welcome and of course, the schedule </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">doesn't preclude discussion or =
review of other relevant documents at anytime.&nbsp;&nbsp; </FONT>
</P>

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

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

<BR><FONT SIZE=3D2 FACE=3D"Courier New">SIPPING WG co-chair</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7342E.C538F7C9--


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

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




From sipping-bounces@ietf.org Tue Jan 09 17:21:29 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4PLP-0002V2-VI; Tue, 09 Jan 2007 17:21:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4PLP-0002Ux-9d
	for sipping@ietf.org; Tue, 09 Jan 2007 17:21:23 -0500
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4PLO-0000i6-2N
	for sipping@ietf.org; Tue, 09 Jan 2007 17:21:23 -0500
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail1.lucent.com (8.13.8/IER-o) with ESMTP id l09MLJU4024702;
	Tue, 9 Jan 2007 16:21:19 -0600 (CST)
Received: from [135.180.240.247] (volker-hopc2.dnrc.bell-labs.com
	[135.180.240.247])
	by homail.ho.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l09MLJW13697; Tue, 9 Jan 2007 17:21:19 -0500 (EST)
Message-ID: <45A4155F.8060407@bell-labs.com>
Date: Tue, 09 Jan 2007 17:21:19 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dale.Worley@comcast.net
Subject: Re: [Sipping] Overload error codes
References: <OF5D52DDB8.E030AC4E-ON8525725D.005B9E87-8525725D.005BAAA6@csc.com>	<200701081754.l08Hs3Bg011735@dragon.ariadne.com>	<45A2B47E.9040106@bell-labs.com>
	<200701082226.l08MQf8h031565@dragon.ariadne.com>
In-Reply-To: <200701082226.l08MQf8h031565@dragon.ariadne.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 192.11.226.41
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dale.Worley@comcast.net wrote:
>    From: Volker Hilt <volkerh@bell-labs.com>
> 
>    This problem seems to apply in general to all cases in which a proxy 
>    generates an error and not the final recipient. In all those cases, 
>    there might be an alternative path to the target. Since there are 
>    different reasons why a proxy could fail besides overload, I'm not sure 
>    if this is really a problem that is specific to overload control or if 
>    this is another issue.
> 
> Yes, that's true.  But most failure responses we now have can be
> classified as "coming from the UA" vs. "coming from intermediate
> systems".  E.g., 486 vs. 404.  Since we're now discussing overload,
> I'd like to get its response codes clearly classified.
> 
I think overload can occur in the UAS and in an intermediate system. So 
I don't think a new overload response code would really fall into one of 
the categories "coming from the UA" or "coming from intermediate 
systems". However, I agree that it may still make sense to make it 
explicit that a request has been rejected because of overload instead of 
using the more generic 500 response. An alternative to a new response 
code could be the use of a warning header in a 500 response.

Volker


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



From sipping-bounces@ietf.org Tue Jan 09 18:00:48 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4Px9-00037B-Qb; Tue, 09 Jan 2007 18:00:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4Px7-00036c-PY
	for sipping@ietf.org; Tue, 09 Jan 2007 18:00:21 -0500
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4Px6-0003ri-Dp
	for sipping@ietf.org; Tue, 09 Jan 2007 18:00:21 -0500
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l09N0FkY022525; 
	Tue, 9 Jan 2007 17:00:15 -0600 (CST)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90])
	by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l09N0Au19711; Tue, 9 Jan 2007 17:00:15 -0600 (CST)
Message-ID: <45A41E7A.3080804@alcatel-lucent.com>
Date: Tue, 09 Jan 2007 17:00:10 -0600
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dale Worley <worley@dworley.hsd1.ma.comcast.net>
Subject: Re: [Sipping] WGLC review of draft-ietf-sipping-spam-03
References: <459C1D99.2010504@alcatel-lucent.com>
	<200701091651.l09GphBG015188@dragon.ariadne.com>
In-Reply-To: <200701091651.l09GphBG015188@dragon.ariadne.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dale Worley wrote:
> This isn't exactly true -- if the recipient demands USD 1.00 as a
> payment at risk, the currency at the location of the sender is not
> important.  

In the Payments at Risk scheme, the recipient does not get to
demand the payment he or she will accept.  That attribute is
left to the sender of the request.  Thus, if the sender of the
request is in a low-cost country, then the value would be
chosen accordingly.

> This is mitigated by the fact that introductions are relatively
> uncommon, and people at greatly different income levels tend to be in
> different social circles.  

That will depend; a software engineer practicing in a low-cost
country and one practicing in a high-cost country could be
considered to be in the same social circle, albeit different
income level.

Interestingly enough, in the Payments at Risk scheme, the
refunding portion is optional; so you may have an unscrupulous
receiver that accepts non-spam emails and never refunds the
money ;-)  Of course, for email spam, it would have to be made
mandatory.

Ciao.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs

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



From sipping-bounces@ietf.org Tue Jan 09 18:07:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4Q3p-0005k8-BY; Tue, 09 Jan 2007 18:07:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4Q3o-0005jq-5b
	for sipping@ietf.org; Tue, 09 Jan 2007 18:07:16 -0500
Received: from alnrmhc13.comcast.net ([206.18.177.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4Q3m-0005A4-Uf
	for sipping@ietf.org; Tue, 09 Jan 2007 18:07:16 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (alnrmhc13) with ESMTP
	id <20070109230651b1300qctc7e>; Tue, 9 Jan 2007 23:07:12 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l09N6pbM010039
	for <sipping@ietf.org>; Tue, 9 Jan 2007 18:06:51 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l09N6pgm010035;
	Tue, 9 Jan 2007 18:06:51 -0500
Date: Tue, 9 Jan 2007 18:06:51 -0500
Message-Id: <200701092306.l09N6pgm010035@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <A09345776B6C7A4985573569C0F3004313B4855B@rrc-dte-exs01.dte.telcordia.com>
	(jhaluska@telcordia.com)
Subject: Re: [Sipping] seeking comments on
	draft-haluska-sipping-directory-assistance-01.txt
References: <A09345776B6C7A4985573569C0F3004313B4855B@rrc-dte-exs01.dte.telcordia.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Haluska, John J" <jhaluska@telcordia.com>

   I am seeking comments on
   draft-haluska-sipping-directory-assistance-01.txt.

I'm mystified by what this draft is trying to accomplish.  If a SIP
user wishes to contact an Information Service, he can just issue an
INVITE to the service's URI.  This draft seems to assume that all
information services are integrated into the fabric of the transport
network, which is a poor architectural decision with adverse economic
consequences.

At the very least, you can correct the first sentence of the abstract:

   Information Services are services whereby information is provided by 
   the network in response to user requests

By definition, a network doesn't *provide* information, it
*transports* it.  Network endpoints provide information.

OK, I'm being cranky here.  But if all this apparatus is necessary,
there must be some requirements that I don't see stated clearly.

Dale

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



From sipping-bounces@ietf.org Wed Jan 10 13:11:36 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4hu8-0004S0-Ei; Wed, 10 Jan 2007 13:10:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4hu4-0004P2-Rf
	for sipping@ietf.org; Wed, 10 Jan 2007 13:10:24 -0500
Received: from dnsmx1rrc.telcordia.com ([128.96.20.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4htr-00039d-VQ
	for sipping@ietf.org; Wed, 10 Jan 2007 13:10:24 -0500
Received: from rrc-dte-ieg01.cc.telcordia.com (rrc-dte-ieg01.cc.telcordia.com
	[128.96.20.22])
	by dnsmx1rrc.telcordia.com (8.11.7+Sun/8.9.3) with SMTP id l0AIA8v03946
	for <sipping@ietf.org>; Wed, 10 Jan 2007 13:10:08 -0500 (EST)
Received: from rrc-dte-exbh01.dte.telcordia.com ([128.96.150.31])
	by rrc-dte-ieg01.cc.telcordia.com (SMSSMTP 4.1.9.35) with SMTP id
	M2007011013102428578
	for <sipping@ietf.org>; Wed, 10 Jan 2007 13:10:24 -0500
Received: from rrc-dte-exs01.dte.telcordia.com ([128.96.150.34]) by
	rrc-dte-exbh01.dte.telcordia.com with Microsoft SMTPSVC(6.0.3790.0); 
	Wed, 10 Jan 2007 13:10:54 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: Re: Re: [Sipping] seeking comments on
	draft-haluska-sipping-directory-assistance-01.txt
Date: Wed, 10 Jan 2007 13:10:22 -0500
Message-ID: <A09345776B6C7A4985573569C0F3004313B4906C@rrc-dte-exs01.dte.telcordia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: Re: [Sipping] seeking comments on
	draft-haluska-sipping-directory-assistance-01.txt
Thread-Index: Acc04pf2nFf+5cwPR7acSdcI41DfrA==
From: "Haluska, John J" <jhaluska@telcordia.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 10 Jan 2007 18:10:54.0442 (UTC)
	FILETIME=[AB4AFCA0:01C734E2]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 72be645574b2b4b84446d27f730bf563
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-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-Type: multipart/mixed; boundary="===============1292983768=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1292983768==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C734E2.99511134"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C734E2.99511134
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Dale

=20

Thank you for taking the time to comment on this draft.

=20

=20

>I'm mystified by what this draft is trying to accomplish.  If a SIP
>user wishes to contact an Information Service, he can just issue an
>INVITE to the service's URI.  This draft seems to assume that all
>information services are integrated into the fabric of the transport
>network, which is a poor architectural decision with adverse economic
>consequences.

=20

=20

Currently, services like Directory Assistance (DA) and Operator Services
often use traditional interfaces that are challenging to evolve. What we
are ultimately trying to do is specify how these existing services  and
future advanced DA services could be implemented in a standardized way
using SIP interfaces. This would simplify the integration efforts for
the vendors and service providers. Also, it would simplify the
connectivity to such services via SIP, rather than requiring VSPs to
implement customized solutions or hand off via a PSTN interface. Going
forward, it would allow DA providers to deploy more advanced services by
taking advantage of SIP, rather than simply replicating what is
currently possible on the PSTN. I am referring to "DA" here, but there
are other services to which this all applies. We would hope that the end
results of this would result in positive economic consequences.

=20

=20

>At the very least, you can correct the first sentence of the abstract:
>=20
>   Information Services are services whereby information is provided by

>   the network in response to user requests
>=20
>By definition, a network doesn't *provide* information, it
>*transports* it.  Network endpoints provide information.

=20

Definitely in the next revision, we plan to reduce the scope,
concentrating on solutions to the technical problems. The abstract would
be updated, and your comments are well taken. The draft definitely does
not mean to imply that the services are woven into the fabric of the
transport network, if it comes across that way then we need to change
it. Nor should it come across as implying that layer 3 entities or the
network itself are providing these services. So the wording will
definitely change.

=20

=20

=20

>OK, I'm being cranky here.  But if all this apparatus is necessary,
>there must be some requirements that I don't see stated clearly.

=20

Not at all, we need these kinds of comments to make sure things are
clear. Again, in the next revision of the draft, we'll make sure these
requirements are very clear.=20

=20

The draft covers several areas, but a good amount of text is devoted to
handling different network scenarios, which are driven by different
business relationships. It probably does seem like a lot of complexity,
so I'll give some explanations here.=20

=20

The draft is inclusive of several business models. It includes the
Service URN, so that a UA could make use of that mechanism to resolve
the provider's URI to make the call directly as you indicate, if the
infrastructure to support that is in place. Also, if a user's provider
has the ability to provide such services natively, then little else is
needed to get the caller to the service. So the simple case is included.

=20

Services like DA require specialized infrastructure as well as
personnel, so many voice providers farm this out to third parties. The
draft includes the model where the subscriber's provider has a business
agreement with a separate DA provider. This is commonplace today both in
the PSTN and also with VOIP providers. This is what we are calling the
"direct" third party provider in the draft. An example would be provider
A has a relationship with DA provider C to handle DA queries for its
customers.

=20

The draft is also inclusive of the model where the subscriber's provider
for whatever reason does not have any agreement with a DA provider. But
it does have an agreement with another provider, which in turn has such
agreements. This facilitates among other things the "little guy" being
able to offer such services to his customers without having to have an
arrangement directly with a DA provider. This is what we are calling the
"indirect" third party provider. An example would be where provider A
has an agreement with provider B for any services it cannot provide
natively, including DA. Provider B might provide some services natively,
and might farm others out. For instance it might farm out DA to provider
C.

=20

Services like DA are usually branded - the identity of the caller's
provider impacts how the call is processed, based on the agreement
between the caller's provider and the DA provider. One example is that
providers want the DA provider to play a custom greeting when providing
service to their customers. So, a subscriber of provider A makes a 411
call for DA, and provider A hands the call off to DA provider C with
whom it has such arrangements. Provider A wants the customer to be
greeted with some custom greeting like "thank you for using provider A".
Also, provider A may have contracted for other services such as call
completion, where once the requested listing is provided, the DA
provider offers to complete the call to that party, so the user need not
remember the number, hang up, and then dial the number. Another example
might be that DA providers could have different default languages for
each provider with whom they have agreements (this would not rule out a
per subscriber language preference).=20

=20

In the indirect model, we allow for the processing to take account of
both the caller's provider as well as the provider with the direct
relationship to the DA provider.=20

=20

The draft is not trying to weave these complicated relationships into
the fabric - it just needs be inclusive of them as well as the simple
case. It sounds like a lot of complexity, but in the end we are just
trying to specify ways to use existing SIP mechanisms to support them.
>From my original email, this currently comes down to specifying the use
of P-Asserted-Identity and Via headers, with a few constraints.=20

=20

We need to make sure this all comes through clearly in the draft. I'm
hoping that the reduction in scope in the next revision will help to
make this come through more clearly.

=20

=20

I would also appreciate any technical comments on the questions in my
previous post:

=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D

I am seeking comments on
draft-haluska-sipping-directory-assistance-01.txt. Specifically,

=20

1. Assuming that the providers involved agree, does it seem reasonable
to specify the use of the domain-name format of P-Asserted-Identity, in
order to determine the identity of the home provider? This seems to make
sense, especially given the fact that SBCs can break SIP Identity, as
pointed out in the recent identity coexistence draft.

=20

2. Does it seem reasonable to maintain a list of values for "via"
headers expected from providers from which the Operator and Information
Services Provider (OISP)  would expect to receive calls, to identify the
provider who is sending the call to the OISP? These would be providers
with whom the OISP has a pre existing relationship.

=20

3. For identifying the caller's terminal capabilities and
characteristics, we plan to specify  the use of RFC 3840 (indicating UA
capabilities in SIP) when it is supported - it is not in the current
revision of the draft. Where it is not supported, the session either
needs to do without this information, or some lookup (e.g. HSS in am IMS
environment) could be done.

=20

4. We plan to reduce the scope - it will not normatively define an
architecture (it will still describe one for the purposes of discussion)
and concentrate more on identifying existing SIP mechanisms for
conveying the required information, and will include additional call
flows.=20

=20

Any comments are greatly appreciated.

=20

=20

=20

=20

=20

=20

=20


------_=_NextPart_001_01C734E2.99511134
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0pt;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thank you for taking the time to comment on this =
draft.<o:p></o:p></span></font></p>

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

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

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;I'm mystified by what this draft is =
trying to accomplish.&nbsp; If a =
SIP<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt;user =
wishes to contact an Information Service, he can just issue =
an<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;INVITE to the service's URI.&nbsp; This =
draft seems to assume that all<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;information services are integrated into =
the fabric of the transport<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;network, which is a poor architectural =
decision with adverse economic<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;consequences.<o:p></o:p></span></font></pr=
e>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Currently, services like Directory Assistance (DA) =
and
Operator Services often use traditional interfaces that are challenging =
to
evolve. What we are ultimately trying to do is specify how these =
existing
services&nbsp; and future advanced DA services could be implemented in a
standardized way using SIP interfaces. This would simplify the =
integration
efforts for the vendors and service providers. Also, it would simplify =
the
connectivity to such services via SIP, rather than requiring VSPs to =
implement
customized solutions or hand off via a PSTN interface. Going forward, it =
would
allow DA providers to deploy more advanced services by taking advantage =
of SIP,
rather than simply replicating what is currently possible on the PSTN. I =
am
referring to &#8220;DA&#8221; here, but there are other services to =
which this
all applies. We would hope that the end results of this would result in
positive economic consequences.<o:p></o:p></span></font></p>

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

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

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;At the very least, you can correct the =
first sentence of the abstract:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></pre><pre>=
<font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;&nbsp;&nbsp; Information Services are =
services whereby information is provided by =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;&nbsp;&nbsp; the network in response to =
user requests<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></pre><pre>=
<font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt;By =
definition, a network doesn't *provide* information, =
it<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;*transports* it.&nbsp; Network endpoints =
provide information.<o:p></o:p></span></font></pre>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Definitely in the next revision, we plan to reduce =
the
scope, concentrating on solutions to the technical problems. The =
abstract would
be updated, and your comments are well taken. The draft definitely does =
not
mean to imply that the services are woven into the fabric of the =
transport
network, if it comes across that way then we need to change it. Nor =
should it
come across as implying that layer 3 entities or the network itself are
providing these services. So the wording will definitely =
change.<o:p></o:p></span></font></p>

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

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

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

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt;OK, I'm being cranky here.&nbsp; But if =
all this apparatus is =
necessary,<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt;there =
must be some requirements that I don't see stated =
clearly.<o:p></o:p></span></font></pre>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Not at all, we need these kinds of comments to make =
sure
things are clear. Again, in the next revision of the draft, we&#8217;ll =
make sure
these requirements are very clear. <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The draft covers several areas, but a good amount of =
text is
devoted to handling different network scenarios, which are driven by =
different
business relationships. It probably does seem like a lot of complexity, =
so
I&#8217;ll give some explanations here. <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The draft is inclusive of several business models. It
includes the Service URN, so that a UA could make use of that mechanism =
to
resolve the provider&#8217;s URI to make the call directly as you =
indicate, if
the infrastructure to support that is in place. Also, if a user&#8217;s
provider has the ability to provide such services natively, then little =
else is
needed to get the caller to the service. So the simple case is =
included.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Services like DA require specialized infrastructure =
as well
as personnel, so many voice providers farm this out to third parties. =
The draft
includes the model where the subscriber&#8217;s provider has a business
agreement with a separate DA provider. This is commonplace today both in =
the
PSTN and also with VOIP providers. This is what we are calling the
&#8220;direct&#8221; third party provider in the draft. An example would =
be
provider A has a relationship with DA provider C to handle DA queries =
for its
customers.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The draft is also inclusive of the model where the
subscriber&#8217;s provider for whatever reason does not have any =
agreement
with a DA provider. But it does have an agreement with another provider, =
which
in turn has<font color=3Dblue><span =
style=3D'color:blue'>&nbsp;</span></font>such
agreements. This facilitates among other things the &#8220;little =
guy&#8221;
being able to offer such services to his customers without having to =
have an
arrangement directly with a DA provider. This is what we are calling the
&#8220;indirect&#8221; third party provider. An example would be where =
provider
A has an agreement with provider B for any services it cannot provide =
natively,
including DA. Provider B might provide some services natively, and might =
farm
others out. For instance it might farm out DA to provider =
C.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Services like DA are usually branded &#8211; the =
identity of
the caller&#8217;s provider impacts how the call is processed, based on =
the
agreement between the caller&#8217;s provider and the DA provider. One =
example
is that providers want the DA provider to play a custom greeting when =
providing
service to their customers. So, a subscriber of provider A makes a =
411&nbsp;call
for DA, and provider A hands the call off to DA provider C with whom it =
has
such arrangements. Provider A wants the customer to be greeted with some =
custom
greeting like &#8220;thank you for using provider A&#8221;. Also, =
provider A
may have contracted for other services such as call completion, where =
once the
requested listing is provided, the DA provider offers to complete the =
call to
that party, so the user need not remember the number, hang up, and then =
dial
the number. Another example might be that DA providers could have =
different
default languages for each provider with whom they have agreements (this =
would
not rule out a per subscriber language preference). =
<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In the indirect model, we allow for the processing to =
take
account of both the caller&#8217;s provider as well as the provider with =
the
direct relationship to the DA provider. <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The draft is not trying to weave these complicated
relationships into the fabric &#8211; it just needs be inclusive of them =
as
well as the simple case. It sounds like a lot of complexity, but in the =
end we
are just trying to specify ways to use existing SIP mechanisms to =
support them.
>From my original email, this currently comes down to specifying the use =
of
P-Asserted-Identity and Via headers, with a few constraints. =
<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>We need to make sure this all comes through clearly =
in the
draft. I&#8217;m hoping that the reduction in scope in the next revision =
will
help to make this come through more =
clearly.<o:p></o:p></span></font></p>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I would also appreciate any technical comments on the =
questions
in my previous post:<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>=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=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=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span><=
/font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>I am seeking
comments on draft-haluska-sipping-directory-assistance-01.txt. =
Specifically,<U1:P></U1:P></span></font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><U1:P>&nbsp;</U1:P></span></=
font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>1. Assuming
that the providers involved agree, does it seem reasonable to specify =
the use
of the domain-name format of P-Asserted-Identity, in order to determine =
the
identity of the home provider? This seems to make sense, especially =
given the
fact that SBCs can break SIP Identity, as pointed out in the recent =
identity
coexistence draft.<U1:P></U1:P></span></font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><U1:P>&nbsp;</U1:P></span></=
font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>2. Does it
seem reasonable to maintain a list of values for &#8220;via&#8221; =
headers
expected from providers from which the Operator and Information Services
Provider (OISP) &nbsp;would expect to receive calls, to identify the =
provider
who is sending the call to the OISP? These would be providers with whom =
the
OISP has a pre existing =
relationship.<U1:P></U1:P></span></font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><U1:P>&nbsp;</U1:P></span></=
font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>3. For
identifying the caller&#8217;s terminal capabilities and =
characteristics, we
plan to specify &nbsp;the use of RFC 3840 (indicating UA capabilities in =
SIP)
when it is supported &#8211; it is not in the current revision of the =
draft.
Where it is not supported, the session either needs to do without this
information, or some lookup (e.g. HSS in am IMS environment) could be =
done.<U1:P></U1:P></span></font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><U1:P>&nbsp;</U1:P></span></=
font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>4. We plan
to reduce the scope &#8211; it will not normatively define an =
architecture (it
will still describe one for the purposes of discussion) and concentrate =
more on
identifying existing SIP mechanisms for conveying the required =
information, and
will include additional call flows. =
<U1:P></U1:P></span></font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><U1:P>&nbsp;</U1:P></span></=
font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Any comments
are greatly appreciated.<U1:P></U1:P></span></font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><U1:P>&nbsp;</U1:P></span></=
font><o:p></o:p></p>

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

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

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

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

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

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

</div>

</body>

</html>

------_=_NextPart_001_01C734E2.99511134--


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

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




From sipping-bounces@ietf.org Wed Jan 10 13:49:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4iVd-0007Ze-8r; Wed, 10 Jan 2007 13:49:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4iVc-0007Yr-5Y
	for sipping@ietf.org; Wed, 10 Jan 2007 13:49:12 -0500
Received: from alnrmhc12.comcast.net ([204.127.225.92])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4iVa-0008K9-TM
	for sipping@ietf.org; Wed, 10 Jan 2007 13:49:12 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (alnrmhc12) with ESMTP
	id <20070110184900b1200brv90e>; Wed, 10 Jan 2007 18:49:10 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l0AImSbM031280
	for <sipping@ietf.org>; Wed, 10 Jan 2007 13:48:28 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l0AImS2I031276;
	Wed, 10 Jan 2007 13:48:28 -0500
Date: Wed, 10 Jan 2007 13:48:28 -0500
Message-Id: <200701101848.l0AImS2I031276@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <A09345776B6C7A4985573569C0F3004313B4906C@rrc-dte-exs01.dte.telcordia.com>
	(jhaluska@telcordia.com)
Subject: Re: [Sipping] seeking comments on
	draft-haluska-sipping-directory-assistance-01.txt
References: <A09345776B6C7A4985573569C0F3004313B4906C@rrc-dte-exs01.dte.telcordia.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Haluska, John J" <jhaluska@telcordia.com>

   Currently, services like Directory Assistance (DA) and Operator Services
   often use traditional interfaces that are challenging to evolve. What we
   are ultimately trying to do is specify how these existing services  and
   future advanced DA services could be implemented in a standardized way
   using SIP interfaces. This would simplify the integration efforts for
   the vendors and service providers.

OK, so much of this draft is "inward facing", toward the
community/market of existing DA vendors/providers, and much of what it
addresses is migrating an existing architecture to the SIP universe.
Hence, when a naive "outside" reader (e.g., me) reads it, it appears
to be a straitjacket, it documents only one approach to implementing
DA, but that's because what it documents is parallel to the existing
DA infrastructure.

   Definitely in the next revision, we plan to reduce the scope,
   concentrating on solutions to the technical problems. The abstract would
   be updated, and your comments are well taken. The draft definitely does
   not mean to imply that the services are woven into the fabric of the
   transport network, if it comes across that way then we need to change
   it. Nor should it come across as implying that layer 3 entities or the
   network itself are providing these services. So the wording will
   definitely change.

   The draft is inclusive of several business models. [...]  The draft
   includes the model where the subscriber's provider has a business
   agreement with a separate DA provider. [...]

How does this relate to what I expect to be the most common business
model, where the user contracts with a DA provider directly, and the
(transport) service provider is used only to move bits between the
two?  (This would be somewhat like long-distance calling in the US,
which is typically not subcontracted through one's local service
provider.)

(I would expect the commonest exception to the above to be when the
service provider has bundled DA services and offers them at a
discounted price.)

Perhaps another way to look at this is this:  You're working on two
problems, which may be intertwined:  One is the technological
specifics of providing DA services, but the other is the technological
specifics of supporting various business models (really, charging
schemes).  I suspect the DA services themselves are fairly
straightforward, but the charging schemes are a nearly virgin area of
research.  The interesting consequence of looking at it this way is
that the charging scheme work may be applicable to a much wider range
of problems than you are addressing now.

Dale

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



From sipping-bounces@ietf.org Wed Jan 10 14:05:05 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4ikh-0005zJ-Va; Wed, 10 Jan 2007 14:04:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4ikh-0005z8-3N
	for sipping@ietf.org; Wed, 10 Jan 2007 14:04:47 -0500
Received: from rwcrmhc14.comcast.net ([204.127.192.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4ikf-00023t-R3
	for sipping@ietf.org; Wed, 10 Jan 2007 14:04:47 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc14) with ESMTP
	id <20070110190439m1400ffclfe>; Wed, 10 Jan 2007 19:04:44 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l0AJ3cbM032414
	for <sipping@ietf.org>; Wed, 10 Jan 2007 14:03:38 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l0AJ3KFU032393;
	Wed, 10 Jan 2007 14:03:20 -0500
Date: Wed, 10 Jan 2007 14:03:20 -0500
Message-Id: <200701101903.l0AJ3KFU032393@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <45A41E7A.3080804@alcatel-lucent.com> (vkg@alcatel-lucent.com)
Subject: Re: [Sipping] WGLC review of draft-ietf-sipping-spam-03
References: <459C1D99.2010504@alcatel-lucent.com>
	<200701091651.l09GphBG015188@dragon.ariadne.com>
	<45A41E7A.3080804@alcatel-lucent.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>

   In the Payments at Risk scheme, the recipient does not get to
   demand the payment he or she will accept.  That attribute is
   left to the sender of the request.  Thus, if the sender of the
   request is in a low-cost country, then the value would be
   chosen accordingly.

Although isn't the use of Payments at Risk ultimately enforced by the
recipient's UA verifying that the payment is high enough (or that the
sender is whitelisted)?  So the recipient has final say whether the
payment is adequate.

   > This is mitigated by the fact that introductions are relatively
   > uncommon, and people at greatly different income levels tend to be in
   > different social circles.  

   That will depend; a software engineer practicing in a low-cost
   country and one practicing in a high-cost country could be
   considered to be in the same social circle, albeit different
   income level.

Good point.  (Though the reports I hear are that the nominal pay rates
of software engineers in different countries are converging more than
one would expect due to vigorous outsourcing.)

   Interestingly enough, in the Payments at Risk scheme, the
   refunding portion is optional; so you may have an unscrupulous
   receiver that accepts non-spam emails and never refunds the
   money ;-)

Though I suppose that the sender could then blacklist the recipient.
But it's a risk that has to be considered.

Could this be used to generate "inverse spam", where someone posts an
attractive public solicitation.  Thousands of people send introductory
e-mail, enclosing their Payment at Risk of (say) USD 0.05.  Then the
recipient just keeps the money.

Dale

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



From sipping-bounces@ietf.org Wed Jan 10 14:59:11 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4jad-0005bb-5Y; Wed, 10 Jan 2007 14:58:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4jac-0005bV-6u
	for sipping@ietf.org; Wed, 10 Jan 2007 14:58:26 -0500
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4jaZ-0008S8-TV
	for sipping@ietf.org; Wed, 10 Jan 2007 14:58:26 -0500
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id l0AJwGnx021360; 
	Wed, 10 Jan 2007 13:58:16 -0600 (CST)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90])
	by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l0AJwGu05890; Wed, 10 Jan 2007 13:58:16 -0600 (CST)
Message-ID: <45A54558.2000200@alcatel-lucent.com>
Date: Wed, 10 Jan 2007 13:58:16 -0600
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dale.Worley@comcast.net
Subject: Re: [Sipping] WGLC review of draft-ietf-sipping-spam-03
References: <459C1D99.2010504@alcatel-lucent.com>	<200701091651.l09GphBG015188@dragon.ariadne.com>	<45A41E7A.3080804@alcatel-lucent.com>
	<200701101903.l0AJ3KFU032393@dragon.ariadne.com>
In-Reply-To: <200701101903.l0AJ3KFU032393@dragon.ariadne.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dale.Worley@comcast.net wrote:
>    From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
> 
>    In the Payments at Risk scheme, the recipient does not get to
>    demand the payment he or she will accept.  That attribute is
>    left to the sender of the request.  Thus, if the sender of the
>    request is in a low-cost country, then the value would be
>    chosen accordingly.
> 
> Although isn't the use of Payments at Risk ultimately enforced by the
> recipient's UA verifying that the payment is high enough (or that the
> sender is whitelisted)?  So the recipient has final say whether the
> payment is adequate.

There is a difference: yes, the recipient has a final say whether
the payment is adequate, but he (or she) does not have a final
say in *determining* the amount of that payment (at least, that is
how I interpret this scheme when I read the paper.)

> Could this be used to generate "inverse spam", where someone posts an
> attractive public solicitation.  Thousands of people send introductory
> e-mail, enclosing their Payment at Risk of (say) USD 0.05.  Then the
> recipient just keeps the money.

Oh, neat.  I like this inverse spam idea.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs

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



From sipping-bounces@ietf.org Thu Jan 11 14:07:37 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H55GY-0004c2-Ib; Thu, 11 Jan 2007 14:07:10 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H55GW-0004bm-6t
	for sipping@ietf.org; Thu, 11 Jan 2007 14:07:08 -0500
Received: from outmx023.isp.belgacom.be ([195.238.4.204])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H55GT-00009w-LK
	for sipping@ietf.org; Thu, 11 Jan 2007 14:07:08 -0500
Received: from outmx023.isp.belgacom.be (localhost [127.0.0.1])
	by outmx023.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22)
	with ESMTP id l0BJ6xjF020727
	for <sipping@ietf.org>; Thu, 11 Jan 2007 20:06:59 +0100
	(envelope-from <gdawirs@gmail.com>)
Received: from [10.0.1.2] (127.0-65-87.adsl-dyn.isp.belgacom.be [87.65.0.127])
	by outmx023.isp.belgacom.be
	(8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id
	l0BJ6wZI020715; Thu, 11 Jan 2007 20:06:58 +0100
	(envelope-from <gdawirs@gmail.com>)
Message-ID: <45A68AD1.8000305@gmail.com>
Date: Thu, 11 Jan 2007 20:06:57 +0100
From: Geoffrey Dawirs <gdawirs@gmail.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>, sipping@ietf.org,
	Thomas Froment <Thomas.Froment@alcatel.fr>
Subject: Re: [Sipping] WGLC: draft-ietf-sipping-spam-03.txt --- REVIEW
References: <E3F9D87C63E2774390FE67C924EC99BB0AB3DFF9@zrc2hxm1.corp.nortel.com>
	<45A4011D.1090301@cisco.com> <45A52B16.90904@gmail.com>
	<45A560D2.8000203@cisco.com>
In-Reply-To: <45A560D2.8000203@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by
	outmx023.isp.belgacom.be id l0BJ6xjF020727
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hello all,

Jonathan Rosenberg a =E9crit :
> inline.
>=20
> Geoffrey Dawirs wrote:
>=20
>> Dear Jonathan,
>>
>> Glad to read you!
>>
>> See my answer inline...
>>
>>> 1. on sieve - in what way is this different from black and white=20
>>> lists? The draft doesn't get into details on how you create and=20
>>> manage such lists. Certainly sieve is one such option, but that level=
=20
>>> of detail is beyond the scope of the draft.
>>
>>
>> Don't worry, I'm not trying to include low-level details in the draft.=
=20
>> ;-)
>> I'm completely aware that we are talking about the WHAT and not about=20
>> the HOW.
>>
>> Though, there is a main interesting difference between black/white=20
>> lists and SIEVE: by default, talking about black/white lists mean that=
=20
>> we block/allow senders. In other words, the main criteria comes from=20
>> the "From" header. SIEVE brings the new idea that we can choose to=20
>> accept or reject a message basing on multiple criteria's: request=20
>> size, value or content of some headers...
>=20
> Its not clear to me how that is helpful in the case of SIP spam. Clearl=
y=20
> message size is irrelevant for SIP; it might be more useful for email=20
> where the content is sent in the message. What other headers did you=20
> have in mind with SIP? Nothing seemed apparent to me.

For MESSAGE requests, size could be usefull. But this is clear that size=20
is really less important than having the opportunity to  look at the=20
value or the content of SIP requests: From (of course), Route (if some=20
proxies are identified as SPAM intermediates), presence of some words in=20
the Subject, or even in the Body...

For example, I could want not to receive SIP requests that contains Sex=20
neither in their Subject nor in their Body!

Thomas, any other ideas?

>>
>> This way we would also explain that we could block unsollicited=20
>> request thanks to very rich criteria's!
>>
>>> 2. on using buddy lists, white lists and black lists from different=20
>>> users together, this too is discussed in the draft under reputation=20
>>> systems. The document doesn't go into details on HOW one might do=20
>>> that; such detail is outside of the scope of the document.
>>
>>
>> Ok, that's right. I didn't intend to include technical details in the=20
>> draft, but rather underline that federating lists and empower the=20
>> filtering features could be "easily" made from what currently exists.
>=20
> Sure. My point only is that the draft already says that, so it was=20
> unclear what more you thought needed to be said.

If you think this is clear enough, ok for me.

> Thanks,

Thanks to you!
Geoffrey
> Jonathan R.
>=20
>=20

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



From sipping-bounces@ietf.org Thu Jan 11 14:18:12 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H55R3-0003h6-4I; Thu, 11 Jan 2007 14:18:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H55R1-0003cF-3y
	for sipping@ietf.org; Thu, 11 Jan 2007 14:17:59 -0500
Received: from rwcrmhc12.comcast.net ([216.148.227.152])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H55Qz-0008Eu-Oo
	for sipping@ietf.org; Thu, 11 Jan 2007 14:17:59 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc12) with ESMTP
	id <20070111191750m1200ak4jie>; Thu, 11 Jan 2007 19:17:56 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l0BJHnbM008977
	for <sipping@ietf.org>; Thu, 11 Jan 2007 14:17:49 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l0BJHmtb008973;
	Thu, 11 Jan 2007 14:17:48 -0500
Date: Thu, 11 Jan 2007 14:17:48 -0500
Message-Id: <200701111917.l0BJHmtb008973@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Subject: [Sipping] Some more thoughts on
	draft-haluska-sipping-directory-assistance-01.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

* This draft touches on a lot of interesting matters, many of which seem
to be advances in the state of the art.

This draft seems to intertwine at least 3 seperable issues:

- the execution of an OIS service

- the billing of an OIS service 

- determining that an abstract OIS request is such, and determining
  which OISP endpoint to route it to

In the PSTN, these are tightly tied together, but I expect that in the
SIP world, they will quickly become disaggregated.  I think the draft
would be more useful if these issues were identified for the reader
and explicitly treated as separable.

Of these, the execution of OIS services is probably the best-defined
in current SIP practice.  (Except for the case of wanting to re-route
the caller's dialog to the OISP after the caller's UA completes a call
to a specified third party -- I don't think there is current SIP CC
for that operation.)

* Is this draft intended to only apply to the IMS sub-world, or is it
intended for broader applicability?

This should be stated.

* The range of business models considered seems to be quite narrow:

   There are several network scenarios which must be supported: 

   Services are provided by the caller's home provider. 

   Services are provided a third party provider which has direct SIP 
   layer connectivity as well as business relationships with the 
   caller's home provider. 

   Services are provided a third party provider which has no direct SIP 
   layer connectivity and no business relationships with the caller's 
   home provider. 

For instance, consider "Services are provided a third party provider
which has direct SIP layer connectivity but no business relationships
with the caller's home provider. " and "Services are provided a third
party provider which has no business relationships with the caller,
but does have a business relationship with another third party
provider which has a direct business relationship with the caller."
And I expect a little thought could construct many other cases.  Any
proposed mechanisms should work in a broad range of business models.

* On page 22:

   It is assumed that the right-hand side of the caller's SIP URI 
   unambiguously defines the caller's home provider. 

I expect that this will not be true for long, even in "walled garden"
environments -- For e-mail, businesses and even individuals have
clamored for "vanity" domain names, and large commercial e-mail
providers support such services.  I expect that vanity SIP domain
names will be popular from Day 1.  And if there is any possibility
that an organization's SIP service can be provided by multiple network
providers, the SIP domain name will not be a reliable provider
identification.  (This will probably be true for all organizations
with multiple physical locations.)

It may be necessary to have the network assert a "network identity"
for the caller which is bound to the network service provider *for
this call*, and which is not the same as the caller's AOR or From
header.  This doesn't seem to be difficult, but has to be planned for.

* The resolution of an OIS service request to the actual OISP is an
interesting question and deserves more attention.

Currently, the SIP caller accesses an OIS by a SIP URI that identifies
the OSIP.  But this draft assumes (without stating) that the caller
specifies a URI that specifies the nature of the service without
identifying what OISP should provide it, a URN rather than a URL.  So
there is (1) a space of URIs that provide such service
identifications, and (2) a resolution process that converts these URIs
to routable URIs (before the call escapes the initial SIP provider's
network).

This is a very interesting question, and as far as I know, there is no
standardized architecture for providing such resolution.  But this
draft implies such an architecture without giving any of the details.

* The draft refers to the OSIP querying the caller's UA to determine
its capabilities.  But it should also be able to query the network
path to the caller's UA.  For example, if the user has a combiled
cellular/WiFi phone, depending on the connectivity mode, the available
bandwidth to the phone may differ by a factor of 100.  Indeed, even
when using WiFi the bandwidth may vary, with a low rate when using a
commercial "hotspot" and a higher rate when using the free Wifi in the
office.  This can probably be integrated into the QoS and bandwidth
reservation needed for any truly demanding media stream.  But it may
be desirable to standardize how an OSIP accesses this information (for
the series of links which connect it to the caller).

Dale

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



From sipping-bounces@ietf.org Thu Jan 11 14:36:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H55ix-00050I-Or; Thu, 11 Jan 2007 14:36:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H55iv-0004zm-T7
	for sipping@ietf.org; Thu, 11 Jan 2007 14:36:29 -0500
Received: from out002.iad.hostedmail.net ([209.225.56.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H55it-0004mX-CD
	for sipping@ietf.org; Thu, 11 Jan 2007 14:36:29 -0500
Received: from ATL1VEXC020.usdom003.tco.tc ([10.158.7.31]) by
	out002.iad.hostedmail.net with Microsoft SMTPSVC(6.0.3790.1830);
	Thu, 11 Jan 2007 14:36:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 11 Jan 2007 14:36:27 -0500
Message-ID: <BBE61D1553D8A34F812FF87377B2935F2D5E29@ATL1VEXC020.usdom003.tco.tc>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: streaming media without sending 18x containing sdp
Thread-Index: Acc1MjxUpIe+OqkrToaOFKrv8Ta3TAAZBPYgAAbFWIA=
From: "Brett Tate" <brett@broadsoft.com>
To: <sipping@ietf.org>, <tu-sawada@kddi.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 11 Jan 2007 19:36:25.0995 (UTC)
	FILETIME=[C85995B0:01C735B7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: 
Subject: [Sipping] streaming media without sending 18x containing sdp
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Paul, Takuya:

In order to request modification to draft-ietf-sipping-sip-offeranswer,
this email is the follow-up to my sip-implementors posting:

https://lists.cs.columbia.edu/pipermail/sip-implementors/2007-January/01
5236.html


As a means to bypass the offer/answer rules, some vendors are currently
choosing to stream early media without placing an sdp within the 18x
response.

Since I have not noticed any draft/rfc explicitly discussing such
behavior, I prefer it be discussed (valid/invalid
encouraged/discouraged) within draft-ietf-sipping-sip-offeranswer.

The following snapshot of the above link presents why I think such
behavior should be clarified.  Even if some find rfc3264 clear
concerning the topic, it seems like it would still be beneficial to
discuss it within draft-ietf-sipping-sip-offeranswer.

Thanks,
Brett


-----Original Message-----
From: sip-implementors-bounces@cs.columbia.edu
[mailto:sip-implementors-bounces@cs.columbia.edu] On Behalf Of Brett
Tate
Sent: Thursday, January 11, 2007 12:55 PM
To: Paul Kyzivat
Cc: tu-sawada@kddi.com; sip-implementors@cs.columbia.edu
Subject: Re: [Sip-implementors] streaming media without sending
18xcontaining sdp

Hi Paul,

Thanks for the response.  My replies are inline.


> > Some vendors are currently choosing to stream early media without=20
> > including an SDP within the 18x response.  Is such behavior=20
> > explicitly discouraged within an existing RFC?  And if not, should=20
> > text discussing/discouraging it be added to=20
> > draft-ietf-sipping-sip-offeranswer?
>=20
> AFAIK there is nothing in 3261 to suggest that this is improper=20
> behavior. 3261 (or maybe it is 3264) explicitly says that the offerer=20
> should be prepared to receive media as soon as the offer is sent.

Yes; the "MUST be prepared to receive" is discussed at the end of
rfc3264 section 5.1.  And my understanding is that this text is to avoid
clipping instead of giving the answerer approval to avoid sending an
answer SDP or "preview" answer SDP.

Section 6.1 discusses that the answerer may send media immediately after
sending answer.  However I haven't found any text discussing the
validity (valid or invalid) of sending media without also sending an
answer SDP.


> Nor am I aware of any more recent drafts or RFCs that try to impose=20
> any stronger rules, at least not normatively.

My understanding is that it isn't discussed because nobody expected
vendors to stream media without attempting to deliver an answer SDP or
"preview" answer SDP.

Wouldn't draft-ietf-sipping-sip-offeranswer be a good place to discuss
the validity and if it is encouraged or discouraged?  (I will likely
post a follow up to the sipping list.)

RFC 3960 indirectly discusses it by discussing the problems of forking
and early media.  However it doesn't specifically discuss the situation
I'm asking about.

=20
> I know there are deployed operating environments that make tighter=20
> assumptions, but I think these must be viewed as added requirements=20
> for those particular environments. You can perhaps find fault for a=20
> particular device not following such added rules, but I don't think it

> is currently an ietf issue.

I'm not looking to find fault.  I'm looking for clarification and if
this it is encouraged or discouraged as a way to bypass the offer/answer
rules.


> > I assume the vendors are attempting to bypass the various rules and=20
> > complexities of offer/answer by trying to take advantage of products

> > willing to render the media (to avoid clipping) under the pretence=20
> > that the related 18x/200 containing the SDP is slow to arrive.
> >=20
> > Some of the reasons to discourage such behavior is discussed within=20
> > rfc3960.  However I have not found any text explicitly discussing=20
> > devices acting like answer SDP or "preview" answer SDP has been sent

> > without intention of actually sending it.
>=20
> If there is consensus that such behavior is to be mandated then it=20
> will take some new draft to do it.

I'm not asking for a mandate.  I'm asking for a sip related IETF
document to discuss it.  If people think it is a good way to bypass the
offer/answer model; it should be encouraged.  If people think it is a
bad thing, it should be discouraged.


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



From sipping-bounces@ietf.org Thu Jan 11 18:08:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H591D-0008DB-C5; Thu, 11 Jan 2007 18:07:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H591B-0008D6-Ti
	for sipping@ietf.org; Thu, 11 Jan 2007 18:07:33 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H591A-0007Y3-Kt
	for sipping@ietf.org; Thu, 11 Jan 2007 18:07:33 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 11 Jan 2007 15:07:32 -0800
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l0BN7Wp2006799; 
	Thu, 11 Jan 2007 15:07:32 -0800
Received: from dwingwxp (dhcp-128-107-100-78.cisco.com [128.107.100.78])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l0BN7Vho000368;
	Thu, 11 Jan 2007 15:07:31 -0800 (PST)
From: "Dan Wing" <dwing@cisco.com>
To: "'Vijay K. Gurbani'" <vkg@alcatel-lucent.com>, <Dale.Worley@comcast.net>
Subject: RE: [Sipping] WGLC review of draft-ietf-sipping-spam-03
Date: Thu, 11 Jan 2007 15:07:31 -0800
Message-ID: <057401c735d5$45c39420$20a36b80@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <45A54558.2000200@alcatel-lucent.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: Acc08fN6B+xvzt8SRj+Tmd6YiyN/lAA4gb7Q
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1081; t=1168556852;
	x=1169420852; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20WGLC=20review=20of=20draft-ietf-sipping-s
	pam-03 |Sender:=20;
	bh=CTXzisX90bDKlwuWuFkmmulF6yWwVYOalP5J3z3i+r8=;
	b=q6+9vFuBimG5fXqhg5JOrm27W437BPvQbzvjOgYXZMkPHhxA1M+t1VyhTlfiAhTRW8rqNiDi
	qA++RwvHW0dt3qqiBmOWeueaZjE6AutEemNM/omlq8ygNM2yjym8P2yj;
Authentication-Results: sj-dkim-7; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

> > Could this be used to generate "inverse spam", where 
> > someone posts an
> > attractive public solicitation.  Thousands of people send 
> > introductory
> > e-mail, enclosing their Payment at Risk of (say) USD 0.05.  Then the
> > recipient just keeps the money.
> 
> Oh, neat.  I like this inverse spam idea.

Such an 'attractive solicitation' could appear to be an important 
message from your employer, your bank, your employer's healthcare 
billing company, etc., but it would actually belong to someone 
in a far-away country.  Like today's spam, rotating through 
identities (to thwart reputation systems and black lists)
and a "small" 0.01% take rate can be sufficient to make a 
profit.

It seems the escrowing company would need to detect such 
activity and police it or prevent it -- it's in their business
interest to do so, or else nobody will trust them.  

Similarly, the users have an interest in not falling for such
phishing emails -- they'll get charged money (costs them money)
or have to contest the charge (costs them time).

-d

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



From sipping-bounces@ietf.org Fri Jan 12 01:42:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5G5y-0000wM-Rb; Fri, 12 Jan 2007 01:40:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H5G5x-0000t2-DT
	for sipping@ietf.org; Fri, 12 Jan 2007 01:40:57 -0500
Received: from dnsmx1rrc.telcordia.com ([128.96.20.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5G5v-0007x2-DS
	for sipping@ietf.org; Fri, 12 Jan 2007 01:40:56 -0500
Received: from pya-dte-ieg01.cc.telcordia.com (pya-dte-ieg01.cc.telcordia.com
	[128.96.20.21])
	by dnsmx1rrc.telcordia.com (8.11.7+Sun/8.9.3) with SMTP id l0C6eov00291
	for <sipping@ietf.org>; Fri, 12 Jan 2007 01:40:50 -0500 (EST)
Received: from rrc-dte-exbh01.dte.telcordia.com ([128.96.150.31])
	by pya-dte-ieg01.cc.telcordia.com (SMSSMTP 4.1.9.35) with SMTP id
	M2007011201410608407
	for <sipping@ietf.org>; Fri, 12 Jan 2007 01:41:06 -0500
Received: from rrc-dte-exs01.dte.telcordia.com ([128.96.150.34]) by
	rrc-dte-exbh01.dte.telcordia.com with Microsoft SMTPSVC(6.0.3790.0); 
	Fri, 12 Jan 2007 01:41:06 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: Re: [Sipping] Some more thoughts on
	draft-haluska-sipping-directory-assistance-01.txt
Date: Fri, 12 Jan 2007 01:37:53 -0500
Message-ID: <A09345776B6C7A4985573569C0F300430EAE520E@rrc-dte-exs01.dte.telcordia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Some more thoughts on
	draft-haluska-sipping-directory-assistance-01.txt
Thread-Index: Acc2FC9oVfHZBNtyTpiaF3EF8LXwCw==
From: "Haluska, John J" <jhaluska@telcordia.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 12 Jan 2007 06:41:06.0801 (UTC)
	FILETIME=[A329A610:01C73614]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 746e7c8096e71e3815c27253c4c3edc6
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-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-Type: multipart/mixed; boundary="===============0554998798=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0554998798==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C73614.A2E08906"

This is a multi-part message in MIME format.

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

Dale

Thanks so much again for taking the time to look at this. You've said a =
lot, and I want to=20
give each of your points due consideration. I have addressed a few of =
them in line below,=20
I'll have to think about the others a bit more.

-John





>* This draft touches on a lot of interesting matters, many of which =
seem
>to be advances in the state of the art.
>
>This draft seems to intertwine at least 3 seperable issues:
>
>- the execution of an OIS service
>
>- the billing of an OIS service
>
>- determining that an abstract OIS request is such, and determining
>  which OISP endpoint to route it to
>
>In the PSTN, these are tightly tied together, but I expect that in the
>SIP world, they will quickly become disaggregated.  I think the draft
>would be more useful if these issues were identified for the reader
>and explicitly treated as separable.
>

JH - This is good advice - thank you.


>Of these, the execution of OIS services is probably the best-defined
>in current SIP practice.  (Except for the case of wanting to re-route
>the caller's dialog to the OISP after the caller's UA completes a call
>to a specified third party -- I don't think there is current SIP CC
>for that operation.)
>
>* Is this draft intended to only apply to the IMS sub-world, or is it
>intended for broader applicability?
>
>This should be stated.

JH - IMS is one target. But it is not intended to be limited to IMS.=20
The next revision will be clear about that, and probably will limit =
mention of
IMS specific details mainly as examples.


>
>* The range of business models considered seems to be quite narrow:
>
>   There are several network scenarios which must be supported:
>
>   Services are provided by the caller's home provider.
>
>   Services are provided a third party provider which has direct SIP
>   layer connectivity as well as business relationships with the
>   caller's home provider.
>
>   Services are provided a third party provider which has no direct SIP
>   layer connectivity and no business relationships with the caller's
>   home provider.
>
>For instance, consider "Services are provided a third party provider
>which has direct SIP layer connectivity but no business relationships
>with the caller's home provider. " and "Services are provided a third
>party provider which has no business relationships with the caller,
>but does have a business relationship with another third party
>provider which has a direct business relationship with the caller."
>And I expect a little thought could construct many other cases.  Any
>proposed mechanisms should work in a broad range of business models.
>

JH - yes. I've also been thinking that SPEERMINT might have some =
thoughts
about this, since a lot of what they deal with is driven by business=20
relationships between providers.=20


>* On page 22:
>
>   It is assumed that the right-hand side of the caller's SIP URI
>   unambiguously defines the caller's home provider.
>
>I expect that this will not be true for long, even in "walled garden"
>environments -- For e-mail, businesses and even individuals have
>clamored for "vanity" domain names, and large commercial e-mail
>providers support such services.  I expect that vanity SIP domain
>names will be popular from Day 1.  And if there is any possibility
>that an organization's SIP service can be provided by multiple network
>providers, the SIP domain name will not be a reliable provider
>identification.  (This will probably be true for all organizations
>with multiple physical locations.)

JH - We thought a lot about this for cases where some VSP provides =
service
including something like a vanity name for an enterprise. Each "vanity =
domain"=20
is just another SIP domain; it just happens to point to the actual =
provider's=20
resources. Then each of these "vanity domains" needs to be specified to =
the OISP=20
by the VSP that contracts with the OISP when that business arrrangement =
is set up.=20

If VSP "A" provides service to the east coast office, and VSP "B" to the =
west coast=20
office, it's not clear to me that the 2 offices could use the same =
vanity domain.=20

I'd tend to agree that this could start to become unmanageable if we =
start seeing vanity domains
at the individual level.




>
>It may be necessary to have the network assert a "network identity"
>for the caller which is bound to the network service provider *for
>this call*, and which is not the same as the caller's AOR or From
>header.  This doesn't seem to be difficult, but has to be planned for.
>

JH - We thought about this, but thought it would be nearly impossible to
get something like a P-Header, so we opted to use something which =
already
exists. Right now we're mainly considering the subscriber's provider, =
and=20
also allowing for the possibility that it could be a different provider =
that
has the relationship with the OISP. I've been pondering whether there's =
any basis for
needing the identity of some arbitrary provider along the way, when =
there are=20
more than 2 levels of agreeements. This might be a question for =
SPEERMINT.




>* The resolution of an OIS service request to the actual OISP is an
>interesting question and deserves more attention.
>
>Currently, the SIP caller accesses an OIS by a SIP URI that identifies
>the OSIP.  But this draft assumes (without stating) that the caller
>specifies a URI that specifies the nature of the service without
>identifying what OISP should provide it, a URN rather than a URL.  So
>there is (1) a space of URIs that provide such service
>identifications, and (2) a resolution process that converts these URIs
>to routable URIs (before the call escapes the initial SIP provider's
>network).
>
>This is a very interesting question, and as far as I know, there is no
>standardized architecture for providing such resolution.  But this
>draft implies such an architecture without giving any of the details.
>
>* The draft refers to the OSIP querying the caller's UA to determine
>its capabilities.  But it should also be able to query the network
>path to the caller's UA.  For example, if the user has a combiled
>cellular/WiFi phone, depending on the connectivity mode, the available
>bandwidth to the phone may differ by a factor of 100.  Indeed, even
>when using WiFi the bandwidth may vary, with a low rate when using a
>commercial "hotspot" and a higher rate when using the free Wifi in the
>office.  This can probably be integrated into the QoS and bandwidth
>reservation needed for any truly demanding media stream.  But it may
>be desirable to standardize how an OSIP accesses this information (for
>the series of links which connect it to the caller).
>
>Dale



------_=_NextPart_001_01C73614.A2E08906
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 =
6.5.7226.0">
<TITLE>Re: [Sipping] Some more thoughts on =
draft-haluska-sipping-directory-assistance-01.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Dale<BR>
<BR>
Thanks so much again for taking the time to look at this. You've said a =
lot, and I want to<BR>
give each of your points due consideration. I have addressed a few of =
them in line below,<BR>
I'll have to think about the others a bit more.<BR>
<BR>
-John<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
&gt;* This draft touches on a lot of interesting matters, many of which =
seem<BR>
&gt;to be advances in the state of the art.<BR>
&gt;<BR>
&gt;This draft seems to intertwine at least 3 seperable issues:<BR>
&gt;<BR>
&gt;- the execution of an OIS service<BR>
&gt;<BR>
&gt;- the billing of an OIS service<BR>
&gt;<BR>
&gt;- determining that an abstract OIS request is such, and =
determining<BR>
&gt;&nbsp; which OISP endpoint to route it to<BR>
&gt;<BR>
&gt;In the PSTN, these are tightly tied together, but I expect that in =
the<BR>
&gt;SIP world, they will quickly become disaggregated.&nbsp; I think the =
draft<BR>
&gt;would be more useful if these issues were identified for the =
reader<BR>
&gt;and explicitly treated as separable.<BR>
&gt;<BR>
<BR>
JH - This is good advice - thank you.<BR>
<BR>
<BR>
&gt;Of these, the execution of OIS services is probably the =
best-defined<BR>
&gt;in current SIP practice.&nbsp; (Except for the case of wanting to =
re-route<BR>
&gt;the caller's dialog to the OISP after the caller's UA completes a =
call<BR>
&gt;to a specified third party -- I don't think there is current SIP =
CC<BR>
&gt;for that operation.)<BR>
&gt;<BR>
&gt;* Is this draft intended to only apply to the IMS sub-world, or is =
it<BR>
&gt;intended for broader applicability?<BR>
&gt;<BR>
&gt;This should be stated.<BR>
<BR>
JH - IMS is one target. But it is not intended to be limited to IMS.<BR>
The next revision will be clear about that, and probably will limit =
mention of<BR>
IMS specific details mainly as examples.<BR>
<BR>
<BR>
&gt;<BR>
&gt;* The range of business models considered seems to be quite =
narrow:<BR>
&gt;<BR>
&gt;&nbsp;&nbsp; There are several network scenarios which must be =
supported:<BR>
&gt;<BR>
&gt;&nbsp;&nbsp; Services are provided by the caller's home =
provider.<BR>
&gt;<BR>
&gt;&nbsp;&nbsp; Services are provided a third party provider which has =
direct SIP<BR>
&gt;&nbsp;&nbsp; layer connectivity as well as business relationships =
with the<BR>
&gt;&nbsp;&nbsp; caller's home provider.<BR>
&gt;<BR>
&gt;&nbsp;&nbsp; Services are provided a third party provider which has =
no direct SIP<BR>
&gt;&nbsp;&nbsp; layer connectivity and no business relationships with =
the caller's<BR>
&gt;&nbsp;&nbsp; home provider.<BR>
&gt;<BR>
&gt;For instance, consider &quot;Services are provided a third party =
provider<BR>
&gt;which has direct SIP layer connectivity but no business =
relationships<BR>
&gt;with the caller's home provider. &quot; and &quot;Services are =
provided a third<BR>
&gt;party provider which has no business relationships with the =
caller,<BR>
&gt;but does have a business relationship with another third party<BR>
&gt;provider which has a direct business relationship with the =
caller.&quot;<BR>
&gt;And I expect a little thought could construct many other =
cases.&nbsp; Any<BR>
&gt;proposed mechanisms should work in a broad range of business =
models.<BR>
&gt;<BR>
<BR>
JH - yes. I've also been thinking that SPEERMINT might have some =
thoughts<BR>
about this, since a lot of what they deal with is driven by business<BR>
relationships between providers.<BR>
<BR>
<BR>
&gt;* On page 22:<BR>
&gt;<BR>
&gt;&nbsp;&nbsp; It is assumed that the right-hand side of the caller's =
SIP URI<BR>
&gt;&nbsp;&nbsp; unambiguously defines the caller's home provider.<BR>
&gt;<BR>
&gt;I expect that this will not be true for long, even in &quot;walled =
garden&quot;<BR>
&gt;environments -- For e-mail, businesses and even individuals have<BR>
&gt;clamored for &quot;vanity&quot; domain names, and large commercial =
e-mail<BR>
&gt;providers support such services.&nbsp; I expect that vanity SIP =
domain<BR>
&gt;names will be popular from Day 1.&nbsp; And if there is any =
possibility<BR>
&gt;that an organization's SIP service can be provided by multiple =
network<BR>
&gt;providers, the SIP domain name will not be a reliable provider<BR>
&gt;identification.&nbsp; (This will probably be true for all =
organizations<BR>
&gt;with multiple physical locations.)<BR>
<BR>
JH - We thought a lot about this for cases where some VSP provides =
service<BR>
including something like a vanity name for an enterprise. Each =
&quot;vanity domain&quot;<BR>
is just another SIP domain; it just happens to point to the actual =
provider's<BR>
resources. Then each of these &quot;vanity domains&quot; needs to be =
specified to the OISP<BR>
by the VSP that contracts with the OISP when that business arrrangement =
is set up.<BR>
<BR>
If VSP &quot;A&quot; provides service to the east coast office, and VSP =
&quot;B&quot; to the west coast<BR>
office, it's not clear to me that the 2 offices could use the same =
vanity domain.<BR>
<BR>
I'd tend to agree that this could start to become unmanageable if we =
start seeing vanity domains<BR>
at the individual level.<BR>
<BR>
<BR>
<BR>
<BR>
&gt;<BR>
&gt;It may be necessary to have the network assert a &quot;network =
identity&quot;<BR>
&gt;for the caller which is bound to the network service provider =
*for<BR>
&gt;this call*, and which is not the same as the caller's AOR or =
From<BR>
&gt;header.&nbsp; This doesn't seem to be difficult, but has to be =
planned for.<BR>
&gt;<BR>
<BR>
JH - We thought about this, but thought it would be nearly impossible =
to<BR>
get something like a P-Header, so we opted to use something which =
already<BR>
exists. Right now we're mainly considering the subscriber's provider, =
and<BR>
also allowing for the possibility that it could be a different provider =
that<BR>
has the relationship with the OISP. I've been pondering whether there's =
any basis for<BR>
needing the identity of some arbitrary provider along the way, when =
there are<BR>
more than 2 levels of agreeements. This might be a question for =
SPEERMINT.<BR>
<BR>
<BR>
<BR>
<BR>
&gt;* The resolution of an OIS service request to the actual OISP is =
an<BR>
&gt;interesting question and deserves more attention.<BR>
&gt;<BR>
&gt;Currently, the SIP caller accesses an OIS by a SIP URI that =
identifies<BR>
&gt;the OSIP.&nbsp; But this draft assumes (without stating) that the =
caller<BR>
&gt;specifies a URI that specifies the nature of the service without<BR>
&gt;identifying what OISP should provide it, a URN rather than a =
URL.&nbsp; So<BR>
&gt;there is (1) a space of URIs that provide such service<BR>
&gt;identifications, and (2) a resolution process that converts these =
URIs<BR>
&gt;to routable URIs (before the call escapes the initial SIP =
provider's<BR>
&gt;network).<BR>
&gt;<BR>
&gt;This is a very interesting question, and as far as I know, there is =
no<BR>
&gt;standardized architecture for providing such resolution.&nbsp; But =
this<BR>
&gt;draft implies such an architecture without giving any of the =
details.<BR>
&gt;<BR>
&gt;* The draft refers to the OSIP querying the caller's UA to =
determine<BR>
&gt;its capabilities.&nbsp; But it should also be able to query the =
network<BR>
&gt;path to the caller's UA.&nbsp; For example, if the user has a =
combiled<BR>
&gt;cellular/WiFi phone, depending on the connectivity mode, the =
available<BR>
&gt;bandwidth to the phone may differ by a factor of 100.&nbsp; Indeed, =
even<BR>
&gt;when using WiFi the bandwidth may vary, with a low rate when using =
a<BR>
&gt;commercial &quot;hotspot&quot; and a higher rate when using the free =
Wifi in the<BR>
&gt;office.&nbsp; This can probably be integrated into the QoS and =
bandwidth<BR>
&gt;reservation needed for any truly demanding media stream.&nbsp; But =
it may<BR>
&gt;be desirable to standardize how an OSIP accesses this information =
(for<BR>
&gt;the series of links which connect it to the caller).<BR>
&gt;<BR>
&gt;Dale<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C73614.A2E08906--


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

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




From sipping-bounces@ietf.org Fri Jan 12 03:32:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5Hp3-00049g-Is; Fri, 12 Jan 2007 03:31:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H5Hp2-00049U-1c
	for sipping@ietf.org; Fri, 12 Jan 2007 03:31:36 -0500
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5Hoy-00074R-F6
	for sipping@ietf.org; Fri, 12 Jan 2007 03:31:36 -0500
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JBQ0064IYBS6Y@siemenscomms.co.uk> for sipping@ietf.org;
	Fri, 12 Jan 2007 08:31:04 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <Z1TGFSC7>; Fri, 12 Jan 2007 08:31:00 +0000
Content-return: allowed
Date: Fri, 12 Jan 2007 08:30:59 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sipping] streaming media without sending 18x containing sdp
To: Brett Tate <brett@broadsoft.com>, sipping@ietf.org, tu-sawada@kddi.com,
	Paul Kyzivat <pkyzivat@cisco.com>
Message-id: <50B1CBA96870A34799A506B2313F26670ABDA377@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Brett,

I am not aware of anything to prevent it in straightforward circumstances,
but be aware that in some situations it simply will not work:
- use of security descriptions - the SDP answer is necessary before sending
SRTP;
- certain NAT environments, e.g., when using ICE or when  forward RTP is
needed to open the NAT binding for backward RTP.

So any clarification in the sip-offeranswer draft should mention these
points.

John 

> -----Original Message-----
> From: Brett Tate [mailto:brett@broadsoft.com] 
> Sent: 11 January 2007 19:36
> To: sipping@ietf.org; tu-sawada@kddi.com; Paul Kyzivat
> Subject: [Sipping] streaming media without sending 18x containing sdp
> 
> Paul, Takuya:
> 
> In order to request modification to 
> draft-ietf-sipping-sip-offeranswer,
> this email is the follow-up to my sip-implementors posting:
> 
> https://lists.cs.columbia.edu/pipermail/sip-implementors/2007-
> January/01
> 5236.html
> 
> 
> As a means to bypass the offer/answer rules, some vendors are 
> currently
> choosing to stream early media without placing an sdp within the 18x
> response.
> 
> Since I have not noticed any draft/rfc explicitly discussing such
> behavior, I prefer it be discussed (valid/invalid
> encouraged/discouraged) within draft-ietf-sipping-sip-offeranswer.
> 
> The following snapshot of the above link presents why I think such
> behavior should be clarified.  Even if some find rfc3264 clear
> concerning the topic, it seems like it would still be beneficial to
> discuss it within draft-ietf-sipping-sip-offeranswer.
> 
> Thanks,
> Brett
> 
> 
> -----Original Message-----
> From: sip-implementors-bounces@cs.columbia.edu
> [mailto:sip-implementors-bounces@cs.columbia.edu] On Behalf Of Brett
> Tate
> Sent: Thursday, January 11, 2007 12:55 PM
> To: Paul Kyzivat
> Cc: tu-sawada@kddi.com; sip-implementors@cs.columbia.edu
> Subject: Re: [Sip-implementors] streaming media without sending
> 18xcontaining sdp
> 
> Hi Paul,
> 
> Thanks for the response.  My replies are inline.
> 
> 
> > > Some vendors are currently choosing to stream early media without 
> > > including an SDP within the 18x response.  Is such behavior 
> > > explicitly discouraged within an existing RFC?  And if 
> not, should 
> > > text discussing/discouraging it be added to 
> > > draft-ietf-sipping-sip-offeranswer?
> > 
> > AFAIK there is nothing in 3261 to suggest that this is improper 
> > behavior. 3261 (or maybe it is 3264) explicitly says that 
> the offerer 
> > should be prepared to receive media as soon as the offer is sent.
> 
> Yes; the "MUST be prepared to receive" is discussed at the end of
> rfc3264 section 5.1.  And my understanding is that this text 
> is to avoid
> clipping instead of giving the answerer approval to avoid sending an
> answer SDP or "preview" answer SDP.
> 
> Section 6.1 discusses that the answerer may send media 
> immediately after
> sending answer.  However I haven't found any text discussing the
> validity (valid or invalid) of sending media without also sending an
> answer SDP.
> 
> 
> > Nor am I aware of any more recent drafts or RFCs that try to impose 
> > any stronger rules, at least not normatively.
> 
> My understanding is that it isn't discussed because nobody expected
> vendors to stream media without attempting to deliver an answer SDP or
> "preview" answer SDP.
> 
> Wouldn't draft-ietf-sipping-sip-offeranswer be a good place to discuss
> the validity and if it is encouraged or discouraged?  (I will likely
> post a follow up to the sipping list.)
> 
> RFC 3960 indirectly discusses it by discussing the problems of forking
> and early media.  However it doesn't specifically discuss the 
> situation
> I'm asking about.
> 
>  
> > I know there are deployed operating environments that make tighter 
> > assumptions, but I think these must be viewed as added requirements 
> > for those particular environments. You can perhaps find fault for a 
> > particular device not following such added rules, but I 
> don't think it
> 
> > is currently an ietf issue.
> 
> I'm not looking to find fault.  I'm looking for clarification and if
> this it is encouraged or discouraged as a way to bypass the 
> offer/answer
> rules.
> 
> 
> > > I assume the vendors are attempting to bypass the various 
> rules and 
> > > complexities of offer/answer by trying to take advantage 
> of products
> 
> > > willing to render the media (to avoid clipping) under the 
> pretence 
> > > that the related 18x/200 containing the SDP is slow to arrive.
> > > 
> > > Some of the reasons to discourage such behavior is 
> discussed within 
> > > rfc3960.  However I have not found any text explicitly discussing 
> > > devices acting like answer SDP or "preview" answer SDP 
> has been sent
> 
> > > without intention of actually sending it.
> > 
> > If there is consensus that such behavior is to be mandated then it 
> > will take some new draft to do it.
> 
> I'm not asking for a mandate.  I'm asking for a sip related IETF
> document to discuss it.  If people think it is a good way to 
> bypass the
> offer/answer model; it should be encouraged.  If people think it is a
> bad thing, it should be discouraged.
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org Fri Jan 12 12:58:50 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5Qer-0000ry-72; Fri, 12 Jan 2007 12:57:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H5Qeq-0000q3-6X
	for sipping@ietf.org; Fri, 12 Jan 2007 12:57:40 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5Qem-0000Iu-NS
	for sipping@ietf.org; Fri, 12 Jan 2007 12:57:40 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 12 Jan 2007 09:57:36 -0800
X-IronPort-AV: i="4.13,179,1167638400"; 
	d="scan'208"; a="50687545:sNHT53298380"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l0CHvavO013066; 
	Fri, 12 Jan 2007 12:57:36 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l0CHvZOC003344; 
	Fri, 12 Jan 2007 12:57:35 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 12 Jan 2007 12:57:35 -0500
Received: from [161.44.183.248] ([161.44.183.248]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 12 Jan 2007 12:57:34 -0500
Message-ID: <45A7CC0E.4090705@cisco.com>
Date: Fri, 12 Jan 2007 12:57:34 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Brett Tate <brett@broadsoft.com>
References: <BBE61D1553D8A34F812FF87377B2935F2D5E29@ATL1VEXC020.usdom003.tco.tc>
In-Reply-To: <BBE61D1553D8A34F812FF87377B2935F2D5E29@ATL1VEXC020.usdom003.tco.tc>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Jan 2007 17:57:34.0998 (UTC)
	FILETIME=[239D0360:01C73673]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5438; t=1168624656;
	x=1169488656; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20streaming=20media=20without=20sending=2018x=20contain
	ing=20sdp |Sender:=20
	|To:=20Brett=20Tate=20<brett@broadsoft.com>;
	bh=Hsf6DcHZnUvdkB+wa8GQR0pFomMeG02rgr1L+RF023U=;
	b=m3KuAQnNWIUrbOMwcNl+eQZ0oA1u4dzaNm4tcSqq90+i4Ij3yGZYU1eRYCiy8zgUbGdRSgLR
	Y1wgFtq8m+Tpq6/BcHe+KIRzt0fFdK0+Bmzn+eHg8TfRn1jMAARYcEtM;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: tu-sawada@kddi.com, sipping@ietf.org
Subject: [Sipping] Re: streaming media without sending 18x containing sdp
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Brett,

We have been trying to have the offeranswer draft explain things that 
are specified in standards and/or generally agreed to have been implied 
by the standards.

IMO what you are asking doesn't, yet, fall into that category. I think 
we at least need some further list discussion leading to consensus about 
what correct behavior is in this case. What you are looking for may be:
- an explicit statement that the behavior you have seen is
   in fact legal, or
- a tightening of the specifications, declaring the kind of
   behavior you are concerned with to in fact be illegal, or
- a BCP specifying this behavior.

Once there is a clear sense of the way to go on this, I think it *might* 
be appropriate for the offeranswer draft.

I don't know if there are any important use cases where sending media 
before the answer is necessary. I'd be interested to hear if there are.

	Paul

Brett Tate wrote:
> Paul, Takuya:
> 
> In order to request modification to draft-ietf-sipping-sip-offeranswer,
> this email is the follow-up to my sip-implementors posting:
> 
> https://lists.cs.columbia.edu/pipermail/sip-implementors/2007-January/01
> 5236.html
> 
> 
> As a means to bypass the offer/answer rules, some vendors are currently
> choosing to stream early media without placing an sdp within the 18x
> response.
> 
> Since I have not noticed any draft/rfc explicitly discussing such
> behavior, I prefer it be discussed (valid/invalid
> encouraged/discouraged) within draft-ietf-sipping-sip-offeranswer.
> 
> The following snapshot of the above link presents why I think such
> behavior should be clarified.  Even if some find rfc3264 clear
> concerning the topic, it seems like it would still be beneficial to
> discuss it within draft-ietf-sipping-sip-offeranswer.
> 
> Thanks,
> Brett
> 
> 
> -----Original Message-----
> From: sip-implementors-bounces@cs.columbia.edu
> [mailto:sip-implementors-bounces@cs.columbia.edu] On Behalf Of Brett
> Tate
> Sent: Thursday, January 11, 2007 12:55 PM
> To: Paul Kyzivat
> Cc: tu-sawada@kddi.com; sip-implementors@cs.columbia.edu
> Subject: Re: [Sip-implementors] streaming media without sending
> 18xcontaining sdp
> 
> Hi Paul,
> 
> Thanks for the response.  My replies are inline.
> 
> 
>>> Some vendors are currently choosing to stream early media without 
>>> including an SDP within the 18x response.  Is such behavior 
>>> explicitly discouraged within an existing RFC?  And if not, should 
>>> text discussing/discouraging it be added to 
>>> draft-ietf-sipping-sip-offeranswer?
>> AFAIK there is nothing in 3261 to suggest that this is improper 
>> behavior. 3261 (or maybe it is 3264) explicitly says that the offerer 
>> should be prepared to receive media as soon as the offer is sent.
> 
> Yes; the "MUST be prepared to receive" is discussed at the end of
> rfc3264 section 5.1.  And my understanding is that this text is to avoid
> clipping instead of giving the answerer approval to avoid sending an
> answer SDP or "preview" answer SDP.
> 
> Section 6.1 discusses that the answerer may send media immediately after
> sending answer.  However I haven't found any text discussing the
> validity (valid or invalid) of sending media without also sending an
> answer SDP.
> 
> 
>> Nor am I aware of any more recent drafts or RFCs that try to impose 
>> any stronger rules, at least not normatively.
> 
> My understanding is that it isn't discussed because nobody expected
> vendors to stream media without attempting to deliver an answer SDP or
> "preview" answer SDP.
> 
> Wouldn't draft-ietf-sipping-sip-offeranswer be a good place to discuss
> the validity and if it is encouraged or discouraged?  (I will likely
> post a follow up to the sipping list.)
> 
> RFC 3960 indirectly discusses it by discussing the problems of forking
> and early media.  However it doesn't specifically discuss the situation
> I'm asking about.
> 
>  
>> I know there are deployed operating environments that make tighter 
>> assumptions, but I think these must be viewed as added requirements 
>> for those particular environments. You can perhaps find fault for a 
>> particular device not following such added rules, but I don't think it
> 
>> is currently an ietf issue.
> 
> I'm not looking to find fault.  I'm looking for clarification and if
> this it is encouraged or discouraged as a way to bypass the offer/answer
> rules.
> 
> 
>>> I assume the vendors are attempting to bypass the various rules and 
>>> complexities of offer/answer by trying to take advantage of products
> 
>>> willing to render the media (to avoid clipping) under the pretence 
>>> that the related 18x/200 containing the SDP is slow to arrive.
>>>
>>> Some of the reasons to discourage such behavior is discussed within 
>>> rfc3960.  However I have not found any text explicitly discussing 
>>> devices acting like answer SDP or "preview" answer SDP has been sent
> 
>>> without intention of actually sending it.
>> If there is consensus that such behavior is to be mandated then it 
>> will take some new draft to do it.
> 
> I'm not asking for a mandate.  I'm asking for a sip related IETF
> document to discuss it.  If people think it is a good way to bypass the
> offer/answer model; it should be encouraged.  If people think it is a
> bad thing, it should be discouraged.
> 

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



From sipping-bounces@ietf.org Fri Jan 12 17:32:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5Uvo-0004wA-3X; Fri, 12 Jan 2007 17:31:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H5Uvl-0004vk-Ey
	for sipping@ietf.org; Fri, 12 Jan 2007 17:31:26 -0500
Received: from out002.iad.hostedmail.net ([209.225.56.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5Uvk-0007Nt-7a
	for sipping@ietf.org; Fri, 12 Jan 2007 17:31:25 -0500
Received: from ATL1VEXC020.usdom003.tco.tc ([10.158.7.31]) by
	out002.iad.hostedmail.net with Microsoft SMTPSVC(6.0.3790.1830);
	Fri, 12 Jan 2007 17:31:21 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 12 Jan 2007 17:31:22 -0500
Message-ID: <BBE61D1553D8A34F812FF87377B2935F2D61B6@ATL1VEXC020.usdom003.tco.tc>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: streaming media without sending 18x containing sdp
Thread-Index: Acc2cyWo5woenYKCRiWfSFCAV9Z6WwACe3Hw
From: "Brett Tate" <brett@broadsoft.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 12 Jan 2007 22:31:21.0141 (UTC)
	FILETIME=[625B8650:01C73699]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: tu-sawada@kddi.com, sipping@ietf.org
Subject: [Sipping] RE: streaming media without sending 18x containing sdp
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Thanks for the response.  My replies are inline.


> We have been trying to have the offeranswer draft explain=20
> things that are specified in standards and/or generally=20
> agreed to have been implied by the standards.
>=20
> IMO what you are asking doesn't, yet, fall into that=20
> category. I think we at least need some further list=20
> discussion leading to consensus about what correct=20
> behavior is in this case.=20

Sounds fair.  Maybe those sending media without sending an answer SDP or
"preview" answer SDP will reply. =20

I think it violates the spirit of rfc3264; however depending upon
interpretation of section 6.1, it might not actually violate rfc3264.

RFC 3264 section 5.1 lists some of the restrictions concerning receiving
media prior to receiving the answer SDP.  It cannot send media.  It
cannot send RTCP receiver reports.

RFC 3959 and RFC 3960 discuss the forking related limitations; however I
don't recall if all are discussed.  The receiver might not be able to
handle media being streamed from multiple locations.  Clipping might
occur upon answer if not currently presenting the media associated with
the dialog which answered (INVITE 200).  The user might not like the
sound of media being mixed to avoid the clipping problem.

And John Elwell mentioned problems with:
"
- use of security descriptions - the SDP answer is necessary before
sending SRTP;
- certain NAT environments, e.g., when using ICE or when forward RTP is
needed to open the NAT binding for backward RTP.
"


> What you are looking for may be:
> - an explicit statement that the behavior you have seen is
>    in fact legal, or
> - a tightening of the specifications, declaring the kind of
>    behavior you are concerned with to in fact be illegal, or
> - a BCP specifying this behavior.
>
> Once there is a clear sense of the way to go on this, I=20
> think it *might* be appropriate for the offeranswer draft.

Thanks for the potential willingness to provide clarification=20
within draft-ietf-sipping-sip-offeranswer.


> I don't know if there are any important use cases where=20
> sending media before the answer is necessary. I'd be=20
> interested to hear if there are.

As far as I know, there are two reasons.  However the importance level
is debatable since I really think it is just a lack of desire to comply
with the spirit of rfc3264.

1) Simplification: avoid the restrictions and complication caused by the
only 1 answer rules.  Thus violate the spirit of rfc3264 and act as
answerer without actually sending the SDP. :)

2) Optimization: avoid the extra dialogs, UPDATEs, or re-INVITEs which
would have been required by sending different SDPs when early-session
(rfc3959) not used or adequate.  For instance if not using
early-session, extra messaging would be required if first wanted return
SDP containing sendonly and subsequently send SDP containing sendrecv.

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



From sipping-bounces@ietf.org Sat Jan 13 08:37:54 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5j4K-0001BJ-1N; Sat, 13 Jan 2007 08:37:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H5j4I-0001BC-5n
	for sipping@ietf.org; Sat, 13 Jan 2007 08:37:10 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5j4D-0003Sw-Sm
	for sipping@ietf.org; Sat, 13 Jan 2007 08:37:10 -0500
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 9903A595; 
	Sat, 13 Jan 2007 14:36:48 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 13 Jan 2007 14:36:48 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: streaming media without sending 18x containing sdp
Date: Sat, 13 Jan 2007 14:36:46 +0100
Message-ID: <7374777208BDC7449D5620EF942325670166D9C2@esealmw113.eemea.ericsson.se>
In-Reply-To: <BBE61D1553D8A34F812FF87377B2935F2D61B6@ATL1VEXC020.usdom003.tco.tc>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] RE: streaming media without sending 18x containing sdp
Thread-Index: Acc2cyWo5woenYKCRiWfSFCAV9Z6WwACe3HwACaPBWA=
From: "Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
To: "Brett Tate" <brett@broadsoft.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 13 Jan 2007 13:36:48.0467 (UTC)
	FILETIME=[DFF79A30:01C73717]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: tu-sawada@kddi.com, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


Hi,=20

>>I don't know if there are any important use cases where=20
>>sending media before the answer is necessary. I'd be=20
>>interested to hear if there are.
>=20
>As far as I know, there are two reasons.  However the importance level
>is debatable since I really think it is just a lack of desire=20
>to comply with the spirit of rfc3264.
>=20
>1) Simplification: avoid the restrictions and complication=20
>caused by the only 1 answer rules.  Thus violate the spirit of rfc3264
and act as
>answerer without actually sending the SDP. :)
>=20
>2) Optimization: avoid the extra dialogs, UPDATEs, or re-INVITEs which
>would have been required by sending different SDPs when early-session
>(rfc3959) not used or adequate.  For instance if not using
>early-session, extra messaging would be required if first wanted return
>SDP containing sendonly and subsequently send SDP containing sendrecv.

Both cases can be solved with a very simple trick: changing of the To
tag. If the UAS wants to change the answer, it simply changes the To tag
in the response (18x or 200) where the new answer is sent. No need for
any UPDATE or re-INVITE, and no violation of any RFC.

Regards,

Christer

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



From sipping-bounces@ietf.org Sat Jan 13 13:02:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5nCA-00007u-AS; Sat, 13 Jan 2007 13:01:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5aVu-0005tc-LS; Fri, 12 Jan 2007 23:29:06 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H5aVs-0002bo-Bi; Fri, 12 Jan 2007 23:29:06 -0500
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-5.cisco.com with ESMTP; 12 Jan 2007 20:29:03 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l0D4T2Ia012932; 
	Fri, 12 Jan 2007 20:29:02 -0800
Received: from [192.168.1.9] (sjc-vpn7-387.cisco.com [10.21.145.131])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l0D4T2nF020709;
	Fri, 12 Jan 2007 20:29:02 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <F488C7FA-A0AB-44D2-A995-1A44AE183FF6@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: rai@ietf.org, avt@ietf.org, ECRIT <ecrit@ietf.org>, enum@ietf.org,
	mmusic@ietf.org, sigtran@ietf.org, simple@ietf.org, geopriv@ietf.org,
	ieprep@ietf.org, SIP <sip@ietf.org>, sipping@ietf.org,
	speechsc@ietf.org, speermint@ietf.org, xcon@ietf.org,
	RAI Chairs <rai-chairs@ietf.org>, RAI Discuss <rai-discuss@ietf.org>
From: Cullen Jennings <fluffy@cisco.com>
Date: Fri, 12 Jan 2007 20:28:52 -0800
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=484; t=1168662542;
	x=1169526542; c=relaxed/relaxed; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20New=20RAI=20mailing=20list=20formed |Sender:=20;
	bh=oy9hMDTAd3CLwx2VjaSlGDIiUGc4zeKQTh4WxAq1xfU=;
	b=nzE6bx99AfmpN9XXdKKYeMzdSrPYLU0XznGtkrDuKY24XeITEuEnaaVR9hz7VFmVb9njtbTr
	5VVkwN8evTl13ZapqifDuRHeokxVdDOoFkvhoDOAduovqFL7TFD5fRZC;
Authentication-Results: sj-dkim-8; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim8002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
X-Mailman-Approved-At: Sat, 13 Jan 2007 13:01:33 -0500
Cc: 
Subject: [Sipping] New RAI mailing list formed
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


Please don't reply to this message so you don't cross post to all the  
groups.

A new mailing list for announcement and discussion of general topics  
of interest to RAI Area has been created. The list is rai@ietf.org

You can subscribe at:
https://www1.ietf.org/mailman/listinfo/rai
Or by sending email with a body containing "subscribe" to rai- 
request@ietf.org

Please do subscribe to it so you can find announcements for things  
like RAI BOFs.

Thanks,
Cullen & Jon


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



From sipping-bounces@ietf.org Sat Jan 13 14:47:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5oqO-0004ZC-Sa; Sat, 13 Jan 2007 14:47:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H5oqN-0004Z6-9C
	for sipping@ietf.org; Sat, 13 Jan 2007 14:47:11 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5oqM-0004kv-0B
	for sipping@ietf.org; Sat, 13 Jan 2007 14:47:11 -0500
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-5.cisco.com with ESMTP; 13 Jan 2007 11:47:09 -0800
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l0DJl9XU019559
	for <sipping@ietf.org>; Sat, 13 Jan 2007 11:47:09 -0800
Received: from [192.168.1.5] (sjc-vpn2-444.cisco.com [10.21.113.188])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l0DJl9ho018475
	for <sipping@ietf.org>; Sat, 13 Jan 2007 11:47:09 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <73ED455E-8512-463A-B568-384672E8241F@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: sipping@ietf.org
From: Cullen Jennings <fluffy@cisco.com>
Date: Sat, 13 Jan 2007 11:46:59 -0800
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=444; t=1168717629;
	x=1169581629; c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20New=20RAI=20mailing=20list=20formed=20=20
	|Sender:=20; bh=5f8EvdfGiOmFIoCw5HV0P0Q9jbcKK05G7vueJlh3cUA=;
	b=tL4A+McW+ryzQ7lq4CXfkDIbnJ75KdQXaCX9WKti8/kG7R4UiCP6oeWpv9/k3Uf4k2FHPogX
	Hr1GmjeiDYeRQB6IFCLv+90qi6qH3GwLRO4hxEm/L9UUtIfLE7ufMy2a;
Authentication-Results: sj-dkim-6; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim6002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: [Sipping] New RAI mailing list formed  
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Sorry for the many duplicate posts.

A new mailing list for announcement and discussion of general topics  
of interest to RAI Area has been created. The list is rai@ietf.org

You can subscribe at:
https://www1.ietf.org/mailman/listinfo/rai
Or by sending email with a body containing "subscribe" to rai- 
request@ietf.org

Please do subscribe to it so you can find announcements for things  
like RAI BOFs.

Thanks,
Cullen & Jon


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



From sipping-bounces@ietf.org Sun Jan 14 23:10:21 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6J8y-0006eY-CE; Sun, 14 Jan 2007 23:08:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6J8x-0006eR-A2
	for sipping@ietf.org; Sun, 14 Jan 2007 23:08:23 -0500
Received: from athena.kddi.com ([210.141.112.39] helo=UTMC1104.kddi.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6J8v-00039Y-GD
	for sipping@ietf.org; Sun, 14 Jan 2007 23:08:23 -0500
Received: from usjk1039 (unknown [10.5.16.73])
	by UTMC1104.kddi.com (Postfix) with SMTP id 858342661;
	Mon, 15 Jan 2007 13:08:15 +0900 (JST)
Received: from localhost (localhost [127.0.0.1])
	by localhost.kddi.com (Postfix) with SMTP id AE2811AE5;
	Mon, 15 Jan 2007 13:08:12 +0900 (JST)
Received: from UTMC1118.kddi.com (unknown [10.5.16.33])
	by UTMC1122.kddi.com (Postfix) with ESMTP id 853761AE6;
	Mon, 15 Jan 2007 13:08:04 +0900 (JST)
Received: from KDDI-0608PC0139 ([133.128.137.20] [133.128.137.20]) by
	post-ims.kddi.com with ESMTPA; Mon, 15 Jan 2007 13:08:04 +0900
To: pkyzivat@cisco.com, brett@broadsoft.com
Subject: Re: [Sipping] Re: streaming media without sending 18x containing sdp
From: Takuya Sawada <tu-sawada@kddi.com>
References: <BBE61D1553D8A34F812FF87377B2935F2D5E29@ATL1VEXC020.usdom003.tco.tc>
	<45A7CC0E.4090705@cisco.com>
In-Reply-To: <45A7CC0E.4090705@cisco.com>
Message-Id: <200701151308.FJD65600.XBBUtBVET@kddi.com>
X-Mailer: Winbiff [Version 2.50]
X-Accept-Language: ja,en
Date: Mon, 15 Jan 2007 13:08:04 +0900
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-WAuditID: 0701151308120000220473
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
Cc: tu-sawada@kddi.com, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Brett,

Actually so far I intended the offer/answer draft to be independent 
>from the media layer, because;

1) offer/answer exchange is not limited to sending/receiving media.
  It can negotiate key management or pre-conditions, for example.
  We want it to be general where possible.
2) early-media discussion is so controversial to be fixed here.

However, if it is useful, we can add something about the issue you raised 
here. I am not sure but maybe we need to add new section or some notes
to do that. As Paul said, we need further discussion.

IMHO, what is defined in RFCs is just to prepare to receive media when 
sending SDP, and it may be enough in most cases.
I do not know whether it is perfectly good thing to recommend not to send
any media packets until it send out SDP answer. But possibly it can reduce
the potential problems.

Regards,
Takuya

> Brett,
> 
> We have been trying to have the offeranswer draft explain things that 
> are specified in standards and/or generally agreed to have been implied 
> by the standards.
> 
> IMO what you are asking doesn't, yet, fall into that category. I think 
> we at least need some further list discussion leading to consensus about 
> what correct behavior is in this case. What you are looking for may be:
> - an explicit statement that the behavior you have seen is
>    in fact legal, or
> - a tightening of the specifications, declaring the kind of
>    behavior you are concerned with to in fact be illegal, or
> - a BCP specifying this behavior.
> 
> Once there is a clear sense of the way to go on this, I think it *might* 
> be appropriate for the offeranswer draft.
> 
> I don't know if there are any important use cases where sending media 
> before the answer is necessary. I'd be interested to hear if there are.
> 
> 	Paul
> 
> Brett Tate wrote:
> > Paul, Takuya:
> > 
> > In order to request modification to draft-ietf-sipping-sip-offeranswer,
> > this email is the follow-up to my sip-implementors posting:
> > 
> > https://lists.cs.columbia.edu/pipermail/sip-implementors/2007-January/01
> > 5236.html
> > 
> > 
> > As a means to bypass the offer/answer rules, some vendors are currently
> > choosing to stream early media without placing an sdp within the 18x
> > response.
> > 
> > Since I have not noticed any draft/rfc explicitly discussing such
> > behavior, I prefer it be discussed (valid/invalid
> > encouraged/discouraged) within draft-ietf-sipping-sip-offeranswer.
> > 
> > The following snapshot of the above link presents why I think such
> > behavior should be clarified.  Even if some find rfc3264 clear
> > concerning the topic, it seems like it would still be beneficial to
> > discuss it within draft-ietf-sipping-sip-offeranswer.
> > 
> > Thanks,
> > Brett
> > 
> > 
> > -----Original Message-----
> > From: sip-implementors-bounces@cs.columbia.edu
> > [mailto:sip-implementors-bounces@cs.columbia.edu] On Behalf Of Brett
> > Tate
> > Sent: Thursday, January 11, 2007 12:55 PM
> > To: Paul Kyzivat
> > Cc: tu-sawada@kddi.com; sip-implementors@cs.columbia.edu
> > Subject: Re: [Sip-implementors] streaming media without sending
> > 18xcontaining sdp
> > 
> > Hi Paul,
> > 
> > Thanks for the response.  My replies are inline.
> > 
> > 
> >>> Some vendors are currently choosing to stream early media without 
> >>> including an SDP within the 18x response.  Is such behavior 
> >>> explicitly discouraged within an existing RFC?  And if not, should 
> >>> text discussing/discouraging it be added to 
> >>> draft-ietf-sipping-sip-offeranswer?
> >> AFAIK there is nothing in 3261 to suggest that this is improper 
> >> behavior. 3261 (or maybe it is 3264) explicitly says that the offerer 
> >> should be prepared to receive media as soon as the offer is sent.
> > 
> > Yes; the "MUST be prepared to receive" is discussed at the end of
> > rfc3264 section 5.1.  And my understanding is that this text is to avoid
> > clipping instead of giving the answerer approval to avoid sending an
> > answer SDP or "preview" answer SDP.
> > 
> > Section 6.1 discusses that the answerer may send media immediately after
> > sending answer.  However I haven't found any text discussing the
> > validity (valid or invalid) of sending media without also sending an
> > answer SDP.
> > 
> > 
> >> Nor am I aware of any more recent drafts or RFCs that try to impose 
> >> any stronger rules, at least not normatively.
> > 
> > My understanding is that it isn't discussed because nobody expected
> > vendors to stream media without attempting to deliver an answer SDP or
> > "preview" answer SDP.
> > 
> > Wouldn't draft-ietf-sipping-sip-offeranswer be a good place to discuss
> > the validity and if it is encouraged or discouraged?  (I will likely
> > post a follow up to the sipping list.)
> > 
> > RFC 3960 indirectly discusses it by discussing the problems of forking
> > and early media.  However it doesn't specifically discuss the situation
> > I'm asking about.
> > 
> >  
> >> I know there are deployed operating environments that make tighter 
> >> assumptions, but I think these must be viewed as added requirements 
> >> for those particular environments. You can perhaps find fault for a 
> >> particular device not following such added rules, but I don't think it
> > 
> >> is currently an ietf issue.
> > 
> > I'm not looking to find fault.  I'm looking for clarification and if
> > this it is encouraged or discouraged as a way to bypass the offer/answer
> > rules.
> > 
> > 
> >>> I assume the vendors are attempting to bypass the various rules and 
> >>> complexities of offer/answer by trying to take advantage of products
> > 
> >>> willing to render the media (to avoid clipping) under the pretence 
> >>> that the related 18x/200 containing the SDP is slow to arrive.
> >>>
> >>> Some of the reasons to discourage such behavior is discussed within 
> >>> rfc3960.  However I have not found any text explicitly discussing 
> >>> devices acting like answer SDP or "preview" answer SDP has been sent
> > 
> >>> without intention of actually sending it.
> >> If there is consensus that such behavior is to be mandated then it 
> >> will take some new draft to do it.
> > 
> > I'm not asking for a mandate.  I'm asking for a sip related IETF
> > document to discuss it.  If people think it is a good way to bypass the
> > offer/answer model; it should be encouraged.  If people think it is a
> > bad thing, it should be discouraged.
> > 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

--------
Takuya Sawada
KDDI Corporation (KDDI)
Garden Air Tower, 3-10-10, Iidabashi, 
Chiyoda-ku, Tokyo 102-8460, Japan
Tel: +81-3-6678-2997
Fax: +81-3-6678-0286
tu-sawada@kddi.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 sipping-bounces@ietf.org Mon Jan 15 07:15:44 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6Qjd-0004h4-Ab; Mon, 15 Jan 2007 07:14:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6Qjb-0004gw-Tm
	for sipping@ietf.org; Mon, 15 Jan 2007 07:14:43 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6QjZ-000444-Hl
	for sipping@ietf.org; Mon, 15 Jan 2007 07:14:43 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 87E6C20031E5
	for <sipping@ietf.org>; Mon, 15 Jan 2007 13:15:13 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7nYDLh80g8YT for <sipping@ietf.org>;
	Mon, 15 Jan 2007 13:15:13 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 7562520001AF
	for <sipping@ietf.org>; Mon, 15 Jan 2007 13:15:13 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 15 Jan 2007 13:14:33 +0100
Message-ID: <113091BD57179D4491C19DA7E10CD696983EC5@mx1.office>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IETF Standardization related to SPIT
Thread-Index: Acc4nrd6cdisB0jmS72aYW4CWbwx3Q==
From: "Saverio Niccolini" <Saverio.Niccolini@netlab.nec.de>
To: <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [Sipping] IETF Standardization related to SPIT
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dear all,

In order to start a discussion on the question if there is a need for =
IETF=20
standards related to SPIT prevention, we have submitted an Internet =
draft
that tries to identify the need for standards on a very high level. =
Please
find it at:

http://www.ietf.org/internet-drafts/draft-niccolini-sipping-spitstop-00.t=
xt

We hope to refine this work and elaborate requirements for SPIT-related
standards in the next months and we would like to do it together with =
you.

For discussing the general need for standards we set up the spitstop =
mailing
list:

https://listserv.netlab.nec.de/mailman/listinfo/spitstop

You are very welcome to join this list and to invite other interested =
people
to do so.

I hope this topic is interesting to you and I look forward to vivid and
fruitful discussions with you.

Best regards,

  Saverio Niccolini

=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=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=3D=3D
Dr. Saverio Niccolini
Senior Research Staff Member
Network Laboratories, NEC Europe Ltd.
Kurfuerstenanlage 36, D-69115 Heidelberg
Tel.     +49 (0)6221 4342-118
Fax:     +49 (0)6221 4342-155
e-mail:  saverio.niccolini@netlab.nec.de
=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=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=3D=3D


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



From sipping-bounces@ietf.org Mon Jan 15 11:57:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6V8M-0002lo-Q6; Mon, 15 Jan 2007 11:56:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6V8L-0002jH-Kb
	for sipping@ietf.org; Mon, 15 Jan 2007 11:56:33 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6V8K-0002OW-34
	for sipping@ietf.org; Mon, 15 Jan 2007 11:56:33 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 15 Jan 2007 11:56:32 -0500
X-IronPort-AV: i="4.13,191,1167627600"; 
	d="scan'208"; a="111711796:sNHT60020932"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l0FGuVxU022028; 
	Mon, 15 Jan 2007 11:56:31 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l0FGuTOA021742; 
	Mon, 15 Jan 2007 11:56:29 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 15 Jan 2007 11:56:29 -0500
Received: from [10.86.242.232] ([10.86.242.232]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 15 Jan 2007 11:56:28 -0500
Message-ID: <45ABB23B.6020607@cisco.com>
Date: Mon, 15 Jan 2007 11:56:27 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Takuya Sawada <tu-sawada@kddi.com>
Subject: Re: [Sipping] Re: streaming media without sending 18x containing sdp
References: <BBE61D1553D8A34F812FF87377B2935F2D5E29@ATL1VEXC020.usdom003.tco.tc>	<45A7CC0E.4090705@cisco.com>
	<200701151308.FJD65600.XBBUtBVET@kddi.com>
In-Reply-To: <200701151308.FJD65600.XBBUtBVET@kddi.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Jan 2007 16:56:28.0584 (UTC)
	FILETIME=[197FE280:01C738C6]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8317; t=1168880191;
	x=1169744191; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Re=3A=20streaming=20media=20without=20sen
	ding=2018x=20containing=0A=20sdp |Sender:=20
	|To:=20Takuya=20Sawada=20<tu-sawada@kddi.com>;
	bh=znIWWwl59m6+xFBk1EVUSfgbIe/ZQwLAaPeWYymeTzc=;
	b=Kg+De+Sog2nqbg5q32kmsOncu0y5XXPWFdv8OvPBmvMiKGFgyAQIc+7o1BSwG12KzemuwiV5
	ZQ73IPHZHzStyRjvsuThIy3qGe4pS3wvNvCvXacE5gqP7zpnJMP6aS+B;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: sipping@ietf.org, brett@broadsoft.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Thinking about this further...

The only reason I can see for waiting until the answer has been sent 
before sending media is if the answer is needed by the offerer or 
something along the path between them for the media to reach its 
intended destination and be properly understood.

One example is when security descriptions are being exchanged.

Another case is when the offerer is itself only willing to receive media 
from a known source. (Note that the answer only defines the source for 
received media if the answerer's receiving port is also used for 
sending. This is not required by 3261 or 3264.)

Another case is when some middlebox is going to gate the media. The 
implications of that are much the same as if the answerer gates the 
media itself.

These are all special sub-cases of offer/answer, rather than being 
general. I think it might be better to formalize this kind of special 
behavior, and identify those cases where it does and does not apply. Key 
to this is that IMO there should be something explicit in the offer that 
  indicates to the answerer that the answer will be required before 
media can be received.

	Paul

Takuya Sawada wrote:
> Brett,
> 
> Actually so far I intended the offer/answer draft to be independent 
>>from the media layer, because;
> 
> 1) offer/answer exchange is not limited to sending/receiving media.
>   It can negotiate key management or pre-conditions, for example.
>   We want it to be general where possible.
> 2) early-media discussion is so controversial to be fixed here.
> 
> However, if it is useful, we can add something about the issue you raised 
> here. I am not sure but maybe we need to add new section or some notes
> to do that. As Paul said, we need further discussion.
> 
> IMHO, what is defined in RFCs is just to prepare to receive media when 
> sending SDP, and it may be enough in most cases.
> I do not know whether it is perfectly good thing to recommend not to send
> any media packets until it send out SDP answer. But possibly it can reduce
> the potential problems.
> 
> Regards,
> Takuya
> 
>> Brett,
>>
>> We have been trying to have the offeranswer draft explain things that 
>> are specified in standards and/or generally agreed to have been implied 
>> by the standards.
>>
>> IMO what you are asking doesn't, yet, fall into that category. I think 
>> we at least need some further list discussion leading to consensus about 
>> what correct behavior is in this case. What you are looking for may be:
>> - an explicit statement that the behavior you have seen is
>>    in fact legal, or
>> - a tightening of the specifications, declaring the kind of
>>    behavior you are concerned with to in fact be illegal, or
>> - a BCP specifying this behavior.
>>
>> Once there is a clear sense of the way to go on this, I think it *might* 
>> be appropriate for the offeranswer draft.
>>
>> I don't know if there are any important use cases where sending media 
>> before the answer is necessary. I'd be interested to hear if there are.
>>
>> 	Paul
>>
>> Brett Tate wrote:
>>> Paul, Takuya:
>>>
>>> In order to request modification to draft-ietf-sipping-sip-offeranswer,
>>> this email is the follow-up to my sip-implementors posting:
>>>
>>> https://lists.cs.columbia.edu/pipermail/sip-implementors/2007-January/01
>>> 5236.html
>>>
>>>
>>> As a means to bypass the offer/answer rules, some vendors are currently
>>> choosing to stream early media without placing an sdp within the 18x
>>> response.
>>>
>>> Since I have not noticed any draft/rfc explicitly discussing such
>>> behavior, I prefer it be discussed (valid/invalid
>>> encouraged/discouraged) within draft-ietf-sipping-sip-offeranswer.
>>>
>>> The following snapshot of the above link presents why I think such
>>> behavior should be clarified.  Even if some find rfc3264 clear
>>> concerning the topic, it seems like it would still be beneficial to
>>> discuss it within draft-ietf-sipping-sip-offeranswer.
>>>
>>> Thanks,
>>> Brett
>>>
>>>
>>> -----Original Message-----
>>> From: sip-implementors-bounces@cs.columbia.edu
>>> [mailto:sip-implementors-bounces@cs.columbia.edu] On Behalf Of Brett
>>> Tate
>>> Sent: Thursday, January 11, 2007 12:55 PM
>>> To: Paul Kyzivat
>>> Cc: tu-sawada@kddi.com; sip-implementors@cs.columbia.edu
>>> Subject: Re: [Sip-implementors] streaming media without sending
>>> 18xcontaining sdp
>>>
>>> Hi Paul,
>>>
>>> Thanks for the response.  My replies are inline.
>>>
>>>
>>>>> Some vendors are currently choosing to stream early media without 
>>>>> including an SDP within the 18x response.  Is such behavior 
>>>>> explicitly discouraged within an existing RFC?  And if not, should 
>>>>> text discussing/discouraging it be added to 
>>>>> draft-ietf-sipping-sip-offeranswer?
>>>> AFAIK there is nothing in 3261 to suggest that this is improper 
>>>> behavior. 3261 (or maybe it is 3264) explicitly says that the offerer 
>>>> should be prepared to receive media as soon as the offer is sent.
>>> Yes; the "MUST be prepared to receive" is discussed at the end of
>>> rfc3264 section 5.1.  And my understanding is that this text is to avoid
>>> clipping instead of giving the answerer approval to avoid sending an
>>> answer SDP or "preview" answer SDP.
>>>
>>> Section 6.1 discusses that the answerer may send media immediately after
>>> sending answer.  However I haven't found any text discussing the
>>> validity (valid or invalid) of sending media without also sending an
>>> answer SDP.
>>>
>>>
>>>> Nor am I aware of any more recent drafts or RFCs that try to impose 
>>>> any stronger rules, at least not normatively.
>>> My understanding is that it isn't discussed because nobody expected
>>> vendors to stream media without attempting to deliver an answer SDP or
>>> "preview" answer SDP.
>>>
>>> Wouldn't draft-ietf-sipping-sip-offeranswer be a good place to discuss
>>> the validity and if it is encouraged or discouraged?  (I will likely
>>> post a follow up to the sipping list.)
>>>
>>> RFC 3960 indirectly discusses it by discussing the problems of forking
>>> and early media.  However it doesn't specifically discuss the situation
>>> I'm asking about.
>>>
>>>  
>>>> I know there are deployed operating environments that make tighter 
>>>> assumptions, but I think these must be viewed as added requirements 
>>>> for those particular environments. You can perhaps find fault for a 
>>>> particular device not following such added rules, but I don't think it
>>>> is currently an ietf issue.
>>> I'm not looking to find fault.  I'm looking for clarification and if
>>> this it is encouraged or discouraged as a way to bypass the offer/answer
>>> rules.
>>>
>>>
>>>>> I assume the vendors are attempting to bypass the various rules and 
>>>>> complexities of offer/answer by trying to take advantage of products
>>>>> willing to render the media (to avoid clipping) under the pretence 
>>>>> that the related 18x/200 containing the SDP is slow to arrive.
>>>>>
>>>>> Some of the reasons to discourage such behavior is discussed within 
>>>>> rfc3960.  However I have not found any text explicitly discussing 
>>>>> devices acting like answer SDP or "preview" answer SDP has been sent
>>>>> without intention of actually sending it.
>>>> If there is consensus that such behavior is to be mandated then it 
>>>> will take some new draft to do it.
>>> I'm not asking for a mandate.  I'm asking for a sip related IETF
>>> document to discuss it.  If people think it is a good way to bypass the
>>> offer/answer model; it should be encouraged.  If people think it is a
>>> bad thing, it should be discouraged.
>>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sip@ietf.org for new developments of core SIP
>>
> 
> --------
> Takuya Sawada
> KDDI Corporation (KDDI)
> Garden Air Tower, 3-10-10, Iidabashi, 
> Chiyoda-ku, Tokyo 102-8460, Japan
> Tel: +81-3-6678-2997
> Fax: +81-3-6678-0286
> tu-sawada@kddi.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 sipping-bounces@ietf.org Mon Jan 15 12:01:29 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6VCq-0005JP-93; Mon, 15 Jan 2007 12:01:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6VCo-0005JI-P6
	for sipping@ietf.org; Mon, 15 Jan 2007 12:01:10 -0500
Received: from out002.iad.hostedmail.net ([209.225.56.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6VCm-00034A-Ap
	for sipping@ietf.org; Mon, 15 Jan 2007 12:01:10 -0500
Received: from ATL1VEXC020.usdom003.tco.tc ([10.158.7.31]) by
	out002.iad.hostedmail.net with Microsoft SMTPSVC(6.0.3790.1830);
	Mon, 15 Jan 2007 12:01:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: streaming media without sending 18x containing sdp
Date: Mon, 15 Jan 2007 12:01:02 -0500
Message-ID: <BBE61D1553D8A34F812FF87377B2935F2D63C8@ATL1VEXC020.usdom003.tco.tc>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] RE: streaming media without sending 18x containing sdp
Thread-Index: Acc2cyWo5woenYKCRiWfSFCAV9Z6WwACe3HwACaPBWAAapYn4A==
From: "Brett Tate" <brett@broadsoft.com>
To: "Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
X-OriginalArrivalTime: 15 Jan 2007 17:01:03.0596 (UTC)
	FILETIME=[BD6B62C0:01C738C6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

> > As far as I know, there are two reasons. =20
> > However the importance level is debatable since=20
> > I really think it is just a lack of desire to=20
> > comply with the spirit of rfc3264.
> >=20
> > 1) Simplification: avoid the restrictions and=20
> > complication caused by the only 1 answer rules. =20
> > Thus violate the spirit of rfc3264 and act as
> > answerer without actually sending the SDP. :)
> >=20
> > 2) Optimization: avoid the extra dialogs,=20
> > UPDATEs, or re-INVITEs which would have been=20
> > required by sending different SDPs when=20
> > early-session (rfc3959) not used or adequate. =20
> > For instance if not using early-session, extra=20
> > messaging would be required if first wanted=20
> > return SDP containing sendonly and subsequently=20
> > send SDP containing sendrecv.
>=20
> Both cases can be solved with a very simple trick:=20
> changing of the To tag. If the UAS wants to change=20
> the answer, it simply changes the To tag in the=20
> response (18x or 200) where the new answer is sent.=20
> No need for any UPDATE or re-INVITE, and no=20
> violation of any RFC.

Thanks for the response.

I agree that the solution can be used; this solution was what I was
implying by the "extra dialogs".

The "no violation of any RFC" aspects of your comment is one of things
I'm attempting to get clarified within
draft-ietf-sipping-sip-offeranswer.  Some are interpreting the RFCs to
indicate that there is no violation.

If anyone has an opinion on the matter, please reply to the list even if
you think no clarity should be provided within
draft-ietf-sipping-sip-offeranswer.

Thanks,
Brett

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



From sipping-bounces@ietf.org Mon Jan 15 12:52:24 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6W09-0005Lp-5J; Mon, 15 Jan 2007 12:52:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6W08-0005KX-44
	for sipping@ietf.org; Mon, 15 Jan 2007 12:52:08 -0500
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6VvN-00017A-CV
	for sipping@ietf.org; Mon, 15 Jan 2007 12:47:14 -0500
Received: from [192.168.1.128] (unknown [91.89.53.224])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id B2ADB13CF82
	for <sipping@ietf.org>; Mon, 15 Jan 2007 18:54:22 +0100 (CET)
Date: Mon, 15 Jan 2007 18:47:11 +0100
From: Juergen Quittek <quittek@netlab.nec.de>
To: sipping@ietf.org
Subject: Re: [Sipping] IETF Standardization related to SPIT
Message-ID: <1087197A2B3C350CCAF33199@juergen-quitteks-computer.local>
In-Reply-To: <113091BD57179D4491C19DA7E10CD696983EC5@mx1.office>
References: <113091BD57179D4491C19DA7E10CD696983EC5@mx1.office>
X-Mailer: Mulberry/4.0.5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dear all,

One of the goals of discussions on the spitstop mailing list
would be having a BoF on SPIT-related issues at IETF#69 in Chicago.

Thanks,

    Juergen


--On 15.01.07 13:14 +0100 Saverio Niccolini wrote:

> Dear all,
>
> In order to start a discussion on the question if there is a need for IETF
> standards related to SPIT prevention, we have submitted an Internet draft
> that tries to identify the need for standards on a very high level. Please
> find it at:
>
> http://www.ietf.org/internet-drafts/draft-niccolini-sipping-spitstop-00.txt
>
> We hope to refine this work and elaborate requirements for SPIT-related
> standards in the next months and we would like to do it together with you.
>
> For discussing the general need for standards we set up the spitstop mailing
> list:
>
> https://listserv.netlab.nec.de/mailman/listinfo/spitstop
>
> You are very welcome to join this list and to invite other interested people
> to do so.
>
> I hope this topic is interesting to you and I look forward to vivid and
> fruitful discussions with you.
>
> Best regards,
>
>   Saverio Niccolini
>
> ============================================================
> Dr. Saverio Niccolini
> Senior Research Staff Member
> Network Laboratories, NEC Europe Ltd.
> Kurfuerstenanlage 36, D-69115 Heidelberg
> Tel.     +49 (0)6221 4342-118
> Fax:     +49 (0)6221 4342-155
> e-mail:  saverio.niccolini@netlab.nec.de
> ============================================================
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP



-- 
Juergen Quittek        quittek@netlab.nec.de       Tel: +49 6221 4342-115
NEC Europe Ltd.,       Network Laboratories        Fax: +49 6221 4342-155
Kurfuersten-Anlage 36, 69115 Heidelberg, Germany   http://www.netlab.nec.de

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



From sipping-bounces@ietf.org Mon Jan 15 14:46:11 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6XkL-00078F-NS; Mon, 15 Jan 2007 14:43:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6XkJ-000760-TD
	for sipping@ietf.org; Mon, 15 Jan 2007 14:43:55 -0500
Received: from out001.iad.hostedmail.net ([209.225.56.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6XkI-0007nV-NE
	for sipping@ietf.org; Mon, 15 Jan 2007 14:43:55 -0500
Received: from ATL1VEXC020.usdom003.tco.tc ([10.158.7.31]) by
	out001.iad.hostedmail.net with Microsoft SMTPSVC(6.0.3790.1830);
	Mon, 15 Jan 2007 14:43:54 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Re: streaming media without sending 18x containing sdp
Date: Mon, 15 Jan 2007 14:43:53 -0500
Message-ID: <BBE61D1553D8A34F812FF87377B2935F2D644D@ATL1VEXC020.usdom003.tco.tc>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Re: streaming media without sending 18x containing sdp
Thread-Index: Acc4Wsn856GWADKcTCK9I+FxXcuoDwAbTOEg
From: "Brett Tate" <brett@broadsoft.com>
To: "Takuya Sawada" <tu-sawada@kddi.com>
X-OriginalArrivalTime: 15 Jan 2007 19:43:54.0295 (UTC)
	FILETIME=[7D35BC70:01C738DD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

> IMHO, what is defined in RFCs is just to prepare=20
> to receive media when sending SDP, and it may=20
> be enough in most cases.

The last paragraph of rfc3264 section 6.1 also places restrictions upon
the answerer concerning sending media.


> I do not know whether it is perfectly good=20
> thing to recommend not to send any media packets=20
> until it send out SDP answer. But possibly it can=20
> reduce the potential problems.

Because there can be delays in actually streaming the answer SDP or
"preview" answer SDP (like reopening a TCP connection), I'm not
necessarily advocating waiting until the answer SDP actually gets sent.
I'm more trying to clarify if it is considered appropriate to act as
answerer without sending or attempting to send a 18x containing an
answer SDP or "preview" answer SDP.

If it is appropriate, I guess that the 6.1 answerer restrictions don't
apply until the answer SDP is sent.

Within an offer/answer model, it seems a little strange to not define as
"answerers" those sending media in response to offer (or those acting
answerer upon their behalf).  However I guess that it is all a matter of
definition.

Thanks for the response,
Brett

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



From sipping-bounces@ietf.org Mon Jan 15 15:59:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6Yv5-0004z4-P9; Mon, 15 Jan 2007 15:59:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6Yv3-0004yj-Uz
	for sipping@ietf.org; Mon, 15 Jan 2007 15:59:05 -0500
Received: from rwcrmhc13.comcast.net ([204.127.192.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6Yv2-0002gH-Lg
	for sipping@ietf.org; Mon, 15 Jan 2007 15:59:05 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc13) with ESMTP
	id <20070115205903m1300buimge>; Mon, 15 Jan 2007 20:59:03 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l0FKx2bM024069
	for <sipping@ietf.org>; Mon, 15 Jan 2007 15:59:02 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l0FKx2nc024065;
	Mon, 15 Jan 2007 15:59:02 -0500
Date: Mon, 15 Jan 2007 15:59:02 -0500
Message-Id: <200701152059.l0FKx2nc024065@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <113091BD57179D4491C19DA7E10CD696983EC5@mx1.office>
	(Saverio.Niccolini@netlab.nec.de)
Subject: Re: [Sipping] IETF Standardization related to SPIT
References: <113091BD57179D4491C19DA7E10CD696983EC5@mx1.office>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Saverio Niccolini" <Saverio.Niccolini@netlab.nec.de>

   In order to start a discussion on the question if there is a need for IETF 
   standards related to SPIT prevention, we have submitted an Internet draft
   that tries to identify the need for standards on a very high level. Please
   find it at:

   http://www.ietf.org/internet-drafts/draft-niccolini-sipping-spitstop-00.txt

   We hope to refine this work and elaborate requirements for SPIT-related
   standards in the next months and we would like to do it together with you.

It seems like this I-D presupposes a particular model of how SPIT
prevention will be implemented, but it does not make explicit what
that model is.  Given that SPIT prevention has not yet been
implemented anywhere, shouldn't we first be discussing the model and
whether it suffices for SPIT prevention before attempting to
standardize the details of how the components implied by the model
will communicate?

Dale

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



From sipping-bounces@ietf.org Mon Jan 15 16:40:54 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6ZZD-0003Qv-49; Mon, 15 Jan 2007 16:40:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6ZZB-0003QA-8X
	for sipping@ietf.org; Mon, 15 Jan 2007 16:40:33 -0500
Received: from rwcrmhc14.comcast.net ([216.148.227.154])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6ZYv-0000NN-NN
	for sipping@ietf.org; Mon, 15 Jan 2007 16:40:32 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc14) with ESMTP
	id <20070115214016m140035l7se>; Mon, 15 Jan 2007 21:40:16 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l0FLeFbM024629
	for <sipping@ietf.org>; Mon, 15 Jan 2007 16:40:15 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l0FLeF0R024625;
	Mon, 15 Jan 2007 16:40:15 -0500
Date: Mon, 15 Jan 2007 16:40:15 -0500
Message-Id: <200701152140.l0FLeF0R024625@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <A09345776B6C7A4985573569C0F300430EAE520E@rrc-dte-exs01.dte.telcordia.com>
	(jhaluska@telcordia.com)
Subject: Re: [Sipping] Some more thoughts on
	draft-haluska-sipping-directory-assistance-01.txt
References: <A09345776B6C7A4985573569C0F300430EAE520E@rrc-dte-exs01.dte.telcordia.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Haluska, John J" <jhaluska@telcordia.com>

   >* The range of business models considered seems to be quite narrow:
   >
   >   There are several network scenarios which must be supported:
   >
   >   Services are provided by the caller's home provider.
   >
   >   Services are provided a third party provider which has direct SIP
   >   layer connectivity as well as business relationships with the
   >   caller's home provider.
   >
   >   Services are provided a third party provider which has no direct SIP
   >   layer connectivity and no business relationships with the caller's
   >   home provider.
   >
   >For instance, consider "Services are provided a third party provider
   >which has direct SIP layer connectivity but no business relationships
   >with the caller's home provider. " and "Services are provided a third
   >party provider which has no business relationships with the caller,
   >but does have a business relationship with another third party
   >provider which has a direct business relationship with the caller."
   >And I expect a little thought could construct many other cases.  Any
   >proposed mechanisms should work in a broad range of business models.

   JH - yes. I've also been thinking that SPEERMINT might have some
   thoughts about this, since a lot of what they deal with is driven
   by business relationships between providers.

Permit me to suggest that you might consider information services that
are *not* driven by business relationships between providers, but are
freely chosen by the customers, outside the control of their
communication providers.

Indeed, let me make that statement stronger -- If you propose a
mechanism that constrains SIP users to only use information services
chosen and approved by their communication providers, and that
mechanism is somehow implemented, thousands of "net-heads" will work
night and day to subvert that control by the communication providers.

That is what is called "an open network".

The economic driver of Internet adoption is freeing users from the
control of their communication providers, and many people are very
passionate about that.  Do not attempt to standardize (though the
IETF!) an approach that the Internet community sees as necessary to
destroy.

Remember: VoIP was started by people who didn't want to pay the high
international voice charges between Israel and the US.

Dale

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



From sipping-bounces@ietf.org Mon Jan 15 17:14:42 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6a61-0004bQ-2J; Mon, 15 Jan 2007 17:14:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6a5z-0004UG-LB
	for sipping@ietf.org; Mon, 15 Jan 2007 17:14:27 -0500
Received: from chip2og54.obsmtp.com ([64.18.13.45])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H6a5y-0004o8-9Z
	for sipping@ietf.org; Mon, 15 Jan 2007 17:14:27 -0500
Received: from source ([192.150.11.134]) by chip2ob54.postini.com
	([64.18.5.12]) with SMTP; Mon, 15 Jan 2007 14:13:36 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com
	[192.150.20.198] (may be forged))
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l0FMAMvV001216; Mon, 15 Jan 2007 14:10:26 -0800 (PST)
Received: from fe2.corp.adobe.com (fe2.corp.adobe.com [10.8.192.72])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	l0FMDUeA009587; Mon, 15 Jan 2007 14:13:30 -0800 (PST)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe2.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 15 Jan 2007 14:13:30 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Some more thoughts
	ondraft-haluska-sipping-directory-assistance-01.txt
Date: Mon, 15 Jan 2007 14:13:12 -0800
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223ADDD0@namail5.corp.adobe.com>
In-Reply-To: <200701152140.l0FLeF0R024625@dragon.ariadne.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Some more thoughts
	ondraft-haluska-sipping-directory-assistance-01.txt
Thread-Index: Acc47eY+GEriaPESQr2NqzSgmNLFAQAA66Qg
References: <A09345776B6C7A4985573569C0F300430EAE520E@rrc-dte-exs01.dte.telcordia.com>
	<200701152140.l0FLeF0R024625@dragon.ariadne.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: <Dale.Worley@comcast.net>, <sipping@ietf.org>
X-OriginalArrivalTime: 15 Jan 2007 22:13:30.0014 (UTC)
	FILETIME=[6327C3E0:01C738F2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

>freely chosen by the customers, outside the control of their
>communication providers

100% correct.

I could only add: Models based on roaming charges such as the Visiting
Proxy are a rip-off for the users.

Such models have nothing to do with Internet usage which is mostly e2e
for the media (or using a media relay if there is no ICE) and two
proxies like in the trapezoid model in RFC 3261.

Thanks, Henry

-----Original Message-----
From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]=20
Sent: Monday, January 15, 2007 3:40 PM
To: sipping@ietf.org
Subject: Re: [Sipping] Some more thoughts
ondraft-haluska-sipping-directory-assistance-01.txt

   From: "Haluska, John J" <jhaluska@telcordia.com>

   >* The range of business models considered seems to be quite narrow:
   >
   >   There are several network scenarios which must be supported:
   >
   >   Services are provided by the caller's home provider.
   >
   >   Services are provided a third party provider which has direct SIP
   >   layer connectivity as well as business relationships with the
   >   caller's home provider.
   >
   >   Services are provided a third party provider which has no direct
SIP
   >   layer connectivity and no business relationships with the
caller's
   >   home provider.
   >
   >For instance, consider "Services are provided a third party provider
   >which has direct SIP layer connectivity but no business
relationships
   >with the caller's home provider. " and "Services are provided a
third
   >party provider which has no business relationships with the caller,
   >but does have a business relationship with another third party
   >provider which has a direct business relationship with the caller."
   >And I expect a little thought could construct many other cases.  Any
   >proposed mechanisms should work in a broad range of business models.

   JH - yes. I've also been thinking that SPEERMINT might have some
   thoughts about this, since a lot of what they deal with is driven
   by business relationships between providers.

Permit me to suggest that you might consider information services that
are *not* driven by business relationships between providers, but are
freely chosen by the customers, outside the control of their
communication providers.

Indeed, let me make that statement stronger -- If you propose a
mechanism that constrains SIP users to only use information services
chosen and approved by their communication providers, and that
mechanism is somehow implemented, thousands of "net-heads" will work
night and day to subvert that control by the communication providers.

That is what is called "an open network".

The economic driver of Internet adoption is freeing users from the
control of their communication providers, and many people are very
passionate about that.  Do not attempt to standardize (though the
IETF!) an approach that the Internet community sees as necessary to
destroy.

Remember: VoIP was started by people who didn't want to pay the high
international voice charges between Israel and the US.

Dale

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org Mon Jan 15 17:39:48 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6aU9-0003qJ-9W; Mon, 15 Jan 2007 17:39:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6aU8-0003p7-36
	for sipping@ietf.org; Mon, 15 Jan 2007 17:39:24 -0500
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6aU6-0008RX-NP
	for sipping@ietf.org; Mon, 15 Jan 2007 17:39:24 -0500
Received: from [192.168.1.128] (unknown [91.89.53.224])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id A31A113CF82;
	Mon, 15 Jan 2007 23:46:32 +0100 (CET)
Date: Mon, 15 Jan 2007 23:39:20 +0100
From: Juergen Quittek <quittek@netlab.nec.de>
To: Dale.Worley@comcast.net, sipping@ietf.org
Subject: Re: [Sipping] IETF Standardization related to SPIT
Message-ID: <D8D16346B3FE9482EC7F582C@juergen-quitteks-computer.local>
In-Reply-To: <200701152059.l0FKx2nc024065@dragon.ariadne.com>
References: <113091BD57179D4491C19DA7E10CD696983EC5@mx1.office>
	<200701152059.l0FKx2nc024065@dragon.ariadne.com>
X-Mailer: Mulberry/4.0.5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi Dale,

--On 15.01.07 21:59 +0100 Dale.Worley@comcast.net wrote:

>
>    From: "Saverio Niccolini" <Saverio.Niccolini@netlab.nec.de>
>
>    In order to start a discussion on the question if there is a need for IETF
>    standards related to SPIT prevention, we have submitted an Internet draft
>    that tries to identify the need for standards on a very high level. Please
>    find it at:
>
>    http://www.ietf.org/internet-drafts/draft-niccolini-sipping-spitstop-00.txt
>
>    We hope to refine this work and elaborate requirements for SPIT-related
>    standards in the next months and we would like to do it together with you.
>
> It seems like this I-D presupposes a particular model of how SPIT
> prevention will be implemented, but it does not make explicit what
> that model is.  Given that SPIT prevention has not yet been
> implemented anywhere, shouldn't we first be discussing the model and
> whether it suffices for SPIT prevention before attempting to
> standardize the details of how the components implied by the model
> will communicate?

We have a running system that we use for testing purposes in our office
and demonstrated at ITU Telecom 06 in Hong Kong.

Of course we had this system in the back of our heads when writing the draft.
But we do not think that our way is the only way to build a SPIT prevention
system.  We tried to be rather generic in the draft and start this discussion
in order to also include other views and alternative systems - maybe better
ones than ours ;-)

Thanks,

    Juergen

> Dale
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org Mon Jan 15 18:47:37 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6bXU-0006ql-0N; Mon, 15 Jan 2007 18:46:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6bXS-0006qf-Fa
	for sipping@ietf.org; Mon, 15 Jan 2007 18:46:54 -0500
Received: from out002.iad.hostedmail.net ([209.225.56.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6bXQ-00007g-8k
	for sipping@ietf.org; Mon, 15 Jan 2007 18:46:54 -0500
Received: from ATL1VEXC020.usdom003.tco.tc ([10.158.7.31]) by
	out002.iad.hostedmail.net with Microsoft SMTPSVC(6.0.3790.1830);
	Mon, 15 Jan 2007 18:46:49 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Re: streaming media without sending 18x containing sdp
Date: Mon, 15 Jan 2007 18:46:49 -0500
Message-ID: <BBE61D1553D8A34F812FF87377B2935F2D6547@ATL1VEXC020.usdom003.tco.tc>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Re: streaming media without sending 18x containing sdp
Thread-Index: Acc4xhxnSvq1WyM3TgeRyT3trHJq6QAGY+cQ
From: "Brett Tate" <brett@broadsoft.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 15 Jan 2007 23:46:49.0887 (UTC)
	FILETIME=[6CF092F0:01C738FF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

> The only reason I can see for waiting until the=20
> answer has been sent before sending media is if=20
> the answer is needed by the offerer or something=20
> along the path between them for the media to reach=20
> its intended destination and be properly understood.

<snip>

> These are all special sub-cases of offer/answer,=20
> rather than being general. I think it might be=20
> better to formalize this kind of special behavior,=20
> and identify those cases where it does and does=20
> not apply. Key to this is that IMO there should=20
> be something explicit in the offer that indicates=20
> to the answerer that the answer will be required=20
> before media can be received.

The "special sub-cases" that you mention are reasons to ensure answer
delivery before uselessly streaming media within the time between answer
sent and answer received.

Within the offer/answer model, the answerer may stream immediately upon
sending the answer (rfc3264 section 6.1 last paragraph).  Within the
offer/answer model, I have seen no indication that media may be streamed
prior to sending the answer.  Otherwise SIP is only using an
offer/answer model when the answer is sent instead of also following it
prior to sending the answer SDP or "preview" answer SDP.  However of
course, I might be misinterpreting rfc3264. :) =20

If something is needed to avoid uselessly streaming media during the
time between offer received and answer received, RFC 3959 and RFC 3960
provide a decent solution.  The solution follows the offer/answer model
and provides a decent forking solution.

Because of forking concerns and clipping concerns (and delay of new
offer until answer), I am unaware of a solution which could solely rely
upon offerer including something within the INVITE.  However of course,
that doesn't mean someone couldn't define an enhancement to offer/answer
or something to only solve a portion of the problem.


Thanks for the response,
Brett

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



From sipping-bounces@ietf.org Mon Jan 15 22:22:37 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6esu-0005in-FZ; Mon, 15 Jan 2007 22:21:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6est-0005ib-0V
	for sipping@ietf.org; Mon, 15 Jan 2007 22:21:15 -0500
Received: from rwcrmhc14.comcast.net ([204.127.192.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6esq-0007na-Mu
	for sipping@ietf.org; Mon, 15 Jan 2007 22:21:14 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc14) with ESMTP
	id <20070116032109m140035uk6e>; Tue, 16 Jan 2007 03:21:09 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l0G3L8bM003177
	for <sipping@ietf.org>; Mon, 15 Jan 2007 22:21:08 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l0G3L8bL003173;
	Mon, 15 Jan 2007 22:21:08 -0500
Date: Mon, 15 Jan 2007 22:21:08 -0500
Message-Id: <200701160321.l0G3L8bL003173@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <D8D16346B3FE9482EC7F582C@juergen-quitteks-computer.local>
Subject: Re: [Sipping] IETF Standardization related to SPIT
References: <113091BD57179D4491C19DA7E10CD696983EC5@mx1.office>
	<200701152059.l0FKx2nc024065@dragon.ariadne.com>
	<D8D16346B3FE9482EC7F582C@juergen-quitteks-computer.local>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: Juergen Quittek <quittek@netlab.nec.de>

   We have a running system that we use for testing purposes in our
   office and demonstrated at ITU Telecom 06 in Hong Kong.

Nice!

   Of course we had this system in the back of our heads when writing
   the draft.  But we do not think that our way is the only way to
   build a SPIT prevention system.  We tried to be rather generic in
   the draft and start this discussion in order to also include other
   views and alternative systems - maybe better ones than ours ;-)

I don't want to seem to be a complainer, but when I read the draft, it
was clear to me that you had already made many architecture decisions
about the system, it did not seem very generic to me.

Dale

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



From sipping-bounces@ietf.org Tue Jan 16 03:09:52 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6jMe-0000it-Jg; Tue, 16 Jan 2007 03:08:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6jMd-0000il-Er
	for sipping@ietf.org; Tue, 16 Jan 2007 03:08:15 -0500
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6jMb-0000MV-2B
	for sipping@ietf.org; Tue, 16 Jan 2007 03:08:15 -0500
Received: from [10.1.1.104] (mito.netlab.nec.de [195.37.70.39])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id 119D413CF82;
	Tue, 16 Jan 2007 09:15:25 +0100 (CET)
Date: Tue, 16 Jan 2007 09:08:13 +0100
From: Juergen Quittek <quittek@netlab.nec.de>
To: Dale.Worley@comcast.net, sipping@ietf.org
Subject: Re: [Sipping] IETF Standardization related to SPIT
Message-ID: <55A76550CF5FDA3181B0571C@n-quittek2.office>
In-Reply-To: <200701160321.l0G3L8bL003173@dragon.ariadne.com>
References: <113091BD57179D4491C19DA7E10CD696983EC5@mx1.office>	<200701152059.l0FKx2nc024065@dragon.ariadne.com>	<D8D16346B3FE9482EC7F582C@juergen-quitteks-computer.local>
	<200701160321.l0G3L8bL003173@dragon.ariadne.com>
X-Mailer: Mulberry/4.0.5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi Dale,

--On 15.01.07 22:21 -0500 Dale.Worley@comcast.net wrote:

>    From: Juergen Quittek <quittek@netlab.nec.de>
>
>    We have a running system that we use for testing purposes in our
>    office and demonstrated at ITU Telecom 06 in Hong Kong.
>
> Nice!
>
>    Of course we had this system in the back of our heads when writing
>    the draft.  But we do not think that our way is the only way to
>    build a SPIT prevention system.  We tried to be rather generic in
>    the draft and start this discussion in order to also include other
>    views and alternative systems - maybe better ones than ours ;-)
>
> I don't want to seem to be a complainer, but when I read the draft, it
> was clear to me that you had already made many architecture decisions
> about the system, it did not seem very generic to me.

I think you're right.  But that's why we want to have a public discussion
on the general topic.  We do not insist on the architectural assumptions
made in our draft but rather look forward to improve (or radically change)
them based on feedback from the community.  Just for starting the
discussion we had to present something: our view.

Thanks,

    Juergen

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



-- 
Juergen Quittek        quittek@netlab.nec.de       Tel: +49 6221 4342-115
NEC Europe Ltd.,       Network Laboratories        Fax: +49 6221 4342-155
Kurfuersten-Anlage 36, 69115 Heidelberg, Germany   http://www.netlab.nec.de

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



From sipping-bounces@ietf.org Tue Jan 16 09:56:28 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6pip-0001nE-Eh; Tue, 16 Jan 2007 09:55:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H6pio-0001lx-MD
	for sipping@ietf.org; Tue, 16 Jan 2007 09:55:34 -0500
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6pim-0004wT-CU
	for sipping@ietf.org; Tue, 16 Jan 2007 09:55:34 -0500
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l0GEtV2g011814
	for <sipping@ietf.org>; Tue, 16 Jan 2007 08:55:31 -0600 (CST)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90])
	by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l0GEtVu12770
	for <sipping@ietf.org>; Tue, 16 Jan 2007 08:55:31 -0600 (CST)
Message-ID: <45ACE763.6070704@alcatel-lucent.com>
Date: Tue, 16 Jan 2007 08:55:31 -0600
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: SIPPING LIST <sipping@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [Sipping] In preparation for WGLC of SIP/IPv6 Torture Tests
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Folks: Over the next two weeks we will be updating SIP/IPv6
torture test draft for WGLC (available at
http://www.ietf.org/internet-drafts/draft-ietf-sipping-ipv6-torture-tests-00.txt).

The idea is to have WGLC done between Jan 29 - Feb 16, and have
it well on its way by the Prague IETF.

If you can think of any other tests to add to the document, please
let one of the co-authors know.

Thank you.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs

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



From sipping-bounces@ietf.org Thu Jan 18 04:59:47 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H7U2m-0002AX-Su; Thu, 18 Jan 2007 04:58:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H7U2k-00025m-Dn
	for sipping@ietf.org; Thu, 18 Jan 2007 04:58:50 -0500
Received: from eastmail1.ntt-east.co.jp ([202.229.5.44]
	helo=evx1.enoc.east.ntt.co.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H7U2j-0005Z5-2n
	for sipping@ietf.org; Thu, 18 Jan 2007 04:58:50 -0500
Received: from emix1.enoc.east.ntt.co.jp 
	by evx1.enoc.east.ntt.co.jp with ESMTP id l0I9whY14669;
	Thu, 18 Jan 2007 18:58:43 +0900 (JST)
Received: from cip9.noc.east.ntt.co.jp 
	by emix1.enoc.east.ntt.co.jp with ESMTP id l0I9whx27975;
	Thu, 18 Jan 2007 18:58:43 +0900 (JST)
Received: from mail.east.ntt.co.jp ([10.8.52.77])
	by cip9.noc.east.ntt.co.jp (MOS 3.4.6-GR) with SMTP id CLX10185;
	Thu, 18 Jan 2007 18:58:42 +0900 (JST)
Message-Id: <200701180958.CLX10185@cip9.noc.east.ntt.co.jp>
Date: Thu, 18 Jan 2007 18:59:22 +0900
From: Miki HASEBE <hasebe.miki@east.ntt.co.jp>
X-Mailer: EdMax Ver2.85.5F
MIME-Version: 1.0
To: Dale.Worley@comcast.net
Subject: Re: [Sipping] Comments on draft-ietf-sipping-race-examples-00
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
In-Reply-To: <200612280403.kBS432vQ006508@dragon.ariadne.com>
References: <200612280403.kBS432vQ006508@dragon.ariadne.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: fec852dbea6d068499ed3250edf328e2
Cc: pkyzivat@cisco.com, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Thank you for your many usuful comments.
I apologize for late reply.
My opinions inline.

Dale.Worley@comcast.net wrote:

> I've read over draft-ietf-sipping-race-examples-00.  Please consider
> the following questions for clarification.
> 
> Thanks,
> 
> Dale
> ----------------------------------------------------------------------
> ** Content
> 
> In section 2:
> 
> * Figure 1:  The figure does not show the generation of DSMs by new
> tags as clearly as it might.  The difficulty is that the new DSMs are
> not really generated by the existing DSM (the DSM for the first dialog
> generated by the early dialog).  In reality, DSMs are generated from
> the INVITE transaction -- as long as the INVITE transaction is alive,
> if it receives a response with a new tag, a DSM is generated for the
> dialog created by that response.
> 
> There is one exception -- the first DSM, in the Trying state, is
> generated when the INVITE is sent, and the first to-tag that is
> received causes that DSM to transition into the other states.
> 
> Later new to-tags cause the generation of new DSMs in much the same
> way that the first DSM is generated.  But since new DSMs are generated
> by responses with tags, they start in the Early, Confirmed, or
> Terminated state, never the Preparative state.

I agree that the draft has to be clear about what you pointed out.
The figure does not show the exact behavior when a response to
INVITE with a different To-tag is received in forking.

Below is how I understand your point.

For example, multiple early dialogs are established when responses
with different To-tag (here, A, B, and C) are received.
If a 2xx response with the To-tag B is received, only the early dialog
related to the tag B moves to the Confirmed state.
The other early dialogs, related to the tags A and C, are terminated
in 64*T1 after the reception of the 2xx with the tag B.

In sum, I have to describe the influence on the INVITE transaction
to state the exact behavior of mulitple early dialogs in forking.

Also, if a 2xx response with another To-tag is received in 64*T1
after the reception of the 2xx with the first tag, the early dialog
related to the second tag also moves to the Confirmed state,
resulting in the establishment of multiple confirmed dialogs.
A UAC usually does not receive multiple 2xx responses like this,
because a proxy which forked send CANCEL after it receives
a 200 response.
However, if there is a crossover of CANCEL and 2xx between the
forking proxy and a UAS, the reception of multiple 2xx with
different To-tags can happen.

The behavior of UAC in this case will be an implementational matter,
but I think the UAC will usually terminate by BYE as in CANCEL
crossover (Section 3.1.2).

I think it is difficult to include the forking case in one figure because
the handling of the dialog in forking is complicated.
Threrefore I may address this issue by adding another appendix for
the behavior in forking if necessary.
I will post to SIPPING ML about this, so I hope you could wait for that.


> * Figure 1:  There seem to be missing cases:  BYE(r) will transition
> from Early and Confirmed to Mortal.

As you pointed out, the state moves to the Mortal state
after receiving BYE.
But, Figure 1 and 2 are not for the caller (e.g. Alice) and
callee (e.g. Bob), but generalized for UAC and UAS.
Therefore, Figure 2 has to be checked, instead of Figure 1,
to know the state transition upon the reception of BYE in
for example, the Early and Confirmed state.

The reason for making two figures is as follows.
A UAC is a caller when sending an INVITE request, but
this combination is invalid from the Confirmed state and
after. This would require different figures for all combinations,
caller+UAC, caller+UAS and so on, making figures more
complicated. Therefore, the figures are generalized for UAC
and UAS to simplify the figures.

So, Figure 2 has to be referred to know the behavior of UAS
upon the reception of BYE in the Confirmed state, regardless
of caller or callee.


> * The handling of ACK is more complicated than is shown here.  For
> instance, if BYE is sent or received in Moratorium state, the dialog
> goes to Mortal state, but it must still send ACK.  
> 
> For example, see the figure in section 3.1.6.  The UAC in Mortal state
> receives 200 for an INVITE, and must re-send ACK.  Neither the receive
> nor the send are shown as possible in Figure 1.
> 
> Might it be better to consider ACK part of the INVITE transaction
> (despite that it has a different CSeq number), and leave sending the
> ACK to the INVITE transaction state machine, rather than having the
> DSM send it?

Your point is absolutely right.
ACK can be sent in the Mortal state.
Care is needed for the ACK for 200 because it is generated
as a new request, but this is related to the INVITE three-way
handshake.
This is not expressed in the figure, but its handling is detailed
in Appendix D.

ACK is not expressed in the figure simply because it does not
involve in the dialog state transition.
Other messages which are not related to the state transition,
e.g. re-INVITE and UPDATE in the Confirmed state, are also
not illustrated in the figure.
This does not mean that it is banned to send messages which
are not in the figure. It just tries to omit the unrelated messages
for simplification.

I would like to handle this issue by adding some text to explain
this as above.
Do you think it is agreeable?


> * In the state diagrams, I think it would be easier to understand the
> designations of the states if they were placed below the message
> send/receive that causes the transition into the state.  This is
> because the UA is in that state for a period of time, rather than at a
> particular moment, and placing the label below the message shows that
> the state continues downward until the next state.
> 
> For example, change this:
> 
>   State  Alice                               Bob  State
>          |                                     |
>          |            ini-INVITE F1            |
>     Pre  |------------------------------------>|  Pre
>          |         180 F2(Packet loss)         |
>          |            x<-----------------------|  Ear
>          |                                     |
>          | ini-INVITE(=F1) F4           200 F3 |
>          |------------------     --------------|  Mora
>          |                   \ /               |
>          |                    X                |
>          |                   / \               |
>    Mora  |<-----------------     ------------->|  *race*
>          |                ACK F5               |
>     Est  |------------------------------------>|  Est
>          |                                     |
>          |                                     |
> 
> into this:
> 
>   State  Alice                               Bob  State
>          |                                     |
>          |            ini-INVITE F1            |
>          |------------------------------------>|  
>     Pre  |         180 F2(Packet loss)         |  Pre 
>          |            x<-----------------------|        
>          |                                     |  Ear 
>          | ini-INVITE(=F1) F4           200 F3 |        
>          |------------------     --------------|        
>          |                   \ /               |  Mora
>          |                    X                |      
>          |                   / \               |
>          |<-----------------     ------------->|  *race*
>    Mora  |                ACK F5               |
>          |------------------------------------>|  
>     Est  |                                     |  Est
>          |                                     |

Thank you for your suggestion.
I will revise the picture according to your idea.


> In section 3.1.6:
> 
> * The phrase "Alice may want to start a session again" does not
> seem to correspond with the rest of the paragraph.

This is a mistake.
The correct sentence is "Alice may start a session again".


> In Appendix A:
> 
> * The figure is hard to read because the responses aren't labeled to
> show which requests they are from.  This version is easier to read:
> 
> Appendix A - BYE on the Early Dialog
> 
>    This section, related to Section 3.1.3, explains why BYE is not
>    recommended in the Early state, illustrating the case in which BYE
>    in the Early dialog triggers confusion.
> 
> 
>    Alice                 Proxy                      Bob   Carol
>      |                     |                         |      |
>      |   INVITE F1         |                         |      |
>      |-------------------->|    INVITE F2            |      |
>      |     100 F3          |------------------------>|      |
>      |<--------------------|    180(To-tag=1) F4     |      |
>      |    180(1) F5        |<------------------------|      |
>      |<--------------------|                         |      |
>      |                     |    INVITE(Fork) F6             |
>      |                     |------------------------------->|
>      |                     |      100 F7                    |
>      |    BYE(1) F8        |<-------------------------------|
>      |-------------------->|    BYE(1) F9            |      |
>      |                     |------------------------>|      |
>      |                     |    200(1,BYE) F10       |      |
>      |   200(1,BYE) F11    |<------------------------|      |
>      |<--------------------|    487(1,INV) F12       |      |
>      |                     |<------------------------|      |
>      |                     |    ACK(1) F13           |      |
>      |                     |------------------------>|      |
>      |                     |                         |      |
>      |                     |                                |
>      |                     |    200(To-tag=2) F13           |
>      |   200(2,INV) F14    |<-------------------------------|
>      |<--------------------|                                |
>      |   ACK(2) F15        |                                |
>      |-------------------->|            ACK(2) F16          |
>      |                     |------------------------------->|
>      |   BYE(2) F17        |                                |
>      |-------------------->|            BYE(2) F18          |
>      |                     |------------------------------->|
>      |                     |            200(2,BYE) F19      |
>      |   200(2,BYE) F20    |<-------------------------------|
>      |<--------------------|                                |
>      |                     |                                |
>      |                     |                                |

Thank you for your suggestion.
I will reflect this in the next version of the draft.


> In Appendix B:
> 
> * It is always possible for a re-sent request to receive a 500 (Out Of
> Order) response if the recipient has already processed a later
> request.  So this sentence:
> 
>    UAS's TU sends an appropriate error response (probably 481) for F4
>    INVITE, because the TU knows that the dialog which matches to the
>    INVITE is in the Terminated state.
> 
> should be revised to:
> 
>    UAS's TU sends an appropriate error response for F4 INVITE, either
>    481 (because the TU knows that the dialog which matches to the
>    INVITE is in the Terminated state) or 500 (because the re-sent F4
>    has an out-of-order CSeq).

I think it is correct to respond with 500 when Cseq is
out of order.
I will correct the text.
I think there is no dialog for outwardly in the Mortal state,
but dialog is still being managed internally. Therefore I assume
it is possible to respond 500 after checking the Cseq which is
related to a dialog.


> ** Editorial

I appreciate for pointing them out.
I will take care of them in the next version.

Again, thank you for your many poductive comments.

Thank you
Miki,


> "s.b." = "should be".  Quoted words in [brackets] are shown for
> context.
> 
> In Table of Contents:
> 
> * Section 3 s.b. titled "Race conditions".
> 
> * Section 3.3 s.b. titled "Other race conditions".
> 
> * Section 3.3.1 s.b. titled "Re-INVITE crossover".
> 
> In section 2:
> 
> * "[some internal states] showed [in the FSM]" s.b. "shown".
> 
> * Figures 1 and 2 are not put entirely on their own pages with their
> own captions.  Page breaks should be added to force alignment.
> 
> * The caption for Figure 1 ("Figure 1 represents ... dialog usage.")
> is not separated from the following paragraph ("UAC MAY send a BYE in
> the early state...")
> 
> * "[the Early dialog] between [a particular UA]" s.b. "with".
> 
> * Line 50 of page 8 contains non-ASCII characters:  "[information
> about]??[the dialog which is being terminated]".
> 
> In section 3.1.6:
> 
> * Near the top of page 22, "BYE request at the same time.  Depending
> on the implementation" looks like there might be a paragraph break
> intended between the two sentences.
> 
> In Appendix C:
> 
> * It would be clearer to revise this sentence:
> 
>    (Note that, from the point of UAC's behavior, it can be expected
>    that UAS receives BYE immediately after the reception of CANCEL and
>    moves to the Terminated state.  However, the UAS's state does not
>    transit until it actually receives BYE.)
> 
> to:
> 
>    (Note that, because of UAC's behavior, a UAS that receives a CANCEL
>    in the Confirmed state can expect to receive a BYE immediately and
>    move to the Terminated state.  However, the UAS's state does not
>    transit until it actually receives BYE.)
> 
> In Appendix D:
> 
> * "[However, the ACK for 2xx and] the one [for error responses are
> both a part of the INVITE transaction, even though their] hadlings
> differ" s.b "the ACK" and "handling differs".
> 
> In Acknowledgment:
> 
> * "[for] the [comments on this document]" s.b. "their".
> ----------------------------------------------------------------------
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org Thu Jan 18 17:18:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H7faE-0001aY-2D; Thu, 18 Jan 2007 17:18:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H7faC-0001XH-EC
	for sipping@ietf.org; Thu, 18 Jan 2007 17:18:08 -0500
Received: from alnrmhc13.comcast.net ([204.127.225.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H7faB-00032E-74
	for sipping@ietf.org; Thu, 18 Jan 2007 17:18:08 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (alnrmhc13) with ESMTP
	id <20070118221806b130039pdoe>; Thu, 18 Jan 2007 22:18:06 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l0IMI5bM022789
	for <sipping@ietf.org>; Thu, 18 Jan 2007 17:18:05 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l0IMI50G022785;
	Thu, 18 Jan 2007 17:18:05 -0500
Date: Thu, 18 Jan 2007 17:18:05 -0500
Message-Id: <200701182218.l0IMI50G022785@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <459AABFF.8000404@cisco.com> (pkyzivat@cisco.com)
Subject: Re: [Sipping]
	I-DACTION:draft-loreto-sipping-dialog-correlation-00.txt/
	use of same-session header with KMPL
References: <2AF8FF7D89242541B12E7A47F6ECB4BE04D1E542@ftrdmel3.rd.francetelecom.fr>
	<459AABFF.8000404@cisco.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   CHADLI Youssef RD-CORE-ISS wrote:
   > 
   > The use of  the Same-Session header can resolve this problem : UA2
   > inserts the Same-Session header in the SUBSCRIBE request set to D2, then
   > the B2BUA entity modifies this header and sets it to D1 before
   > forwarding the request to UA1. Consequently, UA2 knows that KPML request
   > is correlated with the media session corresponding to dialog D1. 
   > Do you see any problem for doing that ?

   From: Paul Kyzivat <pkyzivat@cisco.com>

   It seems to me that if the B2BUA is going to stick its ugly nose into 
   this, then it has the obligation to figure out the mess it has made and 
   fix it. That should be part of the work in B2BUA-"proxying" the 
   SUBSCRIBE, without any extra hints from the subscriber.

I agree -- It is much more likely that having the B2BUA understand and
adjust the KPML will work correctly, than that all UAs in the world
will look for a Same-Session header and process it correctly.

Dale

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



From sipping-bounces@ietf.org Fri Jan 19 08:41:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H7tzQ-0007sF-JX; Fri, 19 Jan 2007 08:41:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H7tzO-0007oT-Af
	for sipping@ietf.org; Fri, 19 Jan 2007 08:41:06 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H7tzM-0000kB-GN
	for sipping@ietf.org; Fri, 19 Jan 2007 08:41:06 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l0JDcgVh018255; Fri, 19 Jan 2007 15:38:46 +0200
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Jan 2007 15:41:01 +0200
Received: from [172.21.58.172] ([172.21.58.172]) by esebh001.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 19 Jan 2007 15:41:02 +0200
Message-ID: <45B0CA69.2020404@nokia.com>
Date: Fri, 19 Jan 2007 15:40:57 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Sipping" <sipping@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jan 2007 13:41:02.0308 (UTC)
	FILETIME=[75BF2A40:01C73BCF]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070119153846-46C79BB0-6D346464/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: "Matuszewski Marcin \(Nokia-NRC/Helsinki\)" <marcin.matuszewski@nokia.com>,
	Nicklas Beijar <nbeijar@netlab.hut.fi>,
	Juuso Lehtinen <juuso.lehtinen@netlab.tkk.fi>
Subject: [Sipping] Remote file listing with SIP
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi:

We submitted recently an updated version of three drafts that describe 
how a UA can get a list of files stored in a remote UA or server. Then 
the UA can use the file transfer mechanism to download any of the files 
(modulo authorization).

The authors are requesting feedback and comments. Specifically, we are 
interested to taste the waters whether this is some interesting 
functionality that we should pursue or not.

I would recommend to start with the framework document,
http://www.ietf.org/internet-drafts/draft-garcia-sipping-resource-sharing-framework-01.txt

And if you want to further go to the details, you can continue with 
these other two:
http://www.ietf.org/internet-drafts/draft-garcia-sipping-resource-event-package-01.txt
http://www.ietf.org/internet-drafts/draft-garcia-sipping-resource-desc-pidf-00.txt

Looking forward to your comments.

/Miguel
-- 
Miguel A. Garcia           tel:+358-50-4804586
sip:miguel.garcia@neonsite.net
Nokia Research Center      Helsinki, 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 sipping-bounces@ietf.org Fri Jan 19 10:56:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H7w6N-00045X-5r; Fri, 19 Jan 2007 10:56:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H7w6L-00045S-LY
	for sipping@ietf.org; Fri, 19 Jan 2007 10:56:25 -0500
Received: from sccrmhc13.comcast.net ([204.127.200.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H7w6J-0004Da-Ek
	for sipping@ietf.org; Fri, 19 Jan 2007 10:56:25 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (sccrmhc13) with ESMTP
	id <2007011915561901300lsod9e>; Fri, 19 Jan 2007 15:56:23 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l0JFuJbM003027
	for <sipping@ietf.org>; Fri, 19 Jan 2007 10:56:19 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l0JFuJtv003023;
	Fri, 19 Jan 2007 10:56:19 -0500
Date: Fri, 19 Jan 2007 10:56:19 -0500
Message-Id: <200701191556.l0JFuJtv003023@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <45B0CA69.2020404@nokia.com> (Miguel.An.Garcia@nokia.com)
Subject: Re: [Sipping] Remote file listing with SIP
References: <45B0CA69.2020404@nokia.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: Miguel Garcia <Miguel.An.Garcia@nokia.com>

   We submitted recently an updated version of three drafts that
   describe how a UA can get a list of files stored in a remote UA or
   server. Then the UA can use the file transfer mechanism to download
   any of the files (modulo authorization).

Why could one not just use the file transfer mechanism to get a
directory listing?

Dale

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



From sipping-bounces@ietf.org Fri Jan 19 16:04:02 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H80tW-0005x1-2O; Fri, 19 Jan 2007 16:03:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H80tU-0005tf-Jl; Fri, 19 Jan 2007 16:03:28 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H80tQ-0001Cg-77; Fri, 19 Jan 2007 16:03:28 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 19 Jan 2007 13:03:24 -0800
X-IronPort-AV: i="4.13,212,1167638400"; 
	d="scan'208"; a="458537975:sNHT102601984"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l0JL3Nbr032287; 
	Fri, 19 Jan 2007 13:03:23 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l0JL3MUw004853;
	Fri, 19 Jan 2007 13:03:22 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Jan 2007 13:03:20 -0800
Received: from [10.32.241.158] ([10.32.241.158]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Jan 2007 13:03:20 -0800
Message-ID: <45B13215.7060500@cisco.com>
Date: Fri, 19 Jan 2007 16:03:17 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF Sipping List <sipping@ietf.org>, rai@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jan 2007 21:03:20.0549 (UTC)
	FILETIME=[3FC56150:01C73C0D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2625; t=1169240603;
	x=1170104603; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20new=20proposed=20BoF=20and=20mailing=20list=20on=20feature=20
	interoperability |Sender:=20;
	bh=AiYFENnVo6mu9iB9F49qQMDur0QNDUZHImkRBpYwhZw=;
	b=k4gOQPQrtLzhVAU4hZofkIPkrC5lGsdUOR4kw+y8Csoh49pQflbB3WHeLwlfANrjkTYLkLnT
	T0zL41/WlcTP6Hk8MdMl/SFXX2ws+/PL9ZIxEwjrazbxjtM4U9H7+n/D;
Authentication-Results: sj-dkim-3; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
Subject: [Sipping] new proposed BoF and mailing list on feature
	interoperability
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Please do not reply to this mail.

SIP has come a long way in terms of interoperability over the years. 
However, there are several places where we still have a poor track 
record of interoperability. One of these is in the area of more advanced 
types of features. These include many of the features traditionally 
found on enterprise PBXs, such as park/pickup, shared line extension, 
and so on. There has been sporadic work on this topic, with many drafts, 
but no real solution yet.

There is a real need to get these interoperability problems solved. This 
need is coming from the IP PBX/Centrex side and from the consumer side, 
from groups like TISPAN that want some of these features to work.

The interop problems stem from several root cause issues. One is too 
much variety in the way these features can be implemented. This is good 
from a flexibility point of view, but it causes interop problems when 
both endpoints do things differently and won't work together as a 
consequence. Another problem is lack of sufficient functionality from 
the specs, in which cases people turn to proprietary techniques. Combine 
this with the standard "dont want to implement the right thing because 
its too hard" and general bug problems, and its a mess.

To fix this, I think it makes sense to start a working group thats 
formally tasked with the problem. The idea is to take on individual 
features, one at a time, figure out the real issues causing interop 
problems, and address them by either writing some requirements for sip 
enhancements, or developing some BCPs or informational documents 
specifying minimum interop requirements. Its also important to do this 
without trying to formally define what the feature is; we want to allow 
variation as much as possible while preserving interop.

I've been with Cullen, Shida Schubert and a number of others on getting 
a BoF going in Prague on this. We've got a mailing list that is now set 
up, and a proposed charter, all of which can be found here:

http://sip101.net/index.html

Please join the list and participate in the discussions. The more of it 
we can have prior to Prague, the better the chances we can arrive there 
with a charter and deliverables that are on target.

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

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



From sipping-bounces@ietf.org Sat Jan 20 04:58:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H8CyA-0002zE-82; Sat, 20 Jan 2007 04:57:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H8Cy8-0002xT-P5
	for sipping@ietf.org; Sat, 20 Jan 2007 04:57:04 -0500
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H8Cy7-0004Vi-Aa
	for sipping@ietf.org; Sat, 20 Jan 2007 04:57:04 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l0K9tCd9018897; Sat, 20 Jan 2007 11:55:13 +0200
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 20 Jan 2007 11:56:56 +0200
Received: from [10.162.17.190] ([10.162.17.190]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Sat, 20 Jan 2007 11:56:56 +0200
Message-ID: <45B1E768.2080308@nokia.com>
Date: Sat, 20 Jan 2007 11:56:56 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: dale.worley@comcast.net
Subject: Re: [Sipping] Remote file listing with SIP
References: <45B0CA69.2020404@nokia.com>
	<200701191556.l0JFuJtv003023@dragon.ariadne.com>
In-Reply-To: <200701191556.l0JFuJtv003023@dragon.ariadne.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jan 2007 09:56:57.0223 (UTC)
	FILETIME=[5243C170:01C73C79]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070120115513-49BF9BB0-25322356/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dale,

The file transfer mechanism does not include directory listing. The file 
transfer mechanism allows you to do two things:

a) Push a file to the remote UA
b) If you happen to know an identifier of a remote file (such as the 
hash of the file), then you can pull a file from the remote UA.

The resource sharing drafts are trying to solve the "if you happen to 
know an identifier of a remote file", i.e., get a directory list of 
remote files. Once you have got them, you can start the file transfer 
mechanism to pull the file.

/Miguel

sipping-bounces@ietf.org wrote:
>    From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
> 
>    We submitted recently an updated version of three drafts that
>    describe how a UA can get a list of files stored in a remote UA or
>    server. Then the UA can use the file transfer mechanism to download
>    any of the files (modulo authorization).
> 
> Why could one not just use the file transfer mechanism to get a
> directory listing?
> 
> Dale
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

-- 
Miguel A. Garcia           tel:+358-50-4804586
sip:miguel.garcia@neonsite.net
Nokia Research Center      Helsinki, 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 sipping-bounces@ietf.org Sat Jan 20 14:00:07 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H8LQ3-0004yw-LM; Sat, 20 Jan 2007 13:58:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H8LQ2-0004yo-Dn
	for sipping@ietf.org; Sat, 20 Jan 2007 13:58:26 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H8LQ1-0006Yw-3g
	for sipping@ietf.org; Sat, 20 Jan 2007 13:58:26 -0500
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-5.cisco.com with ESMTP; 20 Jan 2007 10:58:24 -0800
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l0KIwNHC004719; 
	Sat, 20 Jan 2007 10:58:23 -0800
Received: from [10.255.254.191] (sjc-vpn-hwcore-12.cisco.com [10.21.152.12])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l0KIwJho002230;
	Sat, 20 Jan 2007 10:58:19 -0800 (PST)
In-Reply-To: <OF00AB5E52.679FA931-ON85257268.007F2E69-85257268.00809D4B@mitel.com>
References: <OF00AB5E52.679FA931-ON85257268.007F2E69-85257268.00809D4B@mitel.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1E682531-9778-467C-AAB4-FE17A00E8A06@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Date: Sat, 20 Jan 2007 10:58:10 -0800
To: peter_blatherwick@mitel.com
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2383; t=1169319503;
	x=1170183503; c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20draft-ietf-sipping-config-framework-10 |Sender:=20;
	bh=wEVACjbv6A79N3seo3BbVzG/zGY4sxy/go4RseNKi7I=;
	b=p8kcauvEXW/4uKmpmF8BCkfpWWuBZGo77XyIp2DwY1KNWTBau5YIvwiVWHGTsXmldkiSESbn
	yzZxBU+nQu0SWKId7pKV/WMtA80zp55b1btedWrDsYkFG80+bDj4V+Zs;
Authentication-Results: sj-dkim-6; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim6002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: sipping@ietf.org
Subject: [Sipping] draft-ietf-sipping-config-framework-10
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


Thanks for getting this out.

Big comments :

My one big comment is about the security stuff - I think we should  
have a phone call about the security model for this works, what we  
need to secure from, and how we are going to do it. We need to talk  
about what credential will be used at various stages and where theses  
will come from. I suspect  some changes are needed here but we need  
to get on the same page first. We also need to consider things like  
where do the credentials come from and in what order. I want to make  
sure it is possible that the device profile can have the credentials  
used for user. (I'm fine if some uses do not, I just want to make  
sure this use case is possible).

Related to the security issues, the approach in 5.6.1 significantly  
complicates things. I have yet to understand why this additional  
flexibility in the order of things was needed. I would like to  
consider if we really need it and what it will take to secure it in  
practical deployments

Small Comments:

In section 5.6.1, I think it is mandatory that if this approach is  
used, that it results in the information to form a subscriptions  
which must be formed. Without this the framework fails to meet it's  
requirements of being to get notifications about changes.

I think there are places where the From gets used in the wrong way  
and the Contact header should be used instead. Specifically I have  
problems with how the From is used in subscription for the local- 
network profile. This is the wrong semantics form From (and exactly  
the right semantics for Contact) and breaks things like Identity and  
makes the meaning of the From header in SIP even more confused than  
it is now.

Small notes - don't be surprised if the the IESG tells you the MAC:  
looks like a a URN and request you define it as a URN.


When looking a local network config, if DHCP says the domain is  
example.com, I do not think we should look at example.com, I think we  
should only look at _sipuaconfig.example.com. This stops us from  
sending random requests to things that don't support this framework  
and seem to still provide all the flexibility for people that want to  
use DHCP based discovery.

Instead of a DNS name of sipuaconfig, it should be _sipuaconfig.


Cullen <with my individual contributor hat on>



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



From sipping-bounces@ietf.org Mon Jan 22 13:53:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H94HS-0002WI-VF; Mon, 22 Jan 2007 13:52:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H94HR-0002WB-C0
	for sipping@ietf.org; Mon, 22 Jan 2007 13:52:33 -0500
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H94HP-0002f1-UX
	for sipping@ietf.org; Mon, 22 Jan 2007 13:52:33 -0500
Received: from kyzyl.cablelabs.com (kyzyl.cablelabs.com [10.253.0.7])
	by ondar.cablelabs.com (8.13.8/8.13.8) with ESMTP id l0MIqU7g007082;
	Mon, 22 Jan 2007 11:52:30 -0700 (MST)
Received: from srvxchg.cablelabs.com (10.5.0.20)
	by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com);
	Mon, 22 Jan 2007 11:52:29 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com)
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"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] draft-ietf-sipping-config-framework-10
Date: Mon, 22 Jan 2007 11:52:29 -0700
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D8480402106516@srvxchg.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] draft-ietf-sipping-config-framework-10
Thread-Index: Acc8xX6sOqDLrhDUQHCwO7QxVScINwBkC4fA
From: "Sumanth Channabasappa" <sumanth@cablelabs.com>
To: "Cullen Jennings" <fluffy@cisco.com>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Cullen,

Thanks for your comments. v10 was submitted (Fri eve), but is not yet
available on the IETF website (when I last checked). Once available, I
will send across an email listing changes at a high level (also listed
in the I-D).=20

The 'Security section' (as you will see in the I-D) has not undergone
sufficient discussion and will benefit from feedback (so your email
definitely helps :) ). As indicated at the last IETF, ad-hoc calls are
being conducted and will continue to do so for this I-D. Folks
interested can send me an email directly to me or the co-chairs.=20


- S


-----Original Message-----
From: Cullen Jennings [mailto:fluffy@cisco.com]=20
Sent: Saturday, January 20, 2007 11:58 AM
To: peter_blatherwick@mitel.com
Cc: sipping@ietf.org
Subject: [Sipping] draft-ietf-sipping-config-framework-10


Thanks for getting this out.

Big comments :

My one big comment is about the security stuff - I think we should have
a phone call about the security model for this works, what we need to
secure from, and how we are going to do it. We need to talk about what
credential will be used at various stages and where theses will come
from. I suspect  some changes are needed here but we need to get on the
same page first. We also need to consider things like where do the
credentials come from and in what order. I want to make sure it is
possible that the device profile can have the credentials used for user.
(I'm fine if some uses do not, I just want to make sure this use case is
possible).

Related to the security issues, the approach in 5.6.1 significantly
complicates things. I have yet to understand why this additional
flexibility in the order of things was needed. I would like to consider
if we really need it and what it will take to secure it in practical
deployments

Small Comments:

In section 5.6.1, I think it is mandatory that if this approach is used,
that it results in the information to form a subscriptions which must be
formed. Without this the framework fails to meet it's requirements of
being to get notifications about changes.

I think there are places where the From gets used in the wrong way and
the Contact header should be used instead. Specifically I have problems
with how the From is used in subscription for the local- network
profile. This is the wrong semantics form From (and exactly the right
semantics for Contact) and breaks things like Identity and makes the
meaning of the From header in SIP even more confused than it is now.

Small notes - don't be surprised if the the IESG tells you the MAC: =20
looks like a a URN and request you define it as a URN.


When looking a local network config, if DHCP says the domain is
example.com, I do not think we should look at example.com, I think we
should only look at _sipuaconfig.example.com. This stops us from sending
random requests to things that don't support this framework and seem to
still provide all the flexibility for people that want to use DHCP based
discovery.

Instead of a DNS name of sipuaconfig, it should be _sipuaconfig.


Cullen <with my individual contributor hat on>



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org Mon Jan 22 15:51:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9682-0007on-T9; Mon, 22 Jan 2007 15:50:58 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H967d-0007ZF-Te; Mon, 22 Jan 2007 15:50:34 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1H967d-0000Cf-BT; Mon, 22 Jan 2007 15:50:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 07D6A175F4;
	Mon, 22 Jan 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1H9678-000839-JK; Mon, 22 Jan 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1H9678-000839-JK@stiedprstage1.ietf.org>
Date: Mon, 22 Jan 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-config-framework-10.txt 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

--NextPart

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

	Title		: A Framework for Session Initiation Protocol User Agent Profile Delivery
	Author(s)	: D. Petrie, S. Channabasappa
	Filename	: draft-ietf-sipping-config-framework-10.txt
	Pages		: 56
	Date		: 2007-1-22
	
This document defines a framework to enable configuration of Session
   Initiation Protocol (SIP) User Agents in SIP deployments.  The
   framework provides a means to deliver profile data that User Agents
   need to be functional, automatically and with minimal (preferably
   none) User and Administrative intervention.  The framework describes
   how SIP User Agents can discover sources, request profiles and
   receive notifications related to profile modifications.  As part of
   this framework, a new SIP event package is defined for notification
   of profile changes.  The framework provides for multiple data
   retrieval options, without requiring or defining retrieval protocols.
   The framework does not include specification of the profile data
   within its scope.

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

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

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sipping-config-framework-10.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-10.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

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

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

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


--OtherAccess--

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

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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--





From sipping-bounces@ietf.org Mon Jan 22 16:30:30 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H96k8-0005L2-23; Mon, 22 Jan 2007 16:30:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H96k6-0005Kq-IU
	for sipping@ietf.org; Mon, 22 Jan 2007 16:30:18 -0500
Received: from hme1.july.broomfield1.level3.net ([209.245.18.8]
	helo=f4bb49-05.idc1.level3.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H96k4-0003pH-7I
	for sipping@ietf.org; Mon, 22 Jan 2007 16:30:18 -0500
Received: from montag.eng.level3.com (montag.eng.l3.com [10.1.68.57])
	by f4bb49-05.idc1.level3.com (8.12.10/8.12.10) with ESMTP id
	l0MLUELT021698 for <sipping@ietf.org>; Mon, 22 Jan 2007 21:30:14 GMT
Subject: [Sipping] Updated Draft: SIP End-to-End Performance Metrics
From: Daryl Malas <daryl@level3.net>
To: sipping@ietf.org
Content-Type: text/plain
Date: Mon, 22 Jan 2007 14:38:02 -0700
Message-Id: <1169501882.17141.9.camel@montag.eng.level3.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.0 (2.6.0-1) 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

To all:

I have submitted a revision to the SIP End-to-End Performance Metrics
draft.

The following revisions have been made to the draft:

- Added a template for metrics in order to guide extensibility (Section
5.4)
- Replaced verbiage in section 5.2 to be more general towards any
network management protocols
- Changed Term "Time Begin" to begin when the first bit is sent
(reference E.721 Post-selection Delay) and not the last; also, provided
clarity around the term.
- Changed all metrics "average" description to indicate the calculation
as one of the uses of the metric
- On some metrics, specified a single time value of milliseconds instead
of "seconds and/or milliseconds"
- Added new terms: Session, Session Setup, and Session Establishment
(clarified "media" is not measured in these metrics)
- Combined conventions and terminology into one section per IETF
guidelines
- Expanded acronyms on first use per IETF guidelines
- Clarified RRD to indicate what response to utilize to determine
failure
- Added reference to ITU E.721 for Post-selection Delay as related to
SRD
- Added back in Average Hops per INVITE (AHI) as requested by working
group
- Removed statement "all metrics calculated by inputs at UAC"
- Added statements to metrics which can be calculated at both UAC and
UAS, and included diagrams where applicable (Section 3.3 and 3.4)
- Added references to ASR (E.411) and PDD (E.721)
- Added new "Additional Metrics for Consideration" (Section 5.5)
- Added considerations regarding forking
- Clarified terms TB/TS

Please let me know your thoughts on this revision.  Thank you to
everyone who provided feedback in San Diego, email, and the mailing
list. --Daryl
----------------------------------------------------------------------

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


	Title		: SIP End-to-End Performance Metrics
	Author(s)	: D. Malas
	Filename	: draft-malas-performance-metrics-06.txt
	Pages		: 26
	Date		: 2007-1-22
	
This document defines a set of metrics and their usage to evaluate 
the performance of end-to-end Session Initiation Protocol (SIP) based 
services in both production and testing environments.  The purpose of 
this document is to combine a set of common metrics, allowing 
interoperable performance measurements, easing the comparison of 
industry implementations.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-malas-performance-metrics-06.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



From sipping-bounces@ietf.org Mon Jan 22 20:21:27 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9AKd-0003iV-E0; Mon, 22 Jan 2007 20:20:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9AKb-0003iE-OC
	for sipping@ietf.org; Mon, 22 Jan 2007 20:20:13 -0500
Received: from brinza.cc.columbia.edu ([128.59.29.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9AKZ-0001fP-GZ
	for sipping@ietf.org; Mon, 22 Jan 2007 20:20:13 -0500
Received: from [192.168.0.41] (pool-141-153-190-218.mad.east.verizon.net
	[141.153.190.218]) (user=hgs10 mech=PLAIN bits=0)
	by brinza.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id l0N1KAMl008374
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <sipping@ietf.org>; Mon, 22 Jan 2007 20:20:11 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <347B8EC7-87C1-4A04-B3AA-B60D5D760110@cs.columbia.edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: sipping <sipping@ietf.org>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Date: Mon, 22 Jan 2007 20:20:04 -0500
X-Mailer: Apple Mail (2.752.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.8
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Subject: [Sipping] Comments on draft-ietf-sipping-config-framework-10
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Thanks for putting together a first revised version. It's  
significantly improved, but I think it still is overly complicated  
and needs too much reading ahead to make sense.

Some quick-read random comments:

(1) It would be most helpful to state up front what you assume the UA  
needs to know to be configured - MAC address? A SIP AOR and password?  
Does this vary by model? If so, does a user agent have to be "born"  
for a specific environment? I thought the idea was that we would have  
generic devices that would work just as well in a home environment,  
in a carrier environment and in an enterprise environment, without  
manual intervention and flipping a "you are now in a LAN" switch.  
 From the draft, I get the feeling that this is not the case; if I  
misread the draft, maybe this needs to be stated as a clear goal up  
front.

I would find it much more helpful to go by knowledge, rather than by  
deployment scenario. An end device does not and should not know  
whether I use the same provider as VSP and ISP, say.

Thus, I could follow logic that said: "If you only know your MAC  
address, do X. This gives you one or more SIP AOR. Once you have a  
SIP AOR, do Y and you get configuration information from A and B."

(2) Client and User Agent are used in somewhat confusing ways.  
Sometimes client seems to be the same as "piece of hardware", in  
other cases its more abstract or is only used for device  
configuration. Given that client is such an overused term, I'd stick  
with SIP terminology (UAC, say) unless it really means something  
fundamentally different. For DHCP, we obviously need to use the term  
host. If there's some 1:N relationship here, it needs to be explained  
early, not just in some glossary.

(3) Editorially, I find the way of writing like the US Constitution  
annoying, i.e., where Every Important Word is Capitalized. This looks  
like You Are Screaming. Once you define a term, it is understood to  
have a certain meaning, without the need to capitalize it.

As a nit, "such as" and "etc" are never used together.

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 sipping-bounces@ietf.org Tue Jan 23 10:43:02 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9Nmq-0004XJ-Aj; Tue, 23 Jan 2007 10:42:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Nmp-0004Wv-39
	for sipping@ietf.org; Tue, 23 Jan 2007 10:42:15 -0500
Received: from maild.telecomitalia.it ([156.54.233.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9Nmi-0008VI-TJ
	for sipping@ietf.org; Tue, 23 Jan 2007 10:42:15 -0500
Received: from ptpxch008ba020.idc.cww.telecomitalia.it ([156.54.240.51]) by
	maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Tue, 23 Jan 2007 16:42:04 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.228]) by
	ptpxch008ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 23 Jan 2007 16:42:04 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Comments on draft-ietf-sipping-config-framework-10
Date: Tue, 23 Jan 2007 16:42:00 +0100
Message-ID: <F5F8BEB3F2C54240999C08F4D455D28801E33214@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <347B8EC7-87C1-4A04-B3AA-B60D5D760110@cs.columbia.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Comments on draft-ietf-sipping-config-framework-10
thread-index: Acc+jPXRFtjtgNzmQ722WxDPfOf+FAAdgkaw
From: "Goix Laurent Walter" <laurentwalter.goix@telecomitalia.it>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>, "sipping" <sipping@ietf.org>
X-OriginalArrivalTime: 23 Jan 2007 15:42:04.0207 (UTC)
	FILETIME=[07D403F0:01C73F05]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: AZEMARD Sophie RD-SIRP-ISS <sophie.azemard@orange-ftgroup.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

All,

>From a first look at -10 (already in -09 in fact) it seems that the =
'application' profile type has definitely moved for exclusive usage with =
XCAP.=20

>From =
http://www.ietf.org/internet-drafts/draft-ietf-sip-xcap-config-01.txt : =
" Specifying the "application" type profile also implies the use of =
XCAP."

In OMA the BAC-CD (Push) group is working at defining an OMA SIP Push =
specification that relies on the config-framework to push to mobile =
devices using SIP, and in particular to the "application" profile type =
(although not using XCAP).

Since -09 we are trying to understand how to deal with this issue, would =
it be defining a parallel profile-type (by the way also with a =
"AUID"/application-id kind of concept) if using the config-framework, or =
specify our own Event package.

In both cases we would probably need some IANA registration and some =
further guidelines on the related process & time needed to release our =
specification.=20

Any comment or suggestion would be helpful.

Cheers
Walter Goix
PS: I am wondering at this point why the profile-type is 'xcap-config' =
isn't renamed "xcap", since it seems very tighten to it, leaving =
"application" for real "application"-level information (potentially of =
any type of content). While also not thinking about using XCAP for other =
"levels" of configuration/information and not only at 'application' =
level?


-----Original Message-----
From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]=20
Sent: marted=EC 23 gennaio 2007 2.20
To: sipping
Subject: [Sipping] Comments on draft-ietf-sipping-config-framework-10

Thanks for putting together a first revised version. It's =20
significantly improved, but I think it still is overly complicated =20
and needs too much reading ahead to make sense.

Some quick-read random comments:

(1) It would be most helpful to state up front what you assume the UA =20
needs to know to be configured - MAC address? A SIP AOR and password? =20
Does this vary by model? If so, does a user agent have to be "born" =20
for a specific environment? I thought the idea was that we would have =20
generic devices that would work just as well in a home environment, =20
in a carrier environment and in an enterprise environment, without =20
manual intervention and flipping a "you are now in a LAN" switch. =20
 From the draft, I get the feeling that this is not the case; if I =20
misread the draft, maybe this needs to be stated as a clear goal up =20
front.

I would find it much more helpful to go by knowledge, rather than by =20
deployment scenario. An end device does not and should not know =20
whether I use the same provider as VSP and ISP, say.

Thus, I could follow logic that said: "If you only know your MAC =20
address, do X. This gives you one or more SIP AOR. Once you have a =20
SIP AOR, do Y and you get configuration information from A and B."

(2) Client and User Agent are used in somewhat confusing ways. =20
Sometimes client seems to be the same as "piece of hardware", in =20
other cases its more abstract or is only used for device =20
configuration. Given that client is such an overused term, I'd stick =20
with SIP terminology (UAC, say) unless it really means something =20
fundamentally different. For DHCP, we obviously need to use the term =20
host. If there's some 1:N relationship here, it needs to be explained =20
early, not just in some glossary.

(3) Editorially, I find the way of writing like the US Constitution =20
annoying, i.e., where Every Important Word is Capitalized. This looks =20
like You Are Screaming. Once you define a term, it is understood to =20
have a certain meaning, without the need to capitalize it.

As a nit, "such as" and "etc" are never used together.

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

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From sipping-bounces@ietf.org Wed Jan 24 08:12:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9huU-0007Ir-MS; Wed, 24 Jan 2007 08:11:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9huT-0007Ik-BM
	for sipping@ietf.org; Wed, 24 Jan 2007 08:11:29 -0500
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9huR-0001iw-TM
	for sipping@ietf.org; Wed, 24 Jan 2007 08:11:29 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l0OD9ZKs018491; Wed, 24 Jan 2007 15:09:37 +0200
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Jan 2007 15:11:10 +0200
Received: from [172.21.58.172] ([172.21.58.172]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 24 Jan 2007 15:11:10 +0200
Message-ID: <45B75AED.3060908@nokia.com>
Date: Wed, 24 Jan 2007 15:11:09 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jan 2007 13:11:10.0002 (UTC)
	FILETIME=[1D83B920:01C73FB9]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070124150937-46DAEBB0-300F33F4/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Sipping <sipping@ietf.org>
Subject: [Sipping] Comments to
	draft-rosenberg-sipping-service-identification-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Some comments to the Service Identification draft.

- The draft mandates the usage of the Require header including a service 
URN. I think this usage is too restrictive. Imagine I establish a 
session with you, using a given service, and I want to give you a hint 
of the service that I am using, but it is not strictly required that you 
use exactly the same service. For example: I am using my IM client to 
establish a voice session with you. It would be nice if you happen to 
have an IM service client that supports voice, since we can start with 
voice and add IM later. But it is not necessary: you could answer with 
your telephony client and we could still have voice among both. This 
seems to advocate a Supported header (hint) in some cases.

- I understand the motivation for overloading the Require header for 
transporting URNs, but I think it is an ugly solution, and the fact that 
the RFC says you can only insert standardized option tags is not enough 
to prevent people writing other non-standardize tags if they wish to 
violate the RFC. So, I was wondering why not creating a Service header 
or something like that. The header would have the same constrains about 
how to populate it. And I think it would also solve the previous issue: 
serve as a hint, rather than as a requirement.

- Populating the last Route entry with the Service URN is a nice 
feature. I was wondering if application servers will have to delete this 
last route when they execute the service. I didn't find much written on 
the draft. I think servers will not be able to delete this last route 
ever, because they cannot guarantee that other servers downstream will 
need the same entry to route to other application servers. Think of a 
service that requires originating and terminating support. The draft 
should in any case discuss this topic.

- A definitions section in the draft would help. At least, Service 
Instance URI and Service URI should go there.

/Miguel

-- 
Miguel A. Garcia           tel:+358-50-4804586
sip:miguel.garcia@neonsite.net
Nokia Research Center      Helsinki, 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 sipping-bounces@ietf.org Wed Jan 24 08:30:30 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9iCg-0002DY-KC; Wed, 24 Jan 2007 08:30:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9iCd-0002Cl-JM
	for sipping@ietf.org; Wed, 24 Jan 2007 08:30:16 -0500
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9iCV-0007Nz-R2
	for sipping@ietf.org; Wed, 24 Jan 2007 08:30:15 -0500
Received: from bemail04.netfr.alcatel.fr (bemail04.netfr.alcatel.fr
	[155.132.251.33])
	by smail.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l0ODUDE5018148
	for <sipping@ietf.org>; Wed, 24 Jan 2007 14:30:13 +0100
Received: from [138.203.251.200] ([138.203.251.200])
	by bemail04.netfr.alcatel.fr (Lotus Domino Release 5.0.13aHF163)
	with ESMTP id 2007012414300477:6853 ;
	Wed, 24 Jan 2007 14:30:04 +0100 
Message-ID: <45B75F5D.3020001@alcatel-lucent.be>
Date: Wed, 24 Jan 2007 14:30:05 +0100
From: Torrey.Searle@alcatel-lucent.be
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: sipping@ietf.org
X-MIMETrack: Itemize by SMTP Server on BEMAIL04/BE/ALCATEL(Release
	5.0.13aHF163 | June 23, 2005) at 01/24/2007 14:30:04,
	Serialize by Router on BEMAIL04/BE/ALCATEL(Release 5.0.13aHF163 | June
	23, 2005) at 01/24/2007 14:30:06,
	Serialize complete at 01/24/2007 14:30:06
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [Sipping] Notify syntax in draft-poetzl-sipping-call-completion-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hello,

I have a question regarding the correct syntax of a NOTIFY message for 
the call-completion Event Package.

According to draft-poetzl-sipping-call-completion-01 section 5.7 it says:

    Upon receiving a subscription refresh, the notifier MUST set the 
    Expires header to the current remaining duration of the 
    subscription regardless of the value received in the Expires header 
    (if present) of the subscription refresh

However this seems to contradict RFC 3265 (section 3.2.2) where it states the following:

      Including expiration information for active and pending
      subscriptions is useful in case the SUBSCRIBE request forks, since
      the response to a forked SUBSCRIBE may not be received by the
      subscriber.  Note well that this "expires" value is a parameter on
      the "Subscription-State" header, NOT an "Expires" header.


Shouldn't Subscription-State be used instead of an Expires header for NOTIFY requests?

Torrey
Alcatel-Lucent





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



From sipping-bounces@ietf.org Wed Jan 24 09:18:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9iwn-0001IR-3X; Wed, 24 Jan 2007 09:17:57 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9iwl-0001G4-HR
	for sipping@ietf.org; Wed, 24 Jan 2007 09:17:55 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H9iwf-0007S7-Us
	for sipping@ietf.org; Wed, 24 Jan 2007 09:17:55 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 24 Jan 2007 09:17:48 -0500
X-IronPort-AV: i="4.13,232,1167627600"; 
	d="scan'208"; a="112375452:sNHT2924933704"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l0OEHkLi001529; 
	Wed, 24 Jan 2007 09:17:46 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l0OEHjVZ004819; 
	Wed, 24 Jan 2007 09:17:46 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Jan 2007 09:17:46 -0500
Received: from [161.44.174.190] ([161.44.174.190]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Jan 2007 09:17:46 -0500
Message-ID: <45B76A8A.7050307@cisco.com>
Date: Wed, 24 Jan 2007 09:17:46 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.An.Garcia@nokia.com>
Subject: Re: [Sipping] Comments
	to	draft-rosenberg-sipping-service-identification-00.txt
References: <45B75AED.3060908@nokia.com>
In-Reply-To: <45B75AED.3060908@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jan 2007 14:17:46.0359 (UTC)
	FILETIME=[6B876870:01C73FC2]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5142; t=1169648266;
	x=1170512266; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Comments=20to=09draft-rosenberg-sipping-s
	ervice-identification-00.txt |Sender:=20
	|To:=20Miguel=20Garcia=20<Miguel.An.Garcia@nokia.com>;
	bh=MVcVWf9Hl7aZBxaG5FK9Egknpod3fVOQeJWERYzvsDs=;
	b=TFbxrosbpH5KUpbKS45K8dS7/QM0VJV0P7Rc/W2WjT0uoJ3J7AInkc2NV4UlTmFP6KdSpu2E
	cspJ7PAWj2sUyOWIqzY6fm8TVgXt2Vi/oyPVPyLJ3RDKrk9YftLHYYOW;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: Sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Comments inline.

Miguel Garcia wrote:
> Some comments to the Service Identification draft.
> 
> - The draft mandates the usage of the Require header including a service 
> URN. I think this usage is too restrictive. Imagine I establish a 
> session with you, using a given service, and I want to give you a hint 
> of the service that I am using, but it is not strictly required that you 
> use exactly the same service. For example: I am using my IM client to 
> establish a voice session with you. It would be nice if you happen to 
> have an IM service client that supports voice, since we can start with 
> voice and add IM later. But it is not necessary: you could answer with 
> your telephony client and we could still have voice among both. This 
> seems to advocate a Supported header (hint) in some cases.

This comment highlights the overlap between "service", "capability", and 
"preference".

What you describe is a caller that requires voice (generic voice - no 
special service involving voice), that has a capability to do IM, and 
that has a preference for contacting a UAS that supports IM as well as 
voice.

To deal with that, we already have callerprefs, and mmusic is working on 
SDP capability negotiation that also may bring something useful.

I don't see why the service identification mechanism has to solve this 
problem too.

> - I understand the motivation for overloading the Require header for 
> transporting URNs, but I think it is an ugly solution, and the fact that 
> the RFC says you can only insert standardized option tags is not enough 
> to prevent people writing other non-standardize tags if they wish to 
> violate the RFC.

It doesn't prevent individuals, or developers of closed systems from 
doing so. But it does make it difficult for other SDOs from doing so, 
and developers of systems that interoperate with standards complying 
components will at least get some pressure.

This service mechanism has a high potential to create a real Tower of 
Babel if it isn't managed carefully.

> So, I was wondering why not creating a Service header 
> or something like that. The header would have the same constrains about 
> how to populate it. And I think it would also solve the previous issue: 
> serve as a hint, rather than as a requirement.
> 
> - Populating the last Route entry with the Service URN is a nice 
> feature. I was wondering if application servers will have to delete this 
> last route when they execute the service. I didn't find much written on 
> the draft. I think servers will not be able to delete this last route 
> ever, because they cannot guarantee that other servers downstream will 
> need the same entry to route to other application servers. Think of a 
> service that requires originating and terminating support. The draft 
> should in any case discuss this topic.

I have similar concerns. The Route header is an interesting approach 
that I too like in some ways. But its far from clear how to partition 
responsibility in order to resolve issues such as the one you raise. 
Jonathan already included flexibility to reorder these. (And I already 
complained about the mechanism. I think those that add Route headers 
ought to get the say about what reordering is allowed, rather than 
having it determined by the type of URI.)

But reordering only helps if somebody has reason to know what order is 
appropriate. If the element adding the header didn't know the right 
order, then how can we expect some other element to know?

Your issue is a further extension. In addition to reordering, there is 
the issue of knowing when something has been done. With regular Route 
header values, containing SIP URIs, we generally assume that a server 
knows when it owns that URI, and then removes the Route header. I think 
we need to assume essentially the same model for URNs - the server knows 
when it supports one, and then removes it. If it thinks there is 
*another* server that also supports that URN, then it can add *another* 
Route for that. But of course that raises some horrible issues of 
looping that I don't immediately see how to resolve in the general case.

In the case of adding support on both the originating and terminating 
sides, this might be less of a problem. The UAC, or a proxy on the 
originating side acting for the UAC, can add a Route header with the 
URN, based on the presence of the Require header or something, and then 
this will be resolved on the originating side before the R-URI is 
translated to send the request to the terminating side. Then a proxy on 
the terminating side can add a Route header, again based on the Require 
header of something, which will then be resolved on the terminating side.

IMO it is fundamental that the UAC *not* make assumptions about how the 
service is implemented on the terminating side, as that prevents 
alternative implementations.

	Thanks,
	Paul

> - A definitions section in the draft would help. At least, Service 
> Instance URI and Service URI should go there.
> 
> /Miguel
> 

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



From sipping-bounces@ietf.org Wed Jan 24 10:12:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9jnf-0006zL-Q8; Wed, 24 Jan 2007 10:12:35 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9jne-0006zD-6V
	for sipping@ietf.org; Wed, 24 Jan 2007 10:12:34 -0500
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H9jnb-0005WX-PC
	for sipping@ietf.org; Wed, 24 Jan 2007 10:12:34 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l0OFABmk032374; Wed, 24 Jan 2007 17:10:32 +0200
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Jan 2007 17:12:23 +0200
Received: from [172.21.58.172] ([172.21.58.172]) by esebh001.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 24 Jan 2007 17:12:59 +0200
Message-ID: <45B7775C.80207@nokia.com>
Date: Wed, 24 Jan 2007 17:12:28 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping] Comments
	to	draft-rosenberg-sipping-service-identification-00.txt
References: <45B75AED.3060908@nokia.com> <45B76A8A.7050307@cisco.com>
In-Reply-To: <45B76A8A.7050307@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jan 2007 15:12:59.0151 (UTC)
	FILETIME=[221B59F0:01C73FCA]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Cc: Sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Some inline thoughts.

Paul Kyzivat wrote:
> Comments inline.
> 
> Miguel Garcia wrote:
>> Some comments to the Service Identification draft.
>>
>> - The draft mandates the usage of the Require header including a 
>> service URN. I think this usage is too restrictive. Imagine I 
>> establish a session with you, using a given service, and I want to 
>> give you a hint of the service that I am using, but it is not strictly 
>> required that you use exactly the same service. For example: I am 
>> using my IM client to establish a voice session with you. It would be 
>> nice if you happen to have an IM service client that supports voice, 
>> since we can start with voice and add IM later. But it is not 
>> necessary: you could answer with your telephony client and we could 
>> still have voice among both. This seems to advocate a Supported header 
>> (hint) in some cases.
> 
> This comment highlights the overlap between "service", "capability", and 
> "preference".
> 
> What you describe is a caller that requires voice (generic voice - no 
> special service involving voice), that has a capability to do IM, and 
> that has a preference for contacting a UAS that supports IM as well as 
> voice.

I would say ".... that has a preference for contacting the same service 
that the calling party is using". The reason is that future interactions 
may involve other capabilities that this service is able to offer.


> 
> To deal with that, we already have callerprefs, and mmusic is working on 
> SDP capability negotiation that also may bring something useful.

I still don't see how I can signal my preference for a service to be used.

> 
> I don't see why the service identification mechanism has to solve this 
> problem too.

Because for a basic communication (say voice), any UI or application 
will work, but for more advanced features, if both UAs have the same 
service through an implementation, then that is the desired effect. 
think the service ID fits perfectly in here.


> 
>> - I understand the motivation for overloading the Require header for 
>> transporting URNs, but I think it is an ugly solution, and the fact 
>> that the RFC says you can only insert standardized option tags is not 
>> enough to prevent people writing other non-standardize tags if they 
>> wish to violate the RFC.
> 
> It doesn't prevent individuals, or developers of closed systems from 
> doing so. But it does make it difficult for other SDOs from doing so, 
> and developers of systems that interoperate with standards complying 
> components will at least get some pressure.

Agreed. My point is that you get the same effect by defining a new 
header and writing down the same constraints that Require has. IMHO this 
is not a justification for overloading the semantics of an existing header.

> 
> This service mechanism has a high potential to create a real Tower of 
> Babel if it isn't managed carefully.

I fully agree. It makes me very nervous. And the only usage of the 
Require header makes me nervous exactly in this sense. I believe the 
service preference is enough in most cases, perhaps is the only one that 
should go into the draft.

> 
>> So, I was wondering why not creating a Service header or something 
>> like that. The header would have the same constrains about how to 
>> populate it. And I think it would also solve the previous issue: serve 
>> as a hint, rather than as a requirement.
>>
>> - Populating the last Route entry with the Service URN is a nice 
>> feature. I was wondering if application servers will have to delete 
>> this last route when they execute the service. I didn't find much 
>> written on the draft. I think servers will not be able to delete this 
>> last route ever, because they cannot guarantee that other servers 
>> downstream will need the same entry to route to other application 
>> servers. Think of a service that requires originating and terminating 
>> support. The draft should in any case discuss this topic.
> 
> I have similar concerns. The Route header is an interesting approach 
> that I too like in some ways. But its far from clear how to partition 
> responsibility in order to resolve issues such as the one you raise. 
> Jonathan already included flexibility to reorder these. (And I already 
> complained about the mechanism. I think those that add Route headers 
> ought to get the say about what reordering is allowed, rather than 
> having it determined by the type of URI.)
> 
> But reordering only helps if somebody has reason to know what order is 
> appropriate. If the element adding the header didn't know the right 
> order, then how can we expect some other element to know?
> 
> Your issue is a further extension. In addition to reordering, there is 
> the issue of knowing when something has been done. With regular Route 
> header values, containing SIP URIs, we generally assume that a server 
> knows when it owns that URI, and then removes the Route header. I think 
> we need to assume essentially the same model for URNs - the server knows 
> when it supports one, and then removes it. 

This is the point where things fall apart. In general, a server will not 
have information of whether other servers downstream have to take an 
action based on the invoked service. In my opinion, there isn't harm in 
leaving a Route header there if the service URN was there, so that 
routing can still continue downstream and other servers might get 
involved, if required.

> If it thinks there is 
> *another* server that also supports that URN, then it can add *another* 
> Route for that. 

Well, on the wire there is no difference between preserving the service 
URN and first removing it and then add it again.

> But of course that raises some horrible issues of 
> looping that I don't immediately see how to resolve in the general case.

That is right. There should be me some mechanism to avoid loops. I am 
not sure if the general SIP mechanism for loop avoidance is enough.

> 
> In the case of adding support on both the originating and terminating 
> sides, this might be less of a problem. The UAC, or a proxy on the 
> originating side acting for the UAC, can add a Route header with the 
> URN, based on the presence of the Require header or something, and then 
> this will be resolved on the originating side before the R-URI is 
> translated to send the request to the terminating side. Then a proxy on 
> the terminating side can add a Route header, again based on the Require 
> header of something, which will then be resolved on the terminating side.

This is weird. So we have a proxy inspecting headers to determine that a 
SIP request should be routed to the Service application server.... I 
thought that was the sole purpose of adding the Service URN to the Route 
header.

> 
> IMO it is fundamental that the UAC *not* make assumptions about how the 
> service is implemented on the terminating side, as that prevents 
> alternative implementations.

Agreed.


> 
>     Thanks,
>     Paul
> 

BR,

        Miguel


>> - A definitions section in the draft would help. At least, Service 
>> Instance URI and Service URI should go there.
>>
>> /Miguel
>>

-- 
Miguel A. Garcia           tel:+358-50-4804586
sip:miguel.garcia@neonsite.net
Nokia Research Center      Helsinki, 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 sipping-bounces@ietf.org Wed Jan 24 10:32:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9k6V-00043n-Bm; Wed, 24 Jan 2007 10:32:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9k6T-00041d-Ib
	for sipping@ietf.org; Wed, 24 Jan 2007 10:32:01 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9k6I-00087G-Hq
	for sipping@ietf.org; Wed, 24 Jan 2007 10:32:01 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	ED0525480E9; Wed, 24 Jan 2007 16:27:32 +0100 (CET)
X-AuditID: c1b4fb3c-ae7c5bb0000007de-45-45b77ae46de1 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	C9A84520001; Wed, 24 Jan 2007 16:27:32 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Jan 2007 16:27:32 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Jan 2007 16:27:19 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 6701B236E;
	Wed, 24 Jan 2007 17:27:19 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id ED0D14DACD;
	Wed, 24 Jan 2007 17:27:18 +0200 (EET)
Received: from localhost.localdomain (localhost [IPv6:::1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 8246E4DACC;
	Wed, 24 Jan 2007 17:27:18 +0200 (EET)
Subject: Re: [Sipping] Comments
	to	draft-rosenberg-sipping-service-identification-00.txt
From: "Salvatore Loreto (JO/LMF)" <salvatore.loreto@ericsson.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <45B76A8A.7050307@cisco.com>
References: <45B75AED.3060908@nokia.com>  <45B76A8A.7050307@cisco.com>
Content-Type: text/plain; charset=utf-8
Date: Wed, 24 Jan 2007 17:27:55 +0200
Message-Id: <1169652475.9696.71.camel@n95.nomadiclab.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-4.fc4) 
X-Virus-Scanned: ClamAV using ClamSMTP
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 24 Jan 2007 15:27:19.0526 (UTC)
	FILETIME=[22EE2860:01C73FCC]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
Cc: Miguel Garcia <Miguel.An.Garcia@nokia.com>, Sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hino,

I have read the draft and I think is good that it clearly acknowledges
the need for service identification.

However, the draft really does not seem to have a clear argument to
use service URN/Require header/Route header mechanisms vs media feature
tag to identify services, or at least I am not able to see the
advantages.

see also my comments in line

/sal


On Wed, 2007-01-24 at 09:17 -0500, Paul Kyzivat wrote:
> Comments inline.
>=20
> Miguel Garcia wrote:
> > Some comments to the Service Identification draft.
> >=20
> > - The draft mandates the usage of the Require header including a serv=
ice=20
> > URN. I think this usage is too restrictive. Imagine I establish a=20
> > session with you, using a given service, and I want to give you a hin=
t=20
> > of the service that I am using, but it is not strictly required that =
you=20
> > use exactly the same service. For example: I am using my IM client to=
=20
> > establish a voice session with you. It would be nice if you happen to=
=20
> > have an IM service client that supports voice, since we can start wit=
h=20
> > voice and add IM later. But it is not necessary: you could answer wit=
h=20
> > your telephony client and we could still have voice among both. This=20
> > seems to advocate a Supported header (hint) in some cases.
>=20
> This comment highlights the overlap between "service", "capability", an=
d=20
> "preference".
>=20
> What you describe is a caller that requires voice (generic voice - no=20
> special service involving voice), that has a capability to do IM, and=20
> that has a preference for contacting a UAS that supports IM as well as=20
> voice.
>=20
> To deal with that, we already have callerprefs, and mmusic is working o=
n=20
> SDP capability negotiation that also may bring something useful.
>=20
> I don't see why the service identification mechanism has to solve this=20
> problem too.

here I agree with Miguel, the usage of Require header is too
restrictive. Actually the tag, whatever, a feature tag like in 3gpp
solution or a URN like in the Rosemberg proposal, should be only
informative.

Of course for IM and Voice scenario described Paul is right,=20
we can handle this scenario with callerprefs,=20
but what about the scenario where I want start a PoC session with you,
but if you don t have a PoC client I want establish a normal audio
session. If I use the Require header solution this is not possible at
all.

I really do belive that the Require header proposal destroy all the
service URN potentiality:
"The URN consists of a hierarchical service identifier, ...
For any given service URN, service-identifiers can be removed
right-to-left and resulting URN is still valid, referring a more generic
service" (draft-ietf-ecrit-service-urn-05 in Section 3)



> > - I understand the motivation for overloading the Require header for=20
> > transporting URNs, but I think it is an ugly solution, and the fact t=
hat=20
> > the RFC says you can only insert standardized option tags is not enou=
gh=20
> > to prevent people writing other non-standardize tags if they wish to=20
> > violate the RFC.
>=20
> It doesn't prevent individuals, or developers of closed systems from=20
> doing so. But it does make it difficult for other SDOs from doing so,=20
> and developers of systems that interoperate with standards complying=20
> components will at least get some pressure.
>=20
> This service mechanism has a high potential to create a real Tower of=20
> Babel if it isn't managed carefully.

Paul I see what you are afraid about the risk in the service mechanism,
but in this way IETF should start to standardize and take care also of
the services. I don=C2=B4t know if this is a good idea.



>=20
> > So, I was wondering why not creating a Service header=20
> > or something like that. The header would have the same constrains abo=
ut=20
> > how to populate it. And I think it would also solve the previous issu=
e:=20
> > serve as a hint, rather than as a requirement.
> >=20
> > - Populating the last Route entry with the Service URN is a nice=20
> > feature. I was wondering if application servers will have to delete t=
his=20
> > last route when they execute the service. I didn't find much written =
on=20
> > the draft. I think servers will not be able to delete this last route=
=20
> > ever, because they cannot guarantee that other servers downstream wil=
l=20
> > need the same entry to route to other application servers. Think of a=
=20
> > service that requires originating and terminating support. The draft=20
> > should in any case discuss this topic.
>=20
> I have similar concerns. The Route header is an interesting approach=20
> that I too like in some ways. But its far from clear how to partition=20
> responsibility in order to resolve issues such as the one you raise.=20
> Jonathan already included flexibility to reorder these. (And I already=20
> complained about the mechanism. I think those that add Route headers=20
> ought to get the say about what reordering is allowed, rather than=20
> having it determined by the type of URI.)
>=20
> But reordering only helps if somebody has reason to know what order is=20
> appropriate. If the element adding the header didn't know the right=20
> order, then how can we expect some other element to know?
>=20
> Your issue is a further extension. In addition to reordering, there is=20
> the issue of knowing when something has been done. With regular Route=20
> header values, containing SIP URIs, we generally assume that a server=20
> knows when it owns that URI, and then removes the Route header. I think=
=20
> we need to assume essentially the same model for URNs - the server know=
s=20
> when it supports one, and then removes it. If it thinks there is=20
> *another* server that also supports that URN, then it can add *another*=
=20
> Route for that. But of course that raises some horrible issues of=20
> looping that I don't immediately see how to resolve in the general case=
.
>=20
> In the case of adding support on both the originating and terminating=20
> sides, this might be less of a problem. The UAC, or a proxy on the=20
> originating side acting for the UAC, can add a Route header with the=20
> URN, based on the presence of the Require header or something, and then=
=20
> this will be resolved on the originating side before the R-URI is=20
> translated to send the request to the terminating side. Then a proxy on=
=20
> the terminating side can add a Route header, again based on the Require=
=20
> header of something, which will then be resolved on the terminating sid=
e.
>=20
> IMO it is fundamental that the UAC *not* make assumptions about how the=
=20
> service is implemented on the terminating side, as that prevents=20
> alternative implementations.

the mechanism to trigger an application server in both originating and
terminating side, is not clear in the draft.
And the solution proposed above, to clarify the usage in the terminating
side, seems to be a little bit too complicate.


>=20
> 	Thanks,
> 	Paul
>=20
> > - A definitions section in the draft would help. At least, Service=20
> > Instance URI and Service URI should go there.
> >=20
> > /Miguel
> >=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org Wed Jan 24 11:25:13 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9kvS-0002LV-8W; Wed, 24 Jan 2007 11:24:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9kvR-0002LQ-K3
	for sipping@ietf.org; Wed, 24 Jan 2007 11:24:41 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H9kvP-0006EX-Dt
	for sipping@ietf.org; Wed, 24 Jan 2007 11:24:41 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 24 Jan 2007 11:24:39 -0500
X-IronPort-AV: i="4.13,233,1167627600"; 
	d="scan'208"; a="112387518:sNHT65056816"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l0OGOcrw019393; 
	Wed, 24 Jan 2007 11:24:38 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l0OGOWVb009768; 
	Wed, 24 Jan 2007 11:24:38 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Jan 2007 11:24:36 -0500
Received: from [161.44.183.166] ([161.44.183.166]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Jan 2007 11:24:36 -0500
Message-ID: <45B78843.7030905@cisco.com>
Date: Wed, 24 Jan 2007 11:24:35 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.An.Garcia@nokia.com>
Subject: Re: [Sipping] Comments
	to	draft-rosenberg-sipping-service-identification-00.txt
References: <45B75AED.3060908@nokia.com> <45B76A8A.7050307@cisco.com>
	<45B7775C.80207@nokia.com>
In-Reply-To: <45B7775C.80207@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jan 2007 16:24:36.0185 (UTC)
	FILETIME=[2356B490:01C73FD4]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=12667; t=1169655878;
	x=1170519878; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Comments=20to=09draft-rosenberg-sipping-s
	ervice-identification-00.txt |Sender:=20
	|To:=20Miguel=20Garcia=20<Miguel.An.Garcia@nokia.com>;
	bh=r86y9JaIBRf+Gaoz0n2Wb8IYuqHXDNolpvt+kx4VYTo=;
	b=pDh8zo7bXQTCEh8rIfXE/FrytgoEoM3MfYNJDLN6nkEpAZzX+4rJ5nk6eEtr3B7lh/n7VJsY
	nzp/kZJUfdzfh4irNu2bqEjcAR5RiGtUX837tjNf7xcmeBfw/zjDBGMd;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 162d87dc0b780d17da9b1934777fd451
Cc: Sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

More comments...

Miguel Garcia wrote:
> Some inline thoughts.
> 
> Paul Kyzivat wrote:
>> Comments inline.
>>
>> Miguel Garcia wrote:
>>> Some comments to the Service Identification draft.
>>>
>>> - The draft mandates the usage of the Require header including a 
>>> service URN. I think this usage is too restrictive. Imagine I 
>>> establish a session with you, using a given service, and I want to 
>>> give you a hint of the service that I am using, but it is not 
>>> strictly required that you use exactly the same service. For example: 
>>> I am using my IM client to establish a voice session with you. It 
>>> would be nice if you happen to have an IM service client that 
>>> supports voice, since we can start with voice and add IM later. But 
>>> it is not necessary: you could answer with your telephony client and 
>>> we could still have voice among both. This seems to advocate a 
>>> Supported header (hint) in some cases.
>>
>> This comment highlights the overlap between "service", "capability", 
>> and "preference".
>>
>> What you describe is a caller that requires voice (generic voice - no 
>> special service involving voice), that has a capability to do IM, and 
>> that has a preference for contacting a UAS that supports IM as well as 
>> voice.
> 
> I would say ".... that has a preference for contacting the same service 
> that the calling party is using". The reason is that future interactions 
> may involve other capabilities that this service is able to offer.

This emphasizes a key philosophical difference I think - one that goes 
all the way back to the early discussions around rpids and the meaning 
of "service" in presence. One approach is that a service is just a 
collection of capabilities. (Your "IM Service Client" is just a 
combination of an audio capability and an IM capability.) The other 
approach is that a service has an arbitrary name, which implies some 
combination of capabilities and ways to use those capabilities, but 
doesn't explicitly state what the capabilities are. It is assumed that 
if you support the service then you know what it implies.

Jonathan has attempted to thread the needle once again regarding that 
difference. But it doesn't seem to be succeeding. He was trying to draw 
the distinction between what the capabilities are, and how they are 
used. (So that audio and IM used to support a chess game is different 
from audio and IM used conversationally.)

In the example you give, it doesn't seem to me that any special service 
is needed (or depending on your viewpoint, some generic personal 
communications service may be appropriate - whatever is normally used 
for regular calling.)

>> To deal with that, we already have callerprefs, and mmusic is working 
>> on SDP capability negotiation that also may bring something useful.
> 
> I still don't see how I can signal my preference for a service to be used.

Lets go to Jonathan's example of the Chess service. If you were calling 
from your chess program, I think you would have more than a "preference" 
for a chess service at the other end. Conversely, if you are not calling 
from your chess program, then you don't want a chess service at the 
other end.

For services to be anything different from capabilities and preferences, 
  I find it hard to see how they can be optional.

>> I don't see why the service identification mechanism has to solve this 
>> problem too.
> 
> Because for a basic communication (say voice), any UI or application 
> will work, but for more advanced features, if both UAs have the same 
> service through an implementation, then that is the desired effect. 
> think the service ID fits perfectly in here.

Why isn't IM, and Video, also considered "basic communication"?

IMO basic communication is that we can establish a sip session and then 
we use sip to negotiate the media that we will use in that session. We 
both trust the other side to be able to utilize the media in some 
appropriate way. That may be a human being communicating in an ad-hoc 
manner.

It may be an IVR that has a particular kind of communication it carries 
out when called. As such, an IVR could conceivably be called a 
"service". For instance an airline reservation service or a pharmacy 
prescription ordering service. But hopefully they aren't services in the 
sense discussed by this draft - the caller doesn't have to specify the 
service in the request in order for it to be handled by the proper IVR.

>>> - I understand the motivation for overloading the Require header for 
>>> transporting URNs, but I think it is an ugly solution, and the fact 
>>> that the RFC says you can only insert standardized option tags is not 
>>> enough to prevent people writing other non-standardize tags if they 
>>> wish to violate the RFC.
>>
>> It doesn't prevent individuals, or developers of closed systems from 
>> doing so. But it does make it difficult for other SDOs from doing so, 
>> and developers of systems that interoperate with standards complying 
>> components will at least get some pressure.
> 
> Agreed. My point is that you get the same effect by defining a new 
> header and writing down the same constraints that Require has. IMHO this 
> is not a justification for overloading the semantics of an existing header.

I don't have a strong feeling on this point. I think jonathan's intent 
in going this way was a belief that this isn't really overloading - that 
the purpose really is the same - that chess is an option in the same way 
that 100rel is an option.

>> This service mechanism has a high potential to create a real Tower of 
>> Babel if it isn't managed carefully.
> 
> I fully agree. It makes me very nervous. And the only usage of the 
> Require header makes me nervous exactly in this sense. I believe the 
> service preference is enough in most cases, perhaps is the only one that 
> should go into the draft.
> 
>>
>>> So, I was wondering why not creating a Service header or something 
>>> like that. The header would have the same constrains about how to 
>>> populate it. And I think it would also solve the previous issue: 
>>> serve as a hint, rather than as a requirement.
>>>
>>> - Populating the last Route entry with the Service URN is a nice 
>>> feature. I was wondering if application servers will have to delete 
>>> this last route when they execute the service. I didn't find much 
>>> written on the draft. I think servers will not be able to delete this 
>>> last route ever, because they cannot guarantee that other servers 
>>> downstream will need the same entry to route to other application 
>>> servers. Think of a service that requires originating and terminating 
>>> support. The draft should in any case discuss this topic.
>>
>> I have similar concerns. The Route header is an interesting approach 
>> that I too like in some ways. But its far from clear how to partition 
>> responsibility in order to resolve issues such as the one you raise. 
>> Jonathan already included flexibility to reorder these. (And I already 
>> complained about the mechanism. I think those that add Route headers 
>> ought to get the say about what reordering is allowed, rather than 
>> having it determined by the type of URI.)
>>
>> But reordering only helps if somebody has reason to know what order is 
>> appropriate. If the element adding the header didn't know the right 
>> order, then how can we expect some other element to know?
>>
>> Your issue is a further extension. In addition to reordering, there is 
>> the issue of knowing when something has been done. With regular Route 
>> header values, containing SIP URIs, we generally assume that a server 
>> knows when it owns that URI, and then removes the Route header. I 
>> think we need to assume essentially the same model for URNs - the 
>> server knows when it supports one, and then removes it. 
> 
> This is the point where things fall apart. In general, a server will not 
> have information of whether other servers downstream have to take an 
> action based on the invoked service.

If it doesn't, then it shouldn't be inserting a Route header. Only an 
element that does have the information should add the header.

> In my opinion, there isn't harm in 
> leaving a Route header there if the service URN was there, so that 
> routing can still continue downstream and other servers might get 
> involved, if required.
> 
>> If it thinks there is *another* server that also supports that URN, 
>> then it can add *another* Route for that. 
> 
> Well, on the wire there is no difference between preserving the service 
> URN and first removing it and then add it again.

There is no observable difference from the outside of the black box. But 
there is a conceptual difference. When you receive the request, if the 
Route header matches you, then you should remove it. Then, if you think 
you know of another hop that ought to be involved then you can add a 
Route header for that.

I think this might be clearer if we discuss how a Route header with a 
URN is to be handled. I expect that some server should take 
responsibility for resolving it. That would involve translating the URN 
to a URI using some mechanism. Then a Route header containing the 
translation should replace that containing the URN, and routing of the 
request can continue. The resolution could be by a server different from 
the one identified by the translation, or it could be that the server 
translating it says "I am responsible for that". In the latter case, 
conceptually it would translate. Then once there is a Route header 
identifying itself it would remove that. (In practice of course it can 
just remove the Route header containing the URN, but the model gives the 
rationale for removing.)

>> But of course that raises some horrible issues of looping that I don't 
>> immediately see how to resolve in the general case.
> 
> That is right. There should be me some mechanism to avoid loops. I am 
> not sure if the general SIP mechanism for loop avoidance is enough.

I think they should be enough to detect the loop. But you really want to 
prevent the loop.

Consider an IMS environment. Perhaps the S-CSCF is responsible for 
resolving a Route header containing a URN, replacing with one 
identifying what is most likely an AS, and then routing to it. The AS 
would then remove itself from the route. As long as nobody adds another 
Route for the same URN in things are then ok. But if that AS, or 
another, adds back a Route for that URN then a loop is created with no 
obviously easy way to resolve.

Alternately, the S-CSCF might not replace the URN when resolving it, but 
rather leave it in place and simply route the request to the resolved 
address. And then that server could potentially just leave the URN in 
the route. In that case again there is a troublesome loop.

>> In the case of adding support on both the originating and terminating 
>> sides, this might be less of a problem. The UAC, or a proxy on the 
>> originating side acting for the UAC, can add a Route header with the 
>> URN, based on the presence of the Require header or something, and 
>> then this will be resolved on the originating side before the R-URI is 
>> translated to send the request to the terminating side. Then a proxy 
>> on the terminating side can add a Route header, again based on the 
>> Require header of something, which will then be resolved on the 
>> terminating side.
> 
> This is weird. So we have a proxy inspecting headers to determine that a 
> SIP request should be routed to the Service application server.... I 
> thought that was the sole purpose of adding the Service URN to the Route 
> header.

As I understand it, the point is for whatever component knows that the 
server is needed should add the Route. If the UAC knows then it should 
add it. If the originating proxy knows, then *it* should add it. This 
depends on your view of how responsibility for features is distributed 
among the pieces of the system.

>> IMO it is fundamental that the UAC *not* make assumptions about how 
>> the service is implemented on the terminating side, as that prevents 
>> alternative implementations.
> 
> Agreed.
> 
> 
>>
>>     Thanks,
>>     Paul
>>
> 
> BR,
> 
>        Miguel
> 
> 
>>> - A definitions section in the draft would help. At least, Service 
>>> Instance URI and Service URI should go there.
>>>
>>> /Miguel
>>>
> 

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



From sipping-bounces@ietf.org Wed Jan 24 12:39:52 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9m52-0007bd-NV; Wed, 24 Jan 2007 12:38:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9m51-0007Zj-2A
	for sipping@ietf.org; Wed, 24 Jan 2007 12:38:39 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9m4z-0003FJ-9P
	for sipping@ietf.org; Wed, 24 Jan 2007 12:38:39 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-4.cisco.com with ESMTP; 24 Jan 2007 09:38:36 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l0OHcaiE018711; 
	Wed, 24 Jan 2007 09:38:36 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l0OHcZnF008808;
	Wed, 24 Jan 2007 09:38:36 -0800 (PST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Jan 2007 12:38:35 -0500
Received: from [161.44.174.190] ([161.44.174.190]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Jan 2007 12:38:35 -0500
Message-ID: <45B7999A.3020701@cisco.com>
Date: Wed, 24 Jan 2007 12:38:34 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: "Salvatore Loreto (JO/LMF)" <salvatore.loreto@ericsson.com>
Subject: Re: [Sipping]
	Comments	to	draft-rosenberg-sipping-service-identification-00.txt
References: <45B75AED.3060908@nokia.com> <45B76A8A.7050307@cisco.com>
	<1169652475.9696.71.camel@n95.nomadiclab.com>
In-Reply-To: <1169652475.9696.71.camel@n95.nomadiclab.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 24 Jan 2007 17:38:35.0499 (UTC)
	FILETIME=[796043B0:01C73FDE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=11155; t=1169660316;
	x=1170524316; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Comments=09to=09draft-rosenberg-sipping-s
	ervice-identification-00.txt |Sender:=20;
	bh=VIG912XP4GnSRZLcaT2y1wNBTnj+cvHiGAzVa+MHQlw=;
	b=XP+PIa1+nIE+aPaR/FeKIH5G7sKvoeiEPMYhoftOhLXPl+u/gPRkDwEjdCrO0SWtVimIA+Bl
	4vrtW1dgWqq7BpQp5QeOS9QCfyKUFv9CuGF0UME4pBKpBd8UHYjHWer8;
Authentication-Results: sj-dkim-7; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
Cc: Miguel Garcia <Miguel.An.Garcia@nokia.com>, Sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Salvatore Loreto (JO/LMF) wrote:
> Hino,
> 
> I have read the draft and I think is good that it clearly acknowledges
> the need for service identification.
> 
> However, the draft really does not seem to have a clear argument to
> use service URN/Require header/Route header mechanisms vs media feature
> tag to identify services, or at least I am not able to see the
> advantages.

Well, as you can see from my other comments, I have for *years* not been 
able to distinguish the difference between services and capabilities. 
IMO it indeed should be possible to use capabilities and preferences as 
an alternative to services.

BUT, the examples of services that I often see used don't line up with 
capabilities very well, at least the way they are being done.

So, I think it is fine to use capabilities and preferences for those 
cases where they fit without abusing the callerprefs mechanism. And if 
there are then other things that can't be done that way, then some new 
mechanism may still be needed.

I think one part that callerprefs doesn't support well, if at all, is 
the inclusion of intermediate servers into the call path. Certainly 
there is nothing in RFCs 3840 and 3841 that provides a way to do so, 
unless you use it to select a B2BUA to terminate your call, after which 
the B2BUA would need to orignate some other call. But doing that would 
imply that the B2BUA was one of the candidates in the location server 
for the AOR being called. And even then that would only cover the 
terminating side - it wouldn't help in getting an intermediate server 
into the originating side of a call.

Its my impression that one IMS proposal for this (from Ericsson I think) 
is indeed to use a media feature tag in an accept-contact header. Then 
to involve in intermediate server, an S-CSCF (orig or term) would match 
the existence of the feature tag in an accept-contact header and use 
that as an indication that an intermediate server was required. What I 
haven't seen is any explanation of how that would work given that 
callerprefs permits complex expressions that end up excluding some 
candidates and prioritizing others. For instance one might specify in an 
accept-contact that you want (AUDIO and VIDEO and *not* POC), or that 
AUDIO should be tried first, and if that is unsuccessful then try POC.

If the use of media feature tags for identifying services then restricts 
the ways in which callerprefs can be used, then it is an abuse and 
should not be pursued.

> see also my comments in line
> 
> /sal
> 
> 
> On Wed, 2007-01-24 at 09:17 -0500, Paul Kyzivat wrote:
>> Comments inline.
>>
>> Miguel Garcia wrote:
>>> Some comments to the Service Identification draft.
>>>
>>> - The draft mandates the usage of the Require header including a service 
>>> URN. I think this usage is too restrictive. Imagine I establish a 
>>> session with you, using a given service, and I want to give you a hint 
>>> of the service that I am using, but it is not strictly required that you 
>>> use exactly the same service. For example: I am using my IM client to 
>>> establish a voice session with you. It would be nice if you happen to 
>>> have an IM service client that supports voice, since we can start with 
>>> voice and add IM later. But it is not necessary: you could answer with 
>>> your telephony client and we could still have voice among both. This 
>>> seems to advocate a Supported header (hint) in some cases.
>> This comment highlights the overlap between "service", "capability", and 
>> "preference".
>>
>> What you describe is a caller that requires voice (generic voice - no 
>> special service involving voice), that has a capability to do IM, and 
>> that has a preference for contacting a UAS that supports IM as well as 
>> voice.
>>
>> To deal with that, we already have callerprefs, and mmusic is working on 
>> SDP capability negotiation that also may bring something useful.
>>
>> I don't see why the service identification mechanism has to solve this 
>> problem too.
> 
> here I agree with Miguel, the usage of Require header is too
> restrictive. Actually the tag, whatever, a feature tag like in 3gpp
> solution or a URN like in the Rosemberg proposal, should be only
> informative.

See my response to Miguel

> Of course for IM and Voice scenario described Paul is right, 
> we can handle this scenario with callerprefs, 
> but what about the scenario where I want start a PoC session with you,
> but if you don t have a PoC client I want establish a normal audio
> session. If I use the Require header solution this is not possible at
> all.

If you want a call that prefers POC but will take normal audio as a 
fallback, then the case fits callerprefs pretty well - if POC is 
implemented entirely in the UAC and UAS.

But if POC requires a server in the path, and normal audio doesn't, then 
callerprefs aren't a very good fit for this, and in fact it isn't clear 
to me how you would do this. (I think the proper way is probably to 
establish the call e2e and then have the UAC and UAS invoke a helper 
server if needed for POC.

> I really do belive that the Require header proposal destroy all the
> service URN potentiality:
> "The URN consists of a hierarchical service identifier, ...
> For any given service URN, service-identifiers can be removed
> right-to-left and resulting URN is still valid, referring a more generic
> service" (draft-ietf-ecrit-service-urn-05 in Section 3)
> 
> 
> 
>>> - I understand the motivation for overloading the Require header for 
>>> transporting URNs, but I think it is an ugly solution, and the fact that 
>>> the RFC says you can only insert standardized option tags is not enough 
>>> to prevent people writing other non-standardize tags if they wish to 
>>> violate the RFC.
>> It doesn't prevent individuals, or developers of closed systems from 
>> doing so. But it does make it difficult for other SDOs from doing so, 
>> and developers of systems that interoperate with standards complying 
>> components will at least get some pressure.
>>
>> This service mechanism has a high potential to create a real Tower of 
>> Babel if it isn't managed carefully.
> 
> Paul I see what you are afraid about the risk in the service mechanism,
> but in this way IETF should start to standardize and take care also of
> the services. I don´t know if this is a good idea.

To paraphrase, I think services should be "rare and safe."

I fear that only the ietf is concerned about this risk, and think that 
unless we do something to prevent it there is *substantial* risk that a 
large percentage of calls will be made in a way that is only 
interoperable within a closed club of players.

I do think the callerprefs mechanism, used as intended, has fewer 
potential problems, as long as new capabilities are truly distinct and 
orthogonal to other capabilities, rather than being opaque named 
collections of capabilities.

>>> So, I was wondering why not creating a Service header 
>>> or something like that. The header would have the same constrains about 
>>> how to populate it. And I think it would also solve the previous issue: 
>>> serve as a hint, rather than as a requirement.
>>>
>>> - Populating the last Route entry with the Service URN is a nice 
>>> feature. I was wondering if application servers will have to delete this 
>>> last route when they execute the service. I didn't find much written on 
>>> the draft. I think servers will not be able to delete this last route 
>>> ever, because they cannot guarantee that other servers downstream will 
>>> need the same entry to route to other application servers. Think of a 
>>> service that requires originating and terminating support. The draft 
>>> should in any case discuss this topic.
>> I have similar concerns. The Route header is an interesting approach 
>> that I too like in some ways. But its far from clear how to partition 
>> responsibility in order to resolve issues such as the one you raise. 
>> Jonathan already included flexibility to reorder these. (And I already 
>> complained about the mechanism. I think those that add Route headers 
>> ought to get the say about what reordering is allowed, rather than 
>> having it determined by the type of URI.)
>>
>> But reordering only helps if somebody has reason to know what order is 
>> appropriate. If the element adding the header didn't know the right 
>> order, then how can we expect some other element to know?
>>
>> Your issue is a further extension. In addition to reordering, there is 
>> the issue of knowing when something has been done. With regular Route 
>> header values, containing SIP URIs, we generally assume that a server 
>> knows when it owns that URI, and then removes the Route header. I think 
>> we need to assume essentially the same model for URNs - the server knows 
>> when it supports one, and then removes it. If it thinks there is 
>> *another* server that also supports that URN, then it can add *another* 
>> Route for that. But of course that raises some horrible issues of 
>> looping that I don't immediately see how to resolve in the general case.
>>
>> In the case of adding support on both the originating and terminating 
>> sides, this might be less of a problem. The UAC, or a proxy on the 
>> originating side acting for the UAC, can add a Route header with the 
>> URN, based on the presence of the Require header or something, and then 
>> this will be resolved on the originating side before the R-URI is 
>> translated to send the request to the terminating side. Then a proxy on 
>> the terminating side can add a Route header, again based on the Require 
>> header of something, which will then be resolved on the terminating side.
>>
>> IMO it is fundamental that the UAC *not* make assumptions about how the 
>> service is implemented on the terminating side, as that prevents 
>> alternative implementations.
> 
> the mechanism to trigger an application server in both originating and
> terminating side, is not clear in the draft.
> And the solution proposed above, to clarify the usage in the terminating
> side, seems to be a little bit too complicate.

I am inclined to agree. We suffer because the kinds of things an 
intermediate server would do if involved in a call in order to 
facilitate a "service" is not even within the vocabulary of the ietf. It 
feels to me that we are dancing around the elephant in the room without 
acknowledging its presence.

	Paul

>> 	Thanks,
>> 	Paul
>>
>>> - A definitions section in the draft would help. At least, Service 
>>> Instance URI and Service URI should go there.
>>>
>>> /Miguel
>>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the 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 sipping-bounces@ietf.org Wed Jan 24 15:50:41 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9p4M-0006y7-Ii; Wed, 24 Jan 2007 15:50:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9p4E-0006tk-Tu; Wed, 24 Jan 2007 15:50:02 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H9p4E-00021C-C3; Wed, 24 Jan 2007 15:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 52C703293C;
	Wed, 24 Jan 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1H9p4E-0008VB-4c; Wed, 24 Jan 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1H9p4E-0008VB-4c@stiedprstage1.ietf.org>
Date: Wed, 24 Jan 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-service-examples-12.txt 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

--NextPart

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

	Title		: Session Initiation Protocol Service Examples
	Author(s)	: A. Johnston, et al.
	Filename	: draft-ietf-sipping-service-examples-12.txt
	Pages		: 164
	Date		: 2007-1-24
	
This document gives examples of Session Initiation Protocol (SIP)
   services.  This covers most features offered in so-called IP 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 header fields.  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-12.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sipping-service-examples-12.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-12.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-service-examples-12.txt

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

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


--OtherAccess--

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

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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--




From sipping-bounces@ietf.org Wed Jan 24 16:22:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9pEU-0006SR-3a; Wed, 24 Jan 2007 16:00:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9pEG-0006J4-6x
	for sipping@ietf.org; Wed, 24 Jan 2007 16:00:24 -0500
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9pDv-00061e-HY
	for sipping@ietf.org; Wed, 24 Jan 2007 16:00:23 -0500
Received: from kyzyl.cablelabs.com (kyzyl.cablelabs.com [10.253.0.7])
	by ondar.cablelabs.com (8.13.8/8.13.8) with ESMTP id l0OKsoUb016138
	for <sipping@ietf.org>; Wed, 24 Jan 2007 13:54:51 -0700 (MST)
Received: from srvxchg.cablelabs.com (10.5.0.20)
	by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com);
	Wed, 24 Jan 2007 13:54:49 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com)
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"
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] draft-ietf-sipping-config-framework-10
Date: Wed, 24 Jan 2007 13:54:49 -0700
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D8480402106894@srvxchg.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] draft-ietf-sipping-config-framework-10
Thread-Index: Acc+jP0z18+zPEMZQoS7fWkb0LxC1gBa1zGA
From: "Sumanth Channabasappa" <sumanth@cablelabs.com>
To: "sipping" <sipping@ietf.org>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Folks,

Now that v10 is available online
(http://www.ietf.org/internet-drafts/draft-ietf-sipping-config-framework
-10.txt), here is a brief summary of the changes in this version
(reproduced in part from section 12.1).

   Changes incorporated by the author:
   o  Incorporated numerous edits and corrections from CableLabs review
   o  Used better ascii art picture of overview from Josh Littlefield
   o  Fixed the normative text for network-user so that it is now
      consistant: MAY provide for device profile, MUST provide for
      local-network profile

   Changes incorporated by the editor:
   o  Restructured document based on a) Keith's recommendations in
      the email dated 11/09/2006 and responses (Peter, Sumanth, Josh) b)
      subsequent discussions by the ad-hoc group consisting of the
      editor, the author, expert contributors (Peter Blatherwick, Josh
      Littlefield, Alvin Jiang, Jason Fischl, Martin Dolly, Cullen
      Jennings) and the co-chairs=20
   o  Modified the contents of various sections as part of the
restructuring=20
      efforts (notably: Overview, Introduction, Framework Requirements &

      Security)
   o  Revised Use cases and added detailed examples

This (-v10) is preliminary update and we plan to address the open items
(listed in section 11; for example, the security section could use
expert reviews) in the upcoming weeks. This is being presented to obtain
feedback from the WG. Additionally, if folks wish to participate in
offline discussions or sign up as expert reviewers please let myself,
the author or the co-chairs know.=20

Comments and feedback will be appreciated (thanks to Cullen and Henning
for early feedback on the mailing list).

Thanks!

- S




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



From sipping-bounces@ietf.org Thu Jan 25 09:19:54 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HA5QT-0004LL-QM; Thu, 25 Jan 2007 09:18:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HA5QS-0004LE-CY
	for sipping@ietf.org; Thu, 25 Jan 2007 09:18:04 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HA5QO-00057X-0V
	for sipping@ietf.org; Thu, 25 Jan 2007 09:18:04 -0500
Received: from 24-107-197-43.dhcp.stls.mo.charter.com ([24.107.197.43]
	helo=[192.168.0.40])
	by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.63) (envelope-from <alan@sipstation.com>) id 1HA5QH-000An4-0v
	for sipping@ietf.org; Thu, 25 Jan 2007 09:17:53 -0500
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.107.197.43
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: digitalari
Message-ID: <45B8BC16.2040202@sipstation.com>
Date: Thu, 25 Jan 2007 08:17:58 -0600
From: Alan Johnston <alan@sipstation.com>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: sipping@ietf.org
Subject: Re: [Sipping] I-D ACTION:draft-ietf-sipping-service-examples-12.txt
References: <E1H9p4E-0008VB-4c@stiedprstage1.ietf.org>
In-Reply-To: <E1H9p4E-0008VB-4c@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

All,

With this update, I think I have fixed all the reviewers comments.

Major changes were made to 2.3 Music On Hold (the problematic 3pcc flow 
now uses REFER Replaces) and 2.17 Automatic Redial (adding explicit 
dialog package subscription termination with a SUBSCRIBE Expires:0)

In addition, I have shown the use of the +sip.rendering feature tag for 
on-hold re-INVITEs, and the use of automaton and +sip.byeless for the 
Park Server and Music Server.

Thanks,
Alan

Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.
>
> 	Title		: Session Initiation Protocol Service Examples
> 	Author(s)	: A. Johnston, et al.
> 	Filename	: draft-ietf-sipping-service-examples-12.txt
> 	Pages		: 164
> 	Date		: 2007-1-24
> 	
> This document gives examples of Session Initiation Protocol (SIP)
>    services.  This covers most features offered in so-called IP 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 header fields.  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-12.txt
>
> To remove yourself from the I-D Announcement list, send a message to 
> i-d-announce-request@ietf.org with the word unsubscribe in the body of 
> the message. 
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the 
> username "anonymous" and a password of your e-mail address. After 
> logging in, type "cd internet-drafts" and then 
> "get draft-ietf-sipping-service-examples-12.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-12.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 sipping-bounces@ietf.org Thu Jan 25 10:06:50 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HA6BD-00089b-Up; Thu, 25 Jan 2007 10:06:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HA6BA-000890-Ez; Thu, 25 Jan 2007 10:06:20 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HA6BA-00013K-7a; Thu, 25 Jan 2007 10:06:20 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id F1ED326EFB;
	Thu, 25 Jan 2007 15:06:19 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HA6B9-00035G-Se; Thu, 25 Jan 2007 10:06:19 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1HA6B9-00035G-Se@stiedprstage1.ietf.org>
Date: Thu, 25 Jan 2007 10:06:19 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: Internet Architecture Board <iab@iab.org>,
	sipping mailing list <sipping@ietf.org>,
	sipping chair <sipping-chairs@tools.ietf.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Sipping] Document Action: 'Framework for Transcoding with the 
 Session Initiation Protocol (SIP)' to Informational RFC 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

The IESG has approved the following document:

- 'Framework for Transcoding with the Session Initiation Protocol (SIP) '
   <draft-ietf-sipping-transc-framework-05.txt> as an Informational RFC

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

The IESG contact persons are Jon Peterson and Cullen Jennings.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-transc-framework-05.txt

Technical Summary
 
This document defines a framework for transcoding with SIP. This
framework includes how to discover the need of transcoding services
in a session and how to invoke those transcoding services. Two
models for transcoding services invocation are discussed: the
conference bridge model and the third party call control model. 
Both models meet the requirements for SIP regarding transcoding services
invocation to support deaf, hard of hearing, and speech-impaired
individuals.
 
Working Group Summary
 
The SIPPING WG supports the advancement of this document.
 
Protocol Quality
 
This document was reviewed for the IESG by Jon Peterson.


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



From sipping-bounces@ietf.org Thu Jan 25 10:46:24 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HA6n4-000893-Ub; Thu, 25 Jan 2007 10:45:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HA6n3-00086v-FJ
	for sipping@ietf.org; Thu, 25 Jan 2007 10:45:29 -0500
Received: from outbound-blu.frontbridge.com ([65.55.251.16]
	helo=outbound5-blu-R.bigfish.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HA6mx-0000Gk-R9
	for sipping@ietf.org; Thu, 25 Jan 2007 10:45:29 -0500
Received: from outbound5-blu.bigfish.com (localhost.localdomain [127.0.0.1])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by outbound5-blu-R.bigfish.com (Postfix) with ESMTP id D0C90E43642
	for <sipping@ietf.org>; Thu, 25 Jan 2007 15:45:17 +0000 (UTC)
Received: from mail54-blu-R.bigfish.com (unknown [10.1.252.3])
	by outbound5-blu.bigfish.com (Postfix) with ESMTP id 7F9F5B30069
	for <sipping@ietf.org>; Thu, 25 Jan 2007 15:45:17 +0000 (UTC)
Received: from mail54-blu (localhost.localdomain [127.0.0.1])
	by mail54-blu-R.bigfish.com (Postfix) with ESMTP id 2060E5482BB
	for <sipping@ietf.org>; Thu, 25 Jan 2007 15:45:17 +0000 (UTC)
X-BigFish: V
Received: by mail54-blu (MessageSwitch) id 1169739916681766_25914;
	Thu, 25 Jan 2007 15:45:16 +0000 (UCT)
Received: from smtpgw6.it.sprintspectrum.com (smtpgw6.sprintspectrum.com
	[207.40.188.14])
	by mail54-blu.bigfish.com (Postfix) with ESMTP id 571CD45006E
	for <sipping@ietf.org>; Thu, 25 Jan 2007 15:45:16 +0000 (UTC)
Received: from mailhost.sprintspectrum.com (smtpgw7.it.sprintspectrum.com
	[207.40.65.55])
	by smtpgw6.it.sprintspectrum.com (8.12.11.Beta0/8.12.8) with ESMTP id
	l0PFjFNG000864
	for <sipping@ietf.org>; Thu, 25 Jan 2007 09:45:15 -0600 (CST)
Received: from plswg02a.ad.sprint.com (PLSWG02A.corp.sprint.com [10.214.11.48])
	by mailhost.sprintspectrum.com (Switch-3.2.5/Switch-3.2.5) with ESMTP
	id l0PFj91f029165
	for <sipping@ietf.org>; Thu, 25 Jan 2007 09:45:14 -0600 (CST)
Received: from PLSWB06C.ad.sprint.com ([208.10.70.231]) by
	plswg02a.ad.sprint.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 25 Jan 2007 09:45:12 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 25 Jan 2007 09:45:08 -0600
Message-ID: <B87C644441A70D4A9D6691BF79C8FD650C4FFDCD@PLSWB06C.ad.sprint.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Offer Answer / SDP a=sdplang was [Sip-implementors]
	Accept-Language Header
Thread-Index: AcdAl8p3afdkRZCaQr6p8AUBon5RpA==
From: "Manroa, Arun [CTO]" <Arun.Manroa@sprint.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 25 Jan 2007 15:45:12.0858 (UTC)
	FILETIME=[CD195FA0:01C74097]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
Subject: [Sipping] Offer Answer / SDP a=sdplang was [Sip-implementors]
	Accept-Language Header
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-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-Type: multipart/mixed; boundary="===============0433550150=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0433550150==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C74097.CCBC4408"

This is a multi-part message in MIME format.

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

Hi,

I am trying to understand how to negotiate human language (audio output) =
preferences using SDP or SIP headers;
RFC 2327 defines a=3Dsdplang at the media level and so does the HTTP =
/SIP specs at the signaling level (Accept-Language Header). RFC 3264 =
offer answer does not delve into this.

Consider the following use case, where User A is an "English" language =
speaker using say G711 codec and want to conference in only certain =
members of a group call that not only support the G711 codec, but also =
understand the "English" language.
=20
Assume following are the users characteristics:
User A (English), Codec G711
User B (English), Codec G711
User C (Spanish), Codec G711
User D (English), Codec AMR
User E (English, Spanish), Codec G711
=20
So in this use case User A wants to connect to User B & E only, since =
the language and codec both match.(English, G711)
=20
RFC 3261 20.3 Accept-Language says..

		The Accept-Language header field is used in requests to indicate the
		   preferred languages for reason phrases, session descriptions, or
		   status responses carried as message bodies in the response.

The text says session descriptions but I not clear how that is handled =
in offer answer. Does the "Conferencing Server" send out INVITES with =
Accept-Language: en (with SDP Offer) to all participants and user C is =
going to send a 415 indicating Spanish only, and B & E are going to =
respond with a 200 OK (SDP Ans). Of course User D is going to reject the =
SDP Offer with a 415 since it does not support G711.
=20
Also the Accept-Language in REGISTER is used by the Registrar for =
generating a response, which I think is a different semantic meaning, =
maybe using RFC 3840 the users could register the appropriate language =
in the contact header, that way there is no need to send the INVITES to =
them etc.

=20
Could someone please clarify?
=20
Thanks,

Arun


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.51">
<TITLE>Offer Answer / SDP a=3Dsdplang was [Sip-implementors] =
Accept-Language Header</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

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

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">I =
am trying to understand how to negotiate human =
language</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Courier New">(audio output)</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Courier New">preferences using SDP or SIP headers</FONT><FONT =
SIZE=3D2 FACE=3D"Courier New">;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">RFC 2327 =
define</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">s</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier New"> a=3Dsdplang</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Courier New">at the media level</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Courier New">and so does the</FONT> <FONT SIZE=3D2 =
FACE=3D"Courier New">HTTP</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Courier New">/SIP</FONT> <FONT SIZE=3D2 =
FACE=3D"Courier New">specs</FONT><FONT SIZE=3D2 FACE=3D"Courier =
New"></FONT> <FONT SIZE=3D2 FACE=3D"Courier New">at =
the</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Courier New">signaling</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier New"></FONT> <FONT SIZE=3D2 FACE=3D"Courier New">level =
(Accept-</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Language</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New"> =
Header)</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">. RFC 3264 offer =
answer does not delve into this.</FONT></SPAN></P>

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

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">Consider the =
following use case, where User A is an &quot;English&quot; language =
speaker using say G711 codec and want to conference in only certain =
members of a group call that not only support the =
G711</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Courier New">codec,</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier New"> but also understand th</FONT><FONT SIZE=3D2 =
FACE=3D"Courier New">e &quot;English&quot; language.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Assume following are the users characteristics:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">User A (English</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">),</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier New"> Codec G711</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">User B</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Courier New">(English</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Courier New">), Codec G711</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">User C (Spanish), Codec G711</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">User D (English), Codec AMR</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">User E (English, Spanish), Codec G711</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">So =
in this use case User A</FONT> <FONT SIZE=3D2 FACE=3D"Courier New">wants =
to connect to User B &amp; E only, since the language and codec both =
match.(English, G711)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">RFC 3261 20.3 Accept-Language</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Courier New">says..</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Courier New">The Accept-Language header field is =
used in requests to indicate the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp; preferred languages for reason =
phrases, sessio</FONT><FONT SIZE=3D2 FACE=3D"Courier New">n =
descriptions, or</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp; status responses carried as message =
bodies in the response.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">The text says session descriptions but I not clear how that is =
handled in offer answer. Does the &quot;Conferencing Server&quot; send =
out INVITES with Accept-Language: en (with SDP</FONT> <FONT SIZE=3D2 =
FACE=3D"Courier New">Offer) to all participants and user C is going to =
send a 415 indicating Spanish only, and B &amp; E are going to respond =
with a 200 OK (SDP Ans). Of course User D is going to reject the SDP =
Offer with a 415 since it does not support G711.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Also the Accept-Language in REGISTER is used by the Registrar for =
generating a response, which I think is a different semantic meaning, =
maybe using RFC 3840 the users could register the appropriate language =
in the contact header, that way there is no need</FONT><FONT SIZE=3D2 =
FACE=3D"Courier New"></FONT> <FONT SIZE=3D2 FACE=3D"Courier New">to send =
the INVITES to them etc.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

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

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Could someone please</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Courier New">clarify?</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;</FONT></SPAN></P>

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

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Arun</FONT></SPAN></P>

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

</BODY>
</HTML>
------_=_NextPart_001_01C74097.CCBC4408--



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

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





From sipping-bounces@ietf.org Thu Jan 25 10:51:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HA6sk-0004pR-0y; Thu, 25 Jan 2007 10:51:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HA6sj-0004nG-5q
	for sipping@ietf.org; Thu, 25 Jan 2007 10:51:21 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]
	helo=p-mail1.rd.orange-ftgroup.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HA6sf-0001NE-NJ
	for sipping@ietf.org; Thu, 25 Jan 2007 10:51:21 -0500
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 25 Jan 2007 16:51:13 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Notify syntax in draft-poetzl-sipping-call-completion-01
Date: Thu, 25 Jan 2007 16:50:43 +0100
Message-ID: <49E7012A614B024B80A7D175CB9A64EC0CF2EFC1@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <45B75F5D.3020001@alcatel-lucent.be>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Notify syntax in
	draft-poetzl-sipping-call-completion-01
Thread-Index: Acc/u9NOdqVe2MxmQwSe3vRtZlrxvwA2oL4w
From: "GARCIN Sebastien RD-CORE-ISS" <sebastien.garcin@orange-ftgroup.com>
To: <Torrey.Searle@alcatel-lucent.be>,
	<sipping@ietf.org>
X-OriginalArrivalTime: 25 Jan 2007 15:51:13.0948 (UTC)
	FILETIME=[A45355C0:01C74098]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hello torrey,

I believe that you are right. It should be "...Expires parameter to the =
current remaining duration..." and not "...Expires header...".=20

We will fix this.

Thanks,
s=E9bastien

-----Message d'origine-----
De : Torrey.Searle@alcatel-lucent.be =
[mailto:Torrey.Searle@alcatel-lucent.be]=20
Envoy=E9 : mercredi 24 janvier 2007 14:30
=C0 : sipping@ietf.org
Objet : [Sipping] Notify syntax in =
draft-poetzl-sipping-call-completion-01

Attention, votre correspondant continue de vous =E9crire =E0 votre =
ancienne adresse en @orange-ft.com, qui va =EAtre d=E9sactiv=E9e d=E9but =
avril. Veuillez lui demander de mettre =E0 jour son carnet d'adresses =
avec votre nouvelle adresse en @orange-ftgroup.com.

Caution : your correspondent is still writing to your orange-ft.com =
address, which will be disabled beginning of April. Please ask him/her =
to update his/her address book to orange-ftgroup.com =
..................................................

Hello,

I have a question regarding the correct syntax of a NOTIFY message for

the call-completion Event Package.

According to draft-poetzl-sipping-call-completion-01 section 5.7 it =
says:

    Upon receiving a subscription refresh, the notifier MUST set the

    Expires header to the current remaining duration of the

    subscription regardless of the value received in the Expires header

    (if present) of the subscription refresh

However this seems to contradict RFC 3265 (section 3.2.2) where it =
states the following:

      Including expiration information for active and pending
      subscriptions is useful in case the SUBSCRIBE request forks, since
      the response to a forked SUBSCRIBE may not be received by the
      subscriber.  Note well that this "expires" value is a parameter on
      the "Subscription-State" header, NOT an "Expires" header.


Shouldn't Subscription-State be used instead of an Expires header for =
NOTIFY requests?

Torrey
Alcatel-Lucent





_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org Thu Jan 25 11:59:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HA7vf-0004OA-VO; Thu, 25 Jan 2007 11:58:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HA7vf-0004MY-3q
	for sipping@ietf.org; Thu, 25 Jan 2007 11:58:27 -0500
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HA7vd-0006w5-1g
	for sipping@ietf.org; Thu, 25 Jan 2007 11:58:27 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l0PGwM021598
	for <sipping@ietf.org>; Thu, 25 Jan 2007 11:58:22 -0500 (EST)
Received: from [47.130.18.23] ([47.130.18.23] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 25 Jan 2007 11:58:20 -0500
Message-ID: <45B8E196.9020903@nortel.com>
Date: Thu, 25 Jan 2007 11:57:58 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: "Manroa, Arun [CTO]" <Arun.Manroa@sprint.com>
Subject: Re: [Sipping] Offer Answer / SDP a=sdplang was [Sip-implementors]
	Accept-Language Header
References: <B87C644441A70D4A9D6691BF79C8FD650C4FFDCD@PLSWB06C.ad.sprint.com>
In-Reply-To: <B87C644441A70D4A9D6691BF79C8FD650C4FFDCD@PLSWB06C.ad.sprint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jan 2007 16:58:20.0720 (UTC)
	FILETIME=[0477FB00:01C740A2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

These attributes concern themselves only with signalling content, not 
the language of the media stream. For that I think you need to use 
Caller Preferences.

Manroa, Arun [CTO] wrote:
> Hi,
> 
> I am trying to understand how to negotiate human language (audio output) preferences using SDP or SIP headers;
> 
> RFC 2327 defines a=sdplang at the media level and so does the HTTP /SIP specs at the signaling level (Accept-Language Header). RFC 3264 offer answer does not delve into this.
> 
> Consider the following use case, where User A is an "English" language speaker using say G711 codec and want to conference in only certain members of a group call that not only support the G711 codec, but also understand the "English" language.
> 
>  
> 
> Assume following are the users characteristics:
> 
> User A (English), Codec G711
> 
> User B (English), Codec G711
> 
> User C (Spanish), Codec G711
> 
> User D (English), Codec AMR
> 
> User E (English, Spanish), Codec G711
> 
>  
> 
> So in this use case User A wants to connect to User B & E only, since the language and codec both match.(English, G711)
> 
>  
> 
> RFC 3261 20.3 Accept-Language says..
> 
>                 The Accept-Language header field is used in requests to indicate the
> 
>                    preferred languages for reason phrases, session descriptions, or
> 
>                    status responses carried as message bodies in the response.
> 
> The text says session descriptions but I not clear how that is handled in offer answer. Does the "Conferencing Server" send out INVITES with Accept-Language: en (with SDP Offer) to all participants and user C is going to send a 415 indicating Spanish only, and B & E are going to respond with a 200 OK (SDP Ans). Of course User D is going to reject the SDP Offer with a 415 since it does not support G711.
> 
>  
> 
> Also the Accept-Language in REGISTER is used by the Registrar for generating a response, which I think is a different semantic meaning, maybe using RFC 3840 the users could register the appropriate language in the contact header, that way there is no need to send the INVITES to them etc.
> 
>  
> 
> Could someone please clarify?
> 
>  
> 
> Thanks,
> 
> Arun
> 
> 

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



From sipping-bounces@ietf.org Fri Jan 26 00:12:59 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HAJNV-0003MW-Lr; Fri, 26 Jan 2007 00:11:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HAJNU-0003MM-GO
	for sipping@ietf.org; Fri, 26 Jan 2007 00:11:56 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAJNS-0006gg-P2
	for sipping@ietf.org; Fri, 26 Jan 2007 00:11:56 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 25 Jan 2007 21:11:54 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l0Q5Br68019899; 
	Thu, 25 Jan 2007 21:11:53 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l0Q5BrnF012266;
	Thu, 25 Jan 2007 21:11:53 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 25 Jan 2007 21:11:53 -0800
Received: from [10.32.241.149] ([10.32.241.149]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 25 Jan 2007 21:11:52 -0800
Message-ID: <45B95CF9.3020809@cisco.com>
Date: Thu, 25 Jan 2007 20:44:25 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: what is a service, was: Re: [Sipping] Comments
	to	draft-rosenberg-sipping-service-identification-00.txt
References: <45B75AED.3060908@nokia.com> <45B76A8A.7050307@cisco.com>
	<45B7775C.80207@nokia.com> <45B78843.7030905@cisco.com>
In-Reply-To: <45B78843.7030905@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jan 2007 05:11:53.0331 (UTC)
	FILETIME=[7E077430:01C74108]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=10414; t=1169788313;
	x=1170652313; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20what=20is=20a=20service,
	=20was=3A=20Re=3A=20[Sipping]=20Comme
	nts=20to=09draft-rosenberg-sipping-service-identification-00.txt
	|Sender:=20; bh=UaGThDppuMPFuIDy6kOqW1b7e6u7qd3VwzJtnRuq9P8=;
	b=lXIWxQWCKh9s+wlawBijHdkH7D9CL+o99DEBoXN8r2Cp5FVqHCKJ2r9ahNasF9okzuGITkml
	/sSrhD1pCZvQDB1N5M5N8VuFZMxhUjF0SdJVYkSHz2Bq1a/kkDAlXxrw;
Authentication-Results: sj-dkim-7; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 76c7db407a166e4c39f35d8215d8dd32
Cc: Miguel Garcia <Miguel.An.Garcia@nokia.com>, Sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Splitting this thread up a bit, since we are discussing two separate points.

inline.

Paul Kyzivat wrote:

> More comments...
> 
> Miguel Garcia wrote:
> 
>> Some inline thoughts.
>>
>> Paul Kyzivat wrote:
>>
>>> Comments inline.
>>>
>>> Miguel Garcia wrote:
>>>
>>>> Some comments to the Service Identification draft.
>>>>
>>>> - The draft mandates the usage of the Require header including a 
>>>> service URN. I think this usage is too restrictive. Imagine I 
>>>> establish a session with you, using a given service, and I want to 
>>>> give you a hint of the service that I am using, but it is not 
>>>> strictly required that you use exactly the same service. For 
>>>> example: I am using my IM client to establish a voice session with 
>>>> you. It would be nice if you happen to have an IM service client 
>>>> that supports voice, since we can start with voice and add IM later. 
>>>> But it is not necessary: you could answer with your telephony client 
>>>> and we could still have voice among both. This seems to advocate a 
>>>> Supported header (hint) in some cases.

I think this use case you are describing is NOT the problem that the 
option tag is trying to solve. In this case, there is not some 
additional context on how the signaling or media is interpreted which 
would prevent normal SIP mechanisms from working. You would not need a 
Require in the above case. The 'service' is basic SIP communications, as 
Paul has indicated.

>>>
>>>
>>> This comment highlights the overlap between "service", "capability", 
>>> and "preference".
>>>
>>> What you describe is a caller that requires voice (generic voice - no 
>>> special service involving voice), that has a capability to do IM, and 
>>> that has a preference for contacting a UAS that supports IM as well 
>>> as voice.
>>
>>
>> I would say ".... that has a preference for contacting the same 
>> service that the calling party is using". The reason is that future 
>> interactions may involve other capabilities that this service is able 
>> to offer.
> 
> 
> This emphasizes a key philosophical difference I think - one that goes 
> all the way back to the early discussions around rpids and the meaning 
> of "service" in presence. One approach is that a service is just a 
> collection of capabilities. (Your "IM Service Client" is just a 
> combination of an audio capability and an IM capability.) The other 
> approach is that a service has an arbitrary name, which implies some 
> combination of capabilities and ways to use those capabilities, but 
> doesn't explicitly state what the capabilities are. It is assumed that 
> if you support the service then you know what it implies.
> 
> Jonathan has attempted to thread the needle once again regarding that 
> difference. But it doesn't seem to be succeeding. He was trying to draw 
> the distinction between what the capabilities are, and how they are 
> used. (So that audio and IM used to support a chess game is different 
> from audio and IM used conversationally.)

Exactly. In my mind, the service ID is used when there is some context 
on the side of the originator that governs the interpretation of the 
signaling or media that MUST be shared by the remote side to sensibily 
make use of the session, which is not otherwise signaled by SIP since 
its not a PROTOCOL issue.

I give this example of chess, where a session set up from the chess app 
LOOKS IDENTICAL to a SIP request initiated by a regular telephony app. 
Its only when there is nothing in the protocol to differentiate, that it 
changes from a capability to a required service.

In essence, the option tag in Require has the effect of partitioning a 
SIP network into non-overlapping services, all of which share the 
infrastructure but otherwise can exist for various purposes. Like it or 
not (and I don't) it is my understanding that there is a strong desire 
from the community to have a technique to do exactly this; to allow 
their IMS to support several services which use IMS but which are 
otherwise quite separate and go with their own apps on the phone. PoC in 
particular makes use of some pretty unusual call flows that work ONLY 
under the assumption of mutual understanding that this is PoC; this 
would be a contender for a service URI because of that assumption.

Indeed, it was my understanding here that this was exactly what is 
desired for PoC. I make a call from my PoC client to a number. If the 
terminating user doesn't have POC, they better not accept that call or 
bad things are going to happen. That is Require in every sense of the 
mechanism.



>>
>> I still don't see how I can signal my preference for a service to be 
>> used.
> 
> 
> Lets go to Jonathan's example of the Chess service. If you were calling 
> from your chess program, I think you would have more than a "preference" 
> for a chess service at the other end. Conversely, if you are not calling 
> from your chess program, then you don't want a chess service at the 
> other end.

Right. I think if this is something in the category of a preference that 
can be signaled, then it is normally within the context of a single 
service and that preference would not be signaled using Require.

There is a use case where my phone has this voice-chess app and a normal 
telephony communications app. I 'call' you, indicating we can EITHER do 
voice-chess OR telephony. You pick which one, and both of our phones 
launch teh appropriate app based on this.

I personally think this is an unlikely use case; it could be supported 
by placing the set of services in Supported as you suggest, and the 
response including Require. Lack of a Require in the response means that 
no special service was selected; its just normal multimedia 
communications as SIP normally does.

A far better way to select amongst these services is presence. IMHo that 
is far more elegant and user firendly. I would select a user in my 
address book, and it would show (using presence), the services I can 
get. I would then choose and send an INVITE. I think the notion of 
callee choosing the service is misguided since it is the caller that has 
asked for communications, they are the ones who know WHY they have asked 
for it, and thus what the right service is for that communications. That 
is why presence is so powerful - it enables choice. Please look at the 
presence data model spec which tries to explain this more.


> 
> For services to be anything different from capabilities and preferences, 
>  I find it hard to see how they can be optional.
> 
>>> I don't see why the service identification mechanism has to solve 
>>> this problem too.
>>
>>
>> Because for a basic communication (say voice), any UI or application 
>> will work, but for more advanced features, if both UAs have the same 
>> service through an implementation, then that is the desired effect. 
>> think the service ID fits perfectly in here.
> 
> 
> Why isn't IM, and Video, also considered "basic communication"?
> 
> IMO basic communication is that we can establish a sip session and then 
> we use sip to negotiate the media that we will use in that session. We 
> both trust the other side to be able to utilize the media in some 
> appropriate way. That may be a human being communicating in an ad-hoc 
> manner.

Yes, exactly.

> 
> It may be an IVR that has a particular kind of communication it carries 
> out when called. As such, an IVR could conceivably be called a 
> "service". For instance an airline reservation service or a pharmacy 
> prescription ordering service. But hopefully they aren't services in the 
> sense discussed by this draft - the caller doesn't have to specify the 
> service in the request in order for it to be handled by the proper IVR.

No - an IVR isn't a different service. Here is my take on it. 'basic 
communication' as a service involves the establishment of multimedia 
communications for the purposes of human interaction; the origination 
and consumption of media is governed solely by what the calling or 
called user wishes to say as part of that communications. IVRs have a 
particular 'thing' they want to "say" - the IVR tree. The voice-chess is 
different because the media is not consumed by the called user based on 
what they'd want to say; its consumed by an auotomata that may or may 
not be there.

The distinction is fuzzy, but everything about this problem is splitting 
hairs.

> 
>>>> - I understand the motivation for overloading the Require header for 
>>>> transporting URNs, but I think it is an ugly solution, and the fact 
>>>> that the RFC says you can only insert standardized option tags is 
>>>> not enough to prevent people writing other non-standardize tags if 
>>>> they wish to violate the RFC.
>>>
>>>
>>> It doesn't prevent individuals, or developers of closed systems from 
>>> doing so. But it does make it difficult for other SDOs from doing so, 
>>> and developers of systems that interoperate with standards complying 
>>> components will at least get some pressure.
>>
>>
>> Agreed. My point is that you get the same effect by defining a new 
>> header and writing down the same constraints that Require has. IMHO 
>> this is not a justification for overloading the semantics of an 
>> existing header.
> 
> 
> I don't have a strong feeling on this point. I think jonathan's intent 
> in going this way was a belief that this isn't really overloading - that 
> the purpose really is the same - that chess is an option in the same way 
> that 100rel is an option.

Exactly. It is PRECISELY the semantics of require. What we want is a way 
to say, "hey, if you get this request, and you don't understand service 
foo, you rae NOT going to do the right thing in processing this, so you 
BETTER support it". Whats new is that the Require is pointing to 
application-layer context, not SIP protocol mechanisms.


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

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



From sipping-bounces@ietf.org Fri Jan 26 03:28:40 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HAMQW-00010N-Fy; Fri, 26 Jan 2007 03:27:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HAMQV-000108-3p
	for sipping@ietf.org; Fri, 26 Jan 2007 03:27:15 -0500
Received: from jes-fe2.zx.nl ([194.187.76.133])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAMQP-0007qG-PU
	for sipping@ietf.org; Fri, 26 Jan 2007 03:27:15 -0500
Received: from Inbox ([84.241.219.244])
	by jes-fe2.zx.nl (Sun Java System Messaging Server 6.2-7.05 (built Sep
	5 2006)) with ESMTP id <0JCG00C0ZVG2FG90@jes-fe2.zx.nl> for
	sipping@ietf.org; Fri, 26 Jan 2007 09:26:46 +0100 (CET)
Date: Fri, 26 Jan 2007 09:28:15 +0100
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
Subject: RE: what is a service, was: Re: [Sipping]
	Comments	to	draft-rosenberg-sipping-service-identification-00.txt
To: Jonathan Rosenberg <jdrosen@cisco.com>, Paul Kyzivat <pkyzivat@cisco.com>
Message-id: <0JCG00C10VGCFG90@jes-fe2.zx.nl>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
X-Priority: 3
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: Miguel Garcia <Miguel.An.Garcia@nokia.com>, Sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

There is a relationship between Require and routing, but it is indirect (vi=
a caller prefs). I think there are (at least) two separate issues: route a =
PoC INVITE (for example) to a device/application that supports it, and make=
 sure that a device which does not support it does not accept.

For non-global tel: URIs there is a context parameter that scopes the inter=
pretation. Couldn't a similar mechanism (i.e. URI parameter) be used to ach=
ieve this partitioning?

Regards,
Jeroen=20

-----Oorspronkelijk bericht -----
Van: "Jonathan Rosenberg" <jdrosen@cisco.com>
Aan: "Paul Kyzivat" <pkyzivat@cisco.com>
CC: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>; "Sipping" <sipping@ietf.o=
rg>
Verzonden: 26-1-07 02:44
Onderwerp: what is a service, was: Re: [Sipping] Comments	to	draft-rosenber=
g-sipping-service-identification-00.txt

Splitting this thread up a bit, since we are discussing two separate points=

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



From sipping-bounces@ietf.org Fri Jan 26 04:34:11 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HANRv-0005iK-Qi; Fri, 26 Jan 2007 04:32:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HANRu-0005iF-Kj
	for sipping@ietf.org; Fri, 26 Jan 2007 04:32:46 -0500
Received: from fr7.aha.ru ([62.113.100.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HANRt-0004kr-0R
	for sipping@ietf.org; Fri, 26 Jan 2007 04:32:46 -0500
Received: from aha.ru (backend3.aha.ru [195.2.83.133])
	by gnat.zenon.net (Postfix) with ESMTP id BDE519B9F
	for <sipping@ietf.org>; Fri, 26 Jan 2007 12:32:05 +0300 (MSK)
Received: from [83.242.132.250] (account postmaster@zniis.ru HELO
	83.242.132.250) by backend3.aha.ru (CommuniGate Pro SMTP 4.3.12)
	with ESMTPA id 652022790 for sipping@ietf.org;
	Fri, 26 Jan 2007 12:32:05 +0300
Received: from Konstantin (authenticated user savin@zniis.ru) by zniis.ru
	(MDaemon.PRO.v6.8.5.R) with ESMTP id 57-md50000000024.tmp
	for <sipping@ietf.org>; Fri, 26 Jan 2007 12:36:47 +0300
From: "Konstantin Savin" <savin@zniis.ru>
To: <sipping@ietf.org>
Date: Fri, 26 Jan 2007 12:32:01 +0300
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAALkBV+uSHRZCpm9w5jquwh3CgAAAEAAAAD6RNHR9hoRNrXgQnRcVpdEBAAAAAA==@zniis.ru>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcdBLNTgjoyrDS9gQOWxKRBO3cdJuQ==
X-Authenticated-Sender: savin@zniis.ru
X-Return-Path: savin@zniis.ru
X-MDaemon-Deliver-To: sipping@ietf.org
X-Spam-Status: No, hits=4.7 required=10.0
	tests=FORGED_MUA_OUTLOOK,HTML_70_80,HTML_MESSAGE,
	MISSING_OUTLOOK_NAME version=2.55
X-Spam-Level: ****
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Spam-Report: ---- Start SpamAssassin results 4.70 points, 10 required;
	Message preview:
	Hello everybody! There are two similar protocols (or versions of SIP)
	are used now : SIP-T and SIP-I. [...] Content analysis details:
	HTML_MESSAGE       (0.1 points)  BODY: HTML included in message
	HTML_70_80         (0.5 points)  BODY: Message is 70% to 80% HTML
	FORGED_MUA_OUTLOOK (3.5 points) Forged mail pretending to be from MS
	Outlook
	MISSING_OUTLOOK_NAME (0.6 points)  Message looks like Outlook, but isn't
	---- End SpamAssassin results
X-Spam-Processed: xchange.zniis, Fri, 26 Jan 2007 12:36:52 +0300
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Subject: [Sipping] Differences between SIP-T and SIP-I
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-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-Type: multipart/mixed; boundary="===============1653594158=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1653594158==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001E_01C74145.FA5DAB20"

This is a multi-part message in MIME format.

------=_NextPart_000_001E_01C74145.FA5DAB20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello everybody!

 

There are two similar protocols (or versions of SIP) are used now : SIP-T
and SIP-I.

But can anybody explain me the differences between them? Is the only point
in the owner (IETF, ITU-T).

 

Thank you very much and best regards,

Stan


------=_NextPart_000_001E_01C74145.FA5DAB20
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DRU link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Hello everybody!<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>There are two similar protocols (or versions =
of SIP)
are used now : SIP-T and SIP-I.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>But can anybody explain me the differences =
between
them? Is the only point in the owner (IETF, =
ITU-T).<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Thank you very much and best =
regards,<o:p></o:p></span></font></p>

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

</div>

</body>

</html>

------=_NextPart_000_001E_01C74145.FA5DAB20--



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

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





From sipping-bounces@ietf.org Fri Jan 26 07:41:37 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HAQO5-0006Pt-Ee; Fri, 26 Jan 2007 07:41:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HAQO3-0006Pn-Vg
	for sipping@ietf.org; Fri, 26 Jan 2007 07:40:59 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAQO2-00044o-He
	for sipping@ietf.org; Fri, 26 Jan 2007 07:40:59 -0500
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:52780)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HAQO1-0004iQ-Nd; Fri, 26 Jan 2007 12:40:57 +0000
In-Reply-To: <45B8E196.9020903@nortel.com>
References: <B87C644441A70D4A9D6691BF79C8FD650C4FFDCD@PLSWB06C.ad.sprint.com>
	<45B8E196.9020903@nortel.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <28FA367C-5498-4F5E-9FA3-00F9AC342481@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [Sipping] Offer Answer / SDP a=sdplang was [Sip-implementors]
	Accept-Language Header
Date: Fri, 26 Jan 2007 11:13:23 +0000
To: Tom-PT Taylor <taylor@nortel.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

RFC 4566 defines "a=sdplang:" for the language of the signalling  
content, and "a=lang:" to indicate the language of the media stream.

Colin




On 25 Jan 2007, at 16:57, Tom-PT Taylor wrote:
> These attributes concern themselves only with signalling content,  
> not the language of the media stream. For that I think you need to  
> use Caller Preferences.
>
> Manroa, Arun [CTO] wrote:
>> Hi,
>> I am trying to understand how to negotiate human language (audio  
>> output) preferences using SDP or SIP headers;
>> RFC 2327 defines a=sdplang at the media level and so does the  
>> HTTP /SIP specs at the signaling level (Accept-Language Header).  
>> RFC 3264 offer answer does not delve into this.
>> Consider the following use case, where User A is an "English"  
>> language speaker using say G711 codec and want to conference in  
>> only certain members of a group call that not only support the  
>> G711 codec, but also understand the "English" language.
>>  Assume following are the users characteristics:
>> User A (English), Codec G711
>> User B (English), Codec G711
>> User C (Spanish), Codec G711
>> User D (English), Codec AMR
>> User E (English, Spanish), Codec G711
>>  So in this use case User A wants to connect to User B & E only,  
>> since the language and codec both match.(English, G711)
>>  RFC 3261 20.3 Accept-Language says..
>>                 The Accept-Language header field is used in  
>> requests to indicate the
>>                    preferred languages for reason phrases, session  
>> descriptions, or
>>                    status responses carried as message bodies in  
>> the response.
>> The text says session descriptions but I not clear how that is  
>> handled in offer answer. Does the "Conferencing Server" send out  
>> INVITES with Accept-Language: en (with SDP Offer) to all  
>> participants and user C is going to send a 415 indicating Spanish  
>> only, and B & E are going to respond with a 200 OK (SDP Ans). Of  
>> course User D is going to reject the SDP Offer with a 415 since it  
>> does not support G711.
>>  Also the Accept-Language in REGISTER is used by the Registrar for  
>> generating a response, which I think is a different semantic  
>> meaning, maybe using RFC 3840 the users could register the  
>> appropriate language in the contact header, that way there is no  
>> need to send the INVITES to them etc.
>>  Could someone please clarify?
>>  Thanks,
>> Arun

-- 
Colin Perkins
http://csperkins.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 sipping-bounces@ietf.org Fri Jan 26 09:00:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HARbJ-0006BK-04; Fri, 26 Jan 2007 08:58:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HARbH-00068f-PS
	for sipping@ietf.org; Fri, 26 Jan 2007 08:58:43 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HARbG-0008UB-Gj
	for sipping@ietf.org; Fri, 26 Jan 2007 08:58:43 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 26 Jan 2007 05:58:42 -0800
X-IronPort-AV: i="4.13,243,1167638400"; 
	d="scan'208"; a="51665154:sNHT47458212"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l0QDwgCJ014874; 
	Fri, 26 Jan 2007 08:58:42 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l0QDwfOE011785; 
	Fri, 26 Jan 2007 08:58:42 -0500 (EST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Jan 2007 08:58:18 -0500
Received: from [161.44.183.166] ([161.44.183.166]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Jan 2007 08:58:18 -0500
Message-ID: <45BA08F9.8030108@cisco.com>
Date: Fri, 26 Jan 2007 08:58:17 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: what is a service, was: Re: [Sipping] Comments
	to	draft-rosenberg-sipping-service-identification-00.txt
References: <45B75AED.3060908@nokia.com> <45B76A8A.7050307@cisco.com>
	<45B7775C.80207@nokia.com> <45B78843.7030905@cisco.com>
	<45B95CF9.3020809@cisco.com>
In-Reply-To: <45B95CF9.3020809@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jan 2007 13:58:18.0221 (UTC)
	FILETIME=[081731D0:01C74152]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2093; t=1169819922;
	x=1170683922; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20what=20is=20a=20service,
	=20was=3A=20Re=3A=20[Sipping]
	=20Comments=20to=09draft-rosenberg-sipping-service-identification-00.txt
	|Sender:=20 |To:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>;
	bh=Xn9BwO9aoI01o/fbWOirQxHU7CRmU5OKNBnCYwoN5Uc=;
	b=JkKM4J6elXGV1s7K1va607kHCyZHc2XDnYhDtbKqbRSvwX80p57EPumrMqsII0CAZyKtA12k
	7Eswo9k62kfVVRQGXB7Mx3N39Z2IHtwR1BaB2VSRpvyGt1b9E3WzdYPv;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: Miguel Garcia <Miguel.An.Garcia@nokia.com>, Sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I pretty much agree with everything Jonathan says below. I'm snipping 
one point for further comment.

	Paul

Jonathan Rosenberg wrote:

>> IMO basic communication is that we can establish a sip session and 
>> then we use sip to negotiate the media that we will use in that 
>> session. We both trust the other side to be able to utilize the media 
>> in some appropriate way. That may be a human being communicating in an 
>> ad-hoc manner.
> 
> Yes, exactly.
> 
>> It may be an IVR that has a particular kind of communication it 
>> carries out when called. As such, an IVR could conceivably be called a 
>> "service". For instance an airline reservation service or a pharmacy 
>> prescription ordering service. But hopefully they aren't services in 
>> the sense discussed by this draft - the caller doesn't have to specify 
>> the service in the request in order for it to be handled by the proper 
>> IVR.
> 
> No - an IVR isn't a different service. Here is my take on it. 'basic 
> communication' as a service involves the establishment of multimedia 
> communications for the purposes of human interaction; the origination 
> and consumption of media is governed solely by what the calling or 
> called user wishes to say as part of that communications. IVRs have a 
> particular 'thing' they want to "say" - the IVR tree. The voice-chess is 
> different because the media is not consumed by the called user based on 
> what they'd want to say; its consumed by an auotomata that may or may 
> not be there.
> 
> The distinction is fuzzy, but everything about this problem is splitting 
> hairs.

Yes, it is fuzzy. Thinking about it further, I guess I agree with 
Jonathan on this point too. The key distinction here is that while the 
UAS may have a service-like context, the UAC doesn't have to be aware of 
it or have any special support for it. As a result, the context needed 
at the UAS should be determined by some other means, not a service 
identifier supplied by the caller. For instance, it is ofter determined 
by the request 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 sipping-bounces@ietf.org Fri Jan 26 11:45:59 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HAUBq-0002Vz-V3; Fri, 26 Jan 2007 11:44:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HAUBp-0002Vs-C7
	for sipping@ietf.org; Fri, 26 Jan 2007 11:44:37 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAUBm-0002Ex-Vr
	for sipping@ietf.org; Fri, 26 Jan 2007 11:44:37 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 26 Jan 2007 08:44:34 -0800
X-IronPort-AV: i="4.13,244,1167638400"; 
	d="scan'208,217"; a="51679599:sNHT89887716"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l0QGiYJ4015930; 
	Fri, 26 Jan 2007 11:44:34 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l0QGiYOA022041; 
	Fri, 26 Jan 2007 11:44:34 -0500 (EST)
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Jan 2007 11:44:34 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] Differences between SIP-T and SIP-I
Date: Fri, 26 Jan 2007 11:44:33 -0500
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E30284CBCC@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAALkBV+uSHRZCpm9w5jquwh3CgAAAEAAAAD6RNHR9hoRNrXgQnRcVpdEBAAAAAA==@zniis.ru>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Differences between SIP-T and SIP-I
Thread-Index: AcdBLNTgjoyrDS9gQOWxKRBO3cdJuQAPFnWg
References: <!&!AAAAAAAAAAAYAAAAAAAAALkBV+uSHRZCpm9w5jquwh3CgAAAEAAAAD6RNHR9hoRNrXgQnRcVpdEBAAAAAA==@zniis.ru>
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Konstantin Savin" <savin@zniis.ru>, <sipping@ietf.org>
X-OriginalArrivalTime: 26 Jan 2007 16:44:34.0054 (UTC)
	FILETIME=[42268260:01C74169]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4771; t=1169829874;
	x=1170693874; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mhammer@cisco.com;
	z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20Differences=20between=20SIP-T=20and=20SIP
	-I |Sender:=20
	|To:=20=22Konstantin=20Savin=22=20<savin@zniis.ru>,=20<sipping@ietf.org>;
	bh=uqtMqjIW+4rQ83JEyZkkYwpbjjbAP34JHC1fJbXHpiU=;
	b=j2TuCgJ7MQhZr35qpYkoqxvsEsiSl5CTVcm/VoXhc9SXA6vaklQYi+Idt/5XIgsukl4mMYXp
	5ZlBUXp9L6WAtJpdRVhiO7APCg3U3oiCgscpOwj8TNgFsXMkh4pIyzNU;
Authentication-Results: rtp-dkim-2; header.From=mhammer@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-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-Type: multipart/mixed; boundary="===============0382973111=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0382973111==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C74169.41E4A45E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C74169.41E4A45E
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Besides ownership, there are technical differences in the message
handling.
=20
Mike
=20


________________________________

	From: Konstantin Savin [mailto:savin@zniis.ru]=20
	Sent: Friday, January 26, 2007 4:32 AM
	To: sipping@ietf.org
	Subject: [Sipping] Differences between SIP-T and SIP-I
=09
=09

	Hello everybody!

	=20

	There are two similar protocols (or versions of SIP) are used
now : SIP-T and SIP-I.

	But can anybody explain me the differences between them? Is the
only point in the owner (IETF, ITU-T).

	=20

	Thank you very much and best regards,

	Stan


------_=_NextPart_001_01C74169.41E4A45E
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR>
<STYLE>@page Section1 {size: 595.3pt 841.9pt; margin: 2.0cm 42.5pt 2.0cm =
3.0cm; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DRU vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D463014416-26012007><FONT =
face=3DCourier=20
color=3D#0000ff>Besides ownership, there are technical differences in =
the message=20
handling.</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCourier color=3D#0000ff><SPAN=20
class=3D463014416-26012007>Mike</SPAN></FONT></DIV>
<DIV><FONT face=3DCourier color=3D#0000ff></FONT>&nbsp;</DIV>
<DIV><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Konstantin Savin =
[mailto:savin@zniis.ru]=20
  <BR><B>Sent:</B> Friday, January 26, 2007 4:32 AM<BR><B>To:</B>=20
  sipping@ietf.org<BR><B>Subject:</B> [Sipping] Differences between =
SIP-T and=20
  SIP-I<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hello=20
  everybody!<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">There are two similar =
protocols=20
  (or versions of SIP) are used now : SIP-T and=20
  SIP-I.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">But can anybody explain =
me the=20
  differences between them? Is the only point in the owner (IETF,=20
  ITU-T).<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thank you very much and =
best=20
  regards,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Stan</SPAN></FONT><SPAN=20
  lang=3DEN-US><o:p></o:p></SPAN></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C74169.41E4A45E--


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

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




From sipping-bounces@ietf.org Mon Jan 29 02:36:55 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBR28-0008GR-4R; Mon, 29 Jan 2007 02:34:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBR26-0008FV-L0
	for sipping@ietf.org; Mon, 29 Jan 2007 02:34:30 -0500
Received: from fr7.aha.ru ([62.113.100.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBR21-0000X1-O3
	for sipping@ietf.org; Mon, 29 Jan 2007 02:34:30 -0500
Received: from aha.ru (backend3.aha.ru [195.2.83.133])
	by gnat.zenon.net (Postfix) with ESMTP id 28761280A
	for <sipping@ietf.org>; Mon, 29 Jan 2007 10:33:58 +0300 (MSK)
Received: from [83.242.132.250] (account postmaster@zniis.ru HELO
	83.242.132.250) by backend3.aha.ru (CommuniGate Pro SMTP 4.3.12)
	with ESMTPA id 656495056 for sipping@ietf.org;
	Mon, 29 Jan 2007 10:33:57 +0300
Received: from Konstantin (authenticated user savin@zniis.ru) by zniis.ru
	(MDaemon.PRO.v6.8.5.R) with ESMTP id 42-md50000000042.tmp
	for <sipping@ietf.org>; Mon, 29 Jan 2007 10:38:41 +0300
From: "Konstantin Savin" <savin@zniis.ru>
To: "'Michael Hammer \(mhammer\)'" <mhammer@cisco.com>
Subject: RE: [Sipping] Differences between SIP-T and SIP-I
Date: Mon, 29 Jan 2007 10:33:54 +0300
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAALkBV+uSHRZCpm9w5jquwh3CgAAAEAAAAKMOzZNjTL5HnnFi1R8o47ABAAAAAA==@zniis.ru>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E30284CBCC@xmb-rtp-20b.amer.cisco.com>
Thread-Index: AcdBLNTgjoyrDS9gQOWxKRBO3cdJuQAPFnWgAINySGA=
X-Authenticated-Sender: savin@zniis.ru
X-Return-Path: savin@zniis.ru
X-MDaemon-Deliver-To: sipping@ietf.org
X-Spam-Status: No, hits=4.6 required=10.0
	tests=FORGED_MUA_OUTLOOK,HTML_70_80,HTML_FONT_COLOR_BLUE,
	HTML_FONT_FACE_ODD,HTML_MESSAGE,IN_REP_TO, MISSING_OUTLOOK_NAME
	version=2.55
X-Spam-Level: ****
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Spam-Report: ---- Start SpamAssassin results 4.60 points, 10 required;
	Message preview:
	Thank you Mike! I saw that there are some differences in message
	handling in part of converting the causes of ISUP to 4xx series
	responses. And may be some more detailed than in RFC 3372 or
	3398 description of several procedures. [...] 
	Content analysis details:
	IN_REP_TO          (-0.5 points) Has a In-Reply-To header
	HTML_FONT_FACE_ODD (0.3 points) BODY: HTML font face is not a commonly
	used face
	HTML_MESSAGE       (0.1 points)  BODY: HTML included in message
	HTML_FONT_COLOR_BLUE (0.1 points)  BODY: HTML font color is blue
	HTML_70_80         (0.5 points)  BODY: Message is 70% to 80% HTML
	FORGED_MUA_OUTLOOK (3.5 points) Forged mail pretending to be from MS
	Outlook
	MISSING_OUTLOOK_NAME (0.6 points)  Message looks like Outlook, but isn't
	---- End SpamAssassin results
X-Spam-Processed: xchange.zniis, Mon, 29 Jan 2007 10:38:44 +0300
X-Spam-Score: 1.6 (+)
X-Scan-Signature: f4e722e9456ead69ba4cdd21dd3d3600
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-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-Type: multipart/mixed; boundary="===============1283485940=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1283485940==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0009_01C74390.FA052020"

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01C74390.FA052020
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Thank you Mike!

=20

I saw that there are some differences in message handling in part of
converting the causes of ISUP to 4xx series responses. And may be some =
more
detailed than in RFC 3372 or 3398 description of several procedures.

=20

But I wonder if there any 'global' differences between them?

Why does ITU-T create this SIP-I? SIP-T is not enough?

=20

Best regards,

Stan

  _____ =20

From: Michael Hammer (mhammer) [mailto:mhammer@cisco.com]=20
Sent: Friday, January 26, 2007 7:45 PM
To: Konstantin Savin; sipping@ietf.org
Subject: RE: [Sipping] Differences between SIP-T and SIP-I

=20

Besides ownership, there are technical differences in the message =
handling.

=20

Mike

=20

=20


  _____ =20


From: Konstantin Savin [mailto:savin@zniis.ru]=20
Sent: Friday, January 26, 2007 4:32 AM
To: sipping@ietf.org
Subject: [Sipping] Differences between SIP-T and SIP-I

Hello everybody!

=20

There are two similar protocols (or versions of SIP) are used now : =
SIP-T
and SIP-I.

But can anybody explain me the differences between them? Is the only =
point
in the owner (IETF, ITU-T).

=20

Thank you very much and best regards,

Stan



__________ Hmtnpl`vh=7F NOD32 2009 (20070126) __________

]rn qnnayemhe opnbepemn @mrhbhpsqmni qhqrelni NOD32.
http://www.nod32.com


------=_NextPart_000_0009_01C74390.FA052020
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DRU link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Thank you =
Mike!<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>I saw that there =
are some
differences in message handling in part of converting the causes of ISUP =
to 4xx
series responses. And may be some more detailed than in RFC 3372 or 3398 =
description
of several procedures.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>But I wonder if =
there any
&#8216;global&#8217; differences between =
them?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Why does ITU-T =
create
this SIP-I? SIP-T is not enough?<o:p></o:p></span></font></p>

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

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

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

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Hammer
(mhammer) [mailto:mhammer@cisco.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, January 26, =
2007
7:45 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Konstantin Savin; =
<st1:PersonName
w:st=3D"on">sipping@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Sipping] =
Differences
between SIP-T and SIP-I</span></font><o:p></o:p></p>

</div>

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

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3DCourier><span =
style=3D'font-size:
12.0pt;font-family:Courier;color:blue'>Besides ownership, there are =
technical
differences in the message handling.</span></font><o:p></o:p></p>

<div>

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

</div>

<div>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3DCourier><span =
style=3D'font-size:
12.0pt;font-family:Courier;color:blue'>Mike</span></font><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

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

</div>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0cm 0cm 0cm 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'=
>

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

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

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

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma'>
Konstantin Savin [mailto:savin@zniis.ru] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, January 26, =
2007
4:32 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">sipping@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Sipping] =
Differences
between SIP-T and SIP-I</span></font><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Hello everybody!<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>There are two similar protocols (or versions =
of SIP)
are used now : SIP-T and SIP-I.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>But can anybody explain me the differences =
between
them? Is the only point in the owner (IETF, =
ITU-T).<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Thank you very much and best =
regards,<o:p></o:p></span></font></p>

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

</blockquote>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
<br>
__________ Hmtnpl`vh=7F NOD32 2009 (20070126) __________<br>
<br>
]rn qnnayemhe opnbepemn @mrhbhpsqmni qhqrelni NOD32.<br>
<a =
href=3D"http://www.nod32.com">http://www.nod32.com</a><o:p></o:p></span><=
/font></p>

</div>

</body>

</html>

------=_NextPart_000_0009_01C74390.FA052020--



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

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





From sipping-bounces@ietf.org Mon Jan 29 04:17:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBSc9-00071H-Mr; Mon, 29 Jan 2007 04:15:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBSc8-000712-NZ
	for sipping@ietf.org; Mon, 29 Jan 2007 04:15:48 -0500
Received: from bzq-25-94-44.static.bezeqint.net ([212.25.94.44]
	helo=isr-jlm-mail.Kayote.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBSc4-0005GP-Il
	for sipping@ietf.org; Mon, 29 Jan 2007 04:15:48 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] Differences between SIP-T and SIP-I
Date: Mon, 29 Jan 2007 11:15:26 +0200
Message-ID: <1DDB0D3CC4E7F14FAE946361C0A606550201FB0A@isr-jlm-mail.Kayote.com>
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAALkBV+uSHRZCpm9w5jquwh3CgAAAEAAAAKMOzZNjTL5HnnFi1R8o47ABAAAAAA==@zniis.ru>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Differences between SIP-T and SIP-I
thread-index: AcdBLNTgjoyrDS9gQOWxKRBO3cdJuQAPFnWgAINySGAAA0HWIA==
References: <072C5B76F7CEAB488172C6F64B30B5E30284CBCC@xmb-rtp-20b.amer.cisco.com>
	<!&!AAAAAAAAAAAYAAAAAAAAALkBV+uSHRZCpm9w5jquwh3CgAAAEAAAAKMOzZNjTL5HnnFi1R8o47ABAAAAAA==@zniis.ru>
From: "David Schwartz" <David.Schwartz@Kayote.com>
To: "Konstantin Savin" <savin@zniis.ru>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 94902b99ee6852833c9a2b680a1de4d3
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-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-Type: multipart/mixed; boundary="===============1407999319=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1407999319==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C74386.03D82635"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C74386.03D82635
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

My limited understanding of the "global" differences between the two is
that SIP-T is used more in an environment where SIP is used for transit
between two SS7 networks. In this case the transit SIP network does not
really care about the cause of a problem and just sends this info back
to the originating SS7 network. As such all that is really needed is to
pass the ISUP message in a SIP message body to the terminating SS7
network.=20

=20

SIP-I on the other hand is used when ISUP messages are used by the SIP
network itself.

=20

Cheers,

=20

David

________________________________

From: Konstantin Savin [mailto:savin@zniis.ru]=20
Sent: Monday, January 29, 2007 9:34 AM
To: 'Michael Hammer (mhammer)'
Cc: sipping@ietf.org
Subject: RE: [Sipping] Differences between SIP-T and SIP-I

=20

Thank you Mike!

=20

I saw that there are some differences in message handling in part of
converting the causes of ISUP to 4xx series responses. And may be some
more detailed than in RFC 3372 or 3398 description of several
procedures.

=20

But I wonder if there any 'global' differences between them?

Why does ITU-T create this SIP-I? SIP-T is not enough?

=20

Best regards,

Stan

________________________________

From: Michael Hammer (mhammer) [mailto:mhammer@cisco.com]=20
Sent: Friday, January 26, 2007 7:45 PM
To: Konstantin Savin; sipping@ietf.org
Subject: RE: [Sipping] Differences between SIP-T and SIP-I

=20

Besides ownership, there are technical differences in the message
handling.

=20

Mike

=20

=20

=09
________________________________


	From: Konstantin Savin [mailto:savin@zniis.ru]=20
	Sent: Friday, January 26, 2007 4:32 AM
	To: sipping@ietf.org
	Subject: [Sipping] Differences between SIP-T and SIP-I

	Hello everybody!

	=20

	There are two similar protocols (or versions of SIP) are used
now : SIP-T and SIP-I.

	But can anybody explain me the differences between them? Is the
only point in the owner (IETF, ITU-T).

	=20

	Thank you very much and best regards,

	Stan



__________ Hmtnpl`vh=7F NOD32 2009 (20070126) __________

]rn qnnayemhe opnbepemn @mrhbhpsqmni qhqrelni NOD32.
http://www.nod32.com


------_=_NextPart_001_01C74386.03D82635
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>My limited understanding of the =
&#8220;global&#8221;
differences between the two is that SIP-T is used more in an environment =
where
SIP is used for transit between two SS7 networks. In this case the =
transit SIP
network does not really care about the cause of a problem and just sends =
this
info back to the originating SS7 network. As such all that is really =
needed is
to pass the ISUP message in a SIP message body to the terminating SS7 =
network. <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>SIP-I on the other hand is used =
when ISUP messages
are used by the SIP network itself.<o:p></o:p></span></font></p>

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

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


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

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

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Konstantin Savin
[mailto:savin@zniis.ru] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, January 29, =
2007
9:34 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Michael Hammer =
(mhammer)'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> sipping@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Sipping] =
Differences
between SIP-T and SIP-I</span></font><o:p></o:p></p>

</div>

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

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

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I saw that there are some =
differences in
message handling in part of converting the causes of ISUP to 4xx series
responses. And may be some more detailed than in RFC 3372 or 3398 =
description
of several procedures.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>But I wonder if there any
&#8216;global&#8217; differences between =
them?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Why does ITU-T create this SIP-I? =
SIP-T is
not enough?<o:p></o:p></span></font></p>

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

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

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

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span lang=3DRU =
style=3D'font-size:
10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=3D2 face=3DTahoma><span lang=3DRU =
style=3D'font-size:10.0pt;font-family:Tahoma'>
Michael Hammer (mhammer) [mailto:mhammer@cisco.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, January 26, =
2007
7:45 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Konstantin Savin; =
<st1:PersonName
w:st=3D"on">sipping@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Sipping] =
Differences
between SIP-T and SIP-I</span></font><span =
lang=3DRU><o:p></o:p></span></p>

</div>

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

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3DCourier><span =
lang=3DRU
style=3D'font-size:12.0pt;font-family:Courier;color:blue'>Besides =
ownership,
there are technical differences in the message =
handling.</span></font><span
lang=3DRU><o:p></o:p></span></p>

<div>

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

</div>

<div>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3DCourier><span =
lang=3DRU
style=3D'font-size:12.0pt;font-family:Courier;color:blue'>Mike</span></fo=
nt><span
lang=3DRU><o:p></o:p></span></p>

</div>

<div>

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

</div>

<div>

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

</div>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0cm 0cm 0cm 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'=
>

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

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

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

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
Konstantin Savin [mailto:savin@zniis.ru] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, January 26, =
2007
4:32 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">sipping@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Sipping] =
Differences
between SIP-T and SIP-I</span></font><o:p></o:p></p>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>There are two similar protocols (or versions of SIP) =
are
used now : SIP-T and SIP-I.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>But can anybody explain me the differences between =
them? Is
the only point in the owner (IETF, ITU-T).<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thank you very much and best =
regards,<o:p></o:p></span></font></p>

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

</blockquote>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DRU
style=3D'font-size:12.0pt'><br>
<br>
__________ Hmtnpl`vh=7F NOD32 2009 (20070126) __________<br>
<br>
]rn qnnayemhe opnbepemn @mrhbhpsqmni qhqrelni NOD32.<br>
<a =
href=3D"http://www.nod32.com">http://www.nod32.com</a><o:p></o:p></span><=
/font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C74386.03D82635--


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

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




From sipping-bounces@ietf.org Mon Jan 29 05:25:39 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBTh4-0000ig-P8; Mon, 29 Jan 2007 05:24:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBTh3-0000iJ-1a
	for sipping@ietf.org; Mon, 29 Jan 2007 05:24:57 -0500
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBTh1-0007cL-7C
	for sipping@ietf.org; Mon, 29 Jan 2007 05:24:57 -0500
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JCM005T6KTTQG@szxga04-in.huawei.com> for
	sipping@ietf.org; Mon, 29 Jan 2007 18:22:41 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JCM00AJ0KTSV1@szxga04-in.huawei.com> for
	sipping@ietf.org; Mon, 29 Jan 2007 18:22:40 +0800 (CST)
Received: from h58820 ([10.85.205.0])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JCM005XWKTPGV@szxml03-in.huawei.com> for
	sipping@ietf.org; Mon, 29 Jan 2007 18:22:40 +0800 (CST)
Date: Mon, 29 Jan 2007 18:22:37 +0800
From: "He, Jingtong" <hejingtong@huawei.com>
Subject: RE: [Sipping] Differences between SIP-T and SIP-I
In-reply-to: <!&!AAAAAAAAAAAYAAAAAAAAALkBV+uSHRZCpm9w5jquwh3CgAAAEAAAAKMOzZNjTL5HnnFi1R8o47ABAAAAAA==@zniis.ru>
To: 'Konstantin Savin' <savin@zniis.ru>,
	"'Michael Hammer (mhammer)'" <mhammer@cisco.com>
Message-id: <001201c7438f$66035ff0$00cd550a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: quoted-printable
Thread-index: AcdBLNTgjoyrDS9gQOWxKRBO3cdJuQAPFnWgAINySGAABdfs0A==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

To my knowledge=EF=BC=9A
SIP-T (by IETF) just provides translation and encapsulation for PSTN =
parameters in interconnection with SIP soft switch. SIP-I (by ITU-T, =
based on SIP-T) is more accurate and explicitly defines the parameters =
between PSTN and SIP, also detailedly defines the supplementary services =
for telecommunication interconnection, which is not support by SIP-T. =
SIP-I is widely accepted by manufacturers, carriers and organizations =
(e.g., 3GPP) instead of SIP-T.

--
Regards,
Jingtong=20
________________________________________
From: Konstantin Savin [mailto:savin@zniis.ru]=20
Sent: Monday, January 29, 2007 3:34 PM
To: 'Michael Hammer (mhammer)'
Cc: sipping@ietf.org
Subject: RE: [Sipping] Differences between SIP-T and SIP-I

Thank you Mike!

I saw that there are some differences in message handling in part of =
converting the causes of ISUP to 4xx series responses. And may be some =
more detailed than in RFC 3372 or 3398 description of several =
procedures.

But I wonder if there any =E2=80=98global=E2=80=99 differences between =
them?
Why does ITU-T create this SIP-I? SIP-T is not enough?

Best regards,
Stan
________________________________________
From: Michael Hammer (mhammer) [mailto:mhammer@cisco.com]=20
Sent: Friday, January 26, 2007 7:45 PM
To: Konstantin Savin; sipping@ietf.org
Subject: RE: [Sipping] Differences between SIP-T and SIP-I

Besides ownership, there are technical differences in the message =
handling.
=20
Mike
=20

________________________________________
From: Konstantin Savin [mailto:savin@zniis.ru]=20
Sent: Friday, January 26, 2007 4:32 AM
To: sipping@ietf.org
Subject: [Sipping] Differences between SIP-T and SIP-I
Hello everybody!

There are two similar protocols (or versions of SIP) are used now : =
SIP-T and SIP-I.
But can anybody explain me the differences between them? Is the only =
point in the owner (IETF, ITU-T).

Thank you very much and best regards,
Stan


__________ Hmtnpl`vh=7F NOD32 2009 (20070126) __________

]rn qnnayemhe opnbepemn @mrhbhpsqmni qhqrelni NOD32.
http://www.nod32.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 sipping-bounces@ietf.org Mon Jan 29 16:25:40 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBdzH-00049B-Oa; Mon, 29 Jan 2007 16:24:27 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBdzG-00048S-Gu
	for sipping@ietf.org; Mon, 29 Jan 2007 16:24:26 -0500
Received: from rwcrmhc13.comcast.net ([204.127.192.83])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HBdzB-0000eI-Ak
	for sipping@ietf.org; Mon, 29 Jan 2007 16:24:26 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc13) with ESMTP
	id <20070129212419m1300pfk97e>; Mon, 29 Jan 2007 21:24:19 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l0TLOI98015866
	for <sipping@ietf.org>; Mon, 29 Jan 2007 16:24:18 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l0TLOIII015862;
	Mon, 29 Jan 2007 16:24:18 -0500
Date: Mon, 29 Jan 2007 16:24:18 -0500
Message-Id: <200701292124.l0TLOIII015862@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <45BA08F9.8030108@cisco.com> (pkyzivat@cisco.com)
References: <45B75AED.3060908@nokia.com> <45B76A8A.7050307@cisco.com>
	<45B7775C.80207@nokia.com> <45B78843.7030905@cisco.com>
	<45B95CF9.3020809@cisco.com> <45BA08F9.8030108@cisco.com>
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: [Sipping] draft-rosenberg-sipping-service-identification-00
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I'm a little mystified at what problem this architecture is supposed
to solve.  I know that it is to form a sort of "sub-addressing" within
the target's AOR, but I don't see the particular use of that, since a
user can easily mint a new AOR for every application he wishes to
maintain.  (By hypothesis, these applications are intended to be
long-lived and publically available (for some public, perhaps small).)
If someone wants to connect to my chess application, he is presumably
a chess fanatic that I know, and I can give him the appropriate AOR by
various means.

Where the idea becomes truly useful is if a service designation can be
thought of as being a potential modifier for *every* AOR in a large
set.  This is implied in the requirements:

   REQ 5: It must be possible for a user to initiate a session without
      knowledge of any information about the recipient except for their
      AOR.

   REQ 6: The mechanism must allow a presence server to determine the
      services on the phone, without requiring [advance] knowledge of
      those services.

Sort of like being able to tag a company's phone number with "fax" and
automagically getting routed to their fax number.

But I see that the number of those is going to be small.  Even now,
there are only 4 contact info items for an organization:  main phone
#, fax phone #, web URL, and postal address.

Where this becomes interesting is if there are many, large,
overlapping communities within which there are a significant number of
applications that a majority of members implement.  But I can't
imagine how that would come about.

Dale


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



From sipping-bounces@ietf.org Tue Jan 30 01:57:17 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBmuX-00008e-Me; Tue, 30 Jan 2007 01:56:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBmuV-00008V-Ui
	for sipping@ietf.org; Tue, 30 Jan 2007 01:56:07 -0500
Received: from wip-ec-wd.wipro.com ([203.91.193.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBmuU-0000tH-5U
	for sipping@ietf.org; Tue, 30 Jan 2007 01:56:07 -0500
Received: from wip-ec-wd.wipro.com (localhost.wipro.com [127.0.0.1])
	by localhost (Postfix) with ESMTP id 3FBE4205DB
	for <sipping@ietf.org>; Tue, 30 Jan 2007 12:18:32 +0530 (IST)
Received: from blr-ec-bh01.wipro.com (blr-ec-bh01.wipro.com [10.201.50.91])
	by wip-ec-wd.wipro.com (Postfix) with ESMTP id 13ED8205D9
	for <sipping@ietf.org>; Tue, 30 Jan 2007 12:18:31 +0530 (IST)
Received: from blr-m2-msg.wipro.com ([10.116.50.99]) by blr-ec-bh01.wipro.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Jan 2007 12:25:59 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] draft-rosenberg-sipping-service-identification-00
Date: Tue, 30 Jan 2007 12:30:45 +0530
Message-ID: <532B18E13CF9E64380EF5FDDE265E071B2631D@blr-m2-msg.wipro.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] draft-rosenberg-sipping-service-identification-00
Thread-Index: AcdD7CgOVZHQOjlkREmckmDWDHmhEQATyQew
References: <45B75AED.3060908@nokia.com>
	<45B76A8A.7050307@cisco.com><45B7775C.80207@nokia.com>
	<45B78843.7030905@cisco.com><45B95CF9.3020809@cisco.com>
	<45BA08F9.8030108@cisco.com>
	<200701292124.l0TLOIII015862@dragon.ariadne.com>
From: <ravishankar.shiroor@wipro.com>
To: <Dale.Worley@comcast.net>,
	<sipping@ietf.org>
X-OriginalArrivalTime: 30 Jan 2007 06:55:59.0809 (UTC)
	FILETIME=[B2DF5B10:01C7443B]
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Comments inline.

Regards,
Ravi.

--
=20
Ravishankar. G. Shiroor
Wipro Technologies, Bangalore.
=20
ravishankar.shiroor@wipro.com
--
=20

> -----Original Message-----
> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]=20
> Sent: Tuesday, January 30, 2007 2:54 AM
> To: sipping@ietf.org
> Subject: [Sipping] draft-rosenberg-sipping-service-identification-00
>=20
> I'm a little mystified at what problem this architecture is=20
> supposed to solve.  I know that it is to form a sort of=20
> "sub-addressing" within the target's AOR, but I don't see the=20
> particular use of that, since a user can easily mint a new=20
> AOR for every application he wishes to maintain.  (By=20
> hypothesis, these applications are intended to be long-lived=20
> and publically available (for some public, perhaps small).)=20
> If someone wants to connect to my chess application, he is=20
> presumably a chess fanatic that I know, and I can give him=20
> the appropriate AOR by various means.
>=20
> Where the idea becomes truly useful is if a service=20
> designation can be thought of as being a potential modifier=20
> for *every* AOR in a large set.  This is implied in the requirements:
>=20
>    REQ 5: It must be possible for a user to initiate a session without
>       knowledge of any information about the recipient except=20
> for their
>       AOR.
>=20
>    REQ 6: The mechanism must allow a presence server to determine the
>       services on the phone, without requiring [advance] knowledge of
>       those services.
>=20
> Sort of like being able to tag a company's phone number with=20
> "fax" and automagically getting routed to their fax number.
>=20
> But I see that the number of those is going to be small. =20
> Even now, there are only 4 contact info items for an=20
> organization:  main phone #, fax phone #, web URL, and postal address.
>=20
> Where this becomes interesting is if there are many, large,=20
> overlapping communities within which there are a significant=20
> number of applications that a majority of members implement. =20
> But I can't imagine how that would come about.

NGN standards like IMS promise roll-out of services at a higher speed
than it is possible today.
Given that, it would be possible to have large number of applications
and services used by large number of users.

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

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



From sipping-bounces@ietf.org Tue Jan 30 15:17:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBzNl-0003Ad-30; Tue, 30 Jan 2007 15:15:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBzNj-0003AW-IQ
	for sipping@ietf.org; Tue, 30 Jan 2007 15:15:07 -0500
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBzNi-0001RQ-5E
	for sipping@ietf.org; Tue, 30 Jan 2007 15:15:07 -0500
Received: from kyzyl.cablelabs.com (kyzyl.cablelabs.com [10.253.0.7])
	by ondar.cablelabs.com (8.13.8/8.13.8) with ESMTP id l0UKF5Zg023542
	for <sipping@ietf.org>; Tue, 30 Jan 2007 13:15:05 -0700 (MST)
Received: from srvxchg.cablelabs.com (10.5.0.20)
	by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com);
	Tue, 30 Jan 2007 13:15:04 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com)
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"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] draft-ietf-sipping-config-framework-10
Date: Tue, 30 Jan 2007 13:15:04 -0700
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D84804021B5C28@srvxchg.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] draft-ietf-sipping-config-framework-10
Thread-Index: Acc+jP0z18+zPEMZQoS7fWkb0LxC1gBa1zGAASyJW+A=
From: "Sumanth Channabasappa" <sumanth@cablelabs.com>
To: "sipping" <sipping@ietf.org>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Folks,

As indicated earlier, -v10 was a draft update and we have received
limited comments thus far (thanks to those who provided comments). If
there are additional comments that participants want to share, it would
be beneficial to receive them by Feb 5, 2007 to address them in a timely
manner. If you have not reviewed -v10 as yet, this email is a request to
please do so (as a note, please check the open items for things not
completely addressed in this rev).

If you wish to participate in offline discussions, please send and email
to the co-chairs, the author or myself.

Thanks!
- S



-----Original Message-----
From: Sumanth Channabasappa=20
Sent: Wednesday, January 24, 2007 1:55 PM
To: sipping
Subject: [Sipping] draft-ietf-sipping-config-framework-10

Folks,

Now that v10 is available online
(http://www.ietf.org/internet-drafts/draft-ietf-sipping-config-framework
-10.txt), here is a brief summary of the changes in this version
(reproduced in part from section 12.1).

   Changes incorporated by the author:
   o  Incorporated numerous edits and corrections from CableLabs review
   o  Used better ascii art picture of overview from Josh Littlefield
   o  Fixed the normative text for network-user so that it is now
      consistant: MAY provide for device profile, MUST provide for
      local-network profile

   Changes incorporated by the editor:
   o  Restructured document based on a) Keith's recommendations in
      the email dated 11/09/2006 and responses (Peter, Sumanth, Josh) b)
      subsequent discussions by the ad-hoc group consisting of the
      editor, the author, expert contributors (Peter Blatherwick, Josh
      Littlefield, Alvin Jiang, Jason Fischl, Martin Dolly, Cullen
      Jennings) and the co-chairs=20
   o  Modified the contents of various sections as part of the
restructuring=20
      efforts (notably: Overview, Introduction, Framework Requirements &

      Security)
   o  Revised Use cases and added detailed examples

This (-v10) is preliminary update and we plan to address the open items
(listed in section 11; for example, the security section could use
expert reviews) in the upcoming weeks. This is being presented to obtain
feedback from the WG. Additionally, if folks wish to participate in
offline discussions or sign up as expert reviewers please let myself,
the author or the co-chairs know.=20

Comments and feedback will be appreciated (thanks to Cullen and Henning
for early feedback on the mailing list).

Thanks!

- S




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org Tue Jan 30 20:26:43 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HC4Cx-0006BZ-Io; Tue, 30 Jan 2007 20:24:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HC4Cw-0006BU-Md
	for sipping@ietf.org; Tue, 30 Jan 2007 20:24:18 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HC4Cu-0007DN-Ab
	for sipping@ietf.org; Tue, 30 Jan 2007 20:24:18 -0500
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-4.cisco.com with ESMTP; 30 Jan 2007 17:24:15 -0800
X-IronPort-AV: i="4.13,259,1167638400"; 
	d="scan'208"; a="36184866:sNHT50441121"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l0V1OFe5017217; 
	Tue, 30 Jan 2007 17:24:15 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l0V1O4ho014272;
	Tue, 30 Jan 2007 17:24:04 -0800 (PST)
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Jan 2007 20:24:04 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Subject: RE: [Sipping] Differences between SIP-T and SIP-I
Date: Tue, 30 Jan 2007 20:24:03 -0500
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E3028A2DB5@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <001201c7438f$66035ff0$00cd550a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Differences between SIP-T and SIP-I
Thread-Index: AcdBLNTgjoyrDS9gQOWxKRBO3cdJuQAPFnWgAINySGAABdfs0ABSAEoQ
References: <!&!AAAAAAAAAAAYAAAAAAAAALkBV+uSHRZCpm9w5jquwh3CgAAAEAAAAKMOzZNjTL5HnnFi1R8o47ABAAAAAA==@zniis.ru>
	<001201c7438f$66035ff0$00cd550a@china.huawei.com>
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "He, Jingtong" <hejingtong@huawei.com>, "Konstantin Savin" <savin@zniis.ru>
X-OriginalArrivalTime: 31 Jan 2007 01:24:04.0130 (UTC)
	FILETIME=[7E9DA820:01C744D6]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2687; t=1170206655;
	x=1171070655; c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mhammer@cisco.com;
	z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20Differences=20between=20SIP-T=20and=20SIP
	-I |Sender:=20;
	bh=g8YP3oxlwwGvqWc87lYXB+CERUyywNb0m4ridvNUxRw=;
	b=Mhoo2xRvzw9zmms88h+ZGYTfqCP8SHXJO9x+TcyLtr24Lg3pa2IRHajxmIKR2d0PRytoQqSn
	Nt/1NU4lK9ALKjQ1Jp3VTYtrot8+9lSB+IOvFVsH/guq59iJcEeKwH2M;
Authentication-Results: sj-dkim-6; header.From=mhammer@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim6002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

ITU-T SG11 wished to verify that the interworking did not impact the PSTN networks, while still staying true to the intended operation of the SIP network.

Mike
 

> -----Original Message-----
> From: He, Jingtong [mailto:hejingtong@huawei.com] 
> Sent: Monday, January 29, 2007 5:23 AM
> To: 'Konstantin Savin'; Michael Hammer (mhammer)
> Cc: sipping@ietf.org; Rocky Wang
> Subject: RE: [Sipping] Differences between SIP-T and SIP-I
> 
> To my knowledge$B!'(J
> SIP-T (by IETF) just provides translation and encapsulation 
> for PSTN parameters in interconnection with SIP soft switch. 
> SIP-I (by ITU-T, based on SIP-T) is more accurate and 
> explicitly defines the parameters between PSTN and SIP, also 
> detailedly defines the supplementary services for 
> telecommunication interconnection, which is not support by 
> SIP-T. SIP-I is widely accepted by manufacturers, carriers 
> and organizations (e.g., 3GPP) instead of SIP-T.
> 
> --
> Regards,
> Jingtong
> ________________________________________
> From: Konstantin Savin [mailto:savin@zniis.ru]
> Sent: Monday, January 29, 2007 3:34 PM
> To: 'Michael Hammer (mhammer)'
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] Differences between SIP-T and SIP-I
> 
> Thank you Mike!
> 
> I saw that there are some differences in message handling in 
> part of converting the causes of ISUP to 4xx series 
> responses. And may be some more detailed than in RFC 3372 or 
> 3398 description of several procedures.
> 
> But I wonder if there any $B!F(Jglobal$B!G(J differences between them?
> Why does ITU-T create this SIP-I? SIP-T is not enough?
> 
> Best regards,
> Stan
> ________________________________________
> From: Michael Hammer (mhammer) [mailto:mhammer@cisco.com]
> Sent: Friday, January 26, 2007 7:45 PM
> To: Konstantin Savin; sipping@ietf.org
> Subject: RE: [Sipping] Differences between SIP-T and SIP-I
> 
> Besides ownership, there are technical differences in the 
> message handling.
>  
> Mike
>  
> 
> ________________________________________
> From: Konstantin Savin [mailto:savin@zniis.ru]
> Sent: Friday, January 26, 2007 4:32 AM
> To: sipping@ietf.org
> Subject: [Sipping] Differences between SIP-T and SIP-I Hello 
> everybody!
> 
> There are two similar protocols (or versions of SIP) are used 
> now : SIP-T and SIP-I.
> But can anybody explain me the differences between them? Is 
> the only point in the owner (IETF, ITU-T).
> 
> Thank you very much and best regards,
> Stan
> 
> 
> __________ Hmtnpl`vh NOD32 2009 (20070126) __________
> 
> ]rn qnnayemhe opnbepemn @mrhbhpsqmni qhqrelni NOD32.
> http://www.nod32.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 sipping-bounces@ietf.org Wed Jan 31 10:03:05 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCGy3-0004z5-Lc; Wed, 31 Jan 2007 10:01:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCGy2-0004yw-2j
	for sipping@ietf.org; Wed, 31 Jan 2007 10:01:46 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCGxr-0000wN-EZ
	for sipping@ietf.org; Wed, 31 Jan 2007 10:01:46 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	98D7F2133E; Wed, 31 Jan 2007 16:00:04 +0100 (CET)
X-AuditID: c1b4fb3e-b16d6bb0000007e1-fc-45c0aef41c75 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	8837521337; Wed, 31 Jan 2007 16:00:04 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Jan 2007 16:00:04 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Jan 2007 16:00:03 +0100
Received: from [131.160.36.100] (EH3I2003TGFCPET-131160036100.lmf.ericsson.se
	[131.160.36.100])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 0DFFC2656;
	Wed, 31 Jan 2007 17:00:04 +0200 (EET)
Message-ID: <45C0AEF2.8010101@ericsson.com>
Date: Wed, 31 Jan 2007 17:00:02 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Jan 2007 15:00:04.0045 (UTC)
	FILETIME=[7CFFCFD0:01C74548]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: Mary Barnes <mary.barnes@nortel.com>
Subject: [Sipping] Service Identification in SIP
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Folks,

during the last year, there have been a number of threads on the mailing
list discussing service identification in SIP. In particular, the
following thread discussed 3GPP requirements on this area:

http://www1.ietf.org/mail-archive/web/sipping/current/msg10562.html

At a later point, those 3GPP requirements were documented in the
following (expired by now) Internet Draft, which was presented in a
face-to-face IETF meeting.

http://www.watersprings.org/pub/id/draft-loreto-sipping-3gpp-ics-requirements-00.txt

Lately, the following draft has been submitted to the archives:

http://www.ietf.org/internet-drafts/draft-rosenberg-sipping-service-identification-00.txt

This draft proposes a solution that intends to meet known requirements
in this area.

Given the amount of discussions on issues related to service
identification we have seen during the last year, we believe this is a
fairly important topic for the SIPPING WG to tackle. At some point, we
would like to have a milestone with its associated WG item dealing with
this issue.

Therefore, we would like to encourage people to read this draft and send
comments to the list. Additionally, if you believe that this work is (or
is not) important, we would like to hear that as well.

Cheers,

Gonzalo
SIPPING co-chair


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



