RFC 3804 on Voice Profile for Internet Mail (VPIM) Addressing
rfc-editor@rfc-editor.org Fri, 25 June 2004 16:46 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21396 for <ietf-announce-archive@ietf.org>; Fri, 25 Jun 2004 12:46:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bdtq0-0000R7-He for ietf-announce-archive@ietf.org; Fri, 25 Jun 2004 12:46:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bdtnq-0007TL-00 for ietf-announce-archive@ietf.org; Fri, 25 Jun 2004 12:43:51 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1Bdtls-0006hf-00; Fri, 25 Jun 2004 12:41:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdtFy-000612-08; Fri, 25 Jun 2004 12:08:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdd9Q-0007AM-Fa for ietf-announce@megatron.ietf.org; Thu, 24 Jun 2004 18:57:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25202 for <ietf-announce@ietf.org>; Thu, 24 Jun 2004 18:56:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bdd9N-0005wj-EC for ietf-announce@ietf.org; Thu, 24 Jun 2004 18:56:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BdcWa-0004lu-00 for ietf-announce@ietf.org; Thu, 24 Jun 2004 18:16:53 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1Bdbmj-0003aQ-00 for ietf-announce@ietf.org; Thu, 24 Jun 2004 17:29:29 -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 i5OLRfJ16232; Thu, 24 Jun 2004 14:27:41 -0700 (PDT)
Message-Id: <200406242127.i5OLRfJ16232@boreas.isi.edu>
To: IETF-Announce:;
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 24 Jun 2004 14:27:41 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Mailman-Approved-At: Fri, 25 Jun 2004 12:08:45 -0400
Cc: vpim@lists.neystadt.org, rfc-editor@rfc-editor.org
Subject: RFC 3804 on Voice Profile for Internet Mail (VPIM) Addressing
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60
A new Request for Comments is now available in online RFC libraries.
RFC 3804
Title: Voice Profile for Internet Mail (VPIM) Addressing
Author(s): G. Parsons
Status: Standards Track
Date: June 2004
Mailbox: gparsons@nortelnetworks.com
Pages: 15
Characters: 26122
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-vpim-address-03.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3804.txt
This document lists the various Voice Profile for Internet Mail (VPIM)
email address formats that are currently in common use and defines
several new address formats for special case usage. Requirements are
imposed on the formats of addresses used in VPIM submission mode.
This documenet 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.echo
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.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce