RFC 5853: Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) Deployments
In plain English — editorial summary, not part of the RFC
This document describes functions implemented in Session Initiation Protocol (SIP) intermediaries known as Session Border Controllers (SBCs). The goal of this document is to describe the commonly provided functions of SBCs. A special focus is given to those practices that are viewed to be in conflict with SIP architectural principles. This document also explores the underlying requirements of network operators that have led to the use of these functions and practices in order to identify protocol requirements and determine whether those requirements are satisfied by existing specifications or if additional standards work is required. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5853
- Published
- April 2010
- Authors
- J. Hautakorpi; G. Camarillo; R. Penfield; A. Hawrylyshen; M. Bhatia
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 26
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5850A Call Control and Multi-Party Usage Framework for the Session Initiation Protocol (SIP)Current
May 2010
- RFC 5870A Uniform Resource Identifier for Geographic Locations ('geo' URI)Current
June 2010
- RFC 5874An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) ResourcesCurrent
May 2010
- RFC 5875An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event PackageCurrent
May 2010
- RFC 5876Updates to Asserted Identity in the Session Initiation Protocol (SIP)Current
April 2010
- RFC 5897Identification of Communications Services in the Session Initiation Protocol (SIP)Current
June 2010
- RFC 5808Requirements for a Location-by-Reference MechanismCurrent
May 2010
- RFC 5922Domain Certificates in the Session Initiation Protocol (SIP)Current
June 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?