May 2018 - ALAC - lists.icann.org

Fwd: [SOAC-Leaders-ICANNMeeting-Planning] The cross community session on GDPR Compliance, Access to WHOIS and Accreditation/ICANN62
by León Felipe Sánchez Ambía June 3, 2018

June 3, 2018

Dear Alan, Is this something you ir other ALAC colleagues are following? I think it would be good if the ALAC was involved in the organization and discussion in Panama. Kind regards León Enviado desde mi iPhone Inicio del mensaje reenviado: > De: farzaneh badii <farzaneh.badii(a)gmail.com> > Fecha: 30 de mayo de 2018, 5:38:45 p. m. CDT > Para: SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning(a)icann.org> > Asunto: [SOAC-Leaders-ICANNMeeting-Planning] The cross community session on GDPR Compliance, Access to WHOIS and Accreditation/ICANN62 > > Dear all, > > As we discussed and agreed on 2 May during our production call, GDPR Compliance, Access to WHOIS and Accreditation should be a cross-community session and interested community members must be able to participate in its preparation and on the panel. > > As ICANN 62 is fast approaching, I was wondering how interested stakeholders groups and advisory committees can be involved with organizing and participating. I am not quite sure which ICANN staff member was assigned to this so appreciate a response. > > > > Best > > Farzaneh > _______________________________________________ > SOAC-Leaders-ICANNMeeting-Planning mailing list > SOAC-Leaders-ICANNMeeting-Planning(a)icann.org > https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning

6 5

Fwd: ALAC Response to recent letters regarding At-Large Review
by Alan Greenberg May 29, 2018

May 29, 2018

FYI. Alan >To: Cherine Chalaby <cherine.chalaby(a)board.icann.org>, Khaled Koubaa ><Khaled.koubaa(a)board.icann.org>, Leon Felipe Sanchez Ambia ><leonfelipe(a)sanchez.mx> >From: Alan Greenberg <alan.greenberg(a)mcgill.ca> >Subject: ALAC Response to recent letters regarding At-Large Review >Cc: Board Operations <board-ops-team(a)icann.org>, At-Large Staff ><staff(a)atlarge.icann.org> > >Dear Cherine and Khaled, > >Please find attached a letter to the OEC and the Board in reply to >the recent CPH and NCSG letters regarding the At-Large Review. > >The letter was developed over the last three days with the >involvement and support of the ALAC and its RALO Regional Leaders. > >Warm regards, Alan

14 21

Congratulations to Seun
by Alan Greenberg May 29, 2018

May 29, 2018

It is my pleasure to tell you that at its meeting in Dakar earlier this month, Seun was appointed Vice Chair of AFRINIC Board. Alan

20 19

Re: [ALAC] Fwd: ALAC Response to recent letters regarding At-Large Review
by Alan Greenberg May 28, 2018

May 28, 2018

