<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.campbell-dime-load-considerations" target="https://datatracker.ietf.org/doc/html/draft-campbell-dime-load-considerations-01">
   <front>
      <title>Architectural Considerations for Diameter Load Information</title>
      <author initials="B." surname="Campbell" fullname="Ben Campbell">
         <organization>Oracle</organization>
      </author>
      <author initials="S." surname="Donovan" fullname="Steve Donovan">
         <organization>Oracle</organization>
      </author>
      <author initials="J." surname="Trottin" fullname="Jean-Jacques Trottin">
         <organization>Alcatel-Lucent</organization>
      </author>
      <date month="March" day="9" year="2015" />
      <abstract>
	 <t>   RFC 7068 describes requirements for Overload Control in Diameter.
   This includes a requirement to allow Diameter nodes to send &quot;load&quot;
   information, even when the node is not overloaded.  The Diameter
   Overload Information Conveyance (DOIC) solution describes a mechanism
   meeting most of the requirements, but does not currently include the
   ability to send load information.  This document explores some
   architectural considerations for a mechanism to send Diameter load
   information.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-campbell-dime-load-considerations-01" />
   
</reference>
