Deepak,
Didn't have time to go into this on the call, but the draft and your
slides refer to "96 bits of customer data"
I understand why that was needed for TRILL - basically the entropy for
ECMP/LAG is calculated at each hop in TRILL so it needs to look at the
inner Ethernet, IP, and TCP/UDP headers.
But for NVO3 the thinking is to use a UDP header where the source UDP
port is set (in the ingress NVE) to some hash of those inner addresses
and ports.
If that is the source of entropy, why do we need to also carry 96 bits
of the inner packet in the OAM frames?
Regards,
Erik
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
