Hi, as promised in Ripe64, I want to introduce Ingo Albrecht. He is the person, who is in charge and the owner of the project "Android and Atlas Probes". He sent me a paper called "inital-concept", which I would like to copy to the mailing-list. I hope that we will get a lot of feedback and make progress in defining and funding the project. greetings from Berlin Stefan Wahl Ingo Albrecht: GENERAL CONCEPT The client should implement a proper subset of the features present in the web interface, limiting itself to the most common and most operationally useful features. As such, emphasis should be given to "general" information that has use in network operations, as opposed to "specific" detailed information. Display should concentrate on displaying "current" information as opposed to browsing history, for which a laptop is much better suited. As an example, consider display of per-probe data. The client should display basic probe information and current/recent measurement results, not a whole set of graphs. Also, emphasis should be given to search as opposed to full-list browsing, facilitating ad-hoc use. DEVELOPMENT PROCESS Development would progress in monthly stages, accompanied by public release from the second stage on. The feature set specified in this document should be achievable within 3 to 5 such stages. This concept would be revised during each stage, allowing for integration of feedback. As the developer, I propose that the source code for the project, including history, be published via github or similar. FEATURES Base features: * Display of announcements * Display of "My Probes" list * Display as list * Display map of own probes * Search for probes by AS, IP4/IP6 prefix, country * Result display as list * Result display as map * Notification when a users own probes go down or stay down * Configurable "acceptable downtime" * Configurable "silent times" based on phone timezone * Probe view (reachable from probe lists and maps) * Display standing data * Display most recent measurements Basic browsing features: * View standard measurements (equivalent of "Maps" view) * Fixed destination measurements (reachability and RTT) * Limitable by probe AS and prefix * Limitable by destination * DNS measurements (instance choice and RTT) * Limitable by probe AS and prefix * Limitable by root instance continent * Limitable by specific root instance UDM features: * Display of configured UDMs * Adding/removing UDMs * Display of most recent UDM results * Possibly with history * Maybe with graphs Features not considered: Display of coverage information (not terribly useful ad-hoc).