Re: [Int-area] Call for WG adoption of draft-templin-intarea-parcels-10

Tommy Pauly <tpauly@apple.com> Sat, 02 July 2022 00:17 UTC

Return-Path: <tpauly@apple.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 33FAEC14CF1F for <int-area@ietfa.amsl.com>; Fri, 1 Jul 2022 17:17:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.851
X-Spam-Level:
X-Spam-Status: No, score=-2.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.745, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 TjPDSsR2ekX4 for <int-area@ietfa.amsl.com>; Fri, 1 Jul 2022 17:17:37 -0700 (PDT)
Received: from ma1-aaemail-dr-lapp01.apple.com (ma1-aaemail-dr-lapp01.apple.com [17.171.2.60]) (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 43297C159492 for <int-area@ietf.org>; Fri, 1 Jul 2022 17:17:37 -0700 (PDT)
Received: from pps.filterd (ma1-aaemail-dr-lapp01.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp01.apple.com (8.16.0.42/8.16.0.42) with SMTP id 26209Brx017873; Fri, 1 Jul 2022 17:17:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=UjJyTx01dh56H0zmPLtSJbsScDkqWbQ/eCFI79PVcBc=; b=w+Ib7z4lMHDWOCx3Vajz8st3wdUtikJLtFlJpEvaQtQfPOIXPDg6jbkb2/bwPHXwAVrA wWvOA2yNbW2UnlmnG5a3gBlgIM0+72YflpjCa75QEiT+bOTHy5PL1F3qPv+20cB1vlhL jfcEqJp2tMeDlJkI9UnBvSozU/s7+B3WtoE19WYy6Gjm6mVGwZK5QyNwtU7144uOX23m LdFOEJtuR4dxYphmtbKwK7ppcJAOcJfifJb/jZpszX0UNBzrWgWi7HaId2kDD9aa5tNN OIxf35BarHaQMkVoQacGPkMI0LQIYXzLXNr0HmkWx2VrKUewVDHN6rY52ehzSRnNBzGj YA==
Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by ma1-aaemail-dr-lapp01.apple.com with ESMTP id 3gx1158n1y-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 01 Jul 2022 17:17:33 -0700
Received: from rn-mailsvcp-mmp-lapp01.rno.apple.com (rn-mailsvcp-mmp-lapp01.rno.apple.com [17.179.253.14]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) with ESMTPS id <0RED00FCCA59HYI0@rn-mailsvcp-mta-lapp02.rno.apple.com>; Fri, 01 Jul 2022 17:17:33 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp01.rno.apple.com by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) id <0RED01100A1B8000@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Fri, 01 Jul 2022 17:17:33 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 9db7266d4ce0ebad2afdecea1a717fa6
X-Va-E-CD: 749e33ce836291cc86500e6fbf7f8312
X-Va-R-CD: 089ffb98255f45a4d09c1036eecad9b1
X-Va-CD: 0
X-Va-ID: 33d9d407-5962-44c0-a6b3-955e252c400c
X-V-A:
X-V-T-CD: 9db7266d4ce0ebad2afdecea1a717fa6
X-V-E-CD: 749e33ce836291cc86500e6fbf7f8312
X-V-R-CD: 089ffb98255f45a4d09c1036eecad9b1
X-V-CD: 0
X-V-ID: 8f2ba871-c70e-4e53-a360-3db27ec0428b
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.517, 18.0.883 definitions=2022-07-01_16:2022-06-28, 2022-07-01 signatures=0
Received: from smtpclient.apple (unknown [17.234.27.173]) by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) with ESMTPSA id <0RED007JUA580700@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Fri, 01 Jul 2022 17:17:33 -0700 (PDT)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <6F2C276E-5310-403E-B3CE-EE3496BC13A1@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_D9AF52A3-170D-411F-879D-1407B8D85161"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3721.0.2\))
Date: Fri, 01 Jul 2022 17:17:22 -0700
In-reply-to: <CALx6S37r-JuUpSHwJCQK6dU_L4PY5PdQCYiM+iZH6V7uukJRfA@mail.gmail.com>
Cc: "Juan Carlos Zuniga (juzuniga)" <juzuniga=40cisco.com@dmarc.ietf.org>, "int-area@ietf.org" <int-area@ietf.org>
To: Tom Herbert <tom@herbertland.com>
References: <SJ0PR11MB57692D589B130307F4C9C823D1B29@SJ0PR11MB5769.namprd11.prod.outlook.com> <CALx6S37r-JuUpSHwJCQK6dU_L4PY5PdQCYiM+iZH6V7uukJRfA@mail.gmail.com>
X-Mailer: Apple Mail (2.3721.0.2)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.517, 18.0.883 definitions=2022-07-01_16:2022-06-28, 2022-07-01 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/UddURnilohBwe3wpOB1MUpk--s8>
Subject: Re: [Int-area] Call for WG adoption of draft-templin-intarea-parcels-10
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: Sat, 02 Jul 2022 00:17:42 -0000

I agree with the points being raised by Tom and Joel. I don’t think this is something intarea should adopt at this point. If there’s going to be further discussion on this, I’d want to see more explanation of who would intend to support and deploy this solution to the problem.

If this is a matter of sending fewer packets over a particular link of the network, the use of a proxy or tunnel between hosts may equally well solve the problem without needing to make changes at this layer.

Thanks,
Tommy

> On Jul 1, 2022, at 5:06 PM, Tom Herbert <tom@herbertland.com> wrote:
> 
> At this point, I don't see IP parcels as being a significant benefit to host performance which, as I understand it, is the primary motivation. While it's an interesting idea, I don't support adoption.
> 
> A recent patch to the Linux kernel allows for GSO/GRO segments greater than 64K, using RFC2675 Jumbograms to reassemble so those limitations which were discussed on the list have been addressed in implementation. There is a nice writeup in https://lwn.net/Articles/884104/. 
> 
> As Joel mentions moving any sort of reassembly into network devices is complex and problematic. For instance, if a middebox is trying to perform reassembly of packets for a flow not addressed to it, it's implicitly requiring that all packets of the flow that go through the device perform reassembly which is contrary to the end-to-end model. Also, if reassembly requires buffering of messages then that creates a memory requirement on middleboxes; hosts are in a better position to do reassembly since they are only providing the service for themselves as opposed to some number of devices behind a middlebox.
> 
> Tom
> 
> 
> 
> 
> On Wed, Jun 22, 2022 at 12:25 PM Juan Carlos Zuniga (juzuniga) <juzuniga=40cisco.com@dmarc.ietf.org <mailto:40cisco.com@dmarc.ietf.org>> wrote:
>> Dear IntArea WG,
>> 
>>  
>> 
>> We are starting a 2-week call for adoption of the IP-Parcels draft:
>> 
>> https://www.ietf.org/archive/id/draft-templin-intarea-parcels-10.html
>> 
>>  
>> 
>> The document has been discussed for some time and it has received multiple comments.
>> 
>>  
>> 
>> If you have an opinion on whether this document should be adopted by the IntArea WG please indicate it on the list by the end of Wednesday July 6th.
>> 
>>  
>> 
>> Thanks,
>> 
>>  
>> 
>> Juan-Carlos & Wassim
>> 
>> (IntArea WG chairs)
>> 
>>  
>> 
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org <mailto:Int-area@ietf.org>
>> https://www.ietf.org/mailman/listinfo/int-area
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area