Re: [DNSOP] draft-huston-kskroll-sentinel - naming format?

Paul Vixie <paul@redbarn.org> Tue, 31 October 2017 18:10 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 2711613FA1D for <dnsop@ietfa.amsl.com>; Tue, 31 Oct 2017 11:10:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level:
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 bDDspK-8ZWah for <dnsop@ietfa.amsl.com>; Tue, 31 Oct 2017 11:10:03 -0700 (PDT)
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 55EF213FA12 for <dnsop@ietf.org>; Tue, 31 Oct 2017 11:10:03 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:4987:fe28:d911:202c] (unknown [IPv6:2001:559:8000:c9:4987:fe28:d911:202c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id BC4BC61FA2; Tue, 31 Oct 2017 18:10:02 +0000 (UTC)
Message-ID: <59F8BC79.6040709@redbarn.org>
Date: Tue, 31 Oct 2017 11:10:01 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.20 (Windows/20171012)
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>
CC: Ray Bellis <ray@bellis.me.uk>, dnsop@ietf.org
References: <027a469c-5bb6-7940-fd89-55b91dd97275@bellis.me.uk> <20171030174052.GB87160@isc.org> <ce2c26be-d944-345c-0e63-d063682c78a6@bellis.me.uk> <CFAF5F11-E120-4E5D-A317-00B25DAE9F9A@hopcount.ca> <cf15d0b6-6e8d-851e-248b-5a3dfff21905@bellis.me.uk> <88551C53-593F-4672-9655-4530F4B8068A@hopcount.ca>
In-Reply-To: <88551C53-593F-4672-9655-4530F4B8068A@hopcount.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PhclYp50u-wzWfDQSXuS6KpsWh8>
Subject: Re: [DNSOP] draft-huston-kskroll-sentinel - naming format?
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: Tue, 31 Oct 2017 18:10:09 -0000


Joe Abley wrote:
> If a format is going to be specified that specifically prohibits a
> zone cut, doesn't it make more sense to choose one that can't
> possibly involve one because there are no potential label
> boundaries?

+1.

-- 
P Vixie