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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 10 June 2020 02:25 UTC

Return-Path: <brian.e.carpenter@gmail.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 B4A5A3A0DE1 for <ietf@ietfa.amsl.com>; Tue, 9 Jun 2020 19:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 w6GChPxTV9se for <ietf@ietfa.amsl.com>; Tue, 9 Jun 2020 19:25:39 -0700 (PDT)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 8A4E73A0829 for <ietf@ietf.org>; Tue, 9 Jun 2020 19:25:39 -0700 (PDT)
Received: by mail-pj1-x102e.google.com with SMTP id b7so1579732pju.0 for <ietf@ietf.org>; Tue, 09 Jun 2020 19:25:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=QU6ndzj+Y4yn5x/qlZzccetFxOKQNGxTR2fZDvmHO7I=; b=WEN3Z4oDj/4xP06QsHo1pMXJN3hz8NN6txYju8iGyWC4HyusezULvoac3kVqNYwkXw sXne8FMY8gQsrcaXFN7xROjyWVy1iONu2e/dX6bAmpvVM++Ql9y+IU4OkUIzN3kFdzfo t9lKjP7h6LLKfi01t+KO0/cHcx3c23ADxnYpD2vr8s/9ffR5ekKX0vbjfWfCFlvRiOxs /gZ4wRbjfCfVxxtIDYV/+UcYhLxu1bbWPoPb+gBtcScdaqOtWN2vPbcvRoKGQcUaOoG+ xqNCAA7pNLlJTL2/wIxgZzf99RYdFP+VqpR8pvUgJ3Y5srOc4c6Bc+/ChIGP8YYOTXmB yGlg==
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-language :content-transfer-encoding; bh=QU6ndzj+Y4yn5x/qlZzccetFxOKQNGxTR2fZDvmHO7I=; b=BhioFEslRmsgILK1+LI7utV9DMLAOMmss2K4A6U9lQ4WtEV8/qOKU5D5bkudK+a/OO +Y8TY1STR3Ggu7gX3Suc2q9oqZI9r1SedAfXGJdz1DTxtYVZctximNgEiUig9nn7rvea NjuMRemYSbSotaczu4iF3tT9CB5Lc2Uh0UM7zEwUcasc6QUI7L3j6blYwFTi3oVjrTNO tMrYgTSJu7QN3bNkdrJ/7XLTciQXYdmP5brme6k5xhaI52+aIhHvU0xvDgtXuSbQyPPh hSkrlh0UZUpfjJN/DnilQ6ZAXQukcBRZd3aORK09nlmyKB4JFTwapLcpFkOwwV1qtM89 E/Cw==
X-Gm-Message-State: AOAM5326Ee1lFjWxdaGMqtlEI3wYj3PgEjtRGHlLpqXXNyHnBbTb/W92 R1mhroD5oZBWgoQYR2DwUpAEiaSEaoc=
X-Google-Smtp-Source: ABdhPJyuMnvmg4YK4wHmVeQiom+OBYifKGWJmlelSJHH2Q8Q9M/YvoHHoUX0u2Xkro6eBs+J41/law==
X-Received: by 2002:a17:902:82ca:: with SMTP id u10mr1103979plz.294.1591755938695; Tue, 09 Jun 2020 19:25:38 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.12.178]) by smtp.gmail.com with ESMTPSA id y23sm9333234pgc.78.2020.06.09.19.25.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Jun 2020 19:25:37 -0700 (PDT)
Subject: Re: The TCP and UDP checksum algorithm may soon need updating
To: Michael Thomas <mike@mtcc.com>, Nico Williams <nico@cryptonector.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
References: <2C425F1E-2E12-4E47-ACEC-AF4C4A93FA3E@akamai.com> <140429ad-af8b-e03f-a641-1e78b6056fa4@mtcc.com> <D55AFBFD-0D59-4176-B6BD-D6A1801FEC2C@akamai.com> <f42134de-3d0f-87e5-b13f-82afdb3689c9@mtcc.com> <96c65ca8-6ed5-2afa-a6d5-14905fc75ce8@foobar.org> <8946c5bf-0f6b-7a52-6326-dda59a78a798@mtcc.com> <995f5e46-b79a-ec9a-5465-9ec5abcdb759@foobar.org> <9d18c630-8506-9097-fc8c-86d6264afcbe@mtcc.com> <1783a7fa-fed4-2973-05dd-236f1120a74c@foobar.org> <5bf95457-5d44-86fa-5062-800680cc5a6a@mtcc.com> <20200608190220.GA18021@localhost> <9e0425e8-dffb-78a6-2520-c9214392caf7@gmail.com> <db8db09f-9f35-21a2-e38a-f6f3d4c9e8cf@mtcc.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <8a4f3836-c361-6e1a-1dd4-63e4e5cde659@gmail.com>
Date: Wed, 10 Jun 2020 14:25:32 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <db8db09f-9f35-21a2-e38a-f6f3d4c9e8cf@mtcc.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2VxlyJnlO9TeyFHI7JmzwvbWHSY>
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: Wed, 10 Jun 2020 02:25:41 -0000

On 10-Jun-20 11:52, Michael Thomas wrote:
> 
> On 6/8/20 1:57 PM, Brian E Carpenter wrote:
>> On 09-Jun-20 07:02, Nico Williams wrote:
>>> On Mon, Jun 08, 2020 at 11:23:09AM -0700, Michael Thomas wrote:
>>>> ssl had the advantage that it 1) beat ipsec to market, and 2) wasn't subject
>>>> to API differences from OS layer calls like IPsec was, and with quite a bit
>>>> of churn as i recall too. it's really too bad, imo. we wouldn't have had to
>>>> do the contortions of dtls, for example. and now there's this problem. none
>>>> of them are earth shattering, but it would have been cleaner.
>>> You can sprinkle TLS anywhere you have an octet stream.  You can
>>> sprinkle DTLS anywhere you have datagram flows.
>> Unless someone says "multicast".
> 
> 
> Hasn't that word been obsoleted and reserved for future use? :)

As a desirable function, certainly not. As a feature that is intrinsic
to your favourite L2 technology, and therefore a fairly simple add-on
to layer 3, its days are numbered. As an easy thing to secure, hmm.

   Brian