This is a very "interesting" question. I've pondered things in this
area myself. I believe the over-riding question, however, is: Does
the IETF have change control here? Anyone know one way or the other?
Bill
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
William F. Flanigan, Jr., Ph.D. Voice: (703) 735-3305
Defense Information Systems Agency DSN: 653
Strategic Planning Office (JEBA) Fax: (703)735-3255
10701 Parkridge Boulevard Voice Mail: (703)735-3305
Reston, VA 20191-4357 Internet:
<flanigab(_at_)ncr(_dot_)disa(_dot_)mil>
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-----Original Message-----
From: Chris Bartram [SMTP:RCB(_at_)NOSPAM(_dot_)3K(_dot_)COM]
Sent: Thursday, April 30, 1998 9:06 PM
To: ietf-open-pgp(_at_)imc(_dot_)org
Subject: Legal issues in implementing OpenPGP?
Forgive the rather basic questions, but;
If one wants to implement a *commercial* implementation that supports the
OpenPGP standard, are there *ANY* patent/licensing issues we have to deal
with:
1) Assuming we implement just the "MUST" algorithms?
(Isn't generic "public key encryption" technology still patented? If so,
what steps does one have to take to use it? Who must be contacted?)
2) For the other "SHOULD" algorithms? An appendix listing some info/
contact details on who one should contact would certainly make
implementing the spec much easier.
We're a U.S. based company (if that matters), but I suspect contact info
would
also be useful to organizations in many other countries as well.
Thanks!
-Chris Bartram
3k Associates, Inc.
(remove "nospam" from return address for direct replies)