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] Updated: (MQTT-151) Clarify "store data", and more generally make normative statements self-explanatory (as much as possible)


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

Andrew Schofield updated MQTT-151:
----------------------------------

    Proposal: 
Tighten up the words in Section 4.1 (Storing state)

The Client and Server can store Session state to enable reliable messaging to continue across a sequence of Network Connections. Quality of Service guarantees are only valid so long as both Client and Server store Session state. The Client and Server MUST store Session state for at least as long a Session has an active Network Connection. When a Session lasts across a sequence of Network Connections, both Client and Server SHOULD continue to store the Session state so that reliable messaging can be resumed.

Retained messages do not form part of the Session state in the Server. The Server SHOULD retain messages until deleted by a Client, subject to the usual rules for Quality of Service.

Non normative comment.
The storage capabilities of Client and Server implementations will of course have limits in terms of capacity and may be subject to administrative policies such as the maximum time that a Session is stored between Network Connections. Stored Session state can be discarded as a result of an administrator action, including an automated response to defined conditions. These actions might be prompted by resource constraints or for other operational reasons. It is prudent to evaluate the storage capabilities of the Client and Server to ensure that they are sufficient.

Non normative comment.
It is possible that hardware or software failures may result in loss or corruption of Session state stored by the Client or Server.


The non-normative example should stand.

This proposal is wider in scope than the original suggestion which follows here:

Change 1387 (conformance clause MQTT-4.1.0-1)
The Client and Server MUST store data for at least as long as the Network Connection lasts [MQTT-4.1.0-1].

to:

The Client and Server MUST store Session State for at least as long as the Network Connection lasts [MQTT-4.1.0-1].

  was:
Change 1387 (conformance clause MQTT-4.1.0-1)
The Client and Server MUST store data for at least as long as the Network Connection lasts [MQTT-4.1.0-1].

to:

The Client and Server MUST store Session State for at least as long as the Network Connection lasts [MQTT-4.1.0-1].


Reworded section 4.1 because it was hard to understand the intent of the text.

> Clarify "store data", and more generally make normative statements self-explanatory (as much as possible)
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MQTT-151
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-151
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.1.1
>         Environment: Technical Content Quality 
>            Reporter: Patrick Durusau
>            Priority: Minor
>
> In 4.1:
> The Client and Server MUST store data for at least as long as the Network Connection lasts [MQTT-4.1.0-1]. 
> What kind of data are we talking about? Is it session state? Messages? both? need be more precise, especially within tagged normative statements that can be taken out of context, e.g. when referred by a test suite.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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