[OASIS Issue Tracker] (MQTT-384) 3.3.2.4 Payload Format Indicator.- comments

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

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

Brian Raymor commented on MQTT-384:
-----------------------------------

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

Run on.

matching subscription. In this case, no PFI 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
>            Priority: Trivial
>             Fix For: 5, wd10
>
>
> 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)