Hi Marilyn, CROP allows for one out of trip region—I believe this is my error and that I misspoke when we were drafting and that I had said there were two trips allowed out of region. My apologies for that! In regards to ICANN support of BC Outreach, there are no other areas to add at this time, unless it is worth mentioning the ICANN staff that take time to speak at BC outreach events. Kind regards, Chantelle From: Marilyn Cade <marilynscade@hotmail.com> Date: Monday, August 21, 2017 at 18:27 To: Chantelle Doerksen <chantelle.doerksen@icann.org>, "bc-outreach@icann.org" <bc-outreach@icann.org> Subject: [Ext] Re: [Bc-outreach] Updated version of the BC FY18 Outreach Strategy for 2018 Exactly, Chantelle. We need to acknowledge the additional support that ICANN provides. I thought I made that clear in my draft and in the cover email. I think that all of us on the Outreach Committee are very familiar with [as we have to review it before submitted] the submissions to the ICANN Budget process. So I did assume that colleagues will recognize that additional support that we receive. Apologies if it was unclear. Chantelle, I am a little confused ,though, about one thing. I thought that we could have up to two out of region trips. Can you verify that for us?That is important of us, as our priorities are the developing country regions and sub regions. ________________________________ From: bc-outreach-bounces@icann.org <bc-outreach-bounces@icann.org> on behalf of Chantelle Doerksen <chantelle.doerksen@icann.org> Sent: Monday, August 21, 2017 7:42 PM To: bc-outreach@icann.org Subject: Re: [Bc-outreach] Updated version of the BC FY18 Outreach Strategy for 2018 Hi Marilyn and Lawrence, Thanks so much for the comments. To Marilyn’s point about ICANN’s support regarding Outreach funding, I hope to have more information on that within the next day or so. Off the top of my head, I believe this would include: ICANN’s printing of the BC Newsletter (and other documents); special budget requests to support travel; and collaboration with the Global Stakeholder Engagement team (Chris Mondini, etc.). I’ll confirm if there is anything else, hopefully by COB tomorrow. To Lawrence’s point regarding CROP: requests for travel slots are due six (6) weeks before an event, at minimum. Therefore, they do not need to be determined for the entire year at this time. AfICTA’s event was set for fall 2017, hence the need to have the travel slots approved by late August to allow for the six (6) weeks advance notice, as required by CROP. The FY18 Operating Procedures and Requirements for CROP can be reviewed at, https://community.icann.org/x/7wXfAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_7wXfAw&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=wL3Zo2cS0E1587i1K6plo1c3_QE_VYKpzxK_zxU6nHchrvvSIST7VWCi3I7o_dqG&m=g0U4fxMJHLnikiGt-5EuNEM_6Hvto-MEu4Ht6OJIFHM&s=3RUNF5_w8kj-sndHQ0O997EXmh-y5XsYymQFR8IebmU&e=>. For quick reference, CROP provides the following support for FY18: Standard Travel Authorizations Trip Allocations (4 days, 3 nights maximum): Five (5) individual regional trips are allocated to At-Large RALOs including: AFRALO, APRALO, EURALO, LACRALO, and NARALO Five (5) individual regional trips which may include one (1) out of region trip if necessary, allocated to GNSO Constituencies including: Business, Intellectual Property, Internet Services Provider, Non-Commercial Users, and Not-for-Profit Operational Concerns. Funded Costs/Expenses: Includes transportation (economy class), lodging, and per diem (4 days, 3 nights maximum) Visa Fees & Registration Fees: Travellers will be reimbursed for visa fees (up to $200 USD) and for conference registration fees where applicable (up to $800 USD) Booking: All travel booked via ICANN Constituency Travel to ensure consistency, proper accounting, recordation, and tracking against budget. I hope this is helpful. Let me know if there are any further questions. Kind regards, Chantelle On 8/20/17, 15:23, "bc-outreach-bounces@icann.org on behalf of Lawrence OlaWale-Roberts" <bc-outreach-bounces@icann.org on behalf of icann@microboss.org> wrote: Dear Outreach Committee, I must commend the edits done by Marylyn and Chantelle on this version of our outreach strategy. its a great plan drafted here.Where we are able to implement this to the latter, it would greatly enhance our outreach as BC and lead to new businesses on boarding. Chantelle might need to help check if at this point we would not need to have the CROP Travel slots allocated and indicated in the plan. I recall that for the 2017 outreach plan we had to review the plan midway in order to accommodate the travel slots for the AFICTA summit before the travel request was approved by the CROP Administrators. otherwise this looks good. Lawrence. On Sat, August 19, 2017 8:59 am, Marilyn Cade wrote: > > Dear Outreach Committee colleagues > > > With special thanks to Chantelle who helped greatly in an effort > yesterday to incorporate those comments received, both in writing, and > via informal comments from Outreach Committee members, I present Version 3 > of the Outreach Strategy for 2018. > > It has some new work items and proposed efforts: Let me identify a few: > > > First, we continue and enhance our work with the Engagement team — it is > already pretty strong, as we saw with the great sponsorship and help and > participation during the ICANN59 pre Outreach Event that was organized for > a half day event. And, the Strategy proposes continuing and even > strengthening our engagement. Details are not described there so that we > as the Outreach Committee take some time to plan out a program for 2018 > that we are all engaged in before approaching the Engagement Team. > > Second, we prioritize using CROP across at least 3 regions, and that we > allocate up to 2, to be determined by proposals, out of region CROP > supported travelers, if that is useful to support either in region events, > or to support something where a BC member is a particular expert, invited > to an out of region event, where they can make a difference in the BC > recruitment event. CROP has improved considerably, including even allowing > payment of registration fees for an event. Personally, I usually require > that such fees be waived when I speak, but it may be needed for instance, > for WITSA’s WCIT, or some other such highly visible business conference. > > The Outreach Strategy incorporates CROP into our larger program, which > includes our Leadership Program. It occurs to me as I look at this > again, that we should perhaps identify more clearly the continuance of > the Leadership Program as one of our core and ongoing Outreach > Activities. Perhaps we even need to have an appendix about the funding > that we receive from ICANN and what it is for, for Outreach and then we > can just reference the appendix. > > The Strategy proposes to ask BC members to become “site/ICANN event” > coaches, where they might agree to have a newcomer to join them at a > session that they are attending, and play the role of coach/mentor in > that session, introducing the newcomer, and explaining any new terms, > etc. that would be approached on an ad hoc basis, and just be for a > subject specific session, e.g. a GAG meeting, a working session on WHOIS, > etc. > > It also asks more BC members to volunteer in the ICANN booth, and > identifies possibly 2-3 topics that an expert speaker from ICANN might > speak at, informally, in the booth. Topics suggested were SSR, fraud and > abuse in the DNS — chosen based on the interests of NextGen and new > Fellows. Speakers should commit to speaking only about the approved > policy positions/views of the BC. > > It proposes to improve our use of our Facebook page, and tweeting about > the BC from all members. > > It also proposes the development of an occasional “blog” for the BC, > which will require some careful thought about editorial guidelines, and > would be posted on the BC website, so, like the BC Newsletter, should be > focused on issues of relevance to the full BC. > > It also establishes a firmer deadline for CROP proposals to the Outreach > Committee, with an exception clause but as only a rare exception, as CROP > requires 6 weeks for approval/processing. > > Thanks to Lawrence, Gabi, and Andy for your comments. Please take another > look at the document, as the goal is to distribute it to the BC ExComm on > August 22. > > > Chantelle, can you look at the other areas that we receive funding from > ICANN for outreach, and perhaps we can add an appendix that shows those? > We could put a footnote on page one, in the paragraph about us of other > special funds — just insert a footnote there, and then have an appendix > with the funding that ICANN gives us, which is the Leadership Program; > the printing of the Newsletters/Fact Sheets, and other special funding. > > We have benefitted from in kind contributions from ICANN, such as expert > speakers, distribution of materials like the BCG document for the ICANN59 > Outreach events, etc, and we should be sensitive that ICANN staff do read > this, so we might also want to mention the importance of the in-kind > support and attendance of senior ICANN speakers and staff in our outreach > events? > > Marilyn > > > _______________________________________________ > Bc-outreach mailing list > Bc-outreach@icann.org > https://mm.icann.org/mailman/listinfo/bc-outreach > > _______________________________________________ Bc-outreach mailing list Bc-outreach@icann.org https://mm.icann.org/mailman/listinfo/bc-outreach _______________________________________________ Bc-outreach mailing list Bc-outreach@icann.org https://mm.icann.org/mailman/listinfo/bc-outreach