Hi Nicolas, Comments in lines,
-----Original Message----- From: Nicolas Dichtel [mailto:[email protected]] Sent: Thursday, May 21, 2015 1:40 AM To: Andrew Qu; Jafar Al-Gharaibeh; [email protected] Subject: Re: [quagga-dev 12336] Re: VRF and Multiple-Instance OSPF Le 20/05/2015 20:07, Andrew Qu a écrit : > Hi Nicolas, > > "vrf-lite" I referred is not policy based routing, but I agreed with > you that simply call VRF. > > Just curious, do you have link to the corner case that can't be > solved by implementing VRF? Here is the main thread (but there was also other discussions): http://thread.gmane.org/gmane.linux.network/349351/focus=349575 Some highligths: - "We have been playing with ip rules to implement vrfs. And the blocker today is that we cannot bind a socket to a vrf (routing tables in this case)." - "Also, the downside of using multiple-tables based solution might probably be lack of scalability, as the amount of ip rules in such a scheme grows linearily with number of L3 segments." [Andrew] there is no point to bind a socket to each VRF, the requirement is on wrong design in the first place, it is not VRF's limitation again. VRF itself is just a "table", any object is interested in acquiring VRF table, Just need to talk to Zebra (in quagga) case. Since we are developing the NOS for ASIC/NP based router/switch, so, we are Exactly doing this right now. Please refer to my design spec I send out. We just subscribe to zclient (zebra client) Zebra now due to our support, can Send out all routing table (global, VRFs) to its client. I am not quite follow 2nd limitation, but it does not seem to be VRF's own Limitation at all. VRF is just a separate routing table, it is sharing exact same property As regular routing table. Thanks, Andrew ====== please ignore line below ====== it is not intentional ===== Regards, Nicolas ************* Email Confidentiality Notice ******************** The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you! _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
