IETF Logo Mail Archive

[DNSOP] Re: [v6ops] Re: Re: Fwd: New Version Notification - draft-ietf-dnsop-avoid-fragmentation-18.txt

Philip Homburg <pch-v6ops-13@u-1.phicoh.com> Fri, 05 July 2024 10:02 UTC

Return-Path: <pch-b538D2F77@u-1.phicoh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E375C180B7D; Fri, 5 Jul 2024 03:02:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLwQScbcGSD8; Fri, 5 Jul 2024 03:02:13 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [45.83.6.19]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBAC3C180B75; Fri, 5 Jul 2024 03:01:59 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #158) id m1sPfl7-0000LiC; Fri, 5 Jul 2024 12:01:41 +0200
Message-Id: <m1sPfl7-0000LiC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-13@u-1.phicoh.com>
Sender: pch-b538D2F77@u-1.phicoh.com
References: <171957523370.366291.478718063778248894@dt-datatracker-ff7f57fbb-ch6dm> <491D5E6C-41CC-4E63-B10F-2E8F4BDC2513@apnic.net> <CADyWQ+E+ae6F5yMLGza0aAogP4G7qeb4wY-3aiyaoQNOdfeWqQ@mail.gmail.com> <2880837.88bMQJbFj6@heater.srcl.tisf.net>
In-reply-to: Your message of "Thu, 04 Jul 2024 19:25:22 -0700 ." <2880837.88bMQJbFj6@heater.srcl.tisf.net>
Date: Fri, 05 Jul 2024 12:01:41 +0200
Message-ID-Hash: V2XIQYIP3EFIMK6YC4IOE3OHO47N6QSY
X-Message-ID-Hash: V2XIQYIP3EFIMK6YC4IOE3OHO47N6QSY
X-MailFrom: pch-b538D2F77@u-1.phicoh.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Paul Vixie <paul=40redbarn.org@dmarc.ietf.org>, dnsop <dnsop@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP] Re: [v6ops] Re: Re: Fwd: New Version Notification - draft-ietf-dnsop-avoid-fragmentation-18.txt
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/XBjMx8qaMu--RC7BS5nswGCYao8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

> That is, first see if there is a discovered mtu (such as by PLPMTUD
> or some future method), 

Can we go back to reality? There is no PMTU discovery for DNS replies
over UDP that works at scale. It doesn't work, it never worked.

If, through some major breakthrough, someone can actually make it work in
a way that it can get deployed on a serious scale, then we should work on
a standards track RFC that documents how this works.

Absent any documented PMTU discovery that works for DNS over UDP replies,
this is just adding confusion and serves no purpose.

v2.40.4 | Report a Bug | By Email | System Status