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

Craig Partridge <craig@tereschau.net> Thu, 11 June 2020 18:26 UTC

Return-Path: <craig@tereschau.net>
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 5D9DE3A0C0A for <ietf@ietfa.amsl.com>; Thu, 11 Jun 2020 11:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tereschau.net
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 vPWTyIU5-hOn for <ietf@ietfa.amsl.com>; Thu, 11 Jun 2020 11:26:25 -0700 (PDT)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (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 001D03A082A for <ietf@ietf.org>; Thu, 11 Jun 2020 11:26:24 -0700 (PDT)
Received: by mail-qt1-x836.google.com with SMTP id c12so5282945qtq.11 for <ietf@ietf.org>; Thu, 11 Jun 2020 11:26:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tereschau.net; s=google; h=mime-version:from:date:message-id:subject:to; bh=KqH/p+13q+7eUTdKBhJV+kq98/UtDBZ0gEJOKDZ5CaI=; b=Tko7pAjaj1ngEnZJVGYRXeXVCMO3B94ktVVOXvedalcoerkBMszUV/ZE/WoOGaNaHK Vrw8IIQvVdYpDd8nTvydUFym+d9O7AuGD7/nHSWNuqNslv0A0IhjW5pL8lDWuLXMfJ1z rj6x1juCKBJwJnTHUem6mWc/8lVL+Z7kL6m92ZfAzehCoOyI5TyDGo4Td3K3qxQ0wVnK NfC6T530vyiwWM6kS7Um20vBd6ebKPcQozQ9jNLdu+Ic94mdvcE2FBCdx4f5V9eZ+Ioq usFRQUvn/TTicJUTbnVSUufkgRxBRZhKhtRRNsguDuXts7OgzKWiKCpsAyk08CSLUh1C UwqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=KqH/p+13q+7eUTdKBhJV+kq98/UtDBZ0gEJOKDZ5CaI=; b=HLuhXTDjFB4U/xOxMr6EaJAG/BihJsTAMkF3l7hdf9EgOkZ6dzUNoP73p8rAEBa2kx scSJD2iET4oNpAV/tuWrXGgq/BaygXg5z+GuI1wr+zxTIJTHaiD+8cejeeZNThQ7YC1c BJiCtPVJGXZI8EPHBwc4A0+hcy7pZ41VvBpxKs6zsHkaIhB7VTmoCBiiAhvIeP7WLtKh EfH8gpzCM0i6uq3r/NwW8fzQF6ct9WqC9XHgOB/b1HnIg6Vbjdoxex/fT4f6zigDFQl3 fWMSLqbG7cebM8JlStp1EsF7EcJLeHpKAp1cylMAtZ6lhEHW5ugQlXRXTyFOVn/GATyq t22w==
X-Gm-Message-State: AOAM5315v7NfIv8PsKHcr0J1yTELdssTI2lMS6JYpWo3kIP+gWRbNteg J5rtO6tbl8xdWuuk0PIkaeqC5MFkwlf5WricVnwLyfdA
X-Google-Smtp-Source: ABdhPJzWVtKclW/mVPj8t50ZnpXqrOyBHLZIDbXq5XFfy43Ma7UOhg6ni60EoYf/9wkNQGoFBnSKGxapueikvk1u3m0=
X-Received: by 2002:ac8:468d:: with SMTP id g13mr9865879qto.47.1591899983146; Thu, 11 Jun 2020 11:26:23 -0700 (PDT)
MIME-Version: 1.0
From: Craig Partridge <craig@tereschau.net>
Date: Thu, 11 Jun 2020 12:26:12 -0600
Message-ID: <CAHQj4CfbMK9nRmmVeWExavXbNL1EaX9g+d-9PhnuQAOu=awRug@mail.gmail.com>
Subject: Re: The TCP and UDP checksum algorithm may soon need updating
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000003818505a7d319b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fzBhzoqQQ3HJN7ksE5X_p-GG1EA>
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: Thu, 11 Jun 2020 18:26:26 -0000

Two comments on the several notes that have gone past.

Michael Thomas raises a point about bugs.  He's quite right and there's
reason to believe that if we tracked the Internet paths on which checksum
errors took place, and compared the paths to find commonalities, we'd
locate broken/buggy equipment.  Jonathan Stone did some of that 20 years
ago and found a software bug in a vendor TCP (which the vendor updated in a
matter of days -- kudos to them) and a network interface vendor who was
shipping cards with defective hardware (and adamantly claimed our
measurements identifying their cards were wrong).

There was also a note (which I can't seem to find) to the effect of "the
errors in the papers don't match what I'm seeing on my systems."  That's
not a surprise.  Errors cluster around particular links or devices.
There's also some reason to believe error rates are higher on the fast
links.  So, depending on your environment and where your traffic goes, your
error rates may vary widely.  All the more reason to measure.

Thanks!

Craig
-- 
*****
Craig Partridge's email account for professional society activities and
mailing lists.