some spec questions

> An idea would be to have a "knock Knock" protocol that would state
> protocol types with a challenge response and possibly hash cash, else
it
> will not allow the port to be open for the tunnel.

well, you can't send hashcash until you open the tunnel and port to recieve
the hashcash... ;)

but yes, we will definitely allow routers to 'pay' for messages and tunnels,
 either through hashcash (using something like n-bits of H(message body+day
of year) as the challenge), real cash certificates, authorization certificates
(for web of trust style subnets), or even null certificates.  each router
will have the option of specifying their minimum requirements as well
(e.g. if I set up a router on a DSL line and want to peer only with fast
computers, I set my minimum hashcash to 20 bits per message, or 25 bits
for tunnel participation, while if I set up a router on an OC12 I could
say fsck it and set my minimum hashcash to 4 bits and 8 bits for tunnel
participation)

the protocol types each router supports is explicitly distributed in
the RouterInfo structures (each RouterAddress is a declaration of one
way of contacting the router - e.g. style = 42 (TCP sockets w/ DH), host
= someHostname.mil, port = 666)

(btw, sorry for the piss poor formatting in the message this morning.
 here I was trying to make it pretty and I end up b0rking it)

see y'all tonight in the meeting
-jrandom



Concerned about your privacy? Follow this link to get
FREE encrypted email: https://www.hushmail.com/?l=2

Free, ultra-private instant messaging with Hush Messenger
https://www.hushmail.com/services.php?subloc=messenger&l=434

Promote security and make money with the Hushmail Affiliate Program: 
https://www.hushmail.com/about.php?subloc=affiliate&l=427