Re: [auth48] [Ext] AUTH48: RFC-to-be 9499 <draft-ietf-dnsop-rfc8499bis-10> for your review
Madison Church <mchurch@amsl.com> Mon, 18 March 2024 18:32 UTC
Return-Path: <mchurch@amsl.com>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14C60C1D4A68; Mon, 18 Mar 2024 11:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level:
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
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 ReREi_InA9jm; Mon, 18 Mar 2024 11:32:19 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 4FF1FC14F5E3; Mon, 18 Mar 2024 11:32:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 3FBC0424CD3E; Mon, 18 Mar 2024 11:32:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UbJMTodLmg_q; Mon, 18 Mar 2024 11:32:19 -0700 (PDT)
Received: from smtpclient.apple (unknown [199.192.158.121]) by c8a.amsl.com (Postfix) with ESMTPSA id D8234424B455; Mon, 18 Mar 2024 11:32:18 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\))
From: Madison Church <mchurch@amsl.com>
In-Reply-To: <20240314.104533.1896514305115233081.fujiwara@jprs.co.jp>
Date: Mon, 18 Mar 2024 13:32:07 -0500
Cc: RFC Editor <rfc-editor@rfc-editor.org>, dnsop-ads@ietf.org, DNSOP Chairs <dnsop-chairs@ietf.org>, auth48archive@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <18886CF0-1742-4E8E-BDDA-E8597C4D928A@amsl.com>
References: <9FC3A98B-18AB-4EAC-923F-E1187BA20E72@icann.org> <22ADA781-CCE4-4102-99BD-38FAD5BA38B8@amsl.com> <451E99D5-2BEE-4BC5-8E63-8EA81719971F@icann.org> <20240314.104533.1896514305115233081.fujiwara@jprs.co.jp>
To: Kazunori Fujiwara <fujiwara@jprs.co.jp>, Paul Hoffman <paul.hoffman@icann.org>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/HdmFMjL8iXrPygLajTO4eQekshI>
Subject: Re: [auth48] [Ext] AUTH48: RFC-to-be 9499 <draft-ietf-dnsop-rfc8499bis-10> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2024 18:32:23 -0000
Hi Authors, We have now received all necessary approvals and consider AUTH48 complete (see https://www.rfc-editor.org/auth48/rfc9499) Thank you both for your attention and guidance during the AUTH48 process! We will prepare the document for publication at this time. Best regards, RFC Editor/mc > On Mar 13, 2024, at 8:45 PM, Kazunori Fujiwara <fujiwara@jprs.co.jp> wrote: > > Dear RFC editor, > > I reviewed rfc9499-rfcdiff.html. > > It contains fixes of typos, fixes about singular/plural, > item name tagging, unnecessary "*" deletion, missing "" addition, > add/remove "," in some places, fixes of capitalization, > "fully-qualified" -> "fully qualified", > "512 octet" -> "512-octet", > "a general a general" -> "general-purpose", > "draft-*" -> "RFC9471". > > This version is OK for me. (I approve the publication of this version.) > > What I thought was different this time is that recently published RFCs > do not have page numbers in the table of contents. > > -- > Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp> > >> From: Paul Hoffman <paul.hoffman@icann.org> >> Thanks you for those changes. I approve the publication of this version. We are waiting for Kazunori, who may be delayed by his travels to IETF 119 in Brisbane, but I'm sure he'll reply after his careful review. >> >> --Paul Hoffman
- [auth48] AUTH48: RFC-to-be 9499 <draft-ietf-dnsop… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9499 <draft-ietf-d… rfc-editor
- Re: [auth48] [Ext] AUTH48: RFC-to-be 9499 <draft-… Paul Hoffman
- Re: [auth48] [Ext] AUTH48: RFC-to-be 9499 <draft-… Madison Church
- Re: [auth48] [Ext] AUTH48: RFC-to-be 9499 <draft-… Paul Hoffman
- Re: [auth48] [Ext] AUTH48: RFC-to-be 9499 <draft-… Madison Church
- Re: [auth48] [Ext] AUTH48: RFC-to-be 9499 <draft-… Paul Hoffman
- Re: [auth48] [Ext] AUTH48: RFC-to-be 9499 <draft-… Kazunori Fujiwara
- Re: [auth48] [Ext] AUTH48: RFC-to-be 9499 <draft-… Madison Church
- Re: [auth48] AUTH48: RFC-to-be 9499 <draft-ietf-d… Alice Russo