Versions Compared

Old Version 22

changes.mady.by.user Les Cottrell

Saved on

compared with

New Version 23

changes.mady.by.user Les Cottrell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Time & date 

This meeting:  March 14th,  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.

Format

New items and updates are in boldface.

Coordinates of team members:

Mailing list: pinger-my@googlegroups.com for membership see  https://groups.google.com.

  • Invitation to Saif A. Kazakzeh (xsaifahmadx@gmail.com) of Jordan still pending, awaits Saif response

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 via Doodle 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
Actual Attendees

 

Others

Administration

Use of Zoom

 

IMPORTANT NOTE: The meeting is setup to record automatically. By joining the meeting you are agreeing to being 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-Mac

Jordan  (Updated 3/6/2019)

We had a Zoom meeting with Eyad and Baraa of the Jordan team.

Amity (Updated 3/3/2019).

Amity team photo:

The following are the data analysis projects:

...

Bebo will contact Topher, and look at installing on a spare Android at Bebo's home in San Francisco.  We could also do that at SLAC. Topher will get us some Android phones when he gets back in early March.

Adib (Updated 3/3/2019)

Bebo reviewed and responded to Adib suggesting the second one is a better choice.

 

NUST: (Updated 3/3/2019)

Unable to gather data from maggie1.seecs.edu.pk and monitor.seecs.edu.pk. Email sent 1/26/2019

  • results{monitor.seecs.edu.pk}[0] not defined, unable to gather data for 11 consecutive days this month
  • Skipping monitor.seecs.edu.pk(5) does not ping by name or address 111.68.101.10. Wajahat will look at it.
  • Wajahat fixed maggie.seecs.edu.pk 2/29/2019, Les sent email 2/3/2019 to Wajahat asking about monitor1.seecs.edu.pk.
  • pinger.isra.edu.pk is not pingable and unable to gather data starting 2/11/2019. We will wait a few days and see if it recovers.

Wajahat 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?

  • 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:

    • 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?

Saqib sent email to Wajahat:

  • As discussed in the last meeting, kindly check if it is possible to get an IPv6 address in NUST for installing an IPv6 MA in PK. I will also contact PERN regarding the possibility of getting an IPv6 address. 
  • Wajahat is moving from one office to another in NUST. There are IPs but he has not been able to get to the right person. He will update if situation changes.

UAF/GHZU (Updated 3/3/2019)

  • Saqib's current contract expires February 2019. Saqib reports that things are still unsure, his current contract cannot be renewed. He will return to Pakistan February 15th 2019. He has applied to multiple places in China, Pakistan, etc. He will probably join the University of Agriculture in Faisalabad. He plans to pursue the blockchain paper.
  • Bebo sent email:
    • 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?
      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

Thailand (No update 8/9/2018, No update 9/6/2018, No update 11/19/2018, 1/15/2019, 2/12/2019)

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.

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, 1/15/2019, 2/12/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
  • 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?
  • 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, March week 11-14th 10 pm Pacific time ; a day later 11:00 am Pakistan time; 11:30 am India time; 2:00 pm Malaysian & Guangzhou time;  1:00 pm Thailand time; 8:00 am Jordan time.  We moved the time forward by 2 hours to accommodate the time in Jordan.

...

Old information