I agree with Michael this would be a very useful enhancement to the standardization. In a lot of situations ESBs (like Apache Synapse, Mule, Camel, etc) use the URI prefix as a decider for which protocol to use, and the generic tcp:// prefix is obviously overloaded. The benefit of a dedicated scheme is that it simplifies the configuration of these systems, and it also means that as soon as you see a URI in code or in a config file, you have an idea of the protocol. In other words its helpful to both the machine and the developer.
Dave - yes I agree this is outside the OASIS charter. I personally think this *could* be done in OASIS, but it would require some painful work in the OASIS group to re-charter. The other approach (option #2) would be for the main participants in MQTT to publish a very short joint spec, or alternatively for us to document this under Eclipse Paho and hope that it is adopted. The final approach (option #3) would be to choose a third-party standards body, but that seems a bit weird to me.
Of course if we do a de-facto approach (option #2) then that doesn't preclude the OASIS group taking that on board in the future if it seems a good idea.
Paul
