updates.

[crypto.git] / TODO

diff --git a/TODO b/TODO
index 6e1775820b345c93321f4fd1a853c7128ba6edc0..6ce2572a4e28f4be5265e58df7c4e06ee9aad22e 100644 (file)
--- a/TODO
+++ b/TODO
@@ -102,10 +102,6 @@ Manual (Do these to 0.9 and 1.0).
 TODO in SILC Protocol
 =====================
 
-Current protocol version is 1.0.  However, it is far from being perfect,
-and needs to include additional features.  Following protocol TODO entries
-describe new stuff to be added to protocol versions 1.x.
-
  2. Define that WHOIS and IDENTIFY commands must send list of errors
     if multiple Client ID (or Channel ID and Server ID for IDENTIFY) was
     requested and was not found.  Each unfound entry must cause an error
@@ -113,35 +109,11 @@ describe new stuff to be added to protocol versions 1.x.
     *after* sending successfully found entries (this way receiver may
     ignore them).  To be included in protocol version 1.1.
 
- 4. Add "request parameters" or similar to the WHOIS command, which can
-    be used to request various parameters (something not returned by
-    standard WHOIS command) about clients (info that could be fetched
-    even from clients).  Additional specification (or appendix) should 
-    be done to define the payload and the parameters.  It could be used
-    to make the WHOIS command support various search conditions as well.
-    This would be the way to extend the WHOIS command to support various
-    new features without always making the command incompatible to previous
-    version.  To be included in protocol version 1.1.
-
  17. Cell wide channel founder support, and permanent channels when
      founder mode set.
 
- 20. Services support?
-
- 21. Subscription/IRC's notify kind support?
-
- 22. Session detachment/resume
-
- o Inviting and banning by public key should be made possible.  To be
-   included in protocol version 1.2.
+ 24. Implement the <Requested Attributes> and the Attribute Payload to
+     the core library, client and server.
 
- o UTF-8 support/requirement for nicknames & channel names.  UTF-8 support
-   in terminals and OS's are so hazy that this matter is left for
-   consideration in next version of the protocol (1.2).  For good UTF-8
-   reference and tutorial see: http://www.cl.cam.ac.uk/~mgk25/unicode.html.
-   What should CLI application do if it receives nickname that it cannot
-   display without messing up the terminal?  If UTF-8 is mandatory in
-   SILC then SILC clients cannot be allowed to start on terminals that do
-   not support UTF-8 (which renders 98% of users unable to use CLI SILC
-   app without hacking their environment).  See also site
-   http://gratrix.net/unicode/
+ 26. INVITE notify blocking by mode? Quiet user mode to quiet a user on
+     channel, settable by chan op/founder?