Renumbering Still Needs Work

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 35
Abstract: This document reviews the existing mechanisms for site renumbering for both IPv4 and IPv6, and it identifies operational issues with those mechanisms. It also summarises current technical proposals for additional mechanisms. Finally, there is a gap analysis identifying possible areas for future work. This document is not an Internet Standards Track specification; it is published for informational purposes.
Publication Date: 2010-05-01
Status Note: Informational
DOI: 10.17487/RFC5887
Link: https://doi.org/10.17487/RFC5887
Author(s): Brian E. Carpenter
Ran Atkinson
Hannu Flinck

Latest version of IETF RFC 5887

Document Versions — IETF RFC 5887

▶ IETF RFC 5887 (2010-05-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

IEEE.STD802.1X.2004 — IEEE802.1X EXTERNAL
Bernardos, C., Calderon, M., and H. Moustafa, "Ad-Hoc IP Autoconfiguration Solution Space Analysis", Work in Progress, November 2008. EXTERNAL
Leroy, D. and O. Bonaventure, "Preparing network configurations for IPv6 renumbering", International Journal of Network Management, 2009, < http:// inl.info.ucl.ac.be/system/files/dleroy-nem-2009.pdf >. EXTERNAL
Crocker, S., "Renumbering Considered Normal", 2006, < http://www.arin.net/meetings/minutes/ARIN_XVIII/PDF /wednesday/Renumbering_Crocker.pdf >. EXTERNAL
Cheshire, S. and M. Krochmal, "Multicast DNS" , Work in Progress, March 2010. EXTERNAL
Johnson, R., Kumarasamy, J., Kinnear, K., and M. Stapp, "Subnet Allocation Option", Work in Progress, May 2010. EXTERNAL
Sun, T. and H. Deng, "Route Configuration by DHCPv6 Option for Hosts with Multiple Interfaces", Work in Progress, March 2009. EXTERNAL
Institute of Electrical and Electronics Engineers, "802.1X-REV - Revision of 802.1X-2004 - Port Based Network Access Control: IEEE Standard for Local and Metropolitan Area Networks", 2009. EXTERNAL
Bernardos, C., Calderon, M., and H. Moustafa, "Survey of IP address autoconfiguration mechanisms for MANETs", Work in Progress, November 2008. EXTERNAL
Chakeres, I., Macker, J., and T. Clausen, "Mobile Ad hoc Network Architecture", Work in Progress, November 2007. EXTERNAL
Dec, W. and R. Johnson, "DHCPv6 Route Option" , Work in Progress, March 2010. EXTERNAL
Singh, H., Beebee, W., Donley, C., Stark, B., and O. Troan, Ed., "Basic Requirements for IPv6 Customer Edge Routers", Work in Progress, May 2010. EXTERNAL
Atkinson, R., "ILNP Concept of Operations" , Work in Progress, February 2010. EXTERNAL
Wasserman, M. and F. Baker, "IPv6-to-IPv6 Network Address Translation (NAT66)", Work in Progress, March 2009. EXTERNAL
Handley, M., Wischik, D., and M. Bagnulo, "Multipath Transport, Resource Pooling, and implications for Routing", 2008, < http://www.ietf.org/proceedings/08jul/ slides/RRG-2.pdf >. EXTERNAL
Dickinson, J., Morris, S., and R. Arends, "Design for a Nameserver Control Protocol", Work in Protocol, October 2008. EXTERNAL
Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "Locator/ID Separation Protocol (LISP)", Work in Progress, April 2010. EXTERNAL
Vogt, C., "Six/One: A Solution for Routing and Addressing in IPv6", Work in Progress, October 2009. EXTERNAL
Cheshire, S. and M. Krochmal, "DNS-Based Service Discovery", Work in Progress, March 2010. EXTERNAL
Boot, T. and A. Holtzer, "Border Router Discovery Protocol (BRDP) based Address Autoconfiguration", Work in Progress, July 2009. EXTERNAL
Chown, T., "Things to think about when Renumbering an IPv6 network", Work in Progress, September 2006. EXTERNAL
Xie, Q., Stewart, R., Holdrege, M., and M. Tuexen, "SCTP NAT Traversal Considerations", Work in Progress, November 2007. EXTERNAL
Albitz, P. and C. Liu, "DNS and BIND", 5th Edition, O'Reilly, 2006. EXTERNAL
IETF RFC 1332 [Active*]
IETF RFC 1661 [Active*]
IETF RFC 1900 [Active*]
RFC1916 — RFC1916 EXTERNAL
IETF RFC 1918 [Active*]
IETF RFC 1958 [Active*]
IETF RFC 2071 [Active*]
IETF RFC 2072 [Active*]
IETF RFC 2131 [Active*]
IETF RFC 2407 [Superseded*]
IETF RFC 2608 [Active*]
IETF RFC 2610 [Active*]
IETF RFC 2874 [Active*]
IETF RFC 2894 [Active*]
IETF RFC 3007 [Active*]
RFC3059 — RFC3059 EXTERNAL
IETF RFC 3118 [Active*]
IETF RFC 3203 [Active*]
IETF RFC 3224 [Active*]
IETF RFC 3306 [Active*]
IETF RFC 3315 [Superseded*]
RFC3421 — RFC3421 EXTERNAL
IETF RFC 3633 [Superseded*]
IETF RFC 3736 [Superseded*]
IETF RFC 3756 [Active*]
IETF RFC 3775 [Superseded*]
RFC3795 — RFC3795 EXTERNAL
IETF RFC 3832 [Active*]
IETF RFC 3956 [Active*]
IETF RFC 3958 [Active*]
IETF RFC 3971 [Active*]
IETF RFC 4033 [Active*]
IETF RFC 4034 [Active*]
IETF RFC 4035 [Active*]
IETF RFC 4076 [Active*]
IETF RFC 4191 [Active*]
IETF RFC 4192 [Active*]
IETF RFC 4193 [Active*]
IETF RFC 4306 [Superseded*]
IETF RFC 4340 [Active*]
IETF RFC 4741 [Superseded*]
IETF RFC 4861 [Active*]
IETF RFC 4862 [Active*]
IETF RFC 4941 [Superseded*]
IETF RFC 4960 [Superseded*]
IETF RFC 5059 [Active*]
IETF RFC 5061 [Active*]
IETF RFC 5072 [Active*]
IETF RFC 5280 [Active, Amended*]
IETF RFC 5533 [Active*]
IETF RFC 5558 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5887.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 5887, Renumbering Still Needs Work. Available at https://doi.org/10.17487/RFC5887

Snippet:

IETF RFC 5887, Renumbering Still Needs Work. Available at https://doi.org/10.17487/RFC5887

HTML (ISO 690 compliant)

Preview:

IETF RFC 5887, Renumbering Still Needs Work. Available at https://doi.org/10.17487/RFC5887

Snippet:

<span class="citation"><cite>IETF RFC 5887</cite>, Renumbering Still Needs Work. Available at <a href="https://doi.org/10.17487/RFC5887" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5887</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 5887, Renumbering Still Needs Work
doi: 10.17487/RFC5887
url: https://doi.org/10.17487/RFC5887

Snippet:

<li>
<cite id="bib-rfc5887">IETF RFC 5887</cite>, Renumbering Still Needs Work
<span class="doi">10.17487/RFC5887</span>
</li>

Referenced By

IETF RFC 5902 [Active*]
IETF RFC 6115 [Active*]
IETF RFC 6879 [Active*]