Subject: [lemonade] Content conversion upon submission

From: "Vaudreuil, Greg M (Greg)" <[email-masked]>
Date: Thu, 19 Jun 2003 22:24:23 -0500

Let me throw one more use-case into this submission gunk.   

Say a client wishes to send a message with content generated on the end of a skinny, latent path, say a recorded audio clip.  Say that message is intended to be delivered via VPIM's 32kADPCM or some more common audio/basic construct.

The client here has the obvious choice to send the data in the bulky form over this link, or it could send it using a more compressed, maybe native format such as GSM, AMR, or EVRC.  What would be desireable is to send the audio data upstream via an external content-conversion device, with an indication that the data should be converted prior to submission into a more accessable form say mu-law (audio/basic). 

This is leading me to believe that the "template" as Randy is describing needs to be able to include references to external stuff, and deal with the security issues that are also present in the channel extension.... the alternative of requesting conversion as part of the submission process itself seems to be messy

Thoughts?

Greg V.

_______________________________________________
lemonade mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/lemonade