Hi Randy, Emile,
A few small notes that might be of interest should you wish to progress
this draft:
* 32-bit ASNs don't fit in 16-bit fields. Consider using a set of
Extended Communities?
* The Local Administrator values {64994,64995,64996} might already
be in use and carry local significance.
* I wouldn't avoid setting up an IANA registry merely because there are
'very few categories'
* Section 5's 'well-known prefix' perhaps should be set to TBD, rather
than using widely used RFC 1918 space.
Kind regards,
Job
On Thu, Feb 17, 2022 at 01:22:09PM -0800, Randy Bush wrote:
> six and a half year old draft rises from the dead, with modification
>
> From: internet-dra...@ietf.org
> To: Emile Aben <emile.a...@ripe.net>, Randy Bush <ra...@psg.com>
> Subject: New Version Notification for
> draft-ymbk-grow-bgp-collector-communities-02.txt
> Date: Thu, 17 Feb 2022 13:09:38 -0800
>
> A new version of I-D, draft-ymbk-grow-bgp-collector-communities-02.txt
> has been successfully submitted by Randy Bush and posted to the
> IETF repository.
>
> Name: draft-ymbk-grow-bgp-collector-communities
> Revision: 02
> Title: Marking Announcements to BGP Collectors
> Document date: 2022-02-17
> Group: Individual Submission
> Pages: 5
> URL:
> https://www.ietf.org/archive/id/draft-ymbk-grow-bgp-collector-communities-02.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ymbk-grow-bgp-collector-communities/
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-ymbk-grow-bgp-collector-communities
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ymbk-grow-bgp-collector-communities-02
>
> 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.
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
_______________________________________________
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow
