about me

It's not in the program yet but it looks like most of these items have been on the talking block to embed in the user interface and expose via standard protocols. An example of a thought on information that had been discussed (but all the coders have been busy on bug fixes or hardware enhancements at moment or larger features) is in a early min draft discussed previously http://bloodhound.aredn.org/products/AREDN/wiki/develsandbox/SNMPMib I belive SNMP is slated to make it into a public build soon (tickets already closed on bloodhound) and in a future version it would be expanded (both GUI and mib) to expose more data about the nodes that can be accessed in a standard manner across the network. A lot of these projects just need someone to be willing to adopt them and work with them. Only so many hours in the day many items I think all of us (those active in coding and those using) would like to see just need someone to adopt them and take lead on discussing then. It's generally much better in my opinion to standardized and build in than it is to ADHOC it for a reliable network that can grow predictably. Take a look at the draft mib for some of the suggested items a node should know, like its location, it's owner, it's antenna deployment (predictive mapping and aiming). It's Emcomm capabilities (will it run w/I power and if so how long, etc).