IETF Logo Mail Archive

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> Tue, 30 August 2022 08:49 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 572D9C14CE29 for <idr@ietfa.amsl.com>; Tue, 30 Aug 2022 01:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, 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 nPu0KpxL16eT for <idr@ietfa.amsl.com>; Tue, 30 Aug 2022 01:49:34 -0700 (PDT)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 5A977C14CE43 for <idr@ietf.org>; Tue, 30 Aug 2022 01:49:34 -0700 (PDT)
Received: by mail-ej1-x629.google.com with SMTP id se27so12966032ejb.8 for <idr@ietf.org>; Tue, 30 Aug 2022 01:49:33 -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=oOIOh1BpHJawmh9LbIov64imQyhXlAitBYfmRmG3R2o=; b=XJhS7zMzLndV/Ig/OgR0DEZiVxlPKgyWteEWk2R0nqMTapLePOfE+YWaEGcz15C1br D+TCnxFWVjN113m4Ep3iFoTUTR0FQIhSc18ol85n1fY/WrpWnph+qUko3QV4KqGz7C0J UvkEClhsQqdNlBToogrsbxh6eXh9VbF3c4db/8ztMyKAqgNj3ct3lciIUkSIHk9RhIpE PTdey9OJII18pTrgFu1ZAbdJibQ5DuHqsNIZpWhgzOCn1y57pnmCnc0DLoLlp/+T7/cz COT3uFdNhBh6HDADYijhlJ5TpSo/zzkcFz6CvmZS+vwvmI4aVp2hCEZ7hQL27BIpgY+2 9AyQ==
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=oOIOh1BpHJawmh9LbIov64imQyhXlAitBYfmRmG3R2o=; b=TuMbEPbmPmdql+bNfs5+/olw4xl++3dmA118mNlfBU+IyZtWEQAt9IWk2gdhyg0suc sCKAM55nTtDmQca4sItuKvQsatBqZ/8FM5X/kmAkbkT0b96gdGZs83adzZLXq8jAdhGI WbDstuREVk0kt/U71CJmeiF33edwdnaocOPzXUH6X5fO0BFyGhpACLo/0uv6WWH0R2Sj k6sLIhHGiBIYRzD5RFlm3w/8mK46qWBn0A2P41RFIXztdVa36zKuHvD/xJdVKJ6CKtNe 9jSX6Il/F0H4GeHeQuQ7DLdRfv21q4F1KXM4yY7Sq2anIdCQbDuMSH8zz/KKKTJgCEM8 eADw==
X-Gm-Message-State: ACgBeo045il3C/OSbW0dLVpSLSILSy4DhiJRCL4eYPCT2EtJZ0LBqbPT IrBDvlVu1c+fAtTW/I74s/onvr0hM6yb1lHXqV54HQ==
X-Google-Smtp-Source: AA6agR6EjmA4TALcf7or6mdc6wh0tIq/X2jl0IJFZK1eOpps8K0idyWx6zvEb9DNlp3wkIlb/Xlor7nbixSzsxH5Ick=
X-Received: by 2002:a17:907:70c:b0:740:33f3:cbab with SMTP id xb12-20020a170907070c00b0074033f3cbabmr12343426ejb.600.1661849372487; Tue, 30 Aug 2022 01:49:32 -0700 (PDT)
MIME-Version: 1.0
References: <tencent_3C3279A3B4DAF8DA03F446E7AAE799D8AA09@qq.com> <CAEfhRrz5aAJmy2Ye1gqss2d72nm78n4SfeowO-FU7i4Z6Zpb+A@mail.gmail.com> <0CD78D4C-672F-41AA-8E1B-98CD8A875D21@pfrc.org> <CAEfhRrxkuYMmfcdX=M9PG2mN+D5fCBF5bVxd1bSA2O9PU5G-gA@mail.gmail.com> <000001d8bbba$ceb9e4b0$6c2dae10$@tsinghua.org.cn> <CAEfhRrwrKJ4A=QQBWRXtLKi-U0udv+zPuWoW0wqbeMQ2U-=JXA@mail.gmail.com> <CAOj+MMGLQ6enLxy36ZcFHh6qaCh7Ba1QFDa5XokccT7wvvU_fg@mail.gmail.com> <010101d8bc1c$da2391e0$8e6ab5a0$@tsinghua.org.cn>
In-Reply-To: <010101d8bc1c$da2391e0$8e6ab5a0$@tsinghua.org.cn>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 30 Aug 2022 10:49:22 +0200
Message-ID: <CAOj+MMGuuzLWwMbfuMd-Lu4hZiY_9QUroE9k8fiFZ_uT65aHnw@mail.gmail.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>
Cc: Igor Malyushkin <gmalyushkin@gmail.com>, idr <idr@ietf.org>, Sue Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary="00000000000084863f05e77175d0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-CyXsGBmQFgC3vjejmu0lSLRMjQ>
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: Tue, 30 Aug 2022 08:49:38 -0000

To close this discussion I do not agree at all with neither point #1 or #2
in your reply below.

And from RR I was not proposing RTC but ORF to src PE.

But since you are not willing to discuss any alternatives further emails
are pointless.

Kind regards,
Robert


On Tue, Aug 30, 2022 at 5:01 AM Aijun Wang <wangaijun@tsinghua.org.cn>
wrote:

> Hi, Robert:
>
>
>
> Regarding to your “final question”, my answers are the followings (I think
> you are mentioning again the RTC based approach):
>
> 1.     The overflowed VPN routes can only be identified/triggered via the
> receiving/overwhelmed PE.
>
> 2.     The per RT based maximum number of routes on RR can’t represent
> per VRF limit on the receivers.
>
>
>
> Finally, thanks for your comments and suggestions during the adoption call
> of this draft, the updated draft has already incorporated some of your
> constructive suggestions, and we are glad to hear more such kind comments
> later. We have discussed intensely other possible approaches, there is no
> easier way to achieve such goal.
>
>
>
> Best Regards
>
>
>
> Aijun Wang
>
> China Telecom
>
>
>
> *From:* Robert Raszuk <robert@raszuk.net>
> *Sent:* Tuesday, August 30, 2022 12:24 AM
> *To:* Igor Malyushkin <gmalyushkin@gmail.com>
> *Cc:* Aijun Wang <wangaijun@tsinghua.org.cn>; idr <idr@ietf.org>; Sue
> Hares <shares@ndzh.com>
> *Subject:* Re: [Idr] Adoption and IPR call for
> draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)
>
>
>
>
>
> *Hi Authors of this document, *
>
>
>
> I have final question to you on this proposal.
>
>
>
> Would you be willing to rewrite the draft such that the required behaviour
> and protection can be run on Route Reflectors and not on receiving PEs ?
>
>
>
> That way one hop ORF will easily reach the src PEs and the fire can be
> locally extinguished  where it starts.
>
>
>
> Further if needed to automate things further, receiving PE could push you
> max number of routes it is both willing and expecting to accept on a per RT
> basis via simple extension to existing protocol.
>
>
>
> Kind regards,
>
> Robert.
>
>
>
>
>

v2.23.0 | Report a Bug | By Email