- Internal-cg - lists.icann.org

CALL 01 - Draft Preliminary Report for your consideration
by Alice Jansen July 16, 2014

July 16, 2014

Dear Coordination Group Members, At the start of your call 01 (Thursday, 10 July), it was suggested that minutes of the call would be desirable. Attached to this email is a draft preliminary report for your consideration. The call recording may be found at http://ftp.adigo.com/clients/icann/20140710_CoordinationGroupCall1_ID894448… and you will find the transcript in the attachments (to be posted online today). Please send any edits you may have. Thank you, Best regards Alice

1 0

Naming the group was RE: scheduling meetings
by Narelle Clark July 16, 2014

July 16, 2014

I've been calling it the NISTCG for want of a better term. Ie the NTIA IANA Stewardship Transition Co-ordination Group. Some of our community objected to it being the 'IANA transfer' group because in their mind they didn't think IANA needed to be transferred at all, but the NTIA. That would rule out Daniel's ICOB. Something witty and catchy would be good - NXFER anyone? Narelle -----Original Message----- From: internal-cg-bounces(a)icann.org [mailto:internal-cg-bounces@icann.org] On Behalf Of Wolf-Ulrich.Knoben(a)t-online.de Sent: Sunday, 13 July 2014 9:04 PM To: Jari Arkko Cc: internal-cg(a)icann.org Subject: Re: [Internal-cg] scheduling meetings I also agree. BTW do we have an appropriate acronym for our group? "CG" seems too general. Maybe something with relation to IANA: ICG, CIG, CGI... Let's fix this asap to communicate to our respective groups. Wolf-Ulrich Sent from my personal phone > Am 13.07.2014 um 04:20 schrieb Jari Arkko <jari.arkko(a)piuha.net>: > > >> For those of us with demanding jobs other than ICANN, it would be useful if we could combine CG meetings with other ICANN meetings to some extent. >> E.g., target L.A. ICANN meeting in October for our next F2F, add a day on to the beginning or end. IETF or RIR meetings might serve a similar function if we think we need to increase the frequency of F2F meetings (which I hope we don't!) > > I agree with this as well. And IGF, which is coming up. > > Jari > > P.S. The IETF would be happy to see you all in some of our meetings, and you might even stay a few extra days, as we discuss IANA and other topics. You'd be warmly welcome in our Honolulu meeting (Nov 9-14) for instance :-) Or our upcoming Toronto meeting that starts a day after the coordination group meeting in London ends. Future meetings are at http://www.ietf.org/meeting/upcoming.html We also have an IETF policy guest program run by ISOC, a very popular program and something that you might consider if you have not been to an IETF meeting earlier. >

9 8

amended draft charter
by Milton L Mueller July 16, 2014

July 16, 2014

