Hi Jorge, Inline.
From: BESS <bess-boun...@ietf.org> on behalf of "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.raba...@nokia.com> Date: Friday, February 5, 2021 at 6:05 AM To: TULASI RAM REDDY <tulasiramire...@gmail.com>, Muthu Arul Mozhi Perumal <muthu.a...@gmail.com> Cc: "bess@ietf.org" <bess@ietf.org> Subject: Re: [bess] RFC 8584: EVPN DF Election - Originating Router's IP Address of different address family Hi Tulasi, For the default DF algorithm, I think at that point it will be up to the implementation how to resolve the candidate list PEs with originating IPs of different family. <Satya> This is should be standardized as otherwise It will result in different decisions in different PEs. I suggest a mention in 7432-bis. I know of some implementations that do what you are saying, but you can’t assume all RFC7432/8584 implementations will do that. Thanks. Jorge Thanks, Satya From: BESS <bess-boun...@ietf.org> on behalf of TULASI RAM REDDY <tulasiramire...@gmail.com> Date: Friday, February 5, 2021 at 2:15 PM To: Muthu Arul Mozhi Perumal <muthu.a...@gmail.com> Cc: bess@ietf.org <bess@ietf.org> Subject: Re: [bess] RFC 8584: EVPN DF Election - Originating Router's IP Address of different address family Thanks Muthu. Shouldn't numeric value here mean simply the 4byte or 16 byte unsigned value representation of the IP address field? Thinking loudly on how to interpret numeric value and the limitations here. Any comments? each PE builds an ordered list of the IP addresses of all the PE nodes connected to the Ethernet segment (including itself), in increasing numeric value Thanks, Tulasi. On Fri, Feb 5, 2021 at 3:15 PM Muthu Arul Mozhi Perumal <muthu.a...@gmail.com<mailto:muthu.a...@gmail.com>> wrote: Hi Tulasi, I think the problem is, there is no standard way to numerically compare IPv4 with IPv6 addresses to form an ordered list. So, all the PEs multihomed to an ES may not always arrive at the same DF (or BFD in the case of single-active L-LINE service) with the default DF election algo. This is problematic (and may cause traffic loops). Hence, the default DF election algo works only when all PEs multihomed to an ES have Originating Router's IP Address of the same AF.. Regards, Muthu On Thu, Feb 4, 2021 at 7:58 PM TULASI RAM REDDY <tulasiramire...@gmail.com<mailto:tulasiramire...@gmail.com>> wrote: Hi All, As mentioned in the Problem Statement of RFC8584 Sec 1.3, Default DF algorithm is expected to have all multihomed PEs to have Originating IP of the same address family. Do we see any interop issue if the different address families are considered, i.e. ordering in ascending order based on numerical value in Originating IP here? For IPv4 read 4 octets as unsigned integer and IPv6 is considered as 16 octet unsigned integer. 1.3<https://tools.ietf.org/html/rfc8584#section-1.3>. Problem Statement Default DF election algorithm assumes that all the PEs who are multihomed to the same ES (and interested in the DF election by exchanging EVPN routes) use an Originating Router's IP address [RFC7432<https://tools.ietf.org/html/rfc7432>] of the same family. Thanks, TULASI RAMI REDDY N _______________________________________________ BESS mailing list BESS@ietf.org<mailto:BESS@ietf.org> https://www.ietf.org/mailman/listinfo/bess -- TULASI RAMI REDDY N
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
