Conneg & Timely

Folks,

Attached are the two slides from my presentation at today's working
group meeting.

The presentations were for basic concepts, rather than detailed
specification.

1. Timely

My understanding of the existing working group consensus was that the
existing Timely specification has serious technical and operations
problems and that the working group is *not* interested in fixing
them.

However Graham Klyne and I suggest an alternative mechanism that is
similar, but not as stringent.  It involves no change to the email
infrastcture.  It uses existing SMTP DeliverBy to communicate urgency
and then uses an MDN response to signal *receipt* rather than reading
or other disposition.  Hence this is a voluntary mechanism.

I will produce an I-D pursuing this approach.


2. Conneg

The basic problem with the current specification is that it permits
arbitrary change by arbitrary intermediaries.

The proposal is to enable the sender to signal that content changes
are permitted and to specify which changes are allowed.  Having the
sender include a Conneg map of capabilities appears to be the best way
to accomplish this.

We will produce a revised Conneg draft.

d/

d/
-- 
 Dave Crocker  <mailto:[email protected]>
 TribalWise <http://www.tribalwise.com>
 t +1.408.246.8253; f +1.408.850.1850