Hi Paul,
Regarding Content-Disposition in multiparts:
While it seems "wrong" to me, I can live with using "render" as the
normal disposition for multipart, *if* we can do a careful job of
defining what "render" actually means for SIP. Used this way it clearly
doesn't always mean to display the content to a user.
An entity receiving a 'multipart/mixed' body will process its body parts
based on their disposition types.If the disposition type of a particular
body part is not understood, it will be displayed to the user because
the default disposition type is 'render'.
Therefore, the 'multipart/mixed' body will never be processed based on
its disposition type. This means that it does not make much sense to
talk about its disposition type as a whole. However, we need to have one
in order to be able to set its handling parameter. That's why we can
either keep 'render' explaining that it is actually never used or define
a new disposition type.
Since existing implementations will not understand our newly defined
disposition type, they will treat it as 'render' anyway... but the
resulting behavior would be the same. That's why it may make sense to
keep using 'render'.
On the other hand, semantically, it would make more sense to define a
new disposition type.
Also, if we decide to define the 'by-reference' disposition type (per a
different email thread), it could be used here as well.
Cheers,
Gonzalo
Gonzalo Camarillo wrote:
Folks,
here you have the slides I have put together for the body (MIME)
handling presentation on Monday:
http://users.piuha.net/gonzalo/temp/ietf69-sip-camarillo-body-handling.ppt
These slides relate to this draft:
http://www.ietf.org/internet-drafts/draft-camarillo-sip-body-handling-01.txt
The slides discuss all the open issues that have been brought up in
the list in the last months.
Comments are welcome.
Thanks,
Gonzalo
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
