[idn] Re: Just send UTF-8 with nameprep

[David Hopwood <david.hopwood@zetnet.co.uk>]

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

John C Klensin wrote:
> Dan Oscarsson <Dan.Oscarsson@trab.se> wrote:
> >> Patrik Fältström wrote:
> >>> The day an online stock trader doesn't get his bid in to the
> >>> broker because he typed the wrong version of what according
> >>> to nameprep is the wrong character, you loose.
> >>
> >> This is just spreading FUD. No halfway serious online trader
> >> types in the broker address every time he trades. For that,
> >> there are things such as bookmarks and autocompletion.
> >
> > Also it does not matter if nameprep is not applied at the
> > client end, the DNS server will do nameprep before comparing
> > names - so it will work anyway.
> 
> Dan,
> 
> The above sounds to me as if we are back to requiring that all
> servers need to be upgraded in order to have things work
> properly.

No: only authoritative servers for zones that include IDNs (for proposals
where these servers do nameprep). It doesn't matter that intermediate
servers and proxies don't do nameprep, as long as they are 8-bit clean [*],
which they should be already according to RFC 1034 ("we may someday need
to add full binary domain names for new services"), and RFC 2181 ("any
binary string whatever can be used as the label of any resource record").


[*] "8-bit clean" here means able to handle LDH bytes and bytes >= 0x80.
    For example, if a server cannot handle zero bytes, even though that
    is not compliant with RFC 2181, it would not prevent the server from
    being 8-bit clean in this sense.

- -- 
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

iQEVAwUBO1ybUjkCAxeYt5gVAQG0Sgf9FbaaDY7WeNJq+jc9QjvXBeo07cf84Y7b
bNp69SXMk8FaoTMOdxfGX6oAME3ipQsA0EmqMoOTl7djrZqAZ/QDbflPQVSe1idX
+RGE8wZVI5hRGFIYhnPHm75/m0iZGEj23BDsXBWRmChmK4GzGD/4VxY8q24B0zek
VxCjvcwSyCbxp3e61f6o21jdT8t81Xqb4MLsBUB18Q2mnXOyyT2ONzv067R1ECJl
jayiWOjPmULWK6dabCMzlHwpEsTug2G9siCDVEPnFG+fbjk+wPrugDLtDrCRJ4cQ
lETdvo9bFiVxplK99RRej8BivCp1Z0VO8YXgbP1nY9yoHifB7IUSzg==
=c2MH
-----END PGP SIGNATURE-----