RFC Errata
Found 9 records.
Status: Reported (9)
RFC 8824, "Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)", June 2021
Source of RFC: lpwan (int)
Errata ID: 7389
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF
Reported By: Marco Tiloca
Date Reported: 2023-03-19
Section 3.1 says:
For example, the Uri-Path option is mandatory in the request, and it might not be present in the response.
It should say:
For example, the Uri-Path option can be used in the request, while it is not used in the response.
Notes:
The Uri-Path option is not mandatory in a CoAP request, and it is not supposed to be used in a CoAP response.
Errata ID: 7391
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF
Reported By: Marco Tiloca
Date Reported: 2023-03-19
Section 5.4 says:
The SCHC Rule description MAY define sending some field values by setting the TV to "not-sent", the MO to "ignore", and the CDA to "value-sent".
It should say:
The SCHC Rule description MAY define sending some field values by describing an empty TV, with the MO set to "ignore" and the CDA set to "value-sent".
Notes:
The new text indicates to use an empty TV, consistent with the intended CDA "value-sent".
Errata ID: 7392
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF
Reported By: Marco Tiloca
Date Reported: 2023-03-19
Section 6.2 says:
Since the Observe Option MAY use a RST message to inform a server that the client does not require the Observe response, a specific SCHC Rule SHOULD exist to allow the message's compression with the RST type.
It should say:
Since the Observe extension MAY use a RST message to inform a server that the client does not require the Observe response, a specific SCHC Rule SHOULD exist to allow the message's compression with the RST type.
Notes:
A RST message is not used by the Observe option itself, but by a CoAP client when using Observe.
Errata ID: 7394
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF
Reported By: Marco Tiloca
Date Reported: 2023-03-19
Section 7.1 says:
equal 1
It should say:
equal
Notes:
See the cell value of Table 3, last row, column "MO".
Errata ID: 7395
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF
Reported By: Marco Tiloca
Date Reported: 2023-03-19
Section 7.1 says:
SCHC compression reduces the header, sending only the Type, a mapped code, and the least significant bits of the Message ID (9 bits in the example above).
It should say:
SCHC compression reduces the header, sending only a mapped Type (and only for uplink messages), a mapped code, and the least significant bits of the Message ID (9 bits in the example above).
Notes:
As per the discussed rule from Table 3, the Type is also omitted if it is CON for downlink messages.
Errata ID: 7396
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF
Reported By: Marco Tiloca
Date Reported: 2023-03-19
Section 7.1 says:
Note that a client located in an Application Server sending a request to a server located in the Device may not be compressed through this Rule, since the MID might not start with 7 bits equal to 0.
It should say:
Note that, if a client is located in an Application Server and sends a request to a server located in the Device, then the request may not be compressed through this Rule, since the MID might not start with 7 bits equal to 0.
Notes:
In the old text, "compressed" seems referred to "client" rather than to "request" as intended.
Errata ID: 7397
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF
Reported By: Marco Tiloca
Date Reported: 2023-03-19
Section 7.2 says:
These classes point out that the Outer option contains the OSCORE option and that the message is OSCORE protected; this option carries the information necessary to retrieve the Security Context.
It should say:
As per these classes, the Outer options comprise the OSCORE option, which indicates that the message is OSCORE protected and carries the information necessary to retrieve the Security Context.
Notes:
"Outer options" should be in the plural, to refer to the set of CoAP options left unencrypted. Such a set comprises also the OSCORE option, which is the actual indicator of the message being protected with OSCORE.
Errata ID: 7390
Status: Reported
Type: Editorial
Publication Format(s) : TEXT, PDF
Reported By: Marco Tiloca
Date Reported: 2023-03-19
Section 5.1 says:
CoAP Content and Accept Options
It should say:
CoAP Option Content-Format and Accept Fields
Notes:
The new title of Section 5.1 uses the correct CoAP option name "Content-Format", and is consistent with the title of other sections.
Errata ID: 7393
Status: Reported
Type: Editorial
Publication Format(s) : TEXT, PDF
Reported By: Marco Tiloca
Date Reported: 2023-03-19
Section 6.4 says:
Figure 4 shows the OSCORE option value encoding defined in Section 6.1 of [RFC8613], where the first byte specifies the content of the OSCORE options using flags.
It should say:
Figure 4 shows the OSCORE option value encoding defined in Section 6.1 of [RFC8613], where the first byte specifies the content of the OSCORE option using flags.
Notes:
The end of the sentence should still refer to a single OSCORE option, i.e., in the singular.