Subject: [lisp] LISP Intro document

From: Ronald Bonica <[email-masked]>
Date: Fri, 14 Nov 2014 03:06:20 +0000

Folks,

The following paragraph isn't worded very well:

  The initial motivation in the LISP effort is to be find in the	
 	   routing scalability problem [RFC4984], where, if LISP is completely	
 	   deployed, the Internet core is populated with RLOCs while Traffic	
 	   Engineering mechanisms are pushed to the Mapping System.  Where RLOCs	
 	   are quasi-static (i.e., low churn) and hence, the routing system	
 	   scalable [Quoitin] while EIDs can roam anywhere with no churn to the	
 	   underlying routing system.  However, the separation between location	
 	   and identity that LISP offers makes it suitable for use in additional	
 	   scenarios such as Traffic Engineering (TE), multihoming, and mobility	
 	   among others.

The point I meant to make was:

-	Back in 2007, LISP's initial motivation was to reduce the size of routing tables in the global internet
-	When the LISP transition period ends, LISP will make routing tables shrink. Global routing tables will contain RLOCs only. The LISP mapping system will contain EIDs and EID/RLOC mappings
-	During a transition period, when PxTRs leak EIDs into the global routing system, it is not known whether LISP will make global routing tables grow or shrink or stay the same

Ron Bonica