[NCSG-Discuss] Please Join in NCSG's Monthly Open Policy Meeting - Tue. 12 March (21:00 UTC) agenda & participation details

Sat Mar 9 03:31:53 CET 2013

Thks Robin,

NPOC's monthly call which is on the second Tuesday of the month at 20:00UTC
will just finish when the NCSG Open Policy Meeting starts. I hope NPOC
folks (notably, Rudi Vansnick, Cintra Sooknanan, Sam Lanfranco and Klaus
Stoll) can jump in as soon as finished with NPOC call.

Cheers, Alain

On Thu, Mar 7, 2013 at 11:12 PM, Robin Gross <robin at ipjustice.org> wrote:

> Reminder: I hope you all will join in next Tuesday's NCSG Open Policy
> Meeting, which is an open discussion between the NCSG Policy Committee,
> including the NCSG GNSO Councilors and the entire NCSG membership.
>
> The meeting is on 12 March, which is 2 days before the next GNSO Council
> meeting to help prepare for NCSG's participation in that meeting.  We will
> also discuss preparations for the Beijing ICANN meeting next month and
> review open comment periods and working groups.
>
> Dial-in and remote participation details are below.  Also below is a draft
> discussion agenda.  If anyone needs a dial-out, please let me know *at
> least* 24-hours before the meeting to ensure we have enough time to make
> the dial-out happen.
>
> Please join in the discussion.  Thank you!
>
> Best,
> Robin
> **
> *NCSG Policy Open Meeting*
> *12 March 2013 - Tuesday*
> *21:00 - 23:00 UTC*
>
> Other Time Zones:
> *
> http://www.timeanddate.com/worldclock/fixedtime.html?msg=NCSG+Open+Policy+Meeting+March+2013&iso=20130312T21&p1=136&ah=2
> ***<http://www.timeanddate.com/worldclock/fixedtime.html?msg=NCSG+Open+Policy+Meeting+February+2013&iso=20130212T21&p1=1440&ah=2>
>
> *Remote Participation Details:*
> Telephone:  *http://ipjustice.org/ICANN/NCSG/NCSG_Passcodes.htm*<http://ipjustice.org/ICANN/NCSG/NCSG_Passcodes.htm>
> Adobe Connect:  *https://icann.adobeconnect.com/_a819976787/ncsg/*<https://icann.adobeconnect.com/_a819976787/ncsg/>
>
> *Attendance Records of NCSG Open Policy Meetings:*
>
> https://docs.google.com/spreadsheet/ccc?key=0AmHFgvYjF_e4dGdNcVVfdHI2SWJ4dDZjU2xYaGV0WUE&usp=sharing
> *
> *
> *Draft Discussion Agenda:*
>
> *I. Preparation for 14 March GNSO Council Mee*ting
>
> 14 March GNSO Council Meeting Discussion Agenda:
>
> https://community.icann.org/display/gnsocouncilmeetings/Agenda+14+March+2013
>  GNSO Council meeting audio cast: http://stream.icann.org:8000/gnso.m3u
>
> *A. Motions to be Voted On*
> *   NONE Yet*
>
> https://community.icann.org/display/gnsocouncilmeetings/Motions+14+March+2013
> *
> *
> *B. Discussion Issues (no vote)*
> *
> *
> *1. Policy vs. Implementation*
>
> Recent issues highlight an ongoing broader issue regarding the boundary
> between policy development and implementation work as well as the effective
> integration of policy development and integration work from the outset.
>
> In addition, the Council is increasingly asked to consider issues for
> policy
> guidance and may well need to look at the evolution of its own work and
> processes to accommodate this type of request.
>
> Recent discussions on the Council mailing list indicate that there is an
> interest to undertake further work on this issue. At the same time, ICANN
> Staff has published a paper
> <
> http://gnso.icann.org/en/correspondence/policy-implementation-framework-08j
> an13-en.pdf>   that is intended to facilitate further community discussions
> on this topic.
>
> Further community discussion will take place in Beijing and the inclusion
> of
> this agenda item here serves to keep the issue on the agenda of the Council
> in the interim.
>
> ICANN Public Comment Forum on Policy vs. Implementation:
>
> http://www.icann.org/en/news/public-comment/policy-implementation-31jan13-en.htm
> Reply Comments Due by 14 March
>
>
> *2,  Whois Privacy and Proxy Relay and Reveal Study*
>
> At the ICANN Meeting in Toronto, Lyman Chapin presented the results of the
> survey
> <
> http://toronto45.icann.org/meetings/toronto2012/presentation-whois-survey-1
> 7oct12-en.pdf>  that evaluated the feasibility of conducting a future
> in-depth study into communication Relay and identity Reveal requests sent
> for gTLD domain names registered using Proxy and Privacy services.
>
> The Council discussed this at its 14 February 2013 meeting but did not
> reach
> a firm conclusion.  Some expressed concern about going ahead with the study
> now, when a lot of other Whois activities are going on, while others
> appeared to support moving forward as the study could result in data that
> would help inform ongoing Whois activities.
>
> One  possible way forward is that staff is asked to go ahead with the RFP
> for this work and then report back to the Council before going ahead with
> the study? In this way, some of the preparatory work could be done, which
> would allow us to move forward quickly if/when the Council decides to move
> ahead.
>
> *3.  GNSO Council in Beijing Meeting Planning*
>
> The GNSO Council has the opportunity to shape the topics and
> substance of the Council's proposed meetings with other groups in Beijing
> such as the CCNSO, the GAC and the ICANN board.
>
> What topics would NCSG members like to see on GNSO Council's discussion
> agendas in Beijng?
>
> *4.  Confirmation of attendance of NCSG Representatives for 14 March
> meeting and need for any proxies to be arranged?*
> *
> *
> *II.  Other Policy Issues and Public Comments*
> *
> *
> *A.  Other Policy Issues*
> *
> *
> *1.  2nd Accountability & Transparency Review Team (ATRT2)*
> Background:
> http://www.icann.org/en/news/announcements/announcement-2-15feb13-en.htm
> *
> *
> *2.  Whois Expert Working Group*
> Background:
> http://www.icann.org/en/news/announcements/announcement-14feb13-en.htm
>
> Issue with under-representation of privacy experts in group
> (maybe Stephanie Perin could brief us on this discussion?)
>
> *3.  Thick Whois & Data Protection Sub-Group*
> Background:
> https://community.icann.org/display/PDP/5.+WG+Background+Documents
>
> *4.  Special Protections for Red Cross, Olympic Cmte, IGOs*
> IGO-INGO Working Group
> NCSG Input Statement:
>
> https://community.icann.org/download/attachments/40175441/NCSG_IGO-INGO_Input_Request_FINAL.pdf?version=1&modificationDate=1360810862000
>
> *5.  ICANN's Outreach & Engagement Plans*
> *
> *
> *6.  Public Interest Commitments (PICs) of New TLD applicants*
>  Background:
> http://www.icann.org/en/news/announcements/announcement-2-05mar13-en.htm
> *
> *
> *7.  What is happening with staff's Strawman solution & other TM issues
> for New TLDs?*
> *
> *
> *8.  Registrant Agreement Amendment (RAA Negotiations)*
> Background:
> http://www.icann.org/en/news/announcements/announcement-14feb13-en.htm
> *
> *
> *B.  Open ICANN Public Comments*
> *
> *
> *1.  So-called "closed generic" or "private label" TLD debate.*
> ICANN Public Comment Forum:
> http://www.icann.org/en/news/public-comment/closed-generic-05feb13-en.htm
> Reply Comment Deadline: ?
>
> GNSO to provide policy guidance to board at end of comment period
>
> *2.  Revised New gTLD Registry Agreement Including Additional Public
> Interest Commitments Specification*
> ICANN Public Comment Forum:
> http://www.icann.org/en/news/public-comment/base-agreement-05feb13-en.htm
> Reply Comment Deadline: 20 March
>
> *3.  Whois Registrant Identification Study, Draft Report*
> ICANN Public Comment Forum:
> http://www.icann.org/en/news/public-comment/whois-regid-15feb13-en.htm
> Reply Comment Deadline: 31 March
>
> *4.  Preliminary Issue Report on Uniformity of Reporting*
> ICANN Public Comment Forum:
> http://www.icann.org/en/news/public-comment/whois-regid-15feb13-en.htm
> Comment Close: 22 March   Reply Close: 12 April
>
> *5.  Proposed Modification of GNSO PDP Manual to Address the Suspension
> of a PDP*
> ICANN Public Comment Forum:
> http://www.icann.org/en/news/public-comment/pdp-suspension-07mar13-en.htm
> Comment Close: 6 April   Reply Close: 28 April
>
> *6. ICANN's FY 14 Security, Stability and Resiliency Framework*
> ICANN Public Comment Forum:
> http://www.icann.org/en/news/public-comment/ssr-fy14-06mar13-en.htm
> Comment Close: 20 April   Reply Close: 20 May
>
>
> *III.  NCSG Planning for Beijing ICANN Meeting*
>
> Working draft schedule of NCSG Meetings in Beijing and proposed discussion
> topics so far:
>
> https://docs.google.com/spreadsheet/ccc?key=0AmHFgvYjF_e4dG11eV9fZWJMbUdEQW9PRnY4cnFNWVE#gid=0
>
> *A. Propose Discussion Issues:*
> *
> *
> *1.  NCSG with Board*
> *
> *
> *2.  NCSG with At-Large*
> *
> *
> *3.  Topics for Public Forum*
> *
> *
> *B.  Other Beijing Meeting Plans*
> 1.  Preparation Meeting for NCSG in Beijing on 28 March 15:00 UTC
> *
> *
> *IV.  AoB?*
>
>
>
>
>
>
> IP JUSTICE
> Robin Gross, Executive Director
> 1192 Haight Street, San Francisco, CA  94117  USA
> p: +1-415-553-6261    f: +1-415-462-6451
> w: http://www.ipjustice.org     e: robin at ipjustice.org
>
>
>
>

