Re: [EAI] Body parts

[Shawn Steele <Shawn.Steele at microsoft.com>]

Frank said:
> Adding a "you SHOULD do the obvious" norm does not really help, or does it ?

I think it does.  EAI requires that the client software understand UTF-8 (otherwise From: and To: look stupid), so any application must therefore be able to handle UTF-8 in the body as well.  This would help ensure that new implementations support UTF-8.  (Many modern devices, particularly phones, don't bother leading to the aforementioned compatibility issues).

I wouldn't mind language that said.  "Conforming applications MUST support UTF-8 in the body part and SHOULD use UTF-8 unless they have a really really good reason".

MUST support it so that everyone can expect that recipients will understand the code page (right now there's no *guaranteed* code page that'll work across all environments)

SHOULD use it since it's the most consistent of the encodings and if it MUST be supported, then compatibility is ensured.  I didn't suggest "MUST" because I realize that some devices may have a more difficult time with the transition, although gateways could help.

- Shawn

_______________________________________________
IMA mailing list
IMA at ietf.org
https://www.ietf.org/mailman/listinfo/ima