Algorithm Implementation Requirements and Usage Guidance for DNSSEC
RFC 8624
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2025-06-03
|
(System) | Received changes through RFC Editor sync (removed Errata tag (all errata rejected)) |
|
2020-07-11
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2019-08-26
|
Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events' |
|
2019-08-26
|
Gunter Van de Velde | Assignment of request for Last Call review by OPSDIR to Qin Wu was marked no-response |
|
2019-06-11
|
(System) | Received changes through RFC Editor sync (created alias RFC 8624, changed abstract to 'The DNSSEC protocol makes use of various cryptographic algorithms in order … Received changes through RFC Editor sync (created alias RFC 8624, changed abstract to 'The DNSSEC protocol makes use of various cryptographic algorithms in order to provide authentication of DNS data and proof of nonexistence. To ensure interoperability between DNS resolvers and DNS authoritative servers, it is necessary to specify a set of algorithm implementation requirements and usage guidelines to ensure that there is at least one algorithm that all implementations support. This document defines the current algorithm implementation requirements and usage guidance for DNSSEC. This document obsoletes RFC 6944.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-06-11, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-dnsop-algorithm-update and RFC 6944) |
|
2019-06-11
|
(System) | RFC published |