RFC 8979: Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)
In plain English — editorial summary, not part of the RFC
This document defines the Subscriber and Performance Policy Identifier Context Headers. These Variable-Length Context Headers can be carried in the Network Service Header (NSH) and are used to inform Service Functions (SFs) of subscriber- and performance-related information for the sake of policy enforcement and appropriate Service Function Chaining (SFC) operations. The structure of each Context Header and their use and processing by NSH-aware nodes are described.
Document record
- Document ID
- RFC8979
- Published
- February 2021
- Authors
- B. Sarikaya; D. von Hugo; M. Boucadair
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9015BGP Control Plane for the Network Service Header in Service Function ChainingCurrent
June 2021
- RFC 8677Name-Based Service Function Forwarder (nSFF) Component within a Service Function Chaining (SFC) FrameworkCurrent
November 2019
- RFC 9005Path Computation Element Communication Protocol (PCEP) Extension for Associating Policies and Label Switched Paths (LSPs)Current
March 2021
- RFC 8924Service Function Chaining (SFC) Operations, Administration, and Maintenance (OAM) FrameworkCurrent
October 2020
- RFC 9305Locator/ID Separation Protocol (LISP) Generic Protocol ExtensionCurrent
October 2022
- RFC 8595An MPLS-Based Forwarding Plane for Service Function ChainingCurrent
June 2019
- RFC 9491Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC)Current
November 2023
- RFC 9552Distribution of Link-State and Traffic Engineering Information Using BGPCurrent
December 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?