January 2016 - ALAC - lists.icann.org

Re: [ALAC] [ALAC-Announce] Call for Volunteers: GNSO Policy Development Process (PDP) Working Group on New gTLD Subsequent Procedures
by Cheryl Langdon-Orr Feb. 3, 2016

Feb. 3, 2016

Hi all please note I am already subscribed as a Member of the WG noting my association with NCSG in my application, I am however *more* than happy to represent the interests and concerns or act in a formal capacity) of ALAC and At-Large in this important WG... Just let me know... Not the application only gave 1 choice for Association, but I am sure we can adjust manually on lists and records if needs be... I am not endorsed by NCSG they simply sent out an open call for Members to participate... *Cheryl Langdon-O**rr ... *(CLO) about.me/cheryl.LangdonOrr [image: Cheryl Langdon-Orr on about.me] <http://about.me/cheryl.LangdonOrr> On 29 January 2016 at 08:29, staff(a)atlarge.icann.org < staff(a)atlarge.icann.org> wrote: > > Call for Volunteers: GNSO Policy Development Process (PDP) Working Group > on New gTLD Subsequent Procedures > <https://www.icann.org/news/announcement-2016-01-27-en#> > <https://www.icann.org/news/announcement-2016-01-27-en#> > <https://www.icann.org/news/announcement-2016-01-27-en#> > <https://www.icann.org/news/announcement-2016-01-27-en#> > <https://www.icann.org/news/announcement-2016-01-27-en#> > <https://www.icann.org/news/announcement-2016-01-27-en#> > In Brief > > The Generic Names Supporting Organization (GNSO) Council seeks volunteers > to serve on a PDP Working Group (WG) to develop recommendations for New > generic Top Level Domains (gTLDs) Subsequent Procedures. The GNSO Council > approved the WG's charter > <http://gnso.icann.org/en/drafts/igo-ingo-crp-access-charter-24jun14-en.pdf> > [PDF, 603 KB] on 21 January 2016, tasking this PDP to determine whether > changes or adjustments to the existing policy recommendations on the > Introduction of New Generic Top-Level Domains are needed. > What This Team Will Do > > The New gTLD Subsequent Procedures PDP Working Group (WG) is tasked with > calling upon the community's collective experiences from the 2012 New gTLD > Program round to determine what, if any, changes may need to be made to the > existing *Introduction of New Generic Top-Level Domains > <http://gnso.icann.org/en/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm>* > policy recommendations from 8 August 2007. As the original policy > recommendations as adopted by the GNSO Council and ICANN Board have "been > designed to produce a systemized and ongoing mechanisms for applicants to > propose new top-level domains", those policy recommendations remain in > place for subsequent rounds of the New gTLD Program unless the GNSO > Council would decide to modify those policy recommendations via this PDP. > The work of this PDP WG follows the efforts of the New gTLD Subsequent > Procedures Discussion Group (DG), which identified a set of issues/subjects > for a future PDP WG to consider in their deliberations and recommend > whether to: > > - Clarify, amend or override existing policy principles, > recommendations, and implementation guidance; > - Develop new policy recommendations; > - Supplement or develop new implementation guidance. > > As part of the PDP WG deliberations, the PDP WG should consider at a > minimum, the subjects detailed in the Final Issue Report. These subjects > have been organized in groupings suggested by the DG that may facilitate > deliberations on related subjects. However, additional work methods, such > as those described in the Final Issue Report, or other methods identified > by the PDP WG may be more appropriate to undertake the work. > > In addition to the work of the PDPWG, a number of new gTLD review efforts > are underway which may have an impact on the work of this PDP WG. > Therefore, this PDP WG should not be limited to the issues identified by > the DG and should take into account the findings from the parallel efforts > external to the PDP WG. > How This Team Will Work > > ICANN WGs use transparent, open processes. The meetings of this PDP WG > will be recorded, and the recordings will be made available to the public. > The mailing list for the PDP WG will be archived publicly. The group will > collaborate using a public workspace for draft materials and all final work > products and milestones will be documented on the WG's wiki > <https://community.icann.org/display/NGSPP/New+gTLD+Subsequent+Procedures+PD…>. > The PDP WG is expected to follow the GNSO Working Group Guidelines > <http://gnso.icann.org/en/council/annex-1-gnso-wg-guidelines-08apr11-en.pdf> > [PDF, 349 KB] as well as the GNSOPDP Manual > <http://gnso.icann.org/en/council/annex-2-pdp-manual-24jun15-en.pdf> > [PDF, 260 KB]. > How to Participate > > There are two ways to volunteer: > > - *Individual Members* – anyone interested can volunteer to join the > PDP WG as a WG member, regardless of whether they are members of the > ICANN community. Members are expected to actively contribute to > mailing list conversations as well as meetings – it is anticipated that the > PDP WG will at a minimum meet on a weekly basis via teleconference. > Members are expected to provide essential input to the process. Members > will be required to provide a Statement of Interests (SOI > <https://community.icann.org/display/gnsosoi/New+SOIs>). > - *Mailing list observers* – for those who are merely interested in > monitoring the WG's conversations, there is the possibility to sign up > as a mailing list "observer" which offers read-only access to the mailing > list. Mailing list observers will not be permitted to post, will not > receive invitations to the various meetings or calls of the WG and > will not have to complete a Statement of Interest. At any point in time, a > mailing list observer can join the WG as a member simply by informing > the GNSO Secretariat. > > In addition, there will be opportunities to provide input through public > consultations and public comment processes that the PDP WG is expected to > organize. > How to Join > > If you are interested in joining the WG as an individual participant or > mailing list observer, please fill in the sign up form > <http://goo.gl/forms/FRNZ4pSQl9> or send the PDF document > <http://gnso.icann.org/en/issues/new-gtlds/subsequent-procedures-pdp-27jan16…> > [PDF, 76 KB] filled in to the GNSO Secretariat <gnso-secs(a)icann.org>. > > All members and observers will be listed on the PDP WG's wiki page. > Next Steps > > In its motion, the GNSO Council directed that this call for volunteers be > circulated as widely as possible in order to ensure broad representation > and participation in the WG. This call will remain open until the PDP WG > convenes for the first time. At this juncture, it is anticipated that the > PDP WG may convene online in late February 2016. Following that, regular > online meetings will be scheduled in accordance with the PDP WG's work > plan, which it is expected to develop as one of its first tasks. > Further Information and Preparation > > For those interested in volunteering for this effort, you are strongly > encouraged to review the following materials prior to the first meeting of > the PDP WG. > > - The Final Issue Report > <http://gnso.icann.org/en/issues/new-gtlds/subsequent-procedures-final-issue…> > [PDF, 1.38 MB] > - The approved charter > <http://gnso.icann.org/en/issues/new-gtlds/subsequent-procedures-charter-21j…> > [PDF, 196 KB] > - Materials available at the PDP WG's wiki > <https://community.icann.org/display/NGSPP/New+gTLD+Subsequent+Procedures+PD…>, > such as the 2007 Final Report and other relevant information. > > Background > > In 2005, the Generic Names Supporting Organization (GNSO) began a Policy > Development Process (PDP) to consider the introduction of new gTLDs. The > two-year PDP process resulted in a set of 19 GNSO policy recommendations > for implementing new gTLDs. In order to implement the policy > recommendations of the GNSO, a number of draft Applicant Guidebooks > (AGBs) were developed by ICANN staff in consultation with the > community.In June 2011, ICANN's Board of Directors approved the final AGB > and authorized the launch of the New gTLD Program. > > The New gTLD Program application window opened on 12 January 2012 and a > total of 1930 complete applications were received. The first set of Initial > Evaluation results were released on 22 March 2013, followed by the first > set of new gTLD delegations on 21 October 2013. > > All applications have now completed the evaluation process and as of mid > January 2016, there are nearly 900 gTLDs delegated and approximately 450 > applications still proceeding through the remaining steps of the program. > Although the 2012 round is ongoing, efforts to examine the round have > already begun, which included the creation of the GNSO New gTLD > Subsequent Procedures Discussion Group (DG) > <http://gnso.icann.org/en/group-activities/inactive/2015/non-pdp-new-gtld>. > The DG was created by the GNSO Council to discuss the experiences gained > from the 2012 round of the New gTLD Program and to identify subjects that > might lead to changes or adjustments for subsequent application procedures. > The DG prepared its final deliverables, which included a set of subjects > that it anticipated would be analyzed in detail in the context of an Issue > Report. On 24 June 2015 the GNSO Council passed a resolution requesting > the drafting of a Preliminary Issue Report on New gTLD Subsequent > Procedures. > > In accordance with the PDP Rules, the Preliminary Issue Report was > published for public comment on 31 August 2015. Following review of the > public comments received, the Staff Manager updated the Issue Report > accordingly and submitted the Final Issue Report to the GNSO Council for > its consideration. The GNSO Council officially initiated the PDP on New > gTLD Subsequent Procedures on 17 December 2015, followed by adoption of > the PDP WG's charter on 21 January 2016. > > _______________________________________________ > ALAC-Announce mailing list > ALAC-Announce(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/alac-announce > > At-Large Official Site: http://www.atlarge.icann.org >

