[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=63586#comment-63586 ]
Ed Briggs commented on MQTT-299:
--------------------------------
In the MQTT-TC Face to Face meeting today (26-September-2016), concerning the question of what a Server should do if it needs to forward a packet which it knows exceeds the Clients Maximum Receive Packet Size, discussed the following approaches:
1. The Server could send it, and rely on the client to send a NAK. This would insure transmission would not be attempted on a transport failure, with a possible cycle ensuing. However it wastes network bandwidth and does not protect the session partners 'network' which may have limited capacity or incur usage charges
2 The Server could discard the oversized message, and perhaps tally a local error counter. This saves bandwidth and processing, but may complicate diagnostic efforts to determine the cause of packet loss.
3. Andrew Banks proposed the use of a 'forward abort' technique, in which the Server would send a DISCONNECT message to the CLIENT signifying 'I need to send you a message you can't process'.
> 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]