[CWG-DT-Stewardship] Latest Version of Charter and Notes from Meeting

[Gomes, Chuck]

Thanks Marika.

All: Please see my comments below.

Chuck

From: cwg-dt-stewardship-bounces at icann.org [mailto:cwg-dt-stewardship-bounces at icann.org] On Behalf Of Marika Konings
Sent: Monday, August 04, 2014 10:05 AM
To: Jonathan Robinson; Grace Abuhamad; cwg-dt-stewardship at icann.org
Subject: Re: [CWG-DT-Stewardship] Latest Version of Charter and Notes from Meeting

Dear All,

As per Jonathan's email, please find attached a clean and redline version in which we've incorporated the different sections discussed on the mailing list (please let us know if we've missed anything). Also included are some suggested edits to address the comments in relation to the definition of participants / observers / members. Furthermore, I've updated the definition of divergence in section IV which inadvertently seemed to have the definition of consensus.

To facilitate the mailing list conversation ahead of the next meeting, we would like to propose that, similar to last week, volunteers come forward to propose specific language to address some of the remaining comments / issues and share their proposals with the mailing list. Looking through the latest version, we've identified the following issues:

  1.  Should additional language be included to encourage / allow for participation of new stakeholders? (comments #1, 5, 6R5)
[Chuck Gomes] I think it is very important for us to include such language.  This was a concern that came out of the Netmundial meeting and already there have been questions asked by stakeholders not involved in ICANN how they can participate, not just in naming IANA issues but also IETF, etc.  If this is not addressed in the charter and ultimately by the CWG, there is a risk that some will question the validity of the process after we are finished.  How about the following:
"Procedures and processes for involving participation of stakeholders who are not yet involved in ICANN groups involved in the CWG:

a.       As soon as a draft charter is approved by the DT for distribution to the chartering organizations for their approval, the chairs of the DT should send a request

                                   i.            To the chartering organization stakeholder groups, constituencies and other participants requesting that they develop and implement a plan to open their processes to stakeholders who are not yet a part of ICANN processes as applicable and to provide their plan to their respective chartering organization not later than 30 September 2014

                                 ii.            To organizations that are not directly a part of the ICANN structure such as ISOC, 1Net and any others that may be able to reach stakeholders that may not be a part of ICANN processes that they consider serving as a channel for such stakeholders to provide input to the CWG and to define their procedures for doing that and communicate those to the co-chairs of the DT not later than 30 September 2014.

b.      Not later than 7 October 2014,

                                   i.            The chartering organizations should submit the results of a.i above to the CWG

                                 ii.            The DT co-chairs should submit the results of a.ii above to the CWG

c.       Not later than 14 October 2014, staff supporting the CWG should incorporate the results received above into the draft work plan.

d.      The CWG should edit and approve this part of the work plan not later than 31 October 2014.

e.       A communication describing the procedures for stakeholders that are not a part of ICANN processes to contribute to the CWG should be prepared and distributed as widely as possible not later than 7 November 2014."

  1.  Should further guidance be included on how the ICG is expected to liaise with the CWG? (comment #3)
[Chuck Gomes] One way to approach this would be for the DT chairs to consult with the CWG chairs and jointly develop language in this regard for the charter.

  1.  Should a target deadline be included in the charter for the deliverables in the charter or should this be left up to the CWG to determine? (comment #4)[Chuck Gomes]
[Chuck Gomes] I personally think that the CWG should develop its own target deadlines but should do so in coordination with the CWG.

  1.  In relation to the sentence "Understand the views and concerns of other participants in the chartering organisation that appoints them" in section III, several comments have been made (#7 - 12). How should this sentence be updated to address the comments made?
[Chuck Gomes] How about something like this:  "Solicit and communicate the views and concerns of participants in the organization that appoints them."

  1.  Definition of consensus - it was suggested (comment #14) that a definition of minority should be included or alternatively use the definition 'a position that is supported by at least a supermajority of members'. Is there support for this change or are there other suggestions?
[Chuck Gomes] Using a term like 'supermajority' causes a need for voting, which in turn makes it necessary to define how votes will be counted fairly across all the different interest groups and individuals as applicable.  It would take a large amount of time to do that, assuming that we could even reach agreement on it.  I like the definitions provided by Tijani for full consensus and consensus.  I see no need for defining divergence; it would be the absence of consensus.

  1.  Assessing consensus and use of vote/poll (comments #15, 16 and 17) - if the DT would like to make reference to the possibility of using polls, you may want to consider including language similar to what is currently in the GNSO WG Guidelines, for example: In a rare case, the chair(s) may decide that the use of a poll is reasonable to assess the level of support for a recommendation. However, care should be taking in using polls that they do not become votes as there are often disagreements about the meanings of the poll questions or of the poll results. Would there be support for including a reference to the use of polls, and if so, would the proposed language work or are there other suggestions?
[Chuck Gomes] I support using the GNSO language or something similar.

  1.  Who/how is the final report and possible additional documents (following adoption) submitted to the ICG - should further clarification be added (comment #20, 21)
[Chuck Gomes] I think it is fine for the chairs to submit both provisional and final reports to the ICG chairs after approval is confirmed from the chartering organizations.

  1.  Closure of the WG - what additional language should be added to address comments #22 and 23?
[Chuck Gomes] How about something like  this?  "In the event that no consensus is reached by the CWG, the Final Report will document the process that was followed and will be submitted to the chartering organizations to request possible suggestions for mitigating the issues that are preventing consensus.  If consensus can still not be reached, the Final Report will document the processes followed, including requesting suggestions for mitigating the issues that are preventing consensus from the chartering organizations and will be submitted to ICG for their suggestions for mitigating the issues that are preventing consensus.  If consensus can still not be reached, request for closing the CWG should be made to the chartering organizations."  (I am not terribly comfortable with this but I like it better than simply going straight to closing the CWG.)

If there are any additional issues that need to be addressed, please share those with the mailing list. Also, if you would like to volunteer to address one or more of these issues, please let the mailing list know. Based on the feedback / suggestions provided, staff can try to hold the pen and incorporate any language that has the support of the DT in the next iteration of the draft which will hopefully will get us close to a final version by our next meeting which has been scheduled for next Monday 11 August.
[Chuck Gomes] Here are some additional issues that I think need to be addressed by the full DT:

1.       Should individuals be allowed to participate directly in the CWG or only as part of a participating group?  I favor the latter for efficiency reasons and to simplify determination of consensus as long as representatives from the various groups are required to communicate minority positions from their groups.  If personal views are shared, that should be made clear.

2.       Should observers be allowed to contribute directly in CWG deliberations or only literally as just listen-only observers.  In the latter case, it may be just as well if they listen to the recordings and/or read transcripts.

3.       If subgroups are used, would a maximum of 5 participants per group in the CWG make it impossible to have geographic diversity in subgroups?

4.       If the GNSO is limited to a maximum of 5 representatives in the CWG, that would not cover all of its SGs and constituencies.  If the ccNSO is limited to a maximum of 5 representatives, that would only allow one per geographic region and possibly no-one from ccTLDs that are not members of the ccNSO?  Should the maximum of 5 be reconsidered?

I welcome discussion on all of the above.

Thanks,

Marika

From: Jonathan Robinson <jonathan.robinson at ipracon.com<mailto:jonathan.robinson at ipracon.com>>
Date: Monday 4 August 2014 10:54
To: Grace Abuhamad <grace.abuhamad at icann.org<mailto:grace.abuhamad at icann.org>>, "CWG-DT-Stewardship at icann.org<mailto:CWG-DT-Stewardship at icann.org>" <CWG-DT-Stewardship at icann.org<mailto:CWG-DT-Stewardship at icann.org>>
Subject: Re: [CWG-DT-Stewardship] Latest Version of Charter and Notes from Meeting

All,

Looking back a week and with our target to complete the draft charter on or shortly a 14 August, it seems sensible to pick up on the actions from last week.
Essentially, we have agreed to try to continue to make iterative improvements over the course of this week ahead of meeting for review next week Monday.

Please could staff circulate a redline and clean version of the charter as it currently stands, including incorporating the latest edits discussed / agreed on this list but not necessarily incorporated into the draft yet.

Once we have this latest version, please could all DT members re-read and consider:


A.      Your level of comfort with current / latest edits and proposed changes (if any)

B.      Any changes you wish to propose to the document as it now stands (particularly section III on)

Also:


*        GAC - Do we need to issue any formal note of invitation to join the CWG or should that now wait until we have the Charter in a form we are willing to distribute to all SO & ACs?

*        Warning of pre-consideration to SO & Acs. Informal routes agreed but supplemented by the record of a formal note from CCWG Co-chairs required.

Next meeting is August 11th, 13h00 UTC.


Thanks,


Jonathan





From: cwg-dt-stewardship-bounces at icann.org<mailto:cwg-dt-stewardship-bounces at icann.org> [mailto:cwg-dt-stewardship-bounces at icann.org] On Behalf Of Grace Abuhamad
Sent: 28 July 2014 21:01
To: cwg-dt-stewardship at icann.org<mailto:cwg-dt-stewardship at icann.org>
Subject: [CWG-DT-Stewardship] Latest Version of Charter and Notes from Meeting

Dear All,

As discussed during our meeting today, please find attached the latest version of the draft charter. Notes from today's meeting are below and available on the Wiki at: https://community.icann.org/x/Qr3hAg


Agenda - 28 July 2014

1.      Welcome and roll-call

2.      Confirmation of meeting notes and action items

3.      Timeline Approval of charter and call/appointment of volunteers WG (In order to adopt charter in time, organize membership of the WG itself and have a first full-blown face to face meeting in LA, the draft charter needs to be completed by 14 August, order of approval will be ccNSO (21 August), ALAC (26 August), SSAC (2 September) and GNSO (4 September)).

4.      Timelines and coordination with ICG

5.      Run-through latest version of draft charter

6.      AOB

7.      Closure


Meeting Notes / Action Items 28/7:


?         Meeting notes from 21/7 accepted

?         Byron reached out to GAC chair with reminder and re-invitation to join CWG. Action: Follow up next week for further suggestion regarding GAC participation in CWG

?         Add to agenda for meeting: resourcing; Root Zone maintainer; public consultation.

o   Resourcing was not discussed: defer for 4 August

o   Public Consultation - partly addressed in Timeline overview (Item 4 on the agenda)

Timeline

?         Who will forewarn SSAC, and other groups, to allow pre-consideration - Action: Pre-warning by members and formal documentation by chairs of the convening SOs (Byron and Jonathan) to invite the SOs and ACs as well. Rationale: documentation of process.

?         Linking to Accountability process: to date the timeline and activities of the Accountability Process are not defined enough in detail to map them against the IANA Stewardship Transition Process. Action: Staff to evolve timeline with Accountability process when that information becomes available. Action: Share timelines with staff (Bart).


Discussion draft charter

?         Comment 1: General agreement of attendees that goal is that WG will deliver a single proposal, while recognizing more then one could evolve, with aim to get to one proposal through iterative process. Action: Wordsmith language - volunteers for capturing language on "single proposal": Julie, Leon, and Allan

?         Highlighted phrase to .INT deleted

?         Language on Root Zone Maintaining process: re-focus on role of NTIA in Root Zone maintainer process. Action: Avri and Chuck to propose language to the group. Group aware of Chuck's role and no objection.

?         Relation with Accountability Process: Avri's comment related to ICG language acceptable to all and will be included.

?         Start with Section III next week (4 August).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cwg-dt-stewardship/attachments/20140804/5ceba34f/attachment-0001.html>