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

Document Type Active Internet-Draft (individual)
Last updated 2017-01-05
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
OPS Area Working Group                                             Q. Wu
Internet-Draft                                                    W. Liu
Intended status: Informational                       Huawei Technologies
Expires: July 9, 2017                                          A. Farrel
                                                        Juniper Networks
                                                         January 5, 2017

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

Abstract

   The IETF has produced a considerable number of data models in the
   YANG modelling language.  The majority of these models are used 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).

   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 to 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.

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 http://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 July 9, 2017.

Wu, et al.                Expires July 9, 2017                  [Page 1]
Internet-Draft          Service Models Explained            January 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
   (http://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  . . . . . . . . . . . . . . . . . . . . .   3
   3.  Using Service Models  . . . . . . . . . . . . . . . . . . . .   6
   4.  Service Models in an SDN Context  . . . . . . . . . . . . . .   7
   5.  Possible Causes of Confusion  . . . . . . . . . . . . . . . .  10
   6.  Comparison With Other Work  . . . . . . . . . . . . . . . . .  11
     6.1.  Comparison With Network Service Models  . . . . . . . . .  12
     6.2.  Service Delivery Model Work . . . . . . . . . . . . . . .  13
     6.3.  Customer Service Model Work . . . . . . . . . . . . . . .  14
     6.4.  The MEF Architecture  . . . . . . . . . . . . . . . . . .  15
   7.  Further Concepts  . . . . . . . . . . . . . . . . . . . . . .  16
     7.1.  Technology Agnostic . . . . . . . . . . . . . . . . . . .  16
     7.2.  Relationship to Policy  . . . . . . . . . . . . . . . . .  16
     7.3.  Operator-Specific Features  . . . . . . . . . . . . . . .  17
     7.4.  Supporting Multiple Services  . . . . . . . . . . . . . .  17
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   9.  Manageability Considerations  . . . . . . . . . . . . . . . .  18
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  18
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     12.2.  Informative References . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   In recent years the number of data models written in the YANG
Show full document text