To run a keyserver or not?

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

I will soon be suggesting that my company begin using GPG/PGP to
transfer files securely with a client.  I'm trying to prepare a
scheme that will work for this situation (~6 employees, 1
client) and scale to the whole company (~200 emp, X clients).

One of the major issues I can see with so many keys is
distribution.  A keyserver is the obvious answer, but most of
our employees only have proxy access to the Net.  They, and the
managers, would be displeased with errors, long delays, or
manual reconfiguration should an address change.

Should we just run an in-house keyserver?  I've gotten SKS
running, and can arrange for the extra drive space.  I can
arrange DNS records that make it seamlessly available for users
in the office and on the road (and for clients).

Is there a "community policy" about the availability of the
server?  For instance, would other operators sync with us if we
did not actively encourage public use?

What kind of syncing traffic can we expect on an average day?

If we were a totally public keyserver, how much user traffic
might we see?  I know that will vary, but what's a good value to
tell the boss?

Any generic suggestions?  Words of wisdom?  Random quotes?

- -- 
Through the modem, off the server, over the T1, past the
frame-relay,
< < NOTHIN' BUT NET > >
 
Daniel Johnson
[email protected]
http://dannyj.come.to/
Public PGP Keys & other info: http://dannyj.come.to/pgp/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32) - GPGshell v2.95

iD8DBQE/pYEc6vGcUBY+ge8RAvfkAKD6y/jBaKDL0SeZNt3mScj+xOtysgCZAfsB
E3geMzgq2YwD/kaeraZt/9s=
=oS8d
-----END PGP SIGNATURE-----