[rrg] [lisp] Economic issues of long-path / stretched routing
Noel Chiappa
jnc at mercury.lcs.mit.edu
Mon Jan 26 11:03:07 PST 2009
> From: HeinerHummel at aol.com
> Why LISP 1.5=20? Why not LISP 2 ? or directly:
> Why doesn't the ITR intercept and enhance the DNS lookup as to also request
> the eRLOC address in addition to the dest IP address? It can also
> intercept the respective response and store (EID, eRLOC).
I don't know what the thinking of other people working on LISP is, but I can
give you my thoughts on this point.
Simply put, I don't like designs which _invisibly, outside the host_ tie into
the DNS because it takes two separate subsystems (DNS resolution, and basic
packet forwarding), and tangles them together, which is bad engineering for a
number of reasons (makes it harder to make further changes, creates more
mutual dependencies, increases overall fragility/brittleness, etc).
Some NAT variants do this too, and I especially didn't like them either! :-)
Noel
More information about the rrg
mailing list