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

Henrik Gustafsson <henrik.gustafsson@hotsip.com> Thu, 13 September 2001 12:52 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 IAA02446 for <sip-archive@odin.ietf.org>; Thu, 13 Sep 2001 08:52:19 -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 IAA07609; Thu, 13 Sep 2001 08:27:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA07586 for <sip@ns.ietf.org>; Thu, 13 Sep 2001 08:27:18 -0400 (EDT)
Received: from hotsip.com ([212.28.214.248]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01684 for <sip@ietf.org>; Thu, 13 Sep 2001 08:27:12 -0400 (EDT)
Received: from hotsip.com ([212.28.214.197]) by hotsip.com with Microsoft SMTPSVC(5.0.2195.2966); Thu, 13 Sep 2001 14:08:32 +0200
Message-ID: <3BA0A0EE.60906@hotsip.com>
Date: Thu, 13 Sep 2001 14:05:02 +0200
From: Henrik Gustafsson <henrik.gustafsson@hotsip.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.1) Gecko/20010607
X-Accept-Language: en-us
MIME-Version: 1.0
To: Timothy SOETENS <timothy.soetens@alcatel.be>
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> <3BA081AE.5E87A59F@alcatel.be>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Sep 2001 12:08:32.0303 (UTC) FILETIME=[CE841BF0:01C13C4C]
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

Timothy SOETENS wrote:

>So the chain of service-route headers is actually a set of application
>servers in the originating domain, each responsible for a different
>server?
>
Yes, that's true. I think it is important to point at that the 
service-route
is not the ideal service compositioning mechanism, it is just one
possible tool.

This is also related to the currently very active loose-routing thread.
I belive adding complexity to the existing route header is worse than
adding complexity to the protocol with a new relative simple header.

>
>>
>>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.
>
Yes, it is somewhat unclear. Now it is described at the end of 4.1.

/Henrik

>
>>/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.
>>>
>



_______________________________________________
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