To be clear, what I meant to say was let's NOT make comments... At 28/05/2018 04:50 PM, Alan Greenberg wrote: >This is a public list. Let's making comments targeted at or about >individuals here. Alan > >At 28/05/2018 04:44 PM, Judith Hellerstein wrote: > >>HI Carlton, >> >>Thanks for this. It is no doubt the work of Ayden, Michael , and >>others who have posted their venum on ICANN bad attitude. I am at >>a loss to understand what really is their problem with us. Are they >>upset that we have interpretation into multiple languages? We share >>the same goals as was described in our similar responses to the >>loss of CROP funding. So not really clear what their problems >>are. the GNSO has a similar structure in that they have counselors >>and then have an excom which is like our ALT have alerted Renata >>Aquino and asked her to get to the bottom of this. Let's hope she >>can help calm all these ruffled feathers in GNSO and get some resolution >> >>Best, >> >>Judith >> >> >>_________________________________________________________________________ >>Judith Hellerstein, Founder & CEO >>Hellerstein & Associates >>3001 Veazey Terrace NW, Washington DC 20008 >>Phone: (202) 362-5139 Skype ID: judithhellerstein >>Mobile/Whats app: +1202-333-6517 >>E-mail: >><mailto:Judith@jhellerstein.com>Judith(a)jhellerstein.com Website: >><http://www.jhellerstein.com>www.jhellerstein.com >>Linked In: >><http://www.linkedin.com/in/jhellerstein/>www.linkedin.com/in/jhellerstein/ >>Opening Telecom & Technology Opportunities Worldwide >> >> >> >>On 5/28/2018 4:32 PM, Carlton Samuels wrote: >>>Recall my contention that the NCSG/CPH knockdown narrative was a >>>bee in a bonnet? >>> >>>Well, a correspondent just shared with me an interesting link >>>which led to a bit of content from a yet unidentified shadowy group: >>> >>><https://www.atlarge.watch/>https://www.atlarge.watch/ >>> >>>Quite apart from statements that could reasonably be characterised >>>as blood libels, I have excerpted and reproduced here - I was so >>>tempted to use a porn-related metaphor to convey meaning but I >>>cannot now think of an obsequious way in language to mollify the >>>thought police - the gravamen of this tilt. >>> >>>"Ultimately, we seek to strengthen non-commercial participation in >>>ICANN's agenda-setting and decision-making processes." >>> >>>I doubt it would surprise anyone familiar with politics 101 >>>ICANN-style to know the WHOIS record is privacy-protected. The >>>domain was registered on the 26th May. >>> >>>Here's a useful analogy. These virtuous souls, I'm sure men and >>>women all good and true, would not wish to bother you with their >>>identities. Compare that to the situation where the PIIs of every >>>ALAC member is a public record. >>> >>>Can't get clearer than that. >>> >>>- Carlton >>> >>>On Mon, 28 May 2018, 7:44 am Hadia Abdelsalam Mokhtar EL miniawi, >>><<mailto:Hadia@tra.gov.eg>Hadia(a)tra.gov.eg> wrote: >>>Thank you Alan, looking forward to the response. >>>Kind Regards >>>Hadia >>>-----Original Message----- >>>From: ALAC [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf >>>Of Alan Greenberg >>>Sent: Saturday, May 26, 2018 12:11 AM >>>To: ALAC >>>Subject: [ALAC] Fwd: ALAC Response to recent letters regarding >>>At-Large Review >>>FYI. Alan >>> >To: Cherine Chalaby >>> <<mailto:cherine.chalaby@board.icann.org>cherine.chalaby(a)board.icann.org>, >>> Khaled Koubaa >>> ><<mailto:Khaled.koubaa@board.icann.org>Khaled.koubaa(a)board.icann. >>> org>, Leon Felipe Sanchez Ambia >>> ><<mailto:leonfelipe@sanchez.mx>leonfelipe(a)sanchez.mx> >>> >From: Alan Greenberg >>> <<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> >>> >Subject: ALAC Response to recent letters regarding At-Large Review >>> >Cc: Board Operations >>> <<mailto:board-ops-team@icann.org>board-ops-team(a)icann.org>, At-Large Staff >>> ><<mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org> >>> > >>> >Dear Cherine and Khaled, >>> > >>> >Please find attached a letter to the OEC and the Board in reply to the >>> >recent CPH and NCSG letters regarding the At-Large Review. >>> > >>> >The letter was developed over the last three days with the involvement >>> >and support of the ALAC and its RALO Regional Leaders. >>> > >>> >Warm regards, 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+%28…>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… >>> >>> >>> >>> >>> >>>_______________________________________________ >>>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… >> >>Content-Type: text/plain; charset="us-ascii" >>Content-Transfer-Encoding: 7bit >>Content-Disposition: inline >>X-Microsoft-Exchange-Diagnostics: >> >>1;YTOPR01MB0396;27:Q5bBNlJYgX4kmokJswjA/qFobOWR33eqwZDsLpkQ/U/Y1mLNp115pwDGoPXGEWiH+qeSe4fNswFPi3WOxK+s5uUMDQuHxi0SrJNPY1pFVeyiH109JoLUCJCyiwFurnsW >>X-Microsoft-Antispam-Message-Info: >> >>i01TBnEXCdxIIp4mXYn6QVdGflr2jM2yI9z6P0T4j0t48YNJDc/KMWls8jqHdR2PrmvA5lFOj38MGwEzuClQTzyWT8exKH3TCK5Yr4UYHiks3iza4A/PsqSUkCMsSru+yHdAjfD1iVcZyS3StLopMgEOOUDHiNe4mmaAHF+H8T8z6eVmxaK2ob1gnktrtPpq2uOjGGAhMrt0N0OuNKMBOdLfkpR7gHwWdO5+2Tdm22ww46CSwRKMFVj4YEANEkEzgLhyy67vSepyLPKk7GBSlAPYZHXl2m1xgM3avBWy5d0X1lb0iXNxgSGFPkHaFTLMg6KeWtTP7FPMxO99O1ziyJjiudIlRIXjXYtCRn7QCiiHBMQDhYaabsJqT1CJiKtJfkkMiHdmyXznvdvdhSIQi8C2S7TUl3iNLZaIl8ymzLlL/NOp2o3mBw/GjIZCapK9ym3A2jVJvx2msn751r/YxIqP7psmuCKAVp7MqFqDq5GFKlHQ76xhNCjzKEwzoVrD >> >>_______________________________________________ >>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] Fwd: ALAC Response to recent letters regarding At-Large Review
by Alan Greenberg May 28, 2018

