Re: [tsvwg] RDMA Support by UDP FRAG Option

"C. M. Heard" <heard@pobox.com> Mon, 21 June 2021 22:30 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 031D23A1C5F for <tsvwg@ietfa.amsl.com>; Mon, 21 Jun 2021 15:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-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 (1024-bit key) 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 TPWciKlw7sXk for <tsvwg@ietfa.amsl.com>; Mon, 21 Jun 2021 15:30:03 -0700 (PDT)
Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82FB03A1C5E for <tsvwg@ietf.org>; Mon, 21 Jun 2021 15:30:02 -0700 (PDT)
Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id A4908C8349 for <tsvwg@ietf.org>; Mon, 21 Jun 2021 18:29:57 -0400 (EDT) (envelope-from heard@pobox.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h= mime-version:references:in-reply-to:from:date:message-id:subject :to:cc:content-type; s=sasl; bh=NXZw55CTj4EYrbysZYkZZtauUx4sLPbM zH04A3Pjde0=; b=aOgpf09fqWfgpoeUSJrbaD8cRdS8bi7k9G09OHrw6VzXlKB1 FVKA0qgdCxNfwt5/cLRN5/I9fWcabtqSUvC6/1lfVa/FJxCjc419qWHHc4QWEzX6 teNnznmI4a69nDJR8o2o/NxGrTNQt0z7/4/68JJesoD60G1TeOWnNblnIl0=
Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 9C924C8348 for <tsvwg@ietf.org>; Mon, 21 Jun 2021 18:29:57 -0400 (EDT) (envelope-from heard@pobox.com)
Received: from mail-il1-f179.google.com (unknown [209.85.166.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 271B7C8347 for <tsvwg@ietf.org>; Mon, 21 Jun 2021 18:29:57 -0400 (EDT) (envelope-from heard@pobox.com)
Received: by mail-il1-f179.google.com with SMTP id k5so3133339ilv.8 for <tsvwg@ietf.org>; Mon, 21 Jun 2021 15:29:57 -0700 (PDT)
X-Gm-Message-State: AOAM531VZf/VpH6vwgg4DZ4E1RgHoIDzbu2wNRCbIqD4OwfN3XhCEGqd XNidLXKH927F/Ev2Axj8Le35IQWmyczRQb6DXYc=
X-Google-Smtp-Source: ABdhPJxiFxjvVPcFnm29C7TOSnibMUglv0FCaqMkkFI/k1xoHu/ee63RNq4icTXeFAanovbyazvWNkvrQ4/EYfAaRCM=
X-Received: by 2002:a05:6e02:ee6:: with SMTP id j6mr341676ilk.143.1624314596625; Mon, 21 Jun 2021 15:29:56 -0700 (PDT)
MIME-Version: 1.0
References: <CACL_3VFQR_G5zgjbNiBH3Xu7Dvp+rOXUhNnJ2s4eDwZgq+e-=w@mail.gmail.com> <86D81D07-5CE6-4B89-BF7A-0907AD0AB525@strayalpha.com> <CACL_3VFUFr+bw8wV6zhZhEfj150=AFxgCjKY2mGeRPZcL1NK2w@mail.gmail.com> <20738006-963E-45D6-95DF-3ED842279731@strayalpha.com>
In-Reply-To: <20738006-963E-45D6-95DF-3ED842279731@strayalpha.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Mon, 21 Jun 2021 15:29:44 -0700
X-Gmail-Original-Message-ID: <CACL_3VEMEGQo0zym59NQi7uejuoWaYOV0SSXyucUM6SZ4BPpvQ@mail.gmail.com>
Message-ID: <CACL_3VEMEGQo0zym59NQi7uejuoWaYOV0SSXyucUM6SZ4BPpvQ@mail.gmail.com>
To: Joseph Touch <touch@strayalpha.com>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, TSVWG <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000089122505c54e3667"
X-Pobox-Relay-ID: 352F6C48-D2E0-11EB-9BF4-8B3BC6D8090B-06080547!pb-smtp1.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/d9ZVRq8OvPBy4Sa3VuEjHHCFsHk>
Subject: Re: [tsvwg] RDMA Support by 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: Mon, 21 Jun 2021 22:30:08 -0000

On Mon, Jun 21, 2021 at 3:20 PM Joseph Touch wrote:

> It's true that OCS is optional when UDP CS==0, but my understanding is
> that per the current spec, if it is present, the receiver is required to
> check it and drop the options if it does not follow the rule specified for
> OCS.
>
>
> Yes, and that makes sense - if you’ve added OCS, regardless of whether the
> UDP CS==0 or not, then you want the options checked. All we currently have
> been saying is that “OCS can be omitted when CS==0”, not that it MUST be.
>
> And that rule is not that the surplus area sums to zero, but that the
> surplus area plus the pseudo-header consisting of the surplus are length
> sums to zero.
>
>
> It was originally (through draft-ietf-tsvwg-udp-options-05)  to cover the
> surplus area only; it was in the additional CCO-like behavior that it
> changed to add the pseudo header  (the surplus length). So are we going
> back to the pre-CCO definition?
>

I'm certainly not advocating for that! Tom Hernert seems to want that, but
I sure don't, and as I indicated in my reply to him, I think that going
back to the pre-CCO definition would undermine the chances of successful
deployment.

Mike