Re: [bess] Review of draft-ietf-bess-evpn-ipvpn-interworking-10

Jeffrey Haas <jhaas@pfrc.org> Thu, 25 April 2024 14:26 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B6C5C14F5E6; Thu, 25 Apr 2024 07:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 kf_inGflxNPR; Thu, 25 Apr 2024 07:26:49 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE53C14F6A8; Thu, 25 Apr 2024 07:26:43 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id C0CE61E28C; Thu, 25 Apr 2024 10:26:42 -0400 (EDT)
Date: Thu, 25 Apr 2024 10:26:42 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: draft-ietf-bess-evpn-ipvpn-interworking@ietf.org, bess@ietf.org
Cc: idr@ietf.org, idr-chairs@ietf.org
Message-ID: <20240425142642.GB10862@pfrc.org>
References: <20240425140819.GA10862@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20240425140819.GA10862@pfrc.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/FFDYAMhQsF_r272boS95DWrY8yE>
Subject: Re: [bess] Review of draft-ietf-bess-evpn-ipvpn-interworking-10
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2024 14:26:50 -0000

On Thu, Apr 25, 2024 at 10:08:19AM -0400, Jeffrey Haas wrote:
> ipvpn authors.

A small addendum:

The use of D-PATH Domain IDs for loop detection purposes are split in the
document.

Section 4.d which defines D-PATH mentions two properties:
1. When a looped entry, having been received, may be considered for use even
when it is looped.
2. It MUST NOT be exported.

In traditional BGP-speak, it MAY be eligible circumstantially for selection
in the LocRib, but is ineligible for placement into the AdjRibsOut.

Section 6 covers the changes to route selection when D-PATH is present for
the different forms of ISF routes.  This parallels BGP's route selection
text in RFC 4271, Section 9.1.2.  However, BGP's section discusses the AS
loops as part of that section.

I'd recommend that a portion of the text relating to route selection and
loops be placed in the ipvpn document's section 6.  Having all of the rules
in a single place will likely avoid certain classes of implementation bugs
and will ease in citation of the rules for the future.

-- Jeff