Re: [yam] draft-daboo-srv-email: POP3S/IMAPS?

Ned Freed <ned.freed@mrochek.com> Mon, 18 January 2010 17:11 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: yam@core3.amsl.com
Delivered-To: yam@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7111F3A696B for <yam@core3.amsl.com>; Mon, 18 Jan 2010 09:11:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.347
X-Spam-Level:
X-Spam-Status: No, score=-2.347 tagged_above=-999 required=5 tests=[AWL=0.252, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uDM8v49bK5PC for <yam@core3.amsl.com>; Mon, 18 Jan 2010 09:11:13 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 6E2E03A695E for <yam@ietf.org>; Mon, 18 Jan 2010 09:11:13 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NILLMSBGRK00B9ZR@mauve.mrochek.com> for yam@ietf.org; Mon, 18 Jan 2010 09:11:03 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NIFYPPK6GG004042@mauve.mrochek.com>; Mon, 18 Jan 2010 09:10:59 -0800 (PST)
Message-id: <01NILLMPPQHY004042@mauve.mrochek.com>
Date: Mon, 18 Jan 2010 08:53:48 -0800
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Mon, 18 Jan 2010 13:12:45 +0000" <alpine.LSU.2.00.1001181311440.6203@hermes-2.csi.cam.ac.uk>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <9A584868-5961-4871-B32E-915394043727@sabahattin-gucukoglu.com> <01NIK8RBBRJK004042@mauve.mrochek.com> <alpine.LSU.2.00.1001181311440.6203@hermes-2.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
Cc: imap-protocol@u.washington.edu, Ned Freed <ned.freed@mrochek.com>, yam@ietf.org
Subject: Re: [yam] draft-daboo-srv-email: POP3S/IMAPS?
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yam>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jan 2010 17:11:14 -0000

> On Sun, 17 Jan 2010, Ned Freed wrote:
> >
> > > Why does the spec provision for IMAPS and POP3S?
> >
> > Because a provisioning mechanism that fails to deal with the needs ot
> > real-world deployments - and there's plenty of this secure port stuff deployed
> > out there - makes itself far less likely to deploy.

> In that case shouldn't it also document smtps?

Is smtps as widely deployed as pops or imaps? If it is then yes, it should be
in there. But if it isn't - and my experience has been that it isn't - then
there's no need.

This all goes back to when the various different protocols added and deployed
extension mechanisms as compared with when SSL/TLS support was added and
deployed. The SMTP extension mechansim came first in terms of definition and
deployment, so that when SSL/TLS came along the path of least resistance was to
use STARTTLS inside the protocol. POP3 extensibility came much later, so pops
was the past of least resistance there. And IMAP is somewhere in the middle.
(I actually don't know if in terms of deployment imaps is worth having in
there, but pops sure is.)

				Ned