VPIM v2
Click on the red underlined text to get to the source
... Internet Messaging
(VPIM v2 as defined in RFC 2421(-> 3801draft) [VPIMV2] and revised in RFC 3801draft ...
... VPIMV2R2]) when forwarding messages to remote
voicemail systems. VPIM v2 was designed to allow two voicemail
systems to exchange messages, not to allow a voicemail ...
... desktop e-mail client. It is often not
reasonable to expect a VPIM v2 message to be usable by an e-mail
recipient. The result is messages that cannot be processed by the
recipient (e.g., because of the encoding ...
... client MAY provide a level of
interoperability with VPIM v2 is explained.
It is desirable that unified messaging ...
... voicemail servers. This is possible today,
providing the client implements VPIM v2 [VPIMV2R2], in addition to
this specification, and uses it to construct messages to be sent to a
...
... voice message SHOULD be
multipart/mixed. If the recipient is known to be VPIM v2 compliant,
then multipart/voice-message MAY be used instead (in which case, all
...
... Specifically, Audio/32kadpcm MAY be used when the recipient is known
to support VPIM v2 [VPIMV2R2].
...
... The VOICE parameter on Content-Disposition from VPIM v2 [VPIMV2R2]
SHOULD be used to identify any spoken names or spoken subjects ...
... Content-Disposition VOICE parameter as defined in VPIM v2 [VPIMV2R2].
If there is a single recipient for the message, the spoken name MAY
...
... VPIMV2R2].
If there is a single recipient for the message, the spoken name MAY
also be included (per VPIM v2). A spoken subject MAY also be
provided (per VPIM v2 ...
... VPIM v2). A spoken subject MAY also be
provided (per VPIM v2).
A sending implementation MAY determine the recipient capabilities
...
... MIME2]. A sending
implementation MAY support interoperability with VPIM v2 [VPIMV2R2],
in which case, it MUST be able to record G.726 (indicated as
...
... audio/32kadpcm) to provide
interoperability with VPIM v2. A receiving implementation MAY also
be able to play messages encoded with other codecs ...
... Codec No VPIM v2 Support With VPIM v2 Support
Record Playback Record Playback
------------- ------ -------- ------ --------
...
... Interoperability with VPIM v2 ...
...
Interoperability between VPIM v2 systems and IVM systems can take a
number of different forms. While a thorough investigation of how
...
... full interoperability might be provided between IVM and VPIM v2
systems is beyond the scope of this document; three key alternatives
are discussed below.
...
... Handling VPIM v2 Messages in an IVM Client ...
... content type
of audio/32kadpcm), then a VPIM v2 message that gets routed to that
desktop will be at least usable by the recipient.
...
... interoperability that would ease the
life of end users. However, care should be taken to ensure that any
attempt to reply to such a message does not result in an invalid VPIM
v2 message being sent to a VPIM v2 system. Note that replying to an
e-mail user who has forwarded a VPIM v2 message ...
... life of end users. However, care should be taken to ensure that any
attempt to reply to such a message does not result in an invalid VPIM
v2 message being sent to a VPIM v2 system. Note that replying to an
e-mail user who has forwarded a VPIM v2 message to you is, however,
...
... VPIM
v2 message being sent to a VPIM v2 system. Note that replying to an
e-mail user who has forwarded a VPIM v2 message to you is, however,
acceptable.
...
...
A conformant IVM implementation MUST NOT send a non-VPIM v2 message
to something it knows to be a VPIM v2 system, unless it also knows
...
... IVM implementation MUST NOT send a non-VPIM v2 message
to something it knows to be a VPIM v2 system, unless it also knows
that the destination system can handle such a message (even though
...
... that the destination system can handle such a message (even though
VPIM v2 systems are encouraged to handle non-VPIM v2 messages in a
graceful manner). In general, it must be assumed that if a system
...
... destination system can handle such a message (even though
VPIM v2 systems are encouraged to handle non-VPIM v2 messages in a
graceful manner). In general, it must be assumed that if a system
sends you a conformant VPIM v2 message ...
... VPIM v2 messages in a
graceful manner). In general, it must be assumed that if a system
sends you a conformant VPIM v2 message, then it is a VPIM v2 system,
and so you may only reply with a VPIM v2 ...
... graceful manner). In general, it must be assumed that if a system
sends you a conformant VPIM v2 message, then it is a VPIM v2 system,
and so you may only reply with a VPIM v2 compliant message (unless
...
... VPIM v2 message, then it is a VPIM v2 system,
and so you may only reply with a VPIM v2 compliant message (unless
you know by some other means that the system supports IVM).
...
... In addition, it should be noted that an IVM client may not fully
conform to VPIM v2, even if it supports playing a G.726 message
(e.g., it may not respect the handling of the Sensitivity field
required by VPIM v2 ...
... VPIM v2, even if it supports playing a G.726 message
(e.g., it may not respect the handling of the Sensitivity field
required by VPIM v2). This is one reason why VPIM v2 systems may
choose not to route ...
... (e.g., it may not respect the handling of the Sensitivity field
required by VPIM v2). This is one reason why VPIM v2 systems may
choose not to route messages to any system they do not know to be
...
...
A VPIM v2 system could be extended to also be able to support IVM
compliant messages, and an IVM ...
... IVM conformant client could be extended to
implement VPIM v2 in full when corresponding with a VPIM v2 compliant
...
... client could be extended to
implement VPIM v2 in full when corresponding with a VPIM v2 compliant
system. This is simply a matter of implementing both specifications
...
...
Note that the mechanism for determining if a given recipient is using
a VPIM v2 system or client is outside of the scope of this
specification. Various mechanisms for capabilities discovery exist
...
...
It would be possible to build a gateway linking a set of VPIM v2
users with a set of IVM users. This gateway ...
... defined policies.
For example, VPIM v2 messages with a Sensitivity of Private might be
rejected instead of forwarded to an IVM recipient, because it might
...
... semantics of a Private message, while an IVM
message containing content not supported in VPIM v2 (e.g., a PNG
image ...
...
Such a gateway MUST fully implement this specification and the VPIM
v2 specification [VPIMV2R2], unless it knows somehow that the
specific originators/recipients support capabilities beyond those
...
... gateway issue, it is anticipated that there are no new
additional security issues beyond those identified in VPIM v2
[VPIMV2R2] and in the other RFCs referenced by this document --
...