Thread (4 messages) flat view 4 messages, 2 authors, 2016-11-03

Re: Time to revisit LISP?

From: David Miller <davem@davemloft.net>
Date: 2016-11-03 21:00:20

From: Tom Herbert <redacted>
Date: Thu, 3 Nov 2016 13:57:59 -0700
On Thu, Nov 3, 2016 at 1:37 PM, David Miller [off-list ref] wrote:
quoted
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, rather than towards, these
kinds of architectures.
OVS is quite different I think. LISP is a specific resolution protocol
of identifier to locator as opposed to be some open ended mechanism to
resolve some arbitrary definition of flows like OVS. Also, I don't
think there's any specific requirement in LISP that prevents on from
implementing the mapping protocol in the kernel, it should just be a
simple UDP communication.

Do you see anything in the protocol itself that would be a showstopper?
I'd have to see the code and how it works.  I can't review hypothetical
implementations.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help