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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2019-06-29 (latest revision 2019-06-28)
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                    F. Templin, Ed.
Internet-Draft                              Boeing Research & Technology
Intended status: Standards Track                               A. Whyman
Expires: December 31, 2019               MWA Ltd c/o Inmarsat Global Ltd
                                                           June 29, 2019

   Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
                draft-templin-atn-aero-interface-04.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 31, 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 31, 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 . . . . . . . . . . . . . . . . . .   6
   6.  Frame Format  . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Link-Local Addresses  . . . . . . . . . . . . . . . . . . . .   6
   8.  Address Mapping - Unicast . . . . . . . . . . . . . . . . . .   7
   9.  Address Mapping - Multicast . . . . . . . . . . . . . . . . .   9
   10. Conceptual Sending Algorithm  . . . . . . . . . . . . . . . .   9
     10.1.  Multiple Aero Interfaces . . . . . . . . . . . . . . . .  10
   11. Router and Prefix Discovery . . . . . . . . . . . . . . . . .  11
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   13. Security Considerations . . . . . . . . . . . . . . . . . . .  13
   14. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   15. References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     15.1.  Normative References . . . . . . . . . . . . . . . . . .  14
     15.2.  Informative References . . . . . . . . . . . . . . . . .  15
   Appendix A.  Aero Option Extensions for Special-Purpose Links . .  15
   Appendix B.  Prefix Length Considerations . . . . . . . . . . . .  16
   Appendix C.  Change Log . . . . . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

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 access network data 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 interfaces.

   The aero interface is therefore the only interface abstraction
Show full document text