Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communication-00.txt
Paul Vixie <vixie@vix.com> Wed, 20 December 2006 17:42 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx5Sp-0006tM-Sg; Wed, 20 Dec 2006 12:42:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx5QF-0004zs-Tz for dnsop@ietf.org; Wed, 20 Dec 2006 12:40:07 -0500
Received: from sa.vix.com ([2001:4f8:3:bb::1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx5Q1-0000eB-2h for dnsop@ietf.org; Wed, 20 Dec 2006 12:40:07 -0500
Received: from sa.vix.com (localhost [127.0.0.1]) by sa.vix.com (Postfix) with ESMTP id A1E9E11427 for <dnsop@ietf.org>; Wed, 20 Dec 2006 17:39:45 +0000 (UTC) (envelope-from vixie@sa.vix.com)
To: dnsop@ietf.org
Subject: Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communication-00.txt
References: <C8E51183-6B1E-4738-B370-067EEFCD3E22@icann.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
Date: Wed, 20 Dec 2006 17:39:45 +0000
Message-ID: <56320.1166636385@sa.vix.com>
From: Paul Vixie <vixie@vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 83f2f9cfeef8b2109d058d696530e87e
X-Mailman-Approved-At: Wed, 20 Dec 2006 12:42:46 -0500
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
Errors-To: dnsop-bounces@ietf.org
> > Consider the various approaches used by ISC and others to populate a > > zone with data that can be extracted by a nameserver and used to > > configure itself, for example. No protocol there -- more like a zone > > schema. > > Right. I think the idea (and I'm sure Stephane will correct me if I'm > wrong) is to come up with a standard way to do this sort of thing. X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1 my read on this document is that it describes something more expansive than the ISC tool mentioned above. (see attached PDF.) it's more like "junoscript or netconf for DNS authorities", and a standard like it has been long needed. as to where it belongs, if it's going to be in-band (affecting the wire protocol) then it should be in DNSEXT/namedroppers, but if it's going to be a new protocol (like the regnauld doc describes) or just new ways to use the existing protocol (like the attached PDF describes) then it belongs in DNSOP. the attached paper was published last year but i've not got around to writing an I-D for it nor releasing the software that implements it. i have shared it privately with a number of folks, and it's in fairly wide use among the folks ISC trades slave nameservice with. my big worries are that it's either too BIND-specific or that it'll spawn a dozen competing non-interoperable schemas (like my QUOTE SITE INDEX hack did in wu-ftpd). so if you hate this, plz don't hack up your own -- instead, write an I-D or help me write an I-D, and let the community drive some coherence into this functionality.)
> > Consider the various approaches used by ISC and others to populate a > > zone with data that can be extracted by a nameserver and used to > > configure itself, for example. No protocol there -- more like a zone > > schema. > > Right. I think the idea (and I'm sure Stephane will correct me if I'm > wrong) is to come up with a standard way to do this sort of thing. X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1 my read on this document is that it describes something more expansive than the ISC tool mentioned above. (see attached PDF.) it's more like "junoscript or netconf for DNS authorities", and a standard like it has been long needed. as to where it belongs, if it's going to be in-band (affecting the wire protocol) then it should be in DNSEXT/namedroppers, but if it's going to be a new protocol (like the regnauld doc describes) or just new ways to use the existing protocol (like the attached PDF describes) then it belongs in DNSOP. the attached paper was published last year but i've not got around to writing an I-D for it nor releasing the software that implements it. i have shared it privately with a number of folks, and it's in fairly wide use among the folks ISC trades slave nameservice with. my big worries are that it's either too BIND-specific or that it'll spawn a dozen competing non-interoperable schemas (like my QUOTE SITE INDEX hack did in wu-ftpd). so if you hate this, plz don't hack up your own -- instead, write an I-D or help me write an I-D, and let the community drive some coherence into this functionality.)
-- Paul Vixie
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www1.ietf.org/mailman/listinfo/dnsop
- [DNSOP] I-D ACTION:draft-regnauld-ns-communicatio… Stephane Bortzmeyer
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… bert hubert
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… Roy Arends
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… Joe Abley
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… Måns Nilsson
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… Edward Lewis
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… David Conrad
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… Joe Abley
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… David Conrad
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… Paul Vixie
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… Phil Regnauld
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… Phil Regnauld
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… Paul Vixie
- [DNSOP] Re: I-D ACTION:draft-regnauld-ns-communic… Stephane Bortzmeyer
- [DNSOP] Scope of the future NCP (Was: I-D ACTION:… Stephane Bortzmeyer
- [DNSOP] Aim of the project: a standard way to man… Stephane Bortzmeyer
- Re: [DNSOP] Re: I-D ACTION:draft-regnauld-ns-comm… Roy Arends
- [DNSOP] Metazones in the context of the future NC… Stephane Bortzmeyer
- [DNSOP] View or not views (Was: I-D ACTION:draft-… Stephane Bortzmeyer
- Re: [DNSOP] I-D ACTION:draft-regnauld-ns-communic… Niall O'Reilly
- [DNSOP] Re: Scope of the future NCP (Was: I-D ACT… Edward Lewis
- [DNSOP] Re: I-D ACTION:draft-regnauld-ns-communic… Edward Lewis
- Re: [DNSOP] View or not views (Was: I-D ACTION:dr… David Conrad
- Re: [DNSOP] Re: I-D ACTION:draft-regnauld-ns-comm… Peter Koch
- Re: [DNSOP] Scope of the future NCP (Was: I-D ACT… Robert Story