Re: [secdir] SECDIR review of draft-ietf-hokey-key-mgm

Kurt Zeilenga <Kurt.Zeilenga@Isode.com> Mon, 10 August 2009 18:34 UTC

Return-Path: <Kurt.Zeilenga@Isode.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDD383A6EBF; Mon, 10 Aug 2009 11:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level:
X-Spam-Status: No, score=-2.381 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fNcxddvNgVjW; Mon, 10 Aug 2009 11:34:39 -0700 (PDT)
Received: from boole.openldap.org (boole.openldap.org [IPv6:2001:4f8:3:ba:219:21ff:fe2f:68d5]) by core3.amsl.com (Postfix) with ESMTP id D9BF33A6F10; Mon, 10 Aug 2009 11:33:44 -0700 (PDT)
Received: from [192.168.1.101] (75-141-233-128.dhcp.nv.charter.com [75.141.233.128] (may be forged)) (authenticated bits=0) by boole.openldap.org (8.14.3/8.14.3) with ESMTP id n7AIXZt3082374; Mon, 10 Aug 2009 18:33:36 GMT (envelope-from Kurt.Zeilenga@Isode.com)
Message-Id: <B1002512-9406-4681-965C-17A7C189DF98@Isode.com>
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
To: Glen Zorn <glenzorn@comcast.net>
In-Reply-To: <00bf01ca19e0$1b703e70$5250bb50$@net>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 10 Aug 2009 11:33:34 -0700
References: <369289D9-6E39-4673-B50E-0090BBBB6EB2@Isode.com> <00bf01ca19e0$1b703e70$5250bb50$@net>
X-Mailer: Apple Mail (2.936)
Cc: draft-ietf-hokey-key-mgm@tools.ietf.org, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] SECDIR review of draft-ietf-hokey-key-mgm
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Aug 2009 18:34:39 -0000

On Aug 10, 2009, at 10:29 AM, Glen Zorn wrote:

> Kurt Zeilenga [mailto://Kurt.Zeilenga@Isode.com] writes:
>
> ...
>
>> The security consideration starts by saying:
>>    This section provides security requirements and an analysis on
>> transporting EAP keying material using an AAA protocol.
>> While 6.1 appears to provide the former, 6.2 (the remaining section)
>> seems to discuss a particular concern in transporting EAP keying
>> material in an APP protocol.
>
> No.  AFAIK, the only existing protocols in which EAP key transport  
> take
> place are AAA.

My point that Section 6 description of what section 6.2 provides seems  
not equate (to me) to what 6.2 actually provides.  6.2 seems to  
discuss a particular issue in "transporting EAP keying material using  
an AAA protocol" as opposed to a more comprehensive "analysis on  
transporting EAP keying material using an AAA protocol".

> ? Is this the only concern?
>
> I would assume so; does that need to be spelled out?

Not necessarily.

>
>> I would like to see the Security Consideration section to incorporate
>> by informative references general discussions of security
>> considerations for key technologies (e.g., EAP).
>
> Why?  The EAP (or ERP) authentication is by definition complete by  
> the time
> any keys are exported by the EAP method, so it's hard to see how those
> considerations are relevant.

As the document discusses use of KDE in ERP, it would seem to me that  
ERP security considerations would have some relevance.  I find  
statements such as:

	ERP security considerations are discussed in [RFCxxxx].  EAP security  
considerations are discussed in [RFCyyyy].

useful as they further encourage the reader to consider security  
considerations of key technologies.

>
>> Beyond this, I'm afraid I do not have sufficient experience in the  
>> key
>> technologies to be able to determine if security considerations are
>> well covered or not.
>> Regards, Kurt
>>
>>
>>
>>
>> _______________________________________________
>> secdir mailing list
>> secdir@ietf.org
>> https://www.ietf.org/mailman/listinfo/secdir
>