.ds RF FORMFEED[Page %]
.ds CF
.ds LH Internet Draft
-.ds RH XXX
+.ds RH 13 November 2001
.ds CH
.na
.hy 0
.in 0
.nf
-Network Working Group P. Riikonen
+Network Working Group P. Riikonen
Internet-Draft
-draft-riikonen-silc-commands-02.txt XXX
-Expires: XXX
+draft-riikonen-silc-commands-02.txt 13 November 2001
+Expires: 13 May 2002
.in 3
2 SILC Commands ................................................. 2
2.1 SILC Commands Syntax ...................................... 2
2.2 SILC Commands List ........................................ 4
- 2.3 SILC Command Status Types ................................. 32
- 2.3.1 SILC Command Status Payload ......................... 32
- 2.3.2 SILC Command Status List ............................ 32
-3 Security Considerations ....................................... 37
+ 2.3 SILC Command Status Types ................................. 33
+ 2.3.1 SILC Command Status Payload ......................... 33
+ 2.3.2 SILC Command Status List ............................ 33
+3 Security Considerations ....................................... 38
4 References .................................................... 38
-5 Author's Address .............................................. 39
+5 Author's Address .............................................. 40
.ti 0
Reply messages to the command:
- Max Arguments: 8
+ Max Arguments: 9
Arguments: (1) <Status Payload> (2) <Client ID>
(3) <nickname>[@<server>] (4) <username@host>
(5) <real name> (6) [<Channel Payload
list>]
(7) [<user mode>] (8) [<idle time>]
+ (9) [<fingerprint>]
This command may reply with several command reply messages to
<count> option were defined in the query there will be only
<count> many replies from the server.
- The server MAY return the list of channel the client has joined.
+ The server may return the list of channel the client has joined.
In this case the list is list of Channel Payloads. The Mode Mask
in the Channel Payload (see [SILC2] and section 2.3.2.3 for the
Channel Payload) is the client's mode on the channel. The list
is encoded by adding the Channel Payloads one after the other.
+ The server may also send 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
+ the corresponding private key. Server can do this during the
+ SILC Key Exchange protocol. The <fingerprint> is SHA1 digest.
+
Status messages:
SILC_STATUS_OK
Requirement Levels", BCP 14, RFC 2119, March 1997.
+
+
+
+
+
+
.ti 0
5 Author's Address
EMail: priikone@silcnet.org
-This Internet-Draft expires XXX
+This Internet-Draft expires 13 May 2002