Kindly help on below queries. Regards, Saumya.
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Dikshit, Saumya Sent: Monday, January 15, 2024 8:53 PM To: BESS <bess@ietf.org>; draft-sajassi-bess-evpn-ip-alias...@ietf.org Cc: bess-cha...@ietf.org Subject: Re: [bess] Queries to authors of https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html Resending To the email-alias "draft-sajassi-bess-evpn-ip-alias...@ietf.org<mailto:draft-sajassi-bess-evpn-ip-alias...@ietf.org>" for authors Hello Authors of draft https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html> I have following queries and comments on the draft. Kindly help with your response >>> Context of section >>> https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html#section-4<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html#section-4> >>> , I have two queries about "A PE may need to advertise more than one IP >>> A-D per ES route for a given ES because the ES may be in a multiplicity of >>> IP-VRFs and the Route Targets for all of these IP-VRFs may not fit into a >>> single route." 1. What is the deployment scenario for this ? 2. Is it EVPN connectivity between the PE and CE, which maps to more than one Tenant VRFs. * But then EVPN between PE and CE will render the ES as inactive, >>> In section >>> https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html#name-ethernet-segments-for-l3-al<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html#name-ethernet-segments-for-l3-al> >>> , Do we need to rewrite this sentence ", an active static route to >>> 192.0.2.1 via next hop 192.51.100.2 would make the ES operationally active >>> in PE1, and the eBGP routes received from CE1 with next hop 192.0.2.1 will >>> be re-advertised as RT-5 routes with ESI-1." 1. Why eBGP routes ? Why not same AS, iBGP/ISIS/OSPF ? >>> Under section >>> https://<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html>www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html#section-4.3<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html>: >>> Handling Silent Host MAC/IP route for IP >>> <https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html> >>> Aliasing<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html>, >>> I have few queries 4. The applicability to other models like "Snooping in interface less IP-VRF" scenario ? How is that to be handled. 5. The section heading needs to be rectified, to be made generic for silent host handling. 6. The following statement "Thus, to avoid packet loss, when PE2 detects loss of reachability to PE1, it should trigger ARP/ND requests for all remote IP prefixes received from PE1 across all affected IP-VRFs. " * It should not be remote IP Prefixes. Giving the impression that it's learnt from other PEs and not local to the segment. >>> Section >>> https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html#name-ip-aliasing-for-evpn-ip-pre<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html#name-ip-aliasing-for-evpn-ip-pre> >>> : Aliasing for EVPN IP Prefix >>> <https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html> >>> routes<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html> 7. How should PE2 react to PE1 withdraw for EVPN IP routes? >>> Section >>> https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html#name-ip-aliasing-for-evpn-ip-pre<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html#name-ip-aliasing-for-evpn-ip-pre> >>> : Case: IP >>> <https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html> >>> Aliasing in a Centralized Routing >>> Model<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html> 8. How is CE router ID reachability over EVPN. Shouldn't it be via an underlay network route ? Regards, Saumya.
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
