Hi Shunwan, Nan, Haibo,
The Remote VRF Information TLV nicely closes the "which remote VPN instance did
this best-path come from" gap in RFC 9069 Loc-RIB reporting. I believe there's
a directly analogous problem on the EVPN side that this draft's mechanism could
cover with minor generalization:
*
draft-saum-grow-bmp-afi-safi-evpn defines per-EVI EVPN RIB stats keyed by RD
(Section 2.2), and separately calls out "dynamic inter-VRF route leaking
(IVRL)" for EVPN Type-5/IRB routes as an area needing counters.
*
Today your draft scopes the Remote VRF Information TLV to VPNv4/VPNv6 Loc-RIB
only (Figure 1 example).
*
Would you be open to extending the applicability statement to the EVPN AFI/SAFI
(25/70).
*
Thus, single Remote VRF Information TLV mechanism covers both L3VPN and
EVPN-IRB inter-VRF leak visibility?
* If that's in scope for a -02, we'd like to contribute the EVPN-side text
and an example (analogous to your Figure 1) showing an EVPN Type-5 (prefix)
route leaked across VRFs with the Remote VRF Information TLV attached.
(Hi Nan, a separate topic from your rel-enhancement/filtering thread which I
was trying keep pace with. Just flagging in case both land in your inbox close
together.)
Let us know if a joint revision makes sense, happy to send a draft diff.
@Srivastava, Mukul<mailto:[email protected]> and @Changwang
Lin<mailto:[email protected]> are also co-author to
draft-saum-grow-bmp-afi-safi-evpn
Thanks ,
Saumya
_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]
