Introducing : Brand-new Internet Protocol "Five Fields"

[Technologov]

Hi all,

I have created a new Internet Protocol "Five Fields".

Why ?
Because IPv6 is hard to use, and I wanted to keep look & feel similar to IPv4. Problem with IPv6, is that those addresses are very hard for humans to remember, compare and visualize topologies in human brain.
IPv4 has great look & feel, but it is exhausted. So I wrote a new replacement for IP.

I did it, because I don't like to work with something long like this:
2001:db8:2e1149f:88ff:fe81:6116

And it would be better, if we work with simpler addressing:
192.168.510.971.11

10.0.0.0.1

382.201.769.25.133

Draft spec. available.

"Five Fields" offers 0...999 in each field, in dotted decimal
notation, and includes unique features not found *anywhere else*.

- x230,000 times larger address space than IPv4 (should be enough for several hundred years, including IoT)
-Mobile TCP, allows moving Mobile Nodes between subnets, without losing connectivity. A replacement for Mobile IP. An order of magnitude simpler, and requires no access to routers and configuration-free.
-IP-VRF header extension, allows doing VRF-VPN without MPLS (and without dot1q VLANs)
-Super-lightweight, and should be faster than IPv4 or IPv6 by 1%-2%. Small overhead.
-UDP/IP overhead is 28 bytes; UDP/IPv6 overhead is 48 bytes, but UDP/IP-FF overhead is just 26 bytes ! Even shorter than the original, yay !
-Simpler to implement than IPv4/v6, because no fragmentation. MTU path discovery is the way to go.
-No broadcasts.
-No IP header checksums (done at layer 4)
-No autoconfiguration/SLAAC (this belongs to DHCP territory)
-No IGMP required (it is optional now for Multicasts)
-No Layer2 resolution. ARP-free protocol.

I believe, that it is superior to both IPv4 and IPv6, simpler than both, and intended as a replacement for both. Substantial improvement on both.

This draft specification describes various parts, the protocol itself, addressing scheme, Address Resolution Algorithm (without ARP), DNS extensions, Mobile TCP, and more...

Draft spec download here:
https://www.dropbox.com/s/tnwtsjwav8yxc ... 9.zip?dl=0

IP-FF is about:
o Short, human-readable addresses
o Modularization of some perceived IPv6 bloat (NDP/IGMP/MLD/IPsec/SLAAC/Flow/...)
o New features: IP-VRF and Mobile TCP, TCP Anycast.
o Optimization: UDP/IPFF combo is just 26 bytes, vs UDP/IPv6 48-bytes. Almost 50% cut in overhead. And no ARP.

With more time and polish, I plan to send it to IETF.

Best wishes,
--
-Alexey Eromenko "Technologov"

[dasein]

Moved to Offtopic since it has nothing to do with Debian.

[edbarx]

"Five Fields" offers 0...999 in each field, in dotted decimal

Internally computer do not use decimal but binary. Ten bits of information are required for a range of 0..999 wasting 25 binary permutations. Your idea is nothing new, as it should be obvious that five fields provide a wider coverage compared with four fields.

Essentially, you have 50 bits of information arranged into 5 fields of ten bits each. Since bytes are 8 bits long, your arrangement may need more CPU cycles to process.

[Technologov]

50-bits can be put into 64-bit integer, so there is only 1 extra CPU operation - the bitmask (bit extract). It is way faster than trying to process 128-bits on 64-bit CPU (IPv6) or doing checksums + fragmentation on every hop (IPv4).

Considering the other optimizations (such as no ARP), in reality IPFF should be faster than IPv4 or IPv6.

[edbarx]

Therefore, arrange those 64 bits into 8 bytes and you will lose nothing. Programming languages provide structure overlapping known as unions which means you will be able to access the 8 bytes individually and as a 64 bit integer without additional complexity.