Network Working Group F. Templin, Ed. Internet-Draft The Boeing Company Intended status: Standards Track A. Whyman Expires: April 12, 2021 MWA Ltd c/o Inmarsat Global Ltd October 9, 2020 IPv6 Neighbor Discovery Overlay Multilink Network Interface (OMNI) Option draft-templin-6man-omni-option-00 Abstract A new IPv6 Neighbor Discovery (ND) option termed the "Overlay Multilink Network (OMNI) Interface Option" is defined. This option may appear in any IPv6 ND message type; it is processed by interfaces that recognize the option and ignored by all other 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 April 12, 2021. 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 include Simplified BSD License text as described in Section 4.e of Templin & Whyman Expires April 12, 2021 [Page 1] Internet-Draft IPv6 ND OMNI Option October 2020 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. The Overlay Multilink Network Interface (OMNI) IPv6 ND Option 2 3.1. Sub-Options . . . . . . . . . . . . . . . . . . . . . . . 3 3.1.1. Pad1 . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1.2. PadN . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1.3. Interface Attributes . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . 6 7.2. Informative References . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction This document defines a new IPv6 Neighbor Discovery (ND) option termed the "Overlay Multilink Network (OMNI) Interface Option". This option may appear in any IPv6 ND message type; it is processed by interfaces that recognize the option and ignored by all other interfaces. This document requests a "reclaimable" IPv6 ND option code according to Section 13 of [RFC4861]. 2. Terminology The terminology in the normative references applies. 3. The Overlay Multilink Network Interface (OMNI) IPv6 ND Option An Overlay Multilink Network Interface (OMNI) IPv6 ND option is defined. The option (known as the "OMNI option") is formatted as shown in Figure 1: Templin & Whyman Expires April 12, 2021 [Page 2] Internet-Draft IPv6 ND OMNI Option October 2020 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Preamble | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ Sub-Options ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: OMNI Option Format In this format: o Type is set to TBD. o Length is set to the number of 8 octet blocks in the option. o Preamble is a 2-octet fixed-length opaque field with no pre- defined values. The field format and associated values is specified by IPv6-over-(foo) documents that recognize the option. o Sub-Options is a Variable-length field, of length such that the complete OMNI Option is an integer multiple of 8 octets long. Contains one or more Sub-Options, as described in Section 3.1. 3.1. Sub-Options The OMNI option includes zero or more Sub-Options. Each consecutive Sub-Option is concatenated immediately after its predecessor. All Sub-Options except Pad1 (see below) are in type-length-value (TLV) encoded in the following format: 0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- | Sub-Type | Sub-length | Sub-Option Data ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Figure 2: Sub-Option Format o Sub-Type is a 1-octet field that encodes the Sub-Option type. Sub-Options defined in this document are: Templin & Whyman Expires April 12, 2021 [Page 3] Internet-Draft IPv6 ND OMNI Option October 2020 Option Name Sub-Type Pad1 0 PadN 1 Interface Attributes 2 Figure 3 Sub-Types 253 and 254 are reserved for experimentation. o Sub-Length is a 1-octet field that encodes the length of the Sub- Option Data (i.e., ranging from 0 to 255 octets). o Sub-Option Data is a block of data with format determined by Sub- Type. During processing, unrecognized Sub-Options are ignored and the next Sub-Option processed until the end of the OMNI option is reached. The following Sub-Option types and formats are defined in this document: 3.1.1. Pad1 0 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ | Sub-Type=0 | +-+-+-+-+-+-+-+-+ Figure 4: Pad1 o Sub-Type is set to 0. If multiple instances appear in the same OMNI option all are processed. o No Sub-Length or Sub-Option Data follows (i.e., the "Sub-Option" consists of a single zero octet). 3.1.2. PadN 0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- | Sub-Type=1 | Sub-length=N | N padding octets ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Figure 5: PadN Templin & Whyman Expires April 12, 2021 [Page 4] Internet-Draft IPv6 ND OMNI Option October 2020 o Sub-Type is set to 1. If multiple instances appear in the same OMNI option all are processed. o Sub-Length is set to N (from 0 to 255) being the number of padding octets that follow. o Sub-Option Data consists of N zero-valued octets. 3.1.3. Interface Attributes 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sub-Type=2 | Sub-length=N | ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ ~ ~ ~ Attributes ~ ~ ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 6: Interface Attributes o Sub-Type is set to 2. If multiple instances appear in the same OMNI option all are processed. o Sub-Length is set to N (from 0 to 255) that encodes the number of Sub-Option Data octets that follow. o Sub-Option Data contains an opaque "Attributes" block. The block format is specified by IPv6-over-(foo) documents that recognize the option. 4. IANA Considerations The IANA is instructed to allocate a reclaimable Type number TBD from the registry "IPv6 Neighbor Discovery Option Formats" for the OMNI option according to the provisons outlined in Section 13 of [RFC4861]. 5. Security Considerations Security considerations for IPv6 [RFC8200] and IPv6 Neighbor Discovery [RFC4861] apply. Templin & Whyman Expires April 12, 2021 [Page 5] Internet-Draft IPv6 ND OMNI Option October 2020 6. Acknowledgements This document is aligned with the IETF 6man (IPv6) working group. 7. References 7.1. Normative References [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, DOI 10.17487/RFC4861, September 2007, . [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", STD 86, RFC 8200, DOI 10.17487/RFC8200, July 2017, . 7.2. Informative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . Authors' Addresses Fred L. Templin (editor) The Boeing Company P.O. Box 3707 Seattle, WA 98124 USA Email: fltemplin@acm.org Tony Whyman MWA Ltd c/o Inmarsat Global Ltd 99 City Road London EC1Y 1AX England Email: tony.whyman@mccallumwhyman.com Templin & Whyman Expires April 12, 2021 [Page 6]