Minor comments to draft

[Linus Nordberg]

--=-=-=

In section 5, the terms challenge message and prefix seem to mean the
same thing.

Typo fixes in attached patch.


--=-=-=
Content-Type: text/x-patch
Content-Disposition: attachment

Index: draft-nisse-hash-cash.xml
===================================================================
RCS file: /cvsroot/mta-hashcash/mta-hashcash/doc/draft-nisse-hash-cash.xml,v
retrieving revision 1.5
diff -c -p -c -p -r1.5 draft-nisse-hash-cash.xml
*** draft-nisse-hash-cash.xml	15 Oct 2004 13:10:26 -0000	1.5
--- draft-nisse-hash-cash.xml	21 Oct 2004 07:16:07 -0000
***************
*** 260,266 ****
        </t>
        <t>
  	When these commands are used, both server and client must know
! 	eachother's names. FIXME: How these MTA names are related to
  	the hello messages, envelope addresses, and other information,
  	is not yet clear.
        </t>
--- 260,266 ----
        </t>
        <t>
  	When these commands are used, both server and client must know
! 	each other's names. FIXME: How these MTA names are related to
  	the hello messages, envelope addresses, and other information,
  	is not yet clear.
        </t>
***************
*** 282,288 ****
    300 No hash cash or authentication expected
  
    301-No hash cash expected, authentication encouraged
!   311 &lt;keyid&gt; 
  	      
    310 Expecting hash cash
  
--- 282,288 ----
    300 No hash cash or authentication expected
  
    301-No hash cash expected, authentication encouraged
!   301 &lt;keyid&gt; 
  	      
    310 Expecting hash cash
  
***************
*** 332,338 ****
  	  the server and identifies this particular challenge.
  	</t>
  	<t>
! 	  If none of the methods is supported, the server replies with
  	  code 504. This specification defines one method,
  	  "hmac-sha1", and for this method the text gives the server's
  	  random salt, as a quoted string, followed by optional
--- 332,338 ----
  	  the server and identifies this particular challenge.
  	</t>
  	<t>
! 	  If none of the methods are supported, the server replies with
  	  code 504. This specification defines one method,
  	  "hmac-sha1", and for this method the text gives the server's
  	  random salt, as a quoted string, followed by optional
***************
*** 348,354 ****
  	<t>
  	  After issuing this command, the client may terminate the
  	  current mail transaction (by the QUIT, RSET or EHLO command),
! 	  in this case, the server must store the issued challenge must
  	  be stored for its advertised lifetime, and allow the client to
  	  come back later.
  	</t>
--- 348,354 ----
  	<t>
  	  After issuing this command, the client may terminate the
  	  current mail transaction (by the QUIT, RSET or EHLO command),
! 	  in this case, the issued challenge must
  	  be stored for its advertised lifetime, and allow the client to
  	  come back later.
  	</t>
***************
*** 466,472 ****
  	  </list>
  	</t>
  	<t>
! 	It's desirable that communication between a MUA its border-MTA
  	is in the form of email, rather than a direct connection using
  	SMTP or some other specialized protocol. Commands from MUA to
  	MTA may be sent as email to a special email address.
--- 466,472 ----
  	  </list>
  	</t>
  	<t>
! 	It's desirable that communication between a MUA and its border-MTA
  	is in the form of email, rather than a direct connection using
  	SMTP or some other specialized protocol. Commands from MUA to
  	MTA may be sent as email to a special email address.
***************
*** 496,504 ****
  	something along the lines of
  	<figure>
  	  <artwork>
!   X-MTA-Hashcash: &tl;mta&gt; noauth
!   X-MTA-Hashcash: &tl;mta&gt; auth &lt;keyid&gt;
!   X-MTA-Hashcash: &tl;mta&gt; challenge-response &lt;type&gt; &lt;difficulty&gt; 
  	  </artwork>
  	</figure>
  	The keyid is important, for key revocation/black-listing. This
--- 496,504 ----
  	something along the lines of
  	<figure>
  	  <artwork>
!   X-MTA-Hashcash: &lt;mta&gt; noauth
!   X-MTA-Hashcash: &lt;mta&gt; auth &lt;keyid&gt;
!   X-MTA-Hashcash: &lt;mta&gt; challenge-response &lt;type&gt; &lt;difficulty&gt; 
  	  </artwork>
  	</figure>
  	The keyid is important, for key revocation/black-listing. This
***************
*** 526,532 ****
        </section>
        <section title="Semantics records in the key database">
  	<t>
! 	  When a key is setup using the XHASHCASHNEWKEY mechanism, and
  	  is associated with a peer MTA, not much is known.
  	  Essentially, all we know is that there is some person or
  	  entity other than ourselves that know the key.
--- 526,532 ----
        </section>
        <section title="Semantics records in the key database">
  	<t>
! 	  When a key is set up using the XHASHCASHNEWKEY mechanism, and
  	  is associated with a peer MTA, not much is known.
  	  Essentially, all we know is that there is some person or
  	  entity other than ourselves that know the key.

--=-=-=--