- Bc-gnso - lists.icann.org

New gTLD Program Update for Applicants | ICANN New gTLDs
by Marilyn Cade Aug. 6, 2012

Aug. 6, 2012

BC Members: As you will recall from our discussions in the BC, we are taking the perspective that ICANN needsto do special activities/informational support for applicants [or their designated agents, if they so designate]. I am pleased that our recommendation is the approach that ICANN is taking. I will ask to have the transcripts posted, so that all can follow discussions. Marilyn Cade, BC Chair=========================================================== http://newgtlds.icann.org/en/announcements-and-media/announcement-03aug12-e… gTLD Program Update for ApplicantsWebinar on the Initial Evaluation of New gTLD ApplicationsThe initial evaluation phase of the new generic top-level domain program began on 12 July 2012, and evaluation panels are now processing applications using the criteria in the Applicant Guidebook.Throughout the evaluation process, ICANN will provide regular updates to applicants. One method we plan to use is monthly webinar sessions.This first session will be set for 90 minutes with an opportunity for questions and answers. The sessions will provide updates on evaluation progress, program developments, and other topics of interest to new gTLD applicants. The sessions will be open but opportunity for questions will be reserved for applicants.The first webinar will provide:Information and updates on the various elements of the evaluation processEarly evaluation indications and implications for applicantsDiscussion of the "batching" issue and its impact on the timing of delegations.We hope you can join us for this session but if you can't, you'll find a recording of the webinar in the Announcements & Media section of the new gTLD microsite.Applicant Webinar: Start of New gTLD Initial Evaluation Date: 9 August 2012 Time: 12:00 – 13:30 UTC (5:00 – 6:30am PST) RSVP: If you would like to participate, please reserve a place by emailing newgtldcommunications(a)icann.org by 00:00 UTC on Wednesday, 8 August 2012 (5:00pm PST, Tuesday, 7 August 2012). We will send you an e-mail reminder before the event with log-in details.Please note that space is limited for this live webinar. Priority will be given to applicants on a first come, first served basis. If you are an applicant, we strongly encourage you to send your RSVP as soon as possible from the primary contact's email address. _______________________________________________ soac-infoalert mailing list soac-infoalert(a)icann.org https://mm.icann.org/mailman/listinfo/soac-infoalert

1 0

Alerts from the Secretariat: Period of 02 - 12 August 2012: Public Comment Periods Recently Opened and Approaching Closing Date
by Benedetta Rossi Aug. 6, 2012

Aug. 6, 2012

Dear BC Members, Please find below a link to the recently opened public comments which are approaching closing date: > > > http://www.icann.org/en/news/announcements/announcement-03aug12-en.htm > Period of 02 - 12 August 2012: Public Comment Periods Recently Opened and Approaching Closing Date > > 3 August 2012 > The Following Public Comment periods are Recently Opened or are approaching their Comment or Reply Period Close dates between 02 - 12 August 2012. As a member of the ICANN community, your timely feedback is critical to our accountability and transparency efforts. For your convenience, we have included direct links below to comments that will soon close. > > During the Reply period for Public Comments, participants should only address previous comments submitted and new posts concerning the topic should not be introduced. When constructing Replies, contributors are asked to cite the original poster's name, comment date, and any particular text that is pertinent. > > Please note that comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once that period ends. > > For more information please refer to the ICANN Public Comments page at: http://www.icann.org/en/news/public-comment > > Title > Comment Period Close Date [UTC Time] > Reply Period Close Date [UTC Time] > ICANN's FY 13 Security, Stability and Resiliency Framework > 2 July 2012 [23:59] > 3 August 2012 [23:59] > .name Registry Agreement Renewal > 2 August 2012 [23:59] > 23 August 2012 [23:59] > > Kind regards, Benedetta Rossi BC Secretariat

1 0

Bulk Transfer of Domain Names from Planet Online and Name For Name to NamesBeyond
by Marilyn Cade July 30, 2012

July 30, 2012

For a few days, the Chair will be forwarding the announcements. Our Secretariat is away for a few daysbut returning Wednesday and will resume forwarding of notices re public comments. Marilyn Cade, BC Chair============================================================ Subject: Bulk Transfer of Domain Names from Planet Online and Name For Name to NamesBeyond https://www.icann.org/en/news/announcements/announcement-27jul12-en.htmBulk Transfer of Domain Names from Planet Online and Name For Name to NamesBeyond27 July 2012ICANN has authorized the bulk transfer of Planet Online Corp's gTLD domain names to 2030138 Ontario Inc. dba NamesBeyond.com ("NamesBeyond") due to a compliance action taken by ICANN that resulted in the de-accreditation of registrar Planet Online Corp.ICANN has also authorized the bulk transfer of Name For Name, Inc.'s .com and .net names (which represent all gTLDs currently sponsored by Name For Name) to NamesBeyond as the result of the termination of Name For Name's registry-registrar agreement with Verisign Inc.The affected gTLD registries are processing the bulk transfers. Former registrant-customers of Planet Online and Name For Name should soon receive notices from NamesBeyond of the transfer. Customer questions about the transfer should be directed to NamesBeyond, using the contact details provided below. Additional information about these bulk transfers is provided below.FAQsQ. Why were these transfers authorized by ICANN?A. Planet Online's Registrar Accreditation Agreement (RAA) was terminated by ICANN on 6 July 2012 because of Planet Online's failure to comply with the requirements of the RAA. (The notice of termination is posted at http://www.icann.org/en/news/correspondence/burnette-to-zolfonoon-12jun12-e… [PDF, 222 KB]) As a result, Planet Online is no longer permitted to register or manage gTLD registrations.Name For Name's Registry-Registrar Agreement (RRA) with Verisign to register .com and .net names was terminated by Verisign on 16 July 2012. Name For Name currently has only five gTLD registrations under management, all in com and net. ICANN has notified Name For Name that it is in breach of its RAA with ICANN, which will be terminated on 2 August 2012 if the breaches are not cured. (The notice of breach is posted at http://www.icann.org/en/news/correspondence/burnette-to-taame-12jul12-en.pdf [PDF, 250 KB].)ICANN authorized these bulk transfers pursuant to the Inter-Registrar Transfer Policy to ensure that the registrant-customers of these registrars would not be harmed by their registrars' discontinued ability to manage the registrations.Q. How was the gaining registrar selected?A. ICANN followed its De-Accredited Registrar Transition Procedure (see http://www.icann.org/en/processes/registrars/de-accredited-registrar-transi… [PDF, 119 KB]) to identify a gaining registrar for Planet Online. Through this competitive process, NamesBeyond was selected. Due to the small size of Name For Name (5 domain names) NamesBeyond was asked to also accept these names.Q. Will NamesBeyond attempt to contact the affected registrants? What should former Planet Online and Name For Name customers do?A. Former customers of both registrars should receive a notice of the transfer and instructions for continued management of their names from NamesBeyond. Affected customers who do not receive notices from NamesBeyond should check the web page prepared by NamesBeyond for this bulk transfer at http://www.namesbeyond.com/planetonlinebulktransfer for additional information and contact details.Q. Do registrants have to pay a fee for the bulk transfer?A. No, there is no cost to registrants for the bulk transfer. Unlike a normal inter-registrar transfer, the registration terms will not be extended by a year. Accordingly, it is important to contact NamesBeyond if your registration will expire soon in order to maintain your registration.Q. Why do former Planet Online and Name For Name customers need to contact NamesBeyond?A. Neither Planet Online nor Name For Name participated in the bulk transfers therefore did not forward billing information to NamesBeyond. Accordingly, all registrants must provide updated billing information or transfer their names to other registrars.Q. What if affected registrants want to select a different registrar?A. Registrants will continue to be able to transfer their registrations to other registrars under the Inter-Registrar Transfer Policy (see http://www.icann.org/en/transfers/) Note that NamesBeyond may deny transfers for the first 60 days following the bulk transfer, at its discretion. This 60-day period is permissible under the Inter-Registrar Transfer Policy and is intended to help protect registrants. The registrant may need to renew names that will expire during the first 60 days following the transfer to NamesBeyond by contacting NamesBeyond at:+ 1 877 321 1356 (Toll Free) + 1 817 564 2994 + 1 215 750 2660 support(a)namesbeyond.com or info(a)namesbeyond.comQ. How will Planet Online and Name For Name customers know if a message purportedly from NamesBeyond is legitimate?A. The message from NamesBeyond should direct you to its website hosted at http://www.namesbeyond.com or refer you to other contact information provided above. If you believe a message purportedly from NamesBeyond is not legitimate, you should navigate to their web page directly, at http://www.namesbeyond.com/planetonlinebulktransfer. For general advice about avoiding phishing email messages, you may also wish to refer to the materials prepared by the Anti-Phishing Working Group (see http://www.antiphishing.org/consumer_recs.html)

