[secdir] secdir review of draft-ietf-sidr-rfc6485bis

Sean Turner <sean@sn3rd.com> Thu, 22 October 2015 15:57 UTC

From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <70786949-BB2E-4429-A436-EB7940EEE594@sn3rd.com>
Date: Thu, 22 Oct 2015 11:57:45 -0400
To: secdir@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-sidr-rfc6485bis.all@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Archived-At: <http://mailarchive.ietf.org/arch/msg/secdir/jU8NQhcFRy6vGio5hjS1x71Ebik>
Subject: [secdir] secdir review of draft-ietf-sidr-rfc6485bis
Precedence: list

Fear not as this is just the secdir review!

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 with the intent of improving security requirements and considerations in IETF drafts. Comments not addressed in last call may be included in AD reviews during the IESG review.  Document editors and WG chairs should treat these comments just like any other last call comments.

draft summary: This bis document specifies crypto/CMS-related “stuff” for RPKI subscribers and relying parties: signature and hash algorithm parameters, public key formats, etc.  It doesn’t define new algorithms it just says use these values from these other RFCs in this field or that field.  The authors made it really easy for reviewers in that they included a list of all of the changes since RFC6485 in s8; thanks for that.  There’s a few DOWNREFs in the draft, but they are all referenced in the IETF LC and I have no problem with the new one; two were already in the DOWNREF registry.

secdir summary: We are go for launch! (i.e., ready)

nit: There’s a stray “/>” in s6, but the RFC editor can fix that up.

spt

[secdir] secdir review of draft-ietf-sidr-rfc6485… Sean Turner