May 28, 2018

As it turns out, the domain registration is not only protected by a privacy service but one that uses non-compliant contact information. Just an accident I am sure. The Twitter account page it points to has a letter on it that identifies a problem that the ALAC wants to be involved in policy, coincidentally (but nothing more) similar to a section of the NCSG letter. They are very concerned that if we are more active in policy work, we will overextend ourselves. Their concern is quite touching. Alan At 28/05/2018 04:32 PM, Carlton Samuels wrote: >Recall my contention that the NCSG/CPH knockdown narrative was a bee >in a bonnet? > >Well, a correspondent just shared with me an interesting link which >led to a bit of content from a yet unidentified shadowy group: > ><https://www.atlarge.watch/>https://www.atlarge.watch/ > >Quite apart from statements that could reasonably be characterised >as blood libels, I have excerpted and reproduced here - I was so >tempted to use a porn-related metaphor to convey meaning but I >cannot now think of an obsequious way in language to mollify the >thought police - the gravamen of this tilt. > >"Ultimately, we seek to strengthen non-commercial participation in >ICANN's agenda-setting and decision-making processes." > >I doubt it would surprise anyone familiar with politics 101 >ICANN-style to know the WHOIS record is privacy-protected. The >domain was registered on the 26th May. > >Here's a useful analogy. These virtuous souls, I'm sure men and >women all good and true, would not wish to bother you with their >identities. Compare that to the situation where the PIIs of every >ALAC member is a public record. > >Can't get clearer than that. > >- Carlton > >On Mon, 28 May 2018, 7:44 am Hadia Abdelsalam Mokhtar EL miniawi, ><<mailto:Hadia@tra.gov.eg>Hadia(a)tra.gov.eg> wrote: >Thank you Alan, looking forward to the response. > >Kind Regards >Hadia > >-----Original Message----- >From: ALAC [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf >Of Alan Greenberg >Sent: Saturday, May 26, 2018 12:11 AM >To: ALAC >Subject: [ALAC] Fwd: ALAC Response to recent letters regarding At-Large Review > >FYI. Alan > > >To: Cherine Chalaby > <<mailto:cherine.chalaby@board.icann.org>cherine.chalaby(a)board.icann.org>, > Khaled Koubaa > ><<mailto:Khaled.koubaa@board.icann.org>Khaled.koubaa(a)board.icann.or > g>, Leon Felipe Sanchez Ambia > ><<mailto:leonfelipe@sanchez.mx>leonfelipe(a)sanchez.mx> > >From: Alan Greenberg > <<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> > >Subject: ALAC Response to recent letters regarding At-Large Review > >Cc: Board Operations > <<mailto:board-ops-team@icann.org>board-ops-team(a)icann.org>, At-Large Staff > ><<mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org> > > > >Dear Cherine and Khaled, > > > >Please find attached a letter to the OEC and the Board in reply to the > >recent CPH and NCSG letters regarding the At-Large Review. > > > >The letter was developed over the last three days with the involvement > >and support of the ALAC and its RALO Regional Leaders. > > > >Warm regards, 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…

2 1

Re: [ALAC] Fwd: ALAC Response to recent letters regarding At-Large Review
by Alan Greenberg May 26, 2018

May 26, 2018

