Re: Fix IPV6 literal notation?

Agreed on all comments.  As you stated anything difficult or not as
pleasing visually gets easier over time and with practice.  When you look
at an IPv6 address you hex and 48 bit ugly mac or maybe even Token Ring RIF
field for source routing packets.

I think the most difficult is the visualization and being used to decimal
and now looking at Hex is a huge change for operations to get their arms
around.

Practice makes Perfect!!

Cheers

Gyan

On Sat, Dec 26, 2020 at 9:28 PM Karl Auer <kauer@biplane.com.au> wrote:

> On Sat, 2020-12-26 at 19:42 -0500, Gyan Mishra wrote:
> > I agree just on difficult to read and hard to parse.
>
> Anything new is hard to start with and becomes easy with practice.
>
> For a way to make it even easier, see RFC1924 (
> ftp://ftp.rfc-editor.org/in-notes/rfc1924.txt)
>
> > The  :: Os compression helps, however does add confusion
>
> I generally make the same recommendations as RFC5952.
>
> The other thing people get hung up on is that the term "leading zeroes"
> does not mean ALL the zeroes. In most classes there is at least one
> person who tries to turn ":3000:" into ":3:" (and in one memorable case
> ":3001:" into ":31:").
>
> > Understanding that when an IPv6 prefix is written that the leading
> > higher order hex 0s are the not displayed within the hex field which
> > leads to confusion.
>
> Can we blame IPv4 octal representation? There are no higher-order
> zeroes shown in IPv4 octets either, and nobody gets confused.
>
> A lot of people treat IP addresses as symbols without understanding
> their underlying meaning. Making the link between the written addresses
> and the underlying bits helps a lot.
>
> 128 bits are just plain harder to get your head around than 32. IPv6
> addresses are not easily parsed by the unaided human; they are too big
> to be encompassed at a glance, regardless of the notation.
>
> Regards, K.
>
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Karl Auer (kauer@biplane.com.au)
> http://www.biplane.com.au/kauer
>
> GPG fingerprint: 2561 E9EC D868 E73C 8AF1 49CF EE50 4B1D CCA1 5170
> Old fingerprint: 8D08 9CAA 649A AFEF E862 062A 2E97 42D4 A2A0 616D
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*M 301 502-134713101 Columbia Pike *Silver Spring, MD