|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2049 (1996)
|
|
Title:
|
Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples (RFC 2049)
|
|
|
2.
|
Status of approval:
|
|
|
November 1996 as Standards Track
|
|
3.
|
Justification for the specific reference:
|
|
|
The referenced document constitutes provisions of this Recommendation
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
The IETF Trust's Legal Provisions Relating to IETF Documents(http://trustee.ietf.org/license-info)
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This memo provides information for the Internet community. It does
not specify an Internet standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
These documents are based on earlier work documented in RFC 934, STD
11, and RFC 1049, but extends and revises them. Because RFC 822 said
so little about message bodies, these documents are largely
orthogonal to (rather than a revision of) RFC 822.
The initial document in this set, RFC 2045, specifies the various
headers used to describe the structure of MIME messages. The second
document defines the general structure of the MIME media typing
system and defines an initial set of media types. The third
document, RFC 2047, describes extensions to RFC 822 to allow non-US-ASCII text data in Internet mail header fields. The fourth document,
RFC 2048, specifies various IANA registration procedures for MIME-
related facilities. This fifth and final document describes MIME
conformance criteria as well as providing some illustrative examples
of MIME message formats, acknowledgements, and the bibliography.
These documents are revisions of RFCs 1521, 1522, and 1590, which
themselves were revisions of RFCs 1341 and 1342. Appendix B of this
document describes differences and changes from previous versions.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[ATK]/
Borenstein, Nathaniel S., Multimedia Applications/
Development with the Andrew Toolkit, Prentice-Hall, 1990./
/
[ISO-2022]/
International Standard -- Information Processing --/
Character Code Structure and Extension Techniques,/
ISO/IEC 2022:1994, 4th ed./
/
[ISO-8859]/
International Standard -- Information Processing -- 8-bit/
Single-Byte Coded Graphic Character Sets/
- Part 1: Latin Alphabet No. 1, ISO 8859-1:1987, 1st ed./
- Part 2: Latin Alphabet No. 2, ISO 8859-2:1987, 1st ed./
- Part 3: Latin Alphabet No. 3, ISO 8859-3:1988, 1st ed./
- Part 4: Latin Alphabet No. 4, ISO 8859-4:1988, 1st ed./
- Part 5: Latin/Cyrillic Alphabet, ISO 8859-5:1988, 1st/
ed./
- Part 6: Latin/Arabic Alphabet, ISO 8859-6:1987, 1st ed./
- Part 7: Latin/Greek Alphabet, ISO 8859-7:1987, 1st ed./
- Part 8: Latin/Hebrew Alphabet, ISO 8859-8:1988, 1st ed./
- Part 9: Latin Alphabet No. 5, ISO/IEC 8859-9:1989, 1st/
ed./
International Standard -- Information Technology -- 8-bit/
Single-Byte Coded Graphic Character Sets/
- Part 10: Latin Alphabet No. 6, ISO/IEC 8859-10:1992,/
1st ed./
/
[ISO-646]/
International Standard -- Information Technology -- ISO/
7-bit Coded Character Set for Information Interchange,/
ISO 646:1991, 3rd ed../
/
[JPEG]/
JPEG Draft Standard ISO 10918-1 CD./
/
[MPEG]/
Video Coding Draft Standard ISO 11172 CD, ISO/
IEC/JTC1/SC2/WG11 (Motion Picture Experts Group), May,/
1991./
[PCM]/
CCITT, Fascicle III.4 - Recommendation G.711, "Pulse Code/
Modulation (PCM) of Voice Frequencies", Geneva, 1972./
/
[POSTSCRIPT]/
Adobe Systems, Inc., PostScript Language Reference/
Manual, Addison-Wesley, 1985./
/
[POSTSCRIPT2]/
Adobe Systems, Inc., PostScript Language Reference/
Manual, Addison-Wesley, Second Ed., 1990./
/
[RFC-783]/
Sollins, K.R., "TFTP Protocol (revision 2)", RFC-783,/
MIT, June 1981./
/
[RFC-821]/
Postel, J.B., "Simple Mail Transfer Protocol", STD 10,/
RFC 821, USC/Information Sciences Institute, August 1982./
/
[RFC-822]/
Crocker, D., "Standard for the Format of ARPA Internet/
Text Messages", STD 11, RFC 822, UDEL, August 1982./
/
[RFC-934]/
Rose, M. and E. Stefferud, "Proposed Standard for Message/
Encapsulation", RFC 934, Delaware and NMA, January 1985./
/
[RFC-959]/
Postel, J. and J. Reynolds, "File Transfer Protocol", STD/
9, RFC 959, USC/Information Sciences Institute, October/
1985./
/
[RFC-1049]/
Sirbu, M., "Content-Type Header Field for Internet/
Messages", RFC 1049, CMU, March 1988./
/
[RFC-1154]/
Robinson, D., and R. Ullmann, "Encoding Header Field for/
Internet Messages", RFC 1154, Prime Computer, Inc., April/
1990./
/
[RFC-1341]/
Borenstein, N., and N. Freed, "MIME (Multipurpose/
Internet Mail Extensions): Mechanisms for Specifying and/
Describing the Format of Internet Message Bodies", RFC/
1341, Bellcore, Innosoft, June 1992./
[RFC-1342]/
Moore, K., "Representation of Non-Ascii Text in Internet/
Message Headers", RFC 1342, University of Tennessee, June/
1992./
/
[RFC-1344]/
Borenstein, N., "Implications of MIME for Internet Mail/
Gateways", RFC 1344, Bellcore, June 1992./
/
[RFC-1345]/
Simonsen, K., "Character Mnemonics & Character Sets", RFC/
1345, Rationel Almen Planlaegning, June 1992./
/
[RFC-1421]/
Linn, J., "Privacy Enhancement for Internet Electronic/
Mail: Part I -- Message Encryption and Authentication/
Procedures", RFC 1421, IAB IRTF PSRG, IETF PEM WG,/
February 1993./
/
[RFC-1422]/
Kent, S., "Privacy Enhancement for Internet Electronic/
Mail: Part II -- Certificate-Based Key Management", RFC/
1422, IAB IRTF PSRG, IETF PEM WG, February 1993./
/
[RFC-1423]/
Balenson, D., "Privacy Enhancement for Internet/
Electronic Mail: Part III -- Algorithms, Modes, and/
Identifiers", IAB IRTF PSRG, IETF PEM WG, February 1993./
/
[RFC-1424]/
Kaliski, B., "Privacy Enhancement for Internet Electronic/
Mail: Part IV -- Key Certification and Related/
Services", IAB IRTF PSRG, IETF PEM WG, February 1993./
/
[RFC-1521]/
Borenstein, N., and Freed, N., "MIME (Multipurpose/
Internet Mail Extensions): Mechanisms for Specifying and/
Describing the Format of Internet Message Bodies", RFC/
1521, Bellcore, Innosoft, September, 1993./
/
[RFC-1522]/
Moore, K., "Representation of Non-ASCII Text in Internet/
Message Headers", RFC 1522, University of Tennessee,/
September 1993./
/
[RFC-1524]/
Borenstein, N., "A User Agent Configuration Mechanism for/
Multimedia Mail Format Information", RFC 1524, Bellcore,/
September 1993./
/
[RFC-1543]/
Postel, J., "Instructions to RFC Authors", RFC 1543,/
USC/Information Sciences Institute, October 1993./
/
[RFC-1556]/
Nussbacher, H., "Handling of Bi-directional Texts in/
MIME", RFC 1556, Israeli Inter-University Computer/
Center, December 1993./
/
[RFC-1590]/
Postel, J., "Media Type Registration Procedure", RFC/
1590, USC/Information Sciences Institute, March 1994./
/
[RFC-1602]/
Internet Architecture Board, Internet Engineering/
Steering Group, Huitema, C., Gross, P., "The Internet/
Standards Process -- Revision 2", March 1994./
/
[RFC-1652]/
Klensin, J., (WG Chair), Freed, N., (Editor), Rose, M.,/
Stefferud, E., and Crocker, D., "SMTP Service Extension/
for 8bit-MIME transport", RFC 1652, United Nations/
University, Innosoft, Dover Beach Consulting, Inc.,/
Network Management Associates, Inc., The Branch Office,/
March 1994./
/
[RFC-1700]/
Reynolds, J. and J. Postel, "Assigned Numbers", STD 2,/
RFC 1700, USC/Information Sciences Institute, October/
1994./
/
[RFC-1741]/
Faltstrom, P., Crocker, D., and Fair, E., "MIME Content/
Type for BinHex Encoded Files", December 1994./
/
[RFC-1896]/
Resnick, P., and A. Walker, "The text/enriched MIME/
Content-type", RFC 1896, February, 1996./
[RFC-2045]/
Freed, N., and and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part One: Format of Internet Message/
Bodies", RFC 2045, Innosoft, First Virtual Holdings,/
November 1996./
/
[RFC-2046]/
Freed, N., and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part Two: Media Types", RFC 2046,/
Innosoft, First Virtual Holdings, November 1996./
/
[RFC-2047]/
Moore, K., "Multipurpose Internet Mail Extensions (MIME)/
Part Three: Representation of Non-ASCII Text in Internet/
Message Headers", RFC 2047, University of/
Tennessee, November 1996./
/
[RFC-2048]/
Freed, N., Klensin, J., and J. Postel, "Multipurpose/
Internet Mail Extensions (MIME) Part Four: MIME/
Registration Procedures", RFC 2048, Innosoft, MCI,/
ISI, November 1996./
/
[RFC-2049]/
Freed, N. and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part Five: Conformance Criteria and/
Examples", RFC 2049 (this document), Innosoft, First/
Virtual Holdings, November 1996./
/
[US-ASCII]/
Coded Character Set -- 7-Bit American Standard Code for/
Information Interchange, ANSI X3.4-1986./
/
[X400]/
Schicker, Pietro, "Message Handling Systems, X.400",/
Message Handling Systems and Distributed Applications, E./
Stefferud, O-j. Jacobsen, and P. Schicker, eds., North-/
Holland, 1989, pp. 3-41./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None.
|
|
