[OASIS Issue Tracker] (MQTT-573) Subscription Options

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

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

Ian Craggs updated MQTT-573:
----------------------------
    Proposal: 
Issue 576 introduces the subscribe flags field.

_Table 19 - change Flags to Subscribe Flags_

Section 5.4.15 SUBSCRIBE
 * Length and MsgType: see section 5.2
 * Subscribe Flags:
 ** QoS: the requested QoS level for the subscription
 ** No Local: see section 5.3.6
 ** Retain as Published: see section 5.3.6
 ** Retain handling: see section 5.3.6

Section 5.4.16 SUBACK

_Table 20 - change ''Flags' to 'Subscribe Flags'_

__Field list: change 'Flags' to 'Subscribe Flags'. QoS is the only field used, with the same description as that existing._

Section 5.4.17 UNSUBSCRIBE

_Field list: change 'Flags' to 'Subscribe Flags'. All unused apart from TopicIdType_

> Subscription Options
> --------------------
>
>                 Key: MQTT-573
>                 URL: https://issues.oasis-open.org/browse/MQTT-573
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>            Reporter: Ian Craggs
>            Assignee: Ian Craggs
>            Priority: Major
>
> Subscription options were added to MQTT 5.0.  These are generally well received.  Similar capabilities should be added to MQTT-SN especially as they can result in more efficient operations.
> Subscribe flags field:
> 2 bits - max QoS as now
> 1 bit - noLocal
> 1 bit - retain as published
> 2 bits - retain handling
> 2 bits - topic ID type
> (I think DUP is not needed on subscribe - rely on suback).



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