Re: [Idr] update proposal to draft-ietf-idr-rfc5575bis-14

[Jeffrey Haas <[e-mail]>]

Erçin,

On Thu, May 09, 2019 at 12:02:42PM +0000, ERCIN TORUN wrote:
> Hello All,
> 
> My name is Ercin TORUN<https://tr.linkedin.com/in/ercintorun> and I’m working in Turkcell Turkey (35M-mobile/2M-fixed customer, +digital services) as an IP/MPLS Network Planning Engineer.  I would like to propose an update to draft-ietf-idr-rfc5575bis-14<https://tools.ietf.org/html/draft-ietf-idr-rfc5575bis-14>.
> 
> By default all flowspec entries (filters..) are applied to all routers, and unnecessary application of many filters can easily owerwhelm the capacity of routers resources (e.g. TCAM). We are pushing layer3 to the edges with solutions like seamless-mpls or leaf-spine next-generation DC topologies which widens the layer3 domain easily over thousands of devices. It is best to filter “dirty” traffic where it first enters a network. There are ways to accept BGP announcements only on the targeted router, like defining a community for each router and configuring policies, but an automated way would be much more easier and less error-prone. Our idea is using a route-taget to match with BGP Identifier so that only the targeted router might accept the announcement.

You may find the following draft (expired - sorry... we need to fix it) of
interest:

https://tools.ietf.org/html/draft-ietf-idr-flowspec-interfaceset-04

-- Jeff