Address-specific DNS Name Redirection (ANAME)
draft-ietf-dnsop-aname-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Evan Hunt , Peter van Dijk , Anthony Eden | ||
| Last updated | 2017-11-28 (Latest revision 2017-05-27) | ||
| Replaces | draft-hunt-dnsop-aname | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Yes | ||
| 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 defines the "ANAME" DNS RR type, to provide similar functionality to CNAME, but only redirects type A and AAAA queries. Unlike CNAME, an ANAME can coexist with other record types. The ANAME RR allows zone owners to redirect queries for apex domain names in a standards compliant manner.
Authors
Evan Hunt
Peter van Dijk
Anthony Eden
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)