Subject: Re: [sfc] draft-boucadair-sfc-requirements-03 Service function discovery

From: "Jmh.direct" <[email-masked]>
Date: Wed, 05 Mar 2014 22:14:10 +0000

Yes, we have to pass metadata to the dervice functions een when we are using transport for the chain forwarding.

,Yours,
Joel

Sent from my Samsung smartphone on AT&T

-------- Original message --------
Subject: RE: [sfc] draft-boucadair-sfc-requirements-03 Service function discovery 
From: Nicolas BOUTHORS <[email-masked]> 
To: "Paul Quinn (paulq)" <[email-masked]>,"Joel M. Halpern" <[email-masked]> 
CC: "[email-masked]" <[email-masked]>,"Jim Guichard (jguichar)" <[email-masked]>,Ron Parker <[email-masked]>,Dave Dolson <[email-masked]>,"[email-masked]" <[email-masked]> 

Joel, Paul

>> Agreed, we should not impose forwarding requirement onto SF.   The SFC-proxy assumes responsibility for SFC encap handling, the rest of the architecture remains unchanged (>> i.e. the forwarding is performed by the appropriate logical block)

A reminder maybe.  Routing traffic is not the only objective of SFC, metadata handling is one too.

Not imposing forwarding requirement onto SF should not mean that we do not pass inband metadata (if so exist) to the SF including possible contextual information
such as policy id, application id or subscriber id, as set by the classifier and possibly modified by previous SF in the path.

Nicolas