Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format

Abstract

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Security Threats to Simplified Multicast Forwarding (SMF)

“…This document uses the terminology and notation defined in [RFC5444], [RFC6130], [RFC6621], and [RFC4949].…”

Security Threats for the Neighborhood Discovery Protocol (NHDP)

“…This document uses the terminology and notation defined in "Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format" [RFC5444], "Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)" [RFC6130], and "Internet Security Glossary, Version 2" [RFC4949].…”

“…One of the listed examples uses packet exchanges between neighbor routers (as described in [RFC5444]), e.g., an NHDP router may update the link quality of a neighbor based on receipt or loss of packets if they include a sequential packet sequence number.…”

Multipath optimized link state routing for mobile ad hoc networks

“…Being modular by design, OLSRv2 is made up from a number of generalized building blocks, standardized independently and applicable also for other MANET protocols. Currently, RFC 5148 -Jitter Considerations in Mobile Ad Hoc Networks [6], RFC 5444 -Generalized MANET Packet / Message Format [7] and RFC 5497 -Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs) [8] are published as RFCs, with the remaining constituent parts (MANET Neighborhood Discovery Protocol [9] and OLSRv2 [10]) being in the final phases of standardization. It has a more modular and extensible architecture, and is simpler and more efficient than OLSRv1.…”

“…In this paper, we follow the RFC of OLSR [1], which uses hop count as link metric. However, different metrics can be easily appended to HELLO or TC messages by using the extensible architecture of OLSRv2 [7].…”