- Internal-cg - lists.icann.org

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

Rép: Re: Proposed agenda for July 17-18
by jjs July 15, 2014

July 15, 2014

Hello Alissa, you called for volunteers within our Coordination Group to flesh out our draft agenda, and volunteer to lead the corresponding discussions. Throughout the Transition exercise, proposing viable processes and structures will be of prime importance. Understandably, our draft agenda for London does not identify this as a separate challenge. But I think it must shape all of our work right from the start. I would therefore suggest that on Day 2, from 11:45 to 12:45, we include a discussion on possible types of framework and process, as a replacement for the oversight currently exercised by the USG. Our point of departure must be the 4 criteria laid out by the USG for a transition to be accepted . I'd be prepared to introduce the subject and lead the discussion. Best regards, Jean-Jacques. Alissa Cooper <alissa(a)cooperw.in> a écrit : >I am re-sending the link to the agenda (in .txt and .pdf format) in case >new folks have joined this list over the weekend: > >https://www.alissacooper.com/files/iana/ > > >If you are willing to lead any of the agenda sessions, and particularly if >you’re willing to contribute a proposal for any of the sessions and use >that to structure the discussion, please make that known on the list or by >replying to me directly. I have started reaching out to some of you >individually about leading various sessions and will continue to do so if >we don’t have enough volunteers. > >Best, >Alissa > > >On 7/11/14, 4:11 PM, "Alissa Cooper" <alissa(a)cooperw.in> wrote: > >>I have updated the agenda (attached) based on our call yesterday. Note >>that Day 2 now concludes at 5pm rather than 4:30pm. >> >>For a few of the sessions I put “(IETF)” or “(IAB)” in parentheses where I >>know we are working on proposals and may be able to lead those sessions. >>If you are willing to lead any of the agenda sessions, and particularly if >>you’re willing to contribute a proposal for any of the sessions and use >>that to structure the discussion, please make that known on the list or by >>replying to me directly. I will probably reach out to some of you >>individually about leading various sessions if we don’t have enough >>volunteers. >> >>It would probably be good to publish at least a rough agenda publicly on >>our various mailing lists prior to the meeting so that people watching >>remotely can follow along. Let’s aim to do that by, say, 20:00 UTC. >> >>And please keep the comments/suggestions coming on the agenda. >> >>Alissa >> >>On 7/9/14, 2:04 AM, "WUKnoben" <wolf-ulrich.knoben(a)t-online.de> wrote: >> >>>Thanks Alice and Alissa for preparing the meeting. I'm one of the GNSO >>>appointees and loaded with more than 30 years of experience from the >>>telco >>>sector. My former employer was Deutsche Telekom, and I'm now working for >>>eco, the German internet business association. >>> >>>Easy for me to be in London on time. Looking forward to meet you all >>>there >>> >>> >>>Best regards >>> >>>Wolf-Ulrich Knoben >>> >>>-----Ursprüngliche Nachricht----- >>>From: Alissa Cooper >>>Sent: Wednesday, July 09, 2014 12:19 AM >>>To: internal-cg(a)icann.org >>>Subject: [Internal-cg] Proposed agenda for July 17-18 >>> >>>Hi all, >>> >>>Looking forward to working with you on this important effort. I think I >>>know most of you, but for those who I do not: I’m Alissa Cooper, one of >>>the IETF appointees. I work for Cisco on collaboration technologies >>>(voice, WebEx, video conferencing). I’m currently one of the IETF’s 15 >>>area directors. I’m based in California. >>> >>>I’ve attached a proposed agenda for the July 17-18 meeting, developed in >>>discussion with some IETF/IAB colleagues. This is very much a draft so it >>>would be great to get discussion going with comments/edits/criticisms. >>>Since the group will be somewhat large (~30 people), I made each slot a >>>bit on the long side. >>> >>>Best, >>>Alissa >>> >>> >>> >>> >>> >>> >>> >>>_______________________________________________ >>>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

3 2

Introductions
by Daniel Karrenberg July 15, 2014

July 15, 2014

