Added SILC Thread Queue API

[crypto.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 939dbf871a5b8e55f6a55a8a847022a1b5b5ce70..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
 
@@ -1733,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
@@ -2587,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.
 
@@ -2699,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