RFC 4237: Voice Messaging Directory Service
In plain English — editorial summary, not part of the RFC
This document provides details of the Voice Profile for Internet Mail (VPIM) directory service. The service provides the email address of the recipient that is given a telephone number. It optionally provides the spoken name of the recipient and the media capabilities of the recipient. The VPIM directory Schema provides essential additional attributes to recreate the voice mail user experience using standardized directories. This user experience provides, at the time of addressing, basic assurances that the message will be delivered as intended. This document combines two earlier documents, one from Anne Brown and one from Greg Vaudreuil, that define a voice messaging schema into a single working group submission. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4237
- Published
- October 2005
- Authors
- G. Vaudreuil
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4239Internet Voice Messaging (IVM)Current
November 2005
- RFC 3804Voice Profile for Internet Mail (VPIM) AddressingCurrent
June 2004
- RFC 3801Voice Profile for Internet Mail - version 2 (VPIMv2)Current
June 2004
- RFC 3773High-Level Requirements for Internet Voice MailCurrent
June 2004
- RFC 4024Voice Messaging Client BehaviourCurrent
July 2005
- RFC 4238Voice Message Routing ServiceUpdated
October 2005
- RFC 4236HTTP Adaptation with Open Pluggable Edge Services (OPES)Current
November 2005
- RFC 4259A Framework for Transmission of IP Datagrams over MPEG-2 NetworksCurrent
December 2005
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?