MIF API extension for combining IEEE 802.2
draft-zhang-mif-api-extension-802-21-07

Document Type Active Internet-Draft (individual)
Last updated 2017-11-16
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MIF                                                        Hongke Zhang
Internet Draft                                                 Fei Song
Intended status: Informational                                 Boxin Du
Expires: May 18 2018                                              Mi Du
                                                               Mi Zhang
                                            Beijing Jiaotong University
                                                      November 17, 2017

             MIF API extension for combining IEEE 802.2
             draft-zhang-mif-api-extension-802-21-07.txt

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 May 18, 2018.

Copyright Notice

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

Zhang, et al.            Expires May 17,2018                  [Page 1]
Internet-Draft            MIF API extension                   NOV 2017

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (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.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (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.

Abstract

   The Application Program Interface (API) of MIF, specified in the
   MIFAPI consideration, must rely on lower layer functionalities when
   handover between homogeneous or heterogeneous networks is necessary.
   To improve the connectivity performance, the existing MIF API needs
   to be extended. IEEE is also aimed at the similar issue from
   different way. A kind of logical entities over the link layer
   protocol for handling the seamless handover has been defined in
   IEEE802.21. This document proposes a mechanism via integrating MIF
   API and IEEE 802.21 to support application service better.

Table of Contents

   1. Introduction ................................................  4
   2. Terminology .................................................  4
   3. The Relationship between IEEE MIHF and MIF API ............... 5

Zhang, et al.           Expires May 17, 2018                  [Page 2]
Internet-Draft            MIF API extension                   NOV 2017

   4. The Extension of MIF API for Handover: A Case Study........... 9
      4.1. The MN-initiated Handover ............................... 9
         4.1.1. Get Information  ................................... 10
         4.1.2. Information Post  .................................. 10
         4.1.3. Parameter Report  .................................. 10
         4.1.4. Check Resources MN  ................................ 10
         4.1.5. Resource Availability  ............................. 11
         4.1.6. Connect to Interface  .............................. 11
         4.1.7. Resource Preparation Messages  ..................... 11
         4.1.8. Establish Link Messages  ........................... 11
         4.1.9. Link Up ............................................ 11
         4.1.10. Handover Completed ................................ 12
         4.1.11. Handover Completion Confirmation .................. 12
      4.2. The Network-initiated Handover  ......................... 12
         4.2.1. Candidate Query Notification  ...................... 13
         4.2.2. Candidate Query Result  ............................ 13
         4.2.3. Check Resources Net  ............................... 13
         4.2.4. Confirm Chosen Target  ............................. 13
Show full document text