Time & date
This meeting: Week of April 24 10 pm Pacific time (Nb now on summer time); a day later 10:00 am Pakistan time; 10:30 am India time; 1:00 pm Malaysian & Guangzhou time; 12:00 pm Thailand time; 7:00 am Jordan and 6:00am Turkey.
Doodle poll invites sent 4/10/2019.
Format
New items and updates are in boldface. Action/discussion items are in red
Coordinates of team members:
Mailing list: pinger-my@googlegroups.com for membership see https://groups.google.com.
- Saif A. Kazakzeh (xsaifahmadx@gmail.com) of Jordan added.
Attendees
Invitees:
Wajahat Hussain+ (SEECS), Saqib+ (GZHU); Johari (UNIMAS); Adib (Turkey); Dr. Charnsak Srisawatsakul (Ubru), Eyad Ayoubi (Jordan), Baraa Muslmani+ ( Jordan), Dr. Shadi Jawarneh (Jordan), Bebo White+, Umar Kalim, Les Cottrell+
- + Responded via Doodle will attend; - Responded, but unable to attend on this date; ? extra email sent asking if attending
- Email addresses (all the following are in pinger-my).
- cottrell@slac.stanford.edu; wajahat.hussain@seecs.edu.pk; saqibutm@outlook.com; johari.abdullah@gmail.com; adibhabbal@karabuk.edu.tr; charnsak.s@ubru.ac.th; eyadayoubi@gmail.com; b.muslmani@yahoo.com; shadi.jawarneh@yahoo.com; bebo@slac.stanford.edu; kalim@slac.stanford.edu; xsaifahmadx@gmail.com
Actual Attendees
Bebo, Saqib, Les
Others
Administration
- Set up email list pinger-am@googlegroups.com in https://groups.google.com for the Amity PingER team including Aayush Jain, James David, Naman Madan, Dr Sai Sabitha. Sent invites 1/26/2018.
- This meeting was scheduled with the aid of a Doodle poll.
- It was by Zoom
Use of Zoom
IMPORTANT NOTE: The meeting is set up to record automatically. By joining the meeting you are agreeing to be recorded. (see details.
Also, note that daylight savings time will kick in on Sunday 3/10. Therefore, please consult the time conversion table here.
What: PingER Standing Meeting
When: Mar 14, 2019, 10:00 PM Pacific Time (US and Canada)
Where: Join from PC, Mac, Linux, iOS or Android: https://stanford.zoom.us/j/201093085
How to set up and use Zoom:
To use the software, you would have to download the Zoom client (and installed if prompted). The instructions to do so are listed here: https://zoom.us/download#client_4meeting
The instructions about setting up the software are listed at the URL below. You may want to create an account if you do not have one already. If you are invited to a meeting (i.e., you are not hosting the meeting), you are not required to create an account; you can simply join the meeting using the meeting ID.
https://support.zoom.us/hc/en-us/articles/201362033-Getting-Started-on-PC-and-MacJordan (Updated 3/6/2019)
- Baraa is interested in monitoring other Jordanian hosts. There are 4 other existing targets in Jordan.
- http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=JO.EDU.GJU.WWW&monalias=EDU.SLAC.STANFORD.PINGER
- http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=JO.GOV.CBJ.WWW.N1&monalias=EDU.SLAC.STANFORD.PINGER
- http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=JO.JUST.EDU.N1&monalias=EDU.SLAC.STANFORD.PINGER
- http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=JO.NEXT.WWW&monalias=EDU.SLAC.STANFORD.PINGER
- If there are other sites in Jordan that should be monitored from say SLAC and Jordan please let Les know the details and he can add them to the PingER Oracle NODEDETAILS database, so they are monitored from SLAC. If they are to be monitored from Telephoenics then they will need to be added to the <HostList>stanza of the Telephoenics pinger.xml.
- Baraa asked what the criteria are for choosing targets, emailed him (4/4/2019) about Finding PingER Hosts
Turkey
...
Amity (Updated 3/3/2019).
Amity team photo:
The following are the data analysis projects:
...
- Topher is back, Bebo is contacting him
Adib (Updated 3/3/2019)
- Adib moved to Karabuk University in Turkey where he is an Associate Professor.
- The time difference would probably require a change in meeting time (e.g. 10:00 pm SLAC = 6:00 am Turkey)
- He will discuss with the department head about installing a PingER MA there.
- Regarding the paper, it has been submitted to Journal: Computer Communications
Title: Socio-economic Development Indices and Their Reflection on Internet Performance in ASEAN Countries
Corresponding Author: Adib Habbal
Co-Authors: Les Cottrell, Emmanuel Mkpojiogu, Bebo White, Suhaidi Hassan, Faisal Zulhumadi Unfortunately, it was rejected.
Adib, Bebo and Les are looking for another journal, some possibilities include: https://webscience-journal.net/webscience,https://www.journals.elsevier.com/business-horizons, https://www.journals.elsevier.com/government-information-quarterlyAdib is wondering about- Journal of Computer Information Systemshttps://www.tandfonline.com/action/journalInformation?show=aimsScope&journalCode=ucis20
- The Information Societyhttps://www.tandfonline.com/action/journalInformation?show=aimsScope&journalCode=utis20
Bebo reviewed and responded to Adib suggesting the second one is a better choice. Adib will submit it to the 2nd journal.
NUST: (Updated 3/9/2019)
Wajahat raised the topic: 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.
Discussion . (Wajahat was this useful? Is there something else? Email sent 3/15/2019):
- There is a web page at Future PingER Projects which was last updated July 2018. Topics that currently stand out include:
- Applying Blockchain to PingER data, see the paper by Saqib, here.
- Graphical traceroute maps. Note currently when one looks up the location of a router, it usually gives the location of the home site that is managing the routers, e.g. ESnet routers in the US and Europe are all identified as being at LBL. Using ping minimum RTTs to a router from multiple sites (e.g. the perfSONAR traceroute servers in the US, Canada, and Europe, see http://www.slac.stanford.edu/comp/net/wan-mon/viper/tulipmap.html) one can use trilateration to identify the location of the router. Earlier work on this can be found at http://www.slac.stanford.edu/comp/net/tulip/
- Deploying Android/Pinger devices, understand how their low cost (cheap enough to be disposable), low power (e.g. use of solar power) and potential mobility may be used, i.e. the risks, mitigations, and benefits.
- Linked Open Data applied to PingER data.
- Using PingER data as a source of big data to search anomalies, trends etc.
- Case studies, e.g. can one identify the impact on networking of social unrest such as the current Venezuala difficulties, or of other events such as earthquakes or Tsunamis.
- I have increased the number of working Venezuelan target hosts monitored from SLAC from 3 to 8, to possibly assist in this.
- Another interesting case study would be to look at the impact of hurricanes on Internet connectivity in say the Caribbean, see for example Hurricanes Irma and Maria 2017.
- Compare and contrast IPv6 with IPv4 behavior, identify outliers and understand - Umar, Les, and Saqib are looking at this.
- Also, see PingER Papers and Presentations for some topics that have recently resulted in papers.
- Are any of these of interest?
- There is a web page at Future PingER Projects which was last updated July 2018. Topics that currently stand out include:
- Wajahat also suggested a letter to the higher-ups at NUST about PingER would assist. Les worked with Wajahat to craft such a letter. It was sent to Wajahat by email 4/3/2019. It was sent by paper mail 4/4/2019 to Principal SEECS.
IPv6 host at NUST:
- Wajhat has requested Hasan to install PingER on an IPv6 host at NUST, Saqib has contacted Hasan to tell him where to find and upload the code.
UAF/GHZU (Updated 3/3/2019)
- Saqib joined the University of Agriculture in Faisalabad. He plans to pursue the blockchain paper.
- Bebo sent email, see below. Saqib will follow up.
- Not sure whether this would be relevant for PingER work - maybe Saqib's blockchain paper? I'm not sure that there has been much discussion re: PingER security - thoughts? The submission is due May 24th
Bebo- From: Security and Communication Networks <scn@journals.hindawi.com>Sent: Monday, February 25, 2019 11:58 PM
To: White, Bebo
Subject: Special Issue: "Cryptography and Security Tools and Techniques for Networked Embedded Systems"Dear Dr. White, We are currently accepting submissions for our upcoming Special Issue titled
"Cryptography and Security Tools and Techniques for Networked Embedded Systems," which will
be published in Security and Communication Networks in October 2019. The Special Issue is open to both
original research articles and review articles, and the deadline for submission is May 24, 2019.
You can find the Call for Papers at https://www.hindawi.com/journals/scn/si/136986/cfp/.
Security and Communication Networks is a peer-reviewed journal published by Hindawi
as part of a publishing collaboration with John Wiley & Sons (https://www.hindawi.com/wiley.hindawi/).
Starting January 2017, the journal has been converted to a fully open access publication, which
means that anyone can access it online without a subscription and authors retain the copyright of their work.
The most recent Impact Factor for Security and Communication Networks is 0.904 according to Clarivate Analytics' l
atest Journal Citation Reports. The journal's most recent CiteScore is 1.36 according to the latest
CiteScore metrics released by Scopus. Please read over the journal's author guidelines at
https://www.hindawi.com/journals/scn/guidelines/ for more information on the journal's policies and
the submission process. Manuscripts should be submitted online to the Special Issue at
https://mts.hindawi.com/submit/journals/scn/adcsc/.
Please do not hesitate to contact me if you have any questions. Best regards, Rana Khaled
- From: Security and Communication Networks <scn@journals.hindawi.com>
- Not sure whether this would be relevant for PingER work - maybe Saqib's blockchain paper? I'm not sure that there has been much discussion re: PingER security - thoughts? The submission is due May 24th
Thailand, Charnsak
Charnsak is looking at a host in Champasak University, Chan Parsa province in Laos as a potential site for a PingER MA. Charnsak just got approved to make contact with the Champasak University. He expects to set up the MA in the next 4-5 months (say towards end 2018). It also depends on the partner university, and there may be a lot of paperwork. 4/9/2019 Charnsak said we need to drop this.
UNIMAS (No update 8/9/2018, no update 9/6/2018, no update 10/7/2018, no update 11/19/2018, 12/11/2018, 1/15/2019, 2/12/2019, 3/14/2019)
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.
...
- 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.
Next Meeting
Next meeting: There will be a Doodle poll, May week 13th-16th 10 pm Pacific time; a day later 10:00 am Pakistan time; 10:30 am India time; 1:00 pm Malaysian & Guangzhou time; 2:00 pm Thailand time; 7:00 am Jordan time. 6:00am Turkey time. Any thoughts on time of day.
...