Re: Effective micropayments

"Milan VXdgsvt" <milan_vxdgsvt@seznam.cz> writes:
> Let's imagine the following setup: Alice wants to send many messages to
> Bob, but she's not connected directly to Bob. Instead she has to
> transmit messages to Robert the Retransmitter, who sends them to Bob.
> The trouble is, Robert wants money for this, and does not want to spend
> too much computation power on this.

it is called the internet. Alice is an ISP client. Robert is the ISP.

it used to be that people did offline email ... they called their
local (electronic) postoffice, exchanged email and hung up. both the
telco and the network service provider charged by the minute connected
and (sometimes the service provider charged by bytes transmitted).

there use to be these boxes by livingston and they came up with this
thing called radius (I confess to long ago and far away being involved
in helping with some radius stuff on real livingston box for very
small startup).

radius evolved into an ietf standard for authentication. authorization,
and accounting. misc. collected past postings mentioning radius
http://www.garlic.com/~lynn/subpubkey.html#radius

my rfc index
http://www.garlic.com/~lynn/rfcietff.htm

in the "RFCs listed by" section, click on "Term (term->RFC#)"

and either click on "RADIUS" in the "Acronym fastpath" or scroll
down to

remote authentication dial in user service (RADIUS )
 see also authentication , network access server , network services
 4014 3580 3579 3576 3575 3162 2882 2869 2868 2867 2866 2865 2809
 2621 2620 2619 2618 2548 2139 2138 2059 2058

clicking on the rfc number brings up the rfc summary in the lower
frame. clicking on the ".txt=nnnn" field in the rfc summary, fetches
the actual RFC.

you might also be interest in some of the AAA working group

Authentication, Authorization and Accounting
 see also accounting , authentication , authorization
 3588 3539 3127 2989 2977 2906 2905 2904 2903

-- 
Anne & Lynn Wheeler | http://www.garlic.com/~lynn/