On Aug 23, 2022, at 2:00 PM, Joe Abley <[email protected]> wrote: > > On Aug 23, 2022, at 16:03, Schanzenbach, Martin <[email protected]> > wrote: > >> " >> >> This document uses ".alt" for the pseudo-TLD in the presentation >> format for the DNS, corresponding to a 0x03616c7400 suffix in DNS >> wire format. The presentation and on-the-wire formats for non-DNS >> protocols might be different. >> " >> >> I had to read this 3 times and I am still not sure what is important and >> what not. > > Doesn't this text also imply that the alt label is case-sensitive?
<sigh> Yes. We have at least three options:
1) Pick one capitalization of "alt" and use the binary representation of that;
for example "alt".
2) Pick two capitalizations of "alt" and use the binary representations of
those; for example "alt" and "ALT".
3) Use all nine possible representations ("alt", "Alt", "ALt", ... "ALT")
I picked #1 but the WG might want something else, if we want to say anything
about the wire format at all.
> I may have missed something (I have been trying very hard) but it seems a
> little weird for the wire format for a definitively non-existent domain name
> to be specified at all, to be honest; I'm not sure what imagined audience
> that is intended to help.
This is a very good point, one that I had not considered. Applications that
know about the non-DNS will be getting input both from users or other
applications, and thus get their input case-mixed. The same will be true for
recursive resolvers.
If this thinking is correct, the addition of "corresponding to a 0x03616c7400
suffix in DNS wire format" was wrong. However, I'm not sure what we want to say
instead that will be clear enough for developers to act on.
--Paul Hoffman
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
