Multi-Signer DNSSEC Models
RFC 8901
Revision differences
Document history
Date | By | Action |
---|---|---|
2022-03-31
|
Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events' |
2020-09-24
|
(System) | Received changes through RFC Editor sync (created alias RFC 8901, changed title to 'Multi-Signer DNSSEC Models', changed abstract to 'Many enterprises today employ the … Received changes through RFC Editor sync (created alias RFC 8901, changed title to 'Multi-Signer DNSSEC Models', changed abstract to 'Many enterprises today employ the service of multiple DNS providers to distribute their authoritative DNS service. Deploying DNSSEC in such an environment may present some challenges, depending on the configuration and feature set in use. In particular, when each DNS provider independently signs zone data with their own keys, additional key-management mechanisms are necessary. This document presents deployment models that accommodate this scenario and describes these key-management requirements. These models do not require any changes to the behavior of validating resolvers, nor do they impose the new key-management requirements on authoritative servers not involved in multi-signer configurations.', changed pages to 13, changed standardization level to Informational, changed state to RFC, added RFC published event at 2020-09-24, changed IESG state to RFC Published) |
2020-09-24
|
(System) | RFC published |