- ALAC - lists.icann.org

Fwd: ICANN Board resolutions - from 11 Oct 2011
by Alan Greenberg Oct. 14, 2011

Oct. 14, 2011

Item 2 *VERY* interesting. >Subject: [council] ICANN Board resolutions - from 11 Oct 2011 >Date: Fri, 14 Oct 2011 20:34:59 +1000 >From: Bruce Tonkin <Bruce.Tonkin(a)melbourneit.com.au> >To: GNSO Council List <council(a)gnso.icann.org> > >From: http://www.icann.org/en/minutes/resolutions-11oct11-en.htm > >Approved Board Resolutions | Special Meeting of the ICANN Board > >11 October 2011 > >* Note: Where available, draft Rationale of the >Board's actions is presented under the >associated Resolution. The draft Rationale is >not final until approved with the minutes of the Board meeting. > > >Consent Agenda > >Resolved, the following resolutions in this Consent Agenda are approved: > > >1.1. Approval of Minutes of 25 August 2011 ICANN Board Meeting > >Resolved (2011.10.11.01), the Board approves the >minutes of the 25 August 2011 ICANN Board Meeting. > > >1.2. Approval of Minutes of 17 September 2011 ICANN Board Meeting > >Resolved (2011.10.11.02), the Board approves the >minutes of the 17 September 2011 ICANN Board Meeting. > > >1.3. Approval of Delegation of .CW (Curacao), >Transitional Arrangements for Netherlands Antilles (.AN) >====================================================================================== > >Whereas, CW is the ISO 3166-1 two-letter country-code designated for Curaçao; > >Whereas, ICANN has received a request for >delegation of .CW to the University of the Netherlands Antilles; > >Whereas, ICANN has reviewed the request, and has >determined that the proposed redelegation would >be in the interests of the local and global Internet communities; > >Resolved (2011.10.11.03), the proposed >delegation of the .CW top-level domain to the >University of the Netherlands Antilles is approved. > >Whereas, the .AN top-level domain was delegated >on the basis of its former listing as an ISO >3166-1 two-letter country code designated for the Netherlands Antilles; > >Whereas, the ISO 3166-1 standard has removed the >"AN" code, and the ISO 3166 Maintenance Agency >recommends its use be discontinued; > >Whereas, ICANN is not responsible for deciding >what is or is not a country, and adheres to the >ISO 3166-1 standard for guidance on when to add, >modify and remove country-code top-level domains; > >Whereas, the .AN top-level domain is still the >primary domain used by parties in the countries >and municipalities that comprised the former Netherlands Antilles; > >Whereas, there is a transition plan to move >registrations from the .AN domain to new domains >.CW and .SX, with the University of the >Netherlands Antilles continuing to act as >manager of the .AN domain until transition is complete, > >Resolved (2011.10.11.04), that the University of >Netherlands Antilles be instructed to report >their progress on decommissioning the .AN domain >every six months to ICANN against a relevant set of metrics, > >Resolved (2011.10.11.05), that the University of >Netherlands Antilles work to complete the >transition of the .AN domain to the .CW domain, >the .SX domain, and any other relevant domain; >so that it may be removed from the DNS root zone no later than 31 October 2014. > >Resolved (2011.10.11.06), that the .AN domain be >removed from the DNS root zone on 31 October >2014, if not requested earlier by the manager of the domain. > > >2. Approval of CEO Search Committee Membership >================================================= > >Whereas, 16 August 2011, Rod Beckstrom announced >that he will continue to fulfill his term as >ICANN's President and CEO, which will be completed on 1 July 2012. > >Whereas, the ICANN Board discussed CEO >Succession planning at the Board meeting on 17 September 2011. > >Whereas, the ICANN Board directed the Board >Governance Committee to recommend a slate of >Board members to comprise a CEO Search Process >Management Work Committee for the Board to consider at its next meeting. > >Whereas all members of the current Board and >liaisons, including incoming, have all stated >without reservation that they are not a >candidate for the position of CEO and will not accept it as offered. > >Resolved (2011.10.11.07), no current or incoming >member of the Board or liaisons may be >considered as a candidate for the role of the >CEO for the current CEO Selection process. > >Whereas, the following are the proposed members >of the group, based upon Board Governance >Committee recommendation and as refined by the Board: > >Steve Crocker > >George Sadowsky > >Bertrand de La Chapelle > >Erika Mann > >Chris Disspain > >Cherine Chalaby > >Ray Plzak > >R. Ramaraj > >Resolved (2011.10.11.08), the Board approves the >recommended membership of the CEO Search Process Management Work Committee. > >Resolved (2011.10.11.09), the George Sadowsky >will be the Chair of the CEO Search Committee. > > >Rationale for Resolutions 2011.10.11.07 - 2011.10.11.09 > >The ICANN Board has begun planning for and >developing the CEO succession process, to assist >in transition of the leadership. The >establishment of a work committee will allow the >Board to coordinate this process with regular >reporting to the Board as a whole, as well as >reviewing opportunities for community >involvement in the process. Timely succession of >the ICANN CEO will assist the organization in >maintaining its work in overseeing the security >and the stability of the DNS. The establishment >of the work committee will not have a financial >impact on ICANN, though resources are likely to >be required at later points in the process.

