Skip to main content

An MPLS-Based Forwarding Plane for Service Function Chaining
RFC 8595

Revision differences

Document history

Date By Action
2020-11-30
Jenny Bui Posted related IPR disclosure Huawei Technologies Co.,Ltd's Statement about IPR related to RFC 8595 and RFC 7665
2019-08-26
Gunter Van de Velde Closed request for Telechat review by OPSDIR with state 'Overtaken by Events'
2019-08-26
Gunter Van de Velde Assignment of request for Telechat review by OPSDIR to Carlos Martínez was marked no-response
2019-06-07
(System)
Received changes through RFC Editor sync (created alias RFC 8595, changed abstract to 'This document describes how Service Function Chaining (SFC) can be achieved …
Received changes through RFC Editor sync (created alias RFC 8595, changed abstract to '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.', changed pages to 32, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-06-07, changed IESG state to RFC Published)
2019-06-07
(System) RFC published