Re: [Idr] FW: New Version Notification for draft-wu-idr-flowspec-dip-community-filter-00.txt
Robert Raszuk <robert@raszuk.net> Mon, 04 March 2024 20:18 UTC
Return-Path: <robert@raszuk.net>
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 0267AC157938 for <idr@ietfa.amsl.com>; Mon, 4 Mar 2024 12:18:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hf4Tk2FA4-uQ for <idr@ietfa.amsl.com>; Mon, 4 Mar 2024 12:18:02 -0800 (PST)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9602EC180B76 for <idr@ietf.org>; Mon, 4 Mar 2024 12:17:53 -0800 (PST)
Received: by mail-ed1-x533.google.com with SMTP id 4fb4d7f45d1cf-56682b85220so7886928a12.1 for <idr@ietf.org>; Mon, 04 Mar 2024 12:17:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1709583472; x=1710188272; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=G+xhy+kv1GfFJCyIS+jXOEkeUUQdgLxIabl8vJA+lmE=; b=RieCDUMKiLcnK58xIyNlCBUOw8hdI0gLx4Ces73gDaDjLzXh8kFSBEFmJebwfOXK48 PdvqrrQBBS45iCwnKmRfOl+g0ZB0lES/FTJIfoUDTpFQMsjt+R9JR5aOvVerbnB/W3aj 5fe7pCuYvk2VblytrwglUM0MvS8lN4cVbB2cK5mn7ReUS6zvB/cMQgwVKOT8nLCz9Qpo Xv7fW/3B6hgfHoLNRELimsikWhXW0E0/csL3bSaRxBIsXJ1LBFkFGr5rInpj6Xn6XpEI 0dnMzA6PodlNsKsDvBlLNkAnPjpinjSnO5zlvAjwCqIDPboq6GkBEg99DbS8gY4VzdgM e0xw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709583472; x=1710188272; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=G+xhy+kv1GfFJCyIS+jXOEkeUUQdgLxIabl8vJA+lmE=; b=ixcf/K1qPa8zU4PlNMCiRX/Lj2bhQ0L1lOkrNOfYBwqfPfTBEsUcyIN/fkW+tJda9b Ua0U4VDAoBdtvWDdXyPjsLjrvEq2h+zlsgu4z+ftGdxcruuBKgoOJ4rb2kjhIYETqCNC UVqhO5QLL59VqY0sgz8gQ3m+Zw3sydSfKsjV3ces3Uennm5Xem4QYlZvDPg6wCYHkozZ r2gENtV7v9X7Y4OiTPvgjvztBf6sIzzfEyD2IvQ3x801RXnikMb+eTTAeB9exj69aDUQ jjyi0IO6iOxYm36zzguGir8UY11GzKDvbPNff/S1ngmB690SvFdir7PxBafptWRo9a4L eF8A==
X-Gm-Message-State: AOJu0Yw1dLBehOAQNdpdgfacdslS25QkYCR3vxPMVuRiiHiTE31C2/Wz 4qn1lUn5mlyUhOz95xBkhBiq5m+HY2F4q+PFChZVAYEUuYq43AjuBjEqHY6Z2v25j+Oj/p44rLT 4TH09lA3SmEmFJIBXKmLUk4qfTR1QJ+Ti0jlAwcLY0jSYVB8A
X-Google-Smtp-Source: AGHT+IFvUpr1k3pg/MY5naiKFXTxy58KF1BoTjgbUYGtBCiWCsJdGC0oFvaJFVr93OREelWVv8T5/GeJ6GYCSA6n0DQ=
X-Received: by 2002:a50:cb88:0:b0:565:7b61:4c82 with SMTP id k8-20020a50cb88000000b005657b614c82mr7280084edi.5.1709583471962; Mon, 04 Mar 2024 12:17:51 -0800 (PST)
MIME-Version: 1.0
References: <1d8a9005350548acae681108370cb22d@huawei.com> <CAOj+MMGZ7jSZPYSPj=dhw7PkkjjKdGH=cT4DqXLdbdeGLQ+oEg@mail.gmail.com>
In-Reply-To: <CAOj+MMGZ7jSZPYSPj=dhw7PkkjjKdGH=cT4DqXLdbdeGLQ+oEg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 04 Mar 2024 21:17:41 +0100
Message-ID: <CAOj+MMF6-CkxMhQ23a91dukA7s3UQH5cyeXmbaA9O21Ghw--1w@mail.gmail.com>
To: wutianhao <wutianhao10=40huawei.com@dmarc.ietf.org>
Cc: "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008f81300612db6b69"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/vvQGdMdv5pHScBMyH59FLVx6RVM>
Subject: Re: [Idr] FW: New Version Notification for draft-wu-idr-flowspec-dip-community-filter-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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, 04 Mar 2024 20:18:08 -0000
Btw same comment applies also to draft-wang-idr-flowspec-dip-origin-as-filter. Thx, R. On Mon, Mar 4, 2024 at 9:11 PM Robert Raszuk <robert@raszuk.net> wrote: > Hi, > > I am not sure if this is targeting FlowSpec v2 ... but I would like to > observe that component types as defined in RFC8955 are about data plane. > > You are proposing an addition of a control plane entity - namely BGP > Community Attribute. > > I understand that you want to recursively result local installation into > the data plane all destinations which are advertised in BGP with such > community, but this is a significant departure from the definition of > FlowSpec v1. > > It is about signalling dynamically a BGP policy which FlowSpec v1 is not > doing. With that being said I recommend that if authors of FlowSpec v2 are > still working on it allowing it to carry BGP policy - then this would be > the right place to add the proposed encoding into. > > As currently defined - stand alone extension - it does not seems to even > fit https://www.iana.org/assignments/flow-spec/flow-spec.xhtml. > > Kind regards, > Robert > > > On Mon, Mar 4, 2024 at 11:55 AM wutianhao <wutianhao10= > 40huawei.com@dmarc.ietf.org> wrote: > >> Dear all, >> >> We've submitted a new draft: draft-wu-idr-flowspec-dip-community-filter. >> >> This draft specifies a new BGP Flowspec component type to support >> community-level filtering. Flowspec rules can be reduced by using the >> method defining in this draft. It saves a lot of entry spaces on the >> control plane and forwarding plane, and it would greatly simplify the >> operation of the control plane, and the more destination prefixes with the >> same community has, the more obvious the benefit. >> >> Review and comments are welcome. >> >> Best regards, >> Tianhao >> >> -----Original Message----- >> From: internet-drafts@ietf.org <internet-drafts@ietf.org> >> Sent: 2024年2月29日 17:26 >> To: Wanghaibo (Rainsword) <rainsword.wang@huawei.com>; Gejun (Jack, BGP) >> <jack.gejun@huawei.com>; wutianhao <wutianhao10@huawei.com>; >> Dingxiangfeng <dingxiangfeng@huawei.com> >> Subject: New Version Notification for >> draft-wu-idr-flowspec-dip-community-filter-00.txt >> >> A new version of Internet-Draft >> draft-wu-idr-flowspec-dip-community-filter-00.txt has been successfully >> submitted by Tianhao Wu and posted to the IETF repository. >> >> Name: draft-wu-idr-flowspec-dip-community-filter >> Revision: 00 >> Title: Destination-IP-Community Filter for BGP Flow Specification >> Date: 2024-02-28 >> Group: Individual Submission >> Pages: 7 >> URL: >> https://www.ietf.org/archive/id/draft-wu-idr-flowspec-dip-community-filter-00.txt >> Status: >> https://datatracker.ietf.org/doc/draft-wu-idr-flowspec-dip-community-filter/ >> HTMLized: >> https://datatracker.ietf.org/doc/html/draft-wu-idr-flowspec-dip-community-filter >> >> >> Abstract: >> >> BGP Flowspec mechanism (BGP-FS) propagates both traffic Flow >> Specifications and Traffic Filtering Actions by making use of the BGP >> NLRI and the BGP Extended Community encoding formats. This document >> specifies a new BGP-FS component type to support community-level >> filtering. The match field is the community of the destination IP >> address that is encoded in the Flowspec NLRI. This function is >> applied in a single administrative domain. >> >> >> >> The IETF Secretariat >> >> >> _______________________________________________ >> Idr mailing list >> Idr@ietf.org >> https://www.ietf.org/mailman/listinfo/idr >> >
- [Idr] FW: New Version Notification for draft-wu-i… wutianhao
- Re: [Idr] FW: New Version Notification for draft-… Robert Raszuk
- Re: [Idr] FW: New Version Notification for draft-… Robert Raszuk
- [Idr] 答复: FW: New Version Notification for draft-… wutianhao
- Re: [Idr] 答复: FW: New Version Notification for dr… Robert Raszuk
- Re: [Idr] FW: New Version Notification for draft-… Jeff Haas
- Re: [Idr] FW: New Version Notification for draft-… Robert Raszuk
- [Idr] Feedback from mike during IETF 119 (was Re:… Ketan Talaulikar
- Re: [Idr] Feedback from mike during IETF 119 (was… wutianhao
- Re: [Idr] Feedback from mike during IETF 119 (was… Ketan Talaulikar
- Re: [Idr] Feedback from mike during IETF 119 (was… Robert Raszuk