nanog mailing list archives
Re: IPv4 sunset date set for 2019-12-31
From: Barry Shein <bzs () world std com>
Date: Thu, 21 Oct 2010 21:51:41 -0400
On October 21, 2010 at 20:13 jbates () brightok net (Jack Bates) wrote:
On 10/21/2010 7:53 PM, Niels Bakker wrote:* bzs () world std com (Barry Shein) [Thu 21 Oct 2010, 22:59 CEST]:And, of course, the RIRs could just cancel all the IPv4 route announcements, whatever they do if someone doesn't pay or whatever.I think you're mistaking the default-free zone for Usenet. The DFZ doesn't have 'cmsg cancel' messages.The "whatever they do if someone doesn't pay" is a nightmare. I suspect such a recourse wouldn't work for stopping IPv4.
Well, along with no more IPv4 DNS and it'd be pretty effective (I suggested both for a reason.) The idea isn't to make it impossible to run an ipv4 connection, tho at some point it'd have to be encapsulated in IPv6 to get routed across the public infrastructure, the idea is to declare it dead and stop expending (shared) resources on it. I guess I just answered my own question: "Why bother?" So we can stop expending resources on IPv4 like managing address space allocations, route announcements, firefighting, DNS, all the wonky this inside that encapsulation schemes, etc. I'd let folks like the RIRs and DNS root managers speak to how much of a win that would be tho it would affect others, particularly the firefighting part. If IPv4 is maintained forever then one presumes it works reasonably well forever and that's kinda why everyone here is here, no? Anyhow, it might be an interesting topic to discuss in the appropriate venues, IETF, "What is the cost of maintaining IPv4 forever?" but it's getting a little ahead of ourselves in terms of any pressing need. So...it wasn't a dumb question to raise, just perhaps a bit premature. -- -Barry Shein The World | bzs () TheWorld com | http://www.TheWorld.com Purveyors to the Trade | Voice: 800-THE-WRLD | Dial-Up: US, PR, Canada Software Tool & Die | Public Access Internet | SINCE 1989 *oo*
Current thread:
- IPv4 sunset date set for 2019-12-31, (continued)
- IPv4 sunset date set for 2019-12-31 Jared Mauch (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Dave CROCKER (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Majdi S. Abbas (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Claudio Jeker (Oct 21)
- RE: IPv4 sunset date set for 2019-12-31 Deepak Jain (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Michael Dillon (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Christopher Morrow (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Barry Shein (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Niels Bakker (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Jack Bates (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Barry Shein (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Jared Mauch (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Jack Bates (Oct 21)
- cost of IPv4 bmanning (Oct 21)
- Re: cost of IPv4 Jorge Amodio (Oct 22)
- Re: IPv4 sunset date set for 2019-12-31 Mark Smith (Oct 22)
- Re: IPv4 sunset date set for 2019-12-31 Barry Shein (Oct 21)
- Re: IPv4 sunset date set for 2019-12-31 Dave CROCKER (Oct 22)
- Re: IPv4 sunset date set for 2019-12-31 Joe Maimon (Oct 22)
- Re: IPv4 sunset date set for 2019-12-31 Barry Shein (Oct 22)
- Re: IPv4 sunset date set for 2019-12-31 Michael Dillon (Oct 21)