RFC 9544: Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs)
In plain English — editorial summary, not part of the RFC
This document defines a set of metrics for networking services with performance requirements expressed as Service Level Objectives (SLOs). These metrics, referred to as "Precision Availability Metrics (PAMs)", are useful for defining and monitoring SLOs. For example, PAMs can be used by providers and/or customers of an RFC 9543 Network Slice Service to assess whether the service is provided in compliance with its defined SLOs.
Document record
- Document ID
- RFC9544
- Published
- March 2024
- Authors
- G. Mirsky; J. Halpern; X. Min; A. Clemm; J. Strassner; J. François
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8972Simple Two-Way Active Measurement Protocol Optional ExtensionsCurrent
January 2021
- RFC 9534Simple Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation GroupCurrent
January 2024
- RFC 9533One-Way and Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation GroupCurrent
January 2024
- RFC 9198Advanced Unidirectional Route Assessment (AURA)Current
May 2022
- RFC 8911Registry for Performance MetricsCurrent
November 2021
- RFC 8186Support of the IEEE 1588 Timestamp Format in a Two-Way Active Measurement Protocol (TWAMP)Current
June 2017
- RFC 7820UDP Checksum Complement in the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)Current
March 2016
- RFC 7750Differentiated Service Code Point and Explicit Congestion Notification Monitoring in the Two-Way Active Measurement Protocol (TWAMP)Current
February 2016
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?