8 .ds RF FORMFEED[Page %]
17 Network Working Group P. Riikonen
19 draft-riikonen-silc-pp-05.txt XXX
26 <draft-riikonen-silc-pp-05.txt>
31 This document is an Internet-Draft and is in full conformance with
32 all provisions of Section 10 of RFC 2026. Internet-Drafts are
33 working documents of the Internet Engineering Task Force (IETF), its
34 areas, and its working groups. Note that other groups may also
35 distribute working documents as Internet-Drafts.
37 Internet-Drafts are draft documents valid for a maximum of six months
38 and may be updated, replaced, or obsoleted by other documents at any
39 time. It is inappropriate to use Internet-Drafts as reference
40 material or to cite them other than as "work in progress."
42 The list of current Internet-Drafts can be accessed at
43 http://www.ietf.org/ietf/1id-abstracts.txt
45 The list of Internet-Draft Shadow Directories can be accessed at
46 http://www.ietf.org/shadow.html
48 The distribution of this memo is unlimited.
54 This memo describes a Packet Protocol used in the Secure Internet Live
55 Conferencing (SILC) protocol, specified in the Secure Internet Live
56 Conferencing, Protocol Specification Internet Draft [SILC1]. This
57 protocol describes the packet types and packet payloads which defines
58 the contents of the packets. The protocol provides secure binary packet
59 protocol that assures that the contents of the packets are secured and
73 1 Introduction .................................................. 3
74 1.1 Requirements Terminology .................................. 4
75 2 SILC Packet Protocol .......................................... 4
76 2.1 SILC Packet ............................................... 4
77 2.2 SILC Packet Header ........................................ 5
78 2.3 SILC Packet Types ......................................... 7
79 2.3.1 SILC Packet Payloads ................................ 16
80 2.3.2 Generic payloads .................................... 16
81 2.3.2.1 ID Payload .................................. 17
82 2.3.2.2 Argument Payload ............................ 18
83 2.3.2.3 Channel Payload ............................. 18
84 2.3.2.4 Public Key Payload .......................... 19
85 2.3.3 Disconnect Payload .................................. 20
86 2.3.4 Success Payload ..................................... 21
87 2.3.5 Failure Payload ..................................... 21
88 2.3.6 Reject Payload ...................................... 22
89 2.3.7 Notify Payload ...................................... 22
90 2.3.8 Error Payload ....................................... 28
91 2.3.9 Channel Message Payload ............................. 29
92 2.3.10 Channel Key Payload ................................ 32
93 2.3.11 Private Message Payload ............................ 34
94 2.3.12 Private Message Key Payload ........................ 35
95 2.3.13 Command Payload .................................... 37
96 2.3.14 Command Reply Payload .............................. 38
97 2.3.15 Connection Auth Request Payload .................... 38
98 2.3.16 New ID Payload ..................................... 39
99 2.3.17 New Client Payload ................................. 40
100 2.3.18 New Server Payload ................................. 41
101 2.3.19 New Channel Payload ................................ 42
102 2.3.20 Key Agreement Payload .............................. 43
103 2.3.21 Resume Router Payload .............................. 44
104 2.3.22 File Transfer Payload .............................. 44
105 2.3.23 Resume Client Payload .............................. XXXXXX
106 2.4 SILC ID Types ............................................. 46
107 2.5 Packet Encryption And Decryption .......................... 46
108 2.5.1 Normal Packet Encryption And Decryption ............. 46
109 2.5.2 Channel Message Encryption And Decryption ........... 47
110 2.5.3 Private Message Encryption And Decryption ........... 48
111 2.6 Packet MAC Generation ..................................... 48
112 2.7 Packet Padding Generation ................................. 49
113 2.8 Packet Compression ........................................ 50
114 2.9 Packet Sending ............................................ 50
115 2.10 Packet Reception ......................................... 51
116 2.11 Packet Routing ........................................... 51
117 2.12 Packet Broadcasting ...................................... 52
118 3 Security Considerations ....................................... 53
119 4 References .................................................... 53
120 5 Author's Address .............................................. 54
126 Figure 1: Typical SILC Packet
127 Figure 2: SILC Packet Header
129 Figure 4: Argument Payload
130 Figure 5: Channel Payload
131 Figure 6: Public Key Payload
132 Figure 7: Disconnect Payload
133 Figure 8: Success Payload
134 Figure 9: Failure Payload
135 Figure 10: Reject Payload
136 Figure 11: Notify Payload
137 Figure 12: Error Payload
138 Figure 13: Channel Message Payload
139 Figure 14: Channel Key Payload
140 Figure 15: Private Message Payload
141 Figure 16: Private Message Key Payload
142 Figure 17: Command Payload
143 Figure 18: Connection Auth Request Payload
144 Figure 19: New Client Payload
145 Figure 20: New Server Payload
146 Figure 21: Key Agreement Payload
147 Figure 22: Resume Router Payload
148 Figure 23: File Transfer Payload
149 Figure 24: Resume Client Payload
155 This document describes a Packet Protocol used in the Secure Internet
156 Live Conferencing (SILC) protocol specified in the Secure Internet Live
157 Conferencing, Protocol Specification Internet Draft [SILC1]. This
158 protocol describes the packet types and packet payloads which defines
159 the contents of the packets. The protocol provides secure binary packet
160 protocol that assures that the contents of the packets are secured and
163 The basis of SILC protocol relies in the SILC packets and it is with
164 out a doubt the most important part of the protocol. It is also probably
165 the most complicated part of the protocol. Packets are used all the
166 time in the SILC network to send messages, commands and other information.
167 All packets in SILC network are always encrypted and their integrity
168 is assured by computed MACs. The protocol defines several packet types
169 and packet payloads. Each packet type usually has a specific packet
170 payload that actually defines the contents of the packet. Each packet
171 also includes a default SILC Packet Header that provides sufficient
172 information about the origin of the packet and destination of the
177 1.1 Requirements Terminology
179 The keywords MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED,
180 MAY, and OPTIONAL, when they appear in this document, are to be
181 interpreted as described in [RFC2119].
185 2 SILC Packet Protocol
190 SILC packets deliver messages from sender to receiver securely by
191 encrypting important fields of the packet. The packet consists of
192 default SILC Packet Header, Padding, Packet Payload data, and, packet
195 The following diagram illustrates typical SILC packet.
200 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
201 | n bytes | 1 - n bytes | n bytes | n bytes
202 | SILC Header | Padding | Data Payload | MAC
203 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
207 Figure 1: Typical SILC Packet
210 SILC Header is always the first part of the packet and its purpose
211 is to provide information about the packet. It provides for example
212 the packet type, origin of the packet and the destination of the packet.
213 The header is variable in length. See the following section for
214 description of SILC Packet header. Packets without SILC header or
215 with malformed SILC header MUST be dropped.
217 Padding follows the packet header. The purpose of the padding is to
218 make the packet multiple by eight (8) or by the block size of the
219 cipher used in the encryption, which ever is larger. The maximum
220 length of padding is currently 128 bytes. The padding is always
221 encrypted. The padding is applied always, even if the packet is
222 not encrypted. See the section 2.7 Padding Generation for more
223 detailed information.
225 Data payload area follows padding and it is the actual data of the
226 packet. The packet data is the packet payloads defined in this
227 protocol. The data payload area is always encrypted.
229 The last part of SILC packet is the packet MAC that assures the
230 integrity of the packet. The MAC is always computed from the packet
231 before the encryption is applied to the packet. If compression is used
232 in the packet the MAC is computed after the compression has been
233 applied. The compression, on the other hand, is always applied before
234 encryption. See more details in the section 2.6 Packet MAC Generation.
236 All fields in all packet payloads are always in MSB (most significant
241 2.2 SILC Packet Header
243 The SILC packet header is applied to all SILC packets and it is
244 variable in length. The purpose of SILC Packet header is to provide
245 detailed information about the packet. The receiver of the packet
246 uses the packet header to parse the packet and gain other relevant
247 parameters of the packet.
249 The following diagram represents the SILC packet header.
254 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
256 | Payload Length | Flags | Packet Type |
257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
258 | Pad Length | RESERVED | Source ID Len | Dest ID Len |
259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
275 Figure 2: SILC Packet Header
279 o Payload Length (2 bytes) - Is the length of the packet
280 not including the padding of the packet.
282 o Flags (1 byte) - Indicates flags to be used in packet
283 processing. Several flags may be set by ORing the flags
286 The following flags are reserved for this field:
291 In this case the field is ignored.
294 Private Message Key 0x01
296 Indicates that the packet must include private
297 message that is encrypted using private key set by
298 client. Servers does not know anything about this
299 key and this causes that the private message is
300 not handled by the server at all, it is just
301 passed along. See section 2.5.3 Private Message
302 Encryption And Decryption for more information.
307 Indicates that the packet consists of list of
308 packet payloads indicated by the Packet Type field.
309 The payloads are added one after the other. Note that
310 there are packet types that must not be used as
311 list. Parsing of list packet is done by calculating
312 the length of each payload and parsing them one by
318 Marks the packet to be broadcasted. Client cannot
319 send broadcast packet and normal server cannot send
320 broadcast packet. Only router server may send broadcast
321 packet. The router receiving of packet with this flag
322 set MUST send (broadcast) the packet to its primary
323 route. If router has several router connections the
324 packet may be sent only to the primary route. See
325 section 2.12 Packet Broadcasting for description of
333 o Packet Type (1 byte) - Is the type of the packet. Receiver
334 uses this field to parse the packet. See section 2.3
335 SILC Packets for list of defined packet types.
337 o Pad Length (1 byte) - Indicates the length of the padding
338 applied after the SILC Packet header. Maximum length for
339 padding is 128 bytes.
341 o RESERVED (1 byte) - Reserved field and must include a
344 o Source ID Length (1 byte) - Indicates the length of the
345 Source ID field in the header, not including this or any
348 o Destination ID Length (1 byte) - Indicates the length of the
349 Destination ID field in the header, not including this or
352 o Src ID Type (1 byte) - Indicates the type of ID in the
353 Source ID field. See section 2.4 SILC ID Types for
356 o Source ID (variable length) - The actual source ID that
357 indicates which is the original sender of the packet.
359 o Dst ID Type (1 byte) - Indicates the type of ID in the
360 Destination ID field. See section 2.4 SILC ID Types for
363 o Destination ID (variable length) - The actual destination
364 ID that indicates which is the end receiver of the packet.
369 2.3 SILC Packet Types
371 SILC packet types defines the contents of the packet and it is used by
372 the receiver to parse the packet. The packet type is 8 bits, as a one
373 byte, in length. The range for the packet types are from 0 - 255,
374 where 0 is never sent and 255 is currently reserved for future
375 extensions and MUST NOT be defined to any other purpose. Every SILC
376 specification compliant implementation SHOULD support all of these packet
379 The below list of the SILC Packet types includes reference to the packet
380 payload as well. Packet payloads are the actual packet, that is, the data
381 that the packet consists of. Each packet type defines packet payload
382 which usually may only be sent with the specific packet type.
384 Most of the packets are packets that must be destined directly to entity
385 that is connected to the sender. It is not allowed, for example, for
386 router to send disconnect packet to client that is not directly connected
387 to the router. However, there are some special packet types that may
388 be destined to some entity that the sender has not direct connection
389 with. These packets are for example private message packets, channel
390 message packets, command packets and some other packets that may be
391 broadcasted in the SILC network. If the packet is allowed to be sent to
392 indirectly connected entity it is mentioned separately in the packet
393 description (unless it is obvious as in private and channel message
394 packets). Other packets MUST NOT be sent or accepted, if sent, to
395 indirectly connected entities.
397 List of SILC Packet types are defined as follows.
402 This type is reserved and it is never sent.
405 1 SILC_PACKET_DISCONNECT
407 This packet is sent to disconnect the remote end. Reason of
408 the disconnection is sent inside the packet payload. Client
409 usually does not send this packet.
411 This packet MUST NOT be sent as list and the List flag MUST
414 Payload of the packet: See section 2.3.3 Disconnect Payload
417 2 SILC_PACKET_SUCCESS
419 This packet is sent upon successful execution of some protocol.
420 The status of the success is sent in the packet.
422 This packet MUST NOT be sent as list and the List flag MUST
425 Payload of the packet: See section 2.3.4 Success Payload
428 3 SILC_PACKET_FAILURE
430 This packet is sent upon failure of some protocol. The status
431 of the failure is sent in the packet.
433 This packet MUST NOT be sent as list and the List flag MUST
436 Payload of the packet: See section 2.3.5 Failure Payload
441 This packet MAY be sent upon rejection of some protocol.
442 The status of the rejection is sent in the packet.
444 This packet MUST NOT be sent as list and the List flag MUST
447 Payload of the packet: See section 2.3.6 Reject Payload
452 This packet is used to send notify message, usually from
453 server to client, although it MAY be sent from server to another
454 server as well. Client MUST NOT send this packet. Server MAY
455 send this packet to channel as well when the packet is
456 distributed to all clients on the channel.
458 Payload of the packet: See section 2.3.7 Notify Payload.
463 This packet is sent when an error occurs. Server MAY
464 send this packet. Client MUST NOT send this packet. The
465 client MAY entirely ignore the packet, however, server is
466 most likely to take action anyway. This packet MAY be sent
467 to entity that is indirectly connected to the sender.
469 This packet MUST NOT be sent as list and the List flag MUST
472 Payload of the packet: See section 2.3.8 Error Payload.
475 7 SILC_PACKET_CHANNEL_MESSAGE
477 This packet is used to send messages to channels. The packet
478 includes Channel ID of the channel and the actual message to
479 the channel. Messages sent to the channel are always protected
480 by channel specific keys. Channel Keys are distributed by
481 SILC_PACKET_CHANNEL_KEY packet.
483 This packet MUST NOT be sent as list and the List flag MUST
486 Payload of the packet: See section 2.3.9 Channel Message
490 8 SILC_PACKET_CHANNEL_KEY
492 This packet is used to distribute new key for particular
493 channel. Each channel has their own independent keys that
494 is used to protect the traffic on the channel. Only server
495 may send this packet. This packet MAY be sent to entity
496 that is indirectly connected to the sender.
498 This packet MUST NOT be sent as list and the List flag MUST
501 Payload of the packet: See section 2.3.10 Channel Key Payload
504 9 SILC_PACKET_PRIVATE_MESSAGE
506 This packet is used to send private messages from client
507 to another client. By default, private messages are protected
508 by session keys established by normal key exchange protocol.
509 However, it is possible to use specific key to protect private
510 messages. SILC_PACKET_PRIVATE_MESSAGE_KEY packet is used to
511 agree the key with the remote client. Pre-shared key MAY be
512 used as well if both of the client knows it, however, it needs
513 to be agreed outside SILC. See more of this in [SILC1].
515 This packet MUST NOT be sent as list and the List flag MUST
518 Payload of the packet: See section 2.3.11 Private Message
522 10 SILC_PACKET_PRIVATE_MESSAGE_KEY
524 This packet is used to agree about a key to be used to protect
525 the private messages between two clients. If this is not sent
526 the normal session key is used to protect the private messages
527 inside SILC network. Agreeing to use specific key to protect
528 private messages adds security, as no server between the two
529 clients will be able to decrypt the private message. However,
530 servers inside SILC network are considered to be trusted, thus
531 using normal session key to protect private messages does not
532 degrade security. Whether to agree to use specific keys by
533 default or to use normal session keys by default, is
534 implementation specific issue. See more of this in [SILC1].
536 This packet MUST NOT be sent as list and the List flag MUST
539 Payload of the packet: See section 2.3.12 Private Message
543 11 SILC_PACKET_COMMAND
545 This packet is used to send commands from client to server.
546 Server MAY send this packet to other servers as well. All
547 commands are listed in their own section SILC Command Types
548 in [SILC4]. The contents of this packet is command specific.
549 This packet MAY be sent to entity that is indirectly connected
552 This packet MUST NOT be sent as list and the List flag MUST
555 Payload of the packet: See section 2.3.13 Command Payload
558 12 SILC_PACKET_COMMAND_REPLY
560 This packet is sent as reply to the SILC_PACKET_COMMAND packet.
561 The contents of this packet is command specific. This packet
562 MAY be sent to entity that is indirectly connected to the
565 This packet MUST NOT be sent as list and the List flag MUST
568 Payload of the packet: See section 2.3.14 Command Reply
569 Payload and section 2.3.13 Command
575 13 SILC_PACKET_KEY_EXCHANGE
577 This packet is used to start SILC Key Exchange Protocol,
578 described in detail in [SILC3].
580 This packet MUST NOT be sent as list and the List flag MUST
583 Payload of the packet: Payload of this packet is described
584 in the section SILC Key Exchange
585 Protocol and its sub sections in
589 14 SILC_PACKET_KEY_EXCHANGE_1
591 This packet is used as part of the SILC Key Exchange Protocol.
593 This packet MUST NOT be sent as list and the List flag MUST
596 Payload of the packet: Payload of this packet is described
597 in the section SILC Key Exchange
598 Protocol and its sub sections in
602 15 SILC_PACKET_KEY_EXCHANGE_2
604 This packet is used as part of the SILC Key Exchange Protocol.
606 This packet MUST NOT be sent as list and the List flag MUST
609 Payload of the packet: Payload of this packet is described
610 in the section SILC Key Exchange
611 Protocol and its sub sections in
615 16 SILC_PACKET_CONNECTION_AUTH_REQUEST
617 This packet is used to request the authentication method to
618 be used in the SILC Connection Authentication Protocol. If
619 initiator of the protocol does not know the mandatory
620 authentication method this packet MAY be used to determine it.
622 The party receiving this payload MUST respond with the same
623 packet including the mandatory authentication method.
625 This packet MUST NOT be sent as list and the List flag MUST
628 Payload of the packet: See section 2.3.15 Connection Auth
634 17 SILC_PACKET_CONNECTION_AUTH
636 This packet is used to start and perform the SILC Connection
637 Authentication Protocol. This protocol is used to authenticate
638 the connecting party. The protocol is described in detail in
641 This packet MUST NOT be sent as list and the List flag MUST
644 Payload of the packet: Payload of this packet is described
645 in the section SILC Authentication
646 Protocol and it sub sections in [SILC].
649 18 SILC_PACKET_NEW_ID
651 This packet is used to distribute new ID's from server to
652 router and from router to all routers in the SILC network.
653 This is used when for example new client is registered to
654 SILC network. The newly created ID's of these operations are
655 distributed by this packet. Only server may send this packet,
656 however, client MUST be able to receive this packet. This
657 packet MAY be sent to entity that is indirectly connected
660 Payload of the packet: See section 2.3.16 New ID Payload
663 19 SILC_PACKET_NEW_CLIENT
665 This packet is used by client to register itself to the
666 SILC network. This is sent after key exchange and
667 authentication protocols has been completed. Client sends
668 various information about itself in this packet.
670 This packet MUST NOT be sent as list and the List flag MUST
673 Payload of the packet: See section 2.3.17 New Client Payload
676 20 SILC_PACKET_NEW_SERVER
678 This packet is used by server to register itself to the
679 SILC network. This is sent after key exchange and
680 authentication protocols has been completed. Server sends
681 this to the router it connected to, or, if router was
682 connecting, to the connected router. Server sends its
683 Server ID and other information in this packet. The client
684 MUST NOT send or receive this packet.
686 This packet MUST NOT be sent as list and the List flag MUST
689 Payload of the packet: See section 2.3.18 New Server Payload
692 21 SILC_PACKET_NEW_CHANNEL
694 This packet is used to notify routers about newly created
695 channel. Channels are always created by the router and it MUST
696 notify other routers about the created channel. Router sends
697 this packet to its primary route. Client MUST NOT send this
698 packet. This packet MAY be sent to entity that is indirectly
699 connected to the sender.
701 Payload of the packet: See section 2.3.19 New Channel Payload
706 This packet is used to indicate that re-key must be performed
707 for session keys. See section Session Key Regeneration in
708 [SILC1] for more information. This packet does not have
711 This packet MUST NOT be sent as list and the List flag MUST
715 23 SILC_PACKET_REKEY_DONE
717 This packet is used to indicate that re-key is performed and
718 new keys must be used hereafter.
720 This packet MUST NOT be sent as list and the List flag MUST
724 24 SILC_PACKET_HEARTBEAT
726 This packet is used by clients, servers and routers to keep the
727 connection alive. It is recommended that all servers implement
728 keepalive actions and perform it to both direction in a link.
729 This packet does not have a payload.
731 This packet MUST NOT be sent as list and the List flag MUST
735 25 SILC_PACKET_KEY_AGREEMENT
737 This packet is used by clients to request key negotiation
738 between another client in the SILC network. If the negotiation
739 is started it is performed using the SKE protocol. The result of
740 the negotiation, the secret key material, can be used for
741 example as private message key. The server and router MUST NOT
744 This packet MUST NOT be sent as list and the List flag MUST
747 Payload of the packet: See section 2.3.20 Key Agreement Payload
750 26 SILC_PACKET_RESUME_ROUTER
752 This packet is used during backup router protocol when the
753 original primary router of the cell comes back online and wishes
754 to resume the position as being the primary router of the cell.
756 Payload of the packet: See section 2.3.21 Resume Router Payload
761 This packet is used to perform an file transfer protocol in the
762 SILC session with some entity in the network. The packet is
763 multi purpose. The packet is used to tell other entity in the
764 network that the sender wishes to perform an file transfer
765 protocol. The packet is also used to actually tunnel the
766 file transfer protocol stream. The file transfer protocol
767 stream is always protected with the SILC packet.
769 This packet MUST NOT be sent as list and the List flag MUST
772 Payload of the packet: See section 2.3.22 File Transfer Payload
775 28 SILC_PACKET_RESUME_CLIENT
777 This packet is used to resume a client back to the network
778 after it has been detached. A client is able to detach from
779 the network but the client is still valid client in the network.
780 The client may then later resume its session back by sending
781 this packet to a server. Routers also use this packet to notify
782 other routers in the network that the detached client has resumed.
784 This packet MUST NOT be sent as list and the List flag MUST
787 Payload of the packet: See section 2.3.23 Resume Client Payload
792 Currently undefined commands.
797 These packet types are reserved for private use and they will
798 not be defined by this document.
805 This type is reserved for future extensions and currently it
811 2.3.1 SILC Packet Payloads
813 All payloads resides in the main data area of the SILC packet. However
814 all payloads MUST be at the start of the data area after the SILC
815 packet header and padding. All fields in the packet payload are always
816 encrypted, as they reside in the data area of the packet which is
819 Payloads described in this section are common payloads that MUST be
820 accepted anytime during SILC session. Most of the payloads may only
821 be sent with specific packet type which is defined in the description
824 There are a lot of other payloads in the SILC as well. However, they
825 are not common in the sense that they could be sent at any time.
826 These payloads are not described in this section. These are payloads
827 such as SILC Key Exchange payloads and so on. These are described
828 in [SILC1], [SILC3] and [SILC4].
832 2.3.2 Generic payloads
834 This section describes generic payloads that are not associated to any
835 specific packet type. They can be used for example inside some other
842 This payload can be used to send an ID. ID's are variable in length
843 thus this payload provides a way to send variable length ID's.
845 The following diagram represents the ID Payload.
850 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
851 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
852 | ID Type | ID Length |
853 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
857 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
865 o ID Type (2 bytes) - Indicates the type of the ID. See
866 section 2.4 SILC ID Types for list of defined ID types.
868 o ID Length (2 bytes) - Length of the ID Data area not
869 including the length of any other fields in the payload.
871 o ID Data (variable length) - The actual ID data.
876 2.3.2.2 Argument Payload
878 Argument Payload is used to set arguments for any packet payload that
879 needs and supports arguments, such as commands. Number of arguments
880 associated with a packet MUST be indicated by the packet payload which
881 needs the arguments. Argument Payloads MUST always reside right after
882 the packet payload needing the arguments. Incorrect amount of argument
883 payloads MUST cause rejection of the packet.
891 The following diagram represents the Argument Payload.
896 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
897 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
898 | Payload Length | Argument Type | |
899 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
903 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
907 Figure 4: Argument Payload
911 o Payload Length (2 bytes) - Length of the argument payload data
912 area not including the length of any other fields in the
915 o Argument Type (1 byte) - Indicates the type of the argument.
916 Every argument may have a specific type that MUST be defined
917 by the packet payload needing the argument. For example
918 every command specify a number for each argument that maybe
919 associated with the command. By using this number the receiver
920 of the packet knows what type of argument this is. If there is
921 no specific argument type this field is set to zero (0).
923 o Argument Data (variable length) - Argument data.
928 2.3.2.3 Channel Payload
930 Generic Channel Payload may be used to send information about channel,
931 its name, the Channel ID and a mode.
933 The following diagram represents the Channel Payload.
949 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
950 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
951 | Channel Name Length | |
952 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
956 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
957 | Channel ID Length | |
958 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
962 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
964 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
968 Figure 5: New Channel Payload
972 o Channel Name Length (2 bytes) - Length of the channel name
975 o Channel Name (variable length) - The name of the channel.
977 o Channel ID Length (2 bytes) - Length of the Channel ID field.
979 o Channel ID (variable length) - The Channel ID.
981 o Mode Mask (4 bytes) - A mode. This can be the mode of the
982 channel but it can also be the mode of the client on the
983 channel. The contents of this field is dependent of the
984 usage of this payload. The usage is defined separately
985 when this payload is used. This is a 32 bit MSB first value.
990 2.3.2.4 Public Key Payload
992 Generic Public Key Payload may be used to send different types of
993 public keys and certificates.
995 The following diagram represents the Public Key Payload.
1004 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1005 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1006 | Public Key Length | Public Key Type |
1007 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1009 ~ Public Key of the party (or certificate) ~
1011 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1015 Figure 6: Public Key Payload
1019 o Public Key Length (2 bytes) - The length of the Public Key
1020 (or certificate) field, not including any other field.
1022 o Public Key Type (2 bytes) - The public key (or certificate)
1023 type. This field indicates the type of the public key in
1024 the packet. See the [SILC3] for defined public key types.
1026 o Public Key (or certificate) (variable length) - The
1027 public key or certificate.
1032 2.3.3 Disconnect Payload
1034 Disconnect payload is sent upon disconnection. The payload is simple;
1035 reason of disconnection is sent to the disconnected party.
1037 The payload may only be sent with SILC_PACKET_DISCONNECT packet. It
1038 MUST NOT be sent in any other packet type. The following diagram
1039 represents the Disconnect Payload.
1045 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1046 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1050 ~ Disconnect Message ~
1052 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1056 Figure 7: Disconnect Payload
1059 o Status (1 byte) - Indicates the Status Type, defined in [SILC3]
1060 for the reason of disconnection.
1062 o Disconnect Message (variable length) - Human readable UTF-8
1063 encoded string indicating reason of the disconnection. This
1069 2.3.4 Success Payload
1071 Success payload is sent when some protocol execution is successfully
1072 completed. The payload is simple; indication of the success is sent.
1073 This may be any data, including binary or human readable data.
1078 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1079 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1081 ~ Success Indication ~
1083 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1087 Figure 8: Success Payload
1091 o Success Indication (variable length) - Indication of
1092 the success. This may be for example some flag that
1093 indicates the protocol and the success status or human
1094 readable success message. The true length of this
1095 payload is available by calculating it from the SILC
1102 2.3.5 Failure Payload
1104 This is opposite of Success Payload. Indication of failure of
1105 some protocol is sent in the payload.
1111 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1114 ~ Failure Indication ~
1116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1120 Figure 9: Failure Payload
1124 o Failure Indication (variable length) - Indication of
1125 the failure. This may be for example some flag that
1126 indicates the protocol and the failure status or human
1127 readable failure message. The true length of this
1128 payload is available by calculating it from the SILC
1134 2.3.6 Reject Payload
1136 This payload is sent when some protocol is rejected to be executed.
1137 Other operations MAY send this as well that was rejected. The
1138 indication of the rejection is sent in the payload. The indication
1139 may be binary or human readable data.
1145 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1148 ~ Reject Indication ~
1150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1154 Figure 10: Reject Payload
1158 o Reject Indication (variable length) - Indication of
1159 the rejection. This maybe for example some flag that
1160 indicates the protocol and the rejection status or human
1161 readable rejection message. The true length of this
1162 payload is available by calculating it from the SILC
1168 2.3.7 Notify Payload
1170 Notify payload is used to send notify messages. The payload is usually
1171 sent from server to client, however, server MAY send it to another
1172 server as well. This payload MAY also be sent to a channel. Client
1173 MUST NOT send this payload. The receiver of this payload MAY ignore
1174 the contents of the payload, however, notify message SHOULD be audited.
1176 The payload may only be sent with SILC_PACKET_NOTIFY packet. It MUST
1177 not be sent in any other packet type. The following diagram represents
1186 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1188 | Notify Type | Payload Length |
1189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1195 Figure 11: Notify Payload
1199 o Notify Type (2 bytes) - Indicates the type of the notify
1202 o Payload Length (2 bytes) - Length of the entire Notify Payload
1203 including any associated Argument Payloads.
1205 o Argument Nums (2 bytes) - Indicates the number of Argument
1206 Payloads associated to this payload. Notify types may define
1207 arguments to be send along the notify message.
1210 The following list of currently defined notify types. The format for
1211 notify arguments is same as in SILC commands described in [SILC4].
1212 Note that all ID's sent in arguments are sent inside ID Payload. Also
1213 note that all passphrases that may be sent inside arguments MUST be
1214 UTF-8 [RFC2279] encoded.
1217 0 SILC_NOTIFY_TYPE_NONE
1219 If no specific notify type apply for the notify message this type
1223 Arguments: (1) <message>
1225 The <message> is implementation specific free text string.
1226 Receiver MAY ignore this message.
1229 1 SILC_NOTIFY_TYPE_INVITE
1231 Sent when an client is invited to a channel. This is also sent
1232 when the invite list of the channel is changed. This notify type
1233 is sent between routers and if an client was invited, to the
1234 client as well. In this case the packet is destined to the client.
1237 Arguments: (1) <Channel ID> (2) <channel name>
1238 (3) [<sender Client ID>] (4) [<adding client>]
1239 (5) [<removing client>]
1241 The <Channel ID> is the channel. The <channel name> is the name
1242 of the channel and is provided because the client which receives
1243 this notify packet may not have a way to resolve the name of the
1244 channel from the <Channel ID>. The <sender Client ID> is the
1245 Client ID which invited the client to the channel. The <adding
1246 client> and the <removing client> indicates the added or removed
1247 client from the channel's invite list. The format of the <adding
1248 client> and the <removing client> is defined in the [SILC4] with
1249 SILC_COMMAND_INVITE command.
1251 The <adding client> and <removing client> MUST NOT be sent when
1252 the packet is destined to a client.
1255 2 SILC_NOTIFY_TYPE_JOIN
1257 Sent when client has joined to a channel. The server MUST
1258 distribute this type only to the local clients on the channel
1259 and then send it to its primary router. The router or server
1260 receiving the packet distributes this type to the local clients
1261 on the channel and broadcast it to the network.
1264 Arguments: (1) [<Client ID>] (2) <Channel ID>
1266 The <Client ID> is the client that joined to the channel indicated
1267 by the <Channel ID>.
1270 3 SILC_NOTIFY_TYPE_LEAVE
1272 Sent when client has left a channel. The server must distribute
1273 this type only to the local clients on the channel and then send
1274 it to its primary router. The router or server receiving the
1275 packet distributes this type to the local clients on the channel
1276 and broadcast it to the network.
1279 Arguments: (1) <Client ID>
1281 The <Client ID> is the client which left the channel.
1284 4 SILC_NOTIFY_TYPE_SIGNOFF
1286 Sent when client signoff from SILC network. The server MUST
1287 distribute this type only to the local clients on the channel and
1288 then send it to its primary router. The router or server receiving
1289 the packet distributes this type to the local clients on the
1290 channel and broadcast it to the network.
1293 Arguments: (1) <Client ID> (2) <message>
1295 The <Client ID> is the client which left SILC network. The
1296 <message> is free text string indicating the reason of the signoff.
1299 5 SILC_NOTIFY_TYPE_TOPIC_SET
1301 Sent when topic is set/changed on a channel. This type must be
1302 sent only to the clients which is joined on the channel which
1303 topic was set or changed.
1306 Arguments: (1) <ID Payload> (2) <topic>
1308 The <ID Payload> is the ID of the entity who set the topic. It
1309 usually is Client ID but it can be Server ID and Channel ID as well.
1312 6 SILC_NOTIFY_TYPE_NICK_CHANGE
1314 Sent when client changes nick on a channel. The server MUST
1315 distribute this type only to the local clients on the channel
1316 and then send it to its primary router. The router or server
1317 receiving the packet distributes this type to the local clients
1318 on the channel and broadcast it to the network.
1321 Arguments: (1) <Old Client ID> (2) <New Client ID>
1324 The <Old Client ID> is the old ID of the client which changed
1325 the nickname. The <New Client ID> is the new ID generated by
1326 the change of the nickname. The <nickname> is the new nickname.
1327 Note that it is possible to send this notify even if the nickname
1328 hasn't changed, but client ID has changed.
1331 7 SILC_NOTIFY_TYPE_CMODE_CHANGE
1333 Sent when channel mode has changed. This type MUST be sent only
1334 to the clients which is joined on the channel which mode was
1338 Arguments: (1) <ID Payload> (2) <mode mask>
1339 (3) [<cipher>] (4) <[hmac>]
1342 The <ID Payload> is the ID (usually Client ID but it can be
1343 Server ID as well when the router is enforcing channel mode
1344 change) of the entity which changed the mode. The <mode mask>
1345 is the new mode mask of the channel. The client can safely
1346 ignore the <cipher> argument since the SILC_PACKET_CHANNEL_KEY
1347 packet will force the new channel key change anyway. The <hmac>
1348 argument is important since the client is responsible of setting
1349 the new HMAC and the hmac key into use. The <passphrase> is
1350 the passphrase of the channel, if it was now set.
1353 8 SILC_NOTIFY_TYPE_CUMODE_CHANGE
1355 Sent when user mode on channel has changed. This type MUST be
1356 sent only to the clients which is joined on the channel where
1357 the target client is on.
1360 Arguments: (1) <ID Payload> (2) <mode mask>
1361 (3) <Target Client ID>
1363 The <ID Payload> is the ID (usually Client ID but it can be
1364 Server ID as well when the router is enforcing user's mode
1365 change) of the entity which changed the mode. The <mode mask>
1366 is the new mode mask of the channel. The <Target Client ID>
1367 is the client which mode was changed.
1370 9 SILC_NOTIFY_TYPE_MOTD
1372 Sent when Message of the Day (motd) is sent to a client.
1375 Arguments: (1) <motd>
1377 The <motd> is the Message of the Day.
1380 10 SILC_NOTIFY_TYPE_CHANNEL_CHANGE
1382 Sent when channel's ID has changed for a reason or another.
1383 This is sent by normal server to the client. This can also be
1384 sent by router to other server to force the Channel ID change.
1385 The Channel ID MUST be changed to use the new one. When sent
1386 to clients, this type MUST be sent only to the clients which is
1387 joined on the channel.
1390 Arguments: (1) <Old Channel ID> (2) <New Channel ID>
1392 The <Old Channel ID> is the channel's old ID and the <New
1393 Channel ID> is the new one that MUST replace the old one.
1396 11 SILC_NOTIFY_TYPE_SERVER_SIGNOFF
1398 Sent when server quits SILC network. Those clients from this
1399 server that are on channels must be removed from the channel.
1402 Arguments: (1) <Server ID> (n) [<Client ID>] [...]
1404 The <Server ID> is the server's ID. The rest of the arguments
1405 are the Client ID's of the client's which are coming from this
1406 server and are thus quitting the SILC network also. If the
1407 maximum number of arguments are reached another
1408 SILC_NOTIFY_TYPE_SERVER_SIGNOFF notify packet MUST be sent.
1409 When this notify packet is sent between routers the Client ID's
1410 MAY be omitted. Server receiving the Client ID's in the payload
1411 may use them directly to remove the client.
1414 12 SILC_NOTIFY_TYPE_KICKED
1416 Sent when a client has been kicked from a channel. This is
1417 sent also to the client which was kicked from the channel.
1418 The client which was kicked from the channel MUST be removed
1419 from the channel. This notify type is always destined to the
1420 channel. The router or server receiving the packet distributes
1421 this type to the local clients on the channel and broadcast it
1425 Arguments: (1) <Client ID> (2) [<comment>]
1426 (3) <Kicker's Client ID>
1428 The <Client ID> is the client which was kicked from the channel.
1429 The kicker may have set the <comment> to indicate the reason for
1430 the kicking. The <Kicker's Client ID> is the kicker.
1433 13 SILC_NOTIFY_TYPE_KILLED
1435 Sent when a client has been killed from the network. This is sent
1436 also to the client which was killed from the network. The client
1437 which was killed from the network MUST be removed from the network.
1438 This notify type is destined directly to the client which was
1439 killed and to channel if the client is on any channel. The router
1440 or server receiving the packet distributes this type to the local
1441 clients on the channel and broadcast it to the network.
1444 Arguments: (1) <Client ID> (2) [<comment>]
1447 The <Client ID> is the client which was killed from the network.
1448 The killer may have set the <comment> to indicate the reason for
1449 the killing. The <Killer's ID> is the killer, which may be
1450 client but also router server.
1453 14 SILC_NOTIFY_TYPE_UMODE_CHANGE
1455 Sent when user's mode in the SILC changes. This type is sent
1456 only between routers as broadcast packet.
1459 Arguments: (1) <Client ID> (2) <mode mask>
1461 The <Client ID> is the client which mode was changed. The
1462 <mode mask> is the new mode mask.
1465 15 SILC_NOTIFY_TYPE_BAN
1467 Sent when the ban list of the channel is changed. This type is
1468 sent only between routers as broadcast packet.
1471 Arguments: (1) <Channel ID> (2) [<adding client>]
1472 (3) [<removing client>]
1474 The <Channel ID> is the channel which ban list was changed. The
1475 <adding client> is used to indicate that a ban was added and the
1476 <removing client> is used to indicate that a ban was removed from
1477 the ban list. The format of the <adding client> and the
1478 <removing client> is defined in the [SILC4] with SILC_COMMAND_BAN
1482 16 SILC_NOTIFY_TYPE_ERROR
1484 Sent when an error occurs during processing some SILC procedure.
1485 This is not used when error occurs during command processing, see
1486 [SILC3] for more information about commands and command replies.
1487 This type is sent directly to the sender of the packet whose packet
1488 caused the error. See [SILC1] for definition when this type
1492 Arguments: (1) <Status Type> (n) [...]
1494 The <Status Type> is the error type defined in [SILC3]. Note that
1495 same types are also used with command replies to indicate the
1496 status of a command. Both commands and this notify type share
1497 same status types. Rest of the arguments are status type
1498 dependent and are specified with those status types that can be
1499 sent currently inside this notify type in [SILC3]. The <Status
1500 Type> is of size of 1 byte.
1503 17 SILC_NOTIFY_TYPE_WATCH
1505 Sent to indicate change in a watched user. Client can set
1506 nicknames to be watched with SILC_COMMAND_WATCH command, and
1507 receive notifications when they login to network, signoff from
1508 the network or their user mode is changed. This notify type
1509 is used to deliver these notifications. The notify type is
1510 sent directly to the watching client.
1513 Arguments: (1) <Client ID> (2) [<nickname>]
1514 (3) <user mode> (4) [<Notify Type>]
1516 The <Client ID> is the user's Client ID which is being watched,
1517 and the <nickname> is its nickname. If the client just
1518 changed the nickname, then <nickname> is the new nickname.
1519 The <user mode> is the user's current user mode. The <Notify
1520 Type> can be same as the Notify Payload's Notify Type, and is
1521 16 bit MSB first order value. If provided it may indicate the
1522 notify that occurred for the client. If client logged in to the
1523 network the <Notify Type> MUST NOT be present.
1526 Notify types starting from 16384 are reserved for private notify
1529 Router server which receives SILC_NOTIFY_TYPE_SIGNOFF,
1530 SILC_NOTIFY_TYPE_SERVER_SIGNOFF, SILC_NOTIFY_TYPE_KILLED,
1531 SILC_NOTIFY_TYPE_NICK_CHANGE and SILC_NOTIFY_TYPE_UMODE_CHANGE
1532 MUST chech whether someone in the local cell is watching the nickname
1533 the client has, and send the SILC_NOTIFY_TYPE_WATCH notify to the
1534 watcher, unless the client in case has the SILC_UMODE_REJECT_WATCHING
1535 user mode set. If the watcher client and the client that was
1536 watched is same the notify SHOULD NOT be sent.
1542 Error payload is sent upon error. Error may occur in various
1543 conditions when server sends this packet. Client MUST NOT send this
1544 payload but MUST be able to accept it. However, client MAY
1545 totally ignore the contents of the packet as server is going to
1546 take action on the error anyway. However, it is recommended
1547 that the client takes error packet seriously.
1553 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1554 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1558 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1562 Figure 12: Error Payload
1566 o Error Message (variable length) - Human readable error
1572 2.3.9 Channel Message Payload
1574 Channel messages are the most common messages sent in the SILC.
1575 Channel Message Payload is used to send message to channels. These
1576 messages can only be sent if client has joined to some channel.
1577 Even though this packet is the most common in SILC it is still
1578 special packet. Some special handling on sending and reception
1579 of channel message is required.
1581 Padding MUST be applied into this payload since the payload is
1582 encrypted separately from other parts of the packet with the
1583 channel specific key. Hence the requirement of the padding.
1584 The padding SHOULD be random data. The packet MUST be made
1585 multiple by eight (8) or by the block size of the cipher, which
1588 The SILC header in this packet is encrypted with the session key
1589 of the next receiver of the packet. Nothing else is encrypted
1590 with that key. Thus, the actual packet and padding to be
1591 encrypted with the session key is SILC Header plus padding to it
1592 to make it multiple by eight (8) or multiple by the block size
1593 of the cipher, which ever is larger.
1595 Receiver of the the channel message packet is able to determine
1596 the channel the message is destined to by checking the destination
1597 ID from the SILC Packet header which tells the destination channel.
1598 The original sender of the packet is also determined by checking
1599 the source ID from the header which tells the client which sent
1602 The payload may only be sent with SILC_PACKET_CHANNEL_MESSAGE packet.
1603 It MUST NOT be sent in any other packet type. The following diagram
1604 represents the Channel Message Payload.
1606 (*) indicates that the field is not encrypted.
1612 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1613 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1614 | Message Flags | Message Length |
1615 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1619 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1620 | Padding Length | |
1621 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
1625 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1629 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1631 ~ Initial Vector * ~
1633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1637 Figure 13: Channel Message Payload
1641 o Message Flags (2 bytes) - Includes the Message Flags of
1642 the channel messages. The flags can indicate a reason or
1643 purpose for the channel message. Note that the Private
1644 Message Payload use these same Message Flags for the same
1645 purpose. The following Message Flags are defined:
1647 0x0000 SILC_MESSAGE_FLAG_NONE
1649 No specific flags set.
1651 0x0001 SILC_MESSAGE_FLAG_AUTOREPLY
1653 This message is an automatic reply to an earlier
1656 0x0002 SILC_MESSAGE_FLAG_NOREPLY
1658 There should not be reply messages to this
1661 0x0004 SILC_MESSAGE_FLAG_ACTION
1663 The sender is performing an action and the message
1664 is the indication of the action.
1666 0x0008 SILC_MESSAGE_FLAG_NOTICE
1668 The message is for example an informational notice
1671 0x0010 SILC_MESSAGE_FLAG_REQUEST
1673 This is a generic request flag to send request
1674 messages. A separate document should define any
1675 payloads associated to this flag.
1677 0x0020 SILC_MESSAGE_FLAG_SIGNED
1679 This flag indicates that the message is signed
1680 with sender's private key and thus can be verified
1681 by the receiver using the sender's public key. A
1682 separate document should define the detailed procedure
1683 of the signing process and any associated payloads
1686 0x0040 SILC_MESSAGE_FLAG_REPLY
1688 This is a generic reply flag to send a reply to
1689 previously received request. A separate document
1690 should define any payloads associated to this flag.
1692 0x0080 SILC_MESSAGE_FLAG_DATA
1694 This is a generic data flag, indicating that the
1695 message includes some data which can be interpreted
1696 in a specific way. Using this flag any kind of data
1697 can be delivered inside message payload. A separate
1698 document should define how this flag is interpreted
1699 and define any associated payloads.
1701 0x0100 - 0x0800 RESERVED
1703 Reserved for future flags
1705 0x1000 - 0x8000 PRIVATE RANGE
1707 Private range for free use.
1709 o Message Length (2 bytes) - Indicates the length of the
1710 the Message Data field in the payload, not including any
1713 o Message Data (variable length) - The actual message to
1716 o Padding Length (2 bytes) - Indicates the length of the
1717 Padding field in the payload, not including any other
1720 o Padding (variable length) - The padding that MUST be
1721 applied because this payload is encrypted separately from
1722 other parts of the packet.
1724 o MAC (variable length) - The MAC computed from the
1725 Message Length, Message Data, Padding Length, Padding and
1726 Initial Vector fields. This protects the integrity of the
1727 plaintext channel message. The receiver can verify from
1728 the MAC whether the message decrypted correctly. Also, if
1729 more than one private key has been set for the channel, the
1730 receiver can verify which of the keys decrypted the message
1731 correctly. Note that, this field is encrypted and MUST
1732 be added to the padding calculation.
1734 o Initial Vector (variable length) - The initial vector
1735 that has been used in packet encryption. It needs to be
1736 used in the packet decryption as well. What this field
1737 includes is implementation issue. However, it is
1738 RECOMMENDED that it would be random data or, perhaps,
1739 a timestamp. It is NOT RECOMMENDED to use zero (0) as an
1740 initial vector. This field is not encrypted. This field
1741 is not included into the padding calculation. Length
1742 of this field equals the cipher's block size. This field
1743 is, however authenticated.
1748 2.3.10 Channel Key Payload
1750 All traffic in channels are protected by channel specific keys.
1751 Channel Key Payload is used to distribute channel keys to all
1752 clients on the particular channel. Channel keys are sent when
1753 the channel is created, when new user joins to the channel and
1754 whenever a user has left a channel. Server creates the new
1755 channel key and distributes it to the clients by encrypting this
1756 payload with the session key shared between the server and
1757 the client. After that, client starts using the key received
1758 in this payload to protect the traffic on the channel.
1760 The client which is joining to the channel receives its key in the
1761 SILC_COMMAND_JOIN command reply message thus it is not necessary to
1762 send this payload to the entity which sent the SILC_COMMAND_JOIN
1765 Channel keys are cell specific thus every router in the cell have
1766 to create a channel key and distribute it if any client in the
1767 cell has joined to a channel. Channel traffic between cell's
1768 are not encrypted using channel keys, they are encrypted using
1769 normal session keys between two routers. Inside a cell, all
1770 channel traffic is encrypted with the specified channel key.
1771 Channel key should expire periodically, say, in one hour, in
1772 which case new channel key is created and distributed.
1774 The payload may only be sent with SILC_PACKET_CHANNEL_KEY packet.
1775 It MUST NOT be sent in any other packet type. The following diagram
1776 represents the Channel Key Payload.
1782 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1783 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1784 | Channel ID Length | |
1785 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
1789 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1790 | Cipher Name Length | |
1791 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
1795 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1796 | Channel Key Length | |
1797 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
1801 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1805 Figure 14: Channel Key Payload
1810 o Channel ID Length (2 bytes) - Indicates the length of the
1811 Channel ID field in the payload, not including any other
1814 o Channel ID (variable length) - The Channel ID of the
1815 channel this key is meant for.
1817 o Cipher Name Length (2 bytes) - Indicates the length of the
1818 Cipher name field in the payload, not including any other
1821 o Cipher Name (variable length) - Name of the cipher used
1822 in the protection of channel traffic. This name is
1823 initially decided by the creator of the channel but it
1824 MAY change during the life time of the channel as well.
1826 o Channel Key Length (2 bytes) - Indicates the length of the
1827 Channel Key field in the payload, not including any other
1830 o Channel Key (variable length) - The actual channel key
1836 2.3.11 Private Message Payload
1838 Private Message Payload is used to send private message between
1839 two clients (or users for that matter). The messages are sent only
1840 to the specified user and no other user inside SILC network is
1841 able to see the message. The message is protected by the session
1842 key established by the SILC Key Exchange Protocol. However,
1843 it is also possible to agree to use a private key to protect
1844 just the private messages. See section 2.3.11 Private Message
1845 Key Payload for detailed description of how to agree to use
1848 If normal session key is used to protect the message, every server
1849 between the sender client and the receiving client MUST decrypt the
1850 packet and always re-encrypt it with the session key of the next
1851 receiver of the packet. See section Client To Client in [SILC1].
1853 When private key is used to protect the message, servers between
1854 the sender and the receiver needs not to decrypt/re-encrypt the
1855 packet. Section Client To Client in [SILC1] gives example of this
1858 The payload may only be sent with SILC_PACKET_PRIVATE_MESSAGE
1859 packet. It MUST NOT be sent in any other packet type. The following
1860 diagram represents the Private Message Payload.
1872 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1873 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1874 | Message Flags | Message Data Length |
1875 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1879 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1883 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1887 Figure 15: Private Message Payload
1891 o Message Flags (2 bytes) - This field includes the Message
1892 Flags of the private message. They can indicate a different
1893 reason or purpose for the private message. See the section
1894 2.3.9 Channel Message Payload for defined flags. Note that
1895 the Channel Message Payload use the same flags for the
1898 o Message Data Length (2 bytes) - Indicates the length of the
1899 Message Data field, not includes any other field.
1901 o Message Data (variable length) - The actual message to
1902 the client. Rest of the packet is reserved for the message
1905 o Padding (variable length) - This field is present only
1906 when the private message payload is encrypted with private
1907 message key. In this case the padding is applied to make
1908 the payload multiple by eight (8), or by the block size of
1909 the cipher, which ever is larger. When encrypted with
1910 normal session keys, this field MUST NOT be included.
1915 2.3.12 Private Message Key Payload
1917 This payload is optional and can be used to send private message
1918 key between two clients in the network. The packet is secured with
1919 normal session keys. By default private messages are encrypted
1920 with session keys, and with this payload it is possible to set
1921 private key for private message encryption between two clients.
1923 The receiver of this payload SHOULD verify for example from user
1924 whether user wants to receive private message key. Note that there
1925 are other, more secure ways of exchanging private message keys in
1926 the SILC network. Instead of sending this payload it is possible to
1927 negotiate the private message key with SKE protocol using the Key
1928 Agreement payload directly peer to peer.
1930 This payload may only be sent by client to another client. Server
1931 MUST NOT send this payload at any time. After sending this payload
1932 the sender of private messages must set the Private Message Key
1933 flag into SILC Packet Header.
1935 The payload may only be sent with SILC_PACKET_PRIVATE_MESSAGE_KEY
1936 packet. It MUST NOT be sent in any other packet type. The following
1937 diagram represents the Private Message Key Payload.
1943 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1944 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1945 | Private Message Key Length | |
1946 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
1948 ~ Private Message Key ~
1950 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1951 | Cipher Name Length | |
1952 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
1956 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1960 Figure 16: Private Message Key Payload
1966 o Private Message Key Length (2 bytes) - Indicates the length
1967 of the Private Message Key field in the payload, not including
1970 o Private Message Key (variable length) - The actual private
1971 message key material.
1973 o Cipher Name Length (2 bytes) - Indicates the length of the
1974 Cipher Name field in the payload, not including any other
1977 o Cipher Name (variable length) - Name of the cipher to use
1978 in the private message encryption. If this field does not
1979 exist then the default cipher of the SILC protocol is used.
1980 See the [SILC1] for defined ciphers.
1986 2.3.13 Command Payload
1988 Command Payload is used to send SILC commands from client to server.
1989 Also server MAY send commands to other servers. The following diagram
1990 represents the Command Payload.
1996 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1997 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1998 | Payload Length | SILC Command | Arguments Num |
1999 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2000 | Command Identifier |
2001 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2005 Figure 17: Command Payload
2009 o Payload Length (2 bytes) - Length of the entire command
2010 payload including any command argument payloads associated
2013 o SILC Command (1 byte) - Indicates the SILC command. This MUST
2014 be set to non-zero value. If zero (0) value is found in this
2015 field the packet MUST be discarded.
2017 o Arguments Num (1 byte) - Indicates the number of arguments
2018 associated with the command. If there are no arguments this
2019 field is set to zero (0). The arguments MUST follow the
2020 command payload. See section 2.3.2.2 for definition of the
2023 o Command Identifier (2 bytes) - Identifies this command at the
2024 sender's end. The entity which replies to this command MUST
2025 set the value found from this field into the Command Payload
2026 used to send the reply to the sender. This way the sender
2027 can identify which command reply belongs to which originally
2028 sent command. What this field includes is implementation
2029 issue but it is RECOMMENDED that wrapping counter value is
2030 used in the field. Value zero (0) in this field means that
2031 no specific value is set.
2034 See [SILC4] for detailed description of different SILC commands,
2035 their arguments and their reply messages.
2041 2.3.14 Command Reply Payload
2043 Command Reply Payload is used to send replies to the commands. The
2044 Command Reply Payload is identical to the Command Payload thus see
2045 the upper section for the Command Payload specification.
2047 The entity which sends the reply packet MUST set the Command Identifier
2048 field in the reply packet's Command Payload to the value it received
2049 in the original command packet.
2051 See SILC Commands in [SILC4] for detailed description of different
2052 SILC commands, their arguments and their reply messages.
2056 2.3.15 Connection Auth Request Payload
2058 Client MAY send this payload to server to request the authentication
2059 method that must be used in authentication protocol. If client knows
2060 this information beforehand this payload is not necessary to be sent.
2061 Server performing authentication with another server MAY also send
2062 this payload to request the authentication method. If the connecting
2063 server already knows this information this payload is not necessary
2066 Server receiving this request MUST reply with same payload sending
2067 the mandatory authentication method. Algorithms that may be required
2068 to be used by the authentication method are the ones already
2069 established by the SILC Key Exchange protocol. See section Key
2070 Exchange Start Payload in [SILC3] for detailed information.
2072 The payload may only be sent with SILC_PACKET_CONNECTION_AUTH_REQUEST
2073 packet. It MUST NOT be sent in any other packet type. The following
2074 diagram represents the Connection Auth Request Payload.
2080 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2081 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2082 | Connection Type | Authentication Method |
2083 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2087 Figure 18: Connection Auth Request Payload
2091 o Connection Type (2 bytes) - Indicates the type of the
2092 connection. The following connection types are defined:
2099 If any other type is found in this field the packet MUST be
2100 discarded and the authentication MUST be failed.
2102 o Authentication Method (2 bytes) - Indicates the authentication
2103 method to be used in the authentication protocol. The following
2104 authentication methods are defined:
2107 1 password (mandatory)
2108 2 public key (mandatory)
2110 If any other type is found in this field the packet MUST be
2111 discarded and the authentication MUST be failed. If this
2112 payload is sent as request to receive the mandatory
2113 authentication method this field MUST be set to zero (0),
2114 indicating that receiver should send the mandatory
2115 authentication method. The receiver sending this payload
2116 to the requesting party, MAY also set this field to zero (0)
2117 to indicate that authentication is not required. In this
2118 case authentication protocol still MUST be started but
2119 server is most likely to respond with SILC_PACKET_SUCCESS
2125 2.3.16 New ID Payload
2127 New ID Payload is a multipurpose payload. It is used to send newly
2128 created ID's from clients and servers. When client connects to server
2129 and registers itself to the server by sending SILC_PACKET_NEW_CLIENT
2130 packet, server replies with this packet by sending the created ID for
2131 the client. Server always creates the ID for the client.
2133 This payload is also used when server tells its router that new client
2134 has registered to the SILC network. In this case the server sends
2135 the Client ID of the client to the router. Similarly when router
2136 distributes information to other routers about the client in the SILC
2137 network this payload is used.
2139 Also, when server connects to router, router uses this payload to inform
2140 other routers about new server in the SILC network. However, every
2141 server (or router) creates their own ID's thus the ID distributed by
2142 this payload is not created by the distributor in this case. Servers
2143 create their own ID's. Server registers itself to the network by
2144 sending SILC_PACKET_NEW_SERVER to the router it connected to. The case
2145 is same when router connects to another router.
2147 However, this payload MUST NOT be used to send information about new
2148 channels. New channels are always distributed by sending the dedicated
2149 SILC_PACKET_NEW_CHANNEL packet.
2151 Thus, this payload is very important and used every time when some
2152 new entity is registered to the SILC network. Client MUST NOT send this
2153 payload. Both client and server (and router) MAY receive this payload.
2155 The packet uses generic ID Payload as New ID Payload. See section
2156 2.3.2.1 for generic ID Payload.
2160 2.3.17 New Client Payload
2162 When client is connected to the server, keys has been exchanged and
2163 connection has been authenticated client MUST register itself to the
2164 server. Client's first packet after key exchange and authentication
2165 protocols must be SILC_PACKET_NEW_CLIENT. This payload tells server all
2166 the relevant information about the connected user. Server creates a new
2167 client ID for the client when received this payload and sends it to the
2168 client in New ID Payload.
2170 This payload sends username and real name of the user on the remote host
2171 which is connected to the SILC server with SILC client. The server
2172 creates the client ID according the information sent in this payload.
2173 The nickname of the user becomes the username sent in this payload.
2174 However, client should call NICK command after sending this payload to
2175 set the real nickname of the user which is then used to create new
2178 The payload may only be sent with SILC_PACKET_NEW_CLIENT packet. It
2179 MUST NOT be sent in any other packet type. The following diagram
2180 represents the New Client Payload.
2197 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2199 | Username Length | |
2200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
2204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2205 | Real Name Length | |
2206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
2210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2214 Figure 19: New Client Payload
2218 o Username Length (2 bytes) - Length of the Username field.
2220 o Username (variable length) - The username of the user on
2221 the host where connecting to the SILC server.
2223 o Real Name Length (2 bytes) - Length of the Real Name field.
2225 o Real Name (variable length) - The real name of the user
2226 on the host where connecting to the SILC server.
2231 2.3.18 New Server Payload
2233 This payload is sent by server when it has completed successfully both
2234 key exchange and connection authentication protocols. The server
2235 MUST register itself to the SILC Network by sending this payload.
2236 The first packet after these key exchange and authentication protocols
2237 is SILC_PACKET_NEW_SERVER packet. The payload includes the Server ID
2238 of the server that it has created by itself. It also includes a
2239 name of the server that is associated to the Server ID.
2241 The payload may only be sent with SILC_PACKET_NEW_SERVER packet. It
2242 MUST NOT be sent in any other packet type. The following diagram
2243 represents the New Server Payload.
2252 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2254 | Server ID Length | |
2255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
2259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2260 | Server Name Length | |
2261 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
2265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2269 Figure 20: New Server Payload
2273 o Server ID Length (2 bytes) - Length of the Server ID Data
2276 o Server ID Data (variable length) - The actual Server ID
2279 o Server Name Length (2 bytes) - Length of the server name
2282 o Server Name (variable length) - The server name.
2287 2.3.19 New Channel Payload
2289 Information about newly created channel is broadcasted to all routers
2290 in the SILC network by sending this packet payload. Channels are
2291 created by router of the cell. Server never creates channels unless
2292 it is a standalone server and it does not have router connection,
2293 in this case server acts as router. Normal server send JOIN command
2294 to the router (after it has received JOIN command from client) which
2295 then processes the command and creates the channel. Client MUST NOT
2296 send this packet. Server may send this packet to a router when it is
2297 announcing its existing channels to the router after it has connected
2300 The packet uses generic Channel Payload as New Channel Payload. See
2301 section 2.3.2.3 for generic Channel Payload. The Mode Mask field in the
2302 Channel Payload is the mode of the channel.
2306 2.3.20 Key Agreement Payload
2308 This payload is used by clients to request key negotiation between
2309 another client in the SILC Network. The key agreement protocol used
2310 is the SKE protocol. The result of the protocol, the secret key
2311 material, can be used for example as private message key between the
2312 two clients. This significantly adds security as the key agreement
2313 is performed outside the SILC network. The server and router MUST NOT
2316 The sender MAY tell the receiver of this payload the hostname and the
2317 port where the SKE protocol is running in the sender's end. The
2318 receiver MAY then initiate the SKE negotiation with the sender. The
2319 sender MAY also optionally not to include the hostname and the port
2320 of its SKE protocol. In this case the receiver MAY reply to the
2321 request by sending the same payload filled with the receiver's hostname
2322 and the port where the SKE protocol is running. The sender MAY then
2323 initiate the SKE negotiation with the receiver.
2325 This payload may be sent with SILC_PACKET_KEY_AGREEMENT and
2326 SILC_PACKET_FTP packet types. It MUST NOT be sent in any other packet
2327 types. The following diagram represents the Key Agreement Payload.
2333 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2334 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2335 | Hostname Length | |
2336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
2340 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2342 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2346 Figure 21: Key Agreement Payload
2350 o Hostname Length (2 bytes) - Indicates the length of the
2353 o Hostname (variable length) - The hostname or IP address where
2354 the SKE protocol is running. The sender MAY fill this field
2355 when sending the payload. If the receiver sends this payload
2356 as reply to the request it MUST fill this field.
2358 o Port (4 bytes) - The port where the SKE protocol is bound.
2359 The sender MAY fill this field when sending the payload. If
2360 the receiver sends this payload as reply to the request it
2361 MUST fill this field. This is a 32 bit MSB first order value.
2365 After the key material has been received from the SKE protocol it is
2366 processed as the [SILC3] describes. If the key material is used as
2367 channel private key then the Sending Encryption Key, as defined in
2368 [SILC3] is used as the channel private key. Other key material must
2369 be discarded. The [SILC1] defines the way to use the key material if
2370 it is intended to be used as private message keys. Any other use for
2371 the key material is undefined.
2375 2.3.21 Resume Router Payload
2377 The payload may only be sent with SILC_PACKET_RESUME_ROUTER packet. It
2378 MUST NOT be sent in any other packet type. The Following diagram
2379 represents the Resume Router Payload.
2385 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
2386 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2387 | Type | Session ID |
2388 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2392 Figure 22: Resume Router Payload
2396 o Type (1 byte) - Indicates the type of the backup resume
2397 protocol packet. The type values are defined in [SILC1].
2399 o Session ID (1 bytes) - Indicates the session ID for the
2400 backup resume protocol. The sender of the packet sets this
2401 value and the receiver MUST set the same value in subsequent
2407 2.3.22 File Transfer Payload
2409 File Transfer Payload is used to perform file transfer protocol
2410 between two entities in the network. The actual file transfer
2411 protocol is always encapsulated inside the SILC Packet. The actual
2412 data stream is also sent peer to peer outside SILC network.
2414 When an entity, usually a client wishes to perform file transfer
2415 protocol with another client in the network, they perform Key Agreement
2416 protocol as described in the section 2.3.20 Key Agreement Payload and
2417 in [SILC3], inside File Transfer Payload. After the Key Agreement
2418 protocol has been performed the subsequent packets in the data stream
2419 will be protected using the new key material. The actual file transfer
2420 protocol is also initialized in this stage. All file transfer protocol
2421 packets are always encapsulated in the File Transfer Payload and
2422 protected with the negotiated key material.
2424 The payload may only be sent with SILC_PACKET_FTP packet. It MUST NOT
2425 be sent in any other packet type. The following diagram represents the
2426 File Transfer Payload.
2431 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2442 Figure 23: File Transfer Payload
2446 o Type (1 byte) - Indicates the type of the file transfer
2447 protocol. The following file transfer protocols has been
2450 1 SSH File Transfer Protocol (SFTP) (mandatory)
2452 If zero (0) value or any unsupported file transfer protocol
2453 type is found in this field the packet must be discarded.
2454 The currently mandatory file transfer protocol is SFTP.
2455 The SFTP protocol is defined in [SFTP].
2457 o Data (variable length) - Arbitrary file transfer data. The
2458 contents and encoding of this field is dependent of the usage
2459 of this payload and the type of the file transfer protocol.
2460 When this payload is used to perform the Key Agreement
2461 protocol, this field include the Key Agreement Payload,
2462 as defined in the section 2.3.20 Key Agreement Payload.
2463 When this payload is used to send the actual file transfer
2464 protocol data, the encoding is defined in the corresponding
2465 file transfer protocol.
2470 2.3.23 Resume Client Payload
2472 This payload is used by client to resume its detached session in the
2473 SILC Network. A client is able to detach itself from the network by
2474 sending SILC_COMMAND_DETACH command to its server. The network
2475 connection to the client is lost but the client remains as valid
2476 client in the network. The client is able to resume the session back
2477 by sending this packet and including the old Client ID, and an
2478 Authentication Payload [SILC1] which the server uses to verify with
2479 the detached client's public key. This also implies that the
2480 mandatory authentication method is public key authentication.
2482 Server or router that receives this from the client also sends this,
2483 without the Authentication Payload, to routers in the network so that
2484 they know the detached client has resumed. Refer to the [SILC1] for
2485 detailed description how the detaching and resuming prodecure is
2488 The payload may only be sent with SILC_PACKET_RESUME CLIENT packet. It
2489 MUST NOT be sent in any other packet type. The following diagram
2490 represents the Resume Client Payload.
2495 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2496 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2497 | Client ID Length | |
2498 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
2502 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2504 ~ Authentication Payload ~
2506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2510 Figure 24: Resume Client Payload
2514 o Client ID Length (1 byte) - The length of the Client ID
2515 field not including any other field.
2517 o Client ID (variable length) - The detached client's Client
2518 ID. The client that sends this payload must know the Client
2521 o Authentication Payload (variable length) - The authentication
2522 payload that the server will verify with the detached client's
2523 public key. If the server doesn't know the public key, it must
2524 retrieve it for example with SILC_COMMAND_GETKEY command.
2532 ID's are extensively used in the SILC network to associate different
2533 entities. The following ID's has been defined to be used in the SILC
2539 When ever specific ID cannot be used this is used.
2543 Server ID to associate servers. See the format of
2548 Client ID to associate clients. See the format of
2553 Channel ID to associate channels. See the format of
2557 When encoding different IDs into the ID Payload, all fields are always
2558 in MSB first order. The IP address, port, and/or the random number
2559 are encoded in the MSB first order.
2563 2.5 Packet Encryption And Decryption
2565 SILC packets are encrypted almost entirely. Only small part of SILC
2566 header is not encrypted as described in section 5.2 SILC Packet Header.
2567 The SILC Packet header is the first part of a packet to be encrypted
2568 and it is always encrypted with the key of the next receiver of the
2569 packet. The data payload area of the packet is always entirely
2570 encrypted and it is usually encrypted with the next receiver's key.
2571 However, there are some special packet types and packet payloads
2572 that require special encryption process. These special cases are
2573 described in the next sections. First is described the normal packet
2578 2.5.1 Normal Packet Encryption And Decryption
2580 Normal SILC packets are encrypted with the session key of the next
2581 receiver of the packet. The entire SILC Packet header and the packet
2582 data payload is is also encrypted with the same key. Padding of the
2583 packet is also encrypted always with the session key, also in special
2584 cases. Computed MAC of the packet must not be encrypted.
2586 Decryption process in these cases are straightforward. The receiver
2587 of the packet MUST first decrypt the SILC Packet header, or some parts
2588 of it, usually first 16 bytes of it. Then the receiver checks the
2589 packet type from the decrypted part of the header and can determine
2590 how the rest of the packet must be decrypted. If the packet type is
2591 any of the special cases described in the following sections the packet
2592 decryption is special. If the packet type is not among those special
2593 packet types rest of the packet can be decrypted with the same key.
2595 With out a doubt, this sort of decryption processing causes some
2596 overhead to packet decryption, but never the less, is required.
2600 2.5.2 Channel Message Encryption And Decryption
2602 Channel Messages (Channel Message Payload) are always encrypted with
2603 the channel specific key. However, the SILC Packet header is not
2604 encrypted with that key. As in normal case, the header is encrypted
2605 with the key of the next receiver of the packet, who ever that might
2606 be. Note that in this case the encrypted data area is not touched
2607 at all; it MUST NOT be re-encrypted with the session key.
2609 Receiver of a channel message, who ever that is, is REQUIRED to decrypt
2610 the SILC Packet header to be able to even recognize the packet to be as
2611 channel message. This is same procedure as for normal SILC packets.
2612 As the receiver founds the packet to be channel message, rest of the
2613 packet processing is special. Rest of the SILC Packet header is
2614 decrypted with the same session key along with the padding of the
2615 packet. After that the packet is protected with the channel specific
2616 key and thus can be decrypted only if the receiver is the client on
2617 the channel. See section 2.7 Packet Padding Generation for more
2618 information about padding on special packets.
2620 If the receiver of the channel message is router which is routing the
2621 message to another router then it MUST decrypt the Channel Message
2622 payload. Between routers (that is, between cells) channel messages
2623 are protected with session keys shared between the routers. This
2624 causes another special packet processing for channel messages. If
2625 the channel message is received from another router then the entire
2626 packet, including Channel Message payload, MUST be encrypted with the
2627 session key shared between the routers. In this case the packet
2628 decryption process is as with normal SILC packets. Hence, if the
2629 router is sending channel message to another router the Channel
2630 Message payload MUST have been decrypted and MUST be re-encrypted
2631 with the session key shared between the another router. In this
2632 case the packet encryption is as with any normal SILC packet.
2634 It must be noted that this is only when the channel messages are sent
2635 from router to another router. In all other cases the channel
2636 message encryption and decryption is as described above. This
2637 different processing of channel messages with router to router
2638 connection is because channel keys are cell specific. All cells have
2639 their own channel keys thus the channel message traveling from one
2640 cell to another MUST be protected as it would be any normal SILC
2643 If the SILC_CMODE_PRIVKEY channel mode has been set for the channel
2644 then the router cannot decrypt the packet as it does not know the
2645 private key. In this case the entire packet MUST be encrypted with
2646 the session key and sent to the router. The router receiving the
2647 packet MUST check the channel mode and decrypt the packet accordingly.
2651 2.5.3 Private Message Encryption And Decryption
2653 By default, private message in SILC are protected by session keys.
2654 In this case the private message encryption and decryption process is
2655 equivalent to normal packet encryption and decryption.
2657 However, private messages MAY be protected with private message key
2658 which causes the packet to be special packet. The procedure in this
2659 case is very much alike to channel packets. The actual private message
2660 is encrypted with the private message key and other parts of the
2661 packet is encrypted with the session key. See 2.7 Packet Padding
2662 Generation for more information about padding on special packets.
2664 The difference from channel message processing is that server or router
2665 en route never decrypts the actual private message, as it does not
2666 have the key to do that. Thus, when sending packets between router
2667 the processing is same as in any other case as well; the packet's header
2668 and padding is protected by the session key and the data area is not
2671 The true receiver of the private message, client, that is, is able
2672 to decrypt the private message as it shares the key with the sender
2677 2.6 Packet MAC Generation
2679 Data integrity of a packet is protected by including a message
2680 authentication code (MAC) at the end of the packet. The MAC is computed
2681 from shared secret MAC key, that is established by the SILC Key Exchange
2682 protocol, from packet sequence number, and from the original contents
2683 of the packet. The MAC is always computed before the packet is
2684 encrypted, although after it is compressed if compression is used.
2686 The MAC is computed from entire packet. Every bit of data in the packet,
2687 including SILC Packet Header is used in the MAC computing. This way
2688 the entire packet becomes authenticated.
2690 If the packet is special packet MAC is computed from the entire packet
2691 but part of the packet may be encrypted before the MAC is computed.
2692 This is case, for example, with channel messages where the message data
2693 is encrypted with key that server may not now. In this case the MAC
2694 has been computed from the encrypted data.
2696 Hence, packet's MAC generation is as follows:
2698 mac = MAC(key, sequence number | SILC packet)
2700 The MAC key is negotiated during the SKE protocol. The sequence number
2701 is a 32 bit MSB first value starting from zero for first packet and
2702 increasing for subsequent packets, finally wrapping after 2^32 packets.
2703 The value is never reset, not even after rekey has been performed. Note
2704 that the sequence number is incremented only when MAC is computed for a
2705 packet. If packet is not encrypted and MAC is not computed then the
2706 sequence number is not incremented. Hence, the sequence number is zero
2707 for first encrypted packet.
2709 See [SILC1] for defined and allowed MAC algorithms.
2713 2.7 Packet Padding Generation
2715 Padding is needed in the packet because the packet is encrypted. It
2716 MUST always be multiple by eight (8) or multiple by the block size
2717 of the cipher, which ever is larger. The padding is always encrypted.
2719 For normal packets the padding is added after the SILC Packet Header
2720 and between the Data Payload area. The padding for normal packets
2721 may be calculated as follows:
2724 padding length = 16 - (packet_length mod block_size)
2727 The `block_size' is the block size of the cipher. The maximum padding
2728 length is 128 bytes, and minimum is 1 byte. The above algorithm calculates
2729 the padding to the next block size, and always returns the padding
2730 length between 1 - 16 bytes. However, implementations may add padding
2731 up to 128 bytes. For example packets that include a passphrase or a
2732 password for authentication purposes SHOULD pad the packet up to the
2733 maximum padding length.
2735 For special packets the padding calculation is different as special
2736 packets may be encrypted differently. In these cases the encrypted
2737 data area MUST already be multiple by the block size thus in this case
2738 the padding is calculated only for SILC Packet Header, not for any
2739 other area of the packet. The same algorithm works in this case as
2740 well, except that the `packet length' is now the SILC Packet Header
2743 The padding MUST be random data, preferably, generated by
2744 cryptographically strong random number generator.
2748 2.8 Packet Compression
2750 SILC Packets MAY be compressed. In this case the data payload area
2751 is compressed and all other areas of the packet MUST remain as they
2752 are. After compression is performed for the data area, the length
2753 field of Packet Header MUST be set to the compressed length of the
2756 The compression MUST always be applied before encryption. When
2757 the packet is received and decrypted the data area MUST be decompressed.
2758 Note that the true sender of the packet MUST apply the compression and
2759 the true receiver of the packet MUST apply the decompression. Any
2760 server or router en route MUST NOT decompress the packet.
2766 The sender of the packet MUST assemble the SILC Packet Header with
2767 correct values. It MUST set the Source ID of the header as its own
2768 ID, unless it is forwarding the packet. It MUST also set the Destination
2769 ID of the header to the true destination. If the destination is client
2770 it will be Client ID, if it is server it will be Server ID and if it is
2771 channel it will be Channel ID.
2773 If the sender wants to compress the packet it MUST apply the
2774 compression now. Sender MUST also compute the padding as described
2775 in above sections. Then sender MUST compute the MAC of the packet.
2777 Then sender MUST encrypt the packet as has been described in above
2778 sections according whether the packet is normal packet or special
2779 packet. The computed MAC MUST NOT be encrypted.
2783 2.10 Packet Reception
2785 On packet reception the receiver MUST check that all fields in the
2786 SILC Packet Header are valid. It MUST check the flags of the
2787 header and act accordingly. It MUST also check the MAC of the packet
2788 and if it is to be failed the packet MUST be discarded. Also if the
2789 header of the packet includes any bad fields the packet MUST be
2792 See above sections on the decryption process of the received packet.
2794 The receiver MUST also check that the ID's in the header are valid
2795 ID's. Unsupported ID types or malformed ID's MUST cause packet
2796 rejection. The padding on the reception is always ignored.
2798 The receiver MUST also check the packet type and start parsing the
2799 packet according to the type. However, note the above sections on
2800 special packet types and their parsing.
2806 Routers are the primary entities in the SILC network that takes care
2807 of packet routing. However, normal servers routes packets as well, for
2808 example, when they are routing channel message to the local clients.
2809 Routing is quite simple as every packet tells the true origin and the
2810 true destination of the packet.
2812 It is still RECOMMENDED for routers that has several routing connections
2813 to create route cache for those destinations that has faster route than
2814 the router's primary route. This information is available for the router
2815 when other router connects to the router. The connecting party then
2816 sends all of its locally connected clients, servers and channels. These
2817 informations helps to create the route cache. Also, when new channels
2818 are created to a cell its information is broadcasted to all routers
2819 in the network. Channel ID's are based on router's ID thus it is easy
2820 to create route cache based on these informations. If faster route for
2821 destination does not exist in router's route cache the packet MUST be
2822 routed to the primary route (default route).
2824 However, there are some issues when routing channel messages to group
2825 of users. Routers are responsible of routing the channel message to
2826 other routers, local servers and local clients as well. Routers MUST
2827 send the channel message to only one router in the network, preferrably
2828 to the shortest route to reach the channel users. The message can be
2829 routed into either upstream or downstream. After the message is sent
2830 to a router in the network it MUST NOT be sent to any other router in
2831 either same route or other route. The message MUST NOT be routed to
2832 the router it came from.
2834 When routing for example private messages they should be routed to the
2835 shortest route always to reach the destination client as fast as possible.
2837 For server which receives a packet to be routed to its locally connected
2838 client the server MUST check whether the particular packet type is
2839 allowed to be routed to the client. Not all packets may be sent by
2840 some odd entity to client that is indirectly connected to the sender.
2841 See section 2.3 SILC Packet Types and paragraph about indirectly connected
2842 entities and sending packets to them. The section mentions the packets
2843 that may be sent to indirectly connected entities. It is clear that
2844 server cannot send, for example, disconnect packet to client that is not
2845 directly connected to the server.
2847 Routers form a ring in the SILC network. However, routers may have other
2848 direct connections to other routers in the network too. This can cause
2849 interesting routing problems in the network. Since the network is a ring,
2850 the packets usually should be routed into clock-wise direction, or if it
2851 cannot be used then always counter clock-wise (primary route) direction.
2852 Problems may arise when a faster direct route exists and router is routing
2853 a channel message. Currently channel messages must be routed either
2854 in upstream or downstream, they cannot be routed to other direct routes.
2855 The SILC protocol should have a shortest path discovery protocol, and some
2856 existing routing protocol, that can handle a ring network with other
2857 direct routes inside the ring (so called hybrid ring-mesh topology),
2858 MAY be defined to be used with the SILC protocol. Additional
2859 specifications MAY be written on the subject to permeate this
2864 2.12 Packet Broadcasting
2866 SILC packets MAY be broadcasted in SILC network. However, only router
2867 server may send or receive broadcast packets. Client and normal server
2868 MUST NOT send broadcast packets and they MUST ignore broadcast packets
2869 if they receive them. Broadcast packets are sent by setting Broadcast
2870 flag to the SILC packet header.
2872 Broadcasting packets means that the packet is sent to all routers in
2873 the SILC network, except to the router that sent the packet. The router
2874 receiving broadcast packet MUST send the packet to its primary route.
2875 The fact that SILC routers may have several router connections can
2876 cause problems, such as race conditions inside the SILC network, if
2877 care is not taken when broadcasting packets. Router MUST NOT send
2878 the broadcast packet to any other route except to its primary route.
2880 If the primary route of the router is the original sender of the packet
2881 the packet MUST NOT be sent to the primary route. This may happen
2882 if router has several router connections and some other router uses
2883 the router as its primary route.
2885 Routers use broadcast packets to broadcast for example information
2886 about newly registered clients, servers, channels etc. so that all the
2887 routers may keep these informations up to date.
2891 3 Security Considerations
2893 Security is central to the design of this protocol, and these security
2894 considerations permeate the specification. Common security considerations
2895 such as keeping private keys truly private and using adequate lengths for
2896 symmetric and asymmetric keys must be followed in order to maintain the
2897 security of this protocol.
2903 [SILC1] Riikonen, P., "Secure Internet Live Conferencing (SILC),
2904 Protocol Specification", Internet Draft, April 2001.
2906 [SILC3] Riikonen, P., "SILC Key Exchange and Authentication
2907 Protocols", Internet Draft, April 2001.
2909 [SILC4] Riikonen, P., "SILC Commands", Internet Draft, April 2001.
2911 [IRC] Oikarinen, J., and Reed D., "Internet Relay Chat Protocol",
2914 [IRC-ARCH] Kalt, C., "Internet Relay Chat: Architecture", RFC 2810,
2917 [IRC-CHAN] Kalt, C., "Internet Relay Chat: Channel Management", RFC
2920 [IRC-CLIENT] Kalt, C., "Internet Relay Chat: Client Protocol", RFC
2923 [IRC-SERVER] Kalt, C., "Internet Relay Chat: Server Protocol", RFC
2926 [SSH-TRANS] Ylonen, T., et al, "SSH Transport Layer Protocol",
2929 [PGP] Callas, J., et al, "OpenPGP Message Format", RFC 2440,
2932 [SPKI] Ellison C., et al, "SPKI Certificate Theory", RFC 2693,
2935 [PKIX-Part1] Housley, R., et al, "Internet X.509 Public Key
2936 Infrastructure, Certificate and CRL Profile", RFC 2459,
2939 [Schneier] Schneier, B., "Applied Cryptography Second Edition",
2940 John Wiley & Sons, New York, NY, 1996.
2942 [Menezes] Menezes, A., et al, "Handbook of Applied Cryptography",
2945 [OAKLEY] Orman, H., "The OAKLEY Key Determination Protocol",
2946 RFC 2412, November 1998.
2948 [ISAKMP] Maughan D., et al, "Internet Security Association and
2949 Key Management Protocol (ISAKMP)", RFC 2408, November
2952 [IKE] Harkins D., and Carrel D., "The Internet Key Exchange
2953 (IKE)", RFC 2409, November 1998.
2955 [HMAC] Krawczyk, H., "HMAC: Keyed-Hashing for Message
2956 Authentication", RFC 2104, February 1997.
2958 [PKCS1] Kalinski, B., and Staddon, J., "PKCS #1 RSA Cryptography
2959 Specifications, Version 2.0", RFC 2437, October 1998.
2961 [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
2962 Requirement Levels", BCP 14, RFC 2119, March 1997.
2964 [SFTP] Ylonen T., and Lehtinen S., "Secure Shell File Transfer
2965 Protocol", Internet Draft, March 2001.
2967 [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO
2968 10646", RFC 2279, January 1998.
2975 Snellmanninkatu 34 A 15
2979 EMail: priikone@iki.fi
2981 This Internet-Draft expires XXX