[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Recommended ManageSieve TCP port 2000 is already allocated to Cisco SCCP
> -----Original Message-----
> From: lunohod.baikonur@xxxxxxxxxxxxxx
> [mailto:lunohod.baikonur@xxxxxxxxxxxxxx] On Behalf Of Alexey Melnikov
> Sent: Monday, January 12, 2009 11:23 AM
> To: Dan Wing; ietf-mta-filters@xxxxxxx
> Subject: Recommended ManageSieve TCP port 2000 is already
> allocated to Cisco SCCP
> On Mon, Jan 5, 2009 at 11:21 PM, Amanda Baber via RT
> <drafts-lastcall@xxxxxxxxx> wrote:
> > IESG:
> > IANA has questions about draft-ietf-sieve-managesieve-05.txt:
> > - This document requests the allocation of a TCP port that has
> > already been registered (2000, Cisco SCCP). Should the existing
> > registration be changed from "Cisco SCCP" to "ManageSieve"?
> ManageSieve was invented about 10 years ago and some implementations
> used port 2000 (unfortunately without registering it with IANA). How
> widely is Cisco SCCP implemented and would be changing the IANA
> allocated port number an option for you?
SCCP is our proprietary signaling protocol between our VoIP phones
and Unified Communication Manager (formerly called Call Manager),
with somewhere above 6 million IP phones in the field (as of
most of which use SCCP.
> To the WG: how widespread is usage of port 2000 for ManageSieve? Are
> people using any other port numbers?