idnits 2.17.1 draft-templin-v6ops-icao-int-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 (December 10, 2019) is 1592 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'I-D.templin-atn-aero-interface' is defined on line 181, but no explicit reference was found in the text == Outdated reference: A later version (-21) exists of draft-templin-atn-aero-interface-07 Summary: 0 errors (**), 0 flaws (~~), 3 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 The Boeing Company 4 Intended status: Informational December 10, 2019 5 Expires: June 12, 2020 7 An IPv6 Air/Ground Interface for the International Civil Aviation 8 Organization (Use Case) 9 draft-templin-v6ops-icao-int-00 11 Abstract 13 The International Civil Aviation Organization (ICAO) is building a 14 worldwide IPv6-based Air Traffic Management (ATM) service known as 15 the Aeronautical Telecommunications Network with Internet Protocol 16 Services (ATN/IPS). Aircraft connect to the ATN/IPS via an IPv6 Air/ 17 Ground (A/G) interface that provides a nexus for control and data 18 messages exchanges over all available aviation wireless data links. 19 This document discusses the use case that motivates a new IPv6 20 interface abstraction. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on June 12, 2020. 39 Copyright Notice 41 Copyright (c) 2019 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (https://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. An IPv6 Air/Ground Interface for Civil Aviation (Use Case) . 4 59 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 60 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 61 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 62 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 64 7.2. Informative References . . . . . . . . . . . . . . . . . 4 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 67 1. Introduction 69 The International Civil Aviation Organization (ICAO) is building a 70 worldwide IPv6-based Air Traffic Management (ATM) service known as 71 the Aeronautical Telecommunications Network with Internet Protocol 72 Services (ATN/IPS). Aircraft connect to the ATN/IPS via an Air/ 73 Ground (A/G) interface that provides a nexus for control and data 74 message exchanges over all available underlying aviation wireless 75 data links. Aircraft frequently have many data links and use them 76 according to inbound and outbound traffic engineering profiles in a 77 service known as multilink. 79 As an aircraft travels, it's underlying aviation data link profile 80 may change dynamically. For example, data links that are available 81 in the ground domain may not be available at cruise altitudes, and 82 terrestrial cellular services may not be available during trans- 83 oceanic crossings. In still other cases, handoffs within the same 84 access technology could result in readdressing. For these reasons, 85 aircraft and the ATN/IPS must be able to accommodate mobility. 87 The ATN/IPS provides an IPv6 /32 Mobility Service Prefix (MSP), and 88 ICAO further assigns each aircraft a 24-bit Identification value that 89 is unique among all civil aviation aircraft worldwide. From these 90 two values, the aircaft constructs a /56 Mobile Network Prefix (MNP) 91 that travels with the aircraft wherever it goes. For example, if the 92 MSP is 2001:db8::/32 and the aircraft is assiged the Identification 93 value 0x123456, the resulting MNP is 2001:db8:1234:5600::/56. 95 Each aircraft registers its MNP in the ATN/IPS ground-domain mobility 96 service over its active aviation data links. Since many aviation 97 data links have very low-end performance profiles (e.g., 32Kbps) it 98 is imperative that the MNP is conveyed in the fewest possible 99 messages and with the smallest possible message sizes. This service 100 is termed "prefix registration" (as opposed to "prefix delegation") 101 since the aircraft already knows its MNP and is simply asking for it 102 to be registered in the ATN/IPS routing system. 104 Following prefix registration, the aircraft sends IPv6 data messages 105 over the A/G interface and undelying data links according to its 106 traffic engineering profile. The aircraft keeps the number of 107 control messages to a minimum, since the ground domain is responsible 108 for any keepalive messaging on behalf of the aircraft. In this way, 109 reducing contol message overhead on aviation data links presents the 110 greatest possible capacity for carrying actual data. 112 While the ground domain ATN/IPS network will provide a mobility 113 service, the details of the service need not be exposed to the 114 aircraft. Instead, the aircraft simply operates its A/G interface in 115 a manner that allows optimum data plane usage while providing the 116 ground domain with only the necessary and sufficient control message 117 signaling. This document therefore presents a use case for an 118 aircraft A/G interface. 120 2. Terminology 122 The terminology in the normative references applies; especially, the 123 terms "link" and "interface" are the same as defined in the IPv6 124 [RFC8200] and IPv6 Neighbor Discovery (ND) [RFC4861] specifications. 126 The following terms are defined for the purposes of this document: 128 International Civil Aviation Organization (ICAO) 129 The global governing body for civil aviation standards. 131 Air Traffic Management (ATM) 132 A command and control messaging service for coordinating safe 133 aviation operations. 135 Aeronautical Telecommunciations Network with Internet Protocol 136 Services (ATN/IPS) 137 A proposed worldwide IPv6-based network used to enable ATM 138 services between aircraft and air traffic controllers. 140 multilink 141 The ability of an aircraft to coordinate its available aviation 142 data links through traffic engineering link selections. 144 mobility 145 The ability of an aircraft to adapt to changes in its underlying 146 aviation data link connectivity and availability. 148 3. An IPv6 Air/Ground Interface for Civil Aviation (Use Case) 150 Details of the use case are discussed in the Introduction. 152 4. IANA Considerations 154 This document has no requirements for IANA. 156 5. Security Considerations 158 Security considerations are discussed in the references. 160 6. Acknowledgements 162 This document describes the use case for an Air/Ground interface for 163 aircraft operating in the ATN/IPS service. 165 7. References 167 7.1. Normative References 169 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 170 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 171 DOI 10.17487/RFC4861, September 2007, 172 . 174 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 175 (IPv6) Specification", STD 86, RFC 8200, 176 DOI 10.17487/RFC8200, July 2017, 177 . 179 7.2. Informative References 181 [I-D.templin-atn-aero-interface] 182 Templin, F., "Transmission of IPv6 Packets over 183 Aeronautical ("aero") Interfaces", draft-templin-atn-aero- 184 interface-07 (work in progress), September 2019. 186 Author's Address 187 Fred L. Templin (editor) 188 The Boeing Company 189 P.O. Box 3707 190 Seattle, WA 98124 191 USA 193 Email: fltemplin@acm.org