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

Re: [idn] Which names are valid?



-----BEGIN PGP SIGNED MESSAGE-----

Harald Tveit Alvestrand wrote:
> --On 1. august 2001 14:03 +0100 David Hopwood <david.hopwood@zetnet.co.uk>
> wrote:
>
> > What do you propose to call the query string used for a SRV lookup
> > (e.g. "_ldap._tcp.example.com"), if not a domain name? It is certainly
> > a domain name as defined and used in RFCs 1034, 1035 and 2181 (although
> > not a host name).
>
> with respect:
> draft-ietf-idn-requirements-08.txt has been in the group for a LONG time.

The definitions in that draft are not entirely satisfactory. For example,
consider "_ldap._tcp.π.com". This is clearly a domain name, and it is
clearly internationalized, so the most sensible thing to call it would be
an internationalized domain name. However, it is not a hostname (although
"π.com" is). It makes no sense to lose the useful distinction between
hostnames and domain names just because they are internationalized.

Note that the remit of this WG is to develop standards for internationalized
domain names, not just internationalized hostnames. Users will not be very
happy if lookups for SRV records below a non-ASCII domain don't work.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5 0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO3QKxzkCAxeYt5gVAQFP9wf/Qk5LwyDNWYWDz/2uYeRscIAHQhftBii6
o48A9wPIerUyDzOajiCxepEsX4oso3Hy7htj8k4QFNrQyga0BF4J/xGyRKqo4lwt
qOizKvDaCKjBUDvcsY6ThVTwqN75jNFyJvSSCFGmbDSWB6N4u0yqFL/4uKN6O8rZ
y+DqNn1rohtlchoXPGhcAKTucrp15xDbB9e8lBBAmHx6/J/Y7s6H+Ewx/fUyNy7L
fT7VF6g0XjWH6w0jdp7vIX/gtHzyjT5w9pUWp5cLWexqnmT4MsICXbhn5OSaEHm+
54sLzjpucfP8YGRa5XF0fm9agPXSsWk5n8B+15hAHo6FgKNl1rtk8w==
=ARLN
-----END PGP SIGNATURE-----