Re: [secdir] secdir review of draft-ietf-lamps-rfc5280-i18n-update

Russ Housley <housley@vigilsec.com> Thu, 12 October 2017 07:34 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03BDF133072 for <secdir@ietfa.amsl.com>; Thu, 12 Oct 2017 00:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0ByBWsala6k for <secdir@ietfa.amsl.com>; Thu, 12 Oct 2017 00:34:21 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2355133052 for <secdir@ietf.org>; Thu, 12 Oct 2017 00:34:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 48E2A3005A6 for <secdir@ietf.org>; Thu, 12 Oct 2017 03:34:20 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id zh257SWsVlAw for <secdir@ietf.org>; Thu, 12 Oct 2017 03:34:18 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id B538B3004BC; Thu, 12 Oct 2017 03:34:18 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <ldva80xko8z.fsf@ubuntu-1gb-nyc1-01.localdomain>
Date: Thu, 12 Oct 2017 03:34:17 -0400
Cc: IESG <iesg@ietf.org>, IETF SecDir <secdir@ietf.org>, draft-ietf-lamps-rfc5280-i18n-update.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF352B68-F318-498C-8E17-615D99E684D7@vigilsec.com>
References: <ldva80xko8z.fsf@ubuntu-1gb-nyc1-01.localdomain>
To: Taylor Yu <tlyu@mit.edu>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/A0kg-w_rzzlT7dECi8B2UPaSwUM>
Subject: Re: [secdir] secdir review of draft-ietf-lamps-rfc5280-i18n-update
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 12 Oct 2017 07:34:22 -0000

Okay.  Thanks for the review.  I will move the references to the normative list.

Russ


> On Oct 12, 2017, at 12:02 AM, Taylor Yu <tlyu@mit.edu> wrote:
> 
> 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 summary of the review is: Ready with Nits.
> 
> This seems to be a useful incremental improvement to RFC 5280.  The
> Security Considerations seem reasonable.  The nits are minor and can
> likely be resolved as part of the RFC Editor process.
> 
> Nits:
> 
> * RFC3492 is listed as an Informative reference but section 2.3 (which
>  modifies section 7.2 of RFC5280) is normative text that refers to it.
>  (though not using an RFC2199 keyword)  Arguably this might be OK
>  because I think other normative references in this document
>  transitively cite RFC3492.
> 
> * RFC3629 is listed as an Informative reference but the new text in
>  section 2.4 (which modifies section 7.5 of RFC5280) appears to refer
>  to it normatively (about BOMs).
> 
> Best regards,
> -Taylor