8 10

Reminder - ALAC Monthly Call
by ICANN At-Large Staff Jan. 26, 2016

Jan. 26, 2016

If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number. Please remember that it is now possible to connect your audio via the AC room, without using your telephone. You need a stable internet connection. If you would like a reminder of how to connect please let staff know. Si necesita una llamada a su telefono, por favor póngase en contacto con el personal de At-Large en staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> con su número preferido. Por favor, recuerde que es posible conectar el audio a través de la Adobe Connect , sin necesidad de utilizar su teléfono. Se necesita una conexión a Internet estable . Si desea un recordatorio de cómo conectar por favor que el personal sepa . Si vous avez besoin d'un dial-out, merci de le communiquer au personnel At-Large à staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> avec votre numéro d'appel préféré. Nous vous rappelons que vous pouvez désormais utiliser l'audio de l'Adobe Connect room afin de vous connecter sans utiliser votre ligne téléphonique. Il vous faut une connexion internet stable. Merci de nous confirmer votre participation et dial-out - si nécessaire - ainsi que votre numéro à: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Если вам требуется для набора номера, пожалуйста, свяжитесь с коллективом At-Large по staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> с выбранным номером. Пожалуйста, помните, что это теперь можно подключить аудио через комнату переменного тока, без использования телефона. Вы должны стабильное подключение к интернету. Если вы хотели бы напоминание о том, как подключить, пожалуйста, сообщите сотрудники знают. **************** Dear All, The next ALAC Monthly call is scheduled on Tuesday 26 January 2016 from 04:00-06:00 UTC. Further to the Doodle poll, 3 times were identified as rotating times moving forward: - 04:00 - 06:00 UTC - 12:00 - 14:00 UTC - 21:00 - 23:00 UTC A 4th slot of 14:00-16:00 UTC was considered as well but will not be included. A schedule of the 2016 calls will be presented during the meeting - the calls will remain on the 4th Tuesday of the month. For other times: http://tinyurl.com/j58l4sx The agenda and call details are available at: https://community.icann.org/x/SAF1Aw Adobe Connect Room: http://icann.adobeconnect.com/alac Conference ID's: English: 1638 Spanish: 1738 French: 1838 Russian: 2138 Dial-in numbers: http://adigo.com/icann/ If you are unable to attend the call please send an email indicating your absence and we will note this information on the agenda. If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann <https://www.facebook.com/icannatlarge>atlarge <https://www.facebook.com/icannatlarge> Twitter: @ <https://twitter.com/ICANNAtLarge>ICANNAtLarge <https://twitter.com/ICANNAtLarge> On 07/01/2016 17:50, "alac-bounces(a)atlarge-lists.icann.org<mailto:alac-bounces@atlarge-lists.icann.org> on behalf of Alan Greenberg" <alac-bounces(a)atlarge-lists.icann.org<mailto:alac-bounces@atlarge-lists.icann.org> on behalf of alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>> wrote: The time has come to try to select meeting times for our ALAC calls for the year. As had been the past practice, it will be held on the 4th Tuesday of each month (with exceptions for ICANN meetings). Please fill in the Doodle at http://doodle.com/poll/u2qhf5tidupa5e5f as soon as possible. Ignore the DATE, it is the day of the week and time that counts. If you know you are not available for a specific meeting (such as the January one), please note that in a comment, but fill in the Doodle for the general case. Note that each Doodle time-slot is for the full two hour meeting starting at the designated time. For ALAC Members and Liaisons in particular, PLEASE BE FLEXIBLE. We will try to avoid meetings in the dead of night, but with members spanning the world, that will not always be possible and we will do our best to limit the number of times any individual member needs to participate at really awkward times. It is not fair to force some people to always bear the pain. If you have a particular situation that cannot be easily expressed in the Doodle, please send a private note to me and Gisella. Alan _______________________________________________ ALAC mailing list ALAC(a)atlarge-lists.icann.org<mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+( A LAC)

