RFC 7665: Service Function Chaining (SFC) Architecture

This document describes an architecture for the specification, creation, and ongoing maintenance of Service Function Chains (SFCs) in a network. It includes…

Read RFC 7665 on the RFC Editor

Outgoing relationships (6 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 3022: Traditional IP Network Address Translator (Traditional NAT)
Informative reference — RFC 6146: Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
Informative reference — RFC 6973: Privacy Considerations for Internet Protocols
Informative reference — RFC 6296: IPv6-to-IPv6 Network Prefix Translation
Informative reference — RFC 7498: Problem Statement for Service Function Chaining

Incoming relationships (27 related RFCs)

Normatively referenced by — RFC 8300: Network Service Header (NSH)
Normatively referenced by — RFC 9145: Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context Headers
Normatively referenced by — RFC 8979: Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)
Normatively referenced by — RFC 9192: Network Service Header (NSH) Fixed-Length Context Header Allocation
Normatively referenced by — RFC 9516: Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC)
Normatively referenced by — RFC 9689: Use Cases for a PCE as a Central Controller (PCECC)
Informatively referenced by — RFC 8969: A Framework for Automating Service and Network Management with YANG
Informatively referenced by — RFC 8283: An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central Control
Informatively referenced by — RFC 8404: Effects of Pervasive Encryption on Operators
Informatively referenced by — RFC 9330: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture
Informatively referenced by — RFC 9543: A Framework for Network Slices in Networks Built from IETF Technologies
Informatively referenced by — RFC 8799: Limited Domains and Internet Protocols
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Informatively referenced by — RFC 9834: YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)
Informatively referenced by — RFC 9835: A Network YANG Data Model for Attachment Circuits
Informatively referenced by — RFC 9263: Network Service Header (NSH) Metadata Type 2 Variable-Length Context Headers
Informatively referenced by — RFC 9833: A Common YANG Data Model for Attachment Circuits
Informatively referenced by — RFC 9836: A YANG Data Model for Augmenting VPN Service and Network Models with Attachment Circuits
Informatively referenced by — RFC 8924: Service Function Chaining (SFC) Operations, Administration, and Maintenance (OAM) Framework
Informatively referenced by — RFC 9451: Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH)
Informatively referenced by — RFC 9491: Integration of the Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC)
Informatively referenced by — RFC 9452: Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data
Informatively referenced by — RFC 9473: A Vocabulary of Path Properties
Informatively referenced by — RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim
Informatively referenced by — RFC 8393: Operating the Network Service Header (NSH) with Next Protocol "None"
Informatively referenced by — RFC 8763: Deployment Considerations for Information-Centric Networking (ICN)
Informatively referenced by — RFC 9222: Guidelines for Autonomic Service Agents