IETF Logo Mail Archive

Re: [arch-d] IAB Technical Discussion on Fragmentation: 2023-05-03

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Thu, 04 May 2023 20:14 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D52E5C152D9D; Thu, 4 May 2023 13:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id smajrrVEAf9y; Thu, 4 May 2023 13:14:07 -0700 (PDT)
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 78911C17B35B; Thu, 4 May 2023 13:12:10 -0700 (PDT)
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 344KC9Rb018062; Thu, 4 May 2023 16:12:09 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1683231129; bh=OO0dpg1xQHj7KOrJvTv3zEgRX7LWI7njUgzga14fya4=; h=From:To:Subject:Date:From; b=EJcII1XWqTZWRfTB1UvEjk/cjl4diz5W9MfNfIAykJruHT0H4i1NgknrkfZ6PgiiV v4sPYqEnXVQ9mRn9/tyLLR5C6Ea6t5K0K9Whfjgb6R4tFeHWwWr34Ftdux5CUfXRu5 t7WTDcVnoKbOgGHWM8NKM5njoCoMyk3AYnrdPXrfvjXrb+GaUwvIWkh5zMp6Cp6yXO 8dV2PUCe8PCtyKPRdBt4aDP9qpl9vnxCT7bTdmAqNVzX7dvfIq9Jhz+nuHfOE03g0i z9sHH/a6we4j31aE8cOwtdpvDocNOJK+2Kz5/2H9UV4XMTf1z7xErrs4b1H+odx80l M3bYRv8gGNoVQ==
Received: from XCH16-07-11.nos.boeing.com (xch16-07-11.nos.boeing.com [144.115.66.113]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 344KBv7m017956 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 4 May 2023 16:11:57 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-11.nos.boeing.com (144.115.66.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.17; Thu, 4 May 2023 13:11:56 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.2507.017; Thu, 4 May 2023 13:11:56 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Internet Architecture Board <iab@iab.org>, "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>
Thread-Topic: [arch-d] IAB Technical Discussion on Fragmentation: 2023-05-03
Thread-Index: Adl+wkEwiqiENZE/S/KAQdcjYhdu0w==
Date: Thu, 04 May 2023 20:11:56 +0000
Message-ID: <0f0da4833f81463b972558d972285595@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: 66F16221EFB98583EEEA12CDBC36997B8473BC58B9A9E057FBB87BDAD2EF02302000:8
Content-Type: multipart/alternative; boundary="_000_0f0da4833f81463b972558d972285595boeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/9ecE8P1znnEYmV7l7jdMU1SIks0>
Subject: Re: [arch-d] IAB Technical Discussion on Fragmentation: 2023-05-03
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 May 2023 20:14:10 -0000

Hi, I don’t know what all of this is about or what was discussed, but no technical discussion on

fragmentation can be complete without a consideration of OMNI and IP parcels:



https://datatracker.ietf.org/doc/draft-templin-intarea-omni/

https://datatracker.ietf.org/doc/draft-templin-intarea-parcels/



The IETF seems to want to ignore these and pretend they don’t exist, but all things must pass.

OMNI and IP parcels have profound implications for fragmentation and reassembly in the

Internet, so if it is now time to discuss such things then perhaps their time has come.



Respectfully,



Fred Templin

v2.23.0 | Report a Bug | By Email