July 2007 - NA-Discuss - lists.icann.org

Scheduling: Monday, 9 July 2007
by Bret Fausett July 5, 2007

July 5, 2007

Dear Colleagues, Thank you for responding to my request for a date preference for next week's meeting. Based on the responses, there was a slight preference for Monday (only one person could not make Monday while two people said they couldn't make Tuesday). As I mentioned before, the purpose of the meeting on Monday is to discuss ways forward; all matters for decision, if any, will be sent to the mailing lists and the wikis. Call in information and the agenda is on the wiki site at: https://st.icann.org/naralo/index.cgi?9th_july_2007 To assist our long range planning, I've set up an online calendar for the NARALO at: http://www.trumba.com/calendars/NARALO Once you review the calendar site, I think you'll find a number of helpful things there. First, although the default time zone for the calendar is mine (and ICANN's) here in Pacific Time, a menu pick at the bottom of the page allows you to set you own time zone. All of the events and event reminders will switch to your time zone. You can subscribe to the calendar by RSS, through iCal, or download events for your Microsoft Outlook calendar. You also can sign up for email reminders. Please note that only Monday's call is fixed; all of the other dates for monthly teleconferences are tentative, for discussion purposes. (Generally, they are the first or second Monday of the month.) I look forward to speaking with you on Monday. Bret Fausett

1 1

Status of ALAC board Liaison election & other matters..
by Robert Guerra July 5, 2007

July 5, 2007

