[secdir] secdir Review of draft-ietf-pana-preauth-08

"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> Wed, 20 January 2010 19:36 UTC

Return-Path: <jsalowey@cisco.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 BD01C3A681D; Wed, 20 Jan 2010 11:36:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.984
X-Spam-Level:
X-Spam-Status: No, score=-9.984 tagged_above=-999 required=5 tests=[AWL=0.615, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 6PGCnUBtm-W1; Wed, 20 Jan 2010 11:36:54 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id D158B3A67AA; Wed, 20 Jan 2010 11:36:54 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEACrqVkurRN+K/2dsb2JhbADFUZVkhDYE
X-IronPort-AV: E=Sophos;i="4.49,312,1262563200"; d="scan'208";a="77057371"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 20 Jan 2010 19:36:51 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o0KJaoEF013951; Wed, 20 Jan 2010 19:36:51 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 20 Jan 2010 11:36:50 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Jan 2010 11:36:49 -0800
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE50971A98A@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: secdir Review of draft-ietf-pana-preauth-08
Thread-Index: AcqaB+ivLuYfxyn5SqyKWg++bb7fJg==
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: secdir@ietf.org, iesg@ietf.org, draft-ietf-pana-preauth@tools.ietf.org, pana-chairs@tools.ietf.org
X-OriginalArrivalTime: 20 Jan 2010 19:36:50.0924 (UTC) FILETIME=[E9AB32C0:01CA9A07]
Subject: [secdir] secdir Review of draft-ietf-pana-preauth-08
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: Wed, 20 Jan 2010 19:36:55 -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 as
comments just like any other last call comments.  I apologize for the
late review.  

I did not find any major issues with the document.  The security
considerations section does describe the additional DOS threat
associated with the operation of the protocol.  I think the potential
mitigations could be described better.  1) it seems that the stateless
PCI should be moved up in the section since it is related to the last
sentence of the first paragraph. 2) it's not clear that "authorized" is
the best word to use here since authentication has not completed yet.
It might be better to say "It is recommended that messages are only
accepted from PACs originating from well known IP networks for a given
PAA."  It's not really clear how effective or practical this restriction
would be, but I'm not very familiar with PANA deployments.  

Cheers,

Joe