Good catch.
Bad job of copy/paste in reformating.
On 11/23/22 02:38, Jürgen Schönwälder
via Datatracker wrote:
Reviewer: Jürgen Schönwälder Review result: Serious Issues This I-D requests to add an entry to the IANA 'Algorithm Type Field' of the 'IPSECKEY Resource Record Parameters' section. It also suggests to augment the description of existing entries. Putting things together, the ID suggests this new content: Value Description Format description Reference 0 No key is present [RFC4025] 1 A DSA Public Key [RFC2536], Sec. 2 [RFC4025] 2 A RSA Public Key [RFC3110], Sec. 2 [RFC4025] 3 An ECDSA Public Key [RFC6605], Sec. 4 [RFC4025] TBD An EdDSA Public Key [RFC8080], Sec. 3 [RFC-TBD] Checking this against the current IANA registry values, I note that the current entry for value 3 has [RFC8005] as a reference while the ID suggests [RFC4025]. Looking at Section 9 of RFC 8005, it seems IANA has this right and the author got it wrong and this should be: Value Description Format description Reference 0 No key is present [RFC4025] 1 A DSA Public Key [RFC2536], Sec. 2 [RFC4025] 2 A RSA Public Key [RFC3110], Sec. 2 [RFC4025] 3 An ECDSA Public Key [RFC6605], Sec. 4 [RFC8005] TBD An EdDSA Public Key [RFC8080], Sec. 3 [RFC-TBD]
--
Robert Moskowitz
Owner
HTT Consulting
C: 248-219-2059
F: 248-968-2824
E: rgm@xxxxxxxxxxxxxxxxxxxx
There's no limit to what can be accomplished if it doesn't matter who gets the credit
Robert Moskowitz
Owner
HTT Consulting
C:
F:
E:
There's no limit to what can be accomplished if it doesn't matter who gets the credit
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
