Centralized Address Space Management(CASM) Requirements and Framework
draft-kumar-requirements-and-framework-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Rakesh Kumar , Anil Lohiya , Marc Blanchet | ||
| Last updated | 2017-01-29 | ||
| Replaced by | draft-kumar-casm-requirements-and-framework | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-kumar-casm-requirements-and-framework | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Rakesh Kumar
Anil Lohiya
Marc Blanchet
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)