Dear all Here are my proposed amendments. Other than being a more specific than Jari's first draft, I was impressed while doing this how small the substantive differences are. Take a look. (Word file attached, text appended below) See you in London -MM Draft charter for the IANA Stewardship Transition Coordination Group The IANA transition coordination group (ICG) has one deliverable, a proposal to the U.S. Commerce Department National Telecommunications and Information Administration (NTIA) regarding the transition of NTIA's stewardship of the IANA functions to the Internet community. The group's mission is to coordinate the development of a proposal among the communities affected by the IANA functions. The IANA parameters fall into three categories: domain names, number resources, and other protocol parameters. While there is some overlap among these categories, each poses distinct organizational, operational and technical issues, and each tends to have distinct communities of interest and expertise. For those reasons it is best to have work on the three categories of IANA parameters proceed autonomously in parallel and be based in the respective communities of interest. The coordination group has four main tasks: (i) Act as liaison to the three communities of interest (names, numbers, protocols) (ii) Assess the outputs of the three communities of interest for workability, compatibility and consensus (iii) Assemble a complete proposal for the transition (iv) Information sharing and public communication Describing each in more detail: (i) Liaison Members of the ICG will ensure that the communities from which they are drawn are working on their part of the transition plans. This involves informing them of requirements and schedules, tracking progress, and highlighting the results or remaining issues. The role of a coordination group member during this phase is to provide status updates about the progress of his or her community in developing their component, and to coordinate which community will develop a transition proposal for each area of overlap (e.g., special-use registry) (ii) Assessment When the group receives output from the independent groups it will discuss and assess their workability, assess their compatibility and interoperability with the proposals of the other groups, and verify their levels of support in the respective communities. The ICG might at some point detect problems with the component proposals. At that point the role of the ICG is to communicate that back to the relevant communities so that they (the relevant communities) can address the issues. In assessing consensus, the coordination group will rely to some extent on its members to reflect to the rest of the group the support levels within the member's own community, but the group is also authorized to engage in independent assessments, such as public notice and comment periods. (iii) Assembling and submitting a complete proposal The assembly effort involves taking the proposals for the different components and verifying that they fulfil the intended scope, meet the intended criteria, that there are no missing parts, and that the whole fits together. The ICG will then develop a draft final proposal that achieves consensus within the ICG itself. The ICG will then put this proposal up for public comment period involving a reasonable period of time for reviewing the draft proposal, analyzing and preparing supportive or critical comments. The ICG will then review these comments and determine whether modifications are required. If not, and the coordination group agrees, the proposal will be submitted to NTIA. If The ICG is authorized to make minor amendments in consultation with the affected communities of interest. If, in the ICG's opinion, broad public support for the proposal as articulated by the NTIA is not present, the parts of the proposal that are not supported return to the liaison phase. (iv) Information sharing The ICG should serve as a central clearinghouse for public information about the IANA stewardship transition process. Its secretariat should maintain an independent website, under its own domain, where status updates, meetings and notices are announced, proposals are stored, the ICG members are listed, etc.

1 0

Meeting agenda
by Alice Jansen July 16, 2014

July 16, 2014

Dear Coordination Group Members, It is our understanding that you have been working on refining your meeting agenda in light of recent discussions. In preparation for tomorrow, would you have a final or updated version we could print out for the group to have? We will also make sure to have the agenda posted online. Thanks, Best regards Alice

1 0

Re: [Internal-cg] Welcome and additional information
by Tracy Hackshaw July 16, 2014

July 16, 2014

