Return-Path: 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 76B8FC1D6FBE for ; Thu, 4 Jul 2024 07:11:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.104 X-Spam-Level: X-Spam-Status: No, score=-7.104 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 (2048-bit key) header.d=gmail.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 4HbLm_4yGOaq for ; Thu, 4 Jul 2024 07:11:01 -0700 (PDT) Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1F33C1D6FBA for ; Thu, 4 Jul 2024 07:11:01 -0700 (PDT) Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-5854ac817afso899835a12.2 for ; Thu, 04 Jul 2024 07:11:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720102259; x=1720707059; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=H/zedv/y29JcJSVsR8RiGJb2ZOIoxQcwKDMva4Jy/LU=; b=I3g61+ZbWfXm5BtcHs9RijxiZhBqX6yfR18bBBPXtXq27hSDwkFPiheNd2aGJqLBqv GcR/SDuz9BrXNxrNNnuMxw2VX4I3mtHa+wS722PX/fkEo7cVjSri3Srm3j1szTAO2N+5 RUaRagE5rEL5uCWTEFlCPQuvLyFX+A0qDK4zrlxH/hrKjeZ6Qhm0jYQp6uEEPA4R1zBC kbTJ1fbgrpYuas7JGGFb3Acznjgc7el8I9vdvH+z4DonPfzOQIamV1hiGizDVJZoeuMv uIhLL6fwzOx1I6n/WxW3uhRynpyyPrxCFXrY/Brl9Xai1NLVKq+mtHIX39gmJXXNNXNQ F2tA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720102259; x=1720707059; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=H/zedv/y29JcJSVsR8RiGJb2ZOIoxQcwKDMva4Jy/LU=; b=vBltSKh4Ldjo13rGKSgDnQoh2ZxHfVza23YWJLU3IjO7ioAodTs5xqmAu/NbAIzEEo FfQpjSriOL5oZXrpiXIqKStkSpRRHlrwjIQ40679Xb3i4nZJut4yMl6Zs4AWl+Kd0+9p lXceiqiZf8mKwTEk67eisSanjEr4noTKadLIbL17QoDEm5GH+hrrVhqp5N9Q2D0CbP/g VyxKqRDzv+6XoJx6imCnbgrxgX9dgJtXPAJe7Iivm/FcMF0vg2f6AjhWGYdXxEpszNjb 5R/nRt+rdkwRIGTsEPRRxV80Umo5Y3kt3badR8oECUofsvMC8t1EbTxBp61HJOjwmpFU hkqQ== X-Gm-Message-State: AOJu0YxD2/oL77XNx8dzR2FEPVwQsWDSwC4t8ZXi704OLkUeHiy23PCk A0gZ2s8IJ64WB387wTt14rj0UqSAmoJYcl/LaeiFQ5LCr2/FOWFoMZtH3k9OzCN+zRdm3BPKxeA yOdfUiE7ADyKMWorqrWmG4xkMc5Q= X-Google-Smtp-Source: AGHT+IF515TAD7w7fc8FBZBedOWCp0UyLbA0uiD2SLE73v1iIHGCiKlq5tO5E7xId8rkY+MrvW//B/igg3sVOOeuDEY= X-Received: by 2002:a05:6402:1e92:b0:58c:909f:3d60 with SMTP id 4fb4d7f45d1cf-58e5abdcf89mr1318670a12.16.1720102259169; Thu, 04 Jul 2024 07:10:59 -0700 (PDT) MIME-Version: 1.0 References: <171957523370.366291.478718063778248894@dt-datatracker-ff7f57fbb-ch6dm> <52a77ef4-ec7e-440e-abe7-74d9c3bc325a@isc.org> In-Reply-To: <52a77ef4-ec7e-440e-abe7-74d9c3bc325a@isc.org> From: Tim Wicinski Date: Thu, 4 Jul 2024 10:10:47 -0400 Message-ID: To: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= Content-Type: multipart/alternative; boundary="00000000000022a3e7061c6c84a5" Message-ID-Hash: TDV624GOTXFZJTWBZYJB27V4UULRYGGR X-Message-ID-Hash: TDV624GOTXFZJTWBZYJB27V4UULRYGGR X-MailFrom: tjw.ietf@gmail.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: dnsop@ietf.org X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BDNSOP=5D_Re=3A_Fwd=3A_New_Version_Notification_-_draft-ietf-dns?= =?utf-8?q?op-avoid-fragmentation-18=2Etxt?= List-Id: IETF DNSOP WG mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --00000000000022a3e7061c6c84a5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Petr, On Thu, Jul 4, 2024 at 3:22=E2=80=AFAM Petr =C5=A0pa=C4=8Dek wrote: > I've reviewed version 18 and it seems okay. > > I have only nit: > Section C.1. BIND 9 is using somewhat confusing references to > recommendations. Sometimes it says "recommendation 3" but it means > something else than R3 in the preceding text. > > Some unification would be good, but that's really a nit. This section > will become obsolete over time anyway :-) > > Thanks for this and a good catch. Initially I suggested the recommendations be numbered 1, 2, 3, ... in each section, but then I realized that was confusing and we moved to the R1, R2, .... I also think there has been some consolidation of recommendations. Let me go back a few versions and figure out the changes and apply them to Appendix C.1. I will return with some suggested text. tim Petr =C5=A0pa=C4=8Dek > Internet Systems Consortium > > > On 02. 07. 24 21:49, Tim Wicinski wrote: > > > > (please note I'm sending this to DNSOP and V6OPS) > > > > All > > > > The authors have addressed the comments made during the IESG process an= d > > feedback from DNS implementers, and have published version 18. > > The links for the diff are mentioned below. I will point out the > > additional introduction paragraph added in this version: > > > > This document was originally intended to be a BCP, but due to > > operating system and socket option limitations, some of the > > recommendations have not yet gained real-world experience and > > therefore the document is published as Informational. It is hoped > > and expected that, as operating systems and implementations evolve= , > > we will gain more experience with the recommendations, and plan to > > publish an updated document as a Best Current Practice. > > > > > > Speaking as one who wears many hats, I am OK with this and feel this > > document is the first step in documenting best practices on > > fragmentation with DNS. > > I am always hoping to be proven incorrect. > > > > We will elicit feedback on this latest and we feel the final update. > > We will discuss with Mr Warren tomorrow during our Chairs call if he > > has other concerns. > > > > thanks > > tim > > > > ---------- Forwarded message --------- > > From: > > > Date: Fri, Jun 28, 2024 at 7:47=E2=80=AFAM > > Subject: New Version Notification - > > draft-ietf-dnsop-avoid-fragmentation-18.txt > > To: >, > >, > >, warren@kumari.net>> > > > > > > > > A new version (-18) has been submitted for > > draft-ietf-dnsop-avoid-fragmentation: > > > https://www.ietf.org/archive/id/draft-ietf-dnsop-avoid-fragmentation-18.t= xt > < > https://www.ietf.org/archive/id/draft-ietf-dnsop-avoid-fragmentation-18.t= xt > > > > > > > > The IETF datatracker page for this Internet-Draft is: > > https://datatracker.ietf.org/doc/draft-ietf-dnsop-avoid-fragmentation/ > > > > > > Diff from previous version: > > > https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-dnsop-avoid-fragme= ntation-18 > < > https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-dnsop-avoid-fragme= ntation-18 > > > > > > IETF Secretariat. > > > > > > > > _______________________________________________ > > DNSOP mailing list -- dnsop@ietf.org > > To unsubscribe send an email to dnsop-leave@ietf.org > > -- > Petr =C5=A0pa=C4=8Dek > > _______________________________________________ > DNSOP mailing list -- dnsop@ietf.org > To unsubscribe send an email to dnsop-leave@ietf.org > --00000000000022a3e7061c6c84a5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Petr,

