RFC Errata
Found 2 records.
Status: Held for Document Update (2)
RFC 7183, "Integrity Protection for the Neighborhood Discovery Protocol (NHDP) and Optimized Link State Routing Protocol Version 2 (OLSRv2)", April 2014
Source of RFC: manet (rtg)
Errata ID: 4397
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Jiazi
Date Reported: 2015-06-22
Held for Document Update by: Alvaro Retana
Date Held: 2015-06-22
Section 4 says:
Generation of TIMESTAMP Message TLVs (as defined in [RFC7182]) for inclusion in an outgoing message. An implementation of [RFC6130] and [RFC7181] MAY use more than one ICV TLV in a message, but it MUST NOT use the same type extensio
It should say:
Generation of TIMESTAMP Message TLVs (as defined in [RFC7182]) for inclusion in an outgoing message. An implementation of [RFC6130] and [RFC7181] MAY use more than one TIMESTAMP TLV in a message , but it MUST NOT use the same type extensio
Notes:
We are only talking about TIMESTAMP TLV in this paragraph.
I think it's an error when copying the text from the previous paragraph.
Errata ID: 5144
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Denis Ovsienko
Date Reported: 2017-10-04
Held for Document Update by: Alvaro Retana
Date Held: 2017-11-06
Section 8.1.3 says:
is contained in message. As an attacker cannot modify the content of this timestamp (as it is protected by the identity check value), an attacker cannot replay messages after this time. Within this time
It should say:
is contained in message. As an attacker cannot modify the content of this timestamp (as it is protected by the integrity check value), an attacker cannot replay messages after this time. Within this time
Notes:
Integrity check value (ICV) is the means of protection in this document.