RFC 4083: Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC4083
- Published
- May 2005
- Authors
- M. Garcia-Martin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 36
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5552SIP Interface to VoiceXML Media ServicesCurrent
May 2009
- RFC 5767User-Agent-Driven Privacy Mechanism for SIPCurrent
April 2010
- RFC 4457The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-Header)Current
April 2006
- RFC 5002The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)Updated
August 2007
- RFC 5009Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early MediaCurrent
September 2007
- RFC 5688A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application SubtypesCurrent
January 2010
- RFC 6043MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY)Updated
March 2011
- RFC 7255Using the International Mobile station Equipment Identity (IMEI) Uniform Resource Name (URN) as an Instance IDCurrent
May 2014
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?