From each@isc.org  Wed Mar  9 22:43:07 2016
CC: 
MIME-Version: 1.0
In-Reply-To: <rt-4.2.8-32120-1457561688-1493.41900-4-0@isc.org>
Content-Disposition: inline
X-RT-Interface: API
References: <RT-Ticket-41900@isc.org> <20160309205325.GA9403@mycre.ws> <rt-4.2.8-30826-1457556811-128.41900-3-0@isc.org> <20160309214631.GA25960@isc.org> <rt-4.2.8-31497-1457559992-910.41900-5-0@isc.org> <20160309221444.GA13890@mycre.ws> <rt-4.2.8-32120-1457561688-1493.41900-4-0@isc.org>
Message-ID: <20160309224307.GB25960@isc.org>
content-type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) by bugs.isc.org (Postfix) with ESMTP id 7569871B5A8 for <bind9-bugs@bugs.isc.org>; Wed,  9 Mar 2016 22:43:07 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id 5F923216C1E; Wed,  9 Mar 2016 22:43:07 +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: Wed, 9 Mar 2016 22:43:07 +0000
To: "Robert Edmonds via RT" <bind9-bugs@isc.org>
From: "Evan Hunt" <each@isc.org>
RT-Message-ID: <rt-4.2.8-32120-1457563388-1239.41900-0-0@isc.org>
Content-Length: 403

On Wed, Mar 09, 2016 at 10:14:48PM +0000, Robert Edmonds via RT wrote:
> In the case where you have to render an unpresentable CAA record (for
> instance because you might be writing a text master file format zone to
> disk), couldn't you just fall back on RFC 3597 generic presentation
> format for the record data? E.g.,
> 
>     caa.example. IN CAA \# 03 00 01 20

Very smart suggestion, thank you.