On Aug 11, 2009, at 12:46 PM, Dino Farinacci wrote:
Every host I'm aware of has a facility for setting up an interface
that routes some set of packets--including potentially the default
route--through a tunnel interface that then passes the packet to
userspace for processing.
We call "LISP tunnels" as "dynamic encapsulating tunnels" where an
implementation must not implement the tunnel as a logical
interface. The implementation cannot scale if it does this. You get
the level of indirection by doing another lookup in another data
structure called the "map-cache".
I don't think I understand this...
Why couldn't LISP be implemented as a logical interface that
encapsulates or not based on the contents of the LISP Mapping cache
and the results of mapping lookups?
Because you could have 100K of them. Interface data structures come
with all kinds of other stuff that doesn't apply here. And guess what
if you had 100K map-cache entries, the number of logical interfaces is
equal to the sum of all locators for all 100K entries.
Dino
Margaret
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
