clarification on BLE spec
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 3
- Avg merge
- 20h 14m
- Merged PRs (30d)
- 1
Description
Originally submitted by Kristina Yasuda (Kristina Yasuda) on 2023-08-30
Opening on behalf of Kenichi. who sent on the Mailing List on May 8th 2023 the following:
1. just for clarification
In Section 6.4, ** Chunk sequence number: ** List of chunks that are missing or failed CRC.
Does it mean Chunk sequence number: List of chunk sequence Nos that are missing or failed CRC?
2. Chunk sequence number size (in Section 6.4), (2 byte each upto max MTU)
It should be “2 byte each upto max MTU -4”.
Bitbucket status: new
Bitbucket origin: issue 2054
Contributor guide
No contributing guide indexed for this repository
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 locating Section 6.4 in the BLE specification source and review the definitions of chunk sequence numbers and MTU sizing. Done means resolving the two questions and updating the specification wording if the proposed “max MTU -4” correction is confirmed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100