IETF Logo Mail Archive

[bess] Do we need yet another link bandwidth community?

Ketan Talaulikar <ketant.ietf@gmail.com> Wed, 24 July 2024 21:55 UTC

Return-Path: <ketant.ietf@gmail.com>
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 B2340C1CAE77; Wed, 24 Jul 2024 14:55:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=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] 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 ddmi6fwjt0cY; Wed, 24 Jul 2024 14:55:52 -0700 (PDT)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B1EDC1CAE7D; Wed, 24 Jul 2024 14:55:49 -0700 (PDT)
Received: by mail-lf1-x12d.google.com with SMTP id 2adb3069b0e04-52efba36802so271634e87.2; Wed, 24 Jul 2024 14:55:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721858147; x=1722462947; darn=ietf.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=KAObjv6ct+XYwrz8WW13MDjhrh6ykH9aANKkAW453ZI=; b=MeoulwDJxpYYUmbd9USaqcOWEOYVYJnKZdE9lDouwxGaKnuHdrdLMvuOxLk2DkEf28 Ihfo9s5djOcnXJoDIOQqIA4TYNeXFQIF3yuz0GMfU8fzkvph36LfmMdddghHwAanzeGW 62W4WPSktKLs5vYalkn0oA3WbenMaQb+D2EuOGzJIsjRZL/0udZQHIyuHrvLugYfgvtp WGIgaemacR98VKu/MSnN5QJBG64wC40qfTZomVc/K1Pt/g3LiZzH3ORQ7g90PPr6+Vj7 sRssvC/jfTJYRflLLM8CmYEnxVAzWdDCGwkjYie/VSZ9LcWo/3wIOI7Utd2f/KKVBhbL B0kg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721858147; x=1722462947; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=KAObjv6ct+XYwrz8WW13MDjhrh6ykH9aANKkAW453ZI=; b=pmEWIY70aJh3hon19S8rbOLAfvzgpsOa+w86EZ9iHOZc8jnbdlsw4C7DNte61dNWva j1eUxEwO4Usfo009XdtztyNqt6zF0BvtnnehoZ/PJFwJnzE9GLSaHyTE05XPVzsDqPAD bx9cQatxGPxtc5nqJ8z/TXovFsO59MBSWBc9NR2xR1wpGnTP0UiWRvUfVk9Wrvk0dW3W J9aaY/TBe2yHKCeWQJ2yh24mE9RfPwbk08DPcpNGL1kl0nq25zgZrELVhEZrgho28A3Q uxYi9ujiVAQ1d80uOHXAwuFR37sSKlG5h4MHkiX7pSMmTydtGqvmWRp4UKliYd3l2bIX mAcg==
X-Forwarded-Encrypted: i=1; AJvYcCX+1QphkSdJ0xtvyiEuJh3m2UjG2Z6vp96zYgVD+Xl7cAVqxg60pU2NXksN6dtc4fncjcC6uBgaUwMPrOSH8o94jnO4agkPuhgwO2Ko7EPgOZZp3y8Fr7QU
X-Gm-Message-State: AOJu0YxWO69wT+4yRrtiV9T7flSlYw2Kk5qBYF9jj+7AL4+inN4i/tZ4 umz1TEVTiehql6zveXBMdN90KaPB4fV1viX2Dd3PLBLdxRKZXS1FSeA0z3t9sv6Q3bPET76W1wG ACRistUEI9e5ir1kTiEL6EZqryDskWzyVebajNQ==
X-Google-Smtp-Source: AGHT+IFBHjLhhjCpvEwl+92U3W7U2rqRTCTaEHjuTBtLlABKLyR9gXU7YDZcFa/ZhA3n3Io+vQyR1dFR79CoReyTBu8=
X-Received: by 2002:a05:6512:3e1b:b0:52c:a88b:9997 with SMTP id 2adb3069b0e04-52fd3f7cf35mr674930e87.49.1721858146495; Wed, 24 Jul 2024 14:55:46 -0700 (PDT)
MIME-Version: 1.0
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Wed, 24 Jul 2024 14:55:35 -0700
Message-ID: <CAH6gdPxxsb+6v6ZGjAB=7ZVNK8+0KWs3Aa6RMJArEtMp+ddbrw@mail.gmail.com>
To: "idr@ietf. org" <idr@ietf.org>, draft-li-idr-link-bandwidth-ext@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002cf9a3061e05574b"
Message-ID-Hash: ZNIKHXUIDIHU5N45N6KK2GCZM2QHPBUB
X-Message-ID-Hash: ZNIKHXUIDIHU5N45N6KK2GCZM2QHPBUB
X-MailFrom: ketant.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-bess.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: BESS <bess@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [bess] Do we need yet another link bandwidth community?
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/oRAFfV-YrmUMcKmRdjA6Z-dCRhY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Owner: <mailto:bess-owner@ietf.org>
List-Post: <mailto:bess@ietf.org>
List-Subscribe: <mailto:bess-join@ietf.org>
List-Unsubscribe: <mailto:bess-leave@ietf.org>

Hello All,

Checking on the need for draft-li-idr-link-bandwidth-ex when we already
have the EVPN Link Bandwidth Extended Community
(draft-ietf-bess-evpn-unequal-lb). Is it because of the name containing
"EVPN" or am I missing something?

If it is just the name, I hope we still have the time to change it in
draft-ietf-bess-evpn-unequal-lb?

We already have 2 types (ignoring the transitive/non-transitive variants)
and I hope we can avoid the need for a third one ...

Thanks,
Ketan

v2.26.15 | Report a Bug | By Email | System Status