Re: [DNSOP] A new version of mixfr

Matthijs Mekking <matthijs@pletterpet.nl> Wed, 28 March 2018 15:23 UTC

Return-Path: <matthijs@pletterpet.nl>
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 76E2F1273B1 for <dnsop@ietfa.amsl.com>; Wed, 28 Mar 2018 08:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 mWJ8J31r8wVu for <dnsop@ietfa.amsl.com>; Wed, 28 Mar 2018 08:23:15 -0700 (PDT)
Received: from lb1-smtp-cloud8.xs4all.net (lb1-smtp-cloud8.xs4all.net [194.109.24.21]) (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 5821F127369 for <dnsop@ietf.org>; Wed, 28 Mar 2018 08:23:15 -0700 (PDT)
Received: from [IPv6:2001:981:19be:1:a104:4f71:de86:2e0] ([IPv6:2001:981:19be:1:a104:4f71:de86:2e0]) by smtp-cloud8.xs4all.net with ESMTPSA id 1CuufMTeM4EsM1CuvfI4Cr; Wed, 28 Mar 2018 17:23:13 +0200
To: dnsop@ietf.org
References: <d7c4fc25-9d4b-d934-bad3-61e7b8364ca2@pletterpet.nl> <20180328164353.2cb4cfb3@ananas.home.plexis.eu>
From: Matthijs Mekking <matthijs@pletterpet.nl>
Message-ID: <6e3d929f-b5a4-7e7a-4221-dfbc7e3ff5d0@pletterpet.nl>
Date: Wed, 28 Mar 2018 17:23:12 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <20180328164353.2cb4cfb3@ananas.home.plexis.eu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfBgXFp1/AFe0dkdvbA2f1Bi/TonJ6ziFwksuQmi+6nYC3Bjlz8GjcUc/S+G6Rlb9ahUP+LFOnowj9OLK4BZkg1YGbNCx1vMVRfbmI4ChF2cLeyIwrBtq gmC1zuIlEffezVB9l7SZZ/1QbteHwAQOXVRWUWiPebH58FAq7T9RAkpQX/k8oGoRXTkyf77V/I07o0cnaMuuAX6f0bDTmadA7Qgi+r2BI7mwK9m8MmKHskph hw3m1wDNYatDSlktTg6YR0+VsBOZ2FQMs8oGgPaF9dg=
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/pmOs9fRsaBW4OxZU_b0X1r07Hjs>
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 15:23:17 -0000

Pieter,

On 03/28/2018 04:43 PM, 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?

Probably copy paste error from a different draft. MIXFR is a new query 
type, so that's an error in the IANA section. The intention is to 
request a new RRtype. Thanks for catching this.


> 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.

IXFR solved this by saying "If the query type is not recognized by the 
server, an AXFR (preceded by a UDP SOA query) should be tried, ensuring 
backward compatibility." Probably MIXFR can say something similar.

A resolver should behave similar for MIXFR as it does for AXFR and IXFR. 
I can't find words about this in RFC 1995 or RFC 5936, so I am not sure 
if this document should add something about that.


Groeten,

Matthijs

> 
> Best regards,
> 
> Pieter
>