Subject: [GROW] draft-ymbk-grow-bgp-collector-communities-00.txt

From: Randy Bush <[email-masked]>
Date: Sat, 05 Sep 2015 09:35:30 +0200

Name:		draft-ymbk-grow-bgp-collector-communities
Revision:	00
Title:		Marking Announcements to BGP Collectors
Document date:	2015-09-04
Group:		Individual Submission
Pages:		5
URL:            https://www.ietf.org/internet-drafts/draft-ymbk-grow-bgp-collector-communities-00.txt
Status:         https://datatracker.ietf.org/doc/draft-ymbk-grow-bgp-collector-communities/
Htmlized:       https://tools.ietf.org/html/draft-ymbk-grow-bgp-collector-communities-00

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.