Hi Sasha
My thoughts are that as some NLRI have the Route Type concept explicitly as part of the NLRI framework I think it would be very valuable for operators to have the BGP Yang model updated to reflect those NLRI that are typed and list out all the route types. One consideration is that for example EVPN has had continuous development of new route types, so once BGP Yang is published you would have to update the Yang model for any missed. Also as long as a draft introducing a new route type is adopted can that be the bar that is set that the type can be added to the Yang model or would the draft have to be a published RFC before the route type can be added. Many Thanks for noticing this. Kind Regards Gyan On Wed, Jul 3, 2024 at 9:57 AM Alexander Vainshtein < alexander.vainsht...@rbbn.com> wrote: > Hi all, > > I have a question about usage of BGP policies for “typed” SAFI in MP-BGP. > > > > These days there are already quite a few “typed” SAFI, i.e., SAFI in which > the NLRI of the route includes the route type followed by the > type-specific data. > > > > Known cases include: > > · MCAST-VPN [RFC6514 <https://datatracker.ietf.org/doc/html/rfc6514>] > > · MCAST-VPLS [RFC7117 <https://datatracker.ietf.org/doc/html/rfc7117>] > > · EVPN [RFC7432 <https://datatracker.ietf.org/doc/html/rfc7432>] > > · BGP-LS [RFC7752 <https://datatracker.ietf.org/doc/html/rfc7752>] > > · CAR [Color-aware routing draft > <https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-car-10>]. > > > > > > It seems that the current definitions of BGP policies (e.g., see the BGP > YANG Model > <https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-model-17> > draft) do not provide ability to define conditions that would, when applied > to a specific SAFI with “typed” NLRI, identify NLRI of specific type. One > example could be a rule that would be applied to EVPN Type 5 (IP Prefix) > routes and check their destination IP Prefix bin the same way destination > IP prefixes can be checked for, say, VPNv4 or VPNv6 routes. > > > > I wonder if the corresponding extension would be of any interest to the WG. > > > > > > Regards, and lots of thanks in advance, > > Sasha > > > > > *Disclaimer* > > This e-mail together with any attachments may contain information of > Ribbon Communications Inc. and its Affiliates that is confidential and/or > proprietary for the sole use of the intended recipient. Any review, > disclosure, reliance or distribution by others or forwarding without > express permission is strictly prohibited. If you are not the intended > recipient, please notify the sender immediately and then delete all copies, > including any attachments. > _______________________________________________ > rtgwg mailing list -- rtgwg@ietf.org > To unsubscribe send an email to rtgwg-le...@ietf.org >
_______________________________________________ rtgwg mailing list -- rtgwg@ietf.org To unsubscribe send an email to rtgwg-le...@ietf.org
