RFC 7186: Security Threats for the Neighborhood Discovery Protocol (NHDP)
In plain English — editorial summary, not part of the RFC
This document analyzes common security threats of the Neighborhood Discovery Protocol (NHDP) and describes their potential impacts on Mobile Ad Hoc Network (MANET) routing protocols using NHDP. This document is not intended to propose solutions to the threats described.
Document record
- Document ID
- RFC7186
- Published
- April 2014
- Authors
- J. Yi; U. Herberg; T. Clausen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
- Updated by:
- RFC 7985
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7187Routing Multipoint Relay Optimization for the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
April 2014
- RFC 7185Link Metrics for the Mobile Ad Hoc Network (MANET) Routing Protocol OLSRv2 - RationaleCurrent
April 2014
- RFC 7184Definition of Managed Objects for the Optimized Link State Routing Protocol Version 2Current
April 2014
- RFC 7188Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVsUpdated
April 2014
- RFC 7183Integrity Protection for the Neighborhood Discovery Protocol (NHDP) and Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
April 2014
- RFC 7189Virtual Circuit Connectivity Verification (VCCV) Capability Advertisement for MPLS Transport Profile (MPLS-TP)Current
March 2014
- RFC 7182Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)Current
April 2014
- RFC 7190Use of Multipath with MPLS and MPLS Transport Profile (MPLS-TP)Current
March 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?