- ALAC - lists.icann.org

nomination to ALT
by Vanda Scartezini Aug. 3, 2017

Aug. 3, 2017

Maureen is my first choice for such position! But I support all colleagues leon has suggested. Vanda Scartezini Polo Consultores Associados Av. Paulista 1159, cj 1004 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 Sorry for any typos.

1 0

Re: [ALAC] ALAC Chair
by Alan Greenberg Aug. 1, 2017

Aug. 1, 2017

Barrack, Andrei, Javier and Vanda, Thank you very much for your kind words and votes of confidence. Alan At 31/07/2017 11:11 PM, Alan Greenberg wrote: >One of the results of the first At-Large Review was the >recommendation that the ALAC Chair be appointed for 2-year terms. >The logistics of that was problematic - at any given time, half of >the ALAC only has one year more remaining in their ALAC term. When >the Rules of Procedure were re-written in 2012-13, the solution was >to elect the Chair for a term on one year, but with the option, at >the Chair's discretion, to extend the term to 2 years if the Chair >was still an ALAC Member and willing to serve. That served to >implement the two-year term, but only when the person was available >to serve the 2nd year. The applicable ALAC RoP 5.4, 8.1 and 8.2 are >reproduced at the end of this message. > >I was re-elected as Chair last year, and thus I now have to decide >whether I will stay as Chair for the coming year. I have thought >about this over the last months and considered all of the issues, >including the optics of staying on in light of the ITEMS Review >accusation of entrenched leadership resisting change (a position >that the ALAC strongly rejected in its comments) and in light of >what has been accomplished during my tenure as Chair. Although it >has been a very busy three years, much of my and our efforts have >been focused on the IANA Stewardship Transition and ICANN >Accountability. As a result, my hopes at increasing our ALS >effectiveness have not come to fruition, as clearly evidenced by the >At-Large Review results. > >On balance, I have decided to extend my term for an additional year >to continue the work with ALS effectiveness, to see the ICANN >Accountability efforts come to a completion and to start (and >hopefully partially complete) the At-Large Review Implementation. > >2017-18 will be my last year as ALAC Chair and as an ALAC Member. > >Nominations for the other four ALT positions will open shortly. > >Alan > >========================================== >ALAC Rules of Procedure ( http://tinyurl.com/ALAC-RoP-2016-09) > >5.4 The Chair is elected for a one year term. At the end of that >term, the appointment may be renewed for one additional year subject >to the provisions of Paragraph 8.2. The first priority for the ALAC >is to select the best person to be Chair regardless of their ability >to serve for a second term. > >8.1 All appointments begin at the conclusion of one AAGM and >continue until the conclusion of the following AAGM, unless the ALAC >specifically identifies a different timeframe. > >8.2 If the Chair is still a member of the ALAC in the year following >his or her selection, is willing to continue in that role and >subject to the eligibility rules in Paragraph 5, the Chair?s term is >deemed to be automatically renewed for a second year without any >explicit action of the ALAC.

1 0

ALAC Chair
by Alan Greenberg Aug. 1, 2017

Aug. 1, 2017

One of the results of the first At-Large Review was the recommendation that the ALAC Chair be appointed for 2-year terms. The logistics of that was problematic - at any given time, half of the ALAC only has one year more remaining in their ALAC term. When the Rules of Procedure were re-written in 2012-13, the solution was to elect the Chair for a term on one year, but with the option, at the Chair's discretion, to extend the term to 2 years if the Chair was still an ALAC Member and willing to serve. That served to implement the two-year term, but only when the person was available to serve the 2nd year. The applicable ALAC RoP 5.4, 8.1 and 8.2 are reproduced at the end of this message. I was re-elected as Chair last year, and thus I now have to decide whether I will stay as Chair for the coming year. I have thought about this over the last months and considered all of the issues, including the optics of staying on in light of the ITEMS Review accusation of entrenched leadership resisting change (a position that the ALAC strongly rejected in its comments) and in light of what has been accomplished during my tenure as Chair. Although it has been a very busy three years, much of my and our efforts have been focused on the IANA Stewardship Transition and ICANN Accountability. As a result, my hopes at increasing our ALS effectiveness have not come to fruition, as clearly evidenced by the At-Large Review results. On balance, I have decided to extend my term for an additional year to continue the work with ALS effectiveness, to see the ICANN Accountability efforts come to a completion and to start (and hopefully partially complete) the At-Large Review Implementation. 2017-18 will be my last year as ALAC Chair and as an ALAC Member. Nominations for the other four ALT positions will open shortly. Alan ========================================== ALAC Rules of Procedure (http://tinyurl.com/ALAC-RoP-2016-09) 5.4 The Chair is elected for a one year term. At the end of that term, the appointment may be renewed for one additional year subject to the provisions of Paragraph 8.2. The first priority for the ALAC is to select the best person to be Chair regardless of their ability to serve for a second term. 8.1 All appointments begin at the conclusion of one AAGM and continue until the conclusion of the following AAGM, unless the ALAC specifically identifies a different timeframe. 8.2 If the Chair is still a member of the ALAC in the year following his or her selection, is willing to continue in that role and subject to the eligibility rules in Paragraph 5, the Chair's term is deemed to be automatically renewed for a second year without any explicit action of the ALAC.

