RFC 7498: Problem Statement for Service Function Chaining
In plain English — editorial summary, not part of the RFC
This document provides an overview of the issues associated with the deployment of service functions (such as firewalls, load balancers, etc.) in large-scale environments. The term "service function chaining" is used to describe the definition and instantiation of an ordered list of instances of such service functions, and the subsequent "steering" of traffic flows through those service functions. The set of enabled service function chains reflects operator service offerings and is designed in conjunction with application delivery and service and network policy. This document also identifies several key areas that the Service Function Chaining (SFC) working group will investigate to guide its architectural and protocol work and associated documents.
Document record
- Document ID
- RFC7498
- Published
- April 2015
- Authors
- P. Quinn; T. Nadeau
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8300Network Service Header (NSH)Updated
January 2018
- 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 8924Service Function Chaining (SFC) Operations, Administration, and Maintenance (OAM) FrameworkCurrent
October 2020
- RFC 8979Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)Current
February 2021
- RFC 9015BGP Control Plane for the Network Service Header in Service Function ChainingCurrent
June 2021
- RFC 9451Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH)Current
August 2023
- RFC 9491Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC)Current
November 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?