[bc-gnso] Policy calendar for 10-Jan-2012 BC member call

[Steve DelBianco]

Here is the latest BC policy calendar, for use during 10-Jan-2012 BC member call.
Channel 1. BC participation in ICANN Public Comment process:
ICANN Public Comment page is at http://www.icann.org/en/public-comment/

1. New gTLD Applicant Support Program: Financial Assistance   (10-Jan)

2. Preliminary GNSO Issue Report on RAA Amendments    (13-Jan)

3. IDN Variant Issues Project: Draft Integrated Issues Report  (30-Jan)

4. Initial Report on Universal Acceptance of IDN TLDs    (7-Feb)

5. WHOIS Policy Review Team (AoC) Draft Report    (18-Mar)

Note: BC members are encouraged to submit individual / company comments.  Based on member interest, the BC selects topics on which to submit official positions.
Channel 2. Support for discussion and votes of our representatives on GNSO Council
GNSO Project Status available at https://www.icann.org/en/processes/gnso/current-issues.html
<https://community.icann.org/display/gnsocouncilmeetings/agenda+17+November+2011>Agenda<https://community.icann.org/display/gnsocouncilmeetings/agenda+19+January+2012> and <https://community.icann.org/display/gnsocouncilmeetings/Motions+17+November+2011> motions<https://community.icann.org/display/gnsocouncilmeetings/Motions+19+January+2012> for 19-Jan-2012 GNSO Council teleconference were not yet published as of 9-Jan.

John figures we'll see motions on Outreach, thick Whois, and perhaps cross-community working groups



Channel 3. Supporting discussion and voting on policy matters before the Commercial Stakeholders Group (CSG)
Ron Andruff, CSG Liaison, and Marilyn Cade (alternate)


Channel 4. BC statements and responses during public meetings (outreach events, public forum, etc.)
Affirmation review team for Whois   (Susan Kawaguchi, Lynn Goodendorf, Bill Smith)
Affirmation review team for SSR  (Security, Stability, & Resilience)    (Jeff Brueggeman)

Remaining implementation work for gTLD expansion plan, incl BC letter to ICANN and possible follow-up on specific improvement recommendations:

ICANN's board demonstrated last week that it will continue to direct changes in implementation details for new gTLDs. (summary and briefing documents of the 5-Jan Informational Board meeting here<http://www.icann.org/en/minutes/> ).  The board made it clear that it expects "remaining implementation work":

The Board held an informational call with staff regarding the planning for the opening of the New gTLD Program application window on 12 January 2012.  … The Staff and the Board discussed (1) operational readiness for the New gTLD Program, including the posting of a new version of the Applicant Guidebook reflecting the interim amendments approved by the Board; (2) the status of plans for timely execution of the GAC requests regarding the Early Warning, application batching process, trademark clearinghouse procedures, planning for a second round, and applicant support; (3) providing responses to recent correspondence regarding the New gTLD Program; and (4) next steps in providing the Board further information on remaining implementation work.

In particular, briefing document 4 (here<http://www.icann.org/en/minutes/board-briefing-materials-4-05jan12-en.pdf>) describes ongoing work on implementing RPMs:

TM Clearinghouse Process Development: This work focuses on implementing the new rights protection mechanisms that were agreed on during the new gTLD discussions. An invitation for volunteers from the community to engage with ICANN in building out the clearinghouse processes resulted in a group of over 50 volunteers. This group (Implementation Assistance Group, IAG) began meetings in November and is working through a number of issues from both process and technical standpoints.

Seems to me there are opportunities to press for improvements that advance established BC positions — without delaying the gTLD application process.






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/bc-gnso/attachments/20120110/0c7d9eb4/attachment.html>