Re: [tsvwg] Alternative version of the UDP FRAG option
"C. M. Heard" <heard@pobox.com> Tue, 12 March 2019 22:56 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 50F561200D7 for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2019 15:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_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 nC1mgNP56VXE for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2019 15:56:20 -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 2F16212799F for <tsvwg@ietf.org>; Tue, 12 Mar 2019 15:56:20 -0700 (PDT)
Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 8F2FF13E879 for <tsvwg@ietf.org>; Tue, 12 Mar 2019 18:56:18 -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; s=sasl; bh=07xY1Gt+x5hJ9MikwmSIW92B5xU=; b=cOqP1r omfpH4JdjbG8QyWBZ+137nDgMcjXuZiCTOcRy5pifC6xRGve5J/zOQDrqoZnp8KN KnzdseDgWI9GkkMu2+ytNgiaehTgUz4MtTMPWkc9kLmJqx1QyVCgfWN/SgbBySbN dnLsfIs9Bis2mN6HXtT5LvoCD7P85YsTh6F+Y=
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; q=dns; s=sasl; b=nROOcvpI1BPXNUzPgwd/RQFzU7Dg4x5/ wYMn3pPF/0KMp4oEhFYSXneyWhAAgSdVCURZ9tEfb22uRlROmuZ0H65EcmtUMXeL Xk5XGM0x2Ol0ML4+BYRLXn1QFHf7u2P874HWec5EnEap5NDxwrAoCuiRVE+QOITk htgMSXLGukQ=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 86E0113E878 for <tsvwg@ietf.org>; Tue, 12 Mar 2019 18:56:18 -0400 (EDT)
Received: from mail-it1-f180.google.com (unknown [209.85.166.180]) (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 1ED9413E875 for <tsvwg@ietf.org>; Tue, 12 Mar 2019 18:56:18 -0400 (EDT)
Received: by mail-it1-f180.google.com with SMTP id v83so7274185itf.1 for <tsvwg@ietf.org>; Tue, 12 Mar 2019 15:56:18 -0700 (PDT)
X-Gm-Message-State: APjAAAUoOrybJVV/cUwMwlZZr0oWJNHq2NGbZwM3iFp4+z+MNawjj3pW 5SOP2+3toMMpgh2eWj59DdlLaPMuVgzwnzMZHfI=
X-Google-Smtp-Source: APXvYqzq1aZmzEpPeUTAHnK4iJIAysdNs2bOU1KrbEUSHR18VR88d7qbUK9ACb22tkRptkYVqv1AvFcAf5m7Dwtnqg8=
X-Received: by 2002:a24:5647:: with SMTP id o68mr109808itb.151.1552431377584; Tue, 12 Mar 2019 15:56:17 -0700 (PDT)
MIME-Version: 1.0
References: <CACL_3VE1=0OORUuOKg9GjcdVuhBNTkWhymE7PAs5WYO0ZR0DWQ@mail.gmail.com> <2C035E8C-A59F-4523-9B8D-BBA573C6DEFB@strayalpha.com> <CACL_3VGQo2ObRohJysQ=oWE4fZ1S6MCrytZQZYweuvKToJs_tw@mail.gmail.com> <36A94382-699D-4F8E-BF49-C48D7D784ACC@strayalpha.com> <CACL_3VE-U=t=rg_smtLGTyEyCGjLS8X9yNbPVh-NH38MsaEtzg@mail.gmail.com> <a47d7cadc5e45cf88ec1ed685a4ed393@erg.abdn.ac.uk> <c85b116427aed247b085258ceec58280@strayalpha.com>
In-Reply-To: <c85b116427aed247b085258ceec58280@strayalpha.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Tue, 12 Mar 2019 15:56:06 -0700
X-Gmail-Original-Message-ID: <CACL_3VE00=Cfi+VG8dJsM7+9Ck_QrPjdXRQXO2kx22SkAfLZHQ@mail.gmail.com>
Message-ID: <CACL_3VE00=Cfi+VG8dJsM7+9Ck_QrPjdXRQXO2kx22SkAfLZHQ@mail.gmail.com>
To: Joe Touch <touch@strayalpha.com>
Cc: Raffaele Zullo <raffaele@erg.abdn.ac.uk>, "C. M. Heard" <heard@pobox.com>, tsvwg <tsvwg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
X-Pobox-Relay-ID: 0BD3D90C-451A-11E9-8937-DF19F34BB12D-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/qV_KJFMkw0u7fBJYx-5Tw223wiQ>
Subject: Re: [tsvwg] Alternative version of the UDP FRAG option
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: Tue, 12 Mar 2019 22:56:23 -0000
On Tue, Mar 12, 2019 at 3:40 PM Joe Touch wrote: > I'm still not following the need for this alternative. > > FRAG+LITE works fine - even through broken middleboxes with the checksum > bug - if used with CS=0, which is how it ought to be used. Not all of us agree that this is how it ought to be used, since CS=0 affords no protection for the UDP header itself. > The trailing checksum in the last fragment is over the reassembled total > (or not if also zero) and there's no utility in checksumming the fragments > themselves. My position is that the level of protection that we should strive to achieve is what is available with conventional IP fragmentation coupled with the standard UDP checksum. That combination protects the entire UDP datagram, including the UDP header. The trailing checksum the terminal FRAG option, when used with CS=0, does not do that. A second reason for preferring this proposal to FRAG as now presented in the draft is that it eliminates the hazard of FRAG without LITE. Mike Heard
- Re: [tsvwg] Alternative version of the UDP FRAG o… C. M. Heard
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… C. M. Heard
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… Derek Fawcus
- Re: [tsvwg] Alternative version of the UDP FRAG o… C. M. Heard
- Re: [tsvwg] Alternative version of the UDP FRAG o… Raffaele Zullo
- Re: [tsvwg] Alternative version of the UDP FRAG o… C. M. Heard
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… C. M. Heard
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Derek Fawcus
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… C. M. Heard
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Gorry Fairhurst
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Gorry Fairhurst
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… Gorry Fairhurst
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Derek Fawcus
- [tsvwg] Possible UDP-Option: Cookie Derek Fawcus
- Re: [tsvwg] Possible UDP-Option: Cookie Tom Herbert
- Re: [tsvwg] Possible UDP-Option: Cookie tjw ietf
- Re: [tsvwg] Possible UDP-Option: Cookie Derek Fawcus
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Possible UDP-Option: Cookie Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Joe Touch
- Re: [tsvwg] Alternative version of the UDP FRAG o… Tom Herbert
- Re: [tsvwg] Alternative version of the UDP FRAG o… Gorry Fairhurst