Supporting Service Mobility with SIP
draft-itsumo-sip-mobility-service-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Faramak Vakil | ||
| Last updated | 2000-11-17 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Session Initiation Protocol (SIP) can be used to provide means of personal, terminal, and service mobility in a mobile Internet. This document describes two schemes for supporting service mobility in a SIP environment. The first assumes that call states are maintained and stored within the network and home network always controls calls and services of its subscribers. The second assumes that call states are stored in the mobile stations (MSs) and managed in a distributed manner, and the visited network controls users' calls and services.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)