Marking Announcements to BGP Collectors
draft-ymbk-grow-bgp-collector-communities-01

Document Type Expired Internet-Draft (individual)
Last updated 2016-03-10 (latest revision 2015-09-07)
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-ymbk-grow-bgp-collector-communities-01.txt

Abstract

When BGP route collectors such as RIPE RIS and Route Views are used by operators and researchers, currently one can not tell if a path announced to a collector is from the ISP's customer cone, an internal route, or one learned from peering or transit. This greatly reduces the utility of the collected data. This document specifies the use of BGP communities to differentiate the kinds of views being presented to the collectors.

Authors

Randy Bush (randy@psg.com)
Emile Aben (emile.aben@ripe.net)

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