1 0

ICANN Seeks Input on gTLD Batching | ICANN
by Marilyn Cade July 30, 2012

July 30, 2012

DEAR BC MEMBERSThe BC members had significant concerns about digital archery. As you will recall,the Board has listened to the community and the proposed approach is below. We had originally called for prioritization of IDNs and community facing applications; however,that view is not relevant with the new approach. Please share any views you have on this approach via our bc list. If necessary, we will arrange a conference call, but I would anticipate that we can determinecontinued BC support from our list interactions. Marilyn Cade, BC Chair ICANN Seeks Input on gTLD Batching | ICANN http://www.icann.org/en/news/announcements/announcement-29jul12-en.htm Opportunity for Community Input: Processing of New gTLD ApplicationsAt the Prague ICANN meeting, the newgTLD Program Committee decided to terminate Digital Archery, and instructedICANN staff to proceed with the initial evaluation of applications as quickly as possible. This evaluation is in progress based on a tentative project plan that foresees the processing of applications in a single batch, and simultaneous release of results. ICANN believes this approach is consistent with the constraints that various parts of the community have in performing their respective roles in the evaluation process, and with the feedback received from the community at the Prague meeting.

1 0

ICANN Survey - Tell Us What You Think: Meeting Guide Survey
by Marilyn Cade July 20, 2012

July 20, 2012

Dear BC Members Please consider responding in your individual capacity. >From my personal capacity, I give this a low rating for both useful information and effectiveness. It can be improved, and if so, it might be useful as a resource. ICANN staff/communications team seems not to have a good understanding of the community's needs. This might be a good opportunity to give them some useful feedback. Consider what would be useful to you -- as a newcomer, or as a seasoned attendee. Your responses will be direct to ICANN and I assume confidential. Thanks Marilyn Cade, BC Chair ============================== https://www.icann.org/en/news/announcements/announcement-3-13jul12-en.htmTe… Us What You Think: Meeting Guide Survey 13 July 2012ICANN staff publishes a printed meeting guide for each of its three annual public meetings. We are reviewing this practice and want your feedback. If you attended ICANN 44 in Prague, we ask that you please fill out this short survey on how useful you find the printed guide. Could the same information be provided in other ways, such as through a PDF on the meetings website? Would that be preferable?The survey contains seven questions, one broken into multiple parts so that we can evaluate your satisfaction with different components of the guide. Thank you for sharing your views with us.View the ICANN 44 Meeting Guide [PDF, 4.32 MB]Take the survey: https://www.surveymonkey.com/s/S8RJN7Z Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

ALERTS from the Secretariat: Period of 12 – 22 July 2012: Public Comment Periods Recently Opened and Approaching Closing Date
by Benedetta Rossi July 17, 2012

