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

RFC3178: IPv6 Multihoming Support at Site Exit Routers



	FYI.

itojun



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


        RFC 3178

        Title:	    IPv6 Multihoming Support at Site Exit Routers
        Author(s):  J. Hagino, H. Snyder
        Status:     Informational
	Date:       October 2001
        Mailbox:    itojun@iijlab.net, hal@vailsys.com
        Pages:      12
        Characters: 24453
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-ipngwg-ipv6-2260-02.txt

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


The document describes a mechanism for basic IPv6 multihoming support,
and its operational requirements.  Unlike currently-practiced IPv4
multihoming, the technique does not impact the worldwide routing table
size, nor IGP (Interior Gateway Protocol) routing table size in
upstream ISPs.  The mechanism can be combined with more sophisticated
(or complex) multihoming support mechanisms, and can be used as a
foundation for other mechanisms.  The document is largely based on RFC
2260 by Tony Bates.

This document is a product of the IPNG 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.
<ftp://ftp.isi.edu/in-notes/rfc3178.txt>
Content-type: text/plain