1 0

Fwd: For consideration: RAA Discussion Paper
by Alan Greenberg Oct. 14, 2011

Oct. 14, 2011

I am forwarding this note from Kurt Pritz related to options for amending the Registrar Accreditation Agreement. The discussion paper itself may be found at: <http://gnso.icann.org/issues/final-raa-discussion-paper-13oct11-en.pdf>http://gnso.icann.org/issues/final-raa-discussion-paper-13oct11-en.pdf. Feel free to redistribute this to your RALOs if desired. Alan >From: Kurt Pritz <kurt.pritz(a)icann.org> >To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> >Date: Thu, 13 Oct 2011 11:36:41 -0700 >Subject: [council] For consideration: RAA DIscussion Paper > >Dear GNSO Council Members, > >I would appreciate it if you could please review >the attached Discussion Paper on Next Steps to >Produce a New Form of the RAA. This paper >suggests possible options for consideration by >the community to move the RAA amendment process >forward in a cooperative and timely manner. > >This paper was prepared in response to a request >from the Board to categorize proposed amendment >topics and summarize possible options for next steps. > >The recent efforts by the GNSO Council to >address some of the law enforcement >recommendations demonstrate progress and are >encouraging. There are many other proposals to >be addressed. We believe that this paper can be >useful in identifying additional alternative >paths. To be clear, this is not intended to >interrupt current work or advance ICANN Board or >staff opinion in the policy discussions. The >paper is meant to be responsive to requests for >information. It is also meant to signal that >there will be a high level of staff support to >facilitate the development of RAA amendments and any related policy activities. > >Two additional points: You will find that the >categorization of topics is not as >straightforward as we all might prefer. As >described in the paper, it is difficult to >determine whether a proposal is a policy issue >or is within the picket fence without >considering specific amendment language. >Finally, the paper indicates a preference for >undertaking substantive discussion now, to >develop specific recommendations for amendments >through negotiation or policy development or both. > >We hope that this Discussion Paper will >encourage further dialogue in Dakar with the >GNSO Council, the Registrar Stakeholder Group, >and the ICANN community with regard to >identifying an acceptable path forward. I am >sure this paper is likely to raise questions >also. I think an exchange of questions and >answers is important to realize the full benefit >of the thought that went into this a writing >does not always capture or describe all the >ideas generated. Please direct those questions >to Margie Milam, who will share them with the >cross-functional team that worked on this for your consideration. > >Best regards, > >Kurt > > >Kurt Pritz >ICANN > >4676 Admiralty Way, #330 >Marina del Rey, CA 90292 > >

1 0

Re: [ALAC] [ALAC-ExCom] ALAC/At-Large Improvements Project -- important update
by Beau Brendler Oct. 13, 2011

Oct. 13, 2011

