%% You should probably cite draft-song-sfc-legacy-sf-mapping-08 instead of this revision.
@techreport{song-sfc-legacy-sf-mapping-05,
    number =    {draft-song-sfc-legacy-sf-mapping-05},
    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/05/},
    author =    {Haibin Song and Jianjie You and Lucy Yong and Yuanlong Jiang and Linda Dunbar and Nicolas Bouthors and David Dolson},
    title =     {{SFC Header Mapping for Legacy SF}},
    pagetotal = 17,
    year =      2015,
    month =     jul,
    day =       6,
    abstract =  {A Service Function Chain (SFC) defines a set of abstract Service Functions (SF) and ordering constraints that must be applied to packets and/or frames selected as a result of classification. One assumption of this document is that legacy service functions can participate in service function chains without having support for the SFC header, or even being aware of it. This document provides a mechanism between an SFC proxy and an SFC-unaware service function (herein termed "legacy SF"), to identify the SFC header associated with a packet that is returned from a legacy SF, without an SFC header being explicitly carried in the wired protocol between SFC proxy and legacy SF.},
}