From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <5CDA1410-7635-4455-8B64-7686FF6ECFF9@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_F3920785-2EDD-46FF-B9B7-2436B50E7C1D"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.500.181\))
Date: Thu, 4 Jun 2026 13:38:43 -0700
In-Reply-To: <6B095216-447F-498D-B8D8-6EB774CF1C97@staff.rfc-editor.org>
To: Madison Church <mchurch@staff.rfc-editor.org>
References: <177948050282.17.14048359198082471617@rfc-editor.org>
 <6f808e7d-fab6-4ab6-96dc-4304119690f5@pfrc.org>
 <83583333-D496-491D-A931-DB5B2625B8B9@staff.rfc-editor.org>
 <29A8B5D5-3ACF-4F3A-9454-C8C6D5F94B80@freeradius.org>
 <5CBC0DAD-1906-464D-AEF9-3C1E27C0F3F0@staff.rfc-editor.org>
 <FECA013E-78F6-4E33-897F-148D97B217D1@gmail.com>
 <6B095216-447F-498D-B8D8-6EB774CF1C97@staff.rfc-editor.org>
Message-ID-Hash: CE2X4LJIUP2VBEHU64SASZ3PPAY3LZI3
CC: Alan DeKok <aland@freeradius.org>, Jeffrey Haas <jhaas@pfrc.org>,
 Sonal Agarwal <sagarwal12@gmail.com>,
 Ashesh Mishra <mishra.ashesh@outlook.com>,
 Ketan Talaulikar <ketant.ietf@gmail.com>,
 RFC Editor <rfc-editor@rfc-editor.org>, auth48archive@rfc-editor.org,
 Reshad Rehman <reshad@yahoo.com>, rtg-ads@ietf.org, bfd-chairs@ietf.org,
 Jim Guichard <james.n.guichard@futurewei.com>,
 Gunter van de Velde <gunter.van_de_velde@nokia.com>
Precedence: list
Subject: =?utf-8?q?=5Bauth48=5D_Re=3A_RFC-to-be_9986_draft-ietf-bfd-secure-sequence-n?=
 =?utf-8?q?umbers_for_your_review?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/auth48archive/nFdikbvC842FerwRad4XuEfNNF4>


--Apple-Mail=_F3920785-2EDD-46FF-B9B7-2436B50E7C1D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Madison,

Sonal did respond with an approval and asked for her contact information =
to be updated. Did you see it?

Thanks

p.s. Let me ping Ashesh.