12 14

Re: [ALAC] Reminder - ALAC Monthly Call
by Alan Greenberg Jan. 25, 2016

Jan. 25, 2016

Perhaps I can answer even if I am not Staff. 21:00 WAS included. The original message is at the end of this thread and says we will rotate among 04:00, 12:00 and 21:00. For this meeting, a CCWG Accountability meeting overlaps with the 21:00 slot. 12:00 also had a conflict. The times were chosen based on (not necessarily in this order): - the number of people who could attend; - an attempt to restrict the number of people and times where the meeting was right in the middle of typical sleep hours; - an attempt to ensure that all regions could be reasonably (if not perfectly) represented; - a definite rotation over different times of the day, the need for all Liaisons to be present; - the number of replies where people answered "if need be". Of the 17 people for whom the meetings are mandatory (the ALAC Members + formal Liaisons to the GNSO, ccNSO and SSAC), no time slot had more than 15 people who said they could attend. All of the selected ones had either 14 or 15. Alan At 25/01/2016 06:20 AM, Seun Ojedeji wrote: >Hello Staff, > >While i have noted the time for the next call, I >like to state that I am not sure i understand >how the timings are figured out. Looking at the >doodle result at the following url, i have the following observation: > ><http://doodle.com/poll/u2qhf5tidupa5e5f>http://doodle.com/poll/u2qhf5tidupa5e5f > >1. 19:00 to 21:00 UTC had the highest votes but was not included >2. There are other timing that has more votes than the ones selected > >A clarification would be appreciated as it does >seem the doodle result was not quite in sync with the final outcome. > >Regards > >On Mon, Jan 25, 2016 at 11:18 AM, ICANN At-Large >Staff <<mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org> wrote: >If you require a dial-out please contact >At-Large staff at ><mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org >with your preferred number. >Please remember that it is now possible to >connect your audio via the AC room, without >using your telephone. You need a stable internet >connection. If you would like a reminder of how >to connect please let staff know. > > >Si necesita una llamada a su telefono, por favor >pÃ³ngase en contacto con el personal de At-Large >en ><mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org >con su nÃºmero preferido. > >Por favor, recuerde que es posible conectar el >audio a travÃ©s de la Adobe Connect , sin >necesidad de utilizar su telÃ©fono. Se necesita >una conexiÃ³n a Internet estable . Si desea un >recordatorio de cÃ³mo conectar por favor que el personal sepa . > > > >Si vous avez besoin d'un dial-out, merci de le >communiquer au personnel At-Large >Ã ><mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org >avec votre numÃ©ro d'appel prÃ©fÃ©rÃ©. > >Nous vous rappelons que vous pouvez dÃ©sormais >utiliser l'audio de l'Adobe Connect room afin de >vous connecter sans utiliser votre ligne >tÃ©lÃ©phonique. Il vous faut une connexion internet stable. >Merci de nous confirmer votre participation et >dial-out - si nÃ©cessaire - ainsi que votre >numÃ©ro Ã : <mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org > >ÐÑÐ»Ð¸ Ð²Ð°Ð¼ ÑÑÐµÐ±ÑÐµÑÑÑ Ð´Ð»Ñ >Ð½Ð°Ð±Ð¾ÑÐ° Ð½Ð¾Ð¼ÐµÑÐ°, Ð¿Ð¾Ð¶Ð°Ð»ÑÐ¹ÑÑÐ°, >ÑÐ²ÑÐ¶Ð¸ÑÐµÑÑ Ñ ÐºÐ¾Ð»Ð»ÐµÐºÑÐ¸Ð²Ð¾Ð¼ >At-Large Ð¿Ð¾ ><mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org >Ñ Ð²ÑÐ±ÑÐ°Ð½Ð½ÑÐ¼ Ð½Ð¾Ð¼ÐµÑÐ¾Ð¼. >ÐÐ¾Ð¶Ð°Ð»ÑÐ¹ÑÑÐ°, Ð¿Ð¾Ð¼Ð½Ð¸ÑÐµ, ÑÑÐ¾ >ÑÑÐ¾ ÑÐµÐ¿ÐµÑÑ Ð¼Ð¾Ð¶Ð½Ð¾ >Ð¿Ð¾Ð´ÐºÐ»ÑÑÐ¸ÑÑ Ð°ÑÐ´Ð¸Ð¾ ÑÐµÑÐµÐ· >ÐºÐ¾Ð¼Ð½Ð°ÑÑ Ð¿ÐµÑÐµÐ¼ÐµÐ½Ð½Ð¾Ð³Ð¾ ÑÐ¾ÐºÐ°, >Ð±ÐµÐ· Ð¸ÑÐ¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ >ÑÐµÐ»ÐµÑÐ¾Ð½Ð°. ÐÑ Ð´Ð¾Ð»Ð¶Ð½Ñ >ÑÑÐ°Ð±Ð¸Ð»ÑÐ½Ð¾Ðµ Ð¿Ð¾Ð´ÐºÐ»ÑÑÐµÐ½Ð¸Ðµ Ðº >Ð¸Ð½ÑÐµÑÐ½ÐµÑÑ. ÐÑÐ»Ð¸ Ð²Ñ ÑÐ¾ÑÐµÐ»Ð¸ >Ð±Ñ Ð½Ð°Ð¿Ð¾Ð¼Ð¸Ð½Ð°Ð½Ð¸Ðµ Ð¾ ÑÐ¾Ð¼, ÐºÐ°Ðº >Ð¿Ð¾Ð´ÐºÐ»ÑÑÐ¸ÑÑ, Ð¿Ð¾Ð¶Ð°Ð»ÑÐ¹ÑÑÐ°, >ÑÐ¾Ð¾Ð±ÑÐ¸ÑÐµ ÑÐ¾ÑÑÑÐ´Ð½Ð¸ÐºÐ¸ Ð·Ð½Ð°ÑÑ. > > >**************** >Dear All, >The next ALAC Monthly call is scheduled on >Tuesday 26 January 2016 from 04:00-06:00 UTC. >Further to the Doodle poll, 3 times were identified as rotating times >moving forward: >- 04:00 - 06:00 UTC >- 12:00 - 14:00 UTC >- 21:00 - 23:00 UTC >A 4th slot of 14:00-16:00 UTC was considered as well but will not be included. >A schedule of the 2016 calls will be presented >during the meeting - the calls will remain on the 4th Tuesday of the month. >For other times: ><http://tinyurl.com/j58l4sx>http://tinyurl.com/j58l4sx > >The agenda and call details are available at: ><https://community.icann.org/x/SAF1Aw>https://community.icann.org/x/SAF1Aw >Adobe Connect Room: ><http://icann.adobeconnect.com/alac>http://icann.adobeconnect.com/alac >Conference ID's: >English: 1638 >Spanish: 1738 >French: 1838 >Russian: 2138 >Dial-in numbers: <http://adigo.com/icann/>http://adigo.com/icann/ >If you are unable to attend the call please send an email indicating your >absence and we will note this information on the agenda. >If you require a dial-out please contact At-Large staff at: ><mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org >Thank you. >Regards, > >Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie >Peregrine, Terri Agnew and YeÅim Nazlar >ICANN Policy Staff in support of the At-Large Community >E-mail: <mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org >Facebook: <http://www.facebook.com/icann>www.facebook.com/icann ><https://www.facebook.com/icannatlarge>atlarge ><<https://www.facebook.com/icannatlarge>https://www.facebook.com/icannatlarge> > >Twitter: @ ><<https://twitter.com/ICANNAtLarge%3EICANNAtLarge>https://twitter.com/ICANNAtLarge>ICANNAtLarge > ><https://twitter.com/ICANNAtLarge> > > > > >On 07/01/2016 17:50, >"<mailto:alac-bounces@atlarge-lists.icann.org>alac-bounces(a)atlarge-lists.icann.org >on behalf of >Alan Greenberg" ><<mailto:alac-bounces@atlarge-lists.icann.org>alac-bounces(a)atlarge-lists.icann.org >on behalf of ><mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: > >The time has come to try to select meeting times for our ALAC calls >for the year. As had been the past practice, it will be held on the >4th Tuesday of each month (with exceptions for ICANN meetings). >Please fill in the Doodle at ><http://doodle.com/poll/u2qhf5tidupa5e5f>http://doodle.com/poll/u2qhf5tidupa5e5f > >as soon as possible. Ignore the DATE, it is the day of the week and >time that counts. If you know you are not available for a specific >meeting (such as the January one), please note that in a comment, but >fill in the Doodle for the general case. >Note that each Doodle time-slot is for the full two hour meeting >starting at the designated time. >For ALAC Members and Liaisons in particular, PLEASE BE FLEXIBLE. We >will try to avoid meetings in the dead of night, but with members >spanning the world, that will not always be possible and we will do >our best to limit the number of times any individual member needs to >participate at really awkward times. It is not fair to force some >people to always bear the pain. >If you have a particular situation that cannot be easily expressed in >the Doodle, please send a private note to me and Gisella. >Alan >_______________________________________________ >ALAC mailing list ><mailto:ALAC@atlarge-lists.icann.org>ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac >At-Large Online: <http://www.atlarge.icann.org>http://www.atlarge.icann.org >ALAC Working Wiki: ><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+( > >A >LAC) > > > > > >_______________________________________________ >ALAC mailing list ><mailto:ALAC@atlarge-lists.icann.org>ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac >At-Large Online: <http://www.atlarge.icann.org>http://www.atlarge.icann.org >ALAC Working Wiki: ><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… > > > > >-- >------------------------------------------------------------------------ >Seun Ojedeji, >Federal University Oye-Ekiti >web: <http://www.fuoye.edu.ng>http://www.fuoye.edu.ng >Mobile: +2348035233535 >alt email:<http://goog_1872880453> ><mailto:seun.ojedeji@fuoye.edu.ng>seun.ojedeji(a)fuoye.edu.ng > >Bringing another down does not take you up - think about your action! > >_______________________________________________ >ALAC mailing list >ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: http://www.atlarge.icann.org >ALAC Working Wiki: >https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…

