Re: [Int-area] IP parcels

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 21 December 2021 15:30 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 97CE13A0ED6 for <int-area@ietfa.amsl.com>; Tue, 21 Dec 2021 07:30:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 ELD3Z_bFZoGp for <int-area@ietfa.amsl.com>; Tue, 21 Dec 2021 07:30:54 -0800 (PST)
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 6C8D43A0EB3 for <int-area@ietf.org>; Tue, 21 Dec 2021 07:30:53 -0800 (PST)
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 1BLFUofd029265; Tue, 21 Dec 2021 10:30:51 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1640100651; bh=TSQRkUGI6Wq2cLwRExG1n5BH452NtDTPWtBtGTRdUmk=; h=From:To:Subject:Date:From; b=g9s3B42ofLRdpQVbnMs/O0aWLpYSECa3sLpAyu+Vq9TN79ZLdmdmiPBoHyHnlKoha XZT4rq3e1Ka5j8e59H4X+1XJpmfXUx20fVjkSNukLrzXwYpJSt7QYb3HAB/TV4txnu 0b+i7oNH13yzerP8T6e/szCA0aFOur6M9M91ZbGid2bChf/0WLQ/aoIVnMj0cfHLLS L4atJGJi4wT7uh9/xyxd7ZYoQWLKN1x1qJsSdNihzgEWu9bROY0b8k8+/4tiqgP97p 5ujrURsfKoCdLdZDVwi/yGiRfQdwwIhGU82XfSP+NOH92ndeGv22Tv6cNMdUdjMBwF 1ut1CAyQZwbZg==
Received: from XCH16-07-10.nos.boeing.com (xch16-07-10.nos.boeing.com [144.115.66.112]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 1BLFUh81029186 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 21 Dec 2021 10:30:43 -0500
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.2308.14; Tue, 21 Dec 2021 07:30:41 -0800
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.2308.014; Tue, 21 Dec 2021 07:30:41 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] IP parcels
Thread-Index: Adf2f36r9jHfv6y0Sb+uetnTzkET5g==
Date: Tue, 21 Dec 2021 15:30:41 +0000
Message-ID: <813c9fded33e45e4b9dd4d1a9e039896@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: B9D6762D831BBC5861C5FA65625087291A099D258B6DB655E11ABDB82446739D2000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/8lhOzZgo2QMy5HSvsj7aT7n9-4Y>
Subject: Re: [Int-area] IP parcels
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: Tue, 21 Dec 2021 15:30:59 -0000

Thank you, Alex - have a great holiday!

Fred

> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Alexandre Petrescu
> Sent: Tuesday, December 21, 2021 7:03 AM
> To: int-area@ietf.org
> Subject: Re: [Int-area] IP parcels
> 
> The title and abstract are great.
> 
> About the title, just one little note.  This word 'parcel' is very well
> adapted and suggestive for an English speaker.  I think I heard it very
> well in US English, even though not sure about UK English - to they also
> use 'parcel' to mean a package sent in mail?  Probably yes.
> 
> An 'IP Parcel' is a new concept, akin to an IP packet, IP datagram, or
> to a TCP segment: it is also a delimited 'chunk' of data sent in the
> network.  It is different than an IP packet in that it is made to be
> able to carry more IP packets inside.  An IP tunnel also is known to
> carry another IP packet which itself could carry another packet
> (encapsulated tunnels); however an IP parcel would be different than an
> IP tunnel in that there are less IP headers, presumably, and no trailers
> at all (IP tunnel encapsulation involves trailers, IIRC).  Maybe I could
> understand that if I read the draft.
> 
> The name 'parcel', to a French speaker, makes think it might be a
> 'parcelle'.  That 'parcelle' is a limited domain, like a part of land.
> In our current discussions of 'limited domains' in the Internet, that
> 'parcelle' confuses me.  It is not an 'IP parcelle' limited domain, but
> an 'IP parcel' packet, even though it is pronounced the same.
> 
> Le 18/12/2021 à 02:06, Templin (US), Fred L a écrit :
> > Here's one that should help with shipping, just in time for
> > Christmas. Thanks to everyone for the past and future list
> > exchanges.
> >
> > Fred
> >
> > -----Original Message----- From: I-D-Announce
> > [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> > internet-drafts@ietf.org Sent: Friday, December 17, 2021 5:00 PM To:
> >  i-d-announce@ietf.org Subject: I-D Action:
> > draft-templin-intarea-parcels-00.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >
> >
> > Title           : IP Parcels Author          : Fred L. Templin
> > Filename        : draft-templin-intarea-parcels-00.txt Pages : 8
> > Date : 2021-12-17
> >
> > Abstract: IP packets (both IPv4 and IPv6) are understood to contain a
> > unit of data which becomes the retransmission unit in case of loss.
> > Upper layer protocols such as the Transmission Control Protocol (TCP)
> > prepare data units known as "segments", with traditional arrangements
> > including a single segment per packet.  This document presents a new
> > construct known as the "IP Parcel" which permits a single packet to
> > carry multiple segments.
> 
> It sounds interesting.
> 
> But I wonder whether the IP parcel carries multiple TCP segments (TCP
> payloads that dont have IP headers) or rather multiple IP packets (an IP
> packet might carry a TCP payload)?
> 
> Maybe it's written in the draft, I will have to look.
> 
> > The parcel can be opened at middleboxes on the path with the included
> > segments broken out into individual packets, then rejoined into one
> > or more repackaged parcels to be forwarded further toward the final
> > destination.  Reordering of segments within parcels is unimportant;
> > what matters is that the number of parcels delivered to the final
> > destination should be kept to a minimum, and that loss or receipt of
> > individual segments (and not parcel size) determines the
> > retransmission unit.
> 
> The _segment_ is retransmitted upon segment loss or the entire parcel is?
> 
> Alex
> 
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-templin-intarea-parcels/
> >
> > There is also an htmlized version available at:
> > https://datatracker.ietf.org/doc/html/draft-templin-intarea-parcels-00
> >
> >
> >
> >
> >
> > Internet-Drafts are also available by rsync at
> > rsync.ietf.org::internet-drafts
> >
> >
> > _______________________________________________ I-D-Announce mailing
> >  list I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft
> > directories: http://www.ietf.org/shadow.html or
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> > _______________________________________________ Int-area mailing
> > list 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