> On Jun 4, 2026, at 9:19=E2=80=AFAM, Madison Church =
<mchurch@staff.rfc-editor.org> wrote:
>=20
> Hi Mahesh,
>=20
> Thank you for your reply! We have noted your approval here: =
https://queue.rfc-editor.org/final-review/rfc9986/.
>=20
> Once we receive approvals from Ashesh and Sonal, we will move this =
document forward in the publication process.
>=20
> Thank you!
>=20
> Madison Church
> RFC Production Center
>=20
>> On Jun 3, 2026, at 7:07=E2=80=AFPM, Mahesh Jethanandani =
<mjethanandani@gmail.com> wrote:
>>=20
>> Hi Madison,
>>=20
>> I am not sure if I sent my approval already, but here it is, in case =
I missed sending it
>>=20
>> Thanks.
>>=20
>>> On Jun 2, 2026, at 12:00=E2=80=AFPM, Madison Church =
<mchurch@staff.rfc-editor.org> wrote:
>>>=20
>>> Alan, *Ketan,
>>>=20
>>> *Ketan - We have noted your approval for moving RFC 8341 to the =
Normative References section.
>>>=20
>>> Alan - Thank you for your reply! We have updated the document per =
your response and noted your approval on the Final Review (formerly =
AUTH48) status page; see =
https://queue.rfc-editor.org/final-review/rfc9986/.
>>>=20
>>> The files have been posted here (please refresh):
>>> https://www.rfc-editor.org/authors/rfc9986.txt
>>> https://www.rfc-editor.org/authors/rfc9986.pdf
>>> https://www.rfc-editor.org/authors/rfc9986.html
>>> https://www.rfc-editor.org/authors/rfc9986.xml
>>>=20
>>> Updated diff files have been posted here:
>>> https://www.rfc-editor.org/authors/rfc9986-diff.html
>>> https://www.rfc-editor.org/authors/rfc9986-rfcdiff.html (side by =
side)
>>> https://www.rfc-editor.org/authors/rfc9986-auth48diff.html
>>> https://www.rfc-editor.org/authors/rfc9986-auth48rfcdiff.html (side =
by side)
>>>=20
>>> Once we receive approval from Mahesh, Sonal, and Ashesh, we will =
move this document forward in the publication process.
>>>=20
>>> Thank you!
>>>=20
>>> Madison Church
>>> RFC Production Center
>>>=20
>>>> On Jun 2, 2026, at 11:27=E2=80=AFAM, Alan DeKok =
<aland@freeradius.org> wrote:
>>>>=20
>>>> On May 29, 2026, at 4:47=E2=80=AFPM, Madison Church =
<mchurch@staff.rfc-editor.org> wrote:
>>>>>>> 17) <!-- [rfced] For the "[ISAAC_]" reference, we recommend =
changing the citation
>>>>>>> tag since "[ISAAC]" and "[ISAAC_]" may be easily confused. May =
we update
>>>>>>> "[ISAAC_]" to "[ISAAC+]" or "[ISAAC-Plus]"?
>>>>>>> -->
>>>>>> This question to be answered by Alan and the SEC-ADs.
>>>>>=20
>>>>> [rfced] We will wait for further guidance from Alan before =
proceeding with any updates for the "[ISAAC_]" reference.
>>>>=20
>>>> This should be "[ISAAC-Plus]" for clarity.
>>>>=20
>>>>> [rfced] After further review, we have decided to use "sequence =
number" and "secret key" in this document for consistency across RFC =
5880 and RFC-to-be 9985 (this excludes instances where the terms are =
paired with another noun, e.g., "Sequence Number field"). Please let us =
know any objections.
>>>>=20
>>>> This is fine.
>>>>=20
>>>>>>> Meticulous Keyed ISAAC
>>>>>>> Meticulous keyed ISAAC
>>>>>> The forms I see these in are paired to the sha-1 and md-5 forms =
of the mode.  We are looking for consistency for those pairings.  The =
capitalization for keyed can match the other instances.
>>>>>>> Meticulous Keyed ISAAC Keyed=20
>>>>>>> [Note: Is the second "Keyed" correct here? There are 4 =
instances.]
>>>>>> These instances look like a search and replace issue.  I believe =
the intention here is that each of these instances is intended to be =
"Meticulous Keyed ISAAC, ISAAC format".  This should be audited by Alan.
>>>>>=20
>>>>> [rfced] We will wait for further guidance from Alan before making =
the updates as described above for "Meticulous Keyed ISAAC Keyed". We =
have updated all other terms for consistency.
>>>>=20
>>>> Yes.  The 4 instances can be changed to "Meticulous Keyed ISAAC, =
ISAAC format".
>>>>=20
>>>> Alan DeKok.
>>>>=20
>>>=20
>>=20
>>=20
>> Mahesh Jethanandani
>> mjethanandani@gmail.com
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>=20


Mahesh Jethanandani
mjethanandani@gmail.com


