RFC 8924: Service Function Chaining (SFC) Operations, Administration, and Maintenance (OAM) Framework
In plain English — editorial summary, not part of the RFC
This document provides a reference framework for Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC).
Document record
- Document ID
- RFC8924
- Published
- October 2020
- Authors
- S. Aldrin; C. Pignataro; N. Kumar; R. Krishnan; A. Ghanwani
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8979Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)Current
February 2021
- RFC 8595An MPLS-Based Forwarding Plane for Service Function ChainingCurrent
June 2019
- RFC 8403A Scalable and Topology-Aware MPLS Data-Plane Monitoring SystemCurrent
July 2018
- RFC 8372MPLS Flow Identification ConsiderationsCurrent
May 2018
- RFC 9491Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC)Current
November 2023
- RFC 9546Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data PlaneCurrent
February 2024
- RFC 8300Network Service Header (NSH)Updated
January 2018
- RFC 8256Requirements for Hitless MPLS Path Segment MonitoringCurrent
October 2017
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?