[Lwip] Secdir last call review of draft-ietf-lwig-curve-representations-12

Russ Housley via Datatracker <noreply@ietf.org> Thu, 27 August 2020 19:35 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Russ Housley via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: last-call@ietf.org, lwip@ietf.org, draft-ietf-lwig-curve-representations.all@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <159855690603.24456.6910199800419438393@ietfa.amsl.com>
Reply-To: Russ Housley <housley@vigilsec.com>
Date: Thu, 27 Aug 2020 12:35:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/MOkTFhQyh-RNrTI-guN0Vlq2Wdc>
Subject: [Lwip] Secdir last call review of draft-ietf-lwig-curve-representations-12

Reviewer: Russ Housley
Review result: Ready

I 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 authors, document editors, and WG chairs should
treat these comments just like any other IETF Last Call comments.

Document: draft-ietf-lwig-curve-representations-12
Reviewer: Russ Housley
Review Date: 2020-08-27
IETF LC End Date: 2020-09-08
IESG Telechat date: unknown

Thank you for addressing my earlier comments on -08.

Summary: Ready


Major Concerns:  None


Minor Concerns:  None


Nits:

The Introduction talks about the traditional "short" Weierstrass curve
model, and then most everywhere else talks about short-Weierstrass form.
Can one phrase be used throughout?


Question:

Is support for these curves with in PKIX certificates (see RFC 5280
and RFC 5480) and CMS (see RFC 5652 and RFC 5753) as simple as
assigning an object identifier for the two named curves?  If so, can
Section 10 be expanded to cover these too?

[Lwip] Secdir last call review of draft-ietf-lwig… Russ Housley via Datatracker