Centralized Address Space Management(CASM) Problems and Use cases
draft-kumar-casm-problem-and-use-cases-00

Document Type Active Internet-Draft (individual)
Last updated 2017-01-29
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda casm at IETF-98
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                 R. Kumar
Internet-Draft                                                 A. Lohiya
Intended status: Informational                          Juniper Networks
Expires: August 2, 2017                                      M. Blanchet
                                                                Viagenie
                                                        January 29, 2017

   Centralized Address Space Management(CASM) Problems and Use cases
               draft-kumar-casm-problem-and-use-cases-00

Abstract

   The organisations use IP Address Space Management (IPAM) tools to
   manage their IP address space, often with proprietary database and
   interfaces.  This document describes evolution of IPAM into a
   standardized interfaces for centralized management of IP 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 August 2, 2017.

Copyright Notice

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

Kumar, et al.            Expires August 2, 2017                 [Page 1]
Internet-Draft    Centralized Address Space Management      January 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Address Space Management Use cases  . . . . . . . . . . . . .   3
     4.1.  DHCP server pool  . . . . . . . . . . . . . . . . . . . .   3
     4.2.  Static address configuration  . . . . . . . . . . . . . .   3
     4.3.  Public IP address pool  . . . . . . . . . . . . . . . . .   4
     4.4.  Multicast IP address pool . . . . . . . . . . . . . . . .   4
     4.5.  SDN controllers . . . . . . . . . . . . . . . . . . . . .   4
   5.  Legacy address space management (IPAM) systems  . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   9.  Informative References  . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The address space management is an intergral part of any network
   management solution.  The network may be based on legacy design or a
   more modern private and public cloud, the network may be big or small
   but every network operator need to manage the addressing needs of
   network elements.  Typically, network operators write proprietary
   scripts or use cheat sheets to manage the addressing requirements.
   In recent trends, open source communities have developed tools to
   manage available IP addreess space.

   The open source or proprietray tools and scripts are collectively
   known as Internet Protocol Address Management (IPAM) system.  The
   organizations use IPAM system to manage their IP address space, often
   with proprietary database and interfaces.  One of the biggest
   challenges with IPAM systems, is lack of standardized interface for
   allocation, storing and retrieving information.

   This document describes a diverse set of use cases for a IPAM system
   and the probelms identfied with current IPAM approach.  The problems
   identifed here should become the basis for a new vision defined as
   Centralized Address Space Management (CSAM).

Kumar, et al.            Expires August 2, 2017                 [Page 2]
Show full document text