RFC 4213 on Basic Transition Mechanisms for IPv6 Hosts and Routers

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

 



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


        RFC 4213

        Title:      Basic Transition Mechanisms for IPv6 Hosts and
                    Routers
        Author(s):  E. Nordmark, R. Gilligan
        Status:     Standards Track
        Date:       October 2005
        Mailbox:    erik.nordmark@sun.com, bob.gilligan@acm.org
        Pages:      27
        Characters: 58575
        Obsoletes:  2893

        I-D Tag:    draft-ietf-v6ops-mech-v2-07.txt

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


This document specifies IPv4 compatibility mechanisms that can be
implemented by IPv6 hosts and routers.  Two mechanisms are specified,
dual stack and configured tunneling.  Dual stack implies providing
complete implementations of both versions of the Internet Protocol
(IPv4 and IPv6), and configured tunneling provides a means to carry
IPv6 packets over unmodified IPv4 routing infrastructures.

This document obsoletes RFC 2893.

This document is a product of the IPv6 Operations Working Group of the
IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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.

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/rfc4213.txt>
_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux