RFC 9015: BGP Control Plane for the Network Service Header in Service Function Chaining
In plain English — editorial summary, not part of the RFC
This document describes the use of BGP as a control plane for networks that support service function chaining. The document introduces a new BGP address family called the "Service Function Chain (SFC) Address Family Identifier / Subsequent Address Family Identifier" (SFC AFI/SAFI) with two Route Types. One Route Type is originated by a node to advertise that it hosts a particular instance of a specified service function. This Route Type also provides "instructions" on how to send a packet to the hosting node in a way that indicates that the service function has to be applied to the packet. The other Route Type is used by a controller to advertise the paths of "chains" of service functions and give a unique designator to each such path so that they can be used in conjunction with the Network Service Header (NSH) defined in RFC 8300. This document adopts the service function chaining architecture described in RFC 7665.
Document record
- Document ID
- RFC9015
- Published
- June 2021
- Authors
- A. Farrel; J. Drake; E. Rosen; J. Uttaro; L. Jalil
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 59
- 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 8393Operating the Network Service Header (NSH) with Next Protocol "None"Current
May 2018
- RFC 8300Network Service Header (NSH)Updated
January 2018
- RFC 9451Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH)Current
August 2023
- RFC 9730Interworking of GMPLS Control and Centralized Controller SystemsCurrent
March 2025
- RFC 7498Problem Statement for Service Function ChainingCurrent
April 2015
- RFC 6041Forwarding and Control Element Separation (ForCES) Applicability StatementCurrent
October 2010
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?