DNS Perimeter Overlay
draft-dcrocker-dns-perimeter-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Dave Crocker , J. Trent Adams | ||
| Last updated | 2019-12-13 (Latest revision 2019-06-11) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-dcrocker-dns-perimeter-01.txt
Abstract
The Domain Name System (DNS) naming syntax provides no meta-data for indicating administrative transitions through the hierarchy. For example, it does not distinguish the higher-level portions that operate as public registries, versus those that operate as private organizations. This specification creates a basic overlay mechanism for defining a logical Perimeter between administrative entities through the naming hierarchy. The mechanism can then be applied for a variety of independent administrative indications.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)