<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.mcmurry-dime-overload-reqs" target="https://datatracker.ietf.org/doc/html/draft-mcmurry-dime-overload-reqs-02">
   <front>
      <title>Diameter Overload Control Requirements</title>
      <author initials="E." surname="McMurry" fullname="Eric McMurry">
         <organization>Tekelec</organization>
      </author>
      <author initials="B." surname="Campbell" fullname="Ben Campbell">
         <organization>Tekelec</organization>
      </author>
      <date month="August" day="28" year="2012" />
      <abstract>
	 <t>   When a Diameter server or agent becomes overloaded, it needs to be
   able to gracefully reduce its load, typically by informing clients to
   reduce sending traffic for some period of time.  Otherwise, it must
   continue to expend resources parsing and responding to Diameter
   messages, possibly resulting in congestion collapse.  The existing
   mechanisms provided by Diameter are not sufficient for this purpose.
   This document describes the limitations of the existing mechanisms,
   and provides requirements for new overload management mechanisms.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-mcmurry-dime-overload-reqs-02" />
   
</reference>
