[OASIS Issue Tracker] (MQTT-210) Add clarity to keepAlive interval

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

     [ https://tools.oasis-open.org/issues/browse/MQTT-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Coppen updated MQTT-210:
--------------------------------

    Proposal: 
Replace >> The Keep Alive is a time interval measured in seconds. Expressed as a 16-bit word, it is the maximum time interval that is permitted to elapse between two successive Control Packets sent by the Client. <<

With >> The Keep Alive is a time interval measured in seconds. Expressed as a 16-bit word, it is the maximum time interval that is permitted to elapse between the point at which the Client finishes transmitting one Control Packet to the point it starts sending the next. <<

  was:
Add the following text to 3.1.2.10 Keep Alive

Note that it may take some time to transmit large Packets. From the Server’s viewpoint the Keep Alive time interval starts when the receipt of one Packet has completed and ends when the receipt of the subsequent Packet begins.


> Add clarity to keepAlive interval
> ---------------------------------
>
>                 Key: MQTT-210
>                 URL: https://tools.oasis-open.org/issues/browse/MQTT-210
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.1.1
>            Reporter: Peter Niblett
>
> Issue brought up by Ian Craggs
> "I think it would be worth saying something in the spec about the sending and receiving MQTT packets large enough for the send/receive process to exceed the keepalive interval.  It is a case that implementers of both clients and servers tend to forget about until a bug is raised."



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)