nanog mailing list archives
202401101433.AYC Re: EzIP Re: 202401100645.AYC Re: IPv4 address block
From: "Abraham Y. Chen" <aychen () avinta com>
Date: Wed, 10 Jan 2024 22:11:01 -0500
Hi, Enno: 0) Thanks for your comments referring to historical efforts.1) However, the "IPv4 Unicast Extension Project" that your paper cited does not make any specific recommendation about how to utilize the 240/4 netblock uniformly across the entire Internet. Our proposal, EzIP outlines a scheme that makes a clear use of the 240/4 by the general public, basically discouraging disparate private usages. We were very much lost with what has been going on with the 240/4 netblock, because there was no information about who were using it for what. The RIPE-Lab report clarified the fact that it has been fragmented due to unannounced activities by multi-national conglomerates and likely nerds, while under the cover of "Reserved for Future Use".
2) " As you state yourself this could be considered "unorthodox, if not controversial". ... usually means 'breaks something' ":
I am afraid that you read into my diplomatic expression too far.A. The first step of the EzIP proposal is to enhance the CG-NAT by providing it with a much larger netblock, as I presume that Karim is looking for. Such process (disabling the program code that has been disabling the use of 240/4) does not need any running code to prove it. To be blunt, anyone who claims that this will be a real task only shows that he does not know his own code.
B. The second EzIP step is to utilize RFC791 for setting up end-to-end links which the Internet has not been able to deliver. This is because the current predominant CG-NAT based CDN business is a master-slave model which does not support it. However, this capability is like international postal or telephony services that are not daily needs for everyone. So, it should be treated as a premium service that can be built up with time base on demand.
Let's not mixing B. with A. as a one-shot job in this discussion. Regards, Abe (2024-01-10 22:10 EST) On 2024-01-10 07:57, Enno Rey via NANOG wrote:
On Wed, Jan 10, 2024 at 07:35:01AM -0500, Abraham Y. Chen wrote:Hi, Karim: 1)?????? If you have control of your own equipment (I presume that your business includes IAP - Internet Access Provider, since you are asking to buy IPv4 blocks.), you can get a large block of reserved IPv4 address _/*for free*/_ by _/*disabling*/_ the program codes in your current facility that has been */_disabling_/* the use of 240/4 netblock.As you state yourself this could be considered "unorthodox, if not controversial". Alas in network operations 'unorthodox' usually means 'breaks something'. Which is exactly why you may avoid this, see also: https://theinternetprotocolblog.wordpress.com/2019/10/06/some-notes-on-ipv4-address-space/ cheers Enno Pleasehave a look at the below whitepaper. Utilized according to the outlined disciplines, this is a practically unlimited resources. It has been known that multi-national conglomerates have been using it without announcement. So, you can do so stealthily according to the proposed mechanism which establishes uniform practices, just as well. https://www.avinta.com/phoenix-1/home/RevampTheInternet.pdf 2)?????? Being an unorthodox solution, if not controversial, please follow up with me offline. Unless, other NANOGers express their interests. Regards, Abe (2024-01-10 07:34 EST) On 2024-01-07 22:46, KARIM MEKKAOUI wrote:Hi Nanog Community Any idea please on the best way to buy IPv4 blocs and what is the price? Thank you KARIM-- This email has been checked for viruses by Avast antivirus software. www.avast.com
Current thread:
- Re: IPv4 address block, (continued)
- Re: IPv4 address block John Curran (Jan 07)
- Re: IPv4 address block Eric Kuhnke (Jan 07)
- Re: IPv4 address block John Curran (Jan 07)
- RE: IPv4 address block Tony Wicks (Jan 08)
- Re: IPv4 address block Ben Cox via NANOG (Jan 08)
- {Disarmed} RE: IPv4 address block Tony Wicks (Jan 08)
- Re: {Disarmed} RE: IPv4 address block Ben Cox via NANOG (Jan 08)
- {Disarmed} RE: {Disarmed} Re: {Disarmed} RE: IPv4 address block Tony Wicks (Jan 08)
- Re: IPv4 address block Eric Kuhnke (Jan 07)
- Re: IPv4 address block John Curran (Jan 07)
- Re: 202401100645.AYC Re: IPv4 address block Enno Rey via NANOG (Jan 10)
- 202401101433.AYC Re: EzIP Re: 202401100645.AYC Re: IPv4 address block Abraham Y. Chen (Jan 10)
- Re: 202401101433.AYC Re: EzIP Re: 202401100645.AYC Re: IPv4 address block Forrest Christian (List Account) (Jan 10)
- Streamline the CG-NAT Re: 202401101433.AYC Re: EzIP Re: 202401100645.AYC Re: IPv4 address block Abraham Y. Chen (Jan 11)
- Re: Streamline the CG-NAT Re: 202401101433.AYC Re: EzIP Re: 202401100645.AYC Re: IPv4 address block Christopher Hawker (Jan 11)
- Re: Streamline the CG-NAT Re: 202401101433.AYC Re: EzIP Re: 202401100645.AYC Re: IPv4 address block Abraham Y. Chen (Jan 12)
- Re: Streamline the CG-NAT Re: 202401101433.AYC Re: EzIP Re: 202401100645.AYC Re: IPv4 address block Christopher Hawker (Jan 12)
- Re: Streamline the CG-NAT Re: 202401101433.AYC Re: EzIP Re: 202401100645.AYC Re: IPv4 address block Abraham Y. Chen (Jan 13)