IETF Logo Mail Archive

Re: [consensus] comments on draft-housley-aaa-key-mgmt-07.txt

Sam Hartman <hartmans-ietf@mit.edu> Thu, 05 April 2007 16:03 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HZUQf-0006yB-Qk; Thu, 05 Apr 2007 12:03:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HZUQe-0006xr-2M for ietf@ietf.org; Thu, 05 Apr 2007 12:03:16 -0400
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178] helo=carter-zimmerman.mit.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZUQT-00032x-Jt for ietf@ietf.org; Thu, 05 Apr 2007 12:03:15 -0400
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id DF9F5E0433; Thu, 5 Apr 2007 12:03:05 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Bernard Aboba <bernarda@windows.microsoft.com>
References: <41825.12.108.168.179.1171660575.squirrel@www.trepanning.net> <tslwt2hiybm.fsf@cz.mit.edu> <C24CB51D5AA800449982D9BCB90325134F192B@NAEX13.na.qualcomm.com> <tslfy947pol.fsf@cz.mit.edu> <45D73CEB.2000701@qualcomm.com> <C24CB51D5AA800449982D9BCB90325134F192D@NAEX13.na.qualcomm.com> <0C7B902B470A264FA64D66CBF76FB821014CD3F6@WIN-MSG-20.wingroup.windeploy.ntdev.microsoft.com> <C24CB51D5AA800449982D9BCB90325134F1947@NAEX13.na.qualcomm.com> <tsld52qipph.fsf_-_@cz.mit.edu> <52310.69.12.173.8.1175549276.squirrel@www.trepanning.net> <tsl7ist2dif.fsf@cz.mit.edu> <14965.12.108.168.179.1175731583.squirrel@www.trepanning.net> <tsltzvvei2w.fsf@cz.mit.edu> <0C7B902B470A264FA64D66CBF76FB8210358C4E4@WIN-MSG-20.wingroup.windeploy.ntdev.microsoft.com>
Date: Thu, 05 Apr 2007 12:03:05 -0400
In-Reply-To: <0C7B902B470A264FA64D66CBF76FB8210358C4E4@WIN-MSG-20.wingroup.windeploy.ntdev.microsoft.com> (Bernard Aboba's message of "Thu, 5 Apr 2007 08:29:22 -0700")
Message-ID: <tslabxm6c7a.fsf@cz.mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ietf@ietf.org
Subject: Re: [consensus] comments on draft-housley-aaa-key-mgmt-07.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

>>>>> "Bernard" == Bernard Aboba <bernarda@windows.microsoft.com> writes:

    Bernard> O, I definitely think they are session keys.  [BA] They
    Bernard> are not TSKs according to the definition in the EAP Key
    Bernard> Management Framework.

That's true.
But  that definition is not normative for draft-housley-aaa-key-mgmt.

    Bernard> Wait, what's wrong with giving 100 authenticators 100
    Bernard> different keys provided that each authenticator is
    Bernard> authorized to claim the identity it plans to claim?
    Bernard> Isn't that exactly the sort of thing we do want to do?
 
    Bernard> [BA] The creation of cryptographically separate keys for
    Bernard> each authenticator is not sufficient; the EAP Key
    Bernard> Management Framework describes the problems that can
    Bernard> result without authentication and authorization.

Again, I think that correctness of accounting in this instance is an
additional requirement the key management framework puts on top of
draft-housley-aaa-key-mgmt.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email