nanog mailing list archives
Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC
From: Joe Maimon <jmaimon () jmaimon com>
Date: Tue, 22 Nov 2022 02:09:08 -0500
David Conrad wrote:
How trivial would the change be in a product by a company that no longer exists or a product line that is no longer supported? Will Microsoft update all previous versions of Windows? Will the myriad of deployed embedded systems sitting forgotten in closets be updated? And if you’re going to the trouble to update those systems (in most cases, by simply throwing them away), why not upgrade to IPv6+IPv4aaS?Especially as we have examples of what that type of effort might look like.Again, the issue isn’t fixing a bit of code in a known source tree. It is getting all the instantiations of that bit of code implemented, tested, and deployed across all the myriad supported and unsupported systems (both operational and management) that support 5 billion+ Internet users globally in a timeframe and for a cost that makes business sense. Regards, -drc
Lets agree to stop conflating the issue of products under active support and refresh cycles with the issue of those that are obsolete and only subject to attrition.
Two different problems areas entirely.The former, yes it is trivial. An update in standards could yield rapid results here.
The latter takes time. An update in standards could take years to bear enough fruit. All the more reason it should have happened then, all the more reason to let it happen now.
Joe
Current thread:
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC, (continued)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC Abraham Y. Chen (Nov 21)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC bzs (Nov 21)
- Fwd: Alternative Re: ipv4/25s and above Re: 202211201009.AYC Rubens Kuhl (Nov 21)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC Owen DeLong via NANOG (Nov 21)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC Fred Baker (Nov 26)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC David Conrad (Nov 21)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC Joe Maimon (Nov 21)
- Re: Alternative Re: ipv4/25s and above Jay Hennigan (Nov 21)
- Re: Alternative Re: ipv4/25s and above Joe Maimon (Nov 21)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC David Conrad (Nov 21)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC Joe Maimon (Nov 21)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC John Curran (Nov 22)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC John Curran (Nov 22)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC Joe Maimon (Nov 22)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC John Curran (Nov 22)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC Tom Beecher (Nov 22)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC John Curran (Nov 22)
- Re: Alternative Re: ipv4/25s and above Re: 202211201009.AYC John Gilmore (Nov 27)
- Re: Alternative Re: ipv4/25s and above Re: 202211232221.AYC Abraham Y. Chen (Nov 24)
- RE: Alternative Re: ipv4/25s and above Re: 202211232221.AYC Vasilenko Eduard via NANOG (Nov 24)
- Re: Alternative Re: ipv4/25s and above Re: 202211232221.AYC Abraham Y. Chen (Nov 24)