<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /></head><body>You may be correct that allowing another AC/SO to initiate a petition without the explicit support of the affected SO is a waste of time. But Jordan's proposal is a simple and seeminly sufficient fix to the problem.<br>
-- <br>
Sent from my mobile. Please excuse brevity and typos.<br><br><div class="gmail_quote">On November 19, 2015 12:59:18 AM EST, Seun Ojedeji <seun.ojedeji@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<p dir="ltr">Sent from my Asus Zenfone2<br />
Kindly excuse brevity and typos.<br />
On 19 Nov 2015 00:55, "Jordan Carter" <<a href="mailto:jordan@internetnz.net.nz">jordan@internetnz.net.nz</a>> wrote:<br />
><br />
> Hi everyone,<br />
><br />
> I'd like to clarify for the list that the proposal the CCWG approved at its call yesterday does what Seun asks for: it does not allow the community to veto a bylaws change related to a PDP.<br />
><br />
> Only if the SO that ran the PDP itself feels that the bylaws change is flawed can a veto proceed. Otherwise the SO can prevent it.<br />
></p>
<p dir="ltr">SO: This is what I needed to know. That said, your statement above still seem to imply that SO that did not run the PDP can actually start a petition. Again (for PDP) this is procedurally wrong and IMO it's a waste of resources and time. Secondly using the current threshold proposed, even if the SO that ran the PDP supports the veto there is still likelihood that other SO/AC may not. Leaving such option open weakens the essence of a PDP in the first place.<br /></p>
<p dir="ltr">> The idea behind allowing the community discussion of a Conference Call phases of the escalation path was so that the whole community could hear the issues that were raised. But the veto is off the table.<br />
><br />
SO: I am not against the escalation path, I am against opening a bottom up PDP prolicy that has been implemented correctly to petition, I am against not restricting such option to the SO that ran the PDP only!<br /></p>
<p dir="ltr">> There was good representation on the call yesterday from the SOs who this primarily affects. I hope we can continue to regard the matter as closed.<br />
><br />
SO: I am not questioning the representation on the call, I am asking whether what was raised on the list was considered during the call. From your response (which you should have written the first time I asked this question), it seem part of it was considered. I have indicated the other concern above. It's fine if you want to consider it closed but at least I have made my point.</p>
<p dir="ltr">Regards<br />
> best<br />
> Jordan<br />
><br />
> On 19 November 2015 at 12:38, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:<br />
>><br />
>> Dear Co-Chairs,<br />
>><br />
>> I don't think it's appropriate to give an impression that what is said on the list does not matter unless one says it during the call. I clearly stated that what was proposed by Jordan required some reconsideration yet the minutes of the last call did not take note of that.<br />
>><br />
>> 4. PDP interaction with Standard Bylaws Veto<br />
>><br />
>> · Proposal that PDP changes come through as a package. <br />
>><br />
>> · Read the full proposal here: <a href="http://mm.icann.org/pipermail/accountability-cross-community/2015-November/008104.html">http://mm.icann.org/pipermail/accountability-cross-community/2015-November/008104.html</a><br />
>><br />
>> · No objection to the proposal. <br />
>><br />
>> Even though one expect the communities will not veto bylaw change that emanated from a PDP. It is procedurally wrong to subject outcome of a PDP to community veto. Providing such option opens up can of worms that those who have made this decision may not be there to resolve. The fact that the board approves a policy that emanated out of PDP (which is a bottom up process) implies board's commitment to implement the spirit of the policy and it is if/when the implementation is not rightly done that it should be questioned. Actual implementation of a policy SHOULD not be open to community veto! Even if the policy requires a bylaw change so long as it went through PDP and so long as board approves it, it should be final.<br />
>><br />
>> Overall I think the CCWG is creating too much stumbling block to make an organisation board act efficiently.<br />
>><br />
>> Regards<br />
>> Sent from my Asus Zenfone2<br />
>> Kindly excuse brevity and typos.<br />
>><br />
>> On 17 Nov 2015 22:52, "Brenda Brewer" <<a href="mailto:brenda.brewer@icann.org">brenda.brewer@icann.org</a>> wrote:<br />
>>><br />
>>> Hello all,<br />
>>><br />
>>> <br />
>>><br />
>>> The notes, recordings and transcripts for CCWG ACCT meeting #68 - 17 November will be available here: <a href="https://community.icann.org/x/h7VYAw">https://community.icann.org/x/h7VYAw</a><br />
>>><br />
>>> <br />
>>><br />
>>> A copy of the notes and action items may be found below.<br />
>>><br />
>>> <br />
>>><br />
>>> Thank you.<br />
>>><br />
>>> <br />
>>><br />
>>> Kind regards,<br />
>>><br />
>>> Brenda<br />
>>><br />
>>> <br />
>>><br />
>>> Action Items<br />
>>><br />
>>> · Action (CCWG Members): Chartering Org appointed members to socialise the 'Dublin Update' with respective communities and <br />
>>> prepare for release of full proposal on 30 November. <br />
>>><br />
>>> · Action (Becky/Chairs): Provide an explicit certified description of the task and all of the considerations for legal counsel to incorporate in this <br />
>>> drafting exercise. <br />
>>><br />
>>> · Action (Adler/Sidley): Request that legal counsel review the language for the Mission, noting the group's preference and Sebastien's concern <br />
>>> for non-native English speakers. <br />
>>><br />
>>> · Action (Jordan/WP1): Send a written proposal to the CCWG mailing list describing the issue and the proposed solution(s). Include<br />
>>> clarification on whether or not abstention is considered support or not. <br />
>>><br />
>>> Notes<br />
>>><br />
>>> These high-level notes are designed to help you navigate through content of the call and do not substitute in any way the transcript.<br />
>>><br />
>>> 1. Welcome, Roll Call, SOI<br />
>>><br />
>>> · Agenda slightly modifed in order, but the items remain the same as circulated earlier this week. <br />
>>><br />
>>> · Samantha and Mathieu on audio only. <br />
>>><br />
>>> 2. Opening Remarks<br />
>>><br />
>>> · Dublin Update published on Sunday (was originally labeled as a Summary, but considering the feedback on the list, the document was modified <br />
>>> slightly in purpose) <br />
>>><br />
>>> · There are some outstanding items. These will be discussed on today's call. <br />
>>><br />
>>> · This document is a communication tool for those outside the CCWG who have had a difficult time following the progress. <br />
>>><br />
>>> · Support and endorsement of Chartering Orgs is critical to the success of the CCWG. <br />
>>><br />
>>> Action (CCWG Members): Chartering Org appointed members to socialize the 'Dublin Update' with respective communities and prepare for release <br />
>>> of full proposal on 30 November. <br />
>>><br />
>>> 3. Mission Discussion <br />
>>><br />
>>> · On the left is the language circulated immediately after Dublin (based on 2nd Draft Proposal). <br />
>>><br />
>>> · Since then, the discussion has evolved to present different alternatives (one from Andrew Sullivan, one from Shatan/Mueller/Bladel and one from Mueller). <br />
>>><br />
>>> · Support for Alternative 1 language. <br />
>>><br />
>>> · Add "ICANN shall have the ability to negotiate, enter into and enforce agreements with contracted parties [in service of / in so far as these <br />
>>> agreements are consistent with /in furtherance of / consistent with/ in performing] its Mission.". This group's preference was "in service of"<br />
>>><br />
>>> Action (Becky/Chairs): Provide an explicit certified description of the task and all of the considerations for legal counsel to incorporate in this <br />
>>> drafting exercise. <br />
>>><br />
>>> Action (Adler/Sidley): Request that legal counsel review the language for the Mission, noting the group's preference and Sebastien's concern for non-native English speakers. <br />
>>><br />
>>> 4. PDP interaction with Standard Bylaws Veto<br />
>>><br />
>>> · Proposal that PDP changes come through as a package. <br />
>>><br />
>>> · Read the full proposal here: <a href="http://mm.icann.org/pipermail/accountability-cross-community/2015-November/008104.html">http://mm.icann.org/pipermail/accountability-cross-community/2015-November/008104.html</a><br />
>>><br />
>>> · No objection to the proposal. <br />
>>><br />
>>> 5. Decision-making - thresholds of support<br />
>>><br />
>>> · There is no document for this issue, but there has been discussion on list. <br />
>>><br />
>>> · If the GAC does not participate in the community mechanism, the thresholds currently in place would require unanimous participation.<br />
>>><br />
>>> · GAC position currently: GAC will take a position when we have the position on the paper. Until then, the GAC has consensus <br />
>>> input on the second draft report.<br />
>>><br />
>>> Action (Jordan/WP1): Send a written proposal to the CCWG mailing list describing the issue and the proposed solution(s). Include <br />
>>> clarification on whether or not abstention is considered support or not. <br />
>>><br />
>>> 6. ST-18 subgroup update <br />
>>><br />
>>> · The first ST-18 subgroup call was yesterday. <br />
>>><br />
>>> · Another call scheduled for tomorrow (Wednesday) at 13:00 UTC. <br />
>>><br />
>>> · The goal is to come back to the CCWG by next Monday at the latest (so that results are ready for the CCWG call on Tuesday). <br />
>>><br />
>>> 7. Timeline Discussion<br />
>>><br />
>>> · 21 – 23 Nov-15 Feedback from CCWG<br />
>>><br />
>>> · 23-Nov-15 Final comments on Full Proposal content due from CCWG by midnight UTC<br />
>>><br />
>>> · 24 – 25 Nov Finalizing content (send to translation/formatting at midnight UTC on 25th)<br />
>>><br />
>>> · 30-Nov-15 Beginning of Public Comment Phase 2 (and begin professional proofreading/final editing)<br />
>>><br />
>>> · 12 -Dec-15 Anticipated date for delivery of translations <br />
>>><br />
>>> · 21-Dec-15 Public comment ends<br />
>>><br />
>>> · 24-Dec-15 Staff summary of public comment for review<br />
>>><br />
>>> 8. AOB<br />
>>><br />
>>> n/a<br />
>>><br />
>>> <br />
>>><br />
>>><br />
>>> _______________________________________________<br />
>>> Accountability-Cross-Community mailing list<br />
>>> <a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br />
>>> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br />
>>><br />
>><br />
>> _______________________________________________<br />
>> Accountability-Cross-Community mailing list<br />
>> <a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br />
>> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br />
>><br />
><br />
><br />
><br />
> -- <br />
> Jordan Carter<br />
><br />
> Chief Executive <br />
> InternetNZ<br />
><br />
> +64-4-495-2118 (office) | +64-21-442-649 (mob)<br />
> Email: <a href="mailto:jordan@internetnz.net.nz">jordan@internetnz.net.nz</a> <br />
> Skype: jordancarter<br />
> Web: <a href="http://www.internetnz.nz">www.internetnz.nz</a> <br />
><br />
> A better world through a better Internet <br />
><br />
</p>
<p style="margin-top: 2.5em; margin-bottom: 1em; border-bottom: 1px solid #000"></p><pre class="k9mail"><hr /><br />Accountability-Cross-Community mailing list<br />Accountability-Cross-Community@icann.org<br /><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br /></pre></blockquote></div></body></html>