- EURO-Discuss - lists.icann.org

ALAC Committee - Liaisons to other constituencies and processes
by ICANN At Large Staff Dec. 14, 2006

Dec. 14, 2006

Hello everyone! An interesting discussion has started in the European At-Large community list and considering the nature of the conversation I thought it would be sensible to acquaint those of you not following this discussion (there are many from other regions listening in) with an element of it. For those who are not aware, the At-Large Advisory Committee has the right to appoint a number of liaisons, and in the case of the NomCom, a number of actual members, who participate in the work of the other communities and key working groups and report back to ALAC on what is happening, as well as taking the view of ALAC, and by extension the At-Large community, back to those other constituencies. These positions therefore represent important opportunities for the point of view of the At-Large constituency to be represented, though there are various perspectives about how effective these positions can be, for a whole variety of reasons, which I hope those who have views will express for a more complete and rich debate. A question was raised about who is eligible to fill these positions: members of the ALAC only, or anyone. ICANN's legal staff were asked to provide a view on the subject, and have done so, making clear that since the Bylaws do not require membership in the ALAC in order to, for example, be the ALAC Board Liaison, it is for the ALAC to decide the manner in which these positions are appointed, elected, or otherwise filled. This is in line with ALAC practice, having had Bret Fausett, a non-ALAC member, as GNSO Liaison for some years now. The discussion has moved on to a request that there should be set rules of procedure with respect to these appointments, so that the community could see transparently who was being nominated, how they were being nominated, and on what basis selected. The ALAC did resolve to compile draft procedures relating to these matters, with Vittorio Bertola volunteering to take on this task. There are quite a few liaison positions. The posts are as follows: (5) seats on the Nominating Committee (out of a total of 17 voting members) (1) liaison to the ICANN Board (1) liaison to the GNSO (1) liaison to the ccNSO Additionally the following ad-hoc appointments/liaison positions currently exist: (1) liaison to the IDN Working Group (1) liaison to the WHOIS Working Group (1) liaison to the President's Advisory Committee on IDNs The provisions of the Bylaws with respect to these matters can be found at: http://www.icann.org/general/bylaws.htm. Article XI,s2(4) contains provisions related to the ALAC. Provisions related to the appointment, revocation of appointment, and/or reappointment appear in various places in the Bylaws in respect of the ccNSO and the GNSO, but in both cases, the ALAC may appoint, reappoint, or revoke an appointment, of its liaisons as it pleases and no term is defined for either. Note that there are particular provisions for the Regional At-Large Organisations to provide input into the appointment of the five voting seats on the Nominating Committee - with RALOs in later stages of formation in many regions, you may wish to consider how to provide input to ALAC with respect to these positions in due course. There is one seat per Geographic Region as defined by ICANN. I hope that this email has served to accurately convey the nature of the discussions and introduce (in particular) those who may be new to At-Large to this important subject. -- Regards, Nick Ashton-Hart ICANN At Large Main Tel: +44 (20) 8800-1011] USA Tel: +1 (202) 657-5460 Fax: +44 (20) 7681-3135 mobile: +44 (7774) 932798 email: nashton(a)spamcop.net Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart

3 3

At-Large Advisory Committee Election Results
by Nick Ashton-Hart Dec. 13, 2006

Dec. 13, 2006

