[tsvwg] Re: [v6ops] Re: Carrying large DNS packets over UDP in IPv6 networks
"C. M. Heard" <heard@pobox.com> Sun, 16 June 2024 19:57 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 C6F66C1840E5; Sun, 16 Jun 2024 12:57:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.805
X-Spam-Level:
X-Spam-Status: No, score=-2.805 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FbtVQBAW6XDL; Sun, 16 Jun 2024 12:57:10 -0700 (PDT)
Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C0D9C1840E2; Sun, 16 Jun 2024 12:57:10 -0700 (PDT)
Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 2A63535E52; Sun, 16 Jun 2024 15:57:09 -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=Q0Ge6MvfPbq7Rfz1Z90mUcPW+IKPw+j0 S9I6PzeygHs=; b=EaEqSs9AaFF8MESwvl++3SDG+KCIU0S8u6ERBActjfToZFxq btooLToxMKM31OO19W+ytUnpVojQJLJfSFRTJkEZqruXHDHLxsAHQ8k6UI0fw9qy XGnVpBKs7t+MngwSu/x2sdFrfa6QEql+dFh/BEOghww7lMEoKP+XoUmGDms=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 2104F35E51; Sun, 16 Jun 2024 15:57:09 -0400 (EDT) (envelope-from heard@pobox.com)
Received: from mail-lj1-f169.google.com (unknown [209.85.208.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 3256C35E4C; Sun, 16 Jun 2024 15:57:07 -0400 (EDT) (envelope-from heard@pobox.com)
Received: by mail-lj1-f169.google.com with SMTP id 38308e7fff4ca-2e72224c395so38361751fa.3; Sun, 16 Jun 2024 12:57:07 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCWJvdP5yUi1rxELhEZ5CwRoSuoM/oY3lyPQ606tlPT3yRHLvKPsLbzdGztnhKMa0hXqhUl4meSG3Jo3OkDDuQ==
X-Gm-Message-State: AOJu0YzWyHwz7JZdXpwdY8klOFaoohStbbvRsm0XORuTARJPLwmdWdV5 Z7YOCF8OH6qIjljlyZUJAB/TJmr+hZcHXtemqUleSO4pTptyyQH+tybO1Dg8dS5iDZmRpm6k6Sg HTFCCFTDv9LXRjJwH5v3K39FAT4o=
X-Google-Smtp-Source: AGHT+IGXpbJbYElKVG6ANGw/kDlK8tJjFK6hRw4gd85vQ83ZKq5a7DhY/eIdJHGupv7lTHUFF0KDdv5v374W0dbj0kI=
X-Received: by 2002:a2e:9056:0:b0:2eb:fa26:8ca2 with SMTP id 38308e7fff4ca-2ec0e5b5f48mr58997571fa.4.1718567825796; Sun, 16 Jun 2024 12:57:05 -0700 (PDT)
MIME-Version: 1.0
References: <E35DC12F-D1CE-4AE5-B155-612C639A348B@gmail.com> <DU2PR02MB10160CCA998D5A86B9F11F2C388C22@DU2PR02MB10160.eurprd02.prod.outlook.com> <CACL_3VGzQfn9Gp+Wvx6HDZt=Gbyurirgt8Sa3qah7TpNgLiQug@mail.gmail.com> <BAEBA468-9B3E-41ED-B609-1D0A9D4A0F6E@gmail.com> <Zm81hsg9-O6A3GCQ@Space.Net>
In-Reply-To: <Zm81hsg9-O6A3GCQ@Space.Net>
From: "C. M. Heard" <heard@pobox.com>
Date: Sun, 16 Jun 2024 12:56:55 -0700
X-Gmail-Original-Message-ID: <CACL_3VE+AUDpg8Tn0q7BRPTKk9oPbm3+Xwgj8PCiMoUjR6Nd=g@mail.gmail.com>
Message-ID: <CACL_3VE+AUDpg8Tn0q7BRPTKk9oPbm3+Xwgj8PCiMoUjR6Nd=g@mail.gmail.com>
To: Gert Doering <gert@space.net>, Bob Hinden <bob.hinden@gmail.com>, Suresh Krishnan <suresh.krishnan@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000c781f7061b07406b"
X-Pobox-Relay-ID: 9C254648-2C1A-11EF-9752-965B910A682E-06080547!pb-smtp2.pobox.com
Message-ID-Hash: D3CQNQN4C24OSM4PX52L3Z2TZJPVVAJP
X-Message-ID-Hash: D3CQNQN4C24OSM4PX52L3Z2TZJPVVAJP
X-MailFrom: heard@pobox.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tsvwg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "v6ops@ietf.org" <v6ops@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [tsvwg] Re: [v6ops] Re: Carrying large DNS packets over UDP in IPv6 networks
List-Id: Transport Area Working Group <tsvwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/dN5ysHfww7nY2AofFOVJ1yAZbOs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Owner: <mailto:tsvwg-owner@ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Subscribe: <mailto:tsvwg-join@ietf.org>
List-Unsubscribe: <mailto:tsvwg-leave@ietf.org>
On Sun, Jun 16, 2024 at 11:57 AM Gert Doering wrote: > On Sun, Jun 16, 2024 at 09:07:44AM -0700, Bob Hinden wrote: > This document is aligned with the recommendation in > [I-D.ietf-dnsop-avoid-fragmentation], but focuses on DNS over IPv6, and > also recommends and provides additional details on running DNS over TCP or > QUIC. > > > > I don't think a v6ops document should venture into DNS transport > recommendations - especially as the question "TCP or QUIC" is, basically, > independent of the underlying IP protocol (IPv4 fragments are not safe > from eaten by intermediate grue). > +1 to that. Hence my recommendation to focus efforts on getting [I-D.ietf-dnsop-avoid-fragmentation] published, at least as regards DNS issues. A more fruitful avenue for v6ops might be to encourage applications that use transport protocols that do their own packetization (e.g., TCP, QUIC, TLS, and DTLS) to select settings (e.g., socket options) that will avoid IPv6 fragmentation and to encourage such transport protocols to make such settings available to the layers above. That ultimately is what will make it possible to implement the recommendations in [I-D.ietf-dnsop-avoid-fragmentation] and other such application-specific documents. Something similar may be needed for IPv4, but the problems there are somewhat different and in any case are not the purview of v6ops. Respectfully, Mike Heard
- [tsvwg] Re: [v6ops] Re: Carrying large DNS packet… C. M. Heard
- [tsvwg] Re: [v6ops] Carrying large DNS packets ov… mohamed.boucadair
- [tsvwg] Re: [v6ops] Re: Carrying large DNS packet… Brian E Carpenter
- [tsvwg] Re: [v6ops] Carrying large DNS packets ov… C. M. Heard
- [tsvwg] Re: [v6ops] Carrying large DNS packets ov… Bob Hinden
- [tsvwg] Re: [v6ops] Re: Carrying large DNS packet… Gert Doering
- [tsvwg] Re: [v6ops] Re: Carrying large DNS packet… C. M. Heard
- [tsvwg] Re: [v6ops] Re: Carrying large DNS packet… touch@strayalpha.com
- [tsvwg] Re: [v6ops] Re: Re: Carrying large DNS pa… Mark Smith
- [tsvwg] Re: [v6ops] Re: Carrying large DNS packet… Suresh Krishnan
- [tsvwg] Re: [v6ops] Carrying large DNS packets ov… Suresh Krishnan
- [tsvwg] Re: [v6ops] Carrying large DNS packets ov… C. M. Heard
- [tsvwg] Re: [v6ops] Carrying large DNS packets ov… Suresh Krishnan
- [tsvwg] Re: [v6ops] Re: Carrying large DNS packet… Simon
- [tsvwg] Re: [v6ops] Re: Carrying large DNS packet… Warren Kumari
- [tsvwg] Re: [v6ops] Carrying large DNS packets ov… Suresh Krishnan
- [tsvwg] Re: [v6ops] Carrying large DNS packets ov… Suresh Krishnan
- [tsvwg] Re: [v6ops] Carrying large DNS packets ov… mohamed.boucadair