RFC Errata
Found 5 records.
Status: Verified (2)
RFC 6130, "Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)", April 2011
Note: This RFC has been updated by RFC 7183, RFC 7188, RFC 7466
Source of RFC: manet (rtg)
Errata ID: 3677
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Christopher Dearlove
Date Reported: 2013-07-04
Verifier Name: Adrian Farrel
Date Verified: 2013-09-17
Section App. B p. 65 says:
o L_HEARD_time MUST NOT be greater than L_time.
It should say:
o L_HEARD_time MUST NOT be greater than L_time,
unless L_lost = true.
Notes:
The case currently indicated as a constraint failure,
but not by the relaxed constraint, can occur - and
correctly - in normal operation of the protocol.
Errata ID: 4276
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Christopher Dearlove
Date Reported: 2015-02-23
Verifier Name: Adrian Farrel
Date Verified: 2015-02-24
Section Section 12.6 says:
then create a 2-Hop Neighbor Tuple with:
It should say:
then create a 2-Hop Tuple with:
Notes:
There is no such thing as a 2-Hop Neighbor Tuple. There is a 2-Hop Tuple (which is what is meant) but also a Neighbor Tuple (which is not meant).
Status: Held for Document Update (3)
RFC 6130, "Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)", April 2011
Note: This RFC has been updated by RFC 7183, RFC 7188, RFC 7466
Source of RFC: manet (rtg)
Errata ID: 4866
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Nikolai Malykh
Date Reported: 2016-11-15
Held for Document Update by: Alvaro Retana
Date Held: 2017-01-25
Section 4.3.2 says:
o For each MANET interface, within every time interval equal to the
corresponding REFRESH_INTERVAL, sent HELLO messages MUST
collectively include all of the relevant information in the
corresponding Link Set and the Neighbor Information Base. Note
that when determining whether to include information in a HELLO
message, the sender MUST consider all times up to the latest time
when it may send its next HELLO message on this MANET interface.
o For each MANET interface, within every time interval equal to the
corresponding REFRESH_INTERVAL, sent HELLO messages MUST
collectively include all of the relevant information in the
corresponding Link Set and the Neighbor Information Base.
It should say:
o For each MANET interface, within every time interval equal to the
corresponding REFRESH_INTERVAL, sent HELLO messages MUST
collectively include all of the relevant information in the
corresponding Link Set and the Neighbor Information Base. Note
that when determining whether to include information in a HELLO
message, the sender MUST consider all times up to the latest time
when it may send its next HELLO message on this MANET interface.
Notes:
The second statement is already contained in the first one.
=====
From Christopher Dearlove (author):
it is the other paragraph that should be deleted. Because the paragraph following the two quoted paragraphs, which I copy here:
o When determining whether to include a given piece of neighbor
information in a HELLO message, it is not sufficient to consider
whether that information has been sent in the interval of length
REFRESH_INTERVAL up to the current time. Instead, the router MUST
consider the interval of length REFRESH_INTERVAL that will end at
the latest possible time at which the next HELLO message will be
sent on this MANET interface. (Normally, this will be
HELLO_INTERVAL past the current time, but MAY be earlier if this
router elects to divide its neighbor information among more than
one HELLO message in order to reduce the size of its HELLO
messages.) All neighbor information MUST be sent in this
interval, i.e., the router MUST ensure that this HELLO message
includes all neighbor information that has not already been
included in any HELLO messages sent since the start of this
interval (normally, the current time - (REFRESH_INTERVAL -
HELLO_INTERVAL)).
contains the additional information in the longer paragraph, expanded to explain what it means.
Thus the resolution is to delete the first paragraph:
OLD:
o For each MANET interface, within every time interval equal to the
corresponding REFRESH_INTERVAL, sent HELLO messages MUST
collectively include all of the relevant information in the
corresponding Link Set and the Neighbor Information Base. Note
that when determining whether to include information in a HELLO
message, the sender MUST consider all times up to the latest time
when it may send its next HELLO message on this MANET interface.
NEW:
Errata ID: 5780
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Nikolai Malykh
Date Reported: 2019-07-14
Held for Document Update by: Alvaro Retana
Date Held: 2019-07-17
Section F.3 says:
The content of the Interface Information Base is in this case
identical to than in Example 1, except that the 2-Hop Set contains an
extra 2-Hop Tuple with N2_neighbor_iface_addr_list being {2} and
N2_2hop_addr being {4}. These two 2-Hop Tuples are illustrated by
the two lines from {2} to {3} and (2) to {4}, respectively.
It should say:
The content of the Interface Information Base is in this case
identical to than in Example 1, except that the 2-Hop Set contains an
extra 2-Hop Tuple with N2_neighbor_iface_addr_list being {2} and
N2_2hop_addr being {4}. These two 2-Hop Tuples are illustrated by
the two lines from {2} to {3} and {2} to {4}, respectively.
Notes:
Parentheses are mistakenly typed. s/(2)/{2}
Errata ID: 5785
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Steve Matty
Date Reported: 2019-07-18
Held for Document Update by: Alvaro Retana
Date Held: 2019-07-18
Section F.3 says:
The content of the Interface Information Base is in this case
identical to than in Example 1, except that the 2-Hop Set contains an
extra 2-Hop Tuple with N2_neighbor_iface_addr_list being {2} and
N2_2hop_addr being {4}. These two 2-Hop Tuples are illustrated by
the two lines from {2} to {3} and (2) to {4}, respectively.
It should say:
The content of the Interface Information Base is in this case
identical to that in Example 1, except that the 2-Hop Set contains an
extra 2-Hop Tuple with N2_neighbor_iface_addr_list being {2} and
N2_2hop_addr being {4}. These two 2-Hop Tuples are illustrated by
the two lines from {2} to {3} and (2) to {4}, respectively.
Notes:
Typo in first sentence. "than" should read "that"