Making AES a SHOULD in draft-ietf-smime-rfc2633bis?

Greetings again. draft-ietf-smime-rfc2633bis is in WG last call, and 
I should have probably brought this up before, but...
Do we want to add AES as a SHOULD in section 2.7? We have the 
traditional TripleDES MUST and RC2-40 as SHOULD. That's looking 
backwards (some might say "very backwards" for RC2-40). It might be 
good to add a forwards-looking SHOULD, namely AES.
How do others feel about this?

--Paul Hoffman, Director
--Internet Mail Consortium