Sure, a 128-bit address is going to be unwieldy in any notation. Why is hex better, I am genuinely curious? Does being able to slice at the half-byte boundary allow for some highly advantageous granularity I am failing to appreciate as an IPv6 n00b? -- Sent from mobile device On Oct 21, 2009, at 9:02 AM, Jeff McAdams <jeffm at iglou.com> wrote:
Why don't you take an IPv6 address and convert it to dotted octets, then come back and report on how unweildy that is to deal with.
Yes, hex is indeed more expressive, and once you start using IPv6 addressing some, it becomes very natural to work with.
-- Jeff
-----Original Message----- From: Alex Balashov <abalashov at evaristesys.com> Sent: Wednesday, October 21, 2009 8:27 AM To: David Hiers <hiersd at gmail.com> Cc: VoiceOps <voiceops at voiceops.org> Subject: Re: [VoiceOps] IPV6
David Hiers wrote:
Never looked into it yet. I"m still working on Gerald Ford's Great Metric Conversion :)
Our current business model doesn't contain a lot of drivers that might motivate an investigation.
The day IPv6 is adopted seriously, I am leaving networking/telecom and going to start a bakery. I can barely microwave Lean Cuisine, but perhaps I can secure some assistance from significant other.
There is no way I am going to be managing infrastructure by way of hex nibbles.
Remind me, why is it that nobody thought of using dotted decimal notation for IPv6 addresses, but just adding more octets? Are half-bite nibbles in a base humans aren't normally taught to count in more "expressive" somehow?
-- Alex
-- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops