Merges from Irssi CVS.

[crypto.git] / doc / draft-riikonen-silc-flags-payloads-00.nroff

diff --git a/doc/draft-riikonen-silc-flags-payloads-00.nroff b/doc/draft-riikonen-silc-flags-payloads-00.nroff
index 00c7902f59fd55ce3052f08adafb6d97bddf67a0..a827ccfc80ecc2f197eaef4df51cba38871ebe57 100644 (file)
--- a/doc/draft-riikonen-silc-flags-payloads-00.nroff
+++ b/doc/draft-riikonen-silc-flags-payloads-00.nroff
@@ -95,7 +95,7 @@ Message Flags to the Private Message Payload and Channel Message Payload
 and how it should be interpreted.  Some of the Message Flags may define 
 additional payloads to be associated with the flag, but the [SILC2] does 
 not define them.  This memo defines the payloads for those Message Flags 
-that was marked to include additional payloads in [SILC1].
+that was marked to include additional payloads in [SILC2].
 
 By defining the payloads for the Message Flags the SILC message payloads 
 can be augmented to support any kind of data, which can be easily 
@@ -215,9 +215,10 @@ Hence, the MIME Header in the message payload may be as follows:
 
 .in 8
 .nf
-MIME-Version: 1.0
-Content-Type: discrete/composite
-Content-Transfer-Encoding: binary
+MIME-Version: 1.0\\r\\n
+Content-Type: discrete/composite\\r\\n
+Content-Transfer-Encoding: binary\\r\\n
+\\r\\n
 .in 3
 
 The Content-Transfer-Encoding field behaves as defined in [RFC2045] and 
@@ -260,10 +261,10 @@ support S/MIME may be desired in some implementations.
 5 References 
 
 [SILC1]      Riikonen, P., "Secure Internet Live Conferencing (SILC),
-             Protocol Specification", Internet Draft, April 2001.
+             Protocol Specification", Internet Draft, May 2002.
 
 [SILC2]      Riikonen, P., "SILC Packet Protocol", Internet Draft,
-             April 2001.
+             May 2002.
 
 [RFC2045]    Freed, N., et al., "Multipurpose Internet Mail Extensions 
              (MIME) Part One: Format of Internet Message Bodies",