fantel
bofreq-geng-fantel-03
| Document | Type | Proposed BOF request Snapshot | |
|---|---|---|---|
| Title | fantel | ||
| Last updated | 2024-12-25 | ||
| State | Proposed | ||
| Editor | Xuesong Geng | ||
| Responsible leadership | |||
| Send notices to | (None) |
Name: Fast Notification for Traffic Engineering and Load Balancing (fantel)
Description
The fantel BOF (Fast Notification for Traffic Engineering and Load Balancing) aims to discuss notification mechanisms in adaptive/perceptive routing to address dynamic traffic protection, congestion, and performance issues. It focuses on the requirements of fast notification for efficient routing decisions based on real-time network sensing and conditions, facilitating more responsive traffic engineering and load balancing.
Required Details
- Status: non WG Forming
- Responsible AD: James Guichard
- BOF proponents: Xuesong Geng <gengxuesong@huawei.com>, Tianran Zhou <zhoutianran@huawei.com>
- Number of people expected to attend: 100
- Length of session (1 or 2 hours): 2 hours
- Conflicts (whole Areas and/or WGs)
- Chair Conflicts: RTGWG/IDR/LSR
- Technology Overlap: Traffic Engineering, Load Balancing, Failure Protection, Congestion Avoidance
- Key Participant Conflict: John Scudder, Gunter van de Velde, Jeff Tantsura, Yingzhen Qu, Acee Lindem, Christian Hopps, Jeffrey Haas, Keyur Patel, Susan Hares
Information for IAB/IESG
Ongoing efforts in adaptive and perceptive routing are being explored in WGs like RTGWG, LSR, and IDR. However, these efforts are scattered across different WGs without sufficient alignment. These works are closely related to the fast notification mechanism we plan to discuss, but there is no consensus on terminology, solutions, or standard requirements in this topic, underscoring the need for further discussion and alignment with BOF .
-
Which (if any) modifications to existing protocols or practices are required; Which (if any) entirely new protocols or practices are required:
Several existing documents discuss potential solutions for fast notification, which could be implemented using IGP or BGP extensions. Fantel could be realized by modifying existing protocols or, if necessary, introducing a new protocol in different deployment scenarios. -
Existing implementation about this work:
There are some private implementations of this work within data centers. Additionally, several tests are currently under discussion, based on existing documents, to explore and validate potential solutions for fast notification.
Agenda
- Fantel Use Case
- Gap Analysis
- Potential Solutions for fantel
Links to the mailing list, draft charter if any, relevant Internet-Drafts, etc.
- Mailing List: fantel@ietf.org
- Relevant Internet-Drafts: