July 2014 - Internal-cg - lists.icann.org

final version of the charter
by Jari Arkko July 18, 2014

July 18, 2014

As agreed, I have taken what we had at the end of this morning’s session, taken into account Paul’s suggested edits, Joe’s suggested edits, and showed this to Milton, Alissa, and Joe. We four believe it is ready. (But I have not read the mailing list in the meanwhile.) The document has change marks from v5->v6. Jari

3 2

charter version 5
by Jari Arkko July 18, 2014

July 18, 2014

3 4

Suggested input for Secretariat tasks (non-tasks)
by Tracy Hackshaw July 18, 2014

July 18, 2014

Hello Colleagues, The [Secretariat] should scan the global landscape for discussions/forums/events on the IANA Stewardship and related issues, especially in the regional/local IGFs and similar meetings - alert the CG and provide briefs/summaries on the outcomes of same. If not the Secretariat, I am not certain that this important part of the input - which may float outside of the "traditional" community consciousness should be left to the members of the CG. Respectfully submitted, TRACY HACKSHAW (MR.) | Dy National Chief Information Officer | Ministry of Science and Technology | Level 19, Tower D, International Waterfront Complex, Wrightson Rd. Port of Spain, Republic of Trinidad and Tobago | Direct: + 1 868 743 5576 | Mobile: +1 868 678 8710 |

1 0

GAC Participation on the IANA Transition Coordination Group
by Lynn St.Amour July 18, 2014

July 18, 2014

Dear CG members, thank you for all the goodwill shown in our discussion earlier today. There was a clear focus on moving ahead, and it was a real team effort. As discussed, I offer the following text for your review. Once we agree the text, I believe the next step is to send this to the GAC Chair - Heather Dryden, either from the CG Chair if one has been appointed at that point, if not perhaps from ICANN staff (Theresa?). Note also: I assumed successful conclusion in Day 2 on several items where we seem to be well advanced; obviously if we are not able to close on these in Day 2, we may need to alter the text below. Fire away, I am sure it can be improved. Best, Lynn -------- To be sent to: Heather Dryden - GAC Chair Heather, the IANA Transition Coordination Group (CG) would like to thank you for your participation in our inaugural meeting, especially as it came in the middle of your vacation. As you likely observed, significant progress was made on several fronts. In particular, the CG has high alignment [reached agreement] on: 1) a group charter, 2) a scoping statement for our work, 3) clear expectations that the work be done in the respective communities, with participation from all stakeholders, leaving the CG the relatively narrow role of coordination, and 4) a nascent agreement that we would operate by "consensus" judged more by the merit of the objections rather then the number. These are important to note as these are expectations for all members of the CG, and it is critically important that we all commit to them. We have quite an ambitious goal and an aggressive timetable. To the question at hand, following on from the GAC request that the GAC be allowed to appoint five (5) individuals to the CG, and noting that the original allotment was not established through consultation with the GAC, nor of course the CG as it had not been established at that time. The CG recognized the benefit to all of gaining an early and broad perspective from governments. We also believe that this will allow for liasing beyond the normal GAC processes, and this will ultimately be key to global acceptance of the transition proposal. The CG also asked for assurance that there would be participation from the GAC in other IANA Transition community efforts. In other words, increased participation in the CG should not supplant participation in other community efforts related to the IANA Stewardship Transition. In closing, we would like to thank the GAC for working with us through this process, and believe we have a solution that will benefit us all in the end. Best regards,

6 6

Re: [Internal-cg] report on self-organization
by Mohamed El Bashir July 18, 2014

July 18, 2014

The representation of non-operational community stakeholders is important, beside ALAC being the community that able solicit regional community inputs in the process ( via its RALO structures ) . I would like to Nominate Jean-Jack S. for a co-chair seat . Second nomination of Kieth as a co-chair. Regards, Mohamed On Fri, Jul 18, 2014 at 1:35 PM, Drazek, Keith <kdrazek(a)verisign.com> wrote: > I volunteer to serve as Co-Chair on behalf of the GNSO/gTLD group. > > I also support Alissa, Russ and Patrik. > > Thanks, > Keith > > -----Original Message----- > From: internal-cg-bounces(a)icann.org [mailto:internal-cg-bounces@icann.org] > On Behalf Of Patrik Fältström > Sent: Friday, July 18, 2014 6:17 AM > To: Russ Housley > Cc: tom(a)acig.com.au; ICANN Internal > Subject: Re: [Internal-cg] report on self-organization > > My email access is spotty so my apologies if this is a duplicate. > > I support Alissa and volunteer myself given my knowledge of all three main > groups plus the fact SSAC is chartered to look at all three while not being > part of any of the PDPs more than as advisor. > > Patrik > > > On 18 jul 2014, at 10:22, Russ Housley <housley(a)vigilsec.com> wrote: > > > > Alissa did a great job putting together the agenda, recruiting people to > serve as session leaders, and running the meeting. I support her for one > of the co-chair slots. > > > > I am willing to serve as another co-chair. > > > > Russ > > > > > >> On Jul 18, 2014, at 3:26 AM, Alissa Cooper wrote: > >> > >> Since some folks are remote or not able to attend, I think it would > >> help for the discussion later today for people to volunteer by email > >> to this list. I’m willing to volunteer for a co-chair slot. > >> > >> Alissa > >> > >> > >> > >>> On 7/17/14, 11:45 PM, "joseph alhadeff" <joseph.alhadeff(a)oracle.com> > wrote: > >>> > >>> Colleagues: > >>> > >>> Please find attached a summary of the discussion, findings and > >>> outstanding items of the session on self-organization. > >>> > >>> Heather, Tom I am copying you for the information of the 5 GAC > >>> nominees as well. > >>> > >>> There will be a further session on this topic tomorrow with the > >>> potential for volunteers to identify themselves and set forth what > >>> they could bring to their roles. Depending on the outcome of that > >>> process, we may be able to finalize the positions tomorrow. > >>> > >>> Best regards, > >>> > >>> Joe > > > > _______________________________________________ > > Internal-cg mailing list > > Internal-cg(a)icann.org > > https://mm.icann.org/mailman/listinfo/internal-cg > _______________________________________________ > Internal-cg mailing list > Internal-cg(a)icann.org > https://mm.icann.org/mailman/listinfo/internal-cg > _______________________________________________ > Internal-cg mailing list > Internal-cg(a)icann.org > https://mm.icann.org/mailman/listinfo/internal-cg >

1 0

report on self-organization
by joseph alhadeff July 18, 2014

July 18, 2014

Colleagues: Please find attached a summary of the discussion, findings and outstanding items of the session on self-organization. Heather, Tom I am copying you for the information of the 5 GAC nominees as well. There will be a further session on this topic tomorrow with the potential for volunteers to identify themselves and set forth what they could bring to their roles. Depending on the outcome of that process, we may be able to finalize the positions tomorrow. Best regards, Joe

7 6

Your mailing list archives
by Alice Jansen July 18, 2014

July 18, 2014

Dear Coordination Group Members, Further to your decision (18 July) to make public the mailing list archives, please see the link at: http://mm.icann.org/pipermail/internal-cg/ Thanks, Best regards Alice

1 0

Verisign June 25 Blog Post on IANA Transition and ICANN Accountability
by Drazek, Keith July 18, 2014

July 18, 2014

All, In case you haven’t already seen it, this is my CircleID blog post from the London #50 ICANN meeting. It is focused primarily on the Naming and gTLD perspectives and not on Numbers and Protocol Parameters, but I wanted to share this to provide context and to ensure there’s no confusion about Verisign’s position as we embark on this very important process. http://www.circleid.com/posts/20140625_iana_ensuring_icann_accountability_a… Please let me know if you have any questions. Regards, Keith “This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.”

1 0

Charter version 4
by Jari Arkko July 18, 2014

July 18, 2014

Version 4 after a breakfast meeting with Milton, Mary, and Alissa. We have I believe gone through all comments (in some cases making our own version of the suggested change, however). Change marks are turned on in the document, so you see what has been done. The scope language edited yesterday by the group has also been included (with small edits from Milton). We can discuss this further in the group meeting today. Thanks, all. Jari

7 13

GNSO Joint Statement on ICANN Accountability and IANA Transition
by Drazek, Keith July 18, 2014

July 18, 2014

All, for your information, the text below is the final GNSO Joint Statement on ICANN Accountability and IANA Transition from the ICANN London meeting three weeks ago. I wanted to share this with you to help inform our discussions and to help everyone better understand the perspectives of the GNSO. This is a consensus position of the GNSO with full support of all constituencies and stakeholder groups. Such a consensus statement of the entire GNSO was actually an unprecedented event. Here’s the text: The entire GNSO joins together today calling for the Board to support community creation of an independent accountability mechanism that provides meaningful review and adequate redress for those harmed by ICANN action or inaction in contravention of an agreed upon compact with the community. This deserves the Board's serious consideration - not only does it reflect an unprecedented level of consensus across the entire GNSO community, it is a necessary and integral element of the IANA stewardship transition. True accountability does not mean ICANN is only accountable to itself, or to some vague definition of "the world." It does not mean that governments should have the ultimate say over community policy without regard to the rule of law. Rather, the Board's decisions must be open to challenge and the Board cannot be in a position of reviewing and certifying its own decisions. We need an independent accountability structure that holds the ICANN Board, Staff, and various stakeholder groups accountable under ICANN's governing documents, serves as an ultimate review of Board/Staff decisions, and through the creation of precedent, creates prospective guidance for the board, the staff, and the entire community. As part of the IANA stewardship transition, the multi-stakeholder community has the opportunity and responsibility to propose meaningful accountability structures that go beyond just the IANA-specific accountability issues. We are committed to coming together and developing recommendations for creation of these mechanisms. We ask the ICANN Board and Staff to fulfill their obligations and support this community driven, multi-stakeholder initiative. Regards, Keith “This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.”

1 0