NSEC(3) TTLs and NSEC Aggressive Use
draft-vandijk-dnsop-nsec-ttl-00
| Document | Type | Replaced Internet-Draft (dnsop WG) | |
|---|---|---|---|
| Author | Peter van Dijk | ||
| Last updated | 2021-01-06 (Latest revision 2020-11-23) | ||
| Replaced by | RFC 9077 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dnsop-nsec-ttl | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Due to a combination of unfortunate wording in earlier documents, aggressive use of NSEC(3) records may deny names far beyond the intended lifetime of a denial. This document changes the definition of the NSEC(3) TTL to correct that situation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)