Internet DRAFT - draft-ietf-ngtrans-6to4anycast

draft-ietf-ngtrans-6to4anycast



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


        RFC 3068

        Title:      An Anycast Prefix for 6to4 Relay Routers
        Author(s):  C. Huitema
        Status:     Standards Track
        Date:       June 2001
        Mailbox:    huitema@exchange.microsoft.com
        Pages:      9
        Characters: 20120
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ngtrans-6to4anycast-03.txt

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


This memo introduces a "6to4 anycast address" in order to simplify the
configuration of 6to4 routers.  It also defines how this address will
be used by 6to4 relay routers, how the corresponding "6to4 anycast
prefix" will be advertised in the IGP and in the EGP.  The memo
documents the reservation by IANA (Internet Assigned Numbers
Authority) of the "6to4 relay anycast prefix."

This document is a product of the Next Generation Transistion 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.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.