2 1

Re: [ALAC] Reminder - ALAC Monthly Call
by Wafa Dahmani Jan. 25, 2016

Jan. 25, 2016

Dear all, Please need dial out +21698349943. Regards envoyer par huawei telephone Le 25 janv. 2016 11:18, ICANN At-Large Staff <staff(a)atlarge.icann.org> a écrit : > > If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org with your preferred number. > > Please remember that it is now possible to connect your audio via the AC room, without using your telephone. You need a stable internet connection. If you would like a reminder of how to connect please let staff know. > > > > Si necesita una llamada a su telefono, por favor póngase en contacto con el personal de At-Large en staff(a)atlarge.icann.org con su número preferido. > > Por favor, recuerde que es posible conectar el audio a través de la Adobe Connect , sin necesidad de utilizar su teléfono. Se necesita una conexión a Internet estable . Si desea un recordatorio de cómo conectar por favor que el personal sepa . > > > > > > Si vous avez besoin d'un dial-out, merci de le communiquer au personnel At-Large à staff(a)atlarge.icann.org avec votre numéro d'appel préféré. > > Nous vous rappelons que vous pouvez désormais utiliser l'audio de l'Adobe Connect room afin de vous connecter sans utiliser votre ligne téléphonique. Il vous faut une connexion internet stable. > > Merci de nous confirmer votre participation et dial-out - si nécessaire - ainsi que votre numéro à: staff(a)atlarge.icann.org > > > > Если вам требуется для набора номера, пожалуйста, свяжитесь с коллективом At-Large по staff(a)atlarge.icann.org с выбранным номером. > > Пожалуйста, помните, что это теперь можно подключить аудио через комнату переменного тока, без использования телефона. Вы должны стабильное подключение к интернету. Если вы хотели бы напоминание о том, как подключить, пожалуйста, сообщите сотрудники знают. > > > > **************** > > Dear All, > > The next ALAC Monthly call is scheduled on Tuesday 26 January 2016 from 04:00-06:00 UTC. > > Further to the Doodle poll, 3 times were identified as rotating times > moving forward: > - 04:00 - 06:00 UTC > - 12:00 - 14:00 UTC > - 21:00 - 23:00 UTC > > A 4th slot of 14:00-16:00 UTC was considered as well but will not be included. > > A schedule of the 2016 calls will be presented during the meeting - the calls will remain on the 4th Tuesday of the month. > > For other times: > http://tinyurl.com/j58l4sx > > > The agenda and call details are available at: > https://community.icann.org/x/SAF1Aw > > Adobe Connect Room: > http://icann.adobeconnect.com/alac > > Conference ID's: > English: 1638 > Spanish: 1738 > French: 1838 > Russian: 2138 > > Dial-in numbers: http://adigo.com/icann/ > > If you are unable to attend the call please send an email indicating your > absence and we will note this information on the agenda. > > If you require a dial-out please contact At-Large staff at: > staff(a)atlarge.icann.org > > Thank you. > Regards, > > > Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie > Peregrine, Terri Agnew and Yeşim Nazlar > ICANN Policy Staff in support of the At-Large Community > E-mail: staff(a)atlarge.icann.org > Facebook: www.facebook.com/icann > <https://www.facebook.com/icannatlarge>atlarge > <https://www.facebook.com/icannatlarge> > Twitter: @ <https://twitter.com/ICANNAtLarge>ICANNAtLarge > <https://twitter.com/ICANNAtLarge> > > > > >>> On 07/01/2016 17:50, "alac-bounces(a)atlarge-lists.icann.org on behalf of >>> Alan Greenberg" <alac-bounces(a)atlarge-lists.icann.org on behalf of >>> alan.greenberg(a)mcgill.ca> wrote: >>> >>>> The time has come to try to select meeting times for our ALAC calls >>>> for the year. As had been the past practice, it will be held on the >>>> 4th Tuesday of each month (with exceptions for ICANN meetings). >>>> >>>> Please fill in the Doodle at http://doodle.com/poll/u2qhf5tidupa5e5f >>>> as soon as possible. Ignore the DATE, it is the day of the week and >>>> time that counts. If you know you are not available for a specific >>>> meeting (such as the January one), please note that in a comment, but >>>> fill in the Doodle for the general case. >>>> >>>> Note that each Doodle time-slot is for the full two hour meeting >>>> starting at the designated time. >>>> >>>> For ALAC Members and Liaisons in particular, PLEASE BE FLEXIBLE. We >>>> will try to avoid meetings in the dead of night, but with members >>>> spanning the world, that will not always be possible and we will do >>>> our best to limit the number of times any individual member needs to >>>> participate at really awkward times. It is not fair to force some >>>> people to always bear the pain. >>>> >>>> If you have a particular situation that cannot be easily expressed in >>>> the Doodle, please send a private note to me and Gisella. >>>> >>>> Alan >>>> >>>> _______________________________________________ >>>> ALAC mailing list >>>> ALAC(a)atlarge-lists.icann.org >>>> https://atlarge-lists.icann.org/mailman/listinfo/alac >>>> >>>> At-Large Online: http://www.atlarge.icann.org >>>> ALAC Working Wiki: >>>> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+( >>>> A >>>> LAC) >>> >>> >> >>

