Methods for Detection and Mitigation of BGP Route Leaks
draft-sriram-route-leak-detection-mitigation-00

Document Type Expired Internet-Draft (individual)
Authors Kotikalapudi Sriram  , Doug Montgomery 
Last updated 2015-04-30 (latest revision 2014-10-27)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-sriram-route-leak-detection-mitigation-00.txt

Abstract

In [I-D.ietf-sriram-route-leak-problem-definition], the authors have provided a definition of the route leak problem, and also enumerated several types of route leaks. In this document, we first examine which of those route-leak types are detected and mitigated by the existing BGPSEC protocol [I-D.ietf-sidr-bgpsec-protocol-09]. Where the current BGPSEC protocol doesn't offer a solution, this document suggests an enhancement that would extend the route-leak detection and mitigation capability of BGPSEC. The solution can be implemented in BGP without necessarily tying it to BGPSEC. Incorporating the solution in BGPSEC is one way of implementing it in a secure way. We do not claim to have provided a solution for all possible types of route leaks, but the solution covers several, especially considering some significant route-leak attacks or occurrences that have been observed in recent years. The document also includes a stopgap method for detection and mitigation of route leaks for the phase when BGPSEC (path validation) is not yet deployed but only origin validation is deployed.

Authors

Kotikalapudi Sriram (ksriram@nist.gov)
Doug Montgomery (dougm@nist.gov)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)