5 4

Re: [ALAC] [registration-issues-wg] Changes to .vlaanderen and .brussels TLDs
by Alan Greenberg July 23, 2017

July 23, 2017

I've added the ALAC list back onto the recipients. To be clear, I did not advocate a comment. I asked whether this had user implications. The only answer to date was from John Levine who noted that the only implication was that the drop of the Add Grace Period (AGP) would stop registrants from cancelling a domain if they made a mistake. Since in fact very few (if any) Registrars actually extend that privilege to registrants these days (the AGP was added when registrations tended to be done on the phone and errors were much more common), I do not consider that as a real impact. The issue will be raised as a possible comment on the ALAC call on Tuesday, so it would be good if any any further research were done prior to that time. If we have a problem with the timing, a public comment on the specifics of an RSEP is not, in my mind, the proper place to do it. It will just be made and largely ignored since those processing the comments have no discretion to do anything about it. If RSEP needs to be changed, we should approach it head on. The timing is one issue, and the lack of consideration of registrant rights is another that we might want to focus on. If we think it is of sufficient import to put time into it. Alan At 22/07/2017 11:42 PM, Holly Raiche wrote: >I agree with Olivier and Christopher and Alan. > >Yes, the issue is tiny - the principle is >not. There is nothing wrong with saying that >our concern is not with these facts, but that >there is so little time for a considered >response. It takes a sentence or two - but >thats an important sentence or two. > >Holly >On 22 Jul 2017, at 11:43 pm, Olivier MJ >Crépin-Leblond <<mailto:ocl@gih.com>ocl(a)gih.com> wrote: > >>I understand that the case itself is minor, but >>isn't the principle itself important? If the >>principle is as Alan has described it, the case >>could create a precedent thus opening the door to other cases? >>Kindest regards, >> >>Olivier >> >>On 22/07/2017 10:19, Christopher Wilkinson wrote: >>> >>>Based in Belgium I naturally pay some attention to this one. >>>However I think that John is right here. >>> >>>Regards >>> >>>CW >>> >>>On 22 Jul 2017, at 09:07, John R. Levine >>><mailto:johnl@iecc.com><johnl(a)iecc.com> wrote: >>> >>>>>> >>>>>>Is it out of line to formally reply that >>>>>>this is not enough time to deliver a quality response? >>>> >>>>This is a tiny change to a pair of tiny TLDs, with about 6000 names each. >>>> >>>>As far as I can tell, the main thing >>>>registrants will see is that if they register >>>>the wrong name, they can't get their money >>>>back, They still have auto-renew and >>>>redemption grace periods so inattentive >>>>registrants aren't going to lose their names. >>>> >>>>This does not strike me as a good use of our limited time. >>>> >>>>Regards, >>>>John Levine, >>>><mailto:johnl@iecc.com>johnl(a)iecc.com, >>>>Primary Perpetrator of "The Internet for Dummies", >>>>Please consider the environment before >>>>reading this e-mail. <https://jl.ly/>https://jl.ly >>>>_______________________________________________ >>>>registration-issues-wg mailing list >>>><mailto:registration-issues-wg@atlarge-lists.icann.org>registration-issues-wg(a)atlarge-lists.icann.org >>>>https://mm.icann.org/mailman/listinfo/registration-issues-wg >>> >>>_______________________________________________ >>>registration-issues-wg mailing list >>><mailto:registration-issues-wg@atlarge-lists.icann.org>registration-issues-wg(a)atlarge-lists.icann.org >>>https://mm.icann.org/mailman/listinfo/registration-issues-wg >>> >> >> >>-- >>Olivier MJ Crépin-Leblond, PhD >><http://www.gih.com/ocl.html>http://www.gih.com/ocl.html >> >>_______________________________________________ >>registration-issues-wg mailing list >><mailto:registration-issues-wg@atlarge-lists.icann.org>registration-issues-wg(a)atlarge-lists.icann.org >>https://mm.icann.org/mailman/listinfo/registration-issues-wg

