From:
David Conrad [mailto:david.conrad@icann.org]
Sent: Monday, February 04, 2008
9:30 PM
To: Christian Huitema; blue
Cc: Brian E Carpenter;
v6ops@ops.ietf.org
Subject: Re: [Fwd: Re: About IPv6
private address]
Christian,
Just to be sure I understand, you’re saying Microsoft has introduced
something in Vista that looks a whole lot like a domain name in
VeriSign’s .NET domain namespace but that isn’t really a domain
name to deal with some applications that had trouble dealing with IPv6
literals?
Thanks,
-drc
On 2/4/08 8:49 PM, "Christian Huitema"
<huitema@windows.microsoft.com> wrote:
Firefox
does not do anything there. The name resolution service in Windows Vista
resolves names of the form fe80--213-49ff-fe04-507s8.ipv6-literal.net into the
corresponding IPv6 address, in that example [fe80::213:49ff:fe04:507%8]. For
Firefox, it is just a name lookup.
We put that feature in Vista because some applications had a very hard time
parsing colons and percent signs. It really is a work around…
From:
blue [mailto:susan.lan@zyxel.com.tw]
Sent: Monday, February 04, 2008
7:15 PM
To: Christian Huitema
Cc: Brian E Carpenter;
v6ops@ops.ietf.org
Subject: Re: [Fwd: Re: About IPv6
private address]
Dear Christian:
Do you mean Firefox on Vista will translate the link-local address to the
domain name suffixed "ipv6-literal.net"?
Currently my platform is Microsoft Windows XP instead of Windows Vista.
However, I don't consider this behavior is related to the OS version.
Which version is your Firefox, please?
Thanks.
BR,
Yi-Wen
Christian Huitema wrote:
If you are running Firefox on
Windows Vista, you should be able to try http://fe80--213-49ff-fe04-507s8.ipv6-literal.net/
From:
owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org]
On Behalf Of blue
Sent: Monday, February 04, 2008
5:34 PM
To: Brian E Carpenter
Cc: v6ops@ops.ietf.org
Subject: Re: [Fwd: Re: About IPv6
private address]
Please forgive my dumbness but my Firefox version is 2.0.0.9
My IE could not connect to IPv6 URL either! (IE version 6.0)
Thanks.
BR,
Yi-Wen
Brian E Carpenter wrote:
That
is a Firefox configuration issue, I think. I don't see that
problem (with Firefix 2.0.0.7, or with IE).
Is it possible that your browser is going to a proxy?
Brian
On 2008-02-05 13:24, blue wrote:
Hi,
But after typing a link-local address, Firefox' message shows:
Unable to find "www.fe80::213:49ff:fe04:507%8.com <http://www.fe80::213:49ff:fe04:507%258.com>
"
It translated typed "http://[fe80::213:49ff:fe04:507%8]"
<http://%5Bfe80::213:49ff:fe04:507%258%5D>
to
"http://[www.fe80::213:49ff:fe04:507%8.com]/"
<http://%5Bwww.fe80::213:49ff:fe04:507%258.com%5D/>
.
However, a global unique IPv6 address worked!
I thought it proved that Firefox does not support link-local address.
Thanks.
BR,
Yi-Wen
Brian E Carpenter wrote:
Yes, users need to configure our device via http,
and if there's no
well-known IPv6 address, how do users know which address to connect to?
I have thought about a pre-configured link-local address; however,
browsers such as Firefox does not support link-local address. Any
suggestions?
How come Firefox (or any other browser) knows how to
*not* support
link-local addresses? As far as I can tell, it does support them.
Just don't forget the [ ] brackets.
When I tell Firefox to connect to http://[fe80::1
<http://%5Bfe80::1> ]/ it gives me
an "unable to connect" message, but that's exactly what I'd expect.
When I tell Firefox to connect to http://[fe80::21a:a0ff:fe4a:d680%5
<http://%5Bfe80::21a:a0ff:fe4a:d680%255>
]/
(my own link-local address) it gives me a "server not found" message,
which is also exactly what I'd expect, since I'm not listening on
port 80.
Brian