IETF Logo Mail Archive

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

Igor Malyushkin <gmalyushkin@gmail.com> Thu, 01 September 2022 16:36 UTC

Return-Path: <gmalyushkin@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 A5E6BC14F728 for <idr@ietfa.amsl.com>; Thu, 1 Sep 2022 09:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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_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 9VqrUV833Tli for <idr@ietfa.amsl.com>; Thu, 1 Sep 2022 09:36:24 -0700 (PDT)
Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (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 5A8E8C14F734 for <idr@ietf.org>; Thu, 1 Sep 2022 09:36:24 -0700 (PDT)
Received: by mail-io1-xd30.google.com with SMTP id n202so15049786iod.6 for <idr@ietf.org>; Thu, 01 Sep 2022 09:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=nHjEfnTDSbwnWBK7tr2FQn6t8CDK1tTUngytA3G6xmY=; b=IXnW8UJvleZPzrjONtUvffZS9JoJhRz4ic4jbJTXpeGoY90L+6UiE7cXNlxJKZR4qp +koTa44GAFf2diTeIfklD0xFgu5rudDgVkjZBdHFyAbGYmXiFFwiatj4XZr2VbLAXA45 cp9JtT5GfoQLzxq/SoBcKb7roKRLZbOuM6ctr9HgD+gUkBhGYN5xWRBpuo4DjeeBZClg N1oQq8uWHCVrLsU+d/nqheTP9OZ51Cr8EyTI4dhlnpJolXupC2nqhYNn0zWvhj5IadGz fQmh/cwsOpTPbsHG8IFGUZjz8k1njGx0vwtpdo1IOXBUQzz3WKO+a4+gohfS7UWT03AO tyng==
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:subject:date; bh=nHjEfnTDSbwnWBK7tr2FQn6t8CDK1tTUngytA3G6xmY=; b=xbw9ibZjX2FLbhc1hPp/jQf+COrHQ61R35eM35SmgGMd2Vtor7ZRKNML7dsfpB0WMf uUMMmQyLemMuSSo61+bzIKtjBv2nzttaETw3Hv4ojLWL2F9XQJt8+t5KXv5p+Eyp07J4 KpOnUHfPrlPc8LVoagqx8vsNU69x/4nXmlPoelM7yeJhq6q9+JFqbOVWQBU8ZfFi4dtn aGzePwbAN5dwSu54tYZ1I8L4G9jBhyqbfdZQZr8znUkZjfyx1OmGov8/1ShrOkwyiVHU gZEzOZL5DTYykVnShEDTqWWwJaWTOnZCRCmZVixD9Ken5mkjSd5GoeiSJvV38mYlO77A xpfA==
X-Gm-Message-State: ACgBeo0AagN/1s0tjA+QZ6VwYAKsK80a3pGHfVnsE9xLK4VG1tbJyPze Fg6t92NWTKaj10992g9V6ecLD/SfLoj0m8lJFH4=
X-Google-Smtp-Source: AA6agR5ZfAht3k8Ap6XrEeEolDaXRj/xG2Fs6glR1tguaIXk9EOfVMADac5PJ0SgI35+g7jhhvj9eZhU+hQHXQ3aQkw=
X-Received: by 2002:a05:6638:1387:b0:349:e047:fcc6 with SMTP id w7-20020a056638138700b00349e047fcc6mr18032386jad.67.1662050183335; Thu, 01 Sep 2022 09:36:23 -0700 (PDT)
MIME-Version: 1.0
References: <CAEfhRrzcMc7G75K8iz4ojpSMg_m5b+qcDJ9tWEM+fY0gdDcYkw@mail.gmail.com> <1A23140A-D92B-4427-8A02-DAFFA215209A@tsinghua.org.cn> <CAEfhRryvHZop1_kgT3m8vr37Wj839C2Av766-ne=oEqeuTfG+w@mail.gmail.com> <DD8E411D-7B4F-4CC7-A72E-C6984158D098@pfrc.org>
In-Reply-To: <DD8E411D-7B4F-4CC7-A72E-C6984158D098@pfrc.org>
From: Igor Malyushkin <gmalyushkin@gmail.com>
Date: Thu, 01 Sep 2022 18:36:12 +0200
Message-ID: <CAEfhRrydVSFHvj=muQ44Df=wR6MxbDbcHtG4Q0TDDCg1wcbZbg@mail.gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: Aijun Wang <wangaijun@tsinghua.org.cn>, idr <idr@ietf.org>, Sue Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary="000000000000c6d4e105e7a03698"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/70HghYBGl02Jz5Hf1JOXNGHxNw4>
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: Thu, 01 Sep 2022 16:36:26 -0000

Hi Jeff,

Not sure I get your point. Let me clarify mine. Aijun and I discussed a
case when a CE is connected to two PEs. These PEs use different RDs for
routes coming from the CE. SoO is highly popular with such schemes. I
suggested using SoO by a destination PE to attach it to an ORF message (in
a TLV). This helps an RR to stop sending and to withdraw excessive routes
with the SoO. Due to the same routes coming from two (or even more) source
PEs it`s impractical to cease sources one by one. Hope it helps.

чт, 1 сент. 2022 г. в 02:49, Jeffrey Haas <jhaas@pfrc.org>:

> Igor,
>
>
> On Aug 30, 2022, at 7:07 AM, Igor Malyushkin <gmalyushkin@gmail.com>
> wrote:
> Actually, I thought about SoO in this case, but the attitude is the
> similar. And I’m glad it is obvious that at least sometimes it’s better to
> pause the all flow of routes :)
>
>
> It would accomplish somewhat similar goals as route-distinguisher, true.
> And, having been used in that fashion would mostly revert to a prior ORF
> proposal:
> https://datatracker.ietf.org/doc/html/draft-chen-bgp-ext-community-orf-02
>
> That ORF procedure was replaced by rt-constrain for various reasons that
> have turned out well for us.  But the ORF in this case was in the "send me
> this" sense rather than "don't send me this".
>
> For many deployments, there's only a single CE instance within a VRF.  In
> such cases, the case of site-of-origin becomes indistinguishable from the
> route-distinguisher case.
>
> -- Jeff
>
>

v2.23.0 | Report a Bug | By Email