[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] (Joao Luis Silva Damas)
- Date: Fri, 2 Aug 2002 15:06:09 +0200
- In-reply-to: <[email protected]>
- References: <2B81403386729140A3A899A8B39B046405E235@server2000.arneill-py.sacramento.c <2B81403386729140A3A899A8B39B046405E235@server2000.arneill-py.sacramento.c a.us> <p05111703b96ff38e4a14@[193.0.1.186]> <[email protected]>
At 15:02 +0200 2/8/02, Gert Doering wrote:
>Hi,
>
>On Fri, Aug 02, 2002 at 10:39:40AM +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 :-)
> > 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?
Joao