One document matched: draft-ietf-ipngwg-router-renum-10.txt

Differences from draft-ietf-ipngwg-router-renum-09.txt

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


        RFC 2894

        Title:      Router Renumbering for IPv6
        Author(s):  M. Crawford
        Status:     Standards Track
        Date:       August 2000
        Mailbox:    crawdad@fnal.gov
        Pages:      32
        Characters: 69135
        Obsoletes/Updates/SeeAlso:  None

        I-D Tag:    draft-ietf-ipngwg-router-renum-10.txt

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


IPv6 Neighbor Discovery and Address Autoconfiguration conveniently
make initial assignments of address prefixes to hosts.  Aside from
the problem of connection survival across a renumbering event, these
two mechanisms also simplify the reconfiguration of hosts when the
set of valid prefixes changes.
 
This document defines a mechanism called Router Renumbering ("RR")
which allows address prefixes on routers to be configured and
reconfigured almost as easily as the combination of Neighbor
Discovery and Address Autoconfiguration works for hosts.  It
provides a means for a network manager to make updates to the
prefixes used by and advertised by IPv6 routers throughout a site.

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