Centralized Address Space Management(CASM) Requirements and Framework
draft-kumar-casm-requirements-and-framework-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Rakesh Kumar , Anil Lohiya , Marc Blanchet | ||
| Last updated | 2017-08-03 (latest revision 2017-01-30) | ||
| Replaces | draft-kumar-requirements-and-framework | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-kumar-casm-requirements-and-framework-00.txt
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
(rkkumar@juniper.net)
Anil Lohiya
(alohiya@juniper.net)
Marc Blanchet
(Marc.Blanchet@viagenie.ca)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)