Skip to main content

1. Introduction

1. Introduction​

[RFC9417] describes an architecture and a set of involved components for service assurance, called Service Assurance for Intent-based Networking (SAIN). This document complements the architecture by specifying a data model for the interfaces between components. More specifically, the document provides YANG modules for the purpose of service assurance in a format that is:

  • machine readable,

  • vendor independent, and

  • augmentable such that SAIN agents from Figure 1 of [RFC9417] can support and expose new subservices to SAIN orchestrators and collectors.

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

The terms used in this document are defined in [RFC9417].

The meanings of the symbols in the tree diagrams are defined in [RFC8340].

Last updated on