[OASIS Issue Tracker] (MQTT-299) Metadata: CONNECT and CONNACK Maximum Message Length

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/MQTT-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63585#comment-63585 ] 

Ed Briggs commented on MQTT-299:
--------------------------------

In the MQTT-TC Face to Face meeting today (26-September-2016), the TC reached consensus by show of hands on the following components of this JIRQ

1. A Client or Server receiving a Max Message Length advertisement from its session partner MUST NOT send packets exceeding the advertised Maximum-Packet-Size.

2. The Maximum Message Size term is replaced by the Maximum Packet Size. The maximum packet size is the number of bytes for the entire packet, including fixed header, variable header, variable length header, topics, metadata tags and payload.

> 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)