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

unified Israel, Gaza and West Bank to AS923-4 #31

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gradoj
Copy link
Collaborator

@gradoj gradoj commented Apr 29, 2022

This fixes #30

Before with Gaza and West Bank Unknown:
image

After with Gaza and West Bank set to AS923-4:
image

@gradoj gradoj changed the title unified Israel, Gaza and West Bank to AS923-4 unified Israel, Gaza and West Bank to AS923-4 fixes #30 Apr 29, 2022
@gradoj gradoj changed the title unified Israel, Gaza and West Bank to AS923-4 fixes #30 unified Israel, Gaza and West Bank to AS923-4 Apr 29, 2022
@abhay
Copy link
Collaborator

abhay commented Apr 29, 2022

I agree with having this area have a regional value but do we have any lorawan alliance documentation on what frequency plan it should be?

@gradoj
Copy link
Collaborator Author

gradoj commented Apr 29, 2022

from version 1.0.3 of the regional parameters
image

@eladraviv
Copy link

Hi guys,
Can you please merge this commit?

Thanks!
Elad.

@gradoj
Copy link
Collaborator Author

gradoj commented May 6, 2022

I'm not sure of the exact process but I doubt this is going to happen quickly. It's going to take someone to advocate in hip-45 on discord and get this infront of the lorawan alliance

@eladraviv
Copy link

Thanks @gradoj .
@abhay - can you please share what is the process of committing this fix?
I can do whatever needed, just not sure what and where...

@abhay
Copy link
Collaborator

abhay commented May 8, 2022

The LoRa Alliance is an organization that manages regional plans around the world. Once they define a plan for this area, the process is approximately:

  1. Merge this PR (if it's what the alliance decides).
  2. Generate the chain variables that reflect the PRs changes
  3. Have the variable signed and deployed on chain.

The hardest part here isn't really technical but rather getting the LoRa Alliance to figure out what they want to do here but as soon as the standards body makes a decision, we can move quickly on our network.

@eladraviv
Copy link

Thanks @abhay , understood.
I will try to see if I can approach LoRa Alliance in order to push this decision.

@eladraviv
Copy link

@gradoj , @abhay
I approached LoRa Alliance and I will wait for their response.
But I must say I think there is a more basic logical error here - while Gaza strip is indeed a different entity and should get it's own parameters from the LoRa Alliance, the West Bank on the other hand is under Israel authorities and Israeli's Ministry of Communication rules and laws.
Decouple the west bank from Israel regional parameter can be a source of future problem because it must always match Israel frequency (otherwise in practice the law enforcement in the region will shut down communication in frequencies not authorized by Israel Ministry of Communication), and there is no sense in holding 2 separate variables where one must always be the same as the other.

Thanks,
Elad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Entire Israel West Bank area is not recognized as Israel
3 participants