IETF Logo Mail Archive

Re: [DNSOP] I-D Action: draft-muks-dnsop-dns-catalog-zones-04.txt

Mukund Sivaraman <muks@isc.org> Tue, 13 March 2018 06:25 UTC

Return-Path: <muks@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 E2647126DFF for <dnsop@ietfa.amsl.com>; Mon, 12 Mar 2018 23:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level:
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 6jSnDmylxtLu for <dnsop@ietfa.amsl.com>; Mon, 12 Mar 2018 23:25:49 -0700 (PDT)
Received: from mail.banu.com (mail.banu.com [46.4.129.225]) by ietfa.amsl.com (Postfix) with ESMTP id 85CDA126BF6 for <dnsop@ietf.org>; Mon, 12 Mar 2018 23:25:49 -0700 (PDT)
Received: from jurassic (unknown [49.203.219.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 4ED1B32C0738; Tue, 13 Mar 2018 06:25:46 +0000 (UTC)
Date: Tue, 13 Mar 2018 11:55:41 +0530
From: Mukund Sivaraman <muks@isc.org>
To: 神明達哉 <jinmei@wide.ad.jp>
Cc: dnsop <dnsop@ietf.org>, Ray Bellis <ray@bellis.me.uk>
Message-ID: <20180313062541.GA13587@jurassic>
References: <151990782328.10030.7325038774873512859@ietfa.amsl.com> <9ab0208f-29e3-10b0-e360-125257b2b238@bellis.me.uk> <CAJE_bqe-5-aD7yTkTSzu+fpSDEJw_TCYyL792cfqboDQXhmJ_g@mail.gmail.com> <20180310162615.GA28458@jurassic> <CAJE_bqfttqXqCnH6d8EKFVVsnoyRkdNW2ZmTX6Veqn3zF2oHLA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAJE_bqfttqXqCnH6d8EKFVVsnoyRkdNW2ZmTX6Veqn3zF2oHLA@mail.gmail.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/uxsoMBZN0cupqkIctCBT7NeGWlk>
Subject: Re: [DNSOP] I-D Action: draft-muks-dnsop-dns-catalog-zones-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 13 Mar 2018 06:25:51 -0000

Hi Jinmei

On Mon, Mar 12, 2018 at 10:59:11AM -0700, 神明達哉 wrote:
> > > this proposal.  (in that sense, I'm curious: is there other DNS
> > > developer than ISC that is interested in implementing this proposal?)
> >
> > So far: I was told that PowerDNS has implemented a plug-in/script that
> > provides support for catalog zones.
> 
> if there is actually an interest (or better, implementation or
> deployment cases) in having an interoperable way of synchronizing
> primary/secondary meta info, it may become more convincing.  I'd
> suggest you confirming the rumor and including the implementation
> status in the draft.

It was not a rumor. I heard this directly from one of the PowerDNS
developers.

https://github.com/PowerDNS/powercatz

		Mukund

v2.23.0 | Report a Bug | By Email