Debian Codegraph @

rfc9109.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 9109: Network Time Protocol Version 4: Port Randomization</title>
8 <meta content="Fernando Gont" name="author">
9 <meta content="Guillermo Gont" name="author">
10 <meta content="Miroslav Lichvar" name="author">
11 <meta content="
12
13 The Network Time Protocol (NTP) can operate in several modes. Some of these
14 modes are based on the receipt of unsolicited packets and therefore
15 require the use of a well-known port as the local port. However, in
16 the case of NTP modes where the use of a well-known port is not required,
17 employing such a well-known port unnecessarily facilitates the ability of
18 attackers to perform blind/off-path attacks. This document formally
19 updates RFC 5905, recommending the use of transport-protocol ephemeral port
20 randomization for those modes where use of the NTP well-known port is not
21 required.
22 " name="description">
23 <meta content="xml2rfc 3.9.1" name="generator">
24 <meta content="security" name="keyword">
25 <meta content="transport protocols" name="keyword">
26 <meta content="9109" name="rfc.number">
27 <!-- Generator version information:
28 xml2rfc 3.9.1
29 Python 3.6.10
30 appdirs 1.4.4
31 ConfigArgParse 1.2.3
32 google-i18n-address 2.3.5
33 html5lib 1.0.1
34 intervaltree 3.0.2
35 Jinja2 2.11.2
36 kitchen 1.2.6
37 lxml 4.4.2
38 pycairo 1.19.0
39 pycountry 19.8.18
40 pyflakes 2.1.1
41 PyYAML 5.3.1
42 requests 2.22.0
43 setuptools 40.6.2
44 six 1.14.0
45 WeasyPrint 51
46 -->
47 <link href="rfc9109.xml" rel="alternate" type="application/rfc+xml">
48 <link href="#copyright" rel="license">
49 <style type="text/css">/*
50
51 NOTE: Changes at the bottom of this file overrides some earlier settings.
52
53 Once the style has stabilized and has been adopted as an official RFC style,
54 this can be consolidated so that style settings occur only in one place, but
55 for now the contents of this file consists first of the initial CSS work as
56 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
57 commented changes found necssary during the development of the v3
58 formatters.
59
60 */
61
62 /* fonts */
63 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
64 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
65 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
66
67 @viewport {
68 zoom: 1.0;
69 width: extend-to-zoom;
70 }
71 @-ms-viewport {
72 width: extend-to-zoom;
73 zoom: 1.0;
74 }
75 /* general and mobile first */
76 html {
77 }
78 body {
79 max-width: 90%;
80 margin: 1.5em auto;
81 color: #222;
82 background-color: #fff;
83 font-size: 14px;
84 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
85 line-height: 1.6;
86 scroll-behavior: smooth;
87 }
88 .ears {
89 display: none;
90 }
91
92 /* headings */
93 #title, h1, h2, h3, h4, h5, h6 {
94 margin: 1em 0 0.5em;
95 font-weight: bold;
96 line-height: 1.3;
97 }
98 #title {
99 clear: both;
100 border-bottom: 1px solid #ddd;
101 margin: 0 0 0.5em 0;
102 padding: 1em 0 0.5em;
103 }
104 .author {
105 padding-bottom: 4px;
106 }
107 h1 {
108 font-size: 26px;
109 margin: 1em 0;
110 }
111 h2 {
112 font-size: 22px;
113 margin-top: -20px; /* provide offset for in-page anchors */
114 padding-top: 33px;
115 }
116 h3 {
117 font-size: 18px;
118 margin-top: -36px; /* provide offset for in-page anchors */
119 padding-top: 42px;
120 }
121 h4 {
122 font-size: 16px;
123 margin-top: -36px; /* provide offset for in-page anchors */
124 padding-top: 42px;
125 }
126 h5, h6 {
127 font-size: 14px;
128 }
129 #n-copyright-notice {
130 border-bottom: 1px solid #ddd;
131 padding-bottom: 1em;
132 margin-bottom: 1em;
133 }
134 /* general structure */
135 p {
136 padding: 0;
137 margin: 0 0 1em 0;
138 text-align: left;
139 }
140 div, span {
141 position: relative;
142 }
143 div {
144 margin: 0;
145 }
146 .alignRight.art-text {
147 background-color: #f9f9f9;
148 border: 1px solid #eee;
149 border-radius: 3px;
150 padding: 1em 1em 0;
151 margin-bottom: 1.5em;
152 }
153 .alignRight.art-text pre {
154 padding: 0;
155 }
156 .alignRight {
157 margin: 1em 0;
158 }
159 .alignRight > *:first-child {
160 border: none;
161 margin: 0;
162 float: right;
163 clear: both;
164 }
165 .alignRight > *:nth-child(2) {
166 clear: both;
167 display: block;
168 border: none;
169 }
170 svg {
171 display: block;
172 }
173 .alignCenter.art-text {
174 background-color: #f9f9f9;
175 border: 1px solid #eee;
176 border-radius: 3px;
177 padding: 1em 1em 0;
178 margin-bottom: 1.5em;
179 }
180 .alignCenter.art-text pre {
181 padding: 0;
182 }
183 .alignCenter {
184 margin: 1em 0;
185 }
186 .alignCenter > *:first-child {
187 border: none;
188 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
189 support flexbox yet.
190 */
191 display: table;
192 margin: 0 auto;
193 }
194
195 /* lists */
196 ol, ul {
197 padding: 0;
198 margin: 0 0 1em 2em;
199 }
200 ol ol, ul ul, ol ul, ul ol {
201 margin-left: 1em;
202 }
203 li {
204 margin: 0 0 0.25em 0;
205 }
206 .ulCompact li {
207 margin: 0;
208 }
209 ul.empty, .ulEmpty {
210 list-style-type: none;
211 }
212 ul.empty li, .ulEmpty li {
213 margin-top: 0.5em;
214 }
215 ul.ulBare, li.ulBare {
216 margin-left: 0em !important;
217 }
218 ul.compact, .ulCompact,
219 ol.compact, .olCompact {
220 line-height: 100%;
221 margin: 0 0 0 2em;
222 }
223
224 /* definition lists */
225 dl {
226 }
227 dl > dt {
228 float: left;
229 margin-right: 1em;
230 }
231 /*
232 dl.nohang > dt {
233 float: none;
234 }
235 */
236 dl > dd {
237 margin-bottom: .8em;
238 min-height: 1.3em;
239 }
240 dl.compact > dd, .dlCompact > dd {
241 margin-bottom: 0em;
242 }
243 dl > dd > dl {
244 margin-top: 0.5em;
245 margin-bottom: 0em;
246 }
247
248 /* links */
249 a {
250 text-decoration: none;
251 }
252 a[href] {
253 color: #22e; /* Arlen: WCAG 2019 */
254 }
255 a[href]:hover {
256 background-color: #f2f2f2;
257 }
258 figcaption a[href],
259 a[href].selfRef {
260 color: #222;
261 }
262 /* XXX probably not this:
263 a.selfRef:hover {
264 background-color: transparent;
265 cursor: default;
266 } */
267
268 /* Figures */
269 tt, code, pre, code {
270 background-color: #f9f9f9;
271 font-family: 'Roboto Mono', monospace;
272 }
273 pre {
274 border: 1px solid #eee;
275 margin: 0;
276 padding: 1em;
277 }
278 img {
279 max-width: 100%;
280 }
281 figure {
282 margin: 0;
283 }
284 figure blockquote {
285 margin: 0.8em 0.4em 0.4em;
286 }
287 figcaption {
288 font-style: italic;
289 margin: 0 0 1em 0;
290 }
291 @media screen {
292 pre {
293 overflow-x: auto;
294 max-width: 100%;
295 max-width: calc(100% - 22px);
296 }
297 }
298
299 /* aside, blockquote */
300 aside, blockquote {
301 margin-left: 0;
302 padding: 1.2em 2em;
303 }
304 blockquote {
305 background-color: #f9f9f9;
306 color: #111; /* Arlen: WCAG 2019 */
307 border: 1px solid #ddd;
308 border-radius: 3px;
309 margin: 1em 0;
310 }
311 cite {
312 display: block;
313 text-align: right;
314 font-style: italic;
315 }
316
317 /* tables */
318 table {
319 width: 100%;
320 margin: 0 0 1em;
321 border-collapse: collapse;
322 border: 1px solid #eee;
323 }
324 th, td {
325 text-align: left;
326 vertical-align: top;
327 padding: 0.5em 0.75em;
328 }
329 th {
330 text-align: left;
331 background-color: #e9e9e9;
332 }
333 tr:nth-child(2n+1) > td {
334 background-color: #f5f5f5;
335 }
336 table caption {
337 font-style: italic;
338 margin: 0;
339 padding: 0;
340 text-align: left;
341 }
342 table p {
343 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
344 be allowed within tables more generally, it would be far better to select on a class. */
345 margin: 0;
346 }
347
348 /* pilcrow */
349 a.pilcrow {
350 color: #666; /* Arlen: AHDJ 2019 */
351 text-decoration: none;
352 visibility: hidden;
353 user-select: none;
354 -ms-user-select: none;
355 -o-user-select:none;
356 -moz-user-select: none;
357 -khtml-user-select: none;
358 -webkit-user-select: none;
359 -webkit-touch-callout: none;
360 }
361 @media screen {
362 aside:hover > a.pilcrow,
363 p:hover > a.pilcrow,
364 blockquote:hover > a.pilcrow,
365 div:hover > a.pilcrow,
366 li:hover > a.pilcrow,
367 pre:hover > a.pilcrow {
368 visibility: visible;
369 }
370 a.pilcrow:hover {
371 background-color: transparent;
372 }
373 }
374
375 /* misc */
376 hr {
377 border: 0;
378 border-top: 1px solid #eee;
379 }
380 .bcp14 {
381 font-variant: small-caps;
382 }
383
384 .role {
385 font-variant: all-small-caps;
386 }
387
388 /* info block */
389 #identifiers {
390 margin: 0;
391 font-size: 0.9em;
392 }
393 #identifiers dt {
394 width: 3em;
395 clear: left;
396 }
397 #identifiers dd {
398 float: left;
399 margin-bottom: 0;
400 }
401 #identifiers .authors .author {
402 display: inline-block;
403 margin-right: 1.5em;
404 }
405 #identifiers .authors .org {
406 font-style: italic;
407 }
408
409 /* The prepared/rendered info at the very bottom of the page */
410 .docInfo {
411 color: #666; /* Arlen: WCAG 2019 */
412 font-size: 0.9em;
413 font-style: italic;
414 margin-top: 2em;
415 }
416 .docInfo .prepared {
417 float: left;
418 }
419 .docInfo .prepared {
420 float: right;
421 }
422
423 /* table of contents */
424 #toc {
425 padding: 0.75em 0 2em 0;
426 margin-bottom: 1em;
427 }
428 nav.toc ul {
429 margin: 0 0.5em 0 0;
430 padding: 0;
431 list-style: none;
432 }
433 nav.toc li {
434 line-height: 1.3em;
435 margin: 0.75em 0;
436 padding-left: 1.2em;
437 text-indent: -1.2em;
438 }
439 /* references */
440 .references dt {
441 text-align: right;
442 font-weight: bold;
443 min-width: 7em;
444 }
445 .references dd {
446 margin-left: 8em;
447 overflow: auto;
448 }
449
450 .refInstance {
451 margin-bottom: 1.25em;
452 }
453
454 .references .ascii {
455 margin-bottom: 0.25em;
456 }
457
458 /* index */
459 .index ul {
460 margin: 0 0 0 1em;
461 padding: 0;
462 list-style: none;
463 }
464 .index ul ul {
465 margin: 0;
466 }
467 .index li {
468 margin: 0;
469 text-indent: -2em;
470 padding-left: 2em;
471 padding-bottom: 5px;
472 }
473 .indexIndex {
474 margin: 0.5em 0 1em;
475 }
476 .index a {
477 font-weight: 700;
478 }
479 /* make the index two-column on all but the smallest screens */
480 @media (min-width: 600px) {
481 .index ul {
482 -moz-column-count: 2;
483 -moz-column-gap: 20px;
484 }
485 .index ul ul {
486 -moz-column-count: 1;
487 -moz-column-gap: 0;
488 }
489 }
490
491 /* authors */
492 address.vcard {
493 font-style: normal;
494 margin: 1em 0;
495 }
496
497 address.vcard .nameRole {
498 font-weight: 700;
499 margin-left: 0;
500 }
501 address.vcard .label {
502 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
503 margin: 0.5em 0;
504 }
505 address.vcard .type {
506 display: none;
507 }
508 .alternative-contact {
509 margin: 1.5em 0 1em;
510 }
511 hr.addr {
512 border-top: 1px dashed;
513 margin: 0;
514 color: #ddd;
515 max-width: calc(100% - 16px);
516 }
517
518 /* temporary notes */
519 .rfcEditorRemove::before {
520 position: absolute;
521 top: 0.2em;
522 right: 0.2em;
523 padding: 0.2em;
524 content: "The RFC Editor will remove this note";
525 color: #9e2a00; /* Arlen: WCAG 2019 */
526 background-color: #ffd; /* Arlen: WCAG 2019 */
527 }
528 .rfcEditorRemove {
529 position: relative;
530 padding-top: 1.8em;
531 background-color: #ffd; /* Arlen: WCAG 2019 */
532 border-radius: 3px;
533 }
534 .cref {
535 background-color: #ffd; /* Arlen: WCAG 2019 */
536 padding: 2px 4px;
537 }
538 .crefSource {
539 font-style: italic;
540 }
541 /* alternative layout for smaller screens */
542 @media screen and (max-width: 1023px) {
543 body {
544 padding-top: 2em;
545 }
546 #title {
547 padding: 1em 0;
548 }
549 h1 {
550 font-size: 24px;
551 }
552 h2 {
553 font-size: 20px;
554 margin-top: -18px; /* provide offset for in-page anchors */
555 padding-top: 38px;
556 }
557 #identifiers dd {
558 max-width: 60%;
559 }
560 #toc {
561 position: fixed;
562 z-index: 2;
563 top: 0;
564 right: 0;
565 padding: 0;
566 margin: 0;
567 background-color: inherit;
568 border-bottom: 1px solid #ccc;
569 }
570 #toc h2 {
571 margin: -1px 0 0 0;
572 padding: 4px 0 4px 6px;
573 padding-right: 1em;
574 min-width: 190px;
575 font-size: 1.1em;
576 text-align: right;
577 background-color: #444;
578 color: white;
579 cursor: pointer;
580 }
581 #toc h2::before { /* css hamburger */
582 float: right;
583 position: relative;
584 width: 1em;
585 height: 1px;
586 left: -164px;
587 margin: 6px 0 0 0;
588 background: white none repeat scroll 0 0;
589 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
590 content: "";
591 }
592 #toc nav {
593 display: none;
594 padding: 0.5em 1em 1em;
595 overflow: auto;
596 height: calc(100vh - 48px);
597 border-left: 1px solid #ddd;
598 }
599 }
600
601 /* alternative layout for wide screens */
602 @media screen and (min-width: 1024px) {
603 body {
604 max-width: 724px;
605 margin: 42px auto;
606 padding-left: 1.5em;
607 padding-right: 29em;
608 }
609 #toc {
610 position: fixed;
611 top: 42px;
612 right: 42px;
613 width: 25%;
614 margin: 0;
615 padding: 0 1em;
616 z-index: 1;
617 }
618 #toc h2 {
619 border-top: none;
620 border-bottom: 1px solid #ddd;
621 font-size: 1em;
622 font-weight: normal;
623 margin: 0;
624 padding: 0.25em 1em 1em 0;
625 }
626 #toc nav {
627 display: block;
628 height: calc(90vh - 84px);
629 bottom: 0;
630 padding: 0.5em 0 0;
631 overflow: auto;
632 }
633 img { /* future proofing */
634 max-width: 100%;
635 height: auto;
636 }
637 }
638
639 /* pagination */
640 @media print {
641 body {
642
643 width: 100%;
644 }
645 p {
646 orphans: 3;
647 widows: 3;
648 }
649 #n-copyright-notice {
650 border-bottom: none;
651 }
652 #toc, #n-introduction {
653 page-break-before: always;
654 }
655 #toc {
656 border-top: none;
657 padding-top: 0;
658 }
659 figure, pre {
660 page-break-inside: avoid;
661 }
662 figure {
663 overflow: scroll;
664 }
665 h1, h2, h3, h4, h5, h6 {
666 page-break-after: avoid;
667 }
668 h2+*, h3+*, h4+*, h5+*, h6+* {
669 page-break-before: avoid;
670 }
671 pre {
672 white-space: pre-wrap;
673 word-wrap: break-word;
674 font-size: 10pt;
675 }
676 table {
677 border: 1px solid #ddd;
678 }
679 td {
680 border-top: 1px solid #ddd;
681 }
682 }
683
684 /* This is commented out here, as the string-set: doesn't
685 pass W3C validation currently */
686 /*
687 .ears thead .left {
688 string-set: ears-top-left content();
689 }
690
691 .ears thead .center {
692 string-set: ears-top-center content();
693 }
694
695 .ears thead .right {
696 string-set: ears-top-right content();
697 }
698
699 .ears tfoot .left {
700 string-set: ears-bottom-left content();
701 }
702
703 .ears tfoot .center {
704 string-set: ears-bottom-center content();
705 }
706
707 .ears tfoot .right {
708 string-set: ears-bottom-right content();
709 }
710 */
711
712 @page :first {
713 padding-top: 0;
714 @top-left {
715 content: normal;
716 border: none;
717 }
718 @top-center {
719 content: normal;
720 border: none;
721 }
722 @top-right {
723 content: normal;
724 border: none;
725 }
726 }
727
728 @page {
729 size: A4;
730 margin-bottom: 45mm;
731 padding-top: 20px;
732 /* The follwing is commented out here, but set appropriately by in code, as
733 the content depends on the document */
734 /*
735 @top-left {
736 content: 'Internet-Draft';
737 vertical-align: bottom;
738 border-bottom: solid 1px #ccc;
739 }
740 @top-left {
741 content: string(ears-top-left);
742 vertical-align: bottom;
743 border-bottom: solid 1px #ccc;
744 }
745 @top-center {
746 content: string(ears-top-center);
747 vertical-align: bottom;
748 border-bottom: solid 1px #ccc;
749 }
750 @top-right {
751 content: string(ears-top-right);
752 vertical-align: bottom;
753 border-bottom: solid 1px #ccc;
754 }
755 @bottom-left {
756 content: string(ears-bottom-left);
757 vertical-align: top;
758 border-top: solid 1px #ccc;
759 }
760 @bottom-center {
761 content: string(ears-bottom-center);
762 vertical-align: top;
763 border-top: solid 1px #ccc;
764 }
765 @bottom-right {
766 content: '[Page ' counter(page) ']';
767 vertical-align: top;
768 border-top: solid 1px #ccc;
769 }
770 */
771
772 }
773
774 /* Changes introduced to fix issues found during implementation */
775 /* Make sure links are clickable even if overlapped by following H* */
776 a {
777 z-index: 2;
778 }
779 /* Separate body from document info even without intervening H1 */
780 section {
781 clear: both;
782 }
783
784
785 /* Top align author divs, to avoid names without organization dropping level with org names */
786 .author {
787 vertical-align: top;
788 }
789
790 /* Leave room in document info to show Internet-Draft on one line */
791 #identifiers dt {
792 width: 8em;
793 }
794
795 /* Don't waste quite as much whitespace between label and value in doc info */
796 #identifiers dd {
797 margin-left: 1em;
798 }
799
800 /* Give floating toc a background color (needed when it's a div inside section */
801 #toc {
802 background-color: white;
803 }
804
805 /* Make the collapsed ToC header render white on gray also when it's a link */
806 @media screen and (max-width: 1023px) {
807 #toc h2 a,
808 #toc h2 a:link,
809 #toc h2 a:focus,
810 #toc h2 a:hover,
811 #toc a.toplink,
812 #toc a.toplink:hover {
813 color: white;
814 background-color: #444;
815 text-decoration: none;
816 }
817 }
818
819 /* Give the bottom of the ToC some whitespace */
820 @media screen and (min-width: 1024px) {
821 #toc {
822 padding: 0 0 1em 1em;
823 }
824 }
825
826 /* Style section numbers with more space between number and title */
827 .section-number {
828 padding-right: 0.5em;
829 }
830
831 /* prevent monospace from becoming overly large */
832 tt, code, pre, code {
833 font-size: 95%;
834 }
835
836 /* Fix the height/width aspect for ascii art*/
837 pre.sourcecode,
838 .art-text pre {
839 line-height: 1.12;
840 }
841
842
843 /* Add styling for a link in the ToC that points to the top of the document */
844 a.toplink {
845 float: right;
846 margin-right: 0.5em;
847 }
848
849 /* Fix the dl styling to match the RFC 7992 attributes */
850 dl > dt,
851 dl.dlParallel > dt {
852 float: left;
853 margin-right: 1em;
854 }
855 dl.dlNewline > dt {
856 float: none;
857 }
858
859 /* Provide styling for table cell text alignment */
860 table td.text-left,
861 table th.text-left {
862 text-align: left;
863 }
864 table td.text-center,
865 table th.text-center {
866 text-align: center;
867 }
868 table td.text-right,
869 table th.text-right {
870 text-align: right;
871 }
872
873 /* Make the alternative author contact informatio look less like just another
874 author, and group it closer with the primary author contact information */
875 .alternative-contact {
876 margin: 0.5em 0 0.25em 0;
877 }
878 address .non-ascii {
879 margin: 0 0 0 2em;
880 }
881
882 /* With it being possible to set tables with alignment
883 left, center, and right, { width: 100%; } does not make sense */
884 table {
885 width: auto;
886 }
887
888 /* Avoid reference text that sits in a block with very wide left margin,
889 because of a long floating dt label.*/
890 .references dd {
891 overflow: visible;
892 }
893
894 /* Control caption placement */
895 caption {
896 caption-side: bottom;
897 }
898
899 /* Limit the width of the author address vcard, so names in right-to-left
900 script don't end up on the other side of the page. */
901
902 address.vcard {
903 max-width: 30em;
904 margin-right: auto;
905 }
906
907 /* For address alignment dependent on LTR or RTL scripts */
908 address div.left {
909 text-align: left;
910 }
911 address div.right {
912 text-align: right;
913 }
914
915 /* Provide table alignment support. We can't use the alignX classes above
916 since they do unwanted things with caption and other styling. */
917 table.right {
918 margin-left: auto;
919 margin-right: 0;
920 }
921 table.center {
922 margin-left: auto;
923 margin-right: auto;
924 }
925 table.left {
926 margin-left: 0;
927 margin-right: auto;
928 }
929
930 /* Give the table caption label the same styling as the figcaption */
931 caption a[href] {
932 color: #222;
933 }
934
935 @media print {
936 .toplink {
937 display: none;
938 }
939
940 /* avoid overwriting the top border line with the ToC header */
941 #toc {
942 padding-top: 1px;
943 }
944
945 /* Avoid page breaks inside dl and author address entries */
946 .vcard {
947 page-break-inside: avoid;
948 }
949
950 }
951 /* Tweak the bcp14 keyword presentation */
952 .bcp14 {
953 font-variant: small-caps;
954 font-weight: bold;
955 font-size: 0.9em;
956 }
957 /* Tweak the invisible space above H* in order not to overlay links in text above */
958 h2 {
959 margin-top: -18px; /* provide offset for in-page anchors */
960 padding-top: 31px;
961 }
962 h3 {
963 margin-top: -18px; /* provide offset for in-page anchors */
964 padding-top: 24px;
965 }
966 h4 {
967 margin-top: -18px; /* provide offset for in-page anchors */
968 padding-top: 24px;
969 }
970 /* Float artwork pilcrow to the right */
971 @media screen {
972 .artwork a.pilcrow {
973 display: block;
974 line-height: 0.7;
975 margin-top: 0.15em;
976 }
977 }
978 /* Make pilcrows on dd visible */
979 @media screen {
980 dd:hover > a.pilcrow {
981 visibility: visible;
982 }
983 }
984 /* Make the placement of figcaption match that of a table's caption
985 by removing the figure's added bottom margin */
986 .alignLeft.art-text,
987 .alignCenter.art-text,
988 .alignRight.art-text {
989 margin-bottom: 0;
990 }
991 .alignLeft,
992 .alignCenter,
993 .alignRight {
994 margin: 1em 0 0 0;
995 }
996 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
997 possibly even requiring a new line */
998 @media print {
999 a.pilcrow {
1000 display: none;
1001 }
1002 }
1003 /* Styling for the external metadata */
1004 div#external-metadata {
1005 background-color: #eee;
1006 padding: 0.5em;
1007 margin-bottom: 0.5em;
1008 display: none;
1009 }
1010 div#internal-metadata {
1011 padding: 0.5em; /* to match the external-metadata padding */
1012 }
1013 /* Styling for title RFC Number */
1014 h1#rfcnum {
1015 clear: both;
1016 margin: 0 0 -1em;
1017 padding: 1em 0 0 0;
1018 }
1019 /* Make .olPercent look the same as <ol><li> */
1020 dl.olPercent > dd {
1021 margin-bottom: 0.25em;
1022 min-height: initial;
1023 }
1024 /* Give aside some styling to set it apart */
1025 aside {
1026 border-left: 1px solid #ddd;
1027 margin: 1em 0 1em 2em;
1028 padding: 0.2em 2em;
1029 }
1030 aside > dl,
1031 aside > ol,
1032 aside > ul,
1033 aside > table,
1034 aside > p {
1035 margin-bottom: 0.5em;
1036 }
1037 /* Additional page break settings */
1038 @media print {
1039 figcaption, table caption {
1040 page-break-before: avoid;
1041 }
1042 }
1043 /* Font size adjustments for print */
1044 @media print {
1045 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1046 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1047 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1048 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1049 h4 { font-size: 1em; padding-top: 1.5em; }
1050 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1051 }
1052 /* Sourcecode margin in print, when there's no pilcrow */
1053 @media print {
1054 .artwork,
1055 .sourcecode {
1056 margin-bottom: 1em;
1057 }
1058 }
1059 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1060 table {
1061 min-width: 20em;
1062 }
1063 /* ol type a */
1064 ol.type-a { list-style-type: lower-alpha; }
1065 ol.type-A { list-style-type: upper-alpha; }
1066 ol.type-i { list-style-type: lower-roman; }
1067 ol.type-I { list-style-type: lower-roman; }
1068 /* Apply the print table and row borders in general, on request from the RPC,
1069 and increase the contrast between border and odd row background sligthtly */
1070 table {
1071 border: 1px solid #ddd;
1072 }
1073 td {
1074 border-top: 1px solid #ddd;
1075 }
1076 tr:nth-child(2n+1) > td {
1077 background-color: #f8f8f8;
1078 }
1079 /* Use style rules to govern display of the TOC. */
1080 @media screen and (max-width: 1023px) {
1081 #toc nav { display: none; }
1082 #toc.active nav { display: block; }
1083 }
1084 /* Add support for keepWithNext */
1085 .keepWithNext {
1086 break-after: avoid-page;
1087 break-after: avoid-page;
1088 }
1089 /* Add support for keepWithPrevious */
1090 .keepWithPrevious {
1091 break-before: avoid-page;
1092 }
1093 /* Change the approach to avoiding breaks inside artwork etc. */
1094 figure, pre, table, .artwork, .sourcecode {
1095 break-before: avoid-page;
1096 break-after: auto;
1097 }
1098 /* Avoid breaks between <dt> and <dd> */
1099 dl {
1100 break-before: auto;
1101 break-inside: auto;
1102 }
1103 dt {
1104 break-before: auto;
1105 break-after: avoid-page;
1106 }
1107 dd {
1108 break-before: avoid-page;
1109 break-after: auto;
1110 orphans: 3;
1111 widows: 3
1112 }
1113 span.break, dd.break {
1114 margin-bottom: 0;
1115 min-height: 0;
1116 break-before: auto;
1117 break-inside: auto;
1118 break-after: auto;
1119 }
1120 /* Undo break-before ToC */
1121 @media print {
1122 #toc {
1123 break-before: auto;
1124 }
1125 }
1126 /* Text in compact lists should not get extra bottim margin space,
1127 since that would makes the list not compact */
1128 ul.compact p, .ulCompact p,
1129 ol.compact p, .olCompact p {
1130 margin: 0;
1131 }
1132 /* But the list as a whole needs the extra space at the end */
1133 section ul.compact,
1134 section .ulCompact,
1135 section ol.compact,
1136 section .olCompact {
1137 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1138 }
1139 /* The tt and code background above interferes with for instance table cell
1140 backgrounds. Changed to something a bit more selective. */
1141 tt, code {
1142 background-color: transparent;
1143 }
1144 p tt, p code, li tt, li code {
1145 background-color: #f8f8f8;
1146 }
1147 /* Tweak the pre margin -- 0px doesn't come out well */
1148 pre {
1149 margin-top: 0.5px;
1150 }
1151 /* Tweak the comact list text */
1152 ul.compact, .ulCompact,
1153 ol.compact, .olCompact,
1154 dl.compact, .dlCompact {
1155 line-height: normal;
1156 }
1157 /* Don't add top margin for nested lists */
1158 li > ul, li > ol, li > dl,
1159 dd > ul, dd > ol, dd > dl,
1160 dl > dd > dl {
1161 margin-top: initial;
1162 }
1163 /* Elements that should not be rendered on the same line as a <dt> */
1164 /* This should match the element list in writer.text.TextWriter.render_dl() */
1165 dd > div.artwork:first-child,
1166 dd > aside:first-child,
1167 dd > figure:first-child,
1168 dd > ol:first-child,
1169 dd > div:first-child > pre.sourcecode,
1170 dd > table:first-child,
1171 dd > ul:first-child {
1172 clear: left;
1173 }
1174 /* fix for weird browser behaviour when <dd/> is empty */
1175 dt+dd:empty::before{
1176 content: "\00a0";
1177 }
1178 /* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
1179 li > p {
1180 margin-bottom: 0.5em
1181 }
1182 /* Don't let p margin spill out from inside list items */
1183 li > p:last-of-type {
1184 margin-bottom: 0;
1185 }
1186 </style>
1187 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1188 <link href="https://dx.doi.org/10.17487/rfc9109" rel="alternate">
1189 <link href="urn:issn:2070-1721" rel="alternate">
1190 <link href="https://datatracker.ietf.org/doc/draft-ietf-ntp-port-randomization-08" rel="prev">
1191 </head>
1192 <body>
1193 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1194 <table class="ears">
1195 <thead><tr>
1196 <td class="left">RFC 9109</td>
1197 <td class="center">NTP Port Randomization</td>
1198 <td class="right">August 2021</td>
1199 </tr></thead>
1200 <tfoot><tr>
1201 <td class="left">Gont, et al.</td>
1202 <td class="center">Standards Track</td>
1203 <td class="right">[Page]</td>
1204 </tr></tfoot>
1205 </table>
1206 <div id="external-metadata" class="document-information"></div>
1207 <div id="internal-metadata" class="document-information">
1208 <dl id="identifiers">
1209 <dt class="label-stream">Stream:</dt>
1210 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1211 <dt class="label-rfc">RFC:</dt>
1212 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9109" class="eref">9109</a></dd>
1213 <dt class="label-updates">Updates:</dt>
1214 <dd class="updates">
1215 <a href="https://www.rfc-editor.org/rfc/rfc5905" class="eref">5905</a> </dd>
1216 <dt class="label-category">Category:</dt>
1217 <dd class="category">Standards Track</dd>
1218 <dt class="label-published">Published:</dt>
1219 <dd class="published">
1220 <time datetime="2021-08" class="published">August 2021</time>
1221 </dd>
1222 <dt class="label-issn">ISSN:</dt>
1223 <dd class="issn">2070-1721</dd>
1224 <dt class="label-authors">Authors:</dt>
1225 <dd class="authors">
1226 <div class="author">
1227 <div class="author-name">F. Gont</div>
1228 <div class="org">SI6 Networks</div>
1229 </div>
1230 <div class="author">
1231 <div class="author-name">G. Gont</div>
1232 <div class="org">SI6 Networks</div>
1233 </div>
1234 <div class="author">
1235 <div class="author-name">M. Lichvar</div>
1236 <div class="org">Red Hat</div>
1237 </div>
1238 </dd>
1239 </dl>
1240 </div>
1241 <h1 id="rfcnum">RFC 9109</h1>
1242 <h1 id="title">Network Time Protocol Version 4: Port Randomization</h1>
1243 <section id="section-abstract">
1244 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1245 <p id="section-abstract-1">
1246 The Network Time Protocol (NTP) can operate in several modes. Some of these
1247 modes are based on the receipt of unsolicited packets and therefore
1248 require the use of a well-known port as the local port. However, in
1249 the case of NTP modes where the use of a well-known port is not required,
1250 employing such a well-known port unnecessarily facilitates the ability of
1251 attackers to perform blind/off-path attacks. This document formally
1252 updates RFC 5905, recommending the use of transport-protocol ephemeral port
1253 randomization for those modes where use of the NTP well-known port is not
1254 required.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1255 </section>
1256 <div id="status-of-memo">
1257 <section id="section-boilerplate.1">
1258 <h2 id="name-status-of-this-memo">
1259 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1260 </h2>
1261 <p id="section-boilerplate.1-1">
1262 This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1263 <p id="section-boilerplate.1-2">
1264 This document is a product of the Internet Engineering Task Force
1265 (IETF). It represents the consensus of the IETF community. It has
1266 received public review and has been approved for publication by
1267 the Internet Engineering Steering Group (IESG). Further
1268 information on Internet Standards is available in Section 2 of
1269 RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1270 <p id="section-boilerplate.1-3">
1271 Information about the current status of this document, any
1272 errata, and how to provide feedback on it may be obtained at
1273 <span><a href="https://www.rfc-editor.org/info/rfc9109">https://www.rfc-editor.org/info/rfc9109</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1274 </section>
1275 </div>
1276 <div id="copyright">
1277 <section id="section-boilerplate.2">
1278 <h2 id="name-copyright-notice">
1279 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1280 </h2>
1281 <p id="section-boilerplate.2-1">
1282 Copyright (c) 2021 IETF Trust and the persons identified as the
1283 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1284 <p id="section-boilerplate.2-2">
1285 This document is subject to BCP 78 and the IETF Trust's Legal
1286 Provisions Relating to IETF Documents
1287 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1288 publication of this document. Please review these documents
1289 carefully, as they describe your rights and restrictions with
1290 respect to this document. Code Components extracted from this
1291 document must include Simplified BSD License text as described in
1292 Section 4.e of the Trust Legal Provisions and are provided without
1293 warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1294 </section>
1295 </div>
1296 <div id="toc">
1297 <section id="section-toc.1">
1298 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1299 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1300 </h2>
1301 <nav class="toc"><ul class="ulBare toc ulEmpty compact">
1302 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.1">
1303 <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
1304 </li>
1305 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.2">
1306 <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-terminology" class="xref">Terminology</a></p>
1307 </li>
1308 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.3">
1309 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-considerations-about-port-r" class="xref">Considerations about Port Randomization in NTP</a></p>
1310 <ul class="ulBare toc ulEmpty compact">
1311 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.3.2.1">
1312 <p id="section-toc.1-1.3.2.1.1" class="keepWithNext"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-mitigation-against-off-path" class="xref">Mitigation against Off-Path Attacks</a></p>
1313 </li>
1314 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.3.2.2">
1315 <p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>.  <a href="#name-effects-on-path-selection" class="xref">Effects on Path Selection</a></p>
1316 </li>
1317 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.3.2.3">
1318 <p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>.  <a href="#name-filtering-of-ntp-traffic" class="xref">Filtering of NTP Traffic</a></p>
1319 </li>
1320 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.3.2.4">
1321 <p id="section-toc.1-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>.  <a href="#name-effect-on-napt-devices" class="xref">Effect on NAPT Devices</a></p>
1322 </li>
1323 </ul>
1324 </li>
1325 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.4">
1326 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-update-to-rfc-5905" class="xref">Update to RFC 5905</a></p>
1327 </li>
1328 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.5">
1329 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
1330 </li>
1331 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.6">
1332 <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>
1333 </li>
1334 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.7">
1335 <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>
1336 <ul class="ulBare toc ulEmpty compact">
1337 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.7.2.1">
1338 <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>
1339 </li>
1340 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.7.2.2">
1341 <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>
1342 </li>
1343 </ul>
1344 </li>
1345 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.8">
1346 <p id="section-toc.1-1.8.1"><a href="#appendix-A" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a></p>
1347 </li>
1348 <li class="ulBare toc ulEmpty compact" id="section-toc.1-1.9">
1349 <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>
1350 </li>
1351 </ul>
1352 </nav>
1353 </section>
1354 </div>
1355 <div id="sect-1">
1356 <section id="section-1">
1357 <h2 id="name-introduction">
1358 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1359 </h2>
1360 <p id="section-1-1">
1361 The Network Time Protocol (NTP) is one of the oldest Internet
1362 protocols and is currently specified in <span>[<a href="#RFC5905" class="xref">RFC5905</a>]</span>. Since its original
1363 implementation, standardization, and deployment, a number of
1364 vulnerabilities have been found both in the NTP specification and in
1365 some of its implementations <span>[<a href="#NTP-VULN" class="xref">NTP-VULN</a>]</span>. Some of these
1366 vulnerabilities allow for blind/off-path attacks, where an attacker
1367 can send forged packets to one or both NTP peers to achieve Denial
1368 of Service (DoS), time shifts, or other undesirable outcomes. Many
1369 of these attacks require the attacker to guess or know at least a
1370 target NTP association, typically identified by the tuple {srcaddr,
1371 srcport, dstaddr, dstport, keyid} (see <span><a href="https://www.rfc-editor.org/rfc/rfc5905#section-9.1" class="relref">Section 9.1</a> of [<a href="#RFC5905" class="xref">RFC5905</a>]</span>).
1372 Some of these parameters may be known or easily guessed.<a href="#section-1-1" class="pilcrow">¶</a></p>
1373 <p id="section-1-2">
1374 NTP can operate in several modes. Some of these modes rely on the
1375 ability of nodes to receive unsolicited packets and therefore
1376 require the use of the NTP well-known port (123). However, for modes
1377 where the use of a well-known port is not required, employing the
1378 NTP well-known port unnecessarily facilitates the ability of attackers
1379 to perform blind/off-path attacks (since knowledge of the port
1380 numbers is typically required for such attacks). A recent study
1381 <span>[<a href="#NIST-NTP" class="xref">NIST-NTP</a>]</span> that analyzes the port numbers employed by NTP clients
1382 suggests that numerous NTP clients employ the NTP well-known port as their local port, or select predictable ephemeral
1383 port numbers, thus unnecessarily facilitating the ability of
1384 attackers to perform blind/off-path attacks against NTP.<a href="#section-1-2" class="pilcrow">¶</a></p>
1385 <p id="section-1-3">
1386 BCP 156 <span>[<a href="#RFC6056" class="xref">RFC6056</a>]</span> already recommends the randomization of transport-protocol ephemeral ports. This document aligns NTP with the
1387 recommendation in BCP 156 <span>[<a href="#RFC6056" class="xref">RFC6056</a>]</span> by formally updating <span>[<a href="#RFC5905" class="xref">RFC5905</a>]</span>
1388 such that port randomization is employed for those NTP modes for
1389 which the use of the NTP well-known port is not needed.<a href="#section-1-3" class="pilcrow">¶</a></p>
1390 </section>
1391 </div>
1392 <div id="sect-2">
1393 <section id="section-2">
1394 <h2 id="name-terminology">
1395 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
1396 </h2>
1397 <p id="section-2-1">
1398 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>",
1399 "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and
1400 "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as described in BCP
1401 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when, they appear in all
1402 capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p>
1403 </section>
1404 </div>
1405 <div id="sect-3">
1406 <section id="section-3">
1407 <h2 id="name-considerations-about-port-r">
1408 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-considerations-about-port-r" class="section-name selfRef">Considerations about Port Randomization in NTP</a>
1409 </h2>
1410 <p id="section-3-1">
1411 The following subsections analyze a number of considerations about
1412 transport-protocol ephemeral port randomization when applied to NTP.<a href="#section-3-1" class="pilcrow">¶</a></p>
1413 <div id="sect-3.1">
1414 <section id="section-3.1">
1415 <h3 id="name-mitigation-against-off-path">
1416 <a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-mitigation-against-off-path" class="section-name selfRef">Mitigation against Off-Path Attacks</a>
1417 </h3>
1418 <p id="section-3.1-1">
1419 There has been a fair share of work in the area of blind/off-path
1420 attacks against transport protocols and upper-layer protocols, such
1421 as <span>[<a href="#RFC4953" class="xref">RFC4953</a>]</span> and <span>[<a href="#RFC5927" class="xref">RFC5927</a>]</span>. Whether the target of the attack is a
1422 transport-protocol instance (e.g., TCP connection) or an upper-layer
1423 protocol instance (e.g., an application-protocol instance), the
1424 attacker is required to know or guess the five-tuple {Protocol, IP
1425 Source Address, IP Destination Address, Source Port, Destination
1426 Port} that identifies the target transport-protocol instance or the
1427 transport-protocol instance employed by the target upper-layer
1428 protocol instance. Therefore, increasing the difficulty of guessing
1429 this five-tuple helps mitigate blind/off-path attacks.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
1430 <p id="section-3.1-2">
1431 As a result of these considerations, transport-protocol ephemeral
1432 port randomization is a best current practice (BCP 156) that helps
1433 mitigate off-path attacks at the transport layer. This document
1434 aligns the NTP specification <span>[<a href="#RFC5905" class="xref">RFC5905</a>]</span> with the existing best current
1435 practice on transport-protocol ephemeral port selection, irrespective of other
1436 techniques that may (and should) be implemented for mitigating off-path attacks.<a href="#section-3.1-2" class="pilcrow">¶</a></p>
1437 <p id="section-3.1-3">
1438 We note that transport-protocol ephemeral port randomization is a
1439 transport-layer mitigation against blind/off-path attacks and does
1440 not preclude (nor is it precluded by) other possible mitigations for
1441 off-path attacks that might be implemented at other layers (e.g.,
1442 <span>[<a href="#I-D.ietf-ntp-data-minimization" class="xref">NTP-DATA-MINIMIZATION</a>]</span>). For instance, some of the
1443 aforementioned mitigations may be ineffective against some off-path
1444 attacks <span>[<a href="#NTP-FRAG" class="xref">NTP-FRAG</a>]</span> or may benefit from the additional entropy
1445 provided by port randomization <span>[<a href="#NTP-security" class="xref">NTP-security</a>]</span>.<a href="#section-3.1-3" class="pilcrow">¶</a></p>
1446 </section>
1447 </div>
1448 <div id="sect-3.2">
1449 <section id="section-3.2">
1450 <h3 id="name-effects-on-path-selection">
1451 <a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-effects-on-path-selection" class="section-name selfRef">Effects on Path Selection</a>
1452 </h3>
1453 <p id="section-3.2-1">
1454 Intermediate systems implementing the Equal-Cost Multipath (ECMP)
1455 algorithm may select the outgoing link by computing a hash over a
1456 number of values, including the transport-protocol source port.
1457 Thus, as discussed in <span>[<a href="#NTP-CHLNG" class="xref">NTP-CHLNG</a>]</span>, the selected client port may have
1458 an influence on the measured offset and delay.<a href="#section-3.2-1" class="pilcrow">¶</a></p>
1459 <p id="section-3.2-2">
1460 If the source port is changed with each request, packets in different
1461 exchanges will be more likely to take different paths, which could
1462 cause the measurements to be less stable and have a negative impact
1463 on the stability of the clock.<a href="#section-3.2-2" class="pilcrow">¶</a></p>
1464 <p id="section-3.2-3">
1465
1466 Network paths to/from a given server are less likely to change between
1467 requests if port randomization is applied on a per-association basis. This
1468 approach minimizes the impact on the stability of NTP measurements,
1469 but it may cause different clients in the same network synchronized to the
1470 same NTP server to have a significant stable offset between their clocks.
1471 This is due to their NTP exchanges consistently taking different paths with
1472 different asymmetry in the network delay.<a href="#section-3.2-3" class="pilcrow">¶</a></p>
1473 <p id="section-3.2-4">
1474 <a href="#sect-4" class="xref">Section 4</a> recommends that NTP implementations randomize the ephemeral
1475 port number of client/server associations. The choice of whether to
1476 randomize the port number on a per-association or a per-request basis
1477 is left to the implementation.<a href="#section-3.2-4" class="pilcrow">¶</a></p>
1478 </section>
1479 </div>
1480 <div id="sect-3.3">
1481 <section id="section-3.3">
1482 <h3 id="name-filtering-of-ntp-traffic">
1483 <a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-filtering-of-ntp-traffic" class="section-name selfRef">Filtering of NTP Traffic</a>
1484 </h3>
1485 <p id="section-3.3-1">
1486 In a number of scenarios (such as when mitigating DDoS attacks), a
1487 network operator may want to differentiate between NTP requests sent
1488 by clients and NTP responses sent by NTP servers. If an
1489 implementation employs the NTP well-known port for the client port, requests/responses cannot be readily differentiated by
1490 inspecting the source and destination port numbers.
1491
1492
1493 Implementation of port randomization for nonsymmetrical modes allows for
1494 simple differentiation of NTP requests and responses and for the
1495 enforcement of security policies that may be valuable for the mitigation of
1496 DDoS attacks, when all NTP clients in a given network employ port randomization.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
1497 </section>
1498 </div>
1499 <div id="sect-3.4">
1500 <section id="section-3.4">
1501 <h3 id="name-effect-on-napt-devices">
1502 <a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-effect-on-napt-devices" class="section-name selfRef">Effect on NAPT Devices</a>
1503 </h3>
1504 <p id="section-3.4-1">
1505 Some NAPT devices will reportedly not translate the source port of a
1506 packet when a system port number (i.e., a port number in the range
1507 0-1023) <span>[<a href="#RFC6335" class="xref">RFC6335</a>]</span> is employed. In networks where such NAPT devices
1508 are employed, use of the NTP well-known port for the client port may
1509 limit the number of hosts that may successfully employ NTP client
1510 implementations at any given time.<a href="#section-3.4-1" class="pilcrow">¶</a></p>
1511 <aside id="section-3.4-2">
1512 <p id="section-3.4-2.1">NOTES:<a href="#section-3.4-2.1" class="pilcrow">¶</a></p>
1513 <p style="margin-left: 1.5em" id="section-3.4-2.2">NAPT devices are defined in <span><a href="https://www.rfc-editor.org/rfc/rfc2663#section-4.1.2" class="relref">Section 4.1.2</a> of [<a href="#RFC2663" class="xref">RFC2663</a>]</span>.<a href="#section-3.4-2.2" class="pilcrow">¶</a></p>
1514 <p style="margin-left: 1.5em" id="section-3.4-2.3">The reported behavior is similar to the special treatment of UDP
1515 port 500, which has been documented in <span><a href="https://www.rfc-editor.org/rfc/rfc3715#section-2.3" class="relref">Section 2.3</a> of [<a href="#RFC3715" class="xref">RFC3715</a>]</span>.<a href="#section-3.4-2.3" class="pilcrow">¶</a></p>
1516 </aside>
1517 <p id="section-3.4-3">
1518 In the case of NAPT devices that will translate the source port even
1519 when a system port is employed, packets reaching the external realm
1520 of the NAPT will not employ the NTP well-known port as the source
1521 port, as a result of the port translation function being performed by the
1522 NAPT device.<a href="#section-3.4-3" class="pilcrow">¶</a></p>
1523 </section>
1524 </div>
1525 </section>
1526 </div>
1527 <div id="sect-4">
1528 <section id="section-4">
1529 <h2 id="name-update-to-rfc-5905">
1530 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-update-to-rfc-5905" class="section-name selfRef">Update to RFC 5905</a>
1531 </h2>
1532 <p id="section-4-1">
1533 The following text from Section
1534 <span><a href="https://www.rfc-editor.org/rfc/rfc5905#section-9.1" class="relref">9.1</a> (<a href="https://www.rfc-editor.org/rfc/rfc5905#section-9.1" class="relref">Peer
1535 Process Variables</a>)</span> of <span>[<a href="#RFC5905" class="xref">RFC5905</a>]</span>:<a href="#section-4-1" class="pilcrow">¶</a></p>
1536 <blockquote id="section-4-2">
1537 <span class="break"></span><dl class="dlParallel" id="section-4-2.1">
1538 <dt id="section-4-2.1.1">dstport:</dt>
1539 <dd style="margin-left: 1.5em" id="section-4-2.1.2"> UDP port number of the client, ordinarily the NTP port
1540 number PORT (123) assigned by the IANA. This becomes the source
1541 port number in packets sent from this association.<a href="#section-4-2.1.2" class="pilcrow">¶</a>
1542 </dd>
1543 <dd class="break"></dd>
1544 </dl>
1545 </blockquote>
1546 <p id="section-4-3">is replaced with:<a href="#section-4-3" class="pilcrow">¶</a></p>
1547 <blockquote id="section-4-4">
1548 <span class="break"></span><dl class="dlParallel" id="section-4-4.1">
1549 <dt id="section-4-4.1.1">dstport:</dt>
1550 <dd style="margin-left: 1.5em" id="section-4-4.1.2"> UDP port number of the client. In the case of broadcast
1551 server mode (5) and symmetric modes (1 and 2), it <span class="bcp14">SHOULD</span> contain
1552 the NTP port number PORT (123) assigned by IANA. In the
1553 client mode (3), it <span class="bcp14">SHOULD</span> contain a randomized port number, as
1554 specified in <span>[<a href="#RFC6056" class="xref">RFC6056</a>]</span>. The value in this variable becomes the
1555 source port number of packets sent from this association. The
1556 randomized port number <span class="bcp14">SHOULD NOT</span> be shared with other
1557 associations, to avoid revealing the randomized port to other
1558 associations.<a href="#section-4-4.1.2" class="pilcrow">¶</a>
1559 </dd>
1560 <dd class="break"></dd>
1561 <dt id="section-4-4.1.3"></dt>
1562 <dd style="margin-left: 1.5em" id="section-4-4.1.4">If a client implementation performs transport-protocol ephemeral port randomization
1563 on a per-request basis, it <span class="bcp14">SHOULD</span> close the corresponding socket/port
1564 after each request/response exchange. In order to prevent duplicate
1565 or delayed server packets from eliciting ICMP port unreachable error
1566 messages <span>[<a href="#RFC0792" class="xref">RFC0792</a>]</span> <span>[<a href="#RFC4443" class="xref">RFC4443</a>]</span> at the client, the client <span class="bcp14">MAY</span> wait for more responses from
1567 the server for a specific period of time (e.g., 3 seconds) before
1568 closing the UDP socket/port.<a href="#section-4-4.1.4" class="pilcrow">¶</a>
1569 </dd>
1570 <dd class="break"></dd>
1571 <dt id="section-4-4.1.5"></dt>
1572 <dd style="margin-left: 1.5em" id="section-4-4.1.6"></dd>
1573 <dd class="break"></dd>
1574 </dl>
1575 <span class="break"></span><dl class="dlParallel" id="section-4-4.2">
1576 <dt id="section-4-4.2.1"></dt>
1577 <dd style="margin-left: 3.0em" id="section-4-4.2.2">
1578 <p id="section-4-4.2.2.1">NOTES:<a href="#section-4-4.2.2.1" class="pilcrow">¶</a></p>
1579 <p id="section-4-4.2.2.2">Randomizing the ephemeral port number on a per-request basis
1580 will better mitigate blind/off-path attacks, particularly if
1581 the socket/port is closed after each request/response exchange,
1582 as recommended above. The choice of whether to randomize the
1583 ephemeral port number on a per-request or a per-association
1584 basis is left to the implementation, and it should consider the
1585 possible effects on path selection along with its possible
1586 impact on time measurement.<a href="#section-4-4.2.2.2" class="pilcrow">¶</a></p>
1587 </dd>
1588 <dd class="break"></dd>
1589 <dt id="section-4-4.2.3"></dt>
1590 <dd style="margin-left: 3.0em" id="section-4-4.2.4">On most current operating systems, which implement ephemeral
1591 port randomization <span>[<a href="#RFC6056" class="xref">RFC6056</a>]</span>, an NTP client may normally rely
1592 on the operating system to perform ephemeral port
1593 randomization. For example, NTP implementations using POSIX
1594 sockets may achieve ephemeral port randomization by <em>not</em>
1595 binding the socket with the bind() function or binding it to
1596 port 0, which has a special meaning of "any port". Using the connect() function for the socket will make the port inaccessible
1597 by other systems (that is, only packets from the specified remote socket will be
1598 received by the application).<a href="#section-4-4.2.4" class="pilcrow">¶</a>
1599 </dd>
1600 <dd class="break"></dd>
1601 </dl>
1602 </blockquote>
1603 </section>
1604 </div>
1605 <div id="sect-6">
1606 <section id="section-5">
1607 <h2 id="name-iana-considerations">
1608 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
1609 </h2>
1610 <p id="section-5-1">
1611 This document has no IANA actions.<a href="#section-5-1" class="pilcrow">¶</a></p>
1612 </section>
1613 </div>
1614 <div id="sect-7">
1615 <section id="section-6">
1616 <h2 id="name-security-considerations">
1617 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
1618 </h2>
1619 <p id="section-6-1">
1620 The security implications of predictable numeric identifiers
1621 <span>[<a href="#I-D.irtf-pearg-numeric-ids-generation" class="xref">PEARG-NUMERIC-IDS</a>]</span> (and of predictable
1622 transport-protocol port numbers <span>[<a href="#RFC6056" class="xref">RFC6056</a>]</span> in particular) have been
1623 known for a long time now. However, the NTP specification has
1624 traditionally followed a pattern of employing common settings even
1625 when not strictly necessary, which at times has resulted in negative
1626 security and privacy implications (see, e.g.,
1627 <span>[<a href="#I-D.ietf-ntp-data-minimization" class="xref">NTP-DATA-MINIMIZATION</a>]</span>). The use of the NTP well-known
1628 port (123) for the srcport and dstport variables is not required for
1629 all operating modes. Such unnecessary usage comes at the expense of
1630 reducing the amount of work required for an attacker to successfully
1631 perform blind/off-path attacks against NTP. Therefore, this document
1632 formally updates <span>[<a href="#RFC5905" class="xref">RFC5905</a>]</span>, recommending the use of transport-protocol port randomization when use of the NTP well-known port is
1633 not required.<a href="#section-6-1" class="pilcrow">¶</a></p>
1634 <p id="section-6-2">
1635 This issue has been assigned CVE-2019-11331 <span>[<a href="#VULN-REPORT" class="xref">VULN-REPORT</a>]</span> in the U.S.
1636 National Vulnerability Database (NVD).<a href="#section-6-2" class="pilcrow">¶</a></p>
1637 </section>
1638 </div>
1639 <section id="section-7">
1640 <h2 id="name-references">
1641 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-references" class="section-name selfRef">References</a>
1642 </h2>
1643 <section id="section-7.1">
1644 <h3 id="name-normative-references">
1645 <a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
1646 </h3>
1647 <dl class="references">
1648 <dt id="RFC2119">[RFC2119]</dt>
1649 <dd>
1650 <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>
1651 <dd class="break"></dd>
1652 <dt id="RFC5905">[RFC5905]</dt>
1653 <dd>
1654 <span class="refAuthor">Mills, D.</span>, <span class="refAuthor">Martin, J., Ed.</span>, <span class="refAuthor">Burbank, J.</span>, and <span class="refAuthor">W. Kasch</span>, <span class="refTitle">"Network Time Protocol Version 4: Protocol and Algorithms Specification"</span>, <span class="seriesInfo">RFC 5905</span>, <span class="seriesInfo">DOI 10.17487/RFC5905</span>, <time datetime="2010-06" class="refDate">June 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5905">https://www.rfc-editor.org/info/rfc5905</a>&gt;</span>. </dd>
1655 <dd class="break"></dd>
1656 <dt id="RFC6056">[RFC6056]</dt>
1657 <dd>
1658 <span class="refAuthor">Larsen, M.</span> and <span class="refAuthor">F. Gont</span>, <span class="refTitle">"Recommendations for Transport-Protocol Port Randomization"</span>, <span class="seriesInfo">BCP 156</span>, <span class="seriesInfo">RFC 6056</span>, <span class="seriesInfo">DOI 10.17487/RFC6056</span>, <time datetime="2011-01" class="refDate">January 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6056">https://www.rfc-editor.org/info/rfc6056</a>&gt;</span>. </dd>
1659 <dd class="break"></dd>
1660 <dt id="RFC8174">[RFC8174]</dt>
1661 <dd>
1662 <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>
1663 <dd class="break"></dd>
1664 </dl>
1665 </section>
1666 <section id="section-7.2">
1667 <h3 id="name-informative-references">
1668 <a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
1669 </h3>
1670 <dl class="references">
1671 <dt id="NIST-NTP">[NIST-NTP]</dt>
1672 <dd>
1673 <span class="refAuthor">Sherman, J.</span> and <span class="refAuthor">J. Levine</span>, <span class="refTitle">"Usage Analysis of the NIST Internet Time Service"</span>, <span class="refContent">Journal of Research of the National Institute of Standards and Technology, Volume 121</span>, <span class="seriesInfo">DOI 10.6028/jres.121.003</span>, <time datetime="2016-03" class="refDate">March 2016</time>, <span>&lt;<a href="https://tf.nist.gov/general/pdf/2818.pdf">https://tf.nist.gov/general/pdf/2818.pdf</a>&gt;</span>. </dd>
1674 <dd class="break"></dd>
1675 <dt id="NTP-CHLNG">[NTP-CHLNG]</dt>
1676 <dd>
1677 <span class="refAuthor">Sommars, S.</span>, <span class="refTitle">"Challenges in Time Transfer using the Network Time Protocol (NTP)"</span>, <span class="refContent">Proceedings of the 48th Annual Precise Time and Time Interval Systems and Applications Meeting, pp. 271-290</span>, <span class="seriesInfo">DOI 10.33012/2017.14978</span>, <time datetime="2017-01" class="refDate">January 2017</time>, <span>&lt;<a href="http://leapsecond.com/ntp/NTP_Paper_Sommars_PTTI2017.pdf">http://leapsecond.com/ntp/NTP_Paper_Sommars_PTTI2017.pdf</a>&gt;</span>. </dd>
1678 <dd class="break"></dd>
1679 <dt id="I-D.ietf-ntp-data-minimization">[NTP-DATA-MINIMIZATION]</dt>
1680 <dd>
1681 <span class="refAuthor">Franke, D.</span> and <span class="refAuthor">A. Malhotra</span>, <span class="refTitle">"NTP Client Data Minimization"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-ntp-data-minimization-04</span>, <time datetime="2019-03-25" class="refDate">25 March 2019</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-ntp-data-minimization-04">https://datatracker.ietf.org/doc/html/draft-ietf-ntp-data-minimization-04</a>&gt;</span>. </dd>
1682 <dd class="break"></dd>
1683 <dt id="NTP-FRAG">[NTP-FRAG]</dt>
1684 <dd>
1685 <span class="refAuthor">Malhotra, A.</span>, <span class="refAuthor">Cohen, I.</span>, <span class="refAuthor">Brakke, E.</span>, and <span class="refAuthor">S. Goldberg</span>, <span class="refTitle">"Attacking the Network Time Protocol"</span>, <span class="refContent">NDSS '16</span>, <span class="seriesInfo">DOI 10.14722/ndss.2016.23090</span>, <time datetime="2016-02" class="refDate">February 2016</time>, <span>&lt;<a href="https://www.cs.bu.edu/~goldbe/papers/NTPattack.pdf">https://www.cs.bu.edu/~goldbe/papers/NTPattack.pdf</a>&gt;</span>. </dd>
1686 <dd class="break"></dd>
1687 <dt id="NTP-security">[NTP-security]</dt>
1688 <dd>
1689 <span class="refAuthor">Malhotra, A.</span>, <span class="refAuthor">Van Gundy, M.</span>, <span class="refAuthor">Varia, M.</span>, <span class="refAuthor">Kennedy, H.</span>, <span class="refAuthor">Gardner, J.</span>, and <span class="refAuthor">S. Goldberg</span>, <span class="refTitle">"The Security of NTP's Datagram Protocol"</span>, <span class="refContent">Cryptology ePrint Archive Report 2016/1006</span>, <span class="seriesInfo">DOI 10.1007/978-3-319-70972-7_23</span>, <time datetime="2017-02" class="refDate">February 2017</time>, <span>&lt;<a href="https://eprint.iacr.org/2016/1006.pdf">https://eprint.iacr.org/2016/1006.pdf</a>&gt;</span>. </dd>
1690 <dd class="break"></dd>
1691 <dt id="NTP-VULN">[NTP-VULN]</dt>
1692 <dd>
1693 <span class="refTitle">"Network Time Foundation"</span>, <span>&lt;<a href="http://support.ntp.org/bin/view/Main/SecurityNotice">http://support.ntp.org/bin/view/Main/SecurityNotice</a>&gt;</span>. </dd>
1694 <dd class="break"></dd>
1695 <dt id="I-D.irtf-pearg-numeric-ids-generation">[PEARG-NUMERIC-IDS]</dt>
1696 <dd>
1697 <span class="refAuthor">Gont, F.</span> and <span class="refAuthor">I. Arce</span>, <span class="refTitle">"On the Generation of Transient Numeric Identifiers"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-irtf-pearg-numeric-ids-generation-07</span>, <time datetime="2021-02-02" class="refDate">2 February 2021</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-irtf-pearg-numeric-ids-generation-07">https://datatracker.ietf.org/doc/html/draft-irtf-pearg-numeric-ids-generation-07</a>&gt;</span>. </dd>
1698 <dd class="break"></dd>
1699 <dt id="RFC0792">[RFC0792]</dt>
1700 <dd>
1701 <span class="refAuthor">Postel, J.</span>, <span class="refTitle">"Internet Control Message Protocol"</span>, <span class="seriesInfo">STD 5</span>, <span class="seriesInfo">RFC 792</span>, <span class="seriesInfo">DOI 10.17487/RFC0792</span>, <time datetime="1981-09" class="refDate">September 1981</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc792">https://www.rfc-editor.org/info/rfc792</a>&gt;</span>. </dd>
1702 <dd class="break"></dd>
1703 <dt id="RFC2663">[RFC2663]</dt>
1704 <dd>
1705 <span class="refAuthor">Srisuresh, P.</span> and <span class="refAuthor">M. Holdrege</span>, <span class="refTitle">"IP Network Address Translator (NAT) Terminology and Considerations"</span>, <span class="seriesInfo">RFC 2663</span>, <span class="seriesInfo">DOI 10.17487/RFC2663</span>, <time datetime="1999-08" class="refDate">August 1999</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2663">https://www.rfc-editor.org/info/rfc2663</a>&gt;</span>. </dd>
1706 <dd class="break"></dd>
1707 <dt id="RFC3715">[RFC3715]</dt>
1708 <dd>
1709 <span class="refAuthor">Aboba, B.</span> and <span class="refAuthor">W. Dixon</span>, <span class="refTitle">"IPsec-Network Address Translation (NAT) Compatibility Requirements"</span>, <span class="seriesInfo">RFC 3715</span>, <span class="seriesInfo">DOI 10.17487/RFC3715</span>, <time datetime="2004-03" class="refDate">March 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3715">https://www.rfc-editor.org/info/rfc3715</a>&gt;</span>. </dd>
1710 <dd class="break"></dd>
1711 <dt id="RFC4443">[RFC4443]</dt>
1712 <dd>
1713 <span class="refAuthor">Conta, A.</span>, <span class="refAuthor">Deering, S.</span>, and <span class="refAuthor">M. Gupta, Ed.</span>, <span class="refTitle">"Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification"</span>, <span class="seriesInfo">STD 89</span>, <span class="seriesInfo">RFC 4443</span>, <span class="seriesInfo">DOI 10.17487/RFC4443</span>, <time datetime="2006-03" class="refDate">March 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4443">https://www.rfc-editor.org/info/rfc4443</a>&gt;</span>. </dd>
1714 <dd class="break"></dd>
1715 <dt id="RFC4953">[RFC4953]</dt>
1716 <dd>
1717 <span class="refAuthor">Touch, J.</span>, <span class="refTitle">"Defending TCP Against Spoofing Attacks"</span>, <span class="seriesInfo">RFC 4953</span>, <span class="seriesInfo">DOI 10.17487/RFC4953</span>, <time datetime="2007-07" class="refDate">July 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4953">https://www.rfc-editor.org/info/rfc4953</a>&gt;</span>. </dd>
1718 <dd class="break"></dd>
1719 <dt id="RFC5927">[RFC5927]</dt>
1720 <dd>
1721 <span class="refAuthor">Gont, F.</span>, <span class="refTitle">"ICMP Attacks against TCP"</span>, <span class="seriesInfo">RFC 5927</span>, <span class="seriesInfo">DOI 10.17487/RFC5927</span>, <time datetime="2010-07" class="refDate">July 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5927">https://www.rfc-editor.org/info/rfc5927</a>&gt;</span>. </dd>
1722 <dd class="break"></dd>
1723 <dt id="RFC6335">[RFC6335]</dt>
1724 <dd>
1725 <span class="refAuthor">Cotton, M.</span>, <span class="refAuthor">Eggert, L.</span>, <span class="refAuthor">Touch, J.</span>, <span class="refAuthor">Westerlund, M.</span>, and <span class="refAuthor">S. Cheshire</span>, <span class="refTitle">"Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry"</span>, <span class="seriesInfo">BCP 165</span>, <span class="seriesInfo">RFC 6335</span>, <span class="seriesInfo">DOI 10.17487/RFC6335</span>, <time datetime="2011-08" class="refDate">August 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6335">https://www.rfc-editor.org/info/rfc6335</a>&gt;</span>. </dd>
1726 <dd class="break"></dd>
1727 <dt id="VULN-REPORT">[VULN-REPORT]</dt>
1728 <dd>
1729 <span class="refAuthor">The MITRE Corporation</span>, <span class="refTitle">"CVE-2019-1133"</span>, <span class="refContent">National Vulnerability Database</span>, <time datetime="2020-08" class="refDate">August 2020</time>, <span>&lt;<a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11331">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11331</a>&gt;</span>. </dd>
1730 <dd class="break"></dd>
1731 </dl>
1732 </section>
1733 </section>
1734 <div id="sect-8">
1735 <section id="appendix-A">
1736 <h2 id="name-acknowledgments">
1737 <a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
1738 </h2>
1739 <p id="appendix-A-1">
1740 The authors would like to thank (in alphabetical order) <span class="contact-name">Ivan Arce</span>,
1741 <span class="contact-name">Roman Danyliw</span>, <span class="contact-name">Dhruv Dhody</span>, <span class="contact-name">Lars Eggert</span>, <span class="contact-name">Todd Glassey</span>, <span class="contact-name">Blake Hudson</span>,
1742 <span class="contact-name">Benjamin Kaduk</span>, <span class="contact-name">Erik Kline</span>, <span class="contact-name">Watson Ladd</span>, <span class="contact-name">Aanchal Malhotra</span>, <span class="contact-name">Danny Mayer</span>, <span class="contact-name">Gary E. Miller</span>, <span class="contact-name">Bjorn Mork</span>, <span class="contact-name">Hal Murray</span>, <span class="contact-name">Francesca Palombini</span>,
1743 <span class="contact-name">Tomoyuki Sahara</span>, <span class="contact-name">Zaheduzzaman Sarker</span>, <span class="contact-name">Dieter Sibold</span>, <span class="contact-name">Steven Sommars</span>,
1744 <span class="contact-name">Jean St-Laurent</span>, <span class="contact-name">Kristof Teichel</span>, <span class="contact-name">Brian Trammell</span>, <span class="contact-name">Éric Vyncke</span>, <span class="contact-name">Ulrich Windl</span>, and <span class="contact-name">Dan Wing</span> for providing valuable comments on earlier draft versions of this document.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
1745 <p id="appendix-A-2">
1746 <span class="contact-name">Watson Ladd</span> raised the problem of DDoS mitigation when the NTP well-known
1747 port is employed as the client port (discussed in <a href="#sect-3.3" class="xref">Section 3.3</a> of this document).<a href="#appendix-A-2" class="pilcrow">¶</a></p>
1748 <p id="appendix-A-3">
1749 The authors would like to thank <span class="contact-name">Harlan Stenn</span> for answering questions
1750 about a popular NTP implementation (see <span>&lt;<a href="https://www.nwtime.org">https://www.nwtime.org</a>&gt;</span>).<a href="#appendix-A-3" class="pilcrow">¶</a></p>
1751 <p id="appendix-A-4">
1752 <span class="contact-name">Fernando Gont</span> would like to thank <span class="contact-name">Nelida Garcia</span> and <span class="contact-name">Jorge Oscar Gont</span> for
1753 their love and support.<a href="#appendix-A-4" class="pilcrow">¶</a></p>
1754 </section>
1755 </div>
1756 <div id="authors-addresses">
1757 <section id="appendix-B">
1758 <h2 id="name-authors-addresses">
1759 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
1760 </h2>
1761 <address class="vcard">
1762 <div dir="auto" class="left"><span class="fn nameRole">Fernando Gont</span></div>
1763 <div dir="auto" class="left"><span class="org">SI6 Networks</span></div>
1764 <div dir="auto" class="left"><span class="street-address">Evaristo Carriego 2644</span></div>
1765 <div dir="auto" class="left">
1766 <span class="postal-code">1706</span> <span class="locality">Haedo, Provincia de Buenos Aires</span>
1767 </div>
1768 <div dir="auto" class="left"><span class="country-name">Argentina</span></div>
1769 <div class="tel">
1770 <span>Phone:</span>
1771 <a href="tel:+54%2011%204650%208472" class="tel">+54 11 4650 8472</a>
1772 </div>
1773 <div class="email">
1774 <span>Email:</span>
1775 <a href="mailto:[email protected]" class="email">[email protected]</a>
1776 </div>
1777 <div class="url">
1778 <span>URI:</span>
1779 <a href="https://www.si6networks.com" class="url">https://www.si6networks.com</a>
1780 </div>
1781 </address>
1782 <address class="vcard">
1783 <div dir="auto" class="left"><span class="fn nameRole">Guillermo Gont</span></div>
1784 <div dir="auto" class="left"><span class="org">SI6 Networks</span></div>
1785 <div dir="auto" class="left"><span class="street-address">Evaristo Carriego 2644</span></div>
1786 <div dir="auto" class="left">
1787 <span class="postal-code">1706</span> <span class="locality">Haedo, Provincia de Buenos Aires</span>
1788 </div>
1789 <div dir="auto" class="left"><span class="country-name">Argentina</span></div>
1790 <div class="tel">
1791 <span>Phone:</span>
1792 <a href="tel:+54%2011%204650%208472" class="tel">+54 11 4650 8472</a>
1793 </div>
1794 <div class="email">
1795 <span>Email:</span>
1796 <a href="mailto:[email protected]" class="email">[email protected]</a>
1797 </div>
1798 <div class="url">
1799 <span>URI:</span>
1800 <a href="https://www.si6networks.com" class="url">https://www.si6networks.com</a>
1801 </div>
1802 </address>
1803 <address class="vcard">
1804 <div dir="auto" class="left"><span class="fn nameRole">Miroslav Lichvar</span></div>
1805 <div dir="auto" class="left"><span class="org">Red Hat</span></div>
1806 <div dir="auto" class="left"><span class="street-address">Purkynova 115</span></div>
1807 <div dir="auto" class="left">
1808 <span class="postal-code">612 00</span> <span class="locality">Brno</span>
1809 </div>
1810 <div dir="auto" class="left"><span class="country-name">Czech Republic</span></div>
1811 <div class="email">
1812 <span>Email:</span>
1813 <a href="mailto:[email protected]" class="email">[email protected]</a>
1814 </div>
1815 </address>
1816 </section>
1817 </div>
1818 <script>const toc = document.getElementById("toc");
1819 toc.querySelector("h2").addEventListener("click", e => {
1820 toc.classList.toggle("active");
1821 });
1822 toc.querySelector("nav").addEventListener("click", e => {
1823 toc.classList.remove("active");
1824 });
1825 </script>
1826 </body>
1827 </html>