Re: [Sip] questions about drat-bjorkner-serviceroute-00

Timothy SOETENS <timothy.soetens@alcatel.be> Thu, 13 September 2001 10:15 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00043 for <sip-archive@odin.ietf.org>; Thu, 13 Sep 2001 06:15:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA04115; Thu, 13 Sep 2001 05:53:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA04087 for <sip@optimus.ietf.org>; Thu, 13 Sep 2001 05:53:03 -0400 (EDT)
Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29872 for <sip@ietf.org>; Thu, 13 Sep 2001 05:52:54 -0400 (EDT)
Received: from bemail01.net.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with SMTP id f8D9prS24989; Thu, 13 Sep 2001 11:51:53 +0200 (MET DST)
Received: from alcatel.be ([138.203.67.193]) by bemail01.net.alcatel.be (Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) with SMTP id C1256AC6.00362C7B; Thu, 13 Sep 2001 11:51:43 +0200
Message-ID: <3BA081AE.5E87A59F@alcatel.be>
Date: Thu, 13 Sep 2001 11:51:42 +0200
From: Timothy SOETENS <timothy.soetens@alcatel.be>
Organization: Alcatel
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Henrik Gustafsson <henrik.gustafsson@hotsip.com>
CC: sip mailing list <sip@ietf.org>
Subject: Re: [Sip] questions about drat-bjorkner-serviceroute-00
References: <3BA06D0B.E16E78D9@alcatel.be> <3BA07CED.5000401@hotsip.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>
X-BeenThere: sip@ietf.org
Content-Transfer-Encoding: 7bit


Henrik Gustafsson wrote:
> 
> The service route is actually a loose route and the chain of service
> routes could
> be considered as a chain of outbound proxies. We didn't like initial
> routing
> and filtering services to be visited for a all following request, that
> is the reason
> we stated a service-route SHOULD only be inserted in a initial request.
> If a
> service needs to keep the call state, you should add a record-route,
> like you do
> today.
>
So the chain of service-route headers is actually a set of application
servers in the originating domain, each responsible for a different
server?
> 
> Actually there is an error in the draft, the service route must also be
> added to
> the CANCEL.
> 
> If a message contains both route-headers and service-route-headers, it is a
> result of an error and the damage is minimized by just go for the route.
> 
I think this should be repeated in section 4.2. As the text is stated
now, section 4.2 says to go for the service-route header, at least that
s how I interpreted it.
>
> /Henrik Gustafsson
> 
> Timothy SOETENS wrote:
> 
> >Hi All,
> >
> >I have some questions regarding the draft
> >draft-bjorkner-serviceroute-00.txt.
> >
> >I think it is a good thing to route requests according to the service a
> >user is subscribed for, but still I am confused in how the service-route
> >header is used.
> >
> >1. "The service-route header should only be inserted in the first
> >request in a call leg." (4.1, page 4) Is it not possible that you first
> >contact the callee before deciding on which service to use?
> >
> >2. "If a request contians both route headers and service-route headers
> >the route headers MUST be used for request routing." (4.1, page 5)
> >Indeed, if the route headers are used for request routing, it is not
> >useful to insert service-route headers in the subsequent requests.
> >However, I have the feeling that service-route headers can be useful in
> >subsequent requests.
> >
> >Comments?
> >
> >Thanks,
> >Tim.
> >

-- 
Timothy Soetens
_________________________________________

From the Network Strategy Group @ Alcatel

Tel. +32-3-240.42.11
Fax  +32-3-240.48.88

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