Requirements and Architecture of Carrier IP Service Models
draft-li-opsawg-carrier-ip-service-model-req-arch-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhenbin Li , Nan Wu | ||
| Last updated | 2016-04-21 (Latest revision 2015-10-19) | ||
| RFC stream | (None) | ||
| Formats | |||
| 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) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Service Model is a fundamental building block for a controller's North-Bound Interface (NBI). Defining a service model for different multi-layered and heterogeneous networks is a complicated work and may require lots of consideration since different model users may have different perspective and concerns. This document proposes the requirements and architecture for service models to facilitate future work. This document does not attempt to provide a detailed description of all the architectural components, but rather it describes a set of building blocks, requirements, architecture and guidelines from which models may be constructed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)