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: [OASIS Issue Tracker] (MQTT-601) Transition from AWAKE to LOST status unclear


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

Simon Johnson updated MQTT-601:
-------------------------------
    Assignee: Simon Johnson

> Transition from AWAKE to LOST status unclear
> --------------------------------------------
>
>                 Key: MQTT-601
>                 URL: https://issues.oasis-open.org/browse/MQTT-601
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>            Reporter: Davide Lenzarini
>            Assignee: Simon Johnson
>            Priority: Major
>
> A Client status is defined by the Gateway so the following sentence in the cell AWAKE of the table in 3.6 is unclear:
> "The client transitions back to the *ASLEEP* state on receipt of a PINGRESP packet or *LOST* (by way of supervised gateway timers)."
> The client should go back to ASLEEP as soon as the PINGRESP is sent by the gateway, right? If it is true, do we really need the transition AWAKE->LOST?ÂWhat is the scenario of the AWAKE->LOST transition?
> Â



--
This message was sent by Atlassian Jira
(v8.3.3#803004)


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