Skip to main content

Guide for application developers on session continuity by using MIF API
draft-deng-mif-api-session-continuity-guide-03

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
Authors DENG Hui , Suresh Krishnan , Ted Lemon , Margaret Cullen
Last updated 2013-04-25 (Latest revision 2012-10-22)
RFC stream (None)
Formats
Additional resources
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

Today most smart terminals are equiped with multiple interfaces such as 3G/LTE and WiFi, and users experience some loss of connectivity while switching interfaces. The MIF API draft [I-D.ietf-mif-api-extension] has specified an API to announce interface status information to the applications. Once the application receives such information, it can use this information reconnect to its peer(s), and this could significantly improve the user experience.

Authors

DENG Hui
Suresh Krishnan
Ted Lemon
Margaret Cullen

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)