[kitten] Opsdir last call review of draft-ietf-kitten-pkinit-alg-agility-04

Scott Bradner <sob@sobco.com> Sun, 17 February 2019 20:21 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Scott Bradner <sob@sobco.com>
To: ops-dir@ietf.org
Cc: kitten@ietf.org, ietf@ietf.org, draft-ietf-kitten-pkinit-alg-agility.all@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155043488911.4083.7977373920397028733@ietfa.amsl.com>
Date: Sun, 17 Feb 2019 12:21:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/b9V7o2F3G-rs1gFARtamKx1zbxA>
Subject: [kitten] Opsdir last call review of draft-ietf-kitten-pkinit-alg-agility-04

Reviewer: Scott Bradner
Review result: Has Nits

This is an OPS-DIR review of PKINIT Algorithm Agility
(draft-ietf-kitten-pkinit-alg-agility).  This ID updates PKINIT following the
guidelines in BCP 201 to make it algorithm agile and to expose acceptable
algorithms.

This is a very well written clear document.  I do not find any operational
issues with the document except that the document could use a section on
interoperability (old server-new client, new server-old client).

There are a few words about the topic deep in section 6 about the supportedKDFs
field but I do not see a general discussion or a discussion about the kdf
field. The text about the supportedKDFs field could be moved to a new section
and each of the old/new combinations could be addressed.  I see this as an
operational issue because compatibility issues are a frequent source of
operational headaches.

[kitten] Opsdir last call review of draft-ietf-ki… Scott Bradner
[kitten] resend: [OPS-DIR] Opsdir last call revie… Scott Bradner
Re: [kitten] resend: [OPS-DIR] Opsdir last call r… Benjamin Kaduk
Re: [kitten] Opsdir last call review of draft-iet… Benjamin Kaduk
Re: [kitten] Opsdir last call review of draft-iet… Scott Bradner