| rfc9418v2.txt | rfc9418.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) B. Claise | Internet Engineering Task Force (IETF) B. Claise | |||
| Request for Comments: 9418 J. Quilbeuf | Request for Comments: 9418 J. Quilbeuf | |||
| Category: Standards Track Huawei | Category: Standards Track Huawei | |||
| ISSN: 2070-1721 P. Lucente | ISSN: 2070-1721 P. Lucente | |||
| NTT | NTT | |||
| P. Fasano | P. Fasano | |||
| TIM S.p.A | TIM S.p.A | |||
| T. Arumugam | T. Arumugam | |||
| Cisco Systems, Inc. | Consultant | |||
| June 2023 | June 2023 | |||
| A YANG Data Model for Service Assurance | A YANG Data Model for Service Assurance | |||
| Abstract | Abstract | |||
| This document specifies YANG modules for representing assurance | This document specifies YANG modules for representing assurance | |||
| graphs. These graphs represent the assurance of a given service by | graphs. These graphs represent the assurance of a given service by | |||
| decomposing it into atomic assurance elements called subservices. | decomposing it into atomic assurance elements called subservices. | |||
| The companion document, "Service Assurance for Intent-Based | The companion document, "Service Assurance for Intent-Based | |||
| skipping to change at line 198 ¶ | skipping to change at line 198 ¶ | |||
| * device: Whether a device is healthy, and if not, what are the | * device: Whether a device is healthy, and if not, what are the | |||
| symptoms? Such a subservice might monitor the device resources, | symptoms? Such a subservice might monitor the device resources, | |||
| such as CPU, RAM, or Ternary Content-Addressable Memory (TCAM). | such as CPU, RAM, or Ternary Content-Addressable Memory (TCAM). | |||
| Potential symptoms are "CPU overloaded", "Out of RAM", or "Out of | Potential symptoms are "CPU overloaded", "Out of RAM", or "Out of | |||
| TCAM". | TCAM". | |||
| * ip-connectivity: Given two IP addresses bound to two devices, what | * ip-connectivity: Given two IP addresses bound to two devices, what | |||
| is the quality of the IP connectivity between them? Potential | is the quality of the IP connectivity between them? Potential | |||
| symptoms are "No route available" or "Equal-Cost Multipaths | symptoms are "No route available" or "Equal-Cost Multipaths | |||
| (ECMPs) Imbalance". | (ECMPs) imbalance". | |||
| An instance of the device subservice is representing a subpart of the | An instance of the device subservice is representing a subpart of the | |||
| network system, namely a specific device. An instance of the ip- | network system, namely a specific device. An instance of the ip- | |||
| connectivity subservice is representing a feature of the network, | connectivity subservice is representing a feature of the network, | |||
| namely the connectivity between two specific IP addresses on two | namely the connectivity between two specific IP addresses on two | |||
| devices. In both cases, these subservices might depend on other | devices. In both cases, these subservices might depend on other | |||
| subservices, for instance, the connectivity might depend on a | subservices, for instance, the connectivity might depend on a | |||
| subservice representing the routing system and on a subservice | subservice representing the routing system and on a subservice | |||
| representing ECMPs. | representing ECMPs. | |||
| skipping to change at line 1987 ¶ | skipping to change at line 1987 ¶ | |||
| Email: paolo@ntt.net | Email: paolo@ntt.net | |||
| Paolo Fasano | Paolo Fasano | |||
| TIM S.p.A | TIM S.p.A | |||
| via G. Reiss Romoli, 274 | via G. Reiss Romoli, 274 | |||
| 10148 Torino | 10148 Torino | |||
| Italy | Italy | |||
| Email: paolo2.fasano@telecomitalia.it | Email: paolo2.fasano@telecomitalia.it | |||
| Thangam Arumugam | Thangam Arumugam | |||
| Cisco Systems, Inc. | Consultant | |||
| Milpitas, California | Milpitas, California | |||
| United States of America | United States of America | |||
| Email: thangavelu@yahoo.com | Email: thangavelu@yahoo.com | |||
| End of changes. 3 change blocks. | ||||
| 3 lines changed or deleted | 3 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||