OMNI interface - MTU

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 18 February 2020 16:50 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B4061208A6; Tue, 18 Feb 2020 08:50:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Plp_zWwH_32v; Tue, 18 Feb 2020 08:50:20 -0800 (PST)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F716120875; Tue, 18 Feb 2020 08:50:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 01IGoFPx019775; Tue, 18 Feb 2020 11:50:18 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1582044618; bh=GNqF32slqRrqWOc3XCgYRgSS7NV30BeVBE+f8Kp8E6M=; h=From:To:Subject:Date:From; b=QFKuiKkDsKaiv7Fmafw3LzXM7xuJs5d0NH5M5naLAgi6ExD8fpv9cPZt6nZEJClt5 nSYoWeYq1xgMfejG86V5HYJWWC1pyz9ELIZwNmmvOUW+frI5ZcOwyL56oeOmRs21uE LyuzQ+pZq4O/SR44eUtsIVHg31S/pZYL/2dkJX4DR4E31oobc9sV8QWLQx2woEGNEZ 8h4/3TBQheJyh3UjS9SUQpzF0nPhtQflSoDRc5etfhzZ9yZ11Ey0/JJlkQnizr6Fcu Wt722ObVFMBso4XSXXH7Exizd1agOMs18RAh+HwNYBhkge9bE710vTC6ToN4dqagL2 7MkXL1f6KonQA==
Received: from XCH16-07-10.nos.boeing.com (xch16-07-10.nos.boeing.com [144.115.66.112]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 01IGo490018536 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Tue, 18 Feb 2020 11:50:04 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-10.nos.boeing.com (144.115.66.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1913.5; Tue, 18 Feb 2020 08:50:03 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.1913.005; Tue, 18 Feb 2020 08:50:03 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>, "atn@ietf.org" <atn@ietf.org>
Subject: OMNI interface - MTU
Thread-Topic: OMNI interface - MTU
Thread-Index: AdXmedVdjwpwzVSgRiqhefM2/T8jqA==
Date: Tue, 18 Feb 2020 16:50:02 +0000
Message-ID: <796970f6d0894efa9ef3b3e20fd386bf@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 079E7ECFBA12ABA508F6EA84608C8CBF8678B7CAB27A10F49DD58E2BF74978BE2000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/QUr0b3CXKbCoMx3ogQ85592V_aE>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2020 16:50:23 -0000

Like any IPv6 interface, the OMNI interface must configure a Maximum Transmission Unit (MTU)
that provides the IPv6 layer with a maximum size that the interface can transport as a single unit.
The OMNI spec mandates that the OMNI interface MTU is 9180 bytes (see: RFC2492) but this
means that the interface must be adaptive in its dealings with underlying interfaces that may
have different MTU sizes. For example, if the OMNI interface is configured over three underlying
interfaces with MTUs 1280, 1500 and 9000 the OMNI interface needs to decide what to do when
a large packet (e.g., 4096 byes) arrives. For the 9000 interface, the OMNI interface can just send
the packet out according to the native underlying interface frame format. For the 1280 and 1500
interfaces, however, the OMNI interface has two options: 1) drop and return a Packet Too Big,
or 2) Encapsulate using link-layer encapsulation per RFC2473 and employ IPv6 fragmentation
and reassembly. Both approaches will provide correct behavior, but 1) maybe more prone to
dropping packets and returning PTB, while 2) may provide improved performance at the
expense of including additional code. Please bring any discussion points regarding the OMNI
interface MTU under this thread.

Fred

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Templin (US), Fred L
> Sent: Tuesday, February 18, 2020 8:07 AM
> To: ipv6@ietf.org; atn@ietf.org
> Subject: FW: I-D Action: draft-templin-6man-omni-interface-00.txt
> 
> 6man and atn list members,
> 
> We have received direction to rename the OMNI interface draft to more closely match the
> document title and to indicate the target working group. This submission therefore replaces
> the former draft name thread, and should be used as the basis for further discussion.
> 
> The OMNI interface spec introduces many important constructs that would be very difficult
> to track in a single discussion thread. I will initiate multiple sub-threads to invite discussion
> on specific aspects of the document in subsequent messages.
> 
> Thanks - Fred
> 
> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Tuesday, February 18, 2020 7:35 AM
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-templin-6man-omni-interface-00.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Transmission of IPv6 Packets over Overlay Multilink Network (OMNI) Interfaces
>         Authors         : Fred L. Templin
>                           Tony Whyman
> 	Filename        : draft-templin-6man-omni-interface-00.txt
> 	Pages           : 36
> 	Date            : 2020-02-18
> 
> 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.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-templin-6man-omni-interface/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-templin-6man-omni-interface-00
> https://datatracker.ietf.org/doc/html/draft-templin-6man-omni-interface-00
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------