<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-soc-overload-design" target="https://datatracker.ietf.org/doc/html/draft-ietf-soc-overload-design-08">
   <front>
      <title>Design Considerations for Session Initiation Protocol (SIP) Overload Control</title>
      <author initials="V." surname="Hilt" fullname="Volker Hilt">
         <organization>Bell Labs/Alcatel-Lucent</organization>
      </author>
      <author initials="E." surname="Noel" fullname="Eric Noel">
         <organization>AT&amp;T Labs</organization>
      </author>
      <author initials="C." surname="Shen" fullname="Charles Shen">
         <organization>Columbia University</organization>
      </author>
      <author initials="A." surname="Abdelal" fullname="Ahmed Abdelal">
         <organization>Sonus Networks</organization>
      </author>
      <date month="July" day="11" year="2011" />
      <abstract>
	 <t>Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive.  Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload.  This document discusses models and design considerations for a SIP overload control mechanism.  This document is not an Internet Standards Track specification; it is published for informational purposes.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-soc-overload-design-08" />
   
</reference>
