The IESG has received a request from the Domain Name System Operations WG (dnsop) to consider the following document: - 'DNSSEC Cryptographic Algorithm Recommendation Update Process' <draft-ietf-dnsop-rfc8624-bis-08.txt> as Proposed Standard
*** The IETF Last Call period is extended until the 16th of March as the intended status has changed from "informational" to "proposed standard".*** The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the [email protected] mailing lists by 2025-03-16. Exceptionally, comments may be sent to [email protected] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The DNSSEC protocol makes use of various cryptographic algorithms to provide authentication of DNS data and proof of non-existence. To ensure interoperability between DNS resolvers and DNS authoritative servers, it is necessary to specify both a set of algorithm implementation requirements and usage guidelines to ensure that there is at least one algorithm that all implementations support. This document updates RFC8624 by moving the canonical source of algorithm implementation requirements and usage guidance for DNSSEC from RFC8624 to an IANA registry. This is done both to allow the list to be more easily updated, and to allow the list to be more easily referenced. Future extensions to this registry can be made under new, incremental update RFCs. The document does not change the status (MUST, MAY, RECOMMENDED, etc) of any of the algorithms listed in RFC8624; that is the work of future documents. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc8624-bis/ No IPR declarations have been submitted directly on this I-D. _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
