This appendix lists national, international, and industry standards related to electronic messaging and for which support is claimed by Sun Internet Mail Server (SIMS) 4.0. Most of these are Internet standards, published by the Internet Engineering Task Force (IETF) and approved by the Internet Activities Board (IAB). Standards for documents from other sources are noted.

Several of the documents are listed with an obsolete status. These are included because they describe protocol features that were obsolete or replaced by later documents, but are still in widespread use.

Messaging

The following documents are relevant to national and international standards for messaging, specifically messaging structure.

Basic Message Structure

The structure of basic messages is explained in the documents listed in TABLE A-1.

TABLE  A-1   Basic Message Structure 

Standard	Status	Description
RFC 822 STD 11	Standard	David H. Crocker, University of Delaware, Standard for the Format of ARPA Internet Text Messages, August 1982.
RFC 1123	Standard	Robert Braden (Editor), Requirements for Internet Hosts - Application and Support, Internet Engineering Task Force, October 1989.

Access Protocols and Message Store

The documents listed in TABLE A-2 contain information about access protocols and message stores.

TABLE  A-2   Access Protocols and Message Store

Standard	Status	Description
RFC 1731	Proposed Standard	John G. Myers, (Carnegie-Mellon University), IMAP4 Authentication Mechanisms, December 1994.
RFC 1733	Information	Mark R. Crispin, (University of Washington), Distributed Electronic Mail Models in IMAP4, December 1994.
RFC 1939	STD 53	John G. Myers (Carnegie-Mellon University) and Marshall T. Rose (Dover Beach Consulting), Standard Post Office Protocol - Version 3, May 1996.
RFC 2060	Proposed Standard	Mark Crispin (University of Washington), Internet Message Access Protocol - Version 4rev1, December 1996.
RFC 2061	Information	Mark R. Crispin (University of Washington), IMAP4 Compatibility With IMAP2bis, December 1996.
RFC 2177	Proposed Standard	Barry Leiba (IBM T.J. Watson Research Center), IMAP4 IDLE Command, June 1997.

SMTP and Extended SMTP

The documents listed in TABLE A-3 contain information about Simple Mail Transfer Protocol (SMTP) and Extended SMTP.

TABLE  A-3   SMTP and Extended SMTP  

Standard	Status	Description
RFC 821 STD 10	Standard	Jonathan B. Postel, USC/Information Sciences Institute, Simple Mail Transfer Protocol, August 1982.
RFC 1047	Information	Craig Partridge, CIC BBN Laboratories Inc., Duplicate Messages and SMTP, February 1988.
RFC 1428	Information	Greg Vaudreuil, Corporation for National Research Initiatives, Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME, February 1993.
RFC 1652	Draft Standard	John Klensin (United Nations University), Einar Stefferud (Network Management Associates, Inc.), Ned Freed (Innosoft), Marshall Rose (Dover Beach Consulting), David Crocker (Brandenburg Consulting), SMTP Service Extension for 8bit-MIME transport, July 1994.
RFC 1869 STD 10	Standard	John Klensin (United Nations University), Ned Freed (Innosoft), Marshall Rose (Dover Beach Consulting), Einar Stefferud (Network Management Associates, Inc.), David Crocker (The Branch Office), SMTP Service Extensions, November 1995.
RFC 1870 STD 10	Standard	John Klensin (United Nations University), Ned Freed (Innosoft), Keith Moore (University of Tennessee), SMTP Service Extension for Message Size Declaration, November 1995.
RFC 1893	Proposed Standard	Greg Vaudreuil (Corporation for National Research Initiatives), Enhanced Mail System Status Codes, January 15, 1996.
RFC 1985	Proposed Standard	J. De Winter, SMTP Service Extension for Remote Message Queue Starting, August 1996.
RFC 2442	Information	J. Belissent, The Batch SMTP Media Type, November 1998.

Message Content and Structure

The following documents specify message contents handling, most of which is covered by the Multipurpose Internet Mail Extensions (MIME). There are also several non-standard message content RFCs that are supported by the SIMS product, which are listed separately in TABLE A-4.

