[Idr] Re: draft-ietf-idr-link-bandwidth
Jeffrey Haas <jhaas@pfrc.org> Mon, 22 July 2024 20:23 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 09149C14F602 for <idr@ietfa.amsl.com>; Mon, 22 Jul 2024 13:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 RBS5-iB6BpJu for <idr@ietfa.amsl.com>; Mon, 22 Jul 2024 13:23:47 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 292AAC14F5E9 for <idr@ietf.org>; Mon, 22 Jul 2024 13:23:46 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 71F291E28C; Mon, 22 Jul 2024 16:23:46 -0400 (EDT)
Date: Mon, 22 Jul 2024 16:23:46 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Donatas Abraitis <donatas.abraitis@gmail.com>
Message-ID: <20240722202346.GA12387@pfrc.org>
References: <AS2PR02MB883985E02A8FCAB794BD8CA0F0A82@AS2PR02MB8839.eurprd02.prod.outlook.com> <CAPF+HwUvnUrwRN+4_0GY1809wwFj1Hq=v+eNYBW7-fNP38-tUg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAPF+HwUvnUrwRN+4_0GY1809wwFj1Hq=v+eNYBW7-fNP38-tUg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Message-ID-Hash: B37STBYQAWYM4HVKHEJ4UHAHFY7U6JKW
X-Message-ID-Hash: B37STBYQAWYM4HVKHEJ4UHAHFY7U6JKW
X-MailFrom: jhaas@slice.pfrc.org
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: bruno.decraene@orange.com, idr <idr@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: draft-ietf-idr-link-bandwidth
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/NvsE1_3G8FLw6HUIhR3gzjoRDBk>
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>
Donatas, On Mon, Jul 22, 2024 at 09:43:53PM +0300, Donatas Abraitis wrote: > Speaking from the FRRouting field, FRR supports both drafts. > > P.S. TBH, I'd support "draft-li-idr-link-bandwidth-ext" rather than > "draft-ietf-idr-link-bandwidth". > It might be useful to share how your implementation deals with conflicting link-bw and link-bw-ext state in the route. One of the items the link-bw authors have been requested to include in their forthcoming update is reconciling the case where more than one type is present. Another thing that would be useful to hear is whether FRR provides a mechanism to map link-bw-ext between link-bw. If so, what's your strategy to deal with precision errors due to rounding? -- Jeff
- [Idr] draft-ietf-idr-link-bandwidth bruno.decraene
- [Idr] Re: draft-ietf-idr-link-bandwidth Donatas Abraitis
- [Idr] Re: draft-ietf-idr-link-bandwidth Donatas Abraitis
- [Idr] Re: draft-ietf-idr-link-bandwidth Jeffrey Haas
- [Idr] Re: draft-ietf-idr-link-bandwidth Jeffrey Haas
- [Idr] Re: draft-ietf-idr-link-bandwidth Donatas Abraitis
- [Idr] Re: draft-ietf-idr-link-bandwidth Reshma Das