> And, regarding UTF-8 or ACE, the most important thing is the nameprep > and not what encoding the labels uses. I am sorry to say that I am > extremely worried that if we go with an encoding that is implemented > (like UTF-8) people will not do nameprep. Any application which is modern enough to use the new API should also be applying the nameprep rules. If it doesn't, it is broken. Just-use-ACE is actually the most succeptible to this particular problem, since old and new applications pass data into the system through the old APIs equally, without any distinctive markings. Was it nameprepped? nobody knows... At least with the new API approach we know that a particular IDN was most likely nameprepped. -- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/
- Re: [idn] Why follow IDNA with UTF-8? Adam M. Costello
- Re: [idn] Why follow IDNA with UTF-8? Eric A. Hall
- Re: [idn] Why follow IDNA with UTF-8? Adam M. Costello
- Re: [idn] Why follow IDNA with UTF-8? Eric A. Hall
- Re: [idn] Why follow IDNA with UTF-8? Paul Hoffman / IMC
- Re: [idn] Why follow IDNA with UTF-8? Martin Duerst
- Re: [idn] Why follow IDNA with UTF-8? D. J. Bernstein
- Re: [idn] Why follow IDNA with UTF-8? Steve Atkins
- Re: [idn] Why follow IDNA with UTF-8? Patrik F�ltstr�m
- Re: [idn] Why follow IDNA with UTF-8? Patrik F�ltstr�m
- Re: [idn] Why follow IDNA with UTF-8? Eric A. Hall
- Re: [idn] Why follow IDNA with UTF-8? Keith Moore
- Re: [idn] Why follow IDNA with UTF-8? Keith Moore
- Re: [idn] Why follow IDNA with UTF-8? Bright Fulton
- Re: [idn] Why follow IDNA with UTF-8? Adam M. Costello
- Re: [idn] Why follow IDNA with UTF-8? Soobok Lee
