Publishing Organization Boundaries in the DNS
draft-levine-orgboundary-02
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | John R. Levine | ||
| Last updated | 2014-02-01 (Latest revision 2013-07-31) | ||
| Replaced by | draft-levine-dbound-dns, draft-levine-dbound-dns | ||
| RFC stream | (None) | ||
| Formats | |||
| 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 is available in these formats:
Abstract
Often, the organization that manages a subtree in the DNS is different from the one that manages the tree above it. Rather than describing a particular design, we describe an architecture to publish in the DNS the boundaries between organizations that can be adapted to various policy models.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)