July 17, 2012

Dear BC Members, Please find below an ICANN announcement of relevance to the BC regarding the Public Comment Periods Recently Opened and Approaching Closing Date from 12-22 July 2012. http://www.icann.org/en/news/announcements/announcement-2-13jul12-en.htm *Period of 12 – 22 July 2012: Public Comment Periods Recently Opened and Approaching Closing Date* 13 July 2012 The Following Public Comment periods are*Recently Opened*or are approaching their*Comment or Reply Period Close*dates*between 12 – 22 July 2012*. As a member of theICANNcommunity, your timely feedback is critical to our accountability and transparency efforts. For your convenience, we have included direct links below to comments that will soon close. During the Reply period for Public Comments, participants should only address previous comments submitted and new posts concerning the topic should not be introduced. When constructing Replies, contributors are asked to cite the original poster's name, comment date, and any particular text that is pertinent. Please note that comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once that period ends. For more information please refer to theICANNPublic Comments page at:http://www.icann.org/en/news/public-comment *Title* *Comment Period Close Date [UTC Time]* *Reply Period Close Date [UTC Time]* WHOIS Technical Requirements Survey - Draft <http://www.icann.org/en/news/public-comment/draft-whois-requirements-survey…> 20 June 2012 [23:59] 16 July 2012 [23:59] Public Comment Solicitation for FY13 Community Travel Support Guidelines <http://www.icann.org/en/news/public-comment/travel-support-2013-01jun12-en.…> 22 June 2012 [23:59] 13 July 2012 [23:59] Interisle Consulting Group's WHOIS Proxy/Privacy Reveal & Relay Feasibility Survey <http://www.icann.org/en/news/public-comment/whois-pp-survey-04jun12-en.htm> 25 June 2012 [23:59] 16 July 2012 [23:59] PreliminaryGNSOIssue Report on the Protection of International Organization Names in New gTLDS <http://www.icann.org/en/news/public-comment/prelim-protection-io-names-04ju…> 25 June 2012 [23:59] 16 July 2012 [23:59] Security, Stability & Resiliency of theDNSReview Team (SSR RT) Final Report <http://www.icann.org/en/news/public-comment/ssr-rt-final-report-21jun12-en.…> 30 July 2012 [23:59] 29 August 2012 [23:59] Proposed Modifications toGNSOOperating Procedures <http://www.icann.org/en/news/public-comment/gnso-operating-procedures-2012-…> 30 July 2012 [23:59] 20 August 2012 [23:59] .name Registry Agreement Renewal <http://www.icann.org/en/news/public-comment/name-renewal-2012-03jul12-en.htm> 2 August 2012 [23:59] 23 August 2012 [23:59] -- Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org

1 0

Business Constituency comments on WHOIS Proxy/Privacy Reveal & Relay Feasibility Survey
by Steve DelBianco July 16, 2012

July 16, 2012

The Business Constituency (BC) offers the attached comments on survey results regarding feasibility of studying WHOIS Proxy/Privacy response to reveal and relay requests. Susan Kawaguchi was lead drafter for these comments, which were authorized by BC membership on 16-July-2012. -- Steve DelBianco Vice chair for policy coordination ICANN Business Constituency http://www.bizconst.org<http://Www.bizconst.org/>

1 0

for expedited review: BC comment on feasibility of a study of Privacy/Proxy relay and reveal
by Steve DelBianco July 15, 2012

July 15, 2012

As we decided on Wednesday's member call, the BC will file comments encouraging ICANN to follow-through on a study of relay and reveal practices of privacy/proxy providers. Susan Kawaguchi of Facebook prepared draft comments for the BC (attached). Please review over the weekend and use Track Changes if you make document edits. And please provide responses before noon (Eastern US Time) on Monday 16-July. Thanks to Susan for taking the lead on this critical issue for BC members. -- Steve DelBianco Executive Director NetChoice http://www.NetChoice.org and http://blog.netchoice.org +1.202.420.7482

