[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-532) update Chapter 5 intro re. non-normative
[ https://issues.oasis-open.org/browse/MQTT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=69650#comment-69650 ] Richard Coppen commented on MQTT-532: ------------------------------------- wd20 currently says MQTT Implementations will likely need to keep pace with an evolving security landscape. Suggest we change this to: Implementations will need to keep pace with an evolving security landscape. > update Chapter 5 intro re. non-normative > ---------------------------------------- > > Key: MQTT-532 > URL: https://issues.oasis-open.org/browse/MQTT-532 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Bug > Components: edits > Affects Versions: 5, wd18 > Reporter: Richard Coppen > Assignee: Andrew Banks > Priority: Minor > Labels: editorial > Fix For: 5, wd20 > > > Section 5 heading reads: > 5 Security (non-normative) > 5.1 Introduction > It is strongly recommended that Server implementations that offer TLS [RFC5246] should use TCP port 8883 (IANA service name: secure-mqtt). > For 3.1.1 we say: > 5 Security > 5.1 Introduction > This Chapter is provided for guidance only and is Non Normative. However, it is strongly recommended that Server implementations that offer TLS [RFC5246] SHOULD use TCP port 8883 (IANA service name: secure-mqtt). > While it's true that the section is provided as implementer guidance only, the intent of the 3.1.1 wording to make a strong recommendation for using TLS on 8883. It's primarily a cosmetic change, but reverting to the 3.1.1 style makes it consistent -- 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]