It delays progress because the implementation of the RFC 1422 PEM,
i.e. the TIS/PEM Version 6.1 has been removed from the ftp site at
TIS. Even if the new MIME-friendly implementation support the RFC
1422 PEM, anyone with existing PEM user base has to convert to using
MIME to be unable to use or expand their use of RFC 1422 PEM.
_______________________________________________________________________
Alireza Bahreman E-Mail:
bahreman(_at_)bellcore(_dot_)com
Bellcore, Room RRC-1K221 Phone : +1 908 699 7398
444 Hoes Lane, Piscataway, NJ 08854 Fax : +1 908 336 2943
You write:
Date: Tue, 13 Dec 94 20:00:50 EST
From: Ali Bahreman <ali(_at_)ctt(_dot_)bellcore(_dot_)com>
I strongly believe PEM RFC 1422 is the nearest to our solution
(especially for e-commerce) than anything else. (Well, I have not
considered PKCS.) I think MIME-PEM (while a good idea to have MIME)
sets us back some and delays progress forward with PEM.
... but the MIME-PEM document goes to great lengths to assert that it is
*not* a replacement for RFC 1422. It is merely another way of doing so,
that happens to be more MIME-friendly. People are still free to use
1422, if they wish. Given this, do you still believe that it delays
forward progress of PEM?
- Ted