Implement RFC 8768 (Hop-Limit Option)
Open
Nobody has claimed this yet.
enhancement
RFC 8768
- Dominant language
- TypeScript
- Stars
- 552
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
RFC 8768 introduces a new Hop-Limit option that can be used to prevent infinite loops in when multiple proxies are involved. As node-coap provides proxy features for servers, we should also implement this RFC.
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 8768 and then inspect node-coap's existing proxy features to identify the relevant entry points. Done means the Hop-Limit option described by the RFC is implemented for proxy handling, with behavior consistent with the RFC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100