[Webfunds-commits] html/guide sox.html

Ian Grigg iang@cypherpunks.ai
Mon, 18 Sep 2000 09:56:00 -0400 (AST)


iang        00/09/18 09:56:00

  Modified:    guide    sox.html
  Log:
  some updates

Revision  Changes    Path
1.2       +22 -4     html/guide/sox.html

Index: sox.html
===================================================================
RCS file: /home/webfunds/cvsroot/html/guide/sox.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sox.html	2000/07/05 14:28:52	1.1
+++ sox.html	2000/09/18 13:56:00	1.2
@@ -8,9 +8,21 @@
 SOX is a payment protocol that is implemented within
 WebFunds as a wallet.  It consists of a request model
 over an encryption layer.  Requests go from client to
-server and are repeatable.
+server, and replies back from the server to the client.
+
+<p>
+Requests have these characteristics:
 </p>
 
+<ul><li>
+    reliable - idempotent (repeatable and unique)
+  </li><li>
+    extensible - add your own
+  </li><li>
+    secure - protected by encryption / integrity / authentication
+</li></ul>
+
+
 <h2>Reading</h2>
 
 <p>
@@ -23,8 +35,8 @@
     is the original author's paper on the protocol.
     Whilst the concepts have changed little, this
     paper is in need of an update.
-  </li><p></p><li>
 
+  </li><p></p><li>
     <a href="http://www.systemics.com/docs/sox/execsummary.html">
     Executive Summary</a>
     quickly describes the core features of the protocol.
@@ -42,9 +54,9 @@
 <ul><li>
     <p>
     <b>account</b> is primarily
-    a public and private key pair.
+    a public and private key pair created by the SOX Client.
     The private key is kept secret and the public key can
-    be <i>registered</i> with the Issuer, thus making the account
+    be <i>registered</i> with the SOX Server, thus making the account
     the unit of
     <i>authentication</i>.
     </p>
@@ -68,6 +80,12 @@
     transactions.
 
 </li></ul>
+
+Note that most documentation assumes that SOX is used for a
+payments protocol;  this is not necessarily a limitation, and
+SOX is also being used for at least one other application,
+being RTGS trading, which shares similar requirements to
+payments applications.
 
 <p>
 </p>