IETF Logo Mail Archive

Re: [Idr] draft-dong-idr-node-target-ext-comm-05.txt - WG Adoption and IPR call (9/27 to 10/11/2022)

Robert Raszuk <robert@raszuk.net> Tue, 27 September 2022 21:42 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 9C166C15DD55 for <idr@ietfa.amsl.com>; Tue, 27 Sep 2022 14:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 ZsFVme57V31n for <idr@ietfa.amsl.com>; Tue, 27 Sep 2022 14:42:14 -0700 (PDT)
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (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 28026C15AE3E for <idr@ietf.org>; Tue, 27 Sep 2022 14:41:51 -0700 (PDT)
Received: by mail-wm1-x32a.google.com with SMTP id i203-20020a1c3bd4000000b003b3df9a5ecbso10245465wma.1 for <idr@ietf.org>; Tue, 27 Sep 2022 14:41:50 -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:subject:date; bh=ejZP3pG+ijhIijtyXGsCcaISh6vjVW+1GNmOiksCXy8=; b=FROy5/uhbw/GUmyG5JpfG9XXsn6BqF5VzStyiSaw5kD2cqm8hwexGyqJua6wETGlFP pEIWk9lrEzf2uirZrr5I7uQVxfJ8Ew+n0SDkYoRovvs5+9m0AoTjvmrfINEjmaDHQzE1 an4hWEs85/5IHgycJkXmErwniA21bMNnZr5bGRp7jtGRoC+RWP21lHvutB9YQ5PRsTmf v/KC8DxLayP3OaHUxLj7F//cfiRnAP1AAYCnVXQBe1PmsIjB5jjDKe5UbS9JGk4Y7l6M YAPS3P44Hc/5Jgu7YGZMr2j3fRMZvwncUt1KgxxTzEwlLjoP2ukQy6CeT5OqSjaHCnO1 HgBA==
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=ejZP3pG+ijhIijtyXGsCcaISh6vjVW+1GNmOiksCXy8=; b=oyFrzGedO7x364L+lCLSG4B//PXgG33UvZbeyKsT6d1PjQOe6ak1ErE7eeZQK5VYJJ iQ1r7CtUq5x6ygt49ooVLiTs3bKqPYBfQ3YjnjaIPa2Vg1SlUdVFUpxLKcIzp9e6ZHhT q565U8tSPs+HCnjmv545a/ecWdsJ1GzQsX93jKEIOl8lmQHmQ6eCh4zpArOLYVD3blAZ NZC7KzuwxQE+tNdPF5CAfX19qZSqscSG/wCNDZh/MWPD9w6d9KvqGp/SxNE8QkFoN+tE 0cpRRc3/vPsZP3MVIq0kAlTfATcDEU/U7hoJKXF95vEZTQE95qbicrRXiSnTGvIGSyFw TA+g==
X-Gm-Message-State: ACrzQf2+I8sk9tjzbOPThi5FObq87e6B7NMCzPUUpCKc5FZQq/W4fiwA zNnPpqyl42rf0HlYMdUVv0ZpksBTTL2Co6Nd9MiFYA==
X-Google-Smtp-Source: AMsMyM5trZJW/+7BaivBVoMvCTUANY8gq8lVGFT7eWtUI9JQ2mBjyLHhO8YV3GxgXOOir6VVbbXbwvkVLd7FzCiwSx0=
X-Received: by 2002:a7b:c047:0:b0:3b4:adc7:1ecb with SMTP id u7-20020a7bc047000000b003b4adc71ecbmr4190174wmc.144.1664314909165; Tue, 27 Sep 2022 14:41:49 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR08MB4872EEE329BDDDCC0F387B17B3559@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB4872EEE329BDDDCC0F387B17B3559@BYAPR08MB4872.namprd08.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 27 Sep 2022 23:42:15 +0200
Message-ID: <CAOj+MMGmOvK-THYVc=+A27Fwfp-BHooeNrDJVYsj0owC=N68Xw@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: "idr@ietf.org" <idr@ietf.org>, "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>
Content-Type: multipart/alternative; boundary="000000000000f4a08105e9af82bb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/1cnbY-x14dKRGl14ad0U9kYjcKY>
Subject: Re: [Idr] draft-dong-idr-node-target-ext-comm-05.txt - WG Adoption and IPR call (9/27 to 10/11/2022)
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, 27 Sep 2022 21:42:18 -0000

Hi Sue & Authors,

I have re-read the draft and have two concerns and suggestion. Concerns IMO
need to be addressed before we adopt the draft. Suggestions can be added
later.

*Major concern: *

The document talks about procedure during dissemination of update
message(s). It is however completely silent about withdraws. As we know BGP
UPDATE which contains withdraws can be build using only subject NLRIs. That
means that those may/will not be subject to discussed filtering.

I am not 100% sure if all nodes will continue to operate fine if they will
be receiving withdraws for NLRIs never previously received. Yet propagating
withdraws will happen everywhere.

To address this well it seems that capability negotiation would be the
safest bet. But isn't this too much to ask ?

*Minor concern: *

Which is more important RT or NT ? (RT when used with RTC of course).

*Suggestion: *

I would propose to make Target BGP Id to be a prefix not fixed 4 octet
field. Wisely choosing BGP Ids can lead to very efficient distribution.

*Final word: *

Of course this proposal goes against BGP p2mp principle, but at least it is
not p2p, but have potential built in to make it
p2(subset-of-multipoint)peers.

Thx a lot,
Robert.


On Tue, Sep 27, 2022 at 7:31 PM Susan Hares <shares@ndzh.com> wrote:

> This begins a 2 week WG adoption and IPR call for
> draft-dong-idr-node-target-ext-comm-05.txt.
>
> https://datatracker.ietf.org/doc/draft-dong-idr-node-target-ext-comm/
>
>
>
> The authors should respond to this email with an IPR statement.
>
>
>
> The WG should consider in their discussion:
>
> 1) Will this new  transitive extended community help
>
> in operational networks?
>
>
>
> 2) What conflicts does this new Extended Community have
>
> with other functions in general BGP route distribution or
>
> VPNs (EVPN, IPVPN)?
>
>
>
> 3) do you have any concern about the text in the draft?
>
>
>
> Cheerily, Sue
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>

v2.23.0 | Report a Bug | By Email