[dnssec-key-tf] agreements on the use of the repository

On Fri, Sep 07, 2007 at 12:10:54PM +0200, Daniel Karrenberg wrote:

> I will do my best with another hat on to see that .arpa is not going to
> be a problem; in fact I do not expect it to be. 

Thanks, Daniel. The ARPA domain (and the beasts underneath) were the ones I had
in mind.

> Publication format: As many as are required by the users.  Pragmatic. 
> At least one easily parseable format. Possibly tools to make popular
> textual formats out of hat one, e.g. config files for popular DNS software.

The I-D <draft-larson-dnsop-trust-anchor-01> works on the human interface.
Maybe we need to re-phrase "format" to "method": Do we expect the Trust Anchor
Repository to be dynamically queried ("TLD only DLV") or only occasionally
transferred/downloadded?

> Location: very preferably IANA itself.  If that ccannot be achieved RIPE
> NCC requiring simple MoUs with each TLD concerned. Explicit intention 
> by RIPE NCC to turn service over to IANA when IANA is ready to perform it.

Just a clarification question: is this with any hat?
If we start with someone else but IANA, how would this entity authenticate
the TLD contact?

> Exit strategy: Yearly review if service is still necessary.  Definitely
> stop 6 months after root signed.  Announce a definite stop year? 

In these n months, would the TLD TAs still be maintained or would the root
TA be entered as soon as it is available and the publication stopped
eventually?

-Peter