SFC Header Mapping for Legacy SF draft-song-sfc-legacy-sf-mapping-03 Haibin Song Jianjie You Lucy Yong Yuanlong Jiang Linda Dunbar Nicolas Bouthors 1IETF91 Honolulu

Motivation 2 SFC-unaware SF SFC Proxy (1) (2) (3) (4) SFC-unaware SF: A conventional service function that does not support SFC header. SFC Proxy: Removes and inserts SFC encapsulation on behalf of an SFC-unaware service function. How to identify the SFC header associated with a packet that is returned from a legacy SF? IETF91 Honolulu Existing SFs may not be able to support SFC solution developed here SFC Proxy is used b/w SFF and SFC-unaware SFs

For Transparent SF 3 SFC-unaware SF SFC Proxy (1) (2) (3) (4) L2 MAC Address VLAN QinQ VXLAN 5-tuple For Transparent SFs Transparent SF: A service function that does not change any bit of the original service packet header (Layer 2, layer 3, and layer 4) sent to it, but it may drop packets. IETF91 Honolulu

For Non-Transparent SF 4 SFC-unaware SF SFC Proxy (3) (4) (5) (6) Non-transparent SF: A service function that changes some part of the original service packet header sent to it. Control Plane (1) (2) 5-tuple mapping rules 5-tuple mapping Control plane provides 5- tuple mapping rules. For Non-transparent SFs IETF91 Honolulu

Operation Considerations 5IETF90 Toronto

Next Steps Solicit comments from the WG Request WG adoption IETF91 Honolulu6