RFC 3801: Voice Profile for Internet Mail - version 2 (VPIMv2)
In plain English — editorial summary, not part of the RFC
This document specifies a restricted profile of the Internet multimedia messaging protocols for use between voice processing server platforms. The profile is referred to as the Voice Profile for Internet Mail (VPIM) in this document. 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. This profile is intended to specify the minimum common set of features to allow interworking between conforming systems. This document obsoletes RFC 2421 and describes version 2 of the profile with greater precision. No protocol changes were made in this revision. A list of changes from RFC 2421 are noted in Appendix F. Appendix A summarizes the protocol profiles of this version of VPIM. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3801
- Published
- June 2004
- Authors
- G. Vaudreuil; G. Parsons
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 55
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3804Voice Profile for Internet Mail (VPIM) AddressingCurrent
June 2004
- RFC 3773High-Level Requirements for Internet Voice MailCurrent
June 2004
- RFC 4237Voice Messaging Directory ServiceCurrent
October 2005
- RFC 4239Internet Voice Messaging (IVM)Current
November 2005
- RFC 4024Voice Messaging Client BehaviourCurrent
July 2005
- RFC 4238Voice Message Routing ServiceUpdated
October 2005
- RFC 3354Internet Open Trading Protocol Version 2 RequirementsCurrent
August 2002
- RFC 4416Goals for Internet Messaging to Support Diverse Service EnvironmentsCurrent
February 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?