RFC 7183: Integrity Protection for the Neighborhood Discovery Protocol (NHDP) and Optimized Link State Routing Protocol Version 2 (OLSRv2)
In plain English — editorial summary, not part of the RFC
This document specifies integrity and replay protection for the Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP) and the Optimized Link State Routing Protocol version 2 (OLSRv2). This protection is achieved by using an HMAC-SHA-256 Integrity Check Value (ICV) TLV and a Timestamp TLV based on Portable Operating System Interface (POSIX) time. The mechanism in this specification can also be used for other protocols that use the generalized packet/message format described in RFC 5444. This document updates RFC 6130 and RFC 7181 by mandating the implementation of this integrity and replay protection in NHDP and OLSRv2.
Document record
- Document ID
- RFC7183
- Published
- April 2014
- Authors
- U. Herberg; C. Dearlove; T. Clausen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7859Identity-Based Signatures for Mobile Ad Hoc Network (MANET) Routing ProtocolsCurrent
May 2016
- RFC 7182Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)Current
April 2014
- RFC 7185Link Metrics for the Mobile Ad Hoc Network (MANET) Routing Protocol OLSRv2 - RationaleCurrent
April 2014
- RFC 7188Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVsUpdated
April 2014
- RFC 7466An Optimization for the Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)Current
March 2015
- RFC 6622Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)Obsoleted
May 2012
- RFC 7184Definition of Managed Objects for the Optimized Link State Routing Protocol Version 2Current
April 2014
- RFC 7128Resource Public Key Infrastructure (RPKI) Router Implementation ReportCurrent
February 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?