Anandhi Dhanabalan
Anandhi Dhanabalan
MACSEC rules are bound to a port. These rules have MACSEC flow as action. The MACSEC flow can have multiple SCs. Adding Port to SC association at MACSEC SC, could...
> > This change does not allow using a MACsec flow for multiple MACsec ports. Instead of binding a MACsec port to a MACsec flow, can a MACsec port be...
If MACsec port is allowed to be bound to SC, that would break the existing semantics For example, In illustration below MACSEC port P1 would point to a MACsec flow...
> There is no implicit relationship limiting a flow from being used for multiple ports. Multiple ACL entries can be bound to a MACsec flow, and those can belong to...
@SidharajU , AFAIK, It not prudent to share a flow across macsec ports in hardware though current SAI software modelling does not prevent it explicitly. As @dipankar-ba stated, if your...
@dipankar-ba , Attaching port to SC or Flow, will have same limitation as multiple ACL tables bound to different physical ports can point to these. Hence a work flow from...
Can you also add the spec you are referring for this trimming feature ?
Creating a generic solution for all next hop group types would be more future extensible.