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

Joe Abley <> Thu, 30 September 2010 13:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 985AB3A6C9A; Thu, 30 Sep 2010 06:25:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.567
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pTJOyW74G00U; Thu, 30 Sep 2010 06:25:27 -0700 (PDT)
Received: from ( [IPv6:2001:418:1::62]) by (Postfix) with ESMTP id 8A07A3A6A9B; Thu, 30 Sep 2010 06:25:27 -0700 (PDT)
Received: from majordom by with local (Exim 4.72 (FreeBSD)) (envelope-from <>) id 1P1J4m-0008Y1-Kb for; Thu, 30 Sep 2010 13:21:32 +0000
Received: from [2001:4900:1:392:213:20ff:fe1b:3bfe] ( by with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <>) id 1P1J4k-0008XE-5J for; Thu, 30 Sep 2010 13:21:30 +0000
Received: from [] (helo=[]) by with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <>) 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 <>
In-Reply-To: <>
Date: Thu, 30 Sep 2010 13:20:53 +0000
Cc: namedroppers WG <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: John Dickinson <>
X-Mailer: Apple Mail (2.1081)
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
Precedence: bulk
List-ID: <>
List-Unsubscribe: To unsubscribe send a message to with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <>

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.


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