In message <CAPkb-7AMjiVPqTSmTvk7Wa0NW3WysOPhxPyEGhTJ+8O54=UEzw@mail.gmail.com>, Baldur Norddahl writes:
On 13 June 2016 at 02:05, Owen DeLong <owen@delong.com> wrote:
2. Consistent and easier comparisons for equality or ranges In iPv4, this was useful. In IPv6, it=E2=80=99s essential= .
You could also normalize your IPv6 text representation. There is even RFC 5952 for that. Abbreviated the rule is:
1) lower case 2) as short as possible, except do not shorten just one :0: into ::. 3) if there is more than one possible :: block that results in the same shortest length, choose the first block as ::.
I am not quite sure why they put in the exception not to shorten one zero, but otherwise this is what most people would naturally come up with.
Those rules are good for equality but not much more.
Also, technically there is more than one IPv4 representation too. I have in the past poked security holes through this as most people forget (or don't know):
As Owen mentioned.
Baldurs-MacBook-Pro-2:~ baldur$ ping -c1 100000000 PING 100000000 (5.245.225.0): 56 data bytes
Regards,
Baldur -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org