Re: [DNSOP] DNSOP Digest, Vol 125, Issue 31

2017-04-13 Thread Paul Vixie
i think we can't use something in a standard that doesn't have a canonical format. if there is a F(name) that produces a minimal I18N result which is the same as any other F(name) that would look the same or mean the same if written, then we should outlaw on-the-wire strings that are not in that

Re: [DNSOP] DNSOP Digest, Vol 125, Issue 31

2017-04-13 Thread Andrew Sullivan
On Thu, Apr 13, 2017 at 02:41:20PM -0400, Viktor Dukhovni wrote: > What I should have said is that the variant with the upper case > first letter is invalid (as opposed to being "different") in > IDNA2008. This is IMHO a poor user interface, so running code > will generally go with UTS#46

Re: [DNSOP] DNSOP Digest, Vol 125, Issue 31

2017-04-13 Thread Viktor Dukhovni
> On Apr 13, 2017, at 7:30 AM, dnsop-requ...@ietf.org wrote: > > Well, IIRC they sensibly converged on a case-folded normal form > that ensures that https://Духовный.org maps to the same underlying > wire-form domain as https://духовный.org, i.e. both result in > queries for