updates.

[runtime.git] / doc / draft-riikonen-silc-commands-03.nroff

diff --git a/doc/draft-riikonen-silc-commands-03.nroff b/doc/draft-riikonen-silc-commands-03.nroff
index 2de56b4685bcfb66a5aa0bb8407cafda85c11e27..7a071b27a20926e004c39bfed2af7661f3f1b791 100644 (file)
--- a/doc/draft-riikonen-silc-commands-03.nroff
+++ b/doc/draft-riikonen-silc-commands-03.nroff
@@ -282,7 +282,9 @@ List of all defined commands in SILC follows.
         include STATUS_LIST_START status in the first reply and
         STATUS_LIST_END in the last reply to indicate the end of the
         list.  If there are only one reply the status is set to normal
-        STATUS_OK.
+        STATUS_OK.  If multiple Client IDs was requested then each found
+        and unfound client must cause successful or error reply,
+        respectively.
 
         The command replies include the Client ID of the nickname,
         nickname and server name, user name and host name and user's real
@@ -306,7 +308,7 @@ List of all defined commands in SILC follows.
         The server also returns client's user mode, idle time, and the
         fingerprint of the client's public key.  The <fingerprint> is the
         binary hash digest of the public key.  The fingerprint MUST NOT
-        be sent if the server has not verified the proof of posession of
+        be sent if the server has not verified the proof of possession of
         the corresponding private key.  Server can do this during the
         SILC Key Exchange protocol.  The <fingerprint> is SHA1 digest.
 
@@ -422,7 +424,9 @@ List of all defined commands in SILC follows.
         a list of results.  In this case the status payload will include
         STATUS_LIST_START status in the first reply and STATUS_LIST_END in 
         the last reply to indicate the end of the list.  If there are only 
-        one reply the status is set to normal STATUS_OK.
+        one reply the status is set to normal STATUS_OK.  If multiple Client
+        IDs was requested then each found and unfound client must cause
+        successful or error reply, respectively.
 
         When querying clients the <entity's name> must include the client's
         nickname in the following format: nickname[@server].  The
@@ -889,7 +893,8 @@ List of all defined commands in SILC follows.
         privileges the same way as the client had given the
         SILC_COMMAND_CUMODE command to gain founder privileges.  The
         client is still able to join the channel even if the founder
-        privileges could not be gained.
+        privileges could not be gained.  The hash function used with
+        the <founder payload> MUST be sha1.
 
         The server MUST check whether the user is allowed to join to
         the requested channel.  Various modes set to the channel affect
@@ -1177,7 +1182,7 @@ List of all defined commands in SILC follows.
         of a channel.  Modes may be masked together by ORing them thus
         having several modes set.  The <Channel ID> is the ID of the
         target channel.  The client changing channel mode MUST be on
-        the same channel and poses sufficient privileges to be able to
+        the same channel and posses sufficient privileges to be able to
         change the mode.
 
         When the mode is changed SILC_NOTIFY_TYPE_CMODE_CHANGE notify
@@ -1334,7 +1339,8 @@ List of all defined commands in SILC follows.
               used to verify the payload is the public key of the
               client sending this command.  The mode may be set only
               if the <auth payload> was verified successfully.  The
-              server also MUST save the founder's public key.
+              server also MUST save the founder's public key.  The
+              hash function used with the <auth payload> MUST be sha1.
 
               The public key of the founder is sent in the
               SILC_NOTIFY_TYPE_CMODE_CHANGE notify type so that other
@@ -1425,7 +1431,7 @@ List of all defined commands in SILC follows.
         The <Channel ID> is the ID of the target channel.  The <mode mask>
         is OR'ed mask of modes.  The <Client ID> is the target client.
         The client changing channel user modes MUST be on the same channel
-        as the target client and poses sufficient privileges to be able to
+        as the target client and posses sufficient privileges to be able to
         change the mode.
 
         When the mode is changed SILC_NOTIFY_TYPE_CUMODE_CHANGE notify
@@ -1992,7 +1998,9 @@ send both list of successful replies and list of error
 replies at the same time, however in this case the
 list of error replies MUST be sent after the successful
 replies.  This way the recipient may ignore the multiple
-errors if it wishes to do so.
+errors if it wishes to do so.  Also note that in this
+case the successful and error replies belong to the
+same list.
 
 All Status messages are described in the next section.
 
@@ -2292,13 +2300,13 @@ security of this protocol.
 4 References
 
 [SILC1]      Riikonen, P., "Secure Internet Live Conferencing (SILC),
-             Protocol Specification", Internet Draft, April 2001.
+             Protocol Specification", Internet Draft, May 2002.
 
 [SILC2]      Riikonen, P., "SILC Packet Protocol", Internet Draft,
-             April 2001.
+             May 2002.
 
 [SILC3]      Riikonen, P., "SILC Key Exchange and Authentication 
-             Protocols", Internet Draft, April 2001.
+             Protocols", Internet Draft, May 2002.
 
 [IRC]        Oikarinen, J., and Reed D., "Internet Relay Chat Protocol",
              RFC 1459, May 1993.
@@ -2356,8 +2364,8 @@ security of this protocol.
 [RFC2279]    Yergeau, F., "UTF-8, a transformation format of ISO
              10646", RFC 2279, January 1998.
 
-
-
+[ATTRS]      Riikonen, P., "User Online Presence and Information
+             Attributes", Internet Draft, May 2002.
 
 
 .ti 0
@@ -2365,7 +2373,7 @@ security of this protocol.
 
 .nf
 Pekka Riikonen
-Snellmanninkatu 34 A 15
+Snellmaninkatu 34 A 15
 70100 Kuopio
 Finland