Re: [Int-area] Side meeting follow-up: What exact features do we want from the Internet?

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Wed, 08 December 2021 01:39 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D3DF3A07C1 for <int-area@ietfa.amsl.com>; Tue, 7 Dec 2021 17:39:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 bauxnw-Rz-1p for <int-area@ietfa.amsl.com>; Tue, 7 Dec 2021 17:39:04 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 C43F33A07BF for <int-area@ietf.org>; Tue, 7 Dec 2021 17:39:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 1B81cxSX016405; Tue, 7 Dec 2021 20:39:01 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1638927542; bh=aurCLr+JzdEeSsaYZrNE+HVCbODR0fn4BF4fdeydP00=; h=From:To:CC:Subject:Date:From; b=vVHciprAKTjQMsuqDnSOQYx4vZ2dAvIq+2Z2hUG5GCtFzQ8vNp4kisLE7l3La+wLF GguiLBJKySAPWh6fdxm6/3bsuXfwbixSg2x/dzDSL0b2QaB1nxVuq/nTFc9YGlmBEO sPl2sYZxX0nkuoDMeBnbcRGy7Pu7yqwkELDdQ3PXNm+GavOPAkBqOYNYs4SnTS71wp IzuWT4BtbzHOY5sX+K8DYtdhCE5Udfb3NO6koVQQGycC+VUijklYpHeA++XFaPK05e +FDQINxR7IUYnRzCVBuBpCnPQChuKvIaRCgrFYZ4+KVfL0WVOOHT2bpHghc4NT5GlS dbQGI9OyUyS2g==
Received: from XCH16-07-08.nos.boeing.com (xch16-07-08.nos.boeing.com [144.115.66.110]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 1B81cqdJ016363 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 7 Dec 2021 20:38:52 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-08.nos.boeing.com (144.115.66.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2308.14; Tue, 7 Dec 2021 17:38:51 -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.2308.014; Tue, 7 Dec 2021 17:38:51 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "touch@strayalpha.com" <touch@strayalpha.com>, Dino Farinacci <farinacci@gmail.com>
CC: "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] Side meeting follow-up: What exact features do we want from the Internet?
Thread-Index: Adfr0LIX77Thl37bQbWUYNCnTdbg/g==
Date: Wed, 08 Dec 2021 01:38:51 +0000
Message-ID: <f559cfbde8a64b6eab6b8862bf1d00aa@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: D9AE9DAF6BEF903F7B285F6C10F7C1429AE689DBF8276EDCEEE2316B844B70992000:8
Content-Type: multipart/alternative; boundary="_000_f559cfbde8a64b6eab6b8862bf1d00aaboeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/tUcbBGVzjVGJeJ6CUJTKz_2dac8>
Subject: Re: [Int-area] Side meeting follow-up: What exact features do we want from the Internet?
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area WG Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2021 01:39:10 -0000

This conversation is missing some fundamental points – really the most important
points – which are the minimum sizes guaranteed to work everywhere. For IPv6,
the minimum MTU/MRU are 1280/1500. For IPv4, they are only 68/576 but since
the IPv4 network supports fragmentation we can nominally designate the IPv4
minimum MTU as 576 also if we clear the DF bit. It means that, without probing
or having some divine knowledge of paths that have not been previously visited,
the ONLY sizes guaranteed to work are 1280 for IPv6 and 576 for IPv4.

Now take the case of Multinet where a path may traverse multiple concatenated
IP networks of arbitrary IP protocol versions - remember “Catenet”? Since there
may be no advanced knowledge of network IP protocol versions, the most we can
absolutely and for sure count on across the entire path is 576.

What this gives us is not the *maximum packet size*; instead, it determines the
*minimum cell size*. We know that a 576 cell will traverse all paths, so we never
send a non-final cell smaller than this (which might trigger a tiny fragment alarm).
But, we can certainly send packets larger than the path MTU - *much* larger in
many cases. And for paths that support them, we can also send Brian’s jumbograms.

Speaking of jumbos, on a different list I made a point about how this all harkens back
to RFC1149 and RFC6214. But nowadays, we can imagine substituting a memory stick
for the slips of paper with whitestuff and blackstuff and those avian carriers will
transport jumbos just fine. Not quite unlimited MTU, but close enough.

Fred