The DELEGATION_ONLY DNSKEY flag
draft-pwouters-powerbind-04

Document Type Replaced Internet-Draft (dnsop WG)
Last updated 2020-05-04 (latest revision 2020-04-30)
Replaced by draft-ietf-dnsop-delegation-only
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-dnsop-delegation-only
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-pwouters-powerbind-04.txt

Abstract

This document introduces a new DNSKEY flag called DELEGATION_ONLY that indicates that the particular zone will never sign zone data across a label. That is, every label (dot) underneath is considered a zone cut and must have its own (signed) delegation. Additionally, it indicates the zone is expecting its parent to never bypass or override the zone. DNSSEC Validating Resolvers can use this flag to mark any data that violates the DELEGATION_ONLY policy as BOGUS.

Authors

Paul Wouters (pwouters@redhat.com)
Wes Hardaker (ietf@hardakers.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)