Debian Codegraph @

rfc9011.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 9011: Static Context Header Compression and Fragmentation (SCHC) over LoRaWAN</title>
8 <meta content="Olivier Gimenez" name="author">
9 <meta content="Ivaylo Petrov" name="author">
10 <meta content="
11 The Static Context Header Compression and fragmentation (SCHC) specification (RFC 8724) describes
12 generic header compression and fragmentation techniques for Low-Power
13 Wide Area Network (LPWAN) technologies. SCHC is a generic mechanism
14 designed for great flexibility so that it can be adapted for any of the
15 LPWAN technologies.
16 This document defines a profile of SCHC (RFC 8724) for use in
17 LoRaWAN networks and provides elements such as efficient
18 parameterization and modes of operation.
19 " name="description">
20 <meta content="xml2rfc 3.7.0" name="generator">
21 <meta content="header compression" name="keyword">
22 <meta content="compression" name="keyword">
23 <meta content="fragmentation" name="keyword">
24 <meta content="static context" name="keyword">
25 <meta content="rule-based" name="keyword">
26 <meta content="LPWAN" name="keyword">
27 <meta content="LPWANs" name="keyword">
28 <meta content="low power" name="keyword">
29 <meta content="low-power" name="keyword">
30 <meta content="LoRa" name="keyword">
31 <meta content="LoRaWAN" name="keyword">
32 <meta content="IoT" name="keyword">
33 <meta content="Internet of Things" name="keyword">
34 <meta content="adaptation layer" name="keyword">
35 <meta content="UDP" name="keyword">
36 <meta content="IPv6" name="keyword">
37 <meta content="sensor network" name="keyword">
38 <meta content="wireless sensor network" name="keyword">
39 <meta content="802.15.4" name="keyword">
40 <meta content="constrained network" name="keyword">
41 <meta content="constrained node" name="keyword">
42 <meta content="constrained-node network" name="keyword">
43 <meta content="SCHC" name="keyword">
44 <meta content="9011" name="rfc.number">
45 <!-- Generator version information:
46 xml2rfc 3.7.0
47 Python 3.6.10
48 appdirs 1.4.4
49 ConfigArgParse 1.2.3
50 google-i18n-address 2.3.5
51 html5lib 1.0.1
52 intervaltree 3.0.2
53 Jinja2 2.11.2
54 kitchen 1.2.6
55 lxml 4.4.2
56 pycairo 1.19.0
57 pycountry 19.8.18
58 pyflakes 2.1.1
59 PyYAML 5.3.1
60 requests 2.22.0
61 setuptools 40.6.2
62 six 1.14.0
63 WeasyPrint 51
64 -->
65 <link href="rfc9011.xml" rel="alternate" type="application/rfc+xml">
66 <link href="#copyright" rel="license">
67 <style type="text/css">/*
68
69 NOTE: Changes at the bottom of this file overrides some earlier settings.
70
71 Once the style has stabilized and has been adopted as an official RFC style,
72 this can be consolidated so that style settings occur only in one place, but
73 for now the contents of this file consists first of the initial CSS work as
74 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
75 commented changes found necssary during the development of the v3
76 formatters.
77
78 */
79
80 /* fonts */
81 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
82 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
83 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
84
85 @viewport {
86 zoom: 1.0;
87 width: extend-to-zoom;
88 }
89 @-ms-viewport {
90 width: extend-to-zoom;
91 zoom: 1.0;
92 }
93 /* general and mobile first */
94 html {
95 }
96 body {
97 max-width: 90%;
98 margin: 1.5em auto;
99 color: #222;
100 background-color: #fff;
101 font-size: 14px;
102 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
103 line-height: 1.6;
104 scroll-behavior: smooth;
105 }
106 .ears {
107 display: none;
108 }
109
110 /* headings */
111 #title, h1, h2, h3, h4, h5, h6 {
112 margin: 1em 0 0.5em;
113 font-weight: bold;
114 line-height: 1.3;
115 }
116 #title {
117 clear: both;
118 border-bottom: 1px solid #ddd;
119 margin: 0 0 0.5em 0;
120 padding: 1em 0 0.5em;
121 }
122 .author {
123 padding-bottom: 4px;
124 }
125 h1 {
126 font-size: 26px;
127 margin: 1em 0;
128 }
129 h2 {
130 font-size: 22px;
131 margin-top: -20px; /* provide offset for in-page anchors */
132 padding-top: 33px;
133 }
134 h3 {
135 font-size: 18px;
136 margin-top: -36px; /* provide offset for in-page anchors */
137 padding-top: 42px;
138 }
139 h4 {
140 font-size: 16px;
141 margin-top: -36px; /* provide offset for in-page anchors */
142 padding-top: 42px;
143 }
144 h5, h6 {
145 font-size: 14px;
146 }
147 #n-copyright-notice {
148 border-bottom: 1px solid #ddd;
149 padding-bottom: 1em;
150 margin-bottom: 1em;
151 }
152 /* general structure */
153 p {
154 padding: 0;
155 margin: 0 0 1em 0;
156 text-align: left;
157 }
158 div, span {
159 position: relative;
160 }
161 div {
162 margin: 0;
163 }
164 .alignRight.art-text {
165 background-color: #f9f9f9;
166 border: 1px solid #eee;
167 border-radius: 3px;
168 padding: 1em 1em 0;
169 margin-bottom: 1.5em;
170 }
171 .alignRight.art-text pre {
172 padding: 0;
173 }
174 .alignRight {
175 margin: 1em 0;
176 }
177 .alignRight > *:first-child {
178 border: none;
179 margin: 0;
180 float: right;
181 clear: both;
182 }
183 .alignRight > *:nth-child(2) {
184 clear: both;
185 display: block;
186 border: none;
187 }
188 svg {
189 display: block;
190 }
191 .alignCenter.art-text {
192 background-color: #f9f9f9;
193 border: 1px solid #eee;
194 border-radius: 3px;
195 padding: 1em 1em 0;
196 margin-bottom: 1.5em;
197 }
198 .alignCenter.art-text pre {
199 padding: 0;
200 }
201 .alignCenter {
202 margin: 1em 0;
203 }
204 .alignCenter > *:first-child {
205 border: none;
206 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
207 support flexbox yet.
208 */
209 display: table;
210 margin: 0 auto;
211 }
212
213 /* lists */
214 ol, ul {
215 padding: 0;
216 margin: 0 0 1em 2em;
217 }
218 ol ol, ul ul, ol ul, ul ol {
219 margin-left: 1em;
220 }
221 li {
222 margin: 0 0 0.25em 0;
223 }
224 .ulCompact li {
225 margin: 0;
226 }
227 ul.empty, .ulEmpty {
228 list-style-type: none;
229 }
230 ul.empty li, .ulEmpty li {
231 margin-top: 0.5em;
232 }
233 ul.compact, .ulCompact,
234 ol.compact, .olCompact {
235 line-height: 100%;
236 margin: 0 0 0 2em;
237 }
238
239 /* definition lists */
240 dl {
241 }
242 dl > dt {
243 float: left;
244 margin-right: 1em;
245 }
246 /*
247 dl.nohang > dt {
248 float: none;
249 }
250 */
251 dl > dd {
252 margin-bottom: .8em;
253 min-height: 1.3em;
254 }
255 dl.compact > dd, .dlCompact > dd {
256 margin-bottom: 0em;
257 }
258 dl > dd > dl {
259 margin-top: 0.5em;
260 margin-bottom: 0em;
261 }
262
263 /* links */
264 a {
265 text-decoration: none;
266 }
267 a[href] {
268 color: #22e; /* Arlen: WCAG 2019 */
269 }
270 a[href]:hover {
271 background-color: #f2f2f2;
272 }
273 figcaption a[href],
274 a[href].selfRef {
275 color: #222;
276 }
277 /* XXX probably not this:
278 a.selfRef:hover {
279 background-color: transparent;
280 cursor: default;
281 } */
282
283 /* Figures */
284 tt, code, pre, code {
285 background-color: #f9f9f9;
286 font-family: 'Roboto Mono', monospace;
287 }
288 pre {
289 border: 1px solid #eee;
290 margin: 0;
291 padding: 1em;
292 }
293 img {
294 max-width: 100%;
295 }
296 figure {
297 margin: 0;
298 }
299 figure blockquote {
300 margin: 0.8em 0.4em 0.4em;
301 }
302 figcaption {
303 font-style: italic;
304 margin: 0 0 1em 0;
305 }
306 @media screen {
307 pre {
308 overflow-x: auto;
309 max-width: 100%;
310 max-width: calc(100% - 22px);
311 }
312 }
313
314 /* aside, blockquote */
315 aside, blockquote {
316 margin-left: 0;
317 padding: 1.2em 2em;
318 }
319 blockquote {
320 background-color: #f9f9f9;
321 color: #111; /* Arlen: WCAG 2019 */
322 border: 1px solid #ddd;
323 border-radius: 3px;
324 margin: 1em 0;
325 }
326 cite {
327 display: block;
328 text-align: right;
329 font-style: italic;
330 }
331
332 /* tables */
333 table {
334 width: 100%;
335 margin: 0 0 1em;
336 border-collapse: collapse;
337 border: 1px solid #eee;
338 }
339 th, td {
340 text-align: left;
341 vertical-align: top;
342 padding: 0.5em 0.75em;
343 }
344 th {
345 text-align: left;
346 background-color: #e9e9e9;
347 }
348 tr:nth-child(2n+1) > td {
349 background-color: #f5f5f5;
350 }
351 table caption {
352 font-style: italic;
353 margin: 0;
354 padding: 0;
355 text-align: left;
356 }
357 table p {
358 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
359 be allowed within tables more generally, it would be far better to select on a class. */
360 margin: 0;
361 }
362
363 /* pilcrow */
364 a.pilcrow {
365 color: #666; /* Arlen: AHDJ 2019 */
366 text-decoration: none;
367 visibility: hidden;
368 user-select: none;
369 -ms-user-select: none;
370 -o-user-select:none;
371 -moz-user-select: none;
372 -khtml-user-select: none;
373 -webkit-user-select: none;
374 -webkit-touch-callout: none;
375 }
376 @media screen {
377 aside:hover > a.pilcrow,
378 p:hover > a.pilcrow,
379 blockquote:hover > a.pilcrow,
380 div:hover > a.pilcrow,
381 li:hover > a.pilcrow,
382 pre:hover > a.pilcrow {
383 visibility: visible;
384 }
385 a.pilcrow:hover {
386 background-color: transparent;
387 }
388 }
389
390 /* misc */
391 hr {
392 border: 0;
393 border-top: 1px solid #eee;
394 }
395 .bcp14 {
396 font-variant: small-caps;
397 }
398
399 .role {
400 font-variant: all-small-caps;
401 }
402
403 /* info block */
404 #identifiers {
405 margin: 0;
406 font-size: 0.9em;
407 }
408 #identifiers dt {
409 width: 3em;
410 clear: left;
411 }
412 #identifiers dd {
413 float: left;
414 margin-bottom: 0;
415 }
416 #identifiers .authors .author {
417 display: inline-block;
418 margin-right: 1.5em;
419 }
420 #identifiers .authors .org {
421 font-style: italic;
422 }
423
424 /* The prepared/rendered info at the very bottom of the page */
425 .docInfo {
426 color: #666; /* Arlen: WCAG 2019 */
427 font-size: 0.9em;
428 font-style: italic;
429 margin-top: 2em;
430 }
431 .docInfo .prepared {
432 float: left;
433 }
434 .docInfo .prepared {
435 float: right;
436 }
437
438 /* table of contents */
439 #toc {
440 padding: 0.75em 0 2em 0;
441 margin-bottom: 1em;
442 }
443 nav.toc ul {
444 margin: 0 0.5em 0 0;
445 padding: 0;
446 list-style: none;
447 }
448 nav.toc li {
449 line-height: 1.3em;
450 margin: 0.75em 0;
451 padding-left: 1.2em;
452 text-indent: -1.2em;
453 }
454 /* references */
455 .references dt {
456 text-align: right;
457 font-weight: bold;
458 min-width: 7em;
459 }
460 .references dd {
461 margin-left: 8em;
462 overflow: auto;
463 }
464
465 .refInstance {
466 margin-bottom: 1.25em;
467 }
468
469 .references .ascii {
470 margin-bottom: 0.25em;
471 }
472
473 /* index */
474 .index ul {
475 margin: 0 0 0 1em;
476 padding: 0;
477 list-style: none;
478 }
479 .index ul ul {
480 margin: 0;
481 }
482 .index li {
483 margin: 0;
484 text-indent: -2em;
485 padding-left: 2em;
486 padding-bottom: 5px;
487 }
488 .indexIndex {
489 margin: 0.5em 0 1em;
490 }
491 .index a {
492 font-weight: 700;
493 }
494 /* make the index two-column on all but the smallest screens */
495 @media (min-width: 600px) {
496 .index ul {
497 -moz-column-count: 2;
498 -moz-column-gap: 20px;
499 }
500 .index ul ul {
501 -moz-column-count: 1;
502 -moz-column-gap: 0;
503 }
504 }
505
506 /* authors */
507 address.vcard {
508 font-style: normal;
509 margin: 1em 0;
510 }
511
512 address.vcard .nameRole {
513 font-weight: 700;
514 margin-left: 0;
515 }
516 address.vcard .label {
517 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
518 margin: 0.5em 0;
519 }
520 address.vcard .type {
521 display: none;
522 }
523 .alternative-contact {
524 margin: 1.5em 0 1em;
525 }
526 hr.addr {
527 border-top: 1px dashed;
528 margin: 0;
529 color: #ddd;
530 max-width: calc(100% - 16px);
531 }
532
533 /* temporary notes */
534 .rfcEditorRemove::before {
535 position: absolute;
536 top: 0.2em;
537 right: 0.2em;
538 padding: 0.2em;
539 content: "The RFC Editor will remove this note";
540 color: #9e2a00; /* Arlen: WCAG 2019 */
541 background-color: #ffd; /* Arlen: WCAG 2019 */
542 }
543 .rfcEditorRemove {
544 position: relative;
545 padding-top: 1.8em;
546 background-color: #ffd; /* Arlen: WCAG 2019 */
547 border-radius: 3px;
548 }
549 .cref {
550 background-color: #ffd; /* Arlen: WCAG 2019 */
551 padding: 2px 4px;
552 }
553 .crefSource {
554 font-style: italic;
555 }
556 /* alternative layout for smaller screens */
557 @media screen and (max-width: 1023px) {
558 body {
559 padding-top: 2em;
560 }
561 #title {
562 padding: 1em 0;
563 }
564 h1 {
565 font-size: 24px;
566 }
567 h2 {
568 font-size: 20px;
569 margin-top: -18px; /* provide offset for in-page anchors */
570 padding-top: 38px;
571 }
572 #identifiers dd {
573 max-width: 60%;
574 }
575 #toc {
576 position: fixed;
577 z-index: 2;
578 top: 0;
579 right: 0;
580 padding: 0;
581 margin: 0;
582 background-color: inherit;
583 border-bottom: 1px solid #ccc;
584 }
585 #toc h2 {
586 margin: -1px 0 0 0;
587 padding: 4px 0 4px 6px;
588 padding-right: 1em;
589 min-width: 190px;
590 font-size: 1.1em;
591 text-align: right;
592 background-color: #444;
593 color: white;
594 cursor: pointer;
595 }
596 #toc h2::before { /* css hamburger */
597 float: right;
598 position: relative;
599 width: 1em;
600 height: 1px;
601 left: -164px;
602 margin: 6px 0 0 0;
603 background: white none repeat scroll 0 0;
604 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
605 content: "";
606 }
607 #toc nav {
608 display: none;
609 padding: 0.5em 1em 1em;
610 overflow: auto;
611 height: calc(100vh - 48px);
612 border-left: 1px solid #ddd;
613 }
614 }
615
616 /* alternative layout for wide screens */
617 @media screen and (min-width: 1024px) {
618 body {
619 max-width: 724px;
620 margin: 42px auto;
621 padding-left: 1.5em;
622 padding-right: 29em;
623 }
624 #toc {
625 position: fixed;
626 top: 42px;
627 right: 42px;
628 width: 25%;
629 margin: 0;
630 padding: 0 1em;
631 z-index: 1;
632 }
633 #toc h2 {
634 border-top: none;
635 border-bottom: 1px solid #ddd;
636 font-size: 1em;
637 font-weight: normal;
638 margin: 0;
639 padding: 0.25em 1em 1em 0;
640 }
641 #toc nav {
642 display: block;
643 height: calc(90vh - 84px);
644 bottom: 0;
645 padding: 0.5em 0 0;
646 overflow: auto;
647 }
648 img { /* future proofing */
649 max-width: 100%;
650 height: auto;
651 }
652 }
653
654 /* pagination */
655 @media print {
656 body {
657
658 width: 100%;
659 }
660 p {
661 orphans: 3;
662 widows: 3;
663 }
664 #n-copyright-notice {
665 border-bottom: none;
666 }
667 #toc, #n-introduction {
668 page-break-before: always;
669 }
670 #toc {
671 border-top: none;
672 padding-top: 0;
673 }
674 figure, pre {
675 page-break-inside: avoid;
676 }
677 figure {
678 overflow: scroll;
679 }
680 h1, h2, h3, h4, h5, h6 {
681 page-break-after: avoid;
682 }
683 h2+*, h3+*, h4+*, h5+*, h6+* {
684 page-break-before: avoid;
685 }
686 pre {
687 white-space: pre-wrap;
688 word-wrap: break-word;
689 font-size: 10pt;
690 }
691 table {
692 border: 1px solid #ddd;
693 }
694 td {
695 border-top: 1px solid #ddd;
696 }
697 }
698
699 /* This is commented out here, as the string-set: doesn't
700 pass W3C validation currently */
701 /*
702 .ears thead .left {
703 string-set: ears-top-left content();
704 }
705
706 .ears thead .center {
707 string-set: ears-top-center content();
708 }
709
710 .ears thead .right {
711 string-set: ears-top-right content();
712 }
713
714 .ears tfoot .left {
715 string-set: ears-bottom-left content();
716 }
717
718 .ears tfoot .center {
719 string-set: ears-bottom-center content();
720 }
721
722 .ears tfoot .right {
723 string-set: ears-bottom-right content();
724 }
725 */
726
727 @page :first {
728 padding-top: 0;
729 @top-left {
730 content: normal;
731 border: none;
732 }
733 @top-center {
734 content: normal;
735 border: none;
736 }
737 @top-right {
738 content: normal;
739 border: none;
740 }
741 }
742
743 @page {
744 size: A4;
745 margin-bottom: 45mm;
746 padding-top: 20px;
747 /* The follwing is commented out here, but set appropriately by in code, as
748 the content depends on the document */
749 /*
750 @top-left {
751 content: 'Internet-Draft';
752 vertical-align: bottom;
753 border-bottom: solid 1px #ccc;
754 }
755 @top-left {
756 content: string(ears-top-left);
757 vertical-align: bottom;
758 border-bottom: solid 1px #ccc;
759 }
760 @top-center {
761 content: string(ears-top-center);
762 vertical-align: bottom;
763 border-bottom: solid 1px #ccc;
764 }
765 @top-right {
766 content: string(ears-top-right);
767 vertical-align: bottom;
768 border-bottom: solid 1px #ccc;
769 }
770 @bottom-left {
771 content: string(ears-bottom-left);
772 vertical-align: top;
773 border-top: solid 1px #ccc;
774 }
775 @bottom-center {
776 content: string(ears-bottom-center);
777 vertical-align: top;
778 border-top: solid 1px #ccc;
779 }
780 @bottom-right {
781 content: '[Page ' counter(page) ']';
782 vertical-align: top;
783 border-top: solid 1px #ccc;
784 }
785 */
786
787 }
788
789 /* Changes introduced to fix issues found during implementation */
790 /* Make sure links are clickable even if overlapped by following H* */
791 a {
792 z-index: 2;
793 }
794 /* Separate body from document info even without intervening H1 */
795 section {
796 clear: both;
797 }
798
799
800 /* Top align author divs, to avoid names without organization dropping level with org names */
801 .author {
802 vertical-align: top;
803 }
804
805 /* Leave room in document info to show Internet-Draft on one line */
806 #identifiers dt {
807 width: 8em;
808 }
809
810 /* Don't waste quite as much whitespace between label and value in doc info */
811 #identifiers dd {
812 margin-left: 1em;
813 }
814
815 /* Give floating toc a background color (needed when it's a div inside section */
816 #toc {
817 background-color: white;
818 }
819
820 /* Make the collapsed ToC header render white on gray also when it's a link */
821 @media screen and (max-width: 1023px) {
822 #toc h2 a,
823 #toc h2 a:link,
824 #toc h2 a:focus,
825 #toc h2 a:hover,
826 #toc a.toplink,
827 #toc a.toplink:hover {
828 color: white;
829 background-color: #444;
830 text-decoration: none;
831 }
832 }
833
834 /* Give the bottom of the ToC some whitespace */
835 @media screen and (min-width: 1024px) {
836 #toc {
837 padding: 0 0 1em 1em;
838 }
839 }
840
841 /* Style section numbers with more space between number and title */
842 .section-number {
843 padding-right: 0.5em;
844 }
845
846 /* prevent monospace from becoming overly large */
847 tt, code, pre, code {
848 font-size: 95%;
849 }
850
851 /* Fix the height/width aspect for ascii art*/
852 pre.sourcecode,
853 .art-text pre {
854 line-height: 1.12;
855 }
856
857
858 /* Add styling for a link in the ToC that points to the top of the document */
859 a.toplink {
860 float: right;
861 margin-right: 0.5em;
862 }
863
864 /* Fix the dl styling to match the RFC 7992 attributes */
865 dl > dt,
866 dl.dlParallel > dt {
867 float: left;
868 margin-right: 1em;
869 }
870 dl.dlNewline > dt {
871 float: none;
872 }
873
874 /* Provide styling for table cell text alignment */
875 table td.text-left,
876 table th.text-left {
877 text-align: left;
878 }
879 table td.text-center,
880 table th.text-center {
881 text-align: center;
882 }
883 table td.text-right,
884 table th.text-right {
885 text-align: right;
886 }
887
888 /* Make the alternative author contact informatio look less like just another
889 author, and group it closer with the primary author contact information */
890 .alternative-contact {
891 margin: 0.5em 0 0.25em 0;
892 }
893 address .non-ascii {
894 margin: 0 0 0 2em;
895 }
896
897 /* With it being possible to set tables with alignment
898 left, center, and right, { width: 100%; } does not make sense */
899 table {
900 width: auto;
901 }
902
903 /* Avoid reference text that sits in a block with very wide left margin,
904 because of a long floating dt label.*/
905 .references dd {
906 overflow: visible;
907 }
908
909 /* Control caption placement */
910 caption {
911 caption-side: bottom;
912 }
913
914 /* Limit the width of the author address vcard, so names in right-to-left
915 script don't end up on the other side of the page. */
916
917 address.vcard {
918 max-width: 30em;
919 margin-right: auto;
920 }
921
922 /* For address alignment dependent on LTR or RTL scripts */
923 address div.left {
924 text-align: left;
925 }
926 address div.right {
927 text-align: right;
928 }
929
930 /* Provide table alignment support. We can't use the alignX classes above
931 since they do unwanted things with caption and other styling. */
932 table.right {
933 margin-left: auto;
934 margin-right: 0;
935 }
936 table.center {
937 margin-left: auto;
938 margin-right: auto;
939 }
940 table.left {
941 margin-left: 0;
942 margin-right: auto;
943 }
944
945 /* Give the table caption label the same styling as the figcaption */
946 caption a[href] {
947 color: #222;
948 }
949
950 @media print {
951 .toplink {
952 display: none;
953 }
954
955 /* avoid overwriting the top border line with the ToC header */
956 #toc {
957 padding-top: 1px;
958 }
959
960 /* Avoid page breaks inside dl and author address entries */
961 .vcard {
962 page-break-inside: avoid;
963 }
964
965 }
966 /* Tweak the bcp14 keyword presentation */
967 .bcp14 {
968 font-variant: small-caps;
969 font-weight: bold;
970 font-size: 0.9em;
971 }
972 /* Tweak the invisible space above H* in order not to overlay links in text above */
973 h2 {
974 margin-top: -18px; /* provide offset for in-page anchors */
975 padding-top: 31px;
976 }
977 h3 {
978 margin-top: -18px; /* provide offset for in-page anchors */
979 padding-top: 24px;
980 }
981 h4 {
982 margin-top: -18px; /* provide offset for in-page anchors */
983 padding-top: 24px;
984 }
985 /* Float artwork pilcrow to the right */
986 @media screen {
987 .artwork a.pilcrow {
988 display: block;
989 line-height: 0.7;
990 margin-top: 0.15em;
991 }
992 }
993 /* Make pilcrows on dd visible */
994 @media screen {
995 dd:hover > a.pilcrow {
996 visibility: visible;
997 }
998 }
999 /* Make the placement of figcaption match that of a table's caption
1000 by removing the figure's added bottom margin */
1001 .alignLeft.art-text,
1002 .alignCenter.art-text,
1003 .alignRight.art-text {
1004 margin-bottom: 0;
1005 }
1006 .alignLeft,
1007 .alignCenter,
1008 .alignRight {
1009 margin: 1em 0 0 0;
1010 }
1011 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
1012 possibly even requiring a new line */
1013 @media print {
1014 a.pilcrow {
1015 display: none;
1016 }
1017 }
1018 /* Styling for the external metadata */
1019 div#external-metadata {
1020 background-color: #eee;
1021 padding: 0.5em;
1022 margin-bottom: 0.5em;
1023 display: none;
1024 }
1025 div#internal-metadata {
1026 padding: 0.5em; /* to match the external-metadata padding */
1027 }
1028 /* Styling for title RFC Number */
1029 h1#rfcnum {
1030 clear: both;
1031 margin: 0 0 -1em;
1032 padding: 1em 0 0 0;
1033 }
1034 /* Make .olPercent look the same as <ol><li> */
1035 dl.olPercent > dd {
1036 margin-bottom: 0.25em;
1037 min-height: initial;
1038 }
1039 /* Give aside some styling to set it apart */
1040 aside {
1041 border-left: 1px solid #ddd;
1042 margin: 1em 0 1em 2em;
1043 padding: 0.2em 2em;
1044 }
1045 aside > dl,
1046 aside > ol,
1047 aside > ul,
1048 aside > table,
1049 aside > p {
1050 margin-bottom: 0.5em;
1051 }
1052 /* Additional page break settings */
1053 @media print {
1054 figcaption, table caption {
1055 page-break-before: avoid;
1056 }
1057 }
1058 /* Font size adjustments for print */
1059 @media print {
1060 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1061 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1062 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1063 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1064 h4 { font-size: 1em; padding-top: 1.5em; }
1065 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1066 }
1067 /* Sourcecode margin in print, when there's no pilcrow */
1068 @media print {
1069 .artwork,
1070 .sourcecode {
1071 margin-bottom: 1em;
1072 }
1073 }
1074 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1075 table {
1076 min-width: 20em;
1077 }
1078 /* ol type a */
1079 ol.type-a { list-style-type: lower-alpha; }
1080 ol.type-A { list-style-type: upper-alpha; }
1081 ol.type-i { list-style-type: lower-roman; }
1082 ol.type-I { list-style-type: lower-roman; }
1083 /* Apply the print table and row borders in general, on request from the RPC,
1084 and increase the contrast between border and odd row background sligthtly */
1085 table {
1086 border: 1px solid #ddd;
1087 }
1088 td {
1089 border-top: 1px solid #ddd;
1090 }
1091 tr:nth-child(2n+1) > td {
1092 background-color: #f8f8f8;
1093 }
1094 /* Use style rules to govern display of the TOC. */
1095 @media screen and (max-width: 1023px) {
1096 #toc nav { display: none; }
1097 #toc.active nav { display: block; }
1098 }
1099 /* Add support for keepWithNext */
1100 .keepWithNext {
1101 break-after: avoid-page;
1102 break-after: avoid-page;
1103 }
1104 /* Add support for keepWithPrevious */
1105 .keepWithPrevious {
1106 break-before: avoid-page;
1107 }
1108 /* Change the approach to avoiding breaks inside artwork etc. */
1109 figure, pre, table, .artwork, .sourcecode {
1110 break-before: avoid-page;
1111 break-after: auto;
1112 }
1113 /* Avoid breaks between <dt> and <dd> */
1114 dl {
1115 break-before: auto;
1116 break-inside: auto;
1117 }
1118 dt {
1119 break-before: auto;
1120 break-after: avoid-page;
1121 }
1122 dd {
1123 break-before: avoid-page;
1124 break-after: auto;
1125 orphans: 3;
1126 widows: 3
1127 }
1128 span.break, dd.break {
1129 margin-bottom: 0;
1130 min-height: 0;
1131 break-before: auto;
1132 break-inside: auto;
1133 break-after: auto;
1134 }
1135 /* Undo break-before ToC */
1136 @media print {
1137 #toc {
1138 break-before: auto;
1139 }
1140 }
1141 /* Text in compact lists should not get extra bottim margin space,
1142 since that would makes the list not compact */
1143 ul.compact p, .ulCompact p,
1144 ol.compact p, .olCompact p {
1145 margin: 0;
1146 }
1147 /* But the list as a whole needs the extra space at the end */
1148 section ul.compact,
1149 section .ulCompact,
1150 section ol.compact,
1151 section .olCompact {
1152 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1153 }
1154 /* The tt and code background above interferes with for instance table cell
1155 backgrounds. Changed to something a bit more selective. */
1156 tt, code {
1157 background-color: transparent;
1158 }
1159 p tt, p code, li tt, li code {
1160 background-color: #f8f8f8;
1161 }
1162 /* Tweak the pre margin -- 0px doesn't come out well */
1163 pre {
1164 margin-top: 0.5px;
1165 }
1166 /* Tweak the comact list text */
1167 ul.compact, .ulCompact,
1168 ol.compact, .olCompact,
1169 dl.compact, .dlCompact {
1170 line-height: normal;
1171 }
1172 /* Don't add top margin for nested lists */
1173 li > ul, li > ol, li > dl,
1174 dd > ul, dd > ol, dd > dl,
1175 dl > dd > dl {
1176 margin-top: initial;
1177 }
1178 /* Elements that should not be rendered on the same line as a <dt> */
1179 /* This should match the element list in writer.text.TextWriter.render_dl() */
1180 dd > div.artwork:first-child,
1181 dd > aside:first-child,
1182 dd > figure:first-child,
1183 dd > ol:first-child,
1184 dd > div:first-child > pre.sourcecode,
1185 dd > table:first-child,
1186 dd > ul:first-child {
1187 clear: left;
1188 }
1189 /* fix for weird browser behaviour when <dd/> is empty */
1190 dt+dd:empty::before{
1191 content: "\00a0";
1192 }
1193 /* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
1194 li > p {
1195 margin-bottom: 0.5em
1196 }
1197 /* Don't let p margin spill out from inside list items */
1198 li > p:last-of-type {
1199 margin-bottom: 0;
1200 }
1201 </style>
1202 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1203 <link href="https://dx.doi.org/10.17487/rfc9011" rel="alternate">
1204 <link href="urn:issn:2070-1721" rel="alternate">
1205 <link href="https://datatracker.ietf.org/doc/draft-ietf-lpwan-schc-over-lorawan-14" rel="prev">
1206 </head>
1207 <body>
1208 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1209 <table class="ears">
1210 <thead><tr>
1211 <td class="left">RFC 9011</td>
1212 <td class="center">SCHC over LoRaWAN</td>
1213 <td class="right">April 2021</td>
1214 </tr></thead>
1215 <tfoot><tr>
1216 <td class="left">Gimenez &amp; Petrov</td>
1217 <td class="center">Standards Track</td>
1218 <td class="right">[Page]</td>
1219 </tr></tfoot>
1220 </table>
1221 <div id="external-metadata" class="document-information"></div>
1222 <div id="internal-metadata" class="document-information">
1223 <dl id="identifiers">
1224 <dt class="label-stream">Stream:</dt>
1225 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1226 <dt class="label-rfc">RFC:</dt>
1227 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9011" class="eref">9011</a></dd>
1228 <dt class="label-category">Category:</dt>
1229 <dd class="category">Standards Track</dd>
1230 <dt class="label-published">Published:</dt>
1231 <dd class="published">
1232 <time datetime="2021-04" class="published">April 2021</time>
1233 </dd>
1234 <dt class="label-issn">ISSN:</dt>
1235 <dd class="issn">2070-1721</dd>
1236 <dt class="label-authors">Authors:</dt>
1237 <dd class="authors">
1238 <div class="author">
1239 <div class="author-name">O. Gimenez, <span class="editor">Ed.</span>
1240 </div>
1241 <div class="org">Semtech</div>
1242 </div>
1243 <div class="author">
1244 <div class="author-name">I. Petrov, <span class="editor">Ed.</span>
1245 </div>
1246 <div class="org">Acklio</div>
1247 </div>
1248 </dd>
1249 </dl>
1250 </div>
1251 <h1 id="rfcnum">RFC 9011</h1>
1252 <h1 id="title">Static Context Header Compression and Fragmentation (SCHC) over LoRaWAN</h1>
1253 <section id="section-abstract">
1254 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1255 <p id="section-abstract-1">The Static Context Header Compression and fragmentation (SCHC) specification (RFC 8724) describes
1256 generic header compression and fragmentation techniques for Low-Power
1257 Wide Area Network (LPWAN) technologies. SCHC is a generic mechanism
1258 designed for great flexibility so that it can be adapted for any of the
1259 LPWAN technologies.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1260 <p id="section-abstract-2">This document defines a profile of SCHC (RFC 8724) for use in
1261 LoRaWAN networks and provides elements such as efficient
1262 parameterization and modes of operation.<a href="#section-abstract-2" class="pilcrow">¶</a></p>
1263 </section>
1264 <div id="status-of-memo">
1265 <section id="section-boilerplate.1">
1266 <h2 id="name-status-of-this-memo">
1267 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1268 </h2>
1269 <p id="section-boilerplate.1-1">
1270 This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1271 <p id="section-boilerplate.1-2">
1272 This document is a product of the Internet Engineering Task Force
1273 (IETF). It represents the consensus of the IETF community. It has
1274 received public review and has been approved for publication by
1275 the Internet Engineering Steering Group (IESG). Further
1276 information on Internet Standards is available in Section 2 of
1277 RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1278 <p id="section-boilerplate.1-3">
1279 Information about the current status of this document, any
1280 errata, and how to provide feedback on it may be obtained at
1281 <span><a href="https://www.rfc-editor.org/info/rfc9011">https://www.rfc-editor.org/info/rfc9011</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1282 </section>
1283 </div>
1284 <div id="copyright">
1285 <section id="section-boilerplate.2">
1286 <h2 id="name-copyright-notice">
1287 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1288 </h2>
1289 <p id="section-boilerplate.2-1">
1290 Copyright (c) 2021 IETF Trust and the persons identified as the
1291 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1292 <p id="section-boilerplate.2-2">
1293 This document is subject to BCP 78 and the IETF Trust's Legal
1294 Provisions Relating to IETF Documents
1295 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1296 publication of this document. Please review these documents
1297 carefully, as they describe your rights and restrictions with
1298 respect to this document. Code Components extracted from this
1299 document must include Simplified BSD License text as described in
1300 Section 4.e of the Trust Legal Provisions and are provided without
1301 warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1302 </section>
1303 </div>
1304 <div id="toc">
1305 <section id="section-toc.1">
1306 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1307 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1308 </h2>
1309 <nav class="toc"><ul class="compact ulEmpty toc">
1310 <li class="compact ulEmpty toc" id="section-toc.1-1.1">
1311 <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>
1312 </li>
1313 <li class="compact ulEmpty toc" id="section-toc.1-1.2">
1314 <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>
1315 </li>
1316 <li class="compact ulEmpty toc" id="section-toc.1-1.3">
1317 <p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>.  <a href="#name-schc-overview" class="xref">SCHC Overview</a></p>
1318 </li>
1319 <li class="compact ulEmpty toc" id="section-toc.1-1.4">
1320 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-lorawan-architecture" class="xref">LoRaWAN Architecture</a></p>
1321 <ul class="compact ulEmpty toc">
1322 <li class="compact ulEmpty toc" id="section-toc.1-1.4.2.1">
1323 <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-device-classes-a-b-c-and-in" class="xref">Device Classes (A, B, C) and Interactions</a></p>
1324 </li>
1325 <li class="compact ulEmpty toc" id="section-toc.1-1.4.2.2">
1326 <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-device-addressing" class="xref">Device Addressing</a></p>
1327 </li>
1328 <li class="compact ulEmpty toc" id="section-toc.1-1.4.2.3">
1329 <p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>.  <a href="#name-general-frame-types" class="xref">General Frame Types</a></p>
1330 </li>
1331 <li class="compact ulEmpty toc" id="section-toc.1-1.4.2.4">
1332 <p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>.  <a href="#name-lorawan-mac-frames" class="xref">LoRaWAN MAC Frames</a></p>
1333 </li>
1334 <li class="compact ulEmpty toc" id="section-toc.1-1.4.2.5">
1335 <p id="section-toc.1-1.4.2.5.1"><a href="#section-4.5" class="xref">4.5</a>.  <a href="#name-lorawan-fport" class="xref">LoRaWAN FPort</a></p>
1336 </li>
1337 <li class="compact ulEmpty toc" id="section-toc.1-1.4.2.6">
1338 <p id="section-toc.1-1.4.2.6.1"><a href="#section-4.6" class="xref">4.6</a>.  <a href="#name-lorawan-empty-frame" class="xref">LoRaWAN Empty Frame</a></p>
1339 </li>
1340 <li class="compact ulEmpty toc" id="section-toc.1-1.4.2.7">
1341 <p id="section-toc.1-1.4.2.7.1"><a href="#section-4.7" class="xref">4.7</a>.  <a href="#name-unicast-and-multicast-techn" class="xref">Unicast and Multicast Technology</a></p>
1342 </li>
1343 </ul>
1344 </li>
1345 <li class="compact ulEmpty toc" id="section-toc.1-1.5">
1346 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-schc-over-lorawan" class="xref">SCHC over LoRaWAN</a></p>
1347 <ul class="compact ulEmpty toc">
1348 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.1">
1349 <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-lorawan-fport-and-ruleid" class="xref">LoRaWAN FPort and RuleID</a></p>
1350 </li>
1351 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.2">
1352 <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-ruleid-management" class="xref">RuleID Management</a></p>
1353 </li>
1354 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.3">
1355 <p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>.  <a href="#name-interface-identifier-iid-co" class="xref">Interface IDentifier (IID) Computation</a></p>
1356 </li>
1357 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.4">
1358 <p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>.  <a href="#name-padding" class="xref">Padding</a></p>
1359 </li>
1360 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.5">
1361 <p id="section-toc.1-1.5.2.5.1"><a href="#section-5.5" class="xref">5.5</a>.  <a href="#name-decompression" class="xref">Decompression</a></p>
1362 </li>
1363 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.6">
1364 <p id="section-toc.1-1.5.2.6.1"><a href="#section-5.6" class="xref">5.6</a>.  <a href="#name-fragmentation" class="xref">Fragmentation</a></p>
1365 <ul class="compact ulEmpty toc">
1366 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.6.2.1">
1367 <p id="section-toc.1-1.5.2.6.2.1.1"><a href="#section-5.6.1" class="xref">5.6.1</a>.  <a href="#name-dtag" class="xref">DTag</a></p>
1368 </li>
1369 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.6.2.2">
1370 <p id="section-toc.1-1.5.2.6.2.2.1"><a href="#section-5.6.2" class="xref">5.6.2</a>.  <a href="#name-uplink-fragmentation-from-d" class="xref">Uplink Fragmentation: From Device to SCHC Gateway</a></p>
1371 </li>
1372 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.6.2.3">
1373 <p id="section-toc.1-1.5.2.6.2.3.1"><a href="#section-5.6.3" class="xref">5.6.3</a>.  <a href="#name-downlink-fragmentation-from" class="xref">Downlink Fragmentation: From SCHC Gateway to Device</a></p>
1374 </li>
1375 </ul>
1376 </li>
1377 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.7">
1378 <p id="section-toc.1-1.5.2.7.1"><a href="#section-5.7" class="xref">5.7</a>.  <a href="#name-schc-fragment-format" class="xref">SCHC Fragment Format</a></p>
1379 <ul class="compact ulEmpty toc">
1380 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.7.2.1">
1381 <p id="section-toc.1-1.5.2.7.2.1.1"><a href="#section-5.7.1" class="xref">5.7.1</a>.  <a href="#name-all-0-schc-fragment" class="xref">All-0 SCHC Fragment</a></p>
1382 </li>
1383 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.7.2.2">
1384 <p id="section-toc.1-1.5.2.7.2.2.1"><a href="#section-5.7.2" class="xref">5.7.2</a>.  <a href="#name-all-1-schc-fragment" class="xref">All-1 SCHC Fragment</a></p>
1385 </li>
1386 <li class="compact ulEmpty toc" id="section-toc.1-1.5.2.7.2.3">
1387 <p id="section-toc.1-1.5.2.7.2.3.1"><a href="#section-5.7.3" class="xref">5.7.3</a>.  <a href="#name-delay-after-each-lorawan-fr" class="xref">Delay after Each LoRaWAN Frame to Respect Local Regulation</a></p>
1388 </li>
1389 </ul>
1390 </li>
1391 </ul>
1392 </li>
1393 <li class="compact ulEmpty toc" id="section-toc.1-1.6">
1394 <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>
1395 </li>
1396 <li class="compact ulEmpty toc" id="section-toc.1-1.7">
1397 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
1398 </li>
1399 <li class="compact ulEmpty toc" id="section-toc.1-1.8">
1400 <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-references" class="xref">References</a></p>
1401 <ul class="compact ulEmpty toc">
1402 <li class="compact ulEmpty toc" id="section-toc.1-1.8.2.1">
1403 <p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="xref">8.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
1404 </li>
1405 <li class="compact ulEmpty toc" id="section-toc.1-1.8.2.2">
1406 <p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="xref">8.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
1407 </li>
1408 </ul>
1409 </li>
1410 <li class="compact ulEmpty toc" id="section-toc.1-1.9">
1411 <p id="section-toc.1-1.9.1"><a href="#section-appendix.a" class="xref">Appendix A</a>.  <a href="#name-examples" class="xref">Examples</a></p>
1412 <ul class="compact ulEmpty toc">
1413 <li class="compact ulEmpty toc" id="section-toc.1-1.9.2.1">
1414 <p id="section-toc.1-1.9.2.1.1"><a href="#section-a.1" class="xref">A.1</a>.  <a href="#name-uplink-compression-example-" class="xref">Uplink - Compression Example - No Fragmentation</a></p>
1415 </li>
1416 <li class="compact ulEmpty toc" id="section-toc.1-1.9.2.2">
1417 <p id="section-toc.1-1.9.2.2.1"><a href="#section-a.2" class="xref">A.2</a>.  <a href="#name-uplink-compression-and-frag" class="xref">Uplink - Compression and Fragmentation Example</a></p>
1418 </li>
1419 <li class="compact ulEmpty toc" id="section-toc.1-1.9.2.3">
1420 <p id="section-toc.1-1.9.2.3.1"><a href="#section-a.3" class="xref">A.3</a>.  <a href="#name-downlink" class="xref">Downlink</a></p>
1421 </li>
1422 </ul>
1423 </li>
1424 <li class="compact ulEmpty toc" id="section-toc.1-1.10">
1425 <p id="section-toc.1-1.10.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
1426 </li>
1427 <li class="compact ulEmpty toc" id="section-toc.1-1.11">
1428 <p id="section-toc.1-1.11.1"><a href="#section-appendix.c" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a></p>
1429 </li>
1430 <li class="compact ulEmpty toc" id="section-toc.1-1.12">
1431 <p id="section-toc.1-1.12.1"><a href="#section-appendix.d" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
1432 </li>
1433 </ul>
1434 </nav>
1435 </section>
1436 </div>
1437 <div id="Introduction">
1438 <section id="section-1">
1439 <h2 id="name-introduction">
1440 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1441 </h2>
1442 <p id="section-1-1">The SCHC specification <span>[<a href="#RFC8724" class="xref">RFC8724</a>]</span> describes
1443 generic header compression and fragmentation techniques that can be used on all
1444 Low-Power Wide Area Network (LPWAN) technologies defined in
1445 <span>[<a href="#RFC8376" class="xref">RFC8376</a>]</span>. Even though those technologies share a great
1446 number of common features like star-oriented topologies, network architecture,
1447 devices with communications that are mostly quite predictable, etc., they do have some
1448 slight differences with respect to payload sizes, reactiveness, etc.<a href="#section-1-1" class="pilcrow">¶</a></p>
1449 <p id="section-1-2">SCHC provides a generic framework that enables those devices to communicate on
1450 IP networks. However, for efficient performance, some parameters
1451 and modes of operation need to be set appropriately for each of the LPWAN
1452 technologies.<a href="#section-1-2" class="pilcrow">¶</a></p>
1453 <p id="section-1-3">This document describes the parameters and modes of operation when
1454 SCHC is used over LoRaWAN networks. The LoRaWAN protocol is specified by
1455 the LoRa Alliance in <span>[<a href="#LORAWAN-SPEC" class="xref">LORAWAN-SPEC</a>]</span>.<a href="#section-1-3" class="pilcrow">¶</a></p>
1456 </section>
1457 </div>
1458 <div id="terminology">
1459 <section id="section-2">
1460 <h2 id="name-terminology">
1461 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
1462 </h2>
1463 <p id="section-2-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>",
1464 "<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>",
1465 "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
1466 "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are
1467 to be interpreted as described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and
1468 only when, they appear in all capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p>
1469 <p id="section-2-2">This section defines the terminology and abbreviations used in this document. For
1470 all other definitions, please look up the SCHC specification
1471 <span>[<a href="#RFC8724" class="xref">RFC8724</a>]</span>.<a href="#section-2-2" class="pilcrow">¶</a></p>
1472 <aside id="section-2-3">
1473 <p id="section-2-3.1">
1474 Note: The SCHC acronym is pronounced like "sheek" in English (or "chic" in French).
1475 Therefore, this document writes "a SCHC Packet" instead of "an SCHC Packet".<a href="#section-2-3.1" class="pilcrow">¶</a></p>
1476 </aside>
1477 <span class="break"></span><dl class="dlParallel" id="section-2-4">
1478 <dt id="section-2-4.1">AppKey:
1479 </dt>
1480 <dd style="margin-left: 1.5em" id="section-2-4.2">Application Key. An AES-128 root key specific to each device.<a href="#section-2-4.2" class="pilcrow">¶</a>
1481 </dd>
1482 <dd class="break"></dd>
1483 <dt id="section-2-4.3">AppSKey:
1484 </dt>
1485 <dd style="margin-left: 1.5em" id="section-2-4.4">Application Session Key. An AES-128 key derived from the AppKey for
1486 each new session. It is used to encrypt the payload field of a LoRaWAN
1487 applicative frame.<a href="#section-2-4.4" class="pilcrow">¶</a>
1488 </dd>
1489 <dd class="break"></dd>
1490 <dt id="section-2-4.5">DevAddr:
1491 </dt>
1492 <dd style="margin-left: 1.5em" id="section-2-4.6">
1493 <p id="section-2-4.6.1">A 32-bit non-unique identifier assigned to a device either:<a href="#section-2-4.6.1" class="pilcrow">¶</a></p>
1494 <span class="break"></span><dl class="dlParallel" id="section-2-4.6.2">
1495 <dt id="section-2-4.6.2.1">Statically:
1496 </dt>
1497 <dd style="margin-left: 1.5em" id="section-2-4.6.2.2">by the device manufacturer in "Activation-by-Personalization"
1498 mode, or<a href="#section-2-4.6.2.2" class="pilcrow">¶</a>
1499 </dd>
1500 <dd class="break"></dd>
1501 <dt id="section-2-4.6.2.3">Dynamically:
1502 </dt>
1503 <dd style="margin-left: 1.5em" id="section-2-4.6.2.4">after a LoRaWAN "Join Procedure" by the Network Gateway in "Over-the-Air-Activation" mode.<a href="#section-2-4.6.2.4" class="pilcrow">¶</a>
1504 </dd>
1505 <dd class="break"></dd>
1506 </dl>
1507 </dd>
1508 <dd class="break"></dd>
1509 <dt id="section-2-4.7">DevEUI:
1510 </dt>
1511 <dd style="margin-left: 1.5em" id="section-2-4.8">Device Extended Unique Identifier, an IEEE EUI-64 identifier used to
1512 identify the device during the procedure while joining the network (Join
1513 Procedure). It is assigned by the manufacturer or the device owner and
1514 provisioned on the Network Gateway.<a href="#section-2-4.8" class="pilcrow">¶</a>
1515 </dd>
1516 <dd class="break"></dd>
1517 <dt id="section-2-4.9">Downlink:
1518 </dt>
1519 <dd style="margin-left: 1.5em" id="section-2-4.10">A LoRaWAN term for a frame transmitted by the network and received by the device.<a href="#section-2-4.10" class="pilcrow">¶</a>
1520 </dd>
1521 <dd class="break"></dd>
1522 <dt id="section-2-4.11">EUI:
1523 </dt>
1524 <dd style="margin-left: 1.5em" id="section-2-4.12">Extended Unique Identifier<a href="#section-2-4.12" class="pilcrow">¶</a>
1525 </dd>
1526 <dd class="break"></dd>
1527 <dt id="section-2-4.13">FRMPayload:
1528 </dt>
1529 <dd style="margin-left: 1.5em" id="section-2-4.14">Application data in a LoRaWAN frame<a href="#section-2-4.14" class="pilcrow">¶</a>
1530 </dd>
1531 <dd class="break"></dd>
1532 <dt id="section-2-4.15">IID:
1533 </dt>
1534 <dd style="margin-left: 1.5em" id="section-2-4.16">Interface Identifier<a href="#section-2-4.16" class="pilcrow">¶</a>
1535 </dd>
1536 <dd class="break"></dd>
1537 <dt id="section-2-4.17">LoRaWAN:
1538 </dt>
1539 <dd style="margin-left: 1.5em" id="section-2-4.18">LoRaWAN is a wireless technology based on Industrial, Scientific, and
1540 Medical (ISM) radio bands that is used for long-range, low-power,
1541 low-data-rate applications developed by the LoRa Alliance, a membership
1542 consortium: <span>&lt;<a href="https://www.lora-alliance.org">https://www.lora-alliance.org</a>&gt;</span>.<a href="#section-2-4.18" class="pilcrow">¶</a>
1543 </dd>
1544 <dd class="break"></dd>
1545 <dt id="section-2-4.19">MSB:
1546 </dt>
1547 <dd style="margin-left: 1.5em" id="section-2-4.20">Most Significant Byte<a href="#section-2-4.20" class="pilcrow">¶</a>
1548 </dd>
1549 <dd class="break"></dd>
1550 <dt id="section-2-4.21">NGW:
1551 </dt>
1552 <dd style="margin-left: 1.5em" id="section-2-4.22">Network Gateway<a href="#section-2-4.22" class="pilcrow">¶</a>
1553 </dd>
1554 <dd class="break"></dd>
1555 <dt id="section-2-4.23">OUI:
1556 </dt>
1557 <dd style="margin-left: 1.5em" id="section-2-4.24">Organizationally Unique Identifier. IEEE-assigned prefix for EUI.<a href="#section-2-4.24" class="pilcrow">¶</a>
1558 </dd>
1559 <dd class="break"></dd>
1560 <dt id="section-2-4.25">RCS:
1561 </dt>
1562 <dd style="margin-left: 1.5em" id="section-2-4.26">Reassembly Check Sequence. Used to verify the integrity of the fragmentation-reassembly process.<a href="#section-2-4.26" class="pilcrow">¶</a>
1563 </dd>
1564 <dd class="break"></dd>
1565 <dt id="section-2-4.27">RGW:
1566 </dt>
1567 <dd style="margin-left: 1.5em" id="section-2-4.28">Radio Gateway<a href="#section-2-4.28" class="pilcrow">¶</a>
1568 </dd>
1569 <dd class="break"></dd>
1570 <dt id="section-2-4.29">RX:
1571 </dt>
1572 <dd style="margin-left: 1.5em" id="section-2-4.30">A device's reception window.<a href="#section-2-4.30" class="pilcrow">¶</a>
1573 </dd>
1574 <dd class="break"></dd>
1575 <dt id="section-2-4.31">RX1/RX2:
1576 </dt>
1577 <dd style="margin-left: 1.5em" id="section-2-4.32">LoRaWAN class A devices open two RX windows following an uplink, called "RX1" and "RX2".<a href="#section-2-4.32" class="pilcrow">¶</a>
1578 </dd>
1579 <dd class="break"></dd>
1580 <dt id="section-2-4.33">SCHC C/D:
1581 </dt>
1582 <dd style="margin-left: 1.5em" id="section-2-4.34">SCHC Compression/Decompression<a href="#section-2-4.34" class="pilcrow">¶</a>
1583 </dd>
1584 <dd class="break"></dd>
1585 <dt id="section-2-4.35">SCHC F/R:
1586 </dt>
1587 <dd style="margin-left: 1.5em" id="section-2-4.36">SCHC Fragmentation/Reassembly<a href="#section-2-4.36" class="pilcrow">¶</a>
1588 </dd>
1589 <dd class="break"></dd>
1590 <dt id="section-2-4.37">SCHC gateway:
1591 </dt>
1592 <dd style="margin-left: 1.5em" id="section-2-4.38">The LoRaWAN Application Server that manages translation between an IPv6
1593 network and the Network Gateway (LoRaWAN Network Server).<a href="#section-2-4.38" class="pilcrow">¶</a>
1594 </dd>
1595 <dd class="break"></dd>
1596 <dt id="section-2-4.39">Tile:
1597 </dt>
1598 <dd style="margin-left: 1.5em" id="section-2-4.40">A piece of a fragmented packet as described in <span><a href="https://www.rfc-editor.org/rfc/rfc8724#section-8.2.2.1" class="relref">Section 8.2.2.1</a> of [<a href="#RFC8724" class="xref">RFC8724</a>]</span>.<a href="#section-2-4.40" class="pilcrow">¶</a>
1599 </dd>
1600 <dd class="break"></dd>
1601 <dt id="section-2-4.41">Uplink:
1602 </dt>
1603 <dd style="margin-left: 1.5em" id="section-2-4.42">LoRaWAN term for a frame transmitted by the device and received by the network.<a href="#section-2-4.42" class="pilcrow">¶</a>
1604 </dd>
1605 <dd class="break"></dd>
1606 </dl>
1607 </section>
1608 </div>
1609 <div id="static-context-header-compression-overview">
1610 <section id="section-3">
1611 <h2 id="name-schc-overview">
1612 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-schc-overview" class="section-name selfRef">SCHC Overview</a>
1613 </h2>
1614 <p id="section-3-1">This section contains a short overview of SCHC. For a detailed
1615 description, refer to the full specification <span>[<a href="#RFC8724" class="xref">RFC8724</a>]</span>.<a href="#section-3-1" class="pilcrow">¶</a></p>
1616 <p id="section-3-2">It defines:<a href="#section-3-2" class="pilcrow">¶</a></p>
1617 <ol start="1" type="1" class="normal type-1" id="section-3-3">
1618 <li id="section-3-3.1">Compression mechanisms to avoid
1619 transporting information known by both sender and receiver over the
1620 air. Known information is part of the "context". This component is
1621 called the "SCHC Compression/Decompression" (SCHC C/D).<a href="#section-3-3.1" class="pilcrow">¶</a>
1622 </li>
1623 <li id="section-3-3.2">Fragmentation mechanisms to allow SCHC Packet transportation on a
1624 small, and potentially variable, MTU. This component is called the "SCHC
1625 Fragmentation/Reassembly" (SCHC F/R).<a href="#section-3-3.2" class="pilcrow">¶</a>
1626 </li>
1627 </ol>
1628 <p id="section-3-4">Context exchange or pre-provisioning is out of scope of this document.<a href="#section-3-4" class="pilcrow">¶</a></p>
1629 <span id="name-architecture"></span><div id="Fig-archi">
1630 <figure id="figure-1">
1631 <div class="artwork art-text alignLeft" id="section-3-5.1">
1632 <pre>
1633 Device App
1634 +----------------+ +----+ +----+ +----+
1635 | App1 App2 App3 | |App1| |App2| |App3|
1636 | | | | | | | |
1637 | UDP | |UDP | |UDP | |UDP |
1638 | IPv6 | |IPv6| |IPv6| |IPv6|
1639 | | | | | | | |
1640 |SCHC C/D and F/R| | | | | | |
1641 +--------+-------+ +----+ +----+ +----+
1642 | +---+ +----+ +----+ +----+ . . .
1643 +~ |RGW| === |NGW | == |SCHC| == |SCHC|...... Internet ....
1644 +---+ +----+ |F/R | |C/D |
1645 +----+ +----+
1646 |&lt;- - - - LoRaWAN - - -&gt;|
1647 </pre>
1648 </div>
1649 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
1650 <a href="#name-architecture" class="selfRef">Architecture</a>
1651 </figcaption></figure>
1652 </div>
1653 <p id="section-3-6"><a href="#Fig-archi" class="xref">Figure 1</a> represents the
1654 architecture for compression/decompression; it is based on the terminology from <span>[<a href="#RFC8376" class="xref">RFC8376</a>]</span>. The device is sending
1655 application flows using IPv6 or IPv6/UDP protocols. These flows might
1656 be compressed by a SCHC C/D to reduce header size, and fragmented
1657 by the SCHC F/R. The resulting
1658 information is sent on a Layer 2 (L2) frame to an LPWAN Radio Gateway
1659 (RGW) that forwards the frame to a Network Gateway (NGW). The NGW sends
1660 the data to a SCHC F/R for reassembly, if required, then to a SCHC C/D for
1661 decompression. The SCHC C/D shares the same rules with the device. The
1662 SCHC C/D and SCHC F/R can be located on the NGW or in
1663 another place as long as a communication is established between the NGW
1664 and the SCHC F/R, then SCHC F/R and SCHC C/D. The SCHC C/D and SCHC F/R in the
1665 device and the SCHC gateway <span class="bcp14">MUST</span> share the same set of
1666 rules. After decompression, the packet can be sent on the Internet to
1667 one or several LPWAN Application Servers (App).<a href="#section-3-6" class="pilcrow">¶</a></p>
1668 <p id="section-3-7">The SCHC C/D and SCHC F/R process is bidirectional, so the same principles
1669 can be applied to the other direction.<a href="#section-3-7" class="pilcrow">¶</a></p>
1670 <p id="section-3-8">In a LoRaWAN network, the RGW is called a "Gateway", the NGW is a
1671 "Network Server", and the SCHC C/D and SCHC F/R are one or more
1672 "Application Servers".
1673
1674 Application servers can be provided by the NGW or any third-party
1675 software. <a href="#Fig-archi" class="xref">Figure 1</a> can be mapped in
1676 LoRaWAN terminology to:<a href="#section-3-8" class="pilcrow">¶</a></p>
1677 <span id="name-schc-architecture-mapped-to"></span><div id="Fig-archi-lorawan">
1678 <figure id="figure-2">
1679 <div class="artwork art-text alignLeft" id="section-3-9.1">
1680 <pre>
1681 End Device App
1682 +--------------+ +----+ +----+ +----+
1683 |App1 App2 App3| |App1| |App2| |App3|
1684 | | | | | | | |
1685 | UDP | |UDP | |UDP | |UDP |
1686 | IPv6 | |IPv6| |IPv6| |IPv6|
1687 | | | | | | | |
1688 |SCHC C/D &amp; F/R| | | | | | |
1689 +-------+------+ +----+ +----+ +----+
1690 | +-------+ +-------+ +-----------+ . . .
1691 +~ |Gateway| == |Network| == |Application|..... Internet ....
1692 +-------+ |server | |server |
1693 +-------+ | F/R - C/D |
1694 +-----------+
1695 |&lt;- - - - - LoRaWAN - - - -&gt;|
1696 </pre>
1697 </div>
1698 <figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
1699 <a href="#name-schc-architecture-mapped-to" class="selfRef">SCHC Architecture Mapped to LoRaWAN</a>
1700 </figcaption></figure>
1701 </div>
1702 </section>
1703 </div>
1704 <div id="lorawan-architecture">
1705 <section id="section-4">
1706 <h2 id="name-lorawan-architecture">
1707 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-lorawan-architecture" class="section-name selfRef">LoRaWAN Architecture</a>
1708 </h2>
1709 <p id="section-4-1">An overview of the LoRaWAN protocol and architecture <span>[<a href="#LORAWAN-SPEC" class="xref">LORAWAN-SPEC</a>]</span> is described in <span>[<a href="#RFC8376" class="xref">RFC8376</a>]</span>. The mapping between the LPWAN
1710 architecture entities as described in <span>[<a href="#RFC8724" class="xref">RFC8724</a>]</span> and the ones in <span>[<a href="#LORAWAN-SPEC" class="xref">LORAWAN-SPEC</a>]</span> is as follows:<a href="#section-4-1" class="pilcrow">¶</a></p>
1711 <ul class="normal">
1712 <li class="normal" id="section-4-2.1">Devices are LoRaWAN End Devices (e.g., sensors, actuators, etc.). There
1713 can be a very high density of devices per radio gateway (LoRaWAN
1714 gateway). This entity maps to the LoRaWAN end device.<a href="#section-4-2.1" class="pilcrow">¶</a>
1715 </li>
1716 <li class="normal" id="section-4-2.2">The RGW is the endpoint of the constrained
1717 link. This entity maps to the LoRaWAN Gateway.<a href="#section-4-2.2" class="pilcrow">¶</a>
1718 </li>
1719 <li class="normal" id="section-4-2.3">The NGW is the interconnection node between the Radio
1720 Gateway and the SCHC gateway (LoRaWAN Application Server). This entity maps to
1721 the LoRaWAN Network Server.<a href="#section-4-2.3" class="pilcrow">¶</a>
1722 </li>
1723 <li class="normal" id="section-4-2.4">The SCHC C/D and SCHC F/R are handled by the LoRaWAN Application Server.<a href="#section-4-2.4" class="pilcrow">¶</a>
1724 </li>
1725 <li class="normal" id="section-4-2.5">The LPWAN-AAA Server is the LoRaWAN Join Server. Its role is to manage and
1726 deliver security keys in a secure way so that the devices root key is never
1727 exposed.<a href="#section-4-2.5" class="pilcrow">¶</a>
1728 </li>
1729 </ul>
1730 <span id="name-lpwan-architecture"></span><div id="Fig-LPWANarchi">
1731 <figure id="figure-3">
1732 <div class="artwork art-text alignLeft" id="section-4-3.1">
1733 <pre>
1734 (LPWAN-AAA Server)
1735 () () () | +------+
1736 () () () () / \ +---------+ | Join |
1737 () () () () () / \======| ^ |===|Server| +-----------+
1738 () () () | | &lt;--|--&gt; | +------+ |Application|
1739 () () () () / \==========| v |=============| Server |
1740 () () () / \ +---------+ +-----------+
1741 End devices Gateways Network Server (SCHC C/D and F/R)
1742 (devices) (RGW) (NGW)
1743 </pre>
1744 </div>
1745 <figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
1746 <a href="#name-lpwan-architecture" class="selfRef">LPWAN Architecture</a>
1747 </figcaption></figure>
1748 </div>
1749 <aside id="section-4-4">
1750 <p id="section-4-4.1">Note: <a href="#Fig-LPWANarchi" class="xref">Figure 3</a> terms
1751 are from LoRaWAN, with <span>[<a href="#RFC8376" class="xref">RFC8376</a>]</span>
1752 terminology in brackets.<a href="#section-4-4.1" class="pilcrow">¶</a></p>
1753 </aside>
1754 <p id="section-4-5">The SCHC C/D and SCHC F/R are performed on the LoRaWAN end
1755 device and the Application Server (called the SCHC gateway). While the
1756 point-to-point link between the device and the Application Server
1757 constitutes a single IP hop, the ultimate endpoint of the IP
1758 communication may be an Internet node beyond the Application Server. In
1759 other words, the LoRaWAN Application Server (SCHC gateway) acts as the
1760 first-hop IP router for the device. The Application Server and Network
1761 Server may be co-located, which effectively turns the
1762 Network/Application Server into the first-hop IP router.<a href="#section-4-5" class="pilcrow">¶</a></p>
1763 <div id="device-classes-a-b-c-and-interactions">
1764 <section id="section-4.1">
1765 <h3 id="name-device-classes-a-b-c-and-in">
1766 <a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-device-classes-a-b-c-and-in" class="section-name selfRef">Device Classes (A, B, C) and Interactions</a>
1767 </h3>
1768 <p id="section-4.1-1">The LoRaWAN Medium Access Control (MAC) layer supports three
1769 classes of devices named A, B, and C. All devices implement Class
1770 A, and some devices may implement Class B or Class C. Class B and Class C
1771 are mutually exclusive.<a href="#section-4.1-1" class="pilcrow">¶</a></p>
1772 <span class="break"></span><dl class="dlParallel" id="section-4.1-2">
1773 <dt id="section-4.1-2.1">Class A:
1774 </dt>
1775 <dd style="margin-left: 1.5em" id="section-4.1-2.2">Class A is the simplest class of devices. The device is allowed to
1776 transmit at any time, randomly selecting a communication channel. The Network
1777 Gateway may reply with a downlink in one of the two receive windows immediately
1778 following the uplinks. Therefore, the Network Gateway cannot initiate a
1779 downlink; it has to wait for the next uplink from the device to get a downlink
1780 opportunity. Class A is the lowest power consumption class.<a href="#section-4.1-2.2" class="pilcrow">¶</a>
1781 </dd>
1782 <dd class="break"></dd>
1783 <dt id="section-4.1-2.3">Class B:
1784 </dt>
1785 <dd style="margin-left: 1.5em" id="section-4.1-2.4">
1786 <p id="section-4.1-2.4.1">Class B devices implement all the functionalities of Class A devices but
1787 also schedule periodic listen windows. Therefore, as opposed to Class A
1788 devices, Class B devices can receive downlinks that are initiated by the
1789 Network Gateway and not following an uplink. There is a trade-off between the
1790 periodicity of those scheduled Class B listen windows and the power
1791 consumption of the device:<a href="#section-4.1-2.4.1" class="pilcrow">¶</a></p>
1792 <span class="break"></span><dl class="dlParallel" id="section-4.1-2.4.2">
1793 <dt id="section-4.1-2.4.2.1">High periodicity:</dt>
1794 <dd style="margin-left: 1.5em" id="section-4.1-2.4.2.2">Downlinks from the NGW will be sent faster but the device wakes up more
1795 often and power consumption is increased.<a href="#section-4.1-2.4.2.2" class="pilcrow">¶</a>
1796 </dd>
1797 <dd class="break"></dd>
1798 <dt id="section-4.1-2.4.2.3">Low periodicity:</dt>
1799 <dd style="margin-left: 1.5em" id="section-4.1-2.4.2.4">Downlinks from the NGW will have higher latency but lower power consumption.<a href="#section-4.1-2.4.2.4" class="pilcrow">¶</a>
1800 </dd>
1801 <dd class="break"></dd>
1802 </dl>
1803 </dd>
1804 <dd class="break"></dd>
1805 <dt id="section-4.1-2.5">Class C:
1806 </dt>
1807 <dd style="margin-left: 1.5em" id="section-4.1-2.6">Class C devices implement all the functionalities of Class A devices but
1808 keep their receiver open whenever they are not transmitting. Class C devices
1809 can receive downlinks at any time at the expense of a higher power
1810 consumption. Battery-powered devices can only operate in Class C for a limited
1811 amount of time (for example, for a firmware upgrade over-the-air). Most of the
1812 Class C devices are grid powered (for example, Smart Plugs).<a href="#section-4.1-2.6" class="pilcrow">¶</a>
1813 </dd>
1814 <dd class="break"></dd>
1815 </dl>
1816 </section>
1817 </div>
1818 <div id="device-addressing">
1819 <section id="section-4.2">
1820 <h3 id="name-device-addressing">
1821 <a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-device-addressing" class="section-name selfRef">Device Addressing</a>
1822 </h3>
1823 <p id="section-4.2-1">LoRaWAN end devices use a 32-bit network address (DevAddr) to
1824 communicate with the Network Gateway over the air; this address might
1825 not be unique in a LoRaWAN network. Devices using the same DevAddr are
1826 distinguished by the Network Gateway based on the cryptographic
1827 signature appended to every LoRaWAN frame.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
1828 <p id="section-4.2-2">To communicate with the SCHC gateway, the Network Gateway
1829 <span class="bcp14">MUST</span> identify the devices by a unique 64-bit device
1830 identifier called the "DevEUI".<a href="#section-4.2-2" class="pilcrow">¶</a></p>
1831 <p id="section-4.2-3">The DevEUI is assigned to the device during the manufacturing
1832 process by the device's manufacturer. It is built like an Ethernet MAC
1833 address by concatenating the manufacturer's IEEE OUI field with a
1834 vendor unique number. For example, a 24-bit OUI is concatenated with a 40-bit
1835 serial number. The Network Gateway translates the DevAddr into a
1836 DevEUI in the uplink direction and reciprocally on the downlink
1837 direction.<a href="#section-4.2-3" class="pilcrow">¶</a></p>
1838 <span id="name-lorawan-addresses"></span><div id="Fig-LoRaWANaddresses">
1839 <figure id="figure-4">
1840 <div class="artwork art-text alignLeft" id="section-4.2-4.1">
1841 <pre>
1842 +--------+ +---------+ +---------+ +----------+
1843 | Device | &lt;=====&gt; | Network | &lt;====&gt; | SCHC | &lt;======&gt; | Internet |
1844 | | DevAddr | Gateway | DevEUI | Gateway | IPv6/UDP | |
1845 +--------+ +---------+ +---------+ +----------+
1846 </pre>
1847 </div>
1848 <figcaption><a href="#figure-4" class="selfRef">Figure 4</a>:
1849 <a href="#name-lorawan-addresses" class="selfRef">LoRaWAN Addresses</a>
1850 </figcaption></figure>
1851 </div>
1852 </section>
1853 </div>
1854 <div id="general-frame-types">
1855 <section id="section-4.3">
1856 <h3 id="name-general-frame-types">
1857 <a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-general-frame-types" class="section-name selfRef">General Frame Types</a>
1858 </h3>
1859 <p id="section-4.3-1">LoRaWAN implements the possibility to send confirmed or unconfirmed frames:<a href="#section-4.3-1" class="pilcrow">¶</a></p>
1860 <span class="break"></span><dl class="dlParallel" id="section-4.3-2">
1861 <dt id="section-4.3-2.1">Confirmed frame:
1862 </dt>
1863 <dd style="margin-left: 1.5em" id="section-4.3-2.2">The sender asks the receiver to acknowledge the frame.<a href="#section-4.3-2.2" class="pilcrow">¶</a>
1864 </dd>
1865 <dd class="break"></dd>
1866 <dt id="section-4.3-2.3">Unconfirmed frame:
1867 </dt>
1868 <dd style="margin-left: 1.5em" id="section-4.3-2.4">The sender does not ask the receiver to acknowledge the frame.<a href="#section-4.3-2.4" class="pilcrow">¶</a>
1869 </dd>
1870 <dd class="break"></dd>
1871 </dl>
1872 <p id="section-4.3-3">As SCHC defines its own acknowledgment mechanisms, SCHC does not require
1873 the use of LoRaWAN Confirmed frames (FType = 0b100 as per
1874 <span>[<a href="#LORAWAN-SPEC" class="xref">LORAWAN-SPEC</a>]</span>).<a href="#section-4.3-3" class="pilcrow">¶</a></p>
1875 </section>
1876 </div>
1877 <div id="lorawan-mac-frames">
1878 <section id="section-4.4">
1879 <h3 id="name-lorawan-mac-frames">
1880 <a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-lorawan-mac-frames" class="section-name selfRef">LoRaWAN MAC Frames</a>
1881 </h3>
1882 <p id="section-4.4-1">In addition to regular data frames, LoRaWAN implements JoinRequest and JoinAccept
1883 frame types, which are used by a device to join a network:<a href="#section-4.4-1" class="pilcrow">¶</a></p>
1884 <span class="break"></span><dl class="dlParallel" id="section-4.4-2">
1885 <dt id="section-4.4-2.1">JoinRequest:
1886 </dt>
1887 <dd style="margin-left: 1.5em" id="section-4.4-2.2">This frame is used by a device to join a network. It contains the device's
1888 unique identifier DevEUI and a random nonce that will be used for session key
1889 derivation.<a href="#section-4.4-2.2" class="pilcrow">¶</a>
1890 </dd>
1891 <dd class="break"></dd>
1892 <dt id="section-4.4-2.3">JoinAccept:
1893 </dt>
1894 <dd style="margin-left: 1.5em" id="section-4.4-2.4">To onboard a device, the Network Gateway responds to the JoinRequest
1895 issued by a device with a JoinAccept frame. That frame is encrypted with the
1896 device's AppKey and contains (among other fields) the network's major
1897 settings and a random nonce used to derive the session keys.<a href="#section-4.4-2.4" class="pilcrow">¶</a>
1898 </dd>
1899 <dd class="break"></dd>
1900 <dt id="section-4.4-2.5">Data:
1901 </dt>
1902 <dd style="margin-left: 1.5em" id="section-4.4-2.6">This refers to MAC and application data. Application data is protected with AES-128
1903 encryption. MAC-related data is AES-128 encrypted with another key.<a href="#section-4.4-2.6" class="pilcrow">¶</a>
1904 </dd>
1905 <dd class="break"></dd>
1906 </dl>
1907 </section>
1908 </div>
1909 <div id="lorawan-fport">
1910 <section id="section-4.5">
1911 <h3 id="name-lorawan-fport">
1912 <a href="#section-4.5" class="section-number selfRef">4.5. </a><a href="#name-lorawan-fport" class="section-name selfRef">LoRaWAN FPort</a>
1913 </h3>
1914 <p id="section-4.5-1">The LoRaWAN MAC layer features a frame port field in all frames. This field
1915 (FPort) is 8 bits long and the values from 1 to 223 can be used. It allows
1916 LoRaWAN networks and applications to identify data.<a href="#section-4.5-1" class="pilcrow">¶</a></p>
1917 </section>
1918 </div>
1919 <div id="lorawan-empty-frame">
1920 <section id="section-4.6">
1921 <h3 id="name-lorawan-empty-frame">
1922 <a href="#section-4.6" class="section-number selfRef">4.6. </a><a href="#name-lorawan-empty-frame" class="section-name selfRef">LoRaWAN Empty Frame</a>
1923 </h3>
1924 <p id="section-4.6-1">A LoRaWAN empty frame is a LoRaWAN frame without FPort (cf. <a href="#lorawan-schc-payload" class="xref">Section 5.1</a>) and FRMPayload.<a href="#section-4.6-1" class="pilcrow">¶</a></p>
1925 </section>
1926 </div>
1927 <div id="unicast-and-multicast-technology">
1928 <section id="section-4.7">
1929 <h3 id="name-unicast-and-multicast-techn">
1930 <a href="#section-4.7" class="section-number selfRef">4.7. </a><a href="#name-unicast-and-multicast-techn" class="section-name selfRef">Unicast and Multicast Technology</a>
1931 </h3>
1932 <p id="section-4.7-1">LoRaWAN technology supports unicast downlinks but also multicast; a
1933 multicast packet sent over a LoRaWAN radio link can be received by several
1934 devices. It is useful to address many devices with the same content:
1935 either a large binary file (firmware upgrade) or the same command (e.g.,
1936 lighting control). As IPv6 is also a multicast technology, this
1937 feature can be used to address a group of devices.<a href="#section-4.7-1" class="pilcrow">¶</a></p>
1938 <aside id="section-4.7-2">
1939 <p id="section-4.7-2.1">Note 1: IPv6 multicast addresses must be defined as per
1940 <span>[<a href="#RFC4291" class="xref">RFC4291</a>]</span>. The LoRaWAN multicast group
1941 definition in a Network Gateway and the relation between those groups
1942 and IPv6 groupID are out of scope of this document.<a href="#section-4.7-2.1" class="pilcrow">¶</a></p>
1943 </aside>
1944 <aside id="section-4.7-3">
1945 <p id="section-4.7-3.1">Note 2: The LoRa Alliance defined <span>[<a href="#LORAWAN-REMOTE-MULTICAST-SET" class="xref">LORAWAN-REMOTE-MULTICAST-SET</a>]</span> as the
1946 <span class="bcp14">RECOMMENDED</span> way to set up multicast groups on devices
1947 and create a synchronized reception window.<a href="#section-4.7-3.1" class="pilcrow">¶</a></p>
1948 </aside>
1949 </section>
1950 </div>
1951 </section>
1952 </div>
1953 <div id="schc-over-lorawan">
1954 <section id="section-5">
1955 <h2 id="name-schc-over-lorawan">
1956 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-schc-over-lorawan" class="section-name selfRef">SCHC over LoRaWAN</a>
1957 </h2>
1958 <div id="lorawan-schc-payload">
1959 <section id="section-5.1">
1960 <h3 id="name-lorawan-fport-and-ruleid">
1961 <a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-lorawan-fport-and-ruleid" class="section-name selfRef">LoRaWAN FPort and RuleID</a>
1962 </h3>
1963 <p id="section-5.1-1">The FPort field is part of the SCHC Message, as shown in
1964 <a href="#Fig-lorawan-schc-payload" class="xref">Figure 5</a>. The SCHC C/D and the SCHC F/R <span class="bcp14">SHALL</span> concatenate
1965 the FPort field with the LoRaWAN payload to recompose the SCHC Message.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
1966 <span id="name-schc-message-in-lorawan"></span><div id="Fig-lorawan-schc-payload">
1967 <figure id="figure-5">
1968 <div class="artwork art-text alignLeft" id="section-5.1-2.1">
1969 <pre>
1970 | FPort | LoRaWAN payload |
1971 + ------------------------ +
1972 | SCHC Message |
1973 </pre>
1974 </div>
1975 <figcaption><a href="#figure-5" class="selfRef">Figure 5</a>:
1976 <a href="#name-schc-message-in-lorawan" class="selfRef">SCHC Message in LoRaWAN</a>
1977 </figcaption></figure>
1978 </div>
1979 <aside id="section-5.1-3">
1980 <p id="section-5.1-3.1">Note: The SCHC Message is any datagram sent by the SCHC C/D or F/R layers.<a href="#section-5.1-3.1" class="pilcrow">¶</a></p>
1981 </aside>
1982 <p id="section-5.1-4">A fragmented datagram with application payload transferred from device to
1983 Network Gateway is called an "uplink-fragmented datagram". It uses an FPort for data uplink
1984 and its associated SCHC control downlinks, named "FPortUp" in this document. The
1985 other way, a fragmented datagram with application payload transferred from
1986 Network Gateway to device is called a "downlink-fragmented datagram". It uses another
1987 FPort for data downlink and its associated SCHC control uplinks, named "FPortDown"
1988 in this document.<a href="#section-5.1-4" class="pilcrow">¶</a></p>
1989 <p id="section-5.1-5">All RuleIDs can use arbitrary values inside the FPort range allowed
1990 by the LoRaWAN specification <span>[<a href="#LORAWAN-SPEC" class="xref">LORAWAN-SPEC</a>]</span> and
1991 <span class="bcp14">MUST</span> be shared by the device and SCHC gateway prior to
1992 the communication with the selected rule. The uplink and downlink
1993 fragmentation FPorts <span class="bcp14">MUST</span> be different.<a href="#section-5.1-5" class="pilcrow">¶</a></p>
1994 </section>
1995 </div>
1996 <div id="rule-id-management">
1997 <section id="section-5.2">
1998 <h3 id="name-ruleid-management">
1999 <a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-ruleid-management" class="section-name selfRef">RuleID Management</a>
2000 </h3>
2001 <p id="section-5.2-1">The RuleID <span class="bcp14">MUST</span> be 8 bits and encoded in the LoRaWAN
2002 FPort as described in <a href="#lorawan-schc-payload" class="xref">Section 5.1</a>.
2003
2004
2005
2006 LoRaWAN supports up to 223 application FPorts in
2007 the range [1..223] as defined in Section 4.3.2 of <span>[<a href="#LORAWAN-SPEC" class="xref">LORAWAN-SPEC</a>]</span>; it implies that the RuleID MSB
2008 <span class="bcp14">SHOULD</span> be inside this range. An application can send
2009 non-SCHC traffic by using FPort values different from the ones used
2010 for SCHC.<a href="#section-5.2-1" class="pilcrow">¶</a></p>
2011 <p id="section-5.2-2">In order to improve interoperability, <span class="bcp14">RECOMMENDED</span> fragmentation RuleID values are:<a href="#section-5.2-2" class="pilcrow">¶</a></p>
2012 <ul class="normal">
2013 <li class="normal" id="section-5.2-3.1">RuleID = 20 (8-bit) for uplink fragmentation, named FPortUp.<a href="#section-5.2-3.1" class="pilcrow">¶</a>
2014 </li>
2015 <li class="normal" id="section-5.2-3.2">RuleID = 21 (8-bit) for downlink fragmentation, named FPortDown.<a href="#section-5.2-3.2" class="pilcrow">¶</a>
2016 </li>
2017 <li class="normal" id="section-5.2-3.3">RuleID = 22 (8-bit) for which SCHC compression was not possible (i.e., no matching
2018 compression Rule was found), as described in <span><a href="https://www.rfc-editor.org/rfc/rfc8724#section-6" class="relref">Section 6</a> of [<a href="#RFC8724" class="xref">RFC8724</a>]</span>.<a href="#section-5.2-3.3" class="pilcrow">¶</a>
2019 </li>
2020 </ul>
2021 <p id="section-5.2-4">The FPortUp value <span class="bcp14">MUST</span> be different from the FPortDown value. The
2022 remaining RuleIDs are available for compression. RuleIDs are shared
2023 between uplink and downlink sessions. A RuleID not in the set(s) of
2024 FPortUp or FPortDown means that the fragmentation is not used; thus,
2025 on reception, the SCHC Message <span class="bcp14">MUST</span> be sent to the SCHC
2026 C/D layer.<a href="#section-5.2-4" class="pilcrow">¶</a></p>
2027 <p id="section-5.2-5">The only uplink frames using the FPortDown port are the
2028 fragmentation SCHC control messages of a downlink-fragmented datagram
2029 (for example, SCHC ACKs). Similarly, the only downlink frames using
2030 the FPortUp port are the fragmentation SCHC control messages of an
2031 uplink-fragmented datagram.<a href="#section-5.2-5" class="pilcrow">¶</a></p>
2032 <p id="section-5.2-6">An application can have multiple fragmented datagrams between a device and one
2033 or several SCHC gateways. A set of FPort values is <span class="bcp14">REQUIRED</span> for each SCHC gateway
2034 instance the device is required to communicate with. The application can use
2035 additional uplinks or downlink-fragmented parameters but <span class="bcp14">SHALL</span> implement at
2036 least the parameters defined in this document.<a href="#section-5.2-6" class="pilcrow">¶</a></p>
2037 <p id="section-5.2-7">The mechanism for context distribution across devices and gateways is
2038 outside the scope of this document.<a href="#section-5.2-7" class="pilcrow">¶</a></p>
2039 </section>
2040 </div>
2041 <div id="IID">
2042 <section id="section-5.3">
2043 <h3 id="name-interface-identifier-iid-co">
2044 <a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-interface-identifier-iid-co" class="section-name selfRef">Interface IDentifier (IID) Computation</a>
2045 </h3>
2046 <p id="section-5.3-1">In order to mitigate the risks described in <span>[<a href="#RFC8064" class="xref">RFC8064</a>]</span> and <span>[<a href="#RFC8065" class="xref">RFC8065</a>]</span>,
2047 implementations <span class="bcp14">MUST</span> implement the following algorithm and <span class="bcp14">SHOULD</span> use it.<a href="#section-5.3-1" class="pilcrow">¶</a></p>
2048 <ol start="1" type="1" class="normal type-1" id="section-5.3-2">
2049 <li id="section-5.3-2.1">key = LoRaWAN AppSKey<a href="#section-5.3-2.1" class="pilcrow">¶</a>
2050 </li>
2051 <li id="section-5.3-2.2">cmac = aes128_cmac(key, DevEUI)<a href="#section-5.3-2.2" class="pilcrow">¶</a>
2052 </li>
2053 <li id="section-5.3-2.3">IID = cmac[0..7]<a href="#section-5.3-2.3" class="pilcrow">¶</a>
2054 </li>
2055 </ol>
2056 <p id="section-5.3-3">The aes128_cmac algorithm is described in <span>[<a href="#RFC4493" class="xref">RFC4493</a>]</span>. It has been chosen as it is already used by
2057 devices for the LoRaWAN protocol.<a href="#section-5.3-3" class="pilcrow">¶</a></p>
2058 <p id="section-5.3-4">As AppSKey is renewed each time a device joins or rejoins a LoRaWAN
2059 network, the IID will change over time; this
2060 mitigates privacy concerns, for example, location tracking or correlation
2061 over time. Join periodicity is defined at the application level.<a href="#section-5.3-4" class="pilcrow">¶</a></p>
2062 <p id="section-5.3-5">Address-scan risk is mitigated thanks to the entropy added to
2063 the IID by the inclusion of AppSKey.<a href="#section-5.3-5" class="pilcrow">¶</a></p>
2064 <p id="section-5.3-6">Using this algorithm will also ensure that there is no correlation
2065 between the hardware identifier (DevEUI) and the IID, so an
2066 attacker cannot use the manufacturer OUI to target devices.<a href="#section-5.3-6" class="pilcrow">¶</a></p>
2067 <p id="section-5.3-7">Example with:<a href="#section-5.3-7" class="pilcrow">¶</a></p>
2068 <ul class="normal">
2069 <li class="normal" id="section-5.3-8.1">DevEUI: 0x1122334455667788<a href="#section-5.3-8.1" class="pilcrow">¶</a>
2070 </li>
2071 <li class="normal" id="section-5.3-8.2">AppSKey: 0x00AABBCCDDEEFF00AABBCCDDEEFFAABB<a href="#section-5.3-8.2" class="pilcrow">¶</a>
2072 </li>
2073 </ul>
2074 <span id="name-example-of-iid-computation"></span><div id="Fig-iid-computation-example">
2075 <figure id="figure-6">
2076 <div id="section-5.3-9.1">
2077 <pre class="sourcecode">
2078 1. key: 0x00AABBCCDDEEFF00AABBCCDDEEFFAABB
2079 2. cmac: 0x4E822D9775B2649928F82066AF804FEC
2080 3. IID: 0x4E822D9775B26499
2081 </pre>
2082 </div>
2083 <figcaption><a href="#figure-6" class="selfRef">Figure 6</a>:
2084 <a href="#name-example-of-iid-computation" class="selfRef">Example of IID Computation</a>
2085 </figcaption></figure>
2086 </div>
2087 <p id="section-5.3-10">There is a small probability of IID collision in a LoRaWAN
2088 network. If this occurs, the IID can be changed by rekeying the device
2089 at the L2 level (i.e., triggering a LoRaWAN join). The way the device is
2090 rekeyed is out of scope of this document and left to the
2091 implementation.<a href="#section-5.3-10" class="pilcrow">¶</a></p>
2092 <aside id="section-5.3-11">
2093 <p id="section-5.3-11.1">Note: Implementations also using another IID source
2094 <span class="bcp14">MUST</span> ensure that the same IID is shared between the
2095 device and the SCHC gateway in the compression and decompression of
2096 the IPv6 address of the device.<a href="#section-5.3-11.1" class="pilcrow">¶</a></p>
2097 </aside>
2098 </section>
2099 </div>
2100 <div id="padding">
2101 <section id="section-5.4">
2102 <h3 id="name-padding">
2103 <a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-padding" class="section-name selfRef">Padding</a>
2104 </h3>
2105 <p id="section-5.4-1">All padding bits <span class="bcp14">MUST</span> be 0.<a href="#section-5.4-1" class="pilcrow">¶</a></p>
2106 </section>
2107 </div>
2108 <div id="Decomp">
2109 <section id="section-5.5">
2110 <h3 id="name-decompression">
2111 <a href="#section-5.5" class="section-number selfRef">5.5. </a><a href="#name-decompression" class="section-name selfRef">Decompression</a>
2112 </h3>
2113 <p id="section-5.5-1">The SCHC C/D <span class="bcp14">MUST</span> concatenate FPort and LoRaWAN payload
2114 to retrieve the SCHC Packet as per <a href="#lorawan-schc-payload" class="xref">Section 5.1</a>.<a href="#section-5.5-1" class="pilcrow">¶</a></p>
2115 <p id="section-5.5-2">RuleIDs matching FPortUp and FPortDown are reserved for SCHC fragmentation.<a href="#section-5.5-2" class="pilcrow">¶</a></p>
2116 </section>
2117 </div>
2118 <div id="Frag">
2119 <section id="section-5.6">
2120 <h3 id="name-fragmentation">
2121 <a href="#section-5.6" class="section-number selfRef">5.6. </a><a href="#name-fragmentation" class="section-name selfRef">Fragmentation</a>
2122 </h3>
2123 <p id="section-5.6-1">The L2 Word Size used by LoRaWAN is 1 byte (8 bits). The SCHC
2124 fragmentation over LoRaWAN uses the ACK-on-Error mode for uplink
2125 fragmentation and ACK-Always mode for downlink fragmentation. A
2126 LoRaWAN device cannot support simultaneous interleaved fragmented
2127 datagrams in the same direction (uplink or downlink).<a href="#section-5.6-1" class="pilcrow">¶</a></p>
2128 <p id="section-5.6-2">The fragmentation parameters are different for uplink- and
2129 downlink-fragmented datagrams and are successively described in the
2130 next sections.<a href="#section-5.6-2" class="pilcrow">¶</a></p>
2131 <div id="DTag">
2132 <section id="section-5.6.1">
2133 <h4 id="name-dtag">
2134 <a href="#section-5.6.1" class="section-number selfRef">5.6.1. </a><a href="#name-dtag" class="section-name selfRef">DTag</a>
2135 </h4>
2136 <p id="section-5.6.1-1"><span><a href="https://www.rfc-editor.org/rfc/rfc8724#section-8.2.4" class="relref">Section 8.2.4</a> of [<a href="#RFC8724" class="xref">RFC8724</a>]</span> describes the possibility to interleave several
2137 fragmented SCHC datagrams for the same RuleID. This is not used in
2138 the SCHC-over-LoRaWAN profile. A device cannot interleave several
2139 fragmented SCHC datagrams on the same FPort. This field is not used,
2140 and its size is 0.<a href="#section-5.6.1-1" class="pilcrow">¶</a></p>
2141 <aside id="section-5.6.1-2">
2142 <p id="section-5.6.1-2.1">Note: The device can still have several parallel fragmented
2143 datagrams with more than one SCHC gateway thanks to distinct sets of FPorts,
2144 cf. <a href="#rule-id-management" class="xref">Section 5.2</a>.<a href="#section-5.6.1-2.1" class="pilcrow">¶</a></p>
2145 </aside>
2146 </section>
2147 </div>
2148 <div id="uplink-fragmentation-from-device-to-schc-gateway">
2149 <section id="section-5.6.2">
2150 <h4 id="name-uplink-fragmentation-from-d">
2151 <a href="#section-5.6.2" class="section-number selfRef">5.6.2. </a><a href="#name-uplink-fragmentation-from-d" class="section-name selfRef">Uplink Fragmentation: From Device to SCHC Gateway</a>
2152 </h4>
2153 <p id="section-5.6.2-1">In this case, the device is the fragment transmitter and the SCHC
2154 gateway is the fragment receiver. A single fragmentation rule is
2155 defined. The SCHC F/R <span class="bcp14">MUST</span> concatenate FPort and LoRaWAN
2156 payload to retrieve the SCHC Packet, as per <a href="#lorawan-schc-payload" class="xref">Section 5.1</a>.<a href="#section-5.6.2-1" class="pilcrow">¶</a></p>
2157 <span class="break"></span><dl class="dlParallel" id="section-5.6.2-2">
2158 <dt id="section-5.6.2-2.1">SCHC fragmentation reliability mode:
2159 </dt>
2160 <dd style="margin-left: 1.5em" id="section-5.6.2-2.2">
2161 <code>ACK-on-Error</code>.<a href="#section-5.6.2-2.2" class="pilcrow">¶</a>
2162 </dd>
2163 <dd class="break"></dd>
2164 <dt id="section-5.6.2-2.3">SCHC header size:
2165 </dt>
2166 <dd style="margin-left: 1.5em" id="section-5.6.2-2.4">2 bytes (the FPort byte + 1 additional byte).<a href="#section-5.6.2-2.4" class="pilcrow">¶</a>
2167 </dd>
2168 <dd class="break"></dd>
2169 <dt id="section-5.6.2-2.5">RuleID:
2170 </dt>
2171 <dd style="margin-left: 1.5em" id="section-5.6.2-2.6">8 bits stored in the LoRaWAN FPort (cf. <a href="#rule-id-management" class="xref">Section 5.2</a>).<a href="#section-5.6.2-2.6" class="pilcrow">¶</a>
2172 </dd>
2173 <dd class="break"></dd>
2174 <dt id="section-5.6.2-2.7">DTag:
2175 </dt>
2176 <dd style="margin-left: 1.5em" id="section-5.6.2-2.8">Size T = 0 bits, not used (cf. <a href="#DTag" class="xref">Section 5.6.1</a>).<a href="#section-5.6.2-2.8" class="pilcrow">¶</a>
2177 </dd>
2178 <dd class="break"></dd>
2179 <dt id="section-5.6.2-2.9">Window index:
2180 </dt>
2181 <dd style="margin-left: 1.5em" id="section-5.6.2-2.10">4 windows are used, encoded on M = 2 bits.<a href="#section-5.6.2-2.10" class="pilcrow">¶</a>
2182 </dd>
2183 <dd class="break"></dd>
2184 <dt id="section-5.6.2-2.11">FCN:
2185 </dt>
2186 <dd style="margin-left: 1.5em" id="section-5.6.2-2.12">The FCN field is encoded on N = 6 bits, so WINDOW_SIZE = 63 tiles
2187 are allowed in a window.<a href="#section-5.6.2-2.12" class="pilcrow">¶</a>
2188 </dd>
2189 <dd class="break"></dd>
2190 <dt id="section-5.6.2-2.13">Last tile:
2191 </dt>
2192 <dd style="margin-left: 1.5em" id="section-5.6.2-2.14">
2193 <p id="section-5.6.2-2.14.1">It can be carried in a Regular SCHC Fragment, alone in an All-1 SCHC
2194 Fragment, or with any of these two methods. Implementations must ensure that:<a href="#section-5.6.2-2.14.1" class="pilcrow">¶</a></p>
2195 <ul class="normal">
2196 <li class="normal" id="section-5.6.2-2.14.2.1">The sender <span class="bcp14">MUST</span> ascertain that the receiver will not
2197 receive the last tile through both a Regular SCHC Fragment and an All-1
2198 SCHC Fragment during the same session.<a href="#section-5.6.2-2.14.2.1" class="pilcrow">¶</a>
2199 </li>
2200 <li class="normal" id="section-5.6.2-2.14.2.2">If the last tile is in an All-1 SCHC Message, the current L2 MTU
2201 <span class="bcp14">MUST</span> be big enough to fit the All-1 header and the last
2202 tile.<a href="#section-5.6.2-2.14.2.2" class="pilcrow">¶</a>
2203 </li>
2204 </ul>
2205 </dd>
2206 <dd class="break"></dd>
2207 <dt id="section-5.6.2-2.15">Penultimate tile:
2208 </dt>
2209 <dd style="margin-left: 1.5em" id="section-5.6.2-2.16">
2210 <span class="bcp14">MUST</span> be equal to the regular size.<a href="#section-5.6.2-2.16" class="pilcrow">¶</a>
2211 </dd>
2212 <dd class="break"></dd>
2213 <dt id="section-5.6.2-2.17">RCS:
2214 </dt>
2215 <dd style="margin-left: 1.5em" id="section-5.6.2-2.18">Use the recommended calculation algorithm in <span><a href="https://www.rfc-editor.org/rfc/rfc8724#section-8.2.3" class="relref">Section 8.2.3</a> of [<a href="#RFC8724" class="xref">RFC8724</a>]</span>, Integrity Checking.<a href="#section-5.6.2-2.18" class="pilcrow">¶</a>
2216 </dd>
2217 <dd class="break"></dd>
2218 <dt id="section-5.6.2-2.19">Tile:
2219 </dt>
2220 <dd style="margin-left: 1.5em" id="section-5.6.2-2.20">Size is 10 bytes.<a href="#section-5.6.2-2.20" class="pilcrow">¶</a>
2221 </dd>
2222 <dd class="break"></dd>
2223 <dt id="section-5.6.2-2.21">Retransmission timer:
2224 </dt>
2225 <dd style="margin-left: 1.5em" id="section-5.6.2-2.22">Set by the implementation depending on the application
2226 requirements. The default <span class="bcp14">RECOMMENDED</span> duration of this
2227 timer is 12 hours; this value is mainly driven by application requirements
2228 and <span class="bcp14">MAY</span> be changed by the application.<a href="#section-5.6.2-2.22" class="pilcrow">¶</a>
2229 </dd>
2230 <dd class="break"></dd>
2231 <dt id="section-5.6.2-2.23">Inactivity timer:
2232 </dt>
2233 <dd style="margin-left: 1.5em" id="section-5.6.2-2.24">The SCHC gateway implements an "inactivity timer". The default
2234 <span class="bcp14">RECOMMENDED</span> duration of this timer is 12 hours; this value
2235 is mainly driven by application requirements and <span class="bcp14">MAY</span> be
2236 changed by the application.<a href="#section-5.6.2-2.24" class="pilcrow">¶</a>
2237 </dd>
2238 <dd class="break"></dd>
2239 <dt id="section-5.6.2-2.25">MAX_ACK_REQUESTS:
2240 </dt>
2241 <dd style="margin-left: 1.5em" id="section-5.6.2-2.26"> 8. With this set of parameters, the SCHC Fragment Header is 16 bits,
2242 including FPort; payload overhead will be 8 bits as FPort is already a
2243 part of LoRaWAN payload. MTU is: 4 windows * 63 tiles * 10 bytes per
2244 tile = 2520 bytes.<a href="#section-5.6.2-2.26" class="pilcrow">¶</a>
2245 </dd>
2246 <dd class="break"></dd>
2247 </dl>
2248 <p id="section-5.6.2-3">In addition to the per-rule context parameters specified in <span>[<a href="#RFC8724" class="xref">RFC8724</a>]</span>,
2249 for uplink rules, an additional context parameter is added: whether or
2250 not to ack after each window.
2251 For battery powered devices, it is <span class="bcp14">RECOMMENDED</span> to use the ACK mechanism at the
2252 end of each window instead of waiting until the end of all windows:<a href="#section-5.6.2-3" class="pilcrow">¶</a></p>
2253 <ul class="normal">
2254 <li class="normal" id="section-5.6.2-4.1">The SCHC receiver <span class="bcp14">SHOULD</span> send a SCHC ACK after every window even if there is no
2255 missing tile.<a href="#section-5.6.2-4.1" class="pilcrow">¶</a>
2256 </li>
2257 <li class="normal" id="section-5.6.2-4.2">The SCHC sender <span class="bcp14">SHOULD</span> wait for the SCHC ACK
2258 from the SCHC receiver before sending tiles from the next
2259 window. If the SCHC ACK is not received, it <span class="bcp14">SHOULD</span>
2260 send a SCHC ACK REQ up to MAX_ACK_REQUESTS times, as described
2261 previously.<a href="#section-5.6.2-4.2" class="pilcrow">¶</a>
2262 </li>
2263 </ul>
2264 <p id="section-5.6.2-5">This will avoid useless uplinks if the device has lost network coverage.<a href="#section-5.6.2-5" class="pilcrow">¶</a></p>
2265 <p id="section-5.6.2-6">For non-battery powered devices, the SCHC receiver
2266 <span class="bcp14">MAY</span> also choose to send a SCHC ACK only at the end
2267 of all windows. This will reduce downlink load on the LoRaWAN
2268 network by reducing the number of downlinks.<a href="#section-5.6.2-6" class="pilcrow">¶</a></p>
2269 <p id="section-5.6.2-7">SCHC implementations <span class="bcp14">MUST</span> be compatible with both behaviors, and this selection is
2270 part of the rule context.<a href="#section-5.6.2-7" class="pilcrow">¶</a></p>
2271 <div id="regular-fragments">
2272 <section id="section-5.6.2.1">
2273 <h5 id="name-regular-fragments">
2274 <a href="#section-5.6.2.1" class="section-number selfRef">5.6.2.1. </a><a href="#name-regular-fragments" class="section-name selfRef">Regular Fragments</a>
2275 </h5>
2276 <p id="section-5.6.2.1-1"><a href="#Fig-fragmentation-header-long-all0" class="xref">Figure 7</a>
2277 is an example of a regular fragment for all fragments except
2278 the last one. SCHC Header Size is 16 Bits, including the
2279 LoRaWAN FPort.<a href="#section-5.6.2.1-1" class="pilcrow">¶</a></p>
2280 <span id="name-all-fragments-except-the-la"></span><div id="Fig-fragmentation-header-long-all0">
2281 <figure id="figure-7">
2282 <div class="artwork art-text alignLeft" id="section-5.6.2.1-2.1">
2283 <pre>
2284 | FPort | LoRaWAN payload |
2285 + ------ + ------------------------- +
2286 | RuleID | W | FCN | Payload |
2287 + ------ + ------ + ------ + ------- +
2288 | 8 bits | 2 bits | 6 bits | |
2289 </pre>
2290 </div>
2291 <figcaption><a href="#figure-7" class="selfRef">Figure 7</a>:
2292 <a href="#name-all-fragments-except-the-la" class="selfRef">All Fragments Except the Last One.</a>
2293 </figcaption></figure>
2294 </div>
2295 </section>
2296 </div>
2297 <div id="last-fragment-all-1">
2298 <section id="section-5.6.2.2">
2299 <h5 id="name-last-fragment-all-1">
2300 <a href="#section-5.6.2.2" class="section-number selfRef">5.6.2.2. </a><a href="#name-last-fragment-all-1" class="section-name selfRef">Last Fragment (All-1)</a>
2301 </h5>
2302 <p id="section-5.6.2.2-1">Following figures are examples of All-1 messages. <a href="#Fig-fragmentation-header-all1-no-tile" class="xref">Figure 8</a>
2303 is without the last tile, <a href="#Fig-fragmentation-header-all1-last-tile" class="xref">Figure 9</a>
2304 is with the last tile.<a href="#section-5.6.2.2-1" class="pilcrow">¶</a></p>
2305 <span id="name-all-1-schc-message-without-"></span><div id="Fig-fragmentation-header-all1-no-tile">
2306 <figure id="figure-8">
2307 <div class="artwork art-text alignLeft" id="section-5.6.2.2-2.1">
2308 <pre>
2309 | FPort | LoRaWAN payload |
2310 + ------ + ---------------------------- +
2311 | RuleID | W | FCN=All-1 | RCS |
2312 + ------ + ------ + --------- + ------- +
2313 | 8 bits | 2 bits | 6 bits | 32 bits |
2314 </pre>
2315 </div>
2316 <figcaption><a href="#figure-8" class="selfRef">Figure 8</a>:
2317 <a href="#name-all-1-schc-message-without-" class="selfRef">All-1 SCHC Message without Last Tile</a>
2318 </figcaption></figure>
2319 </div>
2320 <span id="name-all-1-schc-message-with-las"></span><div id="Fig-fragmentation-header-all1-last-tile">
2321 <figure id="figure-9">
2322 <div class="artwork art-text alignLeft" id="section-5.6.2.2-3.1">
2323 <pre>
2324 | FPort | LoRaWAN payload |
2325 + ------ + ---------------------------------------------------------- +
2326 | RuleID | W | FCN=All-1 | RCS | Last tile | Opt. padding |
2327 + ------ + ------ + --------- + ------- + ------------ + ------------ +
2328 | 8 bits | 2 bits | 6 bits | 32 bits | 1 to 80 bits | 0 to 7 bits |
2329 </pre>
2330 </div>
2331 <figcaption><a href="#figure-9" class="selfRef">Figure 9</a>:
2332 <a href="#name-all-1-schc-message-with-las" class="selfRef">All-1 SCHC Message with Last Tile</a>
2333 </figcaption></figure>
2334 </div>
2335 </section>
2336 </div>
2337 <div id="schc-ack">
2338 <section id="section-5.6.2.3">
2339 <h5 id="name-schc-ack">
2340 <a href="#section-5.6.2.3" class="section-number selfRef">5.6.2.3. </a><a href="#name-schc-ack" class="section-name selfRef">SCHC ACK</a>
2341 </h5>
2342 <span id="name-schc-ack-format-correct-rcs"></span><div id="Fig-frag-header-long-schc-ack-rcs-ok">
2343 <figure id="figure-10">
2344 <div class="artwork art-text alignLeft" id="section-5.6.2.3-1.1">
2345 <pre>
2346 | FPort | LoRaWAN payload |
2347 + ------ + --------------------------+
2348 | RuleID | W | C = 1 | padding |
2349 | | | | (b'00000) |
2350 + ------ + ----- + ----- + --------- +
2351 | 8 bits | 2 bit | 1 bit | 5 bits |
2352 </pre>
2353 </div>
2354 <figcaption><a href="#figure-10" class="selfRef">Figure 10</a>:
2355 <a href="#name-schc-ack-format-correct-rcs" class="selfRef">SCHC ACK Format - Correct RCS Check</a>
2356 </figcaption></figure>
2357 </div>
2358 <span id="name-schc-ack-format-incorrect-r"></span><div id="Fig-frag-header-long-schc-ack-rcs-fail">
2359 <figure id="figure-11">
2360 <div class="artwork art-text alignLeft" id="section-5.6.2.3-2.1">
2361 <pre>
2362 | FPort | LoRaWAN payload |
2363 + ------ + --------------------------------- + ---------------- +
2364 | RuleID | W | C = 0 | Compressed bitmap | Optional padding |
2365 | | | | (C = 0) | (b'0...0) |
2366 + ------ + ----- + ----- + ----------------- + ---------------- +
2367 | 8 bits | 2 bit | 1 bit | 5 to 63 bits | 0, 6, or 7 bits |
2368 </pre>
2369 </div>
2370 <figcaption><a href="#figure-11" class="selfRef">Figure 11</a>:
2371 <a href="#name-schc-ack-format-incorrect-r" class="selfRef">SCHC ACK Format - Incorrect RCS Check</a>
2372 </figcaption></figure>
2373 </div>
2374 <aside id="section-5.6.2.3-3">
2375 <p id="section-5.6.2.3-3.1">Note: Because of the bitmap compression mechanism and L2 byte alignment, only
2376 the following discrete values are possible for the compressed bitmap size: 5, 13, 21, 29, 37, 45, 53, 61, 62, and 63.
2377 Bitmaps of 63 bits will require 6 bits of padding.<a href="#section-5.6.2.3-3.1" class="pilcrow">¶</a></p>
2378 </aside>
2379 </section>
2380 </div>
2381 <div id="receiver-abort">
2382 <section id="section-5.6.2.4">
2383 <h5 id="name-receiver-abort">
2384 <a href="#section-5.6.2.4" class="section-number selfRef">5.6.2.4. </a><a href="#name-receiver-abort" class="section-name selfRef">Receiver-Abort</a>
2385 </h5>
2386 <span id="name-receiver-abort-format"></span><div id="Fig-fragmentation-receiver-abort">
2387 <figure id="figure-12">
2388 <div class="artwork art-text alignLeft" id="section-5.6.2.4-1.1">
2389 <pre>
2390 | FPort | LoRaWAN payload |
2391 + ------ + -------------------------------------------- +
2392 | RuleID | W = b'11 | C = 1 | b'11111 | 0xFF (all 1's) |
2393 + ------ + -------- + ------+-------- + ----------------+
2394 | 8 bits | 2 bits | 1 bit | 5 bits | 8 bits |
2395 next L2 Word boundary -&gt;| &lt;-- L2 Word --&gt; |
2396 </pre>
2397 </div>
2398 <figcaption><a href="#figure-12" class="selfRef">Figure 12</a>:
2399 <a href="#name-receiver-abort-format" class="selfRef">Receiver-Abort Format</a>
2400 </figcaption></figure>
2401 </div>
2402 </section>
2403 </div>
2404 <div id="schc-acknowledge-request">
2405 <section id="section-5.6.2.5">
2406 <h5 id="name-schc-acknowledge-request">
2407 <a href="#section-5.6.2.5" class="section-number selfRef">5.6.2.5. </a><a href="#name-schc-acknowledge-request" class="section-name selfRef">SCHC Acknowledge Request</a>
2408 </h5>
2409 <span id="name-schc-ack-req-format"></span><div id="Fig-fragmentation-schc-ack-req">
2410 <figure id="figure-13">
2411 <div class="artwork art-text alignLeft" id="section-5.6.2.5-1.1">
2412 <pre>
2413 | FPort | LoRaWAN payload |
2414 +------- +------------------------- +
2415 | RuleID | W | FCN = b'000000 |
2416 + ------ + ------ + --------------- +
2417 | 8 bits | 2 bits | 6 bits |
2418 </pre>
2419 </div>
2420 <figcaption><a href="#figure-13" class="selfRef">Figure 13</a>:
2421 <a href="#name-schc-ack-req-format" class="selfRef">SCHC ACK REQ Format</a>
2422 </figcaption></figure>
2423 </div>
2424 </section>
2425 </div>
2426 </section>
2427 </div>
2428 <div id="downlink-fragmentation-from-schc-gateway-to-device">
2429 <section id="section-5.6.3">
2430 <h4 id="name-downlink-fragmentation-from">
2431 <a href="#section-5.6.3" class="section-number selfRef">5.6.3. </a><a href="#name-downlink-fragmentation-from" class="section-name selfRef">Downlink Fragmentation: From SCHC Gateway to Device</a>
2432 </h4>
2433 <p id="section-5.6.3-1">In this case, the device is the fragmentation receiver and the
2434 SCHC gateway is the fragmentation transmitter. The following fields are
2435 common to all devices. The SCHC F/R <span class="bcp14">MUST</span> concatenate
2436 FPort and LoRaWAN payload to retrieve the SCHC Packet as described
2437 in <a href="#lorawan-schc-payload" class="xref">Section 5.1</a>.<a href="#section-5.6.3-1" class="pilcrow">¶</a></p>
2438 <span class="break"></span><dl class="dlParallel" id="section-5.6.3-2">
2439 <dt id="section-5.6.3-2.1">SCHC fragmentation reliability mode:
2440 </dt>
2441 <dd style="margin-left: 1.5em" id="section-5.6.3-2.2">
2442 <ul class="normal ulEmpty">
2443 <li class="normal ulEmpty" id="section-5.6.3-2.2.1.1">
2444 <span class="break"></span><dl class="dlParallel" id="section-5.6.3-2.2.1.1.1">
2445 <dt id="section-5.6.3-2.2.1.1.1.1">Unicast downlinks:
2446 </dt>
2447 <dd style="margin-left: 1.5em" id="section-5.6.3-2.2.1.1.1.2">ACK-Always.<a href="#section-5.6.3-2.2.1.1.1.2" class="pilcrow">¶</a>
2448 </dd>
2449 <dd class="break"></dd>
2450 <dt id="section-5.6.3-2.2.1.1.1.3">Multicast downlinks:
2451 </dt>
2452 <dd style="margin-left: 1.5em" id="section-5.6.3-2.2.1.1.1.4">No-ACK; reliability has to be ensured by the upper layer. This feature is
2453 <span class="bcp14">OPTIONAL</span> for the SCHC gateway and <span class="bcp14">REQUIRED</span> for the device.<a href="#section-5.6.3-2.2.1.1.1.4" class="pilcrow">¶</a>
2454 </dd>
2455 <dd class="break"></dd>
2456 </dl>
2457 </li>
2458 </ul>
2459 </dd>
2460 <dd class="break"></dd>
2461 <dt id="section-5.6.3-2.3">RuleID:
2462 </dt>
2463 <dd style="margin-left: 1.5em" id="section-5.6.3-2.4">8 bits stored in the LoRaWAN FPort (cf. <a href="#rule-id-management" class="xref">Section 5.2</a>).<a href="#section-5.6.3-2.4" class="pilcrow">¶</a>
2464 </dd>
2465 <dd class="break"></dd>
2466 <dt id="section-5.6.3-2.5">DTag:
2467 </dt>
2468 <dd style="margin-left: 1.5em" id="section-5.6.3-2.6">Size T = 0 bit, not used (cf. <a href="#DTag" class="xref">Section 5.6.1</a>).<a href="#section-5.6.3-2.6" class="pilcrow">¶</a>
2469 </dd>
2470 <dd class="break"></dd>
2471 <dt id="section-5.6.3-2.7">FCN:
2472 </dt>
2473 <dd style="margin-left: 1.5em" id="section-5.6.3-2.8">The FCN field is encoded on N = 1 bit, so WINDOW_SIZE = 1 tile.<a href="#section-5.6.3-2.8" class="pilcrow">¶</a>
2474 </dd>
2475 <dd class="break"></dd>
2476 <dt id="section-5.6.3-2.9">RCS:
2477 </dt>
2478 <dd style="margin-left: 1.5em" id="section-5.6.3-2.10">Use the recommended calculation algorithm in <span><a href="https://www.rfc-editor.org/rfc/rfc8724#section-8.2.3" class="relref">Section 8.2.3</a> of [<a href="#RFC8724" class="xref">RFC8724</a>]</span>, Integrity Checking.<a href="#section-5.6.3-2.10" class="pilcrow">¶</a>
2479 </dd>
2480 <dd class="break"></dd>
2481 <dt id="section-5.6.3-2.11">Inactivity timer:
2482 </dt>
2483 <dd style="margin-left: 1.5em" id="section-5.6.3-2.12">The default <span class="bcp14">RECOMMENDED</span> duration of this timer is 12 hours;
2484 this value is mainly driven by application requirements and <span class="bcp14">MAY</span>
2485 be changed by the application.<a href="#section-5.6.3-2.12" class="pilcrow">¶</a>
2486 </dd>
2487 <dd class="break"></dd>
2488 </dl>
2489 <p id="section-5.6.3-3">The following parameters apply to ACK-Always (Unicast) only:<a href="#section-5.6.3-3" class="pilcrow">¶</a></p>
2490 <span class="break"></span><dl class="dlParallel" id="section-5.6.3-4">
2491 <dt id="section-5.6.3-4.1">Retransmission timer:
2492 </dt>
2493 <dd style="margin-left: 1.5em" id="section-5.6.3-4.2">See <a href="#downlink-retransmission-timer" class="xref">Section 5.6.3.5</a>.<a href="#section-5.6.3-4.2" class="pilcrow">¶</a>
2494 </dd>
2495 <dd class="break"></dd>
2496 <dt id="section-5.6.3-4.3">MAX_ACK_REQUESTS:
2497 </dt>
2498 <dd style="margin-left: 1.5em" id="section-5.6.3-4.4">8.<a href="#section-5.6.3-4.4" class="pilcrow">¶</a>
2499 </dd>
2500 <dd class="break"></dd>
2501 <dt id="section-5.6.3-4.5">Window index (unicast only):
2502 </dt>
2503 <dd style="margin-left: 1.5em" id="section-5.6.3-4.6">encoded on M = 1 bit, as per <span>[<a href="#RFC8724" class="xref">RFC8724</a>]</span>.<a href="#section-5.6.3-4.6" class="pilcrow">¶</a>
2504 </dd>
2505 <dd class="break"></dd>
2506 </dl>
2507 <p id="section-5.6.3-5">As only one tile is used, its size can change for each downlink and
2508 will be the currently available MTU.<a href="#section-5.6.3-5" class="pilcrow">¶</a></p>
2509 <p id="section-5.6.3-6">Class A devices can only receive during an RX slot, following the
2510 transmission of an uplink. Therefore, the SCHC gateway cannot
2511 initiate communication (e.g., start a new SCHC session). In order to
2512 create a downlink opportunity, it is <span class="bcp14">RECOMMENDED</span> for
2513 Class A devices to send an uplink every 24 hours when no SCHC
2514 session is started; this is application specific and can be
2515 disabled. The <span class="bcp14">RECOMMENDED</span> uplink is a LoRaWAN empty
2516 frame as defined in <a href="#lorawan-empty-frame" class="xref">Section 4.6</a>. As this uplink is sent only to open an RX window, any
2517 LoRaWAN uplink frame from the device <span class="bcp14">MAY</span> reset this
2518 counter.<a href="#section-5.6.3-6" class="pilcrow">¶</a></p>
2519 <aside id="section-5.6.3-7">
2520 <p id="section-5.6.3-7.1">Note: The FPending bit included in the LoRaWAN protocol <span class="bcp14">SHOULD NOT</span> be used for the SCHC-over-LoRaWAN protocol. It might be set by the
2521 Network Gateway for other purposes but not SCHC needs.<a href="#section-5.6.3-7.1" class="pilcrow">¶</a></p>
2522 </aside>
2523 <div id="regular-fragments-1">
2524 <section id="section-5.6.3.1">
2525 <h5 id="name-regular-fragments-2">
2526 <a href="#section-5.6.3.1" class="section-number selfRef">5.6.3.1. </a><a href="#name-regular-fragments-2" class="section-name selfRef">Regular Fragments</a>
2527 </h5>
2528 <p id="section-5.6.3.1-1"><a href="#Fig-fragmentation-downlink-header-all0" class="xref">Figure 14</a>
2529 is an example of a regular fragment for all fragments except
2530 the last one. SCHC Header Size is 10 Bits, including the
2531 LoRaWAN FPort.<a href="#section-5.6.3.1-1" class="pilcrow">¶</a></p>
2532 <span id="name-all-fragments-but-the-last-"></span><div id="Fig-fragmentation-downlink-header-all0">
2533 <figure id="figure-14">
2534 <div class="artwork art-text alignLeft" id="section-5.6.3.1-2.1">
2535 <pre>
2536 | FPort | LoRaWAN payload |
2537 + ------ + ------------------------------------ +
2538 | RuleID | W | FCN = b'0 | Payload |
2539 + ------ + ----- + --------- + ---------------- +
2540 | 8 bits | 1 bit | 1 bit | X bytes + 6 bits |
2541 </pre>
2542 </div>
2543 <figcaption><a href="#figure-14" class="selfRef">Figure 14</a>:
2544 <a href="#name-all-fragments-but-the-last-" class="selfRef">All Fragments but the Last One.</a>
2545 </figcaption></figure>
2546 </div>
2547 </section>
2548 </div>
2549 <div id="last-fragment-all-1-1">
2550 <section id="section-5.6.3.2">
2551 <h5 id="name-last-fragment-all-1-2">
2552 <a href="#section-5.6.3.2" class="section-number selfRef">5.6.3.2. </a><a href="#name-last-fragment-all-1-2" class="section-name selfRef">Last Fragment (All-1)</a>
2553 </h5>
2554 <span id="name-all-1-schc-message-the-last"></span><div id="Fig-fragmentation-downlink-header-all1">
2555 <figure id="figure-15">
2556 <div class="artwork art-text alignLeft" id="section-5.6.3.2-1.1">
2557 <pre>
2558 | FPort | LoRaWAN payload |
2559 + ------ + --------------------------- + ------------------------- +
2560 | RuleID | W | FCN = b'1 | RCS | Payload | Opt padding |
2561 + ------ + ----- + --------- + ------- + ----------- + ----------- +
2562 | 8 bits | 1 bit | 1 bit | 32 bits | 6 to X bits | 0 to 7 bits |
2563 </pre>
2564 </div>
2565 <figcaption><a href="#figure-15" class="selfRef">Figure 15</a>:
2566 <a href="#name-all-1-schc-message-the-last" class="selfRef">All-1 SCHC Message: The Last Fragment</a>
2567 </figcaption></figure>
2568 </div>
2569 </section>
2570 </div>
2571 <div id="schc-ack-1">
2572 <section id="section-5.6.3.3">
2573 <h5 id="name-schc-ack-2">
2574 <a href="#section-5.6.3.3" class="section-number selfRef">5.6.3.3. </a><a href="#name-schc-ack-2" class="section-name selfRef">SCHC ACK</a>
2575 </h5>
2576 <span id="name-schc-ack-format-correct-rcs-"></span><div id="Fig-frag-downlink-header-schc-ack-rcs-ok">
2577 <figure id="figure-16">
2578 <div class="artwork art-text alignLeft" id="section-5.6.3.3-1.1">
2579 <pre>
2580 | FPort | LoRaWAN payload |
2581 + ------ + ---------------------------------- +
2582 | RuleID | W | C = b'1 | Padding b'000000 |
2583 + ------ + ----- + ------- + ---------------- +
2584 | 8 bits | 1 bit | 1 bit | 6 bits |
2585 </pre>
2586 </div>
2587 <figcaption><a href="#figure-16" class="selfRef">Figure 16</a>:
2588 <a href="#name-schc-ack-format-correct-rcs-" class="selfRef">SCHC ACK Format - Correct RCS Check</a>
2589 </figcaption></figure>
2590 </div>
2591 <span id="name-schc-ack-format-incorrect-rc"></span><div id="Fig-frag-downlink-header-schc-ack-rcs-fail">
2592 <figure id="figure-17">
2593 <div class="artwork art-text alignLeft" id="section-5.6.3.3-2.1">
2594 <pre>
2595 | FPort | LoRaWAN payload |
2596 + ------ + ------------------------------------------------- +
2597 | RuleID | W | C = b'0 | Bitmap = b'1 | Padding b'000000 |
2598 + ------ + ----- + ------- + ------------ + ---------------- +
2599 | 8 bits | 1 bit | 1 bit | 1 bit | 5 bits |
2600 </pre>
2601 </div>
2602 <figcaption><a href="#figure-17" class="selfRef">Figure 17</a>:
2603 <a href="#name-schc-ack-format-incorrect-rc" class="selfRef">SCHC ACK Format - Incorrect RCS Check</a>
2604 </figcaption></figure>
2605 </div>
2606 </section>
2607 </div>
2608 <div id="receiver-abort-1">
2609 <section id="section-5.6.3.4">
2610 <h5 id="name-receiver-abort-2">
2611 <a href="#section-5.6.3.4" class="section-number selfRef">5.6.3.4. </a><a href="#name-receiver-abort-2" class="section-name selfRef">Receiver-Abort</a>
2612 </h5>
2613 <p id="section-5.6.3.4-1"><a href="#Fig-fragmentation-downlink-header-abort" class="xref">Figure 18</a>
2614 is an example of a Receiver-Abort packet, following an All-1
2615 SCHC Fragment with incorrect RCS.<a href="#section-5.6.3.4-1" class="pilcrow">¶</a></p>
2616 <span id="name-receiver-abort-packet"></span><div id="Fig-fragmentation-downlink-header-abort">
2617 <figure id="figure-18">
2618 <div class="artwork art-text alignLeft" id="section-5.6.3.4-2.1">
2619 <pre>
2620 | FPort | LoRaWAN payload |
2621 + ------ + ---------------------------------------------- +
2622 | RuleID | W = b'1 | C = b'1 | b'111111 | 0xFF (all 1's) |
2623 + ------ + ------- + ------- + -------- + --------------- +
2624 | 8 bits | 1 bit | 1 bits | 6 bits | 8 bits |
2625 next L2 Word boundary -&gt;| &lt;-- L2 Word --&gt; |
2626 </pre>
2627 </div>
2628 <figcaption><a href="#figure-18" class="selfRef">Figure 18</a>:
2629 <a href="#name-receiver-abort-packet" class="selfRef">Receiver-Abort Packet</a>
2630 </figcaption></figure>
2631 </div>
2632 </section>
2633 </div>
2634 <div id="downlink-retransmission-timer">
2635 <section id="section-5.6.3.5">
2636 <h5 id="name-downlink-retransmission-tim">
2637 <a href="#section-5.6.3.5" class="section-number selfRef">5.6.3.5. </a><a href="#name-downlink-retransmission-tim" class="section-name selfRef">Downlink Retransmission Timer</a>
2638 </h5>
2639 <p id="section-5.6.3.5-1">Class A, Class B, and Class C devices do not manage
2640 retransmissions and timers the same way.<a href="#section-5.6.3.5-1" class="pilcrow">¶</a></p>
2641 <div id="class-a-devices">
2642 <section id="section-5.6.3.5.1">
2643 <h6 id="name-class-a-devices">
2644 <a href="#section-5.6.3.5.1" class="section-number selfRef">5.6.3.5.1. </a><a href="#name-class-a-devices" class="section-name selfRef">Class A Devices</a>
2645 </h6>
2646 <p id="section-5.6.3.5.1-1">Class A devices can only receive in an RX slot following the
2647 transmission of an uplink.<a href="#section-5.6.3.5.1-1" class="pilcrow">¶</a></p>
2648 <p id="section-5.6.3.5.1-2">The SCHC gateway implements an inactivity timer with a
2649 <span class="bcp14">RECOMMENDED</span> duration of 36 hours. For devices
2650 with very low transmission rates (for example, 1 packet a day in
2651 normal operation), that duration may be extended; it is
2652 application specific.<a href="#section-5.6.3.5.1-2" class="pilcrow">¶</a></p>
2653 <p id="section-5.6.3.5.1-3">RETRANSMISSION_TIMER is application specific and its
2654 <span class="bcp14">RECOMMENDED</span> value is
2655 INACTIVITY_TIMER/(MAX_ACK_REQUESTS + 1).<a href="#section-5.6.3.5.1-3" class="pilcrow">¶</a></p>
2656 <p id="section-5.6.3.5.1-4"><strong>SCHC All-0 (FCN = 0)</strong><a href="#section-5.6.3.5.1-4" class="pilcrow">¶</a></p>
2657 <p id="section-5.6.3.5.1-5">All fragments but the last have an FCN = 0 (because the window size
2658 is 1). Following an All-0 SCHC Fragment, the device
2659 <span class="bcp14">MUST</span> transmit the SCHC ACK message. It
2660 <span class="bcp14">MUST</span> transmit up to MAX_ACK_REQUESTS SCHC ACK
2661 messages before aborting. In order to progress the fragmented
2662 datagram, the SCHC layer should immediately queue for
2663 transmission those SCHC ACK messages if no SCHC downlink has been
2664 received during the RX1 and RX2 windows. The LoRaWAN layer will respect
2665 the applicable local spectrum regulation.<a href="#section-5.6.3.5.1-5" class="pilcrow">¶</a></p>
2666 <aside id="section-5.6.3.5.1-6">
2667 <p id="section-5.6.3.5.1-6.1">Note: The ACK bitmap is 1 bit long and is always 1.<a href="#section-5.6.3.5.1-6.1" class="pilcrow">¶</a></p>
2668 </aside>
2669 <p id="section-5.6.3.5.1-7"><strong>SCHC All-1 (FCN = 1)</strong><a href="#section-5.6.3.5.1-7" class="pilcrow">¶</a></p>
2670 <p id="section-5.6.3.5.1-8">SCHC All-1 is the last fragment of a datagram, and the
2671 corresponding SCHC ACK message might be lost; therefore, the SCHC
2672 gateway <span class="bcp14">MUST</span> request a retransmission of this ACK
2673 when the retransmission timer expires. To open a downlink
2674 opportunity, the device <span class="bcp14">MUST</span> transmit an uplink
2675 every interval of RETRANSMISSION_TIMER/(MAX_ACK_REQUESTS *
2676 SCHC_ACK_REQ_DN_OPPORTUNITY). The format of this uplink is
2677 application specific. It is <span class="bcp14">RECOMMENDED</span> for a
2678 device to send an empty frame (see <a href="#lorawan-empty-frame" class="xref">Section 4.6</a>), but it is
2679 application specific and will be used by the NGW to transmit a
2680 potential SCHC ACK REQ. SCHC_ACK_REQ_DN_OPPORTUNITY is
2681 application specific and its recommended value is 2. It
2682 <span class="bcp14">MUST</span> be greater than 1. This allows the opening of a
2683 downlink opportunity to any downlink with higher priority than
2684 the SCHC ACK REQ message.<a href="#section-5.6.3.5.1-8" class="pilcrow">¶</a></p>
2685 <aside id="section-5.6.3.5.1-9">
2686 <p id="section-5.6.3.5.1-9.1">Note: The device <span class="bcp14">MUST</span> keep this SCHC
2687 ACK message in memory until it receives a downlink SCHC
2688 Fragmentation Message (with FPort == FPortDown) that is not a
2689 SCHC ACK REQ; this indicates that the SCHC gateway has received
2690 the SCHC ACK message.<a href="#section-5.6.3.5.1-9.1" class="pilcrow">¶</a></p>
2691 </aside>
2692 </section>
2693 </div>
2694 </section>
2695 </div>
2696 <div id="class-b-or-class-c-devices">
2697 <section id="section-5.6.3.6">
2698 <h5 id="name-class-b-or-class-c-devices">
2699 <a href="#section-5.6.3.6" class="section-number selfRef">5.6.3.6. </a><a href="#name-class-b-or-class-c-devices" class="section-name selfRef">Class B or Class C Devices</a>
2700 </h5>
2701 <p id="section-5.6.3.6-1">Class B devices can receive in scheduled RX slots or in RX
2702 slots following the transmission of an uplink. Class C devices are
2703 almost in constant reception.<a href="#section-5.6.3.6-1" class="pilcrow">¶</a></p>
2704 <p id="section-5.6.3.6-2"><span class="bcp14">RECOMMENDED</span> retransmission timer values are:<a href="#section-5.6.3.6-2" class="pilcrow">¶</a></p>
2705 <span class="break"></span><dl class="dlParallel" id="section-5.6.3.6-3">
2706 <dt id="section-5.6.3.6-3.1">Class B:
2707 </dt>
2708 <dd style="margin-left: 1.5em" id="section-5.6.3.6-3.2">3 times the ping slot periodicity.<a href="#section-5.6.3.6-3.2" class="pilcrow">¶</a>
2709 </dd>
2710 <dd class="break"></dd>
2711 <dt id="section-5.6.3.6-3.3">Class C:
2712 </dt>
2713 <dd style="margin-left: 1.5em" id="section-5.6.3.6-3.4">30 seconds.<a href="#section-5.6.3.6-3.4" class="pilcrow">¶</a>
2714 </dd>
2715 <dd class="break"></dd>
2716 </dl>
2717 <p id="section-5.6.3.6-4">The <span class="bcp14">RECOMMENDED</span> inactivity timer value is 12
2718 hours for both Class B and Class C devices.<a href="#section-5.6.3.6-4" class="pilcrow">¶</a></p>
2719 </section>
2720 </div>
2721 </section>
2722 </div>
2723 </section>
2724 </div>
2725 <div id="schc-fragment-format">
2726 <section id="section-5.7">
2727 <h3 id="name-schc-fragment-format">
2728 <a href="#section-5.7" class="section-number selfRef">5.7. </a><a href="#name-schc-fragment-format" class="section-name selfRef">SCHC Fragment Format</a>
2729 </h3>
2730 <div id="all-0-schc-fragment">
2731 <section id="section-5.7.1">
2732 <h4 id="name-all-0-schc-fragment">
2733 <a href="#section-5.7.1" class="section-number selfRef">5.7.1. </a><a href="#name-all-0-schc-fragment" class="section-name selfRef">All-0 SCHC Fragment</a>
2734 </h4>
2735 <p id="section-5.7.1-1"><strong>Uplink Fragmentation (Ack-on-Error)</strong>:<a href="#section-5.7.1-1" class="pilcrow">¶</a></p>
2736 <p id="section-5.7.1-2">All-0 is distinguishable from a SCHC ACK REQ, as <span>[<a href="#RFC8724" class="xref">RFC8724</a>]</span> states "This condition is also
2737 met if the SCHC Fragment Header is a multiple of L2 Words", the
2738 following condition being met: SCHC header is 2 bytes.<a href="#section-5.7.1-2" class="pilcrow">¶</a></p>
2739 <p id="section-5.7.1-3"><strong>Downlink fragmentation (ACK-Always)</strong>:<a href="#section-5.7.1-3" class="pilcrow">¶</a></p>
2740 <p id="section-5.7.1-4">As per <span>[<a href="#RFC8724" class="xref">RFC8724</a>]</span>, SCHC All-1
2741 <span class="bcp14">MUST</span> contain the last tile, and implementations
2742 <span class="bcp14">MUST</span> ensure that SCHC All-0 message Payload will be
2743 at least the size of an L2 Word.<a href="#section-5.7.1-4" class="pilcrow">¶</a></p>
2744 </section>
2745 </div>
2746 <div id="all-1-schc-fragment">
2747 <section id="section-5.7.2">
2748 <h4 id="name-all-1-schc-fragment">
2749 <a href="#section-5.7.2" class="section-number selfRef">5.7.2. </a><a href="#name-all-1-schc-fragment" class="section-name selfRef">All-1 SCHC Fragment</a>
2750 </h4>
2751 <p id="section-5.7.2-1">All-1 is distinguishable from a SCHC Sender-Abort, as <span>[<a href="#RFC8724" class="xref">RFC8724</a>]</span> states "This condition is met
2752 if the RCS is present and is at least the size of an L2 Word",
2753 the following condition being met: RCS is 4 bytes.<a href="#section-5.7.2-1" class="pilcrow">¶</a></p>
2754 </section>
2755 </div>
2756 <div id="delay-after-each-lorawan-frame-to-respect-local-regulation">
2757 <section id="section-5.7.3">
2758 <h4 id="name-delay-after-each-lorawan-fr">
2759 <a href="#section-5.7.3" class="section-number selfRef">5.7.3. </a><a href="#name-delay-after-each-lorawan-fr" class="section-name selfRef">Delay after Each LoRaWAN Frame to Respect Local Regulation</a>
2760 </h4>
2761 <p id="section-5.7.3-1">This profile does not define a delay to be added after each
2762 LoRaWAN frame; local regulation compliance is expected to be
2763 enforced by the LoRaWAN stack.<a href="#section-5.7.3-1" class="pilcrow">¶</a></p>
2764 </section>
2765 </div>
2766 </section>
2767 </div>
2768 </section>
2769 </div>
2770 <div id="security-considerations">
2771 <section id="section-6">
2772 <h2 id="name-security-considerations">
2773 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
2774 </h2>
2775 <p id="section-6-1">This document is only providing parameters that are expected to be best
2776 suited for LoRaWAN networks for <span>[<a href="#RFC8724" class="xref">RFC8724</a>]</span>. IID
2777 security is discussed in <a href="#IID" class="xref">Section 5.3</a>. As such, this document does not contribute to
2778 any new security issues beyond those already identified in
2779 <span>[<a href="#RFC8724" class="xref">RFC8724</a>]</span>.
2780 Moreover, SCHC data (LoRaWAN payload) are protected at the LoRaWAN level by an AES-128
2781 encryption with a session key shared by the device and the SCHC gateway. These session keys are renewed at each
2782 LoRaWAN session (i.e., each join or rejoin to the LoRaWAN network).<a href="#section-6-1" class="pilcrow">¶</a></p>
2783 </section>
2784 </div>
2785 <div id="iana-considerations">
2786 <section id="section-7">
2787 <h2 id="name-iana-considerations">
2788 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
2789 </h2>
2790 <p id="section-7-1">This document has no IANA actions.<a href="#section-7-1" class="pilcrow">¶</a></p>
2791 </section>
2792 </div>
2793 <section id="section-8">
2794 <h2 id="name-references">
2795 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-references" class="section-name selfRef">References</a>
2796 </h2>
2797 <section id="section-8.1">
2798 <h3 id="name-normative-references">
2799 <a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
2800 </h3>
2801 <dl class="references">
2802 <dt id="LORAWAN-SPEC">[LORAWAN-SPEC]</dt>
2803 <dd>
2804 <span class="refAuthor">LoRa Alliance</span>, <span class="refTitle">"LoRaWAN 1.0.4 Specification Package"</span>, <span>&lt;<a href="https://lora-alliance.org/resource_hub/lorawan-104-specification-package/">https://lora-alliance.org/resource_hub/lorawan-104-specification-package/</a>&gt;</span>. </dd>
2805 <dd class="break"></dd>
2806 <dt id="RFC2119">[RFC2119]</dt>
2807 <dd>
2808 <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>
2809 <dd class="break"></dd>
2810 <dt id="RFC4291">[RFC4291]</dt>
2811 <dd>
2812 <span class="refAuthor">Hinden, R.</span> and <span class="refAuthor">S. Deering</span>, <span class="refTitle">"IP Version 6 Addressing Architecture"</span>, <span class="seriesInfo">RFC 4291</span>, <span class="seriesInfo">DOI 10.17487/RFC4291</span>, <time datetime="2006-02" class="refDate">February 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4291">https://www.rfc-editor.org/info/rfc4291</a>&gt;</span>. </dd>
2813 <dd class="break"></dd>
2814 <dt id="RFC4493">[RFC4493]</dt>
2815 <dd>
2816 <span class="refAuthor">Song, JH.</span>, <span class="refAuthor">Poovendran, R.</span>, <span class="refAuthor">Lee, J.</span>, and <span class="refAuthor">T. Iwata</span>, <span class="refTitle">"The AES-CMAC Algorithm"</span>, <span class="seriesInfo">RFC 4493</span>, <span class="seriesInfo">DOI 10.17487/RFC4493</span>, <time datetime="2006-06" class="refDate">June 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4493">https://www.rfc-editor.org/info/rfc4493</a>&gt;</span>. </dd>
2817 <dd class="break"></dd>
2818 <dt id="RFC8174">[RFC8174]</dt>
2819 <dd>
2820 <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>
2821 <dd class="break"></dd>
2822 <dt id="RFC8724">[RFC8724]</dt>
2823 <dd>
2824 <span class="refAuthor">Minaburo, A.</span>, <span class="refAuthor">Toutain, L.</span>, <span class="refAuthor">Gomez, C.</span>, <span class="refAuthor">Barthel, D.</span>, and <span class="refAuthor">JC. Zúñiga</span>, <span class="refTitle">"SCHC: Generic Framework for Static Context Header Compression and Fragmentation"</span>, <span class="seriesInfo">RFC 8724</span>, <span class="seriesInfo">DOI 10.17487/RFC8724</span>, <time datetime="2020-04" class="refDate">April 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8724">https://www.rfc-editor.org/info/rfc8724</a>&gt;</span>. </dd>
2825 <dd class="break"></dd>
2826 </dl>
2827 </section>
2828 <section id="section-8.2">
2829 <h3 id="name-informative-references">
2830 <a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
2831 </h3>
2832 <dl class="references">
2833 <dt id="LORAWAN-REMOTE-MULTICAST-SET">[LORAWAN-REMOTE-MULTICAST-SET]</dt>
2834 <dd>
2835 <span class="refAuthor">LoRa Alliance</span>, <span class="refTitle">"LoRaWAN Remote Multicast Setup Specification v1.0.0"</span>, <span>&lt;<a href="https://lora-alliance.org/resource_hub/lorawan-remote-multicast-setup-specification-v1-0-0/">https://lora-alliance.org/resource_hub/lorawan-remote-multicast-setup-specification-v1-0-0/</a>&gt;</span>. </dd>
2836 <dd class="break"></dd>
2837 <dt id="RFC8064">[RFC8064]</dt>
2838 <dd>
2839 <span class="refAuthor">Gont, F.</span>, <span class="refAuthor">Cooper, A.</span>, <span class="refAuthor">Thaler, D.</span>, and <span class="refAuthor">W. Liu</span>, <span class="refTitle">"Recommendation on Stable IPv6 Interface Identifiers"</span>, <span class="seriesInfo">RFC 8064</span>, <span class="seriesInfo">DOI 10.17487/RFC8064</span>, <time datetime="2017-02" class="refDate">February 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8064">https://www.rfc-editor.org/info/rfc8064</a>&gt;</span>. </dd>
2840 <dd class="break"></dd>
2841 <dt id="RFC8065">[RFC8065]</dt>
2842 <dd>
2843 <span class="refAuthor">Thaler, D.</span>, <span class="refTitle">"Privacy Considerations for IPv6 Adaptation-Layer Mechanisms"</span>, <span class="seriesInfo">RFC 8065</span>, <span class="seriesInfo">DOI 10.17487/RFC8065</span>, <time datetime="2017-02" class="refDate">February 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8065">https://www.rfc-editor.org/info/rfc8065</a>&gt;</span>. </dd>
2844 <dd class="break"></dd>
2845 <dt id="RFC8376">[RFC8376]</dt>
2846 <dd>
2847 <span class="refAuthor">Farrell, S., Ed.</span>, <span class="refTitle">"Low-Power Wide Area Network (LPWAN) Overview"</span>, <span class="seriesInfo">RFC 8376</span>, <span class="seriesInfo">DOI 10.17487/RFC8376</span>, <time datetime="2018-05" class="refDate">May 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8376">https://www.rfc-editor.org/info/rfc8376</a>&gt;</span>. </dd>
2848 <dd class="break"></dd>
2849 </dl>
2850 </section>
2851 </section>
2852 <div id="examples">
2853 <section id="section-appendix.a">
2854 <h2 id="name-examples">
2855 <a href="#section-appendix.a" class="section-number selfRef">Appendix A. </a><a href="#name-examples" class="section-name selfRef">Examples</a>
2856 </h2>
2857 <p id="section-appendix.a-1">In the following examples, "applicative data" refers to the IPv6 payload
2858 sent by the application to the SCHC layer.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
2859 <div id="uplink-compression-example-no-fragmentation">
2860 <section id="section-a.1">
2861 <h2 id="name-uplink-compression-example-">
2862 <a href="#section-a.1" class="section-number selfRef">A.1. </a><a href="#name-uplink-compression-example-" class="section-name selfRef">Uplink - Compression Example - No Fragmentation</a>
2863 </h2>
2864 <p id="section-a.1-1">This example represents an applicative data going through SCHC over
2865 LoRaWAN; no fragmentation required.<a href="#section-a.1-1" class="pilcrow">¶</a></p>
2866 <p id="section-a.1-2">An applicative data of 78 bytes is passed to the SCHC compression
2867 layer. Rule 1 is used by the SCHC C/D layer, allowing to compress it
2868 to 40 bytes and 5 bits: 1 byte RuleID, 21 bits residue + 37 bytes
2869 payload.<a href="#section-a.1-2" class="pilcrow">¶</a></p>
2870 <span id="name-uplink-example-schc-message"></span><div id="Fig-example-uplink-no-fragmentation-payload-schc-message">
2871 <figure id="figure-19">
2872 <div class="artwork art-text alignLeft" id="section-a.1-3.1">
2873 <pre>
2874 | RuleID | Compression residue | Payload | Padding=b'000 |
2875 + ------ + ------------------- + --------- + ------------- +
2876 | 1 | 21 bits | 37 bytes | 3 bits |
2877 </pre>
2878 </div>
2879 <figcaption><a href="#figure-19" class="selfRef">Figure 19</a>:
2880 <a href="#name-uplink-example-schc-message" class="selfRef">Uplink Example: SCHC Message</a>
2881 </figcaption></figure>
2882 </div>
2883 <p id="section-a.1-4">The current LoRaWAN MTU is 51 bytes, although 2-byte FOpts are
2884 used by the LoRaWAN protocol: 49 bytes are available for SCHC payload; no
2885 need for fragmentation. The payload will be transmitted through FPort
2886 = 1.<a href="#section-a.1-4" class="pilcrow">¶</a></p>
2887 <span id="name-uplink-example-lorawan-pack"></span><div id="Fig-example-uplink-no-fragmentation-compression">
2888 <figure id="figure-20">
2889 <div class="artwork art-text alignLeft" id="section-a.1-5.1">
2890 <pre>
2891 | LoRaWAN Header | LoRaWAN payload (40 bytes) |
2892 + ------------------------- + --------------------------------------- +
2893 | | FOpts | RuleID=1 | Compression | Payload | Padding=b'000 |
2894 | | | | residue | | |
2895 + ---- + ------- + -------- + ----------- + --------- + ------------- +
2896 | XXXX | 2 bytes | 1 byte | 21 bits | 37 bytes | 3 bits |
2897 </pre>
2898 </div>
2899 <figcaption><a href="#figure-20" class="selfRef">Figure 20</a>:
2900 <a href="#name-uplink-example-lorawan-pack" class="selfRef">Uplink Example: LoRaWAN Packet</a>
2901 </figcaption></figure>
2902 </div>
2903 </section>
2904 </div>
2905 <div id="uplink-compression-and-fragmentation-example">
2906 <section id="section-a.2">
2907 <h2 id="name-uplink-compression-and-frag">
2908 <a href="#section-a.2" class="section-number selfRef">A.2. </a><a href="#name-uplink-compression-and-frag" class="section-name selfRef">Uplink - Compression and Fragmentation Example</a>
2909 </h2>
2910 <p id="section-a.2-1">This example represents an applicative data going through SCHC, with
2911 fragmentation.<a href="#section-a.2-1" class="pilcrow">¶</a></p>
2912 <p id="section-a.2-2">An applicative data of 300 bytes is passed to the SCHC compression layer. Rule 1
2913 is used by the SCHC C/D layer, allowing to compress it to 282 bytes and 5 bits: 1 byte
2914 RuleID, 21 bits residue + 279 bytes payload.<a href="#section-a.2-2" class="pilcrow">¶</a></p>
2915 <span id="name-uplink-example-schc-message-2"></span><div id="Fig-example-uplink-fragmentation-schc-message">
2916 <figure id="figure-21">
2917 <div class="artwork art-text alignLeft" id="section-a.2-3.1">
2918 <pre>
2919 | RuleID | Compression residue | Payload |
2920 + ------ + ------------------- + --------- +
2921 | 1 | 21 bits | 279 bytes |
2922 </pre>
2923 </div>
2924 <figcaption><a href="#figure-21" class="selfRef">Figure 21</a>:
2925 <a href="#name-uplink-example-schc-message-2" class="selfRef">Uplink Example: SCHC Message</a>
2926 </figcaption></figure>
2927 </div>
2928 <p id="section-a.2-4">The current LoRaWAN MTU is 11 bytes; 0-byte FOpts are used by
2929 the LoRaWAN protocol: 11 bytes are available for SCHC payload + 1 byte
2930 FPort field. The SCHC header is 2 bytes (including FPort), so 1 tile is
2931 sent in the first fragment.<a href="#section-a.2-4" class="pilcrow">¶</a></p>
2932 <span id="name-uplink-example-lorawan-packe"></span><div id="Fig-example-uplink-fragmentation-lorawan-packet-1">
2933 <figure id="figure-22">
2934 <div class="artwork art-text alignLeft" id="section-a.2-5.1">
2935 <pre>
2936 | LoRaWAN Header | LoRaWAN payload (11 bytes) |
2937 + -------------------------- + -------------------------- +
2938 | | RuleID=20 | W | FCN | 1 tile |
2939 + -------------- + --------- + ----- + ------ + --------- +
2940 | XXXX | 1 byte | 0 0 | 62 | 10 bytes |
2941 </pre>
2942 </div>
2943 <figcaption><a href="#figure-22" class="selfRef">Figure 22</a>:
2944 <a href="#name-uplink-example-lorawan-packe" class="selfRef">Uplink Example: LoRaWAN Packet 1</a>
2945 </figcaption></figure>
2946 </div>
2947 <p id="section-a.2-6">The tile content is described in <a href="#Fig-example-uplink-fragmentation-lorawan-packet-1-tile-content" class="xref">Figure 23</a><a href="#section-a.2-6" class="pilcrow">¶</a></p>
2948 <span id="name-uplink-example-first-tile-c"></span><div id="Fig-example-uplink-fragmentation-lorawan-packet-1-tile-content">
2949 <figure id="figure-23">
2950 <div class="artwork art-text alignLeft" id="section-a.2-7.1">
2951 <pre>
2952 Content of the tile is:
2953 | RuleID | Compression residue | Payload |
2954 + ------ + ------------------- + ----------------- +
2955 | 1 | 21 bits | 6 bytes + 3 bits |
2956 </pre>
2957 </div>
2958 <figcaption><a href="#figure-23" class="selfRef">Figure 23</a>:
2959 <a href="#name-uplink-example-first-tile-c" class="selfRef">Uplink Example: First Tile Content</a>
2960 </figcaption></figure>
2961 </div>
2962 <p id="section-a.2-8">Next transmission MTU is 11 bytes, although 2-byte FOpts are used
2963 by the LoRaWAN protocol: 9 bytes are available for SCHC payload + 1
2964 byte FPort field, a tile does not fit inside so the LoRaWAN stack will
2965 send only FOpts.<a href="#section-a.2-8" class="pilcrow">¶</a></p>
2966 <p id="section-a.2-9">Next transmission MTU is 242 bytes, 4-byte FOpts. 23 tiles are transmitted:<a href="#section-a.2-9" class="pilcrow">¶</a></p>
2967 <span id="name-uplink-example-lorawan-packet"></span><div id="Fig-example-uplink-fragmentation-lorawan-packet-2">
2968 <figure id="figure-24">
2969 <div class="artwork art-text alignLeft" id="section-a.2-10.1">
2970 <pre>
2971 | LoRaWAN Header | LoRaWAN payload (231 bytes) |
2972 + --------------------------------------+ --------------------------- +
2973 | | FOpts | RuleID=20 | W | FCN | 23 tiles |
2974 + -------------- + ------- + ---------- + ----- + ----- + ----------- +
2975 | XXXX | 4 bytes | 1 byte | 0 0 | 61 | 230 bytes |
2976 </pre>
2977 </div>
2978 <figcaption><a href="#figure-24" class="selfRef">Figure 24</a>:
2979 <a href="#name-uplink-example-lorawan-packet" class="selfRef">Uplink Example: LoRaWAN Packet 2</a>
2980 </figcaption></figure>
2981 </div>
2982 <p id="section-a.2-11">Next transmission MTU is 242 bytes, no FOpts. All 5 remaining tiles are
2983 transmitted, the last tile is only 2 bytes + 5 bits. Padding is added for
2984 the remaining 3 bits.<a href="#section-a.2-11" class="pilcrow">¶</a></p>
2985 <span id="name-uplink-example-lorawan-packet-"></span><div id="Fig-example-uplink-fragmentation-lorawan-packet-3">
2986 <figure id="figure-25">
2987 <div class="artwork art-text alignLeft" id="section-a.2-12.1">
2988 <pre>
2989 | LoRaWAN Header | LoRaWAN payload (44 bytes) |
2990 + ---- + ---------- + ----------------------------------------------- +
2991 | | RuleID=20 | W | FCN | 5 tiles | Padding=b'000 |
2992 + ---- + ---------- + ----- + ----- + --------------- + ------------- +
2993 | XXXX | 1 byte | 0 0 | 38 | 42 bytes+5 bits | 3 bits |
2994 </pre>
2995 </div>
2996 <figcaption><a href="#figure-25" class="selfRef">Figure 25</a>:
2997 <a href="#name-uplink-example-lorawan-packet-" class="selfRef">Uplink Example: LoRaWAN Packet 3</a>
2998 </figcaption></figure>
2999 </div>
3000 <p id="section-a.2-13">Then All-1 message can be transmitted:<a href="#section-a.2-13" class="pilcrow">¶</a></p>
3001 <span id="name-uplink-example-lorawan-packet-4"></span><div id="Fig-example-uplink-fragmentation-lorawan-packet-4">
3002 <figure id="figure-26">
3003 <div class="artwork art-text alignLeft" id="section-a.2-14.1">
3004 <pre>
3005 | LoRaWAN Header | LoRaWAN payload (44 bytes) |
3006 + ---- + -----------+ -------------------------- +
3007 | | RuleID=20 | W | FCN | RCS |
3008 + ---- + ---------- + ----- + ----- + ---------- +
3009 | XXXX | 1 byte | 0 0 | 63 | 4 bytes |
3010 </pre>
3011 </div>
3012 <figcaption><a href="#figure-26" class="selfRef">Figure 26</a>:
3013 <a href="#name-uplink-example-lorawan-packet-4" class="selfRef">Uplink Example: LoRaWAN Packet 4 - All-1 SCHC Message</a>
3014 </figcaption></figure>
3015 </div>
3016 <p id="section-a.2-15">All packets have been received by the SCHC gateway, computed RCS is
3017 correct so the following ACK is sent to the device by the SCHC receiver:<a href="#section-a.2-15" class="pilcrow">¶</a></p>
3018 <span id="name-uplink-example-lorawan-packet-5"></span><div id="Fig-example-uplink-fragmentation-lorawan-packet-5">
3019 <figure id="figure-27">
3020 <div class="artwork art-text alignLeft" id="section-a.2-16.1">
3021 <pre>
3022 | LoRaWAN Header | LoRaWAN payload |
3023 + -------------- + --------- + ------------------- +
3024 | | RuleID=20 | W | C | Padding |
3025 + -------------- + --------- + ----- + - + ------- +
3026 | XXXX | 1 byte | 0 0 | 1 | 5 bits |
3027 </pre>
3028 </div>
3029 <figcaption><a href="#figure-27" class="selfRef">Figure 27</a>:
3030 <a href="#name-uplink-example-lorawan-packet-5" class="selfRef">Uplink Example: LoRaWAN Packet 5 - SCHC ACK</a>
3031 </figcaption></figure>
3032 </div>
3033 </section>
3034 </div>
3035 <div id="downlink">
3036 <section id="section-a.3">
3037 <h2 id="name-downlink">
3038 <a href="#section-a.3" class="section-number selfRef">A.3. </a><a href="#name-downlink" class="section-name selfRef">Downlink</a>
3039 </h2>
3040 <p id="section-a.3-1">An applicative data of 155 bytes is passed to the SCHC compression layer. Rule 1
3041 is used by the SCHC C/D layer, allowing to compress it to 130 bytes and 5 bits: 1 byte
3042 RuleID, 21 bits residue + 127 bytes payload.<a href="#section-a.3-1" class="pilcrow">¶</a></p>
3043 <span id="name-downlink-example-schc-messa"></span><div id="Fig-example-downlink-fragmentation-schc-message">
3044 <figure id="figure-28">
3045 <div class="artwork art-text alignLeft" id="section-a.3-2.1">
3046 <pre>
3047 | RuleID | Compression residue | Payload |
3048 + ------ + ------------------- + --------- +
3049 | 1 | 21 bits | 127 bytes |
3050 </pre>
3051 </div>
3052 <figcaption><a href="#figure-28" class="selfRef">Figure 28</a>:
3053 <a href="#name-downlink-example-schc-messa" class="selfRef">Downlink Example: SCHC Message</a>
3054 </figcaption></figure>
3055 </div>
3056 <p id="section-a.3-3">The current LoRaWAN MTU is 51 bytes; no FOpts are used by the
3057 LoRaWAN protocol: 51 bytes are available for SCHC payload + FPort
3058 field; the applicative data has to be fragmented.<a href="#section-a.3-3" class="pilcrow">¶</a></p>
3059 <span id="name-downlink-example-lorawan-pa"></span><div id="Fig-example-downlink-fragmentation-lorawan-packet-1">
3060 <figure id="figure-29">
3061 <div class="artwork art-text alignLeft" id="section-a.3-4.1">
3062 <pre>
3063 | LoRaWAN Header | LoRaWAN payload (51 bytes) |
3064 + ---- + ---------- + -------------------------------------- +
3065 | | RuleID=21 | W = 0 | FCN = 0 | 1 tile |
3066 + ---- + ---------- + ------ + ------- + ------------------- +
3067 | XXXX | 1 byte | 1 bit | 1 bit | 50 bytes and 6 bits |
3068 </pre>
3069 </div>
3070 <figcaption><a href="#figure-29" class="selfRef">Figure 29</a>:
3071 <a href="#name-downlink-example-lorawan-pa" class="selfRef">Downlink Example: LoRaWAN Packet 1 - SCHC Fragment 1</a>
3072 </figcaption></figure>
3073 </div>
3074 <p id="section-a.3-5">The tile content is described in <a href="#Fig-example-downlink-fragmentation-lorawan-packet-1-tile-content" class="xref">Figure 30</a><a href="#section-a.3-5" class="pilcrow">¶</a></p>
3075 <span id="name-downlink-example-first-tile"></span><div id="Fig-example-downlink-fragmentation-lorawan-packet-1-tile-content">
3076 <figure id="figure-30">
3077 <div class="artwork art-text alignLeft" id="section-a.3-6.1">
3078 <pre>
3079 | RuleID | Compression residue | Payload |
3080 + ------ + ------------------- + ------------------ +
3081 | 1 | 21 bits | 48 bytes and 1 bit |
3082 </pre>
3083 </div>
3084 <figcaption><a href="#figure-30" class="selfRef">Figure 30</a>:
3085 <a href="#name-downlink-example-first-tile" class="selfRef">Downlink Example: First Tile Content</a>
3086 </figcaption></figure>
3087 </div>
3088 <p id="section-a.3-7">The receiver answers with a SCHC ACK:<a href="#section-a.3-7" class="pilcrow">¶</a></p>
3089 <span id="name-downlink-example-lorawan-pac"></span><div id="Fig-example-downlink-fragmentation-lorawan-packet-2">
3090 <figure id="figure-31">
3091 <div class="artwork art-text alignLeft" id="section-a.3-8.1">
3092 <pre>
3093 | LoRaWAN Header | LoRaWAN payload |
3094 + ---- + --------- + -------------------------------- +
3095 | | RuleID=21 | W = 0 | C = 1 | Padding=b'000000 |
3096 + ---- + --------- + ----- + ----- + ---------------- +
3097 | XXXX | 1 byte | 1 bit | 1 bit | 6 bits |
3098 </pre>
3099 </div>
3100 <figcaption><a href="#figure-31" class="selfRef">Figure 31</a>:
3101 <a href="#name-downlink-example-lorawan-pac" class="selfRef">Downlink Example: LoRaWAN Packet 2 - SCHC ACK</a>
3102 </figcaption></figure>
3103 </div>
3104 <p id="section-a.3-9">The second downlink is sent, two FOpts:<a href="#section-a.3-9" class="pilcrow">¶</a></p>
3105 <span id="name-downlink-example-lorawan-pack"></span><div id="Fig-example-downlink-fragmentation-lorawan-packet-3">
3106 <figure id="figure-32">
3107 <div class="artwork art-text alignLeft" id="section-a.3-10.1">
3108 <pre>
3109 | LoRaWAN Header | LoRaWAN payload (49 bytes) |
3110 + --------------------------- + ------------------------------------- +
3111 | | FOpts | RuleID=21 | W = 1 | FCN = 0 | 1 tile |
3112 + ---- + ------- + ---------- + ----- + ------- + ------------------- +
3113 | XXXX | 2 bytes | 1 byte | 1 bit | 1 bit | 48 bytes and 6 bits |
3114 </pre>
3115 </div>
3116 <figcaption><a href="#figure-32" class="selfRef">Figure 32</a>:
3117 <a href="#name-downlink-example-lorawan-pack" class="selfRef">Downlink Example: LoRaWAN Packet 3 - SCHC Fragment 2</a>
3118 </figcaption></figure>
3119 </div>
3120 <p id="section-a.3-11">The receiver answers with a SCHC ACK:<a href="#section-a.3-11" class="pilcrow">¶</a></p>
3121 <span id="name-downlink-example-lorawan-packe"></span><div id="Fig-example-downlink-fragmentation-lorawan-packet-4">
3122 <figure id="figure-33">
3123 <div class="artwork art-text alignLeft" id="section-a.3-12.1">
3124 <pre>
3125 | LoRaWAN Header | LoRaWAN payload |
3126 + ---- + --------- + -------------------------------- +
3127 | | RuleID=21 | W = 1 | C = 1 | Padding=b'000000 |
3128 + ---- + --------- + ----- + ----- + ---------------- +
3129 | XXXX | 1 byte | 1 bit | 1 bit | 6 bits |
3130 </pre>
3131 </div>
3132 <figcaption><a href="#figure-33" class="selfRef">Figure 33</a>:
3133 <a href="#name-downlink-example-lorawan-packe" class="selfRef">Downlink Example: LoRaWAN Packet 4 - SCHC ACK</a>
3134 </figcaption></figure>
3135 </div>
3136 <p id="section-a.3-13">The last downlink is sent, no FOpts:<a href="#section-a.3-13" class="pilcrow">¶</a></p>
3137 <span id="name-downlink-example-lorawan-packet"></span><div id="Fig-example-downlink-fragmentation-lorawan-packet-5">
3138 <figure id="figure-34">
3139 <div class="artwork art-text alignLeft" id="section-a.3-14.1">
3140 <pre>
3141 | LoRaWAN Header | LoRaWAN payload (37 bytes) |
3142 + ---- + ------- + -------------------------------------------------- +
3143 | | RuleID | W | FCN | RCS | 1 tile | Padding |
3144 | | 21 | 0 | 1 | | | b'00000 |
3145 + ---- + ------- + ----- + ----- + ------- + -------------- + ------- +
3146 | XXXX | 1 byte | 1 bit | 1 bit | 4 bytes | 31 bytes+1 bit | 5 bits |
3147 </pre>
3148 </div>
3149 <figcaption><a href="#figure-34" class="selfRef">Figure 34</a>:
3150 <a href="#name-downlink-example-lorawan-packet" class="selfRef">Downlink Example: LoRaWAN Packet 5 - All-1 SCHC Message</a>
3151 </figcaption></figure>
3152 </div>
3153 <p id="section-a.3-15">The receiver answers to the sender with a SCHC ACK:<a href="#section-a.3-15" class="pilcrow">¶</a></p>
3154 <span id="name-downlink-example-lorawan-packet-"></span><div id="Fig-example-downlink-fragmentation-lorawan-packet-6">
3155 <figure id="figure-35">
3156 <div class="artwork art-text alignLeft" id="section-a.3-16.1">
3157 <pre>
3158 | LoRaWAN Header | LoRaWAN payload |
3159 + ---- + --------- + -------------------------------- +
3160 | | RuleID=21 | W = 0 | C = 1 | Padding=b'000000 |
3161 + ---- + --------- + ----- + ----- + ---------------- +
3162 | XXXX | 1 byte | 1 bit | 1 bit | 6 bits |
3163 </pre>
3164 </div>
3165 <figcaption><a href="#figure-35" class="selfRef">Figure 35</a>:
3166 <a href="#name-downlink-example-lorawan-packet-" class="selfRef">Downlink Example: LoRaWAN Packet 6 - SCHC ACK</a>
3167 </figcaption></figure>
3168 </div>
3169 </section>
3170 </div>
3171 </section>
3172 </div>
3173 <div id="acknowledgements">
3174 <section id="section-appendix.b">
3175 <h2 id="name-acknowledgements">
3176 <a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
3177 </h2>
3178 <p id="section-appendix.b-1">Thanks to all those listed in the Contributors Section for the
3179 excellent text, insightful discussions, reviews, and suggestions, and
3180 also to (in alphabetical order) <span class="contact-name">Dominique Barthel</span>,
3181 <span class="contact-name">Arunprabhu Kandasamy</span>, <span class="contact-name">Rodrigo Munoz</span>, <span class="contact-name">Alexander Pelov</span>, <span class="contact-name">Pascal Thubert</span>, and <span class="contact-name">Laurent Toutain</span> for
3182 useful design considerations, reviews, and comments.<a href="#section-appendix.b-1" class="pilcrow">¶</a></p>
3183 <p id="section-appendix.b-2">LoRaWAN is a registered trademark of the LoRa Alliance.<a href="#section-appendix.b-2" class="pilcrow">¶</a></p>
3184 </section>
3185 </div>
3186 <div id="contributors">
3187 <section id="section-appendix.c">
3188 <h2 id="name-contributors">
3189 <a href="#name-contributors" class="section-name selfRef">Contributors</a>
3190 </h2>
3191 <p id="section-appendix.c-1">Contributors ordered by family name.<a href="#section-appendix.c-1" class="pilcrow">¶</a></p>
3192 <address class="vcard">
3193 <div dir="auto" class="left"><span class="fn nameRole">Vincent Audebert</span></div>
3194 <div dir="auto" class="left"><span class="org">EDF R&amp;D</span></div>
3195 <div class="email">
3196 <span>Email:</span>
3197 <a href="mailto:[email protected]" class="email">[email protected]</a>
3198 </div>
3199 </address>
3200 <address class="vcard">
3201 <div dir="auto" class="left"><span class="fn nameRole">Julien Catalano</span></div>
3202 <div dir="auto" class="left"><span class="org">Kerlink</span></div>
3203 <div class="email">
3204 <span>Email:</span>
3205 <a href="mailto:[email protected]" class="email">[email protected]</a>
3206 </div>
3207 </address>
3208 <address class="vcard">
3209 <div dir="auto" class="left"><span class="fn nameRole">Michael Coracin</span></div>
3210 <div dir="auto" class="left"><span class="org">Semtech</span></div>
3211 <div class="email">
3212 <span>Email:</span>
3213 <a href="mailto:[email protected]" class="email">[email protected]</a>
3214 </div>
3215 </address>
3216 <address class="vcard">
3217 <div dir="auto" class="left"><span class="fn nameRole">Marc Le Gourrierec</span></div>
3218 <div dir="auto" class="left"><span class="org">Sagemcom</span></div>
3219 <div class="email">
3220 <span>Email:</span>
3221 <a href="mailto:[email protected]" class="email">[email protected]</a>
3222 </div>
3223 </address>
3224 <address class="vcard">
3225 <div dir="auto" class="left"><span class="fn nameRole">Nicolas Sornin</span></div>
3226 <div dir="auto" class="left"><span class="org">Chirp Foundation</span></div>
3227 <div class="email">
3228 <span>Email:</span>
3229 <a href="mailto:[email protected]" class="email">[email protected]</a>
3230 </div>
3231 </address>
3232 <address class="vcard">
3233 <div dir="auto" class="left"><span class="fn nameRole">Alper Yegin</span></div>
3234 <div dir="auto" class="left"><span class="org">Actility</span></div>
3235 <div class="email">
3236 <span>Email:</span>
3237 <a href="mailto:[email protected]" class="email">[email protected]</a>
3238 </div>
3239 </address>
3240 </section>
3241 </div>
3242 <div id="authors-addresses">
3243 <section id="section-appendix.d">
3244 <h2 id="name-authors-addresses">
3245 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
3246 </h2>
3247 <address class="vcard">
3248 <div dir="auto" class="left"><span class="fn nameRole">Olivier Gimenez (<span class="role">editor</span>)</span></div>
3249 <div dir="auto" class="left"><span class="org">Semtech</span></div>
3250 <div dir="auto" class="left"><span class="street-address">14 Chemin des Clos</span></div>
3251 <div dir="auto" class="left"><span class="locality">Meylan</span></div>
3252 <div dir="auto" class="left"><span class="country-name">France</span></div>
3253 <div class="email">
3254 <span>Email:</span>
3255 <a href="mailto:[email protected]" class="email">[email protected]</a>
3256 </div>
3257 </address>
3258 <address class="vcard">
3259 <div dir="auto" class="left"><span class="fn nameRole">Ivaylo Petrov (<span class="role">editor</span>)</span></div>
3260 <div dir="auto" class="left"><span class="org">Acklio</span></div>
3261 <div dir="auto" class="left"><span class="street-address">1137A Avenue des Champs Blancs</span></div>
3262 <div dir="auto" class="left">
3263 <span class="postal-code">35510</span> <span class="locality">Cesson-Sévigné Cedex</span>
3264 </div>
3265 <div dir="auto" class="left"><span class="country-name">France</span></div>
3266 <div class="email">
3267 <span>Email:</span>
3268 <a href="mailto:[email protected]" class="email">[email protected]</a>
3269 </div>
3270 </address>
3271 </section>
3272 </div>
3273 <script>const toc = document.getElementById("toc");
3274 toc.querySelector("h2").addEventListener("click", e => {
3275 toc.classList.toggle("active");
3276 });
3277 toc.querySelector("nav").addEventListener("click", e => {
3278 toc.classList.remove("active");
3279 });
3280 </script>
3281 </body>
3282 </html>