%% You should probably cite draft-song-sfc-legacy-sf-mapping-08 instead of this revision. @techreport{song-sfc-legacy-sf-mapping-01, number = {draft-song-sfc-legacy-sf-mapping-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-song-sfc-legacy-sf-mapping/01/}, author = {Haibin Song and Lucy Yong and Yuanlong Jiang}, title = {{SFC Header Mapping for Legacy SF}}, pagetotal = 11, year = 2014, month = apr, day = 17, abstract = {SFC (Service Function Chaining) is used to manipulate service functions with easy creation, updating and deletion. A service function chain goes through a list of ordered service function instances. One assumption of this document is that legacy service function instances can participate in the service chain. They are not aware of the SFC header, nor interpret it. This document provides a mechanism between a Service Forwarding Entity (SFE) and a Service Function Instance (SFI), to identify the SFC header associated with a packet that is returned from an SFI, without SFC header being explicitly carried in the wired protocol between SFE and SFI.}, }