IETF Logo Mail Archive

RE: Recommended ManageSieve TCP port 2000 is already allocated to Cisco SCCP

"Dan Wing" <dwing@cisco.com> Mon, 12 January 2009 19:39 UTC

Return-Path: <owner-ietf-mta-filters@mail.imc.org>
X-Original-To: ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com
Delivered-To: ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63C323A699E for <ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com>; Mon, 12 Jan 2009 11:39:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.577
X-Spam-Level:
X-Spam-Status: No, score=-6.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 x-PxaT9uKn4t for <ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com>; Mon, 12 Jan 2009 11:39:37 -0800 (PST)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 3E31C3A680D for <sieve-archive-Aet6aiqu@ietf.org>; Mon, 12 Jan 2009 11:39:36 -0800 (PST)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0CJX7RF036037 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Jan 2009 12:33:07 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n0CJX7Lv036036; Mon, 12 Jan 2009 12:33:07 -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 sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0CJWumb036005 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for <ietf-mta-filters@imc.org>; Mon, 12 Jan 2009 12:33:07 -0700 (MST) (envelope-from dwing@cisco.com)
X-IronPort-AV: E=Sophos;i="4.37,254,1231113600"; d="scan'208";a="121766635"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 12 Jan 2009 19:32:55 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0CJWtbx006810; Mon, 12 Jan 2009 11:32:55 -0800
Received: from dwingwxp01 ([10.32.240.194]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0CJWt1h014143; Mon, 12 Jan 2009 19:32:55 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Alexey Melnikov' <alexey.melnikov@isode.com>, ietf-mta-filters@imc.org
References: <29d3c4cb0901121122m55f1630fn3d3a375427b188b4@mail.gmail.com>
Subject: RE: Recommended ManageSieve TCP port 2000 is already allocated to Cisco SCCP
Date: Mon, 12 Jan 2009 11:32:55 -0800
Message-ID: <05a301c974ec$911d4c10$6157150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Acl06yAD8c3W28brRuWgHO3w4kbR4wAAQNAQ
In-Reply-To: <29d3c4cb0901121122m55f1630fn3d3a375427b188b4@mail.gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1406; t=1231788775; x=1232652775; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20Recommended=20ManageSieve=20TCP=20port= 202000=20is=20already=20allocated=20to=20Cisco=20SCCP |Sender:=20; bh=w1yP7ptslGJtVmkc+mw3yxl31NoaJDBZ8BUY5k0EflI=; b=sIWI1Ny+10OdOCJVJbuU4+dTULay3BMwJ3lxN2Yb+E9KKAO4OlwpE8R5Ro Wug2AUy1VdzjWi2OUs5QxJ1n4CUS8JqYCzXG3oRAdgGzM/6tXD5DntoBpciB A2JgZ1ILav6vYI6sVRSgZg7ommbbNF2IBzuqsPpnrc6dtaNXXFPsM=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
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>

 

> -----Original Message-----
> From: lunohod.baikonur@googlemail.com 
> [mailto:lunohod.baikonur@googlemail.com] On Behalf Of Alexey Melnikov
> Sent: Monday, January 12, 2009 11:23 AM
> To: Dan Wing; ietf-mta-filters@imc.org
> 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@icann.org> 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"?
> 
> Dan,
> 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 
2005, 
<http://newsroom.cisco.com/dlls/global/asiapac/news/2005/pr_09-23.html>,
most of which use SCCP.

-d

> To the WG: how widespread is usage of port 2000 for ManageSieve? Are
> people using any other port numbers?

v2.46.0 | Report a Bug | By Email | System Status