Proposal 165: Easy migration for voting authority sets

[Sebastian Hahn]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This time, it really is the right feedback for 165. I almost promise.

On May 28, 2009, at 6:51 PM, Nick Mathewson wrote:
> Filename: 165-simple-robust-voting.txt

I thought about issues when we add/remove more than one authority  
before all operators had a chance to upgrade or upgrade again (in case  
of removal), but couldn't come up with an actually bad situation. But  
this led to the realization that the work flow described just talks  
about one authority getting added/removed at a time, I think the  
situation with more than one change can quickly get complex (and it's  
easy to imagine that with 15 authorities, some operators will be on  
vacation for a month, for example). The proposal could maybe be  
clearer on how those cases should be handled by the operators.


Sebastian

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAkopuuAACgkQCADWu989zubVMgCgzxFa/rdmmyRcOEpUPb36NsNS
24wAoLOKxbQ1xN6ScEAswcB2SRXEhdUr
=hvZP
-----END PGP SIGNATURE-----