[Idr] BGP routes with color, Question 2: Route origination and propagation

Jeffrey Haas <jhaas@pfrc.org> Fri, 18 February 2022 15:44 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 5D0AC3A10E0 for <idr@ietfa.amsl.com>; Fri, 18 Feb 2022 07:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FvygL_0rXKtg for <idr@ietfa.amsl.com>; Fri, 18 Feb 2022 07:44:16 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 791063A133E for <idr@ietf.org>; Fri, 18 Feb 2022 07:43:27 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id D00281E342; Fri, 18 Feb 2022 10:43:26 -0500 (EST)
Date: Fri, 18 Feb 2022 10:43:26 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: idr@ietf.org
Message-ID: <20220218154326.GV15589@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/4MYIFyHWITj8-Kk38AmKlkhh5b8>
Subject: [Idr] BGP routes with color, Question 2: Route origination and propagation
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 18 Feb 2022 15:44:19 -0000

As promised during the recent IDR interim, we want to start a set of threads
to the IDR mailing list to clarify points discussed during that interim
about the BGP routes with color proposals.  These questions are directed to
the authors of those proposals.  The responses to those questions will be
used to drive Working Group discussion about the solution space.


Question 2: Route origination and propagation.

A point of strong discussion during the recent IDR interim covering BGP
routes with color was related to where routes within a given proposal were
originated, and what their expected propagation was within the proposal.

Two examples during the discussion:
1. Origination of a route with color at an Autonomous System Border Router
(ASBR) for a domain containing an endpoint address.

2. Origination at the Provider Edge device hosting the endpoint.

There may be other scenarios.

A route-selection "pinch point" is any place in the BGP topology wherein
multiple paths for the same NLRI may be received, only one is selected, and
is propagated.  There is a loss of forwarding-diversity at such points under
some circumstances.  Mechanisms that permit additional BGP routes to be
propagated can address such loss of forwarding diversity.

With regard to propagation through route-selection pinch-points, the interim
discussion illustrated that there were differences of opinion as to when it
made sense at an ASBR to use next-hop-self or propagate more than one path
across the peering session.

The above inputs to the scenario(s) culminate in an ingress device having
one or more than one instances of the received path.

What is the default scenario you expect your proposal to use?

Are there situations where you may want to have origination or propagation
behave differently than your default scenario?  If so, how does that work?

Please illustrate the scenarios with a topology for discussion.

-- Jeff