Re: [dnsext] Fwd: I-D Action:draft-jabley-dnssec-trust-anchor-00.txt

Joe Abley <jabley@hopcount.ca> Thu, 30 September 2010 13:25 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 985AB3A6C9A; Thu, 30 Sep 2010 06:25:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.567
X-Spam-Level:
X-Spam-Status: No, score=-101.567 tagged_above=-999 required=5 tests=[AWL=1.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTJOyW74G00U; Thu, 30 Sep 2010 06:25:27 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8A07A3A6A9B; Thu, 30 Sep 2010 06:25:27 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1P1J4m-0008Y1-Kb for namedroppers-data0@psg.com; Thu, 30 Sep 2010 13:21:32 +0000
Received: from [2001:4900:1:392:213:20ff:fe1b:3bfe] (helo=monster.hopcount.ca) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1P1J4k-0008XE-5J for namedroppers@ops.ietf.org; Thu, 30 Sep 2010 13:21:30 +0000
Received: from [217.64.100.66] (helo=[10.10.10.120]) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1P1J4g-0005eb-5a; Thu, 30 Sep 2010 13:21:26 +0000
Subject: Re: [dnsext] Fwd: I-D Action:draft-jabley-dnssec-trust-anchor-00.txt
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20BF6C85-1969-4127-AF95-CCFB566EC3F1@jadickinson.co.uk>
Date: Thu, 30 Sep 2010 13:20:53 +0000
Cc: namedroppers WG <namedroppers@ops.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <915556A6-DE8D-4094-8D4C-AF67E8D8584F@hopcount.ca>
References: <20100929124503.ECDA13A6ECD@core3.amsl.com> <EE62C0B3-ACC5-4811-A047-54B21EAC8EC1@hopcount.ca> <20BF6C85-1969-4127-AF95-CCFB566EC3F1@jadickinson.co.uk>
To: John Dickinson <jad@jadickinson.co.uk>
X-Mailer: Apple Mail (2.1081)
X-SA-Exim-Connect-IP: 217.64.100.66
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

On 2010-09-30, at 13:12, John Dickinson wrote:

> Would it be useful for the xml to be able to provide information on the intentions of the zone operator. For example, at the moment a validator operator has no information about which of the 4 possible sections of an unbound conf to put this TA in.
> 
> Some hint like <RollMethod>RFC5011</RollMethod> would be useful IMHO.

If we were to include such machine-parseable tokens then I imagine we'd do it with XML elements that were specified in the schema, e.g.

  <RollMethod><rfc5011/></RollMethod>

However, I'm not convinced I understand the use case to which you refer. Can you explain further?


Joe