Thanks Dev. No opportunity to change it now, but I am not particularly worried that it will be misinterpreted by the OEC. Alan At 26/05/2018 03:21 PM, Dev Anand Teelucksingh wrote: >Great response. However on page 6 re: the ALT, this paragraph > >"It is the ALACâs understanding that many other groups in ICANN have a >leadership team (often called an Executive Committee), including the Board >and the NCSG. In many such cases, including the Board, this group actually >does have significant decision-making rights" > >The last sentence isn't clear as to "this group" is referring to, with a >potential interpretation that "this group" is the ALT. I presume this is >what you were intending > >"It is the ALACâs understanding that many other groups in ICANN (such as >the Board and the NCSG) have a leadership team (often called an Executive >Committee). Such leadership teams do have significant decision-making >rights." > >Kind Regards, > >Dev Anand > > >On Fri, May 25, 2018 at 7:48 PM Maureen Hilyard <maureen.hilyard(a)gmail.com> >wrote: > > > A good summary of our discussions. We can now look forward to the >Board's response/s to all the letters. > > > > > On Fri, May 25, 2018 at 12:11 PM, Alan Greenberg > > <alan.greenberg(a)mcgill.ca> >wrote: > > >> FYI. Alan > > >>> To: Cherine Chalaby <cherine.chalaby(a)board.icann.org>, Khaled Koubaa < >Khaled.koubaa(a)board.icann.org>, Leon Felipe Sanchez Ambia < >leonfelipe(a)sanchez.mx> > >>> From: Alan Greenberg <alan.greenberg(a)mcgill.ca> > >>> Subject: ALAC Response to recent letters regarding At-Large Review > >>> Cc: Board Operations <board-ops-team(a)icann.org>, At-Large Staff < >staff(a)atlarge.icann.org> > > >>> Dear Cherine and Khaled, > > >>> Please find attached a letter to the OEC and the Board in reply to the >recent CPH and NCSG letters regarding the At-Large Review. > > >>> The letter was developed over the last three days with the involvement >and support of the ALAC and its RALO Regional Leaders. > > >>> Warm regards, Alan > > > >> _______________________________________________ > >> ALAC mailing list > >> ALAC(a)atlarge-lists.icann.org > >> https://atlarge-lists.icann.org/mailman/listinfo/alac > > >> At-Large Online: http://www.atlarge.icann.org > >> ALAC Working Wiki: >https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… > > > > _______________________________________________ > > 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

Notification of Standard Bylaw Ammendment
by Alan Greenberg May 21, 2018

May 21, 2018

