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-532) style: Section 5 heading differs from 3.1.1


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

Richard Coppen updated MQTT-532:
--------------------------------

    Proposal: 
Update introduction subsection 5.1 as follows to replace 3510-3515 (paras 1,2  and 5):
>>>
5.1 Introduction

MQTT Implementations will likely need to keep pace with an evolving security landscape.

MQTT is a transport protocol specification for message transmission, allowing implementers a choice of network, privacy, authentication and authorisation technologies. Since the exact security technologies chosen will be context specific, it is the implementer's responsibility to include the appropriate features as part of their design. 

This Chapter provides general implementation guidance so as not to restrict choices available and is therefore Non Normative. This should not detract from its importance. 

TLS [RFC5246] is often used to provide a secure network layer. It is strongly recommended that Server implementations that offer TLS should use TCP port 8883 (IANA service name: secure-mqtt).
<<<
rejoin at existing para 3 "There are a number ..."

  was:
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).


> style: Section 5 heading differs from 3.1.1
> -------------------------------------------
>
>                 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: wd18
>            Reporter: Richard Coppen
>            Priority: Minor
>              Labels: editorial
>
> 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]