Hello Colleagues, Thank you for the welcome and for the information provided. Due to the tight logistics and flight schedules involved, I will be joining in person on Friday morning ... arriving to the meeting direct from my overnight flight from the Caribbean to London Gatwick. My flight is due to arrive at 850 am and I will do my best to join the meeting as soon as possible thereafter. Apologies in advance for my late arrival. Rgds, 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 | Voice: + 1 868 728 7304 | Mobile: +1 868 678 8710 | Sent from Android -------- Original message -------- From: Theresa Swinehart Date:16/07/2014 7:35 AM (GMT-04:00) To: internal-cg(a)icann.org Subject: [Internal-cg] Welcome and additional information Dear Coordination Group Members, First, welcome everyone and thank you for all the work you have and are about to undertake. The full list of Coordination Group members is in place, but for the decision regarding the GAC members per your call last week. As an interim measure, yesterday we were advised that the GAC has identified 2 participants who will be attending, Chair, Heather Dryden, and one Vice-Chair, Tracy Hackshaw. The Coordination Group membership will be updated shortly to reflect this as well. The full list can be found at: https://www.icann.org/resources/pages/coordination-group-2014-06-17-en Coordination Group members confirmed to participate remotely or in person in the attachment. Second, with this note I wanted to provide some additional information to complement the information sent out last week (please see attached). I'd been asked to also provide a summary of some thinking around the secretariat related work, which I'll send out separately. Before getting to the information below, one thing - I'd like to provide some administrative and operational information to the Coordination Group at the start of the meeting. Would it be possible to add that to the start of the agenda? Skeletal outline of breakfast, meals, and meeting room: (as shared last week) (please let us know if you don't wish to join for the dinners). Wednesday, 16 July: Depending on your arrival time, please join us at the Library (located in hotel lobby) for an informal cocktail reception at 19:00-20:30. Thursday, 17 July: 07:00-09:00: Breakfast available at the Fiamma Restaurant in hotel lobby (breakfast is included in the room rate) 09:00-17:00/18:00 – Coordination Group Meeting – times at the group's discretion. 18:30 – Shuttle leaves hotel for dinner location. 19:00-21:00 – Dinner at Galvin¹s Restaurant in Park Lane Hilton Hotel 21:00 – Shuttle returns to hotel. Friday, 18 July 07:00-09:00: Breakfast available at the Fiamma Restaurant in hotel lobby. 09:00-17:00/18:00 – Coordination Group Meeting – times at the group's discretion. 19:00-21:00 – Dinner at Minako restaurant on 23rd floor Logistics for the London meeting: * Meeting room: Viscount meeting room (see venue map here <http://london50.icann.org/en/venue-map>). * Coordination Group members who are unable to attend in-person may participate remotely through a phone bridge. * Dial-in numbers may be found at: http://adigo.com/ICANN/ * Conference ID 92957255 * To ensure that stakeholders across the global Internet community are reached, the meeting will be streamed live through a Virtual Meeting Room <https://icann.adobeconnect.com/coordinationgroup/> and real-time audio interpretation will be available in: * English <http://stream.icann.org:8000/coordinationgroup-en.m3u> * French <http://stream.icann.org:8000/coordinationgroup-fr.m3u> * Spanish <http://stream.icann.org:8000/coordinationgroup-es.m3u> * Chinese <http://stream.icann.org:8000/coordinationgroup-zh.m3u> * Russian <http://stream.icann.org:8000/coordinationgroup-ru.m3u> * Arabic <http://stream.icann.org:8000/coordinationgroup-ar.m3u> * Portuguese <http://stream.icann.org:8000/coordinationgroup-pt.m3u> * Scribing will be available. The full transcript will be posted online shortly after the meeting ends. * If you have any presentations to be projected during the meeting also into the virtual meeting / adobe room, please send it to Ergys Ramaj at: ergys.ramaj(a)icann.org<mailto:ergys.ramaj@icann.org> * Additional interim secretariat support: * ICANN staff support present at the meeting: General support: Theresa Swinehart, Ergys Ramaj, Alice Jansen. For Communications support, Jim Trengrove and Luna Madi. Meetings team lead is Nancy Lupiano; IT lead is Cory Schruth. * Non-ICANN staff support: Samantha Dickinson, who many of you know, will provide any support writing, processing of information, draft meeting report, or other areas the Coordination Group would find useful. writing, summarization, or meeting report preparations. She will be available for the Coordination Group as needed. * Meetings and the IT teams are available to accommodate additional needs. * For communications there is support on site, and the comms team is prepared to be on stand by for several aspects including managing media inquires, preparing any final press statement the Coordination may want, as well as supporting the Coordination Group on ensuring transparency. Jim is also available to do video interviews with any coordination group members who wish to. Additional support available to the Coordination Group: * Photos, bios, video interviews of Coordination Group Representatives: Help familiarize the community with the CG Representatives, enable a strong sense of transparency and begin building a relationship between the community and the CG Representatives. * Blogging and social media: The Coordination Group may want to use blog posts and social media to increase community engagement. * Announcement at end of the meeting and information updates: The Coordination Group may consider an update on progress and other developments at the conclusion of the two-day meeting. * Language/Translation support: As indicated, interpretation and translation is provided. The language services team is available to translate announcements or proposals by the Coordination Group and will be on-site. * Website hosting: A platform to provide, house, link to other information and discussion tools for the most up to date information on the transition. Discussions still continue on the many community forums, community mailing lists, and previous ICANN-hosted IANA transition mailing list. We look forward to seeing you in London! Kind regards, Theresa

1 0

Welcome and additional information
by Theresa Swinehart July 16, 2014

July 16, 2014

