Protocol agnostic.

diff --git a/blog/data/2014-03-25-trusted-timestamping.txt b/blog/data/2014-03-25-trusted-timestamping.txt
index 01b68597975a75b7a4db16e8e0ac17dad9ab04e9..51d86c9c48358e2ef3f6f6fb341fe840b7c804f6 100644 (file)
--- a/blog/data/2014-03-25-trusted-timestamping.txt
+++ b/blog/data/2014-03-25-trusted-timestamping.txt
@@ -25,11 +25,13 @@ few years ago as <a href="http://tools.ietf.org/html/rfc3161">RFC
 3161</a>.  The mechanism is simple.  Create a hash of the file in
 question, send it to a trusted third party which add a time stamp to
 the hash and sign the result with its private key, and send back the
-signed hash + timestamp.  Anyone with the document and the signature
-can then verify that the document matches the signature by creating
-their own hash and checking the signature using the trusted third
-party public key.  There are several commercial services around
-providing such timestamping.  A quick search for
+signed hash + timestamp.  Both email, FTP and HTTP can be used to
+request such signature, depending on what is provided by the service
+used. Anyone with the document and the signature can then verify that
+the document matches the signature by creating their own hash and
+checking the signature using the trusted third party public key.
+There are several commercial services around providing such
+timestamping.  A quick search for
 "<a href="https://duckduckgo.com/?q=rfc+3161+service">rfc 3161
 service</a>" pointed me to at least
 <a href="https://www.digistamp.com/technical/how-a-digital-time-stamp-works/">DigiStamp</a>,