Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
draft-templin-atn-aero-interface-02

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10
• 11
• 12
• 13
• 14
• 15
• 16
• 17
• 18
• 19
• 20
• 21

Network Working Group                                    F. Templin, Ed.
Internet-Draft                              Boeing Research & Technology
Intended status: Standards Track                               A. Whyman
Expires: December 15, 2019               MWA Ltd c/o Inmarsat Global Ltd
                                                           June 13, 2019

   Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
                draft-templin-atn-aero-interface-02.txt

Abstract

   Mobile nodes (e.g., aircraft of various configurations) communicate
   with networked correspondents over multiple access network data links
   and configure mobile routers to connect their on-board networks.
   Mobile nodes configure a virtual interface (termed the "aero
   interface") as a thin layer over their underlying data link
   interfaces.  This document specifies the transmission of IPv6 packets
   over aeronautical ("aero") interfaces.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 15, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

Templin & Whyman        Expires December 15, 2019               [Page 1]
Internet-Draft          IPv6 over AERO Interfaces              June 2019

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Aeronautical ("aero") Interface Model . . . . . . . . . . . .   4
   5.  Maximum Transmission Unit . . . . . . . . . . . . . . . . . .   5
   6.  Frame Format  . . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Link-Local Addresses  . . . . . . . . . . . . . . . . . . . .   6
   8.  Address Mapping - Unicast . . . . . . . . . . . . . . . . . .   6
   9.  Address Mapping - Multicast . . . . . . . . . . . . . . . . .   9
   10. Mobility Service Discovery  . . . . . . . . . . . . . . . . .   9
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   12. Security Considerations . . . . . . . . . . . . . . . . . . .  11
   13. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     14.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     14.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Appendix A.  Aero Option Extensions for Special-Purpose Links . .  13
   Appendix B.  Prefix Length Considerations . . . . . . . . . . . .  15
   Appendix C.  Change Log . . . . . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   Mobile Nodes (MNs) such as aircraft of various configurations may
   have multiple data links for communicating with networked
   correspondents.  These data links often have differing performance,
   cost and availability characteristics that can change dynamically
   according to mobility patterns, flight phases, proximity to
   infrastructure, etc.

   Each MN receives an IPv6 Mobile Network Prefix (MNP) that can be used
   by on-board networks regardless of the actual link or links selected
   for data transport.  The MN performs router discovery the same as for
   customer edge routers [RFC7084], and acts as a mobile router on
   behalf of its on-board networks.  A virtual interface (termed the
   "aero interface") is configured as a thin layer over the underlying
   access network data link interfaces.

   The aero interface is therefore the only interface abstraction
   exposed to the IPv6 layer and behaves according to the Non-Broadcast,
   Multiple Access (NBMA) interface principle, while underlying access