1 0

Meeting Invitation - ALAC Monthly Call
by ICANN At-Large Staff Jan. 22, 2016

Jan. 22, 2016

Dear All, Happy New Year 2016! Further to the Doodle poll, 3 times were identified as rotating times moving forward: - 04:00 - 06:00 UTC - 12:00 - 14:00 UTC - 21:00 - 23:00 UTC A 4th slot of 14:00-16:00 UTC was considered as well but will not be included. Due to the current call schedule on Tuesday 26th January 2016, the ALAC call will be held from 04:00-06:00 UTC. A schedule of the 2016 calls will be presented during the meeting - the calls will remain on the 4th Tuesday of the month. For other times: http://tinyurl.com/j58l4sx The agenda (to be updated) and call details are available at: https://community.icann.org/x/SAF1Aw Adobe Connect Room: http://icann.adobeconnect.com/alac Conference ID's: English: 1638 Spanish: 1738 French: 1838 Russian: 2138 Dial-in numbers: http://adigo.com/icann/ If you are unable to attend the call please send an email indicating your absence and we will note this information on the agenda. If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org Thank you. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org Facebook: www.facebook.com/icann <https://www.facebook.com/icannatlarge>atlarge <https://www.facebook.com/icannatlarge> Twitter: @ <https://twitter.com/ICANNAtLarge>ICANNAtLarge <https://twitter.com/ICANNAtLarge> One World, One Internet On 07/01/2016 17:50, "alac-bounces(a)atlarge-lists.icann.org on behalf of Alan Greenberg" <alac-bounces(a)atlarge-lists.icann.org on behalf of alan.greenberg(a)mcgill.ca> wrote: >The time has come to try to select meeting times for our ALAC calls >for the year. As had been the past practice, it will be held on the >4th Tuesday of each month (with exceptions for ICANN meetings). > >Please fill in the Doodle at http://doodle.com/poll/u2qhf5tidupa5e5f >as soon as possible. Ignore the DATE, it is the day of the week and >time that counts. If you know you are not available for a specific >meeting (such as the January one), please note that in a comment, but >fill in the Doodle for the general case. > >Note that each Doodle time-slot is for the full two hour meeting >starting at the designated time. > >For ALAC Members and Liaisons in particular, PLEASE BE FLEXIBLE. We >will try to avoid meetings in the dead of night, but with members >spanning the world, that will not always be possible and we will do >our best to limit the number of times any individual member needs to >participate at really awkward times. It is not fair to force some >people to always bear the pain. > >If you have a particular situation that cannot be easily expressed in >the Doodle, please send a private note to me and Gisella. > >Alan > >_______________________________________________ >ALAC mailing list >ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: http://www.atlarge.icann.org >ALAC Working Wiki: >https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(A >LAC)

