RFC Errata
Found 2 records.
Status: Verified (2)
RFC 6824, "TCP Extensions for Multipath Operation with Multiple Addresses", January 2013
Note: This RFC has been obsoleted by RFC 8684
Source of RFC: mptcp (tsv)
Errata ID: 3578
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Kasper Dupont
Date Reported: 2013-04-01
Verifier Name: Martin Stiemerling
Date Verified: 2013-04-12
Section 3.1 says:
Note that new subflows MUST NOT be established (using the process documented in Section 3.2) until a Digital Signature Standard (DSS) option has been successfully received across the path (as documented in Section 3.3).
It should say:
Note that new subflows MUST NOT be established (using the process documented in Section 3.2) until a Data Sequence Signal (DSS) option has been successfully received across the path (as documented in Section 3.3).
Notes:
In this document DSS is indicated as short for both "Digital Signature Standard" and "Data Sequence Signal". I guess the reference to "Digital Signature Standard" was a mistake.
Errata ID: 4129
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Friedrich Haussmann
Date Reported: 2014-10-11
Verifier Name: Martin Stiemerling
Date Verified: 2016-01-12
Section B.1.1. says:
MPTCP.Checksum (flag): This flag is set to true if at least one of the hosts has set the C bit in the MP_CAPABLE options exchanged during connection establishment, and is set to false otherwise. If this flag is set, the checksum must be computed in all DSS options.
It should say:
MPTCP.Checksum (flag): This flag is set to true if at least one of the hosts has set the A bit in the MP_CAPABLE options exchanged during connection establishment, and is set to false otherwise. If this flag is set, the checksum must be computed in all DSS options.
Notes:
Checksum is not on bit "C", but instead on bit "A". There are no other instances of referring on bit "C" as the checksum. Bit "C" is unassigned in this version.
Other instances of bit "A" as checksum:
* Section 3.1. Connection Initiation, p. 16 f.
* Section 8. IANA Considerations, Table 3: MPTCP Handshake Algorithms, p. 56