[151848] in North American Network Operators' Group
Re: ipv6 classful addressing with mesh?
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Sat Mar 31 21:48:42 2012
To: Charles N Wyble <charles-lists@knownelement.com>
In-Reply-To: Your message of "Sat, 31 Mar 2012 19:35:05 -0500."
<4F77A2B9.2000801@knownelement.com>
From: Valdis.Kletnieks@vt.edu
Date: Sat, 31 Mar 2012 21:47:35 -0400
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--==_Exmh_1333244855_1901P
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
On Sat, 31 Mar 2012 19:35:05 -0500, Charles N Wyble said:
> How much geographical accuracy does this imply? Just enough to indicate=
> where the =22heart=22 of a network is, or was traditionally. A chunk ca=
n
> represent any number from 0-65534, because it can represent up to 65535=
> unique numbers and we start at 0. So, longitude can be expressed as a
> number of degrees =22moved east=22 of the prime meridian from 0-360. Th=
is
> means the difference between each integer in a longitude chunk is
> 360=B0/65535, or .005493=B0. At the equator, where a degree represents =
the
> longest distance, that works out to about .4 miles =5B1=5D. For any oth=
er
> latitude, however, precision is better than that. Latitude, which goes
> from -90 to +90, can be represented as a 0-180 number where the equator=
> is at 90, which works out to .002747=B0 precision.
I'll bite. Is 60 Hudson 0.4 miles wide?
> I'm not sure what to make of it. Seems like someone trying to re
> establish classful addressing and not understanding routing, subnets,
> managed networks etc.
No, it's somebody trying to re-invent geographical routing and not unders=
tanding yadda
yadda yadda.
The traceroute from my apartment to my office, a 20 minute bike ride iin =
the real world:
traceroute -A 192.70.187.198
traceroute to 192.70.187.198 (192.70.187.198), 30 hops max, 60 byte packe=
ts
1 192.168.2.1 (192.168.2.1) =5BAS8151/AS28513=5D 1.491 ms 1.452 ms 3=
.909 ms
2 71.62.120.1 (71.62.120.1) =5BAS21508=5D 18.133 ms 18.203 ms 37.221=
ms
3 te-8-2-ur01.blacksburg.va.richmond.comcast.net (68.85.71.97) =5BAS202=
14=5D 18.002 ms 17.986 ms 17.959 ms
4 te-8-3-ar01.staunton.va.richmond.comcast.net (69.139.165.161) =5BAS33=
287=5D 21.101 ms 21.075 ms 21.047 ms
5 te-8-1-ar01.chesterfield.va.richmond.comcast.net (68.86.173.165) =5BA=
S21508=5D 29.087 ms 29.089 ms 29.029 ms
6 te-0-1-0-0-cr01.charlotte.nc.ibone.comcast.net (68.86.91.113) =5BAS79=
22=5D 38.882 ms 46.911 ms 46.916 ms
7 pos-3-14-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.213) =5BAS79=
22=5D 43.328 ms 45.617 ms 45.602 ms
8 nyc-e5.nyc.us.net.dtag.de (68.86.88.186) =5BAS7922=5D 45.585 ms 45.=
563 ms 45.540 ms
9 te4-2.ccr01.atl02.atlas.cogentco.com (154.54.10.233) =5BAS174=5D 42.=
049 ms 42.978 ms 42.959 ms
10 te0-0-0-1.ccr21.atl01.atlas.cogentco.com (154.54.0.165) =5BAS174=5D =
41.061 ms 41.088 ms 41.097 ms
11 te0-5-0-7.ccr21.dca01.atlas.cogentco.com (154.54.42.193) =5BAS174=5D =
40.750 ms te0-0-0-7.ccr21.dca01.atlas.cogentco.com (154.54.28.213) =5BAS=
174=5D 40.914 ms te0-0-0-3.ccr21.dca01.atlas.cogentco.com (154.54.28.201=
) =5BAS174=5D 40.878 ms
12 te0-1-0-5.ccr21.iad02.atlas.cogentco.com (154.54.2.50) =5BAS174=5D 4=
0.638 ms te0-1-0-1.ccr21.iad02.atlas.cogentco.com (154.54.26.130) =5BAS17=
4=5D 40.195 ms te0-3-0-5.ccr21.iad02.atlas.cogentco.com (154.54.41.230) =
=5BAS174=5D 43.299 ms
13 38.127.193.146 (38.127.193.146) =5BAS174=5D 43.281 ms 43.171 ms 43=
.208 ms
14 isb-7606-1.vl155.cns.vt.edu (192.70.187.148) =5BAS1312=5D 48.902 ms =
* *
Quite the little trip - north to Staunton, south to Atlanta, north to DC,=
south to B'burg again, and I dunno WHAT happened at hop 8. :)
Every single person who suggests geographically-based routing or addressi=
ng
fails to understand that there's no cable connecting AS21508 to AS1312. A=
nd
there's likely to never be one (we invited all the local providers to pee=
r,
several did accept because it lowered their upstream transit costs, Comca=
st
apparently didn't see the added complexity as being worth the infinitesma=
l
savings it would get them at their Cogent interconnect). So sending packe=
ts to
21508 because it's geographically =22close=22 and hoping it will get to 1=
312 (or
vice versa) is a fool's errand. And if you're not basing routing decisio=
ns based
on the geographic address, who *cares* if the address reflects location? =
At
that point, you're much better off basing my IP address off the fact that=
I'm
a Comcast customer and Comcast probably knows how to get packets to
me.
I'll overlook the little detail that trying to use latitude and longitude=
as the
basis for IPv6 addresses ends up wasting literally an entire Pacific's wo=
rth
of address space. ;)
--==_Exmh_1333244855_1901P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001
iQIVAwUBT3eztwdmEQWDXROgAQJbPA//STQqpkJLlYM6CdV7zv/eF9kBz309HkXi
K9+p9LR/JC7/sdvCWRZEg/XkCndZYedZhZ3JYx97Oa5sCNokkLYQ5M9YyJ6sbdP1
BdoVOIgzsd0UgXoDU3ZWFE2O3gsV0wMakGKswmbnyBLqz3Y1d9FLifVBBzyEODmU
xZq8f1ziFVWfqRg/aUyCo5l5rChGUBv4QmtBWmgmIGDb4PwDvsoXdZseZkn8HsuV
/gMHK0hK6b8RXRUQElcxOf1tpvzqYb6TAN4M30b230w1XVoqzWTmIaJYsxXKyIWJ
ZaFolflUznS36fsEKEnSBME/56wBrdqrIyyU9njP/ftWR3IRkGbC0xGRf2kJlEIf
QbZzNGZRj916Lr/Hm1J4Fwi1jUrOPQZB/QZgUUoEqyJPHnrWGZcckx/6m/ocaLRa
LhbnKTMnE+7l+eRPtDusrPpY0xfuG835mgpKdaxK4gGOOkBMxXx6hA6j2+btuWXC
Bzw6VPwNFM3AEplPLkq1kHxwfHM03eSBR+10smif1yuw+7NBruR9sHqFCHFt9wvO
YAVpA1EyBfKF7p4A6Lhlnup2IQkA5RUXXF+y5Bu2SWlJL3ZaF8qSgBOtuZlqA20N
wb3EqCAYQla0nTh+W4Yi7hgUnmQ+Z1HZGPGXpMH/SwwBoe0qJTEzyEYjnOujj4TG
NQKN3fjJKqc=
=E2I9
-----END PGP SIGNATURE-----
--==_Exmh_1333244855_1901P--
