We need 3DES as a fallback default to smoothly integrate ECC keys
into existing installed base, as I mentioned earlier.
then (reluctantly, but not violently against) how about:
MAY implement ECC
o MUST implement SHA256
o MUST implement ECC256
[ o MUST implement 3DES - directly inherited from 4880, like it or not]
o MUST implement AES128 [or just inherit the SHOULD from 4880??]
o SHOULD implement AES256-SHA512-521ECC
o MAY implement AES256-SHA384-384ECC
o SHOULD try to match cipher strength with ECC strength, where
recipient key preferences allow.
(then need to add wording in about restrictions required for if strict
Suite B compliance is required.)