RFC 7349: LDP Hello Cryptographic Authentication
In plain English — editorial summary, not part of the RFC
This document introduces a new optional Cryptographic Authentication TLV that LDP can use to secure its Hello messages. It secures the Hello messages against spoofing attacks and some well-known attacks against the IP header. This document describes a mechanism to secure the LDP Hello messages using Hashed Message Authentication Code (HMAC) with the National Institute of Standards and Technology (NIST) Secure Hash Standard family of algorithms.
Document record
- Document ID
- RFC7349
- Published
- August 2014
- Authors
- L. Zheng; M. Chen; M. Bhatia
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7353Security Requirements for BGP Path ValidationCurrent
August 2014
- RFC 7356IS-IS Flooding Scope Link State PDUs (LSPs)Current
September 2014
- RFC 7357Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) ProtocolCurrent
September 2014
- RFC 7358Label Advertisement Discipline for LDP Forwarding Equivalence Classes (FECs)Current
October 2014
- RFC 7338Requirements and Framework for Point-to-Multipoint Pseudowires over MPLS Packet Switched NetworksCurrent
September 2014
- RFC 7361LDP Extensions for Optimized MAC Address Withdrawal in a Hierarchical Virtual Private LAN Service (H-VPLS)Current
September 2014
- RFC 7334PCE-Based Computation Procedure to Compute Shortest Constrained Point-to-Multipoint (P2MP) Inter-Domain Traffic Engineering Label Switched PathsCurrent
August 2014
- RFC 7364Problem Statement: Overlays for Network VirtualizationCurrent
October 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?