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

p vixie <paul@redbarn.org> Thu, 06 December 2018 15:29 UTC

Return-Path: <paul@redbarn.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 7511012896A for <dnsop@ietfa.amsl.com>; Thu, 6 Dec 2018 07:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 WHhpShgvSDS7 for <dnsop@ietfa.amsl.com>; Thu, 6 Dec 2018 07:29:30 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F098128A6E for <dnsop@ietf.org>; Thu, 6 Dec 2018 07:29:28 -0800 (PST)
Received: from [192.168.44.209] (unknown [5.33.2.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 6CBDA892C6; Thu, 6 Dec 2018 15:29:24 +0000 (UTC)
Date: Thu, 6 Dec 2018 16:29:13 +0100 (GMT+01:00)
From: p vixie <paul@redbarn.org>
To: Mukund Sivaraman <muks@mukund.org>, dnsop@ietf.org
Message-ID: <4559130.e78567a6.16784231f73@redbarn.org>
In-Reply-To: <20181206144504.GA17780@jurassic.lan.banu.com>
References: <20181206144504.GA17780@jurassic.lan.banu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Mailer: R2Mail2
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/pKUT2dCFM6pT_4zqNA3yViKfFUY>
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 15:29:33 -0000

It's an error in the specification.

----- Original Message -----
From: Mukund Sivaraman <muks@mukund.org>
Sent: 2018-12-06 - 15:45
To: dnsop@ietf.org
Subject: [DNSOP] RFC 2136 pre-requisite checks before client authorization checks

> Hi all
> 
> Does anyone know why RFC 2136 sequences pre-requisite checks (section
> 3.2) to be performed before client permission checks (section 3.3)?  It
> seems weird to sequence them in this way, especially as it is cheaper to
> perform client IP address checks (and some zone permission checks)
> earlier in order.
> 
> Section 3.3.2 talks about why the client permissions check is in that
> position previous to subsequent actions, but not why it can't be
> performed earlier.
> 
> 		Mukund
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop