Multiple Provisioning Domains API Requirements
draft-kline-mif-mpvd-api-reqs-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Erik Kline | ||
| Last updated | 2016-05-04 (Latest revision 2015-11-01) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-kline-mif-mpvd-api-reqs-00.txt
Abstract
RFC 7556 [RFC7556] provides the essential conceptual guidance an API designer would need to support use of PvDs. This document aims to capture the requirements for an API that can be used by applications that would be considered "advanced", according to section 6.3 [1] of RFC 7556 [RFC7556]. The "basic" [2] and "intermediate" [3] API support levels can in principle be implemented by means of layers wrapping the advanced API.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)