[Curdle] AD Review: draft-ietf-curdle-pkix-04.txt

[Eric Rescorla <[e-mail]>]

AD Review: draft-ietf-curdle-pkix-04.txt

TECHNICAL
I see that Brian Smith made a number of comments on 4/29. Is the WG
convinced that they have addressed them adequately.

S 5.
The RFC5280 text on {encipher,decipher}Only is kind of obscure.
Say that I have keyAgreement | encipherOnly, can I use this key
for TLS?

   one of the following MAY also be present:

Am I supposed to read from this that no other extension may be
present? I think this should be explicitly stated. The same
applies to signature certificates.

Also, did the WG discuss whether you should mandate keyUsage?


EDITORIAL
S 1.
   HashEdDSA mode with pre-hashing.  The convention used for identifying
   the algorithm/curve combinations are to use the Ed25519 and Ed448 for

convention is

RFC 7748 seems to use "curveXXX" rather than "CurveXXX"


S 4.

    o  subjectPublicKey contains the byte stream of the public key.
      While the encoded public keys for the current algorithms are all
      an even number of octets, future curves could change that.

I know what you mean by "even number" but I think it would be clearer
to say "an exact multiple of 8 bits" so people don't think you are
talking about the parity of the number of bytes.


S 13.
Diffie-Hellman has two ls

-Ekr