Ground-Based LISP for the Aeronautical Telecommunications Network
draft-haindl-lisp-gb-atn-03

Document Type Active Internet-Draft (individual)
Last updated 2019-06-07
Replaces draft-haindl-ground-lisp-atn
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
LISP Working Group                                             B. Haindl
Internet-Draft                                                M. Lindner
Intended status: Informational                                Frequentis
Expires: December 9, 2019                                      R. Rahman
                                                             M. Portoles
                                                               V. Moreno
                                                                F. Maino
                                                    B. Venkatachalapathy
                                                           Cisco Systems
                                                            June 7, 2019

   Ground-Based LISP for the Aeronautical Telecommunications Network
                      draft-haindl-lisp-gb-atn-03

Abstract

   This document describes the use of the LISP architecture and
   protocols to address the requirements of the worldwide Aeronautical
   Telecommunications Network with Internet Protocol Services, as
   articulated by the International Civil Aviation Organization.

   The ground-based LISP overlay provides mobility and multi-homing
   services to the IPv6 networks hosted on commercial aircrafts, to
   support Air Traffic Management communications with Air Traffic
   Controllers and Air Operation Controllers.  The proposed architecture
   doesn't require support for LISP protocol in the airborne routers,
   and can be easily deployed over existing ground infrastructures.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

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

Haindl, et al.          Expires December 9, 2019                [Page 1]
Internet-Draft          draft-haindl-lisp-gb-atn               June 2019

   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 9, 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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Definition of Terms . . . . . . . . . . . . . . . . . . . . .   3
   3.  Design Overview . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Basic Protocol Operation  . . . . . . . . . . . . . . . . . .   7
     4.1.  Endsystem Registration  . . . . . . . . . . . . . . . . .   7
     4.2.  Ground to Airborne Traffic Flow . . . . . . . . . . . . .   8
     4.3.  Airborne to Ground Traffic Flow . . . . . . . . . . . . .   8
     4.4.  Default forwarding path . . . . . . . . . . . . . . . . .   9
     4.5.  Traffic symmetry  . . . . . . . . . . . . . . . . . . . .  10
   5.  Multi-Homing and Mobility . . . . . . . . . . . . . . . . . .  10
   6.  Convergence . . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Use of RLOC-probing . . . . . . . . . . . . . . . . . . .  12
     6.2.  Use of Solicit-Map-Request  . . . . . . . . . . . . . . .  12
     6.3.  Use of LISP pub-sub . . . . . . . . . . . . . . . . . . .  12
   7.  Multi-domain structure of the ATN/IPS . . . . . . . . . . . .  13
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
     8.1.  LISP Basic Security Mechanisms  . . . . . . . . . . . . .  13
     8.2.  Control Plane overload protection . . . . . . . . . . . .  14
     8.3.  Protecting the LISP control plane from overclaim attacks   14
     8.4.  LISP Reliable Transport . . . . . . . . . . . . . . . . .  14
     8.5.  Reachability Control  . . . . . . . . . . . . . . . . . .  15
     8.6.  Data Plane Security . . . . . . . . . . . . . . . . . . .  16
       8.6.1.  Segmentation  . . . . . . . . . . . . . . . . . . . .  16
Show full document text