Port 2000

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Fri, 12 May 2006 13:15 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k4CDFOmA082261; Fri, 12 May 2006 06:15:25 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k4CDFOlc082260; Fri, 12 May 2006 06:15:24 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k4CDFNWO082252 for <ietf-mta-filters@imc.org>; Fri, 12 May 2006 06:15:24 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 3C4E54AC3A; Fri, 12 May 2006 15:15:22 +0200 (CEST)
Message-Id: <Lkq+11z4ZCHoHy9ZdiNTKg.md5@libertango.oryx.com>
Date: Fri, 12 May 2006 15:19:10 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Port 2000
Content-Type: text/plain; format="flowed"
MIME-Version: 1.0
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mta-filters/mail-archive/>
List-ID: <ietf-mta-filters.imc.org>
List-Unsubscribe: <mailto:ietf-mta-filters-request@imc.org?body=unsubscribe>

IANA registration is pending, or so the latest draft says. Well, what'll 
the draft say if IANA won't hand out port 2000?

I see three possibilities:

1. Advise servers to listen to a standard port, and "MAY also listen to 
2000 for legacy compatibility". Advise servers to try the standard 
port, then 2000?

2. Advise servers to listen to a standard port, site admins to add a SRV 
record, and client to look for the SRV record and fall back to port 
2000 if there is none?

3. Mention only the IANA-assigned port, not 2000, and pretend to ignore 
that all servers listen to port 2000 too, and every client falls back 
to 2000?

Arnt