--Apple-Mail=_F3920785-2EDD-46FF-B9B7-2436B50E7C1D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" =
content=3D"text/html; charset=3Dutf-8"></head><body =
style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;">Hi Madison,<div><br></div><div>Sonal did =
respond with an approval&nbsp;and asked for her contact information to =
be updated. Did you see =
it?</div><div><br></div><div>Thanks</div><div><br></div><div>p.s. Let me =
ping Ashesh.<br id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote =
type=3D"cite"><div>On Jun 4, 2026, at 9:19=E2=80=AFAM, Madison Church =
&lt;mchurch@staff.rfc-editor.org&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div><div>Hi Mahesh,<br><br>Thank =
you for your reply! We have noted your approval here: =
https://queue.rfc-editor.org/final-review/rfc9986/.<br><br>Once we =
receive approvals from Ashesh and Sonal, we will move this document =
forward in the publication process.<br><br>Thank you!<br><br>Madison =
Church<br>RFC Production Center<br><br><blockquote type=3D"cite">On Jun =
3, 2026, at 7:07=E2=80=AFPM, Mahesh Jethanandani =
&lt;mjethanandani@gmail.com&gt; wrote:<br><br>Hi Madison,<br><br>I am =
not sure if I sent my approval already, but here it is, in case I missed =
sending it<br><br>Thanks.<br><br><blockquote type=3D"cite">On Jun 2, =
2026, at 12:00=E2=80=AFPM, Madison Church =
&lt;mchurch@staff.rfc-editor.org&gt; wrote:<br><br>Alan, =
*Ketan,<br><br>*Ketan - We have noted your approval for moving RFC 8341 =
to the Normative References section.<br><br>Alan - Thank you for your =
reply! We have updated the document per your response and noted your =
approval on the Final Review (formerly AUTH48) status page; see =
https://queue.rfc-editor.org/final-review/rfc9986/.<br><br>The files =
have been posted here (please =
refresh):<br>https://www.rfc-editor.org/authors/rfc9986.txt<br>https://www=
.rfc-editor.org/authors/rfc9986.pdf<br>https://www.rfc-editor.org/authors/=
rfc9986.html<br>https://www.rfc-editor.org/authors/rfc9986.xml<br><br>Upda=
ted diff files have been posted =
here:<br>https://www.rfc-editor.org/authors/rfc9986-diff.html<br>https://w=
ww.rfc-editor.org/authors/rfc9986-rfcdiff.html (side by =
side)<br>https://www.rfc-editor.org/authors/rfc9986-auth48diff.html<br>htt=
ps://www.rfc-editor.org/authors/rfc9986-auth48rfcdiff.html (side by =
side)<br><br>Once we receive approval from Mahesh, Sonal, and Ashesh, we =
will move this document forward in the publication process.<br><br>Thank =
you!<br><br>Madison Church<br>RFC Production Center<br><br><blockquote =
type=3D"cite">On Jun 2, 2026, at 11:27=E2=80=AFAM, Alan DeKok =
&lt;aland@freeradius.org&gt; wrote:<br><br>On May 29, 2026, at =
4:47=E2=80=AFPM, Madison Church &lt;mchurch@staff.rfc-editor.org&gt; =
wrote:<br><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">17) &lt;!-- [rfced] For the "[ISAAC_]" reference, we =
recommend changing the citation<br>tag since "[ISAAC]" and "[ISAAC_]" =
may be easily confused. May we update<br>"[ISAAC_]" to "[ISAAC+]" or =
"[ISAAC-Plus]"?<br>--&gt;<br></blockquote>This question to be answered =
by Alan and the SEC-ADs.<br></blockquote><br>[rfced] We will wait for =
further guidance from Alan before proceeding with any updates for the =
"[ISAAC_]" reference.<br></blockquote><br>This should be "[ISAAC-Plus]" =
for clarity.<br><br><blockquote type=3D"cite">[rfced] After further =
review, we have decided to use "sequence number" and "secret key" in =
this document for consistency across RFC 5880 and RFC-to-be 9985 (this =
excludes instances where the terms are paired with another noun, e.g., =
"Sequence Number field"). Please let us know any =
objections.<br></blockquote><br>This is fine.<br><br><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Meticulous Keyed ISAAC<br>Meticulous keyed =
ISAAC<br></blockquote>The forms I see these in are paired to the sha-1 =
and md-5 forms of the mode. &nbsp;We are looking for consistency for =
those pairings. &nbsp;The capitalization for keyed can match the other =
instances.<br><blockquote type=3D"cite">Meticulous Keyed ISAAC Keyed =
<br>[Note: Is the second "Keyed" correct here? There are 4 =
instances.]<br></blockquote>These instances look like a search and =
replace issue. &nbsp;I believe the intention here is that each of these =
instances is intended to be "Meticulous Keyed ISAAC, ISAAC format". =
&nbsp;This should be audited by Alan.<br></blockquote><br>[rfced] We =
will wait for further guidance from Alan before making the updates as =
described above for "Meticulous Keyed ISAAC Keyed". We have updated all =
other terms for consistency.<br></blockquote><br>Yes. &nbsp;The 4 =
instances can be changed to "Meticulous Keyed ISAAC, ISAAC =
format".<br><br>Alan =
DeKok.<br><br></blockquote><br></blockquote><br><br>Mahesh =
Jethanandani<br>mjethanandani@gmail.com<br><br><br><br><br><br><br></block=
quote><br></div></div></blockquote></div><br><div>
<div dir=3D"auto" style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none; caret-color: =
rgb(0, 0, 0); color: rgb(0, 0, 0); word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><div =
dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div style=3D"color: rgb(0, 0, 0); letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div><br class=3D"Apple-interchange-newline">Mahesh =
Jethanandani</div><div>mjethanandani@gmail.com</div><div><br></div></div><=
br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline" style=3D"caret-color: rgb(0, 0, 0); =
color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail=_F3920785-2EDD-46FF-B9B7-2436B50E7C1D--