Making Use of 240/4 NetBlock Re: 202203162242.AYC

Thu Mar 17 02:59:43 UTC 2022

Hi, Fred:

1)    " ... you will need to replace the existing DNS and DHCP 
systems...  ":    I am glad that you have touched the next level of 
considerations. Operating an RAN with one 240/4 netblock, there will be 
more than enough IP addresses to assign to all client premises. So, the 
EzIP deployment will operate with static IP address disciplines, 
negating the fundamental reasons to have DNS and DHCP. That is, 
transition to running the electronic equivalent of telephony White and 
Yellow Pages would be what EzIP deployment should rely upon.

2)    " ... hear the relevant organizations saying that it changes their 
networking model, ... similar to what has happened with the IPv6 
deployment.  ":    Do they recognize that implementing EzIP address plan 
on CG-NAT changes no network model? So, the perturbation is far less 
than deploying IPv6.

Regards,

Abe (2022-03-16 22:59)

On 2022-03-16 12:03, Fred Baker wrote:
>> On Mar 16, 2022, at 7:50 AM, Abraham Y. Chen<aychen at avinta.com>  wrote:
>>
>> 2)    Re: Ur. Pt. 2) " So replace every CPE device, including ...   ":     It is evident that  you even did not glance at the EzIP Draft Abstract before commenting, but just relying on your recollection of the past 240/4 efforts.
> I did read it. Correct my understanding.
>
> Your proposal is to replace the IP addressing model and IP (yes, you're using options, but the architecture changed). Do so do, you will need to replace the existing DNS and DHCP systems with a PABX-like model - you need to find a way to let systems address each other. It also replaces firewalls with a model that prevents communication with devices that don't know the PABX port numbers.
>
> Frankly, I can already hear the relevant organizations saying that it changes their networking model, and it starts a process similar to what has happened with the IPv6 deployment.

-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20220316/a3d850ee/attachment.html>