Problem Definition and Classification of BGP Route Leaks
draft-ietf-grow-route-leak-problem-definition-04

The information below is for an old version of the document
Document Type None Internet-Draft (grow WG)
Last updated 2016-04-06 (latest revision 2016-02-11)
Stream IETF
Intended RFC status Informational
Formats
Expired & archived
pdf htmlized bibtex
Reviews
Additional URLs
- Mailing list discussion
Stream WG state (None)
Document shepherd Chris Morrow
Shepherd write-up Show (last changed 2016-03-09)
IESG IESG state Unknown state
Consensus Boilerplate Yes
Telechat date
Responsible AD Joel Jaeggli
Send notices to "Christopher Morrow" <christopher.morrow@gmail.com>

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-ietf-grow-route-leak-problem-definition-04.txt

Abstract

A systemic vulnerability of the Border Gateway Protocol routing system, known as 'route leaks', has received significant attention in recent years. Frequent incidents that result in significant disruptions to Internet routing are labeled "route leaks", but to date we have lacked a common definition of the term. In this document, we provide a working definition of route leaks, keeping in mind the real occurrences that have received significant attention. Further, we attempt to enumerate (though not exhaustively) different types of route leaks based on observed events on the Internet. We aim to provide a taxonomy that covers several forms of route leaks that have been observed and are of concern to Internet user community as well as the network operator community.

Authors

Kotikalapudi Sriram (ksriram@nist.gov)
Doug Montgomery (dougm@nist.gov)
Danny McPherson (dmcpherson@verisign.com)
Eric Osterweil (eosterweil@verisign.com)
Brian Dickson (brian.peter.dickson@gmail.com)

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