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

Jeff Tantsura <jefftant.ietf@gmail.com> Sat, 15 October 2022 21:47 UTC

Return-Path: <jefftant.ietf@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 4C166C14F72A for <idr@ietfa.amsl.com>; Sat, 15 Oct 2022 14:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ViyhBF_s1L6b for <idr@ietfa.amsl.com>; Sat, 15 Oct 2022 14:47:23 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 05374C14F745 for <idr@ietf.org>; Sat, 15 Oct 2022 14:47:22 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id o17-20020a17090aac1100b0020d98b0c0f4so9631904pjq.4 for <idr@ietf.org>; Sat, 15 Oct 2022 14:47:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=tUhhBEDuKOVwhHE3zfwEx53atkwuLOlLUbbm8+jpoHs=; b=bjPvPjM6xjtmfhb4FfiQfUD2/1uoVWlF1OVbJOBXwxtlG2Emaz7fo4zoQf9qW5DToS dW3y01+6SCOxd/nGdqvfNYfshY7tlnCahFF5u5A6iGeNr/ts+bUzgAufqRR/a4fsdoRe hlUeM/jS92UixB3MaqEAUkEMv3LhX0gBUMacpAdRYy3O9ZBdaN+MeCcIZ9WGWaP5+a9G XtwBT7bLA1rJvohRQA3AozhJW3sIJRp/MO2L7QQsWokfRTB1su7tBm+Y/r/wOcVujaoD Zxs9/sKkXve6mB2klxxwe7MdC87ks6+UY1UoKnkUdxqBTavRvWAPONyTNFDpFVyllXf6 WsCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=tUhhBEDuKOVwhHE3zfwEx53atkwuLOlLUbbm8+jpoHs=; b=sIN4XdqsC+YDquNfYEA8wk3GznFeu/jxIqbUkwR+dm1ytezSOjDdNT6qBX3Atxm+eV zfyYxsXtn1xcce5JvqIOA/pywk7o5ghc8pRmqUVd7g+DV0gDnP7/WQelYan2/7uAY8Oq D4Yqw5fzOMfzAQSDy8emcaMRilC0saurvkaz13Nd1oXqOHxOEboZ3RbxZsqvAPFEXMeY PdZym8tyYWCDkTM0eYFbtIRMUxloZVYRul0MS8sWbp48RQls6x1pbYsGvzRWWsecqGh0 XGgU08s7OtOQiDBMfGfoZtll2ax4LSaegWDT5T9JgiNFHp0owY6NoLY4tfMg4DRKYUdt LZSQ==
X-Gm-Message-State: ACrzQf2kulBozyl0zGMIQ8FAvDllYZFPuUX1TEhw2qc84EbILN5A+fUZ MNNb0cTahdiRVNnSxs5eRyCBsX8nz0w=
X-Google-Smtp-Source: AMsMyM7mBsfkPDvkrYCyWe/NueNsu/Py411CY85yYPq4Y0v9K7gIDFexJvviUxDD+BxoBIxW5pGSIw==
X-Received: by 2002:a17:903:32d2:b0:17a:e62:16e2 with SMTP id i18-20020a17090332d200b0017a0e6216e2mr4535263plr.93.1665870442284; Sat, 15 Oct 2022 14:47:22 -0700 (PDT)
Received: from smtpclient.apple (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id m34-20020a634c62000000b004561e7569f8sm3499166pgl.8.2022.10.15.14.47.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 15 Oct 2022 14:47:21 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Jeff Tantsura <jefftant.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Sat, 15 Oct 2022 14:47:10 -0700
Message-Id: <790B75F1-2EB1-49B5-93E3-28F7D26B75AB@gmail.com>
References: <Y0mJ2CJQbUbf6pzO@Space.Net>
Cc: "Dongjie (Jimmy)" <jie.dong=40huawei.com@dmarc.ietf.org>, idr@ietf.org, Susan Hares <shares@ndzh.com>, "Van De Velde, Gunter \\(Nokia - BE/Antwerp\\)" <gunter.van_de_velde@nokia.com>
In-Reply-To: <Y0mJ2CJQbUbf6pzO@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: iPhone Mail (20A392)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/szaZHezwFhtW33TzHQIYHWslCBE>
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: Sat, 15 Oct 2022 21:47:25 -0000

Hey Gert (long time ;-)),

We are much beyond the time when an AS was bunch of ASBRs with RR and iBGP in between only.
/* fictional 
Imagine a 1000s devices in 9-11-13 stages multi-planar leaf-spine block with eBGP (next-hop rewrite) between them, policies are horizontally consistent (based on a position of a device in the block). When everything is up and running, stage interconnection is highly consistent (equidistant end-points)and works just great with consistent distribution of reachability (p2mp).
Single or even double failures are easily mitigated by wide ECMP (with fast rehash, easily below 100ms).
When an optical span fails however, it is a very different story, so you need to update either all relevant receivers (could be just a subset of routes, could be some additional meta-data(metrics/BW/etc) or sender(s) (or a controller that injects said subset m). In many cases, being able to target a specific set of BGP speakers is the only solution (temp mitigation).

As you rightfully said - all of this can be done with 0 changes to the protocol (through management plane), however has a number of its own issues (trade-offs).

I agree that 1:1 mapping doesn’t really scale, we could think a a more efficient distribution through wildcarding (requires some planning of how router-ids are allocated). Would be somewhat similar to “passive BGP” in some implementations - accept all peers that come from 10/8.

I have a mixed feeling about this, BGP person in me is saying (throw this over the board to management), operating this stuff at scale one is seeing some opportunities  ;-)
Hence my support.

Cheers,
Jeff

> On Oct 14, 2022, at 09:10, Gert Doering <gert@space.net> wrote:
> 
> Hi,
> 
>> 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.
> 
> Gert Doering
>        -- NetMaster
> -- 
> have you enabled IPv6 on something today...?
> 
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279