Marking Announcements to BGP Collectors
draft-ymbk-grow-bgp-collector-communities-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Randy Bush , Emile Aben | ||
Last updated | 2022-08-21 (Latest revision 2022-02-17) | ||
RFC stream | (None) | ||
Intended RFC status | (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 the collection of paths announced to a collector represents the ISP's customer cone, includes internal routes, includes paths learned from peerings or transits. 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.)