add proposal about planned/unplanned downtime tracking and bootnode a…

…udits

proposals/4_planned_downtime_for_geodns.md

@@ -0,0 +1,19 @@
+# Planned downtime in the GeoDNS service
+
+Currently the GeoDNS service is being run by 2 members that are expected to
+remove manually the participants for the service and thats just hell of a 
+burden for them to remove and add the participants back manually.
+
+For example being removed from the GeoDNS the traffic from philippines
+moves to use following endpoints when removed that seems suboptimal.
+```bash
+PING sys.dotters.network (103.240.197.6) 56(84) bytes of data.
+64 bytes from 103.240.197.6: icmp_seq=1 ttl=50 time=387 ms
+
+PING sys.ibp.network (104.247.178.10) 56(84) bytes of data.
+64 bytes from 104.247.178.10: icmp_seq=1 ttl=236 time=311 ms
+```
+
+I propose to have a api/onchain-remarks for each participant to be able
+to set a planned downtime for the services that GeoDNS code follows and
+takes actions based on.

proposals/5_bootnode_audits.md

@@ -0,0 +1,13 @@
+# Bootnode audits 
+
+I am planning to proceed with the following audits to bootnodes:
+
+1. Go through polkadot-sdk / encointer / paseo chain-specs and
+compare them with the ibp-network/config/bootnodes.json file.
+2. Write helper functions to find missing entries.
+3. Fill in the missing entries based on the official chain-specs.
+4. Notify about missing bootnode entries to the syncicate members.
+5. Once all bootnodes are added, develope a script to check the bootnodes.
+6. Write daily monitoring that all bootnodes are in syncable condition.
+
+