Renumbering Still Needs Work
RFC 5887
| Document | Type |
RFC - Informational
(May 2010; No errata)
Was draft-carpenter-renum-needs-work (individual in ops area)
|
|
|---|---|---|---|
| Authors | Randall Atkinson , Brian Carpenter , Hannu Flinck | ||
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5887 (Informational) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Dan Romascanu | ||
| Send notices to | ran.atkinson@gmail.com | ||
Internet Engineering Task Force (IETF) B. Carpenter
Request for Comments: 5887 Univ. of Auckland
Category: Informational R. Atkinson
ISSN: 2070-1721 Extreme Networks
H. Flinck
Nokia Siemens Networks
May 2010
Renumbering Still Needs Work
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.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc5887.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Carpenter, et al. Informational [Page 1]
RFC 5887 Renumbering Still Needs Work May 2010
Table of Contents
1. Introduction ....................................................3
2. Existing Host-Related Mechanisms ................................5
2.1. DHCP .......................................................5
2.2. IPv6 Stateless Address Autoconfiguration ...................6
2.3. IPv6 ND Router/Prefix Advertisements .......................7
2.4. PPP ........................................................7
2.5. DNS Configuration ..........................................8
2.6. Dynamic Service Discovery ..................................9
3. Existing Router-Related Mechanisms ..............................9
3.1. Router Renumbering .........................................9
4. Existing Multi-Addressing Mechanism for IPv6 ...................10
5. Operational Issues with Renumbering Today ......................11
5.1. Host-Related Issues .......................................11
5.1.1. Network-Layer Issues ...............................11
5.1.2. Transport-Layer Issues .............................13
5.1.3. DNS Issues .........................................14
5.1.4. Application-Layer Issues ...........................14
5.2. Router-Related Issues .....................................16
5.3. Other Issues ..............................................17
5.3.1. NAT State Issues ...................................17
5.3.2. Mobility Issues ....................................18
5.3.3. Multicast Issues ...................................18
5.3.4. Management Issues ..................................19
5.3.5. Security Issues ....................................21
6. Proposed Mechanisms ............................................22
6.1. SHIM6 .....................................................22
6.2. MANET Proposals ...........................................22
6.3. Other IETF Work ...........................................23
6.4. Other Proposals ...........................................23
7. Gaps ...........................................................24
7.1. Host-Related Gaps .........................................24
7.2. Router-Related Gaps .......................................25
7.3. Operational Gaps ..........................................25
7.4. Other Gaps ................................................26
8. Security Considerations ........................................26
Show full document text