maxExchanges

The most exchanges in progress with all peers together, counted as for maxExchangesPerPeer: requests of this endpoint awaiting their response and its observations, and over datagrams every message the messaging layer keeps, also each Non-confirmable one kept for NON_LIFETIME so that a Reset can match it. At the bound a new datagram message first takes the place of the oldest Non-confirmable message kept only for a Reset (RFC 7252 §4.3 lets a sender ignore a Reset), then of the oldest Confirmable message that is still unacknowledged after a retransmission, which is given up early as if it had timed out and reported with EXCHANGES: a peer that answers acknowledges within ACK_TIMEOUT, while a spoofed source only draws retransmissions (§11.3). Otherwise a request fails with CoapException.Reason.IDENTIFIERS_EXHAUSTED, a separate response is not sent, and a notification is sent later with the latest state while the observer stays (RFC 7641 §4.5), each reported with EXCHANGES.