Per slack thread, it was not sufficiently clear that the library should be in the CONNECTING state when it's attempting to reconnect. In particular the lib must not be in the CONNECTED state when not actually connected to the server, which is not currently made explicit. Clarified this spec item and added brief descriptions of all the connection states.
(I allowed the library to optionally go through DISCONNECTED on its way to CONNECTING in the case of an immediate reconnect since there are SDKs which do that and I don't want to make them suddenly be not in compliance, it's no big deal to do that if they want)
Also cleaned up RTN15a (which previously waffled on a bit about various things not relevant to actions to take if the transport is disconnected).
Per slack thread, it was not sufficiently clear that the library should be in the CONNECTING state when it's attempting to reconnect. In particular the lib must not be in the CONNECTED state when not actually connected to the server, which is not currently made explicit. Clarified this spec item and added brief descriptions of all the connection states.
(I allowed the library to optionally go through DISCONNECTED on its way to CONNECTING in the case of an immediate reconnect since there are SDKs which do that and I don't want to make them suddenly be not in compliance, it's no big deal to do that if they want)
Also cleaned up RTN15a (which previously waffled on a bit about various things not relevant to actions to take if the transport is disconnected).