Colleagues, as suggested during our phone call on Thursday here is some background on RSSAC as well as about Liman and myself. The Root Server Systems Advisory Committee has a very narrow charter: https://www.icann.org/resources/pages/charter-2013-07-14-en We recently (re-)organised ourselves according to suggestions from a structural review. The current composition of the committee can be found at https://www.icann.org/resources/pages/rssac-4c-2012-02-25-en We have just established a caucus that will carry out our work. Liman and I have been selected to serve on the coordination group with support from all committee members. I have attached the initial guidance of the committee to us. Our committee is small and communication lines are short. It should be noted however that no-one can speak for the 12 organisations that operate the DNS root name servers. We consider the diversity and independence of these organisations to be an essential element for the stability of the DNS. Our role here is first and foremost to help create a proposal that has the widest support that can practically be achieved. We will work for that first while making sure no harm will come from it, particularly for the root name server operators. I am looking forward to work with all of you to make this happen. Daniel (also for Liman who is enjoying a few holidays) ---- The RSSAC gives the following guidance requested by its representatives in the "NTIA IANA Functions’ Stewardship Transition Coordination Group": The primary objective is to produce a plan that is accepted as widely as practical, maintains IANA functionality and does not reduce the security and stability of the Internet. This plan should, as much as possible, be produced in a bottom-up fashion, based within the groups most closely involved in each of the IANA functions as users or partners. Secondary objectives include: - practical oversight for IANA maintenance of root name server data - operational continuity of IANA - practicality of all oversight arrangements RSSAC wishes to avoid any perception that it is trying to influence the content of the DNS root zone. DNS Root name server operators are publishers but not editors of the zone content. While RSSAC would like to see a result as soon as practical, it is not an objective to achieve this in the shortest possible time; particularly not at the expense of the primary objective of the widest practical support. ---- Lars-Johan Liman I'm a Senior Systems Specialist at Netnod Ineternet Exchange in Stockholm, Sweden - the home of i.root-servers.net, for which I am the technical lead. My bio can be foundin the ICANN Wiki, at http://icannwiki.com/index.php/Lars-Johan_Liman but some highlights include * Early days at the Royal Institute of Technology in Stockholm and its Network Operations Centre. * 25 years of experience in operating large servers and network infrastructure. * Has a keen interest for the operations of public infrastructure systems for the Internet, and especially for the stability thereof. * Has strong feelings for openness and transparency. * Has been involved in international Internet related work for more than 20 years - at all levels, from installing equipment in racks to attending UN conferences. * Likes to make policy and implementation fit together. ---- Daniel Karrenberg is chief scientist at the RIPE NCC, the regional Internet registry for Europe and surrounding areas. He advises on research, creation and piloting of new services as well as general strategy development. A computer scientist by training, Daniel likes to invent, design and implement Internet related systems, especially those collecting and processing data about the Internet itself. He also likes to occasionally inject physics, engineering and "networking style" into debates about Internet governance. Daniel maintains his public bio on linkedin: https://www.linkedin.com/pub/daniel-karrenberg/36/261/742 Ample information about his past sins can be found using your favourite search engine. Following are a few additional keywords you might use, arranged by decade: 1980s: GUUG EUUG EUnet unido mcvax cwi RARE iepg RIPE 1990s: RIPE+NCC rir iana postel terena ebone centr k.root-servers.net 2000s: dnsmon nsd ris internet+society rssac 2010s: ripe+labs ripestat ripe+atlas

1 0

scheduling meetings
by Milton L Mueller July 14, 2014

July 14, 2014

On this agenda item: 14:15 - 15:00 CG meeting/conference call schedule. 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!) Just a thought. MM

8 8

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

July 14, 2014

As the important concepts here are - transfer of STEWARDSHIP, - Iana FUNCTIONS, I would suggest a shortened acronym, TSIF, for "Transfer of Stewardship of the IANA Functions". Jean-Jacques. Xiaodong Lee <xl(a)cnnic.cn> a écrit : > >IANA Stewardship Transition Co-ordination Group might be better > > >Xiaodong Lee > >> >>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. >>> >> >>_______________________________________________ >>Internal-cg mailing list

1 0

Re: [Internal-cg] Welcome to the "Internal-cg" mailing list
by Mary Uduma July 12, 2014

July 12, 2014

Test Mary Uduma On Saturday, July 12, 2014 2:22 PM, "internal-cg-request(a)icann.org" <internal-cg-request(a)icann.org> wrote: Welcome to the Internal-cg(a)icann.org mailing list! To post to this list, send your email to: internal-cg(a)icann.org General information about the mailing list is at: https://mm.icann.org/mailman/listinfo/internal-cg If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: https://mm.icann.org/mailman/options/internal-cg/mnuduma%40yahoo.com You can also make such adjustments via email by sending a message to: Internal-cg-request(a)icann.org with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is: beawdibi Normally, Mailman will remind you of your icann.org mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you.