The Empowered Community (EC) had received notice that the Board approved an amendment to the Bylaws (https://www.icann.org/resources/board-material/resolutions-2018-05-13-en#1.d) As a member of the EC, the ALAC may take action to object to this change. The change is to implement the new GNSO voting thresholds associated with exercising EC powers, and had previously been the subject of a Public Comment (https://community.icann.org/x/toLpB) I recommend that we take no action. Alan

12 11

Selection of ALAC Chair
by Alan Greenberg May 17, 2018

May 17, 2018

My current term as an ALAC Member expires at the end of the AGM in October of this year, as does my term as ALAC Chair. I have previously said that I would not be a candidate for Chair of the ALAC for the coming year and in fact I am not a candidate for an ALAC seat. When the issue was discussed in San Juan, there was a general consensus within the ALAC that the position should be opened sooner rather than later, but not before the selection of RALO-appointed ALAC members was complete. The nomination and acceptance period is now complete. In three of the five RALOs, the ALAC seat is not contested, but it is in LACRALO and NARALO. The election is due to begin on Friday and end on Thursday, 24 May. Presuming the two elections result in definitive selections, I will formally initiate a call for nominations for ALAC Chair soon after. According to the ALAC Rules of Procedure, the call must be open for at least 14 days. That puts the end of the nomination period on or around Friday, 08 June. There is a 7 day period allowing for acceptances, but I am optimistic that any nominations will be accepted or declined quickly. Nominations may only be made by current ALAC Members, nominees must have a reasonable expectation of being on the post-AGM ALAC, and the electorate is the current ALAC. If there is only one candidate, that person will be declared incoming Chair. If there is more than one candidate, I will request that a teleconference be scheduled to allow the candidates to present themselves and address any questions the ALAC may have for them (as well as a Wiki space for written questions and answers). That will allow the election to be conducted electronically prior to departure for Panama. If, for some reason this schedule cannot be met, then the election may be conducted in Panama. If there is an ALAC consensus, the election may be deferred until Panama regardless of timing. There are specific rules covering the situation of more than two candidates and to address ties. For those interested in all of the details, see section 17.2 of the ALAC RoP (<http://tinyurl.com/ALAC-RoP-2016-09>http://tinyurl.com/ALAC-RoP-2016-09) PLEASE NOTE that this message is NOT the call for nominations. That will not happen until after the current ALAC selection process is complete. Alan

4 3

Webinar on GDPR compliance Temporary Specification
by León Felipe Sánchez Ambía May 14, 2018

May 14, 2018

Dear all, After some very lengthy and robust discussions about the proposed temporary specification, the Board requested ICANN Org that it updated the proposed temporary specification in order to incorporate much of the feedback received by the community. Of course not all feedback was able to be included for various reasons and of course the updated proposed temporary specification is not flawless but it is a document that tries to take care of the most urgent matters in order to allow the community to develop a policy while complying with the GDPR in the mean time. This document is not being circulated looking for feedback but, of course, any feedback is always well received. ICANN Org will be holding a webinar on the updated proposed temporary specification tomorrow May 15 at 16:15 UTC. You can find the information to join and participate here <https://www.icann.org/news/announcement-2018-05-14-en>. You can also have more information on the updated documente here <https://www.icann.org/news/blog/data-protection-privacy-update-revised-prop…>. I invite you and encourage you to join this important webinar. Kind regards, León

1 0

Re: [ALAC] Suggested revision of At-Large Policy Development template
by Alan Greenberg May 13, 2018

May 13, 2018

We have again had a problem with the original comment being changed without clear notice and causing confusion. I have investigated whether Maureen suggestion is possible (have additional DRAFT boxes be added as needed) and found that this is not practical for a number of reasons (a) it would have to be done by staff since non-staff do not have the privileges to alter these macros; b) few staff have the skills; c) having specific staff do it on a tight time-frame is not practical). In light of that, I have instructed that staff modify the pages to give clear instructions for what can be done without extensive training or staff time to address the issue. Alan At 01/02/2018 11:07 PM, Alan Greenberg wrote: >This happens relatively infrequently. Why create >a new process that requires staff intervention >when simply stacking the version in the box now >called DRAFT(s) will do. And it allows for more than two version is required? > >At 01/02/2018 09:54 PM, Maureen Hilyard wrote: >>But as Holly said, sometimes you just need >>another space to reorganise your thoughts >>before it becomes the final draft... although >>sometimes it ends up as the final draft.. >> >>But you are only currently given 2 options, first and final.. >> >>There should be two boxes to start off with, >>and the penholder can ask for another one if >>required as a transition section before the >>final statement . But it should be highlighted >>in another colour what changes have been made. >> >>On Thu, Feb 1, 2018 at 12:23 PM, Alan Greenberg >><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >>When I was drafting more statements, I also >>would often post my "first draft" in the >>comment area and move it up if it had general >>acceptance. But there will always be cases >>where there are multiple draft versions posted >>and I was trying to find a really easy path for >>doing that without losing history along the >>way. Having staff create new boxes along the >>ways seems likea much more challenging way to address the problem... >>Alan >>At 01/02/2018 04:33 PM, Maureen Hilyard wrote: >>>I think there is room for having personal >>>comments remaining at the bottom of the wiki >>>page, but drafts of the statement should be >>>able to be inserted as they develop. It might >>>mean teaching penholders how to create these >>>boxes for new drafts or asking the new policy >>>support staff person to create one for them. >>> >>> >>>On Thu, Feb 1, 2018 at 11:28 AM, Holly Raiche >>><<mailto:h.raiche@internode.on.net> h.raiche(a)internode.on.net> wrote: >>>Makes sense to me. When I died to post a >>>Ã¢firirst draftÃ¢ of f the privacy stuff, >>>I couldnÃ¢t, and so put stuff in tn the >>>Ã¢commentÃ¢ ¬â¢ space. While that whole >>>wiki reflects pretty much what the discussion >>>was, it doesnÃ¢t follow the concept of firfirst and final draft >>>Holly >>>On 2 Feb 2018, at 6:40 am, Maureen Hilyard >>><<mailto:maureen.hilyard@gmail.com> maureen.hilyard(a)gmail.com> wrote: >>> >>>>Sounds good to me because when you don't see >>>>the developments as new contributions are >>>>incorporated into the statements, it may seem >>>>as if its only just been ONE or only a few contributors >>>>Some statements go through several transitions. >>>>M >>>>On Thu, Feb 1, 2018 at 8:42 AM, Alan >>>>Greenberg <<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca > wrote: >>>>It has been pointed out to me that the >>>>template we use has a space for "First Draft" >>>>and then "Final Draft". This works for issues >>>>that do not generate a lot of dialogue and >>>>revision of the statement. For such >>>>statements, there is no specific place to >>>>post the revised version(s). Simply changing >>>>the first draft does not really work, because >>>>then we are left with Wiki comments on that >>>>draft that refer back to something that s no >>>>longer there (unless you go to the trouble of >>>>finding the correct earlier version). >>>>I suggest that we change the title from >>>>"FIRST DRAFT SUBMITTED" to "DRAFT STATEMENTS" >>>>and add instructions saying that if multiple >>>>draft versions are posted, old versions >>>>should remain, with the newer version posted >>>>at the top of the box, prefixed with the date >>>>posted and author, and separated from earlier versions by a horizontal line. >>>>That way we have a full history of the draft evolution. >>>>Does anyone see a reason not to do this? >>>>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… >>>> >>>_______________________________________________ >>>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… >>>

4 4