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-384) 3.3.2.4 Payload Format Indicator.- comments


    [ https://issues.oasis-open.org/browse/MQTT-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64826#comment-64826 ] 

Rahul Gupta commented on MQTT-384:
----------------------------------

I have fixed this section with text below:
--------------------------------------------
1 (0x01) Byte, Identifier of the Payload Format Indicator. Followed by the value of the Payload Format Indicator, either of: 

0 (0x00) Byte Indicates that the payload is unspecified bytes, which is equivalent to not sending a Payload Format Indicator.

1 (0x01) Byte Indicates that the payload is UTF-8 Encoded Character Data.  Note that the UTF-8 Data in the payload does not include a length prefix, nor is it subject to the restrictions described in section 1.5.3.

===> If the Payload Format Indicator is absent, then the PUBLISH payload consists of unspecified bytes. 

A Server MUST send the Payload Format Indicator unaltered to all subscribers receiving the publication, using this version of MQTT. The receiver is not required to validate that the payload is of the format indicated, but MAY close the Network Connection if it discovers that the payload does not match the Payload Format Indicator.

The Server MUST send the publication to an MQTT client using the MQTT V3.1.1 protocol with a matching subscription. In this case no Payload Format Indicator is included. 
--------------------------------------------------------------



> 3.3.2.4 Payload Format Indicator.- comments
> -------------------------------------------
>
>                 Key: MQTT-384
>                 URL: https://issues.oasis-open.org/browse/MQTT-384
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd10
>            Reporter: Brian Raymor
>            Assignee: Rahul Gupta
>            Priority: Trivial
>             Fix For: 5, wd11
>
>
> 1704 0 (0x00) Byte Indicates that the payload is unspecified bytes, this is equivalent to not sending a
> 1705 Payload Format Indicator.
> Run on sentence. 
> 0 (0x00) Byte Indicates that the payload is unspecified bytes, [which] is equivalent to not sending a
> 1705 Payload Format Indicator.



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