== Day 1 == 9:00 - 9:15 Introduction and level-setting. Brief explanation of why we are gathered to meet. 9:15 - 10:45 Introductions. It would be useful to hear from each rep about their approaches to the work in the coordination group. For instance, what are reps' relationships to their own constituencies, are they "representing" those constituencies ("I speak for XYZ org") or are they designees expressing their own positions, and how do they see their community’s work in relation to the coordination group’s work? 10:45 - 11:00 Break. 11:00 - 12:30 Charter of the CG. It would be good to obtain a shared understanding in the whole group of the role and charter of the CG. Charter proposals circulated in advance of July 17 would help here -- on the IETF/IAB side we may be able to work one up based on the IAB's April 29 comments. 12:30 - 13:30 Lunch. Continued discussion of charter. 13:30 - 15:00 Expectations about work in the communities. It would be good to clarify the CG’s expectations about what the community processes need to produce and where/how areas of overlap will be handled. We will want to communicate this publicly if we get agreement on it. 15:00 - 16:00 Timeline. It would be good to get some agreement about the drop-dead date for the final proposal to be submitted to NTIA (assuming they need some lead time to review it and socialize it within the USG before the contract actually expires). We can then work backwards from there and set goals for when it would be good to have the community discussions come to a close. As with the charter, it would be helpful for someone to come up with a proposal for this in advance of the meeting. Jari is working on a proposal for this. 16:00 - 16:15 Break. 16:15 - 17:15 Self-organization. Initial discussion about how the CG wants to organize itself, e.g., do we want a chair and/or vice-chair, do we need to form sub-groups for any particular tasks, how will we select people for these things. I think it would be good to talk about this on the first day and try to come to some conclusions, and then make the decisions on the second day. If people know they would like to serve in a particular role, they could make that known to the group. 17:15 - 18:00 Parking lot for items we want to come back to before day 2 or in case we run over time. == Day 2 == 9:00 - 9:30 Parking lot for leftover charter/community work discussion items from yesterday. 10:00 - 10:30 Internal and external communications needs. Whether the CG needs public and/or private mailing lists for its own work, whether we should stand up our own web site, where that site should be hosted, what we would use the web site for, what we think about ICANN’s web-based platform and whether it should continue to exist and/or be replaced by other list(s). 10:30 - 10:45 Break. 10:45 - 12:15 Secretariat tasks and selection. ICANN will be selecting an independent secretariat for the CG. To make this selection, they will need an RFP. So the CG needs to agree on what the secretariat's responsibilities will be, and possibly needs to come up with that RFP (or work on it together with ICANN). Again having a draft RFP going into the meeting might be a useful thing. 12:15 - 13:15 Lunch. Self-organization, continued. If we're ready by this point, we could solicit candidates for chair/vice chair/whatever other positions we think we need and hear from them each briefly about what they would bring to the role(s). 13:15 - 14:00 Complete self-organization. 14:00 - 15:00 CG meeting/conference call schedule. We need to figure out how often we'd like to have calls and when our face-to-face meetings will be. This would be another good item to have a proposal for in advance. 15:00 - 15:45 Parking lot for any item we need to come back to. 15:45 - 16:00 Break. 16:00 - 16:30 Summary and wrap-up. Ending a bit earlier than Day 1 assuming some folks will be departing in the evening.