ietf-openpgp
[Top] [All Lists]

Procedures for updating RFC

1998-05-21 13:36:34
-----BEGIN PGP SIGNED MESSAGE-----

Hi,

As it seems that we are comming close to finishing the openPGP spec. I
think now is a good time to establish a mechanism for updating openPGP.

As time goes on there will be users who will wish to add support for other
algorithms. We should have a mechanism in place where ID's and reference
information on these new algorithms can be added in a painless manner.

Hopefully we can come up with a way to add new algorithms quickly without
having to go through the long process of issuing a new RFC and yet have
some type of review process to keep out the snake-oil.

A formalized paper on how a new algorithm can be added to the RFC, what
information is required, and who has the authority on approving/rejecting
application for a new algorithm.

Timelyness seems important in this matter. IMHO the adding of new
functionality should not take 6mo - 1yr to process. :)

Also has anyone though of creating a test suite that potential openPGP
integrators could use to insure that they meet the minimum requirements of
the openPGP RFC?

Such a suite should be two part:

1st part would be a collection of openPGP messages that a compliant
program would need to process.

2nd part would be a binary that would process a collection of openPGP
messages generated by the application and would pass/fail the message
generation.

- -- 
- ---------------------------------------------------------------
William H. Geiger III  http://users.invweb.net/~whgiii
Geiger Consulting    Cooking With Warp 4.0

Author of E-Secure - PGP Front End for MR/2 Ice
PGP & MR/2 the only way for secure e-mail.
OS/2 PGP 5.0 at: http://users.invweb.net/~whgiii/pgp.html
- ---------------------------------------------------------------
 
Tag-O-Matic: OS/2: Your brain.  Windows: Your brain on drugs.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a-sha1
Charset: cp850
Comment: Registered_User_E-Secure_v1.1b1_ES000000

iQCVAwUBNWSSN49Co1n+aLhhAQG0igP9Gsd8k0QGIDsz8zcpsLJXHVNxSDseQUnH
TP9eiEr2FKWB+Aif+9+sa6vuBcXaEfjSArZY9DieGUSR4bqlfhmFpIQSpJtysY0t
fVlez7u6htimO2fPwA9L7JG7LOOmL62nSaxUAY6V+xnnIyWSGpl4QkITYDHrhSNV
NW3puihobcg=
=pNoZ
-----END PGP SIGNATURE-----



<Prev in Thread] Current Thread [Next in Thread>
  • Procedures for updating RFC, William H. Geiger III <=