Re: [apps-discuss] I-D Action: draft-ietf-appsawg-rfc3462bis-00.txt

["John Levine" <[e-mail]>]

>> section 3.  This could also go to a new "i18n considerations"
>> with a pointer to the EAI work:  The assumption that at least
>> the header is 7-bit clean is not more strictly true.  EAI is
>> out of scope, but nevertheless the 7-bit header assumption is
>> now far less clear than in 2003.
>
>I'm not really sure we need to say more than what's already there.
>This text looks fine with or without EAI being applied.  Does anyone
>else with good EAI fu have a comment here?

The EAI group has this reasonably well under control.  There's a draft
that updates the DSN spec, and adds new EAI mime types message/global,
message/global-headers, message/global-delivery-status, and
message/global-disposition-notification.

See draft-ietf-eai-rfc5337bis-dsn-03.txt 

Note that EAI no longer is making any attempt to be backward
compatible to systems that can't handle 8BITMIME, so you don't have to
worry about it.

Dunno what the schedule is for the DSN draft, since it hasn't gotten
much attention lately.  Tony Hansen is the primary author so you can
ask him if you're wondering.

R's,
John