maxReservedMessageIds

The most Message IDs reserved at once, towards all peers together. Every message the endpoint sends with a new Message ID (a request, a separate response, a notification, every message of a Q-Block body) reserves it for EXCHANGE_LIFETIME, since RFC 7252 §4.4 forbids reusing it towards that peer before, and a flood of spoofed Non-confirmable requests makes the endpoint send one response, and so reserve one ID, each. Beyond the bound such a message is refused instead: a request fails with CoapException.Reason.IDENTIFIERS_EXHAUSTED, a separate response is not sent, a notification is sent later with the latest state while the observer stays (RFC 7641 §4.5), and each is reported with MESSAGE_IDS. A quarter of the bound, and of maxReservedMessageIdsPerPeer, is kept from Non-confirmable responses to Non-confirmable requests, which a client may lose anyway (§5.2.3) and a flood from forged addresses makes the endpoint send: they are refused at three quarters, so the rest is left for the endpoint's own requests, notifications and separate responses to Confirmable requests. Piggybacked responses reuse the request's ID and are never refused. The default allows four peers at the most RFC 7252 §4.4 allows one (65 536 per EXCHANGE_LIFETIME), about 1 000 messages a second in all, and takes about 26 MB when full.