<html>
<body>
Parts extracted to keep things concise and my further comments.<br><br>
At 06/09/2017 10:36 PM, Seun Ojedeji wrote:<br>
<blockquote type=cite class=cite cite="">On Sep 6, 2017 6:56 PM,
"Alan Greenberg"
<<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>
> wrote:<br>
<dl><br>
<dd>We do not want to endanger ICANN, but we also do not want to squander
the money. If we ONLY do things that are strictly within ICANN's scope in
how it uses its operational funds, then we may as well just roll the
money into the ICANN operational budget. We need to be
innovative.<br><br>
</dl><br>
SO: Hmm...we should not be very strict but at the same time we have to be
mindful of being within ICANN mission. The funds for instance should not
be used to digitize content of a museum library. I also don't think the
idea of staying within ICANN mission implies we should put the funds into
ICANN operational budget. There are many many activities/projects within
ICANN mission that their budget doesn't cover and rolling back a one time
amount into operational budget isn't a good idea for not-for-profit.<br>
</blockquote><br>
<font color="#0000FF">AG: My suggestion to put the funds into ICANN's
operational budget was not serious, but I was trying to highlight that
*IF* we were going to constrain too tightly, the net effect would be the
same and a lot lest costly interms of this CCAG working for another year
or so and then setting up or contracting for some operational entity to
do the work. <br><br>
Even I would find it hard (or impossible) to justifying digitizing a
library. Unless of course, it was the library associated with early
IAN or related documentation. That is why we WILL have constraints
and the applicants will have to make a strong connection to
them.<br><br>
<br>
</font><blockquote type=cite class=cite cite="">
<dl>
<dd>My classic example is Internet Exchange Points. They are not what I
would consider something that is strictly within ICANN's mission. But
they are very important to parts of our community including ISPs and the
RIRs (the second N in ICANN). And they even (typically) require
Autonomous System Numbers, one of the unique identifiers that we are here
for. And they create great benefit for the "greater Internet
community", and perhaps even more important, they help strenghten
the relatively weak infrastructure in places not necessarily well
served by the Internet.<br><br>
</dl><br>
SO: IMO am not sure why you think IX probably falls outside of ICANN
mission. Espcially if it comes to capacity building and providing
relevant resources to get them more operational to ensure open Internet
because some IX does host registry copies. Section IV of ICANN mission
seem to allow that. That said, I don't think having ICANN build an IX
from scratch for instance should be within scope.</blockquote><br>
<font color="#0000FF">AG: I wasn't saying *I* think that. But I have had
the reaction from some that ANYTHING that smells of infrastructure is
definitely off-limits. If everyone now playing in the sandbox thinks it
is fine, I am delighted. I am not sure that providing the rather minimal
capital cost of the equipment, when it is part of an overall program is
off-limits, but it is certainly something that could be decided.<br><br>
<br>
</font><blockquote type=cite class=cite cite="">
<dl>
<dd>More specifically, I want the CCWG to leave the door as wide open as
possible while meeting the Board's concerns, to allow project requesters
to be innovative in creating viable links from their projects to the
constraints that we must meet.<br><br>
</dl><br>
SO: Okay so it seem we do not necessarily have a significantly different
view on this after all.</blockquote><br>
<font color="#0000FF">AG: I don't think so. My concern is that there are
some people in the group that REALLY want to constrain things, and while
we may not go as liberal as I would prefer, I really want to make sure we
do not end up in a position where we cannot make really good use of the
funds.<br><br>
Alan<br><br>
<br>
</font><blockquote type=cite class=cite cite="">
<dl>
<dd>I hope this helps.<br><br>
</dl><br>
SO: Yes it does.<br><br>
Regards<br>
<dl><br>
<dd>Alan<br><br>
<br><br>
<br>
<dd>At 06/09/2017 03:29 AM, Seun Ojedeji wrote:<br><br>
<blockquote type=cite class=cite cite="">
<dd>Hello,<br><br>
<dd>There has been ongoing discussion in reaction to the attached letter
from the Board. The discussion has been around using the auction funds
for purpose beyond the ICANN mission. I was of the opinion that her
mission though has a scope was broad enough to ensure the funds have a
global reach as much as possible.<br>
<dd>However I have also noticed some members (notably Alan) have the view
that the funds should be used beyond the ICANN mission scope. While it's
not important that we share same opinion I also don't want to take
lightly veterans view on this matter, perhaps am missing something
:-)<br>
<br>
<dd>Specifically, is there a disadvantage for At-Large if the auction
funds is used within ICANN mission that makes it so important for us to
support acting outside of the ICANN mission?<br><br>
<dd>The specific thread can be followed here:<br>
<dd>
<a href="http://mm.icann.org/pipermail/ccwg-auctionproceeds/2017-September/000470.html">
http://mm.icann.org/pipermail/ccwg-auctionproceeds/2017-September/000470.html</a>
<br><br>
<dd>I like to read comments from folks here to better inform my
participation.<br><br>
<dd>Regards<br>
<dd>Sent from my mobile<br>
<dd>Kindly excuse brevity and typos<br>
<dd>---------- Forwarded message ----------<br>
<dd>From: "Erika Mann"
<<a href="mailto:erika@erikamann.com">erika@erikamann.com</a>><br>
<dd>Date: Sep 4, 2017 3:29 PM<br>
<dd>Subject: [Ccwg-auctionproceeds] Fwd: Board reply to CCWG-AP<br>
<dd>To: <<a href="mailto:ccwg-auctionproceeds@icann.org">
ccwg-auctionproceeds@icann.org</a>><br>
<dd>Cc: <br><br>
<dl>
<dd>Dear All - <br>
<dd>herewith I'm forwarding Steve's reply to our letter. <br>
<dd>We will have a first exchange on Thursday this week, during our CCWG
AP call. I send Steve already a quick reply, saying that we will discuss
the Board letter then for the first time. <br>
<dd>Best,
<dd>Erika<br>
<br>
<dd>---------- Forwarded message ----------
<dd>From: Steve Crocker
<<a href="mailto:steve.crocker@board.icann.org">
steve.crocker@board.icann.org</a>>
<dd>Date: Sun, Sep 3, 2017 at 3:19 PM
<dd>Subject: Board reply to CCWG-AP
<dd>To: Erika Mann
<<a href="mailto:erika@erikamann.com">erika@erikamann.com</a>>,
Ching Chiao
<<a href="mailto:chiao@brandma.co">chiao@brandma.co</a>>, Marika
Konings
<<a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>
>
<dd>Cc: Steve Crocker <<a href="mailto:steve.crocker@board.icann.org">
steve.crocker@board.icann.org</a>>, Marika Konings
<<a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>
>, Icann-board ICANN
<<a href="mailto:icann-board@icann.org">icann-board@icann.org</a>>,
Avri Doria <<a href="mailto:avri@apc.org">avri@apc.org</a>>,
"Sarah B. Deutsch"
<<a href="mailto:sarahbdeutsch@gmail.com">sarahbdeutsch@gmail.com</a>
>, Board Operations
<<a href="mailto:Board-Ops-Team@icann.org">Board-Ops-Team@icann.org</a>
>, Sally Costerton <<a href="mailto:sally.costerton@icann.org">
sally.costerton@icann.org</a>>, Samantha Eisner
<<a href="mailto:Samantha.Eisner@icann.org">
Samantha.Eisner@icann.org</a>>, Lauren Allison
<<a href="mailto:lauren.allison@icann.org">lauren.allison@icann.org</a>
><br>
<br>
<dd>Dear Erika and Ching,
<dd>
<dd>Thank you for your letter received on May 22, 2017 on behalf of the
Cross Community Working Group on New gTLD Auction Proceeds (CCWG-AP) in
response to the Board email of March 2nd 2017.
<dd>
<dd>On behalf of the Board, I am delighted to see that we are aligned in
our thinking regarding the points discussed in the original email.
Specifically, in response to your letter, please find attached a letter
including additional acknowledgements and requested clarifications.
<dd>
<dd>Thank you again for your efforts leading this work.
<dd><font color="#888888">
<dd>Steve
<dd> </font><br>
<br>
<br>
<br>
<dd>_______________________________________________
<dd>Ccwg-auctionproceeds mailing list
<dd><a href="mailto:Ccwg-auctionproceeds@icann.org">
Ccwg-auctionproceeds@icann.org</a>
<dd>
<a href="https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds" eudora="autourl">
https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds</a><br><br>
</dl><br>
<dd>Content-Type: text/plain; charset="us-ascii"<br>
<dd>Content-Transfer-Encoding: 7bit<br>
<dd>Content-Disposition: inline<br>
<dd>X-Microsoft-Exchange-Diagnostics:<br>
<dd>
1;DM5PR03MB2714;27:kAfTkegi2gCP9wBV7y1t2Pta3rBAyLtX29O/VKLY/8KH0/vdhnduKFRutXIrhL4AKhSA2l4FX5kvlUOCsuRWx8T5WWy7kRQENXkS34+CJnaUyZfMIpCArNreF3W32RNR<br>
<dd>X-Microsoft-Antispam-Mailbox-Delivery:<br>
<dd>
ex:0;auth:0;dest:I;ENG:(400001000128)(400125000095)(20160514016)(750103)(520002050)(400001001223)(400125100095)(61617095)(400001002128)(400125200095);<br>
<br>
<br>
<dd>_______________________________________________<br>
<dd>ALAC mailing list<br>
<dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a><br>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
<dd>At-Large Online:
<a href="http://www.atlarge.icann.org/">http://www.atlarge.icann.org</a>
<br>
<dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
)</blockquote><br>
</dl></blockquote></body>
</html>