nanog mailing list archives
Re: DoD IP Space
From: William Herrin <bill () herrin us>
Date: Mon, 15 Feb 2021 08:47:57 -0800
On Mon, Feb 15, 2021 at 7:49 AM Valdis Klētnieks <valdis.kletnieks () vt edu> wrote:
On Sun, 14 Feb 2021 22:25:56 -0800, William Herrin said:This particular problem could be quickly resolved if the OSes still getting updates were updated to default name resolution to prioritize the IPv4 addresses instead. That would allow broken IPv6 configurations to exist without breaking the user's entire Internet experience. Which would allow them to leave it turned on so that it resumes working when the error is eventually found and fixed.Oh, come on Bill. This ain't your first rodeo. You know damned well that if we do that, the errors are in fact *not* eventually found and fixed.
I don't know that and neither do you. That remains an untested theory. What I do know, with the perfection of 20/20 hindsight, is that v6-first has impeded deployment for two decades by routinely giving folks a reason to turn IPv6 back off. Hard headed. Regards, Bill Herrin -- William Herrin bill () herrin us https://bill.herrin.us/
Current thread:
- Re: DoD IP Space, (continued)
- Re: DoD IP Space Sabri Berisha (Feb 14)
- Re: DoD IP Space Mark Tinka (Feb 14)
- Re: DoD IP Space William Herrin (Feb 14)
- Re: DoD IP Space Mark Tinka (Feb 14)
- Re: DoD IP Space Mark Andrews (Feb 14)
- Re: DoD IP Space William Herrin (Feb 15)
- Re: DoD IP Space John Curran (Feb 15)
- Re: DoD IP Space Geoff Mulligan (Feb 15)
- Re: DoD IP Space Randy Bush (Feb 15)
- Re: DoD IP Space Valdis Klētnieks (Feb 15)
- Re: DoD IP Space William Herrin (Feb 15)
- Re: DoD IP Space nanog (Feb 15)
- Re: DoD IP Space Mark Tinka (Feb 15)
- Re: DoD IP Space Jay Hennigan (Feb 26)
- Re: DoD IP Space Mel Beckman (Feb 26)
- Re: DoD IP Space Daniel Seagraves (Feb 27)
- Re: DoD IP Space Mark Tinka (Feb 14)