idnits 2.17.1 draft-templin-ipwave-uam-its-00.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 (March 11, 2019) is 1867 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 March 11, 2019 5 Expires: September 12, 2019 7 Urban Air Mobility Implications for Intelligent Transportation Systems 8 draft-templin-ipwave-uam-its-00.txt 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 September 12, 2019. 36 Copyright Notice 38 Copyright (c) 2019 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 . . . . . . . . . . . . . . . . . . . 4 59 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 60 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 62 8.2. Informative References . . . . . . . . . . . . . . . . . 4 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 65 1. Introduction 67 Urban Air Mobility (UAM) concerns the introduction of manned and 68 unmanned aircraft within urban environments. NASA has initiated a 69 program known as the Urban Air Mobility grand challenge with the goal 70 to promote public confidence in UAM safety and facilitate community- 71 wide learning while capturing the public's imagination [UAM]. 73 Autonomy will play a pivotal role in the acceptance of low-altitude 74 operations for aerial vehicles operating in harmony with traditional 75 ground transportation and pedestrian traffic. The UAM vision 76 therefore builds on evolving works on Unmanned Air Systems (UAS), 77 including the NASA UAS Traffic Management (UTM) service model [UTM]. 79 Use cases for autonomous aircraft in the UAM vision are endless, and 80 include personal air vehicles, flying taxis, parcel delivery, law 81 enforcement and countless others. Major industry leaders such as 82 Airbus [AIRBUS] and Boeing [BOEING] have accordingly begun to 83 articulate their UAM strategies. Programs such as Uber Elevate 84 [UBER] anticipate deployment as early as within the next 2-5 years. 86 With the advent of the UAM vision and its related initiatives, 87 questions arise as to how the new model will be harmonized with the 88 existing terrestrial mobility environment. Directions for 89 modernizing terrestrial mobility are emerging in programs such as the 90 US Department of Transportation's Intelligent Transportation Systems 91 [ITS] and anticipate an increasing role for Vehicle to Vehicle (V2V) 92 and Vehicle to Infrastructure (V2I) communications. The IETF 93 recognizes this need and has formed the IP Wireless Access in 94 Vehicular Environments (IPWAVE) working group with charter to produce 95 a document that will specify the mechanisms for transmission of IPv6 96 datagrams [RFC8200] over dedicated short-range wireless 97 communications media. 99 This document anticipates a need to provide a unified V2V and V2I 100 service for all urban mobility agents, including both terrestrial and 101 airborne. Urban air vehicles will employ Vertical Takeoff And 102 Landing (VTOL) and will operate at altitudes below 400 feet, such 103 that coordinations with terrestrial vehicles will be inevitable and 104 commonplace. This work therefore proposes that urban air vehicles 105 also employ a short-range V2V / V2I communications capability using 106 the same types of wireless networking gear used in the terrestrial 107 domain (e.g., DSRC, C-V2X, etc.). 109 As stated by the Boeing CEO in a January 23, 2019 press release, 110 think of the urban mobility landscape as evolving from a two 111 dimensional to a three dimensional environment. Vehicles both on the 112 ground and in the air will therefore need to coordinate with one 113 another on a V2V and V2I basis even when supporting communications 114 infrastructure such as cell towers are unavailable or otherwise too 115 congested to support realtime exchanges. The ipwave working group is 116 therefore advised to consider the rapidly emerging and inevitable 117 Urban Air Mobility future. 119 2. Terminology 121 Terms such as Intelligent Transportation Systems (ITS), Urban Air 122 Mobility (UAM), Unmanned Air Systems (UAS), UAS Traffic Management 123 (UTM) and many others apply to the emerging urban mobility landscape. 124 IETF keywords per [RFC2119] are not applicable within the scope of 125 this document. 127 3. Applicability 129 Urban Air Mobility and Intelligent Transportation System concepts 130 apply within all major urban areas worldwide. 132 4. Implementation Status 134 Early prototyping and testing are underway. 136 5. IANA Considerations 138 This document introduces no IANA considerations. 140 6. Security Considerations 142 Communications networking security is necessary to preserve the 143 confidentiality, integrity and availability necessary for V2V and V2I 144 coordinations. 146 7. Acknowledgements 148 Discussions on the IETF ipwave list (its@ietf.org) helped motivate 149 this document. 151 8. References 153 8.1. Normative References 155 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 156 Requirement Levels", BCP 14, RFC 2119, 157 DOI 10.17487/RFC2119, March 1997, 158 . 160 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 161 (IPv6) Specification", STD 86, RFC 8200, 162 DOI 10.17487/RFC8200, July 2017, 163 . 165 8.2. Informative References 167 [AIRBUS] "https://www.airbus.com/innovation/ 168 Urban-air-mobility-the-sky-is-yours.html", November 2018. 170 [BOEING] "http://www.boeing.com/NeXt/common/docs/ 171 Boeing_Future_of_Mobility_White%20Paper.pdf", March 2019. 173 [ITS] "https://www.its.dot.gov/", November 2018. 175 [UAM] "https://www.nasa.gov/uamgc", October 2018. 177 [UBER] "https://www.uber.com/us/en/elevate/", November 2018. 179 [UTM] "https://utm.arc.nasa.gov/index.shtml", March 2019. 181 Author's Address 182 Fred L. Templin (editor) 183 Boeing Research & Technology 184 P.O. Box 3707 185 Seattle, WA 98124 186 USA 188 Email: fltemplin@acm.org