Here's a Policy Calendar for Tomorrow's BC call. (5-Dec-2013) Channel 1. BC participation in ICANN Public Comment process: ICANN Public Comment page is <http://www.icann.org/en/news/public-comment> <http://www.icann.org/en/news/public-comment> here<https://www.icann.org/en/news/public-comment>. Selected comment opportunities below: 1. Second Accountability & Transparency Review Team (ATRT 2) Draft Report/Recommendations. (reply comments by 13-Dec) The ATRT2 just published its draft review/recommendations (here<http://www.icann.org/en/about/aoc-review/atrt/draft-recommendations-15oct13-...>). The BC offered several suggestions to the ATRT2 when they began in Jun-2013 (link<http://www.bizconst.org/Positions-Statements/BC%20Comment%20on%20ATRT-2%20qu...>) Elisa drafted comments on meetings and Angie on multi-lingual resources (attached). These were circulated to the BC on 18-Nov, so we should finalize soon. 2. Thick Whois PDP recommendations (initial comments by 7-Dec, comments close 28-Dec) The BC commented on the PDP initial report on 3-Aug-2013 (link<http://forum.icann.org/lists/comments-thick-whois-initial-21jun13/msg00008.h...>). Should we do another comment on the final recommendations? 3. Protecting IGO/INGO identifiers in all gTLDs. (initial comments by 18-Dec) The BC filed comments on this plan on 2-Nov (link<http://forum.icann.org/lists/comments-igo-ingo-final-20sep13/msg00021.html>). Should we file further comments before Board considers the plan? 4. Study<http://whois.icann.org/sites/default/files/files/cmu-misuse-study-26nov13-en...> on Whois Misuse (initial comments by 27-Dec) In 2009, the BC prompted this study to learn whether "Public access to WHOIS data leads to a measurable degree of misuse – that is, to actions that cause actual harm, are illegal or illegitimate, or otherwise contrary to the stated legitimate purpose." We need volunteers to analyze the study and draft comments. 5. ICANN draft for Vision, Mission & Focus for 5-year Strategic Plan (comments close 31-Jan) This draft is output of April-September "brainstorming" by board, community and staff. (link<http://www.icann.org/en/about/planning/strategic-engagement/focus-areas-29oc...>) Tim Chen and Chris Chaplow are drafting comments for the BC. Note: BC members are encouraged to submit individual/company comments. The BC selects topics on which to submit official positions based on member interest. --- Channel 2. Support for discussion and votes of our representatives on GNSO Council John Berard and Gabi Szlak, Councilors. Next Council meeting is 12-Dec-2013, 15:00 UTC. Agenda and Motions here<http://gnso.icann.org/en/meetings/agenda-council-12dec13-en.htm>. Highlights: Item 4: motion to accept final report of Joint IDN Working Group (JIG). Item 5: motion to adopt final report (link<http://ccnso.icann.org/workinggroups/dssa-final-08nov13-en.pdf>) of joint DNS Security and Stability and Analysis working group (DSSA WG) Item 7: consider Council response to Accountability & Transparency Review Team (ATRT 2) --- Channel 3. Supporting discussion/voting on matters before the Commercial Stakeholders Group (CSG) Marilyn Cade, CSG Liaison Developments in global internet governance and implications for ICANN and for private sector role. --- Channel 4. BC statements and responses during public meetings (outreach events, public forum, etc.) ICANN plans to delegate Singular and Plural forms of same string, despite GAC advice and community concerns. The BC sent a letter to ICANN CEO and Board on 22-Oct (link<http://www.bizconst.org/Positions-Statements/Singular-Plural%20TLDs.pdf>) with two requests: We asked ICANN to publish any evidence considered by expert panels, arbitration providers, and ICANN staff in its evaluation of these decisions. We asked ICANN to publish specific objective criteria to judge string similarity, and allow for an appeal system where applicants can challenge prior ICDR decisions on singular-plural TLDs based on this criteria. Steve re-iterated those requests at the Public Forum in BA, asking if the Board shared the BC concerns. NGPC member Mike Silber replied, "Yes, several of us are very concerned about this." This topic was on NGPC’s 20-Nov agenda (Report on String Confusion Objection Expert Determinations), , but minutes<http://www.icann.org/en/groups/board/documents/prelim-report-new-gtld-20nov1...> indicate they postponed this item. ICANN’s latest plan to manage collisions between new gTLD strings and domains used in private networks. (link<http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1-...>) To develop the framework for new TLDs, ICANN hired JAS Advisors. JAS posted initial thoughts on detection & response at DomainIncite (link<http://domainincite.com/15205-dns-namespace-collisions-detection-and-respons...>), where BC members can reply with suggestions. Implementing GAC Advice on Safeguards and Exclusive Generic gTLDs. First item in Buenos Aires GAC Communique is a query about open and nondiscriminatory access to domains in new TLDs. Full Communique is here<http://www.icann.org/en/news/correspondence/gac-to-board-20nov13-en>. Excerpt below. 1. Category 1 and Category 2 Safeguard Advice. The GAC welcomed the response of the Board to the GAC's Beijing Communiqué advice on Category 1 and Category 2 safeguards. The GAC received useful information regarding implementation of the safeguards during its discussions with the New gTLD Program Committee. GAC members asked for clarification of a number of issues and look forward to ICANN's response. The GAC highlights the importance of its Beijing advice on 'Restricted Access' registries, particularly with regard to the need to avoid undue preference and/or undue disadvantage. The GAC requests a briefing on whether the Board considers that the existing PIC specifications (including 3c) fully implements this advice. Where this is 3c from Spec 11 of Standard Registry Agreement: c. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.