Folks, The editors correctly observe that Section 6.2 needs to be rewritten. A better approach would be to note that LISP is a map-and-encap strategy. An ingress encapsulation endpoint:
- accepts a packet that is addressed from one address space (EID) - maps the EID addresses to corresponding addresses in another space (LOC) - encapsulates the incoming packet in another that is addressed using LOC space - forwards the packet to the egress encapsulation endpoint where it is de-encapsulated In this regard, LISP is similar to many other encapsulation and VPN technologies (e.g., GRE, L3VPN). LISP is different from GRE and L3VPN because it pulls mapping information to itself. By contrast, GRE mapping information is generally configured statically. L3VPN mapping information is pushed by BGP. Therefore, LISP must deal with the problems of stale mapping information and cache misses. Also, LISP must deal with the problem of egress encapsulation node liveness. Ron Bonica _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
