Re: Port 2000

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 12 May 2006 13:28 UTC

Message-ID: <44648D6E.2050606@isode.com>
Date: Fri, 12 May 2006 14:28:14 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
CC: ietf-mta-filters@imc.org
Subject: Re: Port 2000
References: <Lkq+11z4ZCHoHy9ZdiNTKg.md5@libertango.oryx.com>
In-Reply-To: <Lkq+11z4ZCHoHy9ZdiNTKg.md5@libertango.oryx.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk

Arnt Gulbrandsen wrote:

> 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 assume you are talking about Manage Sieve protocol.

> 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?

Either 1 or 2 would work for me.

Re: Port 2000 Alexey Melnikov
Port 2000 Arnt Gulbrandsen
Re: Port 2000 Tony Hansen