BGP Control Plane for the Network Service Header in Service Function Chaining
RFC 9015
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['Service Function Chaining', 'Service Function Chain', 'Network Service Header', 'Service Function', 'Service Function Forwarder', 'Service Function Path', 'Service Function Path … Changed metadata: changed keywords to '['Service Function Chaining', 'Service Function Chain', 'Network Service Header', 'Service Function', 'Service Function Forwarder', 'Service Function Path', 'Service Function Path Route', 'Service Function Instance', 'Service Function Instance Route', 'Service Function Type', 'Control Plane']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "L. Jalil": changed name from "Luay Jalil" to "L. Jalil", changed order from "4" to "5" |
|
2026-05-20
|
(System) | Changed author "J. Uttaro": changed name from "Jim Uttaro" to "J. Uttaro", changed order from "3" to "4" |
|
2026-05-20
|
(System) | Changed author "E. Rosen": changed name from "Eric Rosen" to "E. Rosen", changed order from "2" to "3" |
|
2026-05-20
|
(System) | Changed author "J. Drake": changed name from "John Drake" to "J. Drake", changed order from "1" to "2" |
|
2026-05-20
|
(System) | Changed author "A. Farrel": changed name from "Adrian Farrel" to "A. Farrel", changed order from "0" to "1" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2021-06-09
|
(System) | IANA registries were updated to include RFC9015 |
|
2021-06-08
|
(System) | Received changes through RFC Editor sync (created alias RFC 9015, changed abstract to 'This document describes the use of BGP as a control plane … Received changes through RFC Editor sync (created alias RFC 9015, changed abstract to '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.', changed pages to 59, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2021-06-08, changed IESG state to RFC Published) |
|
2021-06-08
|
(System) | RFC published |