Re: [Editorial Errata Reported] RFC4343 (5112)
"Peter van Dijk" <[email protected]> Tue, 26 Sep 2017 22:20:14 +0200
| Newsgroups | gmane.ietf.dnsext |
|---|---|
| Message-ID | <[email protected]> |
--===============0021773350052059465== Content-Type: multipart/alternative; boundary="=_MailMate_EE042EF7-4F2F-40D1-8F85-71F290435231_=" Content-Transfer-Encoding: 7bit --=_MailMate_EE042EF7-4F2F-40D1-8F85-71F290435231_= Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hello Jay, neither the original text or the erratum suggest dropping queries with=20 capital letters. The original text already says that queries MUST (2119=20 capital) match uppercase letters to lowercase letters. The suggested=20 erratum (in my eyes unnecessarily) suggests uppercasing a lowercase=20 should to make this even more explicit. As for devices dropping this, I don=E2=80=99t have any documentation hand= y but=20 mixed case is certainly known to trigger bugs in various pieces of=20 software now and then. Kind regards, --=20 Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/ On 13 Sep 2017, at 4:38, Jay Ashworth wrote: > Long time listener, first-time caller, but the problem I have with=20 > this is that it suggests that queries containing capital letters are=20 > dropped. > > I recommend to people with overly complicated and long domain names=20 > that, as best practice, they spell them in camel case in advertising. > > www.MyBadDomain.com > > Partially, of course, this is to attempt to avoid the Pen Island/Who=20 > Represents problem. But I do it knowing that the DNS system will case=20 > fold those queries and they will thus work properly. > > If there are devices dropping those... I gotta say I'm a little=20 > unhappy. Is there documentation of that? > > Cheers, > -- jra > > On September 12, 2017 6:15:00 PM EDT, John Levine <[email protected]>=20 > wrote: >> I would reject this or at most mark it as hold for update. The word >> "should" in lower case appears in two other places where it's not=20 >> used >> in the 2119 sense, and I think this one is not intended to be the=20 >> 2119 >> sense either. The sentence in question is describing the historical >> situation, and the following capital MUSTs tell you what to do. >> >> Having said that, if we ever revisit this document, it would benefit >> from rewording to make it clearer when it is telling you what to do >> and when it's just giving background. >> >> R's, >> John >> >> >> >> In article <[email protected]> you write: >>> The following errata report has been submitted for RFC4343, >>> "Domain Name System (DNS) Case Insensitivity Clarification". >>> >>> -------------------------------------- >>> You may review the report below and at: >>> http://www.rfc-editor.org/errata/eid5112 >>> >>> -------------------------------------- >>> Type: Editorial >>> Reported by: Change "should" to must in section 3.(no subsection) >> <[email protected]> >>> >>> Section: 3 >>> >>> Original Text >>> ------------- >>> comparisons on name lookup for DNS queries should be case=20 >>> insensitive >>> >>> Corrected Text >>> -------------- >>> comparisons on name lookup for DNS queries must be case insensitive >>> >>> Notes >>> ----- >>> Some authoritative DNS servers and/or mitigation devices/software >> silently drop queries that have >>> uppercase letters in them. Furthermore, the clarification of the=20 >>> case >> insensitive comparison in the >>> following two sentences after that particular sentence use the term >> MUST. I suspect some readers of the >>> RFC are reading the word "should" and aren't reading the rest of the >> paragraph. >>> >>> Instructions: >>> ------------- >>> This erratum is currently posted as "Reported". If necessary, please >>> use "Reply All" to discuss whether it should be verified or >>> rejected. When a decision is reached, the verifying party >>> can log in to change the status and edit the report, if necessary. >>> >>> -------------------------------------- >>> RFC4343 (draft-ietf-dnsext-insensitive-06) >>> -------------------------------------- >>> Title : Domain Name System (DNS) Case Insensitivity >> Clarification >>> Publication Date : January 2006 >>> Author(s) : D. Eastlake 3rd >>> Category : PROPOSED STANDARD >>> Source : DNS Extensions >>> Area : Internet >>> Stream : IETF >>> Verifying Party : IESG >>> >>> _______________________________________________ >>> dnsext mailing list >>> [email protected] >>> https://www.ietf.org/mailman/listinfo/dnsext >>> >> >> >> _______________________________________________ >> dnsext mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/dnsext > > --=20 > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > dnsext mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsext --=_MailMate_EE042EF7-4F2F-40D1-8F85-71F290435231_= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"= > </head> <body> <div style=3D"font-family:sans-serif"><div style=3D"white-space:normal"><= p dir=3D"auto">Hello Jay,</p> <p dir=3D"auto">neither the original text or the erratum suggest dropping= queries with capital letters. The original text already says that querie= s MUST (2119 capital) match uppercase letters to lowercase letters. The s= uggested erratum (in my eyes unnecessarily) suggests uppercasing a lowerc= ase should to make this even more explicit.</p> <p dir=3D"auto">As for devices dropping this, I don=E2=80=99t have any do= cumentation handy but mixed case is certainly known to trigger bugs in va= rious pieces of software now and then.</p> <p dir=3D"auto">Kind regards,<br> -- <br> Peter van Dijk<br> PowerDNS.COM BV - <a href=3D"https://www.powerdns.com/" style=3D"color:#3= 983C4">https://www.powerdns.com/</a></p> <p dir=3D"auto">On 13 Sep 2017, at 4:38, Jay Ashworth wrote:</p> </div> <blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5= px; padding-left:5px"><div id=3D"EB42E533-53D4-4CC3-BEC5-495FC84688F8">Lo= ng time listener, first-time caller, but the problem I have with this is = that it suggests that queries containing capital letters are dropped. <br= > <br> I recommend to people with overly complicated and long domain names that,= as best practice, they spell them in camel case in advertising. <br> <br> <a href=3D"http://www.MyBadDomain.com">www.MyBadDomain.com</a><br> <br> Partially, of course, this is to attempt to avoid the Pen Island/Who Repr= esents problem. But I do it knowing that the DNS system will case fold t= hose queries and they will thus work properly.<br> <br> If there are devices dropping those... I gotta say I'm a little unha= ppy. Is there documentation of that?<br> <br> Cheers,<br> -- jra<br><br><div class=3D"gmail_quote">On September 12, 2017 6:15:00 PM= EDT, John Levine <[email protected]> wrote:<blockquote class=3D"gmai= l_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(2= 04, 204, 204); padding-left: 1ex;"> <pre class=3D"k9mail">I would reject this or at most mark it as hold for = update. The word<br />"should" in lower case appears in two ot= her places where it's not used<br />in the 2119 sense, and I think this o= ne is not intended to be the 2119<br />sense either. The sentence in que= stion is describing the historical<br />situation, and the following capi= tal MUSTs tell you what to do. <br /><br />Having said that, if we ever = revisit this document, it would benefit<br />from rewording to make it cl= earer when it is telling you what to do<br />and when it's just giving ba= ckground.<br /><br />R's,<br />John<br /><br /><br /><br />In article <= ;[email protected]> you write:<br /><blockquot= e class=3D"gmail_quote" style=3D"margin: 0pt 0pt 1ex 0.8ex; border-left: = 1px solid #729fcf; padding-left: 1ex;">The following errata report has be= en submitted for RFC4343,<br />"Domain Name System (DNS) Case Insens= itivity Clarification".<br /><br /><hr /><br />You may review the re= port below and at:<br /><a href=3D"http://www.rfc-editor.org/errata/eid51= 12">http://www.rfc-editor.org/errata/eid5112</a><br /><br /><hr /><br />T= ype: Editorial<br />Reported by: Change "should" to must in sec= tion 3.(no subsection) <[email protected]><br /><br />Section:= 3<br /><br />Original Text<br />-------------<br />comparisons on name l= ookup for DNS queries should be case insensitive<br /><br />Corrected Tex= t<br />--------------<br />comparisons on name lookup for DNS queries mus= t be case insensitive<br /><br />Notes<br />-----<br />Some authoritative= DNS servers and/or mitigation devices/software silently drop queries tha= t have<br />uppercase letters in them. Furthermore, the clarification of= the case insensitive comparison in the<br />following two sentences afte= r that particular sentence use the term MUST. I suspect some readers of = the<br />RFC are reading the word "should" and aren't reading t= he rest of the paragraph.<br /><br />Instructions:<br />-------------<br = />This erratum is currently posted as "Reported". If necessary,= please<br />use "Reply All" to discuss whether it should be ve= rified or<br />rejected. When a decision is reached, the verifying party = <br />can log in to change the status and edit the report, if necessary.= <br /><br /><hr /><br />RFC4343 (draft-ietf-dnsext-insensitive-06)<br />= <hr /><br />Title : Domain Name System (DNS) Case Insensiti= vity Clarification<br />Publication Date : January 2006<br />Author(s)= : D. Eastlake 3rd<br />Category : PROPOSED STANDARD= <br />Source : DNS Extensions<br />Area : Int= ernet<br />Stream : IETF<br />Verifying Party : IESG<br = /><br /><hr /><br />dnsext mailing list<br />[email protected]<br /><a href= =3D"https://www.ietf.org/mailman/listinfo/dnsext">https://www.ietf.org/ma= ilman/listinfo/dnsext</a></blockquote><br /><br /><br /><hr /><br />dnsex= t mailing list<br />[email protected]<br /><a href=3D"https://www.ietf.org/= mailman/listinfo/dnsext">https://www.ietf.org/mailman/listinfo/dnsext</a>= <br /></pre></blockquote></div><br> -- <br> Sent from my Android device with K-9 Mail. Please excuse my brevity.</div= ></blockquote> <div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so= lid #777; color:#777; margin:0 0 5px; padding-left:5px"> </blockquote><blockquote style=3D"border-left:2px solid #777; color:#777;= margin:0 0 5px; padding-left:5px"><p dir=3D"auto">______________________= _________________________<br> dnsext mailing list<br> [email protected]<br> <a href=3D"https://www.ietf.org/mailman/listinfo/dnsext" style=3D"color:#= 777">https://www.ietf.org/mailman/listinfo/dnsext</a></p> </blockquote></div> </div> </body> </html> --=_MailMate_EE042EF7-4F2F-40D1-8F85-71F290435231_=-- --===============0021773350052059465== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dnsext mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsext --===============0021773350052059465==--