Re: [DNSOP] RFC 2136 pre-requisite checks before client authorization checks

Mukund Sivaraman <muks@mukund.org> Thu, 06 December 2018 18:41 UTC

Return-Path: <muks@mukund.org>
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 42233130F1A for <dnsop@ietfa.amsl.com>; Thu, 6 Dec 2018 10:41:59 -0800 (PST)
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 hDTB1SrJlirS for <dnsop@ietfa.amsl.com>; Thu, 6 Dec 2018 10:41:57 -0800 (PST)
Received: from mail.banu.com (mail.banu.com [46.4.129.225]) by ietfa.amsl.com (Postfix) with ESMTP id 09E811200D7 for <dnsop@ietf.org>; Thu, 6 Dec 2018 10:41:57 -0800 (PST)
Received: from jurassic.lan.banu.com (unknown [27.5.249.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 2880E32C00D5; Thu, 6 Dec 2018 18:41:54 +0000 (UTC)
Date: Fri, 7 Dec 2018 00:11:49 +0530
From: Mukund Sivaraman <muks@mukund.org>
To: p vixie <paul@redbarn.org>
Cc: dnsop@ietf.org
Message-ID: <20181206184149.GA6464@jurassic.lan.banu.com>
References: <20181206144504.GA17780@jurassic.lan.banu.com> <4559130.e78567a6.16784231f73@redbarn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4559130.e78567a6.16784231f73@redbarn.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZZHvfEhqW7QAsalAtOVJ54VV2FM>
Subject: Re: [DNSOP] RFC 2136 pre-requisite checks before client authorization checks
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, 06 Dec 2018 18:41:59 -0000

On Thu, Dec 06, 2018 at 04:29:13PM +0100, p vixie wrote:
> It's an error in the specification.

Thank you Paul. That clears it. I asked because BIND follows the RFC to
the letter, and an admin may see some log messages that are unexpected
for an address that's not in the update ACL.

		Mukund