[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(ngtrans) RFC 3142 on IPv6-to-IPv4 Transport Relay Translator




A new Request for Comments is now available in online RFC libraries.


        RFC 3142

        Title:	    An IPv6-to-IPv4 Transport Relay Translator
        Author(s):  J. Hagino, K. Yamamoto
        Status:     Informational
	Date:       June 2001
        Mailbox:    itojun@iijlab.net, kazu@iijlab.net
        Pages:      11
        Characters: 20864
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ngtrans-tcpudp-relay-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3142.txt


The document describes an IPv6-to-IPv4 transport relay translator
(TRT).  It enables IPv6-only hosts to exchange {TCP,UDP} traffic with
IPv4-only hosts.  A TRT system, which locates in the middle,
translates {TCP,UDP}/IPv6 to {TCP,UDP}/IPv4, or vice versa.

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. 
 
The memo talks about how to implement a TRT system using existing
technologies.  It does not define any new protocols.

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.
<ftp://ftp.isi.edu/in-notes/rfc3142.txt>
Content-type: text/plain