Re: [secdir] secdir review of draft-hollenbeck-rfc4932bis-01

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 01 June 2009 19:42 UTC

Return-Path: <alexey.melnikov@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 856383A6A19; Mon, 1 Jun 2009 12:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level:
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325, 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 3ZGu8IGdDjwK; Mon, 1 Jun 2009 12:42:44 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id A92803A68C4; Mon, 1 Jun 2009 12:42:44 -0700 (PDT)
Received: from [172.16.2.178] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <SiQvMgAh5C1k@rufus.isode.com>; Mon, 1 Jun 2009 20:42:43 +0100
Message-ID: <4A242EEF.3050508@isode.com>
Date: Mon, 01 Jun 2009 20:41:35 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Chris Lonvick <clonvick@cisco.com>
References: <Pine.GSO.4.63.0906011152370.13437@sjc-cde-011.cisco.com>
In-Reply-To: <Pine.GSO.4.63.0906011152370.13437@sjc-cde-011.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: shollenbeck@verisign.com, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] secdir review of draft-hollenbeck-rfc4932bis-01
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, 01 Jun 2009 19:42:45 -0000

Chris Lonvick wrote:

> Hi,
>
> 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.
>
> I found security-related problems in my review of the document.

Chris,
Can you be more specific?

> I did see, however, that the Security Considerations, which point back 
> to ID 4930.bis, are very similar to the security considerations in RFC 
> 4930.  They hint that a secure transport is needed to thwart common 
> mitm attacks but the section does not give any specific guidance.

> It has been two years since RFC 4930 was published.  Have any secure 
> transports been used?  If so, I think it would be a good idea to state 
> which one(s) and how its attributes do thwart the threats.

See draft-hollenbeck-rfc4934bis-01.txt