In the shared memory case, indeed, it is very reasonable to look at the
proxy as an arm of the function.
In SFC, we do look at it (the proxy as an arm of the SF) that way more
generally. We can do that because the SFC architecture calls that out.
Given that the other cases do involve network
Hi Joel,
Thank you for your email.
A proxy and its associated SF can be seen from the network as a single entity:
a packet enters this entity from the network, gets processed by the SF, and
exits towards the network. The packet modifications that occur between the
entry and exit of this
become a chair issue, in which case, I will look at it through a
different lens. Heck, I may even disagree with myself.>
Let me start by saying that I understand and support what the draft is
trying to do. While I like SFC, I am under no illusions that it is or
should be the only answer to
