Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7068
Discuss this RFC: Send questions or comments to the mailing listdime@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7068
When a Diameter server or agent becomes overloaded, it needs to beable to gracefully reduce its load, typically by advising clients toreduce traffic for some period of time. Otherwise, it must continueto expend resources parsing and responding to Diameter messages,possibly resulting in a progressively severe overload condition. Theexisting Diameter mechanisms are not sufficient for managing overloadconditions. This document describes the limitations of the existingmechanisms. Requirements for new overload management mechanisms arealso provided.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.