Dear Coordination Group Members, First, welcome everyone and thank you for all the work you have and are about to undertake. The full list of Coordination Group members is in place, but for the decision regarding the GAC members per your call last week. As an interim measure, yesterday we were advised that the GAC has identified 2 participants who will be attending, Chair, Heather Dryden, and one Vice-Chair, Tracy Hackshaw. The Coordination Group membership will be updated shortly to reflect this as well. The full list can be found at: https://www.icann.org/resources/pages/coordination-group-2014-06-17-en Coordination Group members confirmed to participate remotely or in person in the attachment. Second, with this note I wanted to provide some additional information to complement the information sent out last week (please see attached). I'd been asked to also provide a summary of some thinking around the secretariat related work, which I'll send out separately. Before getting to the information below, one thing - I'd like to provide some administrative and operational information to the Coordination Group at the start of the meeting. Would it be possible to add that to the start of the agenda? Skeletal outline of breakfast, meals, and meeting room: (as shared last week) (please let us know if you don't wish to join for the dinners). > Wednesday, 16 July: > Depending on your arrival time, please join us at the Library (located in > hotel lobby) for an informal cocktail reception at 19:00-20:30. > > Thursday, 17 July: >> 07:00-09:00: Breakfast available at the Fiamma Restaurant in hotel lobby >> (breakfast is included in the room rate) >> 09:00-17:00/18:00 Coordination Group Meeting times at the group's >> discretion. >> 18:30 Shuttle leaves hotel for dinner location. >> 19:00-21:00 Dinner at Galvin¹s Restaurant in Park Lane Hilton Hotel >> 21:00 Shuttle returns to hotel. > > Friday, 18 July >> 07:00-09:00: Breakfast available at the Fiamma Restaurant in hotel lobby. >> 09:00-17:00/18:00 Coordination Group Meeting times at the group's >> discretion. >> 19:00-21:00 Dinner at Minako restaurant on 23rd floor Logistics for the London meeting: * Meeting room: Viscount meeting room (see venue map here <http://london50.icann.org/en/venue-map>). * Coordination Group members who are unable to attend in-person may participate remotely through a phone bridge. > * Dial-in numbers may be found at: http://adigo.com/ICANN/ > * Conference ID 92957255 > * To ensure that stakeholders across the global Internet community are > reached, the meeting will be streamed live through a Virtual Meeting Room > <https://icann.adobeconnect.com/coordinationgroup/> and real-time audio > interpretation will be available in: >> * English <http://stream.icann.org:8000/coordinationgroup-en.m3u> >> * French <http://stream.icann.org:8000/coordinationgroup-fr.m3u> >> * Spanish <http://stream.icann.org:8000/coordinationgroup-es.m3u> >> * Chinese <http://stream.icann.org:8000/coordinationgroup-zh.m3u> >> * Russian <http://stream.icann.org:8000/coordinationgroup-ru.m3u> >> * Arabic <http://stream.icann.org:8000/coordinationgroup-ar.m3u> >> * Portuguese <http://stream.icann.org:8000/coordinationgroup-pt.m3u> > * Scribing will be available. The full transcript will be posted online > shortly after the meeting ends. > * If you have any presentations to be projected during the meeting also into > the virtual meeting / adobe room, please send it to Ergys Ramaj at: > ergys.ramaj(a)icann.org * Additional interim secretariat support: > * ICANN staff support present at the meeting: General support: Theresa > Swinehart, Ergys Ramaj, Alice Jansen. For Communications support, Jim > Trengrove and Luna Madi. Meetings team lead is Nancy Lupiano; IT lead is Cory > Schruth. > * Non-ICANN staff support: Samantha Dickinson, who many of you know, will > provide any support writing, processing of information, draft meeting report, > or other areas the Coordination Group would find useful. writing, > summarization, or meeting report preparations. She will be available for the > Coordination Group as needed. > * Meetings and the IT teams are available to accommodate additional needs. > * For communications there is support on site, and the comms team is prepared > to be on stand by for several aspects including managing media inquires, > preparing any final press statement the Coordination may want, as well as > supporting the Coordination Group on ensuring transparency. Jim is also > available to do video interviews with any coordination group members who wish > to. Additional support available to the Coordination Group: >> * Photos, bios, video interviews of Coordination Group Representatives: Help >> familiarize the community with the CG Representatives, enable a strong sense >> of transparency and begin building a relationship between the community and >> the CG Representatives. >> * Blogging and social media: The Coordination Group may want to use blog >> posts and social media to increase community engagement. >> * Announcement at end of the meeting and information updates: The >> Coordination Group may consider an update on progress and other developments >> at the conclusion of the two-day meeting. >> * Language/Translation support: As indicated, interpretation and translation >> is provided. The language services team is available to translate >> announcements or proposals by the Coordination Group and will be on-site. >> * Website hosting: A platform to provide, house, link to other information >> and discussion tools for the most up to date information on the transition. >> Discussions still continue on the many community forums, community mailing >> lists, and previous ICANN-hosted IANA transition mailing list. We look forward to seeing you in London! Kind regards, Theresa

