IETF Logo Mail Archive

[DNSOP] BULK RR as optional feature

"John Levine" <johnl@taugh.com> Tue, 28 March 2017 18:32 UTC

Return-Path: <johnl@taugh.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 5EA941297CC for <dnsop@ietfa.amsl.com>; Tue, 28 Mar 2017 11:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 y73ZRc-hYLmW for <dnsop@ietfa.amsl.com>; Tue, 28 Mar 2017 11:32:22 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8589B12944B for <dnsop@ietf.org>; Tue, 28 Mar 2017 11:32:19 -0700 (PDT)
Received: (qmail 15333 invoked from network); 28 Mar 2017 18:32:18 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 28 Mar 2017 18:32:18 -0000
Date: Tue, 28 Mar 2017 18:31:56 -0000
Message-ID: <20170328183156.2467.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Z07x7v5umlLM5GIJpWwCKxhL1TU>
Subject: [DNSOP] BULK RR as optional feature
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 28 Mar 2017 18:32:25 -0000

At yesterday's session, Tale confirmed that since BULK adds so much
new special purpose complexity to DNS servers, the plan is that
support for it will be optional.

An optional RRTYPE with extra semantics introduces some new
compatibility problems.  What happens if a server that doesn't support
BULK tries to load a local zone file with a BULK record.  Does it
reject the whole file, ignore the record, or something else?  What if
such a server receives BULK by AXFR?  By IXFR?  What if one shows up
in a cache from a buggy authoritative server?  In all of these cases,
the current RFC 3597 behavior will just return the BULK record which
seems wrong.

I continue to think that this kind of feature belongs in special
purpose DNS servers, not in the core DNS.

R's,
John

v2.23.0 | Report a Bug | By Email