base.txt | issue62.txt | |
---|---|---|
Skipping to change at page 24, line 12: | ||
entry. This allows nodes that have large difference in their | entry. This allows nodes that have large difference in their | |
clocks to still communicate with each other, by exchanging NS/NA | clocks to still communicate with each other, by exchanging NS/NA | |
pairs. | pairs. | |
o When a message is received from a known peer, i.e., one that | o When a message is received from a known peer, i.e., one that | |
already has an entry in the cache, the time stamp is checked | already has an entry in the cache, the time stamp is checked | |
against the previously received SEND message: | against the previously received SEND message: | |
TSnew + fuzz > TSlast + (RDnew - RDlast) x (1 - drift) - fuzz | TSnew + fuzz > TSlast + (RDnew - RDlast) x (1 - drift) - fuzz | |
o If TSnew < TSlast, which is possible if packets arrive rapidly and | If this does not hold, the message SHOULD be silently discarded. | |
out of order, TSlast MUST NOT be updated, i.e., the stored TSlast | ||
for a given node MUST NOT ever decrease. Otherwise TSlast SHOULD | If it does hold, the message is processed. However, if TSnew < | |
be updated. Independent of whether TSlast is updated or not, | TSlast, which is possible if packets arrive rapidly and out of | |
RDlast is updated in any case. | order, TSlast MUST NOT be updated, i.e., the stored TSlast for a | |
given node MUST NOT ever decrease. Otherwise TSlast and RDlast | ||
SHOULD be updated. | ||
6. Authorization Delegation Discovery | 6. Authorization Delegation Discovery | |
Several protocols (NDP included) allow a node to automatically | Several protocols (NDP included) allow a node to automatically | |
configure itself based on information it learns shortly after | configure itself based on information it learns shortly after | |
connecting to a new link. It is particularly easy to configure | connecting to a new link. It is particularly easy to configure | |
"rogue" routers on an unsecured link, and it is particularly | "rogue" routers on an unsecured link, and it is particularly | |
difficult for a node to distinguish between valid and invalid sources | difficult for a node to distinguish between valid and invalid sources | |
of information, when the node needs this information before being | of information, when the node needs this information before being | |
able to communicate with nodes outside of the link. | able to communicate with nodes outside of the link. | |
End of changes. | ||
This html diff was produced by rfcdiff v0.42, available from http://www.levkowetz.com/ietf/tools/rfcdiff/ |