Content deleted Content added
No edit summary |
m clean up, removed stub tag using AWB |
||
Line 1:
{{unreferenced|date=April 2015}}
The [[Internet Assigned Numbers Authority]] (IANA) officially assigned port 4605 to the SixChat End2End Direct secure messaging protocol created by Sixscape Communications, Pte. Ltd. The assignment was issued by IANA on
There are a very limited number of port numbers, which are assigned by IANA for protocols recognized as viable, complying with current protocol design standards, and not already covered by existing Internet standards. For example, port 25 was assigned to the SMTP email protocol many years ago. This provides a standard port and reduces conflicts with other protocols. The technical review of the SixChat protocol was performed by [[Lars Eggert]], the distinguished chair of the [[Internet Research Task Force]].
Line 15:
The SixChat End2End Messaging protocol is a streaming protocol (tcp based, connection oriented). It cannot be secured with TLS, which is an inherently Client/Server technology. It provides mutual strong authentication using only X.509 client digital certificates (no server cert involved), and symmetric session key exchange (via public/private key encryption or Ephemeral Diffie Hellman Key Exchange). This handshake is based on the design of TLS, but is not Client/Server, rather between peers. Unlike TLS, it lies entirely within the Application Layer the protocol messages are based on XML.
Nodes supporting End2End Direct messaging are neither client nor server, but must be able to originate and accept network connections (hence have characteristics of both clients and servers). Such a node is called a "User Agent".
[[
[[ | |||