Service Assurance for Intent-based Networking Architecture
draft-claise-opsawg-service-assurance-architecture-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
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)
OPSAWG                                                         B. Claise
Internet-Draft                                               J. Quilbeuf
Intended status: Informational                       Cisco Systems, Inc.
Expires: May 6, 2020                                    November 3, 2019

       Service Assurance for Intent-based Networking Architecture
         draft-claise-opsawg-service-assurance-architecture-00

Abstract

   This document describes the architecture for Service Assurance for
   Intent-based Networking (SAIN).  This architecture aims at assuring
   that service instances are correctly running.  As services rely on
   multiple sub-services by the underlying network devices, getting the
   assurance of a healthy service is only possible with a holistic view
   of network devices.  This architecture not only helps to correlate
   the service degradation with the network root cause but also the
   impacted services impacted when a network component fails or
   degrades.

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 May 6, 2020.

Copyright Notice

   Copyright (c) 2019 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

Claise & Quilbeuf          Expires May 6, 2020                  [Page 1]
Internet-DraftService Assurance for Intent-based NetworkingNovember 2019

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Decomposing a Service Instance Configuration into an
           Assurance Tree  . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Intent and Assurance Tree . . . . . . . . . . . . . . . .   9
     3.3.  Subservices . . . . . . . . . . . . . . . . . . . . . . .   9
     3.4.  Building the Expression Tree from the Assurance Tree  . .  10
     3.5.  Building the Expression from a Subservice . . . . . . . .  10
     3.6.  Open Interfaces with YANG Modules . . . . . . . . . . . .  10
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   6.  Open Issues . . . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  Changes between revisions  . . . . . . . . . . . . .  12
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   Agent (SAIN Agent): Component that communicates with a device, a set
   of devices, or another agent to build an expression tree from a
   received assurance tree and perform the corresponding computation.

   Assurance Tree: DAG representing the assurance case for one or
   several service instances.  The nodes are the service instances
   themselves and the subservices, the edges indicate a dependency
   relations.

   Collector (SAIN collector): Component that fetches the computer-
   consumable output of the agent(s) and displays it in a user friendly
   form or process it locally.

Claise & Quilbeuf          Expires May 6, 2020                  [Page 2]
Internet-DraftService Assurance for Intent-based NetworkingNovember 2019
Show full document text