2 1

Proposed Agenda for the GNSO Council Meeting 20 July 2012
by Benedetta Rossi July 14, 2012

July 14, 2012

Dear All, Please find the draft agenda for the GNSO Council Meeting 20 July 2012 at 11:00 UTC which is also posted on the Wiki at: *https://community.icann.org/display/gnsocouncilmeetings/Agenda+20-07-2012* And on the website at: http://gnso.icann.org/en/meetings/agenda-council-20jul12-en.htm Please let me know if you have any questions. Thank you. Kind regards, Glen *Proposed Agenda for the GNSO Council Meeting 20 July 2012* This agenda was established according to the GNSO Council Operating Procedures approved 22 September 2011 for the GNSO Council and updated. http://gnso.icann.org/council/gnso-operating-procedures-16dec11-en.pdf For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. _Meeting Times 11:00 UTC <http://tinyurl.com/ccz4c9u> _*http://tinyurl.com/ccz4c9u* Coordinated Universal Time 11:00 UTC 04:00 Los Angeles; 07:00 Washington; 12:00 London; 13:00 Paris; 20:00 Tokyo. Dial-in numbers will be sent individually to Council members. Councilors should notify the GNSO Secretariat in advance if a dial out call is needed. *GNSO Council meeting audiocast * *http://stream.icann.org:8000/gnso.m3u* *_Item 1: Administrative matters (10 minutes)_* 1.1 Roll Call 1.2 Statement of interest updates 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Draft Minutes of the GNSO Council meeting 27 June 2012 will be approved on 1.5. GNSO Pending Projects List http://gnso.icann.org/meetings/pending-projects-list.pdf * Review main changes. * Comments and/or questions. *_Item 2: Consent agenda (5 minutes)_* A consent agenda item is being added as a standard agenda item to provide for a simplified process to obtain Council approval on specific tasks. No items on the consent agenda. *_Item 3: Final Elections procedure (10 minutes)_* At the Prague meeting, the proposed election procedure was shown to the Council. A refined version <http://gnso.icann.org/en/issues/gnso-council-chair-election-13jul12-en.pdf> was sent to the list. This item is to discuss and approve this procedure, so that it can be started. 3.1 Presentation of procedure (Stéphane Van Gelder) http://gnso.icann.org/en/issues/gnso-council-chair-election-13jul12-en.pdf 3. 2 Discussion 3. 3 Call to approve procedure. *_Item 4: Thick Whois PDP (10 minutes)_* As the .com agreement has now been renewed (see http://www.icann.org/en/groups/board/documents/resolutions-23jun12-en.htm#2) the Council may not want to wait until November before a Drafting Team is formed to develop a charter for the 'thick' Whois Policy Development Process Working Group (PDP WG). 4.1 Update from staff (X Y) 4. 2 Discussion 4. 3 Next steps. *_Item 5: Whois RT Final Report (10 minutes)_* Considering the Board resolution on the Whois Review Team Final Report and the Board's call for input from the GNSO by August 31, 2012, how should the Council respond? 5.1 Update from staff (X Y) 5. 2 Discussion 5. 3 Next steps. *_Item 6: GNSO Review (10 minutes)_* At the wrap-up in Prague, there was discussion around forming a small group to examine possible actions ahead of the 2013 ICANN bylaws-mandated review. This is a discussion item to determine whether the Council wishes to move ahead in this way. 6.1 Update from staff (X Y) 6. 2 Discussion 6. 3 Next steps. *_Item 7: Impact of new gTLD program on existing GNSO structure (10 minutes)_* The new gTLD program may impact the GNSO's Contracted Parties. This item aims to initiate a discussion of potential issues to look at as the new gTLD program comes online and the Registry and Registrar stakeholder groups are affected by this. 7.1 Discussion *_Item 8: Management of work (10 minutes)_* Recent discussions on the Council list have raised concerns about the volume of documents published prior to an ICANN meeting and how these can best be managed by the volunteer community that makes up the GNSO Council as it struggles to read a substantial amount of reports and other documents in order to better inform its own decision making processes with regards to policy. 8.1 Discussion *_Item 9: Fake Renewal Notices (10 minutes)_* The GNSO Council requested that a small group prepare a request for information concerning Fake Renewal Notices for the Registrar Stakeholder Group to help inform its deliberations on the Registration Abuse Policies Working Group (RAP WG) Recommendation on Fake Renewal Notices (#2). The drafting team submitted its report to the GNSO Council on 6 March 2012. Following a presentation of the report to the GNSO Council at the ICANN Meeting in Costa Rica, the GNSO Council decided to put the report out for public comment. A public comment forum was opened (see http://www.icann.org/en/news/public-comment/fake-renewal-notices-report-21m…) and has now closed. At its last meeting, the GNSO Council requested the Drafting Team (DT) to review the comments received, update the report if deemed appropriate and report back accordingly. The DT has reviewed the comments received and submitted its updated report to the GNSO Council on 21 June 2012 (see http://gnso.icann.org/issues/frn/fake-renewal-notices-updated-report-20jun1…) 9.1 Presentation of updated Fake Renewal Notices Report (Mikey O'Connor) 9. 2 Discussion 9. 3 Next steps *_Item 10: Internationalised Registration Data WG Final Report (10 minutes)_* During its June 27 Open Meeting, the GNSO Council approved a motion <http://gnso.icann.org/en/resolutions#20120627-1> to deliver the IRD Final Report to the ICANN Board and to "review the recommendations in the Report and shall provide to the Board its advice with regard to those recommendations that may have policy implications". This agenda item is to discuss next steps in light of this commitment, and to determine how the Council wishes to review and report on the IRD recommendations that may have policy implications. 10.1 Update from Staff (Margie Milam). 10.1 Discussion. 10.1 Next steps. *_Item 11: Any Other Business (5 minutes) _* *Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X,**Section 3)* 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A <http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." *Appendix 2: Absentee Voting Procedures (**GNSO Operating Procedures 4.4 <http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>**) * 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting‟s adjournment. In exceptional circumstances,announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) ---------------------------------------------------------------------------- Local time between March and October, Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 11:00 ---------------------------------------------------------------------------- California, USA (PDT <http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+1DST 04:00 New York/Washington DC, USA (EDT) UTC-5+1DST 07:00 Buenos Aires, Argentina (ART <http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 08:00 Montevideo, Uruguay (UYT <http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+0DST 08:00 London, United Kingdom (BST) UTC+1DST 12:00 Abuja,Nigeria (WAT <http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 12:00 Tunis, Tunisia (CET) UTC+1+0DST 12:00 Bonn, Germany (CEST) UTC+1+1DST 13:00 Paris, France (CEST) UTC+1+1DST 13:00 Ramat Hasharon, Israel(IST <http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 14:00 Karachi, Pakistan (PKT <http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html>) UTC+5+0DST 16:00 Beijing/Hong Kong, China _(HKT_ ) UTC+8+0DST 19:00 Tokyo, Japan (JST <http://www.timeanddate.com/library/abbreviations/timezones/asia/jst.html>) UTC+9+0DST 20:00 Wellington, New Zealand (NZDT <http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html>) UTC+12+0DST 23:00 ---------------------------------------------------------------------------- The DST starts/ends on last Sunday of October 2012, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.comand *http://tinyurl.com/ccz4c9u* Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org <http://gnso.icann.org>

1 0

Agenda: BC Members Pre Council Call
by Benedetta Rossi July 12, 2012

July 12, 2012

BC Members, Please find attached the agenda for the upcoming BC Members Pre Council Call taking place on Tuesday July 17th at 11 a.m. EDT. Please let me know if you need a dial out, Thank you, Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat(a)icann.org

1 0