1 0

Re: [Internal-cg] scheduling meetings
by James M. Bladel July 12, 2014

July 12, 2014

Agree with this. There is significant overlap between the membership of this group, ICANN, and other IG events (IGF, PP14, etc.) Synchronizing meeting calendars may also cut down on travel & meeting expenses, personal or ICANN. Thanks‹ J. On 7/12/14, 10:32 , "Milton L Mueller" <mueller(a)syr.edu> wrote: >On this agenda item: >14:15 - 15:00 CG meeting/conference call schedule. > >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!) > >Just a thought. > >MM >_______________________________________________ >Internal-cg mailing list >Internal-cg(a)icann.org >https://mm.icann.org/mailman/listinfo/internal-cg

1 0

Notification that the IANA transition mailing list has been reopened in response to community feedback
by Ergys Ramaj July 11, 2014

July 11, 2014

?Dear all, This is to inform you that the ianatransition(a)icann.org<mailto:ianatransition@icann.org> mailing list has been reopened in response to community feedback. Please see below for a note from Theresa Swinehart, also accessible here<mailto:http://discuss-stewardship.icann.org/t/reopening-ianatransition-ican…>. --- All, Thank you for your raising some important issues in relation to the migration of the IANA Transition mailing list to a web forum. We were trying to serve the broadest community we could as efficiently, transparently and as accessibly as we could, but recognize that the migration raised some concerns, which was not at all the intention, and I apologize for this. To address the feedback we have received, we are reinstating the mailing list and we are looking into the points raised around the terms of service. Further we apologize for instituting the previous changes without discussion or further feedback. While we are restoring the mailing list, there was - and still is - a purpose in setting up the forum, and though it's after the fact, it's nonetheless appropriate to share with you what motivated the change. We had input that some prospective participants are uncomfortable using email lists. We also had input that many people wanted additional functionality or different ways to manage communications. Specifically, the migration sought to provide a tool to those also less familiar with using only email lists. The forum was set up to provide the functionality expected from a mailing list, including that participants can send and receive posts via email just like the mailing list. It also some additional aspects some may find easier to manage via, including: * ??Ability to choose what they want to see (rather than have to set up email rules to filter out what they don^1t want). They can mute or follow specific threads; * Ability to sign up for digests (full or topic specific) on a schedule of their choosing; * Ability for search engines to search posts; * Ability to view and respond to specific topics; * Ability for participants to identify the most valuable contributions by liking them; * It can be easier for some less familiar with email lists to see new topics and to navigate to different topics; * Questions can be made and answered and referred to, saving repetition; * Future options include such as user selectable machine translation of posts, thereby allowing multiple language participation in the same discussion, without the conversation fragmenting by language or locality. We appreciate that a forum only option raised other concerns, including many don't like to use discussion forums or manage communications that way. Given the interests expressed to retain the mailing list it will be reopened shortly. Thank you again for your continued feedback and suggestions for improvements, they are important to continue to improve the mechanisms and engagement in these important discussions. Kind regards, Theresa

1 0

Re: [Internal-cg] Conference call?
by Narelle Clark July 10, 2014

July 10, 2014

