[lacnog] Making Use of 240/4 NetBlock Re: 202203131603.AYC

Abraham Y. Chen aychen en avinta.com
Dom Mar 13 18:33:04 -03 2022

Hi, Fernando:

1)    I am glad that you like the Unicast Extension Project. Our effort 
is along the same line of thinking, but one step further toward the 
practice by presenting a specific application example.

2)    EzIP starts from utilizing the 240/4 netblock as the fourth 
reusable private network address pool. As such, each RAN (Regional Area 
Network) implementing the EzIP scheme will be entirely isolated from the 
existing Internet proper by an RG (Residential Gateway) via the 
demarcation concept. That is, an RAN is free of the influence from the 
Internet, if so chosen, as long as the IP packets between the two 
conform to applicable internet protocols. In other words, an RAN is an 
overlay network tethered from the existing Internet core via one IPv4 
public address as the umbilical cord. An RAN is able to provide all 
desired contemporary Internet services utilizing desired technologies,  
while avoiding the baggage in the existing Internet operation.

3)    On the other hand, since the 240/4 address pool is much bigger 
than the conventional three private netblocks combined, an RAN can serve 
IoTs of a population up to around 39M, even before making use of any of 
the conventional three netblocks. In terms of geographical coverage, 
this turns out to be able to cover the largest city of the world, the 
Tokyo Metro, which is bigger than any of the 75% smaller countries 
worldwide. Since the current Internet equipment either ignores or drops 
240/4 addressed IP packets, an RAN can be deployed with its own routers 
(called SPR - Semi-Public Router) and then grows on its own pace 
anywhere, without the fear of the interference with the existing 
Internet in either direction. Of course, any existing equipment wishing 
to participate in the EzIP scheme (by disabling the program code that 
has been disabling the use of the 240/4 netblock) will speed up the 
global deployment process.

4)    A quick rule-of-the-thumb calculation shows that fewer than one 
thousand IPv4 public addresses will be more than suffice for this 
addressing system. (For the reference, each of the two most populous 
countries, China 1.5B and India 1.4B, only needs at most six IPv4 public 
addresses for implementing this scheme.) This frees up significant 
number of IPv4 addresses.

5)    In summary, EzIP deployment can not only explicitly identify every 
premises (or, even individuals) on the internet for providing improved 
operations, but also free up IPv4  addresses, leading to other potential 
benefits as mentioned by related EzIP documents.

I look forward to your thoughts.


Abe (2022-03-13 17:32 EDT)

> ----------------------------------------------------------------------
> Resumen de LACNOG, Vol 171, Envío 9
> Message: 1
> Date: Sat, 12 Mar 2022 05:32:28 -0300
> From: Fernando Frediani<fhfrediani en gmail.com>
> To:lacnog en lacnic.net
> Subject: Re: [lacnog] Making Use of 240/4 NetBlock Re:
> 	202203112350.AYC
> Message-ID:<f41732ad-d63e-d4b5-612b-1e8f0aa8bf54 en gmail.com>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
> Hello
> I do not and never accepted the easy justification that working towards
> making any usage of a huge amount of wasted IPv4 addresses due to an
> historical mistake from some network vendor is something that would
> compete with IPv6 deployment. Both things can work in parallel without
> prejudice to each other.
> However I think the best proposal I have seen was the one put but Seth
> and his partners
> (https://github.com/dtaht/unicast-extensions/blob/master/rfcs/draft-gilmore-taht-v4uniext.txt)
> and even though these addresses may not be used globally they will have
> usage that can help making this transition smoother as it is not
> reasonable to think we will turn the key to IPv6 in the next few years
> for more effort and dedication we put into it.
> Fernando
> -------------------------------------------------------------------
> ******************************************

This email has been checked for viruses by Avast antivirus software.
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <https://mail.lacnic.net/pipermail/lacnog/attachments/20220313/ce856b79/attachment.htm>

Más información sobre la lista de distribución LACNOG