RFC 6879: IPv6 Enterprise Network Renumbering Scenarios, Considerations, and Methods
In plain English — editorial summary, not part of the RFC
This document analyzes events that cause renumbering and describes the current renumbering methods. These are described in three categories: those applicable during network design, those applicable during preparation for renumbering, and those applicable during the renumbering operation.
Document record
- Document ID
- RFC6879
- Published
- February 2013
- Authors
- S. Jiang; B. Liu; B. Carpenter
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 17
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6877464XLAT: Combination of Stateful and Stateless TranslationCurrent
April 2013
- RFC 6883IPv6 Guidance for Internet Content Providers and Application Service ProvidersCurrent
March 2013
- RFC 6866Problem Statement for Renumbering IPv6 Hosts with Static Addresses in Enterprise NetworksCurrent
February 2013
- RFC 6894Methodology for Benchmarking MPLS Traffic Engineered (MPLS-TE) Fast Reroute ProtectionCurrent
March 2013
- RFC 6841A Framework for DNSSEC Policies and DNSSEC Practice StatementsCurrent
January 2013
- RFC 6933Entity MIB (Version 4)Current
May 2013
- RFC 6820Address Resolution Problems in Large Data Center NetworksCurrent
January 2013
- RFC 6942Diameter Support for the EAP Re-authentication Protocol (ERP)Current
May 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?