Return-Path: <mchurch@staff.rfc-editor.org>
X-Original-To: auth48archive@mail2.ietf.org
Delivered-To: auth48archive@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1])
	by mail2.ietf.org (Postfix) with ESMTP id 6155AF043428
	for <auth48archive@mail2.ietf.org>; Mon, 18 May 2026 10:59:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1779127168; bh=PKqMm6nVL2QTjEAs1IzgJ1bNrLkk48CfsEq7lfcz2yg=;
	h=Subject:From:In-Reply-To:Date:Cc:References:To;
	b=cGMg5FjY1bccOhO6Vn0Wu/GoyFAYIDiS9fJNdY4gYml8abu9UAtRoqjObtoBe2GUT
	 HHR0G1/0ShOBcOD7l5IzKN0iNZpoYsi713/FcRoxw9gWIAuP+nzvIRZHSM+cpp/MKJ
	 2vrFr0jOu4EoFXfPDYU0OaE6yAnk1wbw+DJbeVuc=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level: 
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5
	tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
	PDS_OTHER_BAD_TLD=1.999, RCVD_IN_DNSWL_NONE=-0.0001,
	SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key)
	header.d=staff-rfc-editor-org.20251104.gappssmtp.com
Received: from mail2.ietf.org ([166.84.6.31])
	by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kb_LuYmXn3ws for <auth48archive@mail2.ietf.org>;
	Mon, 18 May 2026 10:59:27 -0700 (PDT)
Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com
 [IPv6:2607:f8b0:4864:20::231])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256)
	(No client certificate requested)
	by mail2.ietf.org (Postfix) with ESMTPS id 655DAF04341C
	for <auth48archive@rfc-editor.org>; Mon, 18 May 2026 10:59:27 -0700 (PDT)
Received: by mail-oi1-x231.google.com with SMTP id
 5614622812f47-47c7b282e21so988117b6e.1
        for <auth48archive@rfc-editor.org>;
 Mon, 18 May 2026 10:59:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=staff-rfc-editor-org.20251104.gappssmtp.com; s=20251104;
 t=1779127167; x=1779731967; darn=rfc-editor.org;
        h=to:references:message-id:content-transfer-encoding:cc:date
         :in-reply-to:from:subject:mime-version:from:to:cc:subject:date
         :message-id:reply-to;
        bh=xRQ+7XADAjUjU7J6JeY9+bhplAfqPDjGBoVwphHEqWo=;
        b=ilFPJ+rTtimH0j7Ri8BOstpzpNDNoMO+qdjH+4vkK1xbIyXe+Isf5YLc1ziCsEGa5h
         AcIXlNR6wgxcpMxsakJIoyJ2e3XebVqbn6iOPbfPTpKeVsPYukM5kXwxOLhREzX8/suR
         AcLlNmP9PsVNPsZRhUHI/4Iy9bjyrrCBDbG7P0ijgnm/q/WFI0BI5wy8t0XsXGMmNZC2
         GZblf1Q4hMErRvwOQyrxF3/GHrL8Fhki9H2TNFbQkiCuMwVeSpuf3uRbWj/GyT74GITl
         E3HFdQ7u5vtP8UqiuCUa8RUG7XUwJizddHlHP9TXyxQ2of0Js9qlrtgKY+2tR4tCPCSG
         t2zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20251104; t=1779127167; x=1779731967;
        h=to:references:message-id:content-transfer-encoding:cc:date
         :in-reply-to:from:subject:mime-version:x-gm-gg:x-gm-message-state
         :from:to:cc:subject:date:message-id:reply-to;
        bh=xRQ+7XADAjUjU7J6JeY9+bhplAfqPDjGBoVwphHEqWo=;
        b=dW33Vz8akdI2N9l5AczC1+Ao857vf/UhbpqcRnVOD4wAslBGRGXUqQT7/I6BtSNh3U
         Rtj3IkqU447hbcdQmsft5oXVNWfbKw/v5UyRjEL6VMI5OIM1OUgPMm1oz60Krv534Nlj
         5b/Hou+KSvIT6QucJvQtSTfjLRW3w2nfM3rTYtUGe0Gs81hHL3nMjWarbRRVMhzNmVlW
         ksqmS9lIliSGllbi4Fkq1wy1DMKyfxyJ6/miUqOnIZ3peLzHWNQa31Fsiss3X0/Eu6hY
         /jNKX8wCqIX7i/I1f7qEmgYU82q0GT2jDV9coufZWFNmRpQsehobGuBau3mUbsRskwms
         31Vg==
X-Forwarded-Encrypted: i=1;
 AFNElJ85RnVM6MRIq70Xy1vpGjXAM0ysW1M8SZeRPkstCwmPFYIOExTm1vOFqc1WEsrb1TRO75Yf09O4m4o4jJm/@rfc-editor.org
X-Gm-Message-State: AOJu0Yx4Vps7K5TwUCbJgn3zCtXog5aVpVjX1xTrE6tBGdDgqzNy71Cz
	RKL41BXpHcnLk0W6K9mPfQgDvGjnn5gjUe7SqlBTrAuiD5j+uS5njGaUhnSa7pnkCxslOg==
