Re: [Sidrops] WGLC - draft-ietf-sidrops-validating-bgp-speaker - ENDS 09/07/2018 - Sept 7th 2018

[Job Snijders <[e-mail]>]

On Tue, Sep 04, 2018 at 11:07:29PM -0700, Randy Bush wrote:
> >   1) "route origin validation is not as hard to see deploying today"
> 
> see draft-ietf-sidrops-ov-clarify-05.txt.  essentially vendors'
> implementations are funky and so it is hard for me to do it myself.
> 
> and it is not only ov-clarify.  test whether your fave implementation
> re-evaluates a bgp prefix when a roa change comes in over rpki-rtr.  the
> messy story goes on.

the IXP route server software (that is used in practise) is provided by
a single vendor. Perhaps this single vendor got it right, but from a
conceptual point of view they wouldn't be exempted and may still need
'ov-clarify'.

> >   2) "just introducing an IXP lan/RS that simply implements the validation
> > and takes action(s) is the right course of action"
> 
> s/the right course/one right course/
> 
> what is nice is that the ixp-provided filter does not have the same
> problems as above.

because of the single vendor? or because of some other reason? how
exactly is their bgp more magic than others?

> so it is a leapfrog while hardware vendors catch up.  it is driving
> origin validation deployment.

except that we cannot point at a single instance where the approach has
driven origin validation. on the other side, i can point at many
instances where IXP route servers have negatively impacted businesses
because they propagated/amplified incorrect routing information.

What /actually/ drives origin validation is customers asking their
providers (be it ISPs or IXPs) to implement origin validation. This
approach has already been succesfully tested at FranceIX, AMS-IX, and
later this year will be yield positive results at DE-CIX and LINX.

I have to ask, (given the author's affiliations) - if this draft is
published as an RFC, will you turn back the clock and start propagating
invalid route announcements to your customers (marked with an extended
community)? 

Kind regards,

Job