Dear colleagues: It seems that the board liaison election has been postponed . .. (sigh) As many of you know, this past thursday the ALAC meeting agenda item related to presentation from the candidates mysteriously was removed. I spotted the change, and managed to re-insert it into the agenda. With the change, the candidates were able to present themselves and open themselves up to questions from the committee as well as individuals representing ALS's who were present at the meeting. A good exchange resulted To hear that the election might not take place until - Sept - , well, is shocking. After hearing from the candidates, I see no reason why the election needs to be postponed so far into the future. The only reason i've been given is that the rules of procedure for the At-large advisory committee (ALAC) have not been yet approved, as such there is no "real need" to have an election until one month before the Annual general meeting (AGM). Of course, the rules of procedure were - conveniently - left to the end of the meeting, and hence not discussed, and of course not approved. The document, thus now needs to be reviewed, discussed and approved. Knowing how painfully slow the ALAC goes through documents, I'd like to ask for your help to review and fix the document. Looking at the document (below and at the URL below) , well - it isn't perfect and needs major revisions. As i'm for consultation and engagement, i'd like to ask the NA list to review the document and send me any comments or better yet specific revisions that I could introduce. https://st.icann.org/alac/index.cgi?alac_internal_rule_en I look forward to your comments, and help in getting this important document revised and approved by ALAC ASAP so that we can have our board liaison vote. regards, Robert --- Robert Guerra <rguerra(a)privaterra.ca> Managing Director, Privaterra Tel +1 416 893 0377 -- ALAC Internal Rule-EN ICANN EN ALAC/2007/1/1.Rev3 ORIGINAL: English DATE: 21st May 2007 STATUS: DRAFT AT-LARGE ADVISORY COMMITTEE INTERNAL RULES OF PROCEDURE Officers 1. The officers of the At-Large Advisory Committee (“ALAC”) are: * One Chair and one Vice-Chair; * One GNSO Liaison * One ccNSO Liaison * One Board Liaison. Their roles and requirements are set forth in the following sections of these rules. 1. It is forbidden for any person to serve at the same time in two different officer positions. 2. All officers are normally elected at an Annual General Meeting of ICANN, except for the Board Liaison, which is normally elected at the ICANN Meeting preceding the Annual General Meeting. All officers, including the Board Liaison, serve for a term of one year starting from the closure of an Annual General Meeting and ending at the closure of the following Annual General Meeting. 3. All officers can be removed before the end of their term by a vote of recall according to section 6 of these rules. 4. All officers have a duty of performing their roles with diligence and loyalty to the Committee, and are bound to meet the minimum participation requirements set forth in section 10 of these rules. In case of failure to do so, the Chair shall call a vote of recall according to section 6 of these rules. 5. All officers have at least the same rights of access to information, mailing lists and documents as the ordinary ALAC members. 6. Officers shall be freely chosen by the ALAC, according to the following criteria: 7. They shall normally be persons who are current or former members of the ALAC, or are anyway familiar with the activities and functioning of ICANN and of the ALAC; 8. They shall accept to serve on behalf of the ALAC by acting for the good of the entire Committee, working to bridge differences and build consensus, but also recognizing difference and enabling different opinions to be shared; 9. They shall accept, while acting in their capacity as ALAC officer, to put the collective views of the Committee always in front of their own. The Chair a. The mission and responsibilities of the Chair of the ALAC are: * Chairing the meetings of the Committee; * Preparing and proposing the agenda for the meetings; * Interacting with ICANN Staff for administrative and organizational matters; * Representing the Committee in written communication, in the Public Forum and in meetings where there is no specific appointment; * Calling for votes on different matters, and ensuring that the proper instruments are available for the vote; * Ensuring that timelines and deadlines for the work of the Committee are set and met; * Verifying the respect of minimum participation requirements, rules of procedure, Bylaws and other norms applicable to the Committee; * Monitoring money expenditures and the budget situation. b. Only standing members of the At-Large Advisory Committee are eligible to serve as Chair. If at any point in time the Chair leaves the membership of the ALAC for any reason, he / she shall immediately cease the function of Chair as well. The Vice-Chair a. The mission and responsibility of the Vice-Chair of the ALAC is to perform the functions of the Chair, on request of the Chair, if the Chair is unable to perform them. b. Only standing members of the At-Large Advisory Committee are eligible to serve as Vice-Chair. If at any point in time the Vice- Chair leaves the membership of the ALAC for any reason, he / she shall immediately cease the function of Vice-Chair as well. Liaisons a. The mission and responsibilities of each Liaison of the ALAC are: * To participate diligently in the meetings and activities of the body he/she is liaisoning to; * To communicate and advocate the positions of the ALAC to such body; * To report to the ALAC the current and upcoming activities of the body he/she is liaisoning to, as far as this is possible under the timing and confidentiality constraints of such body; * When this is possible under such constraints, ask to the ALAC for advance instructions on matters that are going to be discussed by such body. b. There is no requirement for a Liaison to be a member of the At- Large Advisory Committee. Election of officers a. No earlier than one calendar month and no later than three weeks before the beginning of an ICANN Meeting where, according to the schedule of paragraph 1.c, an ALAC officer has to be elected, the current Chair of the ALAC will send to the public ALAC list an “election call” message, listing the officers that are to be elected at that ICANN Meeting, asking for nominations, and stating the deadline according to the following paragraph 5.b. b. The deadline for nominations for all open officer positions shall be 14 (fourteen) days after the date of the “election call”. Only standing ALAC members and officers can nominate or self-nominate, by posting a message to the public ALAC list. Anyone who will or has a chance to meet eligibility requirements after the next ICANN Annual General Meeting can be nominated; it is not necessary for nominees to meet eligibility requirements at the moment of the nomination, but, if elected, they will have to meet them before taking their position. Nominations of individuals who certainly will not be able to meet the eligibility requirements after the closure of the next Annual General Meeting are invalid. c. Nominations must be accepted by the nominee by sending a message of acceptance to the public ALAC list (or to the person who nominated them, who will then forward it to the public ALAC list, if they do not have posting privileges to the public ALAC list at the time) by the deadline of 7 (seven) days after the deadline for nominations. Nominations that are not accepted are invalid. d. After the deadline for nomination acceptance and before the beginning of the ICANN Meeting, the Chair will post to the public ALAC list an “election summary” message. This message will contain a summary of all valid nominations for any open position. In such message, the Chair will also notify the day and time in which the actual vote will happen; such day and time must be comprised between the beginning and the closure of the ICANN Meeting, except when the Meeting is also the the Annual General Meeting. In this latter case, the day and time of the vote must be comprised in the first 48 (fortyeight) hours after the closure of the Annual General Meeting; thus, the electorate will include the ALAC members whose term starts at the closure of that Annual General Meeting, and will not include the former ALAC members whose term ends at the closure of that Annual General Meeting. e. Nominations shall then be discussed on the public ALAC list and at the physical ALAC meetings during the ICANN Meeting. f. At the day and time of the vote, staff will provide ALAC members with a mechanism for voting that meets the following requirements: * It allows for each ALAC member to cast their vote in a confidential manner, so that no other Committee member or officer shall know it; * It allows for ALAC members who are not physically present to cast their vote remotely (also in advance of the day and time of the vote, if they are unavailable at that moment). g. Each presently standing member of the ALAC can cast up to one preference for each open officer position, picking among the list of validly nominated individuals published at 5.d. Votes for other individuals are considered equivalent to abstention. h. At least ten ALAC members must cast a vote (including abstention) for the election to be valid. i. After votes have been collected, staff will examine them and call the result. j. For any open position, the candidate receiving the highest number of preferences is elected, provided that he/she received at least five preferences, and that no other candidates received the same number of preferences. If the same person is elected in two or more officer positions, he/she shall immediately pick one, and shall be removed from the results of the elections for the other positions. The newly elected officers assume their position at the closure of the Annual General Meeting. k. In case two or more candidates receive the same, highest number of preferences, a tiebreak vote is to be conducted. The Chair will select a new date and time for a new vote on that position, at least 7 (seven) days later than the current vote; in such vote, only the candidates that received the same, highest number of preferences will be eligible to receive preferences. The Chair will then immediately send a new “election summary” message according to 5.d, and the procedure will then restart from 5.e. l. In case no candidate could be elected for any other reason (lack of valid nominations, lack of five valid preferences...), the Chair will immediately post a new “election call”, thus reopening nominations. The procedure will then restart from 5.a. m. Incumbent officers shall continue to serve in their position in full standing until a valid result is obtained for the election and a new officer is elected. n. If for any reason whatsoever (including lack of quorum, lack or loss of eligibility requirements, resignation, or recall) an officer position becomes vacant before the end of the term, the Chair will promptly start an election to fill it, by sending an “election call” message and starting the procedure from 5.a. Recall votes a. A recall vote can be initiated by: * A request, specifying the officer to be recalled and the reasons for such proposal, posted to the public ALAC list and supported by at least five ALAC members; * The Chair, upon verification of the lack or loss of eligibility requirements, or of the officer's failure to meet participation requirements set forth in 1.e. b. In case a recall vote is initiated, the Chair will send a message to the public ALAC list, announcing such vote, and including the date and time for the vote, selected by the Chair and situated no earlier than 7 (seven) and no later than 14 (fourteen) days after the date of the announcement. Between the announcement and the vote, the matter will be discussed on the public ALAC list, including counter- arguments by the officer under recall. c. Staff will set up a voting instrument meeting the requirements set forth in 5.f. Each ALAC member will be allowed to cast a vote picking among “in favour”, “against” or “abstain”. d. In case at least nine votes are cast in favour of recalling the officer and at least threefourths of the ALAC members cast a vote (including abstentions), the recall is successful; in all other cases, it is not. e. In case of successful recall, the Chair will promptly post an “election call” to start the procedure defined in section 5, to elect a replacement. The recalled officer will continue to serve until a replacement is elected. Other ALAC appointments a. The ALAC may, from time to time: * attribute specific tasks or responsibilities to a given individual; * appoint a given individual as ALAC representative in working groups, task forces, or other committees and bodies different from those to which Liaisons are appointed; * form Committees, attribute specific tasks or responsibilities to them, and appoint their members. b. There is no requirement for these appointees to be members of the ALAC. c. Such appointments shall normally be done through an informal call for volunteers, posted by the Chair to the public ALAC list, allowing at least 7 (seven) days for people to volunteer, and trying to reach consensus on the appointment. However, in case that consensus cannot be reached, or in case that this is requested by at least 3 (three) ALAC members, the Chair will start a formal election procedure as set forth in section 5. d. Such appointments can be recalled with the same procedure defined in section 6. e. The appointments described in this section expire at the end of the ICANN Annual General Meeting for the calendar year following the one in which the appointment is made, unless, before that term, the Committee recalls them, the appointee resigns, or the need for the appointment ceases to be. Motions a. Any member of the ALAC can present a motion for discussion and decision by the Committee, on any matter under the purview of the Committee. Motions need to be seconded by another member of the ALAC. b. This section applies to the discussion and vote of all motions, except for matters where more specific rules are defined in other sections of this document. c. Whenever a motion is presented, the Chair will allocate appropriate time for discussion, and the Committee will try to debate and reach full consensus on the matter approached by the motion. The Chair will try to facilitate consensus by proposing possible ALAC/ 2007/1/1.Rev3 Page 6 of 7 compromises that can accommodate the views of all Committee members, including minority views. d. If the Chair deems that consensus has been reached, he/she can propose to the Committee to approve the consensus by a “no objections call”. To this effect, the Chair will post a “no objections call” message to the public ALAC list, stating the text of the motion being proposed – which shall reflect the consensus reached during the discussion, and thus might be different from the original motion, according to the Chair's own judgement – and giving 7 (seven) calendar days for objections. The motion will be approved if no ALAC member posts a formal objection to the motion to the public ALAC list in the seven days, or, even before the deadline, if all ALAC members express formal support for the motion, either in person (if at physical meetings) or remotely. e. If no consensus has been reached, or if the “no objections call” does not result in the approval of a motion, the original motion and any other counter-motions presented during the discussion shall be put to votes in the order of presentation. A motion shall be considered approved if at least five ALAC members cast a non- abstaining vote, and if the number of votes in favour of the motion is higher than the number of votes against. The vote will be open for 7 (seven) days, but the Chair may close it before the deadline if all ALAC members have cast their vote, either in person (if at physical meetings) or remotely. Meetings a. The ALAC shall meet physically at all ICANN meetings, and virtually by mailing lists and conference calls. Ordinarily, at least one conference call per month will be held. b. When meeting physically or telephonically, decisions on a matter of substance cannot be taken unless absent members are given or have been given the opportunity to express their opinion or cast their vote. c. At least 7 (seven) days before each meeting or conference call, the Chair will post a proposal for the agenda of the meeting. In the following 4 (four) days, any ALAC member can request the addition of other items to the agenda of the meeting. A final agenda will then be published by the Chair. d. If the duration of the meeting is insufficient to deal with all agenda items, the remaining ones will be deferred to on-list discussion or to future meetings. Minimum participation requirements a. ALAC members and officers are expected to actively participate in all aspects of the Committee's work. This includes some qualitative commitments and quantitative requirements. b. The qualitative commitments are: • Reading and commenting in the ALAC online forums; * Following the ALS certification process and, if members, voting in accreditation votes; * Participating in ALAC conference calls; * Attending physical ALAC meetings (and/or, for liaisons, meetings of the bodies to which the person is liaisoning) at ICANN meetings; * Serving as a liaison to the public. c. The quantitative requirements are: * If members, casting a vote (including abstention) in at least 3/4 of ALS accreditation votes; * Participating in at least 2/3 of the ALAC conference calls in any 6 month period; • Attending at least one physical ICANN meeting in any 9 month period. d. The participation requirements set forth in this section shall be considered met if and only if the quantitative requirements stated in 10.c are met. e. For ordinary ALAC members, in case of failure to meet the requirements, the Chair will privately encourage the member to resign. If this does not happen by 14 (fourteen) days from that communication, the Chair will formally notify the entity responsible for appointing the member, with a message copied to the public ALAC list, and ask that the appointment is immediately reconsidered. 11.Amendments to these rules a. Proposals for amendment of these rules can be made by any member or officer of the ALAC. Such proposals will be voted by the ALAC, and will be approved only if at least nine votes are cast in favour of adopting the amendment and at least three-fourths of the ALAC members cast a vote (including abstentions).

