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?

from version 1.0.3 of the regional parameters

Hi guys,
Can you please merge this commit?

Thanks!
Elad.

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

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...

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.

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

@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.