From: michi1@michaelblizek.twilightparadox.com
To: netdev@vger.kernel.org, davem@davemloft.net
Subject: [RFC] new connection-oriented layer 3+4 protocol
Date: Wed, 19 Sep 2012 19:08:53 +0200 [thread overview]
Message-ID: <20120919170853.GJ2228@grml> (raw)
Hi!
I am programming a new layer 3+4 protocol for mesh networks. Basically it is
- connection oriented
- source (+optional onion) routed
- doing windowing between each neighbor on every connection (no congestion
avoidance)
- using credits as a metric for QoS
The protocol especially tries to withstand DoS attacks and rough
users/application without human interference. This includes protection against
inserting bogus routes, blackholing/throttling, addressing conflicts (node
address can be a hashed public crypto key) and ressource contention. In theory
it could provide Byzantine robustness, but in practice the overhead for
calculating routes and ressource contention will limit how far this gets.
Right now the layer 3 is running somehow (without any crypto). The layer 4 is
currently rather incomplete and broken.
Project home:
http://michaelblizek.homelinux.net/projects/cor/index.html
Code:
http://repo.or.cz/w/cor.git/tree/HEAD:/net/cor
-Michi
reply other threads:[~2012-09-19 17:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120919170853.GJ2228@grml \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).