Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 50
- Abstract
- 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]
- Publication Date
- 2009-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5626- Link
- https://doi.org/10.17487/RFC5626
- Author(s)
- Cullen Fluffy JenningsRohan MahyFrancois Audet
Latest version of IETF RFC 5626
Document Versions — IETF RFC 5626
-
▶ IETF RFC 5626 (2009-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2141 [Superseded*]
- IETF RFC 2506 [Active*]
- IETF RFC 3261 [Active*]
- IETF RFC 3263 [Active*]
- IETF RFC 3327 [Active*]
- RFC3581 — RFC3581 EXTERNAL
- IETF RFC 3629 [Active*]
- IETF RFC 3840 [Active*]
- IETF RFC 3841 [Active*]
- IETF RFC 3968 [Active*]
- IETF RFC 3969 [Active*]
- IETF RFC 4122 [Superseded*]
- IETF RFC 5234 [Active, Amended*]
- IETF RFC 5389 [Superseded*]
Bibliographic Reference(s)
- Petrie, D. and S. Channabasappa, Ed., "A Framework for Session Initiation Protocol User Agent Profile Delivery", Work in Progress, February 2008. EXTERNAL
- Boulton, C., Rosenberg, J., Camarillo, G., and F. Audet, "Best Current Practices for NAT Traversal for Client-Server SIP", Work in Progress, September 2008. EXTERNAL
- IETF RFC 768 [Active*]
- IETF RFC 793 [Superseded*]
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 2104 [Active, Amended*]
- IETF RFC 2131 [Active*]
- IETF RFC 2782 [Active*]
- RFC3320 — 2 EXTERNAL
- IETF RFC 3489 [Superseded*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 4340 [Active*]
- IETF RFC 4648 [Active*]
- IETF RFC 4960 [Superseded*]
- IETF RFC 5246 [Superseded*]
- RFC5627 — RFC5627 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5626.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5626, Managing Client-Initiated Connections in the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC5626
Snippet:
IETF RFC 5626, Managing Client-Initiated Connections in the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC5626
HTML (ISO 690 compliant)
Preview:
IETF RFC 5626, Managing Client-Initiated Connections in the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC5626
Snippet:
<span class="citation"><cite>IETF RFC 5626</cite>, Managing Client-Initiated Connections in the Session Initiation Protocol (SIP). Available at <a href="https://doi.org/10.17487/RFC5626" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5626</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5626, Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
doi: 10.17487/RFC5626
url: https://doi.org/10.17487/RFC5626
doi: 10.17487/RFC5626
url: https://doi.org/10.17487/RFC5626
Snippet:
<li> <cite id="bib-rfc5626">IETF RFC 5626</cite>, Managing Client-Initiated Connections in the Session Initiation Protocol (SIP) <span class="doi">10.17487/RFC5626</span> </li>
Referenced By
- IETF RFC 5630 [Active*]
- IETF RFC 6230 [Active*]
- IETF RFC 6443 [Active*]
- IETF RFC 6881 [Active*]
- IETF RFC 7254 [Active*]
- IETF RFC 7350 [Active*]
- IETF RFC 8489 [Active*]