DNSSEC Roadblock Avoidance
RFC 8027
also known as BCP 207
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2023-12-12
|
(System) | Imported membership of rfc8027 in bcp207 via sync to the rfc-index |
|
2023-12-12
|
(System) | No history of BCP207 is currently available in the datatracker before this point |
|
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2016-12-05
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2016-11-28
|
(System) | Received changes through RFC Editor sync (created alias RFC 8027, changed abstract to 'This document describes problems that a Validating DNS resolver, stub-resolver, or … Received changes through RFC Editor sync (created alias RFC 8027, changed abstract to 'This document describes problems that a Validating DNS resolver, stub-resolver, or application might run into within a non-compliant infrastructure. It outlines potential detection and mitigation techniques. The scope of the document is to create a shared approach to detect and overcome network issues that a DNSSEC software/system may face.', changed pages to 19, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2016-11-28, changed IESG state to RFC Published, created alias BCP 207) |
|
2016-11-28
|
(System) | RFC published |