Re: [Sidrops] I-D Action: draft-ietf-sidrops-validating-bgp-speaker-00.txt

Hi,

I think a much safer mode of operation for BGP speakers is to reject
invalid announcements, rather than "tag with extended bgp community &
propagate".

Merely tagging announcements with some community and hoping the remote
peer will take some action on the community seems a bit silly...

I'd suggest to remove "Simple tagging" and "Prioritizing and Tagging"
from Section 3. And remove "2 - Lookup result = invalid" from Table 1 in
Section 4.

Kind regards,

Job

On Wed, Feb 07, 2018 at 07:37:24PM +0100, Aris Lambrianidis wrote:
> Greetings everyone,
> 
> Might we again solicit feedback on the draft? It is an evolution of
> draft-ietf-sidr-route-server-rpki-light, with the
> following *key* changes:
> 
> 1. It now discusses BGP speakers instead of IXP route servers
> 
> Reason: The draft can be applicable to any network operator instead of
> just IXPs.
> 
> 2. It introduces a new EBGP Prefix Origin Validation Extended Community
> (instead of re-using the         
> BGP Prefix Origin Validation State Extended Community as described in
> RFC8097).
> 
> Reason: This new community includes the AS number of the validating BGP
> speaker in its Global Administrator
> field, a crucial piece of information for troubleshooting.
> 
> Many thanks to the valuable feedback so far on and off this list for
> bringing the draft to its current state.
> 
> Kind regards,
> Aris
> 
> internet-drafts@ietf.org wrote:
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> > This draft is a work item of the SIDR Operations WG of the IETF.
> >
> >         Title           : Signaling Prefix Origin Validation Results from an RPKI Origin Validating BGP Speaker to BGP Peers
> >         Authors         : Thomas King
> >                           Christoph
> >                           Daniel Kopp
> >                           Aristidis Lambrianidis
> >                           Arnaud Fenioux
> > 	Filename        : draft-ietf-sidrops-validating-bgp-speaker-00.txt
> > 	Pages           : 9
> > 	Date            : 2018-02-01
> >
> > Abstract:
> >    This document defines a new BGP transitive extended community, as
> >    well as its usage, to signal prefix origin validation results from an
> >    RPKI Origin validating BGP speaker to other BGP peers.  Upon
> >    reception of prefix origin validation results, peers can use this
> >    information in their local routing decision process.
> >
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-sidrops-validating-bgp-speaker/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-sidrops-validating-bgp-speaker-00
> > https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-validating-bgp-speaker-00
> >
> >
> > Please note that it may take a couple of minutes from the time of submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > Sidrops mailing list
> > Sidrops@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidrops
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops