-----BEGIN PGP SIGNED MESSAGE-----
Hmmm... you raise an interesting point. I had thought that this was
going to be a new document, and as it is not referred to in the
existing core RFC, then ECC/Suite B was going to be a MAY by
Within that new (MAY) document, there would be several choices for
MUST, SHOULD, MAY, etc.
Or so I thought ... but I'm not fully aware of how these things
At least in theory, we could make ECC be the MUST. But as I said
before, there really isn't a good process to change those things in
OK, if you are happy to carry on this discussion ... what are the
reasons for including the 128-bit profile?
There's nothing wrong 128-bit security. It's also faster. It competes
against 3Kbit integer keys.
If you're doing smart cards, HSMs, mobile phones, etc. they will
likely need 128-bit security for speed reasons.
-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 2.6.3
-----END PGP SIGNATURE-----