On 02:49 09/09/02, Adam M. Costello said:
This is a decision of this WG for the reason you quote. The reason why a Registry would want to prohibit more characters ou string sequences would include (among others) the very same reason, in their own opinion.The primary purpose of Nameprep is to allow names to be compared and reproduced in a sane manner. Nameprep prohibits a few characters, not for policy reasons, but merely because they would make names very hard to compare and reproduce.
True. An this is why nameprep should technically support policy decisions under the form of parameters. When I say that ftp1.jefsey.com is a CNAME it is policy decision. To read and support CNAME is a technical feature documented by the DNS RFCs.Nameprep is technical, not policy.
Absolutely. And only an IDNA-conformant parameter description (or command language?) can provide a consistent support in the way to impose those policies. You do not add a something to the DNS to support "ALIAS", "MIRROR" etc.. you use the DNS CNAME feature.If registries want to impose policies about which names they will and will not register, that's fine, but please don't call it name preparation. Nameprep is something that every IDNA-conformant application must be able to do.