Versions Compared

Key

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

...

  • Future meetings are moved to Tuesdays Pacific time.
  • Bebo: tried to contact Dr. A. Sai Sabitha by email to see how to move forward with the Android PingER project, in particular, schedule a meeting. 
    • Les will forwarded recent emails to Amity, to Bebo.- Done
    • No response from Amity to Bebo's email
  • Les: invited Dr. Taha to join the pinger-my email list. 
  • Wajahat: will provide a list of working or potentially working (e.g. being worked on) Pakistani MAs to Les. 
  • Saqib and Les: worked on being able to gather data from  2001:da8:270:2018:f816:3eff:fef3:bd3 IPv6 node in Beijing working again.
    • Added Les added a lot of debugging, now appears to be working since 9/11/2018.
  • Umar: update his section on the comparison IPv6 vs IPv4 ping RTTs and TCP vs ICMP/ping RTTs.
  • Johari: enter Umar and Dr. Taha into http://pinger.unimas.my/pinger/contact.php
  • Charnsack: We need to get the latest pinger2.pl measurement agent script installed at Ubru so we can get better logging and see why the other hosts are not being monitored.

...

For his IPv6 monitoring site pinger6.ubru.cs.ac.th Charnsak has a pinger.xml configuration file with over 160 IPv6 targets. However, there is a huge discrepancy since according to pingtable.pl there are only about 13 targets responding. We need to get the latest pinger2.pl measurement agent script installed at Ubru so we can get better logging and see why the other hosts are not being monitored.   Charnsak plans to remedy in August.

...

Saqib's future at GZHU will be much clearer after November, current contract expires February 2019. 

Gathering data is working since 9/11/2018.

Blockchain

  • Looking into moving PingER to a "blockchain" database good for decentralizing distribution of data. Monitoring sites would then be able to write to a distributed ledger. This would change the architecture to a more peer to peer architecture. It helps with continuity of PingER since reduces dependence on a single site (SLAC). See BlockChain in Future PingER Projects. Bebo sent several references to Saqib who has looked at them. We could start with real-time data without including the whole archive, i.e. in parallel to the continued centrally managed archive. It would be a private Blockchain and hence not be as compute intensive as a public blockchain. 
  • There was a meeting to discuss blockchain possibilities, see 20180709 PingER Meeting on Blockchains
  • Bebo's impression is that Saqib will lead in putting the ides in his paper into practice. Saqib will need some students.  Saqib is OK with this. He has 2 masters students but they are working in different areas.  Maybe NUST can assist with this. Saqib's partner gave a talk/paper on work so far at the New York meeting on July 31st. The talk went fine but there were not many comments/questions.
  • Saqib is pursuing PingER and Blockchain. He is looking at different references shared by Prof. Bebo and the implementation details using Hyperledger Fabric. Saqib is looking at making a test implementation. The blocksize will be 2MB-10MB. It does not appear to be computationally expensive. He will start testing with Internet of Things measurements such as humidity and temperature
  • There was a discussion on the use of DataBases and whether they could be avoided by caches. Hyperlogic keys are not in an SQL DB, basically, it appears like a cache.  there was a question whether a 10MB block would be adequate for PingER. For example, PingER from SLAC has about 700+ targets, the measurements are each 30 mins (48/day) and for pings of 100B and 1000 Bytes i.e. 2*48*700 measurements and each measurement is ~ 140Bytes, so a day's sets of measurements from just SLAC is ~ 10MBytes. We could choose to ignore the 1000Byte pings which would reduce it to ~ 5MBytes/day. The latency of retrieving a block is proportional to the block size. Things will be clearer after the test set up is in use.

...

  • Les identified and sanitized a Cross Site Scripting (XSS) exposure in ping-data.pl. He sent out a notice to update. Saqib has updated. Unfortunately cannot see from outside the Great Wall of China.
  • Les is cleaning cleaned up the Beacons. Now have 1 or more Beacons in  > 158 different countries, all are working except one inSyria.
  • There was a problem gathering data from  2001:da8:270:2018:f816:3eff:fef3:bd3 the Guangzhou IPv6 host in Beijing. Since it does not use the standard way of gathering data (ping_data.pl), but instead uses anonymous FTP, the standard way of debugging the problem does not work.  Les and Saqib worked onAdded extra debugging to gatherer, it seems OK now.

...

Next Meeting

Next meeting:  Tuesday Tuesday, November 6th 8 pm Pacific time (Nb now on winter time); Wednesday Wednesday, November 7th, 2018 9:00 am Pakistan time; 12:00 noon Malaysian & Guangzhou time; and 11 am Thailand time.

...