RFC 7200: A Session Initiation Protocol (SIP) Load-Control Event Package
In plain English — editorial summary, not part of the RFC
This specification defines a load-control event package for the Session Initiation Protocol (SIP). It allows SIP entities to distribute load-filtering policies to other SIP entities in the network. The load-filtering policies contain rules to throttle calls from a specific user or based on their source or destination domain, telephone number prefix. The mechanism helps to prevent signaling overload and complements feedback-based SIP overload control efforts.
Document record
- Document ID
- RFC7200
- Published
- April 2014
- Authors
- C. Shen; H. Schulzrinne; A. Koike
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 44
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7339Session Initiation Protocol (SIP) Overload ControlCurrent
September 2014
- RFC 9506Explicit Host-to-Network Flow Measurements TechniquesCurrent
October 2023
- RFC 6914SIMPLE Made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence Using the Session Initiation Protocol (SIP)Current
April 2013
- RFC 6404Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested CountermeasuresCurrent
November 2011
- RFC 6357Design Considerations for Session Initiation Protocol (SIP) Overload ControlCurrent
August 2011
- RFC 6080A Framework for Session Initiation Protocol User Agent Profile DeliveryCurrent
March 2011
- RFC 6035Session Initiation Protocol Event Package for Voice Quality ReportingCurrent
November 2010
- RFC 5954Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261Current
August 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?