Why don't we appoint someone from the RALO level (who is not on ALAC) to work with each RALO chair to help resolve issues from below. That would not necessarily help evaluate the performance of the nomcom appointees, but it would help evaluate the bulk of the ALAC elected people. People in each RALO and the chairs could be invited to e-mail that person with concerns which could, in turn, be discussed with the chairs and evaluated. Then that material could be presented in a quarterly report or tri-annual report at the ICANN meetings to the excom. I wouldn't want to use the term ombudsman, but maybe that person could also work in conjunction with the ombudsman's office (since we are, in effect, dealing here with HR issues, but with no HR department, and with, after all, volunteers) to make sure proper procedure and good manners are followed. My guess would be that someone from the secretariat would make a good candidate for such a new "position." And maybe that "position" could come with some kind of stipend to sweeten the deal a little bit. Whoever did it would have to have a good sense of what's right and wrong, good common sense, and preferably some HR experience or interest. Most organizations that lean on a lot of volunteers have a "volunteer coordinator" position that is paid staff, who deals with these sorts of issues. We have no such thing. Instead we keep hand-wringing about it year-in and year-out. The ICANN staff currently assigned to us have their hands full with meeting procedure and whatnot, and it wouldn't be appropriate for ICANN to be evaluating performance in this manner anyway. I mean, we are talking about a lot of volunteers here, at least 30 or so, who are providing free labor worth hundreds of thousands of dollars per year. To not have a basic system of evaluation and "job performance" for a fluid administration of people who have enormous learning curves, and are sometimes thrown into these positions without much preparation, is absurd. It's also a poor return on investment. And asking everyone to do busy work or be judged on the number of (often pointless and time-wasting) conference calls they show up for is a substantial penalty on the people who actually do good work -- it is not the solution to a problem. Just a thought. Beau -----Original Message----- >From: Alan Greenberg <alan.greenberg(a)mcgill.ca> >Sent: Oct 13, 2011 12:58 PM >To: "Thompson, Darlene" <DThompson1(a)gov.nu.ca>, 'Carlton Samuels' <carlton.samuels(a)gmail.com> >Cc: "lac-discuss-en(a)atlarge-lists.icann.org" <lac-discuss-en(a)atlarge-lists.icann.org>, ALAC EXCOM <alac-excom(a)atlarge-lists.icann.org>, At-Large Worldwide <alac(a)atlarge-lists.icann.org> >Subject: Re: [ALAC] [ALAC-ExCom] ALAC/At-Large Improvements Project -- important update > >I am not sure they are difficult to assess, but they are most >definitely subjective. And we tend to have an aversion to making >subjective decisions in this sort of area (although in real life, we >are continually called upon to make them). > >Alan > >At 13/10/2011 11:29 AM, Thompson, Darlene wrote: >>Exactly Carleton, >> >>I've always maintained that we need to track both quantitative and >>qualitative measures - but the qualitative measure are MUCH more >>difficult to assess. I would really like to see suggestions on how >>this can be done - because it must be done. >> >>D >> >>Darlene A. Thompson >>Community Access Program Administrator >>Nunavut Dept. of Education / N-CAP >>P.O. Box 1000, Station 910 >>Iqaluit, NU X0A 0H0 >>Phone: (867) 975-5631 >>Fax: (867) 975-5610 >>E-mail: dthompson(a)gov.nu.ca<mailto:dthompson@gov.nu.ca> >> >>From: Carlton Samuels [mailto:carlton.samuels@gmail.com] >>Sent: Thursday, October 13, 2011 11:13 AM >>To: Thompson, Darlene >>Cc: Evan Leibovitch; Olivier MJ Crepin-Leblond; >>lac-discuss-en(a)atlarge-lists.icann.org; ALAC EXCOM; At-Large Worldwide >>Subject: Re: [ALAC] [ALAC-ExCom] ALAC/At-Large Improvements Project >>-- important update >> >>On Wed, Oct 12, 2011 at 9:11 AM, Thompson, Darlene >><DThompson1(a)gov.nu.ca<mailto:DThompson1@gov.nu.ca>> wrote: >>The members of the region, right now, have no idea if their ALAC rep >>is showing up to meetings or giving any kind of substantive input >>while at these meetings. >> >>Ah, there's the rub.....emphasis on 'substantive input'! >> >>Carlton >> >> >>============================== >>Carlton A Samuels >>Mobile: 876-818-1799 >>Strategy, Planning, Governance, Assessment & Turnaround >>============================= >>_______________________________________________ >>ALAC-ExCom mailing list >>ALAC-ExCom(a)atlarge-lists.icann.org >>https://atlarge-lists.icann.org/mailman/listinfo/alac-excom > >_______________________________________________ >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…

