and needs to include additional features. Following protocol TODO entries
describe new stuff to be added to protocol versions 1.x.
- 1. Re-define the Status Payload: it is now 16 bits, split it into two
- 8 bits fields. First field includes status types from 0 - 9 and
- 10 - n *if* it is not an list of errors. If it is list of errors then
- the first field includes 1, 2 and/or 3, and the second field includes
- the error status 10 - n. This way it is possible to send multiple
- errors (list of errors) and we have a way to tell the receiver that
- there will be other errors as well. The second field is used only
- if there is list of errors. If normal status, or normal (single)
- error status the second field is set to zero, and must be ignored.
- Hence, the status works same way as now except for list of errors.
- To be included in protocol version 1.1.
-
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
new features without always making the command incompatible to previous
version. To be included in protocol version 1.1.
- 5. Inviting and banning by public key should be made possible. To be
- included in protocol version 1.x.
-
- 7. Channel Message Payload needs slight redesining to include the IV
- field to the MAC generation of the payload. It is authenticated
- by the packet's MAC but not by the payload's MAC. Since the IV
- belongs to the payload, its integrity should be protected by the
- payload MAC and not alone by packet MAC. To be included in protocol
- version 1.1.
+ 17. Cell wide channel founder support, and permanent channels when
+ founder mode set.
- 11. Change the wording in Private Message Key Payload definition to
- describe the problems of trusting the payload, and to indicate that
- the receiver may not accept the key in the payload, and to describe
- other means of distributing a key.
+ 20. Services support?
- 16. Add STATS command after all to the protocol for providing practically
- same information client gets when connects to a server. Normal
- server would send this to router always when received from client.
+ 21. Subscription/IRC's notify kind support?
- 17. Cell wide channel founder support, and permanent channels when
- founder mode set.
+ 22. Session detachment/resume?
- 18. Describe the SSH public key, X509, OpenPGP and SPKI certificates
- encoding format in SKE (from their respective definitions).
+ o Inviting and banning by public key should be made possible. To be
+ included in protocol version 1.2.
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
projects / silc.git / blobdiff