Subject: [sip-overload] RFC 6357 on Design Considerations for Session Initiation Protocol (SIP) Overload Control

From: [email-masked]
Date: Wed, 31 Aug 2011 14:36:57 -0700 (PDT)

A new Request for Comments is now available in online RFC libraries.

        RFC 6357

        Title:      Design Considerations for Session Initiation 
                    Protocol (SIP) Overload Control 
        Author:     V. Hilt, E. Noel,
                    C. Shen, A. Abdelal
        Status:     Informational
        Stream:     IETF
        Date:       August 2011
        Mailbox:    [email-masked], 
                    [email-masked], 
                    [email-masked], 
                    [email-masked]
        Pages:      25
        Characters: 64252
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-soc-overload-design-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6357.txt

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.

This document is a product of the SIP Overload Control Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC