From each@isc.org  Thu Mar 10 01:58:47 2016
CC: 
MIME-Version: 1.0
In-Reply-To: <rt-4.2.8-31497-1457569114-723.41900-4-0@isc.org>
Content-Disposition: inline
X-RT-Interface: API
References: <20160309205325.GA9403@mycre.ws> <rt-4.2.8-30826-1457556811-128.41900-3-0@isc.org> <20160309214631.GA25960@isc.org> <rt-4.2.8-32120-1457561688-1493.41900-4-0@isc.org> <20160309224307.GB25960@isc.org> <rt-4.2.8-32120-1457563388-363.41900-4-0@isc.org> <20160310000405.86DF3442E3C3@rock.dv.isc.org> <rt-4.2.8-32120-1457568252-565.41900-4-0@isc.org> <20160310001829.A32C9442E5EA@rock.dv.isc.org> <rt-4.2.8-31497-1457569114-723.41900-4-0@isc.org>
Message-ID: <20160310015846.GA29285@isc.org>
content-type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) by bugs.isc.org (Postfix) with ESMTP id AF2E771B5A8 for <bind9-bugs@bugs.isc.org>; Thu, 10 Mar 2016 01:58:46 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id A820D216C1C; Thu, 10 Mar 2016 01:58:46 +0000 (UTC)
Delivered-To: bind9-bugs@bugs.isc.org
Subject: Re: [ISC-Bugs #41900] Unpresentable records cause AXFR failure?
User-Agent: Mutt/1.5.23 (2014-03-12)
Return-Path: <each@isc.org>
X-Original-To: bind9-bugs@bugs.isc.org
Date: Thu, 10 Mar 2016 01:58:46 +0000
To: "Mark Andrews via RT" <bind9-bugs@isc.org>
From: "Evan Hunt" <each@isc.org>
RT-Message-ID: <rt-4.2.8-31497-1457575127-1649.41900-0-0@isc.org>
Content-Length: 537

On Thu, Mar 10, 2016 at 12:18:34AM +0000, Mark Andrews via RT wrote:
> People also expect nameservers to reject garbage in records which is
> what named and dig are doing when they can.

See my previous statement about obvious correctness.  However, since
other implementors are likely to follow the RFC and allow nonalphanumeric
characters, and this will affect interoperability, I think Robert's
suggestion of allowing such records in wire-format but switching to
unknown-type format when rendering them to text is a pretty good one.