IPv6 Enterprise Network Renumbering Scenarios and Guidelines
draft-ietf-6renum-enterprise-04

The information below is for an old version of the document
Document Type Active Internet-Draft (6renum WG)
Last updated 2012-12-19 (latest revision 2012-11-27)
Replaces draft-jiang-6renum-enterprise
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation
Telechat date
Needs a YES.
Responsible AD Ron Bonica
IESG note Lee Howard (lee.howard@twcable.com) is the document shepherd.
Send notices to 6renum-chairs@tools.ietf.org, draft-ietf-6renum-enterprise@tools.ietf.org
Network Working Group                                          S. Jiang
Internet Draft                                                   B. Liu
Intended status: Informational             Huawei Technologies Co., Ltd
Expires: May 27, 2013                                      B. Carpenter
                                                 University of Auckland
                                                      November 28, 2012

      IPv6 Enterprise Network Renumbering Scenarios and Guidelines
                  draft-ietf-6renum-enterprise-04.txt

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF). Note that other groups may also distribute working
   documents as Internet-Drafts. The list of current Internet-Drafts is
   at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 27, 2013.

Copyright Notice

   Copyright (c) 2012 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.

Jiang, et al.           Expires May 27, 2013                  [Page 1]
Internet-Draft   draft-ietf-6renum-enterprise-04.txt      November 2012

Abstract

   This document analyzes events that cause renumbering and describes
   the best renumbering practice. Best practices are described in three
   categories: those applicable during network design, those applicable
   during preparation for renumbering, and those applicable during the
   renumbering operation.

Table of Contents

   1. Introduction ................................................. 3
   2. Enterprise Network Illustration for Renumbering .............. 3
   3. Enterprise Network Renumbering Scenario Categories ........... 4
      3.1. Renumbering Caused by External Network Factors........... 4
      3.2. Renumbering caused by Internal Network Factors........... 5
   4. Network Renumbering Considerations and Best Current Practices. 5
      4.1. Considerations and Best Current Practices during Network
      Design ....................................................... 6
      4.2. Considerations and Best Current Practices for the Preparation
      of Renumbering .............................................. 10
      4.3. Considerations and Best Current Practices during Renumbering
      Operation ................................................... 11
   5. Security Considerations ..................................... 13
   6. IANA Considerations ......................................... 13
   7. Acknowledgements ............................................ 13
   8. References .................................................. 13
      8.1. Normative References ................................... 13
      8.2. Informative References ................................. 15
   Author's Addresses ............................................. 17

Jiang, et al.               May 27, 2013                      [Page 2]
Internet-Draft   draft-ietf-6renum-enterprise-04.txt      November 2012

1. Introduction

   Site renumbering is difficult. Network managers frequently attempt to
   avoid renumbering by numbering their network resources from Provider
   Independent (PI) address space. However, widespread use of PI might
   create serious BGP4 scaling problems and according to Regional
   Internet Registry (RIR) policies, PI space is not always available
   for enterprises Therefore, it is desirable to develop mechanisms that
   simplify IPv6 renumbering.

   This document undertakes scenario descriptions, including
   documentation of current capabilities and existing BCPs, for
   enterprise networks. It takes [RFC5887] and other relevant documents
   as the primary input.

   Since the IPv4 and IPv6 are logically separated from the perspective
   of renumbering, regardless of overlapping of the IPv4/IPv6 networks
Show full document text