https://bugzilla.wikimedia.org/show_bug.cgi?id=14977

--- Comment #39 from Philippe Verdy <[email protected]> 2011-11-24 05:30:57 
UTC ---
Domain names are free if you want to try from your home, dyndns.org can provide
you a domain name for such tries if you want to see how your website behaves
from the Internet.

But for most tests, you just need to use a local hostname. Or you can
experiment it from the same host as the webserver used for development and then
you can reference it as 127.0.0.1 (yes only IPv4), or by defining a hostname
entry in your local /etc/hosts to configure a name associated with an IPv6
address (this workds also on Windows).

Really, I hope I will never see any site using URLs containing a
[bracketed:IP:v6::address] for its hostname. If such URLs exist, this is only
for the configuration pages to setup devices on the local network only, before
the device itself gets assigned a hostname. But everything connected on the
Internet should have a hostname (including mobile devices: it's up to the ISP
to designate a usable domain name in its reverse IP DNS database).

And even if there's still no hostname assigned or it would be best to still use
the hostname from the special .arpa TLD, even if it creates names that are
longer (64 characters + the special subdomain in .arpa for IPv6 registrations,
although I think that the .arpa registrations will never go above the first 64
bits of the IPv6 address, the rest being private, so that only 32 characters
would be needed for the registered IPv6 address block, plus the lenght of the
.arpa subdomain for IPv6, and in prefix we can simply use the compact hex
representation of the remaining 64-bits, creating a 8-hex digit label). If you
have a local DNS server, it will remap this 8-hex digit label into subnetwork
labels if needed, or it will assign the true domain name you want for your
website.

In other words: we really don't need to support IPv6 hostnames for the local
server, but we need it only in the parser for
- external servers (which are not necessarily webservers running MediaWiki, but
may be some hardware devices, including those found by default host discrovery
mechanisms, such as configurable routers, or unconfigured network printers or
TV/media decoder sets...),
- or much more commonly for the identification of remote clients (in the server
logs for example, or in the early stages of setting up a secured channel when
one client wants to hide his public identity, for privacy reasons, or for
strict confidentiality reasons, but only wants to reveal it to the server on
the secure channel after it has been established on an incoming IPv6 request).

-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.

_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to