Marking Announcements to BGP Collectors
draft-ymbk-grow-bgp-collector-communities-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Randy Bush , Emile Aben | ||
| Last updated | 2016-03-10 (Latest revision 2015-09-07) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)