Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)

Security Threats to Simplified Multicast Forwarding (SMF)

“…Based on [RFC7182], [RFC7183] specifies integrity and replay protection for NHDP using shared keys as a mandatory-to-implement security mechanism. If SMF is using NHDP as the neighborhood discovery protocol, implementing [RFC7183] remains advisable so as to enable integrity protection for NHDP control messages.…”

“…Detection and exclusion of such attackers is, in general, a challenge that is not unrelated to how [RFC7182] is used. If, for example, it is used with a shared key (as per [RFC7183]), excluding single attackers generally is not aided by the use of ICVs.…”

“…[RFC7182] provides a framework that can be used with SMF, and depending on how it is used, may offer some degree of protection against the threats related to identity spoofing described in this document.…”

TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

“…For clarity, all currently allocated TLVs in [RFC5497], [RFC6130], [RFC6621], [RFC7181], and [RFC7182] are listed in the IANA Considerations section of this document, each specifying the updates or indicating no change when that is appropriate (such as the LINK_METRIC TLV and both TLVs defined in [RFC6621]). The only changes are of naming.…”

Identity-Based Signatures for Mobile Ad Hoc Network (MANET) Routing Protocols

“…Introduction [RFC7182] defines Integrity Check Value (ICV) TLVs for use in packets and messages that use the generalized MANET packet/message format defined in [RFC5444]. This specification extends the TLV definitions therein by defining two new cryptographic function code points from within the registries set up by [RFC7182].…”