Mobile Ad hoc NETwork (MANET) Parameters

Created

  • 2008-12-23

Last Updated

  • 2026-02-12

Available Formats


Message Types

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 5444: Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format
  • RFC 8245: Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444

Available Formats

Type Description Reference
0 HELLO : Local signaling RFC 6130
1 TC : Topology Control (MANET-wide signaling) RFC 7181
2-223 Unassigned
224-255 Reserved for Experimental Use RFC 5444

TC Message-Type-specific Message TLV Types

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7181: The Optimized Link State Routing Protocol Version 2

Available Formats

Range Registration Procedures Note
0-127 Reserved Common to all Message Types, per RFC 5444
128-223 Expert Review
224-255 Reserved Common to all Message Types, per RFC 5444
Type Description Reference
0-127 Reserved RFC 5444
128-223 Unassigned
224-255 Reserved RFC 5444

TC Message-Type-specific Address Block TLV Types

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7181: The Optimized Link State Routing Protocol Version 2

Available Formats

Range Registration Procedures Note
0-127 Reserved Common to all Message Types, per RFC 5444
128-223 Expert Review
224-255 Reserved Common to all Message Types, per RFC 5444
Type Description Reference
0-127 Reserved RFC 5444
128-223 Unassigned
224-255 Reserved RFC 5444

Packet TLV Types

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 5444: Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format
  • RFC 8245: Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444

Available Formats

Type Description Reference
0-4 Unassigned
5 ICV RFC 7182
6 TIMESTAMP RFC 7182
7-223 Unassigned
224-255 Reserved for Experimental Use RFC 5444

Message TLV Types

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 5444: Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format
  • RFC 8245: Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444

Available Formats

Range Registration Procedures Note
0-127 Expert Review
128-223 Expert Review Reserved for Message Type Specific Message TLVs
224-255 Reserved for Experimental Use
Type Description Reference
0 Defined by Type Extension RFC 5497
1 Defined by Type Extension RFC 5497
2-4 Unassigned
5 ICV RFC 7182
6 TIMESTAMP RFC 7182
7 Defined by Type Extension RFC 7181
8 Defined by Type Extension RFC 7181
9-223 Unassigned
224-255 Reserved for Experimental Use RFC 5444

Type 0 Message TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 5497: Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Available Formats

Type Extension Name Description Reference
0 INTERVAL_TIME The maximum time before another message of the same type as this message from the same originator should be received RFC 5497
1-223 Unassigned
224-255 Reserved for Experimental Use RFC 5497

Type 1 Message TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 5497: Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Available Formats

Type Extension Name Description Reference
0 VALIDITY_TIME The time from receipt of the message during which the information contained in the message is to be considered valid RFC 5497
1-223 Unassigned
224-255 Reserved for Experimental Use RFC 5497

Type 7 Message TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7181: The Optimized Link State Routing Protocol Version 2
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Available Formats

Type Extension Name Description Reference
0 MPR_WILLING First (most significant) half octet of Value field specifies the originating router's willingness to act as a flooding MPR; subsequent half octets specify the originating router's willingness to act as a routing MPR, either for the link metric types reported in an MPR_TYPES TLV (in the same order), or (if no MPR_TYPES TLV is present) for the single administratively agreed link metric type RFC 7181; RFC 7631; RFC 7722
1 MPR_TYPES The link metric types supported on this OLSRv2 interface of this router (one octet each) RFC 7722
2 SOURCE_ROUTE Indicates that the originator of the message supports source route forwarding. No value. RFC 8218
3-223 Unassigned
224-255 Reserved for Experimental Use RFC 7181

Type 8 Message TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7181: The Optimized Link State Routing Protocol Version 2
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Available Formats

Type Extension Name Description Reference
0 CONT_SEQ_NUM (COMPLETE) Specifies a content sequence number for this complete message. RFC 7181
1 CONT_SEQ_NUM (INCOMPLETE) Specifies a content sequence number for this incomplete message. RFC 7181
2-223 Unassigned
224-255 Reserved for Experimental Use RFC 7181

