BGP Route Leak Protection Community
draft-heitz-idr-route-leak-community-00

Document Type Expired Internet-Draft (individual)
Last updated 2018-04-19 (latest revision 2017-10-01)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-heitz-idr-route-leak-community-00.txt

Abstract

In general, BGP autonomous system (AS) relationships are either customer-transit or peer-peer. If an AS sends a route received from a transit or a peer to another transit or to another peer, it is considered a route leak. AS relationships are sometimes different for different routes or in different regions. A method of detecting route leaks is proposed that does not require participation by the leaking AS or by IXPs. Only the ASes that perform leak detection need to adopt the proposal. ASes that request leak protection need to send a community to make the request. The proposal works even if the leaking AS or other ASes modify or discard path attributes in the route or create more specific routes.

Authors

Jakob Heitz (jheitz@cisco.com)
Job Snijders (job@ntt.net)

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