[Ietf-calsify] Issue 1: new proposed text
lear at cisco.com
Wed Sep 20 08:57:39 PDT 2006
> The issue is that it is not out of the realm of possibility that a
> spam filter or some other 'integrity' checker in email will reject an
> iMIP message because it contains invalid utf-8 (utf-8 multi-octet
> sequence broken across two lines). Another example might be reading
> the utf-8 byte stream into a unicode string object BEFORE doing the
> iCal processing on the unicode string data - that will likely fail if
> there is invalid utf-8. That's been my primary concern rather than
> whether it will be viewable in a text editor.
Sorry- to be clear RFC 2445 already requires that you not split lines in
the middle of characters. This implies valid UTF-8 when used, IMHO.
More information about the Ietf-calsify