Asserting DNS Administrative Boundaries Within DNS Zones
draft-sullivan-domain-origin-assert-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Andrew Sullivan | ||
| Last updated | 2013-07-05 (Latest revision 2012-10-22) | ||
| Replaces | draft-sullivan-zone-policy-assertions | ||
| Replaced by | draft-sullivan-domain-policy-authority | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-sullivan-domain-policy-authority | |
| 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
Some clients on the Internet make inferences about the administrative relationships among servers on the Internet based on the domain names of those servers. Perhaps unfortunately, it is not currently possible to detect the real administrative boundaries in the DNS, and therefore such inferences can go wrong in several ways. Mitigation strategies deployed so far will not scale. The solution to this is to provide a way to make an explicit assertion about the relationships between different domain names and perhaps the services provided at them.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)