1995-01-13 - Re: time stamping service (again)

Header Data

From: eric@remailer.net (Eric Hughes)
To: cypherpunks@toad.com
Message Hash: bea2a895e031eb22733f963e6c054a7212c4e30e66038df123928bee8b825765
Message ID: <199501131916.LAA02991@largo.remailer.net>
Reply To: <m0rSZSa-0009v8C@sdwsys>
UTC Datetime: 1995-01-13 19:17:44 UTC
Raw Date: Fri, 13 Jan 95 11:17:44 PST

Raw message

From: eric@remailer.net (Eric Hughes)
Date: Fri, 13 Jan 95 11:17:44 PST
To: cypherpunks@toad.com
Subject: Re: time stamping service (again)
In-Reply-To: <m0rSZSa-0009v8C@sdwsys>
Message-ID: <199501131916.LAA02991@largo.remailer.net>
MIME-Version: 1.0
Content-Type: text/plain


   From: sdw@lig.net (Stephen D. Williams)

   It should have minimize bandwidth, minimize cpu, minimize storage
   levels of service to allow different levels of users to have
   different possible impact on the machine.  (Ie. : local, paying,
   regional, unknown, domain, etc.)

This is the area of policy, for which there are no general purpose
solutions that I know of.  I see a need for a general purpose module
that would accept authorization requests from various end-user
services (remailing, timestamping, storage, etc.) and return yes or
no.  If money is part of the policy, this is the place to implement
it.

That said, I don't think the lack of a policy engine prevents a
cypherware distribution from happening.

Eric





Thread