HELLO Message-Type-specific Message TLV Types

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 6130: Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)

Available Formats

Range Registration Procedures Note
0-127 Reserved Common to all Message Types, RFC 5444
128-223 Expert Review
224-255 Reserved Common to all Message Types, RFC 5444
Type Description Reference
0-127 Reserved RFC 5444
128 SMF_TYPE RFC 6621
129-223 Unassigned
224-255 Reserved RFC 5444

Address Block TLV Types

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 5444: Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format
  • RFC 8245: Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444

Available Formats

Range Registration Procedures Note
0-127 Expert Review
128-223 Expert Review Reserved for Message Type Specific Address Block TLVs
224-255 Reserved for Experimental Use
Type Description Reference
0 Defined by Type Extension RFC 5497
1 Defined by Type Extension RFC 5497
2 Defined by Type Extension RFC 6130
3 Defined by Type Extension RFC 6130
4 Defined by Type Extension RFC 6130
5 ICV RFC 7182
6 TIMESTAMP RFC 7182
7 LINK_METRIC RFC 7181
8 Defined by Type Extension RFC 7181
9 Defined by Type Extension RFC 7181
10 Defined by Type Extension RFC 7181
11-223 Unassigned
224-255 Reserved for Experimental Use RFC 5444

Type 0 Address Block TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 5497: Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Available Formats

Type Extension Name Description Reference
0 INTERVAL_TIME The maximum time before another message of the same type as this message from the same originator and containing this address should be received RFC 5497
1-223 Unassigned
224-255 Reserved for Experimental Use RFC 5497

Type 1 Address Block TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 5497: Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Available Formats

Type Extension Name Description Reference
0 VALIDITY_TIME The time from receipt of the address during which the information regarding this address is to be considered valid RFC 5497
1-223 Unassigned
224-255 Reserved for Experimental Use RFC 5497

Type 2 Address Block TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 6130: Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Available Formats

Type Extension Name Description Reference
0 LOCAL_IF This value is to be interpreted according to the registry LOCAL_IF TLV Values RFC 6130; RFC 7188
1-223 Unassigned
224-255 Reserved for Experimental Use RFC 6130


Type 4 Address Block TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 6130: Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Available Formats

Type Extension Name Description Reference
0 OTHER_NEIGHB This value is to be interpreted according to the registry OTHER_NEIGHB TLV Values RFC 6130; RFC 7188
1-223 Unassigned
224-255 Reserved for Experimental Use RFC 6130


Type 8 Address Block TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7181: The Optimized Link State Routing Protocol Version 2
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Available Formats

Type Extension Name Description Reference
0 MPR This value is to be interpreted according to the registry MPR TLV Bit Values RFC 7188; RFC 7181
1-223 Unassigned
224-255 Reserved for Experimental Use RFC 7631

Type 9 Address Block TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7181: The Optimized Link State Routing Protocol Version 2
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Available Formats

Type Extension Name Description Reference
0 NBR_ADDR_TYPE This value is to be interpreted according to the registry NBR_ADDR_TYPE Address Block TLV Bit Values RFC 7188; RFC 7181
1-223 Unassigned
224-255 Reserved for Experimental Use RFC 7631

Type 10 Address Block TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7181: The Optimized Link State Routing Protocol Version 2
  • RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Available Formats

Type Extension Name Description Reference
0 GATEWAY Specifies that a given network address is reached via a gateway on the originating router. The number of hops is indicated by the Value field, one octet per link metric type reported in an MPR_TYPES Message TLV (in the same order) or (if no MPR_TYPES Message TLV is present) using a single octet RFC 7181; RFC 7722
1-223 Unassigned
224-255 Reserved for Experimental Use RFC 7631

HELLO Message-Type-specific Address Block TLV Types

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 6130: Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)

Available Formats

