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 9C6D7C1CAE66; Mon, 8 Jul 2024 18:50:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.105 X-Spam-Level: X-Spam-Status: No, score=-7.105 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_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 6R8jqjm-Czfu; Mon, 8 Jul 2024 18:50:39 -0700 (PDT) Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 EAA75C1D4A98; Mon, 8 Jul 2024 18:50:38 -0700 (PDT) Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-2eaa89464a3so48056581fa.3; Mon, 08 Jul 2024 18:50:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720489836; x=1721094636; 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=yZ+1LZjAY1YaVN2UrBFKVg6vOlUIduI/a+nDD3Mjbpg=; b=l5BLHaH/JmSWYsexiyiX8vtJJJRVeqEjGQvgbcaOtTVsfhZP1lnAAzdpVCc00gFW3Y tFV2BOM0J8UWj3JzV30ur108NimeGq0TDtJdZmh1zd00AEqLvenvNBf3Xjwr29rO30pT O6zhFsmDxpF5l8nlk/pLBXfX9IbBUbFgreVuzPZeYCQpNSWAmNQvQHms9iRf3e0a/Kon 8HtjMe6VWCKunK2tCh3zbDuNFkBjeBWI0lKKi6r3rpacw309BJwHCPygB+/DGfF4jwHF UwAlX5GIzJImsUZgubYte15eiGn1w34EJuNn/U4JHJgtLVjKb8/CygFDgzvxgoOeyGNd VnOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720489836; x=1721094636; 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=yZ+1LZjAY1YaVN2UrBFKVg6vOlUIduI/a+nDD3Mjbpg=; b=nzSMYQ/te2MQFZursRwNGUA4od7HFLlgg4g0ktDr/e0nuanTTwBiP3Dqb+aP7f+wsm agqH5eBi52vuUSnc3aPabF7tggtMw3/BVITIl+Bfoo+vGcYpHiK4ZJ3TxlQ4jXs3pM2h 6NgjNu8lbs20tG+6pPYd/5/gosrO4uu1qKRSpIoe57B8z6ZnNFRFRxoCLosP9RQxRcWO RzowZJEo/G/m851tpd8GGVDjF59aNJ1aGZs6kkGGh5pZQxUu/5SMv6EQ89l9PFXmcnUF dsVO8uuo9yxSZAXgOSlCIDKasLecCsIFnE8gniIW2j7Obf+kxXN7hwoz8Q8xSVo6f9NC ucdA== X-Gm-Message-State: AOJu0Yz6ou0WrRp/TH8MPXaIMuH0GNwFBVx0JCYZ8Py/2lrPdQ5Cs9k3 sVTeWqVdOxFk7xDn0Bu8Mj/1cDzzhZBxoLy498VXagVgjUEMLx77WedTZbkEz4518b8OYlk2Uc+ KeVSrM2FDTtXsHJKD32UvUzTdtkvt+w== X-Google-Smtp-Source: AGHT+IHMiB1SaLPBWuKrDxziqGNC+Y0GB0O/Y9I/2k0TVmtVEQRJW8ToEdX5pYk34/lMpo7oYNMm5NysTCRmPXf0zR8= X-Received: by 2002:a2e:9589:0:b0:2ee:8905:769c with SMTP id 38308e7fff4ca-2eeb30fefc2mr7910281fa.28.1720489836055; Mon, 08 Jul 2024 18:50:36 -0700 (PDT) MIME-Version: 1.0 References: <172047471396.458153.12797163404923712142@dt-datatracker-5f88556585-j5r2h> In-Reply-To: <172047471396.458153.12797163404923712142@dt-datatracker-5f88556585-j5r2h> From: Tim Wicinski Date: Mon, 8 Jul 2024 21:50:24 -0400 Message-ID: To: dnsop Content-Type: multipart/alternative; boundary="0000000000008496a6061cc6c1a2" Message-ID-Hash: GB3WAGPOBX4NCFSWG4J3JY64OZCZ6LJT X-Message-ID-Hash: GB3WAGPOBX4NCFSWG4J3JY64OZCZ6LJT 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-chairs X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BDNSOP=5D_Fwd=3A_New_Version_Notification_-_draft-ietf-dnsop-dom?= =?utf-8?q?ain-verification-techniques-05=2Etxt?= List-Id: IETF DNSOP WG mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --0000000000008496a6061cc6c1a2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable All I wanted to call your attention to the most recent update on this document. The authors have worked through a number of open issues primarily around editorial clarity and reorganization of the recommendations. I want to personally thank the authors for working through these issues, and my consistent pushing of them. This is one of those DNSOP documents that may not be relevant to those who implement DNS, or those who operate DNS infrastructure. It is relevant to Applications that use the DNS, and those who focus on what actually DNS records exist in zones. I know there are many new updated drafts that just dropped, but the chairs will confer on sending this back for working group last call in the near term. thanks tim ---------- Forwarded message --------- From: Date: Mon, Jul 8, 2024 at 5:38=E2=80=AFPM Subject: New Version Notification - draft-ietf-dnsop-domain-verification-techniques-05.txt To: A new version (-05) has been submitted for draft-ietf-dnsop-domain-verification-techniques: https://www.ietf.org/archive/id/draft-ietf-dnsop-domain-verification-techni= ques-05.txt https://www.ietf.org/archive/id/draft-ietf-dnsop-domain-verification-techni= ques-05.html The IETF datatracker page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-dnsop-domain-verification-techn= iques/ Diff from previous version: https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-dnsop-domain-verific= ation-techniques-05 IETF Secretariat. --0000000000008496a6061cc6c1a2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

A= ll

I wanted t= o call your attention to the most recent update on this document.=C2=A0 The= authors have worked through a number of open issues primarily around edito= rial clarity and reorganization of the recommendations.=C2=A0 I want to per= sonally thank the authors for working through these issues, and my consiste= nt pushing of them.=C2=A0=C2=A0

This is one of those DNSOP documents that may not be rel= evant to those who implement DNS, or those who operate DNS infrastructure. = It is relevant to Applications that use the DNS, and those who focus on wha= t actually DNS records exist in zones.=C2=A0

I know there are many new updated drafts th= at just dropped, but the chairs will confer on sending this back for workin= g group last call in the near term.

thanks
tim
=C2=A0

---------- Forwarded message ---------
From: <internet-drafts@i= etf.org>
Date: Mon, Jul 8, 2024 at 5:38=E2=80=AFPM
Subj= ect: New Version Notification - draft-ietf-dnsop-domain-verification-techni= ques-05.txt
To: <tjw.ietf@gmai= l.com>



A new version (-05) has been submitted for draft-ietf-dnsop-domain-verifica= tion-techniques:
https://www.ie= tf.org/archive/id/draft-ietf-dnsop-domain-verification-techniques-05.txt
https://www.i= etf.org/archive/id/draft-ietf-dnsop-domain-verification-techniques-05.html<= /a>


The IETF datatracker page for this Internet-Draft is:
https://datatracker= .ietf.org/doc/draft-ietf-dnsop-domain-verification-techniques/

Diff from previous version:
https:= //author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-dnsop-domain-verification-= techniques-05

IETF Secretariat.


--0000000000008496a6061cc6c1a2--