-
Type: Improvement
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 3.1.1, 5
-
Component/s: candidateCN
-
Labels:None
The following changes were made to Disallowed-Unicode code points-v1.0-wd01 when it was merged into the V5 spec. We propose to make the same changes to the committee note
In 1.1 Introduction remove the comma from:
Unicode Noncharacters, which
In 1.3 1.3 Considerations for the use of Disallowed Unicode code points remove the
paragraph containing the double negative...
An implementation of MQTT might choose not to validate Topic Names if Disallowed Unicode
code points will never occur in a particular use case, due to the constraints on Topic
Names being used. In such
cases the burden of validating whether these code points are present is unnecessary.
In 1.5 Remedies replace
3) Restrict the Topic Filters authorized to subscribers so that a Client cannot use
Topic Filters containing Disallowed Unicode code points. If a client is allowed to
make a subscription containing a wild card character, ensure that the publishers
cannot make publications where a Disallowed Unicode code point would match the wildcard.
to the following so as to remove the word ensure...
3) Restrict the Topic Filters authorized to subscribers so that a Client cannot use
Topic Filters containing Disallowed Unicode code points. If a client is allowed to
make a subscription containing a wild card character, ensure that the Server is
configured so that publishers cannot make publications where a Disallowed Unicode
code point would match the wildcard.