idnits 2.17.00 (12 Aug 2021) /tmp/idnits62090/draft-zuniga-mif-802-21-overview-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 : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 14, 2014) is 3011 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'I-D.ietf-mif-api-extension' is defined on line 262, but no explicit reference was found in the text == Outdated reference: A later version (-05) exists of draft-ietf-mif-api-extension-04 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MIF WG JC. Zuniga 3 Internet-Draft InterDigital Communications, LLC 4 Intended status: Informational P. Seite 5 Expires: August 18, 2014 Orange 6 February 14, 2014 8 IEEE 802.21 Overview 9 draft-zuniga-mif-802-21-overview-02 11 Abstract 13 Some of the messages defined by a potential MIF API may rely on 14 functionalities provided by lower layers. The IEEE 802.21 15 specification defines an abstraction of lower layer functions that 16 can be useful for a MIF API. This document provides an overview of 17 the IEEE 802.21 specification and enumerates a subset of functions 18 that can be used in the context of the MIF API to interact with lower 19 layers. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on August 18, 2014. 38 Copyright Notice 40 Copyright (c) 2014 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. IEEE 802.21 Framework . . . . . . . . . . . . . . . . . . . . 2 57 3. Security Considerations . . . . . . . . . . . . . . . . . . . 6 58 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 59 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 60 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 63 1. Introduction 65 There is currently a need to present a coherent connection management 66 behaviour for different terminal platforms (e.g. mobile smart phones, 67 PCs, tablets, etc.), as users often experience a very different 68 behaviour when connecting with various platforms to the same networks 69 and for the same purposes (e.g. web browsing, email access, VPN, 70 dedicated applications, etc.). 72 The IEEE 802.21 specification [IEEE802.21] defines several media 73 independent services that can be used by higher layers (e.g., L3 and 74 above) to interact with lower layers (e.g., L2 and below). This 75 document provides an overview of the IEEE 802.21 specification, 76 focusing on the most relevant functions from a MIF API point of view. 78 2. IEEE 802.21 Framework 80 Some of the connection management services described in 81 [I-D.seite-mif-cm] may rely on standardized abstraction layers such 82 as the IEEE 802.21 framework [IEEE802.21]. 84 The IEEE 802.21-2008 Media Independent Handover (MIH) Services 85 baseline specification defines three types of services: Information 86 Services (IS), Event Services (ES) and Command Services (CS). Each 87 one of these services has a different purpose. The IS provides 88 information about existing networks and services in a potential 89 target network. The ES provides triggers, measurements and events 90 from lower layers (e.g. network access layers) that can be used for 91 instance to proactively trigger actions like a handing over or 92 establishing a new connection to a different access network. The CS 93 allows configuring lower layer interfaces and events. Both ES and CS 94 provide an abstraction layer to upper layers that allows configuring 95 and interacting with different types of network link interfaces in a 96 coherent manner. 98 In 802.21 terminology, the main functionalities are performed by the 99 MIH Function. This MIH Function is in charge of providing services 100 to the MIH User, which is a higher layer entity (e.g., L3 and above). 101 Functions are applied to specific Link Layers, which are lower layer 102 entities (e.g., L2 and below). The basics of the 802.21 ES/CS flow 103 are depicted in Figure 1. 105 MIH User MIH Function Link Layer 106 | | | 107 | | | 108 | | | 109 | subcribe.request | | 110 |------------------->|----------->| 111 | subcribe.confirm | | 112 |<-------------------|<-----------| 113 | | | 114 | | | 115 | | event occurs 116 | event.notif | | 117 |<-------------------|<-----------| 118 | | | 119 | command.request | | 120 |------------------->|----------->| 121 | | Link command 122 | command.confirm | Execution 123 |<-------------------|<-----------| 124 | | | 126 Figure 1: IEEE 802.21 event and command services flow 128 An MIH user may use the following IEEE 802.21 events and commands to 129 complete connection management operations: 131 Link_Event_Subscribe 133 Category: command 135 Description: Subscribe to one or more events from a link. 137 Link_Event_Unsubscribe 139 Category: command 141 Description: Unsubscribe from a set of link-layer events. 143 Link_Parameters_Report 145 Category: Event 147 Description: Link parameters have crossed a specified threshold 148 and need to be reported. 150 Link_Get_Parameters 152 Category: command 154 Description: Get parameters measured by the active link, such as 155 signal-to-noise ratio (SNR), BER, received signal strength 156 indication (RSSI). 158 Link_Detected 160 Category: Event 162 Description: Link of a new access network has been detected. 164 Link_Up 166 Category: Event 168 Description: L2 connection is established and link is available 169 for use. 171 Link_Down 173 Category: Event 175 Description: L2 connection is broken and link is not available for 176 use. 178 Link_Going_Down 180 Category: Event 182 Description: Radio link conditions are degrading and connection 183 loss is very likely. 185 Link_Handover_Imminent 187 Category: Event 188 Description: L2 handover is imminent based on either the changes 189 in the link conditions or additional information available at 190 layer 2. 192 Link_Handover_Complete 194 Category: Event 196 Description: L2 handover has been completed. 198 Link_PDU_Transmit_Status 200 Category: Event 202 Description: indicate transmission status of a PDU. 204 Link_Capability_Discover 206 Category: command 208 Description: Query and discover the list of supported link-layer 209 events and link-layer commands. 211 Link_Configuration_Thresholds 213 Category: command 215 Description: Configure thresholds for future Link Parameters 216 Report events. 218 Link_Action 220 Category: command 222 Description: request an action on a link-layer connection, e.g. 223 perform a scan, shut down an interface, etc. 225 Handover_Query 227 Category: command 229 Description: query and obtain handover related information about 230 possible candidate target networks. 232 Handover_Commit 234 Category: command 235 Description: notify the MIH function of the decided target 236 network. 238 Handover_Complete 240 Category: command 242 Description: indicate the status of the handover completion to the 243 MIH function. 245 3. Security Considerations 247 TBD. 249 4. IANA Considerations 251 This document has no actions for IANA. 253 5. Acknowledgements 255 The authors would like to express their gratitude to Ralph Droms, Ted 256 Lemon, Dave Thaler, Antonio de la Oliva and Subir Das for the 257 fruitful discussions regarding 802.21, MIF API and connection 258 managers. 260 6. References 262 [I-D.ietf-mif-api-extension] 263 Liu, D., Lemon, T., Ismailov, Y., and Z. Cao, "MIF API 264 consideration", draft-ietf-mif-api-extension-04 (work in 265 progress), October 2013. 267 [I-D.seite-mif-cm] 268 Seite, P. and J. Zuniga, "MIF API for Connection 269 Management", draft-seite-mif-cm-02 (work in progress), 270 August 2013. 272 [IEEE802.21] 273 IEEE, "IEEE Standard for Local and Metropolitan Area 274 Networks - Part 21: Media Independent Handover Services", 275 IEEE LAN/MAN Std 802.21-2008, January 2009.", 2009, < 276 http://www.ieee802.org/21/private/Published%20Spec/ 277 802.21-2008.pdf>. 279 Authors' Addresses 281 Juan Carlos Zuniga 282 InterDigital Communications, LLC 283 1000 Sherbrooke Street West, 10th floor 284 Montreal, Quebec H3A 3G4 285 Canada 287 Email: JuanCarlos.Zuniga@InterDigital.com 289 Pierrick Seite 290 Orange 291 4, rue du Clos Courtel, BP 91226 292 Cesson-Sevigne 35512 293 France 295 Email: pierrick.seite@orange.com