Subject: [lamps] Fwd: New Version Notification for draft-mtis-lamps-8410-ku-clarifications-01.txt

From: Sean Turner <[email-masked]>
Date: Wed, 2 Mar 2022 00:06:04 -0500

Hi!

Here are links to the latest version of this I-D. This version includes a refactoring of the text in s3 addressing the KUs for a CA certificate. diffs from -00 to -01 are here:
https://www.ietf.org/rfcdiff?url1=draft-mtis-lamps-8410-ku-clarifications-00&url2=draft-mtis-lamps-8410-ku-clarifications-01 <https://www.ietf.org/rfcdiff?url1=draft-mtis-lamps-8410-ku-clarifications-00&url2=draft-mtis-lamps-8410-ku-clarifications-01>

Cheers,
spt

> Begin forwarded message:
> 
> From: [email-masked]
> Subject: New Version Notification for draft-mtis-lamps-8410-ku-clarifications-01.txt
> Date: March 2, 2022 at 00:03:05 EST
> To: "Daniel McCarney" <[email-masked]>, "Sean Turner" <[email-masked]>, "Simon Josefsson" <[email-masked]>, "Tadahiko Ito" <[email-masked]>
> 
> 
> A new version of I-D, draft-mtis-lamps-8410-ku-clarifications-01.txt
> has been successfully submitted by Sean Turner and posted to the
> IETF repository.
> 
> Name:		draft-mtis-lamps-8410-ku-clarifications
> Revision:	01
> Title:		Clarifications for Ed25519, Ed448, X25519, and X448 Algorithm Identifiers
> Document date:	2022-03-02
> Group:		Individual Submission
> Pages:		5
> URL:            https://www.ietf.org/archive/id/draft-mtis-lamps-8410-ku-clarifications-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-mtis-lamps-8410-ku-clarifications/
> Html:           https://www.ietf.org/archive/id/draft-mtis-lamps-8410-ku-clarifications-01.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-mtis-lamps-8410-ku-clarifications
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-mtis-lamps-8410-ku-clarifications-01
> 
> Abstract:
>   This document updates RFC 8410 to clarify existing and specify
>   missing semantics for key usage bits when used in certificates that
>   support the Ed25519, Ed448, X25519, and X448 Elliptic Curve
>   Cryptography algorithms.
> 
> 
> 
> 
> The IETF Secretariat
> 
>

---

From: Russ Housley <[email-masked]>
Date: Wed, 2 Mar 2022 09:38:47 -0500

Sean:

I think it is clear what you mean, but this is a very awkward sentence:

   If the keyUsage extension is present in a certification authority
   certificate that indicates id-Ed25519 or id-Ed448 in
   SubjectPublicKeyInfo, then the keyUsage extension MUST contain the
   keyUsage extension MUST contain:
I will start the call for adoption.  This can be fixed in a future version.

Russ

> On Mar 2, 2022, at 12:06 AM, Sean Turner <[email-masked]> wrote:
> 
> Hi!
> 
>> From: [email-masked] <mailto:[email-masked]>
>> To: "Daniel McCarney" <[email-masked] <mailto:[email-masked]>>, "Sean Turner" <[email-masked] <mailto:[email-masked]>>, "Simon Josefsson" <[email-masked] <mailto:[email-masked]>>, "Tadahiko Ito" <[email-masked] <mailto:[email-masked]>>
>> 
>> 
>> URL:            https://www.ietf.org/archive/id/draft-mtis-lamps-8410-ku-clarifications-01.txt <https://www.ietf.org/archive/id/draft-mtis-lamps-8410-ku-clarifications-01.txt>
>> Status:         https://datatracker.ietf.org/doc/draft-mtis-lamps-8410-ku-clarifications/ <https://datatracker.ietf.org/doc/draft-mtis-lamps-8410-ku-clarifications/>
>> Html:           https://www.ietf.org/archive/id/draft-mtis-lamps-8410-ku-clarifications-01.html <https://www.ietf.org/archive/id/draft-mtis-lamps-8410-ku-clarifications-01.html>
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-mtis-lamps-8410-ku-clarifications <https://datatracker.ietf.org/doc/html/draft-mtis-lamps-8410-ku-clarifications>
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-mtis-lamps-8410-ku-clarifications-01 <https://www.ietf.org/rfcdiff?url2=draft-mtis-lamps-8410-ku-clarifications-01>
>> 
>> Abstract:
> _______________________________________________
> Spasm mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/spasm

---

From: Sean Turner <[email-masked]>
Date: Wed, 2 Mar 2022 10:04:37 -0500

Yeah that’s a typo:

OLD:

   then the keyUsage extension MUST contain the
   keyUsage extension MUST contain

NEW:

   then the keyUsage extension MUST contain:

spt

> On Mar 2, 2022, at 09:38, Russ Housley <[email-masked]> wrote:
> 
> Sean:
> 
>> https://www.ietf.org/rfcdiff?url1=draft-mtis-lamps-8410-ku-clarifications-00&url2=draft-mtis-lamps-8410-ku-clarifications-01
>> 
>> Cheers,
>> spt
>> 
>>> Begin forwarded message:
>>>

---

From: Sean Turner <[email-masked]>
Date: Wed, 2 Mar 2022 10:12:39 -0500

Fixed here:
https://github.com/seanturner/draft-mtis-lamps-8410-ku-clarifications/pull/3

spt

> On Mar 2, 2022, at 10:04, Sean Turner <[email-masked]> wrote:
> 
> Yeah that’s a typo:
> 
> OLD:
>