On Wed, May 4, 2011 at 4:36 PM, John C Klensin <[email protected]> wrote: <snip> > - a few (stupid but inconsequential) changes needed to > make the revision go through the current version of > XML2RFC.
yes, that is annoying. :) <snip> > The key text is below. I'd appreciate if it the WG would > comment on it (and suggest improvements if needed) before we > post the actual draft (which I hope is otherwise routine). > >> 6.5. Adjust Character Encodings > >> Subject to limits imposed by other protocols and >> specifications, the MSA MAY convert among character sets or >> string encodings to improve message usefulness, likelihood >> of delivery, or conformance with other specifications or >> recommendations. Such conversions MAY include, when >> necessary, replacement of addresses whose encoding does not >> conform to RFC 5321 with ones that do, using information >> available out to band. Should there be advice mentioning that such changes should be done before (or after?) such things as digital signing? I'm thinking PGP and SMIME. -- Jeff Macdonald Ayer, MA _______________________________________________ yam mailing list [email protected] https://www.ietf.org/mailman/listinfo/yam
