DNSSEC Resource Record Should Include AAAA
draft-byrne-v6ops-dnssecaaaa-00

Document Type Expired Internet-Draft (individual)
Last updated 2019-01-02 (latest revision 2018-07-01)
Replaces draft-v6ops-byrne-dnssecaaaa
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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-byrne-v6ops-dnssecaaaa-00.txt

Abstract

DNS64 is a widely deployed technology allowing hundreds of millions of IPv6-only hosts to reach IPv4-only resources. DNSSEC is a technology used to validate the authenticity of information in the DNS. Currently, there are scenarios where DNS64 and DNSSEC do not work well together. This document states that any DNSSEC signed resources record should include a native IPv6 resource record as the most complete and expedient path to solve any deployment conflict with DNS64 and DNSSEC.

Authors

Cameron Byrne (cameron.byrne@t-mobile.com)

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