A new Request for Comments is now available in online RFC libraries.


        RFC 3030

        Title:      SMTP Service Extensions for Transmission of Large
                    and Binary MIME Messages
        Author(s):  G. Vaudreuil
        Status:     Standards Track
        Date:       December 2000
        Mailbox:    GregV@ieee.org
        Pages:      12
        Characters: 23405
        Obsoletes:  1830

        I-D Tag:    draft-vaudreuil-esmtp-binary2-03.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc3030.txt


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 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