X-Gm-Gg: Acq92OGBJXZNhor8ke4YBAoNIbqZ24LJBTbjakH7MD7XTX3JaGcLCr6hm7dM+7sVR2L
	pf1bRAheizYYdp5aGfhAU3WBglC6P8CMk9jjiLdsQ8fC/VGvTgTvcjrYT2SxN0QEMQAXuWCzA90
	PtJ7K5Ft0bxuwVDhXJ2A4E9fQworTB7KUVrKreYMLzK+bZtKZvPGj/51qaHnm3POz37+xHnmm9v
	Zl4USpY/sqI3xQWweeRaq/wkwi754Hies4iZQn2wlVj0NJ8u92wpNZYZN8Y7szb8VZ4WHHO4YiK
	iUKJVOf7Dv5SzHADxDpabcGGVDvsKCvvuFdQfZxvpFyGKd3abtFEn9A55lLC7wQ3QpLnzOhicEM
	K+5cnr4y9tyGS1YCBZ21e91eEIfxID2dYdMSrbjhzUA6P0LeE/4PkDqRU3o6+gd8VRhwJpOXPkc
	ldHwTjh8b+T+6GmB8yHe2N+B/nJ+Gt98h3z40UkQncvLRPvnhvJsU7CR442PnrTyx6/uA=
X-Received: by 2002:a05:6808:6714:b0:47c:34fd:d391 with SMTP id
 5614622812f47-482e596ce9amr11213505b6e.46.1779127166671;
        Mon, 18 May 2026 10:59:26 -0700 (PDT)
