IPv4 Address Literal in URL
draft-osamu-v6ops-ipv4-literal-in-url-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Osamu Nakamura , Hiroaki Hazeyama , Yukito Ueno , Akira Kato | ||
| Last updated | 2014-01-10 (Latest revision 2013-07-09) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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 discusses a few methods to rewrite the URL on an IPv6-only host so that the URL is accessible from the IPv6-only host.
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.)