4 4

Re: [NA-Discuss] Global At-Large Summit
by Thompson, Darlene July 5, 2007

July 5, 2007

EXCELLENT ideas, V! ________________________________ From: Vittorio Bertola [mailto:vb@bertola.eu] Sent: Tue 7/3/2007 4:31 PM To: Thompson, Darlene Subject: Re: [NA-Discuss] Global At-Large Summit Thompson, Darlene ha scritto: > Hi all, > > It was discussed at the meeting in San Juan that there is an interest > amongst the At-Large community to have a global meeting of the ALSs, now > that all of the RALOs are formed. As 1/2 of your interim Secretariat, I > will be having contact with the other RALOs to work on moving this forward. > > Would anybody else be interested in forming a working group or task > force on this matter with me? Please let me know. Please keep me posted. I guess that it will be me (at least if I'm reappointed) to have to convince ICANN's COO and CEO, if not the entire Board, that this event deserves $100-150k of additional expenditure. Especially, we should work out on a compelling case on why such an event would be particularly useful; shaking hands and socializing among such diverse people would be a good thing, but on the other hand discussions are already quite pointless and relatively ineffective in the meetings of 15 ALAC people plus a few from one or two RALOs... just imagine with 100 RALO representatives from five continents in the same room. Such a meeting is absolutely doable, but it would require a clear agenda, clear procedures, clear deliverables and clear objectives: it needs a well thought out plan. On another matter - it occurred to me that Avri Doria, the GNSO Chair, is now living in Lulea (in Sweden) and working on networking and education opportunities for the Sami people, who live in Scandinavia beyond the Arctic circle (well, beyond if looking from where I live). I guess that the Sami might share many challenges with the Inuit; I don't know whether you met Avri in San Juan, in any case it might be interesting for you to get in touch with her. Regards, -- vb. Vittorio Bertola - vb [a] bertola.eu <-------- --------> finally with a new website at http://bertola.eu/ <--------

5 6

New Website for At-Large
by Nick Ashton-Hart July 5, 2007

July 5, 2007

Dear All: Attached you will find the functional specification for the new www.atlarge.icann.org which is being built. This will be a quantum leap forward for At-Large. It incorporates dynamic content - from blogs of members of the community, two-way links between the forums and the mailing lists, fully-imbedded multilingual support, and the ability to seamlessly link the wiki environments into the website - amongst many other features. It will also include 'single-sign-on' functionality, allowing you to login with one userid and password and access the membership system being built in CiviCRM, as well as special content based upon what position or region you belong to in the At-Large community website. Much of the content from www.alac.icann.org will be migrated to the new site, as well as content in the current wiki environments for meetings and documents; we can also bring over historical information which is wanted from www.icannalac.org before updates to that site effectively ceased in December 2006. There should be a preview of the site available in the next few weeks. In completing the site we'll look for input from the community. I hope that you are as excited as I am about what this site will mean to the community - we're once again leading the way in online environments within the ICANN family. -- Regards, Nick Ashton-Hart Director, At-Large ICANN PO Box 32160 London N4 2XY United Kingdom Main Tel: +44 (20) 8800-1011] USA Tel: +1 (202) 657-5460 Fax: +44 (20) 7681-3135 mobile: +44 (7774) 932798 email: nick.ashton-hart(a)icann.org Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart

