SMTP Service Extension for Early Pipelining
draft-harris-early-pipe-01

Document Type Active Internet-Draft (individual)
Last updated 2018-09-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                     J. Harris, Ed.
Internet-Draft                                                      None
Intended status: Experimental                         September 13, 2018
Expires: March 17, 2019

              SMTP Service Extension for Early Pipelining
                       draft-harris-early-pipe-01

Abstract

   PIPE_CONNECT is an SMTP extension supporting the pipelining of
   banner, EHLO and one following command or traditionally-pipelined
   sequence in an SMTP conversation.  It permits a reduction in delivery
   latency by eliminating a nunmber of network round-trips.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on March 17, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Harris                   Expires March 17, 2019                 [Page 1]
Internet-Draft            SMTP Early Pipelining           September 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Framework for the Early Pipelining extension  . . . . . . . .   2
     2.1.  Simple List . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  The Early Pipelining Service Extension  . . . . . . . . . . .   3
     3.1.  Client use of Early Pipelining  . . . . . . . . . . . . .   3
       3.1.1.  Service Acquisition . . . . . . . . . . . . . . . . .   3
       3.1.2.  Service use . . . . . . . . . . . . . . . . . . . . .   3
         3.1.2.1.  Service use in cleatext . . . . . . . . . . . . .   3
         3.1.2.2.  Service use after STARTTLS  . . . . . . . . . . .   4
         3.1.2.3.  Service use in encrypted non-STARTTLS connections   4
       3.1.3.  Cache invalidation  . . . . . . . . . . . . . . . . .   4
     3.2.  Server use of Early Pipelining  . . . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The SMTP protocol [RFC5321] specifies an interlocked sequence of
   commands and responses for the start of the conversation between
   client and server.  Later portions of the conversation can use non-
   interlocked commands when the PIPELINING extession [RFC2920] is used.
   This memo specifies a way to perform non-interlocked operations early
   in the SMTP conversation.

1.1.  Requirements Language

   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].

2.  Framework for the Early Pipelining extension

   The Early Pipielining extension is defined as follows:

2.1.  Simple List

   1.  the name of the SMTP service extension is Early Pipielining;

   2.  the EHLO keyword value associated with the extension is
       PIPE_CONNECT;

Harris                   Expires March 17, 2019                 [Page 2]
Internet-Draft            SMTP Early Pipelining           September 2018

   3.  no parameter is used with the PIPE_CONNECT EHLO keyword;

   4.  no additional parameters are added to either the MAIL FROM or
       RCPT TO commands;

   5.  no additional SMTP verbs are defined by this extension; and,

   6.  the next section specifies how support for the extension affects
       the behavior of a server and client SMTP.
Show full document text