IETF Logo Mail Archive

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

Paul Ebersman <list-dnsop@dragon.net> Thu, 25 July 2019 18:30 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 1DB48120198 for <dnsop@ietfa.amsl.com>; Thu, 25 Jul 2019 11:30:17 -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 gpIifs1VOlRH for <dnsop@ietfa.amsl.com>; Thu, 25 Jul 2019 11:30: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 6B3B2120191 for <dnsop@ietf.org>; Thu, 25 Jul 2019 11:30:15 -0700 (PDT)
Received: from fafnir.remote.dragon.net (localhost [IPv6:::1]) by mail.dragon.net (Postfix) with ESMTP id 2DE4E37402BC for <dnsop@ietf.org>; Thu, 25 Jul 2019 11:30:15 -0700 (PDT)
Received: by fafnir.remote.dragon.net (Postfix, from userid 501) id 33DA315BFD9D; Thu, 25 Jul 2019 14:30:51 -0400 (EDT)
Received: from dhcp-9bbb.meeting.ietf.org (localhost [127.0.0.1]) by fafnir.remote.dragon.net (Postfix) with ESMTP id 31B6315BFD9C for <dnsop@ietf.org>; Thu, 25 Jul 2019 14:30:51 -0400 (EDT)
From: Paul Ebersman <list-dnsop@dragon.net>
To: dnsop@ietf.org
In-reply-to: <alpine.LRH.2.21.1907251332070.10708@bofh.nohats.ca>
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>
Comments: In-reply-to Paul Wouters <paul@nohats.ca> message dated "Thu, 25 Jul 2019 13:32:32 -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: <69246.1564079451.1@dhcp-9bbb.meeting.ietf.org>
Date: Thu, 25 Jul 2019 14:30:51 -0400
Message-Id: <20190725183051.33DA315BFD9D@fafnir.remote.dragon.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/cjbQAikxaJAalf3GjpohHCrdBSU>
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: Thu, 25 Jul 2019 18:30:17 -0000

olafur> My suggestion is to take a step back and say we have outgrown
olafur> AXFR and we need better mechanism to sync various servers.

olafur> Lets start work on a new "SYNC Name servers" protocol that can
olafur> meet modern requirements

paulw> +1

+1.

I think we're allowed to replace something after 20+ years ;)

Things that might go in:

  - AXFR/IXFR/*XFR
  - zone meta data (create/modify/delete/digital-sigs)
  - "covert" data

My only hesitation is we seem to slow logarithmically as we increase
scope but this sure seems like the right direction.

v2.23.0 | Report a Bug | By Email