This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] Have we failed as IPv6 Working Group?
- Previous message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
- Next message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Olivier MJ Crépin-Leblond
ocl at gih.com
Sun Oct 6 17:33:21 CEST 2019
Dear Michel, On 04/10/2019 17:16, Michel Py wrote: > 3 months ago, I turned DECNET off on my network. It was actually not even an IT/network decision; customer decided they were done with a product, and we de-commissioned the tools with DECNET. Business decision. We run OS/2 Warp, MS-DOS, Windows 95, HPUX, Solaris, Windows 2000, and I probably forget some. I don't mean to be criticising in any way, but running services on obsolete operating systems is a risk in itself, if the computer is connected to the Internet. For example, Windows 2000 end of support was as far back as July 13, 2010. https://blogs.technet.microsoft.com/education/2009/11/10/windows-2000-end-of-life/ That means no security updates. With today's Internet being nothing like the Internet back in 2000, is this really reasonable? Unless, of course, the hardware is behind some modern firewalls. Everything has a sell by date. All hardware becomes obsolete too. Kindest regards, Olivier -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ipv6-wg/attachments/20191006/1f621692/attachment.html>
- Previous message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
- Next message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]