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

"Francois Audet" <audet@nortel.com> Fri, 11 January 2008 18:58 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 1JDP53-0001NJ-Q4; Fri, 11 Jan 2008 13:58:13 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JDP52-0001N9-4Q for sip-confirm+ok@megatron.ietf.org; Fri, 11 Jan 2008 13:58:12 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JDP51-0001N0-Oq for sip@ietf.org; Fri, 11 Jan 2008 13:58:11 -0500
Received: from zcars04e.nortel.com ([47.129.242.56]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JDP51-0008OW-0T for sip@ietf.org; Fri, 11 Jan 2008 13:58:11 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id m0BIsSK27246; Fri, 11 Jan 2008 18:54:29 GMT
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: [Sip] RE: Delivering request-URI and parameters to UAS via proxy
Date: Fri, 11 Jan 2008 12:58:04 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF1428F69B@zrc2hxm0.corp.nortel.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0549A47@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] RE: Delivering request-URI and parameters to UAS via proxy
Thread-Index: AchUZtW5bDMRNv3qRbeBDq53RksY6wAC6fXwAAREC3A=
References: <5D1A7985295922448D5550C94DE2918001AC02E9@DEEXC1U01.de.lucent.com> <CA9998CD4A020D418654FCDEF4E707DF040266B1@esealmw113.eemea.ericsson.se> <47878B1E.3010303@cisco.com> <0D5F89FAC29E2C41B98A6A762007F5D0549A47@GBNTHT12009MSX.gb002.siemens.net>
From: "Francois Audet" <audet@nortel.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97c820c82c68af374c4e382a80dc5017
Cc: sip@ietf.org, "Elwell, John" <john.elwell@siemens.com>, Paul Kyzivat <pkyzivat@cisco.com>, "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

I'm also totally confused now about what is being proposed.

The Target seems identical to the To header field.

I tought that what you (Christer) was arguing for is using the P-Called-Header
instead of the new loose route proposal, i.e., not for the "initial target", but for
the "current target".

 

> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens.com] 
> Sent: Friday, January 11, 2008 09:01
> To: Paul Kyzivat; Christer Holmberg
> Cc: sip@ietf.org; DRAGE, Keith (Keith)
> Subject: RE: [Sip] RE: Delivering request-URI and parameters 
> to UAS via proxy
> 
> Christer,
> 
> In addition to Paul's concerns, I am having difficulty 
> understanding why the To header field is insufficient for the 
> cases where the Target header field is proposed. The initial 
> source of this confusion was the statement "the Target header 
> field represents
>    the initial target identity that was used to initiate a session to
>    the target"
> 
> So we now have 4 fields (ignoring Route):
> - To
> - Target
> - P-Called-ID
> - Request-URI
> I think it would benefit from a clearer exposition of the 
> semantics and relationship between these.
> 
> John
> 
>  
> 
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: 11 January 2008 15:29
> > To: Christer Holmberg
> > Cc: sip@ietf.org; DRAGE, Keith (Keith)
> > Subject: Re: [Sip] RE: Delivering request-URI and parameters to UAS 
> > via proxy
> > 
> > Christer,
> > 
> > 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.
> > 
> > - 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. Its not entirely clear to me at the moment whether 
> > the R-URI in the loose-route approach aligns with Target or 
> > P-Called-Party.
> > Since they are different, it can't align with both. So 
> there must be 
> > some features it doesn't cover. I haven't fully grokked that yet.
> > 
> > 	Paul
> > 
> > 
> > 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-targ
> > et-uri-del
> > > 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