1 1

Reminder - Call for Comments: Draft ALAC Statement on the Proposed Implementation of GNSO Thick Whois Consensus Policy Requiring Consistent Labeling and Display of RDDS (Whois) Output for All gTLDs Follow Updates
by Ariel Liang Jan. 20, 2016

Jan. 20, 2016

Hello ALAC, Please be so kind to review the draft ALAC Statement on the Proposed Implementation of GNSO Thick Whois Consensus Policy Requiring Consistent Labeling and Display of RDDS (Whois) Output for All gTLDs Follow Updates <https://community.icann.org/x/FIdlAw> . The internal At-Large commenting period will end on 22 Jan, but no comment has been received. Your input will be appreciated. Thank you, Ariel From: Ariel Liang <ariel.liang(a)icann.org> on behalf of Ariel Liang <ariel.liang(a)icann.org> Date: Wednesday, January 20, 2016 at 12:58 PM To: "'alac-announce(a)atlarge-lists.icann.org'" <alac-announce(a)atlarge-lists.icann.org>, "at-large(a)atlarge-lists.icann.org" <at-large(a)atlarge-lists.icann.org> Subject: Reminder - Call for Comments: Draft ALAC Statement on the Proposed Implementation of GNSO Thick Whois Consensus Policy Requiring Consistent Labeling and Display of RDDS (Whois) Output for All gTLDs Follow Updates Dear All, On behalf of the ALAC, Alan Greenberg, with assistance from Holly Raiche and Carlton Samuels, has developed the first draft ALAC Statement on the Proposed Implementation of GNSO Thick Whois Consensus Policy Requiring Consistent Labeling and Display of RDDS (Whois) Output for All gTLDs Follow Updates <https://community.icann.org/x/FIdlAw> . The draft, as well as pertinent resources that provide background to this Statement, can be found in its wiki workspace here: https://community.icann.org/x/FIdlAw. All At-Large members are welcome to comment on this draft. Please take a moment to review this draft and if you have input, please submit it in the wiki workspace using the comment function by 22 January 2016 at 23:59 UTC. You will need to log in to the wiki to use the comment function. If you don¹t have a login or have other issue using the wiki, kindly contact staff(a)atlarge.icann.org. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org Facebook: www.facebook.com/icann <https://www.facebook.com/icannatlarge> atlarge <https://www.facebook.com/icannatlarge> Twitter: @ <https://twitter.com/ICANNAtLarge> ICANNAtLarge <https://twitter.com/ICANNAtLarge>

1 0

An Update on CEO Succession - ICANN
by rinalia.abdulrahim＠gmail.com Jan. 18, 2016

Jan. 18, 2016

Dear ALAC, FYI > > https://www.icann.org/news/blog/an-update-on-ceo-succession > > Best regards, Rinalia

1 0

Fwd: Re: [council] Charter for New gTLD Subsequent Procedures
by Olivier MJ Crepin-Leblond Jan. 12, 2016

Jan. 12, 2016

Dear ALAC, in my capacity as GNSO Liaison, I am forwarding you the latest version of the Charter for the New gTLD Subsequent Procedures PDP. As you know, the Charter often directs the limits of the work. This proposed charter is a red-line copy, which means it incorporates comments made in the last public consultation, primarily a concern that another PDP on Rights Protection Mechanism might duplicate work here. Coordination between the different PDPs will be needed. If you have any feedback that I might need to let the Charter drafting Team know, please email me in time for the GNSO Council Call on 21 January. Kindest regards, Olivier -------- Forwarded Message -------- Subject: Re: [council] Charter for New gTLD Subsequent Procedures Date: Mon, 11 Jan 2016 23:40:06 +0000 From: Steve Chan <steve.chan(a)icann.org> To: Austin, Donna <Donna.Austin(a)neustar.biz>, council(a)gnso.icann.org <council(a)gnso.icann.org> Dear Councilors, As was agreed on the 17 December GNSO Council call, staff has worked with Susan, Philip, and Paul to develop the attached proposed red-lined changes to the Charter for New gTLD Subsequent Procedures PDP. This amended language is intended to avoid any ambiguity in regards to Rights Protection Mechanisms (RPMs) related activities for the New gTLD Subsequent Procedures PDP. In particular: * RPM related topics can be discussed, but proposing recommendations directly concerning RPMs is beyond the remit of this PDP. * A community liaison should be jointly appointed by the two PDP Working Groups (i.e., New gTLD Subsequent Procedures and RPMs) and confirmed by the GNSO Council in order to promote effective collaboration and coordination, Discussion on these proposed changes is welcomed and encouraged. If you have any questions, please let me know. Best, Steve *Steven Chan* Sr. Policy Manager *ICANN *12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 steve.chan(a)icann.org <mailto:steve.chan@icann.org> direct: +1.310.301.3886 mobile: +1.310.339.4410 tel: +1.310.301.5800 fax: +1.310.823.8649

