TS-0010, clause 6.6 URI Format: undefined behaviour
In TS-0010, 6.6 URI Format, the last paragraph defines a free style topic format for notifications:
There shall always be a path if an MQTT URI is used in a notificationURI attribute. That path gives the entire MQTT topic string that the notification is to be published to (with no leading /). The structure of that topic string does not have to conform to any of the topic string patterns defined in the present document.
The issues here are:
- What should be the topic for the response?
- The reveiver isn't necessarily an AE, and even when it is the CSE cannot determine the necessary information, such as AE-ID, from a free style topic. Since the receiver is unknown to the CSE then, the AE-ID for the request's to attribute cannot be determined. But this attribute is mandatory in a request.
Suggestion for 1. : I would suggest to specify that notification receiver has to respond using the normal response topic "/oneM2M/resp/..."
Suggestions for 2. :
- Make the to attribute optional (huge impact)
- Assign the sending CSE's CSE-ID to the to attribute, even when the CSE is not the receiver.