Re: [DNSOP] proposal: Covert in-band zone data

Mark Andrews <marka@isc.org> Fri, 02 August 2019 16:53 UTC

Return-Path: <marka@isc.org>
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 922D71206DA for <dnsop@ietfa.amsl.com>; Fri, 2 Aug 2019 09:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 6pJvilKPGy5q for <dnsop@ietfa.amsl.com>; Fri, 2 Aug 2019 09:53:53 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E7F91206D8 for <dnsop@ietf.org>; Fri, 2 Aug 2019 09:53:53 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 9C7113AB002; Fri, 2 Aug 2019 16:53:52 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 8004816008E; Fri, 2 Aug 2019 16:53:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 53BB216008D; Fri, 2 Aug 2019 16:53:52 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id aGTVy5n6rqbA; Fri, 2 Aug 2019 16:53:52 +0000 (UTC)
Received: from [172.30.42.67] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 7E272160055; Fri, 2 Aug 2019 16:53:51 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <alpine.BSF.2.21.9999.1907302049030.7062@bikeshed.isc.org>
Date: Sat, 03 Aug 2019 02:53:48 +1000
Cc: Paul Ebersman <list-dnsop@dragon.net>, dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FF1D7FBD-05E0-42C6-971A-579EC1A5BAD3@isc.org>
References: <20190706213024.GA56650@isc.org> <alpine.BSF.2.21.9999.1907221704030.7062@bikeshed.isc.org> <CAN6NTqymm6+OMet0sMZC0Ms5E_5mj_nwONk3fR19HwgWXYNB4Q@mail.gmail.com> <alpine.LRH.2.21.1907251332070.10708@bofh.nohats.ca> <20190725183051.33DA315BFD9D@fafnir.remote.dragon.net> <alpine.BSF.2.21.9999.1907301916050.7062@bikeshed.isc.org> <20190730203634.F2E1315E6F64@fafnir.remote.dragon.net> <alpine.BSF.2.21.9999.1907302049030.7062@bikeshed.isc.org>
To: Dan Mahoney <dmahoney@isc.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lE0xDaI09i6AgXKZFcs70FGp5Ss>
Subject: Re: [DNSOP] proposal: Covert in-band zone data
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 02 Aug 2019 16:53:55 -0000


> On 31 Jul 2019, at 6:51 am, Dan Mahoney <dmahoney@isc.org> wrote:
> 
> 
> 
> On Tue, 30 Jul 2019, Paul Ebersman wrote:
> 
>> dmahoney> I'd be fine with this data ONLY living on the master, but
>> dmahoney> having it survive things like named-compilezone or rndc
>> dmahoney> freeze/thaw, or the slew of DDNS updates that things like ACME
>> dmahoney> DNS-01 requires.
>> 
>> dmahoney> Effectively, this would be an internal-only DNS record that
>> dmahoney> had a database representation but NO defined wire-format, so
>> dmahoney> there'd be little chance of snooping over the wire (absent
>> dmahoney> some kind of memory leak in the DNS implementation).
>> 
>> Gotcha. So presumably also only on hidden master if that's the
>> architecture.
>> 
>> And transfer of data with these super-comments would be done by file
>> copy, not any DNS standard method?
>> 
> 
> Correct.  I do also envision a limited use-case for this feature where 
> BIND might also add a note indicating the source/time of a DDNS update.  
> But again, purely for humans, not for any action by the nameserver.
> 
> One possible format might be:
> 
> ;NOTE	foo.bar.	NOTE	"pauls workstation”

I would do it as '$NOTE <name> <text>' rather than as a comment which
gets mapped to “<name> 0 <class> NOTE <text>”.  This formalises the
construct and wont accidentally covert any existing comments that
start with “;NOTE “. 

> -Dan
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org