Re: [Int-area] IntArea WG Minutes IETF 113

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Thu, 07 April 2022 19: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 870413A15AC for <int-area@ietfa.amsl.com>; Thu, 7 Apr 2022 12:39:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 89q8l00je3VB for <int-area@ietfa.amsl.com>; Thu, 7 Apr 2022 12:39:06 -0700 (PDT)
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 816EE3A0FBF for <int-area@ietf.org>; Thu, 7 Apr 2022 12:39:05 -0700 (PDT)
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 237Jd1nx004813; Thu, 7 Apr 2022 15:39:03 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1649360343; bh=BZUUmUmSZ25yY2CVh8RM3zMJ0iMoQMVscVPPREYH7R8=; h=From:To:Subject:Date:References:In-Reply-To:From; b=BAXGoRKlAebT7lKioqWuXy/vUgRdTpkCfpeiHSAbWiOehUp0Dej0oGVtvRVPQVRFw 0sAsAc8jGyfrs+IZ/23XbSdtguWPs0RF74Ut9fgaxvz8hxFN1b/6Jk6aYg5RQpKvq/ ZqDHvtgiGrood4CJrma2r+IhLoQ4/y+u4Im48bhGzF9UrSFUHOwoo3X3k9JtoMO5cU 3UprP0k05DoDP9bBerUHNi10Zo7gQfBiqd/qgSpouQkP4HupKfK696lka5PkkPdPvW 7dd3XxMwVAG29aThD6mOtW7R81KxjA83W2BLV9A2n5Z58dxhsM2tOhCDhi8fG3AbLB id+0SptL0XAgA==
Received: from XCH16-07-10.nos.boeing.com (xch16-07-10.nos.boeing.com [144.115.66.112]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 237JcsCe004733 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 7 Apr 2022 15:38:54 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-10.nos.boeing.com (144.115.66.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2375.24; Thu, 7 Apr 2022 12:38:53 -0700
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.2375.024; Thu, 7 Apr 2022 12:38:53 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "Juan Carlos Zuniga (juzuniga)" <juzuniga@cisco.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: IntArea WG Minutes IETF 113
Thread-Index: AQHYQ4fwfA+njNqNy0+RY9FTzpx+l6zbK5eQgAhczs6AAV64UA==
Date: Thu, 07 Apr 2022 19:38:52 +0000
Message-ID: <d964fb99d9284d06ae3b27fcfdb6076b@boeing.com>
References: <MW5PR11MB5761D52DDAC78A6672B41EF6D11E9@MW5PR11MB5761.namprd11.prod.outlook.com> <51b46a04338848eda44c9aae6ad5880f@boeing.com> <MW5PR11MB576115DAE9B9DD9ECC8A8147D1E79@MW5PR11MB5761.namprd11.prod.outlook.com>
In-Reply-To: <MW5PR11MB576115DAE9B9DD9ECC8A8147D1E79@MW5PR11MB5761.namprd11.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: 95CA3B426F8AF37399EE6D71E70257BF23B844A78C9CCC4D17F9BACAD44B9CBA2000:8
Content-Type: multipart/alternative; boundary="_000_d964fb99d9284d06ae3b27fcfdb6076bboeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/WD2-XCby4TyJjxJLxa7g0jvccJk>
Subject: Re: [Int-area] IntArea WG Minutes IETF 113
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: Thu, 07 Apr 2022 19:39:13 -0000

Thanks,

Fred

From: Juan Carlos Zuniga (juzuniga) [mailto:juzuniga@cisco.com]
Sent: Wednesday, April 06, 2022 3:45 PM
To: Templin (US), Fred L <Fred.L.Templin@boeing.com>; int-area@ietf.org
Subject: [EXTERNAL] Re: IntArea WG Minutes IETF 113


EXT email: be mindful of links/attachments.




Hi Fred,

Thanks for the review. The minutes have been corrected accordingly.

https://datatracker.ietf.org/meeting/113/materials/minutes-113-intarea-04

Best,

Juan Carlos & Wassim



From: Templin (US), Fred L <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>>
Date: Friday, April 1, 2022 at 11:19 AM
To: Juan Carlos Zuniga (juzuniga) <juzuniga@cisco.com<mailto:juzuniga@cisco.com>>, int-area@ietf.org<mailto:int-area@ietf.org> <int-area@ietf.org<mailto:int-area@ietf.org>>
Subject: RE: IntArea WG Minutes IETF 113
Juan Carlos & Wassim - see below for corrections to the minutes:

Thank you - Fred

1.      IP Parcels - Fred Templin
draft-templin-intarea-parcels - 15 min
o   Fred: packet is the retransmission unit in case of lost. Have a packet of packets.
>> This is incorrect; what I said was that a "segment" is the retransmission unit in case of loss,
>> and a Parcel may contain multiple segments. In that sense, it is a packet-of-packets.
o   Add a jumbo payload option and not 0 in payload length.
o   IP parcels are based on IP Jumbograms, it can be supported in IPv6 and IPv4.
o   Can we adopt the document as a WG Item ?
o   JCZ: need support on the list
o   Lars: how can this increase performance?
o   Fred: it reduced the numbers of interrupts and the overhead of the parcel.
o   Lars: We already do it on the ends, we have already these efficiencies.
o   Fred: There is no additional efficiency over GSO?
o   Fred: The end systems see the same efficiency that we see with GSO GRO TCP segment offload.
>> Because a Parcel may contain multiple segments, end systems will see better performance
>> than just using GSO/GRO when the Parcel is sent intact over links that have sufficient MTU.
>> Also, GSO/GRO are not and cannot be standardized, whereas IP Parcels can be.
o   Luigi: How will the network have the ability to know how to use the parcel.
o   Lars: We start to send regular IP packets and then you send the probe. If the probe succeeds you can then start using parcels.
>> It was me (Fred) who provided this answer, and not Lars.
o   Luigi: What happens if links in the middle suport IP Parcels but the end doesn't.
o   Lars: Then, it will be like regular IP packets.
>> Again, it was me (Fred) and not Lars who provided the answer. But, it was not made clear
>> that there are two kinds of Parcel-capable links - edge network links that support Parcels
>> natively, and the OMNI link in the middle of the network that supports Parcels through
>> the OMNI Adaptation Layer. There is no need for links in the middle of the network that
>> support Parcels natively.


From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Juan Carlos Zuniga (juzuniga)
Sent: Tuesday, March 29, 2022 9:14 AM
To: int-area@ietf.org<mailto:int-area@ietf.org>
Subject: [EXTERNAL] [Int-area] IntArea WG Minutes IETF 113


EXT email: be mindful of links/attachments.




Hi all,

The minutes of the meeting have been uploaded.

A special note to thank Laurent and Ivan for helping with the notes!

https://datatracker.ietf.org/doc/minutes-113-intarea/

As usual, any comments/corrections on the minutes are welcome.

Best,

Juan Carlos & Wassim