Update on Overload Control Draft for IETF 87: Requirements and Open Issues

Jan 05, 2026

50 likes | 171 Vues

This document outlines the updates to the Overload Control draft as it moves towards IETF 87. It includes reference updates, new additions, and a detailed requirements analysis. The second version introduces Appendix B, focusing on requirements compliance, while the third version highlights open issues related to scopes, origin-host, mandatory scopes, and naming clarifications. The next steps involve discussing ongoing issues, exploring use cases, and evaluating proposed mechanisms to ensure broad compliance. Feedback has been positive, and the working group aims for adoption.

wyman

Télécharger la présentation

Update on Overload Control Draft for IETF 87: Requirements and Open Issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

draft-roach-dime-overload-ctrl Update for IETF 87
Changes • Reference updates and additions • Requirements Analysis • Added in 02 version (Appendix B) • Requirements Compliance • In 03 version
Open Issues • Scopes • Origin-Host • Host • Session • Session Group • Mandatory scopes • Which (if any) should be?
Open Issues • Non-adjacent overload control • Default algorithm (drop or rate) • Naming (confusion on AVP names)
Next Steps • Progress open issues discussions • Explore details of use cases and evaluate against mechanism • Focus working group efforts • Time to adopt • Meets all but one requirement • Version at 3 • Good feedback • Ongoing discussions (including pulling in concepts from other drafts)