Problem Statement for Renumbering IPv6 Hosts with Static Addresses
draft-ietf-6renum-static-problem-01

The information below is for an old version of the document
Document Type Active Internet-Draft (6renum WG)
Last updated 2012-08-30
Replaces draft-carpenter-6renum-static-problem
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
6RENUM                                                      B. Carpenter
Internet-Draft                                         Univ. of Auckland
Intended status: Informational                                  S. Jiang
Expires: March 4, 2013                      Huawei Technologies Co., Ltd
                                                         August 31, 2012

   Problem Statement for Renumbering IPv6 Hosts with Static Addresses
                  draft-ietf-6renum-static-problem-01

Abstract

   This document analyses the problems of updating the IPv6 addresses of
   hosts in enterprise networks that for operational reasons require
   static addresses.

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 March 4, 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.

Carpenter & Jiang         Expires March 4, 2013                 [Page 1]
Internet-Draft        Renumbering Static Addresses           August 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1.  Static Addresses Imply Static Prefixes . . . . . . . . . .  4
     2.2.  Other Hosts Need Literal Address . . . . . . . . . . . . .  4
     2.3.  Static Server Addresses  . . . . . . . . . . . . . . . . .  5
     2.4.  Static Virtual Machine Addresses . . . . . . . . . . . . .  6
     2.5.  Asset Management and Security Tracing  . . . . . . . . . .  6
     2.6.  Primitive Software Licensing . . . . . . . . . . . . . . .  7
     2.7.  Network Elements . . . . . . . . . . . . . . . . . . . . .  7
     2.8.  Management Aspects . . . . . . . . . . . . . . . . . . . .  7
   3.  Summary of Problem Statement . . . . . . . . . . . . . . . . .  8
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  9
   7.  Change log [RFC Editor: Please remove] . . . . . . . . . . . . 10
   8.  Informative References . . . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11

Carpenter & Jiang         Expires March 4, 2013                 [Page 2]
Internet-Draft        Renumbering Static Addresses           August 2012

1.  Introduction

   A problem that is frequently mentioned in discussions of renumbering
   enterprise networks [RFC5887] [I-D.jiang-6renum-enterprise]
   [I-D.liu-6renum-gap-analysis] is that of statically assigned
   addresses.  A static address can be defined as an IP address that is
   intended by the network manager to remain constant over a long period
   of time, possibly many years, regardless of system restarts or any
   other unpredictable events.  Static addressing often implies manual
   address assignment, including manual preparation of configuration
   scripts.  An implication of hosts having static addresses is that
   subnets must have static prefixes, which also requires analysis.

   In a sense, the issue of static addresses is a result of history.  As
   discussed in Section 3.2 of [RFC6250], various properties of IP
   addresses that have long been assumed by programmers and operators
   are no longer true today, although they were true when almost all
   addresses were manually assigned.  In some cases, the resulting
   operational difficulties are avoided by static addressing.

   Although static addressing is in general problematic for renumbering,
Show full document text