Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP)
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 36
- Abstract
- The 3rd-Generation Partnership Project (3GPP) has selected Session Initiation Protocol (SIP) as the session establishment protocol for the 3GPP IP Multimedia Core Network Subsystem (IMS). IMS is part of Release 5 of the 3GPP specifications. Although SIP is a protocol that fulfills most of the requirements for establishing a session in an IP network, SIP has never been evaluated against the specific 3GPP requirements for operation in a cellular network. In this document, we express the requirements identified by 3GPP to support SIP for Release 5 of the 3GPP IMS in cellular networks. This memo provides information for the Internet community.
- Publication Date
- 2005-05-01
- Status Note
- Informational
- DOI
10.17487/RFC4083- Link
- https://doi.org/10.17487/RFC4083
- Author(s)
- Miguel Angel García
- Keyword(s)
- 3GPP IP Multimedia Core Network Subsystem, IMS, Cellular Networks
Latest version of IETF RFC 4083
Document Versions — IETF RFC 4083
-
▶ IETF RFC 4083 (2005-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3261 [Active*]
Bibliographic Reference(s)
- 3GPP.TS-23.003.200209 — 26 EXTERNAL
- 3GPP.TS-23.060.200209 — 27 EXTERNAL
- 3GPP.TS-23.228.200209 — 14 EXTERNAL
- 3GPP.TS-24.228.200209 — 29 EXTERNAL
- 3GPP.TS-24.229.200209 — 15 EXTERNAL
- 3GPP.TS-32.203.200209 — 32 EXTERNAL
- 3GPP.TS-32.210.200209 — 33 EXTERNAL
- 3GPP.TS-32.225.200209 — 17 EXTERNAL
- Sparks, R., "Session Initiation Protocol Call Control - Transfer", Work in Progress, February 2005. EXTERNAL
- Johnston, A. and R. Sparks, "Session Initiation Protocol Service Examples", Work in Progress, February 2005. EXTERNAL
- IETF RFC 2246 [Superseded*]
- IETF RFC 2396 [Superseded*]
- IETF RFC 2401 [Superseded*]
- IETF RFC 2486 [Superseded*]
- IETF RFC 2828 [Superseded*]
- IETF RFC 2833 [Superseded*]
- IETF RFC 2916 [Superseded*]
- IETF RFC 3263 [Active*]
- IETF RFC 3264 [Active*]
- IETF RFC 3265 [Superseded*]
- IETF RFC 3310 [Active*]
- IETF RFC 3312 [Active*]
- IETF RFC 3313 [Active*]
- IETF RFC 3319 [Active*]
- IETF RFC 3323 [Active*]
- IETF RFC 3325 [Active*]
- IETF RFC 3515 [Active*]
- IETF RFC 3665 [Active*]
- IETF RFC 3666 [Active*]
- IETF RFC 3680 [Active*]
- IETF RFC 3891 [Active*]
- IETF RFC 3966 [Active*]
- T-REC-E.164.1997 — E.164 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4083.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 4083, Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC4083
Snippet:
IETF RFC 4083, Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC4083
HTML (ISO 690 compliant)
Preview:
IETF RFC 4083, Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC4083
Snippet:
<span class="citation"><cite>IETF RFC 4083</cite>, Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP). Available at <a href="https://doi.org/10.17487/RFC4083" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4083</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4083, Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP)
doi: 10.17487/RFC4083
url: https://doi.org/10.17487/RFC4083
doi: 10.17487/RFC4083
url: https://doi.org/10.17487/RFC4083
Snippet:
<li> <cite id="bib-rfc4083">IETF RFC 4083</cite>, Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP) <span class="doi">10.17487/RFC4083</span> </li>
Referenced By
- IETF RFC 7315 [Active*]