RE: [Sip] Re: RLS and identity
Milinski Alexander <alexander.milinski@siemens.com> Thu, 25 November 2004 08:17 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13258 for <sip-web-archive@ietf.org>; Thu, 25 Nov 2004 03:17:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXEsg-0004Qp-Ly for sip-web-archive@ietf.org; Thu, 25 Nov 2004 03:21:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXEgi-0004vt-QW; Thu, 25 Nov 2004 03:09:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXEce-0003iI-NI for sip@megatron.ietf.org; Thu, 25 Nov 2004 03:05:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11814 for <sip@ietf.org>; Thu, 25 Nov 2004 03:04:58 -0500 (EST)
Received: from david.siemens.de ([192.35.17.14]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXEgg-00046W-As for sip@ietf.org; Thu, 25 Nov 2004 03:09:10 -0500
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.12.6/8.12.6) with ESMTP id iAP84wRt030760; Thu, 25 Nov 2004 09:04:58 +0100
Received: from mchh247e.mchh.siemens.de (mchh247e.mchh.siemens.de [139.21.200.57]) by mail1.siemens.de (8.12.6/8.12.6) with ESMTP id iAP84wts031280; Thu, 25 Nov 2004 09:04:58 +0100
Received: by mchh247e.mchh.siemens.de with Internet Mail Service (5.5.2657.72) id <X1WPWR2J>; Thu, 25 Nov 2004 09:03:24 +0100
Message-ID: <79D5F4B2D775204D9C7852EE41C5477305D0AF6F@mchh2a1e.mchh.siemens.de>
From: Milinski Alexander <alexander.milinski@siemens.com>
To: 'Adam Roach' <adam@nostrum.com>
Subject: RE: [Sip] Re: RLS and identity
Date: Thu, 25 Nov 2004 09:04:56 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: SIP WG <sip@ietf.org>, Aki Niemi <aki.niemi@nokia.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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Dear Adam, 3GPP Rel-6 is close to freezing, thus I would not expect any more major changes. Also, it seems that backward compatibility would need to be addressed. In other words: I believe your proposal is not realistic. Regards, Alexander P.S. Once Dean has cleaned up all SIP evils, there will certainly be the opportunity to consider also other major changes ... :-) -----Original Message----- From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Adam Roach Sent: Thursday, November 25, 2004 4:18 AM To: Adam Roach Cc: SIP WG; Aki Niemi Subject: Re: [Sip] Re: RLS and identity Adam Roach wrote: > Based on Rohan's suggestion, the text will effectively say: > > - Jon's Identity draft will be mandatory to implement, optional to use. > > - Other mechanisms that have properties such that they can adequately > convey the identity of the subscriber and the permission of the RLS > to subscribe on the user's behalf can also be used. As a clarification, I have received specific guidance from the area directors that the draft cannot contain anything about such alternate mechanisms, even if they are not specifically mentioned by name. The use of e.g. P-Asserted-Identity will need to be a modification that 3GPP specifically calls out relative to the draft. Of course, since the identity work is basically done and works so much better than P-Asserted-Identity, there could be a very valid argument made that 3GPP R6 should abandon the inherently insecure P-Asserted-Identity mechanism in favor of the cryptographically secure SIP Identity mechanism. /a _______________________________________________ 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] RLS and identity Aki Niemi
- [Sip] Re: RLS and identity Adam Roach
- Re: [Sip] Re: RLS and identity Adam Roach
- RE: [Sip] Re: RLS and identity Milinski Alexander
- RE: [Sip] Re: RLS and identity Drage, Keith (Keith)
- Re: [Sip] Re: RLS and identity Adam Roach