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.

Sign up for GitHub

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

Jump to bottom

Implement rejoin flow #8

Open
johanstokking opened this issue Jan 29, 2019 · 8 comments
Open

Implement rejoin flow #8

johanstokking opened this issue Jan 29, 2019 · 8 comments
Assignees
@halimi
Labels
c/network server This is related to the Network Server

Comments

@johanstokking
Copy link
Member

Summary:

Rejoin flow should be supported

Why do we need this?

To be compliant with LoRaWAN1.1 spec

What is already there? What do you see now?

No rejoin flow handling

What is missing? What do you want to see?

Rejoin flow handling

How do you propose to implement this?

It should be in big part similar to Join-Request handling

Original issue: https://github.com/TheThingsIndustries/lorawan-stack/issues/557 by @rvolosatovs
@johanstokking johanstokking added c/network server This is related to the Network Server l/open source labels Jan 29, 2019
@johanstokking johanstokking added this to the Backlog milestone Feb 6, 2019
@rvolosatovs rvolosatovs mentioned this issue Apr 18, 2019
Closed
@rvolosatovs rvolosatovs mentioned this issue Apr 30, 2019
Merged
@sentry-io
Copy link

sentry-io bot commented Mar 30, 2021

Sentry issue: THE-THINGS-STACK-7P

@nejraselimovic
Copy link
Contributor

@rvolosatovs this has been raised again recently in the Sentry issue above, are you picking it up? Can we move it from Backlog?

@johanstokking
Copy link
Member Author

Let's keep it here until we start seeing stable LoRaWAN 1.1 stacks that need this.

@htdvisser htdvisser added the needs/triage We still need to triage this label Jun 3, 2021
@nejraselimovic nejraselimovic removed the needs/triage We still need to triage this label Jun 7, 2021
@htdvisser htdvisser removed this from the Backlog milestone Jun 8, 2021
@neoaggelos neoaggelos mentioned this issue Aug 18, 2021
Open
@Ollrogge
Copy link

Hey Guys, any plans of implementing this anytime soon ?

@adriansmares adriansmares removed their assignment Sep 26, 2024
@StevenCellist
Copy link

Chiming in to say that RadioLib is ready for this! (Happy to help testing)

@johanstokking
Copy link
Member Author

LoRaWAN 1.1 has close-to-zero adoption at the moment. With LoRaWAN 1.2 coming, we will definitely implement this. Assigning @halimi. The publication of LoRaWAN 1.2 is delayed for technical reasons and won't be this year. We will have first class support for LoRaWAN 1.2 as soon as it is there.

Do you guys have a need to use rejoin with LoRaWAN 1.1 at the moment? Or is it just compliance testing?

@StevenCellist
Copy link

@johanstokking do you guys have any stats on how much the different LW versions are used? Very interested to see how many devices would use 1.1.

I don't have a use for it myself nor has there been an issue raised yet, but as the placeholders are there in RadioLib, I thought I'd offer a testing ground!

@johanstokking
Copy link
Member Author

@johanstokking do you guys have any stats on how much the different LW versions are used? Very interested to see how many devices would use 1.1.

It's non-existing, really. It's far less than 1%.

I don't have a use for it myself nor has there been an issue raised yet, but as the placeholders are there in RadioLib, I thought I'd offer a testing ground!

Thanks for that, we'll make use of it for LoRaWAN 1.2 testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@halimi halimi

Labels
c/network server This is related to the Network Server
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@htdvisser @halimi @rvolosatovs @johanstokking @Ollrogge @adriansmares @StevenCellist @nejraselimovic