<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:773089592;
mso-list-template-ids:-751022044;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hello all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The notes, recordings and transcripts for the CCWG ACCT meeting #34 - 26 May will be available here:
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="https://community.icann.org/pages/viewpage.action?pageId=53775690">https://community.icann.org/pages/viewpage.action?pageId=53775690</a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">A copy of the notes and acti<span style="color:#1F497D">o</span>n items may be found below.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">Kim<o:p></o:p></p>
<div style="border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt">ACTION Items<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:7.5pt;line-height:14.3pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">ACTION ITEM - CoChairs to reach out to Comms Team to analyse feasibility</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333">. <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:7.5pt;line-height:14.3pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">ACTION ITEM: CCWG to go through memorandums put together by counsel on UAs</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"> - </span><a href="https://community.icann.org/download/attachments/52890082/REVISED%20Memo%20on%20Unincorporated%20Associations%20May%203%2C%202015-207411876-v4.pdf?version=1&modificationDate=1430694085000&api=v2"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#3B73AF;text-decoration:none">https://community.icann.org/download/attachments/52890082/REVISED%20Memo%20on%20Unincorporated%20Associations%20May%203%2C%202015-207411876-v4.pdf?version=1&modificationDate=1430694085000&api=v2 </span></a><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:7.5pt;line-height:14.3pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">ACTION ITEM - Provide clear comparative documentation on models</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:7.5pt;line-height:14.3pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">ACTION ITEM - Cochairs to follow up on F2F/intensive session on list. </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:7.5pt;line-height:14.3pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">ACTION ITEM - staff to investigate whether lawyers have access to mailing list. </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:7.5pt;line-height:14.3pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">ACTION ITEM – Thomas to check whether GAC wants a briefing session</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:7.5pt;line-height:14.3pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">ACTION ITEM - Cochairs to provide lawyers on clear Buenos Aires expectations</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">Notes<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><b>1. Welcome, Roll Call & SoI </b><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">CCWG is encouraged to provide outstanding SoIs - staff can assist as needed.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><b>2. Feedback received on CCWG proposal</b><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">It would be useful to receive a short update on discussions in our respective communities. As a reminder we have currently received 4 comments. The CWG-stewardship is managing 50 comments. It would be valuable to share what comments are currently being drafted. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Mathieu was invited to a ccNSO Council call where the CWG and CCWG proposals were discussed. We should expect that the Council will ask us to highlight which of our proposals affect ccTLDs and in which manner. There might be an official
correspondence. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- BC will be sending in comments: enforcing powers may require that SO/ACs adopt member status under California law and will encourage the CCWG to provide further explanation on this model. Suggestion to start answering these
questions. It was found that slides prepared by Xplane were a very helpful way to digest report content. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Community is seeking clarification about members and UA structure<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- RySG will be submitting comments that are largely supportive. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- IPC is drafting comments that are largely supportive. Jonathan will coordinate with Becky on comments.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Stress Tests Work Party will determine how assessments will change if lack enforceability. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- As we make decision about type of UAs and variation, stress tests should also look at accountability issues in particular <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">--> Specific solutions for specific stress tests. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><b>3 Next Steps on Discussions regarding UAs and other membership models </b><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">There have been very thorough and fruitful discussions regarding membership model and UAs. Many concerns and questions remain to be answered: accountability of members etc being one.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Should we adopt membership model or appoint Chairs to be Members of ICANN?<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">UAs provide legal vehicle for community to hold ICANN accountable. We need legal vehicle to achieve goals. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">UAs is not the only legal vehicle that can provide us with their empowerment. There have been discussions about how corporation in Switzerland could achieve this for instance. UAs has been the easiest model. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">SO/AC Chairs can be appointed as member but this triggers new questions.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Hybrid model could be adopted and would function: SO/ACs could choose to form UAs while others may choose to appoint their Chair. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Bylaws would recognize each member or the figure of the Chair. Bylaws would be recognizing the position of the Chair. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Chair would act on behalf of SO/AC. UAs would be governed by rules stated by each SO/AC.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">To avoid: 1) Chair used as synonym of individual; 2) Equate legal personhood of individual to the one grand to Chair <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Key questions: 1) whether it is possible for Bylaws to recognize only function or figure instead of natural person, whether Bylaws would provide powers to position rather than person; 2) whether the risks could increase through membership model. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><u>Feedback</u>: <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- If you have not uniformed arrangement between SO/ACs - when come to voting, there will be different criteria, this won't be normal. We address one accountability question but transfer another accountability question. Clarity is needed on overall picture. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">--> This needs to further discussed but we need to come to a conclusion on how to address this issue. Answer could be that each SO/AC would apply methods. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- We need to be careful that it not necessarily be Chair of SO/AC but rather the Chair SO/AC designates. We may want to distribute the position (one per region etc). We do not want to make it sound like SO/AC Chair. There may well be situations where
we want to put someone in position but this person cannot. We might want to consider replacements. ALAC has certain rules when it comes to accountability criteria. We have processes that can be written in Bylaws, Charters etc to ensure criteria are being met. Can we tie responsability to a rank? <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- It can be another person that could be designated. We must avoid complicating this. Most SO/ACs have formal processes. In favor with proceeding with this route. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- UAs is really consistent with trying to make SO/ACs into members. Looking at Chairs concept, agree that acting as a conduit for the will of SO/AC. It is symbolically appropriate. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- 1) We need to have the representatives of SO/ACs in the community body accountable to their own SO/ACs we need enforceable tools against these representatives 2) we need to have enforceable tools against ICANN decision that would not respect community body decision 3) we keep things as simple as possible. Do the options we are considering
have these requirements? Are SO/ACs already UAs? Legal counsel to clarify. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Holly said we might already be UAs. There is no difference but difference in how it can be explained to others and how will it be perceived adds a level of complexity. Existence of UA and its descriptions makes it even more complex. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">--> Agrees with three requirements - there are a number of options: 1) UAs as members ; 2) Human beings designated by UAs as members. You need some entity to have enforceable right. There needs to be a level of intent, basis/minimal rules to help indicate who is involved
in organization. There may be benefits in being registered as UA. Discussion around UAs have added a degree of complexity. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">--> We are fine-tuning to make things as easy as possible. The member model is best way for community to get powers. Whether the SO/AC is member or a delegate appointed by SO/AC, you need some power to ensure that that person is respectful of desires of community group he/she represents. Traditionnally the way to get there is to have group be legal person itself. The additional benefit you would have by registering UAs as an entity, you get liability protection that comes with it. As many rules you have, you have formed intent to create
UA, we are advocating final step of registering for legal benefit. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- ICANN will require certain legal balance: enforceability that considers reality. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Are we on same page with respect to enforceability? If the group considers robust enforceability as a requirement, then we are taking about membership model. Question is how do we implement membership model. Using UAs would be a very good implementation model. Concerns about complexity this might add. If we have set of requirements that are implemented including UAs, would you still go for other option even if we had to sacrifice goals? We need to communicate the whole accountability architecure in professional matters. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- The reference that some SO/ACs may already be UAs, we do not want SO/ACs to be UAs but to have a shadow. Perceived complexity of how people will understand ICANN. There has been a discussion on potential problems of if we had ability to go to Court we end up with possibility. When writing these rules can we waive the right to go to court?<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- It might be useful to have a comparitive table betweem UA and non UA membership - pros and cons - degrees of implementation and complexity.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Concerned about discussion - if we want to end up being organization where we are able to go to Court, it is not an organization I would like to join. Best way would be international organization. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Conversation is missplaced - enforceability issue is about having authority that we are putting in Bylaws. It is not about going to Court. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Governance arrangements's basis principle is to prevent going to Court. The fact that you can go to Court is a credible threat so that no one goes to Court. We need to acknowledge feedback on complexity. Suggestion would be for the CCWG to create UA - we submit to group draft articles of association based on legal counsel's legal input. Anyone on this list can comment and add concern on UA. We can report to community first hand.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- If you create a legal person, perception that might lose multistakeholder model soul, it does not have any reality attached to it. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- It is not the legal process, it is the perception that it will cause among others that is problematic. Is it possible to waive litigation?<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Having ability to go to Court and ability to remove Board directors are the two powers/authorities that make it so unnecessary <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Powers that are put in place are far more complex that anything having to do with UAs. Struggling to understand why UAs are causing so much concern when it is the least complex part of this entire process. You can certainly waive rights to Courts but why create such a complex set if not going
to use them? <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Setting up a UA documenting how we do it and explaining steps that need to be taken might help explain concept to community together with far more complex escalation path we have already been working on. Suggestion: Cochairs to talk to Comms Team to see if can facilitate comms to community.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">ACTION ITEM - CoChairs to reach out to Comms Team to analyse feasibility. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Overall structure may be complex and may benefit from further explanation. We need to see how we can boil complexity. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Does this structure increase opportunity for individual members to litigate on their own without community consensus? <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Threshold could probably be set (member approval before litigation).<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">ACTION ITEM: Legal counsel to do some research on litigation threshold. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- How do we have people understand the overall process? A lot of this is about explanability. Issue of individual members taking action.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">ACTION ITEM: CCWG to go through memorandums put together by counsel on UAs - <a href="https://community.icann.org/download/attachments/52890082/REVISED%20Memo%20on%20Unincorporated%20Associations%20May%203%2C%202015-207411876-v4.pdf?version=1&modificationDate=1430694085000&api=v2" target="_blank"><span style="color:#0563C1">https://community.icann.org/download/attachments/52890082/REVISED%20Memo%20on%20Unincorporated%20Associations%20May%203%2C%202015-207411876-v4.pdf?version=1&modificationDate=1430694085000&api=v2 </span></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">We will reach out to comms Team to see how we can explain this. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Complexity for UA membership implementation needs to be added. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">--> We need to define scenarios first and will be able to provide clear table. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">ACTION ITEM - Provide clear comparative documentation on models. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><b>Legal Group & Engagement with Lawyers</b><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">We had discussion on last call where concept of rearranging legal subteam was suggested. We have reached out to ICANN to provide us with information on legal costs incurred so far. We have hit
1 million dollars for CCWG. We will be asking for timesheets and more detail on time being sent on what subject. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Variety of expertise, getting lawyers up-to-speed and research on legal requirements/implementation added to legal costs. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">1,7 million for both CCWG and CWG <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">We will be exercising more control on costs. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><b>Work Plan Post BA - Second Public Comment Period</b><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Public comment will end on 3 June. Staff will populate comment review tool by June 7. Our regular call on June 9 is going to be extended by an hour to ensure everyone is comfortable the PCRT
was populated in appropriate manner. That will kick WP work on analysing comments. June 16 will be freeze date for WPs' output. We will be assessing which parts raise concerns, divergences, agreements etc.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">BA schedule:<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%;mso-list:l0 level1 lfo1">
Board discussion on Sunday<o:p></o:p></li><li class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%;mso-list:l0 level1 lfo1">
Working session on Wednesday and Thursday<o:p></o:p></li><li class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%;mso-list:l0 level1 lfo1">
We are working on engaging each SO/AC to hold dedicated sessions.<o:p></o:p></li></ul>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">We will then move into phase where our goal will be to launch a 40-day comment period. We will attempt to finalize proposal in time for Dublin meeting which means we will need to finalize proposal by October 9. We have the month of July to finalize document for comment. Do we plan for a F2F or intensive session? Do we move fast and finalize this before or after July 20? Is it currently foreseen that there would be a need to have specific work groups or support for that period? There is some support among Chairs and Rapporteurs for a F2F in July. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><u>Feedback</u>:<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- What happened to consensus work plan?'<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">--> We are planning to try and close as many items as early as possible if we get consensus on IRP or reconsideration process e.g.. This is planning for outstanding issues in July. It is not replacing the approach described by Thomas. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- July 16 difficult. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">ACTION ITEM - Cochairs to follow up on F2F/intensive session on list. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Objective is to select dates and determine format asap. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><b>6. A.O.B</b><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Video is not available. As part of engagement activity, we are planning to do videos to help community understand what we are working on. Pilot is currently being finalized by comms Team. We will review and will share with group. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Lawyers have not received stream of emails on UAs. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">ACTION ITEM - staff to investigate whether lawyers have access to mailing list. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Lawyers would welcome guidance on what is needed for Buenos Aires. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">ACTION ITEM – Thomas to check whether GAC wants a briefing session<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">ACTION ITEM - Cochairs to provide lawyers on clear Buenos Aires expectations<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><o:p> </o:p></span></p>
</div>
</body>
</html>