[tsvwg] RDMA Support by UDP FRAG Option

"C. M. Heard" <heard@pobox.com> Sun, 13 June 2021 23:37 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 216733A14E5 for <tsvwg@ietfa.amsl.com>; Sun, 13 Jun 2021 16:37:35 -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 (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 eVC0DxZRhWmU for <tsvwg@ietfa.amsl.com>; Sun, 13 Jun 2021 16:37:30 -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 6008A3A14E3 for <tsvwg@ietf.org>; Sun, 13 Jun 2021 16:37:30 -0700 (PDT)
Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id BCD70D681F for <tsvwg@ietf.org>; Sun, 13 Jun 2021 19:37:28 -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=FkQFcMB9OZHQJaiLwMto4aMzN2Ugg9Dy FqQDp+i4jtY=; b=ihIWabsT/wqzug2YVXJZR24Px9nrAUM+kmwEGD+hrJWOC6kq UFtMB438hXeY9LfNbp+4aAKuqHl7xFCFnHGCbks1dTrNDGMZc467G3VhSUtYleij 4VDQqBjNsDrxf1O3r++4b0FCFHdRz4FLkaS/ZADSf7KA382jqtMUQbWIowY=
Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id B3DA0D681E for <tsvwg@ietf.org>; Sun, 13 Jun 2021 19:37:28 -0400 (EDT) (envelope-from heard@pobox.com)
Received: from mail-il1-f181.google.com (unknown [209.85.166.181]) (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 430F4D681D for <tsvwg@ietf.org>; Sun, 13 Jun 2021 19:37:28 -0400 (EDT) (envelope-from heard@pobox.com)
Received: by mail-il1-f181.google.com with SMTP id d1so10659602ils.5 for <tsvwg@ietf.org>; Sun, 13 Jun 2021 16:37:28 -0700 (PDT)
X-Gm-Message-State: AOAM532XOekgTqbI1ekCo7lxYYKfqoZ76atyzAgcx5TaFhQC75sRzxjU mpcLFSQWeDPSxquNQaaoR4ITLY53AE4/vLYTNu0=
X-Google-Smtp-Source: ABdhPJzHI9Qizcmpo9wSlmDsWabFO4X+uqWs+qc0qlNIQaK/CErYq9BXQ9TVwqubKEPLGEWNdyv4GexSK34iKp5th+c=
X-Received: by 2002:a05:6e02:4b0:: with SMTP id e16mr11341023ils.71.1623627447656; Sun, 13 Jun 2021 16:37:27 -0700 (PDT)
MIME-Version: 1.0
References: <CACL_3VEyLdQZ-3hvzXxyA8ehtWs2hXESZ2OqyAx+BeSg85+-cA@mail.gmail.com> <CACL_3VFE4TjKvmkfZjvNpWo6vVfKjz5w85=Q+yqnYZKcwbYLmQ@mail.gmail.com> <63FFC34B-2179-47F1-B325-21CAC3D1543A@strayalpha.com>
In-Reply-To: <63FFC34B-2179-47F1-B325-21CAC3D1543A@strayalpha.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Sun, 13 Jun 2021 16:37:30 -0700
X-Gmail-Original-Message-ID: <CACL_3VHTfxWaBj7TFEmBXBqovrrAj7XuFEZFUag_iBHr3Hx09g@mail.gmail.com>
Message-ID: <CACL_3VHTfxWaBj7TFEmBXBqovrrAj7XuFEZFUag_iBHr3Hx09g@mail.gmail.com>
To: Joseph Touch <touch@strayalpha.com>
Cc: "C. M. Heard" <heard@pobox.com>, TSVWG <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000043e58a05c4ae3938"
X-Pobox-Relay-ID: 50884D5C-CCA0-11EB-A0FE-8B3BC6D8090B-06080547!pb-smtp1.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/05P8Mskx1DYRHNmdihxHM-o-jNQ>
Subject: [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: Sun, 13 Jun 2021 23:37:35 -0000

On Thu, Jun 10, 2021 at 9:43 PM Joseph Touch wrote:

> - do we want/need RDMA support?
>         if not, we ditch the frag length in non-terminal frags
>


I am going to reveal my ignorance by asking what is meant by RDMA (Remote
Direct Memory Access). But I'm fine with that as long as we end up with an
unambiguous problem statement.

The specification that I found with a Google search is "InfiniBand™
Architecture Specification Release 1.2.1 Annex A17: RoCEv2," available at
https://cw.infinibandta.org/document/dl/7781/.

This is a datacenter protocol and requires very specific conditions in
order to work, not the least of which is that it assumes that the IP/UDP
layer is nearly lossless and free from reordering.

This protocol handles its own data placement and integrity checks -- indeed
it requires UDP CS=0 to avoid redundant work -- and AFAICT would not in any
way benefit from UDP options.

If you have something else in mind, please let us know what it is.
Otherwise, I'd say that UDP options does not need to make any effort to
support RDMA.

Mike Heard