You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two posibilities a confirmable (CON) and a non-confirmable (NON) request:
CON: an acknowledgment (ACK) is required. The response can either be piggybacked in the ACK or in another message. Piggybacked is suggested when able and as discovery is straightforward, it would be as easy as changing the message type:
NON: the response can not be given as an ACK according to the spec. Using the same response type is suggested, but not enforced by the RFC. Message IDs are only shared with their corresponding ACKs, which is not the case. A new ID should be used, maybe randomly generated:
The discovery response message type is being send with both the same type and id as the request:
There are two posibilities a confirmable (CON) and a non-confirmable (NON) request:
The text was updated successfully, but these errors were encountered: