RFC 6863: Analysis of OSPF Security According to the Keying and Authentication for Routing Protocols (KARP) Design Guide
In plain English — editorial summary, not part of the RFC
This document analyzes OSPFv2 and OSPFv3 according to the guidelines set forth in Section 4.2 of the "Keying and Authentication for Routing Protocols (KARP) Design Guidelines" (RFC 6518). Key components of solutions to gaps identified in this document are already underway.
Document record
- Document ID
- RFC6863
- Published
- March 2013
- Authors
- S. Hartman; D. Zhang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6862Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and RequirementsCurrent
March 2013
- RFC 6860Hiding Transit-Only Networks in OSPFCurrent
January 2013
- RFC 6870Pseudowire Preferential Forwarding Status BitUpdated
February 2013
- RFC 6850Definitions of Managed Objects for Routing Bridges (RBridges)Current
January 2013
- RFC 6845OSPF Hybrid Broadcast and Point-to-Multipoint Interface TypeCurrent
January 2013
- RFC 6836Locator/ID Separation Protocol Alternative Logical Topology (LISP+ALT)Current
January 2013
- RFC 6835The Locator/ID Separation Protocol Internet Groper (LIG)Current
January 2013
- RFC 6834Locator/ID Separation Protocol (LISP) Map-VersioningObsoleted
January 2013
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?