RFC 5923: Connection Reuse in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document enables a pair of communicating proxies to reuse a congestion-controlled connection between themselves for sending requests in the forwards and backwards direction. Because the connection is essentially aliased for requests going in the backwards direction, reuse is predicated upon both the communicating endpoints authenticating themselves using X.509 certificates through Transport Layer Security (TLS). For this reason, we only consider connection reuse for TLS over TCP and TLS over Stream Control Transmission Protocol (SCTP). This document also provides guidelines on connection reuse and virtual SIP servers and the interaction of connection reuse and DNS SRV lookups in SIP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5923
- Published
- June 2010
- Authors
- V. Gurbani; R. Mahy; B. Tate
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5922Domain Certificates in the Session Initiation Protocol (SIP)Current
June 2010
- RFC 5539NETCONF over Transport Layer Security (TLS)Obsoleted
May 2009
- RFC 5281Extensible Authentication Protocol Tunneled Transport Layer Security Authenticated Protocol Version 0 (EAP-TTLSv0)Updated
August 2008
- RFC 7590Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)Current
June 2015
- RFC 8253PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)Updated
October 2017
- RFC 3546Transport Layer Security (TLS) ExtensionsObsoleted
June 2003
- RFC 2712Addition of Kerberos Cipher Suites to Transport Layer Security (TLS)Current
October 1999
- RFC 9950A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+)Current
March 2026
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?