Re: [Int-area] About draft-templin-intarea-parcels

Tom Herbert <tom@herbertland.com> Wed, 09 November 2022 17:22 UTC

Return-Path: <tom@herbertland.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 F34A3C14F75F for <int-area@ietfa.amsl.com>; Wed, 9 Nov 2022 09:22:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01, 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=herbertland-com.20210112.gappssmtp.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 A6NClO_mor0m for <int-area@ietfa.amsl.com>; Wed, 9 Nov 2022 09:22:01 -0800 (PST)
Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com [IPv6:2607:f8b0:4864:20::333]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FABAC14F6E5 for <int-area@ietf.org>; Wed, 9 Nov 2022 09:22:01 -0800 (PST)
Received: by mail-ot1-x333.google.com with SMTP id w26-20020a056830061a00b0066c320f5b49so10488773oti.5 for <int-area@ietf.org>; Wed, 09 Nov 2022 09:22:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=p5kuTr3HAKAQv0hiqdTbUMDMlUR7G9I66/pMNsM3VfE=; b=JZoYGwuKmfjT+GXYCRyfqM0z1cHVmmRGh0j2aHGCpNorzPQw86aUuHqStOBmfGqQfG A6aqnhZYZ0aruVeC1U/dYpk19LDjGc3ITYPdxOuoTh/OMYw7Zz/EVPv21xLbctFHN+Ff XmXkLYWVHjFfoftB+xXWGR3RsSyXi8l8fHYSSkWwbhbrO1TTN9YdLp8Y3RDKh3/RoL36 LG+DjWTP7cENqY6UgefgJ99nd5lJN0rcnD1S47o+KtG84fi6SwQq1oam0JWHwRU6slo/ wRdYnT8X+15+mvqISXiaDL79ed5SBdlpWwahWYcefIqczY408qzo3g05cM4PLo0w9h/b eZYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=p5kuTr3HAKAQv0hiqdTbUMDMlUR7G9I66/pMNsM3VfE=; b=gtEkgO+hE7x16iV/G4yMCmCiakJVe8ADUq9Fn3+fbFCnXfSx9z2an8nI7MMBYuFz17 JO5la6XBnFpALxEN5EsFNo7VH2Ekzwuf6iS3QhUY1fJA+hidfCAwG5MomwYFRhXfB7NB W5TkZWyWLgxz3Ez8BDc53HqIbAThNNs8zivdRYSylVISVc/aEpjKLGNi3aZPeTD5zg9P enNSYuPnVgGIXM4Hw2EXDMU9DYIaFCxodC9Wr1hQy2DljktRS74Nk5xChxVP4LsFK81P 4o4Hen2tRy39qpspSlnFNGIvwHa2zoHUJgNn5hG9McItkNDfhXlGapBrRtiFG2fXRoYU PHFg==
X-Gm-Message-State: ACrzQf2pjAMlWaHemyWJ5hh9L+CiE6AOjS6dtaM8kRqCH0ExF6BHeniO 0Hb8BKtSrU0ONz2MJy31qI4E3Gb9Dz85+P2ZNp+vbw==
X-Google-Smtp-Source: AMsMyM7L0hvaVBfBrZRwPF3YUKPxGpA/S/b0wNSbXd3mmOL4qFKCRsYB8HhQuHbRw4c9U/HdTg0xpN+8cHX6B0kzTBI=
X-Received: by 2002:a05:6830:3141:b0:66c:889a:1228 with SMTP id c1-20020a056830314100b0066c889a1228mr15410718ots.227.1668014520057; Wed, 09 Nov 2022 09:22:00 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <ba38e1e6fe9b45e78899feaba7d81e5a@boeing.com>
From: Tom Herbert <tom@herbertland.com>
Date: Wed, 09 Nov 2022 09:21:49 -0800
Message-ID: <CALx6S37ECdpt97T1phUm+p_zBh80gRDxVybnaCkxr9ZVDOtFJA@mail.gmail.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
Cc: Richard Li <richard.li@futurewei.com>, "int-area@ietf.org" <int-area@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/C2xL_JZ_BvKg-NAZn2sPZG2jVEs>
Subject: Re: [Int-area] 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: Wed, 09 Nov 2022 17:22:02 -0000

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://datatracker.ietf.org/meeting/115/materials/slides-115-intarea-ip-parcels
>
>
>
> Running code is also now permanently available here:
>
>
>
>   https://github.com/fltemplin/ip-parcels
>
>
>
> 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://www.ietf.org/mailman/listinfo/int-area