IETF Logo Mail Archive

Re: [DNSOP] A new version of mixfr

Frederico A C Neves <fneves@registro.br> Wed, 28 March 2018 14:52 UTC

Return-Path: <fneves@registro.br>
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 192EF1273B1 for <dnsop@ietfa.amsl.com>; Wed, 28 Mar 2018 07:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 alwYZ8VGscbf for <dnsop@ietfa.amsl.com>; Wed, 28 Mar 2018 07:52:46 -0700 (PDT)
Received: from clone.registro.br (clone.registro.br [IPv6:2001:12ff:0:2::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6405127978 for <dnsop@ietf.org>; Wed, 28 Mar 2018 07:52:46 -0700 (PDT)
Received: by clone.registro.br (Postfix, from userid 1000) id EDAF82A321B; Wed, 28 Mar 2018 11:52:43 -0300 (BRT)
Date: Wed, 28 Mar 2018 11:52:43 -0300
From: Frederico A C Neves <fneves@registro.br>
To: Pieter Lexis <pieter.lexis@powerdns.com>
Cc: dnsop@ietf.org
Message-ID: <20180328145243.GP62218@registro.br>
References: <d7c4fc25-9d4b-d934-bad3-61e7b8364ca2@pletterpet.nl> <20180328164353.2cb4cfb3@ananas.home.plexis.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20180328164353.2cb4cfb3@ananas.home.plexis.eu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/K4a3EhINqcHh0strBn2KeLPaGPc>
Subject: Re: [DNSOP] A new version of mixfr
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: Wed, 28 Mar 2018 14:52:54 -0000

On Wed, Mar 28, 2018 at 04:43:53PM +0200, Pieter Lexis wrote:
> Hi Matthijs,
> 
> On Wed, 28 Mar 2018 15:31:57 +0200
> Matthijs Mekking <matthijs@pletterpet.nl> wrote:
> 
> > It's been a while, but I have put up a new version of the MIXFR draft:
> > 
> >      https://tools.ietf.org/html/draft-mekking-mixfr-02
> 
> The draft speaks of an OPCode in the IANA section and of a meta
> RRType in the examples and Introduction section, which is it?
> 
> If it is an RRType, some words need to be added about the fact that
> current resolvers will pass through the MIXFR query and not reply with
> NOTIMPL. In a similar vein, unaware auths will respond with an NXDOMAIN
> or (more likely) a NODATA in that case.

Draft's samples use regular QUERY opcode and I suppose a new met
RRType MIXFR.

Does current auth server have any special processing for meta RRTypes?
If not your are correct regarding the unaware server and this needs to
be stated and handled by clients.

Fred

v2.23.0 | Report a Bug | By Email