John - Apologies for this late reply to your comment. I think that the way to get started about ARETF / ARSO is... to start. The problem I think that both ideas are trying to solve is that there's no easy / centralized method such as an index or a wiki for someone with a good idea to look and see if it's already been done... is there pri…
John - Apologies for this late reply to your comment. I think that the way to get started about ARETF / ARSO is... to start. The problem I think that both ideas are trying to solve is that there's no easy / centralized method such as an index or a wiki for someone with a good idea to look and see if it's already been done... is there prior art? One recent example I've seen is that there are three independent implementations of using small, inexpensive microcontrollers as Packet Radio Modems, and as well-connected as I am, I keep finding additional implementations. Rounding all of those up in one place would be a good start. The steps to implementing ARETF / ARSO would be:
* Create a starting point - website, wiki, Wordpress, etc.
* Give it a reasonable lifespan - prepay hosting fees, etc. for at least a couple of years.
* Put a few reference standards up and ask for feedback.
* Try to form a group of likeminded folks.
* Find a group that has a 501(c)(3) that is willing to "pass through" funding should the group obtain a grant.
* Apply for an ARDC grant for funding, such as paying hosting fees for 5, maybe even as long as ten years.
* Lather, rinse, repeat.
Some example standards that need to be gathered:
* Open source AX.25 stacks - there are implementations in Linux, in JNOS, in Dire Wolf, in every APRS tracker, etc. Make those easy to find if you're creating something new that requires an AX.25 stack so you don't waste time re-inventing an AX.25 stack.
Lastly, while I think that ARETF / ARSO is a good idea and needed, I know myself and my limitations (bandwidth) that I cannot create such a project - the majority of my creative energies and time is now being consumed by Zero Retries. That said, I'd be happy to advise, and contribute (hey, look at this, yet ANOTHER open source AX.25 stack...).
John, Thanks VERY much for seriously considering implementing this idea. I think it's really needed in Amateur Radio now that much... MOST... of the technological innovation in Amateur Radio is now being done in the Software realm.
Late update:
Here's a perfect example of a good / needed use of ARETF / ARSO - Improved Layer 2 Protocol (IL2P) Forward Error Correction (FEC). It was originally implemented in the NinoTNC, was added into Dire Wolf Software TNC, and it will be used on the forthcoming MMDVM-TNC. The latter two are independent implementations (with some help from the author) made possible because of a well-written specification document. Amateur Radio data communications has long suffered from lack of Forward Error Correction, and now IL2P is available as open source, and we should make it as easy as possible to incorporate it in any new data communications system in Amateur Radio.
John - Apologies for this late reply to your comment. I think that the way to get started about ARETF / ARSO is... to start. The problem I think that both ideas are trying to solve is that there's no easy / centralized method such as an index or a wiki for someone with a good idea to look and see if it's already been done... is there prior art? One recent example I've seen is that there are three independent implementations of using small, inexpensive microcontrollers as Packet Radio Modems, and as well-connected as I am, I keep finding additional implementations. Rounding all of those up in one place would be a good start. The steps to implementing ARETF / ARSO would be:
* Create a starting point - website, wiki, Wordpress, etc.
* Give it a reasonable lifespan - prepay hosting fees, etc. for at least a couple of years.
* Put a few reference standards up and ask for feedback.
* Try to form a group of likeminded folks.
* Find a group that has a 501(c)(3) that is willing to "pass through" funding should the group obtain a grant.
* Apply for an ARDC grant for funding, such as paying hosting fees for 5, maybe even as long as ten years.
* Lather, rinse, repeat.
Some example standards that need to be gathered:
* Open source AX.25 stacks - there are implementations in Linux, in JNOS, in Dire Wolf, in every APRS tracker, etc. Make those easy to find if you're creating something new that requires an AX.25 stack so you don't waste time re-inventing an AX.25 stack.
Lastly, while I think that ARETF / ARSO is a good idea and needed, I know myself and my limitations (bandwidth) that I cannot create such a project - the majority of my creative energies and time is now being consumed by Zero Retries. That said, I'd be happy to advise, and contribute (hey, look at this, yet ANOTHER open source AX.25 stack...).
John, Thanks VERY much for seriously considering implementing this idea. I think it's really needed in Amateur Radio now that much... MOST... of the technological innovation in Amateur Radio is now being done in the Software realm.
Late update:
Here's a perfect example of a good / needed use of ARETF / ARSO - Improved Layer 2 Protocol (IL2P) Forward Error Correction (FEC). It was originally implemented in the NinoTNC, was added into Dire Wolf Software TNC, and it will be used on the forthcoming MMDVM-TNC. The latter two are independent implementations (with some help from the author) made possible because of a well-written specification document. Amateur Radio data communications has long suffered from lack of Forward Error Correction, and now IL2P is available as open source, and we should make it as easy as possible to incorporate it in any new data communications system in Amateur Radio.