Clarify requirements on config messages (ref #377)

This commit is contained in:
Jakob Borg 2014-06-19 01:27:03 +02:00
parent 4dbce32738
commit de75550415

View File

@ -59,10 +59,11 @@ or certificate pinning combined with some out of band first
verification. The reference implementation uses preshared certificate verification. The reference implementation uses preshared certificate
fingerprints (SHA-256) referred to as "Node IDs". fingerprints (SHA-256) referred to as "Node IDs".
There is no required order or synchronization among BEP messages - any There is no required order or synchronization among BEP messages (except
message type may be sent at any time and the sender need not await a for the requirements on Cluster Config messages below) - any message
response to one message before sending another. Responses MUST however type may be sent at any time and the sender need not await a response to
be sent in the same order as the requests are received. one message before sending another. Responses MUST however be sent in
the same order as the requests are received.
The underlying transport protocol MUST be TCP. The underlying transport protocol MUST be TCP.
@ -118,8 +119,9 @@ normalization form C.
### Cluster Config (Type = 0) ### Cluster Config (Type = 0)
This informational message provides information about the cluster This informational message provides information about the cluster
configuration, as it pertains to the current connection. It is sent by configuration as it pertains to the current connection. A Cluster Config
both sides after connection establishment. message MUST be the first message sent on a BEP connection. Additional
Cluster Config messages MUST NOT be sent after the initial exchange.
#### Graphical Representation #### Graphical Representation