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)

Jeffrey Haas <jhaas@pfrc.org> Fri, 14 October 2022 18:23 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 457E0C1522A2 for <idr@ietfa.amsl.com>; Fri, 14 Oct 2022 11:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 rijuI0udl9oa for <idr@ietfa.amsl.com>; Fri, 14 Oct 2022 11:23:56 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 90C44C14F722 for <idr@ietf.org>; Fri, 14 Oct 2022 11:23:56 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 1CF161E35A; Fri, 14 Oct 2022 14:23:54 -0400 (EDT)
Date: Fri, 14 Oct 2022 14:23:54 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Gert Doering <gert@space.net>
Cc: Jeff Tantsura <jefftant.ietf@gmail.com>, idr@ietf.org, "Van De Velde, Gunter \\(Nokia - BE/Antwerp\\)" <gunter.van_de_velde@nokia.com>, "Dongjie (Jimmy)" <jie.dong=40huawei.com@dmarc.ietf.org>, Susan Hares <shares@ndzh.com>
Message-ID: <20221014182353.GF2066@pfrc.org>
References: <39a075e7afd04d94b324075a5c696b84@huawei.com> <028ECC42-2021-4D00-9B31-B323F2480DAA@gmail.com> <Y0mJ2CJQbUbf6pzO@Space.Net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <Y0mJ2CJQbUbf6pzO@Space.Net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0MpiJRApwOXud8Zb6IFdEJIMQw4>
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: Fri, 14 Oct 2022 18:23:57 -0000

Gert,

On Fri, Oct 14, 2022 at 06:10:00PM +0200, Gert Doering wrote:
> On Thu, Oct 13, 2022 at 08:30:45AM -0700, Jeff Tantsura wrote:
> > Looking at my toolset (sometimes i need to move GWs of capacity from one region to another) - this would be a very useful addition.
> 
> If you need a mechanism to actually control routing propagation, this
> can all be built today with route-policies and communities, without
> protocol changes.  Exactly the way an AS needs.
> 
> If you want this to propagate something else, I am yet to be convinced
> BGP is what we should burden with it.

I'm in the process of doing a full re-read of the proposal and expect to
have comments about the distribution machinery for it.

That said, I agree with this high level point.  Minimally, the proposal
covers an extended community that can be used by policy to say: 

  Is my BGP Identifier present in this list of extended communities?
  If so, I'm interested in it.

The distribution machinery is worthy of the scrutiny this thread is bringing
to it.

-- Jeff

v2.23.0 | Report a Bug | By Email