The DELEGATION_ONLY DNSKEY flag
draft-pwouters-powerbind-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Paul Wouters , Wes Hardaker | ||
| Last updated | 2019-09-11 (Latest revision 2019-03-10) | ||
| Replaced by | draft-ietf-dnsop-delegation-only | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
This document introduces a new DNSKEY flag called DELEGATION_ONLY that indicates that the particular zone will never sign zone data aside from records at the apex of the zone or delegation records for its children. That is, every label (dot) underneath is considered a zone cut and must have its own (signed) delegation. DNSSEC Validating Resolvers can use this bit to mark any data that violates the DELEGATION_ONLY policy as BOGUS.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)