RFC 8595

An MPLS-Based Forwarding Plane for Service Function Chaining, June 2019

File formats:
icon for text file icon for PDF icon for HTML
A. Farrel
S. Bryant
J. Drake
mpls (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8595

Discuss this RFC: Send questions or comments to the mailing list mpls@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8595


This document describes how Service Function Chaining (SFC) can be achieved in an MPLS network by means of a logical representation of the Network Service Header (NSH) in an MPLS label stack. That is, the NSH is not used, but the fields of the NSH are mapped to fields in the MPLS label stack. This approach does not deprecate or replace the NSH, but it acknowledges that there may be a need for an interim deployment of SFC functionality in brownfield networks.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search