draft-ietf-opsawg-service-model-explained-00.txt   draft-ietf-opsawg-service-model-explained-01.txt 
OPS Area Working Group Q. Wu OPS Area Working Group Q. Wu
Internet-Draft W. Liu Internet-Draft W. Liu
Intended status: Informational Huawei Technologies Intended status: Informational Huawei Technologies
Expires: December 25, 2017 A. Farrel Expires: December 31, 2017 A. Farrel
Juniper Networks Juniper Networks
June 23, 2017 June 29, 2017
Service Models Explained Service Models Explained
draft-ietf-opsawg-service-model-explained-00 draft-ietf-opsawg-service-model-explained-01
Abstract Abstract
The IETF has produced a considerable number of data modules in the The IETF has produced a considerable number of data modules in the
YANG modelling language. The majority of these modules are used to YANG modelling language. The majority of these modules are used to
construct data models to model devices or monolithic functions and construct data models to model devices or monolithic functions and
they allow access for configuration and to read operational status. they allow access for configuration and to read operational status.
A small number of YANG modules have been defined to model services A small number of YANG modules have been defined to model services
(for example, the Layer Three Virtual Private Network Service Model (for example, the Layer Three Virtual Private Network Service Model
skipping to change at page 1, line 47 skipping to change at page 1, line 47
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 25, 2017. This Internet-Draft will expire on December 31, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 40 skipping to change at page 5, line 40
a human (such as via an order fulfillment system) or by a a human (such as via an order fulfillment system) or by a
software component. Such models are sometimes referred to software component. Such models are sometimes referred to
simply as "service models" [RFC8049]. A customer service model simply as "service models" [RFC8049]. A customer service model
is expressed as a core set of parameters that are common across is expressed as a core set of parameters that are common across
network operators: additional features that are specific to the network operators: additional features that are specific to the
offerings of individual network operators would be defined in offerings of individual network operators would be defined in
extensions or augmentations of the model. Except where extensions or augmentations of the model. Except where
specific technology details (such as encapsulations, or specific technology details (such as encapsulations, or
mechanisms applied on access links) are directly pertinent to mechanisms applied on access links) are directly pertinent to
the customer, customer service models are technology agnostic the customer, customer service models are technology agnostic
so that the customer does have influence over or knowledge of so that the customer does not have influence over or knowledge
how the network operator engineers the service. of how the network operator engineers the service.
An example of where such details are relevant to the customer An example of where such details are relevant to the customer
are when they describe the behavior or interactions on the are when they describe the behavior or interactions on the
interface between the equipment at the customer site (often interface between the equipment at the customer site (often
referred to as the Customer Edge or CE equipment) and the referred to as the Customer Edge or CE equipment) and the
equipment at the network operator's site (usually referred to equipment at the network operator's site (usually referred to
as the Provider Edge or PE equipment). as the Provider Edge or PE equipment).
Service Delivery Model: A service delivery model is used by a Service Delivery Model: A service delivery model is used by a
network operator to define and manage how a service is network operator to define and manage how a service is
skipping to change at page 19, line 13 skipping to change at page 19, line 13
This document makes no requests for IANA action This document makes no requests for IANA action
11. Acknowledgements 11. Acknowledgements
Thanks to Daniel King, Xian Zhang, and Michael Scharf for useful Thanks to Daniel King, Xian Zhang, and Michael Scharf for useful
review and comments. Med Boucadair gave thoughtful and detailed review and comments. Med Boucadair gave thoughtful and detailed
comments on version -04 of this document. Thanks to Dean Bogdanovic comments on version -04 of this document. Thanks to Dean Bogdanovic
and Tianran Zhou for their help coordinating with [I-D.ietf-netmod- and Tianran Zhou for their help coordinating with [I-D.ietf-netmod-
yang-model-classification]. yang-model-classification].
Many thanksto Jerry Bonner for spotting a tiny, one-word, but
critical typo.
12. References 12. References
12.1. Normative References 12.1. Normative References
[I-D.ietf-netmod-yang-model-classification] [I-D.ietf-netmod-yang-model-classification]
Bogdanovic, D., Claise, B., and C. Moberg, "YANG Module Bogdanovic, D., Claise, B., and C. Moberg, "YANG Module
Classification", draft-ietf-netmod-yang-model- Classification", draft-ietf-netmod-yang-model-
classification-08 (work in progress), June 2017. classification-08 (work in progress), June 2017.
[RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between [RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between
 End of changes. 6 change blocks. 
6 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/