1994-11-22 - Re: Borenstein Speech

Header Data

From: Rich Salz <rsalz@osf.org>
To: owner-cypherpunks@toad.com
Message Hash: 6cc820fb5b73043b21baf74629c1dbd81eff32f175937ecc5492d5c070700599
Message ID: <9411221814.AA23517@sulphur.osf.org>
Reply To: N/A
UTC Datetime: 1994-11-22 18:18:39 UTC
Raw Date: Tue, 22 Nov 94 10:18:39 PST

Raw message

From: Rich Salz <rsalz@osf.org>
Date: Tue, 22 Nov 94 10:18:39 PST
To: owner-cypherpunks@toad.com
Subject: Re:  Borenstein Speech
Message-ID: <9411221814.AA23517@sulphur.osf.org>
MIME-Version: 1.0
Content-Type: text/plain


I know better then this.

>Nat Borenstein is speaking nearby on Monday.

What's the global definition of nearby? :(

I'll be the one yelling "thief, thief" as he talks about safe-tcl...

              MITSUBISHI ELECTRIC RESEARCH LABORATORIES
                             201 Broadway
                         Cambridge, MA 02139
                             617-621-7500

               OPEN PROTOCOLS FOR INFORMATION COMMERCE

                Nathaniel Borenstein, Chief Scientist
                     First Virtual Holdings Inc.

                Date:  Monday, November 28, 1994
                Time:  9:30 am

Abstract:

Traditional one-way payment mechanisms, such as cash, credit cards,
and digital cash, presuppose the necessity of payment validation in
advance of the completion of a transaction.  In contrast, a "closed
loop" protocol that verifies both payment information and customer
satisfaction permits a far simpler payment engine in an open Internet
environment, and is well-suited to a broad sub-class of Internet
commerce applications.  In this talk, I will present the underlying
philosophy, design rationale, and specification overview for a
recently-developed set of open protocols for information commerce.

(Dr. Borenstein is well known for his work at Bellcore on the MIME
standard for multimedia messaging; he is also the author of the
Andrew Message System, ATOMICMAIL, Metamail, Safe-TCL, and
_Programming as if People Mattered_.)

Host:  David B Anderson <anderson@merl.com>

Directions to MERL can be found in

        ftp://ftp.merl.com/pub/directions.map





Thread