idnits 2.17.1 draft-templin-ipwave-uam-its-03.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 (July 4, 2020) is 1392 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-99) exists of draft-templin-6man-omni-interface-27 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group F. Templin, Ed. 3 Internet-Draft Boeing Research & Technology 4 Intended status: Informational July 4, 2020 5 Expires: January 5, 2021 7 Urban Air Mobility Implications for Intelligent Transportation Systems 8 draft-templin-ipwave-uam-its-03 10 Abstract 12 Urban Air Mobility concerns the introduction of manned and unmanned 13 aircraft within urban environments, while Intelligent Transportation 14 Systems have traditionally considered only terrestrial vehicles 15 operating on city streets and highways. This document considers the 16 implications for introduction of low-altitude aircraft within urban 17 environments operating in harmony with ground transportation. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on January 5, 2021. 36 Copyright Notice 38 Copyright (c) 2020 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 3 56 4. The Overlay Multilink Network (OMNI) Interface . . . . . . . 3 57 5. Implementation Status . . . . . . . . . . . . . . . . . . . . 4 58 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 59 7. Security Considerations . . . . . . . . . . . . . . . . . . . 4 60 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 61 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 9.1. Normative References . . . . . . . . . . . . . . . . . . 4 63 9.2. Informative References . . . . . . . . . . . . . . . . . 5 64 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 5 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 67 1. Introduction 69 Urban Air Mobility (UAM) concerns the introduction of manned and 70 unmanned aircraft within urban environments. Autonomy will play a 71 pivotal role in the acceptance of low-altitude operations for aerial 72 vehicles operating in harmony with traditional ground transportation 73 and pedestrian traffic. The UAM vision therefore builds on evolving 74 works on Unmanned Air Systems (UAS), including the NASA UAS Traffic 75 Management (UTM) service model [UTM]. 77 Use cases for autonomous aircraft in the UAM vision are endless, and 78 include personal air vehicles, flying taxis, parcel delivery, law 79 enforcement and countless others. Major industry leaders such as 80 Airbus [AIRBUS] and Boeing [BOEING] have accordingly begun to 81 articulate their UAM strategies. Programs such as Uber Elevate 82 [UBER] anticipate deployment as early as within the next 2-5 years. 84 With the advent of the UAM vision and its related initiatives, 85 questions arise as to how the new model will be harmonized with the 86 existing terrestrial mobility environment. Directions for 87 modernizing terrestrial mobility are emerging in programs such as the 88 US Department of Transportation's Intelligent Transportation Systems 89 [ITS] and anticipate an increasing role for Vehicle to Vehicle (V2V) 90 and Vehicle to Infrastructure (V2I) communications. The IETF 91 recognizes this need and has formed the IP Wireless Access in 92 Vehicular Environments (IPWAVE) working group with charter to produce 93 a document that will specify the mechanisms for transmission of IPv6 94 datagrams [RFC8200] over dedicated short-range wireless 95 communications media. 97 This document anticipates a need to provide a unified V2V and V2I 98 service for all urban mobility agents, including both terrestrial and 99 airborne. Urban air vehicles will employ Vertical Takeoff And 100 Landing (VTOL) and will operate at altitudes below 400 feet, such 101 that coordinations with terrestrial vehicles will be inevitable and 102 commonplace. This work therefore proposes that urban air vehicles 103 also employ a short-range V2V / V2I communications capability using 104 the same types of wireless networking gear used in the terrestrial 105 domain (e.g., DSRC, C-V2X, etc.). 107 The urban mobility landscape is evolving from a two dimensional to a 108 three dimensional environment. Vehicles both on the ground and in 109 the air will therefore need to coordinate with one another on a V2V 110 and V2I basis even when supporting communications infrastructure such 111 as cell towers are unavailable or otherwise too congested to support 112 realtime exchanges. The ipwave working group is therefore advised to 113 consider the rapidly emerging and inevitable Urban Air Mobility 114 future. 116 2. Terminology 118 Terms such as Intelligent Transportation Systems (ITS), Urban Air 119 Mobility (UAM), Unmanned Air Systems (UAS), UAS Traffic Management 120 (UTM) and many others apply to the emerging urban mobility landscape. 121 IETF keywords per [RFC2119] are not applicable within the scope of 122 this document. 124 3. Applicability 126 Urban Air Mobility and Intelligent Transportation System concepts 127 apply within all major urban areas worldwide. 129 4. The Overlay Multilink Network (OMNI) Interface 131 UAM end systems will often have multiple diverse wireless 132 transmission media interfaces (including cellular, SATCOM, short- 133 range omni-directional, etc.) offered by different data link service 134 providers. In order to provide mobility, multihop and multilink 135 services, UAM end systems can employ an Overlay Multilink Network 136 (OMNI) interface [I-D.templin-6man-omni-interface] as a virtual Non- 137 Broadcast Multiple Access (NBMA) connection to the serving ground 138 domain infrastructure configured over the underlying data links. 140 The OMNI interface and link model provide a nexus for multilink, 141 multihop and mobility coordination using standard IPv6 Neighbor 142 Discovery (ND) messaging [RFC4861] according to the NBMA principle. 143 The OMNI model therefore supports efficient UAM internetworking 144 services with no need for adjunct mobility messaging, nor 145 modifications to the IPv6 ND messaging services or link model. 147 5. Implementation Status 149 Early prototyping and testing are underway. 151 6. IANA Considerations 153 This document introduces no IANA considerations. 155 7. Security Considerations 157 Communications networking security is necessary to preserve the 158 confidentiality, integrity and availability necessary for V2V and V2I 159 coordinations. 161 8. Acknowledgements 163 Discussions on the IETF ipwave list (its@ietf.org) helped motivate 164 this document. 166 This work is aligned with the NASA Safe Autonomous Systems Operation 167 (SASO) program under NASA contract number NNA16BD84C. 169 This work is aligned with the FAA as per the SE2025 contract number 170 DTFAWA-15-D-00030. 172 This work is aligned with the Boeing Commercial Airplanes (BCA) 173 Internet of Things (IoT) and autonomy programs. 175 This work is aligned with the Boeing Information Technology (BIT) 176 MobileNet program. 178 9. References 180 9.1. Normative References 182 [I-D.templin-6man-omni-interface] 183 Templin, F. and T. Whyman, "Transmission of IPv6 Packets 184 over Overlay Multilink Network (OMNI) Interfaces", draft- 185 templin-6man-omni-interface-27 (work in progress), July 186 2020. 188 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 189 Requirement Levels", BCP 14, RFC 2119, 190 DOI 10.17487/RFC2119, March 1997, 191 . 193 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 194 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 195 DOI 10.17487/RFC4861, September 2007, 196 . 198 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 199 (IPv6) Specification", STD 86, RFC 8200, 200 DOI 10.17487/RFC8200, July 2017, 201 . 203 9.2. Informative References 205 [AIRBUS] "https://www.airbus.com/innovation/Urban-air-mobility-the- 206 sky-is-yours.html", November 2018. 208 [BOEING] "http://www.boeing.com/NeXt/common/docs/ 209 Boeing_Future_of_Mobility_White%20Paper.pdf", March 2019. 211 [ITS] "https://www.its.dot.gov/", November 2018. 213 [UBER] "https://www.uber.com/us/en/elevate/", November 2018. 215 [UTM] "https://utm.arc.nasa.gov/index.shtml", March 2019. 217 Appendix A. Change Log 219 << RFC Editor - remove prior to publication >> 221 Changes from -01 to -02: 223 o Included OMNI interface 225 o Version and reference update 227 Changes from -00 to -01: 229 o Version and reference update 231 Author's Address 233 Fred L. Templin (editor) 234 Boeing Research & Technology 235 P.O. Box 3707 236 Seattle, WA 98124 237 USA 239 Email: fltemplin@acm.org