-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
new-lir@ripe.net and enum@ripe.net is one of the first pieces that we need to remove in order to phase out all the legacy software.
I can't see that this would be a step forward.
PGP-signed mails were introduced to ensure mails from the NCC could be trusted, and I do not see this requirement as "having gone away".
I don't think the requirement has gone away, but I am not sure that maintaining PGP signatures in the emails is actually fulfilling it. I would very much like to know if anyone is regularly checking the PGP signatures of tickets in their workflow (and, if that number is very small, whether there are other sensible ways to fulfil this requirement.) Otherwise, PGP signing is just not solving this problem, and keeping it in place only makes sense if we have confidence that this will change on the user side. Usage (current and future) is the only material point here, imo. We should resist the temptation to get into a discussion of relative costs and technology options. Arbitrarily adding more people to that sort of internal business discussion is not likely to make a better decision. Best regards, Dave - -- Dave Wilson, Project Manager HEAnet Limited, Ireland's Education and Research Network 1st Floor, 5 George's Dock, IFSC, Dublin 1 web: www.heanet.ie Registered in Ireland, no 275301 tel: +353-1-660 9040 fax: +353-1-660 3666 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFkG9AACgkQNFQvoMdXraksNgCfbSR0V0qe3Aat5v5jpWQ1Nu4V puwAoJNBkGxTr/NbfXDuFwhnLby2LKIV =iDLx -----END PGP SIGNATURE-----