I'm pleased to pass along the following important message announcing the leadership of the At-Large Advisory Committee for 2007. ---------- Forwarded message ---------- From: Bret Fausett <bfausett(a)internet.law.pro> Date: 07-Dec-2006 17:28 Subject: [alac] ALAC Election Results To: alac(a)icann.org As the non-voting Chair for today's election, I would like to provide the following report to the ALAC members and other interested members of the larger RALO, ALS, and At Large communities. Fifteen ALAC members were eligible to vote for ALAC officers. Fourteen expressed an intention to vote, with one member unavailable. I enlisted George Sadowsky to assist me, and together we counted and verified fourteen written ballots for three contested positions. Other officers for uncontested positions were elected by acclamation. I am pleased to announce the ALAC Officers for the coming year. Each officer will serve until the close of ICANN's annual meeting in 2007. * Chair: Annette Muehlberg * ALAC Liaison to the ICANN Board: Vittorio Bertola * ALAC Liaison to the ccNSO Council: Siavash Shahshahani * ALAC Liaison to the GNSO Council: Alan Greenberg * ALAC Representative to Whois Task Force: Wendy Seltzer * ALAC Representative to the GNSO's Working Group on IDNs: Hong Xue * ALAC Representative to the President's Advisory Committee on IDNs: Hong Xue We have two Vice-Chair positions, currently unfilled, which will be appointed or elected in the coming weeks. Many thanks to everyone who participated in the election. Bret Fausett -- -- Regards, Nick Ashton-Hart PO Box 32160 London N4 2XY United Kingdom UK Tel: +44 (20) 8800-1011 USA Tel: +1 (202) 657-5460 Fax: +44 (20) 7681-3135 mobile: +44 (7774) 932798 Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart FESTIVE GREETINGS! As per usual, in lieu of cards for friends and colleagues, I have made a donation in your name to Medecins Sans Frontieres, to help them provide medical care to those much less fortunate than ourselves.

9 25

Independent Reviews of ICANN Entities
by Nick Ashton-Hart Dec. 8, 2006

Dec. 8, 2006

FYI: On 8 December 2006 the ICANN Board approved the following schedule for independent review of ICANN entities: - Nominating Committee – estimated launch December 2006 - At-Large Advisory Committee – estimated launch February 2007 - Corporate Administration, including the ICANN Board – estimated launch July 2007 - Root Server System Advisory Committee – estimated launch October 2007 - Security and Stability Advisory Committee – January 2008 - ccNSO Supporting Organisation – July 2008 - Address Supporting Organisation – December 2008 In general, Board/staff steps for conducting independent reviews include: - Establishing terms of reference (TOR) (which includes a period for public comment) - Soliciting proposals for consultant/s to serve as independent reviewers - Selecting consultant/s - Managing and providing information for consultant's work - Public posting and information sharing on final report The Board's resolution also directs staff to post proposed Terms of Reference for the Nominating Committee review for public comment and further consideration. A copy of the resolution approved by the Board is included below. --- Schedule for Periodic Reviews of ICANN Structure and Operations Whereas Article IV, Section 4 of ICANN's Bylaws calls for the Board to cause periodic reviews of the performance and operation of each Supporting Organization, each Supporting Organization Council, each Advisory Committee (other than the Governmental Advisory Committee), and the Nominating Committee by an entity or entities independent of the organization under review. Whereas these reviews are intended to ensure an independent examination of the role and operation of key elements of ICANN, and are part of ICANN's ongoing commitment to its evolution and improvement. Whereas the Board Governance Committee has determined that, although not required by the Bylaws, a review of the Board would be appropriate and consistent with ICANN's commitment. Whereas these reviews will be conducted in an objective way by independent evaluators, under guidance from the Board on the review's terms of reference, and with opportunity for public review and comment on the terms of reference and on the results of the reviews. Whereas the Board Governance Committee considered the age, responsibilities, and activities of each entity to be reviewed, and considered the operational limitations for managing and implementing reviews, and approved a comprehensive review schedule. Whereas the Board Governance Committee approved a proposed plan for the review of the Nominating Committee as the next entity to be reviewed, and recommended that the Board post proposed Terms of Reference for this review for public comment. Nominating Committee – estimated launch December 2006 At-Large Advisory Committee – estimated launch February 2007 Corporate Administration, including the ICANN Board – estimated launch July 2007 Root Server System Advisory Committee – estimated launch October 2007 Security and Stability Advisory Committee – January 2008 ccNSO Supporting Organisation – July 2008 Address Supporting Organisation – December 2008 Whereas, after four cycles, the Nominating Committee, and its critical role in selecting individuals for ICANN leadership positions, is a priority candidate for independent review. Resolved (06.___), the Board asks the General Counsel to examine the Bylaws provisions relating to periodic review, and to recommend any appropriate changes to reflect the new schedule recommended by the Board Governance Committee. Resolved (06.___), the ICANN Board agrees with the comprehensive review schedule and the proposed plan for the review of the Nominating Committee approved by the Board Governance Committee, and directs staff to execute the reviews as scheduled and to post proposed Terms of Reference for the Nominating Committee review for public comment and further consideration. -- -- Regards, Nick Ashton-Hart PO Box 32160 London N4 2XY United Kingdom UK Tel: +44 (20) 8800-1011 USA Tel: +1 (202) 657-5460 Fax: +44 (20) 7681-3135 mobile: +44 (7774) 932798 Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart FESTIVE GREETINGS! As per usual, in lieu of cards for friends and colleagues, I have made a donation in your name to Medecins Sans Frontieres, to help them provide medical care to those much less fortunate than ourselves.

