Considerations for establishing resolution contexts for Internet Names
draft-hardie-resolution-contexts-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ted Hardie | ||
| Last updated | 2016-09-08 (Latest revision 2016-03-07) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
If we model the system of Internet names as a set of directed graphs in an absolute naming context, following RFC 819, an Internet name is not necessarily a name in the domain name system, but is simply a unique name associated with a particular directed graph. The resolution of the name, in other words, is independent from it being an "Internet name". The DNS is a common, but not the only, resolution context for Internet names. This document discusses the consequences of the need to select among multiple resolution contexts.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)