[primer] rename Router/REED to Mesh Extender/Extender-Capable Device#200
[primer] rename Router/REED to Mesh Extender/Extender-Capable Device#200jwhui wants to merge 1 commit into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
EskoDijk
left a comment
EskoDijk
left a comment
There was a problem hiding this comment.
Overall I agree with the term changes and keeping "RLOC".
Comments are about specific improvements suggested, or issues found.
In general, images still mention REED and Router.
jwhui
force-pushed
the
mesh-extender
branch
4 times, most recently
from
9f1198d to
6cd24db
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
EskoDijk
left a comment
EskoDijk
left a comment
There was a problem hiding this comment.
There are a couple of ot-primer-* figures (PNG) that still use the Router/REED terminology. My guess here is that we want to address all of these, in this PR, so that it covers the entire primer? If so: still to be converted.
(If not: maybe discuss why not)
|
Update: terminology was discussed in call 2026-07-01; leading to a new proposal (SPEC-1288). |
jwhui
changed the title
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
jwhui
force-pushed
the
mesh-extender
branch
2 times, most recently
from
555255a to
125eb4b
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request updates the Thread primer documentation to transition from older terminology (such as 'Router' and 'REED') to newer terms like 'Mesh Extender' and 'Extender-Capable Device' (ECD). The review feedback focuses on ensuring precise and consistent application of this new terminology across diagrams, quiz options, and technical descriptions.
Update the Thread Primer documentation to transition terminology from Router and Router Eligible End Device (REED) to Mesh Extender and Extender-Capable Device (ECD), respectively. - Rename "Router" to "Mesh Extender" (or "Active Mesh Extender" where referring specifically to the active parent role). - Rename REED (Router Eligible End Device) to Extender-Capable Device (ECD). - Rename "Router-Router links" to "Mesh Extender links". - Adjust roles, device types, addressing, and MLE attach descriptions to use the new terminology. - Fix grammatical errors and typos introduced during the transition.
@EskoDijk , I updated this PR to reflect the latest consensus in SPEC-1288. Please review.
I don't have access to the source files. We'll get these updated in a separate PR once we settle on the text changes (this PR). |
2 participants
Update the Thread Primer documentation to transition terminology from Router and Router Eligible End Device (REED) to Mesh Extender and Extender-Capable Device (ECD), respectively.