Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: support IEEE 802.15.4 frame version 2 #4858

Closed
OlegHahm opened this issue Feb 20, 2016 · 9 comments
Closed

Feature request: support IEEE 802.15.4 frame version 2 #4858

OlegHahm opened this issue Feb 20, 2016 · 9 comments
Assignees
Labels
Area: network Area: Networking State: don't stale State: Tell state-bot to ignore this issue Type: new feature The issue requests / The PR implemements a new feature for RIOT

Comments

@OlegHahm
Copy link
Member

Since the IEEE 802.15.4-2015 standard is released a new frame format for 802.15.4, tagged as frame version 2, is defined. This is, e.g., required for the TSCH mode of 802.15.4 (or at least for 6TiSCH). Unfortunately, to the best of my knowledge, this frame version is not supported by any transceiver yet, so we would have to implement it in software. Since, AFAIK, the 2015 version of the standard is still not available for free, one might look into the 802.15.4e-2011 amendment.

@jnohlgard
Copy link
Member

The standard has been made available for free at http://standards.ieee.org/about/get/802/802.15.html in case anyone is interested in taking on this task.

@miri64
Copy link
Member

miri64 commented Sep 10, 2017

With gnrc_netif2 this can be handled GNRC-internally (as our frame building is at the moment as well), with a netopt to determine the frame version.

@kYc0o kYc0o mentioned this issue Oct 30, 2017
15 tasks
@kYc0o kYc0o added this to To Do - Issues in Network Stack Low layers Oct 30, 2017
@miri64 miri64 added Type: new feature The issue requests / The PR implemements a new feature for RIOT and removed Feature Request labels Sep 30, 2018
@stale
Copy link

stale bot commented Aug 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@miri64 miri64 added the State: don't stale State: Tell state-bot to ignore this issue label Aug 10, 2019
@stale stale bot removed the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@benpicco
Copy link
Contributor

Sci-Hub has all the standards btw 😉

@MrKevinWeiss MrKevinWeiss added this to the Release 2021.07 milestone Jun 22, 2021
@MrKevinWeiss MrKevinWeiss removed this from the Release 2021.07 milestone Jul 15, 2021
@maribu
Copy link
Member

maribu commented Sep 16, 2022

Ping?

@maribu
Copy link
Member

maribu commented May 17, 2023

PingyMcPingface?

@miri64
Copy link
Member

miri64 commented May 23, 2023

@jia200x?

@jia200x
Copy link
Member

jia200x commented May 23, 2023

I think this is not relevant anymore, as openDSME and openWSN already handle the new versions.

@maribu
Copy link
Member

maribu commented May 23, 2023

Then let's close this.

@maribu maribu closed this as completed May 23, 2023
Network Stack Low layers automation moved this from To Do - Issues to Done May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: network Area: Networking State: don't stale State: Tell state-bot to ignore this issue Type: new feature The issue requests / The PR implemements a new feature for RIOT
Projects
Development

No branches or pull requests

9 participants