- From: Henry S. Thompson <ht@inf.ed.ac.uk>
- Date: Mon, 28 Sep 2009 18:16:29 +0100
- To: Jonathan Rees <jar@creativecommons.org>
- Cc: www-tag@w3.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
To add to your citations from "the canon":
RFC 3986, section 3.2.2. Host
"This specification does not mandate a particular registered name
lookup technology and therefore does not restrict the syntax of
reg-name beyond what is necessary for interoperability. Instead,
it delegates the issue of registered name syntax conformance to the
operating system of each application performing URI resolution, and
that operating system decides what it will allow for the purpose of
host identification. A URI resolution implementation might use
DNS, host tables, yellow pages, NetInfo, WINS, or any other system
for lookup of registered names. However, a globally scoped naming
system, such as DNS fully qualified domain names, is necessary for
URIs intended to have global scope. URI producers should use names
that conform to the DNS syntax, even when use of DNS is not
immediately apparent, and should limit these names to no more than
255 characters in length."
ht
- --
Henry S. Thompson, School of Informatics, University of Edinburgh
Half-time member of W3C Team
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFKwO9tkjnJixAXWBoRAlmOAJ9z2lBVhWxS9Ylji9IDdvyOEl+KLgCeOtby
VODuHBOQmQn4kT5hAZuUE+0=
=60cx
-----END PGP SIGNATURE-----
Received on Monday, 28 September 2009 17:17:22 UTC