From: Charles Breed <cbreed(_at_)pgp(_dot_)com>
The OPEN-PGP Specification will have provisions for;
1. interoperability using cryptographic algorithms
(asymmetric/symmetric including key lengths) that are consider
strong, open and unencumbered, and other algorithms MAY be used
This should be more than one sentence. How about:
1. mandatory support for strong, open and unencumbered cryptographic
algorithms. Other algorithms may be optionally specified, but will
not be required for conformance.
2. limited backwards compatibility with the existing pgp message
I am concerned. How about:
2. strong backwards compatibility with the pgp 5.0, with limited
support for earlier pgp version installed base.
3. Government and legislative policies from any country SHOULD not
impact the specification
Better:
3. Government and legislative policies MUST NOT impact the
specification.
4. certificate structure and underlying trust models, as used in a
public key infrastructure
Which public key infrastructure?
I am planning on writing up SPKI-like message formats that use the PGP
CTB space -- this weekend.
5. certificate and message format
6. basic time stamping service
7. MIME content types will reference RFC 2015
Goals and Milestones:
A rather aggressive schedule. Probably will slip.
Chairpersons:
John W. Noerenberg, II <jwn2(_at_)eudora(_dot_)com>
Charles J. Breed <cbreed(_at_)pgp(_dot_)com> co-chair
Good luck, and thanks!
WSimpson(_at_)UMich(_dot_)edu
Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32
BSimpson(_at_)MorningStar(_dot_)com
Key fingerprint = 2E 07 23 03 C5 62 70 D3 59 B1 4F 5E 1D C2 C1 A2