[OASIS Issue Tracker] (MQTT-455) 3.2.2.3.6 Assigned Client Identifier - redundant text

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

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

Ken Borgendale commented on MQTT-455:
-------------------------------------

It is quite common to first define what the value of the property means, and then define the rule for when it must be used.  As you point out there is some overlap between these, and in this case they are in adjacent paragraphs.  I would leave this as is.

> 3.2.2.3.6 Assigned Client Identifier - redundant text
> -----------------------------------------------------
>
>                 Key: MQTT-455
>                 URL: https://issues.oasis-open.org/browse/MQTT-455
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd14
>            Reporter: Brian Raymor
>            Priority: Trivial
>             Fix For: 5, wd14
>
>
> Lines 1557-1558:
> "The Client Identifier which was assigned by the Server because a zero length Client Identifier was found in the CONNECT packet."
> could be deleted since Lines 1560-1562 state the same information in a more precise manner:
> "If the Client connects using a zero length Client Identifier, the Server MUST respond with a CONNACK containing an Assigned Client Identifier. The Assigned Client Identifier MUST be a new Client Identifier not used by any other Session currently in the Server ..."



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)