datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

MIF API consideration
draft-ietf-mif-api-extension-05

Document type: Active Internet-Draft (mif WG)
Document stream: IETF
Last updated: 2014-02-14
Intended RFC status: Unknown
Other versions: plain text, pdf, html

IETF State: WG Document
Revised I-D Needed - Issue raised by WG, Waiting for Referencing Document
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

MIF                                                               D. Liu
Internet-Draft                                              China Mobile
Intended status: Informational                                Ted. Lemon
Expires: August 19, 2014                                         Nominum
                                                          Yuri. Ismailov
                                                                Ericsson
                                                                  Z. Cao
                                                            China Mobile
                                                       February 15, 2014

                         MIF API consideration
                    draft-ietf-mif-api-extension-05

Abstract

   Hosts may connect to the internet using more than one network API at
   a time, or to a single network on which service is provided by more
   than one provider.  Existing APIs are inadequate to allow
   applications to successfully use the network in this environment.
   This document presents a new abstract API that provides the minimal
   set of messages required to enable an application to communicate
   successfully in this environment.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 19, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Liu, et al.              Expires August 19, 2014                [Page 1]
Internet-Draft            MIF API consideration            February 2014

   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  MIF API Concept . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Provisioning Domains  . . . . . . . . . . . . . . . . . .   4
     3.2.  MIF API Elements  . . . . . . . . . . . . . . . . . . . .   4
       3.2.1.  Application Element . . . . . . . . . . . . . . . . .   5
       3.2.2.  High Level API  . . . . . . . . . . . . . . . . . . .   5
       3.2.3.  MIF API . . . . . . . . . . . . . . . . . . . . . . .   6
       3.2.4.  Communications API  . . . . . . . . . . . . . . . . .   6
       3.2.5.  Network Link API  . . . . . . . . . . . . . . . . . .   6
       3.2.6.  MIF API communication model . . . . . . . . . . . . .   7
       3.2.7.  MIF Messages  . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Example Usage . . . . . . . . . . . . . . . . . . . . . .  14
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  16
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Traditionally, applications that communicate on the network have done
   so over a single network link, which is provided by a single service
   provider.  However, this operating environment is now the exception
   rather than the rule.  Most devices now have multiple wireless
   interfaces that are, in practice, connected to networks operated by
   different providers.  These networks may or may not have different
   reachability characteristics with respect to any given service an
   application may wish to connect to.

[include full document text]