metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 4238: Voice Message Routing Service

Still current, but amended. Parts of this document are changed or extended by RFC 6118. Read both.

In plain English — editorial summary, not part of the RFC

Voice messaging is traditionally addressed using telephone number addressing. This document describes two techniques for routing voice messages based on a telephone number. The complete service uses the Voice Profile for Internet Mail (VPIM) Directory service to lookup a VPIM email address with a telephone number and confirm that the address is both valid and associated with the intended recipient. However, this service will take time to become widely deployed in the near term. This document also describes a basic send-and-pray service that routes and delivers messages using only the ENUM telephone number resolution service and the existing DNS mail routing facilities. [STANDARDS-TRACK]

Document record

Document ID
RFC4238
Published
October 2005
Authors
G. Vaudreuil
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
10
Also known as
—
Updated by:
RFC 6118

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4238-voice-message-routing-service