1 0

Meeting Proposal: 9 July 2007
by Bret Fausett July 4, 2007

July 4, 2007

With national holidays this week in both the U.S. and Canada, let's take this week to reflect on the items that Robert posted on the Wiki (http://st.icann.org/naralo/index.cgi? planning_next_steps_for_na_ralo) and supplement them as necessary. Then, I'd like to propose a conference call on either Monday or Tuesday, July 9th or 10th, at 3:00 pm EDT, 12:00 noon PDT, 9:00 am HST. The Proposed Agenda is: - San Juan Meeting Recap - Priorities for July-August - Outreach Efforts for More NA ALS - Staffing: GA Chair, Secretariat - NARALO Meeting Schedule through 2007. Let me know if we should add something. To keep participation high, I promise we'll end after one hour. Hard stop. We'll decide nothing on the call and defer all decisions to the list, so don't feel that you're going to miss out of you can't make it. Let me know off-list if you have a strong preference for one day over the other. -- Bret

6 8

Re: [NA-Discuss] Global At-Large Summit
by Michael Maranda July 4, 2007

July 4, 2007

We had a meeting to sketch some things out with people from many regions, while in PR. The consensus is that to do it well, we need sufficient planning. We have tentative agreement that we would formulate a collective request that this occur at the meeting in Europe in 2008. On 7/4/07, Jean Armour Polly <mom(a)netmom.com> wrote: > > Not to dissuade you on the idea of an at-large summit-- but before we > get too far on the idea of doing it in Los Angeles--we should see if > there is difficulty in getting a visa to the US these days. My > understanding is that (at least recently) ICANN has been loathe to > have meetings in the US because it's very hard for people to get > visas to attend. There may be another upcoming venue that is easier > (and possibly cheaper.) Can anyone confirm this or suggest a way to > find out? > JP > > _______________________________________________ > NA-Discuss mailing list > NA-Discuss(a)atlarge-lists.icann.org > > http://atlarge-lists.icann.org/mailman/listinfo/na-discuss_atlarge-lists.ic… > --- > Draft MoU with ICANN: > http://www.icannwiki.org/NA_RALO_MOU > > Draft Operating Principles: > http://www.icannwiki.org/NA_RALO_OP > > Draft Code of Conduct: > http://www.icannwiki.org/NARALO_Code_of_Conduct > -- --------------------------------------------------------------- Executive Director, CTCNet Chicago Chapter Co-Founder, Chicago Digital Access Alliance Co-Chair, Illinois Community Technology Coalition President, Association For Community Networking Support the efforts of the Chicago Digital Access Alliance: http://www.digitalaccessalliance.org

1 0

new working group forming!!!!
by Dharma Dailey July 3, 2007

July 3, 2007

People who are interested in planning for North American RALO activities in LA please contact me. -Dharma

2 1

Fwd: Re: limericks
by Wendy Seltzer July 2, 2007

July 2, 2007

From: Robin Gross <robin(a)ipjustice.org> Date:Mon, 02 Jul 2007 10:09:21 -0700 Thanks for sending these - they are really funny! I sent them on to the NCUC list for further amusement. Thanks again! Robin

1 0

Draft: GNSO Reform proposal
by Robert Guerra July 2, 2007

July 2, 2007

The folks from NCUC have asked for At-Large support on this, as such i'm forwarding to the list for your comments and review. regards Robert Begin forwarded message: > From: Milton L Mueller <mueller(a)SYR.EDU> > Date: July 1, 2007 12:01:51 AM EDT (CA) > To: NCUC-DISCUSS(a)LISTSERV.SYR.EDU > Subject: Draft: GNSO Reform proposal > > This document elaborates the ideas about GNSO reform that we > discussed in San Juan. The GNSO reform proposals that were floating > around in Puerto Rico have the potential to really solidify some > recent improvements in ICANN, and they also have the potential to > do a lot of damage if they go the wrong way. Please give this a > look when you get a chance. We need to be unified and informed on > this issue, and we need to get the ALAC people to work together > with us. > > > > Modifications and comments welcome. I think I will propose that > once we complete this document we do some diagrams and print up a > bunch for the Los Angeles meeting. > >

