RFC 9417: Service Assurance for Intent-Based Networking Architecture
In plain English — editorial summary, not part of the RFC
This document describes an architecture that provides some assurance that service instances are running as expected. As services rely upon multiple subservices provided by a variety of elements, including the underlying network devices and functions, getting the assurance of a healthy service is only possible with a holistic view of all involved elements. This architecture not only helps to correlate the service degradation with symptoms of a specific network component but, it also lists the services impacted by the failure or degradation of a specific network component.
Document record
- Document ID
- RFC9417
- Published
- July 2023
- Authors
- B. Claise; J. Quilbeuf; D. Lopez; D. Voyer; T. Arumugam
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 23
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9418A YANG Data Model for Service AssuranceCurrent
July 2023
- RFC 9411Benchmarking Methodology for Network Security Device PerformanceCurrent
March 2023
- RFC 9424Indicators of Compromise (IoCs) and Their Role in Attack DefenceCurrent
August 2023
- RFC 9408A YANG Network Data Model for Service Attachment Points (SAPs)Current
June 2023
- RFC 9432DNS Catalog ZonesCurrent
July 2023
- RFC 9439Application-Layer Traffic Optimization (ALTO) Performance Cost MetricsCurrent
August 2023
- RFC 9390Diameter Group SignalingCurrent
April 2023
- RFC 9445RADIUS Extensions for DHCP-Configured ServicesCurrent
August 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?