Requirements and Architecture of Carrier IP Service Models
draft-li-opsawg-carrier-ip-service-model-req-arch-01

Document Type Expired Internet-Draft (individual)
Last updated 2017-09-14 (latest revision 2017-03-13)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-li-opsawg-carrier-ip-service-model-req-arch-01.txt

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

Zhenbin Li (lizhenbin@huawei.com)
Qiong Sun (sunqiong@ctbri.com.cn)
Yi Zheng (zhengyi39@chinaunicom.cn)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)