Re: The TCP and UDP checksum algorithm may soon need updating

Michael Thomas <mike@mtcc.com> Mon, 08 June 2020 00:21 UTC

Return-Path: <mike@fresheez.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D38AC3A081D for <ietf@ietfa.amsl.com>; Sun, 7 Jun 2020 17:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc-com.20150623.gappssmtp.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 kLDJTlc5VX6c for <ietf@ietfa.amsl.com>; Sun, 7 Jun 2020 17:21:53 -0700 (PDT)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C76613A084F for <ietf@ietf.org>; Sun, 7 Jun 2020 17:21:53 -0700 (PDT)
Received: by mail-pf1-x429.google.com with SMTP id 64so892144pfv.11 for <ietf@ietf.org>; Sun, 07 Jun 2020 17:21:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=6bOSQBuAwLDunhN3/6CtNwnpfW//39RxcN61ilUQIok=; b=FwIXacvbqqNY5J3ZOtCa/dYyd7lMMwH4GUmEd6yQ5I0ztWCDL/mpV1+b5/4GJ/Snwh 4p69dK+oC3jqvWr/QMBruOUJGw4tG6zvdMNDjl4iIHiIKaRutpQ6y191wwnngbUh3ic0 Dv0T20UoI8uHpFLc61ZHUP9svoLo4AP3IJPYHxKeS69S5F0E8IOQ8FZrCZRyYgAzOBz/ 1iy2i17ZX7qEW5Chl2i8FqCwU39UjV199x3l/V+Fp5wfetXWrQ41g4PxCZO0F8KJQdm9 Du/LSVIi6Y+wYl5/u2/8zhu+SrqTvMzKJwGtyyr9XPrd3L6LUNJ1PqcDmLTm/I7oyL2z BEoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=6bOSQBuAwLDunhN3/6CtNwnpfW//39RxcN61ilUQIok=; b=tjuQlltZYfjZHtNDTtwIxez2tLMuA4O4fv3lHRziWLy4kN8MO78adgzUZf8EIJe1VC QxZA5uFckXNvJBtnm88LHCBdovMGt6sgmVerKMGEuzFsWNmX9qtlBiRGVj0DwPtGd/GV ImOj7YJa/9kHA9SWrmYqTTfpAUqT5E5fHJuiqVr3BsfRpCttfDewkDZZ/8NfP/g9ENug 4UgcrQcpCtqIHgoSQo17gIW/OjfqZ4lg3QL+fecdgaxoMbFulhOAd5bUscETlivk3EhX U22BlpHXTgSxaQHqVZOKADXNk4vPSREVREmYNPCAzSc5FfyGYo2b7c4rpgWOSCik5Ebm rESQ==
X-Gm-Message-State: AOAM530BjqF1o5OYlFR8nOT5AgOc78qRr1V2m82K9Ukg+nGTVdoqZXFR 71t4OQVVwt4ai+FcR5J0YDzuPF8KOp4=
X-Google-Smtp-Source: ABdhPJzEl4Qvv8NFAvvNIguQ/Hu8gJDF/UQ8H6JzpaB6GZMXvig7Nwh2O8GaiwXzBoTzKUtSTcu/Pg==
X-Received: by 2002:a63:7d3:: with SMTP id 202mr17656677pgh.279.1591575711334; Sun, 07 Jun 2020 17:21:51 -0700 (PDT)
Received: from MichaelsMacBook.lan (107-182-45-85.volcanocom.com. [107.182.45.85]) by smtp.gmail.com with ESMTPSA id q16sm5282643pfg.49.2020.06.07.17.21.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 07 Jun 2020 17:21:50 -0700 (PDT)
Subject: Re: The TCP and UDP checksum algorithm may soon need updating
To: "Salz, Rich" <rsalz@akamai.com>, Joseph Touch <touch@strayalpha.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
References: <28A2725D-00F8-4739-8A73-ED176F8EF561@strayalpha.com> <3AA98081-A70E-4076-8096-79FFAEE8A738@huitema.net> <830b91c4-0bb5-af5b-f7b8-c5edd43dc87e@mtcc.com> <4512C1BF-5722-479B-8506-24018610BEAD@strayalpha.com> <5b4ea5ea-e2d6-1a01-3676-dd2a72dbd2c1@mtcc.com> <2C425F1E-2E12-4E47-ACEC-AF4C4A93FA3E@akamai.com> <140429ad-af8b-e03f-a641-1e78b6056fa4@mtcc.com> <D55AFBFD-0D59-4176-B6BD-D6A1801FEC2C@akamai.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <f42134de-3d0f-87e5-b13f-82afdb3689c9@mtcc.com>
Date: Sun, 7 Jun 2020 17:21:49 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.8.1
MIME-Version: 1.0
In-Reply-To: <D55AFBFD-0D59-4176-B6BD-D6A1801FEC2C@akamai.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i8-Z2aWsXOI05eu5OajU-xX3CL8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jun 2020 00:21:55 -0000

On 6/7/20 4:52 PM, Salz, Rich wrote:
>>     Because the TCP headers aren't part of the hmac digest? Am I missing
>      something?
>
> And how does that affect the application data?  What corruption of TCP headers would not end up being noticed at the application layer and therefore TLS?
>

well, it could send it to the wrong port, but i'll guess that tls is on 
to that problem. i mean, it kind of sounds like you're saying the 
transport checksum failing isn't a big deal? creating a gigantic window 
would certainly not be a good thing in the face of congestion. transport 
mode ipsec wouldn't suffer those kinds of problems.

Mike