i'm in.
mikey
On Nov 27, 2013, at 10:51 AM, "Jonathan Robinson" <jrobinson@afilias.info> wrote:Great to have this level of engagement on a topic!A couple of points on status:1. The issue arises formally from a recommendation of ATRT 1 i.e. that theGAC should engage earlier with the GNSO PDP.2. My interpretation is:a) that it is intended that this engagement / input should be such that when(and if) the GAC does provide Advice (to the Board), it is at least notunexpected and, at best, consistent with GNSO policy / policy advice.Andb) that the GAC's input (to the GNSO policy work) should be focussedprimarily on the potential (or actual) public policy implications of thecorresponding GNSO policy work.Of course, the devil is in both the detail and the expectations of theformat of and response to the input of the GAC. That is what the table thatMarika sent around attempts to start to flesh out.And, therefore, the scope of the joint team to try to make progress on.I received an update today from Manal which suggests that the GAC mayparticipate with as many as 6 participants. In which case, it seems to me,that we need a balanced number of participants.Should that be the case, some of you on this thread may wish to volunteer toparticipate.To set expectations, I am anticipating that we'll have a mailing list andregular calls (say 2 weekly), not dissimilar to a GNSO working group.Jonathan-----Original Message-----From: Amr Elsadr [mailto:aelsadr@egyptig.org]Sent: 26 November 2013 17:53To: Mary WongCc: Council GNSOSubject: Re: [council] Final GAC communiqueInteresting. Thanks Mary.AmrOn Nov 26, 2013, at 6:43 PM, Mary Wong <mary.wong@icann.org> wrote:For the benefit of some of the newer participants among us and theGNSO community - note that even when GAC members participate in WGs,they do not do so as representatives of the GAC, or even their owncountries, though they may of course be able to inform the WG ofeither the GAC's position (if there is one) on the issue at hand. TheGAC has been very firm about this, and it may partly have to do withhow GAC consensus is achieved - as in other multi-lateral forums,"consensus" is reached if there is no objection by a GAC member to aparticular position.Conversely, if just one GAC member objects to a particular position,there is therefore no consensus. This is of course different from howGNSO PDPs and WGs work.As Marika has mentioned, this discussion could be helpful to the smallgroup from the GNSO that will be discussing methods of earlyengagement with/from the GAC, mindful of Thomas' distinction betweenGAC Advice (as conceived in the ICANN Bylaws) and GAC input.CheersMaryMary WongSenior Policy DirectorInternet Corporation for Assigned Names & Numbers (ICANN)Telephone: +1 603 574 4892Email: mary.wong@icann.org* One World. One Internet. *-----Original Message-----From: Amr Elsadr <aelsadr@egyptig.org>Date: Tuesday, November 26, 2013 12:18 PMTo: Council GNSO <council@gnso.icann.org>Subject: Re: [council] Final GAC communiqueHi all,Thanks for the clarification Thomas. It makes a lot of sense to bewary of what kind of early engagement we¹d like to encourage from theGAC, and I don¹t find it surprising that there seems to be a generalsense of agreement here on how this should be done.I, like others, feel it would be great to have more GACrepresentatives become involved in PDP WGs, but cannot confidentlypredict how this would affect the GAC reaction at-large. I am notfamiliar with how the GAC collectively reaches a position on PDPoutcomes. I wouldn't be surprised to learn that these positions areprepared by only a handful of their members. If anyone else hasinsights on how this is done, I¹d appreciate it if you shared.Like Chuck said, we do have two GAC reps on the policy andimplementation WG, but this is not a PDP WG. And unless I am mistaken(and please correct me if I¹m wrong on this Chuck), theirparticipation both during calls and on-list is quite limited. I bringthis up because encouraging GAC members to join WGs is one thing, andencouraging them to actively engage in the consensus development ofpolicy recommendations is another.I hope we can encourage them to do both. I am curious to see howinteraction at this level (the WG level) might affect GAC Advice(capitalA) and their collective perception of the necessity and manner ofearly engagement.Thanks.AmrOn Nov 26, 2013, at 5:30 PM, Mike O'Connor <mike@haven2.com> wrote:ah!*very* helpful. thanks Thomas for taking the time to craft that reply.and thanks to John for picking up how i misunderstood the core ofThomas' argument.i agree with you that capital-A advice would indeed be complicatedfor a WG to handle, given that the goal of WG discussion is toarrive at positions that are usually different from the startingpoints of each participant.does Berry's contribution to this thread (describing USG commentsduring a comment period) provide an avenue for slightly-less-firminput from the GAC, or GAC members? while WG's are not required toincorporate comments into their final positions, they ARE requiredto respond to each comment -- which might provide an avenue for dialog.focusing on developing that approach might lead us to a good middleground between the WG's need for flexibility/negotiation and theGAC's need for structure and due deliberation.mOn Nov 26, 2013, at 10:14 AM, Thomas Rickert <rickert@anwaelte.de>wrote:John, Mikey and Chuck,to start with, I am not against early GAC input and you willremember that I have encouraged that the GAC or individual GAmembers get involved at the earliest possible date. Let me quotefrom my earlier e-mail where I explicitly stated that:The GAC should engage early so that PDP WGs get an indication asto what the GAC or even individual GAC member's thinking is.This is valuable and will help a lot.What we should discuss, though, is whether GAC Advice (capitalletterA) should be directed at PDP WGs during a PDP or at the G-Council.Bear in mind, I spoke about GAC Advice and not about GAC input.My hesitation with respect to GAC Advice during a PDP stems fromthe following considerations:- The term GAC Advice has legal implications. At the moment GACAdvice is only directed at the Board and the Board can onlydisregard GAC Advice under certain circumstances.- If GAC Advice were also directed at PDP WGs, would or shouldthat be a second opportunity for the GAC to give Advice (capitalA)? If so, what would be the consequences of that?- Could the WG disregard GAC Advice? If so, what would give the WGauthority to do so? PDP WGs work on recommendations to be made tothe Council, but I do not see that it has the legal authority tomake binding decisions on behalf of the GNSO or even ICANN, while,in fact, responding to GAC Advice in one way or the other would beor would be seen as acting on behalf of ICANN.- If the WG followed GAC Advice, would that bind the Board at alater stage so the Board looses the right to disregard it?- Either way PDP WGs are tasked to work and I am not sure we shouldburden their work with issues that might have far-reachingpolitical implications for the whole community.- Comparable issues would arise if GAC Advice would be directed atthe G-Council.Again, I very much in favor of GAC early engagement and thediscussion that we have here should not dilute that. Even more, GACearly engagement can help avoid friction between the GAC'sexpectations and the communities work product at a later stage andmaybe avoid the necessity for GAC Advice to the Board.What I am asking for is that we carefully consider the consequencesof GAC input if such input took the format of GAC Advice for thereasons above.Thanks,ThomasAm 26.11.2013 um 12:36 schrieb John Berard <john@crediblecontext.com>:Thomas,Can you confirm you were arguing against early GAC input?BerardSent from my iPhoneOn Nov 26, 2013, at 10:25 AM, "Mike O'Connor" <mike@haven2.com>wrote:hi all,i lean in Chuck's direction with regard to WG participation. idon't have the history/knowledge to comment on the relationshipbetween Board/GAC/GNSO-Council...as i've come to know the WG process over the years, i've foundthat it works better when there are more inputs rather thanfewer. that doesn't mean that it's easier, only that the results aremore robust.i've always hoped for more participation by members of the GACand am keen to find ways that they could do that.i also agree with Chuck that earlier participation is a great thing.much like any project, the sooner we can get help figuring outthe gaps in our thinking, or the reasons why a given direction isto be desired, the easier it is to get on the right track. andthe less backtracking/repair/recovery we need to do later on.often people don't really mind changing the direction aconversation is going if it resolves a divergence -- but when thejourney is nearly done, WG members are weary and the road to thenew place is long, sometimes participants get frustrated andresist the change just because it's hard to get from here to there.these thoughts don't just apply to the GAC, but any point of viewthat needs to be expressed in a WG. more voices is good.earlier is good.like Chuck, i'm willing to be persuaded. :-)mikeyOn Nov 26, 2013, at 8:12 AM, "Gomes, Chuck"<cgomes@verisign.com>wrote:Thomas,Please see my responses below.Chuck-----Original Message-----From: Thomas Rickert [mailto:rickert@anwaelte.de]Sent: Sunday, November 24, 2013 5:45 PMTo: Gomes, ChuckCc: Avri Doria; Council GNSOSubject: Re: [council] Final GAC communiqueHi Avri and Chuck,in my view, we should have a discussion on our expectations sometime soon.Other than Avri, I do think that the GAC could engage early and/ or acknowledge the role and work products of the GNSO and atthe same time only consider the Board as its equal.[Chuck Gomes] I think the Bylaws should be changed so the GAC isencouraged to provide input to WGs as early as possible likethey did with the IGO-INGO PDP WG, albeit via the Board. Ipersonally think that the language in the Bylaws that says thatthe GAC should be complemented with language that says they alsogive advice to policy WGs that involve public policy issues.The excuse that they are just advisors to the Board should beremoved.During the GAC/GNSO session it was mentioned that the GAC stillneeds to consider when to give advice during a GNSO policydevelopment process and I am not sure we really want GAC Advicedirected at the G-Council or even at the WG level.[Chuck Gomes] Why not?The GAC should engage early so that PDP WGs get an indication asto what the GAC or even individual GAC member's thinking is.This is valuable and will help a lot. I would not like to seespecial rights for the GAC to be implemented. In that regard, itdoes not harm if the GAC sees the Board as the group to directadvice at.[Chuck Gomes] As you can see by my earlier comments, I disagreebut am open to being convinced otherwise.We should discuss this further - maybe in one of the upcomingtelcos.[Chuck Gomes] I am open to discussion but remember that I amonly a temporary alternate on the Council and probably will notbe on any more Council calls.Thanks,ThomasAm 22.11.2013 um 18:09 schrieb "Gomes, Chuck"<cgomes@verisign.com>:Note that we have two GAC participants in the Policy &Implementation (P&I) WG. We suggested in our letter to the GACthat they might be able to serve in some sort of unofficialliaison capacity if the GAC was okay with that, notrepresenting the GAC but being communication channels.Chuck-----Original Message-----From: owner-council@gnso.icann.org[mailto:owner-council@gnso.icann.org] On Behalf Of Avri DoriaSent: Friday, November 22, 2013 12:13 PMTo: Council GNSOSubject: Re: [council] Final GAC communiqueHi,I do not think this should surprise us. And I mean thedisrespect the GAC has for any structure lower than the Board.For them to acknowledge our work would be for them toacknowledge that we have a role on a par with theirs. Andgovernments never admit to being equal to any one else - onlyin the IGF have we seem some loosening of that in the generalInternet governance arena. I expect that they really do notconsider the Board their equals, but they put up with the thingsthey need to put up with.They had a liaison with the Council in the past, butparticipation limited them and limited their ability to giveadvise that took no account of the work done in the GNSO.Early engagement is contradictory to reinforcing the power oftheir advice - which is their ultimate goal.I think we should continue to invite and encourage them toparticipate. Sooner or later one of them will take usseriously again - we have had some WG participants from GAC inthe past, we may again some day. But we should also not foolourselves into expecting them to take any supportive notice of ourefforts.I have every respect for those of you doing the essential workon improving coordination between GAC and the GNSO, as I expectyour main reward will be knowing you tried, as opposed to anyreal GAC early engagement. Hope I am wrong.avriOn 21 Nov 2013, at 18:00, Thomas Rickert wrote:Nonetheless it is sad and I will say that I find itinteresting to show respect to the GNSO's PDP work by workingon ways to engage and then completely ignore work that is donein PDPs which is relevant to what they are deliberating.ThomasAm 21.11.2013 um 17:17 schrieb "Gomes, Chuck"<cgomes@verisign.com>:Remember that they never thought we should be considering this.:(Chuck-----Original Message-----From: owner-council@gnso.icann.org[mailto:owner-council@gnso.icann.org] On Behalf Of ThomasRickertSent: Thursday, November 21, 2013 3:11 PMTo: Glen de Saint GéryCc: council@gnso.icann.orgSubject: Re: [council] Final GAC communiqueAll,sadly, the GAC communique includes Advise on IGO/INGOs, butdoes not mention the GNSO's PDP WG or the motion that passed.Thomas=============thomas-rickert.tel+49.228.74.898.0Am 21.11.2013 um 16:57 schrieb Glen de Saint Géry<Glen@icann.org>:FYIAttached please find the finalised GAC communique fromBuenos Aires.The communique will be posted on the GAC Website later today.Glen de Saint GéryGNSO Secretariatgnso.secretariat@gnso.icann.org http://gnso.icann.org<FINAL_Buenos_Aires_GAC_Communique_20131120.pdf>_______________________________________________gac mailing listgac@gac.icann.orghttps://mm.icann.org/mailman/listinfo/gacPHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE:OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE:OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)
PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)