DTLS fragmentation error? about bc-csharp

[ds600]

Probably not a problem of bouncy castle, but of another library that I use (CoAP.NET) that handles some of the DTLS session management. I'll close this issue until I can be certain

[peterdettman]

We call GetReceiveLimit on the DtlsTransport to size the receive buffer, so it's important to return an appropriate value there. In any case a call to DtlsTransport.Receive should never return a value larger than the available space in the buffer. I've added an extra guard for the latter case.

Note that individual datagrams may contain one or more complete records (no record splitting across datagrams); this usually only happens during the handshake. Individual handshake messages may also be fragmented across multiple records.

[ds600]

I just found out that this issue is not happening because of fragmentation, but because the buffer of the previous (smaller) message is used and it tries to push the new message in a wrong buffer. I'll continue my investigation on how this is happening. This only happens when the messages are received at quite a high interval

[ds600]

For now, I think you shouldn't put any work in, as I can't guarantee that it's not because of my CoAP library