[bess] IDR Interim meeting 23 September, 2024 (was [Idr] Four IDR Interims planned prior to IETF-121 in Dublin)

Jeffrey Haas <jhaas@pfrc.org> Tue, 17 September 2024 22:48 UTC

Return-Path: <jhaas@pfrc.org>
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 7F240C1840FA for <bess@ietfa.amsl.com>; Tue, 17 Sep 2024 15:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
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 eYCnkD7kNPej for <bess@ietfa.amsl.com>; Tue, 17 Sep 2024 15:48:15 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 860F6C1CAE75 for <bess@ietf.org>; Tue, 17 Sep 2024 15:48:15 -0700 (PDT)
Received: from smtpclient.apple (172-125-100-52.lightspeed.livnmi.sbcglobal.net [172.125.100.52]) by slice.pfrc.org (Postfix) with ESMTPSA id 3DE901E2D5; Tue, 17 Sep 2024 18:48:15 -0400 (EDT)
From: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2AA2B78B-F048-4604-8A61-1189EE31C149"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.8\))
Date: Tue, 17 Sep 2024 18:48:14 -0400
References: <C0FF5E1B-9F64-4027-B185-A5F0B950D19B@pfrc.org>
To: bess@ietf.org
Message-Id: <FBE5EF20-70B5-415E-9048-12D907F945ED@pfrc.org>
X-Mailer: Apple Mail (2.3696.120.41.1.8)
Message-ID-Hash: RGXXI2TKNNFAC3RFGLGOS5V2ZSBB646N
X-Message-ID-Hash: RGXXI2TKNNFAC3RFGLGOS5V2ZSBB646N
X-MailFrom: jhaas@pfrc.org
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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [bess] IDR Interim meeting 23 September, 2024 (was [Idr] Four IDR Interims planned prior to IETF-121 in Dublin)
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/1M5JCzvqOfgA7Ek__oB3OE7cVUo>
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>

BESS Working Group,

IDR will be holding an interim meeting this coming Monday.  Two bess WG documents covering the BGP link bandwidth functionality are on the agenda to be discussed.

We hope to see you at the meeting next week.

-- Jeff


> Begin forwarded message:
> 
> From: Jeffrey Haas <jhaas@pfrc.org>
> Subject: Interim meeting 23 September, 2024 (was [Idr] Four IDR Interims planned prior to IETF-121 in Dublin)
> Date: September 17, 2024 at 6:38:54 PM EDT
> To: idr wg <idr@ietf.org>
> 
> Working Group,
> 
> This is a reminder that we have an upcoming IDR interim meeting this coming Monday, 23 September, 2024.  Our topics for this upcoming interim are below along with their associated drafts.
> 
> We look forward to productive discussions on these topics!
> 
> The URL for the meeting is:
> https://datatracker.ietf.org/meeting/interim-2024-idr-12/session/idr <https://datatracker.ietf.org/meeting/interim-2024-idr-12/session/idr>
> 
> 
> -- Jeff
> 
> 
>> Begin forwarded message:
>> 
>> From: Susan Hares <shares@ndzh.com <mailto:shares@ndzh.com>>
>> 
>> IDR WG chairs have planned the following four interims before  IETF-121.
>> We hope this will help make our work at IETF-121 highly interactive and productive.
>>  
>> Interims:
>> [...]
> 
>> #2 interim – September 23, 2024 - BGP Next Hop + BGP Bandwidth Discussions
>> Link (denoted as: Interim-12)
>> https://datatracker.ietf.org/meeting/interim-2024-idr-12/session/idr <https://datatracker.ietf.org/meeting/interim-2024-idr-12/session/idr>
>> Time: 10-12:30 pm EDT (expected duration 1.5-2 hours)
>>  
>> Description: During IETF-120 and in emails afterward, we had discussions on the following;
>> a. BGP next Hop Features, and b. Link Bandwidth.
>> This interim will discuss the potential solutions for each.
>>  
>> Agenda:
>> 1. BGP Next Hop Features from the following drafts [45-60 minutes]
>>   draft-ietf-idr-multinexthop-attribute-01
>>   draft-ssangli-idr-bgp-generic-metric-00
>>   draft-ietf-idr-entropy-label-14
>>  
>> 2. BGP Link Bandwidth [30-45 minutes]
>>     This work has two types of work:  Fixing the transitive/non-transitive community and new work.
>>     The drafts related to bandwidth include the following: 
>>      draft-ietf-idr-link-bandwidth-07,
>>      draft-ietf-bess-ebgp-dmz
>>      draft-ietf-bess-evpn-unequal-lb
>>      draft-li-idr-link-bandwidth-ext/02/
>>      draft-xu-idr-fare-01
>