CNAME at apex - a website publisher perspective
draft-york-dnsop-cname-at-apex-publisher-view-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-05-10 (latest revision 2018-11-06) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
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-york-dnsop-cname-at-apex-publisher-view-01.txt
https://www.ietf.org/archive/id/draft-york-dnsop-cname-at-apex-publisher-view-01.txt
Abstract
There has been a large amount of discussion about the "CNAME at apex" issue within the DNSOP Working Group. This draft provides the perspective of one publisher of multiple websites about why CNAME- like functionality is desirable at the apex of a domain zone.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)