IETF Logo Mail Archive

[Uta] What's the right thing to do about Port 465?

Keith Moore <moore@network-heretics.com> Mon, 10 March 2014 07:02 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A22B1A03D3 for <uta@ietfa.amsl.com>; Mon, 10 Mar 2014 00:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Level:
X-Spam-Status: No, score=-1.2 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LGSdITRgzo9I for <uta@ietfa.amsl.com>; Mon, 10 Mar 2014 00:02:18 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 198021A03D1 for <uta@ietf.org>; Mon, 10 Mar 2014 00:02:17 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 896DE20FED for <uta@ietf.org>; Mon, 10 Mar 2014 03:02:07 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 10 Mar 2014 03:02:07 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=l4qDNjlnu6QyGI4tYdIx9z dHIuk=; b=W3M7hqok60TJO3w7kBmmo63TUbK0JWTqftgGwTCsU/ZyebN5gVhJv2 kOIzgS0atJAm73KwI5A2mUyAmVoUu6EVf6PGs933UZAmAerMPfIDphHQZzU5MkbC lmrMnMkNYTmBwkjzlOvJDi47MHP/7eanlhecKU+MB0Lwm9LRb0Ycg=
X-Sasl-enc: Qnvd7IQvZ3Gk8Nu6NKAKS8Yre5KZv+V2e+7Gu9+Zr87G 1394434927
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id EE9C7680295; Mon, 10 Mar 2014 03:02:06 -0400 (EDT)
Message-ID: <531D6338.7050505@network-heretics.com>
Date: Mon, 10 Mar 2014 03:01:12 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: uta@ietf.org
References: <2A0EFB9C05D0164E98F19BB0AF3708C711FB9AAD89@USMBX1.msg.corp.akamai.com> <8691BA706C9BAB52D64A8444@96B2F16665FF96BAE59E9B90> <00cd01cf3b05$4e5fa500$eb1eef00$@huitema.net> <531D60FC.2090604@cisco.com>
In-Reply-To: <531D60FC.2090604@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/uta/DfcpDP_Iz262PBUDdXL9wXrJTrg
Subject: [Uta] What's the right thing to do about Port 465?
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Mar 2014 07:02:19 -0000

On 03/10/2014 02:51 AM, Eliot Lear wrote:
> Routers running URD intercept all packets using port 465, regardless 
> of destination.

So is the right thing to do:

a)  Recommend port 465 anyway, but document the problem with these routers?

b)  Allocate and recommend a different port, even though that's going to 
increase configuration difficulties for the vast majority of legacy 
clients? (and assuming that new clients default to the new port, also 
complicate configuration of those clients with legacy servers?)

c) Allocate a different port to be the "official" port, recommend that 
servers support both ports when feasible (for the benefit of legacy 
clients), and recommend that new clients use SRV lookup to discover the 
submissions port?

d) something else?

Keith

v2.23.0 | Report a Bug | By Email