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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2020-01-02 (latest revision 2020-01-01)
Replaced by draft-templin-6man-omni-interface
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) 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                                        The Boeing Company
Intended status: Standards Track                               A. Whyman
Expires: July 5, 2020                    MWA Ltd c/o Inmarsat Global Ltd
                                                         January 2, 2020

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

Abstract

   Aeronautical 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.  An Air-to-Ground (A/G) interface specification is
   therefore needed for coordination with the ground domain network.
   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 July 5, 2020.

Copyright Notice

   Copyright (c) 2020 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 July 5, 2020                  [Page 1]
Internet-Draft          IPv6 over AERO Interfaces           January 2020

   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 . . . . . . . . . . . . . . . . . .   7
   6.  Frame Format  . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Link-Local Addresses  . . . . . . . . . . . . . . . . . . . .   7
   8.  Address Mapping - Unicast . . . . . . . . . . . . . . . . . .   8
   9.  Address Mapping - Multicast . . . . . . . . . . . . . . . . .  12
   10. Address Mapping for IPv6 Neighbor Discovery Messages  . . . .  13
   11. Conceptual Sending Algorithm  . . . . . . . . . . . . . . . .  13
     11.1.  Multiple Aero Interfaces . . . . . . . . . . . . . . . .  14
   12. Router Discovery and Prefix Registration  . . . . . . . . . .  14
   13. Detecting and Responding to MSE Failures  . . . . . . . . . .  17
   14. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   15. Security Considerations . . . . . . . . . . . . . . . . . . .  18
   16. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  18
   17. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     17.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     17.2.  Informative References . . . . . . . . . . . . . . . . .  20
   Appendix A.  AERO Option Extensions for Pseudo-DSCP Mappings  . .  21
   Appendix B.  Prefix Length Considerations . . . . . . . . . . . .  22
   Appendix C.  VDL Mode 2 Considerations  . . . . . . . . . . . . .  22
   Appendix D.  Change Log . . . . . . . . . . . . . . . . . . . . .  23
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  25

1.  Introduction

   Aeronautical Mobile Nodes (MNs) such as aircraft of various
   configurations often have multiple data links for communicating with
   networked correspondents.  These data links may 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 independently of the access network data links
   selected for data transport.  The MN performs router discovery (i.e.,
   similar to IPv6 customer edge routers [RFC7084]) and acts as a mobile
Show full document text