Comment 5 for bug 1587486
Revision history for this message
| Igor D.C. (igordcard) wrote Re: Support SFC Encapsulation | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
[Still regarding comment #1 - I've also updated the description in the RFE]
Reply to comment #2:
The classification is the same, TCP, but there is no classifier involved. It is strictly forwarding based on a SFF, i.e. looking up the Service Path Header and deciding the next hop. Somewhere in port-chain #4, before reaching the TCP Optimizer function, a different classification criteria was matched in comparison to port-chain #1, which made traffic go into a different SFP, consequently (potentially) getting processed by different SFs, even if somewhere in the middle the same SF instance processes the same kind of traffic. Flows are encapsulated and isolated by different service path headers, so next hops are no longer only dependent on classification.