Hi Saumya The remote PE router processing the lsp ping packet, does consistency checks between data plane and control plane. RD, ESI fields along with other fields defined in the sub-tlvs are used for that purpose. Wildcard/don’t care values for these fields will defeat the purpose of DP-CP consistency checks.
Thanks Parag From: "Dikshit, Saumya" <saumya.diks...@hpe.com> Date: Thursday, September 2, 2021 at 1:42 PM To: "draft-ietf-bess-evpn-lsp-p...@ietf.org" <draft-ietf-bess-evpn-lsp-p...@ietf.org>, "bess@ietf.org" <bess@ietf.org> Cc: "bess-cha...@ietf.org" <bess-cha...@ietf.org> Subject: Query/comments on draft-ietf-bess-evpn-lsp-ping-05 Resent-From: <alias-boun...@ietf.org> Resent-To: <par...@cisco.com>, <sbout...@ciena.com>, <gregimir...@gmail.com>, <saja...@cisco.com>, <ssa...@cisco.com> Resent-Date: Thursday, September 2, 2021 at 1:42 PM [sending the queries in a different email with changed subject line] Hello Authors of draft-ietf-bess-evpn-lsp-ping draft, I have following queries regarding this draft: >>>> Do we intend-to-use/call-out-usage-of “wild-card/don’t-care” values for >>>> attributes carried in the sub-TLVs ? For example, If the admin intends to check the reachability to host (MAC_X/IP_X) published (in route-type-2) by remote PE. The remote PE learnt it locally over ESI_X against Vlan X (mapped to BD_XYZ). Is it possible, that the “EVPN MAC sub-tlv” can carry the “Route Distinguisher” and “Ethernet Segment Identifier” as don’t care. >>>> Another caseto handle would be test the reachability to tenant-VRF VRF_X >>>> (with EVPN mapped EVI) configured on the remote PE, PE1. VRF_X has no active IP/IPv6 interface configured and its sole usage is to obtain the leaked (via IVRL) routes from other VRFs (non-EVPN) and PE1 published this to other peers via EVPN control plane. Till the first prefix (learnt ) route is published (Route Type 5) by PE1 for the EVI (mapped to VRF_X), the tunnels will not be provisioned on other PEs. In order to test the reachability to VRF_X (on PE1) from another PEs, let’s say, PE2 or a centralized-controller (which can emulate/supports MPLS), It may need to carry all/subset-of attributes with “don’t-care/wild-card” in “EVPN IP Prefix Sub-TLV”. Please let know your thoughts on above. Thanks Saumya.
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess