idnits 2.17.1 draft-templin-ipwave-uam-its-01.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 (January 1, 2020) is 1576 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. -------------------------------------------------------------------------------- 2 Network Working Group F. Templin, Ed. 3 Internet-Draft Boeing Research & Technology 4 Intended status: Informational January 1, 2020 5 Expires: July 4, 2020 7 Urban Air Mobility Implications for Intelligent Transportation Systems 8 draft-templin-ipwave-uam-its-01 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 July 4, 2020. 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. Implementation Status . . . . . . . . . . . . . . . . . . . . 3 57 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 58 6. Security Considerations . . . . . . . . . . . . . . . . . . . 3 59 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 60 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 62 8.2. Informative References . . . . . . . . . . . . . . . . . 4 63 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 5 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 66 1. Introduction 68 Urban Air Mobility (UAM) concerns the introduction of manned and 69 unmanned aircraft within urban environments. Autonomy will play a 70 pivotal role in the acceptance of low-altitude operations for aerial 71 vehicles operating in harmony with traditional ground transportation 72 and pedestrian traffic. The UAM vision therefore builds on evolving 73 works on Unmanned Air Systems (UAS), including the NASA UAS Traffic 74 Management (UTM) service model [UTM]. 76 Use cases for autonomous aircraft in the UAM vision are endless, and 77 include personal air vehicles, flying taxis, parcel delivery, law 78 enforcement and countless others. Major industry leaders such as 79 Airbus [AIRBUS] and Boeing [BOEING] have accordingly begun to 80 articulate their UAM strategies. Programs such as Uber Elevate 81 [UBER] anticipate deployment as early as within the next 2-5 years. 83 With the advent of the UAM vision and its related initiatives, 84 questions arise as to how the new model will be harmonized with the 85 existing terrestrial mobility environment. Directions for 86 modernizing terrestrial mobility are emerging in programs such as the 87 US Department of Transportation's Intelligent Transportation Systems 88 [ITS] and anticipate an increasing role for Vehicle to Vehicle (V2V) 89 and Vehicle to Infrastructure (V2I) communications. The IETF 90 recognizes this need and has formed the IP Wireless Access in 91 Vehicular Environments (IPWAVE) working group with charter to produce 92 a document that will specify the mechanisms for transmission of IPv6 93 datagrams [RFC8200] over dedicated short-range wireless 94 communications media. 96 This document anticipates a need to provide a unified V2V and V2I 97 service for all urban mobility agents, including both terrestrial and 98 airborne. Urban air vehicles will employ Vertical Takeoff And 99 Landing (VTOL) and will operate at altitudes below 400 feet, such 100 that coordinations with terrestrial vehicles will be inevitable and 101 commonplace. This work therefore proposes that urban air vehicles 102 also employ a short-range V2V / V2I communications capability using 103 the same types of wireless networking gear used in the terrestrial 104 domain (e.g., DSRC, C-V2X, etc.). 106 The urban mobility landscape is evolving from a two dimensional to a 107 three dimensional environment. Vehicles both on the ground and in 108 the air will therefore need to coordinate with one another on a V2V 109 and V2I basis even when supporting communications infrastructure such 110 as cell towers are unavailable or otherwise too congested to support 111 realtime exchanges. The ipwave working group is therefore advised to 112 consider the rapidly emerging and inevitable Urban Air Mobility 113 future. 115 2. Terminology 117 Terms such as Intelligent Transportation Systems (ITS), Urban Air 118 Mobility (UAM), Unmanned Air Systems (UAS), UAS Traffic Management 119 (UTM) and many others apply to the emerging urban mobility landscape. 120 IETF keywords per [RFC2119] are not applicable within the scope of 121 this document. 123 3. Applicability 125 Urban Air Mobility and Intelligent Transportation System concepts 126 apply within all major urban areas worldwide. 128 4. Implementation Status 130 Early prototyping and testing are underway. 132 5. IANA Considerations 134 This document introduces no IANA considerations. 136 6. Security Considerations 138 Communications networking security is necessary to preserve the 139 confidentiality, integrity and availability necessary for V2V and V2I 140 coordinations. 142 7. Acknowledgements 144 Discussions on the IETF ipwave list (its@ietf.org) helped motivate 145 this document. 147 This work is aligned with the NASA Safe Autonomous Systems Operation 148 (SASO) program under NASA contract number NNA16BD84C. 150 This work is aligned with the FAA as per the SE2025 contract number 151 DTFAWA-15-D-00030. 153 This work is aligned with the Boeing Commercial Airplanes (BCA) 154 Internet of Things (IoT) and autonomy programs. 156 This work is aligned with the Boeing Information Technology (BIT) 157 MobileNet program. 159 8. References 161 8.1. Normative References 163 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 164 Requirement Levels", BCP 14, RFC 2119, 165 DOI 10.17487/RFC2119, March 1997, 166 . 168 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 169 (IPv6) Specification", STD 86, RFC 8200, 170 DOI 10.17487/RFC8200, July 2017, 171 . 173 8.2. Informative References 175 [AIRBUS] "https://www.airbus.com/innovation/Urban-air-mobility-the- 176 sky-is-yours.html", November 2018. 178 [BOEING] "http://www.boeing.com/NeXt/common/docs/ 179 Boeing_Future_of_Mobility_White%20Paper.pdf", March 2019. 181 [ITS] "https://www.its.dot.gov/", November 2018. 183 [UBER] "https://www.uber.com/us/en/elevate/", November 2018. 185 [UTM] "https://utm.arc.nasa.gov/index.shtml", March 2019. 187 Appendix A. Change Log 189 << RFC Editor - remove prior to publication >> 191 Changes from -00 to -01: 193 o Version and reference update 195 Author's Address 197 Fred L. Templin (editor) 198 Boeing Research & Technology 199 P.O. Box 3707 200 Seattle, WA 98124 201 USA 203 Email: fltemplin@acm.org