DNS Perimeter Overlay
draft-dcrocker-dns-perimeter-00

The information below is for an old version of the document
Document Type None Internet-Draft (individual)
Last updated 2019-04-02
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Additional URLs
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Unknown state
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-dcrocker-dns-perimeter-00.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

Dave Crocker (dcrocker@bbiw.net)
T. Adams (tadams@proofpoint.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)