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

Michael Thomas <mike@mtcc.com> Mon, 08 June 2020 17:24 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 A995F3A0DB7 for <ietf@ietfa.amsl.com>; Mon, 8 Jun 2020 10:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 yZlN4pKCr0co for <ietf@ietfa.amsl.com>; Mon, 8 Jun 2020 10:24:14 -0700 (PDT)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (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 1E9C03A0D2D for <ietf@ietf.org>; Mon, 8 Jun 2020 10:24:13 -0700 (PDT)
Received: by mail-pg1-x536.google.com with SMTP id n23so9017335pgb.12 for <ietf@ietf.org>; Mon, 08 Jun 2020 10:24:13 -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=RAFwi7jaiy4VXchkoB/zFFv1iBUuFGhyUDSZAImHHBo=; b=rTfFTHdWDSJ5nGG4A47cBpHHSCqVK1z4+llCZQKnm8FfZRfk1xFPVwj33eBOFUcDgK dformD/7y/H1ydjfYpix+j++mD4ZYF332dw6Vu7dvkLPxoWMyD6RQFUO+TQOobNODOFf ORV55S03Q0xAwUXS1AhUhn4V83Jg7b8TT1ldHLilUH8xqR0cj1iPsKUjJKmb7YKv3jad pkHuBtMPrA6BD2oWKaW4XejLP1TL5lqlDdxUEWvhHbyTaWf9UsI1bmnRRL3JGzJy/CBx 8LtCyjXg/x8zkMQ3HYfs/HnwTEa4VoLHnv8KdYq8skYZ/fzt9VpXJUcyk1m5X4+1cNyH WLVA==
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=RAFwi7jaiy4VXchkoB/zFFv1iBUuFGhyUDSZAImHHBo=; b=YBX6c3TSAiK9a3ZE+Z0kgEsqoRGim0HX0Gbvx4DvTaapWyHZaDh44V7ZGNy7mkV9cF qhml2M68QNF3ve+W31DmT7wLx6rnHsK1DVekAK9Ugv9e+P54VUddKD1XKTKH5s1awnoF A5vbH2yxjharwdER8gDuwmJll6kMx3wyjEuo3EtXVaRCp02k/yx3/8y45ISYaVlunTzU aXNHDniypuT/Rwx5GP//cdEomGu8Qu+FC7bfurCtoYj+Zy0KXzLbI0xJQuS2b0FjXOSA Rt3OFDC3uOprkbk6/A0ZMLTepaAFTmOemXz56RJO+2Bc8WkXfJNdPhHN0Cy20wDzJrCA hfSA==
X-Gm-Message-State: AOAM531pxhMKH8LfV3I7ezmPg+jh4bRlJHzvMZvfRjZaRK2kSkX9i7Kc X26NJZcCjd4iSVOl+BJcO/pSEv7Ba+M=
X-Google-Smtp-Source: ABdhPJy01EWiNR+uTBk55bWwDjkzkW4rfr/bzA46SnTEMOPkJCxMBhostXl3S7ab4BXe56yHAgUWeQ==
X-Received: by 2002:a62:64ca:: with SMTP id y193mr22387280pfb.123.1591637053037; Mon, 08 Jun 2020 10:24:13 -0700 (PDT)
Received: from MichaelsMacBook.lan (107-182-45-85.volcanocom.com. [107.182.45.85]) by smtp.gmail.com with ESMTPSA id 207sm7623879pfw.190.2020.06.08.10.24.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 08 Jun 2020 10:24:12 -0700 (PDT)
Subject: Re: The TCP and UDP checksum algorithm may soon need updating
To: Nico Williams <nico@cryptonector.com>, Joe Touch <touch@strayalpha.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
References: <8946c5bf-0f6b-7a52-6326-dda59a78a798@mtcc.com> <AF28EDA6-0402-4578-A6C4-B3136F6C8650@strayalpha.com> <20200608171628.GX18021@localhost>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <909178cc-c1b6-2dce-09eb-f8d28b63968c@mtcc.com>
Date: Mon, 8 Jun 2020 10:24:10 -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: <20200608171628.GX18021@localhost>
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/wKu9DTxGoopd8kT61Aef2IMFXtg>
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 17:24:23 -0000

On 6/8/20 10:16 AM, Nico Williams wrote:
> On Mon, Jun 08, 2020 at 10:11:09AM -0700, Joe Touch wrote:
>>> On Jun 8, 2020, at 10:00 AM, Michael Thomas <mike@mtcc.com> wrote:
>>> i assume that you can hack ipsec to emulate clients not having certs.
>> It is called BTNS.  See RFC 5387.
> Yes, but you also need RFC5660 implementations to make it more
> meaningful.  Still, if all you want is error detection, BTNS will do.


this is undoubtedly a complete rehash, but who controls what the root 
CA's are with ipsec? is that something that the application layer has 
some say-so over? could my app say i don't care who the root CA is?

Mike