One document matched: draft-ietf-ngtrans-bis-00.txt

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


        RFC 2767

        Title:      Dual Stack Hosts using the "Bump-In-the-Stack"
                    Technique (BIS)
        Author(s):  K. Tsuchiya, H. Higuchi, Y. Atarashi
        Status:     Informational
        Date:       February 2000
        Mailbox:    tsuchi@ebina.hitachi.co.jp,
                    h-higuti@ebina.hitachi.co.jp,
                    atarashi@ebina.hitachi.co.jp 
        Pages:      13
        Characters: 26402
        Updates/Obsoletes/SeeAlso: None
        I-D Tag:    draft-ietf-ngtrans-bis-00.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2767.txt


In the especially initial stage of the transition from IPv4 to
IPv6, it is hard to provide a complete set of IPv6 applications.
This memo proposes a mechanism of dual stack hosts using the technique
called "Bump-in-the-Stack" in the IP security area. The
mechanism allows the hosts to communicate with other IPv6 hosts
using existing IPv4 applications.

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.