A mobility-related webpage is also maintained on the SIP Website. Check also the mobility documents. Note that many of these documents are coming from 3gpp crowd and may be designed for technologies other than the public Internet. They may or may not be accepted by the IETF. There is a Liason Statement from the IETF to 3GPP with some specific concerns about 3gpp arhictecture.
3gpp Collaboration
draft-ietf-v6ops-3gpp-cases
rfc3455
draft-ietf-sipping-3gpp-r5-requirements
draft-kiss-simple-presence-wireless-reqs
rfc3327
draft-ietf-sip-scvrtdisco
draft-allen-simple-msg-3gpp
draft-drage-3gpp-sip-registration
draft-drage-3gpp-sip-establish
draft-henrikson-sip-charging-information
draft-ietf-v6ops-3gpp-cases-03.txt
 |
"Transition Scenarios for 3GPP Networks", Jonne Soininen, 01-Apr-03,
This document describes different scenarios in Third Generation Partnership Project (3GPP) defined packet network, i.e. General Packet Radio Service (GPRS) that would need IP version 6 and IP version 4 transition. The focus of this document is on the scenarios where the User Equipment (UE) connects to nodes in other networks, e.g. in the Internet. GPRS network internal transition scenarios, i.e. between different GPRS elements in the network, are out of scope. The purpose of the document is to list the scenarios for further discussion and study. |
| rfc3455.txt | Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP) |
| Author(s) | M. Garcia-Martin, E. Henrikson, D. Mills |
| Organization | ietf |
| State | informational |
| Size | 79620 bytes |
| Abstract | This document describes a set of private Session Initiation Protocol (SIP) headers (P-headers) used by the 3rd-Generation Partnership Project (3GPP), along with their applicability, which is limited to particular environments. The P-headers are for a variety of purposes within the networks that the partners use, including charging and information about the networks a call traverses. |
| draft-ietf-sipping-3gpp-r5-requirements-00.txt | 3rd-Generation Partnership Project (3GPP) Release 5 requirements on the Session Initiation Protocol (SIP) |
| Author(s) | Miguel Garcia-Martin |
| Organization | ietf |
| Working group | sipping |
| State | unknown |
| Date | 2002-10-11 |
| Size | 80060 bytes |
| Abstract | The 3rd Generation Partnership Project (3GPP) has selected SIP [2]as the session establishment protocol for the 3GPP IP Multimedia Core Network Subsystem (IMS). IMS is part of the Release 5 of the 3GPP specifications. Although SIP is a protocol that fulfills most of the requirements to establish 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 the Release 5 of the 3GPP IMS in cellular networks. |
| draft-kiss-simple-presence-wireless-reqs-02.txt
|
"Requirements for Presence Service in 3GPP Wireless Systems", Krisztian
Kiss, 07-MAR-03, This Internet-Draft defines requirements for Presence Service in 3GPP wireless systems. |
| rfc3327.txt | Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts |
| Author(s) | D. Willis, B. Hoeneisen |
| Organization | ietf |
| State | proposed standard |
| Size | 36493 bytes |
| Abstract |
The REGISTER function is used in a Session Initiation Protocol (SIP)
system primarily to associate a temporary contact address with an
address-of-record. This contact is generally in the form of a
Uniform Resource Identifier (URI), such as Contact:
|
| draft-ietf-sip-scvrtdisco-04.txt
|
"Session Initiation Protocol Extension Header Field for Service Route
Discovery During Registration", Dean Willis, Bernie Hoeneisen, 14-MAY-03,
This document defines a SIP extension header field used in conjunction with responses to REGISTER requests to provide a mechanism by which a registrar may inform a registering UA of a service route that the UA may use to request outbound services from the registrar's domain. |
| draft-allen-simple-msg-3gpp-02.txt
|
| draft-drage-3gpp-sip-registration-01.txt
|
| draft-drage-3gpp-sip-establish-01.txt
|
| draft-henrikson-sip-charging-information-06.txt%
|