IPv6 Site Renumbering
draft-huitema-ipv6-renumber-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Christian Huitema | ||
Last updated | 2001-07-13 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
There has been recently a lot of the discussion in the IPNG, NGTRANS and DNSEXT working group about the level at which IPv6 shall support renumbering. A specific question is whether we need special support in the DNS to enable renumbering, as specified in [RFC2874], or if the simpler mechanisms specified in [RFC1886] are sufficient. In order to organize the discussion, this memo presents a set of realistic renumbering scenarios, discusses the possible frequency at which such scenarios can be repeated, presents some tools that can be used to organize the renumbering, and summarizes the operational requirements that have to be met by any renumbering solution.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)