[Idr] Re: draft-ietf-idr-link-bandwidth
Jeffrey Haas <jhaas@pfrc.org> Tue, 23 July 2024 06:57 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 E211FC1CAE7B for <idr@ietfa.amsl.com>; Mon, 22 Jul 2024 23:57:07 -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 fGvq-Z-EFGLj for <idr@ietfa.amsl.com>; Mon, 22 Jul 2024 23:57:07 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 35CBCC1CAE6A for <idr@ietf.org>; Mon, 22 Jul 2024 23:57:07 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id BBEC31E28C; Tue, 23 Jul 2024 02:57:06 -0400 (EDT)
Date: Tue, 23 Jul 2024 02:57:06 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Donatas Abraitis <donatas.abraitis@gmail.com>
Message-ID: <20240723065706.GC12387@pfrc.org>
References: <20240722202346.GA12387@pfrc.org> <37625A1E-BE34-48F6-846B-FE784917BAB0@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <37625A1E-BE34-48F6-846B-FE784917BAB0@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Message-ID-Hash: TRLIKV4GOAE475XVZ7FNA2TQMHB4FUN5
X-Message-ID-Hash: TRLIKV4GOAE475XVZ7FNA2TQMHB4FUN5
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/alGtg95Vz2AfiKCZAyUJPg0WBe8>
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>
On Tue, Jul 23, 2024 at 08:12:54AM +0300, Donatas Abraitis wrote: > >It might be useful to share how your implementation deals with conflicting > link-bw and link-bw-ext state in the route. > > Do you mean if both are carried (received)? Exactly that. -- 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