[Rt4-whois] Planning our next steps

[Smith, Bill]

Regarding current ICANN Policy, Denise Michel should be able to help us out on that.

I'd prefer a 2-day format as well and could support even longer sessions, especially if we are doing outreach or are getting input from the region.

I'm in favor of asking stakeholders for their opinions on a number of subjects, including what we should work on; provided that we make it clear our first order of business is to complete the review per the Affirmation of Commitments.

I realize that others would prefer to combine a broader analysis and review with a narrower, perhaps stricter interpretation of the AoC. There are valid concerns and reasons to do this. I'm supportive of those and would genuinely like to address the broader issues related to WHOIS Policy.

I suspect, or perhaps it's a hypothesis, that we could reach consensus quickly and maybe even easily on the narrower analysis and review. I also think we could quickly reach consensus on the broader issues that are at play in WHOIS Policy. Where we might have difficulty, is in reaching consensus on how best to deal with any issues we uncover in either the narrow or broad analysis.

If my hypothesis is correct, we will have had the opportunity to work together, reach consensus, and establish working relationships and rapport that we can rely on as we delve into issues that might be more contentious. Having the prior consensus-building experience will engender trust in each other and could help us make very valuable recommendations regarding an important issue.

From: rt4-whois-bounces at icann.org [mailto:rt4-whois-bounces at icann.org] On Behalf Of Kim G. von Arx
Sent: Friday, November 12, 2010 8:01 AM
To: Emily Taylor
Cc: rt4-whois at icann.org
Subject: Re: [Rt4-whois] Planning our next steps

Hi Emily et al:


- What is ICANN's policy at the moment?  Would any member of the Team be in a position to do a presentation on this?  Or should we invite someone from the staff to cover this point?

I would suggest a staff member to make that presentation

I agree with all of the items listed, but hope that we will have started most of the work already.  My thinking is that our face to face meetings, however, should focus on fine tuning rough brushstroke proposals and advance contentious and problematic areas as well as provide expert presentations to assist us to reach consensus.  I would like to also suggest that we invite someone from the rights-holder constituency to bring their concerns to the table.  With respect to format, I think it would be best if we start all of our face to face meetings with administrative issues first and then dive in to the presentations for half a day and then commence the substantive work for the remaining 1.5 days.


Attendance at San Francisco and other ICANN meetings

I would welcome the Team's thoughts on this.  I'd like to propose the following format for all ICANN meetings that time place during our mandate

- We all aim to have a 1.5 day Team meeting

I would suggest that we aim for a 2-day team meeting to utilize our face to face time as much as possible.


- In addition, we should use ICANN meetings for outreach to:
          - the Supporting Organisations and Advisory Committees
          - the Board
          - any local stakeholder groups who are relevant to our task

I would like to use the outreach sessions to build liaison with the relevant SO/ACs, inform them about how and what we're doing, ask them what they think we should be doing, and how they can contribute to our task.   Would it be possible for those who have been put forward by different SO/ACs to accompany the Chair/Vice Chair to those meetings and help lead the discussions?

agreed



Our next call
I propose that in our next call we focus on:

- broad brush stakeholder identification, from a global perspective
- identifying what, if any, external resources we need.

agreed.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mm.icann.org/pipermail/rt4-whois/attachments/20101112/bfb3cd7c/attachment.html