3 2

London Meeting - Program & Remote Participation
by Alice Jansen July 16, 2014

July 16, 2014

Dear Coordination Group Members, As we prepare for your first gathering in London on 17-18 July, please find below information on remote participation and a suggested program for your consideration. May we also remind individuals who require travel support to attend the meeting to please contact cgtravel(a)icann.org<mailto:cgtravel@icann.org> as soon as possible. Delays in providing your information will not guarantee travel support. Remote Participation Should you not be in a position to attend the meeting in person, please find below audio information on how to be connected to the room. By joining the bridge, you will be able to interact directly with the room. * Dial-in numbers may be found at: http://adigo.com/ICANN/ * Conference ID 92957255 Please make sure to not share and/or communicate the bridge details as its use is intended for Coordination Group Members only. The global multistakeholder community will be able to follow your exchanges through the virtual meeting room: https://icann.adobeconnect.com/coordinationgroup/. Coordination Group Members participating remotely in the meeting should join the adobe connect room to view any material (if any) being displayed in the meeting room. Please note that we will have interpreting services at the meeting. Links to the respective languages are available below: English: http://stream.icann.org:8000/coordinationgroup-en.m3u French: http://stream.icann.org:8000/coordinationgroup-fr.m3u Spanish: http://stream.icann.org:8000/coordinationgroup-es.m3u Chinese: http://stream.icann.org:8000/coordinationgroup-zh.m3u Russian: http://stream.icann.org:8000/coordinationgroup-ru.m3u Arabic: http://stream.icann.org:8000/coordinationgroup-ar.m3u Portuguese: http://stream.icann.org:8000/coordinationgroup-pt.m3u Suggested program Wednesday, 16 July All day arrivals at the Hilton London Metropole Hotel. Depending on your arrival time, please join us at the Library (located in hotel lobby) for an informal cocktail reception at 19:00-20:30. Thursday, 17 July 07:00-09:00: Breakfast at the Fiamma Restaurant in hotel lobby. 09:00-17:00/18:00 – Coordination Group Meeting. The end time of the session will be at the group's discretion. The session will take place in the Viscount room (venue map is available here<http://london50.icann.org/en/venue-map>). 18:30 – Shuttle leaves hotel for dinner location. 19:00-21:00 – Dinner at Galvin’s Restaurant in Park Lane Hilton Hotel 21:00 – Shuttle returns to hotel. Friday, 18 July 07:00-09:00: Breakfast at the Fiamma Restaurant in hotel lobby. 09:00-17:00/18:00 – Coordination Group Meeting. The end time of the session will be at the group's discretion. The session will take place in the Viscount room (venue map is available here<http://london50.icann.org/en/venue-map>). 19:00-21:00 – Dinner at Minako restaurant on 23rd floor Saturday, 19 July All day departures. Meeting agenda The first gathering will be an opportunity for the Coordination Group to define and finalize working methods and modes of operation, among other things. The meeting agenda items will be at the Coordination Group's discretion. We invite you to contact us off-list for any specific questions you may have and look forward to seeing you in London next week. Thank you, Best regards - ICANN staff

4 6

Timeline
by Jari Arkko July 16, 2014

July 16, 2014