1 0

Re: [ALAC] [lac-discuss-en] IO recommends .amazon reconsideration
by Alan Greenberg July 21, 2017

July 21, 2017

I have a somewhat different viewpoint. It is true that the position of the GAC and its advice may be changing, but we need to look at the specifics of this particular case. The GAC has given lots of advice. Some is followed, some is rejected and in some cases a middle-ground is found. In all such cases, there is plenty of debate and discussion. In the case of .amazon, the GAC provided no rationale for the advice (they were not required to at the time). But more surprisingly, the Board did not subject this to debate but rather, and without rationale (which WAS required!) simply accepted the GAC advice. The IRP, in my mind, is simply recognizing that the Board did not follow its usual and proper practice of attempting to balance competing interests in this case. Alan At 19/07/2017 09:55 AM, Carlton Samuels wrote: >Yes mam, this is indeed the key strategic implication from the IRP. >In my own view however, ALAC [re]action may be premature for objective. > >Recent developments, especially this empowered community model, has >already undermined the "GAC advises, Board follows" scheme. I see >this IRP decision as adding grist to the mill in any downstream >federal court action. If and when a federal district court makes >that pronouncement, then stick a fork in it. It is roasted. > >-Carlton > > >============================== >Carlton A Samuels >Mobile: 876-818-1799 >Strategy, Planning, Governance, Assessment & Turnaround >============================= > >On Wed, Jul 19, 2017 at 5:36 AM, Jacqueline Morris ><<mailto:jam@jacquelinemorris.com>jam(a)jacquelinemorris.com> wrote: >But to me, far more important in the long term is the very clear >rejection of "the GAC advises, the Board follows" model. The ruling >has chipped away at the power of the GAC "advice" , and may change >the dynamic of the stakeholder roles in ICANN. >Might this be an opportunity for At-Large to work towards balancing >the roles of the ACs? Given that the relationship with the Board is >different for the various ACs, based on the bye-laws. >Jacqueline > >On 18 Jul 2017 11:38, "Dev Anand Teelucksingh" ><<mailto:devtee@gmail.com>devtee(a)gmail.com> wrote: >The IRP decision: ><https://www.icann.org/en/system/files/files/irp-amazon-final-declaration-11…>https://www.icann.org/en/system/files/files/irp-amazon-final-declaration-11… > >Dev Anand > >On Tue, Jul 18, 2017 at 11:15 AM, Carlton Samuels ><<mailto:carlton.samuels@gmail.com>carlton.samuels(a)gmail.com> wrote: > > Adds to the kerfuffle surrounding geographic names in the DNS. > > > > > <http://domainnamewire.com/2017/07/18/amazon-com-gets-big-win-domain-battle-…>http://domainnamewire.com/2017/07/18/amazon-com-gets-big-win-domain-battle-… > > > > > > -Carlton > > > > ============================== > > Carlton A Samuels > > Mobile: <tel:876-818-1799>876-818-1799 > > Strategy, Planning, Governance, Assessment & Turnaround > > ============================= > > > > _______________________________________________ > > 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… >_______________________________________________ >lac-discuss-en mailing list ><mailto:lac-discuss-en@atlarge-lists.icann.org>lac-discuss-en(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en > > >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;DM5PR03MB2714;27:CMV/fUuyPTmq0Go815gG9Jsumao2rNupQ1hHg8i+Lus2/PvqCJ6fRkdd721Nv0JyhCSB+/f6N7KrW6IeMKVb3I5D/VBtvPUjfPyyAsMaGm2AS967yrO0mYdb6LoJPOeebnbXvRHoWrLJeGkpMbM0ww== >X-Microsoft-Antispam-Mailbox-Delivery: > >ex:0;auth:0;dest:I;ENG:(400001000128)(400125000095)(20160514016)(750103)(520002050)(400001001223)(400125100095)(61617095)(400001002128)(400125200095); > >_______________________________________________ >lac-discuss-en mailing list >lac-discuss-en(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en

