You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The spec currently suggests two ways to indicate the existence of INT after TCP/UDP/ICMP.
DSCP
Destination L4 port
Each has certain drawbacks, for example DSCP approach limits the available DSCP code points from 64 to 32. Changing the destination port will change ECMP behavior and complicate ACL.
The spec currently suggests two ways to indicate the existence of INT after TCP/UDP/ICMP.
Each has certain drawbacks, for example DSCP approach limits the available DSCP code points from 64 to 32. Changing the destination port will change ECMP behavior and complicate ACL.
Another options are
We can discuss pros/cons of the overall approaches in the following meetings and include in the spec.
The text was updated successfully, but these errors were encountered: