IETF Logo Mail Archive

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

Paul Ebersman <list-dnsop@dragon.net> Tue, 30 July 2019 20:33 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 9E656120089 for <dnsop@ietfa.amsl.com>; Tue, 30 Jul 2019 13:33:16 -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 AlFLTsUw6RBK for <dnsop@ietfa.amsl.com>; Tue, 30 Jul 2019 13:33:15 -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 2472A120024 for <dnsop@ietf.org>; Tue, 30 Jul 2019 13:33:15 -0700 (PDT)
Received: from fafnir.remote.dragon.net (localhost [IPv6:::1]) by mail.dragon.net (Postfix) with ESMTP id EB73237402E6; Tue, 30 Jul 2019 13:33:14 -0700 (PDT)
Received: by fafnir.remote.dragon.net (Postfix, from userid 501) id C067B15E6EDC; Tue, 30 Jul 2019 14:33:14 -0600 (MDT)
Received: from fafnir.local (localhost [127.0.0.1]) by fafnir.remote.dragon.net (Postfix) with ESMTP id BC0C215E6EDB; Tue, 30 Jul 2019 14:33:14 -0600 (MDT)
From: Paul Ebersman <list-dnsop@dragon.net>
To: Bob Harold <rharolde@umich.edu>
cc: IETF DNSOP WG <dnsop@ietf.org>
In-reply-to: <CA+nkc8DaTVxcm_7tR1EELPkP=4XKZGGa4uoSFqUcY8xKRe9iSg@mail.gmail.com>
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> <20190730200859.A424215E6AD4@fafnir.remote.dragon.net> <alpine.BSF.2.21.9999.1907302009500.7062@bikeshed.isc.org> <20190730201628.1496015E6BFA@fafnir.remote.dragon.net> <CA+nkc8DaTVxcm_7tR1EELPkP=4XKZGGa4uoSFqUcY8xKRe9iSg@mail.gmail.com>
Comments: In-reply-to Bob Harold <rharolde@umich.edu> message dated "Tue, 30 Jul 2019 16:24:04 -0400."
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: <63066.1564518794.1@fafnir.local>
Date: Tue, 30 Jul 2019 14:33:14 -0600
Message-Id: <20190730203314.C067B15E6EDC@fafnir.remote.dragon.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PQNjxF_iF-sk9KI9P9TJ6p73QzY>
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:33:17 -0000

rharolde> If you are looking at putting it outside the zone, it occurs
rharolde> to me that any of the IPAM solutions have a database where you
rharolde> can attach information to records, zones, IP addresses,
rharolde> etc. Even Active Directory can probably do that.

"Buy a commercial IPAM" isn't an open standards based solution. Nor are
any of those extra compatible between different implementations.

Not being send in the AXFR or stored as zone data doesn't mean separate
database either. That's assuming an implementation before we even have a
protocol design/extension.

v2.23.0 | Report a Bug | By Email