Skip to main content

Unsigned RRsets in Secure Zones
draft-arends-dnsext-rrsets-00

Document Type Expired Internet-Draft (individual)
Author Roy Arends
Last updated 2001-07-11
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text htmlized pdfized bibtex
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 can be found at:
https://www.ietf.org/archive/id/draft-arends-dnsext-rrsets-00.txt

Abstract

In order for DNSSEC to be deployed operationally, there needs to be a mechanism that allows for unsigned RRsets in a secure zone. In the current definition of DNSSEC [RFC 2535], it is allowed to have 2 types of unsigned records, i.e. glue address RRsets and delegation point NS RRsets. There exists several reasons to allow other unsigned RRsets, all related to the scalability and maintenance of a secure zone.

Authors

Roy Arends

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