[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-299) Metadata: CONNECT and CONNACK Maximum Message Length
[ https://issues.oasis-open.org/browse/MQTT-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63708#comment-63708 ]
Ken Borgendale commented on MQTT-299:
-------------------------------------
mqtt-284 only added Reason Strings to CONNACK and DISCONNECT. The spec for these specifically says that these must not be sent if they cause the packet size to be greater than the MaxPacketSize.
In mqtt-309 we propose adding Reason Strings to the various ACKs and I think we would need to put the same words there about the MaxPacketSize. In addition the proposal is to add a id/value on CONNECT which would limit the sending of this data. We could say that if the client requests "quiet" that no Reason String is send on any packet.
> Metadata: CONNECT and CONNACK Maximum Message Length
> ----------------------------------------------------
>
> Key: MQTT-299
> URL: https://issues.oasis-open.org/browse/MQTT-299
> Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
> Issue Type: New Feature
> Components: core
> Affects Versions: 5
> Reporter: Brian Raymor
> Assignee: Ed Briggs
>
> This was discussed in MQTT-276 (with notes from the F2F meetings) and has been tracked in MQTT-256 (Metadata).
> I'm opening a separate, specific issue per Ken's comments - https://issues.oasis-open.org/browse/MQTT-256?focusedCommentId=62192&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-62192:
> "All of these would be defined in separate JIRAs, but what we should do in this JIRA is to define the mechanism used to pass these values."
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]