Re: [Sip] Event Lists: Back-End Credentials
Paul Kyzivat <pkyzivat@cisco.com> Wed, 27 October 2004 13:22 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 JAA02743 for <sip-web-archive@ietf.org>; Wed, 27 Oct 2004 09:22:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMnzJ-00057z-Sq for sip-web-archive@ietf.org; Wed, 27 Oct 2004 09:37:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMnhT-0007Oa-Sa; Wed, 27 Oct 2004 09:18:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMne5-00066h-6K for sip@megatron.ietf.org; Wed, 27 Oct 2004 09:15:21 -0400
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 JAA02355 for <sip@ietf.org>; Wed, 27 Oct 2004 09:15:19 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMnrw-0004zp-4S for sip@ietf.org; Wed, 27 Oct 2004 09:29:41 -0400
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 27 Oct 2004 06:23:52 -0700
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9RDEcYL004855; Wed, 27 Oct 2004 06:14:40 -0700 (PDT)
Received: from cisco.com ([161.44.79.201]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMP06853; Wed, 27 Oct 2004 09:14:44 -0400 (EDT)
Message-ID: <417F9F43.1040704@cisco.com>
Date: Wed, 27 Oct 2004 09:14:43 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
Subject: Re: [Sip] Event Lists: Back-End Credentials
References: <41780D08.3090007@nostrum.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: sip@ietf.org
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: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Adam Roach wrote: > * Add new SIP header field (or maybe method) for credential upload > > One very simple solution would be to add a new header which contains > a triple of [realm,userid,password]. We would specify that this > header is disallowed except over SIPS connections. The client would > include one or more such headers in its SUBSCRIBE request, and the > RLS would use them to obtain information on the user's behalf. Dave then espressed reservations over this because it grants too much capability to the RLS. I agree with Dave's concern over this, and think his suggestion to tackle the problem of delegation head on is the right solution in the long term. OTOH, it doesn't seem like we can wait that long to get something going for RLS. To pursue Adam's suggestion without giving away the ranch, maybe presence servers could have one set of credentials that grant only limited access (subscription by buddies), and another for full permissions. This is really just an implementation technique and so we couldn't standardize it, but it might be a way to allow this crippled mechanism to be useful. Paul _______________________________________________ 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] Event Lists: Back-End Credentials Adam Roach
- Re: [Sip] Event Lists: Back-End Credentials David R Oran
- Re: [Sip] Event Lists: Back-End Credentials Adam Roach
- [Sip] Event Lists: Back-End Credentials Adam Roach
- Re: [Sip] Event Lists: Back-End Credentials David R Oran
- Re: [Sip] Event Lists: Back-End Credentials Paul Kyzivat
- RE: [Sip] Event Lists: Back-End Credentials hisham.khartabil
- Re: [Sip] Event Lists: Back-End Credentials Adam Roach
- Re: [Sip] Event Lists: Back-End Credentials Adam Roach
- RE: [Sip] Event Lists: Back-End Credentials hisham.khartabil
- Re: [Sip] Event Lists: Back-End Credentials David R Oran
- RE: [Sip] Event Lists: Back-End Credentials hisham.khartabil
- Re: [Sip] Event Lists: Back-End Credentials David R Oran
- Re: [Sip] Event Lists: Back-End Credentials Jonathan Rosenberg
- Re: [Sip] Event Lists: Back-End Credentials Jonathan Rosenberg