CAKE

Summary

CAKE is a networking protocol in which all messages are addressed to a public key, and are signed by the source public key. Public key identifiers are treated like IP addresses. They represent the destination or source of any particular message.

For why I chose to make CAKE this way, you may want to check out "CAKE Philosophy and Goals".

If you think CAKE is an interesting project, and would like to donate money to encourage me and keep the website afloat, then I do have a PayPal account, and you can make a donation here:

Detailed documentation

Right now, I just have a collection of documents that aren't tied together especially well. Here's a nice list of them:

Stuff that'll be true of all versions of CAKE.

• CAKE Philosophy and Goals
• Basic types used in building CAKE messages

CAKE protocol version 1

I don't really have any documentation for this yet. Protocol version 1 only has some minor refinements over version 0.

• Version 1 CAKE Messages

CAKE protocol version 0 (deprecated)

• CAKE Message Numbers
• The family of single destination, non-session messages

I also have a Wiki I created for the project.

And, I use Trac to manage the project.

Lastly, there's a mailing list.

I just want to see code!

It's mostly written in Python right now. Conveniently, Subversion repositories are web browsable, so here's a link to it:
the CAKE repository

Links

For a contrasting view of CAKE:
CAKE is the product of a counterrevolutionary conspiracy

Posts I've made in a various places about CAKE:

• LiveJournal posts I've made:
  
  • More CAKE! (progress report 2003-08-10)
  • Progress report 2003-07-14
  • What do I name it?
• Advogato post explaining it and asking about a name
• Slashdot post I made in response to an article asking about SMTP replacements for spam control