Browse Prior Art Database

SMTP Service Extensions for Transmission of Large and Binary MIME Messages (RFC3030)

IP.com Disclosure Number: IPCOM000005222D
Original Publication Date: 2000-Dec-01
Included in the Prior Art Database: 2001-Aug-17
Document File: 13 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Vaudreuil: AUTHOR

Abstract

This memo defines two extensions to the SMTP (Simple Mail Transfer Protocol) service. The first extension enables a SMTP client and server to negotiate the use of an alternative to the DATA command, called "BDAT", for efficiently sending large MIME (Multipurpose Internet Mail Extensions) messages. The second extension takes advantage of the BDAT command to permit the negotiated sending of MIME messages that employ the binary transfer encoding. This document is intended to update and obsolete RFC 1830.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 14% of the total text.

Network Working Group G. Vaudreuil Request for Comments: 3030 Lucent Technologies Obsolete: 1830 December 2000 Category: Standards Track

SMTP Service Extensions for Transmission of Large

and Binary MIME Messages

Status of this Memo

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.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

This memo defines two extensions to the SMTP (Simple Mail Transfer Protocol) service. The first extension enables a SMTP client and server to negotiate the use of an alternative to the DATA command, called "BDAT", for efficiently sending large MIME (Multipurpose Internet Mail Extensions) messages. The second extension takes advantage of the BDAT command to permit the negotiated sending of MIME messages that employ the binary transfer encoding. This document is intended to update and obsolete RFC 1830.

Working Group Summary

This protocol is not the product of an IETF working group, however the specification resulted from discussions within the ESMTP working group. The resulting protocol documented in RFC 1830 was classified as experimental at that time due to questions about the robustness of the Binary Content-Transfer-Encoding deployed in then existent MIME implementations. As MIME has matured and other uses of the Binary Content-Transfer-Encoding have been deployed, these concerns have been allayed. With this document, Binary ESMTP is expected to become standards-track.

Vaudreuil Standards Track [Page 1]

RFC 3030 Binary ESMTP December 2000

Document Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

Table of Contents

1. Overview ................................................... 2 2. Framework for the Large Message Extensions ................. 3 3. Framework for the Binary Service Extension ................. 5 4. Examples ................................................... 8 4.1 Simple Chunking .......................................... 8

4.2 Pipelining BINARYMIME .................................... 8 5. Security Considerations .................................... 9 6. References ................................................. 9 7. Author's Address ........................................... 10 8. Appendix A Changes from RFC 1830 ......................... 11 9. Full Copyright Statement ................................... 12

1. Overview

The MIME extensions to the Internet message format provides for the transmission of many kinds of data that were previously unsupported in Internet mail. Anticipating the need to transport the new media more efficiently, ...