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-555) Clarification of broker behaviour when client REGISTERs a PREDEFINED topic

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

Simon Johnson updated MQTT-555:
5.4.11 REGACK
Length	MsgType	Flags	TopicId	MsgId	ReturnCode
(octet 0)	(1)	(2)	(3-4)	(5-6)	(7)
Table 15: REGACK Message
The REGACK message is sent by a client or by a GW as an acknowledgment to the receipt and processing of a REGISTER message. Its format is illustrated in Table 15:
â Length and MsgType: see Section 5.2.
â Flags:
â DUP: not used.
â QoS: not used.
â Retain: not used.
â CleanSession: not used.
â TopicIdType: indicates the type of information included at the end of the message, namely â0b00â
topic name, â0b01â pre-defined topic id, â0b10â short topic name, and â0b11â reserved.
â TopicId: the value that shall be used as topic id in the PUBLISH messages;
â MsgId: same value as the one contained in the corresponding REGISTER message. â ReturnCode: âacceptedâ, or rejection reason.


> Clarification of broker behaviour when client REGISTERs a PREDEFINED topic
> --------------------------------------------------------------------------
>                 Key: MQTT-555
>                 URL: https://issues.oasis-open.org/browse/MQTT-555
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>            Reporter: Simon Johnson
>            Assignee: Simon Johnson
>            Priority: Minor
>              Labels: Implementation-notes
> If a client issues a âREGISTER âagainst the topic that happens to also be predefined, should  this be allowed? If so, does this yield a normalId in the REGACK, in which case the broker must use an order of precedence when selecting the topic id scheme to use in deliveries to this client.

This message was sent by Atlassian Jira

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