-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi,
I've been playing around with some thoughts on how to improve the calculation of DNS Service Record (SRV) weights lately[0]. I would, however, like to make use of the experience of others in continuing this process. The SRV records are currently used for the sub-pools eu.pool and na.pool. Before implementing a new approach with a higher degree of complexity, that require more effort to implement, I'd appreciate feedback on the current implementation. Are the sub-pools being actively used? are they performing as it should? Or could it be modified in a simpler way and achieve the same real-world benefits? Another obvious question is the factors to consider when calculating these weights. Are there other factors than I've already proposed for a possible new implementation that should be considered? And does it make sense to adjust the weights in favor of Reverse Proxy enabled servers? Please note that [0] is still at a very preliminary stage. [0] http://kfwebs.com/sks-keyservers-SRV.pdf - -- - ---------------------------- Kristian Fiskerstrand http://www.sumptuouscapital.com Twitter: @krifisk - ---------------------------- Corruptissima re publica plurimæ leges The greater the degeneration of the republic, the more of its laws - ---------------------------- This email was digitally signed using the OpenPGP standard. If you want to read more about this The book: Sending Emails - The Safe Way: An introduction to OpenPGP security is now available in both Amazon Kindle and Paperback format at http://www.amazon.com/dp/B006RSG1S4/ - ---------------------------- Public PGP key 0xE3EDFAE3 at http://www.sumptuouscapital.com/pgp/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJPpbFLAAoJEBbgz41rC5UIpvAQAI2o8+Pmtft/gOiDhN5Cge28 u4GU9aFw0MWw2v8Ihkqzw7jG7dyoxKxLeFn6+mge3KCkjSd/TJiR7/ALUqU/sMAp XjkcRHyej+7kdb4iJSk30mzX+RmteDtEYWPMhlQSeDDPsH4HIeM64x4wWLr3QyC3 648FPh8Oaq23eK9oZDAa/cGQCAVGDo23Aqqg81QbPW2ixmMiUR9+GRK7npKYksYb Q861gClxl1eqrpPzCz2DhrSZywKOqv/taBwvCv6awkJXVz5V/acuoY5y/FQ22pGR J52q6BA51XVL1sAfeT3O4Ot3lhI+BKb1k6NJQcdafqNL3Ch2/WfPh5EDlfjRhLBd vivFZ3NrWdZZESRF7edOGWp7aMxDxnZj5mw3XA+ldJjTV0Aj7+Tp9rsejAkXOv+V VcSAEUedbQPBIDyY0EfQ6pD7JVw9VGqFvGunBhbQ1pp0WVbcEZcEdyvGFhIc0bWo AU60mNO6gqP1/WAuTKiRkpJxFgKT/bVtIUxvlabxV6CF9As3YV614tJe+9BUT78O COOddJQXG+Ztd6wnd2TnOF4lGxSCo3z47rgJjmsZfCGBXru007EBfkERZd9m4Zjv MNyzXxMJ7kqbOX7iN4GUrApZ2sm0XXRvPO/UZQtXlMao0U+yF5TtkvEYVMYwwTFB rQb6lNtLYcDwws+j1T+i =aHpi -----END PGP SIGNATURE----- _______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel