[ALAC] For Review and Action ­ Prep For ICANN 52 High Interest Topic Session

[Alan Greenberg]

I just realized that I was negligent in not 
forwarding this message to the ALAC.

As you will see, this is a summary of the Monday 
"High Interest" session. The three topics 
coalesced at the SO-AC-SG Chair meeting on the 
Friday before the LA ICANN meeting, which both 
Olivier and I attended (as present and incoming ALAC Chairs).

The three items are clearly very inter-related, 
and you will notice that the second one is 
superset of the ATLAS II recommendation for a way 
to access Policy info. Following the Chairs' 
identifying these topics, each was assigned to 
one Chair and I am leading the Information 
management one (not that a lot has happened as far as I can see).

We are allocated up to 1 person per RALO on the 
panel. As I am leader of one of the tasks, I will 
exercise Chair's prerogative and will fill the NA 
seat. We need volunteers for the other regions. 
Please contact me via this list or privately if you are interested.

For the record, my personal position is that a 
prioritization exercise is pretty futile. If we 
can even partially address those, the need to 
prioritize will be significantly lessened. Of 
course, that will not address overload at times 
such as this with the IANA and Accountability 
efforts, but there really is not way that we can 
fix the current overload with prioritization - it 
is driven by external events that we cannot choose to ignore.

Alan


At 31/01/2015 04:56 AM, David Olive wrote:
>Dear Community Leaders:
>
>As we all prepare for travel to the ICANN Public 
>Meeting in Singapore (ICANN 52), this note is 
>designed to update you and ask for assistance 
>regarding our preparations for the SO-AC High 
>Interest Topic session scheduled for the main 
>ballroom (Padang) on the afternoon of Monday 9 February at 1400 Local Time.
>
>As you know, based on our recent calls and 
>correspondence, the main topic you agreed to 
>focus on for the ICANN 52 session was the 
>operational and workload improvement efforts 
>that were started at the ICANN 51 meeting in Los Angeles.
>
>During our last meeting (a couple of weeks ago 
>with Fadi) we discussed the brainstorm idea to 
>try to associate that operational improvements 
>discussion with the broader ICANN Accountability 
>topic.  As Jonathan and Keith warned during the 
>meeting, that connection has proven to be too 
>tenuous.  As a result, we have explored 
>re-fining the session to focus directly on the 
>three operational improvement themes -
>
>(1) Establishing a stakeholder-led mechanism for 
>prioritizing ICANN’s overall policy issues and related work areas;
>(2) Developing a comprehensive knowledge 
>database or network to make information about 
>ICANN’s current and past work easily accessible 
>and available to all existing and future ICANN participants; and
>(3) Identifying ways to improve our capabilities 
>to identify and attract new and productive 
>community participation while retaining existing 
>participants who dedicate their time and efforts to ICANN’s work.
>
>The overall goal of the Monday session can now 
>be more focused - to develop a useful dialogue 
>that demonstrates to the broader community that 
>their leadership (all of you) is engaged in 
>developing solutions to the community’s current 
>workload challenges and is interested in 
>absorbing community ideas to help collectively 
>solve these issues. The more concise agenda also 
>works well because due to scheduling of other 
>sessions we are limited to a 75-minute session time block.
>
>We’ve structured the session in two parts. The 
>first part (25 minutes) will offer the audience 
>a general discussion among you and other 
>community representative panelists on the 
>overall view you or communities have about 
>ICANN’s community workload challenges and how 
>those challenges impact ICANN’s operational 
>accountability generally – that is, what is 
>currently working operationally, what can be 
>improved and what ideas are being explored to 
>take improvement steps. You or your fellow 
>community members might even have specific best 
>practice suggestions that work in your communities.
>
>The second part of the session (45 minutes) will 
>address, in turn, each of the three work streams 
>you have developed (15 minutes a piece), so that 
>the community can see and hear the various 
>approaches that are being considered in the 
>three topic areas to help address ICANN’s workload challenges.
>
>We hope that through in-room and remote 
>participation that audience members (via in-room 
>microphones and twitter posts) will be able to 
>contribute some thoughts and ideas to the discussion.
>
>The session will present itself as more of a 
>problem-solving exercise which will enable you 
>and your community representatives to talk about 
>ideas for changes.  We hope the session 
>transcript will be a useful tool to help us take 
>the various subgroups to the next step of their 
>discussions and ultimate recommendations.  We 
>think the modified theme will work nicely - 
>enmeshed with the Monday ICG IANA Stewardship 
>Transition and the CCWG Accountability 
>programming as an example of how ICANN community 
>leadership is looking to improve ICANN’s 
>effectiveness and operational excellence.
>
>We’ve created some draft context/background 
>material and sample “seed” questions for 
>moderator Brad White to consider in introducing 
>the session and keeping things moving.  Please 
>feel free to suggest additional questions or 
>modifications to the context materials for Brad 
>that are attached to this message.
>
>Also, when we meet next Friday in Singapore, 
>please share with me who you plan to have on the 
>stage to represent your community during the 
>session.  We will follow the now-traditional 
>protocol of the following panelist assignments:
>
>“
 a maximum two (2) representatives from each 
>of the ASO, ccNSO, GAC, SSAC and RSSAC 
>communities, and a maximum of four (4) 
>participants from the GNSO (one per Stakeholder 
>Group) and a maximum of 5 from At-Large (one per RALO)”.
>
>I look forward to finalizing these arrangements 
>with you when we meet next week in Singapore. 
>Looking forward to your feedback via email and at the meeting.
>
>Best regards,
>
>David
>
>
>David A. Olive
>Vice President, Policy Development Support
>General Manager, ICANN Regional Headquarters –Istanbul
>Hakki Yeten Cad. Selenium Plaza No:10/C K:10 34349 Fulya, Besiktas, Istanbul
>Internet Corporation for Assigned Names and Numbers (ICANN)
>
>Direct Line: +90.212.999.6212
>Mobile:      + 1. 202.341.3611
>Mobile:      +90.533.341.6550
>Email:  <mailto:david.olive at icann.org>david.olive at icann.org
>www.icann.org
>
>