Re: [tsvwg] A counterproposal to Section 5.5 of draft-ietf-tsvwg-udp-options-12

"C. M. Heard" <heard@pobox.com> Sun, 13 June 2021 22:09 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 7BCAB3A1152 for <tsvwg@ietfa.amsl.com>; Sun, 13 Jun 2021 15:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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, RCVD_IN_DNSWL_LOW=-0.7, 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 Q8tdYa8WetBv for <tsvwg@ietfa.amsl.com>; Sun, 13 Jun 2021 15:09:29 -0700 (PDT)
Received: from pb-smtp20.pobox.com (pb-smtp20.pobox.com [173.228.157.52]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16FFE3A114F for <tsvwg@ietf.org>; Sun, 13 Jun 2021 15:09:28 -0700 (PDT)
Received: from pb-smtp20.pobox.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id BEC7A14B0A8 for <tsvwg@ietf.org>; Sun, 13 Jun 2021 18:09:26 -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=I8U4CRsAk3toQub6GmsN670MD2jeteoP fgV6mgj5sgU=; b=YDrO19WVol5SgdhMuz/35V91T77X3hyLL74s9CwCCL/EfqLM DiXKGHzdY005Z8Q7pRoaqTvmJBraPVnk7T7u9uRcIeQymQ4iGiJcHhyxRRaFxAGi WD2mxmUNHKXE2zFHvyNgV31kTH315Y2tD/Om3rPhB2gDkKpawIjEg9nfJQA=
Received: from pb-smtp20.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id B894C14B0A7 for <tsvwg@ietf.org>; Sun, 13 Jun 2021 18:09:26 -0400 (EDT) (envelope-from heard@pobox.com)
Received: from mail-io1-f51.google.com (unknown [209.85.166.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp20.pobox.com (Postfix) with ESMTPSA id 5BA6014B0A4 for <tsvwg@ietf.org>; Sun, 13 Jun 2021 18:09:24 -0400 (EDT) (envelope-from heard@pobox.com)
Received: by mail-io1-f51.google.com with SMTP id h5so919281iok.5 for <tsvwg@ietf.org>; Sun, 13 Jun 2021 15:09:24 -0700 (PDT)
X-Gm-Message-State: AOAM530HbXsEMuW4GB+JAQogXmPLMcjMgOrc66M+VoB1XsWzk3sOi8AF 5MAmlcXH8q0tZFyhUEaAg98kFAWvhGKrkJ0tNP8=
X-Google-Smtp-Source: ABdhPJyY83hARtc+oIPVulMx415pKLCcjS80uuNPumN5ipumd8X3k958vru0dJUw+YxuqrbZiEd17mRo30MCDrRi8aA=
X-Received: by 2002:a05:6638:2247:: with SMTP id m7mr14529726jas.53.1623622163166; Sun, 13 Jun 2021 15:09:23 -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 15:09:26 -0700
X-Gmail-Original-Message-ID: <CACL_3VHNjeKOBJcmzjpRmJA8MDXMa7L0kaxg0SQPRKfhFX6jXg@mail.gmail.com>
Message-ID: <CACL_3VHNjeKOBJcmzjpRmJA8MDXMa7L0kaxg0SQPRKfhFX6jXg@mail.gmail.com>
To: Joseph Touch <touch@strayalpha.com>
Cc: TSVWG <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000048faec05c4acfe85"
X-Pobox-Relay-ID: 03154CA2-CC94-11EB-9174-D5C30F5B5667-06080547!pb-smtp20.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/RUSr_jchT9Nv-bJMwK7BAdbICMw>
Subject: Re: [tsvwg] A counterproposal to Section 5.5 of draft-ietf-tsvwg-udp-options-12
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 22:09:34 -0000

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

> So at that point, we really have only a few decisions:
>
> - do we want/need RDMA support?
>         if not, we ditch the frag length in non-terminal frags
>
> - do we want to ditch the required post-reassembly checksum?
>         if so, we ditch that field in the terminal frag
>
> THEN we compare the answers to decide how to handle the MF issue:
>         - if we still end up with different length options, length
> indicates MF
>         - if not, we might be better off burning two codepoints on
> FRAG/TERMFRAG than a byte
>         (a single byte throws off our fields as odd-length AND needs to be
> checked for values not 0 or 1)



I'm OK with this as a path forward. I would like to add that I have no
objection to using different KIND codepoints in place of a MF bit or byte.

I'll address the two points above separately.

Mike


>