<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23942">
<STYLE></STYLE>
</HEAD>
<BODY
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space"
bgColor=#ffffff>
<DIV>
<DIV><FONT size=2 face=宋体>Hi,</FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV><FONT size=2 face=宋体>I tried to use WebEx in China. However, I was
not able to load the program because I am still using Windows XP. Although
XP is not being supported by Microsoft anymore, but it is being supported by a
domestic vendor and is still widely being used. Thus, using WebEx may
block many participating from China.</FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV><FONT size=2 face=宋体>Kaili</FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV> </DIV></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 9pt 宋体">----- Original Message ----- </DIV>
<DIV style="FONT: 9pt 宋体; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=h.raiche@internode.on.net
href="mailto:h.raiche@internode.on.net">Holly Raiche</A> </DIV>
<DIV style="FONT: 9pt 宋体"><B>To:</B> <A title=judith@jhellerstein.com
href="mailto:judith@jhellerstein.com">Judith Hellerstein</A> </DIV>
<DIV style="FONT: 9pt 宋体"><B>Cc:</B> <A title=alac@atlarge-lists.icann.org
href="mailto:alac@atlarge-lists.icann.org">alac@atlarge-lists.icann.org</A> ;
<A title=ttf@atlarge-lists.icann.org
href="mailto:ttf@atlarge-lists.icann.org">ttf@atlarge-lists.icann.org</A> ; <A
title=na-discuss@atlarge-lists.icann.org
href="mailto:na-discuss@atlarge-lists.icann.org">na-discuss@atlarge-lists.icann.org</A>
</DIV>
<DIV style="FONT: 9pt 宋体"><B>Sent:</B> Saturday, April 21, 2018 6:47 PM</DIV>
<DIV style="FONT: 9pt 宋体"><B>Subject:</B> Re: [ALAC] Fwd:
[Ccwg-auctionproceeds] ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash
Rangan</DIV>
<DIV><BR></DIV>I, for one, would be happy to go back to Adobe - I have had
real difficulties with webex - I just couldn’t access it. And I miss
having the visibility of the text, the sound of the speaker and the
availability of chat (both public and private
<DIV><BR></DIV>
<DIV>Holly<BR>
<DIV>
<DIV>On 21 Apr 2018, at 4:20 am, Judith Hellerstein <<A
href="mailto:judith@jhellerstein.com">judith@jhellerstein.com</A>>
wrote:</DIV><BR class=Apple-interchange-newline>
<BLOCKQUOTE type="cite">
<DIV
style="TEXT-TRANSFORM: none; TEXT-INDENT: 0px; FONT: 12px Verdana; WHITE-SPACE: normal; LETTER-SPACING: normal; WORD-SPACING: 0px; -webkit-text-stroke-width: 0px"
dir=auto>
<DIV>Hi All,</DIV>
<DIV><BR></DIV>
<DIV>Very interesting blog by Ash Rangan. Forwarding this email widely
so others could read it and discuss it.</DIV>
<DIV><BR></DIV>
<DIV>Best,</DIV>
<DIV>Judith</DIV>
<DIV><BR>Sent from my iPad<SPAN style="FONT-SIZE: 13pt"> </SPAN>
<DIV><SPAN style="FONT-SIZE: 13pt"><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="mailto:judith@jhellerstein.com">judith@jhellerstein.com</A> </SPAN></DIV>
<DIV><SPAN style="FONT-SIZE: 13pt">Skype
ID:JudithHellerstein</SPAN></DIV></DIV>
<DIV><BR>Begin forwarded message:<BR><BR></DIV>
<BLOCKQUOTE type="cite"><B>From:</B><SPAN
class=Apple-converted-space> </SPAN>Nathalie Peregrine <<A
style="COLOR: purple; TEXT-DECORATION: underline"
href="mailto:nathalie.peregrine@icann.org">nathalie.peregrine@icann.org</A>><BR><B>Date:</B><SPAN
class=Apple-converted-space> </SPAN>April 20, 2018 at 2:16:27 PM
EDT<BR><B>To:</B><SPAN class=Apple-converted-space> </SPAN>"<A
style="COLOR: purple; TEXT-DECORATION: underline"
href="mailto:ccwg-auctionproceeds@icann.org">ccwg-auctionproceeds@icann.org</A>"
<<A style="COLOR: purple; TEXT-DECORATION: underline"
href="mailto:ccwg-auctionproceeds@icann.org">ccwg-auctionproceeds@icann.org</A>><BR><B>Subject:</B><SPAN
class=Apple-converted-space> </SPAN><B>[Ccwg-auctionproceeds] ADOBE
CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan</B><BR><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<DIV style="page: WordSection1" class=WordSection1>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><A
name=_MailOriginalBody>Dear all:<O:P></O:P></A></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>Please
take a look at this blog on Adobe Connect. And note the
request:<O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><B>Before
we make these changes, we want to hear from you. What do you think? Please
submit your thoughts on this contemplated move before May 2nd here:<SPAN
class=Apple-converted-space> </SPAN></B></SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="mailto:RP-tool@icann.org"><SPAN><B>RP-tool@icann.org</B></SPAN><SPAN></SPAN></A><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><B></B><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>Best
regards,
David<O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN></SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blog_adobe-2Dconnect-2Dwhat-2Dnext&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=UHqgHAAbiJp4NHOIUqHcg1Y57R0_ZBkAKlNnZW-FMt4&s=lFkfL9p571e1ygGDpMHtzFBnK57qJfDmiC0yWwyGwII&e="><SPAN>https://www.icann.org/news/blog/adobe-connect-what-next[icann.org]</SPAN><SPAN></SPAN></A><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><B>ADOBE
CONNECT – WHAT NEXT?</B><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>As
you know, the ICANN organization took down its Adobe Connect service
midway through the ICANN61 meeting in response to<SPAN
class=Apple-converted-space> </SPAN></SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blog_issues-2Dwith-2Dadobe-2Dconnect-2Dat-2Dicann61&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=UHqgHAAbiJp4NHOIUqHcg1Y57R0_ZBkAKlNnZW-FMt4&s=iO8NyGh9T2oO7mc2eo1jcmmpFO-uSsIlTLqKsypb0qM&e="><SPAN>reported
issues[icann.org]</SPAN><SPAN></SPAN></A><SPAN><SPAN
class=Apple-converted-space> </SPAN>with this service. Concurrently,
we began to conduct our own forensic analysis of the reported incident and
began working with our Adobe cloud service provider, CoSo Cloud LLC, and
through them with Adobe to learn more. Shortly thereafter, we rolled out
instances of Zoom and WebEx for the community to support remote
participation (RP) and collaboration. Here's where we are
now:<O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><B></B><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><B>The
Forensics Investigation</B><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>With
respect to our forensics work, we received application logfiles from CoSo
Cloud, going back for a period of one year. ICANN Engineering and Security
teams have examined these application log files and the results of our
investigation clearly show "fingerprints of incursion" by the researcher
who reported the issue. We were unable to find any other indication that
anyone else either identified or exploited this issue. Thanks to the
person who found the bug again.<O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>Working
closely with CoSo Cloud, we were able to recreate the reported issue, and
understand the conditions required to trigger it. This information has
been communicated to Adobe, and Adobe is working on a software fix to
address the root cause of the issue.<O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>We
have also been working with CoSo on options to re-enable Adobe Connect in
the shorter term. We have determined there are two viable paths to
accomplish this goal. They are:<O:P></O:P></SPAN></DIV>
<OL style="MARGIN-TOP: 0in; MARGIN-BOTTOM: 0in" type=1>
<LI
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"
class=MsoNormal><SPAN>Deploy a hardened configuration to eliminate
"man-in-the-middle" exploitations by encrypting relevant traffic,
or<O:P></O:P></SPAN>
<LI
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"
class=MsoNormal><SPAN>Implement a programmatic fix from CoSo Cloud to
substantially reduce the window during which the issue can be
exploited.<O:P></O:P></SPAN></LI></OL>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>With
respect to the first option, we attempted to hack the hardened
configuration in a test environment last week, and were not able to do so
over the course of 7 hours. Separately, CoSo Cloud and Adobe conducted
similar tests and confirmed that this configuration is protected from
exploitation of the issue.<O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><B></B><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><B>Community
Feedback and Next Steps</B><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>For
the last three weeks, we have been gathering limited feedback regarding
users' experiences with WebEx and Zoom. So far, we have input from about
200 people, including ICANN org meeting organizers and the ICANN
community. Our analysis of this feedback indicates a desire to revert back
to an Adobe Connect, providing the security of the service is
ensured.<O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>Accordingly,
we would like to propose the following plan to the broader community for
consideration:<O:P></O:P></SPAN></DIV>
<OL style="MARGIN-TOP: 0in; MARGIN-BOTTOM: 0in" type=1>
<LI
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"
class=MsoNormal><SPAN>We would like to restore Adobe Connect services
with both the new hardened configuration and the programmatic fix
discussed above. Our intent would be to restore service by 3 May. This
would allow us to use Adobe Connect during several upcoming events
including the Board Workshop, the GDD Industry Summit, and
ICANN62.<O:P></O:P></SPAN>
<LI
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"
class=MsoNormal><SPAN>Once Adobe releases a new version of the software
with a fix for this issue from their perspective, and provides assurance
the update has been adequately tested, we will move toward that release
of Adobe Connect in a prudent manner, with the help of CoSo
Cloud.<O:P></O:P></SPAN></LI></OL>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>We
believe that this approach will ensure the security of our content, and of
our community interactions, while also enabling our community to use the
collaboration tools of their choice.<O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>Before
we make these changes, we want to hear from you. What do you think? Please
submit your thoughts on this contemplated move before May 2nd here:<SPAN
class=Apple-converted-space> </SPAN></SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="mailto:RP-tool@icann.org"><SPAN>RP-tool@icann.org</SPAN><SPAN></SPAN></A><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>Meanwhile,
we will continue to offer WebEx and Zoom for RP and collaboration
purposes. We will also continue to follow industry developments, including
the research ALAC is doing on the RP and collaboration space, to ensure we
are using secure and cost-effective tools that are appropriate for our
needs.<O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN>I
look forward to your comments!<O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV>
<DIV>
<DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><SPAN
style="FONT-SIZE: 12pt"></SPAN><O:P></O:P></SPAN></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><SPAN
style="FONT-SIZE: 9pt">David A. Olive<BR>Senior Vice
President</SPAN><O:P></O:P></SPAN></DIV>
<P
style="MARGIN: 0in 0in 12pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"
class=MsoNormal><SPAN><SPAN style="FONT-SIZE: 9pt">Policy Development
Support</SPAN></SPAN><SPAN><SPAN
style="FONT-FAMILY: PMingLiU, serif; FONT-SIZE: 9pt"><BR></SPAN></SPAN><SPAN><SPAN
style="FONT-SIZE: 9pt">Internet Corporation for Assigned Names and Numbers
(ICANN)</SPAN><O:P></O:P></SPAN></P></DIV>
<DIV
style="MARGIN: 0in 0in 0pt; FONT-FAMILY: Calibri, sans-serif; FONT-SIZE: 11pt"><SPAN><O:P></O:P></SPAN></DIV></DIV></DIV></BLOCKQUOTE>
<BLOCKQUOTE
type="cite"><SPAN>_______________________________________________</SPAN><BR><SPAN>SOAC-Leaders-ICANNMeeting-Planning
mailing list</SPAN><BR><SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="mailto:SOAC-Leaders-ICANNMeeting-Planning@icann.org">SOAC-Leaders-ICANNMeeting-Planning@icann.org</A></SPAN><BR><SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning">https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning</A></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE
type="cite"><SPAN>_______________________________________________</SPAN><BR><SPAN>Gnso-igo-ingo-crp
mailing list</SPAN><BR><SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="mailto:Gnso-igo-ingo-crp@icann.org">Gnso-igo-ingo-crp@icann.org</A></SPAN><BR><SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp">https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp</A></SPAN></BLOCKQUOTE>
<BLOCKQUOTE
type="cite"><SPAN>_______________________________________________</SPAN><BR><SPAN>gnso-rpm-wg
mailing list</SPAN><BR><SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</A></SPAN><BR><SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</A></SPAN></BLOCKQUOTE>
<BLOCKQUOTE
type="cite"><SPAN>_______________________________________________</SPAN><BR><SPAN>Ccwg-auctionproceeds
mailing list</SPAN><BR><SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="mailto:Ccwg-auctionproceeds@icann.org">Ccwg-auctionproceeds@icann.org</A></SPAN><BR><SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds">https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds</A></SPAN></BLOCKQUOTE>_______________________________________________<BR>ALAC
mailing list<BR><A style="COLOR: purple; TEXT-DECORATION: underline"
href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</A><BR><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</A><BR><BR>At-Large
Online:<SPAN class=Apple-converted-space> </SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="http://www.atlarge.icann.org/">http://www.atlarge.icann.org</A><BR>ALAC
Working Wiki:<SPAN class=Apple-converted-space> </SPAN><A
style="COLOR: purple; TEXT-DECORATION: underline"
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</A></DIV></BLOCKQUOTE></DIV><BR></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>ALAC mailing
list<BR>ALAC@atlarge-lists.icann.org<BR>https://atlarge-lists.icann.org/mailman/listinfo/alac<BR><BR>At-Large
Online: http://www.atlarge.icann.org<BR>ALAC Working Wiki:
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</BLOCKQUOTE></BODY></HTML>