Am on the call however in a noisy airport lounge. Narelle -- Narelle Clark Director of Operations - Deputy CEO Australian Communications Consumer Action Network Suite 402 Level 4, 55 Mountain St Ultimo NSW 2007 Ph: 02 9288 4000 Direct: 02 9288 4007 Fax: 02 9288 4019 TTY: 02 9281 5322 "Lynn St.Amour" <Lynn(a)lstamour.org> wrote: Hi Milton, a note came in yesterday - from Alice Jansen included here: Begin forwarded message: > From: Alice Jansen <alice.jansen(a)icann.org> > Subject: [Internal-cg] Coordination Group Call 01 - Thurs, 10 July - 20:00-21:00 UTC > Date: July 9, 2014 5:37:19 PM EDT > To: "internal-cg(a)icann.org" <internal-cg(a)icann.org> > > When: Thursday, July 10, 2014 8:00 PM-9:00 PM. Coordinated Universal Time > Where: Conference ID – 92957255 - Dial-in numbers: http://adigo.com/icann/ > > *~*~*~*~*~*~*~*~*~* > **Thursday, 10 July 2014** > 20:00-21:00 UTC > Timezone converter: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Coordination+Group… > > > Bridge details: > Dial in Numbers - http://adigo.com/icann/ > Conference ID – 92957255 > > Should you need a dial-out for this call, please contact ICANN staff. > The call will be recorded. > On Jul 10, 2014, at 3:16 PM, Milton L Mueller <mueller(a)syr.edu> wrote: > As far as I can tell no one has told us the call-in information for the CG conference call that is supposed to happen in about 45 minutes. > > > > > From: internal-cg-bounces(a)icann.org [mailto:internal-cg-bounces@icann.org] On Behalf Of joseph alhadeff > Sent: Thursday, July 10, 2014 1:13 PM > To: internal-cg(a)icann.org > Subject: Re: [Internal-cg] Timeline > > Colleagues: > > Perhaps the first step is a publication and comment on our operational processes, objectives and input methodology, including consultation mechanisms for those of us representing constituencies. That might give people some comfort in relation to the transparency of our own group's operation? This is likely implied in 1 and 2, but I think we should be more explicit. I understand that this may be more relevant to work other than our own, but issues of optics and comfort with the fairness, inclusiveness and transparency of the process have been huge issues as of late in IG discussions... > > Joe > > On 7/10/2014 1:00 PM, Jari Arkko wrote: > 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) > > > > > _______________________________________________ > 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

2 1

Conference call
by Narelle Clark July 10, 2014

July 10, 2014

I will join in 10-15mins N -- Narelle Clark Director of Operations - Deputy CEO Australian Communications Consumer Action Network Suite 402 Level 4, 55 Mountain St Ultimo NSW 2007 Ph: 02 9288 4000 Direct: 02 9288 4007 Fax: 02 9288 4019 TTY: 02 9281 5322 Milton L Mueller <mueller(a)syr.edu> wrote: As far as I can tell no one has told us the call-in information for the CG conference call that is supposed to happen in about 45 minutes. From: internal-cg-bounces(a)icann.org [mailto:internal-cg-bounces@icann.org] On Behalf Of joseph alhadeff Sent: Thursday, July 10, 2014 1:13 PM To: internal-cg(a)icann.org Subject: Re: [Internal-cg] Timeline Colleagues: Perhaps the first step is a publication and comment on our operational processes, objectives and input methodology, including consultation mechanisms for those of us representing constituencies. That might give people some comfort in relation to the transparency of our own group's operation? This is likely implied in 1 and 2, but I think we should be more explicit. I understand that this may be more relevant to work other than our own, but issues of optics and comfort with the fairness, inclusiveness and transparency of the process have been huge issues as of late in IG discussions... Joe On 7/10/2014 1:00 PM, Jari Arkko wrote: 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) _______________________________________________ Internal-cg mailing list Internal-cg(a)icann.org<mailto:Internal-cg@icann.org> https://mm.icann.org/mailman/listinfo/internal-cg

1 0

Conference call?
by Milton L Mueller July 10, 2014

July 10, 2014

As far as I can tell no one has told us the call-in information for the CG conference call that is supposed to happen in about 45 minutes. From: internal-cg-bounces(a)icann.org [mailto:internal-cg-bounces@icann.org] On Behalf Of joseph alhadeff Sent: Thursday, July 10, 2014 1:13 PM To: internal-cg(a)icann.org Subject: Re: [Internal-cg] Timeline Colleagues: Perhaps the first step is a publication and comment on our operational processes, objectives and input methodology, including consultation mechanisms for those of us representing constituencies. That might give people some comfort in relation to the transparency of our own group's operation? This is likely implied in 1 and 2, but I think we should be more explicit. I understand that this may be more relevant to work other than our own, but issues of optics and comfort with the fairness, inclusiveness and transparency of the process have been huge issues as of late in IG discussions... Joe On 7/10/2014 1:00 PM, Jari Arkko wrote: 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) _______________________________________________ Internal-cg mailing list Internal-cg(a)icann.org<mailto:Internal-cg@icann.org> https://mm.icann.org/mailman/listinfo/internal-cg

3 3

Fwd: Timeline
by Patrik Fältström July 10, 2014

July 10, 2014

