(ngtrans) CORRECTED: RFC 3089 on SOCKS-based IPv6/IPv4 Gateway Mechanism
RFC Editor <rfc-ed@ISI.EDU> Thu, 03 May 2001 16:55 UTC
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA00069 for <ngtrans-archive@odin.ietf.org>; Thu, 3 May 2001 12:55:10 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA00566; Thu, 3 May 2001 09:54:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA05816; Thu, 3 May 2001 09:53:12 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1]) by sunroof.eng.sun.com (8.12.0.Beta8+Sun/8.12.0.Beta8) with ESMTP id f43Gq0IM006580 for <ngtrans-dist@sunroof.eng.sun.com>; Thu, 3 May 2001 09:52:00 -0700 (PDT)
Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.12.0.Beta8+Sun/8.12.0.Beta8) id f43Gpx9j006579 for ngtrans-dist; Thu, 3 May 2001 09:51:59 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6]) by sunroof.eng.sun.com (8.12.0.Beta8+Sun/8.12.0.Beta8) with ESMTP id f43GpmIM006572 for <ngtrans@sunroof.eng.sun.com>; Thu, 3 May 2001 09:51:49 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43]) by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL, v2.1p1) with ESMTP id JAA13352 for <ngtrans@sunroof.eng.sun.com>; Thu, 3 May 2001 09:51:48 -0700 (PDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA27990 for <ngtrans@sunroof.eng.sun.com>; Thu, 3 May 2001 09:51:46 -0700 (PDT)
Received: from jet.isi.edu (jet.isi.edu [128.9.160.87]) by tnt.isi.edu (8.11.2/8.11.2) with ESMTP id f43GpkP28570; Thu, 3 May 2001 09:51:46 -0700 (PDT)
From: RFC Editor <rfc-ed@ISI.EDU>
Received: (from rfc-ed@localhost) by jet.isi.edu (8.8.7/8.8.6) id JAA24194; Thu, 3 May 2001 09:51:46 -0700 (PDT)
Date: Thu, 03 May 2001 09:51:46 -0700
Message-Id: <200105031651.JAA24194@jet.isi.edu>
To: IETF-Announce: all-ietf@ietf.org;
Subject: (ngtrans) CORRECTED: RFC 3089 on SOCKS-based IPv6/IPv4 Gateway Mechanism
Cc: rfc-ed@ISI.EDU, ngtrans@sunroof.eng.sun.com
Content-Type: X-sun-attachment
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: RFC Editor <rfc-ed@ISI.EDU>
---------- X-Sun-Data-Type: text X-Sun-Data-Description: text X-Sun-Data-Name: text X-Sun-Charset: us-ascii X-Sun-Content-Lines: 77 A new Request for Comments is now available in online RFC libraries. RFC 3089 Title: A SOCKS-based IPv6/IPv4 Gateway Mechanism Author(s): H. Kitamura Status: Informational Date: April 2001 Mailbox: kitamura@da.jp.nec.com Pages: 12 Characters: 25193 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ngtrans-socks-gateway-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3089.txt This document describes a SOCKS-based IPv6/IPv4 gateway mechanism that enables smooth heterogeneous communications between the IPv6 nodes and IPv4 nodes. It is based on the SOCKS protocol. By applying the SOCKS mechanism to the heterogeneous communications and relaying two "terminated" IPv4 and IPv6 connections at the "application layer" (the SOCKS server), the SOCKS-based IPv6/IPv4 gateway mechanism is accomplished. Since it is accomplished without introducing new protocols, it provides the same communication environment that is provided by the SOCKS mechanism. The same appearance is provided to the heterogeneous communications. No conveniences or functionalities of current communications are sacrificed. This document is a product of the Next Generation Transition Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ----- End Included Message ----- ---------- X-Sun-Data-Type: Multipart X-Sun-Content-Length: 490 X-Sun-Content-Lines: 22 X-Sun-Charset: us-ascii --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <010503084113.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3099 --OtherAccess Content-Type: Message/External-body; name="rfc3099.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <010503084113.RFC@RFC-EDITOR.ORG> --OtherAccess--