[dnssec-key-tf] physical meeting at RIPE 55- again!

On Sep 11, 2007, at 2:54 PM, Peter Koch wrote:

> On Tue, Sep 11, 2007 at 01:31:25PM +0100, Jim Reid wrote:
>
>> This is why I would like us to make a clear decision. And if we
>> decide to meet at RIPE 55, what are we going to discuss? What would
>> an agenda for that meeting look like? Given the low traffic on the
>
> we've had some discussion of various topics:
>
> o Confirm decision to deal with TLD TAs only
> o Separate TA collection and maintenance from publication
> o Agree on mission statement and communication: "why are we doing  
> this?"
> o Discuss and decide on publication:  static vs. dynamic (or both?)
> o Discuss TLD registry authentication, TA acquisition and rollover
> o Discuss exit strategy
> o Discuss requirements for and recommendation of TAR operator
>
> For at least some of those statements have been sent to the list.
>
>> list to date, I'm not sure if there is enough justification to meet
>> in person. OTOH, perhaps a physical meeting is the thing that's
>> needed to get this TF to make progress. I would like the TF to make a
>
> How else would we make any progress at all?  Also, may I ask that  
> averybody
> on this list, who hasn't spoken up yet (where I'd count that as an  
> implicit
> statement of interest), whether they are still interested (and  
> able) to
> participate in the Task Force?

I haven't spoken up yet, though I'm interested. Holiday interrupt.

My brief on the topics above:

I do agree with the decision of TLD TA's only, with the exception of  
2nd level arpa domains. Logically 2nd level arpa domains are special  
enough to be grouped under its own top level. There are not that many  
2nd level arpa domains, and I don't see that increasing any time soon.

I also see the separation between TA collection, maintenance and  
publication. But this is a separation in processing only, and need to  
be properly defined accordingly.

On the point of static/dynamic, I don't see why we can't do both. I  
don't see DLV as a proper solution, though.

Exit strategy: stop when the root is signed, given an overlap of a  
few months.

Roy