Summary and Motivation
Currently, packets that are not under the Helium NetID are dropped. They belong
to other networks, such as Actility or Senet. However, these other networks
have manifested interest in purchasing these packets and thus "roaming" on the
Helium Network. Ultimately, enabling this makes the existing infrastructure
more valuable as the same hotspots (LoRaWAN gateways) can provide coverage for
these existing LoRaWAN Networks.
We propose to create a new chain_var that maps NetID to OUI. This mapping
will be maintained by the DeWi LoRaWAN Committee who can receive requests from
NetID owners to route these frames to one or many OUIs.
Rendered view
https://github.com/helium/HIP/blob/master/0046-lorawan-netid-routing.md
Summary and Motivation
Currently, packets that are not under the Helium NetID are dropped. They belong
to other networks, such as Actility or Senet. However, these other networks
have manifested interest in purchasing these packets and thus "roaming" on the
Helium Network. Ultimately, enabling this makes the existing infrastructure
more valuable as the same hotspots (LoRaWAN gateways) can provide coverage for
these existing LoRaWAN Networks.
We propose to create a new
chain_varthat maps NetID to OUI. This mappingwill be maintained by the DeWi LoRaWAN Committee who can receive requests from
NetID owners to route these frames to one or many OUIs.
Rendered view
https://github.com/helium/HIP/blob/master/0046-lorawan-netid-routing.md