updates

[crypto.git] / doc / draft-riikonen-silc-commands-04.nroff

diff --git a/doc/draft-riikonen-silc-commands-04.nroff b/doc/draft-riikonen-silc-commands-04.nroff
index 773b83ab0f93025cb807f24e2072d864aebe8882..721cc53b99ae96b3b6866f863e30bb7923bd6194 100644 (file)
--- a/doc/draft-riikonen-silc-commands-04.nroff
+++ b/doc/draft-riikonen-silc-commands-04.nroff
@@ -8,7 +8,7 @@
 .ds RF FORMFEED[Page %]
 .ds CF
 .ds LH Internet Draft
-.ds RH XXX
+.ds RH 25 November 2002
 .ds CH
 .na
 .hy 0
@@ -16,8 +16,8 @@
 .nf
 Network Working Group                                        P. Riikonen
 Internet-Draft
-draft-riikonen-silc-commands-04.txt                          XXX
-Expires: XXX
+draft-riikonen-silc-commands-04.txt                     25 November 2002
+Expires: 25 April 2003
 
 .in 3
 
@@ -73,15 +73,15 @@ Table of Contents
 1 Introduction ..................................................  2
   1.1 Requirements Terminology ..................................  2
 2 SILC Commands .................................................  2
-  2.1 SILC Commands Syntax ......................................  2
-  2.2 SILC Command Argument Idioms ..............................  2
+  2.1 SILC Commands Syntax ......................................  4
+  2.2 SILC Command Argument Idioms ..............................  4
   2.3 SILC Commands List ........................................  4
-  2.4 SILC Command Status Payload ............................... 40
-3 SILC Status Types ............................................. 41
-4 Security Considerations ....................................... 47
-5 References .................................................... 47
-6 Author's Address .............................................. 49
-Appendix A ...................................................... 49
+  2.4 SILC Command Status Payload ............................... 42
+3 SILC Status Types ............................................. 43
+4 Security Considerations ....................................... 49
+5 References .................................................... 49
+6 Author's Address .............................................. 51
+Appendix A ...................................................... 51
 
 
 .ti 0
@@ -198,7 +198,7 @@ Every command reply also defines set of status message that it
 may return inside the <Status Payload>.  All status messages
 are defined in the section 2.3 SILC Command Status Payload
 The status messages defined with the command are recommendations.
-It is possible to return other status messages not listes with
+It is possible to return other status messages not listed with
 the command reply definition.
 .in 3
 
@@ -301,7 +301,7 @@ List of all defined commands in SILC follows.
 
         The command replies include the Client ID of the nickname,
         nickname and server name, user name and host name and user's real
-        name.  Client SHOULD process these replies only after the last
+        name.  Client should process these replies only after the last
         reply has been received with the STATUS_LIST_END status.  If the
         <count> option were defined in the query there will be only
         <count> many replies from the server.
@@ -399,7 +399,7 @@ List of all defined commands in SILC follows.
 
         Identify command is used to query information about an entity by
         the entity's name or ID.  This command can be used to query
-        information about clients, server and channels.
+        information about clients, servers and channels.
 
         The query may find multiple matching entities.  The <count> option
         may be given to narrow down the number of accepted results.  If
@@ -420,8 +420,8 @@ List of all defined commands in SILC follows.
 
         Implementations may not want to give interface access to this
         command as it is hardly a command that would be used by an end
-        user.  However, it must be implemented as it is used with private
-        message sending.
+        user.  However, it must be implemented as it is most likely used
+        with private message sending.
 
         The IDENTIFY command MUST be always sent to the router by server
         so that all users are searched.  However, server MUST still search
@@ -483,8 +483,8 @@ List of all defined commands in SILC follows.
         When nickname is changed new Client ID is generated.  Server MUST
         distribute SILC_NOTIFY_TYPE_NICK_CHANGE to local clients on the
         channels (if any) the client is joined on.  Then it MUST send
-        SILC_PACKET_REPLACE_ID to its primary route to replace the old
-        Client ID with the new one.
+        SILC_NOTIFY_TYPE_NICK_CHANGE notify  to its primary route to 
+        notify about nickname and Client ID change.
 
         Reply messages to the command:
 
@@ -492,7 +492,7 @@ List of all defined commands in SILC follows.
             Arguments:  (1) <Status Payload>  (2) <New ID Payload>
                         (3) <nickname>
 
-        This command is replied always with New ID Payload that is
+        This command replies always with <New ID Payload> that is
         generated by the server every time user changes their nickname.
         Client receiving this payload MUST start using the received
         Client ID as its current valid Client ID.  The New ID Payload
@@ -2486,7 +2486,7 @@ Finland
 
 EMail: priikone@iki.fi
 
-This Internet-Draft expires XXX
+This Internet-Draft expires 25 April 2003
 
 
 .ti 0