3 3

Changes to .vlaanderen and .brussels TLDs
by Alan Greenberg July 21, 2017

July 21, 2017

A registry service request has been submitted to ICANN for the .vlaanderen and .brussels TLDs to remove certain GRACE periods. Some Grace periods impact Registrars only, and others may impact Registrants. The Request can be found at https://www.icann.org/resources/files/1208363-2017-07-20-en. I am a bit troubled because one of the questions the Registry must answer is "Were consultations with end users appropriate? Which groups were consulted? What were the nature and content of these consultations?", and the reply was that Registrars were consulted. I am looking for a volunteer to look at the request and ensure that these grace period removals will not have any impact on Registrants. The timing on these requests is tight and ICANN has only 15 days to review the request, so any comments we wish to make must be within this window. Alan

1 0

RDS-WHOIS2-RT
by Alan Greenberg July 21, 2017

July 21, 2017

As some of you may know, I have been selected as Chair of the RDS-WHOIS2-RT (on an interim basis, but likely permanent). My intent as Chair is to keep this process as lean and short as possible, and my hope is that it will not have a great impact on my serving as ALAC Chair. But to the extent that there will be some impact, I will be looking to the ALT and other ALAC members to help ensure that the ALAC does not suffer from this. Alan

1 0

Fwd: Empowered Community Approval Notice for Board Resolution 201 7.05.18.04 - 2017.05.18.07
by Alan Greenberg July 21, 2017

July 21, 2017

The ICANN Empowered Community has formally taken its first action with the support of all five decisional participants. Alan >From: Stephen Deerhake <sdeerhake(a)nic.as> >Subject: Empowered Community Approval Notice for >Board Resolution 2017.05.18.04 - 2017.05.18.07 >Date: Fri, 21 Jul 2017 13:33:57 +0000 > >Greetings, > >Pleased see the attached correspondence from the >Empowered Community Administration certifying >the decisions made by each Decisional >Participant regarding the Fundamental Bylaw >change proposed by the ICANN Board of Directors >in their Board resolution 2017.05.18.04 2017.05.18.07. > >I am pleased to report that all five Decisional >Participants, through their internal procedures, >reached a decision regarding the matter before >them, and further, that all five Decisional >Participants approved the proposed Bylaw change. > >Best Regards, >Stephen Deerhake >ccNSO Representative to the Empowered Community Administration >

1 0

ALAC Decision: Proposed Revision to Fundamental Bylaw
by Alan Greenberg July 20, 2017

July 20, 2017

To the ICANN Empowered Community Administration: The ALAC conducted an online vote during the period 13-19 July 2017 on whether there ALAC supports the proposed ICANN Fundamental Bylaw revision creating the Board Accountability Mechanisms Committee. In accordance with ALAC Rules of Procedure 24.1 All decisions of the ALAC exercising its power within the EC must be decided by an affirmative vote of at least two-thirds of the sitting ALAC Members. With 14 of 15 ALAC Members voting, 13 Members voted to approve the Bylaw revision and 1 Member voted to reject the Bylaw revision. Accordingly, with more than two-thirds of sitting ALAC Members casting an approving vote, the ALAC supports the proposed Fundamental Bylaw Revision. Alan Greenberg Chair, ALAC ALAC Member of the EC Administration

1 0

Google Asked to Take Down Over 1M websites!
by Carlton Samuels July 20, 2017

July 20, 2017

;;from the latest Google transparency Report.... Story Here: https://www.engadget.com/2017/02/14/google-has-been-asked-to-take-down-over… Transparency Report Here: https://transparencyreport.google.com/copyright/overview#glance -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Planning, Governance, Assessment & Turnaround* =============================

1 0