Range Registration Procedures Note
0-127 Reserved Common to all Message Types, per RFC 5444
128-223 Expert Review
224-255 Reserved Common to all Message Types, per RFC 5444
Type Description Reference
0-127 Reserved RFC 5444
128 SMF_NBR_TYPE RFC 6621
129-223 Unassigned
224-255 Reserved RFC 5444

ICV Packet TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7182: Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)

Available Formats

Type Extension Description Reference
0 ICV of a packet RFC 7182
1 ICV, using a cryptographic function and a hash function, as specified in Section 12 of RFC 7182 RFC 7182
2 ICV, using a cryptographic function and a hash function, and including the IP datagram source address, as specified in Section 12 of RFC 7182 RFC 7182
3-251 Unassigned
252-255 Reserved for Experimental Use RFC 7182

TIMESTAMP Packet TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7182: Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)

Available Formats

Type Extension Description Reference
0 Unsigned timestamp of arbitrary length, given by the TLV Length field. The MANET routing protocol has to define how to interpret this timestamp RFC 7182
1 Unsigned 32-bit timestamp, as specified in IEEE 1003.1-2008 (POSIX) RFC 7182
2 NTP timestamp format, as defined in RFC 5905 RFC 7182
3 Signed timestamp of arbitrary length with no constraints such as monotonicity. In particular, it may represent any random value RFC 7182
4-251 Unassigned
252-255 Reserved for Experimental Use RFC 7182

ICV Message TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7182: Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)

Available Formats

Type Extension Description Reference
0 ICV of a message RFC 7182
1 ICV, using a cryptographic function and a hash function, as specified in Section 12 of RFC 7182 RFC 7182
2 ICV, using a cryptographic function and a hash function, and including the IP datagram source address, as specified in Section 12 of RFC 7182 RFC 7182
3-251 Unassigned
252-255 Reserved for Experimental Use RFC 7182

TIMESTAMP Message TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7182: Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)

Available Formats

Type Extension Description Reference
0 Unsigned timestamp of arbitrary length, given by the TLV Length field. The MANET routing protocol has to define how to interpret this timestamp RFC 7182
1 Unsigned 32-bit timestamp, as specified in IEEE 1003.1-2008 (POSIX) RFC 7182
2 NTP timestamp format, as defined in RFC 5905 RFC 7182
3 Signed timestamp of arbitrary length with no constraints such as monotonicity. In particular, it may represent any random value RFC 7182
4-251 Unassigned
252-255 Reserved for Experimental Use RFC 7182

ICV Address Block TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7182: Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)

Available Formats

Type Extension Description Reference
0 ICV of an object (e.g. an address) RFC 7182
1 ICV, using a cryptographic function and a hash function, as specified in Section 12 of RFC 7182 RFC 7182
2 ICV, using a cryptographic function and a hash function, and including the IP datagram source address, as specified in Section 12 of RFC 7182 RFC 7182
3-251 Unassigned
252-255 Reserved for Experimental Use RFC 7182

TIMESTAMP Address Block TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7182: Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)

Available Formats

Type Extension Description Reference
0 Unsigned timestamp of arbitrary length, given by the TLV Length field. The MANET routing protocol has to define how to interpret this timestamp RFC 7182
1 Unsigned 32-bit timestamp, as specified in IEEE 1003.1-2008 (POSIX) RFC 7182
2 NTP timestamp format, as defined in RFC 5905 RFC 7182
3 Signed timestamp of arbitrary length with no constraints such as monotonicity. In particular, it may represent any random value RFC 7182
4-251 Unassigned
252-255 Reserved for Experimental Use RFC 7182

Hash Functions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7182: Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)

Available Formats

Value Algorithm Description Reference
0 none The "identity function": The hash value of an object is the object itself RFC 7182
1 SHA-1 NIST-FIPS-180-4 RFC 7182
2 SHA-224 NIST-FIPS-180-4 RFC 7182
3 SHA-256 NIST-FIPS-180-4 RFC 7182
4 SHA-384 NIST-FIPS-180-4 RFC 7182
5 SHA-512 NIST-FIPS-180-4 RFC 7182
6-251 Unassigned
252-255 Reserved for Experimental Use RFC 7182

