LISP finally rises again (my 1975 LISP was code, this LISP is ... read on)
but first, skipping LISP and doing ... read on
VL2 = Virtual Layer 2 (virtualize datalink layer 2)
where::= @datacenter
old way: :=
serveripaddress <<<>>> clientipaddress (network layer 3)
macaddress <<<>>> macaddress (datalink layer 2)
problem::=
macaddress:ipaddress mapped with ARP (Address Resoution Protocol) broadcast
*** scale breaks after some point since clouds xx times servers in the old days
solution::=
virtualize away the macaddress:serveripaddress mapping with an applicationaddress
(call it serveraddress) that at layer "2.5" maps to the old ipaddress:macaddress
*** scales better
************************************************************************************
LISP = Locator/ID Separation Protocol (virtualize ipaddress network layer 3)
where::= in network (routers ... network layer 3)
old way::= server pushes packet/datagram to next router who pushes to next router etc
problem: :=
scale breaks after some point since clouds xx times servers in old days results in
routing tables (who is my next router) growing,
running out of ip addresses, can't easily move servers elsewhere
solution::=
map old ipaddress to a new (fake) address along with mapping the old ipaddress to
new next location router (a tunnel router)
*** scales better and fakes better
magic::=
LISP packets (protocol) ... UDP (tranport layer 4
end point "routers" know how to eat and give LISP sauce
************************************************************************************
The net is VL2 virtualizes away macaddress:ipaddress pair
while LISP virtualizes away the ipaddress:nextrouter pair using a secret passage between two routers
How this is done will be rocket science with changes to layer 2.5/3.5 (somewhere there in the net stacks)
Do I like it? well, ...
************************************************************************************
it was just a fly by "notes" I made
************************************************************************************