Re: [Idr] New Version Notification for draft-wang-idr-rd-orf-03.txt

[Robert Raszuk <[e-mail]>]

>
> By day one design L3VPNs or L2VPNs are overloading all PEs to parse and
> drop all BGP updates which do not carry routes containing at least one
> intersecting RT.
>
> *[WAJ]  But until now, various filter policies for the unnecessary BGP
> updates has been added, do you agree?*
>

There is a difference between "unnecessary" and those which are caused by
wrong service deployment.

*[WAJ] Yes, RD-ORF can also be used within the device, but push the policy
> to its upstream peer or final to the overwhelming source is better.*
>

This is one of the biggest issue I have with this draft. ORF is not
transitive and you are making it transitive (even if you pretend it is
not).

I am not against automated filtering (where it make sense), but if so pls
do it correctly. Define a new SAFI just like we did with RTC, call it RDC
(RD Constrained) and use it at your own risk to break VPNs in your network.

While there custom update generation especially based on more then one
constraint has a high cost. You need to generate update per each such peer
individually walking full vpnv4 table. Dropping is cheap. Replication is
cheap. Keep this in mind pls so your vendor's implementation engineers have
easy life :).

Cheers,
R.