3 ms·

Huh? IPv6 does have backwards-compatible-ish notation for writing IPv4 addresses. To take your example: 1.2.3.4 would be ::ffff:1.2.3.4, the 96-bit prefix indic

• mike_d 3y ago
  > they were a deliberate choice so that computers doing string processing could never confuse the two types of addresses. Wait until you try to write an IPv6 address with a port number in standard notation.
  • ale42 3y ago
    Usually IPv6 addresses are enclosed in square brackets when a port number is involved. But it's true that in many configuration files IPv6s are a nightmare to put in, especially because you never remember what syntax you have to use: sometimes you even have to duplicate semicolons (that's what Exim does...). But I think this is rather a convention problem for the config files, rather a problem of IPv6 addresses themselves.
    • tlb 3y ago
      The IPv6 people must have known that : was a common way to separate IPv4 and port numbers. IPv6 was standardized 4 years after the URL format which used a colon to denote a port number.
      • ale42 3y ago
        Makes sense, the choice of the colon is a bit unfortunate.