idnits 2.17.1 draft-zhang-mif-api-extension-802-21-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 29, 2015) is 3227 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 MIF Hongke Zhang 2 Internet Draft Boxin Du 3 Intended status: Informational Mi Zhang 4 Expires: November 25, 2015 Fei Song 5 Beijing Jiaotong University 6 May 29, 2015 8 MIF API extension for combining IEEE 802.21 9 draft-zhang-mif-api-extension-802-21-02.txt 11 Abstract 13 The Application Program Interface (API) of MIF, specified in the MIF 14 API consideration, must rely on lower layer functionalities when 15 handover between homogeneous or heterogeneous networks is necessary. 16 To improve the connectivity experience, the existing MIF API needs to 17 be extended for solving such problem. IEEE is also aimed at the 18 similar issue from different way. A kind of logical entities over the 19 link layer protocol for handling the seamless handover has been 20 defined in IEEE 802.21. This document proposes a mechanism via 21 integrating MIF API and IEEE 802.21 to support application service 22 better. 24 Status of this Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on November 25, 2015. 41 Copyright Notice 43 Copyright (c) 2015 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction ................................................ 4 59 2. Terminology ................................................. 4 60 3. The Relationship between IEEE MIHF and MIF API .............. 4 61 4. The Extension of MIF API for Handover: A Case Study.......... 8 62 4.1. The MN-initiated Handover .............................. 8 63 4.1.1. Get Information ................................... 8 64 4.1.2. Information Post .................................. 9 65 4.1.3. Parameter Report .................................. 9 66 4.1.4. Check Resources MN ................................ 9 67 4.1.5. Resource Availability ............................. 9 68 4.1.6. Connect to Interface .............................. 9 69 4.1.7. Resource Preparation Messages .................... 10 70 4.1.8. Establish Link Messages .......................... 10 71 4.1.9. Link Up .......................................... 10 72 4.1.10. Handover Completed .............................. 10 73 4.1.11. Handover Completion Confirmation ................ 10 74 4.2. The Network-initiated Handover ........................ 10 75 4.2.1. Candidate Query Notification ..................... 11 76 4.2.2. Candidate Query Result ........................... 11 77 4.2.3. Check Resources Net .............................. 11 78 4.2.4. Confirm Chosen Target ............................ 12 79 4.2.5. Establish Link Messages .......................... 12 80 4.2.6. Link Up .......................................... 12 81 4.2.7. Handover Completed ............................... 12 82 4.2.8. Handover Completion Confirmation ................. 12 83 5. Discussions for New Messages from MIF Perspective .......... 12 84 5.1. Get Information ....................................... 12 85 5.2. Release the Ongoing Connection ........................ 13 86 5.3. Establish New L2 Connection ........................... 13 87 6. Discussions for New Messages from IEEE Perspective ......... 13 88 7. Security Considerations .................................... 16 89 8. IANA Considerations ........................................ 16 90 9. References ................................................. 16 91 9.1. Normative References .................................. 16 92 9.2. Informative References ................................ 16 93 10. Acknowledgments ........................................... 17 95 1. Introduction 97 In MIF context, improved connectivity experiences SHOULD be created. 98 Enhancing the performance of horizontal and vertical switches between 99 networks is one of main targets. Such situation is quite similar with 100 Media Independent Handover (MIH) described in [IEEE 802.21]. The MIF 101 Application Program Interface (API) specified in the MIF API 102 consideration [I-D.ietf-mif-api-extension] describes a set of message 103 calls to implement higher level APIs that solve the problems in 104 multiple interface scenarios. However, this draft only provides a 105 minimal set of message calls REQUIRED to implement the API. New 106 functions could be added. 108 According to [IEEE 802.21], the Media Independent Handover Function 109 (MIHF) is a logical entity that facilitates MIH decision making based 110 on inputs from the MIHF. It provides abstracted services to higher 111 layers. Communications with the lower layer of the mobility- 112 management protocol stack can be achieved through technology-specific 113 interfaces in MIHF. 115 Although two mechanisms, MIF API and MIHF, are working in different 116 layers and defined by different organizations, the requirements of 117 compatibility are obvious. Some of the functions of MIF API SHOULD be 118 supported by a connection manager (i.e. the MIHF), and vice versa. 119 Owing to the advantages of both MIHF and its Service Access Points 120 (SAPs), the functions of MIHF could be utilized in MIF API for 121 handover issues. This document extends message calls of MIF API to 122 support the MIH. Like [I-D.ietf-mif-api-extension], no bindings for 123 programming languages are provided because they are left up to the 124 implementation. This document only describes the messages sent and 125 received,which can be read as a checklist for operating system 126 vendors. 128 2. Terminology 130 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 131 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 132 document are to be interpreted as described in RFC-2119 [RFC2119]. 134 3. The Relationship between IEEE MIHF and MIF API 136 The purpose of IEEE 802.21 is to improve the user experience of 137 mobile devices by facilitating handover between IEEE 802 networks 138 regardless of whether they are of different media types or not, 139 including both wired and wireless. It also aims at making it possible 140 for mobile devices to perform seamless handover between IEEE 802 and 141 non IEEE networks. This standard defines: 143 1) A framework that enables service continuity while a Mobile Node 144 (MN) transitions between heterogeneous link-layer technologies. 146 2) MIHF. 148 3) MIH_SAP and associated primitives for users to get services of 149 MIHF. 151 4) The definitions of new link-layer SAPs and associated primitives 152 for each link-layer technology. They help MIHF to collect link 153 information and control link behaviors during handovers. 155 The concept of MIHF is a functional entity to realize the high- 156 performance handovers. The primary advantage of MIHF is that it 157 provides media-independent services to higher layers no matter which 158 media-specific technology of lower layer is being used, such as IEEE 159 Std.802.3, IEEE Std.802.11, IEEE Std.802.16, 3GPP and 3GPP2. It also 160 defines three kinds of SAPs (will be detailed later) of MIHF and 161 their primitives that interact between different layers. The MIHF can 162 also act as a filter: the messages received from link layer SHOULD be 163 processed and submitted to higher layer for meeting the subscribers' 164 need. Therefore, MIHF should work under MIF API. In fact, MIF API 165 SHOULD be served as a user of MIHF, which is shown in Figure 1. The 166 subscribers can then only interact with the MIHF via one kind of SAPs 167 (i.e. MIH_SAP) without knowing lower things. The MIH protocol is not 168 in the scope of this document. 170 Three kinds of MIHF services are defined in the standard, including 171 Media Independent Event Service (MIES), Media Independent Command 172 Service (MICS) and Media Independent Information Service (MIIS). 174 MIES provides event classification, event filtering and event 175 reporting corresponding to dynamic changes in link characteristics, 176 link status and link quality. It originates from lower layers and can 177 be passed to MIHF or upper users for the detection of handover 178 requirement. MICS enables MIH users to manage and control link 179 behavior relevant to handover and mobility. It is invoked by users or 180 MIHF and makes effect on MIHF or lower layers. 182 For example, in MN-initiated handover scenario, MICS is adopted for 183 MN switching between different links. MIIS allows MN and network 184 entities to discover information that influences the selection of 185 appropriate networks during handovers. Figure 2 [IEEE 802.21] shows 186 MIH services and their initiation. 188 +-------------------------------------+ 189 | Application | 190 +-------------------------------------+ 191 /\ || /\ || /\ || 192 || \/ || || || || 193 +--------------+ || || || || 194 |High Level API| || || || || 195 +--------------+ || || || || 196 /\ || || || || || 197 || \/ || \/ || || 198 +------------------------+ || || 199 | MIF API | || || 200 +------------------------+ || || 201 /\ || || \/ 202 || || +--------------------+ 203 || || | Communication API | 204 || || +--------------------+ 205 || || /\ /\ 206 || || || || 207 || \/ \/ \/ 208 +-------------------------------------+ 209 | MIHF | 210 +-------------------------------------+ 211 /\ || 212 || \/ 213 +-------------------------------------+ 214 | Network Link API | 215 +-------------------------------------+ 216 /\ || /\ || 217 || \/ || \/ 218 +---------------+ +---------------+ 219 | Network | | Network | 220 | Interface 1 | | Interface 2 | 221 +---------------+ +---------------+ 223 Figure 1 The relationship of MIHF & MIF API 225 The letters a, b, c in Figure 2 respectively represent: 227 a. MIH_SAP 229 b. MIH_LINK_SAP 231 c. LLC_SAP 233 The SAPs are divided into two categories: 235 1) Media dependent SAP (including MIH_LINK_SAP and LLC_SAP). 237 2) Media independent SAP (MIH_SAP). 239 +-------------+ Command +-----------------------------+ 240 | + Service | | 241 | / \ <---------------+ | 242 | + + | MIH User | 243 | | | Event | | 244 | MIHF | | Service | Layer 3 or Higher | 245 | | a |--------------->| Mobility Protocol | 246 | Event | | | | 247 | Service | | Information | | 248 | + + Service | | 249 | Command \ /<--------------->| +-------+ +-------+ | 250 | Service + +--+ c +-+---+--+ c +-+ 251 | | Command + +-------+ | + +-------+ | 252 | Information | Service / \ | / \ | 253 | Service |--------------->+ + | + + | 254 | | | | Network1 | | | Network2 | 255 | | Event | | (e.g.IEEE| | | (e.g.IEEE| 256 | | Service | b | 802.16) | | b | 802.11) | 257 | |<---------------| | | | | | 258 | | | | | | | | 259 | | Information | | | | | | 260 | | Service + + | + + | 261 | |<--------------->\ / | \ / | 262 | | + | + | 263 | | | | | | 264 +-------------+ +------------+ +------------+ 266 Figure 2 MIH services and their initiation 268 SAP of the MIHF (i.e. MIH_SAP) is media independent. The MIH_SAP 269 defines the interface between the MIHF and MIH users such as an upper 270 layer mobility protocol or a handover function (e.g., MIF API) that 271 might reside at higher layer transport entity as well. MIH_SAP allows 272 the MIHF to provide services to the upper layers, the network 273 management plane and the data bearer plane. Upper layers need to 274 subscribe with the MIHF as users to receive MIHF events. In MIF case, 275 the MIF API can directly send commands to the local MIHF via messages 276 which use the service primitives of the MIH_SAP. 278 All the messages REQUIRED for communicating successfully in MIF 279 environment that described in the [I-D.ietf-mif-api-extension] MUST 280 also be used here. These messages define the way that MIF API 281 interacts with the higher layers or applications. New messages need 282 to be added into this set for handover process. These new messages 283 SHOULD be exchanged between MIHF and MIF API. Some of them may use 284 the services of MIHF. 286 4. The Extension of MIF API in Handover: A Case Study 288 This section introduces the extension of message calls of MIF API in 289 two parts based on the classification of handovers (MN-initiated 290 handover and the network-initiated handover). To handle these two 291 kinds of handovers successfully, MIF API SHOULD be extended 292 respectively based on the characteristics of process. 294 4.1. The MN-initiated Handover 296 The MN-initated handover includes the following steps: 298 1) Information query. The MN collects network information from the 299 MIIS server which the MN is connected to. 301 2) Resource availability check. The MIF API sends request to find 302 candidates and then receives a list of candidate networks in response 303 message. 305 3) Resource preparation. The MN SHOULD determine which target network 306 is suitable and request it for resource preparation. 308 4) Establish new L2 connection. The MIF API initiates a new link 309 connection. 311 5) Link up indication. The MIHF of MN notifies the MIF API that the 312 link is up. 314 6) Higher layer handover execution. 316 7) Resource release. The original serving network resources must be 317 released in the end. 319 The following messages, which are only the interactions between a 320 MIHF and MIF APIs, need to be added. 322 4.1.1. Get Information 324 This message is sent by the MIF API to inquiry the neighboring 325 networks information. In MIH, we can use the MIH_Get_Information. 326 request for the same purpose. After receiving this message, the 327 MIHF inquires the MIIS server for the information,which will return 328 a list of network information needed for MIF API. 330 4.1.2. Information Post 332 This message is sent to the MIF API by the MIIS server as a response 333 to the Get Information message. MIH_Get_Information.confirm can be 334 used to convey such information. 336 4.1.3. Parameter Report 338 When attached to network, the MIF API needs to receive the link 339 status from the lower layers in order to better control the whole 340 connection. The MIHF can receive reports from the link layers and 341 submit them to the higher layers. If the link is going down, the MIF 342 API must notify its subscribers using "Interface is going away" 343 message. The application or higher API could try to establish new 344 connections by sending "Wants to connect" to MIHF and the connection 345 process will restart from step 2 (i.e. Resource availability check). 347 Another situation is that once the MIF API receives a "Wants to 348 connect" message from its subscriber, the MIF API SHOULD accordingly 349 trigger a whole connection process to a new network. This can also 350 begin from step 2. 352 4.1.4. Check Resources MN 354 Before the start of connection, the MN SHOULD check the resource 355 availability at the candidate networks. This message is sent to the 356 MIHF by the MIF API. The serving network SHOULD request each 357 candidate. The final result SHOULD be returned to the higher layer. 358 The MIH_MN_HO_Candidate_Query.request can be used in the MIH case. 360 4.1.5. Resource Availability 362 When receiving the resource availability of the candidates from the 363 serving network, the MIHF SHOULD submit them to the MIF API. The 364 MIH_MN_HO_Candidate_Query.confirm can be used in the MIH case. 366 4.1.6. Connect to Interface 368 This message is sent to the MIF API by the upper applications. When 369 the MIF API receives the Resource Availability, it could post the 370 message to the higher layer. The upper application can use "Connect 371 to Interface" to choose a better network interface. More about the 372 choosing methods need further discussion. 374 4.1.7. Resource Preparation Messages 376 The MIF API can use the MIH_MN_HO_Commit. request, which includs the 377 target network information, to request the network chose for resource 378 preparation. When the preparation is done, the MIHF receives the 379 response from the target network. It sends a MIH_MN_HO_Commit. 380 confirm message to the MIF API in order to inform the status of the 381 previously issued target notification request. 383 4.1.8. Establish Link Messages 385 MIF API can use the MIH_Link_Action. request to solve the problem in 386 connection establishment. This message primitively defined by the 387 [IEEE 802.21] is to control the local or remote lower link layers. It 388 includes a MIHF ID and a Link Actions List, which can realize many 389 controlling functions. After the action has been executed, the MIF 390 API should receive a MIH_Link_Action. confirm to indicate the result. 392 4.1.9. Link Up 394 After the new link is established, the MAC layers MUST deliver a 395 Link_Up.indication to the MIHF. The MIHF then passes the MIH_Link_Up. 396 indication message to the MIF API. The MIF API can notify the upper 397 applications by delivering the "Link is going up" message. Then the 398 higher layer handover execution might be triggered and the traffic 399 flow can be re-established. 401 4.1.10. Handover Completed 403 This message is sent to the local MIHF by the MIH API to release the 404 resources of the previous serving network which was originally 405 allocated to the MN. After identifying that the release is done, the 406 target network Point of Service (PoS) sends the confirm message to 407 the MIHF and the MIHF SHOULD also reply the MIF API with the same 408 information. 410 4.1.11. Handover Completion Confirmation 412 This message is sent to the MIF API by the MIHF indicating that the 413 resource of the previous network is successfully released. 415 4.2. The Network-initiated Handover 417 There are also seven steps in an intact network-initiated handover, 418 like the MN-initiated handover: 420 1) Information query. 422 2) Resource availability check. 424 3) Resource preparation. 426 4) Establish a L2 connection using MIH_Link_Action.request. 428 5) Sent link indications to the MIF API. 430 6) Higher layer handover execution. 432 7) Resource release. 434 The differences between Network-initiated case and MN-initiated case 435 are in step 1 and step 2: the Get Information request and Information 436 Query are respectively initiated by the MIH user of the serving 437 network. When such MIH user obtains the information from the MIIS 438 server, it sends requests to the MN for a response message containing 439 the MN's handover acknowledgement, MN's preferred link and PoS lists. 441 In step 3, the commitment of target network is also initiated by the 442 MIH user of a serving network. After the resource is prepared, the 443 PoS of serving network SHOULD notify the MN for the establishment of 444 L2 connection in step 4. 446 The following messages should be added in MIF API: 448 4.2.1. Candidate Query Notification 450 This message is sent to MN's MIHF from the PoS of the serving network 451 with a list of PoAs of each candidate network link. Such message 452 suggests the MN SHOULD consider new access network. This message can 453 use the MIH_Net_HO_Candidate_Query. indication. 455 4.2.2. Candidate Query Result 457 This message is sent to the local serving network's MIHF from MN's 458 MIF API, specifying whether the request of handover is permitted or 459 not. MIH_Net_HO_Candidate_Query.response can be used here. If the 460 handover is permitted, a new access network SHOULD be considered at 461 the handover initiation stage. 463 4.2.3. Check Resources Net 465 This message is sent to the MN's MIF API by the PoS of serving 466 network with a list of target network information and a set of 467 resource parameters assigned to the MN for handover. 468 MIH_Net_HO_Commit.indication can be used here. Then the MIF API can 469 trigger the establishment of L2 connection by using 470 Link_Action.request. After the link connection is done, MIF API needs 471 to inform the serving network. Link_Action. request might also have a 472 list of actions for handover control during the link connection 473 period. 475 4.2.4. Confirm Chosen Target 477 This message is sent by the MN's MIF API as a response to the 478 MIH_HO_Commit.indication, revealing that the indication is received. 479 MIH_Net_HO_Commit.response can be used here. Also such message might 480 include a list of the results of previous actions. 482 4.2.5. Establish Link Messages 484 This message is exactly the same as that of the MN-initiated process, 485 for establishing a new L2 link connection. 487 4.2.6. Link Up 489 This message is exactly the same as that of the MN-initiated process, 490 for informing the MIF API that the L2 link is completed. 492 4.2.7. Handover Completed 494 This message is exactly the same as that of the MN-initiated process, 495 for releasing the resources that have already attained by the MN. 497 4.2.8. Handover Completion Confirmation 499 This message is exactly the same as that of the MN-initiated process, 500 for confirming that the resources of the previous network are 501 successfully released. 503 5. Discussions for New Messages from MIF Perspective 505 New messages described in this document are critical for information 506 exchanging and function achievement between MIHF and MIF API. Since 507 both "upper layer requirements gathering" and "lower layer command 508 delivering" (or reverse) can be achieved via messages, the logical 509 relationship should be discussed in-depth. The messages below are 510 only the examples. Further updating is needed. 512 5.1. Get Information 514 According to [IEEE 802.21], this information query is related to a 515 specific interface. It has the flexibility to query either a specific 516 data within a network interface or an extended schema of a given 517 network. As an advanced application or upper APIs send "Announce 518 Interface", "Announce PVD" and "Announce IE (Information Elements)", 519 the MIF API could obtain the information by using the 520 Get_information.request in MIH. 522 5.2. Release the Ongoing Connection 524 The [I-D.ietf-mif-api-extension] defines a message "Connection can be 525 broken", which means that the MN can tolerate the connection being 526 broken, e.g. for power conservation. When the subscribers of MIF API 527 delivers this message, the MIF API SHOULD send "Release the ongoing 528 connection" to the MIHF so that directly releasing the current 529 resources of network to cut off this connection. This action will not 530 weaken the function of the application. 532 5.3. Establish New L2 Connection 534 According to [IEEE 802.21], the MIH_Link_Actions can trigger a L2 535 link connection. When MN wants to build a TCP connection with an IP 536 host, the MIF API will receive "Connect to Address" or "Connect to 537 Address from Address" messages. Then the MIF API can use the 538 MIH_Link_Actions.request to ask MIHF for a new L2 link connection. 540 6. Discussions for New Messages from IEEE Perspective 542 The following tables, table1, 2, 3 and 4, are from the [IEEE 802.21]. 543 These messages might be used in the MIF API because they are 544 exchanged between the MIHF and its MIH users. Some of them have been 545 discussed above, but the specific usage of the rest is not 546 represented. This section presents only a direct list of all these 547 messages, their category and brief descriptions. Further discussion 548 is still needed. 550 +---------------------+--------------------------------------------+ 551 | Messages | Description | 552 | (Information) | | 553 +---------------------+--------------------------------------------+ 554 | MIH_Get_Information | Request to get information from repository | 555 +---------------------+--------------------------------------------+ 556 | MIH_Push_Information| Notify the MN of operator policies or | 557 | | other information | 558 +---------------------+--------------------------------------------+ 560 Table 1 Information Messages of MIHF 562 +---------------------+--------------------------------------------+ 563 | Messages (Event) | Description | 564 +---------------------+--------------------------------------------+ 565 | MIH_Link_Detected | Link of a new access network has been | 566 | | detected. This event is typically on the | 567 | | MN when the first PoA of an access network | 568 | | is detected | 569 +---------------------+--------------------------------------------+ 570 | Track_timeout | This event is not generated when | 571 | | subsequent PoAs of the same access network | 572 | | are discovered | 573 +---------------------+--------------------------------------------+ 574 | MIH_Link_Up | L2 connection is established and link is | 575 | | available for use | 576 +---------------------+--------------------------------------------+ 577 | MIH_Link_Down | L2 connection is broken and link is not | 578 | | available for use | 579 +---------------------+--------------------------------------------+ 580 | MIH_Link_Paremeters | Link parameters have crossed a specified | 581 | _Report | threshold and need to be reported | 582 +---------------------+--------------------------------------------+ 583 | MIH_Link_Going_Down | Link conditions are degrading and | 584 | | connection loss is imminent | 585 +---------------------+--------------------------------------------+ 586 | MIH_Link_Handover | L2 handover is imminent based on either | 587 | _Imminent | the changes in the link conditions or | 588 | | additional information available in the | 589 | | network | 590 +---------------------+--------------------------------------------+ 591 | MIH_Link_Handover | L2 handover to a new PoA has been | 592 | _Complete | completed | 593 +---------------------+--------------------------------------------+ 594 | MIH_Link_PDU | Indicate transmission status of a PDU | 595 | _Transmit_Status | | 596 +---------------------+--------------------------------------------+ 598 Table 2 Event Messages of MIHF 600 +--------------------+---------------------------------------------+ 601 | Messages (Command) | Description | 602 +--------------------+---------------------------------------------+ 603 | MIH_Link_Get | Get the status of a link | 604 | _Parameters | | 605 +--------------------+---------------------------------------------+ 606 | MIH_Net_HO | Network initiates handover and sends a list | 607 | _Candidate _Query | of suggested networks and associated points | 608 | | of attachment | 609 +--------------------+---------------------------------------------+ 610 | MIH_Link_Configure | Configure link parameter thresholds | 611 | Thresholds | | 612 +--------------------+---------------------------------------------+ 613 | MIH_Link_Actions | Control the behavior of a set of links | 614 +--------------------+---------------------------------------------+ 615 | MIH_MN_HO_Candidate| Command used by MN to query and obtain | 616 | _Query | handover related information about possible | 617 | | candidate networks | 618 +--------------------+---------------------------------------------+ 619 | MIH_N2N_HO_Query | command sent by the serving MIHF entity to | 620 | _Resources | the target MIHF entity for resource query | 621 +--------------------+---------------------------------------------+ 622 | MIH_MN_HO_Commit | Command used by MN to notify the serving | 623 | | network of the decided target network | 624 | | information | 625 +--------------------+---------------------------------------------+ 626 | MIH_Net_HO_Commit | Command used by the network to notify the | 627 | | MN of the decided target network information| 628 +--------------------+---------------------------------------------+ 629 | MIH_N2N_HO_Commit | Command used by a serving network to inform | 630 | | a target network that an MN is about to | 631 | | move toward that network, initiate context | 632 | | transfer and perform handover preparation | 633 +--------------------+---------------------------------------------+ 634 | MIH_MN_HO_Complete | Notification from MIHF of the MN to the | 635 | | target or source MIHF indicating the | 636 | | status of handover completion | 637 +--------------------+---------------------------------------------+ 638 | MIH_N2N_HO_Complete| Notification from MIHF of the MN to the | 639 | | target or source MIHF indicating the | 640 | | status of handover completion | 641 +--------------------+---------------------------------------------+ 642 | MIH_N2N_HO_Complete| Notification from either source or target | 643 | | MIHF to the peer MIHF indicating the status | 644 | | of the handover completion | 645 +--------------------+---------------------------------------------+ 646 Table 3 Command Messages of MIHF 648 +---------------------+--------------------------------------------+ 649 | Messages | Description | 650 | (Service management)| | 651 +---------------------+--------------------------------------------+ 652 | MIH_Capability | Discover list of Events and Commands | 653 | _Discover | supported by MIHF | 654 +---------------------+--------------------------------------------+ 655 | MIH_Register | Register with a remote MIHF | 656 +---------------------+--------------------------------------------+ 657 | MIH_DeRegister | Deregister with a remote MIHF | 658 +---------------------+--------------------------------------------+ 659 | MIH_Event_Subscribe | Subscribe for MIH event notification | 660 +---------------------+--------------------------------------------+ 661 | MIH_Event_Unsubscibe| Unsubscribe from MIH event notification | 662 +---------------------+--------------------------------------------+ 664 Table 4 Service Management of MIHF 666 7. Security Considerations 668 This document does not contain any security considerations. 670 8. IANA Considerations 672 There are presently no IANA considerations with this document. 674 9. References 676 9.1. Normative References 678 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 679 Requirement Levels", BCP 14, RFC 2119, March 1997. 681 9.2. Informative References 683 [IEEE 802.21] IEEE, "IEEE Standard for Local and Metropolitan Area 684 Networks Part 21: Media Independent Handover Services", 685 IEEE LAN/MAN Std 802.21-2008, January 2009. 686 . 689 [I-D.ietf-mif-api-extension] Liu, D., Lemon, T., Ismailov, Y., and Z. 690 Cao, "MIF API consideration", draft-ietf-mif-api-extension- 691 05 (work in progress), Feb. 2014. 693 10. Acknowledgments 695 This document was prepared using 2-Word-v2.0.template.dot. 697 Authors' Addresses 699 Hongke Zhang 700 Beijing Jiaotong University (BJTU) 701 Beijing, 100044, P.R.China 703 Email: hkzhang@bjtu.edu.cn 705 Boxin Du 706 Beijing Jiaotong University (BJTU) 707 Beijing, 100044, P.R.China 709 Email: 10291070@bjtu.edu.cn 711 Mi Zhang 712 Beijing Jiaotong University (BJTU) 713 Beijing, 100044, P.R.China 715 Email: 13120174@bjtu.edu.cn 717 Fei Song 718 Beijing Jiaotong University (BJTU) 719 Beijing, 100044, P.R.China 721 Email: fsong@bjtu.edu.cn