updates.

diff --git a/doc/draft-riikonen-silc-ke-auth-06.nroff b/doc/draft-riikonen-silc-ke-auth-06.nroff
index e5d0b2809b3b0bdf2745f999e522e73c71d1c51a..b017ff774eb556c2bc22dcf6c2a5a4e71805bde9 100644 (file)
--- a/doc/draft-riikonen-silc-ke-auth-06.nroff
+++ b/doc/draft-riikonen-silc-ke-auth-06.nroff
@@ -851,10 +851,6 @@ is.  The type defines whether this is client, server or router
 connection.  Server uses this information to create the ID for the
 connection.
 
-After the authentication protocol has been successfully completed
-SILC_PACKET_NEW_ID must be sent to the connecting client by the server.
-See the [SILC1] for the details of the connecting procedure.
-
 Server MUST verify the authentication data received and if it is to fail
 the authentication MUST be failed by sending SILC_PACKET_FAILURE packet.
 If everything checks out fine the protocol is ended by server by sending
@@ -897,12 +893,10 @@ Start Payload, established by the SILC Key Exchange protocol.  This
 signature MUST then be verified by the server.  See the section 3.2.2
 Public Key Authentication for more information.
 
-The connecting client of this protocol MUST wait after successful execution
-of this protocol for the SILC_PACKET_NEW_ID packet where it will receive
-the ID it will be using in the SILC network.  The connecting client cannot
-start normal SILC session (sending messages or commands) until it has
-received its ID.  The ID's are always created by the server except
-for server to router connection where servers create their own ID's.
+See the section 4 SILC Procedures in [SILC1] for more information about
+client creating connection to server, and server creating connection
+to router, and how to register the session in the SILC Network after
+successful Connection Authentication protocol.
 
 
 .ti 0

diff --git a/doc/draft-riikonen-silc-pp-06.nroff b/doc/draft-riikonen-silc-pp-06.nroff
index fc4cbe72568ac7d49823a6b594cf73e0a7b75e80..485449930c74f2175e5e81e5063fe35f7d17b62b 100644 (file)
--- a/doc/draft-riikonen-silc-pp-06.nroff
+++ b/doc/draft-riikonen-silc-pp-06.nroff
@@ -1203,7 +1203,7 @@ o Notify Type (2 bytes) - Indicates the type of the notify
 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
+o Argument Nums (1 byte) - Indicates the number of Argument
   Payloads associated to this payload.  Notify types may define
   arguments to be send along the notify message.
 .in 3