RFC 8061: Locator/ID Separation Protocol (LISP) Data-Plane Confidentiality
In plain English — editorial summary, not part of the RFC
This document describes a mechanism for encrypting traffic encapsulated using the Locator/ID Separation Protocol (LISP). The design describes how key exchange is achieved using existing LISP control-plane mechanisms as well as how to secure the LISP data plane from third-party surveillance attacks.
Document record
- Document ID
- RFC8061
- Published
- February 2017
- Authors
- D. Farinacci; B. Weis
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9306Vendor-Specific LISP Canonical Address Format (LCAF)Current
October 2022
- RFC 8060LISP Canonical Address Format (LCAF)Updated
February 2017
- RFC 8059PIM Join Attributes for Locator/ID Separation Protocol (LISP) EnvironmentsUpdated
January 2017
- RFC 8051Applicability of a Stateful Path Computation Element (PCE)Current
January 2017
- RFC 8077Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)Current
February 2017
- RFC 8042OSPF Two-Part MetricCurrent
December 2016
- RFC 8036Applicability Statement for the Routing Protocol for Low-Power and Lossy Networks (RPL) in Advanced Metering Infrastructure (AMI) NetworksCurrent
January 2017
- RFC 8092BGP Large Communities AttributeCurrent
February 2017
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?