Debian Codegraph @

rfc9156.html

raw
1 <!DOCTYPE html>
2 <html lang="en" class="RFC">
3 <head>
4 <meta charset="utf-8">
5 <meta content="Common,Latin" name="scripts">
6 <meta content="initial-scale=1.0" name="viewport">
7 <title>RFC 9156: DNS Query Name Minimisation to Improve Privacy</title>
8 <meta content="Stephane Bortzmeyer" name="author">
9 <meta content="Ralph Dolmans" name="author">
10 <meta content="Paul Hoffman" name="author">
11 <meta content='
12 This document describes a technique called "QNAME minimisation" to improve
13 DNS privacy, where the DNS resolver no longer always sends the full
14 original QNAME and original QTYPE to the upstream name server. This document
15 obsoletes RFC 7816.
16 ' name="description">
17 <meta content="xml2rfc 3.11.1" name="generator">
18 <meta content="QNAME" name="keyword">
19 <meta content="9156" name="rfc.number">
20 <!-- Generator version information:
21 xml2rfc 3.11.1
22 Python 3.6.13
23 appdirs 1.4.4
24 ConfigArgParse 1.4.1
25 google-i18n-address 2.4.0
26 html5lib 1.0.1
27 intervaltree 3.0.2
28 Jinja2 2.11.3
29 kitchen 1.2.6
30 lxml 4.4.2
31 pycairo 1.15.1
32 pycountry 19.8.18
33 pyflakes 2.1.1
34 PyYAML 5.4.1
35 requests 2.24.0
36 setuptools 40.5.0
37 six 1.14.0
38 WeasyPrint 52.5
39 -->
40 <link href="rfc9156.xml" rel="alternate" type="application/rfc+xml">
41 <link href="#copyright" rel="license">
42 <style type="text/css">/*
43
44 NOTE: Changes at the bottom of this file overrides some earlier settings.
45
46 Once the style has stabilized and has been adopted as an official RFC style,
47 this can be consolidated so that style settings occur only in one place, but
48 for now the contents of this file consists first of the initial CSS work as
49 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
50 commented changes found necssary during the development of the v3
51 formatters.
52
53 */
54
55 /* fonts */
56 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
57 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
58 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
59
60 @viewport {
61 zoom: 1.0;
62 width: extend-to-zoom;
63 }
64 @-ms-viewport {
65 width: extend-to-zoom;
66 zoom: 1.0;
67 }
68 /* general and mobile first */
69 html {
70 }
71 body {
72 max-width: 90%;
73 margin: 1.5em auto;
74 color: #222;
75 background-color: #fff;
76 font-size: 14px;
77 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
78 line-height: 1.6;
79 scroll-behavior: smooth;
80 }
81 .ears {
82 display: none;
83 }
84
85 /* headings */
86 #title, h1, h2, h3, h4, h5, h6 {
87 margin: 1em 0 0.5em;
88 font-weight: bold;
89 line-height: 1.3;
90 }
91 #title {
92 clear: both;
93 border-bottom: 1px solid #ddd;
94 margin: 0 0 0.5em 0;
95 padding: 1em 0 0.5em;
96 }
97 .author {
98 padding-bottom: 4px;
99 }
100 h1 {
101 font-size: 26px;
102 margin: 1em 0;
103 }
104 h2 {
105 font-size: 22px;
106 margin-top: -20px; /* provide offset for in-page anchors */
107 padding-top: 33px;
108 }
109 h3 {
110 font-size: 18px;
111 margin-top: -36px; /* provide offset for in-page anchors */
112 padding-top: 42px;
113 }
114 h4 {
115 font-size: 16px;
116 margin-top: -36px; /* provide offset for in-page anchors */
117 padding-top: 42px;
118 }
119 h5, h6 {
120 font-size: 14px;
121 }
122 #n-copyright-notice {
123 border-bottom: 1px solid #ddd;
124 padding-bottom: 1em;
125 margin-bottom: 1em;
126 }
127 /* general structure */
128 p {
129 padding: 0;
130 margin: 0 0 1em 0;
131 text-align: left;
132 }
133 div, span {
134 position: relative;
135 }
136 div {
137 margin: 0;
138 }
139 .alignRight.art-text {
140 background-color: #f9f9f9;
141 border: 1px solid #eee;
142 border-radius: 3px;
143 padding: 1em 1em 0;
144 margin-bottom: 1.5em;
145 }
146 .alignRight.art-text pre {
147 padding: 0;
148 }
149 .alignRight {
150 margin: 1em 0;
151 }
152 .alignRight > *:first-child {
153 border: none;
154 margin: 0;
155 float: right;
156 clear: both;
157 }
158 .alignRight > *:nth-child(2) {
159 clear: both;
160 display: block;
161 border: none;
162 }
163 svg {
164 display: block;
165 }
166 .alignCenter.art-text {
167 background-color: #f9f9f9;
168 border: 1px solid #eee;
169 border-radius: 3px;
170 padding: 1em 1em 0;
171 margin-bottom: 1.5em;
172 }
173 .alignCenter.art-text pre {
174 padding: 0;
175 }
176 .alignCenter {
177 margin: 1em 0;
178 }
179 .alignCenter > *:first-child {
180 border: none;
181 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
182 support flexbox yet.
183 */
184 display: table;
185 margin: 0 auto;
186 }
187
188 /* lists */
189 ol, ul {
190 padding: 0;
191 margin: 0 0 1em 2em;
192 }
193 ol ol, ul ul, ol ul, ul ol {
194 margin-left: 1em;
195 }
196 li {
197 margin: 0 0 0.25em 0;
198 }
199 .ulCompact li {
200 margin: 0;
201 }
202 ul.empty, .ulEmpty {
203 list-style-type: none;
204 }
205 ul.empty li, .ulEmpty li {
206 margin-top: 0.5em;
207 }
208 ul.ulBare, li.ulBare {
209 margin-left: 0em !important;
210 }
211 ul.compact, .ulCompact,
212 ol.compact, .olCompact {
213 line-height: 100%;
214 margin: 0 0 0 2em;
215 }
216
217 /* definition lists */
218 dl {
219 }
220 dl > dt {
221 float: left;
222 margin-right: 1em;
223 }
224 /*
225 dl.nohang > dt {
226 float: none;
227 }
228 */
229 dl > dd {
230 margin-bottom: .8em;
231 min-height: 1.3em;
232 }
233 dl.compact > dd, .dlCompact > dd {
234 margin-bottom: 0em;
235 }
236 dl > dd > dl {
237 margin-top: 0.5em;
238 margin-bottom: 0em;
239 }
240
241 /* links */
242 a {
243 text-decoration: none;
244 }
245 a[href] {
246 color: #22e; /* Arlen: WCAG 2019 */
247 }
248 a[href]:hover {
249 background-color: #f2f2f2;
250 }
251 figcaption a[href],
252 a[href].selfRef {
253 color: #222;
254 }
255 /* XXX probably not this:
256 a.selfRef:hover {
257 background-color: transparent;
258 cursor: default;
259 } */
260
261 /* Figures */
262 tt, code, pre, code {
263 background-color: #f9f9f9;
264 font-family: 'Roboto Mono', monospace;
265 }
266 pre {
267 border: 1px solid #eee;
268 margin: 0;
269 padding: 1em;
270 }
271 img {
272 max-width: 100%;
273 }
274 figure {
275 margin: 0;
276 }
277 figure blockquote {
278 margin: 0.8em 0.4em 0.4em;
279 }
280 figcaption {
281 font-style: italic;
282 margin: 0 0 1em 0;
283 }
284 @media screen {
285 pre {
286 overflow-x: auto;
287 max-width: 100%;
288 max-width: calc(100% - 22px);
289 }
290 }
291
292 /* aside, blockquote */
293 aside, blockquote {
294 margin-left: 0;
295 padding: 1.2em 2em;
296 }
297 blockquote {
298 background-color: #f9f9f9;
299 color: #111; /* Arlen: WCAG 2019 */
300 border: 1px solid #ddd;
301 border-radius: 3px;
302 margin: 1em 0;
303 }
304 cite {
305 display: block;
306 text-align: right;
307 font-style: italic;
308 }
309
310 /* tables */
311 table {
312 width: 100%;
313 margin: 0 0 1em;
314 border-collapse: collapse;
315 border: 1px solid #eee;
316 }
317 th, td {
318 text-align: left;
319 vertical-align: top;
320 padding: 0.5em 0.75em;
321 }
322 th {
323 text-align: left;
324 background-color: #e9e9e9;
325 }
326 tr:nth-child(2n+1) > td {
327 background-color: #f5f5f5;
328 }
329 table caption {
330 font-style: italic;
331 margin: 0;
332 padding: 0;
333 text-align: left;
334 }
335 table p {
336 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
337 be allowed within tables more generally, it would be far better to select on a class. */
338 margin: 0;
339 }
340
341 /* pilcrow */
342 a.pilcrow {
343 color: #666; /* Arlen: AHDJ 2019 */
344 text-decoration: none;
345 visibility: hidden;
346 user-select: none;
347 -ms-user-select: none;
348 -o-user-select:none;
349 -moz-user-select: none;
350 -khtml-user-select: none;
351 -webkit-user-select: none;
352 -webkit-touch-callout: none;
353 }
354 @media screen {
355 aside:hover > a.pilcrow,
356 p:hover > a.pilcrow,
357 blockquote:hover > a.pilcrow,
358 div:hover > a.pilcrow,
359 li:hover > a.pilcrow,
360 pre:hover > a.pilcrow {
361 visibility: visible;
362 }
363 a.pilcrow:hover {
364 background-color: transparent;
365 }
366 }
367
368 /* misc */
369 hr {
370 border: 0;
371 border-top: 1px solid #eee;
372 }
373 .bcp14 {
374 font-variant: small-caps;
375 }
376
377 .role {
378 font-variant: all-small-caps;
379 }
380
381 /* info block */
382 #identifiers {
383 margin: 0;
384 font-size: 0.9em;
385 }
386 #identifiers dt {
387 width: 3em;
388 clear: left;
389 }
390 #identifiers dd {
391 float: left;
392 margin-bottom: 0;
393 }
394 /* Fix PDF info block run off issue */
395 @media print {
396 #identifiers dd {
397 float: none;
398 }
399 }
400 #identifiers .authors .author {
401 display: inline-block;
402 margin-right: 1.5em;
403 }
404 #identifiers .authors .org {
405 font-style: italic;
406 }
407
408 /* The prepared/rendered info at the very bottom of the page */
409 .docInfo {
410 color: #666; /* Arlen: WCAG 2019 */
411 font-size: 0.9em;
412 font-style: italic;
413 margin-top: 2em;
414 }
415 .docInfo .prepared {
416 float: left;
417 }
418 .docInfo .prepared {
419 float: right;
420 }
421
422 /* table of contents */
423 #toc {
424 padding: 0.75em 0 2em 0;
425 margin-bottom: 1em;
426 }
427 nav.toc ul {
428 margin: 0 0.5em 0 0;
429 padding: 0;
430 list-style: none;
431 }
432 nav.toc li {
433 line-height: 1.3em;
434 margin: 0.75em 0;
435 padding-left: 1.2em;
436 text-indent: -1.2em;
437 }
438 /* references */
439 .references dt {
440 text-align: right;
441 font-weight: bold;
442 min-width: 7em;
443 }
444 .references dd {
445 margin-left: 8em;
446 overflow: auto;
447 }
448
449 .refInstance {
450 margin-bottom: 1.25em;
451 }
452
453 .references .ascii {
454 margin-bottom: 0.25em;
455 }
456
457 /* index */
458 .index ul {
459 margin: 0 0 0 1em;
460 padding: 0;
461 list-style: none;
462 }
463 .index ul ul {
464 margin: 0;
465 }
466 .index li {
467 margin: 0;
468 text-indent: -2em;
469 padding-left: 2em;
470 padding-bottom: 5px;
471 }
472 .indexIndex {
473 margin: 0.5em 0 1em;
474 }
475 .index a {
476 font-weight: 700;
477 }
478 /* make the index two-column on all but the smallest screens */
479 @media (min-width: 600px) {
480 .index ul {
481 -moz-column-count: 2;
482 -moz-column-gap: 20px;
483 }
484 .index ul ul {
485 -moz-column-count: 1;
486 -moz-column-gap: 0;
487 }
488 }
489
490 /* authors */
491 address.vcard {
492 font-style: normal;
493 margin: 1em 0;
494 }
495
496 address.vcard .nameRole {
497 font-weight: 700;
498 margin-left: 0;
499 }
500 address.vcard .label {
501 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
502 margin: 0.5em 0;
503 }
504 address.vcard .type {
505 display: none;
506 }
507 .alternative-contact {
508 margin: 1.5em 0 1em;
509 }
510 hr.addr {
511 border-top: 1px dashed;
512 margin: 0;
513 color: #ddd;
514 max-width: calc(100% - 16px);
515 }
516
517 /* temporary notes */
518 .rfcEditorRemove::before {
519 position: absolute;
520 top: 0.2em;
521 right: 0.2em;
522 padding: 0.2em;
523 content: "The RFC Editor will remove this note";
524 color: #9e2a00; /* Arlen: WCAG 2019 */
525 background-color: #ffd; /* Arlen: WCAG 2019 */
526 }
527 .rfcEditorRemove {
528 position: relative;
529 padding-top: 1.8em;
530 background-color: #ffd; /* Arlen: WCAG 2019 */
531 border-radius: 3px;
532 }
533 .cref {
534 background-color: #ffd; /* Arlen: WCAG 2019 */
535 padding: 2px 4px;
536 }
537 .crefSource {
538 font-style: italic;
539 }
540 /* alternative layout for smaller screens */
541 @media screen and (max-width: 1023px) {
542 body {
543 padding-top: 2em;
544 }
545 #title {
546 padding: 1em 0;
547 }
548 h1 {
549 font-size: 24px;
550 }
551 h2 {
552 font-size: 20px;
553 margin-top: -18px; /* provide offset for in-page anchors */
554 padding-top: 38px;
555 }
556 #identifiers dd {
557 max-width: 60%;
558 }
559 #toc {
560 position: fixed;
561 z-index: 2;
562 top: 0;
563 right: 0;
564 padding: 0;
565 margin: 0;
566 background-color: inherit;
567 border-bottom: 1px solid #ccc;
568 }
569 #toc h2 {
570 margin: -1px 0 0 0;
571 padding: 4px 0 4px 6px;
572 padding-right: 1em;
573 min-width: 190px;
574 font-size: 1.1em;
575 text-align: right;
576 background-color: #444;
577 color: white;
578 cursor: pointer;
579 }
580 #toc h2::before { /* css hamburger */
581 float: right;
582 position: relative;
583 width: 1em;
584 height: 1px;
585 left: -164px;
586 margin: 6px 0 0 0;
587 background: white none repeat scroll 0 0;
588 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
589 content: "";
590 }
591 #toc nav {
592 display: none;
593 padding: 0.5em 1em 1em;
594 overflow: auto;
595 height: calc(100vh - 48px);
596 border-left: 1px solid #ddd;
597 }
598 }
599
600 /* alternative layout for wide screens */
601 @media screen and (min-width: 1024px) {
602 body {
603 max-width: 724px;
604 margin: 42px auto;
605 padding-left: 1.5em;
606 padding-right: 29em;
607 }
608 #toc {
609 position: fixed;
610 top: 42px;
611 right: 42px;
612 width: 25%;
613 margin: 0;
614 padding: 0 1em;
615 z-index: 1;
616 }
617 #toc h2 {
618 border-top: none;
619 border-bottom: 1px solid #ddd;
620 font-size: 1em;
621 font-weight: normal;
622 margin: 0;
623 padding: 0.25em 1em 1em 0;
624 }
625 #toc nav {
626 display: block;
627 height: calc(90vh - 84px);
628 bottom: 0;
629 padding: 0.5em 0 0;
630 overflow: auto;
631 }
632 img { /* future proofing */
633 max-width: 100%;
634 height: auto;
635 }
636 }
637
638 /* pagination */
639 @media print {
640 body {
641
642 width: 100%;
643 }
644 p {
645 orphans: 3;
646 widows: 3;
647 }
648 #n-copyright-notice {
649 border-bottom: none;
650 }
651 #toc, #n-introduction {
652 page-break-before: always;
653 }
654 #toc {
655 border-top: none;
656 padding-top: 0;
657 }
658 figure, pre {
659 page-break-inside: avoid;
660 }
661 figure {
662 overflow: scroll;
663 }
664 h1, h2, h3, h4, h5, h6 {
665 page-break-after: avoid;
666 }
667 h2+*, h3+*, h4+*, h5+*, h6+* {
668 page-break-before: avoid;
669 }
670 pre {
671 white-space: pre-wrap;
672 word-wrap: break-word;
673 font-size: 10pt;
674 }
675 table {
676 border: 1px solid #ddd;
677 }
678 td {
679 border-top: 1px solid #ddd;
680 }
681 }
682
683 /* This is commented out here, as the string-set: doesn't
684 pass W3C validation currently */
685 /*
686 .ears thead .left {
687 string-set: ears-top-left content();
688 }
689
690 .ears thead .center {
691 string-set: ears-top-center content();
692 }
693
694 .ears thead .right {
695 string-set: ears-top-right content();
696 }
697
698 .ears tfoot .left {
699 string-set: ears-bottom-left content();
700 }
701
702 .ears tfoot .center {
703 string-set: ears-bottom-center content();
704 }
705
706 .ears tfoot .right {
707 string-set: ears-bottom-right content();
708 }
709 */
710
711 @page :first {
712 padding-top: 0;
713 @top-left {
714 content: normal;
715 border: none;
716 }
717 @top-center {
718 content: normal;
719 border: none;
720 }
721 @top-right {
722 content: normal;
723 border: none;
724 }
725 }
726
727 @page {
728 size: A4;
729 margin-bottom: 45mm;
730 padding-top: 20px;
731 /* The follwing is commented out here, but set appropriately by in code, as
732 the content depends on the document */
733 /*
734 @top-left {
735 content: 'Internet-Draft';
736 vertical-align: bottom;
737 border-bottom: solid 1px #ccc;
738 }
739 @top-left {
740 content: string(ears-top-left);
741 vertical-align: bottom;
742 border-bottom: solid 1px #ccc;
743 }
744 @top-center {
745 content: string(ears-top-center);
746 vertical-align: bottom;
747 border-bottom: solid 1px #ccc;
748 }
749 @top-right {
750 content: string(ears-top-right);
751 vertical-align: bottom;
752 border-bottom: solid 1px #ccc;
753 }
754 @bottom-left {
755 content: string(ears-bottom-left);
756 vertical-align: top;
757 border-top: solid 1px #ccc;
758 }
759 @bottom-center {
760 content: string(ears-bottom-center);
761 vertical-align: top;
762 border-top: solid 1px #ccc;
763 }
764 @bottom-right {
765 content: '[Page ' counter(page) ']';
766 vertical-align: top;
767 border-top: solid 1px #ccc;
768 }
769 */
770
771 }
772
773 /* Changes introduced to fix issues found during implementation */
774 /* Make sure links are clickable even if overlapped by following H* */
775 a {
776 z-index: 2;
777 }
778 /* Separate body from document info even without intervening H1 */
779 section {
780 clear: both;
781 }
782
783
784 /* Top align author divs, to avoid names without organization dropping level with org names */
785 .author {
786 vertical-align: top;
787 }
788
789 /* Leave room in document info to show Internet-Draft on one line */
790 #identifiers dt {
791 width: 8em;
792 }
793
794 /* Don't waste quite as much whitespace between label and value in doc info */
795 #identifiers dd {
796 margin-left: 1em;
797 }
798
799 /* Give floating toc a background color (needed when it's a div inside section */
800 #toc {
801 background-color: white;
802 }
803
804 /* Make the collapsed ToC header render white on gray also when it's a link */
805 @media screen and (max-width: 1023px) {
806 #toc h2 a,
807 #toc h2 a:link,
808 #toc h2 a:focus,
809 #toc h2 a:hover,
810 #toc a.toplink,
811 #toc a.toplink:hover {
812 color: white;
813 background-color: #444;
814 text-decoration: none;
815 }
816 }
817
818 /* Give the bottom of the ToC some whitespace */
819 @media screen and (min-width: 1024px) {
820 #toc {
821 padding: 0 0 1em 1em;
822 }
823 }
824
825 /* Style section numbers with more space between number and title */
826 .section-number {
827 padding-right: 0.5em;
828 }
829
830 /* prevent monospace from becoming overly large */
831 tt, code, pre, code {
832 font-size: 95%;
833 }
834
835 /* Fix the height/width aspect for ascii art*/
836 pre.sourcecode,
837 .art-text pre {
838 line-height: 1.12;
839 }
840
841
842 /* Add styling for a link in the ToC that points to the top of the document */
843 a.toplink {
844 float: right;
845 margin-right: 0.5em;
846 }
847
848 /* Fix the dl styling to match the RFC 7992 attributes */
849 dl > dt,
850 dl.dlParallel > dt {
851 float: left;
852 margin-right: 1em;
853 }
854 dl.dlNewline > dt {
855 float: none;
856 }
857
858 /* Provide styling for table cell text alignment */
859 table td.text-left,
860 table th.text-left {
861 text-align: left;
862 }
863 table td.text-center,
864 table th.text-center {
865 text-align: center;
866 }
867 table td.text-right,
868 table th.text-right {
869 text-align: right;
870 }
871
872 /* Make the alternative author contact informatio look less like just another
873 author, and group it closer with the primary author contact information */
874 .alternative-contact {
875 margin: 0.5em 0 0.25em 0;
876 }
877 address .non-ascii {
878 margin: 0 0 0 2em;
879 }
880
881 /* With it being possible to set tables with alignment
882 left, center, and right, { width: 100%; } does not make sense */
883 table {
884 width: auto;
885 }
886
887 /* Avoid reference text that sits in a block with very wide left margin,
888 because of a long floating dt label.*/
889 .references dd {
890 overflow: visible;
891 }
892
893 /* Control caption placement */
894 caption {
895 caption-side: bottom;
896 }
897
898 /* Limit the width of the author address vcard, so names in right-to-left
899 script don't end up on the other side of the page. */
900
901 address.vcard {
902 max-width: 30em;
903 margin-right: auto;
904 }
905
906 /* For address alignment dependent on LTR or RTL scripts */
907 address div.left {
908 text-align: left;
909 }
910 address div.right {
911 text-align: right;
912 }
913
914 /* Provide table alignment support. We can't use the alignX classes above
915 since they do unwanted things with caption and other styling. */
916 table.right {
917 margin-left: auto;
918 margin-right: 0;
919 }
920 table.center {
921 margin-left: auto;
922 margin-right: auto;
923 }
924 table.left {
925 margin-left: 0;
926 margin-right: auto;
927 }
928
929 /* Give the table caption label the same styling as the figcaption */
930 caption a[href] {
931 color: #222;
932 }
933
934 @media print {
935 .toplink {
936 display: none;
937 }
938
939 /* avoid overwriting the top border line with the ToC header */
940 #toc {
941 padding-top: 1px;
942 }
943
944 /* Avoid page breaks inside dl and author address entries */
945 .vcard {
946 page-break-inside: avoid;
947 }
948
949 }
950 /* Tweak the bcp14 keyword presentation */
951 .bcp14 {
952 font-variant: small-caps;
953 font-weight: bold;
954 font-size: 0.9em;
955 }
956 /* Tweak the invisible space above H* in order not to overlay links in text above */
957 h2 {
958 margin-top: -18px; /* provide offset for in-page anchors */
959 padding-top: 31px;
960 }
961 h3 {
962 margin-top: -18px; /* provide offset for in-page anchors */
963 padding-top: 24px;
964 }
965 h4 {
966 margin-top: -18px; /* provide offset for in-page anchors */
967 padding-top: 24px;
968 }
969 /* Float artwork pilcrow to the right */
970 @media screen {
971 .artwork a.pilcrow {
972 display: block;
973 line-height: 0.7;
974 margin-top: 0.15em;
975 }
976 }
977 /* Make pilcrows on dd visible */
978 @media screen {
979 dd:hover > a.pilcrow {
980 visibility: visible;
981 }
982 }
983 /* Make the placement of figcaption match that of a table's caption
984 by removing the figure's added bottom margin */
985 .alignLeft.art-text,
986 .alignCenter.art-text,
987 .alignRight.art-text {
988 margin-bottom: 0;
989 }
990 .alignLeft,
991 .alignCenter,
992 .alignRight {
993 margin: 1em 0 0 0;
994 }
995 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
996 possibly even requiring a new line */
997 @media print {
998 a.pilcrow {
999 display: none;
1000 }
1001 }
1002 /* Styling for the external metadata */
1003 div#external-metadata {
1004 background-color: #eee;
1005 padding: 0.5em;
1006 margin-bottom: 0.5em;
1007 display: none;
1008 }
1009 div#internal-metadata {
1010 padding: 0.5em; /* to match the external-metadata padding */
1011 }
1012 /* Styling for title RFC Number */
1013 h1#rfcnum {
1014 clear: both;
1015 margin: 0 0 -1em;
1016 padding: 1em 0 0 0;
1017 }
1018 /* Make .olPercent look the same as <ol><li> */
1019 dl.olPercent > dd {
1020 margin-bottom: 0.25em;
1021 min-height: initial;
1022 }
1023 /* Give aside some styling to set it apart */
1024 aside {
1025 border-left: 1px solid #ddd;
1026 margin: 1em 0 1em 2em;
1027 padding: 0.2em 2em;
1028 }
1029 aside > dl,
1030 aside > ol,
1031 aside > ul,
1032 aside > table,
1033 aside > p {
1034 margin-bottom: 0.5em;
1035 }
1036 /* Additional page break settings */
1037 @media print {
1038 figcaption, table caption {
1039 page-break-before: avoid;
1040 }
1041 }
1042 /* Font size adjustments for print */
1043 @media print {
1044 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1045 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1046 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1047 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1048 h4 { font-size: 1em; padding-top: 1.5em; }
1049 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1050 }
1051 /* Sourcecode margin in print, when there's no pilcrow */
1052 @media print {
1053 .artwork,
1054 .sourcecode {
1055 margin-bottom: 1em;
1056 }
1057 }
1058 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1059 table {
1060 min-width: 20em;
1061 }
1062 /* ol type a */
1063 ol.type-a { list-style-type: lower-alpha; }
1064 ol.type-A { list-style-type: upper-alpha; }
1065 ol.type-i { list-style-type: lower-roman; }
1066 ol.type-I { list-style-type: lower-roman; }
1067 /* Apply the print table and row borders in general, on request from the RPC,
1068 and increase the contrast between border and odd row background sligthtly */
1069 table {
1070 border: 1px solid #ddd;
1071 }
1072 td {
1073 border-top: 1px solid #ddd;
1074 }
1075 tr:nth-child(2n+1) > td {
1076 background-color: #f8f8f8;
1077 }
1078 /* Use style rules to govern display of the TOC. */
1079 @media screen and (max-width: 1023px) {
1080 #toc nav { display: none; }
1081 #toc.active nav { display: block; }
1082 }
1083 /* Add support for keepWithNext */
1084 .keepWithNext {
1085 break-after: avoid-page;
1086 break-after: avoid-page;
1087 }
1088 /* Add support for keepWithPrevious */
1089 .keepWithPrevious {
1090 break-before: avoid-page;
1091 }
1092 /* Change the approach to avoiding breaks inside artwork etc. */
1093 figure, pre, table, .artwork, .sourcecode {
1094 break-before: auto;
1095 break-after: auto;
1096 }
1097 /* Avoid breaks between <dt> and <dd> */
1098 dl {
1099 break-before: auto;
1100 break-inside: auto;
1101 }
1102 dt {
1103 break-before: auto;
1104 break-after: avoid-page;
1105 }
1106 dd {
1107 break-before: avoid-page;
1108 break-after: auto;
1109 orphans: 3;
1110 widows: 3
1111 }
1112 span.break, dd.break {
1113 margin-bottom: 0;
1114 min-height: 0;
1115 break-before: auto;
1116 break-inside: auto;
1117 break-after: auto;
1118 }
1119 /* Undo break-before ToC */
1120 @media print {
1121 #toc {
1122 break-before: auto;
1123 }
1124 }
1125 /* Text in compact lists should not get extra bottim margin space,
1126 since that would makes the list not compact */
1127 ul.compact p, .ulCompact p,
1128 ol.compact p, .olCompact p {
1129 margin: 0;
1130 }
1131 /* But the list as a whole needs the extra space at the end */
1132 section ul.compact,
1133 section .ulCompact,
1134 section ol.compact,
1135 section .olCompact {
1136 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1137 }
1138 /* The tt and code background above interferes with for instance table cell
1139 backgrounds. Changed to something a bit more selective. */
1140 tt, code {
1141 background-color: transparent;
1142 }
1143 p tt, p code, li tt, li code {
1144 background-color: #f8f8f8;
1145 }
1146 /* Tweak the pre margin -- 0px doesn't come out well */
1147 pre {
1148 margin-top: 0.5px;
1149 }
1150 /* Tweak the comact list text */
1151 ul.compact, .ulCompact,
1152 ol.compact, .olCompact,
1153 dl.compact, .dlCompact {
1154 line-height: normal;
1155 }
1156 /* Don't add top margin for nested lists */
1157 li > ul, li > ol, li > dl,
1158 dd > ul, dd > ol, dd > dl,
1159 dl > dd > dl {
1160 margin-top: initial;
1161 }
1162 /* Elements that should not be rendered on the same line as a <dt> */
1163 /* This should match the element list in writer.text.TextWriter.render_dl() */
1164 dd > div.artwork:first-child,
1165 dd > aside:first-child,
1166 dd > figure:first-child,
1167 dd > ol:first-child,
1168 dd > div:first-child > pre.sourcecode,
1169 dd > table:first-child,
1170 dd > ul:first-child {
1171 clear: left;
1172 }
1173 /* fix for weird browser behaviour when <dd/> is empty */
1174 dt+dd:empty::before{
1175 content: "\00a0";
1176 }
1177 /* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
1178 li > p {
1179 margin-bottom: 0.5em
1180 }
1181 /* Don't let p margin spill out from inside list items */
1182 li > p:last-of-type {
1183 margin-bottom: 0;
1184 }
1185 </style>
1186 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1187 <link href="https://dx.doi.org/10.17487/rfc9156" rel="alternate">
1188 <link href="urn:issn:2070-1721" rel="alternate">
1189 <link href="https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc7816bis-11" rel="prev">
1190 </head>
1191 <body>
1192 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1193 <table class="ears">
1194 <thead><tr>
1195 <td class="left">RFC 9156</td>
1196 <td class="center">QNAME Minimisation</td>
1197 <td class="right">November 2021</td>
1198 </tr></thead>
1199 <tfoot><tr>
1200 <td class="left">Bortzmeyer, et al.</td>
1201 <td class="center">Standards Track</td>
1202 <td class="right">[Page]</td>
1203 </tr></tfoot>
1204 </table>
1205 <div id="external-metadata" class="document-information"></div>
1206 <div id="internal-metadata" class="document-information">
1207 <dl id="identifiers">
1208 <dt class="label-stream">Stream:</dt>
1209 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1210 <dt class="label-rfc">RFC:</dt>
1211 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9156" class="eref">9156</a></dd>
1212 <dt class="label-obsoletes">Obsoletes:</dt>
1213 <dd class="obsoletes">
1214 <a href="https://www.rfc-editor.org/rfc/rfc7816" class="eref">7816</a> </dd>
1215 <dt class="label-category">Category:</dt>
1216 <dd class="category">Standards Track</dd>
1217 <dt class="label-published">Published:</dt>
1218 <dd class="published">
1219 <time datetime="2021-11" class="published">November 2021</time>
1220 </dd>
1221 <dt class="label-issn">ISSN:</dt>
1222 <dd class="issn">2070-1721</dd>
1223 <dt class="label-authors">Authors:</dt>
1224 <dd class="authors">
1225 <div class="author">
1226 <div class="author-name">S. Bortzmeyer</div>
1227 <div class="org">AFNIC</div>
1228 </div>
1229 <div class="author">
1230 <div class="author-name">R. Dolmans</div>
1231 <div class="org">NLnet Labs</div>
1232 </div>
1233 <div class="author">
1234 <div class="author-name">P. Hoffman</div>
1235 <div class="org">ICANN</div>
1236 </div>
1237 </dd>
1238 </dl>
1239 </div>
1240 <h1 id="rfcnum">RFC 9156</h1>
1241 <h1 id="title">DNS Query Name Minimisation to Improve Privacy</h1>
1242 <section id="section-abstract">
1243 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1244 <p id="section-abstract-1">This document describes a technique called "QNAME minimisation" to improve
1245 DNS privacy, where the DNS resolver no longer always sends the full
1246 original QNAME and original QTYPE to the upstream name server. This document
1247 obsoletes RFC 7816.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1248 </section>
1249 <div id="status-of-memo">
1250 <section id="section-boilerplate.1">
1251 <h2 id="name-status-of-this-memo">
1252 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1253 </h2>
1254 <p id="section-boilerplate.1-1">
1255 This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1256 <p id="section-boilerplate.1-2">
1257 This document is a product of the Internet Engineering Task Force
1258 (IETF). It represents the consensus of the IETF community. It has
1259 received public review and has been approved for publication by
1260 the Internet Engineering Steering Group (IESG). Further
1261 information on Internet Standards is available in Section 2 of
1262 RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1263 <p id="section-boilerplate.1-3">
1264 Information about the current status of this document, any
1265 errata, and how to provide feedback on it may be obtained at
1266 <span><a href="https://www.rfc-editor.org/info/rfc9156">https://www.rfc-editor.org/info/rfc9156</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1267 </section>
1268 </div>
1269 <div id="copyright">
1270 <section id="section-boilerplate.2">
1271 <h2 id="name-copyright-notice">
1272 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1273 </h2>
1274 <p id="section-boilerplate.2-1">
1275 Copyright (c) 2021 IETF Trust and the persons identified as the
1276 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1277 <p id="section-boilerplate.2-2">
1278 This document is subject to BCP 78 and the IETF Trust's Legal
1279 Provisions Relating to IETF Documents
1280 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1281 publication of this document. Please review these documents
1282 carefully, as they describe your rights and restrictions with
1283 respect to this document. Code Components extracted from this
1284 document must include Revised BSD License text as described in
1285 Section 4.e of the Trust Legal Provisions and are provided without
1286 warranty as described in the Revised BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1287 </section>
1288 </div>
1289 <div id="toc">
1290 <section id="section-toc.1">
1291 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1292 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1293 </h2>
1294 <nav class="toc"><ul class="compact toc ulBare ulEmpty">
1295 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
1296 <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction-and-background" class="xref">Introduction and Background</a></p>
1297 <ul class="compact toc ulBare ulEmpty">
1298 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.1">
1299 <p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-experience-from-rfc-7816" class="xref">Experience from RFC 7816</a></p>
1300 </li>
1301 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.2">
1302 <p id="section-toc.1-1.1.2.2.1" class="keepWithNext"><a href="#section-1.2" class="xref">1.2</a>.  <a href="#name-terminology" class="xref">Terminology</a></p>
1303 </li>
1304 </ul>
1305 </li>
1306 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
1307 <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-description-of-qname-minimi" class="xref">Description of QNAME Minimisation</a></p>
1308 <ul class="compact toc ulBare ulEmpty">
1309 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.1">
1310 <p id="section-toc.1-1.2.2.1.1"><a href="#section-2.1" class="xref">2.1</a>.  <a href="#name-qtype-selection" class="xref">QTYPE Selection</a></p>
1311 </li>
1312 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.2">
1313 <p id="section-toc.1-1.2.2.2.1"><a href="#section-2.2" class="xref">2.2</a>.  <a href="#name-qname-selection" class="xref">QNAME Selection</a></p>
1314 </li>
1315 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.3">
1316 <p id="section-toc.1-1.2.2.3.1"><a href="#section-2.3" class="xref">2.3</a>.  <a href="#name-limitation-of-the-number-of" class="xref">Limitation of the Number of Queries</a></p>
1317 </li>
1318 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.4">
1319 <p id="section-toc.1-1.2.2.4.1"><a href="#section-2.4" class="xref">2.4</a>.  <a href="#name-implementation-by-stub-and-" class="xref">Implementation by Stub and Forwarding Resolvers</a></p>
1320 </li>
1321 </ul>
1322 </li>
1323 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3">
1324 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-algorithm-to-perform-qname-" class="xref">Algorithm to Perform QNAME Minimisation</a></p>
1325 </li>
1326 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4">
1327 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-qname-minimisation-examples" class="xref">QNAME Minimisation Examples</a></p>
1328 </li>
1329 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
1330 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-performance-considerations" class="xref">Performance Considerations</a></p>
1331 </li>
1332 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
1333 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
1334 </li>
1335 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
1336 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-references" class="xref">References</a></p>
1337 <ul class="compact toc ulBare ulEmpty">
1338 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1">
1339 <p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
1340 </li>
1341 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2">
1342 <p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
1343 </li>
1344 </ul>
1345 </li>
1346 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
1347 <p id="section-toc.1-1.8.1"><a href="#appendix-A" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a></p>
1348 </li>
1349 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
1350 <p id="section-toc.1-1.9.1"><a href="#appendix-B" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
1351 </li>
1352 </ul>
1353 </nav>
1354 </section>
1355 </div>
1356 <div id="intro">
1357 <section id="section-1">
1358 <h2 id="name-introduction-and-background">
1359 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction-and-background" class="section-name selfRef">Introduction and Background</a>
1360 </h2>
1361 <p id="section-1-1">The problem statement for this document is described in <span>[<a href="#RFC9076" class="xref">RFC9076</a>]</span>.
1362 This specific solution is not
1363 intended to fully solve the DNS privacy problem; instead, it
1364 should be viewed as one tool amongst many.<a href="#section-1-1" class="pilcrow">¶</a></p>
1365 <p id="section-1-2">QNAME minimisation follows the principle explained in
1366 <span><a href="https://www.rfc-editor.org/rfc/rfc6973#section-6.1" class="relref">Section 6.1</a> of [<a href="#RFC6973" class="xref">RFC6973</a>]</span>: the less data you send out,
1367 the fewer privacy problems you have.<a href="#section-1-2" class="pilcrow">¶</a></p>
1368 <p id="section-1-3">Before QNAME minimisation, when a resolver received the query "What is
1369 the AAAA record for www.example.com?", it sent to the root (assuming
1370 a resolver, whose cache is empty) the very same question. Sending
1371 the full QNAME to the authoritative name server was a tradition,
1372 not a protocol requirement. In a conversation with one of the authors in
1373 January 2015, Paul Mockapetris explained that this tradition comes
1374 from a desire to optimise the number of requests, when the same
1375 name server is authoritative for many zones in a given name
1376 (something that was more common in the old days, where the same
1377 name servers served .com and the root) or when the same
1378 name server is both recursive and authoritative (something that is
1379 strongly discouraged now). Whatever the merits of this choice at this
1380 time, the DNS is quite different now.<a href="#section-1-3" class="pilcrow">¶</a></p>
1381 <p id="section-1-4">QNAME minimisation is compatible with the current DNS system and
1382 therefore can easily be deployed. Because it is only a change to
1383 the way that the resolver operates, it does not change the DNS protocol itself.
1384 The behaviour suggested here (minimising the
1385 amount of data sent in QNAMEs from the resolver) is allowed by
1386 <span><a href="https://www.rfc-editor.org/rfc/rfc1034#section-5.3.3" class="relref">Section 5.3.3</a> of [<a href="#RFC1034" class="xref">RFC1034</a>]</span> and
1387 <span><a href="https://www.rfc-editor.org/rfc/rfc1035#section-7.2" class="relref">Section 7.2</a> of [<a href="#RFC1035" class="xref">RFC1035</a>]</span>.<a href="#section-1-4" class="pilcrow">¶</a></p>
1388 <section id="section-1.1">
1389 <h3 id="name-experience-from-rfc-7816">
1390 <a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-experience-from-rfc-7816" class="section-name selfRef">Experience from RFC 7816</a>
1391 </h3>
1392 <p id="section-1.1-1">This document obsoletes <span>[<a href="#RFC7816" class="xref">RFC7816</a>]</span>.
1393 <span>[<a href="#RFC7816" class="xref">RFC7816</a>]</span> was categorised "Experimental", but ideas
1394 from it were widely deployed since its publication.
1395 Many resolver implementations now support QNAME minimisation. The lessons
1396 learned from implementing QNAME minimisation were used to create this new
1397 revision.<a href="#section-1.1-1" class="pilcrow">¶</a></p>
1398 <p id="section-1.1-2">Data from DNSThought <span>[<a href="#dnsthought-qnamemin" class="xref">dnsthought-qnamemin</a>]</span>,
1399 Verisign <span>[<a href="#verisign-qnamemin" class="xref">verisign-qnamemin</a>]</span>, and APNIC <span>[<a href="#apnic-qnamemin" class="xref">apnic-qnamemin</a>]</span>
1400 shows that a large percentage of the resolvers deployed on the Internet already support
1401 QNAME minimisation in some way.<a href="#section-1.1-2" class="pilcrow">¶</a></p>
1402 <p id="section-1.1-3">Academic research has been performed on QNAME minimisation
1403 <span>[<a href="#devries-qnamemin" class="xref">devries-qnamemin</a>]</span>. This
1404 work shows that QNAME minimisation in relaxed mode causes almost no problems.
1405 The paper recommends using the A QTYPE and limiting the number of queries in
1406 some way. Some of the issues that the paper found are covered in <a href="#perf_cons" class="xref">Section 5</a>.<a href="#section-1.1-3" class="pilcrow">¶</a></p>
1407 </section>
1408 <section id="section-1.2">
1409 <h3 id="name-terminology">
1410 <a href="#section-1.2" class="section-number selfRef">1.2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
1411 </h3>
1412 <p id="section-1.2-1">The terminology used in this document is defined in <span>[<a href="#RFC8499" class="xref">RFC8499</a>]</span>.<a href="#section-1.2-1" class="pilcrow">¶</a></p>
1413 <p id="section-1.2-2">In this document, a "cold" cache is one that is empty, having literally no
1414 entries in it. A "warm" cache is one that has some entries in it.<a href="#section-1.2-2" class="pilcrow">¶</a></p>
1415 <p id="section-1.2-3">
1416 The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
1417 "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as
1418 described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span>
1419 when, and only when, they appear in all capitals, as shown here.<a href="#section-1.2-3" class="pilcrow">¶</a></p>
1420 </section>
1421 </section>
1422 </div>
1423 <div id="qname-main">
1424 <section id="section-2">
1425 <h2 id="name-description-of-qname-minimi">
1426 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-description-of-qname-minimi" class="section-name selfRef">Description of QNAME Minimisation</a>
1427 </h2>
1428 <p id="section-2-1">The idea behind QNAME minimisation is to minimise the amount of
1429 privacy-sensitive data sent from the DNS resolver to the authoritative
1430 name server. This section describes how to do QNAME minimisation. The algorithm
1431 is summarised in <a href="#zonecutalgo" class="xref">Section 3</a>.<a href="#section-2-1" class="pilcrow">¶</a></p>
1432 <p id="section-2-2">When a resolver is not able to answer a query from cache, it has
1433 to send a query to an authoritative name server. Traditionally, these
1434 queries would contain the full QNAME and the original QTYPE as received
1435 in the client query.<a href="#section-2-2" class="pilcrow">¶</a></p>
1436 <p id="section-2-3">The full QNAME and original QTYPE are only needed at the name server that
1437 is authoritative for the record requested by the client. All other name servers
1438 queried while resolving the query only need to receive enough of the QNAME to
1439 be able to answer with a delegation. The QTYPE in these queries is not
1440 relevant, as the name server is not able to authoritatively answer the records
1441 the client is looking for. Sending the full QNAME and original QTYPE to
1442 these name servers therefore exposes more privacy-sensitive data than
1443 necessary to resolve the client's request.<a href="#section-2-3" class="pilcrow">¶</a></p>
1444 <p id="section-2-4">A resolver that implements QNAME minimisation obscures the QNAME and QTYPE in
1445 queries directed to an authoritative name server that is not known to be
1446 responsible for the original QNAME. These queries contain:<a href="#section-2-4" class="pilcrow">¶</a></p>
1447 <ul class="normal">
1448 <li class="normal" id="section-2-5.1">a QTYPE selected by the resolver to possibly obscure the original QTYPE<a href="#section-2-5.1" class="pilcrow">¶</a>
1449 </li>
1450 <li class="normal" id="section-2-5.2">the QNAME that is the original QNAME, stripped to just one
1451 label more than the longest matching domain name for which the
1452 name server is known to be authoritative<a href="#section-2-5.2" class="pilcrow">¶</a>
1453 </li>
1454 </ul>
1455 <section id="section-2.1">
1456 <h3 id="name-qtype-selection">
1457 <a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-qtype-selection" class="section-name selfRef">QTYPE Selection</a>
1458 </h3>
1459 <p id="section-2.1-1">Note that this document relaxes the recommendation in <span>[<a href="#RFC7816" class="xref">RFC7816</a>]</span> to use the NS
1460 QTYPE to hide the original QTYPE. Using the NS QTYPE is
1461 still allowed. The authority of NS records lies at the child side. The parent
1462 side of the delegation will answer using a referral, like it will do for queries
1463 with other QTYPEs. Using the NS QTYPE therefore has no added value over other
1464 QTYPEs.<a href="#section-2.1-1" class="pilcrow">¶</a></p>
1465 <p id="section-2.1-2">The QTYPE to use while minimising queries can be any possible data type
1466 (as defined in <span><a href="https://www.rfc-editor.org/rfc/rfc6895#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC6895" class="xref">RFC6895</a>]</span>) for which the authority always lies below the zone cut
1467 (i.e., not DS, NSEC, NSEC3, OPT, TSIG, TKEY, ANY, MAILA, MAILB,
1468 AXFR, and IXFR), as long as there is no relation between the incoming QTYPE and
1469 the selection of the QTYPE to use while minimising.
1470 The A or AAAA QTYPEs are always good candidates to use because these
1471 are the least likely to raise issues in DNS software and middleboxes
1472 that do not properly support all QTYPEs.
1473 QTYPE=A or QTYPE=AAAA queries will also blend into traffic from nonminimising
1474 resolvers, making it in some cases harder to observe that the
1475 resolver is using QNAME minimisation. Using a QTYPE that occurs
1476 most in incoming queries will slightly reduce the number of queries,
1477 as there is no extra check needed for delegations on non-apex
1478 records.<a href="#section-2.1-2" class="pilcrow">¶</a></p>
1479 </section>
1480 <section id="section-2.2">
1481 <h3 id="name-qname-selection">
1482 <a href="#section-2.2" class="section-number selfRef">2.2. </a><a href="#name-qname-selection" class="section-name selfRef">QNAME Selection</a>
1483 </h3>
1484 <p id="section-2.2-1">The minimising resolver works perfectly when it knows the zone cut
1485 (zone cuts are described in
1486 <span><a href="https://www.rfc-editor.org/rfc/rfc2181#section-6" class="relref">Section 6</a> of [<a href="#RFC2181" class="xref">RFC2181</a>]</span>). But zone cuts do not
1487 necessarily exist at every label boundary. In the name
1488 www.foo.bar.example, it is possible that there is a zone cut between
1489 "foo" and "bar" but not between "bar" and "example". So, assuming
1490 that the resolver already knows the name servers of example, when it
1491 receives the query "What is the AAAA record of www.foo.bar.example?",
1492 it does not always know where the zone cut will be. To find the
1493 zone cut, it will query the example name servers for a record for
1494 bar.example. It will get a non-referral answer, so it has to query the
1495 example name servers again with one more label, and so on.
1496 (<a href="#zonecutalgo" class="xref">Section 3</a> describes this algorithm in deeper
1497 detail.)<a href="#section-2.2-1" class="pilcrow">¶</a></p>
1498 </section>
1499 <div id="number-of-queries">
1500 <section id="section-2.3">
1501 <h3 id="name-limitation-of-the-number-of">
1502 <a href="#section-2.3" class="section-number selfRef">2.3. </a><a href="#name-limitation-of-the-number-of" class="section-name selfRef">Limitation of the Number of Queries</a>
1503 </h3>
1504 <p id="section-2.3-1">When using QNAME minimisation, the number of labels in the received QNAME can
1505 influence the number of queries sent from the resolver. This opens an attack
1506 vector and can decrease performance. Resolvers supporting QNAME minimisation
1507 <span class="bcp14">MUST</span> implement a mechanism to limit the number of outgoing queries per user
1508 request.<a href="#section-2.3-1" class="pilcrow">¶</a></p>
1509 <p id="section-2.3-2">Take for example an incoming QNAME with many labels, like
1510 www.host.group.department.example.com, where
1511 host.group.department.example.com is hosted on example.com's
1512 name servers.
1513 (Such deep domains are especially common under ip6.arpa.)
1514 Assume a resolver that knows only the
1515 name servers of example.com. Without QNAME minimisation, it would
1516 send these example.com name servers a query for
1517 www.host.group.department.example.com and immediately get a
1518 specific referral or an answer, without the need for more queries
1519 to probe for the zone cut. For such a name, a cold resolver with
1520 QNAME minimisation will send more queries, one per label. Once the cache is
1521 warm, there will be less difference with a traditional resolver.
1522 Testing of this is described in <span>[<a href="#Huque-QNAME-Min" class="xref">Huque-QNAME-Min</a>]</span>.<a href="#section-2.3-2" class="pilcrow">¶</a></p>
1523 <p id="section-2.3-3">The behaviour of sending multiple queries can be exploited by sending queries with a large number of
1524 labels in the QNAME that will be answered using a wildcard record. Take for
1525 example a record for *.example.com, hosted on example.com's name servers. An
1526 incoming query containing a QNAME with more than 100 labels, ending in
1527 example.com, will result in a query per label. By using random labels, the
1528 attacker can bypass the cache and always require the resolver to send many
1529 queries upstream. Note that <span>[<a href="#RFC8198" class="xref">RFC8198</a>]</span> can limit this attack in
1530 some cases.<a href="#section-2.3-3" class="pilcrow">¶</a></p>
1531 <p id="section-2.3-4">One mechanism that <span class="bcp14">MAY</span> be used to reduce this attack vector is by
1532 appending more than one label per iteration for QNAMEs with a large number of labels.
1533 To do this, a maximum number of QNAME minimisation iterations <span class="bcp14">MUST</span> be
1534 selected (MAX_MINIMISE_COUNT); a <span class="bcp14">RECOMMENDED</span> value is 10. Optionally, a
1535 value for the number of
1536 queries that should only have one label appended <span class="bcp14">MAY</span> be selected
1537 (MINIMISE_ONE_LAB); a good value is 4. The assumption here is that the number
1538 of labels on delegations higher in the hierarchy are rather small; therefore,
1539 not exposing too many labels early on has the most privacy benefit.<a href="#section-2.3-4" class="pilcrow">¶</a></p>
1540 <p id="section-2.3-5">Another potential, optional mechanism for limiting the number of queries is to
1541 assume that labels that begin with
1542 an underscore (_) character do not represent privacy-relevant administrative
1543 boundaries. For example, if the QNAME is "_25._tcp.mail.example.org" and the algorithm
1544 has already searched for "mail.example.org", the next query can be for all the
1545 underscore-prefixed names together, namely "_25._tcp.mail.example.org".<a href="#section-2.3-5" class="pilcrow">¶</a></p>
1546 <p id="section-2.3-6">When a resolver needs to send out a query, it will look for the closest-known
1547 delegation point in its cache. The number of not-yet-exposed labels is
1548 the difference between this closest name server and the incoming QNAME. The
1549 first MINIMISE_ONE_LAB labels will be handled as described in
1550 <a href="#qname-main" class="xref">Section 2</a>. The number of labels that are still not
1551 exposed now need to be divided proportionally over the remaining iterations
1552 (MAX_MINIMISE_COUNT - MINIMISE_ONE_LAB). If the not-yet-exposed labels cannot be
1553 equally divided over the remaining iterations, the remainder of the division should
1554 be added to the last iterations. For example, when resolving a QNAME with 18
1555 labels with MAX_MINIMISE_COUNT set to 10 and MINIMISE_ONE_LAB set to 4, the number of
1556 labels added per iteration are: 1,1,1,1,2,2,2,2,3,3.<a href="#section-2.3-6" class="pilcrow">¶</a></p>
1557 </section>
1558 </div>
1559 <section id="section-2.4">
1560 <h3 id="name-implementation-by-stub-and-">
1561 <a href="#section-2.4" class="section-number selfRef">2.4. </a><a href="#name-implementation-by-stub-and-" class="section-name selfRef">Implementation by Stub and Forwarding Resolvers</a>
1562 </h3>
1563 <p id="section-2.4-1">Stub and forwarding resolvers <span class="bcp14">MAY</span> implement QNAME minimisation.
1564 Minimising queries that will be sent to an upstream resolver does not help in
1565 hiding data from the upstream resolver because all information will end up there
1566 anyway. It might however limit the data exposure between the upstream resolver
1567 and the authoritative name server in the situation where the upstream resolver does
1568 not support QNAME minimisation. Using QNAME minimisation in a stub or forwarding
1569 resolver that does not have a mechanism to find and cache zone cuts will
1570 drastically increase the number of outgoing queries.<a href="#section-2.4-1" class="pilcrow">¶</a></p>
1571 </section>
1572 </section>
1573 </div>
1574 <div id="zonecutalgo">
1575 <section id="section-3">
1576 <h2 id="name-algorithm-to-perform-qname-">
1577 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-algorithm-to-perform-qname-" class="section-name selfRef">Algorithm to Perform QNAME Minimisation</a>
1578 </h2>
1579 <p id="section-3-1">This algorithm performs name resolution with QNAME minimisation in
1580 the presence of zone cuts that are not yet known.<a href="#section-3-1" class="pilcrow">¶</a></p>
1581 <p id="section-3-2">Although a validating resolver already has the logic to find the
1582 zone cuts, implementers of resolvers may want to use
1583 this algorithm to locate the zone cuts.<a href="#section-3-2" class="pilcrow">¶</a></p>
1584 <span class="break"></span><dl class="olPercent" id="section-3-3">
1585 <dt>(0)</dt>
1586 <dd id="section-3-3.1">If the query can be answered from the cache, do so;
1587 otherwise, iterate as follows:<a href="#section-3-3.1" class="pilcrow">¶</a>
1588 </dd>
1589 <dd class="break"></dd>
1590 <dt>(1)</dt>
1591 <dd id="section-3-3.2">
1592 <p id="section-3-3.2.1">Get the closest delegation point that can be used for
1593 the original QNAME from the cache.<a href="#section-3-3.2.1" class="pilcrow">¶</a></p>
1594 <span class="break"></span><dl class="olPercent" id="section-3-3.2.2">
1595 <dt>(1a)</dt>
1596 <dd id="section-3-3.2.2.1">For queries with a QTYPE for which the authority only lies at the
1597 parent side (like QTYPE=DS), this is the NS RRset with the owner matching the
1598 most labels with QNAME stripped by one label. QNAME will be a subdomain of
1599 (but not equal to) this NS RRset. Call this ANCESTOR.<a href="#section-3-3.2.2.1" class="pilcrow">¶</a>
1600 </dd>
1601 <dd class="break"></dd>
1602 <dt>(1b)</dt>
1603 <dd id="section-3-3.2.2.2">For queries with other original QTYPEs, this is the NS RRset with the
1604 owner matching the most labels with QNAME. QNAME will be equal to or a
1605 subdomain of this NS RRset. Call this ANCESTOR.<a href="#section-3-3.2.2.2" class="pilcrow">¶</a>
1606 </dd>
1607 <dd class="break"></dd>
1608 </dl>
1609 </dd>
1610 <dd class="break"></dd>
1611 <dt>(2)</dt>
1612 <dd id="section-3-3.3">Initialise CHILD to the same as ANCESTOR.<a href="#section-3-3.3" class="pilcrow">¶</a>
1613 </dd>
1614 <dd class="break"></dd>
1615 <dt>(3)</dt>
1616 <dd id="section-3-3.4">If CHILD is the same as QNAME, or if CHILD is one
1617 label shorter than QNAME and the original QTYPE can only be at the parent side
1618 (like QTYPE=DS), resolve the original query as normal, starting from ANCESTOR's
1619 name servers. Start over from step 0 if new names need to be resolved as a
1620 result of this answer, for example, when the answer contains a CNAME or DNAME <span>[<a href="#RFC6672" class="xref">RFC6672</a>]</span> record.<a href="#section-3-3.4" class="pilcrow">¶</a>
1621 </dd>
1622 <dd class="break"></dd>
1623 <dt>(4)</dt>
1624 <dd id="section-3-3.5">Otherwise, update the value of CHILD by adding the next relevant label or
1625 labels from QNAME to the start
1626 of CHILD. The number of labels to add is discussed in <a href="#number-of-queries" class="xref">Section 2.3</a>.<a href="#section-3-3.5" class="pilcrow">¶</a>
1627 </dd>
1628 <dd class="break"></dd>
1629 <dt>(5)</dt>
1630 <dd id="section-3-3.6">Look for a cache entry for the RRset at CHILD with the original
1631 QTYPE. If the cached response code is NXDOMAIN and the resolver has support for
1632 <span>[<a href="#RFC8020" class="xref">RFC8020</a>]</span>,
1633 the NXDOMAIN can be used in response to the original query, and stop. If the
1634 cached response code is NOERROR (including NODATA), go back to step 3.
1635 If the cached response code is NXDOMAIN and the resolver does not support
1636 <span>[<a href="#RFC8020" class="xref">RFC8020</a>]</span>, go back to step 3.<a href="#section-3-3.6" class="pilcrow">¶</a>
1637 </dd>
1638 <dd class="break"></dd>
1639 <dt>(6)</dt>
1640 <dd id="section-3-3.7">
1641 <p id="section-3-3.7.1">Query for CHILD with the selected QTYPE using one of ANCESTOR's
1642 name servers. The response can be:<a href="#section-3-3.7.1" class="pilcrow">¶</a></p>
1643 <span class="break"></span><dl class="olPercent" id="section-3-3.7.2">
1644 <dt>(6a)</dt>
1645 <dd id="section-3-3.7.2.1">A referral. Cache the NS RRset from the authority
1646 section, and go back to step 1.<a href="#section-3-3.7.2.1" class="pilcrow">¶</a>
1647 </dd>
1648 <dd class="break"></dd>
1649 <dt>(6b)</dt>
1650 <dd id="section-3-3.7.2.2">A DNAME response. Proceed as if a DNAME is received for the
1651 original query. Start over from step 0 to resolve the new name based on the
1652 DNAME target.<a href="#section-3-3.7.2.2" class="pilcrow">¶</a>
1653 </dd>
1654 <dd class="break"></dd>
1655 <dt>(6c)</dt>
1656 <dd id="section-3-3.7.2.3">All other NOERROR answers (including NODATA).
1657 Cache this answer. Regardless of the answered RRset type, including CNAMEs,
1658 continue with the algorithm from step 3 by building the original QNAME.<a href="#section-3-3.7.2.3" class="pilcrow">¶</a>
1659 </dd>
1660 <dd class="break"></dd>
1661 <dt>(6d)</dt>
1662 <dd id="section-3-3.7.2.4">An NXDOMAIN response.
1663 If the resolver supports <span>[<a href="#RFC8020" class="xref">RFC8020</a>]</span>, return an
1664 NXDOMAIN response to the original
1665 query, and stop. If the resolver does not support <span>[<a href="#RFC8020" class="xref">RFC8020</a>]</span>, go to step 3.<a href="#section-3-3.7.2.4" class="pilcrow">¶</a>
1666 </dd>
1667 <dd class="break"></dd>
1668 <dt>(6e)</dt>
1669 <dd id="section-3-3.7.2.5">A timeout or response with another RCODE. The implementation
1670 may choose to retry step 6 with a different ANCESTOR name server.<a href="#section-3-3.7.2.5" class="pilcrow">¶</a>
1671 </dd>
1672 <dd class="break"></dd>
1673 </dl>
1674 </dd>
1675 <dd class="break"></dd>
1676 </dl>
1677 </section>
1678 </div>
1679 <section id="section-4">
1680 <h2 id="name-qname-minimisation-examples">
1681 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-qname-minimisation-examples" class="section-name selfRef">QNAME Minimisation Examples</a>
1682 </h2>
1683 <p id="section-4-1">As a first example, assume that a resolver receives a request to resolve
1684 foo.bar.baz.example. Assume that the resolver already knows that
1685 ns1.nic.example is authoritative for .example and that the resolver does
1686 not know a more specific authoritative name server. It will send the
1687 query with QNAME=baz.example and the QTYPE selected to hide the original
1688 QTYPE to ns1.nic.example.<a href="#section-4-1" class="pilcrow">¶</a></p>
1689 <span id="name-cold-cache-traditional-reso"></span><table class="left" id="table-1">
1690 <caption>
1691 <a href="#table-1" class="selfRef">Table 1</a>:
1692 <a href="#name-cold-cache-traditional-reso" class="selfRef">Cold Cache, Traditional Resolution Algorithm without QNAME Minimisation,
1693 Request for MX Record of a.b.example.org</a>
1694 </caption>
1695 <thead>
1696 <tr>
1697 <th class="text-left" rowspan="1" colspan="1">QTYPE</th>
1698 <th class="text-left" rowspan="1" colspan="1">QNAME</th>
1699 <th class="text-left" rowspan="1" colspan="1">TARGET</th>
1700 <th class="text-left" rowspan="1" colspan="1">NOTE</th>
1701 </tr>
1702 </thead>
1703 <tbody>
1704 <tr>
1705 <td class="text-left" rowspan="1" colspan="1">MX</td>
1706 <td class="text-left" rowspan="1" colspan="1">a.b.example.org</td>
1707 <td class="text-left" rowspan="1" colspan="1">root name server</td>
1708 <td class="text-left" rowspan="1" colspan="1"></td>
1709 </tr>
1710 <tr>
1711 <td class="text-left" rowspan="1" colspan="1">MX</td>
1712 <td class="text-left" rowspan="1" colspan="1">a.b.example.org</td>
1713 <td class="text-left" rowspan="1" colspan="1">org name server</td>
1714 <td class="text-left" rowspan="1" colspan="1"></td>
1715 </tr>
1716 <tr>
1717 <td class="text-left" rowspan="1" colspan="1">MX</td>
1718 <td class="text-left" rowspan="1" colspan="1">a.b.example.org</td>
1719 <td class="text-left" rowspan="1" colspan="1">example.org name server</td>
1720 <td class="text-left" rowspan="1" colspan="1"></td>
1721 </tr>
1722 </tbody>
1723 </table>
1724 <p id="section-4-3">The following are more detailed examples of requests for an MX record of
1725 a.b.example.org with QNAME minimisation, using A QTYPE to hide the original
1726 QTYPE and using other names and authoritative servers:<a href="#section-4-3" class="pilcrow">¶</a></p>
1727 <span id="name-cold-cache-with-qname-minim"></span><table class="left" id="table-2">
1728 <caption>
1729 <a href="#table-2" class="selfRef">Table 2</a>:
1730 <a href="#name-cold-cache-with-qname-minim" class="selfRef">Cold Cache with QNAME Minimisation</a>
1731 </caption>
1732 <thead>
1733 <tr>
1734 <th class="text-left" rowspan="1" colspan="1">QTYPE</th>
1735 <th class="text-left" rowspan="1" colspan="1">QNAME</th>
1736 <th class="text-left" rowspan="1" colspan="1">TARGET</th>
1737 <th class="text-left" rowspan="1" colspan="1">NOTE</th>
1738 </tr>
1739 </thead>
1740 <tbody>
1741 <tr>
1742 <td class="text-left" rowspan="1" colspan="1">A</td>
1743 <td class="text-left" rowspan="1" colspan="1">org</td>
1744 <td class="text-left" rowspan="1" colspan="1">root name server</td>
1745 <td class="text-left" rowspan="1" colspan="1"></td>
1746 </tr>
1747 <tr>
1748 <td class="text-left" rowspan="1" colspan="1">A</td>
1749 <td class="text-left" rowspan="1" colspan="1">example.org</td>
1750 <td class="text-left" rowspan="1" colspan="1">org name server</td>
1751 <td class="text-left" rowspan="1" colspan="1"></td>
1752 </tr>
1753 <tr>
1754 <td class="text-left" rowspan="1" colspan="1">A</td>
1755 <td class="text-left" rowspan="1" colspan="1">b.example.org</td>
1756 <td class="text-left" rowspan="1" colspan="1">example.org name server</td>
1757 <td class="text-left" rowspan="1" colspan="1"></td>
1758 </tr>
1759 <tr>
1760 <td class="text-left" rowspan="1" colspan="1">A</td>
1761 <td class="text-left" rowspan="1" colspan="1">a.b.example.org</td>
1762 <td class="text-left" rowspan="1" colspan="1">example.org name server</td>
1763 <td class="text-left" rowspan="1" colspan="1">"a" may be delegated</td>
1764 </tr>
1765 <tr>
1766 <td class="text-left" rowspan="1" colspan="1">MX</td>
1767 <td class="text-left" rowspan="1" colspan="1">a.b.example.org</td>
1768 <td class="text-left" rowspan="1" colspan="1">example.org name server</td>
1769 <td class="text-left" rowspan="1" colspan="1"></td>
1770 </tr>
1771 </tbody>
1772 </table>
1773 <p id="section-4-5">Note that, in the above example, one query would have been saved if the incoming QTYPE
1774 was the same as the QTYPE selected by the resolver to hide the
1775 original QTYPE. Only one query for a.b.example.org would have been needed if
1776 the original QTYPE would have been A. Using the most-used QTYPE to hide the
1777 original QTYPE therefore slightly reduces the number of outgoing queries compared to
1778 using any other QTYPE to hide the original QTYPE.<a href="#section-4-5" class="pilcrow">¶</a></p>
1779 <span id="name-warm-cache-with-qname-minim"></span><table class="left" id="table-3">
1780 <caption>
1781 <a href="#table-3" class="selfRef">Table 3</a>:
1782 <a href="#name-warm-cache-with-qname-minim" class="selfRef">Warm Cache with QNAME Minimisation</a>
1783 </caption>
1784 <thead>
1785 <tr>
1786 <th class="text-left" rowspan="1" colspan="1">QTYPE</th>
1787 <th class="text-left" rowspan="1" colspan="1">QNAME</th>
1788 <th class="text-left" rowspan="1" colspan="1">TARGET</th>
1789 <th class="text-left" rowspan="1" colspan="1">NOTE</th>
1790 </tr>
1791 </thead>
1792 <tbody>
1793 <tr>
1794 <td class="text-left" rowspan="1" colspan="1">A</td>
1795 <td class="text-left" rowspan="1" colspan="1">example.org</td>
1796 <td class="text-left" rowspan="1" colspan="1">org name server</td>
1797 <td class="text-left" rowspan="1" colspan="1"></td>
1798 </tr>
1799 <tr>
1800 <td class="text-left" rowspan="1" colspan="1">A</td>
1801 <td class="text-left" rowspan="1" colspan="1">b.example.org</td>
1802 <td class="text-left" rowspan="1" colspan="1">example.org name server</td>
1803 <td class="text-left" rowspan="1" colspan="1"></td>
1804 </tr>
1805 <tr>
1806 <td class="text-left" rowspan="1" colspan="1">A</td>
1807 <td class="text-left" rowspan="1" colspan="1">a.b.example.org</td>
1808 <td class="text-left" rowspan="1" colspan="1">example.org name server</td>
1809 <td class="text-left" rowspan="1" colspan="1">"a" may be delegated</td>
1810 </tr>
1811 <tr>
1812 <td class="text-left" rowspan="1" colspan="1">MX</td>
1813 <td class="text-left" rowspan="1" colspan="1">a.b.example.org</td>
1814 <td class="text-left" rowspan="1" colspan="1">example.org name server</td>
1815 <td class="text-left" rowspan="1" colspan="1"></td>
1816 </tr>
1817 </tbody>
1818 </table>
1819 </section>
1820 <div id="perf_cons">
1821 <section id="section-5">
1822 <h2 id="name-performance-considerations">
1823 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-performance-considerations" class="section-name selfRef">Performance Considerations</a>
1824 </h2>
1825 <p id="section-5-1">The main goal of QNAME minimisation is to improve privacy by
1826 sending less data. However, it may have other advantages. For
1827 instance, if a resolver sends a root name server queries
1828 for A.example followed by B.example followed by C.example, the result
1829 will be three NXDOMAINs, since .example does not exist in the root
1830 zone. When using QNAME minimisation, the resolver would send
1831 only one question (for .example itself) to which they could answer
1832 NXDOMAIN. The resolver can cache this answer and use it to prove that
1833 nothing below .example exists <span>[<a href="#RFC8020" class="xref">RFC8020</a>]</span>. A resolver now
1834 knows a priori that neither B.example nor C.example exist. Thus, in this common case,
1835 the total number of upstream
1836 queries under QNAME minimisation could be counterintuitively less
1837 than the number of queries under the traditional iteration (as
1838 described in the DNS standard).<a href="#section-5-1" class="pilcrow">¶</a></p>
1839 <p id="section-5-2">QNAME minimisation can increase the number of queries based on the incoming
1840 QNAME. This is described in <a href="#number-of-queries" class="xref">Section 2.3</a>.
1841 As described in <span>[<a href="#devries-qnamemin" class="xref">devries-qnamemin</a>]</span>, QNAME minimisation
1842 both increases the number of DNS lookups by up to 26% and leads to up to 5% more failed
1843 lookups. Filling the cache in a production resolver will soften that overhead.<a href="#section-5-2" class="pilcrow">¶</a></p>
1844 </section>
1845 </div>
1846 <section id="section-6">
1847 <h2 id="name-security-considerations">
1848 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
1849 </h2>
1850 <p id="section-6-1">QNAME minimisation's benefits are clear in the case where you want
1851 to decrease exposure of the queried name to the authoritative name server. But
1852 minimising the amount of data sent also, in part, addresses the case of a wire
1853 sniffer as well as the case of privacy invasion by the authoritative name
1854 servers. Encryption is of course a better defense against wire
1855 sniffers, but, unlike QNAME minimisation, it changes the protocol and
1856 cannot be deployed unilaterally. Also, the effect of QNAME
1857 minimisation on wire sniffers depends on whether the sniffer is on
1858 the DNS path.<a href="#section-6-1" class="pilcrow">¶</a></p>
1859 <p id="section-6-2">QNAME minimisation offers no protection against the recursive
1860 resolver, which still sees the full request coming from the stub
1861 resolver.<a href="#section-6-2" class="pilcrow">¶</a></p>
1862 <p id="section-6-3">A resolver using QNAME minimisation can possibly be used to cause
1863 a query storm to be sent to servers when resolving queries containing a QNAME
1864 with a large number of labels, as described in
1865 <a href="#number-of-queries" class="xref">Section 2.3</a>. That section proposes methods to
1866 significantly dampen the effects of such attacks.<a href="#section-6-3" class="pilcrow">¶</a></p>
1867 </section>
1868 <section id="section-7">
1869 <h2 id="name-references">
1870 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-references" class="section-name selfRef">References</a>
1871 </h2>
1872 <section id="section-7.1">
1873 <h3 id="name-normative-references">
1874 <a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
1875 </h3>
1876 <dl class="references">
1877 <dt id="RFC1034">[RFC1034]</dt>
1878 <dd>
1879 <span class="refAuthor">Mockapetris, P.</span>, <span class="refTitle">"Domain names - concepts and facilities"</span>, <span class="seriesInfo">STD 13</span>, <span class="seriesInfo">RFC 1034</span>, <span class="seriesInfo">DOI 10.17487/RFC1034</span>, <time datetime="1987-11" class="refDate">November 1987</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc1034">https://www.rfc-editor.org/info/rfc1034</a>&gt;</span>. </dd>
1880 <dd class="break"></dd>
1881 <dt id="RFC1035">[RFC1035]</dt>
1882 <dd>
1883 <span class="refAuthor">Mockapetris, P.</span>, <span class="refTitle">"Domain names - implementation and specification"</span>, <span class="seriesInfo">STD 13</span>, <span class="seriesInfo">RFC 1035</span>, <span class="seriesInfo">DOI 10.17487/RFC1035</span>, <time datetime="1987-11" class="refDate">November 1987</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc1035">https://www.rfc-editor.org/info/rfc1035</a>&gt;</span>. </dd>
1884 <dd class="break"></dd>
1885 <dt id="RFC2119">[RFC2119]</dt>
1886 <dd>
1887 <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
1888 <dd class="break"></dd>
1889 <dt id="RFC6973">[RFC6973]</dt>
1890 <dd>
1891 <span class="refAuthor">Cooper, A.</span>, <span class="refAuthor">Tschofenig, H.</span>, <span class="refAuthor">Aboba, B.</span>, <span class="refAuthor">Peterson, J.</span>, <span class="refAuthor">Morris, J.</span>, <span class="refAuthor">Hansen, M.</span>, and <span class="refAuthor">R. Smith</span>, <span class="refTitle">"Privacy Considerations for Internet Protocols"</span>, <span class="seriesInfo">RFC 6973</span>, <span class="seriesInfo">DOI 10.17487/RFC6973</span>, <time datetime="2013-07" class="refDate">July 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6973">https://www.rfc-editor.org/info/rfc6973</a>&gt;</span>. </dd>
1892 <dd class="break"></dd>
1893 <dt id="RFC8174">[RFC8174]</dt>
1894 <dd>
1895 <span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
1896 <dd class="break"></dd>
1897 <dt id="RFC8499">[RFC8499]</dt>
1898 <dd>
1899 <span class="refAuthor">Hoffman, P.</span>, <span class="refAuthor">Sullivan, A.</span>, and <span class="refAuthor">K. Fujiwara</span>, <span class="refTitle">"DNS Terminology"</span>, <span class="seriesInfo">BCP 219</span>, <span class="seriesInfo">RFC 8499</span>, <span class="seriesInfo">DOI 10.17487/RFC8499</span>, <time datetime="2019-01" class="refDate">January 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8499">https://www.rfc-editor.org/info/rfc8499</a>&gt;</span>. </dd>
1900 <dd class="break"></dd>
1901 </dl>
1902 </section>
1903 <section id="section-7.2">
1904 <h3 id="name-informative-references">
1905 <a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
1906 </h3>
1907 <dl class="references">
1908 <dt id="apnic-qnamemin">[apnic-qnamemin]</dt>
1909 <dd>
1910 <span class="refAuthor">Huston, G.</span> and <span class="refAuthor">J. Damas</span>, <span class="refTitle">"Measuring Query Name Minimization"</span>, <time datetime="2020-09" class="refDate">September 2020</time>, <span>&lt;<a href="https://indico.dns-oarc.net/event/34/contributions/787/attachments/777/1326/2020-09-28-oarc33-qname-minimisation.pdf">https://indico.dns-oarc.net/event/34/contributions/787/attachments/777/1326/2020-09-28-oarc33-qname-minimisation.pdf</a>&gt;</span>. </dd>
1911 <dd class="break"></dd>
1912 <dt id="devries-qnamemin">[devries-qnamemin]</dt>
1913 <dd>
1914 <span class="refAuthor">de Vries, W.</span>, <span class="refAuthor">Scheitle, Q.</span>, <span class="refAuthor">Müller, M.</span>, <span class="refAuthor">Toorop, W.</span>, <span class="refAuthor">Dolmans, R.</span>, and <span class="refAuthor">R. van Rijswijk-Deij</span>, <span class="refTitle">"A First Look at QNAME Minimization in the Domain Name System"</span>, <time datetime="2019-03" class="refDate">March 2019</time>, <span>&lt;<a href="https://nlnetlabs.nl/downloads/publications/devries2019.pdf">https://nlnetlabs.nl/downloads/publications/devries2019.pdf</a>&gt;</span>. </dd>
1915 <dd class="break"></dd>
1916 <dt id="dnsthought-qnamemin">[dnsthought-qnamemin]</dt>
1917 <dd>
1918 <span class="refTitle">"Qname Minimisation"</span>, <time datetime="2021-10" class="refDate">October 2021</time>, <span>&lt;<a href="https://dnsthought.nlnetlabs.nl/#qnamemin">https://dnsthought.nlnetlabs.nl/#qnamemin</a>&gt;</span>. </dd>
1919 <dd class="break"></dd>
1920 <dt id="Huque-QNAME-Min">[Huque-QNAME-Min]</dt>
1921 <dd>
1922 <span class="refAuthor">Huque, S.</span>, <span class="refTitle">"Query name minimization and authoritative server behavior"</span>, <time datetime="2015-05" class="refDate">May 2015</time>, <span>&lt;<a href="https://indico.dns-oarc.net/event/21/contribution/9">https://indico.dns-oarc.net/event/21/contribution/9</a>&gt;</span>. </dd>
1923 <dd class="break"></dd>
1924 <dt id="RFC2181">[RFC2181]</dt>
1925 <dd>
1926 <span class="refAuthor">Elz, R.</span> and <span class="refAuthor">R. Bush</span>, <span class="refTitle">"Clarifications to the DNS Specification"</span>, <span class="seriesInfo">RFC 2181</span>, <span class="seriesInfo">DOI 10.17487/RFC2181</span>, <time datetime="1997-07" class="refDate">July 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2181">https://www.rfc-editor.org/info/rfc2181</a>&gt;</span>. </dd>
1927 <dd class="break"></dd>
1928 <dt id="RFC6672">[RFC6672]</dt>
1929 <dd>
1930 <span class="refAuthor">Rose, S.</span> and <span class="refAuthor">W. Wijngaards</span>, <span class="refTitle">"DNAME Redirection in the DNS"</span>, <span class="seriesInfo">RFC 6672</span>, <span class="seriesInfo">DOI 10.17487/RFC6672</span>, <time datetime="2012-06" class="refDate">June 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6672">https://www.rfc-editor.org/info/rfc6672</a>&gt;</span>. </dd>
1931 <dd class="break"></dd>
1932 <dt id="RFC6895">[RFC6895]</dt>
1933 <dd>
1934 <span class="refAuthor">Eastlake 3rd, D.</span>, <span class="refTitle">"Domain Name System (DNS) IANA Considerations"</span>, <span class="seriesInfo">BCP 42</span>, <span class="seriesInfo">RFC 6895</span>, <span class="seriesInfo">DOI 10.17487/RFC6895</span>, <time datetime="2013-04" class="refDate">April 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6895">https://www.rfc-editor.org/info/rfc6895</a>&gt;</span>. </dd>
1935 <dd class="break"></dd>
1936 <dt id="RFC7816">[RFC7816]</dt>
1937 <dd>
1938 <span class="refAuthor">Bortzmeyer, S.</span>, <span class="refTitle">"DNS Query Name Minimisation to Improve Privacy"</span>, <span class="seriesInfo">RFC 7816</span>, <span class="seriesInfo">DOI 10.17487/RFC7816</span>, <time datetime="2016-03" class="refDate">March 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7816">https://www.rfc-editor.org/info/rfc7816</a>&gt;</span>. </dd>
1939 <dd class="break"></dd>
1940 <dt id="RFC8020">[RFC8020]</dt>
1941 <dd>
1942 <span class="refAuthor">Bortzmeyer, S.</span> and <span class="refAuthor">S. Huque</span>, <span class="refTitle">"NXDOMAIN: There Really Is Nothing Underneath"</span>, <span class="seriesInfo">RFC 8020</span>, <span class="seriesInfo">DOI 10.17487/RFC8020</span>, <time datetime="2016-11" class="refDate">November 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8020">https://www.rfc-editor.org/info/rfc8020</a>&gt;</span>. </dd>
1943 <dd class="break"></dd>
1944 <dt id="RFC8198">[RFC8198]</dt>
1945 <dd>
1946 <span class="refAuthor">Fujiwara, K.</span>, <span class="refAuthor">Kato, A.</span>, and <span class="refAuthor">W. Kumari</span>, <span class="refTitle">"Aggressive Use of DNSSEC-Validated Cache"</span>, <span class="seriesInfo">RFC 8198</span>, <span class="seriesInfo">DOI 10.17487/RFC8198</span>, <time datetime="2017-07" class="refDate">July 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8198">https://www.rfc-editor.org/info/rfc8198</a>&gt;</span>. </dd>
1947 <dd class="break"></dd>
1948 <dt id="RFC9076">[RFC9076]</dt>
1949 <dd>
1950 <span class="refAuthor">Wicinski, T., Ed.</span>, <span class="refTitle">"DNS Privacy Considerations"</span>, <span class="seriesInfo">RFC 9076</span>, <span class="seriesInfo">DOI 10.17487/RFC9076</span>, <time datetime="2021-07" class="refDate">July 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc9076">https://www.rfc-editor.org/info/rfc9076</a>&gt;</span>. </dd>
1951 <dd class="break"></dd>
1952 <dt id="verisign-qnamemin">[verisign-qnamemin]</dt>
1953 <dd>
1954 <span class="refAuthor">Thomas, M.</span>, <span class="refTitle">"Maximizing Qname Minimization: A New Chapter in DNS Protocol Evolution"</span>, <time datetime="2020-09" class="refDate">September 2020</time>, <span>&lt;<a href="https://blog.verisign.com/security/maximizing-qname-minimization-a-new-chapter-in-dns-protocol-evolution/">https://blog.verisign.com/security/maximizing-qname-minimization-a-new-chapter-in-dns-protocol-evolution/</a>&gt;</span>. </dd>
1955 <dd class="break"></dd>
1956 </dl>
1957 </section>
1958 </section>
1959 <section id="appendix-A">
1960 <h2 id="name-acknowledgments">
1961 <a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
1962 </h2>
1963 <p id="appendix-A-1">The acknowledgments from RFC 7816 apply here.
1964 In addition, many participants from the DNSOP Working Group helped
1965 with proposals for simplification, clarification, and general
1966 editorial help.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
1967 </section>
1968 <div id="authors-addresses">
1969 <section id="appendix-B">
1970 <h2 id="name-authors-addresses">
1971 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
1972 </h2>
1973 <address class="vcard">
1974 <div dir="auto" class="left"><span class="fn nameRole">Stephane Bortzmeyer</span></div>
1975 <div dir="auto" class="left"><span class="org">AFNIC</span></div>
1976 <div dir="auto" class="left"><span class="street-address">1, rue Stephenson</span></div>
1977 <div dir="auto" class="left">
1978 <span class="postal-code">78180</span> <span class="locality">Montigny-le-Bretonneux</span>
1979 </div>
1980 <div dir="auto" class="left"><span class="country-name">France</span></div>
1981 <div class="tel">
1982 <span>Phone:</span>
1983 <a href="tel:+33%201%2039%2030%2083%2046" class="tel">+33 1 39 30 83 46</a>
1984 </div>
1985 <div class="email">
1986 <span>Email:</span>
1987 <a href="mailto:[email protected]" class="email">[email protected]</a>
1988 </div>
1989 <div class="url">
1990 <span>URI:</span>
1991 <a href="https://www.afnic.fr/" class="url">https://www.afnic.fr/</a>
1992 </div>
1993 </address>
1994 <address class="vcard">
1995 <div dir="auto" class="left"><span class="fn nameRole">Ralph Dolmans</span></div>
1996 <div dir="auto" class="left"><span class="org">NLnet Labs</span></div>
1997 <div class="email">
1998 <span>Email:</span>
1999 <a href="mailto:[email protected]" class="email">[email protected]</a>
2000 </div>
2001 </address>
2002 <address class="vcard">
2003 <div dir="auto" class="left"><span class="fn nameRole">Paul Hoffman</span></div>
2004 <div dir="auto" class="left"><span class="org">ICANN</span></div>
2005 <div class="email">
2006 <span>Email:</span>
2007 <a href="mailto:[email protected]" class="email">[email protected]</a>
2008 </div>
2009 </address>
2010 </section>
2011 </div>
2012 <script>const toc = document.getElementById("toc");
2013 toc.querySelector("h2").addEventListener("click", e => {
2014 toc.classList.toggle("active");
2015 });
2016 toc.querySelector("nav").addEventListener("click", e => {
2017 toc.classList.remove("active");
2018 });
2019 </script>
2020 </body>
2021 </html>