By accident a few messages ended up being fork:ed out from the mailing list. Here they are (with approval by the involved parties). Patrik Begin forwarded message: > From: Patrik Fältström <paf(a)frobbit.se> > Subject: Re: [Internal-cg] Timeline > Date: 10 July 2014 19:28:02 +0200 > To: Jari Arkko <jari.arkko(a)piuha.net> > Cc: joseph alhadeff <joseph.alhadeff(a)oracle.com>, Alissa Cooper <alissa(a)cooperw.in> > > I have the same view, or similar, as Jari. > > I think the primary goal MUST be the transition. Not accountability or otherwise changes of ICANN or something else. > > That said, when looking at the transition, there might be implications that for example changes might be "wanted" in the PDP that ICANN runs for ccTLDs. The tricky part will then be to identify which ones of those changes are actual show stoppers for the transition, and what are things that can be put on hold and be done in parallell to the transition. > > Because of this, I find it be extremely important to have consensus in the group that the coordination group must have as a goal to answer the quite well defined scope that is given to it, and nothing more. If nothing else, the current contract between NTIA and ICANN can and should be the scope. > > Patrik > > On 10 Jul 2014, at 19:10, Jari Arkko <jari.arkko(a)piuha.net> wrote: > >> Hi Joe, >> >> (Adding Alissa and Patrik who I think both might have views on this.) >> >> My answer: We do not yet have such a delineation. >> >> We need to come up with our own scope definition. >> >> My personal favourite scope is to divide it to the communities/customers and say, “do whatever you think is necessary for the NTIA stewardship to transfer to the community”. The answers on accountability might differ between names and protocol numbers, for instance. We at the IETF already have contracts and the usual escalation procedures to deal with non-performance/failure of IANA, for instance. And ICANN isn’t responsible for protocol parameters policies, so it might be that we do not need so much from the ICANN accountability process. But that is definitely not the case for names. >> >> Jari >> >> On 10 Jul 2014, at 20:04, joseph alhadeff <joseph.alhadeff(a)oracle.com> wrote: >> >>> Jari: >>> >>> Is there a delineation of mandates and any proposal for coordination between the accountability work and our work? There could be areas of overlap... >>> >>> Joe >>> On 7/10/2014 1:00 PM, Jari Arkko wrote: >>>> 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) >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Internal-cg mailing list >>>> >>>> Internal-cg(a)icann.org >>>> https://mm.icann.org/mailman/listinfo/internal-cg >>> >> >

1 0

Liman unable to make it to London.
by Lars-Johan Liman July 10, 2014

July 10, 2014

Just FYI, Unfortunately I will be unable to attend the meeting in London. It came about on short notice, and I have other committments already booked. RSSAC will still be represented by Daniel Karrenberg. My regrets, /Lars-Johan Liman RSSAC representative #---------------------------------------------------------------------- # Lars-Johan Liman, M.Sc. ! E-mail: liman(a)netnod.se # Senior Systems Specialist ! Tel: +46 8 - 562 860 12 # Netnod Internet Exchange, Stockholm ! http://www.netnod.se/ #----------------------------------------------------------------------

1 0

Coordination Group Call 01 - Thurs, 10 July - 20:00-21:00 UTC
by Alice Jansen July 9, 2014

July 9, 2014

When: Thursday, July 10, 2014 8:00 PM-9:00 PM. Coordinated Universal Time Where: Conference ID – 92957255 - Dial-in numbers: http://adigo.com/icann/ *~*~*~*~*~*~*~*~*~* **Thursday, 10 July 2014** 20:00-21:00 UTC Timezone converter: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Coordination+Group… Bridge details: Dial in Numbers - http://adigo.com/icann/ Conference ID – 92957255 Should you need a dial-out for this call, please contact ICANN staff. The call will be recorded. On 7/9/14 9:40 PM, "Jari Arkko" <jari.arkko(a)piuha.net<mailto:jari.arkko@piuha.net>> wrote: Thanks for responding to the poll. It is pretty obvious that the Thursday option for the call is most popular. Lets have it at that time. The time is tomorrow Thursday, July 10th. 13:00 Pacific 16:00 Easter 22:00 Central Europe 23:00 East Europe 06:00 Brisbane (for this timezone, the date is Friday, July 11th) I will ask for a bridge to be set up. I believe we should be done well within an hour. In the interest of transparency and openness, I’d like to make minutes and a recording of the call to be publicly available. Let me know if there are any concerns. Jari

1 0