1 0

Fw: At-Large Liaison to the Board
by Nick Ashton-Hart Dec. 8, 2006

Dec. 8, 2006

Dear European At-Large and ALAC members, please see below with respect to the questions raised by Wolfgang. -- Regards, Nick Ashton-Hart 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: nashton(a)spamcop.net Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart -----Original Message----- From: Denise Michel <denise.michel(a)icann.org> Date: Fri, 08 Dec 2006 10:31:14 To:Nick Ashton-Hart <nashton(a)spamcop.net> Subject: At-Large Liaison to the Board Nick, Regarding your question about the At-Large Advisory Committee liaison to ICANN's Board -- there is nothing in ICANN's bylaws that require the ALAC to appoint an ALAC member (or a member of a RALO or At-Large Structure, for that matter) as its liaison to ICANN's Board. The relevant provision from the bylaws is included below. Since its inception, the ALAC has not established membership requirements for liaisons it appoints to the Board, the SO Councils, or other entities and, in the past, the ALAC has appointed both ALAC members and non-ALAC members to liaison positions. Let me know if you have any further questions. Denise Denise Michel Vice President, Policy Development ICANN denise.michel(a)icann.org e. The ALAC shall annually appoint one non-voting liaison to the ICANN Board of Directors, without limitation on re-appointment, and shall, after consultation with each RALO, annually appoint five voting delegates (no two of whom shall be citizens of countries in the same Geographic Region, as defined according to Section 5 of Article VI) to the Nominating Committee.

1 0

Latin America / Caribbean ICANN MoU Signing Ceremony
by Nick Ashton-Hart Dec. 6, 2006

Dec. 6, 2006

Hello At-Large World! FYI, the first Regional At-Large Organisation was born yesterday in Sao Paulo. You can see a YouTube short video of the ceremony below - the webcast made as part of the conference yesterday will be available just after the meeting is over. I'll give the URL to everyone as soon as I have it. In the meantime, here's the YouTube version! http://www.youtube.com/watch?v=o1Rmpp0VLQQ -- Regards, Nick Ashton-Hart PO Box 32160 London N4 2XY United Kingdom UK Tel: +44 (20) 8800-1011 USA Tel: +1 (202) 657-5460 Fax: +44 (20) 7681-3135 mobile: +44 (7774) 932798 Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart FESTIVE GREETINGS! As per usual, in lieu of cards for friends and colleagues, I have made a donation in your name to Medecins Sans Frontieres, to help them provide medical care to those much less fortunate than ourselves.

1 0

European Region WiKi
by Nick Ashton-Hart Dec. 5, 2006

Dec. 5, 2006