TABLE  A-4   Message Content and Structure  

Standard	Status	Description
RFC 1341	Obsolete	Nathaniel Borenstein (Bellcore) and Ned Freed (Innosoft), MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies, June 1992.
RFC 1524	Information	Nathaniel Borenstein (Bellcore), A User Agent Configuration Mechanism For Multimedia Mail Format Information, September 1993.
RFC 1806	Experimental	Rens Troost (New Century Systems), Steve Dorner (Qualcomm), Communicating Presentation Information in Internet Messages: The Content-Disposition Header, June 1995.
RFC 2017	Proposed Standard	Ned Freed (Innosoft), Keith Moore (University of Tennessee), Definition of the URL MIME External-Body Access-Type, October 1996.
RFC 2045	Draft Standard	Nathaniel Borenstein (First Virtual Holdings) and Ned Freed (Innosoft), Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies, November 1996.
RFC 2046	Draft Standard	Nathaniel Borenstein (First Virtual Holdings) and Ned Freed (Innosoft), MIME Part Two: Media Types, November 1996.
RFC 2047	Draft Standard	Keith Moore (University of Tennessee), MIME Part Three: Message Header Extensions for Non-ASCII Text, November 1996.
RFC 2048	Policy	Ned Freed (Innosoft), John Klensin (MCI), Jon Postel (USC/Information Sciences Institute), MIME Part Four: Registration Procedures, November 1996.
RFC 2049	Draft Standard	Nathaniel Borenstein (First Virtual Holdings) and Ned Freed (Innosoft), MIME Part Five: Conformance Criteria and Examples, November 1996.

Delivery Status Notifications

The list of documents in TABLE A-5 describe delivery status notification.

TABLE  A-5   Delivery Status Notifications

Standard	Status	Description
RFC 1891	Proposed Standard	SMTP Service Extension for Delivery Status Notifications, Keith Moore (University of Tennessee), January 15, 1996.
RFC 1892	Proposed Standard	Greg Vaudreuil (Corporation for National Research Initiatives), The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages, January 15, 1996.
RFC 1894	Proposed Standard	Keith Moore (University of Tennessee), Greg Vaudreuil (Corporation for National Research Initiatives), An Extensible Message Format for Delivery Status Notifications, January 15, 1996.

Domain Name Service

The documents listed in TABLE A-6 specify the naming facilities of the Internet and how those facilities are used in messaging.

TABLE  A-6   Domain Name Service

Standard	Status	Description
RFC 920	Policy	Jonathan B. Postel and Joyce K. Reynolds, USC/Information Sciences Institute, Domain Requirements, October 1984.
RFC 974	Standard	Craig Partridge, CSNET CIC BBN Laboratories Inc., Mail Routing and the Domain System, January 1986.
RFC 1032	Information	Mary K. Stahl, SRI International, Domain Administrators Guide, November 1987.
RFC 1033	Information	Mark K. Lottor, SRI International, Domain Administrators Operations Guide, November 1987.
RFC 1034	Standard	Paul V. Mockapetris, USC/Information Sciences Institute, Domain Names - Concepts and Facilities, November 1987.
RFC 1035	Standard	Paul V. Mockapetris, USC/Information Sciences Institute, Domain Names - Implementation and Specification, November 1987.

Directory Server Specifications

The following documents are relevant to national and international standards for directory server specifications.

Directory Server Specification

The material listed in TABLE A-7 describes international standards for server specifications.

TABLE  A-7   Server Specification

