Ripe Probes and Android
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).
Hi Stefan, Unfortunately, I was not able to attend RIPE 64. Just to clarify: Is this Android app intended to be an interface to the Atlas data, or an Atlas probe that runs on a smart phone? Thanks, --Richard On May 2, 2012, at 7:16 AM, Stefan Wahl wrote:
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).
On 05/02/2012 03:25 PM, Richard L. Barnes wrote:
Hi Stefan,
Unfortunately, I was not able to attend RIPE 64. Just to clarify: Is this Android app intended to be an interface to the Atlas data, or an Atlas probe that runs on a smart phone?
It clearly is the former: an Android application to browse Atlas data. Stefan was so kind to attach my initial concept document to his introduction of mine. It should answer most questions pertaining to the intended feature set of the application.
Thanks, --Richard
Greetings Ingo
On May 2, 2012, at 7:16 AM, Stefan Wahl wrote:
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
Hi, On Wed, May 02, 2012 at 07:22:23PM +0200, Ingo Albrecht wrote:
On 05/02/2012 03:25 PM, Richard L. Barnes wrote:
Unfortunately, I was not able to attend RIPE 64. Just to clarify: Is this Android app intended to be an interface to the Atlas data, or an Atlas probe that runs on a smart phone?
It clearly is the former: an Android application to browse Atlas data.
Actually, I had the same thoughts as Richard - why not turn Android into the biggest population of Atlas swarm intelligence ever? :-) A user interface sounds nice, but "use the web" is good enough for me, and will work on iThings as well... Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
In your letter dated Wed, 2 May 2012 21:39:12 +0200 you wrote:
Actually, I had the same thoughts as Richard - why not turn Android into the biggest population of Atlas swarm intelligence ever? :-)
Ignoring, all kinds of technical and political issues, just 4 kilobits per second translates into more than 1 gigabyte per month. That's more than I have in my current dataplan. At the same time, the most variable part in a 3g internet connection is the 3g connection itself. And so far, measuring the local loop is not one of the main goals of the Atlas project.
Dear Stefan, Ingo, all, (sorry for the delay in responding) On 5/2/12 1:16 PM, Stefan Wahl wrote:
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".
thank you for your interest in Atlas data! We appreciate your initiative: to propose an alternative way to access and view Atlas, and for investing work in coming up with a proposal. I will respond to your concrete questions privately, and let's work together on looking into the requirements for the Android app, along with taking into consideration our other priorities. Regards, Vesna -- Vesna Manojlovic BECHA@ripe.net Senior Community Builder +31205354444 for Measurements Tools RIPE NCC http://ripe.net
participants (7)
-
Gert Doering -
Ingo Albrecht -
Philip Homburg -
Randy Bush -
Richard L. Barnes -
Stefan Wahl -
Vesna Manojlovic