Re: STARTTLS & EHLO: Errata text?

John C Klensin <john+smtp@jck.com> Fri, 30 January 2009 09:46 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 n0U9k8QF069267 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Jan 2009 02:46:08 -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 n0U9k8ZX069266; Fri, 30 Jan 2009 02:46:08 -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 n0U9jvlX069245 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-smtp@imc.org>; Fri, 30 Jan 2009 02:46:08 -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 1LSpwg-0007lB-58; Fri, 30 Jan 2009 04:45:54 -0500
Date: Fri, 30 Jan 2009 04:45:53 -0500
From: John C Klensin <john+smtp@jck.com>
To: Paul Smith <paul@pscs.co.uk>
cc: Tony Hansen <tony@att.com>, ietf-smtp@imc.org
Subject: Re: STARTTLS & EHLO: Errata text?
Message-ID: <CFC077C262CCF947EF05EC8F@PST.JCK.COM>
In-Reply-To: <4982CAB7.1030308@pscs.co.uk>
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> <3B757DEDD02F9E7C1ADBD4EF@PST.JCK.COM> <4982CAB7.1030308@pscs.co.uk>
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>

--On Friday, January 30, 2009 9:39 +0000 Paul Smith
<paul@pscs.co.uk> wrote:

> John C Klensin wrote:
>>> 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.
>>   
> Just going back a step, shouldn't it be worded something like
> 
> "The client MUST send a EHLO command after a successful TLS
> negotiation if it wishes to start a mail transaction or use
> any SMTP extensions."
> 
> Because that's actually what we mean.
> 
> Also, saying 'or a command that does not require that a mail
> transaction be open' means that you could use an SMTP
> extension which was advertised before the STARTTLS, as long as
> it doesn't involve a mail transaction, without resending EHLO.

That would be a better fix, as would something along the lines
of the "must not trust" suggestion, as long as it was absolutely
clear whether or not EHLO needed to be resent (I think is does
because the client can't know whether or not the server intends
to make use of the argument).

    john