Implement RFC 7967 (No Server Response Option)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 552
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
RFC 7967 adds a "No Server Response" option to CoAP which is currently not supported by node-coap. The option allows clients to express that they are not interested in certain responses by the server, suppressing, for example, responses with a success code (2.xx) to frequent updates using the POST requests.
Compared to other RFCs, it should be relatively easy to implement (famous last words 😉).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading RFC 7967 and reviewing node-coap's existing option-handling paths, since no specific files or tests are named in the issue. Trace how CoAP options and responses are currently processed, then verify that the No Server Response option suppresses the applicable server responses as specified by the RFC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100