Subject: [sfc] FW: New Version Notification for draft-song-sfc-legacy-sf-mapping-00.txt

From: "Songhaibin (A)" <[email-masked]>
Date: Thu, 10 Apr 2014 06:10:10 +0000

Hi guys,

We have just submitted a draft for legacy service function support. The motivation is that legacy service functions can participate in SFC, but they do not understand SFC header. Service Forwarding Engine is responsible for decapsulating the SFC header locally, sending the packet to legacy SFI, and then encapsulating the SFC header after receiving the returned packet. Mechanisms for mapping the SFC header to some field of the packet have been proposed. 

http://www.ietf.org/internet-drafts/draft-song-sfc-legacy-sf-mapping-00.txt

Any comments are appreciated!

Best Regards!
-Haibin

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]
> Sent: Thursday, April 10, 2014 9:40 AM
> To: Songhaibin (A); Lucy yong; Songhaibin (A); Lucy yong; Jiangyuanlong;
> Jiangyuanlong
> Subject: New Version Notification for draft-song-sfc-legacy-sf-mapping-00.txt
> 
> 
> A new version of I-D, draft-song-sfc-legacy-sf-mapping-00.txt
> has been successfully submitted by Haibin Song and posted to the IETF
> repository.
> 
> Name:		draft-song-sfc-legacy-sf-mapping
> Revision:	00
> Title:		SFC Header Mapping for Legacy SF
> Document date:	2014-04-10
> Group:		Individual Submission
> Pages:		10
> URL:
> http://www.ietf.org/internet-drafts/draft-song-sfc-legacy-sf-mapping-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-song-sfc-legacy-sf-mapping/
> Htmlized:
> http://tools.ietf.org/html/draft-song-sfc-legacy-sf-mapping-00
> 
> 
> 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.
> 
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat