Re: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)

Robert Raszuk <robert@raszuk.net> Wed, 31 August 2022 14:16 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 A409BC1524C1 for <idr@ietfa.amsl.com>; Wed, 31 Aug 2022 07:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, 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=ham 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 NfYae6eKF7nq for <idr@ietfa.amsl.com>; Wed, 31 Aug 2022 07:16:54 -0700 (PDT)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (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 77F63C1524B0 for <idr@ietf.org>; Wed, 31 Aug 2022 07:16:54 -0700 (PDT)
Received: by mail-ed1-x531.google.com with SMTP id r4so18571546edi.8 for <idr@ietf.org>; Wed, 31 Aug 2022 07:16:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=p8WmWewvp9lwanzkF8T+jhAnVd3xGaUoDJcnYR4oBrU=; b=PxLZXTk63Szxyt+tTJKRRC7w2w88q28XAHqo1Opd1A9AvQ0sqOdaV25uICtXGVt7hV iP8W+Ft81EuN9hIXQ0NAohaSLSJsBLIWWKzJ28R3lpl6q/BFoGEeHNVggc1LcTcpoo2h vCOH5TCzMBgLNkRtsH37nT0IjYuizmdBmVLq9eUeEIRko+NZJdv6NBkQ3cB7HPKFicMj VVZ5ot2+bc35EVfJfzFi05Tc7kRkPItf9K6TJz5QmshFWy/N0f8xOL2OqjDa/JiSk9Y5 vtygkLaIH83Npz+pBnrz8fYb8/HJ/+d+GJcvzc2aJLHtX/uS6+PM8LiANONB9tD7it58 R0tg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=p8WmWewvp9lwanzkF8T+jhAnVd3xGaUoDJcnYR4oBrU=; b=JSTTOsXc6vNm97sfqsGIjxfjpH+odJWr5XpAUAsep7GMKtLU5z+rcbIBatyzhdZxK3 8uShq3vDNVkPyQJGSEj/DxE6fu8pnuYZl3kjeeQJJ9zGEddJHfG050o2kJS2sqTcLver PSzNSopU+tzn/oChijK9nfyi8bEiYNd/WCSpQG+hPvf7VGnNRVjx5QIpmj/5m7oLsX+E vHE85lkaHHvW8aIWjKs1BvZ0qrb8gsZZIu4ETNb8f/YZPcOKOuIHhtw4iizOUQZtztSy 4Ar8xvSXcu7+n5/dq5ub4d5LkbEdtG1pdCAp+Q0TypDw7azdKl2hxKYjmXykFn1BeJ6V 1l4g==
X-Gm-Message-State: ACgBeo0JQ5muf4JFcIqPraAaRn++FehRZxYqGyV9aXmOewDUNhtomOIh ONnvXPzM3pQxc4Yb777V/a13KDuoBiXfuONWMwuAMQ==
X-Google-Smtp-Source: AA6agR59EGr7YxQeWyrDOFF1m6KJU/t+tbygF8z6EYNpXrZuakU6HIyV6he4M4CokAWg2sPOtj73EEUiNOkrDAk455g=
X-Received: by 2002:a05:6402:348f:b0:448:6005:68af with SMTP id v15-20020a056402348f00b00448600568afmr13647364edc.184.1661955412207; Wed, 31 Aug 2022 07:16:52 -0700 (PDT)
MIME-Version: 1.0
References: <20220831072731.5F2309000AF@hmail-m121149.qiye.163.com> <E413E79B-A819-48AE-9014-BDCF77ADA2EA@tsinghua.org.cn> <CAOj+MMHsNnnvhh=WZP6cw4LZY5PTy727uy3jsHqgnXfbN1R-uA@mail.gmail.com> <CAEfhRrwUYOUmZuaPhdF8m92iedRYeXaEpSXhUTTT5UmXFDyHqA@mail.gmail.com> <tencent_2EF9A30EDA26DA25F5F2E6E4E71DD81C3209@qq.com>
In-Reply-To: <tencent_2EF9A30EDA26DA25F5F2E6E4E71DD81C3209@qq.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 31 Aug 2022 16:16:41 +0200
Message-ID: <CAOj+MMHgKa7obp_SdOG-ikt9FWyjLPi4_MWs9nT-38AYjDTdfw@mail.gmail.com>
To: Wei Wang <weiwang94@foxmail.com>
Cc: Igor Malyushkin <gmalyushkin@gmail.com>, idr <idr@ietf.org>, Sue Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary="000000000000fa3e8705e78a251d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/wcenfXeYdfcSOU4NhQ1MCpxL2CM>
Subject: Re: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)
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: Wed, 31 Aug 2022 14:16:58 -0000

Wei,

I just want to highlight one important principle in respect to your point
#1 about the new quota which I believe was not observed so far during this
discussion and this is a very important change.

*In BGP based LxVPNs architecture when you provision and delete a VPN site
or a VRF you are not required to touch configuration of any other node in
the network other than your immediately adjacent PE. *

Your quota violates this principle completely by requiring you to modify
the <RD,src PE> value or even if the value remains the same to add such
<RD,src PE> pair to the list on each remote PE when you add new VRF or new
sites to existing VPNs.

Regards,
Robert


On Wed, Aug 31, 2022 at 3:03 PM Wei Wang <weiwang94@foxmail.com> wrote:

> Hi All,
>
>
>     The updated draft is the fruit of previous intense discussions, we
> have analyzed various possible situations. Let me explain some major
> concerns again:
>
>
> 1) About the quota:
>    Actually, the quota is not exist in the original version, but we found
> there are some problems during the discussions in the mailing list. So, we
> add the quota to improve the drop strategies after the VPN Prefix ORF
> mechanism is triggered. We can't drop all the routes(from all sources)
> belong to the VPNs when the VRF limit is exceed because one of the rogue PE.
>     The reason that quota is set for every PE is that in real network the
> number of customer routes in each VPN under different PEs may be different.
> So, the quota value should be set depend on the customer scale.
>    For more information about quota, I think you can refer the discussion:
> https://mailarchive.ietf.org/arch/msg/idr/uoQO8vqSA82UCrfXppFjwNbMg1A/
>
>