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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-09-09
Replaced by draft-ietf-opsawg-service-model-explained, rfc8309
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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: March 13, 2017                                        A. Farrel
                                                        Juniper Networks
                                                       September 9, 2016

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

Abstract

   The IETF has produced a considerable number of data models in the
   YANG modelling language.  The majority of these are used to model
   devices and they allow access for configuration and to read
   operational status.

   A small number of YANG models are used 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 shows where a service model might fit into a
   Software Defined Networking architecture or deployment.

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 March 12, 2017.

Copyright Notice

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

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

   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  . . . . . . . . . . . . . . . . . . . .   5
   4.  Service Models in an SDN Context  . . . . . . . . . . . . . .   6
   5.  Possible Causes of Confusion  . . . . . . . . . . . . . . . .   9
   6.  Comparison With Other Work  . . . . . . . . . . . . . . . . .  10
     6.1.  Comparison With Network Service Models  . . . . . . . . .  11
     6.2.  Service Delivery Model Work . . . . . . . . . . . . . . .  12
     6.3.  Customer Service Model Work . . . . . . . . . . . . . . .  13
     6.4.  The MEF Architecture  . . . . . . . . . . . . . . . . . .  14
   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  . . . . . . . . . . . . . . . .  17
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  17
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     12.2.  Informative References . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction

   In recent years the number of data models written in the YANG
   modelling language [RFC6020] for configuration and monitoring has
   blossomed.  Many of these are used for device-level configuration
   (for example, [RFC7223]) or for control of protocols (for example,
   [RFC7407]).

   Within the context of Software Defined Networking (SDN) [RFC7426]
   YANG data models may be used on Southbound Interfaces (SBIs) between
   a controller and network devices, and between network orchestrators
Show full document text