IETF Logo Mail Archive

Re: STARTTLS & EHLO

Peter Bowyer <peter@bowyer.org> Wed, 28 January 2009 21:15 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 n0SLFl9x069307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2009 14:15:48 -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 n0SLFlhV069306; Wed, 28 Jan 2009 14:15:47 -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 nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0SLFaVW069299 for <ietf-smtp@imc.org>; Wed, 28 Jan 2009 14:15:47 -0700 (MST) (envelope-from peeebeee@gmail.com)
Received: by nf-out-0910.google.com with SMTP id 30so1554419nfu.24 for <ietf-smtp@imc.org>; Wed, 28 Jan 2009 13:15:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=jWRFlilVpOC0S15fyfZL5bz9UyFnYgbj65jvFZI850Q=; b=ZupikHVp+AhLf3DIUgNQNP2O28KskT9DZr1uBsmQclyYqb6l7xZ0pIFWP2c/+wb6yq YJY+Xcf9ROHZGJwTru24ykuPnr7/ycY2iKF53HZJhq7yVzqZ/6McRJ05xhbrDg9wKVlZ U60RAimaAv5MCvaQgzQM33tOszyPbVZchgguM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=QQc1uu3Kq99vkxIdt/h43qhYAwNJMhmYSsnE5Ks0K1wyMU9iFEzFNDBSNGNc+yytkO LpV0RpiIvNr69Kf3oWYL3MLbPV/YLUGYBCuRT+441o6kDHBS92Fd3MCMU+p3KEMPHRb/ CU0oLjPb4eLPrmf7vt2VPQ9H9lv1fQ3GighiI=
MIME-Version: 1.0
Received: by 10.223.122.70 with SMTP id k6mr908276far.26.1233177335169; Wed, 28 Jan 2009 13:15:35 -0800 (PST)
In-Reply-To: <498088B8.9040404@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>
Date: Wed, 28 Jan 2009 21:15:35 +0000
X-Google-Sender-Auth: 5a39373fd1d79345
Message-ID: <56152ae90901281315y5847c2demd3431559f6fdcec9@mail.gmail.com>
Subject: Re: STARTTLS & EHLO
From: Peter Bowyer <peter@bowyer.org>
To: ietf-smtp@imc.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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>

2009/1/28 Paul Smith <paul@pscs.co.uk>:

> To me, it was (initially) 'clear' that the example saying 'such as the
> argument to the EHLO command', was precise enough to imply that the fact
> that the EHLO command was sent should not be discarded. It could have
> said 'such as the EHLO command', but it went out of its way to say '*the
> argument to* the EHLO command'.

But the 'domain' argument to the EHLO command is mandatory (RFC1869
S4.2). So a server state of having received a valid EHLO but not
knowing what the domain argument is, is not attainable under 1869. I
don't believe 3207's intent is to introduce that state as valid after
STARTTLS.

Peter

-- 
Peter Bowyer
Email: peter@bowyer.org
Follow me on Twitter: twitter.com/peeebeee

v2.23.0 | Report a Bug | By Email