Re: [Idr] WG adoption for draft-haas-flowspec-capability-bits

Agreed.   +1

On Thu, Apr 8, 2021 at 8:36 PM Jakob Heitz (jheitz) <jheitz=
40cisco.com@dmarc.ietf.org> wrote:

> This makes sense.
>
> You should probably modify or delete section 4.
>
> A BGP speaker has basically 2 jobs. 1. to propagate a received route to
> other neighbors and 2. to act on the route (install the filter). A BGP
> capability advertised by a router is only known to the neighbor of that
> router, not necessarily to the originator of a route. Therefore, BGP
> capabilities are an insufficient means to discover the capabilities of all
> routers in a network. All that BGP capabilities can really do is to prevent
> a neighbor from tearing down a BGP session when you send it a route it does
> not recognize (by enabling you to not send the unrecognized route in the
> first place). To find out how many routers in your network will install a
> given flowspec requires more capable network management techniques.
>
>
> Regards,
> Jakob.
>
> -----Original Message-----
> From: Idr <idr-bounces@ietf.org> On Behalf Of Jeffrey Haas
> Sent: Thursday, April 8, 2021 3:43 AM
> To: Robert Raszuk <robert@raszuk.net>
> Cc: idr@ietf. org <idr@ietf.org>; Susan Hares <shares@ndzh.com>
> Subject: Re: [Idr] WG adoption for draft-haas-flowspec-capability-bits -
> 3/30 to 4/13
>
> On Thu, Apr 08, 2021 at 09:36:01AM +0200, Robert Raszuk wrote:
> > Hi Jeff,
> >
> > Looks like we have converged.
> >
> > Would it be possible to include your below sentence explicitly/verbatim
> in
> > the draft:
> >
> > "It is also an option for an implementation that understands a new
> component
> > that doesn't want to implement it in forwarding to advertise support for
> > that component and propagate it even if it doesn't locally use it. "
> >
> > With that I am happy as that was my point. And of course anyone is free
> to
> > do what they like (both implementation and operation wise). The draft/rfc
> > will only provide options.
>
> I'm happy to add some text to this effect.
>
> -- Jeff
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*

*M 301 502-1347*

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