1 0

Re: [ALAC] [ALAC-ExCom] ALAC/At-Large Improvements Project -- important update
by Alan Greenberg Oct. 13, 2011

Oct. 13, 2011

I am not sure they are difficult to assess, but they are most definitely subjective. And we tend to have an aversion to making subjective decisions in this sort of area (although in real life, we are continually called upon to make them). Alan At 13/10/2011 11:29 AM, Thompson, Darlene wrote: >Exactly Carleton, > >I've always maintained that we need to track both quantitative and >qualitative measures - but the qualitative measure are MUCH more >difficult to assess. I would really like to see suggestions on how >this can be done - because it must be done. > >D > >Darlene A. Thompson >Community Access Program Administrator >Nunavut Dept. of Education / N-CAP >P.O. Box 1000, Station 910 >Iqaluit, NU X0A 0H0 >Phone: (867) 975-5631 >Fax: (867) 975-5610 >E-mail: dthompson(a)gov.nu.ca<mailto:dthompson@gov.nu.ca> > >From: Carlton Samuels [mailto:carlton.samuels@gmail.com] >Sent: Thursday, October 13, 2011 11:13 AM >To: Thompson, Darlene >Cc: Evan Leibovitch; Olivier MJ Crepin-Leblond; >lac-discuss-en(a)atlarge-lists.icann.org; ALAC EXCOM; At-Large Worldwide >Subject: Re: [ALAC] [ALAC-ExCom] ALAC/At-Large Improvements Project >-- important update > >On Wed, Oct 12, 2011 at 9:11 AM, Thompson, Darlene ><DThompson1(a)gov.nu.ca<mailto:DThompson1@gov.nu.ca>> wrote: >The members of the region, right now, have no idea if their ALAC rep >is showing up to meetings or giving any kind of substantive input >while at these meetings. > >Ah, there's the rub.....emphasis on 'substantive input'! > >Carlton > > >============================== >Carlton A Samuels >Mobile: 876-818-1799 >Strategy, Planning, Governance, Assessment & Turnaround >============================= >_______________________________________________ >ALAC-ExCom mailing list >ALAC-ExCom(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac-excom

1 0

Re: [ALAC] [ALAC-ExCom] ALAC/At-Large Improvements Project -- important update
by Alan Greenberg Oct. 13, 2011

Oct. 13, 2011

As the person who arguably started this discussion by proposing monitoring and subsequent possible actions several years ago (and still bear the scars from presiding over what may be the hottest-under-the-collar ALAC meeting on record), I would like to add a few thoughts. I agree that the word "sanctions" is far too strong and onerous a word to be used here, but as Olivier has pointed out, we still need to discuss what type of action the ALAC or perhaps the ALAC Chair or officers) *might* take in the case of significant under-performance. And I of course agree that we do need to be as specific as possible in identifying ahead of time what is expected of ALAC members and RALO officers. There are three additional perspectives that I have not seen being raised. In my years on and watching the ALAC, I have seen all three, so they are not just theoretical. - For a RALO appointed ALAC member, if the RALO is happy with their representatives performance, perhaps the rest of At-Large should accept that. But even if they are not, it is counter to the personality (and cultures) of some to actually confront the person who they often have to deal with in other contexts, and who they often consider a friend. Having the ALAC (or a someone) do the dirty work for them might be a safe way out of the situation. - If an ALAC member severely under-performs, it is not just their region that suffers. This adds to the load carried by the rest of the ALAC. If (as sadly has been the case in some past years), a significant percentage of the ALAC are in this category, the load on the rest becomes ridiculous. - The overall reputation and credibility of ALAC and At-Large can be impacted the poor performance of just a few. I am not proposing how we deal with such situations, but it is important to consider all implications when we discuss what if anything should be done other than collect and make available performance data (as all seem to agree should be done). Alan At 12/10/2011 11:56 AM, Wolf Ludwig wrote: >Hi all, > >I share Evan's basic question: "accountable to who?" and subsequent >considerations. And I would say: In a broader sense to the Internet >users in general, in a causal sense to the regional community that >selected them = the RALOs concerned by such an under-performing >candidate should be "in charge" of any potential "sanction" >mechanisms because the two *RALO selected* ALAC members are - first >and foremost - accountable to their electorate. A defective >performance of a regional representative / ALAC member affects >performance and reputation of the particular region and cannot be in >their interest = be tolerated over a certain span of time (except >for serious circumstances such as sickness and the like). > >I understand Carlton's reservations against sanctions or punishments >of volunteers but as soon as limited seats (15 or 2 per region) and >financial (travel etc.) resources are associated with a volunteer's >engagement, the mandated person and his community have a special >responsibility and accountability towards ALAC and ICANN. Otherwise, >we cannot fulfill our role and commitments - what we stand for - >diligently representing the users at ICANN. > >The key deliberation must be: The standards and professionalism we >expect and demand from others, we must fulfill ourselves at first >hand (typical trap of credibility ;-). > >Best, >Wolf > > >Evan Leibovitch wrote Tue, 11 Oct 2011 19:39: > >On 11 October 2011 19:04, Olivier MJ Crepin-Leblond <ocl(a)gih.com> wrote: > > > >> Take imaginary example candidate A, ALAC member, does not attend calls, > >> does not attend meetings, or when he travels, uses their time outside of > >> the ALAC room. A does not get involved in ALAC & other working groups. A > >> is basically using their affiliation to ALAC as something that looks > >> good on their CV. Admittedly, this is an extreme, but Carlton, at the > >> moment, nothing can be done about that person, and that imaginary person > >> is occupying a seat on the ALAC, one of the only 15 seats of people > >> supposed to act in the best interests of the 2.1Bn Internet users out > >> there. That person is failing those 2.1Bn people. That person is not > >> accountable. > >> > >I guess the big question -- at least MY big question -- is, accountable to > >who? > > > >If that person was sent by a RALO, the RALO should be able to handle this > >issue through a recall or other similar measure. > > > >If the person was appointed by the NomCom, the procedure is different but a > >mechanism is still required. By definition a NomCom ALAC appointee is not > >accountable to ALAC or the region, however it reflects badly on the NomCom > >and ICANN itself if non-performing ALAC members are chosen and allowed to > >under-serve for an entire two-year term. > > > >What bothers me the most is the prospect of ALAC passing judgment over its > >own members. If a RALO elects someone who reflects their viewpoint, and that > >viewpoint is that only a small number of issues matter, this is indeed the > >RALO's choice to make and ALAC has no right to engage in top-down > >second-guessing. Education and persuasion, certainly, but not sanctions. > > > >I fully agree on requesting that every RALO has some kind of recall > >mechanism for their elected officials -- not just ALAC members but also RALO > >chairs, secretariats and liaisons as applicable. Indeed I have long > >advocated this within my own RALO. I am also greatly in favour of staff's > >providing attendance and other performance metrics that allow a RALO to act > >appropriately on factual inputs. But I am very much against any scheme that > >has ALAC members being accountable to other ALAC members. > > > >It's bad enough that the ICANN Board has no legal, fiduciary duty to the > >public, but only to ICANN itself. Let's not justify, let alone propagate > >that mistake within our own bounds. > > > >But in any case, this debate is premature. We're at an intermediate > >> stage, with more than 50 recommendations in this report, some of which > >> are completed, some of which need to be taken to the next stage. The > >> debate on sanctions/no sanctions will happen later. > > > > > >I don't think there's any problem with that. As I've mentioned, it's simply > >that the wording in the report right now could easily be interpreted by a > >casual reader to infer that we have already had the discussion, agreed on a > >regime of sanctions, and are simply discussing appropriate implementation > >going forward. WE know the debate is incomplete, but that is not what the > >report indicates. > > > >- Evan > >_______________________________________________ > >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… > > > >EuroDIG Secretariat >http://www.eurodig.org/ >mobile +41 79 204 83 87 >Skype: Wolf-Ludwig > >EURALO - ICANN's Regional At-Large Organisation >http://euralo.org > >Profile on LinkedIn >http://ch.linkedin.com/in/wolfludwig >_______________________________________________ >ALAC-ExCom mailing list >ALAC-ExCom(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac-excom

