[Sip] Re: RLS and identity
Adam Roach <adam@nostrum.com> Thu, 11 November 2004 22:48 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 RAA08460 for <sip-web-archive@ietf.org>; Thu, 11 Nov 2004 17:48:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSNle-0007xX-8t for sip-web-archive@ietf.org; Thu, 11 Nov 2004 17:50:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSNhu-0000tq-Sz; Thu, 11 Nov 2004 17:46:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSNWf-0005Zk-VR for sip@megatron.ietf.org; Thu, 11 Nov 2004 17:34:46 -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 RAA07121 for <sip@ietf.org>; Thu, 11 Nov 2004 17:34:43 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSNXv-0007Z5-Bc for sip@ietf.org; Thu, 11 Nov 2004 17:36:03 -0500
Received: from [130.129.132.245] ([130.129.132.245]) (authenticated bits=0) by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iABMYh7e006813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Nov 2004 16:34:44 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4193E902.7010206@nostrum.com>
Date: Thu, 11 Nov 2004 16:34:42 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Aki Niemi <aki.niemi@nokia.com>
References: <4193DAAC.3020609@nokia.com>
In-Reply-To: <4193DAAC.3020609@nokia.com>
X-Enigmail-Version: 0.86.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Cc: SIP WG <sip@ietf.org>
Subject: [Sip] Re: RLS and identity
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: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Aki Niemi wrote: > > Just a minor note on this: if/when mandating the support for asserted > identity in the event-list draft, please remember to say that > p-asserted identities also count (to some extent). 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. If you think that your architecture, in combination with P-Asserted-Identity, satisfies the second bullet, then you're probably fine. However, I think it is a really bad idea to specifically include any mention of P-Asserted-Identity in the draft. /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] 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