IETF Logo Mail Archive

Re: [Idr] Destination-IP-Origin-AS Filter for BGP Flow Specification

Jeffrey Haas <jhaas@pfrc.org> Mon, 11 November 2019 08:20 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 D735612085D; Mon, 11 Nov 2019 00:20:16 -0800 (PST)
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 Ei-oGU-R7etV; Mon, 11 Nov 2019 00:20:15 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 8FA4B120855; Mon, 11 Nov 2019 00:20:15 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 460BB1E2F5; Mon, 11 Nov 2019 03:24:03 -0500 (EST)
Date: Mon, 11 Nov 2019 03:24:03 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Wanghaibo (Rainsword)" <rainsword.wang@huawei.com>
Cc: "idr-chairs@ietf.org" <idr-chairs@ietf.org>, Robert Raszuk <robert@raszuk.net>, "wangaj3@chinatelecom.cn" <wangaj3@chinatelecom.cn>, Zhuangshunwan <zhuangshunwan@huawei.com>, "idr@ietf. org" <idr@ietf.org>
Message-ID: <20191111082403.GB32420@pfrc.org>
References: <CAOj+MMHLFxe94chd1woN74KeJy3UQa2mfSjXjrE7uudPBDw6KQ@mail.gmail.com> <1E61161D6E31D849BEA887261DB609348C9A97E0@nkgeml514-mbx.china.huawei.com> <20191107173733.GR3277@pfrc.org> <1E61161D6E31D849BEA887261DB609348C9AA9E5@nkgeml514-mbx.china.huawei.com> <092F40A2-3FD5-4712-8147-D71DAAA86A6D@pfrc.org> <1E61161D6E31D849BEA887261DB609348C9BF7D5@nkgeml514-mbx.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1E61161D6E31D849BEA887261DB609348C9BF7D5@nkgeml514-mbx.china.huawei.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/McYpJQ2RBPlOgmOVLxSfOB853CI>
Subject: Re: [Idr] Destination-IP-Origin-AS Filter for BGP Flow Specification
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: Mon, 11 Nov 2019 08:20:17 -0000

On Mon, Nov 11, 2019 at 07:21:17AM +0000, Wanghaibo (Rainsword) wrote:
> Hi Jeffrey,
> 
> 	Thanks for your suggestion.
> 
> 	Flowspec is intended to match only the message fields. 
> 	Our solution here is an enhancement to Flowspec, which can effectively reduce the space of the flowspec.
> 
> 	The rules here are also used in conjunction with the existing Flowspec rules, so using the new SAFI to describe it is not appropriate.
> 	We can increase OPEN capability negotiation to enable when this feature is supported.

BGP NLRI are transitive across a network.  If you want a feature that varies
on NLRI parsing or processing behavior, it needs to be uniformly supported
across all BGP speakers that receive it.  This cannot be a capability.  That
behavior is covered by afi/safis.

-- Jeff

v2.23.0 | Report a Bug | By Email