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

Jeffrey Haas <jhaas@pfrc.org> Fri, 09 April 2021 14:57 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49D323A23ED for <idr@ietfa.amsl.com>; Fri, 9 Apr 2021 07:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lmywpcevePAg for <idr@ietfa.amsl.com>; Fri, 9 Apr 2021 07:57:52 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id BBF3C3A23E7 for <idr@ietf.org>; Fri, 9 Apr 2021 07:57:52 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 622E61E459; Fri, 9 Apr 2021 11:20:20 -0400 (EDT)
Date: Fri, 9 Apr 2021 11:20:20 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Aijun Wang <wangaijun@tsinghua.org.cn>
Cc: "'Aseem Choudhary (asechoud)'" <asechoud=40cisco.com@dmarc.ietf.org>, "'idr@ietf. org'" <idr@ietf.org>
Message-ID: <20210409152020.GB29502@pfrc.org>
References: <CAOj+MMFaJGk7-hif7Qm7Hp1=iThn5gyvmpp+UYY_q6PJEAVAPw@mail.gmail.com> <20210407223222.GD7355@pfrc.org> <CAOj+MMEmpMA9YOSU304mQed6o5gm1eUKbYNwyt88M5_E-7=woA@mail.gmail.com> <20210408004720.GF7355@pfrc.org> <CAOj+MMGukAL-fNpWh1yu=AHqnONPq9mCqqFGjK5pspFkHfn0UA@mail.gmail.com> <20210408104259.GH7355@pfrc.org> <BYAPR11MB3207F949DD2C8ECA0465CD1EC0739@BYAPR11MB3207.namprd11.prod.outlook.com> <CABNhwV1fxAXHjy7=bc5QGWi0Jt89330U93tp8Hs0wvj3wdy6og@mail.gmail.com> <8B262FE8-EEFB-44E4-8AD0-2EBD3348DEF2@cisco.com> <005b01d72cf3$4f39c4a0$edad4de0$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <005b01d72cf3$4f39c4a0$edad4de0$@tsinghua.org.cn>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/btjMTWpkYHnQ8qV6OVNBSPWQ1TA>
Subject: Re: [Idr] WG adoption for draft-haas-flowspec-capability-bits - 3/30 to 4/13
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Apr 2021 14:57:55 -0000

Aijun,

On Fri, Apr 09, 2021 at 11:49:14AM +0800, Aijun Wang wrote:
> And, how to express the IPv4 filter(parsing) capabilities and IPv6 filter(parsing) capabilities individually?

Please see the response to Aseem.

> Based on the discussion, how about change the capabilities name from “BGP Flowspec Capability Bits” to “BGP Flowspec Parsing Capability Bits”?

That might be reasonable.  Let's see how the totality of the discussion
goes.

> Then the BGP neighbor will not send the un-recognized component type. For the recognized component type, the routers within the domain will propagate the flowspec NLRI regardless of their actions on these rules.

Local filtering already has RFC impact to propagation of the route.  From
Section 4.2 of RFC 8955:

: All combinations of components within a single Flow Specification are
: allowed. However, some combinations cannot match any packets (e.g., "ICMP
: Type AND Port" will never match any packets) and thus SHOULD NOT be
: propagated by BGP.




-- Jeff