[Idr] BGP-LS Flex Algo Extensions draft submitted to catch up with LSR work

Ketan Talaulikar <ketant.ietf@gmail.com> Fri, 18 October 2024 09:07 UTC

Return-Path: <ketant.ietf@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 5A9FAC151535; Fri, 18 Oct 2024 02:07:33 -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, FREEMAIL_FROM=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=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 prlz_MM-LD1g; Fri, 18 Oct 2024 02:07:29 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 878C1C151086; Fri, 18 Oct 2024 02:07:29 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id d9443c01a7336-20ca388d242so13906215ad.2; Fri, 18 Oct 2024 02:07:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729242449; x=1729847249; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Pacdnc5nlPWktDPJJyWlqAQobhpaqNRdC/m46fBGR60=; b=bonidkDj5KVSr3tPhcFwegarBaj8257X6DL5LSQJiF4ESbOOQXBIjOJEb5K3IKYpJo C5dskCs1D3HrBS4009NwErydFEoGMmGSTtgeUnuWQTKU1OI5quv0nJs8tThqcl2ByDpN /d4MFCf98v4pLVWP5eg6FlAbjz+PYZbHa7FH4OGrXcqP/dJpBnsUPQ/ZCqMOMQ32zjot TvIoftPqVRwzc1DWweO/rjS5a3Z1u1zlffpflim1/8fgTPE+6teFuLtpXV3EJa52Gu7m lCyhPDvJiFZEwdi0ramU2/v8mewlRnEazAe57vUMYs+3WPPwBNB40LhXrIxtxr3cpWCG CLWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729242449; x=1729847249; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Pacdnc5nlPWktDPJJyWlqAQobhpaqNRdC/m46fBGR60=; b=RR5eKhXVSzs8U/LAZHX7Mjl1l8QrR5NwzmEUtLJB39DPAo7NqUxJcOdlr4mPTAYvWT OOvhzqGts6s9Lp/1n4D6Q5T4WhNtZrIUMd4tZ6M76w6VNJQnjEVl6gjgA/2ivYXGxrUx VmW1PF3HIl3N3V7noH8cM6vT7DtjJhm+5e3TCamhZIIIBKpSxa3V9c/79rkKoxeu46wF Ek9ZBXRbwILKFg2galzQvW3+SzZOUhG4+qg8bzZIG6wbxLMCFnysTsA9QownMVSIGO+8 W0KClfBLJn6MeBEj1YT2+AtdLOHshmUbf+144nwAFWnsGPaZCrZTKESETGQj90l/slmc LLBg==
X-Gm-Message-State: AOJu0YygGZrALMhLfMIj+XRcB5YUoSSFUHHk/XNc9rs6stjgg6kCHwlK 76xZYiWgrXtU5hYozkx8WkF8H9YXJxVCII3e64dfbzOtIawgG4XX4bgKb/Alm2LGEO8iKh9WZMj QY5z8MBt3tFNNHcPePyyeIBWnl45I0XmT
X-Google-Smtp-Source: AGHT+IHXtyb06lvv1iZQR3mz8Eis6hMeKJEidjd0RlIJC1mJSD3A4p9TjTfkwTrSzs15Woaoq6bkxQdaofdwLrirvdY=
X-Received: by 2002:a17:903:32c9:b0:20c:7d7d:7ba8 with SMTP id d9443c01a7336-20e5a9508acmr22653475ad.46.1729242448634; Fri, 18 Oct 2024 02:07:28 -0700 (PDT)
MIME-Version: 1.0
References: <172924091815.1512602.15735030091934052857@dt-datatracker-78dc5ccf94-w8wgc>
In-Reply-To: <172924091815.1512602.15735030091934052857@dt-datatracker-78dc5ccf94-w8wgc>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Fri, 18 Oct 2024 14:37:16 +0530
Message-ID: <CAH6gdPxTVaFXt4Fk2y1FyvM_2qQUi4u0diPGsrGY2KwTeu14Tg@mail.gmail.com>
To: "idr@ietf. org" <idr@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: VVKNOKTVDEGPNNZUEYA2TXWPDKD6EIOE
X-Message-ID-Hash: VVKNOKTVDEGPNNZUEYA2TXWPDKD6EIOE
X-MailFrom: ketant.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: lsr <lsr@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] BGP-LS Flex Algo Extensions draft submitted to catch up with LSR work
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3dxi-4Tei9rmIjLw6l7_LzMNW0M>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Hello IDR WG,

We've posted a "routine" BGP-LS draft that includes extensions for
conveying some of the more recent Flex Algo IGP extensions defined by
the LSR WG into BGP-LS.

https://datatracker.ietf.org/doc/draft-hegdearavind-idr-bgp-ls-flex-algo-ext/

These are extensions beyond the base Flex Algo spec which was covered
by the BGP-LS RFC9351

This document catches up with the following LSR WG documents:
- IP Flex Algo: https://datatracker.ietf.org/doc/rfc9502/
- https://datatracker.ietf.org/doc/draft-ietf-lsr-flex-algo-bw-con/
- https://datatracker.ietf.org/doc/draft-ietf-lsr-igp-flex-algo-reverse-affinity/

Request the WG to review and provide feedback/comments. Also including LSR WG.

Given that these are straightforward BGP-LS extensions that are
aligned with and in continuation of RFC9552 and RFC9351, we would like
to ask for IDR WG adoption. We can also present this during the IDR
session at IETF 121 if required and if time allows.

Thanks,
Ketan (on behalf of all co-authors)

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Fri, Oct 18, 2024 at 2:11 PM
Subject: New Version Notification for
draft-hegdearavind-idr-bgp-ls-flex-algo-ext-00.txt
To: Aravind Babu MahendraBabu <aramahen@cisco.com>, Bruno Decraene
<bruno.decraene@orange.com>, Ketan Talaulikar <ketant.ietf@gmail.com>,
Peter Psenak <ppsenak@cisco.com>, Shraddha Hegde
<shraddha@juniper.net>


A new version of Internet-Draft
draft-hegdearavind-idr-bgp-ls-flex-algo-ext-00.txt has been successfully
submitted by Ketan Talaulikar and posted to the
IETF repository.

Name:     draft-hegdearavind-idr-bgp-ls-flex-algo-ext
Revision: 00
Title:    Advertising Flexible Algorithm Extensions in BGP Link-State
Date:     2024-10-18
Group:    Individual Submission
Pages:    16
URL:      https://www.ietf.org/archive/id/draft-hegdearavind-idr-bgp-ls-flex-algo-ext-00.txt
Status:   https://datatracker.ietf.org/doc/draft-hegdearavind-idr-bgp-ls-flex-algo-ext/
HTMLized: https://datatracker.ietf.org/doc/html/draft-hegdearavind-idr-bgp-ls-flex-algo-ext


Abstract:

   Flexible Algorithm is a solution that allows some routing protocols
   (e.g., OSPF and IS-IS) to compute paths over a network based on user-
   defined (and hence, flexible) constraints and metrics.  The
   computation is performed by routers participating in the specific
   network in a distributed manner using a Flexible Algorithm
   Definition.  This Definition is provisioned on one or more routers
   and propagated through the network by OSPF and IS-IS flooding.

   BGP Link-State (BGP-LS) enables the collection of various topology
   information from the network.  BGP-LS supports the advertisement of
   Flexible Algorithm Definition and other Flexible Algorithm related
   advertisements as a part of the topology information from the
   network.  This document specifies the advertisement of further
   Flexible Algorithm related extensions in BGP-LS.



The IETF Secretariat