<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jul 16, 2014 at 3:04 PM, Adam Peake <span dir="ltr"><<a href="mailto:ajp@glocom.ac.jp" target="_blank">ajp@glocom.ac.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">for info on the IANA coordination group from an ISOC list </span><a href="https://elists.isoc.org/pipermail/ianaxfer/" style="font-family:arial,sans-serif;font-size:13px" target="_blank">https://elists.isoc.org/pipermail/ianaxfer/</a><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">Again on the issue of GAC seats. GAC does work in regions, five makes sense for them to use to gather/share information. </div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">What's missing in the discussion of stakeholder groups below is that by any standard when we consider multistakeholder arrangements govt are a distinct group. </div>
</div></blockquote><div> </div><div>I agree but what i don't agree on is the fact that you think it is okay to adjust things after we all (including govt as a stakeholder) has earlier agreed on the formation! Perhaps I would have been the first to +1 your valid comment if the formation was still under discussion, but that is not the case. IMO going the route you are suggesting creates un-necessary precedence and starts to put the CG in a decision making position which should be avoided!<br>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:arial,sans-serif;font-size:13px"> In the coordinating group they are being treated as equal to ALAC, ISOC, IETF, IAB (can anyone explain the distinction between these three in this CG context)</div>
</div></blockquote><div><br></div><div>Here comes the number thing....while you may be right (excluding ALAC ofcourse). I think the point for me is not whether they have equal number, the point is that the group has now become "READ ONLY" and changing the number at this point should not be entertained.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:arial,sans-serif;font-size:13px"> and somehow less deserving that ccNSO, GNSO, RIR+NRO (there is no difference, they are one in the same).</div>
</div></blockquote><div><br></div><div>If you ask me, one could still equate ccNSO to GAC and i am sure you will agree that the names(ccNSO+GNSO) and numbers (RIR+NRO) are 2 distinct community.<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Milton, please support five GAC reps on the committee.</div><span class="HOEnZb"><font color="#888888"><div style="font-family:arial,sans-serif;font-size:13px">
<br></div></font></span></div></blockquote><div>-1 <br><br></div><div>Cheers!<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="HOEnZb"><font color="#888888"><div style="font-family:arial,sans-serif;font-size:13px">
</div><div style="font-family:arial,sans-serif;font-size:13px">Adam</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><br></font></span><div class="gmail_quote"><div class="">---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">Narelle Clark</b> <span dir="ltr"><<a href="mailto:narelle@isoc-au.org.au" target="_blank">narelle@isoc-au.org.au</a>></span><br></div><div><div class="h5">
Date: Tue, Jul 15, 2014 at 11:26 PM<br>Subject: [IANAxfer] Fwd: Update from position zero in the NTIA IANA transfer of stewardship<br>To: "<a href="mailto:ianaxfer@elists.isoc.org" target="_blank">ianaxfer@elists.isoc.org</a>" <<a href="mailto:ianaxfer@elists.isoc.org" target="_blank">ianaxfer@elists.isoc.org</a>>, <a href="mailto:Isoc-advisory-council@elists.isoc.org" target="_blank">Isoc-advisory-council@elists.isoc.org</a><br>
<br><br><div dir="ltr"><div>Fwding as promised - for your inputs, also while we get the Connect forum established and consolidate the inputs.<br><br></div>N<br><div><div><br><div class="gmail_quote">---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">Narelle Clark</b> <span dir="ltr"><<a href="mailto:narelle@isoc-au.org.au" target="_blank">narelle@isoc-au.org.au</a>></span><br>Date: Wed, Jul 16, 2014 at 12:04 AM<br>Subject: Update from position zero in the NTIA IANA transfer of stewardship<br>
To: Chapter Delegates <<a href="mailto:chapter-delegates@elists.isoc.org" target="_blank">chapter-delegates@elists.isoc.org</a>><br><br><br><div dir="ltr">[note: NISTCG == NTIA IANA Stewardship Transition Co-ordination Group == CG ]<br>
<div><br></div><div>Evening everyone!<br></div><div><br><div><div><div><div><div><div><div><div><div>Here is an update from me -
I propose to send something fairly similar out to the ianaxfer@isoc and
AC lists. Also there is a new connect group that is being set up. Once I get set up over there.<br><br></div><div>What follows is a mixture of recollections, reflections and ideas from me. We will need to break out (fork) the topics - right now it is late and I don't want to delay this message any further. To give Demi and I some assitance, Sally, Konstantinos and Olaf will be locate and send through the extra information we all need, and help sort this essay (stream of consciousness??) into topics over on Connect.<br>
<br>-------------------8<--------------------------------8<-----------------------8<-----------------------8<-----------
</div><div><br>The Story So Far<br></div>=================<br>So far the NISTCG has had one official
teleconference and there was
fairly strong agreement that we were keen to get going, set out a clear
path forward, and to focus on the essential IANA piece whilst ensuring we categorise the myriad of other
issues appropriately.<br><br>Quite a few people didn't get to the teleconference because appointments haven't been finalised, or it was too short notice. If you look at:<br><a href="https://www.icann.org/resources/pages/coordination-group-2014-06-17-en" target="_blank">https://www.icann.org/resources/pages/coordination-group-2014-06-17-en</a><br>
</div><div>all but the GAC reps are there, but a number have only just joined. More on that further in the message.<br></div><div>
<br>The first real meeting is in London later this week - it will be streamed live, with translations, and many of the group will be there. Demi will, however I will be attending remotely due to work commitments.<br><br>
</div>The IETF reps et al have put together a draft
agenda for the London meeting and CG members have had a chance to comment. That agenda appears at the
bottom of this message. It should go forward fairly unchanged.<br><br>It was agreed the charter and purpose of the group needs real clarity and agreement and soon.<br>
</div><div><br></div>The topic of whether the GAC should get three extra
members was briefly discussed. It seemed to be the case that there is an argument the GAC should get its five
nominees on the basis that should any stakeholder group feel strongly
disenfranchised then in the long term they will also probably disavow
any proposal that consensus was reached. OTOH the group is 27 already,
and arguably its role is coordination, thus two should be adequate. They
will argue that they have five regions and each needs its position put. It can also be argued that there have been discussions aplenty already about
the membership of the group and reopening those would be
counterproductive. ALAC could conceivably put the same argument, as could the RIRs... and then how many do we end up with?<br><br></div><div>A solution could be that the group sticks with the 2 reps for the GAC and give 3 more some sort of elevated observer status, as per EU meetings and other diplomatic forums.<br>
<br></div><div>The timeframe for an effective process has been raised. In
the interests of ideal governance you take as long as it takes.
However, if this all takes too long it will collide with the US
elections and the appetite for change may be lost or worse. Thus the 30
Sept has a lot of merit, but realistically that would need closure by 31
July (or earlier) given contract time frames.</div><div>
<br>-------------------8<--------------------------------8<-----------------------8<-----------------------8<-----------
<br></div><div><br>Reflections for ISOC<br></div>=================<br>There is also the timeframe issue: what process do we - ISOC - want to use to consult with our members/stakeholders?<br></div>
<br></div>Surely what is needed is this type of process:<br><br></div>Definition phase--> Call for proposals--> Consult & Review proposals --> Recommend<br><br></div>Each piece (between the arrows) also has a community review/discussion aspect that runs over each piece in the time frame allotted.<br>
<br>
</div>In parallel the CG should undertake some risk and governance frameworks to provide some extra input and checking.<br><div><br></div><div>Scope and Charter<br>=================<br></div><div>Right now we are in Phase 0 : what is the scope and charter ISOC wants for this group?<br>
<br>Does the CG/NISTCG write proposals? Does it make decisions?<br><br></div><div>What is in scope, and what is out of scope? For what is out of scope, where do those issues go?<br><br></div><div>What is utterly non-negotiable as for scope, and what can be lost?<br>
<br></div><div>I hope we can agree that the essential piece is the ongoing reliable function of IANA - the database - in one complete piece with a set of operational performance parameters. Those things are enough of a task to define.<br>
<br>After that, what should also be considered? <br><br></div><div>Where are the boundaries?<br><br></div><div>The IAB and IETF have started by putting together some really solid proposals. Paul Wilson has written a brilliant piece on the IANA functions:<br>
<a href="http://www.circleid.com/posts/20140713_breaking_it_down_the_iana_transition_in_practical_pieces/" target="_blank">http://www.circleid.com/posts/20140713_breaking_it_down_the_iana_transition_in_practical_pieces/</a><br>
<br></div>
<div>And then there's a great RFC:<br><a href="https://www.rfc-editor.org/rfc/rfc6220.txt" target="_blank">https://www.rfc-editor.org/rfc/rfc6220.txt</a><br></div><div><br></div><div>I'll post through sample charters as they come up, but we can certainly submit proposals!<br>
</div><div><br></div><div><br><br></div><div>THOUGHTS? COMMENTS?<br></div><br><br>-------------------8<--------------------------------8<-----------------------8<-----------------------8<-----------
<br>
<p>Proposed Agenda<br></p>== Day 1 ==<br>9:00 - 9:15<br>Introduction and level-setting.<br>Brief explanation of why we are gathered to meet.<br><br>9:15 - 10:45<br>Introductions.<br>It would be useful to hear from each rep about:<br>
- What group appointed them<br>- What that group does and who participates in it<br>- How that group does its work and what its decision processes are<br>- Whether they are "representing" their groups or participating as individuals in the CG<br>
- How they view their group's work in relation to the coordination group's work<br><br><br>10:45 - 11:00<br>Break.<br><br>11:00 - 12:30<br>Charter of the CG. (IETF)<br>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.<br>
<br>12:30 - 13:30<br>Lunch.<br><br>Continued discussion of charter.<br> <br>13:30 - 15:00<br>Transition
scope and expectations about work in the communities. (IAB) It would be
good to clarify the CG’s understanding of the scope of the work of the
transition, 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.<br>
<br><br>15:00 - 16:15<br>Coordination group participation.<br>Having
hopefully developed some shared understanding of the charter of the CG
and the work expected in the communities, it would be good to verify
that the composition of the CG is suitable for its tasks and to resolve
any outstanding questions concerning group representation in the CG.<br>
<br><br>16:15 - 16:30<br>Break.<br><br>16:30 - 17:30<br>Self-organization.<br>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.<br>
<br><br>17:30 - 18:00<br>Parking lot for items we want to come back to before day 2 or in case we run over time.<br><br><br>== Day 2 ==<br>9:00 - 9:45<br>Parking lot for leftover charter/community work/CG participation discussion items from yesterday.<br>
<br>9:45 - 10:15<br>Internal and external communications needs.<br>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).<br>
<br>10:15 - 10:30<br>Break.<br><br>10:30 - 11:45<br>Secretariat tasks and selection.<br>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.<br>
<br>11:45 - 12:45<br>Lunch.<br><br>Self-organization, continued.<br>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).<br>
<br><br>12:45 - 13:30<br>Complete self-organization.<br><br><br>13:30 - 14:15<br>Timeline. (IETF)<br>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 has provided a
proposal for this.<br>
<br><br>14:15 - 15:00<br>CG meeting/conference call schedule.<br>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.<br>
<br>15:00 - 15:45<br>Parking lot for any item we need to come back to.<br><br>15:45 - 16:00<br>Break.<br><br><br>16:00 - 16:30<br>Parking lot for any item we need to come back to.<br><br>16:30 - 17:00<br>Summary and wrap-up.<br>
<br><br></div><div>best regards<span><font color="#888888"><br><br><br></font></span></div><span><font color="#888888"><div>Narelle<span><font color="#888888"><br clear="all"></font></span></div><span><font color="#888888"><div>
<br>-- <br><div dir="ltr"><br><br>
<br>Narelle Clark<br>President and Board Member<br>Internet Society of Australia<br>ph: 0412 297 043<br>
int ph: <a href="tel:%2B61%20412%20297%20043" value="+61412297043" target="_blank">+61 412 297 043</a><br><a href="mailto:president@isoc-au.org.au" target="_blank">narelle@isoc-au.org.au</a><br><a href="http://www.isoc-au.org.au" target="_blank">www.isoc-au.org.au</a><br>
The Internet is for Everyone!<br>
</div>
</div></font></span></font></span></div><span><font color="#888888">
</font></span></div><span><font color="#888888"><br><br clear="all"><br>-- <br><div dir="ltr"><br><br><br>Narelle Clark<br>President and Board Member<br>Internet Society of Australia<br>ph: 0412 297 043<br>int ph: <a href="tel:%2B61%20412%20297%20043" value="+61412297043" target="_blank">+61 412 297 043</a><br>
<a href="mailto:president@isoc-au.org.au" target="_blank">narelle@isoc-au.org.au</a><br>
<a href="http://www.isoc-au.org.au" target="_blank">www.isoc-au.org.au</a><br>The Internet is for Everyone!<br></div>
</font></span></div></div></div>
<br></div></div><div class="">_______________________________________________<br>
IANAxfer mailing list<br>
<a href="mailto:IANAxfer@elists.isoc.org" target="_blank">IANAxfer@elists.isoc.org</a><br>
<a href="https://elists.isoc.org/mailman/listinfo/ianaxfer" target="_blank">https://elists.isoc.org/mailman/listinfo/ianaxfer</a><br>
<br></div></div><br></div>
</blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">------------------------------------------------------------------------<br><font color="#888888"><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:garamond,serif">
<i><span style="color:rgb(0,102,0)">Seun Ojedeji,<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Federal University Oye-Ekiti<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">web: </span><a href="http://www.fuoye.edu.ng" target="_blank">http://www.fuoye.edu.ng</a><br>
<span style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Mobile: <a value="+2348035233535">+2348035233535</a></span><span style="color:rgb(0,102,0)"></span><br></i><i><span style="color:rgb(0,102,0)">alt email:<a href="http://goog_1872880453" target="_blank"> </a><a href="mailto:seun.ojedeji@fuoye.edu.ng" target="_blank">seun.ojedeji@fuoye.edu.ng</a></span></i><br>
<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The key to understanding is humility - my view !<br></blockquote></blockquote></font><br></div>
</div></div>