4 3

Planning / Next steps for NA RALO
by Robert Guerra July 2, 2007

July 2, 2007

For those who couldn't make it to San Juan, I thought you should know that a brainstorming/planning session was held on June 27th on possible NARALO activities in the coming 12 months. Details of the session can be found below @ at the following URL: https://st.icann.org/naralo/index.cgi?planning_next_steps_for_na_ralo it would be good to prioritize the list, and start moving forward. Thus, please comment on the wiki or via email .. regards Robert -- All the NARALO community is welcome to add suggestions to the list. We will first compile them and then prioritize them. North American outreach activities * Organize a thematic workshop during upcoming ICANN LA meeting * Organize or suggest orientation activities during the LA meeting * Develop initiative for recruitment of new potential ALSs * Produce resources to assist ALSs in educating their constituencies (and the public) about ICANN and its issues * Produce strategic plan regarding strategic ALS recruitment * Create a working group, and organize a workshop at the LA meeting, related to individual participation within At-Large * Target 50% growth in 2008 * Plan outreach activities in advance of LA meeting * Encourage new ALS outreach through peer groups of existing ALSs * Start the process for an At-Large Global Summit to involve ALSs and RALOs * Organize outreach meeting in the US similar to the one Jacob held in Toronto o Compile list of potential events where such meetings Structural activities * Select chair and secretariat * Launch initiative for At-Large to have voting representation on ICANN board * Launch initiative to review selection and appointment of ALAC members Policy activities * Rights of Registrants o What Registrants' rights do we advocate * New gTLDs * IDNs * IPv6 * DNSsec * Promote inclusion of youth into Fellowship program We should connect with research institutions to generate more research and discourse on topics of importance to At Large. (Understood that studies can be requested directly from ICANN - but this would integrate with an outreach strategy.) Global Policy Working Groups * Telecom * Identify other policy fields which impact ICANN policy * Social Responsibility * Youth Engagement *

3 2