Appendix A Supported Standards

Appendix A
Supported Standards

This appendix lists national, international, and industry standards related to electronic messaging and for which support is claimed by Sun Java System Messaging Server. 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.
RFC 2822	Proposed Standard	P. Resnick (Editor), Internet Message Format, April 2001.

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 1730	Proposed Standard	Mark R. Crispin, (University of Washington), Internet Message Access Protocol - Version 4, December 1994.
RFC 1731	Proposed Standard	John G. Myers, (Carnegie-Mellon University), IMAP4 Authentication Mechanisms, 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 1957	Information	R. Nelson, Some Observations on Implementations of the Post Office Protocol (POP3), June 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 2062	Proposed Standard	Mark R. Crispin (University of Washington), Internet Message Access Protocol - Obsolete Syntax, December 1996.
RFC 2086	Proposed Standard	John G. Myers, IMAP4 ACL Extension, January 1997.
RFC 2087	Proposed Standard	John G. Myers, IMAP4 QUOTA Extension, January 1997.
RFC 2088	Proposed Standard	John G. Myers, IMAP4 Non-Synchronizing Literals, January 1997.
RFC 2180	Information	M. Gahrns, IMAP4 Multi-Accessed Mailbox Practice, July 1997.
RFC 2342	Proposed Standard	M. Gahrns, IMAP4 Namespaces, July 1997.
RFC 2359	Proposed Standard	John G. Myers, IMAP4 UIDPLUS Extension, June 1998.
RFC 2683	Information	B. Leiba, IMAP4 Implementation Recommendations, September 1999.
RFC 3206	Proposed Standard	R. Gellens, SYS and AUTH POP Response Codes, February 2002.
RFC 3501	Proposed Standard	M. Crispin, Internet Message Access Protocol - Version 4rev1, March 2003.
RFC 3516	Proposed Standard	L. Nerenberg, IMAP4 Binary Content Extension, April 2003

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 974 STD 14	Standard	C. Partridge, Mail Routing and the Domain System, January 1986.
RFC 1123 STD 3	Standard	R.T. Braden, Requirements for Internet Hosts - Application and Support, October 1989.
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 1985	Proposed Standard	J. De Winter, SMTP Service Extension for Remote Message Queue Starting, August 1996.
RFC 2034	Proposed Standard	Ned Freed, SMTP Service Extension for Returning Enhanced Error Codes, October 1996.
RFC 2442	Information	J. Belissent, The Batch SMTP Media Type, November 1998.
RFC 2476	Proposed Standard	R. Gellens, Message Submission, December 1998.
RFC 2821	Proposed Standard	J. Klensin (Editor), Simple Mail Transfer Protocol, April 2001.
RFC 2920 STD 60	Standard	Ned Freed, SMTP Service Extension for Command Pipelining, September 2000.
RFC 3028	Proposed Standard	T. Showalter, Sieve: A Mail Filtering Language, January 2001.
RFC 3207	Proposed Standard	P. Hoffman, SMTP Service Extension for Secure SMTP over Transport Layer Security, February 2002
RFC 3431	Proposed Standard	W. Segmuller, Sieve Extension: Relational Tests, December 2002
RFC 3461	Standard	K. Moore, Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs), January 2003. (Obsoletes RFC1891)
RFC 3462	Standard	G. Vaudreuil, The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages, January 2003. Draft. (Obsoletes RFC1892)
RFC 3463	Standard	G. Vaudreuil, Enhanced Mail System Status Codes, January 2003. (Obsoletes RFC1893)
RFC 3598	Proposed Standard	K. Murchison, Sieve Email Filtering -- Subaddress Extension, September 2003

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 1847	Proposed Standard	J. Galvin, S. Murphy, S. Crocker, N. Freed, Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted, October 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.
RFC 2231	Proposed Standard	N. Freed, K. Moore, MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations, November 1997.
RFC 2298	Proposed Standard	R. Fajman, An Extensible Message Format for Message Disposition Notifications, March 1998.

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 3464	Full Standard	K. Moore, G. Vaudreuil, An Extensible Message Format for Delivery Status Notifications, January 2003.

Security

The list of documents in Table A-6 describe security protocols.

Table A-6 Security
Standard	Status	Description
RFC 1731	Proposed Standard	John G. Myers, IMAP4 Authentication Mechanisms, December 1994.
RFC 2195	Proposed Standard	J. Klensin, R. Catoe, P. Krumviede, IMAP/POP AUTHorize Extension for Simple Challenge/Response, September 1997.
RFC 2222	Proposed Standard	John G. Myers, Simple Authentication and Security Layer (SASL), October 1997.
RFC 2246	Proposed Standard	T. Dierks, C. Allen, The TLS Protocol Version 1.0, January 1999.
RFC 2505 BCP 30	Best Current Practice	G. Lindberg, Anti-Spam Recommendations for SMTP MTAs, February 1999.
RFC 2554	Proposed Standard	John G. Myers, SMTP Service Extension for Authentication, March 1999.
RFC 2595	Proposed Standard	C. Newman, Using TLS with IMAP, POP3, and ACAP, June 1999. (Supported by MMP, POP and IMAP.)
RFC 2831	Proposed Standard	P. Leach, C. Newman, Using Digest Authentication as a SASL Mechanism, May 2000. (Not yet supported by MMP.)
RFC 3207	Proposed Standard	P. Hoffman, SMTP Service Extension for Secure SMTP over Transport Layer Security, February 2002.

Domain Name Service

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

Table A-7 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.

Text and Character Set Specifications

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



Note	Sun Java System Messaging Server supports additional character set and language standards not listed here.

National and International

Table A-8 contains material pertaining to national and international telecommunications and information exchange standards.

Table A-8 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.
UTF-8	International Standard	F. Yergeau, UTF-8, a transformation format of ISO 10646, January 1998

Internet References

The documentation in Table A-9 describes Internet communications standards.

Table A-9 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.

Previous Contents Index Next

Previous Contents Index Next
Sun Java System Messaging Server 6 2004Q2 Administration Reference