Re: [Lsr] Thoughts about PUAs - are we not over-engineering?

Robert Raszuk <robert@raszuk.net> Tue, 14 June 2022 14:43 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0466BC15AAC0 for <lsr@ietfa.amsl.com>; Tue, 14 Jun 2022 07:43:37 -0700 (PDT)
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_BLOCKED=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 xjtpqE_GnPyp for <lsr@ietfa.amsl.com>; Tue, 14 Jun 2022 07:43:33 -0700 (PDT)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (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 3A080C15948F for <lsr@ietf.org>; Tue, 14 Jun 2022 07:43:33 -0700 (PDT)
Received: by mail-ed1-x531.google.com with SMTP id z7so11940205edm.13 for <lsr@ietf.org>; Tue, 14 Jun 2022 07:43:33 -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=negoCBTR5YBqo0RjW3nO7sTl7DzUFUh1IEFQ1yl2zJ8=; b=KBZax9K7+N4O3XtvSM+4tquE7333THR/8hjZh7Lgg9+9zDjrzpaK7JtjiXQmqH6OZE i48/3QWWPvUE5YYqh7MO6wN/zTiGqqyxzH8m3fYGpgB5l0RhHP8rVdKkMitBxX8K02/5 195jSArDYMKQYsQjmDN54/mf4LyrtzaKaERIV9zXsnJoPaQ2opFHlPHaga62Gse7dYOX VKPYDdaPgSk4UbgHDG90jAk+NI7MfIf37Jh3ppgMepIvuGIooMUe4hm30WkTRp0fVIGw eOE0dB5tJoXuwvDqLA6TgDz2S3D56T03XrWYIPT3x7YZBeqwE2Jkuqu0o43ZF6NPfskD ulDw==
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=negoCBTR5YBqo0RjW3nO7sTl7DzUFUh1IEFQ1yl2zJ8=; b=PCkSpi09jiGyWBy8zppzAfEK5NPJE434G/25c3oYzlhorDaKhInSHVlc9EAE0vxKm8 xbPg6PhWXbbGzmw3QvAdQhxrbFxnfQ7wnZCIRRDSduForXtekj84s9b2/d/vzW4fwELu gUfdy6FcvIc7y2Cr7/lcr3OycZm8buCoTVMdgwk9OdyWaaCtBVNMF7cnvvni/DaKd4OP 5pgA17df6UZyhNfckyQ3GaFXjk05VbuzsCPqi9JrCoog4yJqscYMwLut/u1RquvJ51z7 jU6Bu53Nrp//l7E7PUxXnheofa0FB1n7YhwiyJcbc/E5LxoT0bUBChAcpLhuQRpgcQX8 vZhw==
X-Gm-Message-State: AOAM530L977j5KDlT8uJdiVx5w93OkqY0o4DdNT/hBQRdxOYSo7OPsrW z2j8OyLKb4e8+NqAQw2R2ER+x0MkDZDhZQTeNaFrww==
X-Google-Smtp-Source: AGRyM1vIqiJZOvgyExl79ELmF9QoXan+/8mXeVCNXHtKZUiKVGibAjA0QwfIADm24/Z0eb47IH4CVqIgIojKMkRU+fM=
X-Received: by 2002:a05:6402:17d0:b0:42d:ccc1:f4e4 with SMTP id s16-20020a05640217d000b0042dccc1f4e4mr6523544edy.150.1655217811236; Tue, 14 Jun 2022 07:43:31 -0700 (PDT)
MIME-Version: 1.0
References: <AM0PR07MB63863359D147F9EC0FF67689E0AA9@AM0PR07MB6386.eurprd07.prod.outlook.com> <7932F2B5-7F14-4EA9-A270-1A860B7FF9E9@chopps.org> <CAOj+MMGQCB25QX3GW-AcLKQVnkdakHugrEq7snkJZpV9r9WN+w@mail.gmail.com> <7DDA5508-46C3-4337-8667-5EFC769948AF@cisco.com>
In-Reply-To: <7DDA5508-46C3-4337-8667-5EFC769948AF@cisco.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 14 Jun 2022 16:43:20 +0200
Message-ID: <CAOj+MMG3KC=wCYM2hKuK64jfMrPW3aQPWbx4Lma1fSaogGHnMA@mail.gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Cc: Christian Hopps <chopps@chopps.org>, "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>, lsr <lsr@ietf.org>, "draft-ppsenak-lsr-igp-ureach-prefix-announce@ietf.org" <draft-ppsenak-lsr-igp-ureach-prefix-announce@ietf.org>, draft-wang-lsr-prefix-unreachable-annoucement <draft-wang-lsr-prefix-unreachable-annoucement@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aa3fd305e1696dab"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/kEN1C9s6nWuHXF6OBUA5rvgpz0E>
Subject: Re: [Lsr] Thoughts about PUAs - are we not over-engineering?
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2022 14:43:37 -0000

Acee,

> Note that any good implementation will allow one to punch holes in their
area ranges so that critical prefixes are advertised or

Every PE address is critical. The story that one PE can be more important
than any other is just to mislead you at best.

And we are (I hope) scoped the discussion to summaries.

I realize  PUE also wants to cover P failures so in this case each P is
also equally important.

Thx,
R,


On Tue, Jun 14, 2022 at 3:57 PM Acee Lindem (acee) <acee@cisco.com> wrote:

> Speaking as WG member:
>
>
>
> *From: *Lsr <lsr-bounces@ietf.org> on behalf of Robert Raszuk <
> robert@raszuk.net>
> *Date: *Tuesday, June 14, 2022 at 9:27 AM
> *To: *Christian Hopps <chopps@chopps.org>
> *Cc: *Gunter Van de Velde <gunter.van_de_velde@nokia.com>, lsr <
> lsr@ietf.org>, "draft-ppsenak-lsr-igp-ureach-prefix-announce@ietf.org" <
> draft-ppsenak-lsr-igp-ureach-prefix-announce@ietf.org>,
> draft-wang-lsr-prefix-unreachable-annoucement <
> draft-wang-lsr-prefix-unreachable-annoucement@ietf.org>
> *Subject: *Re: [Lsr] Thoughts about PUAs - are we not over-engineering?
>
>
>
> All,
>
>
>
> > What is wrong with simply not doing summaries
>
>
>
> What's wrong is that you are reaching the scaling issue much sooner than
> when you inject summaries.
>
>
>
> Note that any good implementation will allow one to punch holes in their
> area ranges so that critical prefixes are advertised or included in the
> range existence criteria.
>
>
>
> Thanks,
>
> Acee
>
>
>
>
>
> Note that the number of those host routes is flooded irrespective of the
> actual need everywhere based on the sick assumption that perhaps they may
> be needed there. There is no today to the best of my knowledge controlled
> leaking to only subset to what is needed.
>
>
>
> But this is not the main worry. Main worry is that in redundant networks
> you are seeing many copies of the very same route being flooded all over
> the place. So in a not so big 1000 node network the number of host routes
> may exceed 8000 easily. cri
>
>
>
> Sure when things are stable all is cool. But we should prepare for the
> worst, not the best. In fact, the ability to encapsulate to an aggregate
> switch IP (GRE or UDP) or nowadays SRv6 has been one of the strongest
> advantages.
>
>
>
> So as started before the problem does exist. Neither PULSE nor PUE solve
> it which are both limited to PE failures detection which is not enough
> (maybe even not worth). But PE-CE failures need to be signalled in the case
> of injecting summaries. Maybe as I said in previous msg just BGP withdrawal
> is fine. If not we should seek a solution which addresses the real problem,
> not an infrequent one.
>
>
>
> Best,
>
> R.
>
>
>
>
>
>
>
> On Tue, Jun 14, 2022 at 2:51 PM Christian Hopps <chopps@chopps.org> wrote:
>
>
>
> > On Jun 14, 2022, at 04:59, Van De Velde, Gunter (Nokia - BE/Antwerp) <
> gunter.van_de_velde@nokia.com> wrote:
> >
> > What is wrong with simply not doing summaries and forget about these
> PUAs to pinch holes in the summary prefixes? this worked very well during
> last two decennia. Are we not over-engineering with PUAs?
>
> 100% yes, IMO.
>
> Thanks,
> Chris.
> [as wg-member]
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>
>