Upload
dae-young-kim
View
29
Download
1
Embed Size (px)
Citation preview
IAB Routing & Addressing Workshop 2006
• Explosion of DFZ routing table
• << Incompetence of multi-homing
• << Semantic overloading of IP address
• >> Separation of Loc and ID
Migration
*losing all sever connections at transition
renumbering*
ISP2
nw prefix subnet host i/faddr
Loc doesn't help• Same fate as IP address
• Renumbering at migration
• Tend to be injected into DFZ
• Doesn't help mitigate table explosion
• LIS, not a solution to the problem
Norms…?
• Shach[’78]
• name(what), address(where), route(how)
• Saltzer[’78 & rfc1498]
• service, node, PoA, route
LISP EID• IP address? ... !
• Flat? ... !
• Static? ... !
• Globally unique? ... !
• no changes in host behaviour? ... !
if EID = IP address• Not flat
• hierarchically assigned PoA address
• changes as PoA changes
• Not globally unique
• need a new EID at migration to a new LISP site
• Semantically overloaded
Let EID == node ID• Pointing to the node(host, router; system)
• not to the interface
• Use ISIS for IGP, and
• In-site host/subnet mobility, a default
• no need for Mobile IP
EID global? Why not local?
• Name already global
• Server identified by a name
• name <-> [RLOC + (local) EID]
• Client given a temporary id anyway; DHCP