IETF Logo Mail Archive

Re: [tsvwg] UDP Options: on forcing the use of UDP CS=0 in connection with FRAG+LITE

"C. M. Heard" <heard@pobox.com> Mon, 01 July 2019 19:49 UTC

Return-Path: <heard@pobox.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 3C4291200C1 for <tsvwg@ietfa.amsl.com>; Mon, 1 Jul 2019 12:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.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 vSCkvQ7NHc2w for <tsvwg@ietfa.amsl.com>; Mon, 1 Jul 2019 12:49:14 -0700 (PDT)
Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D17F1200D6 for <tsvwg@ietf.org>; Mon, 1 Jul 2019 12:49:14 -0700 (PDT)
Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 38AA5168645 for <tsvwg@ietf.org>; Mon, 1 Jul 2019 15:49:13 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type:content-transfer-encoding; s=sasl; bh=p0RDpW3ZMsoK p6/Zid+MbbjbgTU=; b=ReEXxrREck0Ewe0aBiX10Jfb8Wmk/klI0o550BqQMdD5 w5/n5sqZrMC6A/jvQexqsv8jFHpIjLsnoSzgN/I3+U+qeCvVOG6AJSoldiKHv3QP fzGHIGANmV1lBiSkNvl/xEVC5rTAdFAfd6CqlVp0Psfjk8xpiM7ODdAFFq1KEf0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type:content-transfer-encoding; q=dns; s=sasl; b=P4AM5z bkimrX4eEr4lKsBEKI5PrpymzyhWvIKaw3TS02X3Qcjg7MjXUGP5tWOpcpxg4fsI OjLmtUBCcVxZLxyBSUlM6N/fRLS8l/kQNkdEfwGji90CVebZjR5LQDP7WfvQdrMq lr9da6JKb/1lXui0r4LcmEO0N3PP73RzSxeOw=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 31109168644 for <tsvwg@ietf.org>; Mon, 1 Jul 2019 15:49:13 -0400 (EDT)
Received: from mail-io1-f53.google.com (unknown [209.85.166.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id B0208168643 for <tsvwg@ietf.org>; Mon, 1 Jul 2019 15:49:12 -0400 (EDT)
Received: by mail-io1-f53.google.com with SMTP id s7so31498197iob.11 for <tsvwg@ietf.org>; Mon, 01 Jul 2019 12:49:12 -0700 (PDT)
X-Gm-Message-State: APjAAAX0tepJkcRu+tsTYh7v9UdDEfmnrxV4gfKTdwdIaBIeISqnGjk1 iy8FFQQqeJtpH+c3/1nMCqmE8MHd3H+9yfelkzU=
X-Google-Smtp-Source: APXvYqzxl+3Tj8atCf0+kJIkZ5dXcOEpJ7IW3LOQR8ao/tc2cOeHmqNJk00AQK6CiJNtqusJsAlgg3LWEusAdXE1sJg=
X-Received: by 2002:a6b:8b8b:: with SMTP id n133mr10395834iod.183.1562010552164; Mon, 01 Jul 2019 12:49:12 -0700 (PDT)
MIME-Version: 1.0
References: <CACL_3VHGtMz3htgfFLRGhjXm=qC7kOXQs+cchtamhh-giBnpLA@mail.gmail.com> <CALx6S35T9ApzMaoSVgHSJPpcpfXsbHHogoBbEjMPj6vH-kxYeA@mail.gmail.com> <CACL_3VE6kr33Vk5si5AxSZNmhqysZZGoy6HK37COUgwbvcRkdA@mail.gmail.com> <24692A9B-4AF1-4E32-A760-7D4908A61262@strayalpha.com> <CACL_3VExhAdFCu-kFLLO5DeRYUOFyJztUgJg-vQmnPoecvzeJg@mail.gmail.com> <6DB954BC-8D40-4347-A172-C00FED1AE4AF@strayalpha.com>
In-Reply-To: <6DB954BC-8D40-4347-A172-C00FED1AE4AF@strayalpha.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Mon, 01 Jul 2019 12:49:00 -0700
X-Gmail-Original-Message-ID: <CACL_3VF38oR7emB0K6yrL7Npj4eb-Q-KFVu3=7L66syGaTrJtA@mail.gmail.com>
Message-ID: <CACL_3VF38oR7emB0K6yrL7Npj4eb-Q-KFVu3=7L66syGaTrJtA@mail.gmail.com>
To: Joe Touch <touch@strayalpha.com>
Cc: Tom Herbert <tom@herbertland.com>, TSVWG <tsvwg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Pobox-Relay-ID: 4CD12F88-9C39-11E9-9D51-72EEE64BB12D-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/gWFYAKjFkh5hDk2d511QX7AkTcI>
Subject: Re: [tsvwg] UDP Options: on forcing the use of UDP CS=0 in connection with FRAG+LITE
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: Mon, 01 Jul 2019 19:49:16 -0000

> You haven’t addressed the data copying issue.

Yes, I have, in
https://mailarchive.ietf.org/arch/msg/tsvwg/RJBWi_tiW6M_phfc22zKuVn_vh4

Can you please respond to that message and explain exactly why you think
that the proposal in the thread "DP Options: how to do FRAG without LITE
and forced UDP CS=0" imposes data movement requirements for packet
reassembly beyond those required by FRAG+LITE (or FRAG without LITE) in
in draft-ietf-tsvwg-udp-options-07? I sure don't see it.

Mike

v2.23.0 | Report a Bug | By Email