Re: [Idr] I-D Action: draft-ietf-idr-rtc-hierarchical-rr-04.txt

Robert Raszuk <robert@raszuk.net> Wed, 06 March 2024 16:05 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 AE094C14F619 for <idr@ietfa.amsl.com>; Wed, 6 Mar 2024 08:05:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, 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_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 vU1rjYfjHYo6 for <idr@ietfa.amsl.com>; Wed, 6 Mar 2024 08:05:28 -0800 (PST)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 9ADBAC14F681 for <idr@ietf.org>; Wed, 6 Mar 2024 08:05:28 -0800 (PST)
Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-563c595f968so10348710a12.0 for <idr@ietf.org>; Wed, 06 Mar 2024 08:05:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1709741127; x=1710345927; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tz1jLurjBsrah1DhFvfhjTKPXgfFf3SMlS9zw443iM4=; b=PJR5aEtU4RnT6ePJ9/KNKAoFHJ52TtxMsXNI6Z4iRg6VeBvJ+Yx7G4LNfYoqYK3W2+ ZzrvKbOsvVsw59Eutklnz9DmMNarCXAe0n8ADNpPYE+5d/xJ8XLu/zjszCWtxKJm2S4n J2Vxd0KG23tcXjA1RAD+j/ESQ1aGBBsUA48UNoqXkxYeMR0ZEZf1NLIP9ZO/XvJLXRJn JCZtC3R1k6KHsfACR58SySPSQF+ei/EKf75Do6zkP2nP6yRoV8jLmVrcyYcPnAzeFjLJ VD0fCGYc+nQA4oTBcrjyZys/nY7CygZvPB2Rh8hftjP5oAI8iDO/x08wyhneux3+WEgL 0urA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709741127; x=1710345927; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tz1jLurjBsrah1DhFvfhjTKPXgfFf3SMlS9zw443iM4=; b=ho/yWoCAnsK4F+2PAjkMKzBj8cd5SvpfBC/SwJtG/omZwc65YfDd+/v0tCg7lxZBA0 aCYW83d+x2Zu4icENki9HLA8EtSDtRpPiSR5VbMS6p8K0HyDXzqDsyV00yygrBmxjlkx 3kpWjFAScBMi47LX77Q/hidfMVXFogjgtlV9exdbavrLv5OVloSbNHicUhUxNhTlgg13 XSEiE1fgF1hpZMw3AZCahvEru/BI4wSYSRDiJlEa22tr5MpjVcG2kZi5D3pCvc2PO+AT KTayNdWm2WltGYmkR/GVoQ1JlQO9A8iahgI5Q6qLFzg6g/klD8MGF4OGOFKo3O2TdERx mb3g==
X-Forwarded-Encrypted: i=1; AJvYcCU/zeb6abEmFl47hczBJulRQOCC+TlGluAp43wxNMMlh1zncRifeylGFqx+WCWQ8wZs4s8WHMa8UTXlQGc=
X-Gm-Message-State: AOJu0YyRAlVOqEkdv54uQiY4Nv3AwJdJstp3PYFjQktZdo+voHJzPgLk A5vZHitT4jmRpH3bz0vZAYnHAXZdQrV+NQzzV5IZ2hMvRntC7PChnCs6JQCwcGye4w76xRlMo8A schvI5hKRn/n8EYB6iL/cVFnw4fJVztVn3PVIn4imqJXL33Q8
X-Google-Smtp-Source: AGHT+IFgbQsAw+2GEaCcG+RW5hmyaGM8hUjRleIZ4VSdGsho46K+fGwkstBIiRzZs4TBZw4ojes+084EcsqZ6AtJkks=
X-Received: by 2002:a05:6402:1053:b0:564:d715:1d67 with SMTP id e19-20020a056402105300b00564d7151d67mr10843930edu.17.1709741126563; Wed, 06 Mar 2024 08:05:26 -0800 (PST)
MIME-Version: 1.0
References: <170954803408.43395.8450424120941872596@ietfa.amsl.com> <60B94E98-3D0E-44CF-8521-96A0F217AFDA@gmail.com> <CAOj+MMH7PrQGaZ__-ZGnEmvkZWT38xuaP+fhraUtJ4C=iK=Thw@mail.gmail.com> <667F1B5D-68AC-410C-B490-5DD020B8D5E0@gmail.com> <CAOj+MMHTmvXqgLmJtkOZcb-ZF-3T7UZpbaaCmys2kw7eEtwS7w@mail.gmail.com> <BDF5AD35-7F4C-4F28-9406-E82BBD52B2C5@gmail.com> <871f9f9a204644b990d2796609896c93@huawei.com> <CEC8AF34-6008-4A82-81B0-B827C4A6AE03@gmail.com>
In-Reply-To: <CEC8AF34-6008-4A82-81B0-B827C4A6AE03@gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 06 Mar 2024 17:05:15 +0100
Message-ID: <CAOj+MMFtSgpNwEdmm48k8iLpP=Yr3L2LOobWGSc2HtJPe=mVxA@mail.gmail.com>
To: Alexander Okonnikov <alexander.okonnikov@gmail.com>
Cc: "Dongjie (Jimmy)" <jie.dong@huawei.com>, IDR List <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000081d55106130020fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/g6lbTqiJJNkFtM5sthGjhy9BjHo>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-rtc-hierarchical-rr-04.txt
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: Wed, 06 Mar 2024 16:05:32 -0000

Hi Alex,

I have been trying to see if what is written in best-external document is
really going to help. With that I have a question -

Imagine top level RR (RR1) from our picture having 100 IBGP clients each
connected to other (lower level RRs). For simplicity let's assume that
there are 10 low level RR clusters.

Question: How would top level RR (RR1) compute the cluster meshes members ?
The only way I can think of today would be to infer those from received
advertisements by looking at the CLUSTER LIST however this seems pretty
fragile.

My take on this here is that if we go that path we should perhaps add
CLUSTER_ID to BGP OPEN CAPABILITIES ...

Thx,
R.


On Tue, Mar 5, 2024 at 2:46 PM Alexander Okonnikov <
alexander.okonnikov@gmail.com> wrote:

> Hi Jimmy,
>
> To be precise, I don't think the 'best external' feature in Junos OS was
> implemented specifically to address issue with hierarchical RRs for RT. The
> implementation works for multiple families. Fortunately, it works for RT
> family too.
>
> Thank you.
>
> BR
> Alexander Okonnikov
>


>