RFC 8592: Key Performance Indicator (KPI) Stamping for the Network Service Header (NSH)
In plain English — editorial summary, not part of the RFC
This document describes methods of carrying Key Performance Indicators (KPIs) using the Network Service Header (NSH). These methods may be used, for example, to monitor latency and QoS marking to identify problems on some links or service functions.
Document record
- Document ID
- RFC8592
- Published
- May 2019
- Authors
- R. Browne; A. Chilikin; T. Mizrahi
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9192Network Service Header (NSH) Fixed-Length Context Header AllocationCurrent
February 2022
- RFC 6294Survey of Proposed Use Cases for the IPv6 Flow LabelCurrent
June 2011
- RFC 2549IP over Avian Carriers with Quality of ServiceCurrent
April 1999
- RFC 8325Mapping Diffserv to IEEE 802.11Updated
February 2018
- RFC 8979Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)Current
February 2021
- RFC 9034Packet Delivery Deadline Time in the Routing Header for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)Current
June 2021
- RFC 9064Considerations in the Development of a QoS Architecture for CCNx-Like Information-Centric Networking ProtocolsCurrent
June 2021
- RFC 9318IAB Workshop Report: Measuring Network Quality for End-UsersCurrent
October 2022
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?