IETF Logo Mail Archive

Re: [DNSOP] A new version of mixfr

Ray Bellis <ray@bellis.me.uk> Wed, 28 March 2018 15:50 UTC

Return-Path: <ray@bellis.me.uk>
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 6A3D2127369 for <dnsop@ietfa.amsl.com>; Wed, 28 Mar 2018 08:50:35 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 dPA6ksHQBXK7 for <dnsop@ietfa.amsl.com>; Wed, 28 Mar 2018 08:50:33 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 408E9120047 for <dnsop@ietf.org>; Wed, 28 Mar 2018 08:50:33 -0700 (PDT)
Received: from 88-212-170-147.customer.gigaclear.net ([88.212.170.147]:60905 helo=rays-mbp.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1f1DLJ-0006xC-Kl (Exim 4.72) for dnsop@ietf.org (return-path <ray@bellis.me.uk>); Wed, 28 Mar 2018 16:50:29 +0100
To: dnsop@ietf.org
References: <d7c4fc25-9d4b-d934-bad3-61e7b8364ca2@pletterpet.nl> <20180328164353.2cb4cfb3@ananas.home.plexis.eu>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <0f1bde63-b46b-38e8-af96-2682ee493a79@bellis.me.uk>
Date: Wed, 28 Mar 2018 16:50:31 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; 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"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-3bA4pKHQM2e0c7kIZpLGzteP6s>
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:50:35 -0000

On 28/03/2018 15:43, Pieter Lexis wrote:

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

A Meta RRType should never be passed through resolvers - they're only
used on the wire between client and server, and not end-to-end.

Ray

v2.23.0 | Report a Bug | By Email