Message Submission BURL Extension
draft-ietf-lemonade-burl-04

The information below is for an old version of the document that is already published as an RFC
Document Type RFC Internet-Draft (lemonade WG)
Author Chris Newman 
Last updated 2020-01-21 (latest revision 2005-11-11)
Stream Internet Engineering Task Force (IETF)
Formats pdf htmlized (tools) htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 4468 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Ted Hardie
Send notices to (None)
Network Working Group                                          C. Newman
Internet-Draft                                          Sun Microsystems
Updates: 3463 (if approved)                            November 10, 2005
Expires: May 14, 2006

                   Message Submission BURL Extension
                    draft-ietf-lemonade-burl-04.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on May 14, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   The submission profile of Simple Mail Transfer Protocol (SMTP)
   provides a standard way for an email client to submit a complete
   message for delivery.  This specification extends the submission
   profile by adding a new BURL command which can be used to fetch
   submission data from an Internet Message Access Protocol (IMAP)
   server.  This permits a mail client to inject content from an IMAP
   server into the SMTP infrastructure without downloading it to the
   client and uploading it back to the server.

Newman                    Expires May 14, 2006                  [Page 1]
Internet-Draft      Message Submission BURL Extension      November 2005

Table of Contents

   1.  Conventions Used in this Document  . . . . . . . . . . . . . .  3
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  BURL Submission Extension  . . . . . . . . . . . . . . . . . .  3
     3.1   SMTP Submission Extension Registration . . . . . . . . . .  3
     3.2   BURL Transaction . . . . . . . . . . . . . . . . . . . . .  4
     3.3   The BURL IMAP Option . . . . . . . . . . . . . . . . . . .  4
     3.4   Examples . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.5   Formal Syntax  . . . . . . . . . . . . . . . . . . . . . .  7
   4.  8-bit and Binary . . . . . . . . . . . . . . . . . . . . . . .  7
   5.  Updates to RFC 3463  . . . . . . . . . . . . . . . . . . . . .  8
   6.  Response Codes . . . . . . . . . . . . . . . . . . . . . . . .  8
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     9.1   Normative References . . . . . . . . . . . . . . . . . . . 11
     9.2   Informative References . . . . . . . . . . . . . . . . . . 12
       Author's Address . . . . . . . . . . . . . . . . . . . . . . . 13
   A.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 13
       Intellectual Property and Copyright Statements . . . . . . . . 14

Newman                    Expires May 14, 2006                  [Page 2]
Internet-Draft      Message Submission BURL Extension      November 2005

1.  Conventions Used in this Document

   The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY"
   in this document are to be interpreted as defined in "Key words for
   use in RFCs to Indicate Requirement Levels" [RFC2119].

   The formal syntax use the Augmented Backus-Naur Form (ABNF) [RFC4234]
   notation including the core rules defined in Appendix B of RFC 4234.

2.  Introduction

   This specification defines an extension to the standard Message
   Submission [I-D.gellens-submit-bis] protocol to permit data to be
   fetched from an IMAP server at message submission time.  This MAY be
   used in conjunction with the CHUNKING [RFC3030] mechanism so that
   chunks of the message can come from an external IMAP server.  This
   provides the ability to forward an email message without first
   downloading it to the client.

3.  BURL Submission Extension

   This section defines the BURL submission extension.

3.1  SMTP Submission Extension Registration

   1.  The name of this submission extension is "BURL".  This extends
       the Message Submission protocol on port 587 and MUST NOT be
       advertised by a regular SMTP [RFC2821] server on port 25 that
       acts as a relay for incoming mail from other SMTP relays.

   2.  The EHLO keyword value associated with the extension is "BURL".
Show full document text