A SOCKS-based IPv6/IPv4 Translator Architecture
draft-kitamura-socks-ipv6-trans-arch-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Hiroshi Kitamura | ||
| Last updated | 1998-11-16 | ||
| 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
This document describes an IPv6/IPv4 Translator architecture that is based on the SOCKSv5 [RFC1928] mechanism. In this architecture, the SOCKS mechanism is extended by adding adaptive address family distinguish functions for supporting heterogeneous communications. By applying the mechanism together with protocol conversion functions, the IPv6/IPv4 Translator architecture is accomplished. This Translator provides communications between IPv6 and IPv4 nodes without sacrificing any convenience and functionalities of current communication methods. It is NOT necessary to modify the current DNS system at all. Only socksify environment is needed to communicate between IPv6 and IPv4 nodes. By using multiple chained Translators, a tunneling-like communication topology can be realized. With the architecture, there is no vulnerability of the packet fragmentation, and the connection can be authenticated by the native SOCKS authentication methods.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)