Hi Andrew, Allow me to share some more thoughts.
Given we are talking about quagga specific command keywords here, I think the implementation (in quagga routing suite) we are talking about is only dealing with routing and forwarding(just RIB there actually) aspects of this package. Traditionally, Logical Router is a router level concept. Multiple instances within quagga may also be needed for cases where user is not designing a 'Logical Router' as such. Hence (also) my suggestion to not take a keyword that already has some wider/narrower defined/assumed notions. Extending one of your point partly, and given quagga zebra is RIB only, which isn't doing forwarding. Do we want to think of just 'MR' ? - Multiple Routing that is. Regards, Vipin On Mon, Jun 15, 2015 at 3:57 PM, Andrew Qu <[email protected]> wrote: > Hi Vipin, > > > > I still feel LR or DLR kind key word may be better. > > Firstly, LR is not “logical routing” in this thread, it means “logical > router”. > > Hence LR is a more a logical container while MRF may be contained within. > > And MRF is very close to VRF in meaning anyway which I personally want to > avoid > > In using. > > > > Again, as I said earlier, when a user uses such CLI, it means > administratively that > > He must have created logical containers already, so let’s try to use > container level > > CLI key word for this. > > > > Thanks, > > Andrew > > > > > > > > *From:* Vipin Kumar [mailto:[email protected]] > *Sent:* Monday, June 15, 2015 3:22 PM > *To:* Andrew Qu > *Cc:* Jafar Al-Gharaibeh; Vincent JARDIN; [email protected] > *Subject:* Re: [quagga-dev 12737] Re: VRF -> TBD/XXX > > > > > > Bringing back keyword MRF (Multiple Routing and Forwarding) into the > discussion. > > > > MRF name is abstract enough to accommodate different mapping technologies > underneath (netns, route-tables, ..) while being close to what the > design/code structure is for this feature. Implementation just segregates > routing and forwarding vertically into multiple instances working on > different set of interfaces. > > (And there isn't much virtual about it, its real multiplication) > > > > The snippet from Vincent may look like this > > > > On Linux, it'll be: > - MRF -> netns > - MRF -> table kernel IDs > > For other OS, > - MRF -> technology XYZ > > > > > > Not that we have to be biased based on the feedback from other > communities, but Linux kernel community also likes this name. > > > > On a lighter note, " 'logical' routing and forwarding", sounds as if > 'routing and forwarding' was not logical prior to that ;) > > > > Sounds ok? > > > > Regards, > > Vipin > > > > > > On Mon, Jun 15, 2015 at 10:11 AM, Andrew Qu <[email protected]> > wrote: > > Also, if we consider the perspective when such CLI may be used, there are > more properties than just forwarding in > The physical system. To let backend process be clear which container/LR > to assign this forwarding > Table, LR <name_of_logical_container | namespace_in_linux_as_example> > table_id <ID> might be less confusing. > > Thanks, > > Andrew > > > -----Original Message----- > From: Jafar Al-Gharaibeh [mailto:[email protected]] > Sent: Monday, June 15, 2015 10:02 AM > To: Vincent JARDIN; [email protected] > Subject: [quagga-dev 12736] Re: VRF -> TBD/XXX > > I think of "LR: logical router" as something more than a table. i.e, a > collection of logical tables might serve the same logical router, just like > a physical router might have multiple routing tables. So I suggest LR to > mean Logical Routing table, if LRF: Logical Routing and Forwarding table is > too long. :) > > --Jafar > > > On 6/15/2015 4:33 AM, Vincent JARDIN wrote: > > We agree that VRF is tainted and we need an internal name which is > > more neutral. > > > > On Linux, it'll be: > > - XXX -> netns > > - XXX -> table kernel IDs > > > > For other OS, > > - XXX -> technology XYZ > > > > proposals are: > > LRF, Logical Routing and Forwarding, > > logical-table, > > Routing Domain (and hence Routing Domain ID), > > Network Domain (NDID), > > LR (logical router), > > > > Do I forget a proposal into this list? Please, add it to this thread. > > > > Thank you, > > Vincent > > > > _______________________________________________ > > Quagga-dev mailing list > > [email protected] > > https://lists.quagga.net/mailman/listinfo/quagga-dev > > > > > _______________________________________________ > Quagga-dev mailing list > [email protected] > https://lists.quagga.net/mailman/listinfo/quagga-dev > > ************* 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 > > > > ************* 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
