Treat invalid topic alias as a protocol error.

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • wd08
    • Affects Version/s: 5
    • Component/s: core
    • None
    • Hide

      Replace "receiver sends a No Topic return code on the PUBACK or PUBREL response."

      With "receiver sends a No Topic return code in a DISCONNECT packet and then closes the network connection.".

      Replace "sends an Alias Not Accepted return code on the PUBACK or PUBREL response."

      With "sends an Alias Not Accepted return code in a DISCONNECT packet and then closes the network connection.

      Show
      Replace "receiver sends a No Topic return code on the PUBACK or PUBREL response." With "receiver sends a No Topic return code in a DISCONNECT packet and then closes the network connection.". Replace "sends an Alias Not Accepted return code on the PUBACK or PUBREL response." With "sends an Alias Not Accepted return code in a DISCONNECT packet and then closes the network connection.

      Issue 269 MQTT-SN Feature: Topic Registration allows the protocol to continue where an invalid topic alias has been used.

      The network is required to provided an in order lossless connection so the only possible causes of an invalid alias are an incorrect implementation or the sending of publications by the client before the connack has been received informing it of the servers maximum topic alias value.

      Continuing the message flow risks data loss. In all cases where an invalid topic alias is received the receiver should disconnect with a 130 0x82 Protocol error disconnect code.

            Assignee:
            Andrew Banks (Inactive)
            Reporter:
            Andrew Banks (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: