RE: [Sip] Question on Service Route Discovery Procedure duringRegistration

"Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com> Fri, 21 April 2006 08:08 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWqgp-0005fM-T3; Fri, 21 Apr 2006 04:08:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWqgo-0005fH-FW for sip@ietf.org; Fri, 21 Apr 2006 04:08:30 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWqgk-0007UC-Na for sip@ietf.org; Fri, 21 Apr 2006 04:08:30 -0400
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 3260F4F0018; Fri, 21 Apr 2006 10:08:26 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Apr 2006 10:08:25 +0200
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Apr 2006 10:08:25 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] Question on Service Route Discovery Procedure duringRegistration
Date: Fri, 21 Apr 2006 10:08:25 +0200
Message-ID: <5EB80D22825EEE42872083AD5BFFB5945D1D7B@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Question on Service Route Discovery Procedure duringRegistration
Thread-Index: AcZkhGEBdHdQ8+glQgWH8eCinWLnjAAlhrpA
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
X-OriginalArrivalTime: 21 Apr 2006 08:08:25.0775 (UTC) FILETIME=[C3F423F0:01C6651A]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: sip@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Hi Paul, 

>>>>2. Registrar processing of Path
>>>>
>>>>I think we should also take Jonathan's draft, 
>>>>draft-rosenberg-sip-route-construct-00, into consideration, which 
>>>>allows a registrar to build a Service-Route set based on the
received 
>>>>Path headers.
>>>
>>>Lovely idea, and 3608 suggests it as a possibility. Doesn't work for

>>>IMS AFAIk, so it can't be a MUST.
>> 
>>I need to check that. But, is there something special you have in mind

>>why it wouldn't work with IMS?
>
>The way IMS is organized, it is possible to have two UAs registered to
the same AOR (Public User Identity), but accessing via different
P-CSCFs.
>
>The Path must include the P-CSCF so that requests can reach the
intended UA via the P-CSCF it uses. That means in the two UA case there
must be two Paths 
>- one for each registered Contact. This is supported by RFC 3327.
>
>If route-construct were used to construct the Service-Route, then there
would be two different Service-Routes for the same AOR. But according to
RFC 3608 
>there may be only one Service-Route per AOR. So the algorithm of
route-construct won't work for IMS as currently defined.

[CHH] Ok. So, it's more an RFC issue than an IMS issue.

>I believe Jonathan has advocated a revision to RFC 3608 so that there
may be a separate Service-Route for each registered contact. But there
has been no 
>action to make such a change.

[CHH] I guess that change would have to be done together with the other
change(s).

Regards,

Christer

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