Re: [dispatch] Improve UX in Encrypted Email (distinguish between forwarded and otherwise wrapped messages)

[[e-mail]]

Bernie Hoeneisen <[e-mail]> writes:
> This I-D suggests a new Content-Type Header Field Parameter "forwarded": 
> If set to "yes", the contained message was forwarded; if set to "no", the 
> message was "wrapped" for signature/encryption with Header Protection.

There's a category problem:  What you're trying to capture is "What is
the significance of this body part within the whole structure?"  It does
not describe the *type* of the contents of the body part.

I've noticed this before in SIP, the idea that if you know the *type* of
a body part, then you know its *significance*.  That works in the
simplest cases, but it's like saying that you can always tell which
parameter in a function call means what if you know their types.

What we need is a new "Content-Semantics" header for parts of multipart
bodies which describes the semantics of this part within the whole.
E.g., "contained encrypted content" or "forwarded message".

Dale