-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm replying to this now with my implementer's hat on, rather than
spec-writer's hat.
I expect that after 2440bis is done, we'll see requests for various
national ciphers. I'm okay with it. My customers in Japan would like
to see Camillia used. I'm happy to do that for them, especially if I
don't have to pay for it. Even if I do have to pay for it, I'm happy
to do it for them -- I'll just charge them money for it. Ditto for
SEED, GOST, and any other cipher that is secure.
I see it as a good thing because the people who don't care about them
don't have to implement or use them, and those who do can do as they
want. The only potential problem is if you had private keys encrypted
with one of these ciphers and you imported those keys into an
implementation that didn't have them.
I see it as a good thing because S/MIME can use them. I don't want to
be so rigid in what goes into OpenPGP that people who want to use
OpenPGP but have a desire or need to use one of these other ciphers
have to use a different protocol.
My products (the PGP family) implement both the OpenPGP and S/MIME
standards. It would be a real pity if my Japanese product did
Camillia for S/MIME but not for OpenPGP.
Jon
-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 2.6.1
Charset: US-ASCII
wj8DBQFGLRx3sTedWZOD3gYRArpnAJ9l2achZPCtAs1zGs2lAj/LDuZyZQCg7XrA
PVOOUofZ5gM33hn4RkWkAvo=
=OYyf
-----END PGP SIGNATURE-----