Eric,

I'll try not to cry too much 😉

I don't know what happens to the mailing list. I assume that there is an IETF 
policy regarding mailing list retention.

And, by the way, I still have a flip phone somewhere in my house.

                                                            Ron



Juniper Business Use Only

________________________________
From: Eric Vyncke (evyncke) <[email protected]>
Sent: Tuesday, July 30, 2024 10:31 AM
To: Jen Linkova <[email protected]>; opsec WG <[email protected]>
Cc: OpSec Chairs <[email protected]>; Warren Kumari <[email protected]>
Subject: Re: [OPSEC]Sunsetting the OPSec WG: It's Been a Secure Ride!


[External Email. Be cautious of content]


Also a tear or two in my eyes when reading this...



Thank you to Jen, Ron, and Warren



-éric



PS: what is the status of the mailing list ? Will it be kept open ?



From: Jen Linkova <[email protected]>
Date: Friday, 26 July 2024 at 19:41
To: opsec WG <[email protected]>
Cc: OpSec Chairs <[email protected]>, Warren Kumari <[email protected]>
Subject: [OPSEC]Sunsetting the OPSec WG: It's Been a Secure Ride!

Hello,

With security woven into every modern IETF protocol (like a comfy
security blanket), this group has been unsurprisingly quiet lately.

So, with a touch of nostalgia (and maybe a tear or two), the chairs
and the responible AD have decided it's time to say farewell to the
OpSec WG.

The mail archive reveals the very first email was sent to this list on
December 19th, 2007—back when flip phones were still cool!

It's been a fantastic 16 years. The group has published 18 RFCs,
making the internet (and, most importantly, IPv6) a safer and
all-around more awesome place.

A massive thank you to everyone for their contributions and hard work!

---
Ron, Jen and Warren

_______________________________________________
OPSEC mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
OPSEC mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to