Service Models Explained
draft-ietf-opsawg-service-model-explained-04

The information below is for an old version of the document
Document Type Active Internet-Draft (opsawg WG)
Authors Qin Wu  , Will LIU  , Adrian Farrel 
Last updated 2017-10-12 (latest revision 2017-09-27)
Replaces draft-wu-opsawg-service-model-explained
Stream Internet Engineering Task Force (IETF)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Tianran Zhou
Shepherd write-up Show (last changed 2017-08-31)
IESG IESG state Approved-announcement to be sent
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to Tianran Zhou <zhoutianran@huawei.com>
IANA IANA review state IANA OK - No Actions Needed
OPS Area Working Group                                             Q. Wu
Internet-Draft                                                    W. Liu
Intended status: Informational                       Huawei Technologies
Expires: March 31, 2018                                        A. Farrel
                                                        Juniper Networks
                                                      September 27, 2017

                        Service Models Explained
              draft-ietf-opsawg-service-model-explained-04

Abstract

   The IETF has produced many modules in the YANG modeling language.
   The majority of these modules are used to construct data models to
   model devices or monolithic functions.

   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 describes service models as used within the IETF, and
   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 modules that
   are not exposed through the Customer-Provider Interface.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 31, 2018.

Wu, et al.               Expires March 31, 2018                 [Page 1]
Internet-Draft          Service Models Explained          September 2017

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terms and Concepts  . . . . . . . . . . . . . . . . . . . . .   4
   3.  Using Service Models  . . . . . . . . . . . . . . . . . . . .   6
   4.  Service Models in an SDN Context  . . . . . . . . . . . . . .   8
   5.  Possible Causes of Confusion  . . . . . . . . . . . . . . . .  10
   6.  Comparison With Other Work  . . . . . . . . . . . . . . . . .  12
     6.1.  Comparison With Network Service Models  . . . . . . . . .  12
     6.2.  Service Delivery and Network Element Model Work . . . . .  14
     6.3.  Customer Service Model Work . . . . . . . . . . . . . . .  14
     6.4.  The MEF Architecture  . . . . . . . . . . . . . . . . . .  16
   7.  Further Concepts  . . . . . . . . . . . . . . . . . . . . . .  17
     7.1.  Technology Agnostic . . . . . . . . . . . . . . . . . . .  17
     7.2.  Relationship to Policy  . . . . . . . . . . . . . . . . .  17
     7.3.  Operator-Specific Features  . . . . . . . . . . . . . . .  18
     7.4.  Supporting Multiple Services  . . . . . . . . . . . . . .  18
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  19
   9.  Manageability Considerations  . . . . . . . . . . . . . . . .  19
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  20
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  20
     12.2.  Informative References . . . . . . . . . . . . . . . . .  20
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Introduction

   In recent years the number of modules written in the YANG modeling
   language [RFC6020] for configuration and monitoring has blossomed.
   Many of these are used for device-level configuration (for example,
Show full document text