[10180] in www-talk@info.cern.ch
Re: URL parsing and IPv6 addresses
daemon@ATHENA.MIT.EDU (Kim)
Tue Aug 6 09:18:34 1996
From: Kim <bookwyrm@agii.solluna.org>
To: dee@cybercash.com (Donald E. Eastlake 3rd)
Date: Tue, 6 Aug 1996 09:12:20 -0400 (EDT)
Cc: www-talk@w3.org
In-Reply-To: <Pine.SUN.3.91.960806084419.10135A-100000@cybercash.com> from "Donald E. Eastlake 3rd" at Aug 6, 96 08:46:16 am
Resent-From: www-talk@w3.org
Earlier, <Donald E. Eastlake 3rd> inscribed:
>
> How about just putting square brakets around the address. I thought IPv4,
> and presumably IPv6, raw addresses were supposed to bge noted that way.
> so you would have, for example, http://[::83F7:6C0E]:8080/ or
> http://[::83F7:6C0E:8080]/
Well, my copy of netscape refuses to parse that notation for IPv4 addresses,
as does Lynx:
http://[131.247.108.14]:80/
If there is a standards document that points to this, I would appreciate the
reference.
I dislike this idea because it adds more special characters, the '[' and ']'
to parse. Also, it would make more sense to put them around the port
specifier - http://131.247.108.14[:80]/ - as that allows them to be omitted
in the default case.
Kim
