Re: [Idr] [[e-mail]: I-D Action: draft-haas-flowspec-capability-bits-02.txt]

["Dongjie (Jimmy)" <[e-mail]>]

Hi Jeff, all, 

I've read the recent discussion and the updated version of this draft, here are some thoughts and comments: 

I fully agree that incremental deployment of new flowspec components is important, and it does not need to wait for Flowspec 2.0.

Regarding a BGP flowspec component, there could be three different capabilities: 

1.	The capability of parsing and implementing the component as a filter

2.	The capability of parsing and propagating the component, but not for local use

3.	The capability of propagating the component further even it is not parsed

The first two capabilities are discussed in this thread and the updated draft, and to me it makes sense to distinguish these two capabilities. 

As sometimes a flowspec rule only needs to be installed on a subset of nodes, a node which is not required to install it or even support it may be on the propagation path of the flowspec rule. If there is some mechanism to limit the propagation scope or indicate the target nodes of the flowspec, the third capability may further help the incremental deployment of new flowspec components.

Then back to the encoding of the flowspec capability bits, if we want to consider the case that a node can propagate unknown flowspec components, one reserved bit in the bit-string may be used to indicate such capability, other mechanism is also possible. 

Thoughts?

Best regards,
Jie

> -----Original Message-----
> From: Idr [mailto:[e-mail]] On Behalf Of Jeffrey Haas
> Sent: Saturday, April 10, 2021 4:11 AM
> To: [e-mail]
> Subject: [Idr] [[e-mail]: I-D Action:
> draft-haas-flowspec-capability-bits-02.txt]
> 
> This version attempts to address the review comments received to date.
> 
> -- Jeff
> 
> ----- Forwarded message from [e-mail] -----
> 
> Date: Fri, 09 Apr 2021 12:45:48 -0700
> From: [e-mail]
> To: [e-mail]
> Subject: I-D Action: draft-haas-flowspec-capability-bits-02.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : BGP Flowspec Capability Bits
>         Author          : Jeffrey Haas
> 	Filename        : draft-haas-flowspec-capability-bits-02.txt
> 	Pages           : 8
> 	Date            : 2021-04-09
> 
> Abstract:
>    BGP Flowspec (RFC 8955) provides the ability to filter traffic using
>    various matching components.  The NLRI format currently defined does
>    not permit incremental deployment of new BGP Flowspec components.
>    This draft defines a new BGP Capability to permit incremental
>    deployment of such new Flowspec component types.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-haas-flowspec-capability-bits/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-haas-flowspec-capability-bits-02
> https://datatracker.ietf.org/doc/html/draft-haas-flowspec-capability-bits-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-haas-flowspec-capability-bits-02
> 
> 
> 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/
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> ----- End forwarded message -----
> 
> _______________________________________________
> Idr mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/idr