Re: [SECMECH] AAA requirement for middleware

Josh Howlett <josh.howlett@bristol.ac.uk> Mon, 27 June 2005 11:42 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dms0p-0006Dx-9c; Mon, 27 Jun 2005 07:42:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dms0n-0006Ds-Kd for secmech@megatron.ietf.org; Mon, 27 Jun 2005 07:42:49 -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 HAA09908 for <secmech@ietf.org>; Mon, 27 Jun 2005 07:42:48 -0400 (EDT)
Received: from dirg.bris.ac.uk ([137.222.10.102]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DmsPt-00018a-Uz for secmech@ietf.org; Mon, 27 Jun 2005 08:08:48 -0400
Received: from seis.bris.ac.uk ([137.222.10.93]) by dirg.bris.ac.uk with esmtp (Exim 4.51) id 1Dms0F-0000Ag-En; Mon, 27 Jun 2005 12:42:20 +0100
Received: from cumulus.cse.bris.ac.uk ([137.222.12.162]) by seis.bris.ac.uk with esmtp (Exim 4.51) id 1DmrzJ-0005Bb-DM; Mon, 27 Jun 2005 12:41:28 +0100
Date: Mon, 27 Jun 2005 12:41:16 +0100
From: Josh Howlett <josh.howlett@bristol.ac.uk>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [SECMECH] AAA requirement for middleware
Message-ID: <BDF2F587280947CE549536C2@cumulus>
In-Reply-To: <tslpsu8993r.fsf@cz.mit.edu>
References: <Pine.GSO.4.44.0506232014570.2267-100000@shark.cse.bris.ac.uk> <tslpsu8993r.fsf@cz.mit.edu>
Originator-Info: login-token=Mulberry:01KPkDfYpubeNrYkncYolpMPBlcDfWaI0nZe9cbTfUWFZubg==; token_authority=postmaster@bristol.ac.uk
X-Mailer: Mulberry/3.1.5 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: -2.8
X-Spam-Level: --
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Cc: secmech@ietf.org
X-BeenThere: secmech@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Josh Howlett <josh.howlett@bristol.ac.uk>
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

--On Sunday, June 26, 2005 16:06:00 -0400 Sam Hartman 
<hartmans-ietf@mit.edu> wrote:
> I don't think extending EAP to those other frameworks is the right
> solution. I do think that making it possible to use cross-realm AAA
> is a requirement.

In which case, it's important to me that these frameworks offer mechanisms 
that share the properties of EAP (or, at least, the tunelled EAP methods) 
that make it so good for cross-realm AAA.

Thanks, josh.

-- 
-----------------------------------------------------------
Josh Howlett, Networking & Digital Communications,
Information Systems & Computing, University of Bristol, U.K.
'phone: 0117 928 7850 email: josh.howlett@bris.ac.uk
------------------------------------------------------------

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