[vpim] RFC 4237 on Voice Messaging Directory Service
rfc-editor@rfc-editor.org Tue, 25 October 2005 23:46 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUYVE-0006JH-DZ; Tue, 25 Oct 2005 19:46:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUYVC-0006Ih-Av; Tue, 25 Oct 2005 19:46:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06219; Tue, 25 Oct 2005 19:46:31 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUYiE-0002ln-T0; Tue, 25 Oct 2005 20:00:15 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j9PNjSL29280; Tue, 25 Oct 2005 16:45:28 -0700 (PDT)
Message-Id: <200510252345.j9PNjSL29280@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: Tue, 25 Oct 2005 16:45:28 -0700
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: 6d95a152022472c7d6cdf886a0424dc6
Cc: vpim@ietf.org, rfc-editor@rfc-editor.org
Subject: [vpim] RFC 4237 on Voice Messaging Directory 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 4237 Title: Voice Messaging Directory Service Author(s): G. Vaudreuil Status: Standards Track Date: October 2005 Mailbox: GregV@ieee.org Pages: 13 Characters: 26093 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-vpim-vpimdir-11.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4237.txt 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. 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 VPIM@ietf.org https://www1.ietf.org/mailman/listinfo/vpim