Centralized Address Space Management(CASM) Requirements and Framework
draft-kumar-casm-requirements-and-framework-00

Document Type Active Internet-Draft (individual)
Last updated 2017-01-30
Replaces draft-kumar-requirements-and-framework
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 3, 2017                                      M. Blanchet
                                                                Viagenie
                                                        January 30, 2017

 Centralized Address Space Management(CASM) Requirements and Framework
             draft-kumar-casm-requirements-and-framework-00

Abstract

   The organizations 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 3, 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 3, 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 . . . . . . . . . . . . . . . . . . . .   2
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Requirements from CASM system . . . . . . . . . . . . . . . .   3
     4.1.  General operational requirements  . . . . . . . . . . . .   3
     4.2.  Interafce modeling requirements . . . . . . . . . . . . .   3
     4.3.  Functional requirements . . . . . . . . . . . . . . . . .   4
       4.3.1.  Address pools . . . . . . . . . . . . . . . . . . . .   4
       4.3.2.  Pool management . . . . . . . . . . . . . . . . . . .   5
       4.3.3.  Integration with other address services . . . . . . .   5
   5.  Archiectural framework  . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   9.  Informative References  . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The address space management is an intergral part of any network
   management solution.  The network architectures are rapidally
   changing with the migration toward private and public clouds.  At the
   same time, application architectures are also evolving with a shift
   toward micro-services and multi-tiered approach.

   There is a pressing need to define a new address management system
   which can meet these diverse set of requirements.  Such a system must
   be built with well defined interfaces so users can easily migrate
   from one vendor to another without rewriting their network management
   systems.

   This document identifies a broad set of requirements and defins a
   architectural framework that should become the basis to develop a new
   address management system.  We are calling this new system as
   Centralized Address Space Management (CSAM) system.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
Show full document text