%% You should probably cite draft-song-sfc-legacy-sf-mapping-08 instead of this revision. @techreport{song-sfc-legacy-sf-mapping-02, number = {draft-song-sfc-legacy-sf-mapping-02}, 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/02/}, author = {Haibin Song and Jianjie You and Lucy Yong and Yuanlong Jiang}, title = {{SFC Header Mapping for Legacy SF}}, pagetotal = 12, year = 2014, month = jul, day = 7, abstract = {A Service Function Chain (SFC) goes through a list of ordered service functions. One assumption of this document is that legacy service function can participate in the service function chain, but they are not aware of the SFC header, nor interpret it. This document provides a mechanism between an SFC proxy and an SFC-unaware Service Function (i.e. legacy SF), to identify the SFC header associated with a packet that is returned from a legacy SF, without SFC header being explicitly carried in the wired protocol between SFC Proxy and legacy SF.}, }