[OASIS Issue Tracker] Issue Comment Edited: (MQTT-139) Unclear normative quality of Security section

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

    [ http://tools.oasis-open.org/issues/browse/MQTT-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36538#action_36538 ] 

Richard Coppen edited comment on MQTT-139 at 2/13/14 11:44 AM:
---------------------------------------------------------------

Issue MQTT-176 clarifies that Section 5 is non normative.
The use of port 8883 is strongly recommended, but optional, therefore it cannot be enforced as a conformance clause. As such, it should be removed from the list sof conformance clauses in Chapter 7

      was (Author: coppen):
    Issue MQTT-179 clarifies that Section 5 is non normative.
The use of port 8883 is strongly recommended, but optional, therefore it cannot be enforced as a conformance clause. As such, it should be removed from the list sof conformance clauses in Chapter 7
  
> Unclear normative quality of Security section
> ---------------------------------------------
>
>                 Key: MQTT-139
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-139
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.1.1
>         Environment: Conformance 
>            Reporter: Patrick Durusau
>
> The conformance clause requires that "all of the MUST level requirements in the following chapters " be satisfied.
> But there is no MUST level requirements in Security section, nor there are any MQTT normative tags. So it is unclear what it takes to conform to this section.

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