RE: [VPIM] VPIM in the real world


Eric Burger (eburger@snowshore.com)
Tue, 23 Oct 2001 20:48:51 -0400


Note that while the minutes suggested that an Internet Voice Mail should
have at least one audio part, the drafts explicitly, and on purpose, do not
have that requirement.

-----Original Message-----
[snip]

Overall, I think we are probably on the same page. I see the
following in the VPIM meeting minutes from the 10 August meeting:

    * If a Message-context of voice-message is not required, what
      makes a message an Internet Voice Message? Does it have to
      contains an approved voice content type (or rather any voice
      content type, as this is permitted)? Can a message with no voice
      content be an IVM? This is permitted for a Message-context of
      voice-message, but does it make sense for an Internet Voice
      Message? This could be addressed by rewording the requirement on
      content type as follows: "An Internet Voice Message MUST contain
      at least one audio part, which may be at any location within a
      message and SHOULD be contained in either an audio/wav or
      audio/basic content-type - the only exception being when the
      originator is aware that the recipient can handle other
      content."

I'm trying to answer the first question: what makes a message an IVM?

I don't believe that the presense of audio/wav is sufficient to be
considered an IVM because an email message sent with a wav attachment
would be considered a voice message. That kind of false positive is
not acceptable, IMHO.

A more fundamental problem exists because wav attachments are not
guaranteed to show up as audio/wav. I'm going to use Outlook Express
as an example, since it is the MUA that most of our customers use.
I'm looking for a solution that will interoperate with its current
behavior.

When Outlook Express forwards an email with an attachment, as far as I
can tell it regenerates the content-type for each attachment based on
the file extension. If the user does not have a handler configured
for the wav extension, then the attachment will be of type
"application/octet-stream". Granted, most email users will probably
have a wav handler installed, but I would prefer not to depend on it.
[snip]



This archive was generated by hypermail 2.0b3 on Wed Oct 24 2001 - 02:47:09 IST ubscribed to
vpim@lists.neystadt.org. You can manage your subscription at
http://www.neystadt.org/cgi-bin/majordomo



This archive was generated by hypermail 2.0b3 on Wed Oct 24 2001 - 02:47:09 IST