Re: increasing DNS message entropy, a solution for NATs

Ben Laurie <ben@links.org> Thu, 31 July 2008 08:56 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 067E03A6855; Thu, 31 Jul 2008 01:56:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level:
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
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 fjJG80uSIzFv; Thu, 31 Jul 2008 01:56:43 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id BD7F33A6804; Thu, 31 Jul 2008 01:56:42 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1KOTsT-000GAR-AO for namedroppers-data@psg.com; Thu, 31 Jul 2008 08:51:17 +0000
Received: from [217.155.92.109] (helo=mail.links.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <ben@links.org>) id 1KOTsP-000G9L-Cp for namedroppers@ops.ietf.org; Thu, 31 Jul 2008 08:51:15 +0000
Received: from [193.133.15.218] (localhost [127.0.0.1]) by mail.links.org (Postfix) with ESMTP id 9C63A33C1E; Thu, 31 Jul 2008 09:51:09 +0100 (BST)
Message-ID: <48917CFE.1030206@links.org>
Date: Thu, 31 Jul 2008 09:51:10 +0100
From: Ben Laurie <ben@links.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.4.0
MIME-Version: 1.0
To: Duane <duane@e164.org>
CC: namedroppers@ops.ietf.org
Subject: Re: increasing DNS message entropy, a solution for NATs
References: <OF6B63EC19.5E0A6D58-ON8025748D.003A54A9-C125748D.003E1133@nominet.org.uk> <488517CE.6060404@necom830.hpcl.titech.ac.jp> <4891381B.1070400@links.org> <48913FA1.5010501@necom830.hpcl.titech.ac.jp> <B9A58880FC2AE5B486F366FF@Ximines.local> <48916FCA.3040402@e164.org> <489175AA.2050403@links.org> <489176FA.90406@e164.org> <489178A3.404@links.org> <489179E8.3070106@e164.org> <48917AD3.5080200@links.org> <48917B59.6090209@e164.org>
In-Reply-To: <48917B59.6090209@e164.org>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>

Duane wrote:
> Ben Laurie wrote:
> 
>>> Beats me, everyone seems rather concerned over an issue that no one
>>> could fix if they wanted to in any case. That isn't to say that someone
>>> shouldn't be doing in terms of getting NAT better for in future, but
>>> existing deployments by and large are never going to be upgraded until
>>> new hardware is purchased.
>> Whether that's true or not, isn't it a good idea that the new hardware
>> actually does the right thing?
> 
> I already suggested that, but apparently NAT needs to be fixed as much
> as DNS in new hardware.

Exactly.

-- 
http://www.apache-ssl.org/ben.html           http://www.links.org/

"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>