Re: STARTTLS & EHLO: Errata text?

John C Klensin <john+smtp@jck.com> Thu, 29 January 2009 19:59 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0TJxHu4037948 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2009 12:59:17 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n0TJxHbx037947; Thu, 29 Jan 2009 12:59:17 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0TJx5ih037936 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-smtp@imc.org>; Thu, 29 Jan 2009 12:59:17 -0700 (MST) (envelope-from john+smtp@jck.com)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1LSd2W-000Ich-RA; Thu, 29 Jan 2009 14:59:05 -0500
Date: Thu, 29 Jan 2009 14:59:04 -0500
From: John C Klensin <john+smtp@jck.com>
To: Tony Hansen <tony@att.com>, ietf-smtp@imc.org
Subject: Re: STARTTLS & EHLO: Errata text?
Message-ID: <3B757DEDD02F9E7C1ADBD4EF@PST.JCK.COM>
In-Reply-To: <4981E1AB.9000002@att.com>
References: <497DE492.4080506@pscs.co.uk> <497DED29.70402@att.com> <497ED420.30708@pscs.co.uk> <alpine.LSU.2.00.0901271403220.4546@hermes-2.csi.cam.ac.uk> <497F86CB.60904@att.com> <alpine.LSU.2.00.0901281434440.4546@hermes-2.csi.cam.ac.uk> <498088B8.9040404@pscs.co.uk> <alpine.LSU.2.00.0901291310080.4546@hermes-2.csi.cam.ac.uk> <4981C0D5.1010401@pscs.co.uk> <4981C6BD.2040900@att.com> <37F39FF37390694B69567838@PST.JCK.COM> <4981E1AB.9000002@att.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>

Tony,

Given the confusion about readings, I'd recommend modifying your
changes to make them brutally clear.  Suggestions below.

--On Thursday, January 29, 2009 12:04 -0500 Tony Hansen
<tony@att.com> wrote:

> 
> If we were to write an Errata against RFC 3207, I'd suggest
> text such as the following (in Errata format):
> 
> Section:
>    4.2 Result of the STARTTLS Command
> 
> Old text:
>    The server MUST discard any knowledge obtained from the
> client, such    as the argument to the EHLO command, which was
> not obtained from the    TLS negotiation itself.
> 
> New text:
>    The server MUST discard any knowledge obtained from the
> client that    was not obtained from the TLS negotiation
> itself. The server state    is otherwise as if the connection
> had just been opened.

s/opened/opened, i.e., before a session has been established by
the client sending EHLO/
 
> Reason:
>    The example is misleading and has lead some people to think
> that    knowledge of an EHLO having been sent previously
> should be    remembered.
 
> Section:
>    4.2 Result of the STARTTLS Command
> 
> Old text:
>    The client SHOULD send an EHLO command as the
>    first command after a successful TLS negotiation.
> 
> New text:
>    The client MUST send either an EHLO command or a HELO
> command as the    first command after a successful TLS
> negotiation.

s/HELO command as/HELO command, or a command that does not
require that a mail transaction be open, as/

That can be done in several other ways, but I don't think you
can or should prohibit VRFY, EXPN, HELP, etc., there.

> Reason:
>    Since the state is reset to that of a connection having
> just been    opened, the requirement from RFC 5321 applies:
> 
> 	In any event, a client MUST issue HELO or EHLO before
> starting a 	mail transaction.
> 
>    The previous text implied that a client can get by without
> sending    one or the either.

 
> Now for the $64k questions:
> 
> 1) Is there consensus behind this viewpoint?

Wfm, with the changes above.

> 2) If so, does the text above cover the ground?

See suggestions above.

> 3) If so, who wants to file the Errata?

Having written it, is there any reason why you should not just
go ahead and do it?

    john