Dear all,
On Mon, Oct 28, 2019 at 07:21:13PM +0000, Job Snijders wrote:
> Milestones
> ==========
>
> Jan 2020 - "Support for Local RIB in BGP Monitoring Protocol (BMP)" to IESG
> Feb 2020 - "BMP Peer Up Message Namespace" to IESG
> Apr 2020 - "Revision to Registration Procedures for Multiple BMP Registries"
> to IESG.
> Jul 2020 - “Document negative consequences of de-aggregating received routes
> for traffic engineering purposes” - to IESG
> Nov 2020 - "TLV support for BMP Route Monitoring and Peer Down Messages" to
> IESG.
> Jan 2021 - “A BCP on using IRR and RPKI data to improve filtering of BGP
> peering sessions” to IESG or via “Evolving Documents”
Perhaps as a milestone we can also add an effort to create a mechanism
to allow mapping integer values in BGP {Classic, Extended, Large, Wide}
Communities to semantics by devising a system to express equivalence
relations for use in Internet inter-domain routing.
The above is a fancy way of saying that documentation like
https://www.us.ntt.net/support/policy/routing.cfm is not anywhere close
to being programmatically interpretable, and perhaps we can do better.
In a way RPSL was an attempt to address the problem space, but now in
2019/2020 the solution space maybe has expanded, and we now have a
better understanding of what worked well in RPSL and what didn't.
I'd like to add: September 2020 - "Devise a BGP Community Description System"
Kind regards,
Job
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
