VPIM Voice Message MIME Sub-type Registration
RFC 2423

Document Type RFC - Proposed Standard (September 1998; No errata)
Obsoleted by RFC 3801
Obsoletes RFC 1911
Was draft-ema-vpim-vmsg (individual)
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 2423 (Proposed Standard)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         G. Vaudreuil
Request for Comments: 2423                             Lucent Technologies
Obsoletes: 1911                                                 G. Parsons
Category: Standards Track                                 Northern Telecom
                                                            September 1998

                           VPIM Voice Message
                       MIME Sub-type Registration

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

Overview

   This document describes the registration of the MIME sub-type
   multipart/voice-message for use with the Voice Profile for Internet
   Mail (VPIM).  A full description of usage can be found in the VPIM v2
   specification.

1.  Abstract

   This document describes the registration of the MIME sub-type
   multipart/voice-message for use with the Voice Profile for Internet
   Mail (VPIM).  A full description of usage can be found in the VPIM v2
   specification [VPIM2].  This document revises an earlier sub-type
   registration in RFC 1911 [VPIM1].

2. VPIM Scope

   The VPIM specification defines a restricted profile of the Internet
   multimedia messaging protocols for use between voice processing
   platforms.  These platforms have historically been special-purpose
   computers and often do not have the same facilities normally
   associated with a traditional Internet Email-capable computer.  As a
   result, VPIM also specifies additional functionality as it is needed.
   The profile is intended to specify the minimum common set of features
   to allow interworking between compliant systems.

Vaudreuil & Parsons         Standards Track                     [Page 1]
RFC 2423                multipart/voice-message           September 1998

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [REQ].

3. Voice Message Interchange

3.1 multipart/voice-message

   The MIME sub-type multipart/voice-message is defined to hold specific
   media contents that are interchanged in messages between voice
   messaging systems described in [VPIM2].  Essentially, the sub-type
   provides a simple wrapper that easily identifies the entire content
   as being the components of a single voice message.  The sub-type is
   identical in semantics and syntax to multipart/mixed, as defined in
   [MIME2].  As such, it may be safely interpreted as a multipart/mixed
   by systems that do not understand the sub-type (only the
   identification as a voice message would be lost).

   This mechanism allows the insertion of an explanatory preamble (e.g.
   VPIM voice message attached) for recipients who read the message with
   pre-MIME software, since the preamble will be ignored by MIME-
   compliant software.

   In addition to the MIME required boundary parameter, a version
   parameter is also required for this sub-type.  This is to
   distinguish, this refinement of the sub-type from the previous
   definition in [VPIM1].  The value of the version parameter is "2.0"
   if the content conforms to the requirements of [VPIM2].  Should there
   be further revisions of this content type, there MUST be backwards
   compatibility (i.e. systems implementing version n can read version
   2, and systems implementing version 2 can read version 2 contents
   within a version n).  The default version value (when the parameter
   is missing) is 1, indicating the content conforms to the requirements
   of [VPIM1].

   [VPIM2] describes the restriction that only specific media types,
   applicable to voice messaging, are valid `next-level' contents of
   this sub-type (when version=2.0).  They are: audio/*, image/*,
   message/rfc822 and application/directory.  The multipart provides for
   the packaging of as many of these contents as is necessary.

3.2 VPIM v2 Usage

   The multipart/voice-message sub-type is a primary component of the
   VPIM specification [VPIM2].  All VPIM Messages MUST contain this
   sub-type to identify the wrapping of a voice message.  The contents
   of this wrapper can vary from only one audio/32KADPCM content to a
   complex set of related and nested contents.

Vaudreuil & Parsons         Standards Track                     [Page 2]
RFC 2423                multipart/voice-message           September 1998

   Typically, if more than one audio segment is present, the first is
   the spoken name of the originator, the second is the spoken subject,
Show full document text