Configuration of INT Sink role

[mhira1]

The INT role of a network element is typically a function of the location of the element in the network topology. Elements in the network core serve as INT transit hops. Elements at the edge of the network function as (i) INT source for a “watchlist” of traffic flows received from the workloads and/or (ii) INT sink for all traffic carrying INT headers received from the core of the network.

However, some use-cases may require INT sink role to be configurable, i.e. a network element may serve as INT transit hop for some traffic whereas it may strip off INT headers and act as INT sink for some other traffic. One possible use-case is where a software entity behind a Top-of-Rack switch (ToR) serves as INT source, but the ToR closest to the destination acts as INT sink for traffic flowing to destinations that may want to offload INT sink capability to the Top-of-Rack switch.

This issue is being created to discuss relevant use-cases and an approach of addressing the use-cases. For example, would it be enough to configure INT sink role based on egress port ID?