[121747] in North American Network Operators' Group
Re: Using /126 for IPv6 router links
daemon@ATHENA.MIT.EDU (David Barak)
Tue Jan 26 09:40:35 2010
Date: Tue, 26 Jan 2010 06:38:43 -0800 (PST)
From: David Barak <thegameiam@yahoo.com>
To: Mark Smith <nanog@85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org>,
Christopher Morrow <morrowc.lists@gmail.com>
In-Reply-To: <20100126191434.79cd11e1@opy.nosense.org>
Cc: nanog@nanog.org, Mathias Seiler <mathias.seiler@mironet.ch>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
From: Mark Smith nanog@85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org=
=0A=0A>Why can't IPv6 node addressing be as easy to understand and work wit=
h=0A>as Ethernet addresses? They were designed in the early 1980s*. 28 year=
s=0A>or so years later, it's time for layer 3 addressing to catch up.=0A=0A=
Becase Ethernet addresses are only locally significant, are not manually as=
signed in the vast majority of cases, and changing a MAC by replacing a NIC=
has no bearing on the configuration of a { server | router ACL | etc }.=0A=
=0ALayer 3 addressing is globally significant, and the case we're discussin=
g is addresses which are human-assigned rather than automatically configure=
d.=A0 Link-local autoconfiguration in IPv6 works like a champ, and behaves =
pretty much the way I would want it to.=A0=A0Global addressing approaches, =
on the other hand, are highly optimized in directions which make them less =
flexible or have surprising consequences (hence this thread).=0ADavid Barak=
=0ANeed Geek Rock? Try The Franchise: =0Ahttp://www.listentothefranchise.co=
m =0A=0A=0A=0A
