[vpim] RFC 4238 on Voice Message Routing Service

rfc-editor@rfc-editor.org Tue, 01 November 2005 01:00 UTC

Received: from localhost.cnri.reston.va.us ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWkVP-0004Tg-4Z; Mon, 31 Oct 2005 20:00:03 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWkVN-0004TA-H0; Mon, 31 Oct 2005 20:00:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27170; Mon, 31 Oct 2005 19:59:42 -0500 (EST)
Received: from boreas.isi.edu ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EWkjf-000439-6W; Mon, 31 Oct 2005 20:14:47 -0500
Received: from ISI.EDU (adma.isi.edu []) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id jA10uXL18783; Mon, 31 Oct 2005 16:56:33 -0800 (PST)
Message-Id: <200511010056.jA10uXL18783@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 31 Oct 2005 16:56:33 -0800
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: vpim@ietf.org, rfc-editor@rfc-editor.org
Subject: [vpim] RFC 4238 on Voice Message Routing Service
X-BeenThere: vpim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Voice Profile for Internet Mail Discussion Archive <vpim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/vpim>, <mailto:vpim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:vpim@ietf.org>
List-Help: <mailto:vpim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/vpim>, <mailto:vpim-request@ietf.org?subject=subscribe>
Sender: vpim-bounces@ietf.org
Errors-To: vpim-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        RFC 4238

        Title:      Voice Message Routing Service
        Author(s):  G. Vaudreuil
        Status:     Standards Track
        Date:       October 2005
        Mailbox:    GregV@ieee.org
        Pages:      10
        Characters: 18902
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-vpim-routing-10.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4238.txt

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.

This document is a product of the Voice Profile for Internet Mail
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
VPIM mailing list