On Thu, Jul 4, 2024 at 3:22=E2=80=AFAM Petr = =C5=A0pa=C4=8Dek <pspacek@isc.org= > wrote:
I= 9;ve reviewed version 18 and it seems okay.

I have only nit:
Section C.1. BIND 9 is using somewhat confusing references to
recommendations. Sometimes it says "recommendation 3" but it mean= s
something else than R3 in the preceding text.

Some unification would be good, but that's really a nit. This section <= br> will become obsolete over time anyway :-)


Thanks for this and a good catch.=C2=A0 Initially I sugge= sted the recommendations be numbered 1, 2, 3, ... in each section, but then= I realized that was confusing and we moved to the R1, R2, ....=C2=A0 I als= o think there has been some consolidation=C2=A0of recommendations.=C2=A0

<= div class=3D"gmail_default" style=3D"font-family:monospace">Let me go back = a few versions and figure out the changes and apply them=C2=A0to Appendix C= .1.=C2=A0=C2=A0

I will return with some suggested text.

tim



Petr =C5=A0pa=C4=8Dek
Internet Systems Consortium


On 02. 07. 24 21:49, Tim Wicinski wrote:
>
> (please note I'm sending this to DNSOP and V6OPS)
>
> All
>
> The authors have=C2=A0addressed=C2=A0the comments=C2=A0made during the= IESG process and
> feedback=C2=A0from DNS implementers, and have published version 18. > The=C2=A0links for the diff are mentioned below.=C2=A0 =C2=A0I will po= int out the
> additional introduction paragraph=C2=A0added in this version:
>
>=C2=A0 =C2=A0 =C2=A0 This document was originally intended to be a BCP,= but due to
>=C2=A0 =C2=A0 =C2=A0 operating system and socket option limitations, so= me of the
>=C2=A0 =C2=A0 =C2=A0 recommendations have not yet gained real-world exp= erience and
>=C2=A0 =C2=A0 =C2=A0 therefore the document is published as Information= al.=C2=A0 It is hoped
>=C2=A0 =C2=A0 =C2=A0 and expected that, as operating systems and implem= entations evolve,
>=C2=A0 =C2=A0 =C2=A0 we will gain more experience with the recommendati= ons, and plan to
>=C2=A0 =C2=A0 =C2=A0 publish an updated document as a Best Current Prac= tice.
>
>
> Speaking as one who wears many hats, I am OK with=C2=A0this and feel t= his
> document is the first step in documenting best practices on
> fragmentation with DNS.
> I am always hoping=C2=A0to be proven incorrect.
>
> We will elicit feedback on this latest and we feel the final update.= =C2=A0
>=C2=A0 =C2=A0We will discuss with Mr Warren tomorrow during our Chairs = call if he
> has other concerns.
>
> thanks
> tim
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
> Date: Fri, Jun 28, 2024 at 7:47=E2=80=AFAM
> Subject: New Version Notification -
> draft-ietf-dnsop-avoid-fragmentation-18.txt
> To: <benno@= nlnetlabs.nl <mailto:benno@nlnetlabs.nl>>, <swoolf@pir.org
> <mailto:swoolf@= pir.org>>, <tjw.ietf@gmail.com
> <mailto:tjw= .ietf@gmail.com>>, <warren@kumari.net <mailto:warren@kumari.net>>
>
>
>
> A new version (-18) has been submitted for
> draft-ietf-dnsop-avoid-fragmentation:
> https://www.ietf.org= /archive/id/draft-ietf-dnsop-avoid-fragmentation-18.txt <https://www.ietf.org/archive/id/draf= t-ietf-dnsop-avoid-fragmentation-18.txt>
>
>
> The IETF datatracker page for this Internet-Draft is:
> https://datatracker.ietf.= org/doc/draft-ietf-dnsop-avoid-fragmentation/
> <https://datatracker.i= etf.org/doc/draft-ietf-dnsop-avoid-fragmentation/>
>
> Diff from previous version:
> https://auth= or-tools.ietf.org/iddiff?url2=3Ddraft-ietf-dnsop-avoid-fragmentation-18= <https://auth= or-tools.ietf.org/iddiff?url2=3Ddraft-ietf-dnsop-avoid-fragmentation-18= >
>
> IETF Secretariat.
>
>
>
> _______________________________________________
> DNSOP mailing list -- dnsop@ietf.org
> To unsubscribe send an email to dnsop-leave@ietf.org

--
Petr =C5=A0pa=C4=8Dek

_______________________________________________
DNSOP mailing list -- d= nsop@ietf.org
To unsubscribe send an email to dnsop-leave@ietf.org
--00000000000022a3e7061c6c84a5--