Transmission of IPv6 Packets over AERO Interfaces
draft-templin-atn-aero-interface-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-03-29
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
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: September 30, 2019 MWA Ltd c/o Inmarsat Global Ltd
March 29, 2019
Transmission of IPv6 Packets over AERO Interfaces
draft-templin-atn-aero-interface-00.txt
Abstract
Mobile nodes (e.g., aircraft of various configurations) act as mobile
routers for their on-board networks, and may have multiple data links
for communicating with networked correspondents. 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 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 September 30, 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
Templin & Whyman Expires September 30, 2019 [Page 1]
Internet-Draft IPv6 over AERO Interfaces March 2019
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 . . . . . . . . . . . . . . . . . . . . . . . . 3
4. AERO Interface Model . . . . . . . . . . . . . . . . . . . . 4
5. Maximum Transmission Unit . . . . . . . . . . . . . . . . . . 4
6. Frame Format . . . . . . . . . . . . . . . . . . . . . . . . 6
7. Link-Local Addresses . . . . . . . . . . . . . . . . . . . . 6
8. Address Mapping - Unicast . . . . . . . . . . . . . . . . . . 7
9. Address Mapping - Multicast . . . . . . . . . . . . . . . . . 10
10. Router Discovery and MNP Assertion . . . . . . . . . . . . . 10
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
12. Security Considerations . . . . . . . . . . . . . . . . . . . 11
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
14.1. Normative References . . . . . . . . . . . . . . . . . . 12
14.2. Informative References . . . . . . . . . . . . . . . . . 12
Appendix A. S/TLLAO Extensions for Special-Purpose Links . . . . 13
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
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 acts as a mobile router on behalf of its
on-board networks, but appears as a multi-addressed host from the
perspective of off-board correspondents. This implies the need for a
virtual interface (termed the "AERO interface") configured as a thin
layer over the underlying 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. This document
specifies the transmission of IPv6 packets [RFC8200] over AERO
Show full document text