IETF Logo Mail Archive

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

Paul Ebersman <list-dnsop@dragon.net> Tue, 30 July 2019 20:36 UTC

Return-Path: <list-dnsop@dragon.net>
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 5CA0712027E for <dnsop@ietfa.amsl.com>; Tue, 30 Jul 2019 13:36:51 -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 GqqZ20ngVXcC for <dnsop@ietfa.amsl.com>; Tue, 30 Jul 2019 13:36:49 -0700 (PDT)
Received: from mail.dragon.net (mail.dragon.net [IPv6:2001:4f8:3:36::235]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 632A012010F for <dnsop@ietf.org>; Tue, 30 Jul 2019 13:36:35 -0700 (PDT)
Received: from fafnir.remote.dragon.net (localhost [IPv6:::1]) by mail.dragon.net (Postfix) with ESMTP id 375D937402E6; Tue, 30 Jul 2019 13:36:35 -0700 (PDT)
Received: by fafnir.remote.dragon.net (Postfix, from userid 501) id F2E1315E6F64; Tue, 30 Jul 2019 14:36:34 -0600 (MDT)
Received: from fafnir.local (localhost [127.0.0.1]) by fafnir.remote.dragon.net (Postfix) with ESMTP id EE26C15E6F63; Tue, 30 Jul 2019 14:36:34 -0600 (MDT)
From: Paul Ebersman <list-dnsop@dragon.net>
To: Dan Mahoney <dmahoney@isc.org>
cc: dnsop@ietf.org
In-reply-to: <alpine.BSF.2.21.9999.1907301916050.7062@bikeshed.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>
Comments: In-reply-to Dan Mahoney <dmahoney@isc.org> message dated "Tue, 30 Jul 2019 19:39:00 -0000."
X-Mailer: MH-E 7.4.2; nmh 1.7.1; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <63155.1564518994.1@fafnir.local>
Date: Tue, 30 Jul 2019 14:36:34 -0600
Message-Id: <20190730203634.F2E1315E6F64@fafnir.remote.dragon.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/b1c1zKHC6WtcN6Rusw50X6aUiA8>
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: Tue, 30 Jul 2019 20:37:11 -0000

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?

v2.23.0 | Report a Bug | By Email