Browse Prior Art Database

Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements (RFC6862) Disclosure Number: IPCOM000225746D
Original Publication Date: 2013-Mar-01
Included in the Prior Art Database: 2013-Mar-02
Document File: 52 page(s) / 68K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Lebovitz: AUTHOR [+2]


In March 2006, the Internet Architecture Board (IAB) held a workshop on the topic "Unwanted Internet Traffic". The report from that workshop is documented in [RFC4948]. Section 8.1 of that document states, "A simple risk analysis would suggest that an ideal attack target of minimal cost but maximal disruption is the core routing infrastructure". Section 8.2 calls for "[t]ightening the security of the core routing infrastructure". Four main steps were identified for that tightening:

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Internet Engineering Task Force (IETF)                       G. Lebovitz Request for Comments: 6862 Category: Informational                                        M. Bhatia ISSN: 2070-1721                                           Alcatel-Lucent                                                                  B. Weis                                                            Cisco Systems                                                               March 2013

          Keying and Authentication for Routing Protocols (KARP)                   Overview, Threats, and Requirements


   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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

 Lebovitz, et al.              Informational                     [Page 1]
 RFC 6862        KARP Overview, Threats, and Requirements      March 2013

 Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (htt...