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-506) Session Expiry in CONNACK


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

Andrew Banks updated MQTT-506:
------------------------------

    Proposal: 
Add to CONNACK properties.

3.2.2.3.2 Session Expiry Interval
17 (0x11) Byte, Identifier of the Session Expiry Interval.
Followed by the Four Byte Integer representing the Session Expiry Interval in seconds. It is a Protocol Error to include the Session Expiry Interval more than once.

If the Session Expiry Interval is absent the value in the CONNECT Packet used. The server uses this property to inform the Client that it is using a value other than that sent by the Client in the CONNACK. Refer to section 3.1.2.11.2 for a description of the use of Session Expiry Interval.


> Session Expiry in CONNACK
> -------------------------
>
>                 Key: MQTT-506
>                 URL: https://issues.oasis-open.org/browse/MQTT-506
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 5, CSD01
>            Reporter: Dominik Obermaier
>            Assignee: Ken Borgendale
>             Fix For: 5, wd16
>
>
> The Session Expiry Interval Property (0x11) can only be present in the CONNECT and DISCONNECT header.
> For clients connecting to a MQTT broker it may be a useful information how long the session expiry interval is, especially if an administrative session expiry interval was configured on the broker and the client is not aware of it.
> Also, if a client sets a session expiry interval in the CONNECT message, it may be overridden by the broker implementation. Currently there is no way to notify the client of his "new" session expiry interval.
> So the proposal is to add the Session Expiry Interval Property as valid property for the CONACK packet.



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