3 2

Re: [ALAC] [ALAC-ExCom] ALAC/At-Large Improvements Project -- important update
by Olivier MJ Crepin-Leblond Oct. 12, 2011

Oct. 12, 2011

Carlton, On 11/10/2011 15:49, Carlton Samuels wrote : > As I have already stated, I cannot vote for any report that recommends > "sanctions" on volunteers, even if they are yet to be determined. The > state of mind that delivers this gem can only be repudiated for cause. Take imaginary example candidate A, ALAC member, does not attend calls, does not attend meetings, or when he travels, uses their time outside of the ALAC room. A does not get involved in ALAC & other working groups. A is basically using their affiliation to ALAC as something that looks good on their CV. Admittedly, this is an extreme, but Carlton, at the moment, nothing can be done about that person, and that imaginary person is occupying a seat on the ALAC, one of the only 15 seats of people supposed to act in the best interests of the 2.1Bn Internet users out there. That person is failing those 2.1Bn people. That person is not accountable. Yes, that person is a volunteer, but when you volunteer for ALAC, you're not doing it as a piece of fun. There is a deep responsibility that goes along with that. There is accountability to users in the rest of the world. But in any case, this debate is premature. We're at an intermediate stage, with more than 50 recommendations in this report, some of which are completed, some of which need to be taken to the next stage. The debate on sanctions/no sanctions will happen later. (and in Dakar we have a session on metric which might touch on that... or we might have to wait until after Dakar. In any case, there will be plenty of times to debate this) Warmest regards, Olivier -- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html

