< draft-ietf-dnsop-dnssec-iana-cons-03.txt		draft-ietf-dnsop-dnssec-iana-cons-04.txt >
	Network Working Group P. Hoffman		Network Working Group P. Hoffman
	Internet-Draft ICANN		Internet-Draft ICANN
	Updates: 5155, 6014, 8624 (if approved) 16 September 2021		Updates: 5155, 6014, 8624 (if approved) 16 September 2021
	Intended status: Standards Track		Intended status: Standards Track
	Expires: 20 March 2022		Expires: 20 March 2022
	Revised IANA Considerations for DNSSEC		Revised IANA Considerations for DNSSEC
	draft-ietf-dnsop-dnssec-iana-cons-03		draft-ietf-dnsop-dnssec-iana-cons-04
	Abstract		Abstract
	This document changes the review requirements needed to get DNSSEC		This document changes the review requirements needed to get DNSSEC
	algorithms and resource records added to IANA registries. It updates		algorithms and resource records added to IANA registries. It updates
	RFC 6014 to include hash algorithms for DS records and NSEC3		RFC 6014 to include hash algorithms for DS records and NSEC3
	parameters. It also updates RFC 5155 and RFC 6014, which have		parameters. It also updates RFC 5155 and RFC 6014, which have
	requirements for DNSSEC algorithms, and updates RFC 8624 to say that		requirements for DNSSEC algorithms, and updates RFC 8624 to say that
	algorithms that are described in RFCs that are not on standards track		algorithms that are described in RFCs that are not on standards track
	are only at the "MAY" level of implementation recommendation. The		are only at the "MAY" level of implementation recommendation. The
	skipping to change at page 2, line 31 ¶		skipping to change at page 2, line 31 ¶
	Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 5		Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 5
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
	1. Introduction		1. Introduction
	DNSSEC is primarily described in [RFC4033], [RFC4034], and [RFC4035].		DNSSEC is primarily described in [RFC4033], [RFC4034], and [RFC4035].
	DNSSEC commonly uses two resource records beyond those defined in RFC		DNSSEC commonly uses two resource records beyond those defined in RFC
	4034: DS [RFC3658] (which was obsoleted by RFC 4034) and NSEC3		4034: DS [RFC3658] (which was obsoleted by RFC 4034) and NSEC3
	[RFC5155].		[RFC5155].
	[RFC8126] gives guidelines for listing in the myriad IANA registries.
	[RFC6014] updated the requirements for how DNSSEC cryptographic		[RFC6014] updated the requirements for how DNSSEC cryptographic
	algorithm identifiers in the IANA registries are assigned, reducing		algorithm identifiers in the IANA registries are assigned, reducing
	the requirements from being "Standards Action" to "RFC Required".		the requirements from being "Standards Action" to "RFC Required".
	However, the IANA registry requirements for hash algorithms for DS		However, the IANA registry requirements for hash algorithms for DS
	records [RFC3658] and for the hash algorithms used in NSEC3 [RFC5155]		records [RFC3658] and for the hash algorithms used in NSEC3 [RFC5155]
	are still "Standards Action". This document updates those IANA		are still "Standards Action". This document updates those IANA
	registry requirements. (For reference on how IANA registries can be		registry requirements. (For reference on how IANA registries can be
	updated in general, see [RFC8126].)		updated in general, see [RFC8126].)
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
End of changes. 2 change blocks.
	3 lines changed or deleted		1 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/