Keying and Authentication for Routing Protocols Overview, Threats, and Requirements
RFC 6862, “Keying and Authentication for Routing Protocols Overview, Threats, and Requirements”, is an Informational document published in March 2013 by G. Lebovitz, M. Bhatia, B. Weis. The canonical text is published by the RFC Editor.
Abstract
Different routing protocols employ different mechanisms for securing protocol packets on the wire. While most already have some method for accomplishing cryptographic message authentication, in many cases the existing methods are dated, vulnerable to attack, and employ cryptographic algorithms that have been deprecated. The "Keying and Authentication for Routing Protocols" (KARP) effort aims to overhaul and improve these mechanisms. This document does not contain protocol specifications. Instead, it defines the areas where protocol specification work is needed. This document is a companion document to RFC 6518, "Keying and Authentication for Routing Protocols (KARP) Design Guidelines"; together they form the guidance and instruction KARP design teams will use to review and overhaul routing protocol transport security.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6862 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6861 The "create-form" and "edit-form" Link Relations
- RFC 6863 Analysis of OSPF Security According to the Keying and Authentication for Routing Protocols Design Guide
- RFC 6860 Hiding Transit-Only Networks in OSPF
- RFC 6864 Updated Specification of the IPv4 ID Field
- RFC 6859 Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership
- RFC 6865 Simple Reed-Solomon Forward Error Correction Scheme for FECFRAME
- RFC 6858 Simplified POP and IMAP Downgrading for Internationalized Email
- RFC 6866 Problem Statement for Renumbering IPv6 Hosts with Static Addresses in Enterprise Networks