[157142] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: IPv4 address length technical design

daemon@ATHENA.MIT.EDU (Paul Vinciguerra)
Sun Oct 7 18:21:18 2012

From: Paul Vinciguerra <pvinci@VinciConsulting.com>
To: Steven Noble <snoble@sonn.com>, Barry Shein <bzs@world.std.com>
Date: Sun, 7 Oct 2012 22:20:28 +0000
In-Reply-To: <3B7A62FE-AF9C-49AA-9A49-14508B073315@sonn.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


>=20
> Ok, then let's take a step back, perhaps not permanently, and say DNS=20
> resolution is only really useful for routers with more than just a=20
> single default external route.
>=20
> So DNS could be reduced to an inter-router only protocol, similar to=20
> BGP in some sense.

LISP DDT uses a lookup to determine EID location.

We operate one of the DDT roots, and yes the difference is that LISP uses a=
n on-demand pull mechanism, where the route is looked up and then cached un=
til it ages out from inactivity.  BGP pushes every route to peers and every=
one running BGP pays a hardware tax for carrying each and every route. (See=
 Bill Herrin's work at http://bill.herrin.us/network/bgpcost.html)   DDT pr=
ovides a scalable, distributed database similar to DNS for looking up prefi=
xes in LISP mapping servers.




home help back first fref pref prev next nref lref last post