| rfc8824v2.txt | rfc8824.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) A. Minaburo | Internet Engineering Task Force (IETF) A. Minaburo | |||
| Request for Comments: 8824 Acklio | Request for Comments: 8824 Acklio | |||
| Category: Standards Track L. Toutain | Category: Standards Track L. Toutain | |||
| ISSN: 2070-1721 IMT Atlantique | ISSN: 2070-1721 IMT Atlantique | |||
| R. Andreasen | R. Andreasen | |||
| Universidad de Buenos Aires | Universidad de Buenos Aires | |||
| June 2021 | June 2021 | |||
| Static Context Header Compression and Fragmentation (SCHC) | Static Context Header Compression (SCHC) for the | |||
| for the Constrained Application Protocol (CoAP) | Constrained Application Protocol (CoAP) | |||
| Abstract | Abstract | |||
| This document defines how to compress Constrained Application | This document defines how to compress Constrained Application | |||
| Protocol (CoAP) headers using the Static Context Header Compression | Protocol (CoAP) headers using the Static Context Header Compression | |||
| and fragmentation (SCHC) framework. SCHC defines a header | and fragmentation (SCHC) framework. SCHC defines a header | |||
| compression mechanism adapted for Constrained Devices. SCHC uses a | compression mechanism adapted for Constrained Devices. SCHC uses a | |||
| static description of the header to reduce the header's redundancy | static description of the header to reduce the header's redundancy | |||
| and size. While RFC 8724 describes the SCHC compression and | and size. While RFC 8724 describes the SCHC compression and | |||
| fragmentation framework, and its application for IPv6/UDP headers, | fragmentation framework, and its application for IPv6/UDP headers, | |||
| skipping to change at line 960 ¶ | skipping to change at line 960 ¶ | |||
| |CoAP |8 |1 |Up|1 | equal | not-sent | | | |CoAP |8 |1 |Up|1 | equal | not-sent | | | |||
| |Code | | | | | | | | | |Code | | | | | | | | | |||
| +--------+--+--+--+-----------+---------------+--------------+======+ | +--------+--+--+--+-----------+---------------+--------------+======+ | |||
| |CoAP |8 |1 |Dw|[69,132] | match-mapping | mapping-sent |c | | |CoAP |8 |1 |Dw|[69,132] | match-mapping | mapping-sent |c | | |||
| |Code | | | | | | | | | |Code | | | | | | | | | |||
| +--------+--+--+--+-----------+---------------+--------------+======+ | +--------+--+--+--+-----------+---------------+--------------+======+ | |||
| |CoAP | |1 |Up|temperature| equal | not-sent | | | |CoAP | |1 |Up|temperature| equal | not-sent | | | |||
| |Uri-Path| | | | | | | | | |Uri-Path| | | | | | | | | |||
| +--------+--+--+--+-----------+---------------+--------------+======+ | +--------+--+--+--+-----------+---------------+--------------+======+ | |||
| Table 4: Inner SCHC Rules | Table 4: Inner SCHC Rule | |||
| Figure 10 shows the Plaintext obtained for the example GET request. | Figure 10 shows the Plaintext obtained for the example GET request. | |||
| The packet follows the process of Inner Compression and encryption | The packet follows the process of Inner Compression and encryption | |||
| until the payload. The Outer OSCORE message adds the result of the | until the payload. The Outer OSCORE message adds the result of the | |||
| Inner process. | Inner process. | |||
| ________________________________________________________ | ________________________________________________________ | |||
| | | | | | | |||
| | OSCORE Plaintext | | | OSCORE Plaintext | | |||
| | | | | | | |||
| End of changes. 2 change blocks. | ||||
| 3 lines changed or deleted | 3 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||