[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[6bone] semi-newbie Q on IPv6 address planning
- Subject: [6bone] semi-newbie Q on IPv6 address planning
- From: [email protected] (Gert Doering)
- Date: Fri, 2 Aug 2002 16:26:36 +0200
- In-reply-to: <p0511170cb97033e55e6d@[193.0.1.186]>; from [email protected] on Fri, Aug 02, 2002 at 03:06:09PM +0200
- References: <2B81403386729140A3A899A8B39B046405E235@server2000.arneill-py.sacramento.c <2B81403386729140A3A899A8B39B046405E235@server2000.arneill-py.sacramento.c <p05111703b96ff38e4a14@[193.0.1.186]> <[email protected]> <p0511170cb97033e55e6d@[193.0.1.186]>
Hi,
On Fri, Aug 02, 2002 at 03:06:09PM +0200, Joao Luis Silva Damas wrote:
> >> I chose a /126 (instead of a /127, even before reading Pekka's draft)
> >> also because that's what a lot of network engineers are used to in
> >> IPv4 (a /31) and it minimises human error (which is far more frequent
> >> than a hardware failure).
> >
> >Ummm. I assume a typo here, but the equivalent of a /31 in IPv4 world
> >is a */127*, not a /126...
> Typo indeed, make it /30 :-)
On the other hand, we *do* use /31s on IPv4 ptp links. It's a recent
change, but works well.
> > > And I wish protocol design wasn't a game of designing nice bit
> >> templates and took operational practice into account as a starting
> >> point.
> >
> >Seconded. EUI-64 sucks big time (using MAC addresses and such is a nice
> >idea, but why on earth can't they map 48 bits to 64 in a somewhat more
> >straightforward way than "distribute them over all the 64bits"?)
>
> And, would you use your router interface's mac address ever to
> configure the interface IP?
Definitely not for the routers, nor for servers. For client-only hosts,
it's a nice idea for smallish networks that don't want to setup DHCP.
Gert Doering
-- NetMaster
--
Total number of prefixes smaller than registry allocations: 46631 (46284)
SpaceNet AG Mail: [email protected]
Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0
80807 Muenchen Fax : +49-89-32356-299