Re: [DNSOP] A conversational description of sentinel.

Petr Špaček <petr.spacek@nic.cz> Fri, 02 February 2018 07:50 UTC

Return-Path: <petr.spacek@nic.cz>
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 27C7112778E for <dnsop@ietfa.amsl.com>; Thu, 1 Feb 2018 23:50:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level:
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 N7VRBkYj31qk for <dnsop@ietfa.amsl.com>; Thu, 1 Feb 2018 23:50:35 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 E10C812EAEA for <dnsop@ietf.org>; Thu, 1 Feb 2018 23:50:34 -0800 (PST)
Received: from [10.0.1.220] (unknown [82.202.112.233]) by mail.nic.cz (Postfix) with ESMTPSA id 1805F64117 for <dnsop@ietf.org>; Fri, 2 Feb 2018 08:50:33 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1517557833; bh=X65n5dXpwL3iJCrXVpn1+/T9bwWhwSEbyCmQW91PDIM=; h=To:From:Date; b=g2MhiRE7YgVaVAVcLzcT1yThPTSH00vCign33A3+MrQ3o0EixzfU30UTLUO1XiiHt zKmppckFR0VqXS1gI6rqEvVPfa91+rjvt6F/FhBwchfpq+7m5tMvFYHAz6BYLLRMhk 9vvvjDv6pNjkaFhrcoI3EuDWnOx6X1JwqDY5Dor4=
To: dnsop@ietf.org
References: <CAHw9_iKnD4WtTKyof=nm4ChmDZ5mAPqA7a_-m1t_Lauugf4Uow@mail.gmail.com> <alpine.DEB.2.11.1801251505070.5022@grey.csi.cam.ac.uk> <CAHw9_iJ-gwC1ZoWQ3YiJraD3eoUf-9-Ay--rPYzy1zWYUzvYmg@mail.gmail.com> <FDCED4D6-A7CE-465B-8344-CA89753ADF19@vpnc.org> <74C0CA59-6D53-4A60-ACBA-4AF5B51FE3FF@apnic.net> <D5D013D4-1EAD-434B-863A-29CB1BBEF4E4@vpnc.org> <496EFA88-BA70-460B-BFB2-69B2C7BC905D@apnic.net> <4540A279-4A37-4245-AE61-BEE5342E3F72@vpnc.org> <20180202075530.Horde.UWaxe9eenZ7PyxWYFHCFGdN@andreasschulze.de>
From: Petr Špaček <petr.spacek@nic.cz>
Organization: CZ.NIC
Message-ID: <e8ac7bd0-26e6-cf97-e2ef-0ead50dc18ce@nic.cz>
Date: Fri, 02 Feb 2018 08:50:32 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180202075530.Horde.UWaxe9eenZ7PyxWYFHCFGdN@andreasschulze.de>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/BFzMuqrDSdcbYbC7VhC5Xzv1_Xo>
Subject: Re: [DNSOP] A conversational description of sentinel.
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: Fri, 02 Feb 2018 07:50:37 -0000

On 2.2.2018 07:55, A. Schulze wrote> Paul Hoffman:
>> My preference is #1 because, in general, a label starting with _ has
>> been meant for infrastructure, and that's what these labels are.
>> Others might like #2 so they don't have to add configuration to BIND
>> (and maybe other authoritative servers).
> 
> just checked, my NSD and POWERDNS serve A record for _foo.examle.
> without noise...
> so: #1

For the record, I also like more the underscore variant (#1 above).

BIND spits a warning about it and I like it. After all, this whole KSK
sentinel bussiness is quite specialized thing to do and should be done
only by people who know what they are doing, so warning is appropriate.

After all, what is your guess about number of zones containing such
names? 10? 20 zones globally? I cannot see more, and most likely vast
majority of people who would like to create such zones is following this
dicussion.

Please do not overcomplicate things. The technology seems okay to me.
(I've implemented it including tests, see Knot Resolver 2.0.0.)
Could we polish the text and publish it, pretty please?


(BTW I have seen underscore names with A records in Microsoft Active
Direcotry DNS years ago, so this is not the first time _ A is used.)

-- 
Petr Špaček  @  CZ.NIC