inital outline of LoRa Class-C HIP

00XY-lorawan-class-c.md

@@ -0,0 +1,70 @@
+# LoRaWAN Class-C Implementation
+
+- Author(s): [@leogaggl](https://github.com/leogaggl), [@vkynchev](https://github.com/vkynchev), [@KenD123](https://github.com/KenD123)
+- Start Date: 2022-07-17
+- Category: technical
+- Original HIP PR: <!-- leave this empty; maintainer will fill in ID of this pull request -->
+- Tracking Issue: <!-- leave this empty; maintainer will create a discussion issue -->
+
+# Summary
+[summary]: #summary
+
+Currently Helium LoRaWAN Router does not 
+
+# Motivation
+[motivation]: #motivation
+
+Currently Helium is one of the few LNS where it's router does not support LoRaWAN Class-C downlinks.
+
+
+# Stakeholders
+[stakeholders]: #stakeholders
+
+
+
+We have started reaching out to people
+ - Github repository feedback
+ - Helium Community HIP Discord channel
+ - Other relevant Helium Community Discord channels.
+
+# Detailed Explanation
+[detailed-explanation]: #detailed-explanation
+
+
+
+
+# Drawbacks
+[drawbacks]: #drawbacks
+
+None.
+
+
+# Rationale and Alternatives
+[alternatives]: #rationale-and-alternatives
+
+- Why is this design the best in the space of possible designs?
+
+
+
+# Unresolved Questions
+[unresolved]: #unresolved-questions
+
+
+- Issue escalation procedure with Alliance
+- Positive mental health of members (including reduction of burnout)
+- Risk management.
+
+- [TODO] add some more. 
+
+# Deployment Impact
+[deployment-impact]: #deployment-impact
+
+There is no deployment impact. 
+
+# Success Metrics
+[success-metrics]: #success-metrics
+
+What metrics can be used to measure the success of this design?
+
+- increase in data transfer
+- increase in device numbers