Re: [Int-area] [EXTERNAL] Re: About draft-templin-intarea-parcels
"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Thu, 10 November 2022 17:12 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 74534C1524A0 for <int-area@ietfa.amsl.com>; Thu, 10 Nov 2022 09:12:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 6vHHcG-TUh-V for <int-area@ietfa.amsl.com>; Thu, 10 Nov 2022 09:12:47 -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 BFFEAC14CF10 for <int-area@ietf.org>; Thu, 10 Nov 2022 09:12:46 -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 2AAHCiLc019379; Thu, 10 Nov 2022 12:12:44 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1668100364; bh=AnIizwq0Hnrbp5Gk/YH6AjnFB87fBJKZeKl61uODYHg=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=t1FMMoIYcWkH7JS2TxAsb/mSZ0j80ozochhA1sqSMIrsxr6CzIRjDLdoEYIN/QQX0 GfMdbWMnBG1KARxbp707KyaImfu4DAn+/kPTaLjFi67g9A+/RXJvwXZLkhjSWFrH/Q doVW1mQFZKHnQ51l9RqeucNL6dWHFsdJjkPP+qOkxCyAe0dHS8EG82FMFHnl9UjCSf qo0dm4Cd8ugOdC6n6Lsob+xb+b0hNKZSoaqu/ncnTqEMOGdA0UpqvfT5Iv6oEv7GQF t4l0XqOSmxF1mWkgcFwIWpcGdFXJz4HZFMU+E4CcfmmwvTy4SsbSS6tZP9wMhYvpUY poxdD7N+V56GA==
Received: from XCH16-07-07.nos.boeing.com (xch16-07-07.nos.boeing.com [144.115.66.109]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 2AAHCeAR019334 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 10 Nov 2022 12:12:40 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-07.nos.boeing.com (144.115.66.109) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.12; Thu, 10 Nov 2022 09:12:38 -0800
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.012; Thu, 10 Nov 2022 09:12:38 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Haoyu Song <haoyu.song@futurewei.com>, Tom Herbert <tom@herbertland.com>
CC: "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] [EXTERNAL] Re: About draft-templin-intarea-parcels
Thread-Index: AQHY9Sba7wMQvPDG+EigdYYlyXLB9q44Y/6w
Date: Thu, 10 Nov 2022 17:12:38 +0000
Message-ID: <f343796ceaf540b59f624e218bba7231@boeing.com>
References: <SJ0PR11MB57692D589B130307F4C9C823D1B29@SJ0PR11MB5769.namprd11.prod.outlook.com> <BYAPR13MB2279C0291E3AC5998958824D87BD9@BYAPR13MB2279.namprd13.prod.outlook.com> <4c8d5f4708e449fbb2c1828b5b7f05af@boeing.com> <BYAPR13MB22794A6FEBD6EBF5EB900D16873E9@BYAPR13MB2279.namprd13.prod.outlook.com> <ba38e1e6fe9b45e78899feaba7d81e5a@boeing.com> <CALx6S37ECdpt97T1phUm+p_zBh80gRDxVybnaCkxr9ZVDOtFJA@mail.gmail.com> <3d16be77134844088f3e32456d3bf9f2@boeing.com> <BY3PR13MB4787FF15984AD3070368492A9A019@BY3PR13MB4787.namprd13.prod.outlook.com>
In-Reply-To: <BY3PR13MB4787FF15984AD3070368492A9A019@BY3PR13MB4787.namprd13.prod.outlook.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: E259D17A55BEF0D86BC6E740AA9785DD06B3C9B4B4F5945DFB521AA92D3CAF922000: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/int-area/Vc5mJ0etvvEMNkKMZNTT_FIePzg>
Subject: Re: [Int-area] [EXTERNAL] Re: About draft-templin-intarea-parcels
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 10 Nov 2022 17:12:51 -0000
Hi Haoyu - I appreciate your qualifying your message as coming from a researcher's perspective, but the IETF is about engineering and IP parcels is about engineering. It is here and now and ready to go - it is not to be put on some research back-burner that maybe we come back to 20 years from now. Fred > -----Original Message----- > From: Haoyu Song <haoyu.song@futurewei.com> > Sent: Thursday, November 10, 2022 9:04 AM > To: Templin (US), Fred L <Fred.L.Templin@boeing.com>; Tom Herbert <tom@herbertland.com> > Cc: int-area@ietf.org > Subject: RE: [Int-area] [EXTERNAL] Re: About draft-templin-intarea-parcels > > EXT email: be mindful of links/attachments. > > > > As a researcher, I'd like to provide a suggestion. Given its potentially profound impact to the Internet, I think the blind peer reviews for its > design and evaluation are needed in some top tier research conferences such as SIGCOMM. If it is accepted by the research community, it'll > also help people here gain confidence on it. The PoC code is a good start, more comprehensive tests using both a simulator and a real > network setup would be necessary, and the cost/benefit should also be evaluated. A real promising scheme should be able to sustain such > review (the research community tends to focus more on novelty and feasibility but less on the pragmatic side of a scheme). I believe such > effort can help clear many doubts here and then the standardization can be considered as the next step. > > Best regards, > Haoyu > > -----Original Message----- > From: Int-area <int-area-bounces@ietf.org> On Behalf Of Templin (US), Fred L > Sent: Thursday, November 10, 2022 4:35 PM > To: Tom Herbert <tom@herbertland.com> > Cc: int-area@ietf.org > Subject: Re: [Int-area] [EXTERNAL] Re: About draft-templin-intarea-parcels > > Tom, IP parcels have a very significant difference from the GSO/GRO and others you mentioned in that IP parcels allow a *single* packet to > contain *multiple* upper layer protocol segments; in all of the other schemes you cited, it is always a single ULP segment per packet. This > alone demonstrates that IP parcels at the very least provides a significant savings in terms of reduced packet headers, since only a single > copy of the {TCP,UDP}/IP headers appears and not multiple. > > The maximum IP parcel size is also not constrained by the underlying network path MTU the same way that the maximum GSO/GRO packet > size is. So, even if the path MTU is only 1500 IP parcels up to 64KB and even larger can be sent over an OMNI interface configured over the > path. If you did that with GSO, then the packets would arrive at the destination fragmented and as you know in linux GRO cannot apply > UDP/IP reassembly to packets that have already undergone fragmentation at the sub-IP layer. Yes, you can linearize the packets but the > second you do that any GRO performance gains are lost. > > You mentioned data centers going to 9KB, and while that is good it is still way smaller than what we should be aiming for. IP parcels will > encourage links with much larger MTUs - 64KB is just a starting point, and going much larger into multiple MBs can be a near-term goal. > Yes, IP parcels can take full advantage of 9KB MTUs right away and still be better than the other schemes because larger MTUs at the sub-IP > layer result in less IPv6 fragmentation and associated savings in sub-IP layer encapsulation overhead. > > IP parcels can be thought of as a gateway to larger MTUs in the Internet without having to compromise integrity and/or without having to > retransmit lots of big blocks of data if only just one or a couple of bits were damaged in transit. The IP parcels philosophy is to accept as > much good data as possible while asking for retransmission only of errored data that cannot be locally repaired. This will be good for a vast > array of bulk-transfer Internetworking applications, not only within the local data center but also across the wide area using OMNI. > > I could go on, but I won't for now. I have done the work, and I have shown the work. The community now needs to apply a check-mark to > acknowledge. > > Fred > > > -----Original Message----- > > From: Tom Herbert <tom@herbertland.com> > > Sent: Wednesday, November 09, 2022 9:22 AM > > To: Templin (US), Fred L <Fred.L.Templin@boeing.com> > > Cc: Richard Li <richard.li@futurewei.com>; int-area@ietf.org > > Subject: [EXTERNAL] Re: [Int-area] About draft-templin-intarea-parcels > > > > EXT email: be mindful of links/attachments. > > > > > > > > On Wed, Nov 9, 2022 at 7:47 AM Templin (US), Fred L > > <Fred.L.Templin@boeing.com> wrote: > > > > > > Richard, thank you for your message. The intarea community must > > > understand that > > > > > > the live IP Parcels presentation given today was only a "roadmap" to > > > a proper > > > > > > presentation which could not be given due to time constraints. The > > > charts shown > > > > > > during the live presentation were skipped over quickly, but they > > > provide full > > > > > > detail and are permanently available here: > > > > > > > > > > > > > > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fda > > > tatracker.ietf.org%2Fmeeting%2F115%2Fmaterials%2Fslides-115-intarea- > > > ip-parcels&data=05%7C01%7Chaoyu.song%40futurewei.com%7Cf3d70ea49 > > > 53d4a476cb808dac339892c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7 > > > C638036949165322831%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ > > > IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata > > > =pEndNpnEOWuQctTp54syiw7zL8%2F%2FFM0ib6P6JTY%2Bri0%3D&reserved=0 > > > > > > > > > > > > Running code is also now permanently available here: > > > > > > > > > > > > > > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi > > > thub.com%2Ffltemplin%2Fip-parcels&data=05%7C01%7Chaoyu.song%40fu > > > turewei.com%7Cf3d70ea4953d4a476cb808dac339892c%7C0fee8ff2a3b240189c7 > > > 53a1d5591fedc%7C1%7C0%7C638036949165322831%7CUnknown%7CTWFpbGZsb3d8e > > > yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C > > > 3000%7C%7C%7C&sdata=8%2FUkWd1FnslqWOiMO%2FTeOykcI7HoPLYr3eUY9NIJ > > > zEQ%3D&reserved=0 > > > > > > > > > > > > and provides clear evidence that IP parcels provide an appreciable > > > performance > > > > > > gain which cannot be ignored any longer. > > > > > > > > > > > > IP parcels are good for the Internet, and the presentation charts > > > and running code > > > > > > provide clear evidence. It is time to adopt IP parcels. > > > > Fred, > > > > Thanks for the data and implementation, but I'm still not convinced > > that IP parcels should be adopted. Your data seems to show that when > > the networking stack processes large segments performance increases > > (fewer packets to process in the data path is a win). We've known this > > for a long time and that's why stacks commonly implement various > > segmentation techniques like GSO/TSO, GRO/LRO, UFO, USO, and more > > recently BigTCP. Also, within the data center, 9K MTUs are becoming > > common place which is even better than segmentation with 1500 byte > > MTU. The major difference between these techniques and IP parcels is > > that the segmentation techniques don't require any new protocol or > > changes to an existing protocol, whereas IP parcels requires protocol > > changes. So in order to justify IP parcels adoption, not just in IETF > > but also upstreaming into Linux, I think you'll want to show that it > > has significant benefits over the existing segmentation techniques to > > justify the complexities and cost of a new protocol. > > > > Tom > > > > > > > > > > > > > > Fred > > > > > > > > > > > > From: Int-area <int-area-bounces@ietf.org> On Behalf Of Richard Li > > > Sent: Wednesday, November 09, 2022 6:12 AM > > > To: int-area@ietf.org > > > Subject: [Int-area] About draft-templin-intarea-parcels > > > > > > > > > > > > Hi Chairs and All, > > > > > > > > > > > > At today's intarea meeting, the chair asked the participants if > > > anybody has an interest in this draft or not. If nobody is > > > interested, this draft > > will be closed, and if anyone is interested, he/she is asked to voice it on the mailing list. > > > > > > > > > > > > As a follow up, I am expressing my interest in this draft, and would > > > like to see this draft open and let it go on. A few months ago, I > > > asked > > its authors several questions, and the authors answered and clarified > > them. I do see good values for some use cases, especially for those in > > broadband access and jumbo frames being used on the links. It seems to me that this draft points to a useful direction, some rooms are > remaining for expansion though. > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Richard > > > > > > > > > > > > _______________________________________________ > > > Int-area mailing list > > > Int-area@ietf.org > > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww > > > w.ietf.org%2Fmailman%2Flistinfo%2Fint-area&data=05%7C01%7Chaoyu. > > > song%40futurewei.com%7Cf3d70ea4953d4a476cb808dac339892c%7C0fee8ff2a3 > > > b240189c753a1d5591fedc%7C1%7C0%7C638036949165322831%7CUnknown%7CTWFp > > > bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6 > > > Mn0%3D%7C3000%7C%7C%7C&sdata=ZjlouJMjtalnJWJwi%2Bw0QvEId%2FjYGPw > > > 21HYupE34M04%3D&reserved=0 > > _______________________________________________ > Int-area mailing list > Int-area@ietf.org > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fint- > area&data=05%7C01%7Chaoyu.song%40futurewei.com%7Cf3d70ea4953d4a476cb808dac339892c%7C0fee8ff2a3b240189c753a1d55 > 91fedc%7C1%7C0%7C638036949165322831%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwi > LCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZjlouJMjtalnJWJwi%2Bw0QvEId%2FjYGPw21HYupE34M04%3D&reserved=0
- [Int-area] Call for WG adoption of draft-templin-… Juan Carlos Zuniga (juzuniga)
- Re: [Int-area] Call for WG adoption of draft-temp… Richard Li
- Re: [Int-area] Call for WG adoption of draft-temp… Templin (US), Fred L
- Re: [Int-area] Call for WG adoption of draft-temp… Joel Halpern
- Re: [Int-area] Call for WG adoption of draft-temp… Tom Herbert
- Re: [Int-area] Call for WG adoption of draft-temp… Tommy Pauly
- Re: [Int-area] Call for WG adoption of draft-temp… Bob Hinden
- Re: [Int-area] Call for WG adoption of draft-temp… Gyan Mishra
- [Int-area] Jumbograms [was: Call for WG adoption … Brian E Carpenter
- Re: [Int-area] Jumbograms [was: Call for WG adopt… Gyan Mishra
- Re: [Int-area] Call for WG adoption of draft-temp… Tom Herbert
- Re: [Int-area] Jumbograms [was: Call for WG adopt… Brian E Carpenter
- Re: [Int-area] Jumbograms [was: Call for WG adopt… Gyan Mishra
- Re: [Int-area] Call for WG adoption of draft-temp… Gyan Mishra
- Re: [Int-area] Call for WG adoption of draft-temp… Tom Herbert
- Re: [Int-area] Call for WG adoption of draft-temp… Gyan Mishra
- Re: [Int-area] Jumbograms [was: Call for WG adopt… Richard Li
- Re: [Int-area] Call for WG adoption of draft-temp… Templin (US), Fred L
- Re: [Int-area] Call for WG adoption of draft-temp… Tom Herbert
- Re: [Int-area] [EXTERNAL] Re: Call for WG adoptio… Templin (US), Fred L
- Re: [Int-area] [EXTERNAL] Re: Call for WG adoptio… Tom Herbert
- Re: [Int-area] [EXTERNAL] Re: Call for WG adoptio… Templin (US), Fred L
- Re: [Int-area] [EXTERNAL] Re: Call for WG adoptio… Joel Halpern
- Re: [Int-area] Call for WG adoption of draft-temp… Templin (US), Fred L
- Re: [Int-area] [EXTERNAL] Re: Call for WG adoptio… Robinson, Herbie
- Re: [Int-area] Call for WG adoption of draft-temp… Tom Herbert
- Re: [Int-area] Call for WG adoption of draft-temp… Joel Halpern
- Re: [Int-area] [EXTERNAL] Re: Call for WG adoptio… Tom Herbert
- Re: [Int-area] Call for WG adoption of draft-temp… Templin (US), Fred L
- Re: [Int-area] Call for WG adoption of draft-temp… Templin (US), Fred L
- Re: [Int-area] Call for WG adoption of draft-temp… Tom Herbert
- Re: [Int-area] Call for WG adoption of draft-temp… Joel Halpern
- Re: [Int-area] Call for WG adoption of draft-temp… Templin (US), Fred L
- Re: [Int-area] Call for WG adoption of draft-temp… Joel Halpern
- Re: [Int-area] Call for WG adoption of draft-temp… Templin (US), Fred L
- Re: [Int-area] [EXTERNAL] Re: Re: Call for WG ado… Templin (US), Fred L
- Re: [Int-area] [EXTERNAL] Re: Re: Call for WG ado… Joel Halpern
- Re: [Int-area] [EXTERNAL] Re: Re: Call for WG ado… Templin (US), Fred L
- Re: [Int-area] Call for WG adoption of draft-temp… Tom Herbert
- Re: [Int-area] [EXTERNAL] Re: Re: Call for WG ado… Tom Herbert
- Re: [Int-area] [EXTERNAL] Re: Re: Call for WG ado… Templin (US), Fred L
- Re: [Int-area] [EXTERNAL] Re: Re: Call for WG ado… Tom Herbert
- Re: [Int-area] [EXTERNAL] Re: Re: Call for WG ado… Templin (US), Fred L
- Re: [Int-area] Call for WG adoption of draft-temp… Juan Carlos Zuniga (juzuniga)
- Re: [Int-area] Call for WG adoption of draft-temp… Haoyu Song
- Re: [Int-area] Call for WG adoption of draft-temp… Templin (US), Fred L
- Re: [Int-area] Call for WG adoption of draft-temp… Templin (US), Fred L
- Re: [Int-area] Call for WG adoption of draft-temp… Tom Herbert
- Re: [Int-area] [EXTERNAL] Re: Call for WG adoptio… Templin (US), Fred L
- [Int-area] About draft-templin-intarea-parcels Richard Li
- Re: [Int-area] About draft-templin-intarea-parcels Templin (US), Fred L
- Re: [Int-area] About draft-templin-intarea-parcels Tom Herbert
- Re: [Int-area] [EXTERNAL] Re: About draft-templin… Templin (US), Fred L
- Re: [Int-area] [EXTERNAL] Re: About draft-templin… Haoyu Song
- Re: [Int-area] [EXTERNAL] Re: About draft-templin… Templin (US), Fred L
- Re: [Int-area] [EXTERNAL] Re: About draft-templin… Tom Herbert
- Re: [Int-area] About draft-templin-intarea-parcels Templin (US), Fred L