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

Kurt Zeilenga <Kurt.Zeilenga@Isode.com> Mon, 10 August 2009 16:49 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 725283A6E79; Mon, 10 Aug 2009 09:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level:
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 nC-6VhtUWRgl; Mon, 10 Aug 2009 09:49:38 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 65AA128C18A; Mon, 10 Aug 2009 09:49:03 -0700 (PDT)
Received: from [172.16.2.183] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <SoBPgQB9YSJU@rufus.isode.com>; Mon, 10 Aug 2009 17:49:05 +0100
Message-Id: <369289D9-6E39-4673-B50E-0090BBBB6EB2@Isode.com>
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
To: secdir@ietf.org, iesg@ietf.org
Date: Mon, 10 Aug 2009 09:49:02 -0700
X-Mailer: Apple Mail (2.936)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-hokey-key-mgm@tools.ietf.org
Subject: [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 16:49:39 -0000

I have reviewed this document as part of the security directorate's  
ongoing effort to review all IETF documents being processed by the  
IESG.  These comments were written primarily for the benefit of the  
security area directors.  Document editors and WG chairs should treat  
these comments just like any other last call comments.

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.  That is, the "analysis" appears to be  
limited to a particular concern.  Is this the only concern?
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).
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