-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/25/2013 03:00 PM, Randy Bush wrote: >> For me the most important point is that it is managed on IETF (or IETF's >> contractor) servers. > > as no private data are involved, i am curious why? > Because public does not mean unlimited availability. Let's say that the IETF decides to use a collaboration tool hosted by a service run by an external company. The data is public (although it can be stored in a proprietary format) so anybody can consult it. But suddenly the service is bankrupted/become collateral damage when servers are seized/has its certificates expiring/etc... Unless someone did some preventive data liberation, the data is no longer available, at least until whatever caused the problem is solved. - -- Marc Petit-Huguenin Email: marc@xxxxxxxxxxxxxxxxxx Blog: http://blog.marc.petit-huguenin.org Profile: http://www.linkedin.com/in/petithug -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRK/OkAAoJECnERZXWan7EP/gQAK+bhwya94XYiAXwvwlR5bTX ejSRx7Z8OhE25ggkNOBmY/zaRNyfmFSxmPGlEMWrMjDd/3n761NjyOHnHksNyqT4 WVUbPwIy0fFKPwVsWp6YzrmrmuFkwL3NOGjgBRXQuO1N0dLj42yk1NbSrqxfSzXx wiUCu+U3ucCD7F5aNg3tZh+6BNMCbFjjk9KKrylxfRtg0x1lJjNuPkXUhIsyQLer fwqeRAzZhFBT5xo1Nr0lijb6Eu1rYZjaMESQTPs8IquDI0FLrxLvwyiO7wCK7s5Y b21qN+/yZaxxqgbv3om0gRwWx7r2MZshZD5TXGE7XiUfiTHkp7tgP/ymnh9U2t39 JcnXocng470JfewJk1+zBzrfriTGSpaSK0RpDRd+Ft/KLT4J5iBoD2/5AR3PCWwM nHiab1UqdKEsyMuNEEPSA7xaM0N401IRVePaVv7Woo7YtbrEKmXCwwqQERy2hgqJ W4RSIg8BrI1FTztkRFWrvYZYhU7nIiQY9lxBW7Un84aWeS78TS6ePPfDmVPjPk2e GAV9DQw6yf21hdiHwP0slHeKrcSYA/sNu1vq7f8j1+ympJrqvA6b7/kZzCRx8YNI NYYgEvp4Z8ISCzyIOr16L6M7zs0yAwDHRxCU22tjMIq3GH33nKWpDjIw/RU9sekX /1LePxXi9Xs+mZLAa0KO =7oou -----END PGP SIGNATURE-----