[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I-D ACTION:draft-fenner-literal-zone-00.txt

I tried all the addresses Juergen gave and they all worked for me with
Explorer (6.0) - perhaps the world's commonest browser but perhaps not
so common for those on the ipv6 list;-)

Tom Petch

----- Original Message -----
From: "Juergen Schoenwaelder" <j.schoenwaelder@xxxxxxxxxxxx>
To: "Bill Fenner" <fenner@xxxxxxxxxxxxxxxx>
Cc: <ipv6@xxxxxxxx>
Sent: Monday, December 06, 2004 9:16 PM
Subject: Re: I-D ACTION:draft-fenner-literal-zone-00.txt
> I think it is useful to explore how generic these real-world URI
> parsers really are. I just tried to use
> http://%3134.169.34.18/ and  http://134.169.34.%31%38/
both worked fine

> to access a web page, expecting that parsers would turn that into
worked fine
> but I got lots of "host not found" messages. So it indeed looks like
> the real-world parsers I have access to pass hostnames/IP addresses
> to name lookup functions without preparsing them. I also tried things
> such as <http://%77%77%77.ietf.org/> without much luck. Please make
worked fine
> your own tests.
all works fine
> The conclusion from my little series of tests is clear. The
> implementations I have tried do not interpret % escape sequences
> in the host portion of URIs and so the direction should be to
> simply allow % for IPv6 addresses with a zone identifier and to
> tell URI folks that they better do not mandate that % escape
> encoding is applied to the host portion of URIs since this is
> a) not really useful and b) not widely implemented. Of course,
> if you find implementations that do interpret % escape sequences
> in the host portion of URIs, your conclusions might be different.
> Juergen Schoenwaelder     International University Bremen
> <http://www.eecs.iu-bremen.de/>     P.O. Box 750 561, 28725 Bremen,

IETF IPv6 working group mailing list
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6