metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 5626: Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)

In plain English — editorial summary, not part of the RFC

The Session Initiation Protocol (SIP) allows proxy servers to initiate TCP connections or to send asynchronous UDP datagrams to User Agents in order to deliver requests. However, in a large number of real deployments, many practical considerations, such as the existence of firewalls and Network Address Translators (NATs) or the use of TLS with server-provided certificates, prevent servers from connecting to User Agents in this way. This specification defines behaviors for User Agents, registrars, and proxy servers that allow requests to be delivered on existing connections established by the User Agent. It also defines keep-alive behaviors needed to keep NAT bindings open and specifies the usage of multiple connections from the User Agent to its registrar. [STANDARDS-TRACK]

Document record

Document ID
RFC5626
Published
October 2009
Authors
C. Jennings; R. Mahy; F. Audet
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
50
Also known as
—
Updates:
RFC 3261, RFC 3327

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/5626-managing-client-initiated-connections-in-the-session-initiation-protocol-sip