[tsvwg] Fwd: Can DPLPMTUD for UDP Optionsbe considered to be adopted by tsvwg?

"C. M. Heard" <heard@pobox.com> Fri, 03 September 2021 03:07 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 39D673A0045 for <tsvwg@ietfa.amsl.com>; Thu, 2 Sep 2021 20:07:58 -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 6Z51eiE0_W6y for <tsvwg@ietfa.amsl.com>; Thu, 2 Sep 2021 20:07:52 -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 D516A3A003D for <tsvwg@ietf.org>; Thu, 2 Sep 2021 20:07:52 -0700 (PDT)
Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 2A2AFF1396 for <tsvwg@ietf.org>; Thu, 2 Sep 2021 23:07:51 -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:content-type; s=sasl; bh=rJ11ghhMaSTX8oYvvLha5Dq+Rt9Pc5LZs5M t5lg4BiI=; b=ldlapWw0uBfOinmosvIH8zmSgkGL/9pLnSsf2jR+svYmOBOymzJ SCX3zEApYinj1m9jEoVBh6TzjVgsckHNFzR5vUUGTILeVCqhhSt58ctwYC0O9rys J9KMY8TYOFJvpsIzRT+wKcUQBBEipTsA6pAYTI+attC65XBkFzF9q5TY=
Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 219BAF1395 for <tsvwg@ietf.org>; Thu, 2 Sep 2021 23:07:51 -0400 (EDT) (envelope-from heard@pobox.com)
Received: from mail-pj1-f46.google.com (unknown [209.85.216.46]) (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 93026F1393 for <tsvwg@ietf.org>; Thu, 2 Sep 2021 23:07:50 -0400 (EDT) (envelope-from heard@pobox.com)
Received: by mail-pj1-f46.google.com with SMTP id d3-20020a17090ae28300b0019629c96f25so2986356pjz.2 for <tsvwg@ietf.org>; Thu, 02 Sep 2021 20:07:50 -0700 (PDT)
X-Gm-Message-State: AOAM532aF/m0Fsibx7AEjT6BAOG9T9wYh0+NexnFYslpFt0homo6RzYG aA8GQ1u6jtj3bfpxgpZF/5oK7httjZ2z2tpFaks=
X-Google-Smtp-Source: ABdhPJw7Am+/Fi4QlpRW1j3F/9BKWUdYshWfQjc3S6sNiziyBpZHH7rDiQO2nfUfS4n6jrX8v4lpOPSXTUiB1tHbg5s=
X-Received: by 2002:a17:902:a702:b029:12b:aa0f:d553 with SMTP id w2-20020a170902a702b029012baa0fd553mr1363392plq.3.1630638469712; Thu, 02 Sep 2021 20:07:49 -0700 (PDT)
MIME-Version: 1.0
References: <7e3e6985-9f5e-de1b-da1e-15bb468fdbdc@erg.abdn.ac.uk> <CACL_3VFJkvHAevbQR2wDvaBk-9cE-8GWp92fhGG1+7x16WsqtA@mail.gmail.com>
In-Reply-To: <CACL_3VFJkvHAevbQR2wDvaBk-9cE-8GWp92fhGG1+7x16WsqtA@mail.gmail.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Thu, 02 Sep 2021 20:07:38 -0700
X-Gmail-Original-Message-ID: <CACL_3VGS8dBV-AePbrpD-Vu=aguWSqcnuf4zQrBPZHwxMV6J_w@mail.gmail.com>
Message-ID: <CACL_3VGS8dBV-AePbrpD-Vu=aguWSqcnuf4zQrBPZHwxMV6J_w@mail.gmail.com>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Tom Jones <tom@erg.abdn.ac.uk>, TSVWG <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000be8e4305cb0e9a0e"
X-Pobox-Relay-ID: 1F7CBD2A-0C64-11EC-A24E-D601C7D8090B-06080547!pb-smtp1.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/gUVbo3OOXgIUYdoG0NUR2zO45Sg>
Subject: [tsvwg] Fwd: Can DPLPMTUD for UDP Optionsbe considered to be adopted by tsvwg?
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: Fri, 03 Sep 2021 03:07:59 -0000

[ resend with working address for Tom Jones ]

I certainly support adoption. There is one substantive issue that I have
noticed:

In Section 3.2.1 (page 4) the draft says:

   Implementations MAY track multiple requests and respond acknowledging
   them with a single packet.


That contradicts the following provision in draft-ietf-tsvwg-udp-options-13:

   >> Except for NOP, each option SHOULD NOT occur more than once in a
   single UDP datagram. If an option other than NOP occurs more than
   once, a receiver MUST interpret only the first instance of that
   option and MUST ignore all others.


This inconsistency must be resolved before this draft (or
draft-udp-options) can progress.

Thanks,

Mike Heard

On Mon, Aug 30, 2021 at 11:24 AM Gorry Fairhurst <gorry@erg.abdn.ac.uk>
wrote:

> We submitted revision -05 of draft-fairhurst-tsvwg-udp-options-dplpmtud
> a couple of weeks ago. This, like the last rev, was mainly to tidy NiTs.
> The protocol spec has not changed.
>
> The authors are now asking if this can be adopted to progress with UDP
> Options through to RFC publication.  We've asked for this to be added to
> the Agenda for the next Interim, and thoughts from the WG on-list or at
> that meeting will be most welcome!
>
> Best wishes,
>
> Tom & Gorry
>
> (as individual document authors).
>
>