Re: [Idr] WG adoption for draft-haas-flowspec-capability-bits - 3/30 to 4/13

[Robert Raszuk <[e-mail]>]

Hi Jeff,

I think you're mixing some of the points together.
>

I think actually I am not the one who is mixing it here.

Not a single BGP flowspec implementation implemented the "opaque" property
> in RFC 5575.  Not one.  And it was the strong motivation to remove that
> text
> in RFC 8955.


This is the crux.

The way I read the current draft is that you are putting an equal sign into
supported filtering and advertised capability.

That is not what I would do.

While subject to separate discussion perhaps it is ok to expect BGP to
parse NLRI and validate the types it carries. I am fine with that. But this
is a control plane. This has nothing to do with platform capabilities to
actually perform filtering on such types. That is also an easy software
upgrade across the network.

Even if platform does not support given filtering the bgp speaker will
accept the update and advertise it further. Mission accomplished. Flowspec
is not broken and has a chance to work downstream.

Contrary to the above what's being cooked here is severely breaking the
flowspec propagation chain to hardware capabilities (as most of the
filtering will likely occur in hardware at decent rates).

Now I wonder what is your take on this point ?

Thx,
Robert.