Hi all,
I find some conflicting rules about interface-to-VRF binding between
draft-ietf-rtgwg-ni-model-12 and draft-ietf-bess-l2vpn-yang-09.txt.
It is as below:
RULE1: [NI-model] Section 3.2 says that:
The bind-network-instance-name leaf provides the association between an
inter
Hi,
I agree w/ both Jorge and Krzysztof. All we need is a new DF Election
capability, port active load balancing, and a description of how each of the
defined DF elections is modified. For HRW, RFC 8584 already describes
computing a 32 bit CRC over the concatenation of Ethernet Tag and ESI so