<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc strict='yes'?>
<?rfc iprnotified='no'?>
<rfc category="info" docName="draft-templin-v6ops-icao-int-00"
     ipr="trust200902" obsoletes="">
  <front>
    <title abbrev="A/G Interface for Civil Aviation">An IPv6 Air/Ground
    Interface for the International Civil Aviation Organization (Use
    Case)</title>

    <author fullname="Fred L. Templin" initials="F. L." role="editor"
            surname="Templin">
      <organization>The Boeing Company</organization>

      <address>
        <postal>
          <street>P.O. Box 3707</street>

          <city>Seattle</city>

          <region>WA</region>

          <code>98124</code>

          <country>USA</country>
        </postal>

        <email>fltemplin@acm.org</email>
      </address>
    </author>

    <date day="10" month="December" year="2019"/>

    <keyword>I-D</keyword>

    <keyword>Internet-Draft</keyword>

    <abstract>
      <t>The International Civil Aviation Organization (ICAO) is building a
      worldwide IPv6-based Air Traffic Management (ATM) service known as the
      Aeronautical Telecommunications Network with Internet Protocol Services
      (ATN/IPS). Aircraft connect to the ATN/IPS via an IPv6 Air/Ground (A/G)
      interface that provides a nexus for control and data messages exchanges
      over all available aviation wireless data links. This document discusses
      the use case that motivates a new IPv6 interface abstraction.</t>
    </abstract>
  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <t>The International Civil Aviation Organization (ICAO) is building a
      worldwide IPv6-based Air Traffic Management (ATM) service known as the
      Aeronautical Telecommunications Network with Internet Protocol Services
      (ATN/IPS). Aircraft connect to the ATN/IPS via an Air/Ground (A/G)
      interface that provides a nexus for control and data message exchanges
      over all available underlying aviation wireless data links. Aircraft
      frequently have many data links and use them according to inbound and
      outbound traffic engineering profiles in a service known as
      multilink.</t>

      <t>As an aircraft travels, it's underlying aviation data link profile
      may change dynamically. For example, data links that are available in
      the ground domain may not be available at cruise altitudes, and
      terrestrial cellular services may not be available during trans-oceanic
      crossings. In still other cases, handoffs within the same access
      technology could result in readdressing. For these reasons, aircraft and
      the ATN/IPS must be able to accommodate mobility.</t>

      <t>The ATN/IPS provides an IPv6 /32 Mobility Service Prefix (MSP), and
      ICAO further assigns each aircraft a 24-bit Identification value that is
      unique among all civil aviation aircraft worldwide. From these two
      values, the aircaft constructs a /56 Mobile Network Prefix (MNP) that
      travels with the aircraft wherever it goes. For example, if the MSP is
      2001:db8::/32 and the aircraft is assiged the Identification value
      0x123456, the resulting MNP is 2001:db8:1234:5600::/56.</t>

      <t>Each aircraft registers its MNP in the ATN/IPS ground-domain mobility
      service over its active aviation data links. Since many aviation data
      links have very low-end performance profiles (e.g., 32Kbps) it is
      imperative that the MNP is conveyed in the fewest possible messages and
      with the smallest possible message sizes. This service is termed "prefix
      registration" (as opposed to "prefix delegation") since the aircraft
      already knows its MNP and is simply asking for it to be registered in
      the ATN/IPS routing system.</t>

      <t>Following prefix registration, the aircraft sends IPv6 data messages
      over the A/G interface and undelying data links according to its traffic
      engineering profile. The aircraft keeps the number of control messages
      to a minimum, since the ground domain is responsible for any keepalive
      messaging on behalf of the aircraft. In this way, reducing contol
      message overhead on aviation data links presents the greatest possible
      capacity for carrying actual data.</t>

      <t>While the ground domain ATN/IPS network will provide a mobility
      service, the details of the service need not be exposed to the aircraft.
      Instead, the aircraft simply operates its A/G interface in a manner that
      allows optimum data plane usage while providing the ground domain with
      only the necessary and sufficient control message signaling. This
      document therefore presents a use case for an aircraft A/G
      interface.</t>
    </section>

    <section anchor="terminology" title="Terminology">
      <t>The terminology in the normative references applies; especially, the
      terms "link" and "interface" are the same as defined in the IPv6 <xref
      target="RFC8200"/> and IPv6 Neighbor Discovery (ND) <xref
      target="RFC4861"/> specifications.</t>

      <t>The following terms are defined for the purposes of this
      document:</t>

      <t><list style="hanging">
          <t
          hangText="International Civil Aviation Organization (ICAO)"><vspace/>The
          global governing body for civil aviation standards.</t>

          <t hangText="Air Traffic Management (ATM)"><vspace/>A command and
          control messaging service for coordinating safe aviation
          operations.</t>

          <t
          hangText="Aeronautical Telecommunciations Network with Internet Protocol Services (ATN/IPS)"><vspace/>A
          proposed worldwide IPv6-based network used to enable ATM services
          between aircraft and air traffic controllers.</t>

          <t hangText="multilink"><vspace/>The ability of an aircraft to
          coordinate its available aviation data links through traffic
          engineering link selections.</t>

          <t hangText="mobility"><vspace/>The ability of an aircraft to adapt
          to changes in its underlying aviation data link connectivity and
          availability.</t>
        </list></t>
    </section>

    <section anchor="use-case"
             title="An IPv6 Air/Ground Interface for Civil Aviation (Use Case)">
      <t>Details of the use case are discussed in the Introduction.</t>
    </section>

    <section anchor="iana" title="IANA Considerations">
      <t>This document has no requirements for IANA.</t>
    </section>

    <section anchor="secure" title="Security Considerations">
      <t>Security considerations are discussed in the references.</t>
    </section>

    <section anchor="ack" title="Acknowledgements">
      <t>This document describes the use case for an Air/Ground interface for
      aircraft operating in the ATN/IPS service.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.8200"?>

      <?rfc include="reference.RFC.4861"?>

      <?rfc ?>
    </references>

    <references title="Informative References">
      <?rfc include="reference.I-D.templin-atn-aero-interface"?>
    </references>
  </back>
</rfc>
