Coping with IP Address Literals in HTTP URIs with IPv6/IPv4 Translators
draft-wing-behave-http-ip-address-literals-02

Document Type Expired Internet-Draft (individual)
Last updated 2010-03-06
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
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-wing-behave-http-ip-address-literals-02.txt

Abstract

A small percentage of HTTP URIs contain an IPv4 address literal as the hostname which is not accessible to IPv6-only HTTP clients using an IPv6/IPv4 translator and DNS64. This document proposes a workaround for this problem using an HTTP proxy to handle that traffic.

Authors

Dan Wing (dwing@cisco.com)

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