Merge commit 'origin/silc.1.1.branch'

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

diff --git a/doc/draft-riikonen-silc-pp-03.nroff b/doc/draft-riikonen-silc-pp-03.nroff
index 59e7edc212cf449975e95162939fb8c5a9e30cb4..72d25da643d724abba11b07a7b189866a96e72aa 100644 (file)
--- a/doc/draft-riikonen-silc-pp-03.nroff
+++ b/doc/draft-riikonen-silc-pp-03.nroff
@@ -8,7 +8,7 @@
 .ds RF FORMFEED[Page %]
 .ds CF
 .ds LH Internet Draft
-.ds RH XXX
+.ds RH 21 August 2001
 .ds CH
 .na
 .hy 0
@@ -16,8 +16,8 @@
 .nf
 Network Working Group                                      P. Riikonen
 Internet-Draft
-draft-riikonen-silc-pp-03.txt                                      XXX
-Expires: XXX
+draft-riikonen-silc-pp-03.txt                           21 August 2001
+Expires: 21 February 2002
 
 .in 3
 
@@ -1559,9 +1559,19 @@ o Flags (2 bytes) - Includes the flags of the channel
   0x0010  SILC_MESSAGE_FLAG_REQUEST
 
           This is a generic request flag to send request
-          messages.
+          messages.  A separate document should define any 
+          payloads associated to this flag.
 
-  0x0020 - 0x0200 RESERVED
+  0x0020  SILC_MESSAGE_FLAG_SIGNED
+
+          This flag indicates that the message is signed
+          with sender's private key and thus can be verified
+          by the receiver using the sender's public key.  A
+          separate document should define the detailed procedure
+          of the signing process and any associated payloads
+          of this flag.
+
+  0x0040 - 0x0200 RESERVED
 
           Reserved for future flags
 
@@ -1723,14 +1733,6 @@ packet.  It MUST NOT be sent in any other packet type.  The following
 diagram represents the Private Message Payload.
 
 
-
-
-
-
-
-
-
-
 .in 5
 .nf
                      1                   2                   3
@@ -2577,7 +2579,7 @@ allowed to be routed to the client.  Not all packets may be sent by
 some odd entity to client that is indirectly connected to the sender.
 See section 2.3 SILC Packet Types and paragraph about indirectly connected
 entities and sending packets to them.  The section mentions the packets
-that may be sent to indirectly connected entities.  It is clear that some
+that may be sent to indirectly connected entities.  It is clear that
 server cannot send, for example, disconnect packet to client that is not
 directly connected to the server.
 
@@ -2689,10 +2691,10 @@ security of this protocol.
 
 .nf
 Pekka Riikonen
-Kasarmikatu 11 A4
-70110 Kuopio
+Snellmanninkatu 34 A 15
+70100 Kuopio
 Finland
 
-EMail: priikone@poseidon.pspt.fi
+EMail: priikone@silcnet.org
 
-This Internet-Draft expires XXX
+This Internet-Draft expires 21 February 2002