-- 
Alain Berranger, B.Eng, MBA
Member, Board of Directors, CECI,
http://www.ceci.ca<http://www.ceci.ca/en/about-ceci/team/board-of-directors/>
Executive-in-residence, Schulich School of Business, www.schulich.yorku.ca
Treasurer, Global Knowledge Partnership Foundation, www.gkpfoundation.org
NA representative, Chasquinet Foundation, www.chasquinet.org
Chair, NPOC, NCSG, ICANN, http://npoc.org/
O:+1 514 484 7824; M:+1 514 704 7824
Skype: alain.berranger

AVIS DE CONFIDENTIALITÉ
Ce courriel est confidentiel et est à l’usage exclusif du destinataire
ci-dessus. Toute personne qui lit le présent message sans en être le
destinataire, ou l’employé(e) ou la personne responsable de le remettre au
destinataire, est par les présentes avisée qu’il lui est strictement
interdit de le diffuser, de le distribuer, de le modifier ou de le
reproduire, en tout ou en partie . Si le destinataire ne peut être joint ou
si ce document vous a été communiqué par erreur, veuillez nous en informer
sur le champ  et détruire ce courriel et toute copie de celui-ci. Merci de
votre coopération.

CONFIDENTIALITY MESSAGE
This e-mail message is confidential and is intended for the exclusive use
of the addressee. Please note that, should this message be read by anyone
other than the addressee, his or her employee or the person responsible for
forwarding it to the addressee, it is strictly prohibited to disclose,
distribute, modify or reproduce the contents of this message, in whole or
in part. If the addressee cannot be reached or if you have received this
e-mail in error, please notify us immediately and delete this e-mail and
destroy all copies. Thank you for your cooperation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-discuss/attachments/20130308/4468570e/attachment-0001.html>