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

"DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com> Wed, 09 January 2008 16:31 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 1JCdqI-00013z-KT; Wed, 09 Jan 2008 11:31:50 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JCdqG-00013t-Ms for sip-confirm+ok@megatron.ietf.org; Wed, 09 Jan 2008 11:31:48 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCdqG-00013l-Bt for sip@ietf.org; Wed, 09 Jan 2008 11:31:48 -0500
Received: from ihemail3.lucent.com ([135.245.0.37]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCdqF-0001zJ-Tr for sip@ietf.org; Wed, 09 Jan 2008 11:31:48 -0500
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id m09GVcRX001917 for <sip@ietf.org>; Wed, 9 Jan 2008 10:31:45 -0600 (CST)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 Jan 2008 10:31:41 -0600
Received: from DEEXC1U01.de.lucent.com ([135.248.187.20]) by DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 Jan 2008 17:31:39 +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
Date: Wed, 9 Jan 2008 17:31:39 +0100
Message-ID: <5D1A7985295922448D5550C94DE2918001AC02E9@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Delivering request-URI and parameters to UAS via proxy
Thread-index: Acg2ih6i4UTKPgVSQf2WFbiy3Qsq9wcUuLeA
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: <sip@ietf.org>
X-OriginalArrivalTime: 09 Jan 2008 16:31:39.0883 (UTC) FILETIME=[1C7663B0:01C852DD]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Subject: [Sip] RE: Delivering request-URI and parameters to UAS via proxy
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

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