Hello all! You're about to get an invitation to a new Wiki that's been setup for the European Region - actually, every region is getting one - which is setup in a 'fishbowl' mode. The idea is that all ALSes can edit the site, but the general public can only view it. Before too long, the www.euralo.org website will point to the wiki. Why? Simple - so the community can manage and maintain its own online home, allowing those it wishes to edit to be able to do so, and giving the general public open transparent access without the problems of bots erasing work, or adding porn, which we now experience on the WECANN! wiki. Once everyone has an account I would very much like to move the RALO documents over to this wiki. The bot activity on the WECANN site is getting worse. The last updates I did a few weeks ago I actually had to do twice - bots came in and changed the text literally during my edits. This is another step - the mailing lists being the first - in providing transparent, user-manageable information tools. We hope you like it! -- Regards, Nick Ashton-Hart 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: nashton(a)spamcop.net Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart

1 0

Re: [EURO-Discuss] [Euralo-ml] Completing Work on the Bylaws
by Nick Ashton-Hart Nov. 29, 2006

Nov. 29, 2006

Depends upon what you meant by the line: did you mean that I was altering the text, as I mentioned? If so, that's how I remember it and I did already make that change. That's the only clarifying I remember that I was to do. Nick On 29/11/06, Dr. Christoph Bruch <bruch(a)humanistische-union.de> wrote: > Hi Nick: > > I rephrased the sentence concerning the criteria for the place of > incorporation. > > Did I get you right, you are objecting to the sentence > "Will clarify his suggestion: role and relationship of GA and standing > committee"? > > I will delete this sentence if that is the case. > > Christoph > > > ______________________________________________ > Dr. Christoph Bruch Humanistische Union > Neue Christstr. 6 Greifswalder Str. 4 > 14059 Berlin 10405 Berlin > Tel/Fax: (030) 32103282Tel: (030) 20450256 > Fax: (030) 20450257 > > -----Ursprüngliche Nachricht----- > Von: euralo-ml-bounces(a)euralo.eu [mailto:euralo-ml-bounces@euralo.eu] Im > Auftrag von Nick Ashton-Hart > Gesendet: Dienstag, 28. November 2006 23:10 > An: EURALO Mailing-List; euro-als(a)atlarge-lists.icann.org > Betreff: Re: [Euralo-ml] Completing Work on the Bylaws > > Just a couple of points: > > On place of incorporation, I didn't suggest those two criteria, those > were the criteria which were decided upon in Berlin (minor point but I > thought I'd mention it). > > With respect to the General Assembly: I don't believe I was to clarify > the role with respect to the Standing Committee, except for the > one-word change which was suggested (which is on the Wiki). Perhaps > that's what you meant Christophe :) > > On 28/11/06, bruch <bruch(a)zedat.fu-berlin.de> wrote: > > Dear All, > > > > please find attached my notes from the Athens meeting. > > > > I marked them as draft in case any of the participants has additions or > > corrections. > > > > Best > > > > Christoph > > > > > > _____________________ > > Dr. Christoph Bruch > > Neue Christstr. 6 > > 14059 Berlin > > Tel./Fax: +49 (0)30 - 3210 3282 > > > > > > -----Ursprüngliche Nachricht----- > > Von: euralo-ml-bounces(a)euralo.eu [mailto:euralo-ml-bounces@euralo.eu] Im > > Auftrag von Nick Ashton-Hart > > Gesendet: Samstag, 18. November 2006 16:28 > > An: EURALO Mailing-List > > Cc: philippe(a)epistrophe.fr > > Betreff: [Euralo-ml] Completing Work on the Bylaws > > > > Hello everyone! > > > > I'm sorry it has taken this long to get back to you after the IGF Meeting, > > but we are in the throes of preparing for the Sao Paulo meeting which is > > consuming pretty much everyone in any way connected with it. You will at > > some point be receiving further notes from this meeting courtesy of > > Christophe Bruch. > > > > I have updated the Wiki - removing more bot spam - and including the > > amendments which were discussed and agreed by the participants in the EU > ALS > > Meeting at the Internet Governance Forum. Of course anyone is completely > > within their rights to put forward a contrary view. > > > > What was suggested at that meeting, to make it easier to see changes > > proposed in these last stages of editing the text, is that new text would > be > > in BOLD, and deleted text would be in brackets and ITALICISED. > > > > Accordingly you will find that there are a few bold provisions now - and > > there are details in the annotated discussion page showing the history of > > revisions. > > > > As you'll see below, we are technically at the end of the period for > > proposing further edits to the text. However, I have been to busy to do > all > > of the work associated with the various stages. The Sao Paulo meeting is > in > > 10 days and I know several of us will be fully engaged in preparing to go > to > > it. > > > > May I suggest the following: > > > > 1) The two week period for putting forward additional provisions is > > continued through the 10th December. > > > > 2) At that point, I will send out the summaries as provided below for the > > week of the 20th - 26th November, and the following week we will proceed > as > > if it was the period from 27th November to 3 December. > > > > This will still allow us to (hopefully) conclude the Bylaws by the end of > > the year. > > > > Naturally any thoughts that anyone has are most welcomed! > > > > > > Begin forwarded message: > > > > > > From: "Nick Ashton-Hart" <nashton(a)spamcop.net> > > Date: 1 November 2006 17:52:41 GMT > > To: "EURALO Mailing-List" <euralo-ml(a)euralo.eu> > > Subject: Procedure for Completing Work on the Bylaws > > > > Good evening all: > > > > As a number of you have noted, there is a necessity for additional > > time to be inserted in the procedure that was proposed (and which > no > > objections were raised about). After talking with Annette, > Roberto, > > and others, we propose that the first stage would insert an > > additional > > two weeks into the phase which was to conclude this Monday. > > > > This, then, would be the timeline, which of course will be > discussed > > tomorrow: > > > > PERIOD THROUGH 19th NOVEMBER > > > > During this period: > > > > 1) Everyone should look at the text as a whole. If they: > > a. OBJECT to a provision, say so clearly, state the > objection, > > and > > propose the modification they wish to see –in formal text for > direct > > inclusion in the document – along with the reason for the > objection; > > b. WISH TO ADD a provision, make that clear, and propose the > > change – > > send the list the actual text for inclusion in the document, and > the > > reasons for proposing the addition.. > > c. WISH TO COMMENT ABOUT OR QUERY a provision: state clearly > > whether > > it is a comment or query, followed by the query or comment. > > > > NOTE: It is not necessary to say you agree with anything. SILENCE > > WILL > > BE TAKEN AS AGREEMENT. > > > > If you wish some assistance in drafting a provision you wish to > > change/add, Nick will be happy to help you; just send him a note > and > > ask him to ring, or to comment on something you have drafted. > > > > As amendments and proposals come in, Nick will include them in the > > Wiki, again along with the proposer, the date and subject of the > > email > > in which the proposal was made. > > > > Nick will send a reminder email at the beginning of the week of > the > > 13th November, reminding everyone that one week remains to make > the > > comments requested above. He will place a call to each ALS > > representative during the course of the week to make sure they > > understand the process, and to offer any assistance in drafting > that > > may be required if they have an issue. He will also ask if any > ALS > > is > > happy to let the others decide on the remaining issues; where an > ALS > > states that is the case, Nick will tell them that they need to > make > > that clear by a posting to the list. Of course, any ALS may change > > their mind about this at any point; we just want everyone to know > > that > > none of the ALSes have somehow missed out on what is going on. > > > > WEEK OF 20-26 NOVEMBER > > > > At the beginning of the week, Nick will send out: > > > > 1) An email with all sections for which no comments have been > > received, and no amendments proposed or objections raised. The > email > > will make clear that this is the case, and clearly state that if > no > > objection is received in the course of the week, those clauses for > > which no objection or amendments have been proposed will be > presumed > > to be accepted by consensus and closed to future amendments. > > 2) An individual email for each section where there are > > multiple > > options, or where amendments have been suggested, with > instructions > > at > > the top which ask for the following actions, by the end of the > week: > > > > 1) If changes have been proposed in the previous week, draw > > attention to them; > > 2) Where there are multiple options for a given clause, draw > > attention > > to it and ask that everyone select the options in order of > > acceptability, with the first option chosen being most preferred, > > and > > the last option chosen being least preferred. > > 3) If any options are substantially the same (or have the > same > > effect), it is hoped that the proposers will combine them into one > > option, in order to leave only substantively different options "on > > the > > table". > > > > NOTE: It is not necessary to say you agree with any element. > SILENCE > > WILL BE TAKEN AS AGREEMENT. > > > > Nick will ring around to each ALS near the end of the week to > again > > make sure that nobody has misunderstood the deadlines for > > responding, > > or missed out on any of the emails sent as above, or has any > issues > > to > > raise otherwise. > > > > As with the previous week, As amendments and proposals come in, > Nick > > will include them in the Wiki, again along with the proposer, the > > date > > and subject of the email in which the proposal was made. > > > > WEEK OF 27 NOVEMBER - 3 DECEMBER > > > > At the beginning of the week, an email with a summary of > > comments/objections received in the previous week on the various > > individual sections will be sent out. Where multiple options were > > selected in order of acceptability, all but the two most > acceptable > > will be removed. There are three types of emails that will be sent > > out, corresponding to the individual emails from the previous week > > and > > covering the same areas of the text > > > > 1) Where a given section was sent out the previous week with > no > > comments received or objections raised, if no objections were > made, > > that section will be assumed to be agreed and closed for > amendments. > > 2) Where a section was sent out with amendments proposed, if > no > > objections were received to an amendment, that amendment will be > > assumed to be agreed and closed for further amendments. > > 3) Where remaining sections are still not agreed, a summary > of > > the > > comments received will be provided. The group will then have to > > decide > > on the mailing list how to resolve remaining areas of > disagreement. > > > > The Wiki will be updated as before to reflect the current state of > > the > > whole text, to allow reading of it there. > > > > ABOUT THE SILENCE = AGREEMENT element of the process: This is > > proposed > > not because anyone wishes to exclude any views, but in the > interest > > of > > finishing work on the Bylaws in a reasonable timeframe. If a > > positive > > vote was required at each stage of the process, it would be very > > complex to get to an agreement in any reasonable timeframe. As a > > consequence, we recommend the silent assent procedure but we want > > everyone to know that everyone's views are wanted; everyone's > point > > of > > view will be equally respected, and a part of the reason Nick will > > telephone around to all ALSes twice is to make sure that nobody > has > > accidentally forgotten or overlooked deadlines, so that all ALSes > > can > > be assured of having an equal voice in the provisions of the > bylaws. > > > > ---- > > The following was the procedure as originally proposed. It is > > reproduced here so that everyone can see the variations between > what > > is above, which are minor, and the original: > > > > > > WEEK OF 9-15 OCTOBER > > > > Nick will edit the text on the Wiki so that the source of all > > changes > > from the text as at the end of the Berlin Meeting on 17th > September > > are clearly documented. This will include showing the proposer of > > the > > change, the date and subject line of the email in which the change > > is > > discussed, so that it is easier and more transparent process-wise > > for > > everyone to understand the evolution of the document, especially > > with > > the rapid development of the last two weeks. > > > > Once this is done, he will > > > > 1) Announce that the changes just mentioned have been made, and in > > that announcement also send out the following documents: > > > > 1) The text as at the end of the 17th September meeting, in > > Microsoft > > Word, with the changes necessary to correct English grammar and > > style > > errors shown as redlined additions and deletions from the text; > > 2) The same text, with all the necessary English revisions > > approved, > > so that it is easy to read the output. > > > > The email will also let people know that in the coming week: > > > > 1) Everyone should look at the text as a whole. If they: > > a. OBJECT to a provision, say so clearly, state the > objection, > > and > > propose the modification they wish to see –in formal text for > direct > > inclusion in the document – along with the reason for the > objection; > > b. WISH TO ADD a provision, make that clear, and propose the > > change – > > send the list the actual text for inclusion in the document, and > the > > reasons for proposing the addition.. > > c. WISH TO COMMENT ABOUT OR QUERY a provision: state clearly > > whether > > it is a comment or query, followed by the query or comment. > > > > NOTE: It is not necessary to say you agree with anything. SILENCE > > WILL > > BE TAKEN AS AGREEMENT. > > > > If you wish some assistance in drafting a provision you wish to > > change/add, Nick will be happy to help you; just send him a note > and > > ask him to ring, or to comment on something you have drafted. > > > > As amendments and proposals come in, Nick will include them in the > > Wiki, again along with the proposer, the date and subject of the > > email > > in which the proposal was made. > > > > WEEK OF 16-22 OCTOBER > > > > Nick will send a reminder email to everyone to ask him or her to > > make > > the comments as requested immediately above during the course of > the > > week. He will then place a call to each ALS representative during > > the > > course of the week to make sure they understand the process, and > to > > offer any assistance in drafting that may be required if they have > > an > > issue. He will also ask if any ALS is happy to let the others > > decide > > on the remaining issues; where an ALS states that is the case, > Nick > > will tell them that they need to make that clear by a posting to > the > > list. Of course, any ALS may change their mind about this at any > > point; we just want everyone to know that none of the ALSes have > > somehow missed out on what is going on. > > > > At the end of the week, Nick will send out: > > > > 1) An email with all sections for which no comments have been > > received, and no amendments proposed or objections raised. The > email > > will make clear that this is the case, and clearly state that if > no > > objection is received in the course of the week, those clauses for > > which no objection or amendments have been proposed will be > presumed > > to be accepted by consensus and closed to future amendments. > > 2) An individual email for each section where there are > > multiple > > options, or where amendments have been suggested, with > instructions > > at > > the top which ask for the following actions, by the end of the > week: > > > > 1) If changes have been proposed in the previous week, draw > > attention to them; > > 2) Where there are multiple options for a given clause, draw > > attention > > to it and ask that everyone select the options in order of > > acceptability, with the first option chosen being most preferred, > > and > > the last option chosen being least preferred. > > 3) If any options are substantially the same (or have the > same > > effect), it is hoped that the proposers will combine them into one > > option, in order to leave only substantively different options "on > > the > > table". > > > > NOTE: It is not necessary to say you agree with any element. > SILENCE > > WILL BE TAKEN AS AGREEMENT. > > > > Nick will ring around to each ALS near the end of the week to > again > > make sure that nobody has misunderstood the deadlines for > > responding, > > or missed out on any of the emails sent as above, or has any > issues > > to > > raise otherwise. > > > > As with the previous week, As amendments and proposals come in, > Nick > > will include them in the Wiki, again along with the proposer, the > > date > > and subject of the email in which the proposal was made. > > > > WEEK OF 23-29 OCTOBER > > > > At the beginning of the week, an email with a summary of > > comments/objections received in the previous week on the various > > individual sections will be sent out. Where multiple options were > > selected in order of acceptability, all but the two most > acceptable > > will be removed. There are three types of emails that will be sent > > out, corresponding to the individual emails from the previous week > > and > > covering the same areas of the text > > > > 1) Where a given section was sent out the previous week with > no > > comments received or objections raised, if no objections were > made, > > that section will be assumed to be agreed and closed for > amendments. > > 2) Where a section was sent out with amendments proposed, if > no > > objections were received to an amendment, that amendment will be > > assumed to be agreed and closed for further amendments. > > 3) Where remaining sections are still not agreed, a summary > of > > the > > comments received will be provided. The group will then have to > > decide > > on the mailing list how to resolve remaining areas of > disagreement. > > > > The Wiki will be updated as before to reflect the current state of > > the > > whole text, to allow reading of it there. > > > > ABOUT THE SILENCE = AGREEMENT element of the process: This is > > proposed > > not because anyone wishes to exclude any views, but in the > interest > > of > > finishing work on the Bylaws in a reasonable timeframe. If a > > positive > > vote was required at each stage of the process, it would be very > > complex to get to an agreement in any reasonable timeframe. As a > > consequence, we recommend the silent assent procedure but we want > > everyone to know that everyone's views are wanted; everyone's > point > > of > > view will be equally respected, and a part of the reason Nick will > > telephone around to all ALSes twice is to make sure that nobody > has > > accidentally forgotten or overlooked deadlines, so that all ALSes > > can > > be assured of having an equal voice in the provisions of the > bylaws. > > > > -- > > -- > > Regards, > > > > Nick Ashton-Hart > > PO Box 32160 > > London N4 2XY > > United Kingdom > > UK Tel: +44 (20) 8800-1011 > > USA Tel: +1 (202) 657-5460 > > Fax: +44 (20) 7681-3135 > > mobile: +44 (7774) 932798 > > Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / > > Skype: nashtonhart > > Online Bio: https://www.linkedin.com/in/ashtonhart > > > > > > > > > > _______________________________________________ > > Euralo-ML mailing list > > Euralo-ML(a)euralo.eu > > http://lists.euralo.eu/mailman/listinfo/euralo-ml > > > > > > > > > > > -- > -- > Regards, > > Nick Ashton-Hart > PO Box 32160 > London N4 2XY > United Kingdom > UK Tel: +44 (20) 8800-1011 > USA Tel: +1 (202) 657-5460 > Fax: +44 (20) 7681-3135 > mobile: +44 (7774) 932798 > Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / > Skype: nashtonhart > Online Bio: https://www.linkedin.com/in/ashtonhart > > FESTIVE GREETINGS! As per usual, in lieu of cards for friends and > colleagues, I have made a donation in your name to Medecins Sans > Frontieres, to help them provide medical care to those much less > fortunate than ourselves. > _______________________________________________ > Euralo-ML mailing list > Euralo-ML(a)euralo.eu > http://lists.euralo.eu/mailman/listinfo/euralo-ml > > _______________________________________________ > Euralo-ML mailing list > Euralo-ML(a)euralo.eu > http://lists.euralo.eu/mailman/listinfo/euralo-ml > -- -- Regards, Nick Ashton-Hart PO Box 32160 London N4 2XY United Kingdom UK Tel: +44 (20) 8800-1011 USA Tel: +1 (202) 657-5460 Fax: +44 (20) 7681-3135 mobile: +44 (7774) 932798 Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart FESTIVE GREETINGS! As per usual, in lieu of cards for friends and colleagues, I have made a donation in your name to Medecins Sans Frontieres, to help them provide medical care to those much less fortunate than ourselves.

1 0

EURALO list completely incorporated into new list server
by Nick Ashton-Hart Nov. 29, 2006

Nov. 29, 2006

Hello all! I have now incorporated all subscribers in the old euralo-ml mailing list into the new european regional lists. euro-als(a)atlarge-lists.icann.org: Only accredited ALSes belong. euro-discuss(a)atlarge-lists.icann.org: all of those who are subscribed to euralo-ml are subscribed. Needless to say there are many other lists which you can subscribe to in the At Large world now - feel free - and also several useful new lists that you can send to and get the relevant staff people you need (travel-staff(a)atlarge-lists.icann.org is particularly useful; now only one email will get your TARF requests handled for example). The address for the lists is: http://atlarge-lists.icann.org/mailman/ listinfo -- Regards, Nick Ashton-Hart 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: nashton(a)spamcop.net Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart

1 0