RE: [SECMECH] AAA requirement for middleware

"Salowey, Joe" <jsalowey@cisco.com> Tue, 28 June 2005 16:53 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DnJLT-0008AW-6a; Tue, 28 Jun 2005 12:53:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DnJLR-00089k-6J for secmech@megatron.ietf.org; Tue, 28 Jun 2005 12:53:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00614 for <secmech@ietf.org>; Tue, 28 Jun 2005 12:53:54 -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 1DnJko-000208-AS for secmech@ietf.org; Tue, 28 Jun 2005 13:20:11 -0400
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 28 Jun 2005 09:53:47 -0700
Received: from E2K-SEA-XCH2.sea-alpha.cisco.com (e2k-sea-xch2.cisco.com [10.93.132.68]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j5SGrfod004499; Tue, 28 Jun 2005 09:53:41 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [SECMECH] AAA requirement for middleware
Date: Tue, 28 Jun 2005 09:58:02 -0700
Message-ID: <7210B31550AC934A8637D6619739CE69056DCF3E@e2k-sea-xch2.sea-alpha.cisco.com>
Thread-Topic: [SECMECH] AAA requirement for middleware
Thread-Index: AcV7MmtOFq+LO0poSEiMVSsDAXX1CgAvK/Vw
From: "Salowey, Joe" <jsalowey@cisco.com>
To: "Josh Howlett" <josh.howlett@bristol.ac.uk>, "Sam Hartman" <hartmans-ietf@mit.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: quoted-printable
Cc: secmech@ietf.org
X-BeenThere: secmech@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Security mechanisms BOF <secmech.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/secmech>, <mailto:secmech-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/secmech>
List-Post: <mailto:secmech@lists.ietf.org>
List-Help: <mailto:secmech-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/secmech>, <mailto:secmech-request@lists.ietf.org?subject=subscribe>
Sender: secmech-bounces@lists.ietf.org
Errors-To: secmech-bounces@lists.ietf.org

Hi Josh,

I just posted a link to an Internet draft I have been working on about
creating generally useful authentication mechanisms (GUAM).  

I tried to state your requirements below as requirements for generally
useful authentication mechanisms. 

>  - plays nicely with the cross-realm AAA protocol _du jour_, 
> RADIUS, and successor, Diameter;

[Joe] Generally useful mechanisms should be usable in the EAP
framework/protocol. 

Currently to support RADIUS or DIAMETER it is helpful to be able to use
an authentication mechanism within the EAP framework.  There are other
possibilities but EAP provides a nice interface to AAA servers. 

>  - passthrough mode (authenticator does not participate in 
> authentication, beyond acting as a go-between, and simply 
> honours the success/failure code returned by the AAA backend);

[Joe] Generally useful mechanisms should perform authentication between
two parties and should expect than an arbitrary number of proxies
between the parties may handle the messages.

>  - negotiation of EAP methods;

[Joe] There should be a secure means of negotiating generally useful
mechanisms.  I assume you mean protected negotiation of EAP methods
(perhaps within a tunnel). 

>  - extensible attributes: can be returned by the AAA/H to 
> allow richer AuthZ at the resource;

[Joe] Generally useful mechanism should be able to exchange
authenticated data between authenticated parties and export this data to
the calling framework. In the GUAM draft I referred to this as channel
bindings (EAP).  

>  - ability to pass attributes from the AAA/H to both the peer 
> and the authenticator simultaneously, but distinctly and 
> privately, through the same AAA transaction;

[Joe] can you elaborate on this?

>  - security association can be established between the peer 
> (user) and the AAA/H, and used to provide privacy across the 
> hops between the peer and the AAA/H.

[Joe] Generally useful mechanisms should provide the ability to provide
confidentiality for the data exchanged as channel binding (eap). This
might not be a general requirement for all mechanisms, but a desirable
feature (integrity protection should be required).    

>  - use of anonymous NAIs ("anonymous@example.com") to allow 
> anonymous proxying of requests;

[Joe] Generally useful mechanisms should allow for privacy of the
identity of one of the parties. This might not be a general requirement
for all mechanisms, but it is desirable feature of mechanisms.   

>  - support for legacy AuthN mechanisms;

[Joe] I expect that this would depend upon the specific generally useful
mechanism  and the legacy mechanism.  Not all generally useful
mechanisms will support legacy AuthN mechanisms. What legacy mechanisms
are you interested in supporting?  
 

_______________________________________________
SECMECH mailing list
SECMECH@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/secmech