Time & date
Next meeting: Tuesday December 11th at 8 pm Pacific time ; Wednesday December 12th, 2018 9:00 am Pakistan time; 9:30 am India time; 12:00 noon Malaysian & Guangzhou time; and 11 am Thailand time; 6:
...
00am Jordan time (I think)
...
Format
New items and updates are in boldface.
...
- Membership of pinger-my is in https://groups.google.com.
- Bebo pointed out that the International Web Conference will be in San Francisco in 2019 (see http://www.wikicfp.com/cfp/servlet/event.showcfp?eventid=77195©ownerid=85335). There are a whole range of topics. He would love to see something submitted related to PingER.
- Maybe something on Android PingER and potential uses.
- This meeting was scheduled with the aid of a Doodle poll. It will be via Zoom. Meeting URL: of a Doodle poll.
- It was by Zoom
- It was by Zoom
Use of Zoom
Include Page PingER Meeting use of Zoom PingER Meeting use of Zoom
The use of Zoom was very successful, the instructions (above) were clear, we could hear each other clearly, we had large postage stamps showing video of each person, Les shared his screen showing the meeting notes, we successfully experimented with the leader muting others, we were able to also use a text chat feature. We will use this in the future instead of Skype. In particular, we have a scheduled meeting with the Jordan team at 8:00 pm 12/12/2018. Currently, there will be a different URL for each meeting of the form https://stanford.zoom.us/j/185360638
...
Use of Zoom
Include Page PingER Meeting use of Zoom PingER Meeting use of Zoom where the 185360538 will vary from meeting to meeting.
Action Items from previous meeting
- Figuring out how to move forward with the Android PingER project, in particular, scheduling a Skype meeting awaits Amity. Email reminder to Amity 12/6/2018. No response.
- Wajahat: will provide a list of working or potentially working (e.g. being worked on) Pakistani MAs to Les. They are working on nodes as of email 10/6/2018.
- Johari: enter Umar and Dr. Taha into http://pinger.unimas.my/pinger/contact.php, Les sent reminder email 10/3/2018. No progress 11/16/2018
...
- Bebo sent the Home page: http://www-iepm.slac.stanford.edu/pinger/, plus Remote Host site invitation letter template, Monitor Host site invitation letter template:(txt, doc), form to register a host to the contact.
- Dr Shadi Aljawarneh (<shadi.jawarneh@yahoo.com> skype ID shadi Jawarneh) is unable to attend this week. He has been out of the country, since a week for a program collaboration in India and is busy during next days in this program. It is possible that his students are working on installing the PingER MA. If possible, one of his students could join the upcoming meetings. We sent an invite, received a reply and have scheduled a Zoom meeting 8:00pm 12/12/2018 PST. A reminder was sent by Umar to the Jordan team requesting confirmation.
- At the previous meeting we discussed the many uses of PingER data including:
- the impact on network performance of events such as earthquakes, tsunamis, civil uprisings, the world cup,
- exploring the data semantically e.g. byLinked Open Data
- Correlations with other indices such as economics, human development.
- We also discussed:
- development of new low cost, low power PingER Measurement Agents (MA) utilizing Android devices.
- the possibilities of developing/utilizing a decentralized logging/analysis/presentation structure using BlockChain. This would reduce the dependence on SLAC.
...
- Amity MA is unreliable so using it for a case study does not appear fruitful. Les is working with Amity to try and understand this unreliability (emails to Amity 10/6/2018, 12/6/2018), they say "There is an internet problem we are taking care of it and will get back soon". Meeting planned soon (email reminder sent 12//6/2018), no response.
Thailand (No update 8/9/2018, No update 9/6/2018, No update 11/19/2018)
...
Email requesting update sent 12/6/2018.
UNIMAS (No update 8/9/2018, no update 9/6/2018, no update 10/7/2018, no update 11/19/2018, 12/11/2018)
Need to add Umar Kalim to http://pinger.unimas.my/pinger/contact.php. From the 7/5/2018 meeting: Johari can't ssh into the server so he will go to it on Monday. He will also upload the new UNIMAS PingER website next week.
Sent reminder emails 8/6/2018. 9/3/2018.
UUM (No update 8/9/2018, No update 9/6/2018, 11/19/2018, 12/11/2018))
Les has sent Adib updates to Figs 3, 4, 5 to extend out to 2018. This is for the paper Socio-economic Development Indices and Their Reflection on Internet Performance in ASEAN Countries
Adib will submit the paper to World Development: https://www.journals.elsevier.com/world-development
NUST: (No update 11/19/2018)
Wajahat was unable to attend but provided the following update 12/8/2018
- "We have been aggressively pursuing the three nodes(121.52.146.180 (kohat.edu.pk) down since Nov 22/2017; cae.seecs.edu.pk last time we were able to gather any data was September 2nd 2018; and pinger.isra.edu.pk no data since 5th Sept 2018, so it is a candidate to Disable). It appears to me that the participating institutes have started to lose interest in the project. Anyhow, we will keep pushing. Maybe a letter of appreciation from SLAC might rejuvenate their energies. What is your opinion.opinion?
- We also need to formulate some research problems that have the potential of appearing in some well-known places. This might help in attracting NUST students which is getting harder these days. I need your help in this regard."
UAF/GHZU (Updated 11/19/2018)
- Saqib's future at GZHU will be much clearer after November, current contract expires February 2019. Is there an update? Saqib reports that things are still unsure, his current contract cannot be renewed.
- Gathering data is no longer working. Saqib tried to make the Beijing MA live again. However, he has little control over it as it is in the CERNET cloud. The traceroute server still works. We have given up on the MA. It has been Disabled.
PingER at SLAC (Updated 11/19/2018)SLAC
PingER IPV6 support
- Les disabled the GZHU Beijing MA.
- There was a discussion on GDPR and possible implications for PingER. The PingER-my email list is a Google email list, we believe people can remove themselves. There may be some other implications however, we are not aware of them
- Les cleaned up the Beacons and added some more hosts. Now have 161 Beacons in 156 different countries, all are working.
- We now monitor 830 targets from SLAC this is an increase of ~100 in the last year and is the most monitored from SLAC ever.
- We are monitoring 48 IPv6 nodes from SLAC.
| Host | State | last seen | Status |
|---|---|---|---|
| pinger.gzhu.edu.cn | Is not working | 10/20/2018 | |
| pingersonar-um.myren.net.my | No response | 6/26/2018 | |
| pinger.isra.edu.pk | Down, it came up Sep 2-4, 2018. It is pinging, however, all the targets are not responding after 31 tries, email sent to Wajahat 9/18/2018. As of 10/14/2018 it is not pingable. | March 6, 2018 | |
| pingeramity.in | It has been working since 28th July. It is unclear how stable it is. It is down again 9/5/2018. Worked again from 9/24/2018 to 9/28/2018. Emailed Amity requesting clarification 10/3/2018. They are looking at it. | April 27, 2018 |
Context:
- Is there any statistical difference between ICMP and TCP Ping? The context here is the Internet (not data center). This is important because the network stack is different (e.g., MPI over infiniband) and latencies are significantly less.
Questions:
- Why should we focus on minimum RTT instead of average RTT
- Min RTT essentially reflects fixed delay, while average RTT subsumes variations and path load
- Link to raw results with minRTT results:
- Are the R plots generated using minRTT?
- Averages and computed. Min RTT is available. Scripts need to be updated to use minRTT.
- What is the breakdown of latency between endpoints? If there is a difference, is it because of the type or location of the source? What if the source of traffic was not SLAC? Is there a correlation with the distance between the endpoints?
- Latency for an echo packet to travel up the stack and back down is about 3.75 micro seconds (see StackMap https://www.usenix.org/conference/atc16/technical-sessions/presentation/yasukata). As expected, this is negligible when considered with milli second latencies.The remaining components would be propagation and queuing delay. As we can not breakdown the two in a public network without using an active look like
- To replicate use system tap. See: https://unix.stackexchange.com/questions/419449/how-can-i-determine-if-a-latency-is-due-to-a-driver-or-the-scheduler
- pathchirp etc, we'll continue to consider these as a single component.
- Latency for an echo packet to travel up the stack and back down is about 3.75 micro seconds (see StackMap https://www.usenix.org/conference/atc16/technical-sessions/presentation/yasukata). As expected, this is negligible when considered with milli second latencies.The remaining components would be propagation and queuing delay. As we can not breakdown the two in a public network without using an active look like
- Are the differences limited to a particular region? How do we determine/understand if traffic prioritization is implemented?Test in a controlled environment to avoid variables such as traffic prioritization, queuing delay due to cross traffic. Review the time series of latencies for both ICMP and TCP ping, instead of averages?Is there a difference between IPv4 measurements vs. IPv6.
- It may be that end hosts which are farther away have larger variances and thus the pronounced differences.
- Is there a difference between IPv4 measurements vs. IPv6.
Next Meeting
Next meeting: There will be be a Doodle poll. January week of of 14-18, 8 pm Pacific time (Nb now on winter time); a day later 9:00 am Pakistan time; 9:30 am India time; 12:00 noon Malaysian & Guangzhou time; 11 am Thailand time; 6:00am Jordan 00 am Jordan time (I think). If Shadi and Co. can attend we will move the time forward by 2 hours to accomodate accommodate the time in Jordan.
...
Old information
...