[ippm] Re: [iesg] Deb Cooley's Discuss on status-chang e-ippm-active-passive-methods-03: (with DISCUSS)

--===============7948544797467640888==
Content-Type: multipart/alternative; boundary="000000000000f5667d0652569f64"

--000000000000f5667d0652569f64
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Let me try this again, hopefully on the correct mailing list chain...

Sure, there are RFCs which do stand the test of time.  These are uncommon.

The issues that Ketan raises are good examples of where a refresh makes
sense.  Is there a reason to not do the refresh?  Is there some sort of
urgency?

Deb

On Thu, May 21, 2026 at 9:49=E2=80=AFAM <[email protected]> wrot=
e:

> Hi Deb,
>
> Please see inline.
>
> Cheers,
> Med
>
> > -----Message d'origine-----
> > De : Deb Cooley via Datatracker <[email protected]>
> > Envoy=C3=A9 : jeudi 21 mai 2026 15:31
> > =C3=80 : The IESG <[email protected]>
> > Cc : [email protected]; [email protected]
> > Objet : [iesg] Deb Cooley's Discuss on status-change-ippm-active-
> > passive-methods-03: (with DISCUSS)
> >
> >
> > Deb Cooley has entered the following ballot position for
> > status-change-ippm-active-passive-methods-03: Discuss
> >
> > When responding, please keep the subject line intact and reply to
> > all email addresses included in the To and CC lines. (Feel free to
> > cut this introductory paragraph, however.)
> >
> >
> > ------------------------------------------------------------------
> > DISCUSS:
> > ------------------------------------------------------------------
> >
> > I struggled with my ballot position for this.
> >
> > I find it hard to believe that a 10+ year old Informational RFC
> > doesn't need some updating.
> >
>
> [Med] The publication date is not a criteria. If this is assuring, please
> see for example
> https://datatracker.ietf.org/doc/status-change-rfc1984-to-best-current-pr=
actice/
> (publication date 1996 and status change in 2015): almost two decades!
>
>
> _________________________________________________________________________=
___________________________________
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
> recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme o=
u
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have bee=
n
> modified, changed or falsified.
> Thank you.
>
>

--000000000000f5667d0652569f64
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Let me try this again, hopefully on the correct maili=
ng list chain...=C2=A0=C2=A0</div><div><br></div><div>Sure, there are RFCs =
which do stand the test of time.=C2=A0 These are uncommon.</div><div><br></=
div><div>The issues that Ketan raises are good examples of where a refresh =
makes sense.=C2=A0 Is there a reason to not do the refresh?=C2=A0 Is there =
some sort of urgency?</div><div><br></div><div>Deb</div></div><br><div clas=
s=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_att=
r">On Thu, May 21, 2026 at 9:49=E2=80=AFAM &lt;<a href=3D"mailto:mohamed.bo=
[email protected]">[email protected]</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex">Hi Deb, <br>
<br>
Please see inline.<br>
<br>
Cheers,<br>
Med<br>
<br>
&gt; -----Message d&#39;origine-----<br>
&gt; De=C2=A0: Deb Cooley via Datatracker &lt;<a href=3D"mailto:noreply@iet=
f.org" target=3D"_blank">[email protected]</a>&gt;<br>
&gt; Envoy=C3=A9=C2=A0: jeudi 21 mai 2026 15:31<br>
&gt; =C3=80=C2=A0: The IESG &lt;<a href=3D"mailto:[email protected]" target=3D"=
_blank">[email protected]</a>&gt;<br>
&gt; Cc=C2=A0: <a href=3D"mailto:[email protected]" target=3D"_blank">bmwg@ietf=
.org</a>; <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]<=
/a><br>
&gt; Objet=C2=A0: [iesg] Deb Cooley&#39;s Discuss on status-change-ippm-act=
ive-<br>
&gt; passive-methods-03: (with DISCUSS)<br>
&gt; <br>
&gt; <br>
&gt; Deb Cooley has entered the following ballot position for<br>
&gt; status-change-ippm-active-passive-methods-03: Discuss<br>
&gt; <br>
&gt; When responding, please keep the subject line intact and reply to<br>
&gt; all email addresses included in the To and CC lines. (Feel free to<br>
&gt; cut this introductory paragraph, however.)<br>
&gt; <br>
&gt; <br>
&gt; ------------------------------------------------------------------<br>
&gt; DISCUSS:<br>
&gt; ------------------------------------------------------------------<br>
&gt; <br>
&gt; I struggled with my ballot position for this.<br>
&gt; <br>
&gt; I find it hard to believe that a 10+ year old Informational RFC<br>
&gt; doesn&#39;t need some updating.<br>
&gt; <br>
<br>
[Med] The publication date is not a criteria. If this is assuring, please s=
ee for example <a href=3D"https://datatracker.ietf.org/doc/status-change-rf=
c1984-to-best-current-practice/" rel=3D"noreferrer" target=3D"_blank">https=
://datatracker.ietf.org/doc/status-change-rfc1984-to-best-current-practice/=
</a> (publication date 1996 and status change in 2015): almost two decades!=
<br>
<br>
___________________________________________________________________________=
_________________________________<br>
Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc<br>
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler<br>
a l&#39;expediteur et le detruire ainsi que les pieces jointes. Les message=
s electroniques etant susceptibles d&#39;alteration,<br>
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.<br>
<br>
This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;<br>
they should not be distributed, used or copied without authorisation.<br>
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.<br>
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.<br>
Thank you.<br>
<br>
</blockquote></div>

--000000000000f5667d0652569f64--


--===============7948544797467640888==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaXBwbSBtYWls
aW5nIGxpc3QgLS0gaXBwbUBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv
IGlwcG0tbGVhdmVAaWV0Zi5vcmcK

--===============7948544797467640888==--