6 9

Re: [ALAC] [lac-discuss-en] [ALAC-ExCom] ALAC/At-Large Improvements Project -- important update
by Dev Anand Teelucksingh Oct. 12, 2011

Oct. 12, 2011

Well said, Darlene +1 Dev Anand Teelucksingh On Wed, Oct 12, 2011 at 10:11 AM, Thompson, Darlene <DThompson1(a)gov.nu.ca> wrote: > I agree with both Olivier and Evan. ;) > > One thing that I think is *super* important is to educate the RALOs in: > > 1) What their elected ALAC rep is supposed to be doing. If they know this from the beginning, they may make different choices when electing their ALAC rep. Since this is an elected position that people actually campaign for, the ideals need to be set at the beginning so that those that are running for the position know what is expected of them and the region knows where to set their expectations. > > 2) Being kept informed about how their ALAC rep is actually performing. The members of the region, right now, have no idea if their ALAC rep is showing up to meetings or giving any kind of substantive input while at these meetings. > > Right now, the RALOs are powerless to remove an elected ALAC rep that is non-performing because they have no idea HOW they are performing. This problem needs to be addressed as soon as possible, IMHO. I'm tired of seeing just a few ALAC members over and over again on these lists shouldering all of the work when I know that there are 10 elected reps out there. That also leaves the matter of the NomCom reps. They need to be made accountable too but I'm just not sure how. > > D > > Darlene A. Thompson > Community Access Program Administrator > Nunavut Dept. of Education / N-CAP > P.O. Box 1000, Station 910 > Iqaluit, NU X0A 0H0 > Phone: (867) 975-5631 > Fax: (867) 975-5610 > E-mail: dthompson(a)gov.nu.ca > > > -----Original Message----- > From: alac-bounces(a)atlarge-lists.icann.org [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf Of Evan Leibovitch > Sent: Tuesday, October 11, 2011 7:40 PM > To: Olivier MJ Crepin-Leblond > Cc: Carlton Samuels; lac-discuss-en(a)atlarge-lists.icann.org; ALAC EXCOM; At-Large Worldwide > Subject: Re: [ALAC] [ALAC-ExCom] ALAC/At-Large Improvements Project -- important update > > On 11 October 2011 19:04, Olivier MJ Crepin-Leblond <ocl(a)gih.com> wrote: > > > >> Take imaginary example candidate A, ALAC member, does not attend calls, >> does not attend meetings, or when he travels, uses their time outside of >> the ALAC room. A does not get involved in ALAC & other working groups. A >> is basically using their affiliation to ALAC as something that looks >> good on their CV. Admittedly, this is an extreme, but Carlton, at the >> moment, nothing can be done about that person, and that imaginary person >> is occupying a seat on the ALAC, one of the only 15 seats of people >> supposed to act in the best interests of the 2.1Bn Internet users out >> there. That person is failing those 2.1Bn people. That person is not >> accountable. >> > > I guess the big question -- at least MY big question -- is, accountable to > who? > > If that person was sent by a RALO, the RALO should be able to handle this > issue through a recall or other similar measure. > > If the person was appointed by the NomCom, the procedure is different but a > mechanism is still required. By definition a NomCom ALAC appointee is not > accountable to ALAC or the region, however it reflects badly on the NomCom > and ICANN itself if non-performing ALAC members are chosen and allowed to > under-serve for an entire two-year term. > > What bothers me the most is the prospect of ALAC passing judgment over its > own members. If a RALO elects someone who reflects their viewpoint, and that > viewpoint is that only a small number of issues matter, this is indeed the > RALO's choice to make and ALAC has no right to engage in top-down > second-guessing. Education and persuasion, certainly, but not sanctions. > > I fully agree on requesting that every RALO has some kind of recall > mechanism for their elected officials -- not just ALAC members but also RALO > chairs, secretariats and liaisons as applicable. Indeed I have long > advocated this within my own RALO. I am also greatly in favour of staff's > providing attendance and other performance metrics that allow a RALO to act > appropriately on factual inputs. But I am very much against any scheme that > has ALAC members being accountable to other ALAC members. > > It's bad enough that the ICANN Board has no legal, fiduciary duty to the > public, but only to ICANN itself. Let's not justify, let alone propagate > that mistake within our own bounds. > > But in any case, this debate is premature. We're at an intermediate >> stage, with more than 50 recommendations in this report, some of which >> are completed, some of which need to be taken to the next stage. The >> debate on sanctions/no sanctions will happen later. > > > I don't think there's any problem with that. As I've mentioned, it's simply > that the wording in the report right now could easily be interpreted by a > casual reader to infer that we have already had the discussion, agreed on a > regime of sanctions, and are simply discussing appropriate implementation > going forward. WE know the debate is incomplete, but that is not what the > report indicates. > > - Evan > _______________________________________________ > 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… > > _______________________________________________ > lac-discuss-en mailing list > lac-discuss-en(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en >

1 0

Re: [ALAC] Election Call for ALAC Liaisons to serve from October 2011 to ICANN AGM 2012
by Alan Greenberg Oct. 12, 2011

Oct. 12, 2011

Thank you Evan, Cheryl and Jean-Jacques. I accept. Alan At 12/10/2011 01:53 AM, Jean-Jacques Subrenat wrote: And I too would like to support Evan's nomination of Alan. Jean-Jacques. On 12 October 2011 13:31, Cheryl Langdon-Orr <<https://atlarge-lists.icann.org/mailman/listinfo/alac>langdonorr at gmail.com> wrote: > Hi Evan as I had intended to pen a similar nomination for Alan to continue > with the superb job he does in this role as the ALAC's Liaison to the GNSO, > for the following year, but you 'beat me to it' ;-) So may I stand as a > seconder and supporter for this *most* worthy nomination... > > > Cheryl Langdon-Orr > (CLO) > > > > On 12 October 2011 16:12, Evan Leibovitch <<https://atlarge-lists.icann.org/mailman/listinfo/alac>evan at telly.org> wrote: > > > I nominate Alan Greenberg to continue another term in the admirable job > he > > has done for us as GNSO liaison > > > > - Evan

