netdev - Re: [ANNOUNCE] Enhanced IP

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>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 29 Mar 2014 12:10:18 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Sam Patton <sam@...ancedip.org>
Cc:	netdev@...r.kernel.org
Subject: Re: [ANNOUNCE] Enhanced IP

On Fri, Mar 28, 2014 at 09:41:59PM -0400, Sam Patton wrote:
> The February edition of IEEE Computer has a paper on Enhanced IP, an
> alternative to Ipv6.  Enhanced IP developers have released a version
> of the software in the form of virtual machines, which are designed to
> be used by other kernel developers. At this point, the project is
> interested in attracting kernel developers who want to write network
> code.  The primary website for Enhanced IP is www.enhancedip,org.

The name 'EnhancedIP' may make it too much obvious that the protocol
tries to compete with IPv6 etc. This might make problems if you
at some point try to push this through IETF standardization because of
policitical reasons to try to stick to a single-protocol internet approach
(although it has IP in it). I don't know for sure...

I think a name with 'tunnel' in it might have much better chances in
discussions. ;)

For me, the protocol seems to have enough value in it to get used, but
IMHO this doesn't depend on the protocol itself so much, but on the API
towards the user. It would be best if old applications could just use this
protocol without any change, but this might be very difficult. Somehow
during history user applications got exposed to binary fixed-length
addresses, and they even try to interpret them sometimes. For me this
seems to be the hardest nut to crack.

As a hack one could try to expose sockaddr_ein as sockaddr_in6 as it
has enough storage and people already seem to implement IPv6 API.

In case you want to try to push the protocol upstream I would suggest that
you might send RFC patches early on to this list so that people might
have a look and give feedback early on. In the paper you state that it
currently only needs 700 lines of code (without icmp handling?),
so I guess people here would browse through the code and comment on it.

> Here's the abstract from the paper:
> 
> Enhanced IP (EnIP) offers a solution to the problem of IPv4 address
> depletion without replacing IPv4, as IPv6 does, but by building on top
> of IPv4, maximizing backward compatibility. An experimental EnIP
> deployment between nodes at the University of Maryland and the
> University of Delaware, requiring neither software modification nor
> modification of in-path routers, demonstrates EnIP's potential.

Sorry, I don't have anything to add from a technical PoV currently.

Bye,

  Hannes

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