[Asrg] DNS over SCTP (was: Re: DNS-based Email Sender Authentication Mechanisms: a Critical Review

Alessandro Vesely <vesely@tana.it> Thu, 28 May 2009 13:02 UTC

Return-Path: <vesely@tana.it>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 058BE3A68F3 for <asrg@core3.amsl.com>; Thu, 28 May 2009 06:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.27
X-Spam-Level:
X-Spam-Status: No, score=0.27 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_05=-1.11, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 TRovlJDsat-H for <asrg@core3.amsl.com>; Thu, 28 May 2009 06:02:49 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 1E5303A68F5 for <asrg@irtf.org>; Thu, 28 May 2009 06:02:48 -0700 (PDT)
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 ale@tana.it, TLS: TLS1.0, 256bits, RSA_AES_256_CBC_SHA1) by wmail.tana.it with esmtp; Thu, 28 May 2009 15:04:14 +0200 id 00000000005DC030.000000004A1E8BCE.000015D3
Message-ID: <4A1E8BD3.8000103@tana.it>
Date: Thu, 28 May 2009 15:04:19 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <003d01c9dd01$bf3531d0$800c6f0a@china.huawei.com> <4A1A45BA.5030704@swin.edu.au> <3be421270905250718y5d62f6d5odb6f2bebecf418d0@mail.gmail.com> <6684E747-55CB-4BB3-B838-9F4FE906AFE7@mail-abuse.org> <200905251603.MAA16221@Sparkle.Rodents-Montreal.ORG> <CCE0A3E1-4BCB-460C-AEA0-6548BB4AE8FE@mail-abuse.org> <4A1D64C9.5060505@tana.it> <47BC2197-472E-4615-97D2-F7E42B8F3B7D@mail-abuse.org>
In-Reply-To: <47BC2197-472E-4615-97D2-F7E42B8F3B7D@mail-abuse.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: [Asrg] DNS over SCTP (was: Re: DNS-based Email Sender Authentication Mechanisms: a Critical Review
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2009 13:02:55 -0000

Douglas Otis wrote:
>> Just using TCP would prevent most of the DNS poisoning attacks that 
>> Amir's paper reports.
> 
> TCP is prone to DDoS attack.  As such, TCP is seldom used with DNS.

I thought TCP was the default when the UDP message size is not enough. 
That's, AFAIK, the only advantage of TCP over SCTP: it's already in 
place and ready. (Yes, one needs to run firewalls and all that stuff.)

> A single SCTP connection can support thousands of simultaneous streams,

I agree SCTP is better, and it's been around for nearly a decade now. 
Yet, for those who miss it, good old TCP allows, say, a client to hold 
a couple of connections to its favorite resolver in order to avoid 
many of the threats illustrated by Kaminsky...

> There is also OS support for UDP 
> tunneling of SCTP when supporting legacy NATs and firewalls.  Until 
> there is an significant incentive to make DNS more robust, use of SCTP 
> is likely to remain just a good and under appreciated option.

It seems that DNS over SCTP would solve 90% of the problems with 10% 
of the efforts and resources required to implement DNSSEC. However, I 
hear more often about the latter than the former. How come?