netdev - Brand-new networking Internet Protocol "Five Fields"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAOJ6w=G+27bEVjhUSSm7V17Bx05rmqJ_SPvnOJ+yAAo1d923uQ@mail.gmail.com>
Date:	Mon, 7 Dec 2015 12:59:18 +0200
From:	Alexey Eromenko <al4321@...il.com>
To:	netdev@...r.kernel.org
Subject: Brand-new networking Internet Protocol "Five Fields"

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 IPv6.

I did it, because I don't like to work with something long like this:
   2001:db8:2e1:1a73:149f: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...

https://www.dropbox.com/s/zcinwk05h2zkflw/IP-FF-2015-12-07.zip?dl=0

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

Best wishes,
-- 
-Alexey Eromenko "Technologov"
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html