2 1

Public Comment on Registration Proxy Service for gTLDs Operated by XYZ.COM LLC
by Alan Greenberg Jan. 11, 2016

Jan. 11, 2016

I was asked to look at this public comment and see if the ALAC needed to do anything. Since the name included the terms "proxy" and "registration", it raised red flags that it might be related to the ongoing (and very controversial and complex) PDP on privacy and proxy registrations. It is unrelated. This is a registry request to set up a secondary entry into their normal interfaces to registrars to allow them to service registrars in China, presumably in compliance with certain Chinese regulations related to where data or services reside and to provide local service to these registrars and their registrants. There does not appear to be anything that requires an ALAC comment. You can find the ALAC Policy page at https://community.icann.org/x/ZIplAw and the Registry Service Evaluation Request at https://www.icann.org/en/system/files/files/rsep-2014159-xyz-et-al-request-…. Alan

3 3

ACTION: Thick Whois Implementation Plan
by Alan Greenberg Jan. 9, 2016

Jan. 9, 2016

I volunteered to look at the implementation plan to implement the recommendation of the Thick Whois GNSO PDP. To very briefly recap the background, for most gTLDs (and all of the new ones), the Whois information is maintained by the registry. For ,com, .net and .jobs, the registry only maintains a minimum of information (primarily who the registrar is and when the domain expires) and the registrar maintains the bulk of the information including the identity and contact information of the registrant (subject to privacy/proxy issues). The PDP considered whether all registries (including the three mention above all run by Verisign) should be required to use a thick Whois model. The recommendation was that they should. Nearly two years into the implementation, we have a schedule for one of the ancillary recommendation (August 2016, 5 years after this process started), a date dependant on IETF action for a 2nd phase, and no plan or date for the prime recommendation of a universal Thick Whois. I have posted a draft ALAC comment at https://community.icann.org/x/FIdlAw. I ask staff to formally open a comment period on this draft immediately, and to close on 22 January to allow the statement to be revised and a vote taken by the ALAC.

1 0