Here's the announcement. The work is based on Vixie's draft but he got tired of waiting for the standards process. The thing was held in a queue for about 8 months... The RFC version has changes to document organization and some deletions of addresses which aren't known to be heavily supported already. d/
To: IETF-Announce: ; Subject: RFC 2142 on Mailbox Names Cc: rfc-ed@isi.edu Date: Tue, 06 May 97 10:52:26 PDT Sender: ietf-announce-request@ietf.org From: RFC Editor <rfc-ed@isi.edu>
A new Request for Comments is now available in online RFC libraries.
RFC 2142:
Title: Mailbox Names for Common Services, Roles and Functions Author: D. Crocker Date: May 1997 Mailbox: dcrocker@imc.org Pages: 6 Characters: 12195 Updates/Obsoletes: None
URL: ftp://ds.internic.net/rfc/rfc2142.txt
This specification enumerates and describes Internet mail addresses (mailbox name @ host reference) to be used when contacting personnel at an organization.
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@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@ISI.EDU with the message body help: ways_to_get_rfcs. For example:
To: rfc-info@ISI.EDU 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 admin@DS.INTERNIC.NET. 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@ISI.EDU. Please consult RFC 1543, Instructions to RFC Authors, for further information.
Joyce K. Reynolds and Mary Kennedy 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.
Content-Type: text/plain Content-ID: <970506104804.RFC@ISI.EDU>
[This attachment must be fetched by mail. Open the stationery below and send the resulting message to get the attachment.] Attachment converted: dcrocker 5300ce:Get RFC 2142 on Mailbox Names (EuSn/CSOm) (0001F509) Content-Type: Message/External-body; name="rfc2142.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="rfc"
[This attachment must be fetched by ftp. Open the document below to ask your ftp client to fetch it.] Attachment converted: dcrocker 5300ce:Get rfc2142.txt (AURL/Arch) (0001F50A) Content-Type: text/plain Content-ID: <970506104804.RFC@ISI.EDU>
-------------------- Dave Crocker +1 408 246 8253 Brandenburg Consulting fax: +1 408 249 6205 675 Spruce Dr. dcrocker@brandenburg.com Sunnyvale CA 94086 USA http://www.brandenburg.com Internet Mail Consortium http://www.imc.org, info@imc.org