Received: from smtpclient.apple ([199.192.157.25])
        by smtp.gmail.com with ESMTPSA id
 46e09a7af769-7e55bbd10a3sm7902750a34.16.2026.05.18.10.59.25
        (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
        Mon, 18 May 2026 10:59:26 -0700 (PDT)
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
From: Madison Church <mchurch@staff.rfc-editor.org>
In-Reply-To: 
 <SN7PR14MB649241EFA49CEF99724D63D883032@SN7PR14MB6492.namprd14.prod.outlook.com>
Date: Mon, 18 May 2026 12:59:13 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <82F91043-7246-4240-83C7-18E6E2C2F1EE@staff.rfc-editor.org>
References: <20260427181345.5AB7F2CB8F2@rfcpa.rfc-editor.org>
 <VI0PR07MB11371166950BE4CCB3F2B8D50AB322@VI0PR07MB11371.eurprd07.prod.outlook.com>
 <6321131D-25FE-4593-8EC4-2657CF91A17B@staff.rfc-editor.org>
 <VI0PR07MB1137184A00A08B6EAE1D1738BAB3F2@VI0PR07MB11371.eurprd07.prod.outlook.com>
 <gjlzAlPB7kyxcMTAjmWiWh_RE14RdJQlvVHd7QUWw4Vaauj7jgUpIAAprD5op7KHNlw7_dGAn91YTo5F05XzuK-tOGVAyhWzwvQhDWEeXkk=@ounsworth.ca>
 <A4E71416-7EF3-42F7-8AFC-FF3A78ECF9DC@staff.rfc-editor.org>
 <AS4PR07MB8505DB3EDD5752CF40324754F43D2@AS4PR07MB8505.eurprd07.prod.outlook.com>
 <4AAAEF2E-1231-4A1D-858D-289ACE13C2A5@staff.rfc-editor.org>
 <A205D4D6-2DE2-4E10-8286-AE11C6AD488A@staff.rfc-editor.org>
 <VI0PR07MB113717A3F40AF0A62D6F227D9AB032@VI0PR07MB11371.eurprd07.prod.outlook.com>
 <GV2PR07MB9010B1A7D22A55284CCEECA7FE032@GV2PR07MB9010.eurprd07.prod.outlook.com>
 <F7B8A114-E6E2-46D1-82D2-6B5952598A9E@staff.rfc-editor.org>
 <SN7PR14MB649241EFA49CEF99724D63D883032@SN7PR14MB6492.namprd14.prod.outlook.com>
To: Tim Hollebeek <tim.hollebeek@digicert.com>,
 "Dimitrios Schoinianakis (Nokia)"
 <dimitrios.schoinianakis@nokia-bell-labs.com>,
 Mike Ounsworth <mike@ounsworth.ca>,
 "mike.ounsworth@entrust.com" <mike.ounsworth@entrust.com>,
 "K Tirumaleswar Reddy (Nokia)" <k.tirumaleswar_reddy@nokia.com>,
 "Aritra Banerjee (Nokia)" <aritra.banerjee@nokia.com>
X-Mailer: Apple Mail (2.3864.400.21)
Message-ID-Hash: 2GOIX3KWKDGI4QROYGSYMAMHHMZQIUBD
X-Message-ID-Hash: 2GOIX3KWKDGI4QROYGSYMAMHHMZQIUBD
X-MailFrom: mchurch@staff.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency;
 loop; banned-address; member-moderation; nonmember-moderation; administrivia;
 implicit-dest; max-recipients; max-size; news-moderation; no-subject;
 digests; suspicious-header
CC: "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>,
 "pquip-ads@ietf.org" <pquip-ads@ietf.org>,
 "pquip-chairs@ietf.org" <pquip-chairs@ietf.org>,
 "paul.hoffman@icann.org" <paul.hoffman@icann.org>,
 "stndrds-inacio@andrew.cmu.edu" <stndrds-inacio@andrew.cmu.edu>,
 "auth48archive@rfc-editor.org" <auth48archive@rfc-editor.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: =?utf-8?q?=5Bauth48=5D_Re=3A_AUTH48=3A_RFC-to-be_9958_=3Cdraft-ietf-pquip-pq?=
 =?utf-8?q?c-engineers-14=3E_for_your_review?=
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center,
 the authors, and other related parties" <auth48archive.rfc-editor.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/auth48archive/Y5ghkSV1TO98APmi9qHhif9lX8I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Owner: <mailto:auth48archive-owner@rfc-editor.org>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Subscribe: <mailto:auth48archive-join@rfc-editor.org>
List-Unsubscribe: <mailto:auth48archive-leave@rfc-editor.org>

Hi All,

Tim - Thank you for your reply! We have noted your approval for the =
document=E2=80=99s content on the AUTH48 status page (see =
https://www.rfc-editor.org/auth48/rfc9958).

All - We have received all necessary content approvals for this =
document. We will now proceed with RFCXML conversion to make final =
formatting updates as needed. Please keep an eye out for a followup =
email where we will initiate the second part of AUTH48, which will =
contain the XML file as well as updated output files (see =
https://www.rfc-editor.org/rpc/wiki/doku.php?id=3Dpilot_test_instructions_=
completing_auth48_using_kramdown).=20

Thank you!

Madison Church
RFC Production Center

> On May 18, 2026, at 12:09=E2=80=AFPM, Tim Hollebeek =
<tim.hollebeek@digicert.com> wrote:
>=20
>=20
> I approve the draft.
>=20
> -Tim
>=20
> From: Madison Church <mchurch@staff.rfc-editor.org>
> Sent: Monday, May 18, 2026 11:06 AM
> To: Dimitrios Schoinianakis (Nokia) =
<dimitrios.schoinianakis@nokia-bell-labs.com>; =
mike.ounsworth@entrust.com <mike.ounsworth@entrust.com>; K Tirumaleswar =
Reddy (Nokia) <k.tirumaleswar_reddy@nokia.com>; Aritra Banerjee (Nokia) =
<aritra.banerjee@nokia.com>; Mike Ounsworth <mike@ounsworth.ca>; Tim =
Hollebeek <tim.hollebeek@digicert.com>
> Cc: rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org>; =
pquip-ads@ietf.org <pquip-ads@ietf.org>; pquip-chairs@ietf.org =
<pquip-chairs@ietf.org>; paul.hoffman@icann.org =
<paul.hoffman@icann.org>; stndrds-inacio@andrew.cmu.edu =
<stndrds-inacio@andrew.cmu.edu>; =
auth48archive@rfc-editor.org<auth48archive@rfc-editor.org>
> Subject: Re: AUTH48: RFC-to-be 9958 =
<draft-ietf-pquip-pqc-engineers-14> for your review
>=20
> Hi Dimitrios,
>=20
> Thank you for your reply! We have noted your approval of the =
document=E2=80=99s content on the AUTH48 status page =
(seehttps://url.avanan.click/v2/r01/___https://www.rfc-editor.org/auth48/r=
fc9958___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI4YjNiYTc0=
ZDo3OmViMzY6ZWVhYzY5NGU2ZDUzNGU0M2ViYzRmMTVlZGNkMWY0OWJjMmJhOGZjZTY0OTFiMz=
YyMGUxZTA4ZDBiZjkwMjE0NDpwOlQ6Rg).
>=20
> Once we receive approval from Tim, we will move forward with RFCXML =
conversion and complete formatting updates.
>=20
> Thank you!
>=20
> Madison Church
> RFC Production Center
>=20
> > On May 18, 2026, at 2:18=E2=80=AFAM, Dimitrios Schoinianakis (Nokia) =
<dimitrios.schoinianakis@nokia-bell-labs.com> wrote:
> >
> > P {margin-top:0;margin-bottom:0;} I approve the draft.
> >
> > Best,
> > -=CE=B4
> >
> > -----Original Message-----
> > From: Madison Church <mchurch@staff.rfc-editor.org>
> > Sent: Friday, May 15, 2026 7:39 PM
> > To: Aritra Banerjee (Nokia) <aritra.banerjee@nokia.com>; Mike =
Ounsworth <mike@ounsworth.ca>; K Tirumaleswar Reddy (Nokia) =
<k.tirumaleswar_reddy@nokia.com>; Dimitrios Schoinianakis (Nokia) =
<dimitrios.schoinianakis@nokia-bell-labs.com>; =
tim.hollebeek@digicert.com
> > Cc: mike.ounsworth@entrust.com; rfc-editor@rfc-editor.org; =
pquip-ads@ietf.org; pquip-chairs@ietf.org; paul.hoffman@icann.org; =
stndrds-inacio@andrew.cmu.edu; auth48archive@rfc-editor.org
> > Subject: Re: AUTH48: RFC-to-be 9958 =
<draft-ietf-pquip-pqc-engineers-14> for your review
> >
> >
> > CAUTION: This is an external email. Please be very careful when =
clicking links or opening attachments. See the URL nok.it/ext for =
additional information.
> >
> >
> >
> > Hi,
> >
> > This is a friendly weekly reminder that we await content approvals =
from Dimitrios and Tim. Once we receive them, we will move forward with =
RFCXML conversion of this document. At that time, we will ask for =
approvals for formatting, which will be the final approvals needed for =
publication. For details of the AUTH48 process in kramdown-rfc =
(including the two-part approval process), see =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/rpc/wiki/dok=
u.php?id=3Dpilot_test_kramdown_rfc___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNk=
NjA0ZmRiNGE3ZjI3ZWI4YjNiYTc0ZDo3OjAxNDc6ZWE5YzUwYjcwYzQ0MWRiZmJmOTJkOTAzOW=
JmOTJlMzFlN2Q5MDczMzNiNTU1M2ZmYTFiZjM3YzI2ZTdiYjczNzpwOlQ6Rg.
> >
> > Thank you!
> >
> > Madison Church
> > RFC Production Center
> >
> > > On May 8, 2026, at 12:34=E2=80=AFPM, Madison Church =
<mchurch@staff.rfc-editor.org> wrote:
> > >
> > > Hi Aritra,
> > >
> > > Thank you for your reply! We have noted your approval of the =
document=E2=80=99s contents on the AUTH48 status page (see =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/auth48/rfc99=
58___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI4YjNiYTc0ZDo3=
OjFhMWI6MjAzNTNlYjYwMGRhYmE3NDYzN2ZiMDFmY2E0NDg0ZmY2ODhmZmNkNDRkODJjNTQ2Yz=
AxOTUyNWRjN2E2OTIxMTpwOlQ6Rg). Once we receive approvals from Dimitrios =
and Tim, we will move forward with RFCXML conversion and complete =
formatting updates. For details of the AUTH48 process in kramdown-rfc =
(including the two-part approval process), see =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/rpc/wiki/dok=
u.php?id=3Dpilot_test_kramdown_rfc___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNk=
NjA0ZmRiNGE3ZjI3ZWI4YjNiYTc0ZDo3OmFhYzI6MjkzMjJiNDYwM2JjMzAxMzZhYmM1MGQzND=
Q2N2I5YTg3MTg1ODVhMjYyZjY0ZTIyYzc3ZDhhYWU4ZDg3ZDlmNjpwOlQ6Rg.
> > >
> > > Thank you!
> > >
> > > Madison Church
> > > RFC Production Center
> > >
> > >> On May 8, 2026, at 1:32=E2=80=AFAM, Aritra Banerjee (Nokia) =
<aritra.banerjee@nokia.com> wrote:
> > >>
> > >> Hi Madison,
> > >> I have reviewed the latest AUTH48 version of the document and am =
satisfied with the proposed updates. The revisions and changes looks =
good to me.
> > >> I confirm that I am happy with the latest version and approve =
RFC-to-be 9958 it for publication.
> > >> Regards,
> > >> Aritra.
> > >>
> > >> From: Madison Church <mchurch@staff.rfc-editor.org>
> > >> Date: Thursday, 7 May 2026 at 21:39
> > >> To: Mike Ounsworth <mike@ounsworth.ca>; K Tirumaleswar Reddy =
(Nokia)
> > >> <k.tirumaleswar_reddy@nokia.com>; Aritra Banerjee (Nokia)
> > >> <aritra.banerjee@nokia.com>; Dimitrios Schoinianakis (Nokia)
> > >> <dimitrios.schoinianakis@nokia-bell-labs.com>;
> > >> tim.hollebeek@digicert.com <tim.hollebeek@digicert.com>
> > >> Cc: mike.ounsworth@entrust.com <mike.ounsworth@entrust.com>;
> > >> rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org>;
> > >> pquip-ads@ietf.org <pquip-ads@ietf.org>; pquip-chairs@ietf.org
> > >> <pquip-chairs@ietf.org>; paul.hoffman@icann.org
> > >> <paul.hoffman@icann.org>; stndrds-inacio@andrew.cmu.edu
> > >> <stndrds-inacio@andrew.cmu.edu>; auth48archive@rfc-editor.org
> > >> <auth48archive@rfc-editor.org>
> > >> Subject: Re: AUTH48: RFC-to-be 9958
> > >> <draft-ietf-pquip-pqc-engineers-14> for your review
> > >>
> > >>
> > >> CAUTION: This is an external email. Please be very careful when =
clicking links or opening attachments. See the URL nok.it/ext for =
additional information.
> > >>
> > >>
> > >>
> > >> Hi Mike,
> > >>
> > >> Thank you for your reply! We have noted your approval of the =
document=E2=80=99s content on the AUTH48 status page (see =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/auth48/rfc99=
58___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI4YjNiYTc0ZDo3=
OjEwNzg6ZTJkNGNkMjAxZjBkOTAwMzNiNzNhMGQzN2M4YmY1NzU4Y2NlNjNkYTI1MzM3YjAzYj=
kxM2ZhNWY5NDc5YjgyODpwOlQ6Rg).
> > >>
> > >> Once we receive approvals from Aritra, Dimitrios, and Tim, we =
will move forward with RFCXML conversion and complete formatting =
updates. For details of the AUTH48 process in kramdown-rfc (including =
the two-part approval process), see =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/rpc/wiki/dok=
u.php?id=3Dpilot_test_kramdown_rfc___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNk=
NjA0ZmRiNGE3ZjI3ZWI4YjNiYTc0ZDo3OmM4NzI6ZjRkNzY0ZjgyYTYxMWFkNDg4MDczNTkzYT=
M5ZjIwMjhmNWVlZWY3M2MwYzIzYTgyMzVmM2U3NWI0NmZmNDQ4NjpwOlQ6Rg.
> > >>
> > >> Thank you!
> > >>
> > >> Madison Church
> > >> RFC Production Center
> > >>
> > >>> On May 7, 2026, at 12:58=E2=80=AFPM, Mike Ounsworth =
<mike@ounsworth.ca> wrote:
> > >>>
> > >>> I have also reviewed the diff top-to-bottom: great grammatical =
and consistency changes. Nothing jumped out to me as adversely affecting =
the technical meaning. Very well done!
> > >>>
> > >>> I also approve publication.
> > >>>
> > >>>
> > >>> -Mike Ounsworth
> > >>>
> > >>> "Knowing is a barrier which prevents learning" -- Frank Herbert, =
Dune.
> > >>>
> > >>>
> > >>> "An expert is a person who has found out by his own painful
> > >>> experience all the mistakes that one can make in a very narrow
> > >>> field.=E2=80=9D -- Niels Bohr
> > >>>
> > >>> On Wednesday, May 6th, 2026 at 5:43 AM, K Tirumaleswar Reddy =
(Nokia) <k.tirumaleswar_reddy@nokia.com> wrote:
> > >>>
> > >>>> Hi,
> > >>>>
> > >>>> I've finished reviewing the diff and I am happy to report that =
the updates look good to me.
> > >>>> I approve the publication of the specification.
> > >>>>
> > >>>> Cheers,
> > >>>> -Tiru
> > >>>>
> > >>>> -----Original Message-----
> > >>>> From: Madison Church <mchurch@staff.rfc-editor.org>
> > >>>> Sent: Wednesday, May 6, 2026 3:19 AM
> > >>>> To: K Tirumaleswar Reddy (Nokia) =
<k.tirumaleswar_reddy@nokia.com>;
> > >>>> Aritra Banerjee (Nokia) <aritra.banerjee@nokia.com>; Dimitrios
> > >>>> Schoinianakis (Nokia)
> > >>>> <dimitrios.schoinianakis@nokia-bell-labs.com>;
> > >>>> tim.hollebeek@digicert.com; mike@ounsworth.ca;
> > >>>> mike.ounsworth@entrust.com
> > >>>> Cc: rfc-editor@rfc-editor.org; pquip-ads@ietf.org;
> > >>>> pquip-chairs@ietf.org; paul.hoffman@icann.org;
> > >>>> stndrds-inacio@andrew.cmu.edu; auth48archive@rfc-editor.org
> > >>>> Subject: Re: AUTH48: RFC-to-be 9958
> > >>>> <draft-ietf-pquip-pqc-engineers-14> for your review
> > >>>>
> > >>>>
> > >>>> CAUTION: This is an external email. Please be very careful when =
clicking links or opening attachments. See the URL nok.it/ext for =
additional information.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Authors,
> > >>>>
> > >>>> Tirumaleswar - Thank you for your reply! We have updated the =
document per your response. Please see inline for a few followup items =
for your review (note that we have cut resolved questions to limit the =
length of this thread). Aside from the brief notes below, we have no =
further questions relating to content at this time.
> > >>>>
> > >>>>> On May 1, 2026, at 6:51=E2=80=AFAM, K Tirumaleswar Reddy =
(Nokia) <k.tirumaleswar_reddy=3D40nokia.com@dmarc.ietf.org> wrote:
> > >>>>>
> > >>>>> Hi,
> > >>>>> Please see inline [TR]
> > >>>>> -----Original Message-----
> > >>>>> From: rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org>
> > >>>>> Sent: Monday, April 27, 2026 11:44 PM
> > >>>>> To: Aritra Banerjee (Nokia) <aritra.banerjee@nokia.com>; K
> > >>>>> Tirumaleswar Reddy (Nokia) <k.tirumaleswar_reddy@nokia.com>;
> > >>>>> Dimitrios Schoinianakis (Nokia)
> > >>>>> <dimitrios.schoinianakis@nokia-bell-labs.com>;
> > >>>>> tim.hollebeek@digicert.com; mike.ounsworth@entrust.com
> > >>>>> Cc: rfc-editor@rfc-editor.org; pquip-ads@ietf.org;
> > >>>>> pquip-chairs@ietf.org; paul.hoffman@icann.org;
> > >>>>> stndrds-inacio@andrew.cmu.edu; auth48archive@rfc-editor.org
> > >>>>> Subject: Re: AUTH48: RFC-to-be 9958
> > >>>>> <draft-ietf-pquip-pqc-engineers-14> for your review
> > >>>>> CAUTION: This is an external email. Please be very careful =
when clicking links or opening attachments. See the URL nok.it/ext for =
additional information.
> > >>>>>  Authors,
> > >>>>> While reviewing this document during AUTH48, please resolve =
(as necessary) the following questions, which are also in the source =
file.
> > >>>>> 1) <!-- [rfced] FYI - We will do the following when we convert =
the file to RFCXML:
> > >>>>> a) Correct author names in reference entry for =
draft-ietf-pquip-pqc-hsm-constrained.
> > >>>>> Current:
> > >>>>>  [I-D.ietf-pquip-pqc-hsm-constrained]
> > >>>>>             Reddy.K, T., Wing, D., S, B., and K. Kwiatkowski,
> > >>>>>             "Adapting Constrained Devices for Post-Quantum
> > >>>>>             Cryptography", Work in Progress, Internet-Draft, =
draft-
> > >>>>>             ietf-pquip-pqc-hsm-constrained-02, 18 October =
2025,
> > >>>>>             =
<https://url.avanan.click/v2/r01/___https://datatracker.ietf.org/doc/html/=
draft-ietf-pquip-___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3Z=
WI4YjNiYTc0ZDo3OjJhYTk6NGJlM2I3ZjBhMDgzMjM0OWE0YThhNmE0ZjhkMTkyMTg5M2NiNzE=
0N2U2N2M2Mzk5MDU5OWRmY2M1YTM0MWU0MjpwOlQ6Rg
> > >>>>>             pqc-hsm-constrained-02>.
> > >>>>> -->
> > >>>>> [TR] Okay
> > >>>>>
> > >>>>> 4) <!-- [rfced] In Sections 5.1.1, 5.1.2, and 6.1, may we =
update the lists to better indicate the term being defined? We suggest =
placing the term rather than the citation before the colon. See the =
suggested text in a), b), and c) below.
> > >>>>> We also have some additional questions regarding Section =
5.1.2:
> > >>>>> - How should "FN" in "FN-DSA" be expanded? Perhaps as =
"Fast-Fourier Transform over NTRU-Lattice-Based Digital Signature =
Algorithm"?
> > >>>>> [TR] Yes.
> > >>>>> - The FN-DSA entry includes pointers to Sections 8.1 and 10.2, =
but
> > >>>>> ML-DSA and SLH-DSA are also mentioned in those setions. Should =
the
> > >>>>> pointers to Sections
> > >>>>> 8.1 and 10.2 apply to all entries?
> > >>>>> [TR] Section 8.1 covers lattice-based cryptography and is =
therefore applicable only to ML-DSA and FN-DSA, not to SLH-DSA (which is =
hash-based, covered in Section 8.2). Section 10.2 applies to all three.
> > >>>>> - We do not see "FN-DSA" mentioned in the URL listed for =
[FN-DSA]. Please review. Also, should this reference be to FIPS 206, or =
should the relationship between FIPS 206 and Fast Fourier/Falcon be =
explained for the reader? It seems that FIPS 206 is still in draft form.
> > >>>>> [TR] FIPS 206 has not yet been released by NIST. The current =
reference correctly points =
tohttps://url.avanan.click/v2/r01/___https://falcon-sign.info/___.YXAzOmRp=
Z2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI4YjNiYTc0ZDo3OjMyYTU6OTY4YW=
JmMDY2ZjFmMDQxODk1MWJiODcyNDE5MWQ4MDIxNjE0ODhhNjFjMGIzY2M5MzI4YjhkNGFhYTU3=
YjNlOTpwOlQ6Rg, which is the FALCON project website. The text in the =
draft should make clear that FN-DSA is the name NIST has assigned to =
FALCON for the forthcoming FIPS 206 standard, but since that standard is =
not yet published, the FALCON project website remains the appropriate =
reference for now.
> > >>>>
> > >>>> [rfced] Thank you for this information! We will consult with =
our citation specialist for any additional changes that need to be made =
to this reference. For now, we have updated Sections 5.1.1, 5.1.2, and =
6.1 according to our initial AUTH48 questions with the following change =
in Section 5.1.2 to address FIPS 206. Please let us know if this text =
needs any further updates.
> > >>>>
> > >>>> Current:
> > >>>> FN-DSA:  Fast-Fourier Transform over NTRU-Lattice-Based Digital =
Signature Algorithm. See [FN-DSA]; note that, at the time of =
publication, FIPS 206 has not been published.
> > >>>>
> > >>>>> a) Section 5.1.1
> > >>>>> Original
> > >>>>>  *  [ML-KEM]: Module-Lattice-based Key-Encapsulation Mechanism
> > >>>>>     Standard (FIPS-203).
> > >>>>>   *  [HQC]: Hamming Quasi-Cyclic coding algorithm which is =
based on the
> > >>>>>     hardness of the syndrome decoding problem for quasi-cyclic
> > >>>>>     concatenated Reed-Muller and Reed-Solomon (RMRS) codes in =
the
> > >>>>>     Hamming metric.  Reed-Muller (RM) codes are a class of =
block
> > >>>>>     error-correcting codes commonly used in wireless and =
deep-space
> > >>>>>     communications, while Reed-Solomon (RS) codes are widely =
used to
> > >>>>>     detect and correct multiple-bit errors.  HQC has been =
selected as
> > >>>>>     part of the NIST post-quantum cryptography project but has =
not yet
> > >>>>>     been standardized.
> > >>>>> Perhaps:
> > >>>>>  ML-KEM:  Module-Lattice-Based Key Encapsulation Mechanism. =
See
> > >>>>>     FIPS 203 [ML-DSA].
> > >>>>> [TR] In the above line, replace ML-DSA with ML-KEM
> > >>>>>   HQC:  Hamming Quasi-Cyclic. See [HQC]. The coding algorithm =
based on the
> > >>>>>     hardness of the syndrome decoding problem for quasi-cyclic
> > >>>>>     concatenated Reed-Muller and Reed-Solomon (RMRS) codes in =
the
> > >>>>>     Hamming metric.  Reed-Muller (RM) codes are a class of =
block
> > >>>>>     error-correcting codes commonly used in wireless and =
deep-space
> > >>>>>     communications, while Reed-Solomon (RS) codes are widely =
used to
> > >>>>>     detect and correct multiple-bit errors.  HQC has been =
selected as
> > >>>>>     part of the NIST post-quantum cryptography project but has =
not yet
> > >>>>>     been standardized.
> > >>>>> b) Section 5.1.2
> > >>>>> Original:
> > >>>>>   *  [ML-DSA]: Module-Lattice-Based Digital Signature Standard =
(FIPS-
> > >>>>>      204).
> > >>>>>    *  [SLH-DSA]: Stateless Hash-Based Digital Signature =
(FIPS-205).
> > >>>>>    *  [FN-DSA]: FN-DSA is a lattice signature scheme =
(FIPS-206)
> > >>>>>      (Section 8.1 and Section 10.2).
> > >>>>> Perhaps:
> > >>>>>  ML-DSA:  Module-Lattice-Based Digital Signature Algorithm. =
See FIPS
> > >>>>>     204 [ML-DSA].
> > >>>>>   SLH-DSA: Stateless Hash-Based Digital Signature Algorithm. =
See FIPS
> > >>>>>     205 [SLH-DSA].
> > >>>>>   FN-DSA:  Fast-Fourier Transform over NTRU-Lattice-Based =
Digital
> > >>>>>     Signature Algorithm. See FIPS 206 [FN-DSA].
> > >>>>>   For more information about these, see Sections 8.1 and 10.2.
> > >>>>> [TR] For more information about these, see Sections 8.1, 8.2 =
and 10.2.
> > >>>>> c) Section 6.1
> > >>>>> Original:
> > >>>>>  *  [FrodoKEM]: Key Encapsulation mechanism based on the =
hardness of
> > >>>>>     learning with errors in algebraically unstructured =
lattices.
> > >>>>>   *  [ClassicMcEliece]: Based on the hardness of syndrome =
decoding of
> > >>>>>     Goppa codes.  Goppa codes are a class of error-correcting =
codes
> > >>>>>     that can correct a certain number of errors in a =
transmitted
> > >>>>>     message.  The decoding problem involves recovering the =
original
> > >>>>>     message from the received noisy codeword.
> > >>>>>   *  [NTRU]: Key encapsulation mechanism based on the "N-th =
degree
> > >>>>>     Truncated polynomial Ring Units" (NTRU) lattices.  =
Variants
> > >>>>>     include Streamlined NTRU Prime (sntrup761), which is =
leveraged for
> > >>>>>     use in SSH [I-D.ietf-sshm-ntruprime-ssh].
> > >>>>> Perhaps:
> > >>>>>  FrodoKEM:  KEM based on the hardness of learning with errors =
in
> > >>>>>     algebraically unstructured lattices. See [FrodoKEM].
> > >>>>>   Classic McEliece:  KEM based on the hardness of syndrome =
decoding of
> > >>>>>     Goppa codes.  Goppa codes are a class of error-correcting =
codes
> > >>>>>     that can correct a certain number of errors in a =
transmitted
> > >>>>>     message.  The decoding problem involves recovering the =
original
> > >>>>>     message from the received noisy codeword. See =
[ClassicMcEliece].
> > >>>>>   NTRU:  KEM based on the "N-th degree Truncated polynomial =
Ring
> > >>>>>     Units" (NTRU) lattices.  Variants include Streamlined NTRU =
Prime
> > >>>>>     (sntrup761), which is leveraged for use in SSH [RFC9941]. =
See [NTRU].
> > >>>>> -->
> > >>>>> [TR] Okay.
> > >>>>>
> > >>>>> 15) <!-- [rfced] References
> > >>>>> a) FYI - We note that draft-hale-mls-combiner-01 has been =
replaced with draft-ietf-mls-combiner-02. Should this reference entry be =
updated accordingly? Note that the title has changed.
> > >>>>> Original:
> > >>>>>  [I-D.hale-mls-combiner]
> > >>>>>             Jo=C3=ABl, Hale, B., Mularczyk, M., and X. Tian, =
"Flexible
> > >>>>>             Hybrid PQ MLS Combiner", Work in Progress, =
Internet-Draft,
> > >>>>>             draft-hale-mls-combiner-01, 26 September 2024,
> > >>>>>             =
<https://url.avanan.click/v2/r01/___https://datatracker.ietf.org/doc/html/=
draft-hale-mls-___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI=
4YjNiYTc0ZDo3OjljZmU6YTI5ZjNmMDU2M2U4ODUyZjMyMmFjMjU4OWVkNzhiYzYzZGRmMzNiY=
jRjNTQ0Y2I1ZDVjMjUzNDk3NGM3ODdlNzpwOlQ6Rg
> > >>>>>             combiner-01>.
> > >>>>> Perhaps:
> > >>>>>  [PQ-MLS]
> > >>>>>             Tian, X., Hale, B., Mularczyk, M., and J. Alwen, =
"Amortized
> > >>>>>             PQ MLS Combiner", Work in Progress, =
Internet-Draft,
> > >>>>>             draft-ietf-mls-combiner-02, 20 October 2025,
> > >>>>>             =
<https://url.avanan.click/v2/r01/___https://datatracker.ietf.org/doc/html/=
draft-ietf-mls-combiner-02___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRi=
NGE3ZjI3ZWI4YjNiYTc0ZDo3OmJhNDc6M2Y3MzFiOGMzNzA1MzBmY2I3NDg5MTNlMjFhMWE1ND=
FhYjhlMTAxM2NiODk1MmQ4ODg1MGQyNjQyZDg4MWIxNzpwOlQ6Rg>.
> > >>>>> [TR] Yes.
> > >>>>
> > >>>> [rfced] Noted! We will include this change once we convert to =
RFCXML.
> > >>>>
> > >>>>> 17) <!-- [rfced] Would you like to make use of <sup> for
> > >>>>> superscript in this document? In the HTML and PDF, it appears =
as superscript. In the text output, <sup> generates a^b, which was used =
in the original document. (Note that if you would like to use <sup>, we =
will make the update once the file is converted to RFCXML.)  Instances =
in document:
> > >>>>> 2^{64}
> > >>>>> 2^c
> > >>>>> 2^{(128=E2=88=92c)/2}
> > >>>>> 2^64
> > >>>>> -->
> > >>>>> [TR] Looks good, Thanks.
> > >>>>
> > >>>> [rfced] We will include these changes once we convert to =
RFCXML.
> > >>>>
> > >>>> Please review the contents of the document carefully. Contact =
us with any further updates or with your approval of the document=E2=80=99=
s contents in its current form. We will await approvals from each author =
prior to moving forward with formatting updates.
> > >>>>
> > >>>> For details of the AUTH48 process in kramdown-rfc (including =
the two-part approval process), =
seehttps://url.avanan.click/v2/r01/___https://www.rfc-editor.org/rpc/wiki/=
doku.php?id=3Dpilot_test_kramdown_rfc___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0M=
zNkNjA0ZmRiNGE3ZjI3ZWI4YjNiYTc0ZDo3OmIyNGE6NTU0ZjZhYjVjNWQ0MzA4NGQ2MTIwYWR=
lMWJjZDlmMjkyNTIxM2ZkZTY0N2QwYWVhNmE0YzdlZDMyODE3MDE3NjpwOlQ6Rg.
> > >>>>
> > >>>> The files have been posted here (please refresh):
> > >>>>  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958.txt___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI4YjNiYTc=
0ZDo3OmE3ODc6MWQ3ZDI4YzFhNzk4Mzk5M2VlY2UwY2VmYTI3ODU2YjI4OTUzOTBkN2E4MTAyZ=
jAzMTA0MDcyYzhlMjZlYWZiMjpwOlQ6Rg
> > >>>>  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958.pdf___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI4YjNiYTc=
0ZDo3OmU4MmQ6MWU2MGZlMjMzMGRjNjM5ZDgyZDhiZDQzZWQ5YThjYTJiYmI4MzhmOGEzMzg5Y=
Tg3MmU3NWZhMGYxMzhhNmUxNzpwOlQ6Rg
> > >>>>  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958.html___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI4YjNiYT=
c0ZDo3OmVkZTk6Zjk2MzNkZjBjMTllYzE3YjMyMTViODAzOTc3MmE3OTU5ZDAzNTRkMjE3ZGVk=
ZjViZjI4NTc3YjFkZDQ3M2ExODpwOlQ6Rg
> > >>>>  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958.xml___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI4YjNiYTc=
0ZDo3OjQzNWM6NDczMDZlZGU0ZTc5OGU4ZjQ1MzMwNmM1OWU4ZmIyYzA0MTQwMDQ3MDIxNWQ0M=
mY5NTZkZTg5ZjkxMTg0MjZkYzpwOlQ6Rg
> > >>>>  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958.md___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI4YjNiYTc0=
ZDo3OjdmNjk6ZjhiZGJmZTY2MDMxNTM2MzBjNDZlZmYzOTM3NjA1OWNiNDhhNWQ5OGM0MDU4ZD=
llMDY1NTNlOTExMGE5YWNjNDpwOlQ6Rg
> > >>>>
> > >>>> The relevant diff files have been posted here (please refresh):
> > >>>>  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958-diff.html___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI4Y=
jNiYTc0ZDo3OjQ3ZTI6OTIwOGNjM2NkZmU0MzI2MTlmZTE1NjQzZDE4OWMzZWIxOTNkNDJhN2E=
xZDc1MDhiMjQxNGYxNzUxZWE3Mzk3ODpwOlQ6Rg
> > >>>> (comprehensive diff)
> > >>>> =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958-rfcdiff.html___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZW=
I4YjNiYTc0ZDo3OmQ0OTA6YWFmOTk4OGZhMGRiZjkyMDM3MGJmODE1OTVkYzhjMzZkMWE1MDky=
MmM1MjgyYTY5ZmI2NzhmMGU4MGE4ZmM1YjpwOlQ6Rg (side by
> > >>>> side)  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958-auth48diff.html___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI=
3ZWI4YjNiYTc0ZDo3OjliOWM6Zjk4YzQ3NzJlYjhkMGEzNTczYjRjNzRmNDE5ZjEwZjA0Mzc0Z=
mUxODIxODc0ODhjNjhiMWY4NTE2YzkyY2FmZjpwOlQ6Rg
> > >>>> (AUTH48 changes only)
> > >>>> =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958-auth48rfcdiff.html___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3=
ZjI3ZWI4YjNiYTc0ZDo3OjMzODQ6M2Q0NTc0NzQ1OTM4NDE3YjAwYzYyNDU1NTQ2NTFiNGQwYz=
NhNjQ2OGI4ODJkOWNhYTE1ZGE0MjJmMTllZTdiMzpwOlQ6Rg (side
> > >>>> by side)
> > >>>>
> > >>>> Markdown diffs:
> > >>>>  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958-md-diff.html___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZW=
I4YjNiYTc0ZDo3OmQwMzk6MWE0MTc2ZmU5N2Y3YzU0OWRlMWVkNWU4MGVhYmNiMDE1MGVmMmMx=
NDYzOThkOGI3OGFiMjg4Y2QzYjgyMWMyYTpwOlQ6Rg
> > >>>>  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958-md-rfcdiff.html___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI=
3ZWI4YjNiYTc0ZDo3OjhmM2E6MzAzYmY4ZWVmMzZkOTU4MDUxODI1MmQyYTI2Y2RjMGRhNjg2O=
GNlNzc0MTk4YTZlODE4ZDJjYzY4ZTQ3OTQwYTpwOlQ6Rg
> > >>>>  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958-md-auth48diff.html___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3=
ZjI3ZWI4YjNiYTc0ZDo3OmI3MTc6OGIxMmViYTRjZDQ2OGQyMDNmMjZjMzcyYjY3YjI5YmQ2MD=
I1ZjhkMjA3ZjU1NGRkODg5NmM0NjllMDI4NzgyZjpwOlQ6Rg
> > >>>>  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/authors/rfc9=
958-md-auth48rfcdiff.html___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiN=
GE3ZjI3ZWI4YjNiYTc0ZDo3OmRlMmE6NzMzMzkxZmVhYzdmMGY1MTA2Zjg1Mzc1MzE0N2ZkY2V=
lZjA0OWQ3MzQ5OTc1MGE4YzEzMzQ0ZDZiZjcxZTNlNzpwOlQ6Rg
> > >>>>
> > >>>> For the AUTH48 status of this document, please see:
> > >>>>  =
https://url.avanan.click/v2/r01/___https://www.rfc-editor.org/auth48/rfc99=
58___.YXAzOmRpZ2ljZXJ0OmE6bzplYmE1Mzk0MzNkNjA0ZmRiNGE3ZjI3ZWI4YjNiYTc0ZDo3=
OmVmNDA6NDdhYzJlMDVlZWJkMGFiNWNiYzk1ZGUwMGI5MmU4ZTUyYmJiMzRiODhhMWI0NzY5Zj=
Q1NTc3NDdhOTI0NTkyYjpwOlQ6Rg
> > >>>>
> > >>>> Thank you!
> > >>>> Madison Church
> > >>>> RFC Production Center
> > >>>>
> > >>>>
> > >>
> > >
> >


