.ds RF FORMFEED[Page %]
.ds CF
.ds LH Internet Draft
-.ds RH 13 September 2000
+.ds RH 6 October 2000
.ds CH
.na
.hy 0
.nf
Network Working Group P. Riikonen
Internet-Draft
-draft-riikonen-silc-pp-01.txt 13 September 2000
-Expires: 13 May 2001
+draft-riikonen-silc-pp-01.txt 6 October 2000
+Expires: 6 Jun 2001
.in 3
2.2 SILC Packet Header ........................................ 5
2.3 SILC Packet Types ......................................... 7
2.3.1 SILC Packet Payloads ................................ 15
- 2.3.2 Generic paylods .....................................
- 2.3.2.1 ID Payload ..................................
- 2.3.2.2 Argument Payload ............................
- 2.3.3 Disconnect Payload .................................. 15
- 2.3.4 Success Payload ..................................... 16
- 2.3.5 Failure Payload ..................................... 16
- 2.3.6 Reject Payload ...................................... 17
- 2.3.7 Notify Payload ...................................... 17
- 2.3.8 Error Payload ....................................... 18
- 2.3.9 Channel Message Payload ............................. 19
- 2.3.10 Channel Key Payload ................................ 20
- 2.3.11 Private Message Payload ............................ 23
- 2.3.12 Private Message Key Payload ........................ 24
- 2.3.13 Command Payload .................................... 25
- 2.3.14 Command Reply Payload .............................. 26
- 2.3.15 Connection Auth Request Payload .................... 27
- 2.3.16 New ID Payload ..................................... 28
- 2.3.17 New ID List Payload ................................ 29
- 2.3.18 New Client Payload ................................. 29
- 2.3.19 New Server Payload ................................. 31
- 2.3.20 New Channel Payload ................................ 31
- 2.3.21 New Channel User Payload ........................... 32
- 2.3.22 New Channel List Payload ........................... 33
- 2.3.23 New Channel User List Payload ...................... 34
- 2.3.24 Replace ID Payload ................................. 34
- 2.3.25 Remove ID Payload .................................. 35
- 2.3.26 Remove Channel User Payload ........................
- 2.4 SILC ID Types ............................................. 36
- 2.5 Packet Encryption And Decryption .......................... 37
- 2.5.1 Normal Packet Encryption And Decryption ............. 37
- 2.5.2 Channel Message Encryption And Decryption ........... 37
- 2.5.3 Private Message Encryption And Decryption ........... 38
- 2.6 Packet MAC Generation ..................................... 39
- 2.7 Packet Padding Generation ................................. 39
- 2.8 Packet Compression ........................................ 40
- 2.9 Packet Sending ............................................ 40
- 2.10 Packet Reception ......................................... 41
- 2.11 Packet Routing ........................................... 42
- 2.12 Packet Forwarding ........................................
- 2.13 Packet Broadcasting ...................................... 41
- 2.14 Packet Tunneling ......................................... 42
-3 Security Considerations ....................................... 43
-4 References .................................................... 43
-5 Author's Address .............................................. 44
+ 2.3.2 Generic payloads .................................... 16
+ 2.3.2.1 ID Payload .................................. 16
+ 2.3.2.2 Argument Payload ............................ 16
+ 2.3.3 Disconnect Payload .................................. 17
+ 2.3.4 Success Payload ..................................... 18
+ 2.3.5 Failure Payload ..................................... 18
+ 2.3.6 Reject Payload ...................................... 19
+ 2.3.7 Notify Payload ...................................... 20
+ 2.3.8 Error Payload ....................................... 21
+ 2.3.9 Channel Message Payload ............................. 22
+ 2.3.10 Channel Key Payload ................................ 24
+ 2.3.11 Private Message Payload ............................ 26
+ 2.3.12 Private Message Key Payload ........................ 27
+ 2.3.13 Command Payload .................................... 28
+ 2.3.14 Command Reply Payload .............................. 29
+ 2.3.15 Connection Auth Request Payload .................... 29
+ 2.3.16 New ID Payload ..................................... 30
+ 2.3.17 New ID List Payload ................................ 31
+ 2.3.18 New Client Payload ................................. 31
+ 2.3.19 New Server Payload ................................. 32
+ 2.3.20 New Channel Payload ................................ 33
+ 2.3.21 New Channel User Payload ........................... 34
+ 2.3.22 New Channel List Payload ........................... 35
+ 2.3.23 New Channel User List Payload ...................... 36
+ 2.3.24 Replace ID Payload ................................. 36
+ 2.3.25 Remove ID Payload .................................. 37
+ 2.3.26 Remove Channel User Payload ........................ 38
+ 2.4 SILC ID Types ............................................. 39
+ 2.5 Packet Encryption And Decryption .......................... 39
+ 2.5.1 Normal Packet Encryption And Decryption ............. 39
+ 2.5.2 Channel Message Encryption And Decryption ........... 40
+ 2.5.3 Private Message Encryption And Decryption ........... 41
+ 2.6 Packet MAC Generation ..................................... 41
+ 2.7 Packet Padding Generation ................................. 42
+ 2.8 Packet Compression ........................................ 42
+ 2.9 Packet Sending ............................................ 43
+ 2.10 Packet Reception ......................................... 43
+ 2.11 Packet Routing ........................................... 44
+ 2.12 Packet Forwarding ........................................ 44
+ 2.13 Packet Broadcasting ...................................... 45
+ 2.14 Packet Tunneling ......................................... 45
+3 Security Considerations ....................................... 46
+4 References .................................................... 46
+5 Author's Address .............................................. 47
.ti 0
List of Figures
.nf
Figure 1: Typical SILC Packet
Figure 2: SILC Packet Header
-Figure 3: Disconnect Payload
-Figure 4: Success Payload
-Figure 5: Failure Payload
-Figure 6: Reject Payload
-Figure 7: Notify Payload
-Figure 8: Error Payload
-Figure 9: Channel Message Payload
-Figure 10: Channel Key Payload
-Figure 11: Private Message Payload
-Figure 12: Private Message Key Payload
-Figure 13: Command Payload
-Figure 15: Connection Auth Request Payload
-Figure 16: New ID Payload
+Figure 3: ID Payload
+Figure 4: Argument Payload
+Figure 5: Disconnect Payload
+Figure 6: Success Payload
+Figure 7: Failure Payload
+Figure 8: Reject Payload
+Figure 9: Notify Payload
+Figure 10: Error Payload
+Figure 11: Channel Message Payload
+Figure 12: Channel Key Payload
+Figure 13: Private Message Payload
+Figure 14: Private Message Key Payload
+Figure 15: Command Payload
+Figure 16: Connection Auth Request Payload
Figure 17: New Client Payload
Figure 18: New Server Payload
Figure 19: New Channel Payload
Figure 20: New Channel User Payload
Figure 21: Replace ID Payload
-Figure 22: Remove ID Payload
-Figure 23: Remove Channel User Payload
+Figure 22: Remove Channel User Payload
.ti 0
.in 5
.nf
- 1 2 3
+ 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Payload Length * | Flags | Packet Type |
Following flags are reserved for this field:
-
-
No flags 0x00
In this case the field is ignored.
packet types may be forwarded. Receiver of packet
with this flag set must not forward the packet any
further. See section 2.12 Packet Forwarding for
- desribtion of packet forwarding.
+ description of packet forwarding.
Broadcast 0x04
Source ID field in the header, not including this or any
other fields.
-
-
o Destination ID Length (2 bytes) - Indicates the length of the
Destination ID field in the header, not including this or
any other fields.
the disconnection is sent inside the packet payload. Client
usually does not send this packet.
- Payload of the packet: See section 2.3.2 Disconnect Payload
+ Payload of the packet: See section 2.3.3 Disconnect Payload
2 SILC_PACKET_SUCCESS
This packet is sent upon successful execution of some protocol.
The status of the success is sent in the packet.
- Payload of the packet: See section 2.3.3 Success Payload
+ Payload of the packet: See section 2.3.4 Success Payload
3 SILC_PACKET_FAILURE
This packet is sent upon failure of some protocol. The status
of the failure is sent in the packet.
- Payload of the packet: See section 2.3.4 Failure Payload
+ Payload of the packet: See section 2.3.5 Failure Payload
4 SILC_PACKET_REJECT
This packet may be sent upon rejection of some protocol.
The status of the rejection is sent in the packet.
- Payload of the packet: See section 2.3.5 Reject Payload
+ Payload of the packet: See section 2.3.6 Reject Payload
5 SILC_PACKET_NOTIFY
server to client, although it may be sent from server to another
server as well. Client never sends this packet. Server may
send this packet to channel as well when the packet is
- distributed to all clients on the channel. Receiver of this
- packet may ignore the packet if it chooses so. However, it
- should not be ignored.
+ distributed to all clients on the channel.
- Payload of the packet: See section 2.3.6 Notify Payload.
+ Payload of the packet: See section 2.3.7 Notify Payload.
6 SILC_PACKET_ERROR
most likely to take action anyway. This packet may be sent
to entity that is indirectly connected to the sender.
- Payload of the packet: See section 2.3.7 Error Payload.
+ Payload of the packet: See section 2.3.8 Error Payload.
7 SILC_PACKET_CHANNEL_MESSAGE
by channel specific keys. Channel Keys are distributed by
SILC_PACKET_CHANNEL_KEY packet.
- Payload of the packet: See section 2.3.8 Channel Message
+ Payload of the packet: See section 2.3.9 Channel Message
Payload
may send this packet. This packet may be sent to entity
that is indirectly connected to the sender.
- Payload of the packet: See section 2.3.9 Channel Key Payload
+ Payload of the packet: See section 2.3.10 Channel Key Payload
9 SILC_PACKET_PRIVATE_MESSAGE
used as well if both of the client knows it, however, it needs
to be agreed outside SILC. See more of this in [SILC1].
- Payload of the packet: See section 2.3.10 Private Message
+ Payload of the packet: See section 2.3.11 Private Message
Payload
default or to use normal session keys by default, is
implementation specific issue. See more of this in [SILC1].
- Payload of the packet: See section 2.3.11 Private Message
+ Payload of the packet: See section 2.3.12 Private Message
Key Payload
This packet may be sent to entity that is indirectly connected
to the sender.
- Payload of the packet: See section 2.3.12 Command Payload
+ Payload of the packet: See section 2.3.13 Command Payload
12 SILC_PACKET_COMMAND_REPLY
The contents of this packet is command specific. This packet
maybe sent to entity that is indirectly connected to the sender.
- Payload of the packet: See section 2.3.13 Command Reply
- Payload and section 2.3.12 Command
+ Payload of the packet: See section 2.3.14 Command Reply
+ Payload and section 2.3.13 Command
Payload
The party receiving this payload must respond with the same
packet including the mandatory authentication method.
- Payload of the packet: See section 2.3.14 Connection Auth
+ Payload of the packet: See section 2.3.15 Connection Auth
Request Payload
distributed by this packet. Only server may send this packet,
however, client must be able to receive this packet.
- Payload of the packet: See section 2.3.15 New ID Payload
+ Payload of the packet: See section 2.3.16 New ID Payload
19 SILC_PACKET_NEW_ID_LIST
type except that it may include several ID's. Client must
not send this packet.
- Payload of the packet: See section 2.3.16 New ID List
+ Payload of the packet: See section 2.3.17 New ID List
Payload
authentication protocols has been completed. Client sends
various information about itself in this packet.
- Payload of the packet: See section 2.3.17 New Client Payload
+ Payload of the packet: See section 2.3.18 New Client Payload
21 SILC_PACKET_NEW_SERVER
its Server ID and other information in this packet.
Client must not send or receive this packet.
- Payload of the packet: See section 2.3.18 New Server Payload
+ Payload of the packet: See section 2.3.19 New Server Payload
22 SILC_PACKET_NEW_CHANNEL
packet maybe sent to entity that is indirectly connected to
the sender.
+ When received, the server or router must distribute
+ SILC_NOTIFY_TYPE_JOIN to local clients on the channel.
+
Payload of the packet: See section 2.3.21 New Channel User
Payload
packet SILC_PACKET_NEW_CHANNEL_USER except that it may
include several payloads. Client must not send this packet.
+ When received, the server or router must distribute
+ SILC_NOTIFY_TYPE_JOIN to local clients on the channel.
+
Payload of the packet: See section 2.3.23 New Channel User
List Payload
packet. This packet maybe sent to entity that is indirectly
connected to the sender.
+ When received and the replaced ID is Client ID the server or
+ router must distribute SILC_NOTIFY_TYPE_NICK_CHANGE to the
+ local clients on the channels (if any) of the client whose
+ ID was changed. However, the notify type must be sent only
+ once per client.
+
Payload of the packet: See section 2.3.24 Replace ID Payload
this packet. This packet maybe sent to entity that is
indirectly connected to the sender.
+ When received and the replaced ID is Client ID the server or
+ router must distribute SILC_NOTIFY_TYPE_SIGNOFF to the
+ local clients on the channels (if any) of the client whose
+ ID was changed. However, the notify type must be sent only
+ once per client.
+
Payload of the packet: See section 2.3.25 Remove ID Payload
This packet is used to remove user from a channel. This is
used by router to notify other routers in the network that a
- client has leaved a channel. This packet maybe sent to entity
+ client has left a channel. This packet maybe sent to entity
that is indirectly connected to the sender.
+ When received, the server or router must distribute
+ SILC_NOTIFY_TYPE_LEAVEW to local clients on the channel.
+
Payload of the packet: See section 2.3.26 Remove Channel User
Payload
not have a payload.
- 31 - 254
+ 31 - 199
Currently undefined commands.
+ 200 - 254
+
+ These packet types are reserved for private use and they will not
+ be defined by this document.
+
+
255 SILC_PACKET_MAX
This type is reserved for future extensions and currently it
.ti 0
-2.3.2 Generic paylods
+2.3.2 Generic payloads
-This sections describes generic payloads that are not associated to any
+This section describes generic payloads that are not associated to any
specific packet type. They can be used for example inside some other
packet payloads.
the Disconnect Payload.
+
+
+
+
+
.in 5
.nf
1 2 3
.in 3
.ce
-Figure 3: Disconnect Payload
+Figure 5: Disconnect Payload
.in 3
.ce
-Figure 4: Success Payload
+Figure 6: Success Payload
.in 6
.in 3
.ce
-Figure 5: Failure Payload
+Figure 7: Failure Payload
.in 6
.in 3
.ce
-Figure 6: Reject Payload
+Figure 8: Reject Payload
.in 6
Notify payload is used to send notify messages. The payload is usually
sent from server to client, however, server may send it to another
-server as well. Client must not send this payload. The receiver of
-this payload may totally ignore the contents of the payload, however,
-notify message should be noted and possibly logged.
+server as well. This payload may also be sent to a channel. Client must
+not send this payload. The receiver of this payload may totally ignore the
+contents of the payload, however, notify message should be noted and
+possibly logged.
The payload may only be sent with SILC_PACKET_NOTIFY packet. It must
not be sent in any other packet type. Following diagram represents the
1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-| Notify Type | Argument Nums | |
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
-| |
-~ Notify Message ~
-| |
+| Notify Type | Payload Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+| Argument Nums |
++-+-+-+-+-+-+-+-+
.in 3
.ce
-Figure 7: Notify Payload
+Figure 9: Notify Payload
.in 6
o Notify Type (2 bytes) - Indicates the type of the notify
message.
+o Payload Length (2 bytes) - Length of the entire Notify Payload
+ including any associated Argument Payloads.
+
o Argument Nums (2 bytes) - Indicates the number of Argument
Payloads associated to this payload. Notify types may define
arguments to be send along the notify message.
-
-o Notify Message (variable length) - Human readable notify
- message. The format of this message is implementation specific.
- The message can be for example "%s has joined channel %s".
.in 3
-Following notify types has been defined:
+Following list of currently defined notify types. The format for notify
+arguments is same as in SILC commands described in [SILC1]. Also, all
+ID's sent in arguments are sent inside ID Payload.
.in 6
0 SILC_NOTIFY_TYPE_NONE
- If no specific notify type apply for the notify
- message this type may be used.
+ If no specific notify type apply for the notify message this type
+ may be used.
+
+ Max Arguments: 1
+ Arguments: (1) <message>
+
+ The <message> is implementation specific free text string. Receiver
+ may ignore this message.
- No arguments associated to this type.
1 SILC_NOTIFY_TYPE_INVITE
- Sent when receiver has been invited to a channel.
+ Sent when receiver has been invited to a channel. This type must be
+ sent directly to the invited client.
+
+ Max Arguments: 2
+ Arguments: (1) <Client ID> (2) <Channel ID>
+
+ The <Client ID> is the client who invites the receiver of this type
+ to channel indicated by <Channel ID>.
- This type includes three arguments: nickname and channel name.
2 SILC_NOTIFY_TYPE_JOIN
- Sent when client has joined to a channel.
+ Sent when client has joined to a channel. The server must distribute
+ this type only to the local clients on the channel and then send
+ SILC_PACKET_NEW_CHANNEL_USER packet to its primary route. The router
+ or server receiving the packet distributes this type to the local
+ clients on the channel. See description of SILC_PACKET_NEW_CHANNEL_USER
+ packet for more information.
+
+ Max Arguments: 1
+ Arguments: (1) <Client ID>
+
+ The <Client ID> is the client that joined to the channel.
- This type includes six arguments: Client ID, nickname, username,
- hostname, Channel ID and channel name. The Client ID and Channel ID
- are sent inside ID Payload.
3 SILC_NOTIFY_TYPE_LEAVE
- Sent when client has left a channel.
+ Sent when client has left a channel. The server must distribute
+ this type only to the local clients on the channel and then send
+ SILC_PACKET_REMOVE_CHANNEL_USER packet to its primary route. The
+ router or server receiving the packet distributes this type to the
+ local clients on the channel. See description of
+ SILC_PACKET_REMOVE_CHANNEL_USER packet for more information.
+
+ Max Arguments: 1
+ Arguments: (1) <Client ID>
+
+ The <Client ID> is the client who left the channel.
- This type includes three arguments: nickname, server name,
- Channel ID and channel name. The Channel ID is sent inside ID
- Payload.
4 SILC_NOTIFY_TYPE_SIGNOFF
- Sent when client signoffs from SILC network.
+ Sent when client signoffs from SILC network. This type is sent only
+ if the client was joined to any channel. This type is sent by server
+ or router when SILC_PACKET_REMOVE_ID packet has been received. See
+ detailed information from description of SILC_PACKET_REMOVE_ID packet.
+
+ Max Arguments: 1
+ Arguments: (1) <Client ID>
+
+ The <Client ID> is the client who left SILC network.
+
+
+5 SILC_NOTIFY_TYPE_TOPIC_SET
+
+ Sent when topic is set/changed on a channel. This type must be sent
+ only to the clients who is joined on the channel whose topic was
+ set or changed.
+
+ Max Arguments: 2
+ Arguments: (1) <Client ID> (2) <topic>
+
+ The <Client ID> is the client who set or changed the <topic>.
+
+
+6 SILC_NOTIFY_TYPE_NICK_CHANGE
+
+ Sent when client changes nick on a channel. This type is sent only if
+ the client has joined to any channel. This type is sent by server or
+ router when SILC_PACKET_REPLACE_ID packet has been received. See
+ detailed information from description of SILC_PACKET_REPLACE_ID packet.
+
+ Max Arguments: 2
+ Arguments: (1) <Old Client ID> (2) <New Client ID>
+
+ The <Old Client ID> is the old ID of the client who changed the
+ nickname. The <New Client ID> is the new ID generated by the change
+ of the nickname.
+
+
+7 SILC_NOTIFY_TYPE_CMODE_CHANGE
+
+ Sent when channel mode has changed. This type must be sent only to
+ the clients who is joined on the channel whose mode was changed.
+
+ Max Arguments: 2
+ Arguments: (1) <Client ID> (2) <mode mask>
+
+ The <Client ID> is the client who changed the mode. The <mode mask>
+ is the new mode mask of the channel.
+
+
+8 SILC_NOTIFY_TYPE_CUMODE_CHANGE
+
+ Sent when user mode on channel has changed. This type must be sent
+ only to the clients who is joined on the channel where the target
+ client is on.
+
+ Max Arguments: 3
+ Arguments: (1) <Client ID> (2) <mode mask>
+ (3) <Target Client ID>
+
+ The <Client ID> is the client who changed the mode. The <mode mask>
+ is the new mode mask of the channel. The <Target Client ID> is the
+ client whose mode was changed.
+
+
+9 SILC_NOTIFY_TYPE_MOTD
+
+ Sent when Message of the Day (motd) is sent to client.
- This type includes three arguments: nickname, server name and
- Channel ID. The Channel ID is sent inside ID Payload.
+ Max Arguments: 1
+ Arguments: (1) <motd>
+
+ The <motd> is the Message of the Day.
.in 3
Notify types starting from 16384 are reserved for private notify
.in 3
.ce
-Figure 8: Error Payload
+Figure 10: Error Payload
.in 6
(*) indicates that the field is not encrypted.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
.in 5
.nf
.in 3
.ce
-Figure 9: Channel Message Payload
+Figure 11: Channel Message Payload
.in 6
Channel Key Payload is used to distribute channel keys to all
clients on the particular channel. Channel keys are sent when
the channel is created, when new user joins to the channel and
-whenever a user leaves a channel. Server creates the new
+whenever a user has left a channel. Server creates the new
channel key and distributes it to the clients by encrypting this
payload with the session key shared between the server and
the client. After that, client starts using the key received
are not encrypted using channel keys, they are encrypted using
normal session keys between two routers. Inside a cell, all
channel traffic is encrypted with the specified channel key.
-Channel key should expire peridiocally, say, in one hour, in
+Channel key should expire periodically, say, in one hour, in
which case new channel key is created and distributed.
The payload may only be sent with SILC_PACKET_CHANNEL_KEY packet.
represents the Channel Key Payload.
+
+
+
+
+
+
+
+
+
+
+
.in 5
.nf
1 2 3
.in 3
.ce
-Figure 10: Channel Key Payload
+Figure 12: Channel Key Payload
.in 3
.ce
-Figure 11: Private Message Payload
+Figure 13: Private Message Payload
.in 6
.in 3
.ce
-Figure 12: Private Message Key Payload
+Figure 14: Private Message Key Payload
.in 3
.ce
-Figure 13: Command Payload
+Figure 15: Command Payload
.in 6
.in 3
.ce
-Figure 15: Connection Auth Request Payload
+Figure 16: Connection Auth Request Payload
.in 6
This payload is also used when server tells its router that new client
has registered to the SILC network. In this case the server sends
-the Client ID of the client to the router. Similiary when router
+the Client ID of the client to the router. Similary when router
distributes information to other routers about the client in the SILC
network this payload is used.
the New Client Payload.
+
.in 5
.nf
1 2 3
the New Server Payload.
+
+
+
.in 5
.nf
1 2 3
represents the New Channel Payload.
+
+
.in 5
.nf
1 2 3
diagram represents the New Channel User Payload.
+
+
+
+
.in 5
.nf
1 2 3
-
-
-
-
-
-
.in 5
.nf
1 2 3
Remove Channel User payload is used to remove a user from a channel network
wide. This is used by routers to notify other routers that a user has
-leaved a channel. As routers keep information about users on channels a
+left a channel. As routers keep information about users on channels a
user leaving channel must be removed from all routers. Normal server may
send this payload as well. Client must not send this payload.
represents the Remove Payload Payload.
+
+
+
.in 5
.nf
1 2 3
.in 3
.ce
-Figure 23: Remove Channel User Payload
+Figure 22: Remove Channel User Payload
.in 6
.in 3
+
.ti 0
2.4 SILC ID Types
server or router en route must not decompress the packet.
+
.ti 0
2.9 Packet Sending
2.10 Packet Reception
On packet reception the receiver must check that all fields in the
-SILC Packet Header are valid sain. It must check the flags of the
+SILC Packet Header are valid. It must check the flags of the
header and act accordingly. It must also check the MAC of the packet
and if it is to be failed the packet must be discarded. Also if the
header of the packet includes any bad fields the packet must be
Key Management Protocol (ISAKMP)", RFC 2408, November
1998.
-[IKE] Harkins D., and Carrel D., "The Internet Key Exhange
+[IKE] Harkins D., and Carrel D., "The Internet Key Exchange
(IKE)", RFC 2409, November 1998.
[HMAC] Krawczyk, H., "HMAC: Keyed-Hashing for Message
Authentication", RFC 2104, February 1997.
+
+
+
+
.ti 0
5 Author's Address
EMail: priikone@poseidon.pspt.fi
-This Internet-Draft expires 13 May 2001
+This Internet-Draft expires 6 Jun 2001
projects / silc.git / blobdiff