Re: Time to revisit LISP?

2016-11-03 Thread David Miller
From: Tom Herbert Date: Thu, 3 Nov 2016 13:57:59 -0700 > On Thu, Nov 3, 2016 at 1:37 PM, David Miller wrote: >> Userspace resolution of paths in response to data path signalling >> simply does not scale and is fundamentally an extremely poor design >> choice. We're trying to move away from, rat

Re: Time to revisit LISP?

2016-11-03 Thread Tom Herbert
On Thu, Nov 3, 2016 at 1:37 PM, David Miller wrote: > From: Tom Herbert > Date: Thu, 3 Nov 2016 12:22:52 -0700 > >> For instance, one of the his questions is: >> >> "What is to keep one from having to service a full Map-Request --> >> Map-Reply cycle for every packet received?" >> >> This can be

Re: Time to revisit LISP?

2016-11-03 Thread David Miller
From: Tom Herbert Date: Thu, 3 Nov 2016 12:22:52 -0700 > For instance, one of the his questions is: > > "What is to keep one from having to service a full Map-Request --> > Map-Reply cycle for every packet received?" > > This can be solved by judicious rate limiting, for instance the > infrastr

Time to revisit LISP?

2016-11-03 Thread Tom Herbert
Hi Chris, Looking at netdev archives I see that Dave's response to the LISP patches from June 2014 was: "Sorry, I'm not too thrilled about LISP and this patch in particular, from several different angles. And therefore I'm going to mark this patch deferred and not apply it at this time." It see