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

Sam Hartman <hartmans-ietf@mit.edu> Thu, 05 April 2007 18:54 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 1HZX6j-00026z-Jy; Thu, 05 Apr 2007 14:54:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HZX6i-00026j-6F for ietf@ietf.org; Thu, 05 Apr 2007 14:54:52 -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 1HZX3r-0002S2-Fn for ietf@ietf.org; Thu, 05 Apr 2007 14:52:04 -0400
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id 239EDE0433; Thu, 5 Apr 2007 14:51:55 -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> <tslabxm6c7a.fsf@cz.mit.edu> <0C7B902B470A264FA64D66CBF76FB8210358C4E8@WIN-MSG-20.wingroup.windeploy.ntdev.microsoft.com>
Date: Thu, 05 Apr 2007 14:51:54 -0400
In-Reply-To: <0C7B902B470A264FA64D66CBF76FB8210358C4E8@WIN-MSG-20.wingroup.windeploy.ntdev.microsoft.com> (Bernard Aboba's message of "Thu, 5 Apr 2007 10:25:07 -0700")
Message-ID: <tsl7isq3b91.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: 69a74e02bbee44ab4f8eafdbcedd94a1
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.

    Bernard> That's true.  But that definition is not normative for
    Bernard> draft-housley-aaa-key-mgmt.
 
    Bernard> [BA] If the documents are using a different definition of
    Bernard> "session keys" then I think we need to make sure that the
    Bernard> term is clearly defined in draft-housley to avoid
    Bernard> confusion.
Sure, they should use a consistent definition, but for example, the
"master session key" really needs to be included in the definition of
session key.


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



    Bernard> [BA] The term "AAA" stands for authentication,
    Bernard> authorization and accounting.  Why would the correctness
    Bernard> of accounting data be a requirement only for one
    Bernard> particular AAA usage?



I think it is a true statement that draft-housley-aaa-key-mgmt does
not make this requirement about accounting; you are welcome to show me
text that I've missed about this issue in draft-housley-aaa-key-mgmt.
I take no stand on whether this should have been included in the AAA
key management draft other than to say that it is really late for
adding requirements of this form.


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