Standard	Status	Description
ITU X.520	International Standard	ITU-T Recommendation X.520(1993), ISO/IEC 9594-6, Information Technology - Open Systems Interconnection - The Directory: Selected Attribute Types.
ITU X.521	International Standard	ITU-T Recommendation X.521(1993), ISO/IEC 9594-7.X, Information Technology - Open Systems Interconnection - The Directory: Selected Object Classes.
RFC 1274	Proposed Standard	Paul Barker and Steve Kille, University College London, The COSINE and Internet X.500 Schema, November 1991.
RFC 1279	Information	Steve Kille, University College London, X.500 and Domains, November 1991.
RFC 1781	Proposed Standard	Steve Kille (ISODE Consortium), Using the OSI Directory to Achieve User Friendly Naming, March 1995.
RFC 1801	Experimental	Steve Kille (ISODE Consortium), MHS use of the X.500 Directory to Support MHS Routing, June 1995.
RFC 1803	Information	Russ Wright (Lawrence Berkeley Laboratory), Arlene F. Getchell (Lawrence Livermore National Laboratory), Tim Howes (University of Michigan), Srinivas R. Sataluri (AT&T Bell Laboratories), Peter Yee (Ames Research Center), and Wengyik Yeong (PSI, Inc.), Recommendations for an X.500 Production Directory Service, June 1995.

Access Protocols

The material listed in TABLE A-8 describes information about access protocols.

TABLE  A-8   Access Protocols

Standard	Description
RFC 1777	Wengyik Yeong (PSI, Inc.), Tim Howes (University of Michigan), and Steve Kille (ISODE Consortium), Lightweight Directory Access Protocol, March 1995.
RFC 1778	Tim Howes (University of Michigan), Steve Kille (ISODE Consortium), Wengyik Yeong (PSI, Inc.), and Colin Robbins (NeXor Ltd), The String Representation of Standard Attribute Syntaxes, March 1995.
RFC 1779	Steve Kille (ISODE Consortium), A String Representation of Distinguished Names, March 1995.
RFC 1798	Alan Young (ISODE Consortium), Connection-less Lightweight Directory Access Protocol, June 1995.

Text and Character Set Specifications

The following tables list documents that describe national and international telecommunications and information processing requirements.

National and International

TABLE A-9 contains material pertaining to national and international telecommunications and information exchange standards.

TABLE  A-9   National and International Information Exchange

Standard	Status	Description
IA5	International Standard	ITU-T Recommendation T.50, Fascicle VII.3, Malaga-Torremolinos, International Alphabet No. 5, International Telecommunication Union, 1984, Geneva, 1989.
ISO 2022	International Standard	International Organization for Standardization (ISO), Information processing - ISO 7-bit and 8-bit coded character sets - Code extension techniques, Ref. No. ISO 2022-1986.
JIS X 0201	National Standard	Japanese Standards Association, Code For Information Interchange, JIS X 0201-1976.
JIS X 0208	National Standard	Japanese Standards Association, Code of the Japanese Graphic Character Set For Information Interchange, JIS X 0208-1990.
JUNET	Public Network	JUNET Riyou No Tebiki Sakusei Iin Kai (JUNET User's Guide Drafting Committee), JUNET Riyou No Tebiki (JUNET User's Guide), First Edition, February 1988.
printableString ASN.1	International Standard	ITU-T X.680, aligned with ISO/IEC-8824-1 Abstract Syntax Notation One (ASN.1). Appears in LDAP/X.500 attribute data types. Defined jointly by the ISO, ITU-T standards bodies and have been reused in Internet RFCs and ISO, ITU-T standards.
US ASCII	National Standard	American National Standards Institute, ANSI X3.4-1986, Coded Character Set-7-bit American National Standards Code for information interchange. New York, 1986.
US LATIN	National Standard	American National Standards Institute, ANSI Z39.47-1985, Coded Character Set-Extended Latin alphabet code for bibliographic use. New York, 1985.

Internet References

The documentation in TABLE A-10 describes Internet communications standards.

TABLE  A-10   Internet References

Standard	Status	Description
RFC 1345	Information	Keld Simonsen, Rationel Almen Planlaegning, Internet Activities Board RFC 1345, Character Mnemonics & Character Sets, June 1992.
RFC 1468	Information	Jun Murai (Keio University), Mark Crispin (University of Washington), Japanese Character Encoding for Internet Messages, June 1993.
RFC 1502	Information	Harald Tveit Alvestrand, SINTEF DELAB, Internet Activities Board RFC 1502, X.400 Use of Extended Character Sets, August 1993.