Glenn Parsons (gparsons@nortelnetworks.com)
Tue, 23 Oct 2001 03:19:21 -0400
For those of you who have not been around since we started this 5+ years
ago, let me remind you about what VPIM v2 (RFC 2421 & its revision
draft-ietf-vpim-vpimv2r2-04.txt) is. It is a profile of Internet Mail that
was designed for exchange between voice mail servers. The fact that it is a
MIME message means that any desktop client can read it -- but often it
cannot be understood. Further, it is not possible to create a 'VPIM
message' from these clients. This was viewed as not an issue at the outset
as all UM/VM vendors had their own desktop client (or
Outlook/OE/Eudora/Netscape/Notes plug-in).
Anyway, to avoid this issue in general (and deal with what some would call
'broken' clients), we decided the best way forward was to create a different
spec for the desktop UM case. This message type would have to be understood
and creatable by current clients without alteration. This spec is IVM
(draft-ietf-vpim-ivm-02.txt) and uses the new concepts of critical content,
message context, and a new definition of WAV to define generic UM.
Further, we have been in constant consideration that IMAP will be used to
retrieve messages and wanted to ensure that no enhancements would be
required. In some cases though, we have determined that enhanced UM
features are better served by extensions to IMAP (draft-ema-vpim-cb-02.txt).
In any case, my point is that we have considered these issues, have proposed
solutions and are in the midst of last calling the documents. I would
suggest that you take a look at some of the past meeting minutes for some
history, and then review the existing drafts and provide some comments.
Cheers,
Glenn.
This archive was generated by hypermail 2.0b3 on Tue Oct 23 2001 - 09:20:31 IST