Re: [Sip] draft-jennings-sip-dtls

Dean Willis <dean.willis@softarmor.com> Fri, 18 February 2005 01:09 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05053 for <sip-web-archive@ietf.org>; Thu, 17 Feb 2005 20:09:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1x07-0007VS-Bq for sip-web-archive@ietf.org; Thu, 17 Feb 2005 20:32:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1wTO-0005Dp-PK; Thu, 17 Feb 2005 19:58:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1wDN-0006r0-TY for sip@megatron.ietf.org; Thu, 17 Feb 2005 19:41:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01762 for <sip@ietf.org>; Thu, 17 Feb 2005 19:41:47 -0500 (EST)
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1wYv-0006VS-K0 for sip@ietf.org; Thu, 17 Feb 2005 20:04:06 -0500
Received: from [64.101.149.215] ([64.101.149.215]) (authenticated bits=0) by nylon.softarmor.com (8.13.1/8.12.11) with ESMTP id j1I0gabT021351 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Thu, 17 Feb 2005 18:42:37 -0600
In-Reply-To: <B52FDDEC7CBE9D40B36FE900C9AD78B422A65F@merenge.intern.snom.de>
References: <B52FDDEC7CBE9D40B36FE900C9AD78B422A65F@merenge.intern.snom.de>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Message-Id: <07595f53ac0eb03c7d5406a3207f947c@softarmor.com>
Content-Transfer-Encoding: quoted-printable
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-jennings-sip-dtls
Date: Thu, 17 Feb 2005 18:40:57 -0600
To: Christian Stredicke <Christian.Stredicke@snom.de>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: quoted-printable
Cc: Cullen Jennings <fluffy@cisco.com>, sip@ietf.org, Francois Audet <audet@nortel.com>, Tolga Asveren <asveren@ulticom.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable

On Feb 17, 2005, at 2:00 PM, Christian Stredicke wrote:

> 16 bit set an upper limit of 64 K connections. My feeling is that TCP 
> was not designed for this purpose.
>  
> Sorry for being so pragmatic. Maybe someone can show me an 
> implementation that can handle 100 K connections on one IP address.
>  

Actually, we fairly thoroughly flogged this topic a few years ago.

The net-net was that the 64k limit is a kernel limit, induced by the 
use of 16-bit indices in file descriptor tables and other places.

Some kernels (or embedded IP limitations that are not kernel specific) 
don't seem to have this limitation. I'm told by some of the bootserver 
engineers I talk with occasionally that they can get several hundred 
thousand TCP connections on Solaris 9, at a cost of about 4kB per 
connection. Of course, this eats a boatload of RAM.

But DTLS does have some nice properties, and its ability to scale 
larger on a larger set of OS platforms is quite possibly one of them.

--
Dean

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip