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

[ERCIN TORUN <[e-mail]>]

Hello Jeffrey,

On a router a filter on all interfaces or on one interface consume the same amount of TCAM* that's why in the first place i think that a targeting mechanism would be useful.  An interface set is definitely useful also.

I know your draft, even i'm in touch with my vendor if (when) it will be applied to their software. I think https://tools.ietf.org/html/draft-ietf-idr-flowspec-interfaceset-04  and https://tools.ietf.org/html/draft-dong-idr-node-target-ext-comm-00   together solves "targeted advertisement with an interface set" problem.

* https://community.cisco.com/t5/xr-os-and-platforms/bgp-flowspec-scale-and-performance/td-p/2749018

Regards
Erçin TORUN
-----Original Message-----
From: Jeffrey Haas <[e-mail]>
Sent: Thursday, May 16, 2019 12:12 AM
To: ERCIN TORUN <[e-mail]>
Cc: [e-mail]
Subject: Re: [Idr] update proposal to draft-ietf-idr-rfc5575bis-14

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


[http://www.turkcell.com.tr/downloads/bireysel/img/Tcelldis.gif] <http://turkcell.li/iyaani>

Bu elektronik posta ve onunla iletilen butun dosyalar sadece gondericisi tarafindan almasi amaclanan yetkili gercek ya da tuzel kisinin kullanimi icindir. Eger soz konusu yetkili alici degilseniz bu elektronik postanin icerigini aciklamaniz, kopyalamaniz, yonlendirmeniz ve kullanmaniz kesinlikle yasaktir ve bu elektronik postayi derhal silmeniz gerekmektedir.

TURKCELL bu mesajin icerdigi bilgilerin doğruluğu veya eksiksiz oldugu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin ne sekilde olursa olsun iceriginden, iletilmesinden, alinmasindan ve saklanmasindan sorumlu degildir. Bu mesajdaki gorusler yalnizca gonderen kisiye aittir ve TURKCELLin goruslerini yansitmayabilir

Bu e-posta bilinen butun bilgisayar viruslerine karsi taranmistir.

________________________________

This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited, and the e-mail should immediately be deleted.

TURKCELL makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. The opinions expressed in this message belong to sender alone and may not necessarily reflect the opinions of TURKCELL.

This e-mail has been scanned for all known computer viruses.