datatracker.ietf.org
Sign in
Version 5.6.2.p3, 2014-07-31
Report a bug

Route Leaks -- Proposed Solutions
draft-dickson-sidr-route-leak-solns-01

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2012-09-06 (latest revision 2012-03-05)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-dickson-sidr-route-leak-solns-01.txt

Abstract

The Border Gateway Protocol, version 4, (BGP4) provides the means to advertise reachability for IP prefixes. This reachability information is propagated in a peer-to-peer topology. Sometimes routes are announced to peers for which the local peering policy does not permit. And sometimes routes are propagated indiscriminantly, once they have been accepted. This document considers the situations that can lead to routes being leaked, and tries to find acceptable definitions for describing these scenarios. The purpose of these definitions is to facilitate discussion on what a route leak is, and what the scope of the problem space for route leaks is. This, in turn, is intended to inform a requirements document for detection of (and prevention of) route leaks. And finally, the definitions and requirements are intended to allow proposed solutions which meet these criteria, and to facilitate evaluation of proposed solutions. The fundamental objective is to "solve the route leaks problem".

Authors

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)