Service Models Explained
draft-wu-opsawg-service-model-explained-06

Document Type Replaced Internet-Draft (individual)
Last updated 2017-05-30
Replaced by draft-ietf-opsawg-service-model-explained
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 Replaced by draft-ietf-opsawg-service-model-explained
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-wu-opsawg-service-model-explained-06.txt

Abstract

The IETF has produced a considerable number of data modules in the YANG modelling language. The majority of these modules are used to construct data models to model devices or monolithic functions and they allow access for configuration and to read operational status. A small number of YANG modules have been defined to model services (for example, the Layer Three Virtual Private Network Service Model produced by the L3SM working group and documented in RFC 8049). This document briefly sets out the scope of and purpose of an IETF service model, and it also shows where a service model might fit into a Software Defined Networking architecture. Note that service models do not make any assumption of how a service is actually engineered and delivered for a customer; details of how network protocols and devices are engineered to deliver a service are captured in other models that are not exposed through the Customer-Provider Interface.

Authors

Qin Wu (bill.wu@huawei.com)
Will LIU (liushucheng@huawei.com)
Adrian Farrel (afarrel@juniper.net)

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