1 0

Re: [ALAC] The end of time?
by Alan Greenberg Oct. 12, 2011

Oct. 12, 2011

I know nothing about this particular issue, but I do recall that compilations of sports scores and other sports statistics have long been deemed to be copyrighted by various sports associations and their publishers, so there certainly is precedent to copyrighting compilations of facts. Alan At 11/10/2011 02:19 PM, Evan Leibovitch wrote: >Hello everyone, > >I call your attention to this post on The Economist ><http://www.economist.com/blogs/babbage/2011/10/copyright-and-time-zones>regarding >the database of timezones used by the world's computers. Apparently a US >company has issued a takedown order based on a copyright claim. > >Further in the article there is mention that IANA was considered a possible >custodian of the database, hence the relevance here. The article also >suggests that the takedown notice might be invalid since timezones are facts >and not expression -- but that this won't be tested in court. > >Is there anyone here that understands the issue better than I? Is this >something in which At-Large can -- or should -- play a role? > >More info can be found -- including detauls of efforts to recreate the >database -- are found in this blog >post<http://blog.joda.org/2011/10/today-time-zone-database-was-closed.html> >. > >- Evan >_______________________________________________ >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] Verisign Service Request - Malware monitoring and Malicious site takedown
by Alan Greenberg Oct. 12, 2011

