IETF Logo Mail Archive

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

Alexander Okonnikov <alexander.okonnikov@gmail.com> Tue, 05 March 2024 09:45 UTC

Return-Path: <alexander.okonnikov@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 9CD00C14F615; Tue, 5 Mar 2024 01:45:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.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, FREEMAIL_FROM=0.001, HTML_MESSAGE=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, 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=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 QDHKEIdsS4OV; Tue, 5 Mar 2024 01:45:03 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (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 E8924C14F5FE; Tue, 5 Mar 2024 01:45:03 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id 38308e7fff4ca-2d311081954so62525281fa.2; Tue, 05 Mar 2024 01:45:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709631901; x=1710236701; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=b2RA2Xi0VimM+lMLAw2bd+Rm6XdRFsCBOoVj4uGE09o=; b=Tv9S+R3HXp+PajHiutvvS5p/vjidNarWKBID9+iatds1SMmUNnEsv1T7mzhG/dCllG O6sw9gtCW2AaVNURWnb+G1TLF/C79LXm20jNX5y10u1NP4w8P5E3DlUKQ91siTxyHgHi ATzSpFYnL/s/R8RguqImLqlxFNZh2XOUwqzjXk0w5XCfwEc1RYSJE78itjEDpM20JPu0 oPGSZT0w8zMjqKivlaxniNcZFnSenSJet3sYUTAI+ud6uBdUOwa9u7u5UB/0VOe5iQkA h2BqV7zFkHIBaUy+1vU5MG4cAdhYzZRCZbJYWQp8mrYd4zLzjPBMDCWZVoGKKbah9fVn jhIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709631901; x=1710236701; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=b2RA2Xi0VimM+lMLAw2bd+Rm6XdRFsCBOoVj4uGE09o=; b=LLqJeMaUeeKAjDJF7bSvVS8OaBJpFaxaWq+JND624YrDvc0B+iVuJKb/pknqSiGPkD 3Wpmx+y8ZteLnUC7mhIjv/GtE9gJkDofX4wNa685rBYpV/yg+fUp7i+9hvO4GNWMSRC4 A2vFIdXLeCZ7mceL9DwFE0UUbBIRT5wmGiy0uzVpoyRnk3mhPtxZWTDl8IW4UbwfYSAe pFF7BgMStxJbdGUGj8wsuI0nPxCQ5B5miMlsVV1St8MpCpYqs7CDoLbK3q9pq0C6fpKh ExACXcQFEM9eRdFbdbpyH4Ob6/8sgj4x1W0D06zsf/JPPII6dEDrJHX9cbWEWrrVt0vc c/Cw==
X-Gm-Message-State: AOJu0Yycz6F9WdKxJPqwFZkxdQtAvXefXlJY50To3HroglzgM9dxgi7w jlUa6L6smYbA1Dscs+xHz/dITCXtjayl3eB955k4jnVDwdllw3CZeL4KvYtO
X-Google-Smtp-Source: AGHT+IFSkhdzSOqtBIPxKbYF5jL8OH6m2dDq9Jxl4vRZUJViuCEHEhOfw6ZW2S3mksJqF0swySc0lQ==
X-Received: by 2002:a19:ae11:0:b0:513:27d7:400e with SMTP id f17-20020a19ae11000000b0051327d7400emr879561lfc.29.1709631901184; Tue, 05 Mar 2024 01:45:01 -0800 (PST)
Received: from smtpclient.apple ([94.19.48.224]) by smtp.gmail.com with ESMTPSA id n13-20020a056512310d00b005132ccc6af4sm1814236lfb.172.2024.03.05.01.45.00 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Mar 2024 01:45:00 -0800 (PST)
From: Alexander Okonnikov <alexander.okonnikov@gmail.com>
Message-Id: <60B94E98-3D0E-44CF-8521-96A0F217AFDA@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1D989FE4-DD92-4054-907B-526414E44E8D"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.1\))
Date: Tue, 05 Mar 2024 12:44:49 +0300
In-Reply-To: <170954803408.43395.8450424120941872596@ietfa.amsl.com>
Cc: i-d-announce@ietf.org
To: IDR List <idr@ietf.org>
References: <170954803408.43395.8450424120941872596@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3731.700.6.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/mha3uYfrjLFqJUgcbAtNYAkKCvk>
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: Tue, 05 Mar 2024 09:45:04 -0000

Hi authors,

We have already more generic alternative for the second solution - 'Best external route' described in https://datatracker.ietf.org/doc/html/draft-ietf-idr-best-external-05. What about choosing one of two solutions - I lean towards 'best external' based solution. It seems lightweight and doesn't require Add-paths support.

Thanks.

BR
Alexander Okonnikov

> 4 марта 2024 г., в 13:27, internet-drafts@ietf.org написал(а):
> 
> Internet-Draft draft-ietf-idr-rtc-hierarchical-rr-04.txt is now available. It
> is a work item of the Inter-Domain Routing (IDR) WG of the IETF.
> 
>   Title:   Extensions to RT-Constrain in Hierarchical Route Reflection Scenarios
>   Authors: Jie Dong
>            Mach(Guoyi) Chen
>            Robert Raszuk
>   Name:    draft-ietf-idr-rtc-hierarchical-rr-04.txt
>   Pages:   6
>   Dates:   2024-03-04
> 
> Abstract:
> 
>   The Route Target (RT) Constrain mechanism specified in RFC 4684 is
>   used to build a route distribution graph in order to restrict the
>   propagation of Virtual Private Network (VPN) routes.  In network
>   scenarios where hierarchical route reflection (RR) is used, the
>   existing RT-Constrain mechanism cannot guarantee a correct route
>   distribution graph.  This document describes the problem scenario and
>   proposes a solution to address the RT-Constrain issue in hierarchical
>   RR scenarios.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-idr-rtc-hierarchical-rr/
> 
> There is also an HTMLized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-idr-rtc-hierarchical-rr-04
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-rtc-hierarchical-rr-04
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email