[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [lemonade] Open Issues with IMAP CONVERT



Alexei,

>1). Do we want to allow for conversion of non-leaf bodyparts? E.g. 
>multipart/related to application/pdf?
>
> I am slightly in favor of allowing this, even though I don't 
>think that any server should be required to  perform such conversions.
>
>On a related note: should we allow to convert to non-leaf bodyparts?

Support++

>2). draft -05 currently allows for default conversion (i.e. 
>"just convert to any media type, you know best").
>I don't think this should be allowed and I suggest removing 
>this feature from ABNF.

OMA has a requirement for the server making the decision (based on some
capability information about the client) and I think this is our "hook"
to do that. Removing it would complicate our lives in OMA. I would like
to ask You to re-consider this proposal.

>Somewhat related to this: is the server allowed to convert to 
>image/png instead of image/jpeg when .STRICT suffix to CONVERT 
>is not specified? (I don't think this should be allowed)

I don't think it should be allowed.
In fact, I think STRICT should be removed and if the server cannot
fulfill the convert then it should fail the request. I think mosts
client would add it there anyway because they want exactly what they
asked for - and nothing else. If clients don't want to convert to some
specific type, they will let the server decide the best conversion.

>3). There is one big issue surrounding INFORMATIONLOSS. I will 
>publish an updated draft shortly, but it will not tackle this 
>issue. I will try to address the issue in the subsequent revision.

Could You elaborate this, please?
Thank You.

_______________________________________________
lemonade mailing list
lemonade at ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade