RE: [Sip] RE: Delivering request-URI and parameters to UAS via proxy

"Christer Holmberg" <christer.holmberg@ericsson.com> Fri, 11 January 2008 20:02 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JDQ57-0000Qv-NS; Fri, 11 Jan 2008 15:02:21 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JDQ55-0000PC-Sk for sip-confirm+ok@megatron.ietf.org; Fri, 11 Jan 2008 15:02:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JDQ55-0000P4-3Z for sip@ietf.org; Fri, 11 Jan 2008 15:02:19 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDQ53-0004FC-0a for sip@ietf.org; Fri, 11 Jan 2008 15:02:19 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id CC0AD212AB; Fri, 11 Jan 2008 21:02:15 +0100 (CET)
X-AuditID: c1b4fb3e-b16a4bb00000459d-23-4787cb47c288
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 8BAC820253; Fri, 11 Jan 2008 21:02:15 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 11 Jan 2008 21:02:15 +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: [Sip] RE: Delivering request-URI and parameters to UAS via proxy
Date: Fri, 11 Jan 2008 21:02:14 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF04051CAE@esealmw113.eemea.ericsson.se>
In-Reply-To: <4787C56B.9050002@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] RE: Delivering request-URI and parameters to UAS via proxy
Thread-Index: AchUiWfnBwLh8GzUQYCipl+i5qlSwwAAZW1g
References: <5D1A7985295922448D5550C94DE2918001AC02E9@DEEXC1U01.de.lucent.com><CA9998CD4A020D418654FCDEF4E707DF040266B1@esealmw113.eemea.ericsson.se><47878B1E.3010303@cisco.com><CA9998CD4A020D418654FCDEF4E707DF04051C96@esealmw113.eemea.ericsson.se> <4787C56B.9050002@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 11 Jan 2008 20:02:15.0279 (UTC) FILETIME=[DC924FF0:01C8548C]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Cc: sip@ietf.org, "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.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, 

>>>I have some questions and comments:
>>>
>>>- I don't understand your examples in section 3. They are a bit 
>>>sketchy about the assumptions they are making, and in notation. I get

>>>lost about which referenced component has which address, etc. I am 
>>>far from convinced that these are problems with appropriate use of 
>>>the mechanism.
>> 
>>As indicated in chapter 3, one of the main issues/limitations with the

>>J'draft solution is that the entity wanting to use it must have 
>>knowledge whether the next hop also supports it. My understanding from

>>off-line discussions I had with Jonathan in Vancouver is also that 
>>Jonathan agrees to that issue/limitation.
>> 
>>The purpose of the examples is just to show what can go wrong if the 
>>next hop does not understand the mechanism. But, if we all agree to 
>>the limitation with the J'draft solution I don't know whether we need 
>>to spend too much time on the examples.
> 
>The limitation is the limitation. It means that you don't use 
>the mechanism if you don't know the next hop supports it. So 
>its useless to speculate what would go wrong if you use the 
>mechanism with a next hop that doesn't support it.

We thought it would be good to show some examples, in case people don't
understand WHY the limitation is there.

>>>- It seems from your analysis of use cases that it is P-Called-Party 
>>>that solves many of them, not Target. So both headers seem to be part

>>>of the solution.
>> 
>>No, as far as the alternative to the J'draft solution is concerned, 
>>the alternative is Target. We believe it can be used for all listed 
>>use-cases.
> 
>I don't understand. Several of them called for using P-CPI.

No, we say that there are certain use-case we belive the P-CPI was
defined to be used for, but we also say that the Target header can be
used for those use-cases.

Again, the Target header is our proposal for an alternative to the
J'draft solution.

Regards,

Christer








> >> Christer Holmberg wrote:
> >>> Hi,
> >>>
> >>> We have submitted a draft with an alternative proposal.
> >>>
> >>> It can also be found at:
> >>>
> >>>
> >> 
> http://users.piuha.net/cholmber/drafts/draft-holmberg-sip-target-uri-
> >> d
> >>> el
> >>> ivery-00.txt
> >>>
> >>> Regards,
> >>>
> >>> Christer
> >>>
> >>>  
> >>>
> >>>> -----Original Message-----
> >>>> From: DRAGE, Keith (Keith) [mailto:drage@alcatel-lucent.com]
> >>>> Sent: 9. tammikuuta 2008 18:32
> >>>> To: sip@ietf.org
> >>>> Subject: [Sip] RE: Delivering request-URI and parameters
> >> to UAS via
> >>>> proxy
> >>>>
> >>>> A reminder of the deadline on the 11th January for submitting 
> >>>> alternative proposals on the way forward.
> >>>>
> >>>> Regards
> >>>>
> >>>> Keith
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: DRAGE, Keith (Keith)
> >>>>> Sent: Tuesday, December 04, 2007 3:27 PM
> >>>>> To: sip@ietf.org
> >>>>> Subject: Delivering request-URI and parameters to UAS via proxy
> >>>>>
> >>>>> (As WG chair)
> >>>>>
> >>>>> We have a couple of milestones that we generated as a result of 
> >>>>> discussion of
> >>>>>
> >>>>> http://www.ietf.org/internet-drafts/draft-rosenberg-sip-ua-loo
> >>>>> se-route-01.txt
> >>>>>
> >>>>> Dec 2007    Delivering request-URI and parameters to UAS via 
> >>>>> proxy to WGLC  
> >>>>> Feb 2008    Delivering request-URI and parameters to UAS via 
> >>>>> proxy to IESG (PS)
> >>>>>
> >>>>> This work is currently stalled and the editor needs input.
> >>>>>
> >>>>> The document contains various example scenarios where a
> >> solution is
> >>>>> required, for which there appears to be no dispute that a
> >>>> solution is
> >>>>> needed.
> >>>>>
> >>>>> The document proposes one solution to resolve these example
> >>>> scenarios,
> >>>>> but this solution is not gaining consensus. At least one other 
> >>>>> solution has been talked about, but there is no
> >>>> documentation on the
> >>>>> table.
> >>>>>
> >>>>> This mail is to identify a deadline for other solutions to
> >>>> the example
> >>>>> scenarios to be documented as internet drafts, showing how the 
> >>>>> solution works for those scenarios. This deadline is:
> >>>>>
> >>>>> 	January 11th 2008
> >>>>>
> >>>>> It is appropriate fo these documents to identify any other
> >>>> scenarios
> >>>>> where such a solution is appropriate. Any other input is
> >>>> also welcome
> >>>>> in identifying other scenarios.
> >>>>>
> >>>>> If we have no such internet-drafts by this deadline, we
> >>>> will proceed
> >>>>> with completing the solution we have.
> >>>>>
> >>>>>
> >>>>> Regards
> >>>>>
> >>>>> Keith
> >>>>>
> >>>>>
> >>>> _______________________________________________
> >>>> 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
> >>>>
> >>>
> >>> _______________________________________________
> >>> 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
> >>>
> >>
> >> _______________________________________________
> >> 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
> >>
> > 
> 
> 
> _______________________________________________
> 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
> 


_______________________________________________
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