Some Considerations on the Use of Domain Names Outside of the Global Public Domain Name System
draft-stw-whatsinaname-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Suzanne Woolf | ||
| Last updated | 2018-09-06 (Latest revision 2018-03-05) | ||
| 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
From time to time, networking protocols need to be able to name things used within the protocol, and resolve the names created or referenced. It's common for protocol designers to attempt to use domain names as the starting point for their systems of names, and the DNS protocol as the starting point for name resolution. Such re- use of DNS naming and resolution conventions can cause issues if not carefully defined and handled, as applications and infrastructure in the modern Internet tend to assume that a "domain name" is an identifier that follows certain composition and allocation rules and is to be resolved by DNS protocol in the global default scope. This document acknowledges this class of extensions to the shared domain namespace and considers a framework for the properties a naming and resolution convention should have in the internet protocol environment, including the avoidance of collision with other uses of the namespace. Depending to the answers to the suggested questions, the answer may be that domain names will not meet the constraints at hand.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)