I thought it would be useful to start discussion of some of the topics that the group needs to deal with. I’m sending you some thoughts on the timeline of events looking forward. This is a rough draft and for discussion purposes only. Please comment! — What is described below reads as one timeline, but it may be important to understand that we actually have multiple parallel efforts: protocol parameters, addresses, and names. These efforts have several points of linkage, but allowing parallel operation is probably a good idea. As a result, the timeline may run at slightly different speeds for the different parts. The NTIA has said that the September 2015 deadline is not firm, and that they could extend contracts and prolong the process beyond that. I do believe, however, that there are several reasons why getting done by then is at least useful if not even necessary. First of all, I think we all need a goal. And open-ended timelines lead to open-ended discussions. Second, people, administrations, political climate, etc. may change. So I think we should work towards September 30, 2015. But of course, we also want a good proposal to go forward. In thinking about what is needed before completion, I think see at least the following tasks: 1. Communities: Communities coming up with plans. 2. Coordination and alignment. This includes possible iteration and even going back to the communities. It also includes, possibly, some acceptance phase with the global community for the assembled plan. For instance, the assembled complete plan should probably be something that the customers of IANA are happy with. In other words, coordination can be lead by the coordination group, but it likely includes a lot of work also in the communities. 3. Test run. We may want to show off that the system can actually run in the proposed way for a while. 4. NTIA evaluation and approval process. The community processes are in my opinion the most important ones, and should involve most of the work. In addition, they tend to run for long times. For instance, the simplest IETF last call would be a month already. We also want to give time to the NTIA to do what they need to do. And we should not optimistically assume that there is no need to adjust and iterate over the initially submitted plans. Which may include some additional time confirming with various communities that changes are OK. I’m a little unclear how much testing/demonstration we need. Arguably, the IETF probably runs the system it needs already. But there are other parts where some re-organisation and re-thinking is needed. Not really clear to me how much confidence building would be needed for those parts. Does anyone have thoughts on this? In general, I think we should run this process as the much ourselves as possible, and have everything (including criteria fulfilment) very clearly spelled out for the NTIA, rather leaving any substantial work for them. But they’ll still need some time to process. And we might again need to come back and change something. I guess what I’m coming to is trying to get going pretty early, so that we can iterate in later stages. The tasks are obviously overlapping. For instance, the coordination group should do coordination from day 1, by understanding what the communities are doing and pointing out if they are going into conflicting directions or if there are parts that are not being addressed. So here is one possible overall timeline: Step 1: Communities' work - ready by Dec 30, 2014 (6 months) Step 2: Coordination and alignment, including iteration - ready by March 30, 2015 (+3 months) Step 3: Acceptance and communication - ready by May 30, 2015 (+2 months) Step 4: Testing - ready by July 30, 2015 (+ 2 months) Step 5: NTIA evaluation and acceptance - ready by September 30, 2015 (+2 months)

10 18

Rép: Re: Naming the group was RE: scheduling meetings
by jjs July 16, 2014

July 16, 2014

Hi Milton, having just been nominated by the ALAC to the Coordination Grpup, I was late boarding the train on "naming the group". Your advice is to settle for CG "and not spend more time on this". But I want to take up your remark that "TFSI refer(s) to what we are supposed to facilitate, not to the group itself". I see this as an advantage: we would thus designate our target, rather than contemplate our navel. Jean-Jacques. Milton L Mueller <mueller(a)syr.edu> a écrit : > >I think we're all getting way too cute with this. >CG is fine. The list is already named that. Both TSIF and NXER refer to what we are supposed to facilitate but not to the group itself. >Most everyone aware of us knows the context of the CG, so CG will do. >Generally, I believe this is not something we should spend a lot more time on >--MM > >> -----Original Message----- >> From: internal-cg-bounces(a)icann.org [mailto:internal-cg- >> bounces(a)icann.org] On Behalf Of Jari Arkko >> Sent: Monday, July 14, 2014 8:23 AM >> To: Narelle Clark >> Cc: internal-cg(a)icann.org >> Subject: Re: [Internal-cg] Naming the group was RE: scheduling meetings >> >> >> > Something witty and catchy would be good - NXFER anyone? >> >> I agree. That is pretty good. >> >> I also liked TSIF. >> >> Jari > >_______________________________________________ >Internal-cg mailing list >Internal-cg(a)icann.org >https://mm.icann.org/mailman/listinfo/internal-cg

4 3

Mailing list credentials
by Alissa Cooper July 15, 2014

July 15, 2014

Hi Alice, Would it be possible for us to obtain our mailing list passwords so that we can see the list of subscribers and the archive? Thanks, Alissa

2 2