Re: [Idr] I-D Action: draft-ietf-idr-flowspec-v2-02.txt
Nat Kao <pyxislx@gmail.com> Mon, 22 May 2023 16:00 UTC
Return-Path: <pyxislx@gmail.com>
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 A2CB8C15155E for <idr@ietfa.amsl.com>; Mon, 22 May 2023 09:00:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 N53OyKcHMjHo for <idr@ietfa.amsl.com>; Mon, 22 May 2023 09:00:58 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 147BBC15155B for <idr@ietf.org>; Mon, 22 May 2023 09:00:58 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-510c734fa2dso7773158a12.0 for <idr@ietf.org>; Mon, 22 May 2023 09:00:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684771256; x=1687363256; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=JPsHa/QM2ANa+p9rcNmvCD/eLtlhxdAJ65gkH92KWOQ=; b=gOeqqE9a6kzr7H1ZoyPrQ6CBMoBWxW6JMyEYqL57CzYwAmt5Hxm1LeJRJK8AJjuaUo gOM1W+k0NkR/9vCXGKII+KpsA5u+J9gKLNuzsf9Qlkmix4HLLs02V6BC18gXHhNV+XHC LRpEOhCRDhPka+UFnPpni9zLpnfOXe4i4UXg35XJKzyvC8W8b1Yvxe4JWbRRVV/6EMK9 ZQ3wrbmPqEctebBPhNzpuVJbmXmb3fwQAq7A4dbNkijC+zbKsoEP/V8bnAVgJfmAqLgs Pva85x+srmnWEFEGA9qk6SaBr9r8q1yVXFBtDJyzKYlhOpTddnKP++p/DE0sip85vW06 /CVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684771256; x=1687363256; h=content-transfer-encoding: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=JPsHa/QM2ANa+p9rcNmvCD/eLtlhxdAJ65gkH92KWOQ=; b=cE73PQj0LrMoe0zN+cGqgbqVCphU83DQZ5mwbbKnmgnujKq6e3lar74PfxZ26Pae8h YwvhDCVs0Tyl6uQSPGknTHyQ0H/O7wdjFetbQ39aGoLPqKCw4RrEUtbwiP+DFhnLP20z acPpmUYPEC0BvNoSeLD9zEozzxDNSDTOEn2X63BqeJOj3GjfIF5Pjx3vzd4YjI+bAWJQ sK2sKyH2E6P49jZ7YV3j2O48NAZXIHu1DCIKZdHbZQi2nekttY2+S5hDf4h5xYFMFHFM jLXrrt9/EhlbTsmPihFsFsQb7Bk9h5E5hSv7hbmHTThnrm5N7t0TyXMFNdS25eBlzNcy avyw==
X-Gm-Message-State: AC+VfDzKxYdZoOlVBBPPmsxawD/6dOGdvK2fykuzj6sYsUCQa6DGAi0M bIpYuwnhmjHb/gT6X2Fi6aQX8ObLZTIqXYH0ksi4abEw
X-Google-Smtp-Source: ACHHUZ5TLueu2tbPJLYzUxeVwpjzdFd0xS7jCe52+s/i6Uz+28k7wHFKKUvraBcui5O8cNlOVaTl8LVlEK2kKD2NCwE=
X-Received: by 2002:aa7:da06:0:b0:50d:a804:423 with SMTP id r6-20020aa7da06000000b0050da8040423mr11154545eds.10.1684771256436; Mon, 22 May 2023 09:00:56 -0700 (PDT)
MIME-Version: 1.0
References: <168467537946.25247.13297620515379889447@ietfa.amsl.com>
In-Reply-To: <168467537946.25247.13297620515379889447@ietfa.amsl.com>
From: Nat Kao <pyxislx@gmail.com>
Date: Tue, 23 May 2023 00:00:20 +0800
Message-ID: <CAKEJeo5mGj6CCkxHBnhppjo2sM6NMZ3sh+AUsFzg76gAgLZ7AA@mail.gmail.com>
To: idr@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/qFZY5g2zV6cUuE9akgN8aa7UwZY>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-flowspec-v2-02.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, 22 May 2023 16:00:58 -0000
Hi, All. While carefully evaluating the use cases for FSv2, I have a few questions regarding this version: 1. In section 3.1.1 & 3.1.2, the terms SubTLVs(Sub-subTLVs actually) and components are used interchangeably, should we unify them? 2. Can SubTLV/Component type 1(IP Destination Prefix) or 2(IP Source Prefix) appear multiple times in the same IP/IPv6 traffic rule? If that's not the case, maybe we can add a new SubTLV/Component for matching multiple prefixes? I'm trying to find a solution to disseminating matching rules with multiple prefixes(i.e. a prefix-list) using either FSv1 or FSv2. The underlying hardware support is already there.(see Note 1) With current components of FSv1, we have to expand prefix-list matching rules by each prefix in the list. 3. There's an extra "Reference: " in section 3.1.17. Since EXP field had been rename to Traffic Class field in RFC5462, maybe we should also update this section accordingly? Note 1: AFAIK Juniper JUNOS & Nokia SR-OS have built-in support to match against multiple prefixes in the same rule for a long time. We also have this functionality in Arista EOS(as traffic-policies) & Cisco IOS-XR(as hybrid ACLs) for years. Thanks! Nat On Sun, May 21, 2023 at 9:23 PM <internet-drafts@ietf.org> wrote: > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. This Internet-Draft is a work item of the Inter-Domain Routing > (IDR) WG of the IETF. > > Title : BGP Flow Specification Version 2 > Authors : Susan Hares > Donald Eastlake > Chaitanya Yadlapalli > Sven Maduschke > Filename : draft-ietf-idr-flowspec-v2-02.txt > Pages : 69 > Date : 2023-05-21 > > Abstract: > BGP flow specification version 1 (FSv1), defined in RFC 8955, RFC > 8956, and RFC 9117 describes the distribution of traffic filter > policy (traffic filters and actions) distributed via BGP. Multiple > applications have used BGP FSv1 to distribute traffic filter policy. > These applications include the following: mitigation of denial of > service (DoS), enabling traffic filtering in BGP/MPLS VPNs, > centralized traffic control of router firewall functions, and SFC > traffic insertion. > > During the deployment of BGP FSv1 a number of issues were detected > due to lack of consistent TLV encoding for rules for flow > specifications, lack of user ordering of filter rules and/or actions, > and lack of clear definition of interaction with BGP peers not > supporting FSv1. Version 2 of the BGP flow specification (FSv2) > protocol addresses these features. In order to provide a clear > demarcation between FSv1 and FSv2, a different NLRI encapsulates > FSv2. > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-v2/ > > There is also an HTML version available at: > https://www.ietf.org/archive/id/draft-ietf-idr-flowspec-v2-02.html > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-flowspec-v2-02 > > Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts > > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr
- [Idr] I-D Action: draft-ietf-idr-flowspec-v2-02.t… internet-drafts
- Re: [Idr] I-D Action: draft-ietf-idr-flowspec-v2-… Nat Kao