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

 
Document
Type Expired Internet-Draft (individual)
Last updated 2015-01-04 (latest revision 2014-07-03)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-deng-mif-api-session-continuity-guide-04.txt

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

Hui Deng (denghui02@gmail.com)
Suresh Krishnan (suresh.krishnan@ericsson.com)
Ted Lemon (ted.lemon@nominum.com)
Margaret Wasserman (mrw@painless-security.com)

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