[136944] in North American Network Operators' Group
Re: quietly....
daemon@ATHENA.MIT.EDU (Joe Abley)
Sun Feb 6 19:17:43 2011
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <4D4B3C53.5080507@paulgraydon.co.uk>
Date: Sun, 6 Feb 2011 19:13:35 -0500
To: Paul Graydon <paul@paulgraydon.co.uk>
X-SA-Exim-Mail-From: jabley@hopcount.ca
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 2011-02-03, at 18:37, Paul Graydon wrote:
> On 02/02/2011 06:31 PM, Jay Ashworth wrote:
>>=20
>=20
>> I, personally, have been waiting to hear what happens when network =
techs
>> discover that they can't carry IP addresses around in their heads =
anymore.
>>=20
>> That sounds trivial, perhaps, but I don't think it will be.
>>=20
>=20
> Absolutely, it's certainly one thing I'm dreading.
I'm not sure this is the nightmare people think it will be.
In my (admittedly fairly small-scale) experience with operating v6 on =
real networks, being able to figure out a prefix from a schema such as
ARIN:ARIN:SITE:VLAN::/64
makes things a lot easier. Having to remember ...::1, or ...::2, or =
...:3 for the statically-numbered routers on the VLAN doesn't exactly =
make things much harder. Mix in some special cases (e.g. VLAN=3D0 for =
loopbacks) and you have a recipe that's pretty trivial to remember.
[This is how Stephen Stuart and Paul Vixie set things up within =
2001:4f8::/32 back when I was chasing packets at ISC, and I've followed =
the model ever since.]
It's easier to figure out 2607:f2c0:1::1 in these terms than it is to =
remember 206.248.155.244. For me, at least :-)
I appreciate the full mess of EUI-64 for devices using autoconf requires =
cut and paste, but that's why you hard-wire the host bits for things you =
refer to frequently.
Joe=