Cryptographic Functions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7182: Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)

Available Formats

Value Algorithm Description Reference
0 none The "identity function": The value of an encrypted hash is the hash itself RFC 7182
1 RSA RFC 8017 RFC 7182
2 DSA NIST-FIPS-186-4 RFC 7182
3 HMAC RFC 2104 RFC 7182
4 3DES NIST-SP-800-67 RFC 7182
5 AES NIST-FIPS-197 RFC 7182
6 ECDSA RFC 6090 RFC 7182
7 ECCSI ECCSI RFC 6507 RFC 7859
8 ECCSI-ADDR ECCSI RFC 6507 with an address (source or originator) joined to identity RFC 7859
9-251 Unassigned
252-255 Reserved for Experimental Use RFC 7182

SMF_TYPE Message TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 6621: Simplified Multicast Forwarding

Note

Specifies relay algorithm supported by the SMF router, originating the HELLO message, according to Section 11.4.4.

Available Formats

Type Extension Description Reference
0-127 Unassigned
128-255 Reserved for Experimental Use RFC 6621

SMF_NBR_TYPE Address Block TLV Type Extensions

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 6621: Simplified Multicast Forwarding

Note

Specifies relay algorithm supported by the SMF router corresponding to the advertised address, according to Section 11.4.4.

Available Formats

Type Extension Description Reference
0-127 Unassigned
128-255 Reserved for Experimental Use RFC 6621

SMF Relay Algorithm IDs

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 6621: Simplified Multicast Forwarding

Note

A specification requesting an allocation from the 4-127 range from the SMF Relay Algorithm ID Registry MUST specify the interpretation of the <value> field (if any).

Available Formats

Value Name Description Reference
0 CF Section 4 RFC 6621
1 S-MPR Appendix B RFC 6621
2 E-CDS Appendix A RFC 6621
3 MPR-CDS Appendix C RFC 6621
4-127 Unassigned
128-255 Reserved for Experimental Use RFC 6621

LOCAL_IF TLV Values

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7188: Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs

Available Formats

Value Name Description Reference
0 THIS_IF The network address is associated with this local interface of the sending router RFC 7188
1 OTHER_IF The network address is associated with another local interface of the sending router RFC 7188
2-223 Unassigned
224-254 Reserved for Experimental Use RFC 7188
255 UNSPECIFIED No information about this network address is provided RFC 7188


OTHER_NEIGHB TLV Values

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7188: Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs

Available Formats

Value Name Description Reference
0 LOST The neighbor relationship with the router with that network address has been lost RFC 7188
1 SYMMETRIC The neighbor relationship with the router with that network address is symmetric RFC 7188
2-223 Unassigned
224-254 Reserved for Experimental Use RFC 7188
255 UNSPECIFIED No information about this network address is provided RFC 7188

MPR TLV BIT Values

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7188: Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs

Available Formats

Bit Value Name Description Reference
First octet bit 7 First octet 0x01 Flooding If set, then the neighbor with that network address has been selected as flooding MPR RFC 7188; RFC 7722
From first octet bit 6 From first octet 0x02 Routing If set, then the neighbor with that network address has been selected as routing MPR, either for the link metric types reported in an MPR_TYPES TLV (in the same order), or (if no MPR_TYPES TLV is present) then (first octet bit 6, value 0x02) for the single administratively agreed link metric type RFC 7188; RFC 7722

NBR_ADDR_TYPE Address Block TLV Bit Values

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Justin Dean, Christoper Dearlove (backup)

Reference

  • RFC 7188: Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs

Available Formats

Bit Value Name Description Reference
7 0x01 ORIGINATOR The network address is an originator address reachable via the originating router RFC 7188
6 0x02 ROUTABLE The network address is a routable address reachable via the originating router RFC 7188
0-5 Unassigned RFC 7188