Re: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)

Robert Raszuk <robert@raszuk.net> Wed, 22 June 2022 09: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 42E03C15D862 for <idr@ietfa.amsl.com>; Wed, 22 Jun 2022 02:05:17 -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, 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_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 OwrTOq8CkNW9 for <idr@ietfa.amsl.com>; Wed, 22 Jun 2022 02:05:13 -0700 (PDT)
Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (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 5A3E1C15D869 for <idr@ietf.org>; Wed, 22 Jun 2022 02:05:13 -0700 (PDT)
Received: by mail-ej1-x634.google.com with SMTP id g26so11384542ejb.5 for <idr@ietf.org>; Wed, 22 Jun 2022 02:05:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fxVMkMcjdSpo7bLWCyKub6CorP+740xCc/NB/m31XaE=; b=UFdQ+Zu/jd14Z3PNVyUapui4vzIozidYsonP24vgbHyIHbwJi0x5xijVRs4JvY8hcX hmhzm59y0p1vmMdzzzdGI2q2yIBpnCUdBKST/APyIaoEYbkISmDVe8lI7P+PMH9YbfKy oDfngIuevlI1kjXpiZ0HXh2tqI9USiZtTnY37C7i6T06BMqJW0kXLyCUdhPyNpXyrFjG KBhIBnKMhmA3DIgeH/ii+A2ic9j9XFV82sy1dtxoQLKzc65p+Ewz1PDGa5rSIm4//rwM NnOzI08kEHUhdoSvbFK6NySHcK/Cp5w+O7ctrWmO5ZpqDaT9VLXGD8kCAW2lwvqwHios OSlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fxVMkMcjdSpo7bLWCyKub6CorP+740xCc/NB/m31XaE=; b=KRhI8iHNChnmVLMVms3KtO9HvRkbaiHFpYbTsIFS5bR6yffl47KOThMt4yV1FZKKgJ utLxnz3BWMFmfm5cpkXUM5EhkKHm0W64G2FYly2RL3zW3L+GnTHpB7yamwSfiWciA42n 6nteEkuAvz3nmYMeJPsmyJaflwUKT0FQ7Ql0IG4iXz8a7w+QlamQe+EHI7XGH/TLRl3Y +XBJzaM+bFfCe1x0FKVBnILLWLZ8Sq3rZJzZ+7Ix/tv13sCWW2o45IDMD1eiTp8iYsfP QK0U3E7TcXvxO+Yi9EdoOQwcDNwtHtIv94xryTgB+y3g3+R0GsncsoEAlwWSpMotCxVy kNWA==
X-Gm-Message-State: AJIora8UQYX+XNVmIUBoXjfxgc8Na5p68rpmLiA/fPbtH4gSsq0CDNxi ocCANihM6wHWjMuhyoMqzQkl2ykG1BoIb9D5vc2u3Q8Gv0A=
X-Google-Smtp-Source: AGRyM1uVj/HGYL++0df9fkc/7Dk3pHxd5NJQW4ojsg7+SUxvC0L4vS1TPZD5pDtjOC/kz360WBpNTjMcHCxpvXsFBPk=
X-Received: by 2002:a17:906:dc8b:b0:722:e656:def5 with SMTP id cs11-20020a170906dc8b00b00722e656def5mr2229388ejc.490.1655888711745; Wed, 22 Jun 2022 02:05:11 -0700 (PDT)
MIME-Version: 1.0
References: <BY5PR11MB4337C1704EE6D3A9F889798CC1B39@BY5PR11MB4337.namprd11.prod.outlook.com> <5B5BC7AC-9B56-4497-8572-C6FCA95803C5@tsinghua.org.cn> <A41A94F6-01E2-414C-9836-7DB7AD6D826F@pfrc.org>
In-Reply-To: <A41A94F6-01E2-414C-9836-7DB7AD6D826F@pfrc.org>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 22 Jun 2022 11:05:00 +0200
Message-ID: <CAOj+MMH8aNHVi7Jck197ONyOeP9LdtmEjLmYMdJi_hTAxmPNmA@mail.gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: Aijun Wang <wangaijun@tsinghua.org.cn>, "Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org>, Sue Hares <shares@ndzh.com>, "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000739b9005e205a2dc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_z7OBFJKJtWoeDfSpf9vRvOP474>
Subject: Re: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)
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, 22 Jun 2022 09:05:17 -0000

Hi Jeff,

Again, speaking to the general case... why should it ever be constrained?
> If the feature exists in the IGP, being able to represent it in BGP-LS is
> probably reasonable.
>

Is there any technical reason to send point to point information over a
point 2 multipoint (aka spray) protocol ?

Is there any benefit for BGP to take that load on its shoulders ?

Is this done purely for convinvence of reusing established by BGP TCP
session ? IMHO poor justification.

Are you proposing to bend IDR WG rules and start allowing BGP
protocol extensions without two shipping interoperable implementations and
a documented implementation report ? Note that LSR WG does not have such a
bar.

Is the need for p2p NNI any different then intradomain p2p data
distribution ?

Where in the BGP protocol state machine do we have a rate limit to capping
accepted data (aka churn) from OSPF or ISIS protocols ?

Note - I am asking you those questions targeting yourself in both roles -
IDR WG member and IDR WG co-chair.

Many thx,
Robert.