IETF Logo Mail Archive

Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems

Paul Vixie <vixie@isc.org> Thu, 05 March 2009 18:01 UTC

Return-Path: <vixie@vix.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4694A28C373 for <ietf@core3.amsl.com>; Thu, 5 Mar 2009 10:01:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level:
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599]
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 mG0Dtqt5RhYg for <ietf@core3.amsl.com>; Thu, 5 Mar 2009 10:01:22 -0800 (PST)
Received: from nsa.vix.com (nsa.vix.com [IPv6:2001:4f8:3:bb:230:48ff:fe5a:2f38]) by core3.amsl.com (Postfix) with ESMTP id 78FC128C2AF for <ietf@ietf.org>; Thu, 5 Mar 2009 10:01:22 -0800 (PST)
Received: from nsa.vix.com (localhost [127.0.0.1]) by nsa.vix.com (Postfix) with ESMTP id E6EF2A1022; Thu, 5 Mar 2009 18:01:50 +0000 (UTC) (envelope-from vixie@nsa.vix.com)
From: Paul Vixie <vixie@isc.org>
To: Tony Finch <dot@dotat.at>
Subject: Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
In-Reply-To: Your message of "Thu, 05 Mar 2009 13:34:37 GMT." <alpine.LSU.2.00.0903051333450.8701@hermes-2.csi.cam.ac.uk>
References: <alpine.LSU.2.00.0903041400220.8701@hermes-2.csi.cam.ac.uk> <20563.1236179832@nsa.vix.com> <e90946380903040805v15ad9e7dv92491667cd1f7656@mail.gmail.com> <36372.1236198273@nsa.vix.com> <e90946380903041229x2ce61e85p54ee9bed71acd431@mail.gmail.com> <41007.1236204089@nsa.vix.com> <alpine.LSU.2.00.0903051333450.8701@hermes-2.csi.cam.ac.uk>
X-Mailer: MH-E 8.1; nil; GNU Emacs 22.2.1
Date: Thu, 05 Mar 2009 18:01:50 +0000
Message-ID: <93444.1236276110@nsa.vix.com>
Sender: vixie@vix.com
X-Mailman-Approved-At: Fri, 06 Mar 2009 10:22:38 -0800
Cc: namedroppers@ops.ietf.org, Ondřej Surý <ondrej.sury@nic.cz>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Mar 2009 18:01:23 -0000

> > only in the case where the server is depending on rr ordering within
> > rrsets, which dns has never guaranteed and which many caches (both rdns
> > and stubs) randomize or reorder anyway, and where the server's
> > imputation of topology knows about every private interconnect that may
> > affect client performance, would RFC 3484 do harm.
> 
> No, it does harm when the servers are depending on RRsets being DISordered.

so the policy you're arguing for is that clients should always randomize?

v2.23.0 | Report a Bug | By Email