Re: [Editorial Errata Reported] RFC4343 (5112)
Jay Ashworth <[email protected]> Tue, 12 Sep 2017 22:38:22 -0400
| Newsgroups | gmane.ietf.dnsext |
|---|---|
| Message-ID | <[email protected]> |
--===============4200032709573753588==
Content-Type: multipart/alternative;
boundary="----4A11JDH0DN06B9QTQ19VWRB36MIYZI"
Content-Transfer-Encoding: 7bit
------4A11JDH0DN06B9QTQ19VWRB36MIYZI
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
Long time listener, first-time caller, but the problem I have with this is =
that it suggests that queries containing capital letters are dropped=2E=20
I recommend to people with overly complicated and long domain names that, =
as best practice, they spell them in camel case in advertising=2E=20
www=2EMyBadDomain=2Ecom
Partially, of course, this is to attempt to avoid the Pen Island/Who Repre=
sents problem=2E But I do it knowing that the DNS system will case fold th=
ose queries and they will thus work properly=2E
If there are devices dropping those=2E=2E=2E I gotta say I'm a little unh=
appy=2E Is there documentation of that?
Cheers,
-- jra
On September 12, 2017 6:15:00 PM EDT, John Levine <johnl@taugh=2Ecom> wrot=
e:
>I would reject this or at most mark it as hold for update=2E The word
>"should" in lower case appears in two other places where it's not used
>in the 2119 sense, and I think this one is not intended to be the 2119
>sense either=2E The sentence in question is describing the historical
>situation, and the following capital MUSTs tell you what to do=2E =20
>
>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=2E
>
>R's,
>John
>
>
>
>In article <20170912194513=2E752D0B8114C@rfc-editor=2Eorg> you write:
>>The following errata report has been submitted for RFC4343,
>>"Domain Name System (DNS) Case Insensitivity Clarification"=2E
>>
>>--------------------------------------
>>You may review the report below and at:
>>http://www=2Erfc-editor=2Eorg/errata/eid5112
>>
>>--------------------------------------
>>Type: Editorial
>>Reported by: Change "should" to must in section 3=2E(no subsection)
><rich=2Etom@alticeusa=2Ecom>
>>
>>Section: 3
>>
>>Original Text
>>-------------
>>comparisons on name lookup for DNS queries should be case 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=2E Furthermore, the clarification of the case
>insensitive comparison in the
>>following two sentences after that particular sentence use the term
>MUST=2E I suspect some readers of the
>>RFC are reading the word "should" and aren't reading the rest of the
>paragraph=2E
>>
>>Instructions:
>>-------------
>>This erratum is currently posted as "Reported"=2E If necessary, please
>>use "Reply All" to discuss whether it should be verified or
>>rejected=2E When a decision is reached, the verifying party =20
>>can log in to change the status and edit the report, if necessary=2E=20
>>
>>--------------------------------------
>>RFC4343 (draft-ietf-dnsext-insensitive-06)
>>--------------------------------------
>>Title : Domain Name System (DNS) Case Insensitivity
>Clarification
>>Publication Date : January 2006
>>Author(s) : D=2E Eastlake 3rd
>>Category : PROPOSED STANDARD
>>Source : DNS Extensions
>>Area : Internet
>>Stream : IETF
>>Verifying Party : IESG
>>
>>_______________________________________________
>>dnsext mailing list
>>dnsext@ietf=2Eorg
>>https://www=2Eietf=2Eorg/mailman/listinfo/dnsext
>>
>
>
>_______________________________________________
>dnsext mailing list
>dnsext@ietf=2Eorg
>https://www=2Eietf=2Eorg/mailman/listinfo/dnsext
--=20
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E
------4A11JDH0DN06B9QTQ19VWRB36MIYZI
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><head></head><body>Long time listener, first-time caller, but the pro=
blem I have with this is that it suggests that queries containing capital l=
etters are dropped=2E <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=2E <br>
<br>
<a href=3D"http://www=2EMyBadDomain=2Ecom">www=2EMyBadDomain=2Ecom</a><br>
<br>
Partially, of course, this is to attempt to avoid the Pen Island/Who Repre=
sents problem=2E But I do it knowing that the DNS system will case fold th=
ose queries and they will thus work properly=2E<br>
<br>
If there are devices dropping those=2E=2E=2E I gotta say I'm a little=
unhappy=2E 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 <johnl@taugh=2Ecom> wrote:<blockquote class=3D"gmail=
_quote" style=3D"margin: 0pt 0pt 0pt 0=2E8ex; border-left: 1px solid rgb(20=
4, 204, 204); padding-left: 1ex;">
<pre class=3D"k9mail">I would reject this or at most mark it as hold for u=
pdate=2E The word<br />"should" in lower case appears in two oth=
er places where it's not used<br />in the 2119 sense, and I think this one =
is not intended to be the 2119<br />sense either=2E The sentence in questi=
on is describing the historical<br />situation, and the following capital M=
USTs tell you what to do=2E <br /><br />Having said that, if we ever revis=
it this document, it would benefit<br />from rewording to make it clearer w=
hen it is telling you what to do<br />and when it's just giving background=
=2E<br /><br />R's,<br />John<br /><br /><br /><br />In article <2017091=
2194513=2E752D0B8114C@rfc-editor=2Eorg> you write:<br /><blockquote clas=
s=3D"gmail_quote" style=3D"margin: 0pt 0pt 1ex 0=2E8ex; border-left: 1px so=
lid #729fcf; padding-left: 1ex;">The following errata report has been submi=
tted for RFC4343,<br />"Domain Name System (DNS) Case Insensitivity Cl=
arification"=2E<br /><br /><hr /><br />You may review the report below=
and at:<br /><a href=3D"http://www=2Erfc-editor=2Eorg/errata/eid5112">http=
://www=2Erfc-editor=2Eorg/errata/eid5112</a><br /><br /><hr /><br />Type: E=
ditorial<br />Reported by: Change "should" to must in section 3=
=2E(no subsection) <rich=2Etom@alticeusa=2Ecom><br /><br />Section: 3=
<br /><br />Original Text<br />-------------<br />comparisons on name looku=
p for DNS queries should be case insensitive<br /><br />Corrected Text<br /=
>--------------<br />comparisons on name lookup for DNS queries must be cas=
e insensitive<br /><br />Notes<br />-----<br />Some authoritative DNS serve=
rs and/or mitigation devices/software silently drop queries that have<br />=
uppercase letters in them=2E Furthermore, the clarification of the case in=
sensitive comparison in the<br />following two sentences after that particu=
lar sentence use the term MUST=2E I suspect some readers of the<br />RFC a=
re reading the word "should" and aren't reading the rest of the p=
aragraph=2E<br /><br />Instructions:<br />-------------<br />This erratum i=
s currently posted as "Reported"=2E If necessary, please<br />use=
"Reply All" to discuss whether it should be verified or<br />rej=
ected=2E When a decision is reached, the verifying party <br />can log in =
to change the status and edit the report, if necessary=2E <br /><br /><hr /=
><br />RFC4343 (draft-ietf-dnsext-insensitive-06)<br /><hr /><br />Title =
: Domain Name System (DNS) Case Insensitivity Clarification<br =
/>Publication Date : January 2006<br />Author(s) : D=2E Eastla=
ke 3rd<br />Category : PROPOSED STANDARD<br />Source =
: DNS Extensions<br />Area : Internet<br />Stream =
: IETF<br />Verifying Party : IESG<br /><br /><hr /><br />dnsext m=
ailing list<br />dnsext@ietf=2Eorg<br /><a href=3D"https://www=2Eietf=2Eorg=
/mailman/listinfo/dnsext">https://www=2Eietf=2Eorg/mailman/listinfo/dnsext<=
/a></blockquote><br /><br /><br /><hr /><br />dnsext mailing list<br />dnse=
xt@ietf=2Eorg<br /><a href=3D"https://www=2Eietf=2Eorg/mailman/listinfo/dns=
ext">https://www=2Eietf=2Eorg/mailman/listinfo/dnsext</a><br /></pre></bloc=
kquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E</=
body></html>
------4A11JDH0DN06B9QTQ19VWRB36MIYZI--
--===============4200032709573753588==
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
--===============4200032709573753588==--