Debian Codegraph @

rfc9188.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 9188: Generic Multi-Access (GMA) Encapsulation Protocol</title>
8 <meta content="Jing Zhu" name="author">
9 <meta content="Satish Kanugovi" name="author">
10 <meta content="
11
12 A device can be simultaneously connected to multiple networks, e.g., Wi-Fi,
13 LTE, 5G, and DSL. It is desirable to seamlessly combine the connectivity
14 over these networks below the transport layer (L4) to improve the quality
15 of experience for applications that do not have built-in multi-path
16 capabilities. Such optimization requires additional control information,
17 e.g., a sequence number, in each packet. This document presents a new
18 lightweight and flexible encapsulation protocol for this need. The solution
19 has been developed by the authors based on their experiences in multiple
20 standards bodies including the IETF and 3GPP. However, this document is not
21 an Internet Standard and does not represent the consensus opinion of
22 the IETF. This document will enable other developers to build interoperable
23 implementations in order to experiment with the protocol.
24 " name="description">
25 <meta content="xml2rfc 3.12.1" name="generator">
26 <meta content="9188" name="rfc.number">
27 <!-- Generator version information:
28 xml2rfc 3.12.1
29 Python 3.6.15
30 appdirs 1.4.4
31 ConfigArgParse 1.4.1
32 google-i18n-address 2.4.0
33 html5lib 1.0.1
34 intervaltree 3.0.2
35 Jinja2 2.11.3
36 kitchen 1.2.6
37 lxml 4.4.2
38 pycairo 1.15.1
39 pycountry 19.8.18
40 pyflakes 2.1.1
41 PyYAML 5.4.1
42 requests 2.24.0
43 setuptools 40.5.0
44 six 1.14.0
45 WeasyPrint 52.5
46 -->
47 <link href="rfc9188.xml" rel="alternate" type="application/rfc+xml">
48 <link href="#copyright" rel="license">
49 <style type="text/css">/*
50
51 NOTE: Changes at the bottom of this file overrides some earlier settings.
52
53 Once the style has stabilized and has been adopted as an official RFC style,
54 this can be consolidated so that style settings occur only in one place, but
55 for now the contents of this file consists first of the initial CSS work as
56 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
57 commented changes found necssary during the development of the v3
58 formatters.
59
60 */
61
62 /* fonts */
63 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
64 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
65 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
66
67 @viewport {
68 zoom: 1.0;
69 width: extend-to-zoom;
70 }
71 @-ms-viewport {
72 width: extend-to-zoom;
73 zoom: 1.0;
74 }
75 /* general and mobile first */
76 html {
77 }
78 body {
79 max-width: 90%;
80 margin: 1.5em auto;
81 color: #222;
82 background-color: #fff;
83 font-size: 14px;
84 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
85 line-height: 1.6;
86 scroll-behavior: smooth;
87 }
88 .ears {
89 display: none;
90 }
91
92 /* headings */
93 #title, h1, h2, h3, h4, h5, h6 {
94 margin: 1em 0 0.5em;
95 font-weight: bold;
96 line-height: 1.3;
97 }
98 #title {
99 clear: both;
100 border-bottom: 1px solid #ddd;
101 margin: 0 0 0.5em 0;
102 padding: 1em 0 0.5em;
103 }
104 .author {
105 padding-bottom: 4px;
106 }
107 h1 {
108 font-size: 26px;
109 margin: 1em 0;
110 }
111 h2 {
112 font-size: 22px;
113 margin-top: -20px; /* provide offset for in-page anchors */
114 padding-top: 33px;
115 }
116 h3 {
117 font-size: 18px;
118 margin-top: -36px; /* provide offset for in-page anchors */
119 padding-top: 42px;
120 }
121 h4 {
122 font-size: 16px;
123 margin-top: -36px; /* provide offset for in-page anchors */
124 padding-top: 42px;
125 }
126 h5, h6 {
127 font-size: 14px;
128 }
129 #n-copyright-notice {
130 border-bottom: 1px solid #ddd;
131 padding-bottom: 1em;
132 margin-bottom: 1em;
133 }
134 /* general structure */
135 p {
136 padding: 0;
137 margin: 0 0 1em 0;
138 text-align: left;
139 }
140 div, span {
141 position: relative;
142 }
143 div {
144 margin: 0;
145 }
146 .alignRight.art-text {
147 background-color: #f9f9f9;
148 border: 1px solid #eee;
149 border-radius: 3px;
150 padding: 1em 1em 0;
151 margin-bottom: 1.5em;
152 }
153 .alignRight.art-text pre {
154 padding: 0;
155 }
156 .alignRight {
157 margin: 1em 0;
158 }
159 .alignRight > *:first-child {
160 border: none;
161 margin: 0;
162 float: right;
163 clear: both;
164 }
165 .alignRight > *:nth-child(2) {
166 clear: both;
167 display: block;
168 border: none;
169 }
170 svg {
171 display: block;
172 }
173 .alignCenter.art-text {
174 background-color: #f9f9f9;
175 border: 1px solid #eee;
176 border-radius: 3px;
177 padding: 1em 1em 0;
178 margin-bottom: 1.5em;
179 }
180 .alignCenter.art-text pre {
181 padding: 0;
182 }
183 .alignCenter {
184 margin: 1em 0;
185 }
186 .alignCenter > *:first-child {
187 border: none;
188 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
189 support flexbox yet.
190 */
191 display: table;
192 margin: 0 auto;
193 }
194
195 /* lists */
196 ol, ul {
197 padding: 0;
198 margin: 0 0 1em 2em;
199 }
200 ol ol, ul ul, ol ul, ul ol {
201 margin-left: 1em;
202 }
203 li {
204 margin: 0 0 0.25em 0;
205 }
206 .ulCompact li {
207 margin: 0;
208 }
209 ul.empty, .ulEmpty {
210 list-style-type: none;
211 }
212 ul.empty li, .ulEmpty li {
213 margin-top: 0.5em;
214 }
215 ul.ulBare, li.ulBare {
216 margin-left: 0em !important;
217 }
218 ul.compact, .ulCompact,
219 ol.compact, .olCompact {
220 line-height: 100%;
221 margin: 0 0 0 2em;
222 }
223
224 /* definition lists */
225 dl {
226 }
227 dl > dt {
228 float: left;
229 margin-right: 1em;
230 }
231 /*
232 dl.nohang > dt {
233 float: none;
234 }
235 */
236 dl > dd {
237 margin-bottom: .8em;
238 min-height: 1.3em;
239 }
240 dl.compact > dd, .dlCompact > dd {
241 margin-bottom: 0em;
242 }
243 dl > dd > dl {
244 margin-top: 0.5em;
245 margin-bottom: 0em;
246 }
247
248 /* links */
249 a {
250 text-decoration: none;
251 }
252 a[href] {
253 color: #22e; /* Arlen: WCAG 2019 */
254 }
255 a[href]:hover {
256 background-color: #f2f2f2;
257 }
258 figcaption a[href],
259 a[href].selfRef {
260 color: #222;
261 }
262 /* XXX probably not this:
263 a.selfRef:hover {
264 background-color: transparent;
265 cursor: default;
266 } */
267
268 /* Figures */
269 tt, code, pre, code {
270 background-color: #f9f9f9;
271 font-family: 'Roboto Mono', monospace;
272 }
273 pre {
274 border: 1px solid #eee;
275 margin: 0;
276 padding: 1em;
277 }
278 img {
279 max-width: 100%;
280 }
281 figure {
282 margin: 0;
283 }
284 figure blockquote {
285 margin: 0.8em 0.4em 0.4em;
286 }
287 figcaption {
288 font-style: italic;
289 margin: 0 0 1em 0;
290 }
291 @media screen {
292 pre {
293 overflow-x: auto;
294 max-width: 100%;
295 max-width: calc(100% - 22px);
296 }
297 }
298
299 /* aside, blockquote */
300 aside, blockquote {
301 margin-left: 0;
302 padding: 1.2em 2em;
303 }
304 blockquote {
305 background-color: #f9f9f9;
306 color: #111; /* Arlen: WCAG 2019 */
307 border: 1px solid #ddd;
308 border-radius: 3px;
309 margin: 1em 0;
310 }
311 cite {
312 display: block;
313 text-align: right;
314 font-style: italic;
315 }
316
317 /* tables */
318 table {
319 width: 100%;
320 margin: 0 0 1em;
321 border-collapse: collapse;
322 border: 1px solid #eee;
323 }
324 th, td {
325 text-align: left;
326 vertical-align: top;
327 padding: 0.5em 0.75em;
328 }
329 th {
330 text-align: left;
331 background-color: #e9e9e9;
332 }
333 tr:nth-child(2n+1) > td {
334 background-color: #f5f5f5;
335 }
336 table caption {
337 font-style: italic;
338 margin: 0;
339 padding: 0;
340 text-align: left;
341 }
342 table p {
343 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
344 be allowed within tables more generally, it would be far better to select on a class. */
345 margin: 0;
346 }
347
348 /* pilcrow */
349 a.pilcrow {
350 color: #666; /* Arlen: AHDJ 2019 */
351 text-decoration: none;
352 visibility: hidden;
353 user-select: none;
354 -ms-user-select: none;
355 -o-user-select:none;
356 -moz-user-select: none;
357 -khtml-user-select: none;
358 -webkit-user-select: none;
359 -webkit-touch-callout: none;
360 }
361 @media screen {
362 aside:hover > a.pilcrow,
363 p:hover > a.pilcrow,
364 blockquote:hover > a.pilcrow,
365 div:hover > a.pilcrow,
366 li:hover > a.pilcrow,
367 pre:hover > a.pilcrow {
368 visibility: visible;
369 }
370 a.pilcrow:hover {
371 background-color: transparent;
372 }
373 }
374
375 /* misc */
376 hr {
377 border: 0;
378 border-top: 1px solid #eee;
379 }
380 .bcp14 {
381 font-variant: small-caps;
382 }
383
384 .role {
385 font-variant: all-small-caps;
386 }
387
388 /* info block */
389 #identifiers {
390 margin: 0;
391 font-size: 0.9em;
392 }
393 #identifiers dt {
394 width: 3em;
395 clear: left;
396 }
397 #identifiers dd {
398 float: left;
399 margin-bottom: 0;
400 }
401 /* Fix PDF info block run off issue */
402 @media print {
403 #identifiers dd {
404 float: none;
405 }
406 }
407 #identifiers .authors .author {
408 display: inline-block;
409 margin-right: 1.5em;
410 }
411 #identifiers .authors .org {
412 font-style: italic;
413 }
414
415 /* The prepared/rendered info at the very bottom of the page */
416 .docInfo {
417 color: #666; /* Arlen: WCAG 2019 */
418 font-size: 0.9em;
419 font-style: italic;
420 margin-top: 2em;
421 }
422 .docInfo .prepared {
423 float: left;
424 }
425 .docInfo .prepared {
426 float: right;
427 }
428
429 /* table of contents */
430 #toc {
431 padding: 0.75em 0 2em 0;
432 margin-bottom: 1em;
433 }
434 nav.toc ul {
435 margin: 0 0.5em 0 0;
436 padding: 0;
437 list-style: none;
438 }
439 nav.toc li {
440 line-height: 1.3em;
441 margin: 0.75em 0;
442 padding-left: 1.2em;
443 text-indent: -1.2em;
444 }
445 /* references */
446 .references dt {
447 text-align: right;
448 font-weight: bold;
449 min-width: 7em;
450 }
451 .references dd {
452 margin-left: 8em;
453 overflow: auto;
454 }
455
456 .refInstance {
457 margin-bottom: 1.25em;
458 }
459
460 .references .ascii {
461 margin-bottom: 0.25em;
462 }
463
464 /* index */
465 .index ul {
466 margin: 0 0 0 1em;
467 padding: 0;
468 list-style: none;
469 }
470 .index ul ul {
471 margin: 0;
472 }
473 .index li {
474 margin: 0;
475 text-indent: -2em;
476 padding-left: 2em;
477 padding-bottom: 5px;
478 }
479 .indexIndex {
480 margin: 0.5em 0 1em;
481 }
482 .index a {
483 font-weight: 700;
484 }
485 /* make the index two-column on all but the smallest screens */
486 @media (min-width: 600px) {
487 .index ul {
488 -moz-column-count: 2;
489 -moz-column-gap: 20px;
490 }
491 .index ul ul {
492 -moz-column-count: 1;
493 -moz-column-gap: 0;
494 }
495 }
496
497 /* authors */
498 address.vcard {
499 font-style: normal;
500 margin: 1em 0;
501 }
502
503 address.vcard .nameRole {
504 font-weight: 700;
505 margin-left: 0;
506 }
507 address.vcard .label {
508 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
509 margin: 0.5em 0;
510 }
511 address.vcard .type {
512 display: none;
513 }
514 .alternative-contact {
515 margin: 1.5em 0 1em;
516 }
517 hr.addr {
518 border-top: 1px dashed;
519 margin: 0;
520 color: #ddd;
521 max-width: calc(100% - 16px);
522 }
523
524 /* temporary notes */
525 .rfcEditorRemove::before {
526 position: absolute;
527 top: 0.2em;
528 right: 0.2em;
529 padding: 0.2em;
530 content: "The RFC Editor will remove this note";
531 color: #9e2a00; /* Arlen: WCAG 2019 */
532 background-color: #ffd; /* Arlen: WCAG 2019 */
533 }
534 .rfcEditorRemove {
535 position: relative;
536 padding-top: 1.8em;
537 background-color: #ffd; /* Arlen: WCAG 2019 */
538 border-radius: 3px;
539 }
540 .cref {
541 background-color: #ffd; /* Arlen: WCAG 2019 */
542 padding: 2px 4px;
543 }
544 .crefSource {
545 font-style: italic;
546 }
547 /* alternative layout for smaller screens */
548 @media screen and (max-width: 1023px) {
549 body {
550 padding-top: 2em;
551 }
552 #title {
553 padding: 1em 0;
554 }
555 h1 {
556 font-size: 24px;
557 }
558 h2 {
559 font-size: 20px;
560 margin-top: -18px; /* provide offset for in-page anchors */
561 padding-top: 38px;
562 }
563 #identifiers dd {
564 max-width: 60%;
565 }
566 #toc {
567 position: fixed;
568 z-index: 2;
569 top: 0;
570 right: 0;
571 padding: 0;
572 margin: 0;
573 background-color: inherit;
574 border-bottom: 1px solid #ccc;
575 }
576 #toc h2 {
577 margin: -1px 0 0 0;
578 padding: 4px 0 4px 6px;
579 padding-right: 1em;
580 min-width: 190px;
581 font-size: 1.1em;
582 text-align: right;
583 background-color: #444;
584 color: white;
585 cursor: pointer;
586 }
587 #toc h2::before { /* css hamburger */
588 float: right;
589 position: relative;
590 width: 1em;
591 height: 1px;
592 left: -164px;
593 margin: 6px 0 0 0;
594 background: white none repeat scroll 0 0;
595 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
596 content: "";
597 }
598 #toc nav {
599 display: none;
600 padding: 0.5em 1em 1em;
601 overflow: auto;
602 height: calc(100vh - 48px);
603 border-left: 1px solid #ddd;
604 }
605 }
606
607 /* alternative layout for wide screens */
608 @media screen and (min-width: 1024px) {
609 body {
610 max-width: 724px;
611 margin: 42px auto;
612 padding-left: 1.5em;
613 padding-right: 29em;
614 }
615 #toc {
616 position: fixed;
617 top: 42px;
618 right: 42px;
619 width: 25%;
620 margin: 0;
621 padding: 0 1em;
622 z-index: 1;
623 }
624 #toc h2 {
625 border-top: none;
626 border-bottom: 1px solid #ddd;
627 font-size: 1em;
628 font-weight: normal;
629 margin: 0;
630 padding: 0.25em 1em 1em 0;
631 }
632 #toc nav {
633 display: block;
634 height: calc(90vh - 84px);
635 bottom: 0;
636 padding: 0.5em 0 0;
637 overflow: auto;
638 }
639 img { /* future proofing */
640 max-width: 100%;
641 height: auto;
642 }
643 }
644
645 /* pagination */
646 @media print {
647 body {
648
649 width: 100%;
650 }
651 p {
652 orphans: 3;
653 widows: 3;
654 }
655 #n-copyright-notice {
656 border-bottom: none;
657 }
658 #toc, #n-introduction {
659 page-break-before: always;
660 }
661 #toc {
662 border-top: none;
663 padding-top: 0;
664 }
665 figure, pre {
666 page-break-inside: avoid;
667 }
668 figure {
669 overflow: scroll;
670 }
671 h1, h2, h3, h4, h5, h6 {
672 page-break-after: avoid;
673 }
674 h2+*, h3+*, h4+*, h5+*, h6+* {
675 page-break-before: avoid;
676 }
677 pre {
678 white-space: pre-wrap;
679 word-wrap: break-word;
680 font-size: 10pt;
681 }
682 table {
683 border: 1px solid #ddd;
684 }
685 td {
686 border-top: 1px solid #ddd;
687 }
688 }
689
690 /* This is commented out here, as the string-set: doesn't
691 pass W3C validation currently */
692 /*
693 .ears thead .left {
694 string-set: ears-top-left content();
695 }
696
697 .ears thead .center {
698 string-set: ears-top-center content();
699 }
700
701 .ears thead .right {
702 string-set: ears-top-right content();
703 }
704
705 .ears tfoot .left {
706 string-set: ears-bottom-left content();
707 }
708
709 .ears tfoot .center {
710 string-set: ears-bottom-center content();
711 }
712
713 .ears tfoot .right {
714 string-set: ears-bottom-right content();
715 }
716 */
717
718 @page :first {
719 padding-top: 0;
720 @top-left {
721 content: normal;
722 border: none;
723 }
724 @top-center {
725 content: normal;
726 border: none;
727 }
728 @top-right {
729 content: normal;
730 border: none;
731 }
732 }
733
734 @page {
735 size: A4;
736 margin-bottom: 45mm;
737 padding-top: 20px;
738 /* The follwing is commented out here, but set appropriately by in code, as
739 the content depends on the document */
740 /*
741 @top-left {
742 content: 'Internet-Draft';
743 vertical-align: bottom;
744 border-bottom: solid 1px #ccc;
745 }
746 @top-left {
747 content: string(ears-top-left);
748 vertical-align: bottom;
749 border-bottom: solid 1px #ccc;
750 }
751 @top-center {
752 content: string(ears-top-center);
753 vertical-align: bottom;
754 border-bottom: solid 1px #ccc;
755 }
756 @top-right {
757 content: string(ears-top-right);
758 vertical-align: bottom;
759 border-bottom: solid 1px #ccc;
760 }
761 @bottom-left {
762 content: string(ears-bottom-left);
763 vertical-align: top;
764 border-top: solid 1px #ccc;
765 }
766 @bottom-center {
767 content: string(ears-bottom-center);
768 vertical-align: top;
769 border-top: solid 1px #ccc;
770 }
771 @bottom-right {
772 content: '[Page ' counter(page) ']';
773 vertical-align: top;
774 border-top: solid 1px #ccc;
775 }
776 */
777
778 }
779
780 /* Changes introduced to fix issues found during implementation */
781 /* Make sure links are clickable even if overlapped by following H* */
782 a {
783 z-index: 2;
784 }
785 /* Separate body from document info even without intervening H1 */
786 section {
787 clear: both;
788 }
789
790
791 /* Top align author divs, to avoid names without organization dropping level with org names */
792 .author {
793 vertical-align: top;
794 }
795
796 /* Leave room in document info to show Internet-Draft on one line */
797 #identifiers dt {
798 width: 8em;
799 }
800
801 /* Don't waste quite as much whitespace between label and value in doc info */
802 #identifiers dd {
803 margin-left: 1em;
804 }
805
806 /* Give floating toc a background color (needed when it's a div inside section */
807 #toc {
808 background-color: white;
809 }
810
811 /* Make the collapsed ToC header render white on gray also when it's a link */
812 @media screen and (max-width: 1023px) {
813 #toc h2 a,
814 #toc h2 a:link,
815 #toc h2 a:focus,
816 #toc h2 a:hover,
817 #toc a.toplink,
818 #toc a.toplink:hover {
819 color: white;
820 background-color: #444;
821 text-decoration: none;
822 }
823 }
824
825 /* Give the bottom of the ToC some whitespace */
826 @media screen and (min-width: 1024px) {
827 #toc {
828 padding: 0 0 1em 1em;
829 }
830 }
831
832 /* Style section numbers with more space between number and title */
833 .section-number {
834 padding-right: 0.5em;
835 }
836
837 /* prevent monospace from becoming overly large */
838 tt, code, pre, code {
839 font-size: 95%;
840 }
841
842 /* Fix the height/width aspect for ascii art*/
843 pre.sourcecode,
844 .art-text pre {
845 line-height: 1.12;
846 }
847
848
849 /* Add styling for a link in the ToC that points to the top of the document */
850 a.toplink {
851 float: right;
852 margin-right: 0.5em;
853 }
854
855 /* Fix the dl styling to match the RFC 7992 attributes */
856 dl > dt,
857 dl.dlParallel > dt {
858 float: left;
859 margin-right: 1em;
860 }
861 dl.dlNewline > dt {
862 float: none;
863 }
864
865 /* Provide styling for table cell text alignment */
866 table td.text-left,
867 table th.text-left {
868 text-align: left;
869 }
870 table td.text-center,
871 table th.text-center {
872 text-align: center;
873 }
874 table td.text-right,
875 table th.text-right {
876 text-align: right;
877 }
878
879 /* Make the alternative author contact informatio look less like just another
880 author, and group it closer with the primary author contact information */
881 .alternative-contact {
882 margin: 0.5em 0 0.25em 0;
883 }
884 address .non-ascii {
885 margin: 0 0 0 2em;
886 }
887
888 /* With it being possible to set tables with alignment
889 left, center, and right, { width: 100%; } does not make sense */
890 table {
891 width: auto;
892 }
893
894 /* Avoid reference text that sits in a block with very wide left margin,
895 because of a long floating dt label.*/
896 .references dd {
897 overflow: visible;
898 }
899
900 /* Control caption placement */
901 caption {
902 caption-side: bottom;
903 }
904
905 /* Limit the width of the author address vcard, so names in right-to-left
906 script don't end up on the other side of the page. */
907
908 address.vcard {
909 max-width: 30em;
910 margin-right: auto;
911 }
912
913 /* For address alignment dependent on LTR or RTL scripts */
914 address div.left {
915 text-align: left;
916 }
917 address div.right {
918 text-align: right;
919 }
920
921 /* Provide table alignment support. We can't use the alignX classes above
922 since they do unwanted things with caption and other styling. */
923 table.right {
924 margin-left: auto;
925 margin-right: 0;
926 }
927 table.center {
928 margin-left: auto;
929 margin-right: auto;
930 }
931 table.left {
932 margin-left: 0;
933 margin-right: auto;
934 }
935
936 /* Give the table caption label the same styling as the figcaption */
937 caption a[href] {
938 color: #222;
939 }
940
941 @media print {
942 .toplink {
943 display: none;
944 }
945
946 /* avoid overwriting the top border line with the ToC header */
947 #toc {
948 padding-top: 1px;
949 }
950
951 /* Avoid page breaks inside dl and author address entries */
952 .vcard {
953 page-break-inside: avoid;
954 }
955
956 }
957 /* Tweak the bcp14 keyword presentation */
958 .bcp14 {
959 font-variant: small-caps;
960 font-weight: bold;
961 font-size: 0.9em;
962 }
963 /* Tweak the invisible space above H* in order not to overlay links in text above */
964 h2 {
965 margin-top: -18px; /* provide offset for in-page anchors */
966 padding-top: 31px;
967 }
968 h3 {
969 margin-top: -18px; /* provide offset for in-page anchors */
970 padding-top: 24px;
971 }
972 h4 {
973 margin-top: -18px; /* provide offset for in-page anchors */
974 padding-top: 24px;
975 }
976 /* Float artwork pilcrow to the right */
977 @media screen {
978 .artwork a.pilcrow {
979 display: block;
980 line-height: 0.7;
981 margin-top: 0.15em;
982 }
983 }
984 /* Make pilcrows on dd visible */
985 @media screen {
986 dd:hover > a.pilcrow {
987 visibility: visible;
988 }
989 }
990 /* Make the placement of figcaption match that of a table's caption
991 by removing the figure's added bottom margin */
992 .alignLeft.art-text,
993 .alignCenter.art-text,
994 .alignRight.art-text {
995 margin-bottom: 0;
996 }
997 .alignLeft,
998 .alignCenter,
999 .alignRight {
1000 margin: 1em 0 0 0;
1001 }
1002 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
1003 possibly even requiring a new line */
1004 @media print {
1005 a.pilcrow {
1006 display: none;
1007 }
1008 }
1009 /* Styling for the external metadata */
1010 div#external-metadata {
1011 background-color: #eee;
1012 padding: 0.5em;
1013 margin-bottom: 0.5em;
1014 display: none;
1015 }
1016 div#internal-metadata {
1017 padding: 0.5em; /* to match the external-metadata padding */
1018 }
1019 /* Styling for title RFC Number */
1020 h1#rfcnum {
1021 clear: both;
1022 margin: 0 0 -1em;
1023 padding: 1em 0 0 0;
1024 }
1025 /* Make .olPercent look the same as <ol><li> */
1026 dl.olPercent > dd {
1027 margin-bottom: 0.25em;
1028 min-height: initial;
1029 }
1030 /* Give aside some styling to set it apart */
1031 aside {
1032 border-left: 1px solid #ddd;
1033 margin: 1em 0 1em 2em;
1034 padding: 0.2em 2em;
1035 }
1036 aside > dl,
1037 aside > ol,
1038 aside > ul,
1039 aside > table,
1040 aside > p {
1041 margin-bottom: 0.5em;
1042 }
1043 /* Additional page break settings */
1044 @media print {
1045 figcaption, table caption {
1046 page-break-before: avoid;
1047 }
1048 }
1049 /* Font size adjustments for print */
1050 @media print {
1051 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1052 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1053 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1054 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1055 h4 { font-size: 1em; padding-top: 1.5em; }
1056 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1057 }
1058 /* Sourcecode margin in print, when there's no pilcrow */
1059 @media print {
1060 .artwork,
1061 .sourcecode {
1062 margin-bottom: 1em;
1063 }
1064 }
1065 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1066 table {
1067 min-width: 20em;
1068 }
1069 /* ol type a */
1070 ol.type-a { list-style-type: lower-alpha; }
1071 ol.type-A { list-style-type: upper-alpha; }
1072 ol.type-i { list-style-type: lower-roman; }
1073 ol.type-I { list-style-type: lower-roman; }
1074 /* Apply the print table and row borders in general, on request from the RPC,
1075 and increase the contrast between border and odd row background sligthtly */
1076 table {
1077 border: 1px solid #ddd;
1078 }
1079 td {
1080 border-top: 1px solid #ddd;
1081 }
1082 tr:nth-child(2n+1) > td {
1083 background-color: #f8f8f8;
1084 }
1085 /* Use style rules to govern display of the TOC. */
1086 @media screen and (max-width: 1023px) {
1087 #toc nav { display: none; }
1088 #toc.active nav { display: block; }
1089 }
1090 /* Add support for keepWithNext */
1091 .keepWithNext {
1092 break-after: avoid-page;
1093 break-after: avoid-page;
1094 }
1095 /* Add support for keepWithPrevious */
1096 .keepWithPrevious {
1097 break-before: avoid-page;
1098 }
1099 /* Change the approach to avoiding breaks inside artwork etc. */
1100 figure, pre, table, .artwork, .sourcecode {
1101 break-before: auto;
1102 break-after: auto;
1103 }
1104 /* Avoid breaks between <dt> and <dd> */
1105 dl {
1106 break-before: auto;
1107 break-inside: auto;
1108 }
1109 dt {
1110 break-before: auto;
1111 break-after: avoid-page;
1112 }
1113 dd {
1114 break-before: avoid-page;
1115 break-after: auto;
1116 orphans: 3;
1117 widows: 3
1118 }
1119 span.break, dd.break {
1120 margin-bottom: 0;
1121 min-height: 0;
1122 break-before: auto;
1123 break-inside: auto;
1124 break-after: auto;
1125 }
1126 /* Undo break-before ToC */
1127 @media print {
1128 #toc {
1129 break-before: auto;
1130 }
1131 }
1132 /* Text in compact lists should not get extra bottim margin space,
1133 since that would makes the list not compact */
1134 ul.compact p, .ulCompact p,
1135 ol.compact p, .olCompact p {
1136 margin: 0;
1137 }
1138 /* But the list as a whole needs the extra space at the end */
1139 section ul.compact,
1140 section .ulCompact,
1141 section ol.compact,
1142 section .olCompact {
1143 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1144 }
1145 /* The tt and code background above interferes with for instance table cell
1146 backgrounds. Changed to something a bit more selective. */
1147 tt, code {
1148 background-color: transparent;
1149 }
1150 p tt, p code, li tt, li code {
1151 background-color: #f8f8f8;
1152 }
1153 /* Tweak the pre margin -- 0px doesn't come out well */
1154 pre {
1155 margin-top: 0.5px;
1156 }
1157 /* Tweak the comact list text */
1158 ul.compact, .ulCompact,
1159 ol.compact, .olCompact,
1160 dl.compact, .dlCompact {
1161 line-height: normal;
1162 }
1163 /* Don't add top margin for nested lists */
1164 li > ul, li > ol, li > dl,
1165 dd > ul, dd > ol, dd > dl,
1166 dl > dd > dl {
1167 margin-top: initial;
1168 }
1169 /* Elements that should not be rendered on the same line as a <dt> */
1170 /* This should match the element list in writer.text.TextWriter.render_dl() */
1171 dd > div.artwork:first-child,
1172 dd > aside:first-child,
1173 dd > figure:first-child,
1174 dd > ol:first-child,
1175 dd > div:first-child > pre.sourcecode,
1176 dd > table:first-child,
1177 dd > ul:first-child {
1178 clear: left;
1179 }
1180 /* fix for weird browser behaviour when <dd/> is empty */
1181 dt+dd:empty::before{
1182 content: "\00a0";
1183 }
1184 /* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
1185 li > p {
1186 margin-bottom: 0.5em
1187 }
1188 /* Don't let p margin spill out from inside list items */
1189 li > p:last-of-type {
1190 margin-bottom: 0;
1191 }
1192 </style>
1193 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1194 <link href="https://dx.doi.org/10.17487/rfc9188" rel="alternate">
1195 <link href="urn:issn:2070-1721" rel="alternate">
1196 <link href="https://datatracker.ietf.org/doc/draft-zhu-intarea-gma-14" rel="prev">
1197 </head>
1198 <body>
1199 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1200 <table class="ears">
1201 <thead><tr>
1202 <td class="left">RFC 9188</td>
1203 <td class="center">GMA Encapsulation Protocol</td>
1204 <td class="right">February 2022</td>
1205 </tr></thead>
1206 <tfoot><tr>
1207 <td class="left">Zhu &amp; Kanugovi</td>
1208 <td class="center">Experimental</td>
1209 <td class="right">[Page]</td>
1210 </tr></tfoot>
1211 </table>
1212 <div id="external-metadata" class="document-information"></div>
1213 <div id="internal-metadata" class="document-information">
1214 <dl id="identifiers">
1215 <dt class="label-stream">Stream:</dt>
1216 <dd class="stream">Independent Submission</dd>
1217 <dt class="label-rfc">RFC:</dt>
1218 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9188" class="eref">9188</a></dd>
1219 <dt class="label-category">Category:</dt>
1220 <dd class="category">Experimental</dd>
1221 <dt class="label-published">Published:</dt>
1222 <dd class="published">
1223 <time datetime="2022-02" class="published">February 2022</time>
1224 </dd>
1225 <dt class="label-issn">ISSN:</dt>
1226 <dd class="issn">2070-1721</dd>
1227 <dt class="label-authors">Authors:</dt>
1228 <dd class="authors">
1229 <div class="author">
1230 <div class="author-name">J. Zhu</div>
1231 <div class="org">Intel</div>
1232 </div>
1233 <div class="author">
1234 <div class="author-name">S. Kanugovi</div>
1235 <div class="org">Nokia</div>
1236 </div>
1237 </dd>
1238 </dl>
1239 </div>
1240 <h1 id="rfcnum">RFC 9188</h1>
1241 <h1 id="title">Generic Multi-Access (GMA) Encapsulation Protocol</h1>
1242 <section id="section-abstract">
1243 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1244 <p id="section-abstract-1">
1245 A device can be simultaneously connected to multiple networks, e.g., Wi-Fi,
1246 LTE, 5G, and DSL. It is desirable to seamlessly combine the connectivity
1247 over these networks below the transport layer (L4) to improve the quality
1248 of experience for applications that do not have built-in multi-path
1249 capabilities. Such optimization requires additional control information,
1250 e.g., a sequence number, in each packet. This document presents a new
1251 lightweight and flexible encapsulation protocol for this need. The solution
1252 has been developed by the authors based on their experiences in multiple
1253 standards bodies including the IETF and 3GPP. However, this document is not
1254 an Internet Standard and does not represent the consensus opinion of
1255 the IETF. This document will enable other developers to build interoperable
1256 implementations in order to experiment with the protocol.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1257 </section>
1258 <div id="status-of-memo">
1259 <section id="section-boilerplate.1">
1260 <h2 id="name-status-of-this-memo">
1261 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1262 </h2>
1263 <p id="section-boilerplate.1-1">
1264 This document is not an Internet Standards Track specification; it is
1265 published for examination, experimental implementation, and
1266 evaluation.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1267 <p id="section-boilerplate.1-2">
1268 This document defines an Experimental Protocol for the Internet
1269 community. This is a contribution to the RFC Series,
1270 independently of any other RFC stream. The RFC Editor has chosen to publish this
1271 document at its discretion and makes no statement about its value
1272 for implementation or deployment. Documents approved for publication
1273 by the RFC Editor are not candidates for any level of Internet
1274 Standard; see Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1275 <p id="section-boilerplate.1-3">
1276 Information about the current status of this document, any
1277 errata, and how to provide feedback on it may be obtained at
1278 <span><a href="https://www.rfc-editor.org/info/rfc9188">https://www.rfc-editor.org/info/rfc9188</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1279 </section>
1280 </div>
1281 <div id="copyright">
1282 <section id="section-boilerplate.2">
1283 <h2 id="name-copyright-notice">
1284 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1285 </h2>
1286 <p id="section-boilerplate.2-1">
1287 Copyright (c) 2022 IETF Trust and the persons identified as the
1288 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1289 <p id="section-boilerplate.2-2">
1290 This document is subject to BCP 78 and the IETF Trust's Legal
1291 Provisions Relating to IETF Documents
1292 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1293 publication of this document. Please review these documents
1294 carefully, as they describe your rights and restrictions with
1295 respect to this document.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1296 </section>
1297 </div>
1298 <div id="toc">
1299 <section id="section-toc.1">
1300 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1301 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1302 </h2>
1303 <nav class="toc"><ul class="compact toc ulBare ulEmpty">
1304 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
1305 <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>
1306 <ul class="compact toc ulBare ulEmpty">
1307 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.1">
1308 <p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-scope-of-experiment" class="xref">Scope of Experiment</a></p>
1309 </li>
1310 </ul>
1311 </li>
1312 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
1313 <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-conventions-used-in-this-do" class="xref">Conventions Used in This Document</a></p>
1314 </li>
1315 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3">
1316 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-use-case" class="xref">Use Case</a></p>
1317 </li>
1318 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4">
1319 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-gma-encapsulation-methods" class="xref">GMA Encapsulation Methods</a></p>
1320 <ul class="compact toc ulBare ulEmpty">
1321 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.1">
1322 <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-trailer-based-ip-encapsulat" class="xref">Trailer-Based IP Encapsulation</a></p>
1323 </li>
1324 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2">
1325 <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-header-based-ip-encapsulati" class="xref">Header-Based IP Encapsulation</a></p>
1326 </li>
1327 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3">
1328 <p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>.  <a href="#name-header-based-non-ip-encapsu" class="xref">Header-Based Non-IP Encapsulation</a></p>
1329 </li>
1330 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.4">
1331 <p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>.  <a href="#name-ip-protocol-identifier" class="xref">IP Protocol Identifier</a></p>
1332 </li>
1333 </ul>
1334 </li>
1335 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
1336 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-fragmentation" class="xref">Fragmentation</a></p>
1337 </li>
1338 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
1339 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-concatenation" class="xref">Concatenation</a></p>
1340 </li>
1341 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
1342 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
1343 </li>
1344 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
1345 <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
1346 </li>
1347 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
1348 <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-references" class="xref">References</a></p>
1349 <ul class="compact toc ulBare ulEmpty">
1350 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.1">
1351 <p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
1352 </li>
1353 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.2">
1354 <p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
1355 </li>
1356 </ul>
1357 </li>
1358 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10">
1359 <p id="section-toc.1-1.10.1"><a href="#appendix-A" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
1360 </li>
1361 </ul>
1362 </nav>
1363 </section>
1364 </div>
1365 <div id="sect-1">
1366 <section id="section-1">
1367 <h2 id="name-introduction">
1368 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1369 </h2>
1370 <p id="section-1-1">
1371 A device can be simultaneously connected to multiple networks,
1372 e.g., Wi-Fi, LTE, 5G, and DSL. It is desirable to seamlessly
1373 combine the connectivity over these networks below the transport
1374 layer (L4) to improve the quality of experience for applications that
1375 do not have built-in multi-path capabilities.<a href="#section-1-1" class="pilcrow">¶</a></p>
1376 <p id="section-1-2">
1377 <a href="#Fig1" class="xref">Figure 1</a> shows the Multi-Access Management Service (MAMS) user-plane
1378 protocol stack <span>[<a href="#RFC8743" class="xref">MAMS</a>]</span>, which has been used in today's
1379 multi-access solutions <span>[<a href="#ATSSS" class="xref">ATSSS</a>]</span> <span>[<a href="#LWIPEP" class="xref">LWIPEP</a>]</span> <span>[<a href="#RFC2890" class="xref">GRE1</a>]</span> <span>[<a href="#RFC8157" class="xref">GRE2</a>]</span>. It
1380 consists of two layers: convergence and adaptation.<a href="#section-1-2" class="pilcrow">¶</a></p>
1381 <p id="section-1-3">
1382 The convergence layer is responsible for multi-access operations, including
1383 multi-link (path) aggregation, splitting/reordering, lossless
1384 switching/retransmission, fragmentation, concatenation, etc. It operates on
1385 top of the adaptation layer in the protocol stack. From the perspective of
1386 a transmitter, a User Payload (e.g., IP packet) is processed by the
1387 convergence layer first and then by the adaptation layer before being
1388 transported over a delivery connection; from the receiver's perspective, an
1389 IP packet received over a delivery connection is processed by the
1390 adaptation layer first and then by the convergence layer.<a href="#section-1-3" class="pilcrow">¶</a></p>
1391 <span id="name-mams-user-plane-protocol-st"></span><div id="Fig1">
1392 <figure id="figure-1">
1393 <div class="alignLeft art-text artwork" id="section-1-4.1">
1394 <pre>
1395 +-----------------------------------------------------+
1396 | User Payload, e.g., IP Protocol Data Unit (PDU) |
1397 +-----------------------------------------------------+
1398 +-----------------------------------------------------------+
1399 | +-----------------------------------------------------+ |
1400 | | Multi-Access (MX) Convergence Layer | |
1401 | +-----------------------------------------------------+ |
1402 | +-----------------------------------------------------+ |
1403 | | MX Adaptation | MX Adaptation | MX Adaptation | |
1404 | | Layer | Layer | Layer | |
1405 | +-----------------+-----------------+-----------------+ |
1406 | | Access #1 IP | Access #2 IP | Access #3 IP | |
1407 | +-----------------------------------------------------+ |
1408 | MAMS User-Plane Protocol Stack |
1409 +-----------------------------------------------------------+
1410 </pre>
1411 </div>
1412 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
1413 <a href="#name-mams-user-plane-protocol-st" class="selfRef">MAMS User-Plane Protocol Stack</a>
1414 </figcaption></figure>
1415 </div>
1416 <p id="section-1-5">
1417 GRE (Generic Routing Encapsulation) <span>[<a href="#LWIPEP" class="xref">LWIPEP</a>]</span> <span>[<a href="#RFC2890" class="xref">GRE1</a>]</span> <span>[<a href="#RFC8157" class="xref">GRE2</a>]</span> can be used as
1418 the encapsulation protocol at the convergence layer to encode additional
1419 control information, e.g., key and sequence number. However, there are two
1420 main drawbacks with this approach:<a href="#section-1-5" class="pilcrow">¶</a></p>
1421 <ul class="normal">
1422 <li class="normal" id="section-1-6.1">It is difficult to introduce new control fields because the
1423 GRE header formats are already defined, and<a href="#section-1-6.1" class="pilcrow">¶</a>
1424 </li>
1425 <li class="normal" id="section-1-6.2">IP-over-IP tunneling (required for GRE) leads to higher
1426 overhead especially for small packets.<a href="#section-1-6.2" class="pilcrow">¶</a>
1427 </li>
1428 </ul>
1429 <p id="section-1-7">
1430 For example, the overhead of IP-over-IP/GRE tunneling with both
1431 key and sequence Number is 32 bytes (20-byte IP header + 12-byte
1432 GRE header), which is 80% of a 40-byte TCP ACK packet.<a href="#section-1-7" class="pilcrow">¶</a></p>
1433 <p id="section-1-8">
1434 This document presents a lightweight Generic Multi-Access (GMA)
1435 encapsulation protocol for the convergence layer. It supports three
1436 encapsulation methods: trailer-based IP encapsulation, header-based IP
1437 encapsulation, and non-IP encapsulation. Particularly, the IP
1438 encapsulation methods avoid IP-over-IP tunneling overhead (20 bytes), which
1439 is 50% of a 40-byte TCP ACK packet. Moreover, it introduces new control
1440 fields to support fragmentation and concatenation, which are not available
1441 in GRE-based solutions <span>[<a href="#LWIPEP" class="xref">LWIPEP</a>]</span> <span>[<a href="#RFC2890" class="xref">GRE1</a>]</span> <span>[<a href="#RFC8157" class="xref">GRE2</a>]</span>.<a href="#section-1-8" class="pilcrow">¶</a></p>
1442 <p id="section-1-9">
1443 The GMA protocol only operates between endpoints that have been configured
1444 to use GMA. This configuration can be through any control messages and
1445 procedures, including, for example, Multi-Access Management Services <span>[<a href="#RFC8743" class="xref">MAMS</a>]</span>. Moreover, UDP or IPsec tunneling can
1446 be used at the adaptation sublayer to protect GMA operation from
1447 intermediate nodes.<a href="#section-1-9" class="pilcrow">¶</a></p>
1448 <p id="section-1-10">
1449 The solution described in this document was developed by the authors based
1450 on their experiences in multiple standards bodies including the IETF and
1451 3GPP. However, this document is not an Internet Standard and does not
1452 represent the consensus opinion of the IETF. This document presents the
1453 protocol specification to enable experimentation as described in <a href="#sect-1.1" class="xref">Section 1.1</a> and to facilitate other interoperable
1454 implementations.<a href="#section-1-10" class="pilcrow">¶</a></p>
1455 <div id="sect-1.1">
1456 <section id="section-1.1">
1457 <h3 id="name-scope-of-experiment">
1458 <a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-scope-of-experiment" class="section-name selfRef">Scope of Experiment</a>
1459 </h3>
1460 <p id="section-1.1-1">
1461 The protocol described in this document is an experiment. The
1462 objective of the experiment is to determine whether the protocol
1463 meets the requirements, can be safely used, and has support for
1464 deployment.<a href="#section-1.1-1" class="pilcrow">¶</a></p>
1465 <p id="section-1.1-2">
1466 <a href="#sect-4" class="xref">Section 4</a> describes three possible encapsulation methods that are
1467 enabled by this protocol. Part of this experiment is to assess
1468 whether all three mechanisms are necessary or whether, for
1469 example, all implementations are able to support the main
1470 "trailer-based" IP encapsulation method. Similarly, the experiment
1471 will investigate the relative merits of the IP and non-IP
1472 encapsulation methods.<a href="#section-1.1-2" class="pilcrow">¶</a></p>
1473 <p id="section-1.1-3">
1474 It is expected that this protocol experiment can be conducted on the
1475 Internet since the GMA packets are identified by an IP protocol number and
1476 the protocol is intended for single-hop propagation; devices should not be
1477 forwarding packets, and if they do, they will not need to examine the payload,
1478 while destination systems that do not support this protocol should not
1479 receive such packets and will handle them as unknown payloads according to
1480 normal IP processing. Thus, experimentation is conducted between consenting
1481 end systems that have been mutually configured to participate in the
1482 experiment as described in <a href="#sect-7" class="xref">Section 7</a>.<a href="#section-1.1-3" class="pilcrow">¶</a></p>
1483 <p id="section-1.1-4">
1484 Note that this experiment "reuses" the IP protocol identifier 114
1485 as described in <a href="#sect-4.4" class="xref">Section 4.4</a>. Part of this experiment is to assess
1486 the safety of doing this. The experiment should consider the
1487 following safety mechanisms:<a href="#section-1.1-4" class="pilcrow">¶</a></p>
1488 <ul class="normal">
1489 <li class="normal" id="section-1.1-5.1">GMA endpoints <span class="bcp14">SHOULD</span> detect non-GMA IP packets that also use
1490 114 and log an error to report the situation (although such
1491 error logging <span class="bcp14">MUST</span> be subject to rate limits).<a href="#section-1.1-5.1" class="pilcrow">¶</a>
1492 </li>
1493 <li class="normal" id="section-1.1-5.2">GMA endpoints <span class="bcp14">SHOULD</span> stop using 114 and switch to non-IP encapsulation,
1494 i.e., UDP encapsulation (<a href="#Fig7" class="xref">Figure 7</a>), after detecting any non-GMA usage of 114.<a href="#section-1.1-5.2" class="pilcrow">¶</a>
1495 </li>
1496 </ul>
1497 <p id="section-1.1-6">
1498 The experiment <span class="bcp14">SHOULD</span> use a packet tracing tool, e.g.,
1499 WireShark or TCPDUMP, to monitor both ingress and egress traffic at GMA
1500 endpoints and ensure the above safety mechanisms are implemented.<a href="#section-1.1-6" class="pilcrow">¶</a></p>
1501 <p id="section-1.1-7">
1502 Path quality measurements (one-way delay, loss, etc.) and congestion
1503 detection are performed by the receiver based on the GMA control fields,
1504 e.g., Sequence Number, Timestamp, etc. The receiver will then dynamically
1505 control how to split or steer traffic over multiple delivery connections
1506 accordingly. The GMA control protocol <span>[<a href="#I-D.zhu-intarea-gma-control" class="xref">GMAC</a>]</span> <span class="bcp14">MAY</span>
1507 be used for signaling between GMA endpoints. Another objective of the
1508 experiment is to evaluate the usage of various receiver-based algorithms
1509 <span>[<a href="#GCC" class="xref">GCC</a>]</span> <span>[<a href="#MPIP" class="xref">MPIP</a>]</span>
1510 in multi-path traffic management and the impact on the End-to-End (E2E)
1511 performance (throughput, delay, etc.) of higher-layer (transport)
1512 protocols, e.g., TCP, QUIC, WebRTC, etc.<a href="#section-1.1-7" class="pilcrow">¶</a></p>
1513 <p id="section-1.1-8">
1514 The authors will continually assess the progress of this
1515 experiment and encourage other implementers to contact them to
1516 report the status of their implementations and their experiences
1517 with the protocol.<a href="#section-1.1-8" class="pilcrow">¶</a></p>
1518 </section>
1519 </div>
1520 </section>
1521 </div>
1522 <div id="sect-2">
1523 <section id="section-2">
1524 <h2 id="name-conventions-used-in-this-do">
1525 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-conventions-used-in-this-do" class="section-name selfRef">Conventions Used in This Document</a>
1526 </h2>
1527 <p id="section-2-1">
1528 The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>",
1529 "<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>",
1530 "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
1531 "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are
1532 to be interpreted as described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span>
1533 <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when, they appear in all capitals,
1534 as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p>
1535 </section>
1536 </div>
1537 <div id="sect-3">
1538 <section id="section-3">
1539 <h2 id="name-use-case">
1540 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-use-case" class="section-name selfRef">Use Case</a>
1541 </h2>
1542 <p id="section-3-1">
1543 As shown in <a href="#Fig2" class="xref">Figure 2</a>, a client device (e.g., smartphone,
1544 laptop, etc.) may connect to the Internet via both Wi-Fi and LTE
1545 connections, one of which (e.g., LTE) may operate as the anchor connection,
1546 and the other (e.g., Wi-Fi) may operate as the delivery connection. The
1547 anchor connection provides the IP address and connectivity for end-to-end
1548 Internet access, and the delivery connection provides an additional path
1549 between the client and Multi-Access Gateway for multi-access optimizations.<a href="#section-3-1" class="pilcrow">¶</a></p>
1550 <span id="name-gma-based-multi-access-aggr"></span><div id="Fig2">
1551 <figure id="figure-2">
1552 <div class="alignLeft art-text artwork" id="section-3-2.1">
1553 <pre>
1554 Multi-Access Aggregation
1555
1556 +---+ +---+
1557 | |A|--- LTE Connection -----|C| |
1558 |U|-| |-|S| Internet
1559 | |B|--- Wi-Fi Connection ---|D| |
1560 +---+ +---+
1561 client Multi-Access Gateway
1562 </pre>
1563 </div>
1564 <figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
1565 <a href="#name-gma-based-multi-access-aggr" class="selfRef">GMA-Based Multi-Access Aggregation</a>
1566 </figcaption></figure>
1567 </div>
1568 <span class="break"></span><dl class="dlParallel" id="section-3-3">
1569 <dt id="section-3-3.1">A:</dt>
1570 <dd style="margin-left: 2.0em" id="section-3-3.2"> The adaptation-layer endpoint of the LTE connection
1571 resides in the client.<a href="#section-3-3.2" class="pilcrow">¶</a>
1572 </dd>
1573 <dd class="break"></dd>
1574 <dt id="section-3-3.3">B:</dt>
1575 <dd style="margin-left: 2.0em" id="section-3-3.4"> The adaptation-layer endpoint of the Wi-Fi connection
1576 resides in the client.<a href="#section-3-3.4" class="pilcrow">¶</a>
1577 </dd>
1578 <dd class="break"></dd>
1579 <dt id="section-3-3.5">C:</dt>
1580 <dd style="margin-left: 2.0em" id="section-3-3.6"> The adaptation-layer endpoint of the LTE connection
1581 resides in the Multi-Access Gateway, aka N-MADP (Network
1582 Multi-Access Data Proxy) in <span>[<a href="#RFC8743" class="xref">MAMS</a>]</span>.<a href="#section-3-3.6" class="pilcrow">¶</a>
1583 </dd>
1584 <dd class="break"></dd>
1585 <dt id="section-3-3.7">D:</dt>
1586 <dd style="margin-left: 2.0em" id="section-3-3.8"> The adaptation-layer endpoint of the Wi-Fi connection
1587 resides in the Multi-Access Gateway.<a href="#section-3-3.8" class="pilcrow">¶</a>
1588 </dd>
1589 <dd class="break"></dd>
1590 <dt id="section-3-3.9">U:</dt>
1591 <dd style="margin-left: 2.0em" id="section-3-3.10"> The convergence-layer endpoint resides in the client.<a href="#section-3-3.10" class="pilcrow">¶</a>
1592 </dd>
1593 <dd class="break"></dd>
1594 <dt id="section-3-3.11">S:</dt>
1595 <dd style="margin-left: 2.0em" id="section-3-3.12"> The convergence-layer endpoint resides in the Multi-Access
1596 Gateway.<a href="#section-3-3.12" class="pilcrow">¶</a>
1597 </dd>
1598 <dd class="break"></dd>
1599 </dl>
1600 <p id="section-3-4">
1601 For example, per-packet aggregation allows a single IP flow to use the
1602 combined bandwidth of the two connections. In another example, packets lost
1603 due to a temporary link outage may be retransmitted. Moreover, packets may
1604 be duplicated over multiple connections to achieve high reliability and low
1605 latency, where duplicated packets are eliminated by the receiving
1606 side. Such multi-access optimization requires additional control
1607 information, e.g., a sequence number, in each packet, which can be
1608 supported by the GMA encapsulation protocol described in this document.<a href="#section-3-4" class="pilcrow">¶</a></p>
1609 <p id="section-3-5">
1610 The GMA protocol described in this document is designed for multiple
1611 connections, but it may also be used when there is only one connection
1612 between two endpoints. For example, it may be used for loss detection and
1613 recovery. In another example, it may be used to concatenate multiple small
1614 packets and reduce per-packet overhead.<a href="#section-3-5" class="pilcrow">¶</a></p>
1615 </section>
1616 </div>
1617 <div id="sect-4">
1618 <section id="section-4">
1619 <h2 id="name-gma-encapsulation-methods">
1620 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-gma-encapsulation-methods" class="section-name selfRef">GMA Encapsulation Methods</a>
1621 </h2>
1622 <p id="section-4-1">
1623 The GMA encapsulation protocol supports the following three
1624 methods:<a href="#section-4-1" class="pilcrow">¶</a></p>
1625 <ul class="normal">
1626 <li class="normal" id="section-4-2.1">Trailer-based IP Encapsulation (<a href="#sect-4.1" class="xref">Section 4.1</a>)<a href="#section-4-2.1" class="pilcrow">¶</a>
1627 </li>
1628 <li class="normal" id="section-4-2.2">Header-based IP Encapsulation (<a href="#sect-4.2" class="xref">Section 4.2</a>)<a href="#section-4-2.2" class="pilcrow">¶</a>
1629 </li>
1630 <li class="normal" id="section-4-2.3">Header-based non-IP Encapsulation (<a href="#sect-4.3" class="xref">Section 4.3</a>)<a href="#section-4-2.3" class="pilcrow">¶</a>
1631 </li>
1632 </ul>
1633 <p id="section-4-3">
1634 Non-IP encapsulation <span class="bcp14">MUST</span> be used if the original IP packet is
1635 IPv6.<a href="#section-4-3" class="pilcrow">¶</a></p>
1636 <p id="section-4-4">
1637 Trailer-based IP encapsulation <span class="bcp14">MUST</span> be used if it is supported by
1638 GMA endpoints and the original IP packet is IPv4.<a href="#section-4-4" class="pilcrow">¶</a></p>
1639 <p id="section-4-5">
1640 Header-based encapsulation <span class="bcp14">MUST</span> be used if the trailer-based
1641 method is not supported by either the client or Multi-Access Gateway.
1642 In this case, if the adaptation layer, e.g., UDP tunneling,
1643 supports non-IP packet format, non-IP encapsulation <span class="bcp14">MUST</span> be used;
1644 otherwise, header-based IP encapsulation <span class="bcp14">MUST</span> be used.<a href="#section-4-5" class="pilcrow">¶</a></p>
1645 <p id="section-4-6">
1646 If non-IP encapsulation is configured, a GMA header <span class="bcp14">MUST</span> be
1647 present in every packet. In comparison, if IP encapsulation is configured,
1648 a GMA header or trailer may be added dynamically on a per-packet basis, and
1649 it indicates the presence of a GMA header (or trailer) to set the protocol
1650 type of the GMA PDU to "114" (see <a href="#sect-4.4" class="xref">Section 4.4</a>).<a href="#section-4-6" class="pilcrow">¶</a></p>
1651 <p id="section-4-7">
1652 The GMA endpoints <span class="bcp14">MAY</span> configure the GMA encapsulation method through
1653 control signaling or pre-configuration. For example, the "MX UP Setup
1654 Configuration Request" message as specified in Multi-Access Management
1655 Service <span>[<a href="#RFC8743" class="xref">MAMS</a>]</span> includes "MX Convergence Method Parameters",
1656 which provides the list of parameters to configure the convergence layer,
1657 and can be extended to indicate the GMA encapsulation method.<a href="#section-4-7" class="pilcrow">¶</a></p>
1658 <p id="section-4-8">
1659 GMA endpoint <span class="bcp14">MUST</span> discard a received packet and <span class="bcp14">MAY</span> log an error
1660 to report the situation (although such error logging <span class="bcp14">MUST</span> be
1661 subject to rate limits) under any of the following conditions:<a href="#section-4-8" class="pilcrow">¶</a></p>
1662 <ul class="normal">
1663 <li class="normal" id="section-4-9.1">The GMA version number in the GMA header (or trailer) is not
1664 understood or supported by the GMA endpoint.<a href="#section-4-9.1" class="pilcrow">¶</a>
1665 </li>
1666 <li class="normal" id="section-4-9.2">A flag bit in the GMA header (or trailer) not understood or
1667 supported by the GMA endpoint is set to "1".<a href="#section-4-9.2" class="pilcrow">¶</a>
1668 </li>
1669 </ul>
1670 <div id="sect-4.1">
1671 <section id="section-4.1">
1672 <h3 id="name-trailer-based-ip-encapsulat">
1673 <a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-trailer-based-ip-encapsulat" class="section-name selfRef">Trailer-Based IP Encapsulation</a>
1674 </h3>
1675 <span id="name-gma-pdu-format-with-trailer"></span><div id="Fig3">
1676 <figure id="figure-3">
1677 <div class="alignLeft art-text artwork" id="section-4.1-1.1">
1678 <pre>
1679 |&lt;---------------------GMA PDU -----------------------&gt;|
1680 +------------------------------------------------------+
1681 | IP hdr | IP payload | GMA Trailer |
1682 +------------------------------------------------------+
1683 |&lt;------- GMA SDU (user payload)--------&gt;|
1684 </pre>
1685 </div>
1686 <figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
1687 <a href="#name-gma-pdu-format-with-trailer" class="selfRef">GMA PDU Format with Trailer-based IP Encapsulation</a>
1688 </figcaption></figure>
1689 </div>
1690 <p id="section-4.1-2">
1691 This method <span class="bcp14">SHALL NOT</span> be used if the original IP packet (GMA
1692 service data unit (GMA SDU)) is IPv6.<a href="#section-4.1-2" class="pilcrow">¶</a></p>
1693 <p id="section-4.1-3">
1694 <a href="#Fig3" class="xref">Figure 3</a> shows the trailer-based IP encapsulation GMA protocol
1695 data unit (GMA PDU) format. A (GMA) PDU may carry one or multiple IP
1696 packets, aka (GMA) SDUs, in the payload, or a fragment of the SDU.<a href="#section-4.1-3" class="pilcrow">¶</a></p>
1697 <p id="section-4.1-4">
1698 The protocol type field in the IP header of the GMA PDU <span class="bcp14">MUST</span> be
1699 changed to 114 (Any 0-Hop Protocol) (see <a href="#sect-4.4" class="xref">Section 4.4</a>) to indicate
1700 the presence of the GMA trailer.<a href="#section-4.1-4" class="pilcrow">¶</a></p>
1701 <p id="section-4.1-5">
1702 The following three IP header fields <span class="bcp14">MUST</span> be changed:<a href="#section-4.1-5" class="pilcrow">¶</a></p>
1703 <span class="break"></span><dl class="dlParallel" id="section-4.1-6">
1704 <dt id="section-4.1-6.1">IP Length:</dt>
1705 <dd style="margin-left: 1.5em" id="section-4.1-6.2"> Add the length of "GMA Trailer" to the length of the
1706 original IP packet.<a href="#section-4.1-6.2" class="pilcrow">¶</a>
1707 </dd>
1708 <dd class="break"></dd>
1709 <dt id="section-4.1-6.3">Time To Live (TTL):</dt>
1710 <dd style="margin-left: 1.5em" id="section-4.1-6.4"> Set to "1".<a href="#section-4.1-6.4" class="pilcrow">¶</a>
1711 </dd>
1712 <dd class="break"></dd>
1713 <dt id="section-4.1-6.5">IP checksum:</dt>
1714 <dd style="margin-left: 1.5em" id="section-4.1-6.6"> Recalculate after changing "protocol
1715 type", "TTL", and "IP Length".<a href="#section-4.1-6.6" class="pilcrow">¶</a>
1716 </dd>
1717 <dd class="break"></dd>
1718 </dl>
1719 <p id="section-4.1-7">
1720 The GMA (Generic Multi-Access) trailer <span class="bcp14">MUST</span> consist of two
1721 mandatory fields (the last 3 bytes): Next Header and Flags.<a href="#section-4.1-7" class="pilcrow">¶</a></p>
1722 <p id="section-4.1-8">
1723 This is defined as follows:<a href="#section-4.1-8" class="pilcrow">¶</a></p>
1724 <span class="break"></span><dl class="dlParallel" id="section-4.1-9">
1725 <dt id="section-4.1-9.1">Next Header (1 byte):</dt>
1726 <dd style="margin-left: 1.5em" id="section-4.1-9.2"> This is the IP protocol type of the (first) SDU
1727 in a PDU; it stores the value before it was overwritten to
1728 114.<a href="#section-4.1-9.2" class="pilcrow">¶</a>
1729 </dd>
1730 <dd class="break"></dd>
1731 <dt id="section-4.1-9.3">Flags (2 bytes):</dt>
1732 <dd style="margin-left: 1.5em" id="section-4.1-9.4">
1733 <p id="section-4.1-9.4.1"> Bit 0 is the most significant bit (MSB), and
1734 bit 15 is the least significant bit (LSB).<a href="#section-4.1-9.4.1" class="pilcrow">¶</a></p>
1735 <span class="break"></span><dl class="dlParallel" id="section-4.1-9.4.2">
1736 <dt id="section-4.1-9.4.2.1">Checksum Present (bit 0):</dt>
1737 <dd style="margin-left: 1.5em" id="section-4.1-9.4.2.2"> If the Checksum Present
1738 bit is set to 1, then the Checksum field is present.<a href="#section-4.1-9.4.2.2" class="pilcrow">¶</a>
1739 </dd>
1740 <dd class="break"></dd>
1741 <dt id="section-4.1-9.4.2.3">Concatenation Present (bit 1):</dt>
1742 <dd style="margin-left: 1.5em" id="section-4.1-9.4.2.4"> If the Concatenation
1743 Present bit is set to 1, then the PDU carries multiple SDUs, and
1744 the First SDU Length field is present.<a href="#section-4.1-9.4.2.4" class="pilcrow">¶</a>
1745 </dd>
1746 <dd class="break"></dd>
1747 <dt id="section-4.1-9.4.2.5">Connection ID Present (bit 2):</dt>
1748 <dd style="margin-left: 1.5em" id="section-4.1-9.4.2.6"> If the Connection ID
1749 Present bit is set to 1, then the Connection ID field is
1750 present.<a href="#section-4.1-9.4.2.6" class="pilcrow">¶</a>
1751 </dd>
1752 <dd class="break"></dd>
1753 <dt id="section-4.1-9.4.2.7">Flow ID Present (bit 3):</dt>
1754 <dd style="margin-left: 1.5em" id="section-4.1-9.4.2.8"> If the Flow ID Present bit
1755 is set to 1, then the Flow ID field is present.<a href="#section-4.1-9.4.2.8" class="pilcrow">¶</a>
1756 </dd>
1757 <dd class="break"></dd>
1758 <dt id="section-4.1-9.4.2.9">Fragmentation Present (bit 4):</dt>
1759 <dd style="margin-left: 1.5em" id="section-4.1-9.4.2.10">If the Fragmentation
1760 Present bit is set to 1, then the PDU carry a fragment of the
1761 SDU and the Fragmentation Control field is present.<a href="#section-4.1-9.4.2.10" class="pilcrow">¶</a>
1762 </dd>
1763 <dd class="break"></dd>
1764 <dt id="section-4.1-9.4.2.11">Delivery SN Present (bit 5):</dt>
1765 <dd style="margin-left: 1.5em" id="section-4.1-9.4.2.12"> If the Delivery SN
1766 (Sequence Number) Present bit is set to 1, then the Delivery SN
1767 field is present and contains the valid information.<a href="#section-4.1-9.4.2.12" class="pilcrow">¶</a>
1768 </dd>
1769 <dd class="break"></dd>
1770 <dt id="section-4.1-9.4.2.13">Flow SN Present (bit 6):</dt>
1771 <dd style="margin-left: 1.5em" id="section-4.1-9.4.2.14"> If the Flow SN Present bit
1772 is set to 1, then the Sequence Number field is present.<a href="#section-4.1-9.4.2.14" class="pilcrow">¶</a>
1773 </dd>
1774 <dd class="break"></dd>
1775 <dt id="section-4.1-9.4.2.15">Timestamp Present (bit 7):</dt>
1776 <dd style="margin-left: 1.5em" id="section-4.1-9.4.2.16"> If the Timestamp Present
1777 bit is set to 1, then the Timestamp field is present.<a href="#section-4.1-9.4.2.16" class="pilcrow">¶</a>
1778 </dd>
1779 <dd class="break"></dd>
1780 <dt id="section-4.1-9.4.2.17">TTL Present (bit 8):</dt>
1781 <dd style="margin-left: 1.5em" id="section-4.1-9.4.2.18"> If the TTL Present bit is set
1782 to 1, then the TTL field is present.<a href="#section-4.1-9.4.2.18" class="pilcrow">¶</a>
1783 </dd>
1784 <dd class="break"></dd>
1785 <dt id="section-4.1-9.4.2.19">Reserved (bit 9-12):</dt>
1786 <dd style="margin-left: 1.5em" id="section-4.1-9.4.2.20"> This is set to "0" and ignored
1787 on receipt.<a href="#section-4.1-9.4.2.20" class="pilcrow">¶</a>
1788 </dd>
1789 <dd class="break"></dd>
1790 <dt id="section-4.1-9.4.2.21">Version (bit 13~15):</dt>
1791 <dd style="margin-left: 1.5em" id="section-4.1-9.4.2.22"> This is the GMA version
1792 number; it is set to 0 for the GMA encapsulation protocol specified in
1793 this document.<a href="#section-4.1-9.4.2.22" class="pilcrow">¶</a>
1794 </dd>
1795 <dd class="break"></dd>
1796 </dl>
1797 </dd>
1798 <dd class="break"></dd>
1799 </dl>
1800 <p id="section-4.1-10">
1801 The Flags field is at the end of the PDU, and the Next Header field is the
1802 second last. The receiver <span class="bcp14">SHOULD</span> first decode the Flags
1803 field to determine the length of the GMA trailer and then decode each
1804 optional field accordingly. The Generic Multi-Access (GMA) trailer
1805 <span class="bcp14">MAY</span> consist of the following optional fields:<a href="#section-4.1-10" class="pilcrow">¶</a></p>
1806 <span class="break"></span><dl class="dlParallel" id="section-4.1-11">
1807 <dt id="section-4.1-11.1">Checksum (1 byte):</dt>
1808 <dd style="margin-left: 1.5em" id="section-4.1-11.2"> This contains the (one's
1809 complement) checksum sum of all 8 bits in the trailer. For purposes
1810 of computing the checksum, the value of the Checksum field is
1811 zero. This field is present only if the Checksum Present bit is set
1812 to 1.<a href="#section-4.1-11.2" class="pilcrow">¶</a>
1813 </dd>
1814 <dd class="break"></dd>
1815 <dt id="section-4.1-11.3">First SDU Length (2 bytes):</dt>
1816 <dd style="margin-left: 1.5em" id="section-4.1-11.4"> This is the length of the
1817 first IP packet in the PDU, only included if a PDU contains multiple
1818 IP packets. This field is present only if the Concatenation Present
1819 bit is set to 1.<a href="#section-4.1-11.4" class="pilcrow">¶</a>
1820 </dd>
1821 <dd class="break"></dd>
1822 <dt id="section-4.1-11.5">Connection ID (1 byte):</dt>
1823 <dd style="margin-left: 1.5em" id="section-4.1-11.6">
1824 <p id="section-4.1-11.6.1"> This contains an unsigned integer to identify the
1825 anchor and delivery connection of the GMA PDU. This field is
1826 present only if the Connection ID Present bit is set to 1.<a href="#section-4.1-11.6.1" class="pilcrow">¶</a></p>
1827 <span class="break"></span><dl class="dlParallel" id="section-4.1-11.6.2">
1828 <dt id="section-4.1-11.6.2.1">Anchor Connection ID (MSB 4 bits):</dt>
1829 <dd style="margin-left: 1.5em" id="section-4.1-11.6.2.2"> This contains an
1830 unsigned integer to identify the anchor connection.<a href="#section-4.1-11.6.2.2" class="pilcrow">¶</a>
1831 </dd>
1832 <dd class="break"></dd>
1833 <dt id="section-4.1-11.6.2.3">Delivery Connection ID (LSB 4 bits):</dt>
1834 <dd style="margin-left: 1.5em" id="section-4.1-11.6.2.4"> This contains
1835 an unsigned integer to identify the delivery connection.<a href="#section-4.1-11.6.2.4" class="pilcrow">¶</a>
1836 </dd>
1837 <dd class="break"></dd>
1838 </dl>
1839 </dd>
1840 <dd class="break"></dd>
1841 <dt id="section-4.1-11.7">Flow ID (1 byte):</dt>
1842 <dd style="margin-left: 1.5em" id="section-4.1-11.8"> This contains an unsigned integer to identify the
1843 IP flow that a PDU belongs to, for example Data Radio Bearer (DRB)
1844 ID <span>[<a href="#LWIPEP" class="xref">LWIPEP</a>]</span> for a cellular (e.g., LTE)
1845 connection. This field is present only if the Flow ID Present bit is
1846 set to 1.<a href="#section-4.1-11.8" class="pilcrow">¶</a>
1847 </dd>
1848 <dd class="break"></dd>
1849 <dt id="section-4.1-11.9">Fragmentation Control (FC) (1 byte):</dt>
1850 <dd style="margin-left: 1.5em" id="section-4.1-11.10"> This provides
1851 necessary information for reassembly, only needed if a PDU carries
1852 fragments. This field is present only if the Fragmentation Present
1853 bit is set to 1. Please refer to <a href="#sect-5" class="xref">Section 5</a> for its
1854 detailed format and usage.<a href="#section-4.1-11.10" class="pilcrow">¶</a>
1855 </dd>
1856 <dd class="break"></dd>
1857 <dt id="section-4.1-11.11">Delivery SN (1 byte):</dt>
1858 <dd style="margin-left: 1.5em" id="section-4.1-11.12"> This contains an auto-incremented integer to
1859 indicate the GMA PDU transmission order on a delivery connection.
1860 Delivery SN is needed to measure packet loss of each delivery
1861 connection and therefore generated per delivery connection per
1862 flow. This field is present only if the Delivery SN Present bit is
1863 set to 1.<a href="#section-4.1-11.12" class="pilcrow">¶</a>
1864 </dd>
1865 <dd class="break"></dd>
1866 <dt id="section-4.1-11.13">Flow SN (3 bytes):</dt>
1867 <dd style="margin-left: 1.5em" id="section-4.1-11.14"> This contains an auto-incremented
1868 integer to indicate the GMA SDU (IP packet) order of a flow. Flow SN
1869 is needed for retransmission, reordering, and fragmentation. It
1870 <span class="bcp14">SHALL</span> be generated per flow. This field is present
1871 only if the Flow SN Present bit is set to 1.<a href="#section-4.1-11.14" class="pilcrow">¶</a>
1872 </dd>
1873 <dd class="break"></dd>
1874 <dt id="section-4.1-11.15">Timestamp (4 bytes):</dt>
1875 <dd style="margin-left: 1.5em" id="section-4.1-11.16"> This contains the
1876 current value of the timestamp clock of the transmitter in the unit
1877 of 1 millisecond. This field is present only if the Timestamp
1878 Present bit is set to 1.<a href="#section-4.1-11.16" class="pilcrow">¶</a>
1879 </dd>
1880 <dd class="break"></dd>
1881 <dt id="section-4.1-11.17">TTL (1 byte):</dt>
1882 <dd style="margin-left: 1.5em" id="section-4.1-11.18"> This contains the TTL value of
1883 the original IP header if the GMA SDU is IPv4, or the Hop-Limit
1884 value of the IP header if the GMA SDU is IPv6. This field is present
1885 only if the TTL Present bit is set to 1.<a href="#section-4.1-11.18" class="pilcrow">¶</a>
1886 </dd>
1887 <dd class="break"></dd>
1888 </dl>
1889 <p id="section-4.1-12">
1890 <a href="#Fig4" class="xref">Figure 4</a> shows the GMA trailer format with all the fields present,
1891 and the order of the GMA control fields <span class="bcp14">SHALL</span> follow the bit order
1892 in the Flags field. Note that the bits in the Flags field are
1893 ordered with the first bit transmitted being bit 0 (MSB). All
1894 fields are transmitted in regular network byte order and appear in
1895 reverse order to their corresponding flag bits. If a flag bit is
1896 clear, the corresponding optional field is absent.<a href="#section-4.1-12" class="pilcrow">¶</a></p>
1897 <p id="section-4.1-13">
1898 For example, bit 0 (the MSB) of the Flags field is the Checksum Present
1899 bit, and the Checksum field is the last in the trailer with the exception
1900 of the two mandatory fields. Bit 1 is the Concatenation Present bit, and
1901 the FSL field is the second last.<a href="#section-4.1-13" class="pilcrow">¶</a></p>
1902 <span id="name-gma-trailer-format-with-all"></span><div id="Fig4">
1903 <figure id="figure-4">
1904 <div class="alignLeft art-text artwork" id="section-4.1-14.1">
1905 <pre>
1906 0 1 2 3
1907 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1908 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1909 | TTL | Timestamp
1910 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1911 | Flow SN |
1912 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1913 | Delivery SN | FC | Flow ID | Connection ID |
1914 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1915 | First SDU Length (FSL) | Checksum | Next Header |
1916 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1917 | Flags |
1918 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1919 </pre>
1920 </div>
1921 <figcaption><a href="#figure-4" class="selfRef">Figure 4</a>:
1922 <a href="#name-gma-trailer-format-with-all" class="selfRef">GMA Trailer Format with All Optional Fields Present</a>
1923 </figcaption></figure>
1924 </div>
1925 </section>
1926 </div>
1927 <div id="sect-4.2">
1928 <section id="section-4.2">
1929 <h3 id="name-header-based-ip-encapsulati">
1930 <a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-header-based-ip-encapsulati" class="section-name selfRef">Header-Based IP Encapsulation</a>
1931 </h3>
1932 <p id="section-4.2-1">
1933 This method <span class="bcp14">SHALL NOT</span> be used if the original IP packet (GMA SDU)
1934 is IPv6.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
1935 <p id="section-4.2-2">
1936 <a href="#Fig5" class="xref">Figure 5</a> shows the header-based IP encapsulation format. Here, the
1937 GMA header is inserted right after the IP header of the GMA SDU,
1938 and the IP header fields of the GMA PDU <span class="bcp14">MUST</span> be changed the same
1939 way as in trailer-based IP encapsulation.<a href="#section-4.2-2" class="pilcrow">¶</a></p>
1940 <span id="name-gma-pdu-format-with-header-"></span><div id="Fig5">
1941 <figure id="figure-5">
1942 <div class="alignLeft art-text artwork" id="section-4.2-3.1">
1943 <pre>
1944 +-----------------------------------------------+
1945 |IP hdr | GMA Header | IP payload |
1946 +-----------------------------------------------+
1947 </pre>
1948 </div>
1949 <figcaption><a href="#figure-5" class="selfRef">Figure 5</a>:
1950 <a href="#name-gma-pdu-format-with-header-" class="selfRef">GMA PDU Format with Header-Based IP Encapsulation</a>
1951 </figcaption></figure>
1952 </div>
1953 <p id="section-4.2-4">
1954 <a href="#Fig6" class="xref">Figure 6</a> shows the GMA header format. In comparison to the GMA
1955 trailer, the only difference is that the Flags field is now in the front so
1956 that the receiver can first decode the Flags field to determine the GMA
1957 header length.<a href="#section-4.2-4" class="pilcrow">¶</a></p>
1958 <p id="section-4.2-5">
1959 The "TTL" field <span class="bcp14">MUST</span> be included and the "TTL" bit in the
1960 GMA header (or Trailer) <span class="bcp14">MUST</span> be set to 1 if (trailer- or
1961 header-based) IP encapsulation is used.<a href="#section-4.2-5" class="pilcrow">¶</a></p>
1962 <span id="name-gma-header-format"></span><div id="Fig6">
1963 <figure id="figure-6">
1964 <div class="alignLeft art-text artwork" id="section-4.2-6.1">
1965 <pre>
1966 +------------------------------------------------------+
1967 | Flags | other fields (TTL, Timestamp, Flow SN, etc.) |
1968 +------------------------------------------------------+
1969 </pre>
1970 </div>
1971 <figcaption><a href="#figure-6" class="selfRef">Figure 6</a>:
1972 <a href="#name-gma-header-format" class="selfRef">GMA Header Format</a>
1973 </figcaption></figure>
1974 </div>
1975 </section>
1976 </div>
1977 <div id="sect-4.3">
1978 <section id="section-4.3">
1979 <h3 id="name-header-based-non-ip-encapsu">
1980 <a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-header-based-non-ip-encapsu" class="section-name selfRef">Header-Based Non-IP Encapsulation</a>
1981 </h3>
1982 <p id="section-4.3-1">
1983 <a href="#Fig7" class="xref">Figure 7</a> shows the header-based non-IP encapsulation format. Here,
1984 "UDP Tunneling" is configured at the MX adaptation layer. The
1985 ports for "UDP Tunneling" at the client are chosen from the Dynamic
1986 Port range, and the ports for "UDP Tunneling" at the Multi-Access
1987 Gateway are configured and provided to the client through additional
1988 control messages, e.g., <span>[<a href="#RFC8743" class="xref">MAMS</a>]</span>.<a href="#section-4.3-1" class="pilcrow">¶</a></p>
1989 <p id="section-4.3-2">
1990 "TTL", "FSL", and "Next Header" are no longer needed and <span class="bcp14">MUST</span> not
1991 be included. Moreover, the IP header fields of the GMA SDU remain
1992 unchanged.<a href="#section-4.3-2" class="pilcrow">¶</a></p>
1993 <span id="name-gma-pdu-format-with-non-ip-"></span><div id="Fig7">
1994 <figure id="figure-7">
1995 <div class="alignLeft art-text artwork" id="section-4.3-3.1">
1996 <pre>
1997 +-------------------------------------------------------------+
1998 | IP hdr | UDP hdr | GMA Header | IP hdr | IP payload |
1999 +-------------------------------------------------------------+
2000 |&lt;------- GMA SDU------------&gt;|
2001 |&lt;------------------- GMA PDU------------&gt;|
2002 </pre>
2003 </div>
2004 <figcaption><a href="#figure-7" class="selfRef">Figure 7</a>:
2005 <a href="#name-gma-pdu-format-with-non-ip-" class="selfRef">GMA PDU Format with Non-IP Encapsulation</a>
2006 </figcaption></figure>
2007 </div>
2008 </section>
2009 </div>
2010 <div id="sect-4.4">
2011 <section id="section-4.4">
2012 <h3 id="name-ip-protocol-identifier">
2013 <a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-ip-protocol-identifier" class="section-name selfRef">IP Protocol Identifier</a>
2014 </h3>
2015 <p id="section-4.4-1">
2016 As described in <a href="#sect-4.1" class="xref">Section 4.1</a>, IP-encapsulated GMA PDUs are
2017 indicated using the IP protocol type 114. This is designated and
2018 recorded by IANA <span>[<a href="#IANA" class="xref">IANA</a>]</span> to indicate "any 0-Hop Protocol". No
2019 reference is given in the IANA registry for the definition of this
2020 protocol type, and IANA has no record of why the assignment was
2021 made or how it is used, although it was probably assigned before
2022 1999 <span>[<a href="#IANA1999" class="xref">IANA1999</a>]</span>.<a href="#section-4.4-1" class="pilcrow">¶</a></p>
2023 <p id="section-4.4-2">
2024 There is some risk associated with "reusing" protocol type 114
2025 because there may be implementations of other protocols also using
2026 this protocol type. However, because the protocol described in
2027 this document is used only between adjacent devices specifically
2028 configured for this purpose, the use of protocol type 114 should
2029 be safe.<a href="#section-4.4-2" class="pilcrow">¶</a></p>
2030 <p id="section-4.4-3">
2031 As described in <a href="#sect-1.1" class="xref">Section 1.1</a>, one of the purposes of the experiment
2032 described in this document is to verify the safety of using this
2033 protocol type. Deployments should be aware of the risk of a clash
2034 with other uses of this protocol type.<a href="#section-4.4-3" class="pilcrow">¶</a></p>
2035 </section>
2036 </div>
2037 </section>
2038 </div>
2039 <div id="sect-5">
2040 <section id="section-5">
2041 <h2 id="name-fragmentation">
2042 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-fragmentation" class="section-name selfRef">Fragmentation</a>
2043 </h2>
2044 <p id="section-5-1">
2045 If the MTU size of the anchor connection (for GMA SDU) is configured such
2046 that the corresponding GMA PDU length adding the GMA header (or trailer)
2047 and other overhead (UDP tunneling) <span class="bcp14">MAY</span> exceed the MTU of a
2048 delivery connection, GMA endpoints <span class="bcp14">MUST</span> be configured to
2049 support fragmentation through additional control messages <span>[<a href="#RFC8743" class="xref">MAMS</a>]</span>.<a href="#section-5-1" class="pilcrow">¶</a></p>
2050 <p id="section-5-2">
2051 The fragmentation procedure at the convergence sublayer is similar
2052 to IP fragmentation <span>[<a href="#RFC0791" class="xref">RFC0791</a>]</span> in principle, but with the following
2053 two differences for less overhead:<a href="#section-5-2" class="pilcrow">¶</a></p>
2054 <ul class="normal">
2055 <li class="normal" id="section-5-3.1">The fragment offset field is expressed in number of fragments.<a href="#section-5-3.1" class="pilcrow">¶</a>
2056 </li>
2057 <li class="normal" id="section-5-3.2">The maximum number of fragments per SDU is 2<sup>7</sup> (=128).<a href="#section-5-3.2" class="pilcrow">¶</a>
2058 </li>
2059 </ul>
2060 <p id="section-5-4">
2061 The Fragmentation Control (FC) field in the GMA trailer (or
2062 header) contains the following bits:<a href="#section-5-4" class="pilcrow">¶</a></p>
2063 <span class="break"></span><dl class="dlParallel" id="section-5-5">
2064 <dt id="section-5-5.1">Bit 7:</dt>
2065 <dd style="margin-left: 1.5em" id="section-5-5.2"> a More Fragment (MF) flag to indicate if the fragment
2066 is the last one (0) or not (1)<a href="#section-5-5.2" class="pilcrow">¶</a>
2067 </dd>
2068 <dd class="break"></dd>
2069 <dt id="section-5-5.3">Bit 0-6:</dt>
2070 <dd style="margin-left: 1.5em" id="section-5-5.4"> Fragment Offset (in units of fragments) to specify
2071 the offset of a particular fragment relative to the beginning
2072 of the SDU<a href="#section-5-5.4" class="pilcrow">¶</a>
2073 </dd>
2074 <dd class="break"></dd>
2075 </dl>
2076 <p id="section-5-6">
2077 A PDU carries a whole SDU without fragmentation if the FC field is
2078 set to all "0"s or the FC field is not present in the trailer.
2079 Otherwise, the PDU contains a fragment of the SDU.<a href="#section-5-6" class="pilcrow">¶</a></p>
2080 <p id="section-5-7">
2081 The Flow SN field in the trailer is used to distinguish the
2082 fragments of one SDU from those of another. The Fragment Offset
2083 (FO) field tells the receiver the position of a fragment in the
2084 original SDU. The More Fragment (MF) flag indicates the last
2085 fragment.<a href="#section-5-7" class="pilcrow">¶</a></p>
2086 <p id="section-5-8">
2087 To fragment a long SDU, the transmitter creates n PDUs and copies the
2088 content of the IP header fields from the long PDU into the IP header of all
2089 the PDUs. The length field in the IP header of the PDU
2090 <span class="bcp14">SHOULD</span> be changed to the length of the PDU, and the protocol
2091 type <span class="bcp14">SHOULD</span> be changed to 114.<a href="#section-5-8" class="pilcrow">¶</a></p>
2092 <p id="section-5-9">
2093 The data of the long SDU is divided into n portions based on the
2094 MTU size of the delivery connection. The first portion of the data
2095 is placed in the first PDU. The MF flag is set to "1", and the FO
2096 field is set to "0". The i-th portion of the data is placed in the
2097 i-th PDU. The MF flag is set to "0" if it is the last fragment and
2098 set to "1" otherwise. The FO field is set to i-1.<a href="#section-5-9" class="pilcrow">¶</a></p>
2099 <p id="section-5-10">
2100 To assemble the fragments of an SDU, the receiver combines PDUs
2101 that all have the same Flow SN. The combination is done by placing
2102 the data portion of each fragment in the relative order indicated
2103 by the Fragment Offset in that fragment's GMA trailer (or header).
2104 The first fragment will have the Fragment Offset set to "0", and
2105 the last fragment will have the More Fragment flag set to "0".<a href="#section-5-10" class="pilcrow">¶</a></p>
2106 <p id="section-5-11">
2107 GMA fragmentation operates above the IP layer of individual access
2108 connection (Wi-Fi, LTE) and between the two endpoints of convergence
2109 layer. The convergence layer endpoints (client, Multi-access Gateway)
2110 <span class="bcp14">SHOULD</span> obtain the MTU of individual connection through
2111 either manual configuration or implementing Path MTU Discovery (PMTUD) as
2112 suggested in <span>[<a href="#RFC8900" class="xref">RFC8900</a>]</span>.<a href="#section-5-11" class="pilcrow">¶</a></p>
2113 </section>
2114 </div>
2115 <div id="sect-6">
2116 <section id="section-6">
2117 <h2 id="name-concatenation">
2118 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-concatenation" class="section-name selfRef">Concatenation</a>
2119 </h2>
2120 <p id="section-6-1">
2121 The convergence sublayer <span class="bcp14">MAY</span> support concatenation if a delivery
2122 connection has a larger maximum transmission unit (MTU) than the
2123 original IP packet (SDU). Only the SDUs with the same client IP
2124 address and the same Flow ID <span class="bcp14">MAY</span> be concatenated.<a href="#section-6-1" class="pilcrow">¶</a></p>
2125 <p id="section-6-2">
2126 If the (trailer- or header-based) IP encapsulation method is used,
2127 the First SDU Length (FSL) field <span class="bcp14">SHOULD</span> be included in the GMA
2128 trailer (or header) to indicate the length of the first SDU.
2129 Otherwise, the FSL field <span class="bcp14">SHOULD</span> not be included.<a href="#section-6-2" class="pilcrow">¶</a></p>
2130 <span id="name-example-of-gma-pdu-format-w"></span><div id="Fig8">
2131 <figure id="figure-8">
2132 <div class="alignLeft art-text artwork" id="section-6-3.1">
2133 <pre>
2134 +-----------------------------------------------------------+
2135 |IP hdr| IP payload |IP hdr| IP payload | GMA Trailer |
2136 +-----------------------------------------------------------+
2137 </pre>
2138 </div>
2139 <figcaption><a href="#figure-8" class="selfRef">Figure 8</a>:
2140 <a href="#name-example-of-gma-pdu-format-w" class="selfRef">Example of GMA PDU Format with Concatenation and Trailer-Based IP Encapsulation</a>
2141 </figcaption></figure>
2142 </div>
2143 <p id="section-6-4">
2144 To concatenate two or more SDUs, the transmitter creates one PDU
2145 and copies the content of the IP header field from the first SDU
2146 into the IP header of the PDU. The data of the first SDU is placed
2147 in the first portion of the data of the PDU. The whole second SDU
2148 is then placed in the second portion of the data of the PDU
2149 (<a href="#Fig8" class="xref">Figure 8</a>). The procedure continues until the PDU size reaches the
2150 MTU of the delivery connection. If the FSL field is present, the
2151 IP Length field of the PDU <span class="bcp14">SHOULD</span> be updated to include all
2152 concatenated SDUs and the trailer (or header), and the IP checksum
2153 field <span class="bcp14">SHOULD</span> be recalculated if the packet is IPv4.<a href="#section-6-4" class="pilcrow">¶</a></p>
2154 <p id="section-6-5">
2155 To disaggregate a PDU, if the (header- or trailer-based) IP
2156 encapsulation method is used, the receiver first obtains the
2157 length of the first SDU from the FSL field and decodes the first
2158 SDU. The receiver then obtains the length of the second SDU based
2159 on the length field in the second SDU IP header and decodes the
2160 second SDU. The procedure continues until no byte is left in the
2161 PDU. If the non-IP encapsulation method (<a href="#Fig7" class="xref">Figure 7</a>) is used, the IP
2162 header of the first SDU will not change during the encapsulation
2163 process, and the receiver <span class="bcp14">SHOULD</span> obtain the length of the first
2164 SDU directly from its IP header (<a href="#Fig9" class="xref">Figure 9</a>).<a href="#section-6-5" class="pilcrow">¶</a></p>
2165 <span id="name-example-of-gma-pdu-format-wi"></span><div id="Fig9">
2166 <figure id="figure-9">
2167 <div class="alignLeft art-text artwork" id="section-6-6.1">
2168 <pre>
2169 |&lt;-------1st GMA SDU------------
2170 +---------------------------------------------------------------+
2171 | IP hdr | UDP hdr | GMA Header | IP hdr | IP payload |
2172 +---------------------------------------------------------------+
2173 | IP hdr | IP payload |
2174 +-------------------------------------------+
2175 --------&gt;|&lt;-------2nd GMA SDU---------------&gt;
2176 </pre>
2177 </div>
2178 <figcaption><a href="#figure-9" class="selfRef">Figure 9</a>:
2179 <a href="#name-example-of-gma-pdu-format-wi" class="selfRef">Example of GMA PDU Format with Concatenation and Header-Based Non-IP (UDP) Encapsulation</a>
2180 </figcaption></figure>
2181 </div>
2182 <p id="section-6-7">
2183 If a PDU contains multiple SDUs, the Flow SN field is for the last
2184 SDU, and the Flow SN of other SDUs carried by the same PDU can be
2185 obtained according to its order in the PDU. For example, if the SN
2186 field is 6 and a PDU contains 3 SDUs (IP packets), the SN is 4, 5,
2187 and 6 for the first, second, and last SDU, respectively.<a href="#section-6-7" class="pilcrow">¶</a></p>
2188 <p id="section-6-8">
2189 GMA concatenation can be used for packing small packets of a
2190 single application, e.g., TCP ACKs, or from multiple applications.
2191 Notice that a single GMA flow may carry multiple application flows
2192 (TCP, UDP, etc.).<a href="#section-6-8" class="pilcrow">¶</a></p>
2193 <p id="section-6-9">
2194 GMA endpoints <span class="bcp14">MUST NOT</span> perform concatenation and
2195 fragmentation in a single PDU. If a GMA PDU carries a fragmented SDU, it
2196 <span class="bcp14">MUST NOT</span> carry any other (fragmented or whole) SDU.<a href="#section-6-9" class="pilcrow">¶</a></p>
2197 </section>
2198 </div>
2199 <div id="sect-7">
2200 <section id="section-7">
2201 <h2 id="name-security-considerations">
2202 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
2203 </h2>
2204 <p id="section-7-1">
2205 Security in a network using GMA should be relatively similar to security in
2206 a normal IP network. GMA is unaware of IP- or higher-layer end-to-end
2207 security as it carries the IP packets as opaque payload. Deployers are
2208 encouraged to not consider that GMA adds any form of security and to
2209 continue to use IP- or higher-layer security as well as link-layer
2210 security.<a href="#section-7-1" class="pilcrow">¶</a></p>
2211 <p id="section-7-2">
2212 The GMA protocol at the convergence sublayer is a 0-hop protocol and relies
2213 on the security of the underlying network transport paths. When this cannot
2214 be assumed, appropriate security protocols (IPsec, DTLS, etc.)
2215 <span class="bcp14">SHOULD</span> be configured at the adaptation sublayer. On the
2216 other hand, packet filtering requires either that a firewall looks inside
2217 the GMA packet or that the filtering is done on the GMA endpoints. In those
2218 environments in which this is considered to be a security issue, it may be
2219 desirable to terminate the GMA operation at the firewall.<a href="#section-7-2" class="pilcrow">¶</a></p>
2220 <p id="section-7-3">
2221 Local-only packet leak prevention (HL=0, TTL=1) <span class="bcp14">SHOULD</span> be on
2222 preventing the leak of the local-only GMA PDUs outside the "local domain"
2223 to the Internet or to another domain that could use the same IP protocol
2224 type, i.e., 114.<a href="#section-7-3" class="pilcrow">¶</a></p>
2225 </section>
2226 </div>
2227 <div id="sect-8">
2228 <section id="section-8">
2229 <h2 id="name-iana-considerations">
2230 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
2231 </h2>
2232 <p id="section-8-1">
2233 This document has no IANA actions.<a href="#section-8-1" class="pilcrow">¶</a></p>
2234 </section>
2235 </div>
2236 <section id="section-9">
2237 <h2 id="name-references">
2238 <a href="#section-9" class="section-number selfRef">9. </a><a href="#name-references" class="section-name selfRef">References</a>
2239 </h2>
2240 <section id="section-9.1">
2241 <h3 id="name-normative-references">
2242 <a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
2243 </h3>
2244 <dl class="references">
2245 <dt id="RFC2890">[GRE1]</dt>
2246 <dd>
2247 <span class="refAuthor">Dommety, G.</span>, <span class="refTitle">"Key and Sequence Number Extensions to GRE"</span>, <span class="seriesInfo">RFC 2890</span>, <span class="seriesInfo">DOI 10.17487/RFC2890</span>, <time datetime="2000-09" class="refDate">September 2000</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2890">https://www.rfc-editor.org/info/rfc2890</a>&gt;</span>. </dd>
2248 <dd class="break"></dd>
2249 <dt id="RFC8157">[GRE2]</dt>
2250 <dd>
2251 <span class="refAuthor">Leymann, N.</span>, <span class="refAuthor">Heidemann, C.</span>, <span class="refAuthor">Zhang, M.</span>, <span class="refAuthor">Sarikaya, B.</span>, and <span class="refAuthor">M. Cullen</span>, <span class="refTitle">"Huawei's GRE Tunnel Bonding Protocol"</span>, <span class="seriesInfo">RFC 8157</span>, <span class="seriesInfo">DOI 10.17487/RFC8157</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8157">https://www.rfc-editor.org/info/rfc8157</a>&gt;</span>. </dd>
2252 <dd class="break"></dd>
2253 <dt id="RFC2119">[RFC2119]</dt>
2254 <dd>
2255 <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>
2256 <dd class="break"></dd>
2257 <dt id="RFC8174">[RFC8174]</dt>
2258 <dd>
2259 <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>
2260 <dd class="break"></dd>
2261 </dl>
2262 </section>
2263 <section id="section-9.2">
2264 <h3 id="name-informative-references">
2265 <a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
2266 </h3>
2267 <dl class="references">
2268 <dt id="ATSSS">[ATSSS]</dt>
2269 <dd>
2270 <span class="refAuthor">3GPP</span>, <span class="refTitle">"Study on access traffic steering, switch and splitting support in the 5G System (5GS) architecture"</span>, <span class="refContent">Release 16</span>, <span class="seriesInfo">3GPP TR 23.793</span>, <time datetime="2018-12" class="refDate">December 2018</time>, <span>&lt;<a href="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3254">https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3254</a>&gt;</span>. </dd>
2271 <dd class="break"></dd>
2272 <dt id="GCC">[GCC]</dt>
2273 <dd>
2274 <span class="refAuthor">Holmer, S.</span>, <span class="refAuthor">Lundin, H.</span>, <span class="refAuthor">Carlucci, G.</span>, <span class="refAuthor">De Cicco, L.</span>, and <span class="refAuthor">S. Mascolo</span>, <span class="refTitle">"A Google Congestion Control Algorithm for Real-Time Communication"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-rmcat-gcc-02</span>, <time datetime="2016-07-08" class="refDate">8 July 2016</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-rmcat-gcc-02">https://datatracker.ietf.org/doc/html/draft-ietf-rmcat-gcc-02</a>&gt;</span>. </dd>
2275 <dd class="break"></dd>
2276 <dt id="I-D.zhu-intarea-gma-control">[GMAC]</dt>
2277 <dd>
2278 <span class="refAuthor">Zhu, J.</span> and <span class="refAuthor">M. Zhang</span>, <span class="refTitle">"UDP-based Generic Multi-Access (GMA) Control Protocol"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-zhu-intarea-gma-control-00</span>, <time datetime="2021-10-13" class="refDate">13 October 2021</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-zhu-intarea-gma-control-00">https://datatracker.ietf.org/doc/html/draft-zhu-intarea-gma-control-00</a>&gt;</span>. </dd>
2279 <dd class="break"></dd>
2280 <dt id="IANA">[IANA]</dt>
2281 <dd>
2282 <span class="refAuthor">IANA</span>, <span class="refTitle">"Protocol Numbers"</span>, <span>&lt;<a href="https://www.iana.org/assignments/protocol-numbers">https://www.iana.org/assignments/protocol-numbers</a>&gt;</span>. </dd>
2283 <dd class="break"></dd>
2284 <dt id="IANA1999">[IANA1999]</dt>
2285 <dd>
2286 <span class="refAuthor">IANA</span>, <span class="refTitle">Wayback Machine archive of "Protocol Numbers"</span>, <time datetime="1999-02" class="refDate">February 1999</time>, <span>&lt;<a href="https://web.archive.org/web/19990203044112/http://www.isi.edu:80/in-notes/iana/assignments/protocol-numbers">https://web.archive.org/web/19990203044112/http://www.isi.edu:80/in-notes/iana/assignments/protocol-numbers</a>&gt;</span>. </dd>
2287 <dd class="break"></dd>
2288 <dt id="LWIPEP">[LWIPEP]</dt>
2289 <dd>
2290 <span class="refAuthor">3GPP</span>, <span class="refTitle">"Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-WLAN Radio Level Integration Using Ipsec Tunnel (LWIP) encapsulation; Protocol specification"</span>, <span class="refContent">Release 13</span>, <span class="seriesInfo">3GPP TS 36.361</span>, <time datetime="2020-07" class="refDate">July 2020</time>, <span>&lt;<a href="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3037">https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3037</a>&gt;</span>. </dd>
2291 <dd class="break"></dd>
2292 <dt id="RFC8743">[MAMS]</dt>
2293 <dd>
2294 <span class="refAuthor">Kanugovi, S.</span>, <span class="refAuthor">Baboescu, F.</span>, <span class="refAuthor">Zhu, J.</span>, and <span class="refAuthor">S. Seo</span>, <span class="refTitle">"Multiple Access Management Services Multi-Access Management Services (MAMS)"</span>, <span class="seriesInfo">RFC 8743</span>, <span class="seriesInfo">DOI 10.17487/RFC8743</span>, <time datetime="2020-03" class="refDate">March 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8743">https://www.rfc-editor.org/info/rfc8743</a>&gt;</span>. </dd>
2295 <dd class="break"></dd>
2296 <dt id="MPIP">[MPIP]</dt>
2297 <dd>
2298 <span class="refAuthor">Sun, L.</span>, <span class="refAuthor">Tian, G.</span>, <span class="refAuthor">Zhu, G.</span>, <span class="refAuthor">Liu, Y.</span>, <span class="refAuthor">Shi, H.</span>, and <span class="refAuthor">D. Dai</span>, <span class="refTitle">"Multipath IP Routing on End Devices: Motivation, Design, and Performance"</span>, <time datetime="2017" class="refDate">2017</time>, <span>&lt;<a href="https://eeweb.engineering.nyu.edu/faculty/yongliu/docs/MPIP_Tech.pdf">https://eeweb.engineering.nyu.edu/faculty/yongliu/docs/MPIP_Tech.pdf</a>&gt;</span>. </dd>
2299 <dd class="break"></dd>
2300 <dt id="RFC0791">[RFC0791]</dt>
2301 <dd>
2302 <span class="refAuthor">Postel, J.</span>, <span class="refTitle">"Internet Protocol"</span>, <span class="seriesInfo">STD 5</span>, <span class="seriesInfo">RFC 791</span>, <span class="seriesInfo">DOI 10.17487/RFC0791</span>, <time datetime="1981-09" class="refDate">September 1981</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc791">https://www.rfc-editor.org/info/rfc791</a>&gt;</span>. </dd>
2303 <dd class="break"></dd>
2304 <dt id="RFC8900">[RFC8900]</dt>
2305 <dd>
2306 <span class="refAuthor">Bonica, R.</span>, <span class="refAuthor">Baker, F.</span>, <span class="refAuthor">Huston, G.</span>, <span class="refAuthor">Hinden, R.</span>, <span class="refAuthor">Troan, O.</span>, and <span class="refAuthor">F. Gont</span>, <span class="refTitle">"IP Fragmentation Considered Fragile"</span>, <span class="seriesInfo">BCP 230</span>, <span class="seriesInfo">RFC 8900</span>, <span class="seriesInfo">DOI 10.17487/RFC8900</span>, <time datetime="2020-09" class="refDate">September 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8900">https://www.rfc-editor.org/info/rfc8900</a>&gt;</span>. </dd>
2307 <dd class="break"></dd>
2308 </dl>
2309 </section>
2310 </section>
2311 <div id="authors-addresses">
2312 <section id="appendix-A">
2313 <h2 id="name-authors-addresses">
2314 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
2315 </h2>
2316 <address class="vcard">
2317 <div dir="auto" class="left"><span class="fn nameRole">Jing Zhu</span></div>
2318 <div dir="auto" class="left"><span class="org">Intel</span></div>
2319 <div class="email">
2320 <span>Email:</span>
2321 <a href="mailto:[email protected]" class="email">[email protected]</a>
2322 </div>
2323 </address>
2324 <address class="vcard">
2325 <div dir="auto" class="left"><span class="fn nameRole">Satish Kanugovi</span></div>
2326 <div dir="auto" class="left"><span class="org">Nokia</span></div>
2327 <div class="email">
2328 <span>Email:</span>
2329 <a href="mailto:[email protected]" class="email">[email protected]</a>
2330 </div>
2331 </address>
2332 </section>
2333 </div>
2334 <script>const toc = document.getElementById("toc");
2335 toc.querySelector("h2").addEventListener("click", e => {
2336 toc.classList.toggle("active");
2337 });
2338 toc.querySelector("nav").addEventListener("click", e => {
2339 toc.classList.remove("active");
2340 });
2341 </script>
2342 </body>
2343 </html>