Re: [dane] [apps-discuss] AppsDir review of draft-ietf-dane-protocol-19

[Paul Hoffman <[e-mail]>]

On May 3, 2012, at 2:41 PM, Peter Saint-Andre wrote:

> On 5/3/12 2:34 PM, Paul Hoffman wrote:
>> On May 3, 2012, at 12:52 PM, Peter Saint-Andre wrote:
>> 
>>> Perhaps this is simply a difference between folks who look at
>>> things from the DNS perspective and folks who look at things from
>>> the apps perspective (as users of DNS). All sorts of application
>>> protocols are being updated to support IDNs. Those applications
>>> will need to know how to translate their IDNs (which might consist
>>> of U-labels) into a form that can be placed into the DNS. To make
>>> things perfectly clear, I'm just suggesting that we add a sentence
>>> or two warning those who write code for application protocols using
>>> DANE that they might need to convert U-labels into A-labels. I'll
>>> work to propose specific text today or tomorrow.
>> 
>> 
>> I'll be interested to see that. I cannot see how anyone reading
>> Section 3 of RFC 5891 could think that they would *not* need to
>> convert to A-labels before looking up something in the DNS. If you
>> are saying that every post-5891 protocol that defines a new RRtype
>> must say "and if you are going to look up the domain name in the DNS,
>> convert to A-labels first", that's fine, but it seems kinda late to
>> start saying that.
> 
> Not everyone is as smart as you are.

If you believe that developers who are using IDNs are not following the easiest-to-read section of RFC 5891, the issue is much larger than just DANE. I propose that is not a DANE issue at all.

--Paul Hoffman