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

"Christer Holmberg" <christer.holmberg@ericsson.com> Wed, 16 January 2008 11:38 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 1JF6b9-00069x-0E; Wed, 16 Jan 2008 06:38:23 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JF6b8-00069s-Fm for sip-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 06:38:22 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JF6b8-00069j-3S for sip@ietf.org; Wed, 16 Jan 2008 06:38:22 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JF6b7-0007j0-9Z for sip@ietf.org; Wed, 16 Jan 2008 06:38:21 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 974E220F99; Wed, 16 Jan 2008 12:38:20 +0100 (CET)
X-AuditID: c1b4fb3e-af6a0bb00000459d-d7-478decac6f8f
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 7061320067; Wed, 16 Jan 2008 12:38:20 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Jan 2008 12:38:20 +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] Delivering request-URI and parameters to UAS via proxy
Date: Wed, 16 Jan 2008 12:38:19 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF04173C11@esealmw113.eemea.ericsson.se>
In-Reply-To: <5D1A7985295922448D5550C94DE2918001B09604@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Delivering request-URI and parameters to UAS via proxy
Thread-Index: AchWzqJNXVX4sjNuQSaW1d5oVZlILgBXedEAAAHq++A=
References: <5D1A7985295922448D5550C94DE2918001B09071@DEEXC1U01.de.lucent.com> <5D1A7985295922448D5550C94DE2918001B09604@DEEXC1U01.de.lucent.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>, <sip@ietf.org>
X-OriginalArrivalTime: 16 Jan 2008 11:38:20.0192 (UTC) FILETIME=[4B1EEA00:01C85834]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc:
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 Keith,

I submitted a new version earlier today.

Regards,

Christer 

> -----Original Message-----
> From: DRAGE, Keith (Keith) [mailto:drage@alcatel-lucent.com] 
> Sent: 16. tammikuuta 2008 13:35
> To: sip@ietf.org
> Subject: RE: [Sip] Delivering request-URI and parameters to 
> UAS via proxy
> 
> (As WG chair)
> 
> I am seeing consensus on the second draft.......
> 
> 
> .....that everyone is confused by the semantics applied to 
> the various headers, and the mail exchange does not seem to 
> be clearing it up.
> 
> I urge Christer and Hans Erik to get a new version out as 
> soon as possible in the hope of removing some of the confusion.
> 
> Regards
> 
> Keith 
> 
> > -----Original Message-----
> > From: DRAGE, Keith (Keith) [mailto:drage@alcatel-lucent.com]
> > Sent: Monday, January 14, 2008 4:58 PM
> > To: sip@ietf.org
> > Subject: [Sip] Delivering request-URI and parameters to UAS 
> via proxy
> > 
> > (As WG chair)
> > 
> > In fulfilment of our charter items of
> > 
> > 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)
> > 
> > We now have a couple of proposals on the table for solving the 
> > problem.
> > 
> > The original draft from Jonathan and which led to the 
> creation of the 
> > charter items by the WG is unfortunately expired, but is at:
> > 
> > http://tools.ietf.org/id/draft-rosenberg-sip-ua-loose-route-01.txt
> > 
> > The alternative document from Christer, etc is at:
> > 
> > http://www.ietf.org/internet-drafts/draft-holmberg-sip-target-
> > uri-delive
> > ry-00.txt
> > 
> > We obviously need to make a decision between the two approaches so 
> > please attempt to address the following specific points via the 
> > mailing
> > list:
> > 
> > 1)	Problem cases: These are summarised in section 4.4 of
> > draft-rosenberg-sip-ua-loose-route-01 and from my read of the other 
> > draft, I don't believe that this draft adds any others.
> > If you believe there are other cases that should be covered by the 
> > solution, then please identify them. If there is support on any new 
> > problem cases, I would encourage the authors of both drafts to add 
> > text concerning these problem cases.
> > 
> > 2)	Clarifications: If for any reason you don't understand either
> > draft, or believe that there are technical issues that are not 
> > represented in the current draft, please post your questions / 
> > comments to the list. I would encourage authors of both drafts to 
> > revise as frequently as appropriate to reflect the current state of 
> > discussion.
> > 
> > 3)	Support for either position. If you wish to indicate support for
> > either position please do so, but please accompany this is 
> technical 
> > reasoning as to why you have this position, as that will help other 
> > members of the WG form a position.
> > 
> > I would encourage as much list discussion as possible before 
> > Philadelphia. I suspect we will need to have a discussion at the 
> > face-to-face meeting in Philadephia, but list discussion is 
> essential 
> > prior to that. If we can solve this positions on list, then 
> well and 
> > good, and even better (that is how we are meant to make decisions).
> > 
> > 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