Re: [Idr] Comments about draft-dong-idr-node-target-ext-comm

Robert Raszuk <robert@raszuk.net> Thu, 28 July 2022 20:18 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 10B9DC15C52F for <idr@ietfa.amsl.com>; Thu, 28 Jul 2022 13:18:00 -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 spise8MKjMDm for <idr@ietfa.amsl.com>; Thu, 28 Jul 2022 13:17:56 -0700 (PDT)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (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 01ACEC15C527 for <idr@ietf.org>; Thu, 28 Jul 2022 13:17:55 -0700 (PDT)
Received: by mail-vs1-xe31.google.com with SMTP id 125so2649005vsd.5 for <idr@ietf.org>; Thu, 28 Jul 2022 13:17:55 -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=VhLxcnO29s4ZS8T4f7aidn4Msb3fXy7DKMK4ZHVmnbg=; b=HORrw6NCVgZpwYp1iZ0RULVsEeTD279SpTVwxYQY8d+lhT6cxd0XW2/7T7vnV7xdm0 osTp0Jkk1H7vzF9Fv4c7pvaoVbAS0aZ+a1Ew5zhFJP0lF+U3qSVgI4I95TVfjtee9u9I vLJu+YfEm0p7fWelrq/en4XNBEXt8XHNVMhfgwHAaegvouGML3PGWDSnE/zhdgNfpDo9 fkDwcCrDj7rdN5pe3/smEY8fZjQtC++7kIGFiHM9luvxW8KLb+Xy7wbGFE/2ioI63ZUF r1Kf34gpDYsAWbtXTwVu0r6o5Aj9dRcfh48UdO9Lk1bHaQbR+hHZZd9QloKJuTuSqxuE n8wA==
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=VhLxcnO29s4ZS8T4f7aidn4Msb3fXy7DKMK4ZHVmnbg=; b=kNBsf9ZdaGWeCnaYvPrNE5YxgfI/0Hevxbf8C5zG2D98vGLENqjh78+tjwRmWbPube 5bM2MWcyjjlq+Ld7kcbdm6OwAYaGNQWJSSqHr6so/G4e6WniJiH2glVDulSZqwa9e+jS KvmEUVom/qxzEciiTS8d5FY6sImcWa5beH3Zu3fG3GoJrvktLivQ+Du87P2zjpkNieec 2z1s/FjHWrHWIjZxQOy3qGOPm03HaC5w+5MA8kdfmM66dnGLIoMZUbdsl7YFP6cifMdX Bm2eY9T+dPVA4GjSGy0gFir6LVDako+L3FpGdjxdOueZrS4Gq2Kqm6LRRX2GXPWvxK9b tETQ==
X-Gm-Message-State: AJIora+Wupx/4GrxgcunxfWMfz+RO1tiZgsPMmDE7q4a1t+qHGh9ftMr N+/EYxy/J9eLU0gMRnU8EPwbrhStQKHStK4AtEst1g==
X-Google-Smtp-Source: AGRyM1vHihIe7yc0jYtjdiV/iNa3Nm013xWVt9L2IKjf44qYCNfDvz5iWQIuEV9jaQXtiA6iViBbUsV7ZclWffBbpio=
X-Received: by 2002:a67:df0b:0:b0:357:dcb4:c498 with SMTP id s11-20020a67df0b000000b00357dcb4c498mr145422vsk.38.1659039475072; Thu, 28 Jul 2022 13:17:55 -0700 (PDT)
MIME-Version: 1.0
References: <BL0PR05MB5652EC60D898CA51E2C5F76DD4969@BL0PR05MB5652.namprd05.prod.outlook.com>
In-Reply-To: <BL0PR05MB5652EC60D898CA51E2C5F76DD4969@BL0PR05MB5652.namprd05.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 28 Jul 2022 22:17:44 +0200
Message-ID: <CAOj+MMELhopmN-dwBEMJHaGk4wKpXVSkGCYRCUEQtNiuLxMnSA@mail.gmail.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang=40juniper.net@dmarc.ietf.org>
Cc: "Dongjie (Jimmy)" <jie.dong@huawei.com>, Zhuangshunwan <zhuangshunwan@huawei.com>, "gunter.van_de_velde@nokia.com" <gunter.van_de_velde@nokia.com>, "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000094975505e4e33aec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ugxYZpjoDIUJaw6eFHZ5qJLQUDQ>
Subject: Re: [Idr] Comments about draft-dong-idr-node-target-ext-comm
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: Thu, 28 Jul 2022 20:18:00 -0000

Hi Jeffrey,

> This seems to complicate the RTC based route propagation:
> - the RTC advertisements now need to include these new communities
> - a logical AND criteria is needed
> - if a route needs to go to several nodes, then each needs to be encoded
by the source and compared against on each hop.

It seems that this is yet one more example of RTC overload or to put it
more nicely extend its original scope to new use cases.

With that what seems to be advised is to perhaps spin off RTCv2, make it
TLV based and instead of hacks to skip one AFI/SAFI vs the other or worry
about RT uniqueness just distribute filters fitted to any specific AFI/SAFI.

But again this is all going wrong way as BGP is really not the right
protocol for any targetted data distribution.

Best,
R.