Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
draft-templin-atn-aero-interface-07
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-09-10
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
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: March 13, 2020 MWA Ltd c/o Inmarsat Global Ltd
September 10, 2019
Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
draft-templin-atn-aero-interface-07.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 connect to access networks using either the classic or
mobility service-enabled link model. 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 March 13, 2020.
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 March 13, 2020 [Page 1]
Internet-Draft IPv6 over AERO Interfaces September 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 . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . 8
9. Address Mapping - Multicast . . . . . . . . . . . . . . . . . 11
10. Address Mapping for IPv6 Neighbor Discovery Messages . . . . 11
11. Conceptual Sending Algorithm . . . . . . . . . . . . . . . . 12
11.1. Multiple Aero Interfaces . . . . . . . . . . . . . . . . 12
12. Router Discovery and Prefix Registration . . . . . . . . . . 13
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
14. Security Considerations . . . . . . . . . . . . . . . . . . . 16
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
16.1. Normative References . . . . . . . . . . . . . . . . . . 17
16.2. Informative References . . . . . . . . . . . . . . . . . 18
Appendix A. Aero Registration Option Extensions for Special-
Purpose Links . . . . . . . . . . . . . . . . . . . 19
Appendix B. Prefix Length Considerations . . . . . . . . . . . . 20
Appendix C. VDL Mode 2 Considerations . . . . . . . . . . . . . 20
Appendix D. RS/RA Messaging as the Single Standard API . . . . . 22
Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
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 independently of the access network data links
selected for data transport. The MN performs router discovery the
Show full document text