IETF Logo Mail Archive

Re: [DNSOP] BCP on rrset ordering for round-robin? Also head's up on bind 9.12 bug (sorting rrsets by default)

Shumon Huque <shuque@gmail.com> Fri, 15 June 2018 18:28 UTC

Return-Path: <shuque@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCA4D130E39 for <dnsop@ietfa.amsl.com>; Fri, 15 Jun 2018 11:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MHT_xPjZBfPn for <dnsop@ietfa.amsl.com>; Fri, 15 Jun 2018 11:28:48 -0700 (PDT)
Received: from mail-yb0-x235.google.com (mail-yb0-x235.google.com [IPv6:2607:f8b0:4002:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D562F130DBE for <dnsop@ietf.org>; Fri, 15 Jun 2018 11:28:47 -0700 (PDT)
Received: by mail-yb0-x235.google.com with SMTP id u11-v6so3833155ybi.8 for <dnsop@ietf.org>; Fri, 15 Jun 2018 11:28:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zHnzOHO4vigyJPeOftmTNkXgeeNMyInLpP6eTaizhq4=; b=IuBKQj8pJpSSxmc3ReQlCIII4r11am6EXHyQzdzQkXhpoRR4mu732AJYMEHM+8umj/ Af1DbOshfMbHAuKXgE4DyBKmDHUNOiGHkASysEi8ht7VJtrLsw7ps7O6tgkqGYbeTCa2 mM9IED2Lgbg7niH9wWQXF9uSdjNOLgOXeEmMHRGga6oqvdT+0hIt7jSLb6R7j3MeTpzp 1ahxOg3XYbcf+eJz/vU4zN75GaN3Nl2BKGul3v7SM1CJWO4R66r19mjfY3R+tJOJgWpl rSclS2NcEbXfSPcc92cCgO+OP6iPBy0ocOPDCKEUz6UyHXsls4Gy0QUoGOOXLnkEJbgi lMZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zHnzOHO4vigyJPeOftmTNkXgeeNMyInLpP6eTaizhq4=; b=oGN6Y2/dAzqYzvSFlWUDBBIlfY72vO8YgIxvrqaYunHgdwXLCiBZj8I6hGylR3fsN5 e8v2M3WNJ2pPvuxYdJlDyp6j2NUj9BV8ONKZ49cH1a1+/8L1VUloFMsYR5msB6FT601s vjuu1rYfPXEnN5prkuhgAdVWqLv6Ayiu65ccS+J4JI0/cRGRQb48cGzwFz2nrrLjJknS 6yjfa2L9eoq9rqktkirw2YwUIeFWwX9K+/2MGqOOnuDC97MFD/dHneQKFIKcHLcX5dIy UBIdqw3LCESHfQfkKiTec+Wtr14cQeU1PfdEk5G7AD46b6DrMPo9PdDGiV5OH/5D40ts DAZw==
X-Gm-Message-State: APt69E0QNKsvwSmJ4FbZLQ2GkCbQQfslsoKw5Rg0JnFvtipHRtUkl7x3 JvOB0TCABsN/+SPPDF0JasWdReXrKrsdrFEGlWk=
X-Google-Smtp-Source: ADUXVKLdAefI4El6tpdDINA2vuXcWaFgkJPQH4z204GVfi4q092TGpTJjL3jvnJinB2q/MSuUABuXx9lG/jghbI19bk=
X-Received: by 2002:a25:848d:: with SMTP id v13-v6mr1182749ybk.404.1529087327028; Fri, 15 Jun 2018 11:28:47 -0700 (PDT)
MIME-Version: 1.0
References: <CAKC-DJimMOtNCSE95kRs6Dy3dC_mxB=8O2WVA7badp8GK2ci-Q@mail.gmail.com> <20180615171231.GF1126@mx4.yitter.info>
In-Reply-To: <20180615171231.GF1126@mx4.yitter.info>
From: Shumon Huque <shuque@gmail.com>
Date: Fri, 15 Jun 2018 14:28:35 -0400
Message-ID: <CAHPuVdWP=DVj52diWYTHKqHBET0hFyUWvACT-VpH20iKzed-ww@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f5496f056eb26261"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZOFJR4AjS0SwMTqENqm6TYIQk3s>
Subject: Re: [DNSOP] BCP on rrset ordering for round-robin? Also head's up on bind 9.12 bug (sorting rrsets by default)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2018 18:28:50 -0000

On Fri, Jun 15, 2018 at 1:13 PM Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> On Fri, Jun 15, 2018 at 11:45:19AM -0400, Erik Nygren wrote:
> > A number of folks have been bitten by a bug in bind 9..12 where it
> silently
> > changes the default sorting of rrsets to always be sorted (even if the
> > authoritative response wasn't sorted).
>
> I believe that RRsets are unordered sets by definition.  So I supect
> that if people are relying on the order in which they come off the
> wire, they're making a mistake.
>

This is all true.

Yet, large numbers of application services on the Internet already rely on
the assumption that address RRsets are returned from resolvers in a
shuffled or randomized order for load balancing reasons. So changing this
behavior will elicit many fierce complaints (I already observed it).

-- 
Shumon.

v2.23.0 | Report a Bug | By Email