Transmission of IPv6 Packets over Overlay Multilink Network (OMNI) Interfaces
draft-templin-atn-aero-interface-19
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-02-06
|
|
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: August 9, 2020 MWA Ltd c/o Inmarsat Global Ltd
February 6, 2020
Transmission of IPv6 Packets over Overlay Multilink Network (OMNI)
Interfaces
draft-templin-atn-aero-interface-19
Abstract
Mobile nodes (e.g., aircraft of various configurations, terrestrial
vehicles, seagoing vessels, mobile enterprise devices, etc.)
communicate with networked correspondents over multiple access
network data links and configure mobile routers to connect end user
networks. A multilink interface specification is therefore needed
for coordination with the network-based mobility service. This
document specifies the transmission of IPv6 packets over Overlay
Multilink Network (OMNI) 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 August 9, 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
Templin & Whyman Expires August 9, 2020 [Page 1]
Internet-Draft IPv6 over OMNI Interfaces February 2020
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Overlay Multilink Network (OMNI) Interface Model . . . . . . 5
5. Maximum Transmission Unit and Fragmentataion . . . . . . . . 9
6. Frame Format . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Link-Local Addresses . . . . . . . . . . . . . . . . . . . . 9
8. Address Mapping - Unicast . . . . . . . . . . . . . . . . . . 10
9. Address Mapping - Multicast . . . . . . . . . . . . . . . . . 13
10. Address Mapping for IPv6 Neighbor Discovery Messages . . . . 13
11. Conceptual Sending Algorithm . . . . . . . . . . . . . . . . 14
11.1. Multiple OMNI Interfaces . . . . . . . . . . . . . . . . 14
12. Router Discovery and Prefix Registration . . . . . . . . . . 15
13. AR and MSE Resilience . . . . . . . . . . . . . . . . . . . . 18
14. Detecting and Responding to MSE Failures . . . . . . . . . . 18
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
16. Security Considerations . . . . . . . . . . . . . . . . . . . 19
17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
18. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
18.1. Normative References . . . . . . . . . . . . . . . . . . 20
18.2. Informative References . . . . . . . . . . . . . . . . . 21
Appendix A. OMNI Option Extensions for Pseudo-DSCP Mappings . . 23
Appendix B. Prefix Length Considerations . . . . . . . . . . . . 23
Appendix C. VDL Mode 2 Considerations . . . . . . . . . . . . . 24
Appendix D. Change Log . . . . . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction
Mobile Nodes (MNs) (e.g., aircraft of various configurations,
terrestrial vehicles, seagoing vessels, mobile enterprise devices,
etc.) often have multiple data links for communicating with networked
correspondents. These data links may have diverse performance, cost
and availability properties that can change dynamically according to
mobility patterns, flight phases, proximity to infrastructure, etc.
MNs coordinate their data links in a discipline known as "multilink",
Show full document text