RFC 6866: Problem Statement for Renumbering IPv6 Hosts with Static Addresses in Enterprise Networks
In plain English — editorial summary, not part of the RFC
This document analyses the problems of updating the IPv6 addresses of hosts in enterprise networks that, for operational reasons, require static addresses.
Document record
- Document ID
- RFC6866
- Published
- February 2013
- Authors
- B. Carpenter; S. Jiang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 11
- 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 6879IPv6 Enterprise Network Renumbering Scenarios, Considerations, and MethodsCurrent
February 2013
- RFC 6883IPv6 Guidance for Internet Content Providers and Application Service ProvidersCurrent
March 2013
- RFC 6841A Framework for DNSSEC Policies and DNSSEC Practice StatementsCurrent
January 2013
- RFC 6894Methodology for Benchmarking MPLS Traffic Engineered (MPLS-TE) Fast Reroute ProtectionCurrent
March 2013
- RFC 6820Address Resolution Problems in Large Data Center NetworksCurrent
January 2013
- RFC 6815Applicability Statement for RFC 2544: Use on Production Networks Considered HarmfulCurrent
November 2012
- RFC 6808Test Plan and Results Supporting Advancement of RFC 2679 on the Standards TrackCurrent
December 2012
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?