A Special Purpose TLD to resolve IPv4 Address Literal on DNS64/NAT64 environments
draft-osamu-v6ops-ipv4-literal-in-url-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Osamu Nakamura , Hiroaki Hazeyama , Yukito Ueno , Akira Kato | ||
| Last updated | 2015-04-30 (Latest revision 2014-10-27) | ||
| 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
In an IPv6-only environment with DNS64/NAT64 based translation service, there is no way to get access a URL whose domain name part includes an IPv4 address literal. This memo proposes a special purpose TLD so that the IPv4 address literal is accessible from such a DNS64/NAT64 environments.
Authors
Osamu Nakamura
Hiroaki Hazeyama
Yukito Ueno
Akira Kato
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)