Re: draft-fanf-dane-smtp

Hector Santos <hsantos@isdg.net> Wed, 30 May 2012 02:12 UTC

Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q4U2C6mS060091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 May 2012 19:12:06 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.5/8.13.5/Submit) id q4U2C6B0060090; Tue, 29 May 2012 19:12:06 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from mail.catinthebox.net (secure.winserver.com [208.247.131.9]) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q4U2C491060084 for <ietf-smtp@imc.org>; Tue, 29 May 2012 19:12:05 -0700 (MST) (envelope-from hsantos@isdg.net)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; t=1338343920; h=Received:Received:Received: Received:Message-ID:Date:From:Organization:To:Subject:List-ID; bh=lCd7Bfztd8Nl4UTs3FC2J87e32E=; b=mF/KqBQjOiGktbIbBybfM5bn2Kyn8 IqRRuOGpok0ns1btDF2jjL6ZIVY73Ky8oYnF6EPpVKlGcb63BazIjZwoweTZLDCQ e4HXdAGODm2Ys4ULtXCHKibebEqdVGBN1bVlu5FE9wC1Q8TWrEsrmeYHukyYZOQs zLYFyxuc20odZc=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf-smtp@imc.org; Tue, 29 May 2012 22:12:00 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2955734366.7640.2648; Tue, 29 May 2012 22:11:59 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; t=1338343874; h=Received:Received:Message-ID: Date:From:Organization:To:Subject:List-ID; bh=PNqHySKvMJDtFcuTn0 w+lZjh33xQX8puNTmHhz20DJI=; b=j1iIMYKm6Ux9j90VRdRcRwvEGdQNLmiK/8 HSyRfbW+x5LNtt6ZmgHkNg2BsBSXf2YK1jhPkfKWK6YfbY1gy1jRWGPHy4ZxZS1d Ai9ablD0fzoi+0JnsqsDGjnrX8qvLOgOfgZtUNY/TdNYUg2a5GVOn+ugcJWWWcC4 JzVgnPnN8=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf-smtp@imc.org; Tue, 29 May 2012 22:11:14 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 3554606878.10571.6968; Tue, 29 May 2012 22:11:13 -0400
Message-ID: <4FC58201.7010701@isdg.net>
Date: Tue, 29 May 2012 22:12:17 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
CC: dane@ietf.org, ietf-smtp@imc.org
Subject: Re: draft-fanf-dane-smtp
References: <alpine.LSU.2.00.1205251812480.572@hermes-2.csi.cam.ac.uk> <4FC2AE5F.5010308@isdg.net> <alpine.LSU.2.00.1205291257270.10076@hermes-2.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1205291257270.10076@hermes-2.csi.cam.ac.uk>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
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>

Tony Finch wrote:
> Hector Santos <hsantos@isdg.net> wrote:
>> I guess, if anything else, there are two client suggestions to highlight:
>>
>>   - Automated MTA (router)
>>   - Interactive MUA smtp client
> 
> The draft is for inter-domain SMTP so message submission is out of scope.
> I don't think I can make this clearer.
> 
> Tony.

Oh, so that is what you meant by "inter-domain."   I am not use to 
using that term within the confines of mail systems but it fits. 
Other terms are "routers," "relays," etc or just MTA.  I prefer router.

   Inter-domain SMTP:  SMTP between different ADMDs across the public
       Internet, where a client sends mail to a publicly-referenced SMTP
       server.

I suggest to add an i.e.

    i.e. a router, relaying MTA, not an MUA with a possible interactive
         CN vs Host domain checking method where the HUMAN is involved.

Anyway, ironically, we are having a related thread now in our support 
forum regarding a sysop asking about self-signed vs CA signed certs.

My question is:

If the client has to be modified to do this extra TLSA check, then why 
not just add login to do a CA 3rd party repository?   Or support OCSP 
(Online Certificate Status Protocol) RFC2560?

When change is proposed, then it has to have a payoff.  A client 
trusting a self-signed signature is going to be pre-defined or 
pre-arranged or known upfront.

-- 
HLS