IETF Logo Mail Archive

Re: [tsvwg] design assumptions - draft-ietf-udp-options - trying to see the bigger picture

Joe Touch <touch@strayalpha.com> Thu, 18 July 2019 20:40 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB157120090 for <tsvwg@ietfa.amsl.com>; Thu, 18 Jul 2019 13:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 Xtkstff_rUp1 for <tsvwg@ietfa.amsl.com>; Thu, 18 Jul 2019 13:40:55 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 9DC10120074 for <tsvwg@ietf.org>; Thu, 18 Jul 2019 13:40:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=iyS3LKTHz9omHtbZ1YUYtu5CD3OzJhWTemhz6mjAYtM=; b=wk8ELFj0tRQkYgDzCs6wJhDVI ZW7CBWaArKnOi5MVkdvYJww8aLTsebVCiuNn/F/q1F8vGkpBGBKHa7z9svfIhZUs/uH5A4j6dxdQR Om4KQ26f5vxXwEGfgr2RyIJHPjdeR6cqXaXiFziZL+y0Fq37hzOvT1Ti7mcGDVESZMMhxrBDYrBJC dGZbmxStn0D01Plv5/FOsDQmp85eGEB+qDvmDgQ1pSgS9Sxwp4QH25GNcTI7TSspDUvHZOaaRaIU0 KHIsv0SYp8WR7E6jCe9x+GLzkshAcvro3vyXEY9b8ArIkKSggCJmnWJ33o0+z2W3W3iaUCAxGMHjE amXtUuJaA==;
Received: from [38.64.80.138] (port=58996 helo=[172.21.15.93]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1hoDCt-003NJZ-HI; Thu, 18 Jul 2019 16:40:55 -0400
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Joe Touch <touch@strayalpha.com>
X-Mailer: iPhone Mail (16F203)
In-Reply-To: <5D30B12A.9020405@erg.abdn.ac.uk>
Date: Thu, 18 Jul 2019 13:40:51 -0700
Cc: tsvwg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D94D08A-758B-47BA-B629-FCE027038EA7@strayalpha.com>
References: <CAPDqMeq9GjEQKukH1pZOTdE50e_rc3U6gpdxT-5qrS5phD0RGw@mail.gmail.com> <0ce46e21249f0dc55310b192d382f50a@strayalpha.com> <CALx6S36gaMqNRo_hYKr45T_vTkUB-vRrYRYJz2_KgvejNsJtLQ@mail.gmail.com> <efbf65646a0e0d2535dc5726b34f3472@strayalpha.com> <CALx6S37sZxmGQJq5mxDiF88NeUjj2HMRnQG5KyZA_4ujrLJkqg@mail.gmail.com> <079d7d849d0e6260497a6c0ed37595a2@strayalpha.com> <CALx6S37wOkz0436CmevOjSe=VwAxKstSR9Jc66PUmXwUKK4vBw@mail.gmail.com> <075C3166-DF88-4160-8E6C-1C32511F4D46@strayalpha.com> <811C4C35-48D8-4382-A4B4-784FAC1B9F1D@strayalpha.com> <787AE7BB302AE849A7480A190F8B93302F797897@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <198F5F25-7ECE-431C-A7F2-F0CCFC0BDAA9@strayalpha.com> <787AE7BB302AE849A7480A190F8B93302FA63BED@OPEXCNORMAE.corporate.adroot.infra.ftgroup> <5D304C35.5020004@erg.abdn.ac.uk> <01CB5F98-8B08-4F0A-9067-E1FA837292E0@strayalpha.com> <5D309EF6.2040403@erg.abdn.ac.uk> <8ab75ec2aac4e03ecba6200fda17524c@strayalpha.com> <5D30B12A.9020405@erg.abdn.ac.uk>
To: gorry@erg.abdn.ac.uk
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/WtfTnBUswIATbxGQdzc5ldi69Ek>
Subject: Re: [tsvwg] design assumptions - draft-ietf-udp-options - trying to see the bigger picture
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2019 20:40:57 -0000


On Jul 18, 2019, at 10:49 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:

>> only move is to the first few bytes (the swap). That's exactly why it won't be efficient otherwise - it requires staging the fragments somewhere else which involves a copy.
> Do you moev to reassemble, or just leave a chain of fragments?

If the fragments come in order there is no need to move anything.  In other cases there may be but that may be unavoidable. 

Joe

v2.23.0 | Report a Bug | By Email