IMAP4 Binary Content Extension
draft-nerenberg-imap-binary-07

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3516.
Author Lyndon Nerenberg
Last updated 2020-01-21 (Latest revision 2002-11-06)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
txt htmlized pdf bibtex bibxml
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3516 (Proposed Standard)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Ned Freed
IESG note ** No value found for 'doc.notedoc.note' **
Send notices to (None)
Email authors IPR References Referenced by Nits Search email archive
draft-nerenberg-imap-binary-07 
A new Request for Comments is now available in online RFC libraries.

        RFC 3516

        Title:      IMAP4 Binary Content Extension
        Author(s):  L. Nerenberg
        Status:     Standards Track
        Date:       April 2003
        Mailbox:    lyndon@orthanc.ab.ca
        Pages:      8
        Characters: 14598
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-nerenberg-imap-binary-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3516.txt

This memo defines the Binary extension to the Internet Message Access
Protocol (IMAP4).  It provides a mechanism for IMAP4
clients and servers to exchange message body data without using a MIME
content-transfer-encoding.

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.