OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: MQTT 3.1.1 partial connect packets over TCP

Hello everyone,


Apologies if this has been answered before but I could not find a definitive answer so far.

When using a TCP transport, is a client library sending a partial connect packet (2 byte fixed header only) while connecting to an MQTT broker conforming to the specification?


I understand that it may not be a problem for an MQTT only broker but what about multi protocol brokers, packet inspectors, load balancers? The specification only has a non normative comment on line 395:


Packet inspectors, such as firewalls, could use the Protocol Name to identify MQTT traffic. 



In the above case though, the protocol name is not sent as it resides in the variable header of the packet.


Any assistance would be greatly appreciated.




Alex Kritikos


This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying, or use of this communication or the information in it, is strictly prohibited. If you have received this communication in error please notify us by e-mail and then delete the e-mail and any copies of it.
Software AG (UK) Limited Registered in England & Wales 1310740 - http://www.softwareag.com/uk

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]