Merges from Irssi CVS.

[crypto.git] / doc / draft-riikonen-silc-ke-auth-05.nroff

diff --git a/doc/draft-riikonen-silc-ke-auth-05.nroff b/doc/draft-riikonen-silc-ke-auth-05.nroff
index 4e207e4fa08d4390b3cc5dc3e51c32ed5d7c7782..247e99d5c463feb56c6815aa38d165ff6a6d3642 100644 (file)
--- a/doc/draft-riikonen-silc-ke-auth-05.nroff
+++ b/doc/draft-riikonen-silc-ke-auth-05.nroff
@@ -200,7 +200,9 @@ whether it supports the security properties.
 
 It then sends a Key Exchange Start Payload to the initiator filled with
 security properties it selected from the original payload.  The payload
-sent by responder MUST include only one chosen property per list.
+sent by responder MUST include only one chosen property per list.  The
+character encoding for the security property values as defined in [SILC1] 
+SHOULD be UTF-8 [RFC2279].
 
 The Key Exchange Start Payload is used to tell connecting entities what
 security properties and algorithms should be used in the communication.
@@ -481,7 +483,9 @@ o Public Key Type (2 bytes) - The public key (or certificate)
   be closed immediately.
 
 o Public Key (or certificate) (variable length) - The
-  public key or certificate.
+  public key or certificate.  The public key or certificate
+  in this field is encoded in the manner as defined in their
+  respective definitions;  see previous field.
 
 o Public Data Length (2 bytes) - The length of the Public Data
   field, not including any other field.
@@ -822,6 +826,7 @@ are defined:
 
     Provided version string was not acceptable.
 
+
 11  SILC_SKE_STATUS_INVALID_COOKIE
 
     The cookie in the Key Exchange Start Payload was malformed,
@@ -958,7 +963,13 @@ for defined numerical authentication method types.
 Passphrase authentication or pre-shared-key based authentication is 
 simply an authentication where the party that wants to authenticate 
 itself to the other end sends the passphrase that is required by
-the other end, for example server.
+the other end, for example server.  The plaintext passphrase is put
+to the payload, that is then encrypted.  The plaintext passphrase
+MUST be in UTF-8 [RFC2279] encoding.  If the passphrase is in the
+sender's system in some other encoding it MUST be UTF-8 encoded 
+before transmitted.  The receiver MAY change the encoding of the
+passphrase to its system's default character encoding before verifying
+the passphrase.
 
 If the passphrase matches with the one in the server's end the
 authentication is successful.  Otherwise SILC_PACKET_FAILURE MUST be
@@ -1041,12 +1052,12 @@ security of this protocol.
 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.
 
-[SILC4]      Riikonen, P., "SILC Commands", Internet Draft, April 2001.
+[SILC4]      Riikonen, P., "SILC Commands", Internet Draft, May 2002.
 
 [IRC]        Oikarinen, J., and Reed D., "Internet Relay Chat Protocol",
              RFC 1459, May 1993.
@@ -1101,6 +1112,9 @@ security of this protocol.
 [RFC2119]    Bradner, S., "Key Words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.
 
+[RFC2279]    Yergeau, F., "UTF-8, a transformation format of ISO
+             10646", RFC 2279, January 1998.
+
 
 .ti 0
 6 Author's Address