chrysn/aiocoap

4.02 Bad Option sent rather than RST

Closed this issue · 1 comments

When a critical option is sent and the application sees a critical option it can't process, all the application can do to reject it at request/response layer, but not cause an RST.

While technically violating RFC7252, it can't cause real trouble (given that a proxy would have the same effect) -- so it'll stay this way unless something major crops up that requires a change here.

See-Also: core-wg/corrclar#14

Closing immediately as "won't fix" (but now documented as such).