Oct. 12, 2011

Thanks Jean-Jacques, It is interesting that you use as an example the lax regulatory environment which led to financial problems, because the industry did not exercise prudent restraint itself. In this case, most of those who have commented seem to be worried that Verisign will be TOO active in policing. The discussion of this issue will indeed be interesting. It highlights the sometimes opposing needs to protect the Internet and users from things that are generally agreed upon as bad, while maintaining the freedoms that many of us feel are essential to the Internet. Alan At 11/10/2011 11:46 PM, Jean-Jacques Subrenat wrote: >Thank you Alan for pointing this out. > >The proposal under consideration illustrates the approach of many >large companies today, calling for self-regulation to replace a >proper regulatory body acting in the public interest. We've seen how >Greenspan, Paulson and others, by playing down the regulatory duties >of the US federal government over the years, have allowed widespread >disaster in the financial sector, with incalculable consequences for >taxpayers worldwide. > >Verisign's proposal brings up questions which have been well >formulated by the commentators Alan has pointed to (Kirikos, >Jeftovic) and which should also be looked at from a (higher) policy >standpoint: >- to what extent can a private company be allowed to exercise >regulatory duties, against payment? >- the proposed mechanism carries the risk of collateral damage to >legitimate entities and users. > >Alan, I support your call for ALAC to adopt and make known its >position on this. > >Regards, >Jean-Jacques. > >On 12 October 2011 03:20, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >Verisign has requested ICANN permission to offer a new service under >the Registry Service Evaluation Process (RSTEP). > >There are two services described within the proposed Verisign >Anti-Abuse Domain Use Policy. >- Periodic scans of websites to identify possible malware >- An anti-abuse policy and procedures to take down sites that violate >the policy. >They would be applicable to the .com, .net and .name TLDs managed by Verisgin. > >The full request can be seen at ><http://www.icann.org/en/registries/rsep/verisign-com-net-name-request-10oct…>http://www.icann.org/en/registries/rsep/verisign-com-net-name-request-10oct…, >and there are articles about the request at ><http://www.theregister.co.uk/2011/10/11/verisign_asks_for_web_takedown_powe…>http://www.theregister.co.uk/2011/10/11/verisign_asks_for_web_takedown_powe… >and ><http://domainnamewire.com/2011/10/11/verisign-proposes-takedown-procedures-…>http://domainnamewire.com/2011/10/11/verisign-proposes-takedown-procedures-…. > >There are already a few comments on the service - see ><http://forum.icann.org/lists/registryservice/>http://forum.icann.org/lists/registryservice/. > >In theory, ICANN could approve the service in as little as two weeks >from today. However, in this case I suspect that a longer time will >be allowed, and perhaps a formal Public Comment period will also be opened. > >As you will see from the news articles and the early comments, there >are a number of issues involved here and the ALAC may well want to >comment on this Service Request. > >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+(AL…>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… >

1 0