[NCSG-PC] Fwd: Request for NSCG endorsement -- GNSO Liaison to the GAC
Dr. Tatiana Tropina
t.tropina at mpicc.de
Sat Sep 9 14:04:25 EEST 2017
Hi Ayden,
thanks a lot. It seems that endorsing all three but proposing the
preferred order is the best way.
All: I personally would rather put Julf as number one, but I am fine
with Ayden's proposed order if everyone goes for this.
Cheers,
Tanya
On 09/09/17 12:58, Ayden Férdeline wrote:
> Hi Rafik,
>
> As we did not include a hard deadline in the email on Thursday, I
> suppose Pascal did submit his request for endorsement on time [at
> least by UTC timezone]. For that reason I support us endorsing his
> application.
>
> However, if it would help the SSC in their deliberations, I would
> propose that the preferred order of candidates from the NCSG be as
> follows:
>
> 1. Paul Rosenzweig
> 2. Julf Helsingius
> 3. Pascal Bekono
>
> Best wishes, Ayden
>
>
>
>
>> -------- Original Message --------
>> Subject: Re: [NCSG-PC] Fwd: Request for NSCG endorsement -- GNSO
>> Liaison to the GAC
>> Local Time: 8 September 2017 11:18 PM
>> UTC Time: 8 September 2017 22:18
>> From: rafik.dammak at gmail.com
>> To: Dr. Tatiana Tropina <t.tropina at mpicc.de>
>> ncsg-pc <ncsg-pc at lists.ncsg.is>
>>
>> Hi,
>>
>> Thanks, I see we have support to send the 2 names as endorsed to SSC.
>> We got an extra application lately and not sure that everyone has
>> time to review it.
>> there is no limit to send 3 names. however, I think that sending many
>> names will weaken their chances of those candidatures at SSC
>> deliberation since as Stakeholder group we are not championing
>> clearly for one. that won't make NCSG representatives to SSC easier
>> either give them a clear guidance from their group.
>>
>> for now, I will send Julf and Paul applications by the deadline. if
>> other PC members weigh in and also support sending Pascal application
>> in coming hours, we can submit hs endorsment afterward.
>>
>> Best,
>>
>> Rafik
>>
>> 2017-09-09 3:04 GMT+09:00 Dr. Tatiana Tropina <t.tropina at mpicc.de
>> <mailto:t.tropina at mpicc.de>>:
>>
>> Hi Rafik and all,
>>
>> I support.
>>
>> Cheers,
>>
>> Tanya
>>
>>
>> On 08/09/17 14:28, Rafik Dammak wrote:
>>> Hi,
>>>
>>> due to the time constraint and since we have 2 candidates, we
>>> can endorse both and send their applications to SSC. if there is
>>> no objection, I can submit them just before 23:59UTC.
>>> looking to hear from other PC members.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> 2017-09-08 16:50 GMT+09:00 Ayden Férdeline <icann at ferdeline.com
>>> <mailto:icann at ferdeline.com>>:
>>>
>>> Hi,
>>>
>>> I propose endorsing both. We are only asked, I believe, to
>>> support their candidacies — we have not been delegated the
>>> responsibility as PC of selecting the liaison.
>>>
>>> Best wishes,
>>>
>>> Ayden Férdeline
>>> Sent from ProtonMail Mobile
>>>
>>>
>>> On Fri, Sep 8, 2017 at 8:41 am, Arsène Tungali
>>> <arsenebaguma at gmail.com <mailto:arsenebaguma at gmail.com>> wrote:
>>>> So how are we doing this? Do we vote by a formal poll or
>>>> are we just posting on here? ----------------- Arsène
>>>> Tungali, about.me/ArseneTungali
>>>> <http://about.me/ArseneTungali> +243 993810967
>>>> <tel:+243%20993%20810%20967> GPG: 523644A0 Goma, Democratic
>>>> Republic of Congo Sent from my iPhone (excuse typos) > On
>>>> Sep 8, 2017, at 7:15 AM, Tapani Tarvainen wrote: > >
>>>> Re-sending with the attachment. > > Tapani > > -----
>>>> Forwarded message from Paul Rosenzweig ----- > > Dear
>>>> Tapani (and Farzaneh as incoming Chair) > > I am writing to
>>>> request that you consider endorsing me to be the GNSO >
>>>> Liaison to the GAC. My current SOI is here: >
>>>> https://community.icann.org/display/gnsosoi/Paul+Rosenzweig+SOI
>>>> <https://community.icann.org/display/gnsosoi/Paul+Rosenzweig+SOI>
>>>> > > My completed application template follows: > >
>>>> APPLICATION TEMPLATE > > Name Paul Rosenzweig > Affiliation
>>>> The Heritage Foundation/Red Branch > Consulting -- part of
>>>> the NCSG > > Please provide an overview of your
>>>> experience/expertise with GNSO policy > development
>>>> processes: Since 2014, I have been an active > member of
>>>> the CCWG-A in both WS1 and WS2 regarding accountability
>>>> mechanisms > related to the ICANN transition. As such I
>>>> have participated in the full > gamut of related GNSO/NCSG
>>>> policy issue that are of applicability to that > context.
>>>> Given my legal background, I have particularly focused on
>>>> legal > issues -- viz, ICANN's revised mission statement,
>>>> the new Independent Review > Process, and ongoing
>>>> considerations of jurisdictional issues. I have been, > and
>>>> remain, especially focused on areas where the influence of
>>>> the GAC seems > to reflect governmental interests that are
>>>> inconsistent with GNSO policy. > > Please provide an
>>>> overview of your Previous engagements in GNSO work in a >
>>>> leadership capacity: I have not had a previous opportunity
>>>> to serve in > the GNSO or NCSG in a leadership capacity.
>>>> This is the first instance in > which I have volunteered
>>>> for such a position. > > Please describe your familiarity
>>>> with GAC processes, including GAC > engagement in GNSO
>>>> policy development: As part of my work > with the CCWG-A I
>>>> came to be intimately familiar with GAC processes for >
>>>> engaging in GNSO policy development. I suspect that few in
>>>> the GNSO have > paid quite as much attention as I have to
>>>> the GAC's rules of operation, its > definition of
>>>> consensus, and the ways in which it is permitted to
>>>> influence > ICANN policy. Indeed the changes to those
>>>> processes were one of the > particular focuses of my
>>>> interest in the CCWG-A and one of the reasons I was >
>>>> skeptical of the ultimate product of the CCWG and the
>>>> resulting changes to > ICANN's methods for considering GAC
>>>> advice. I remain of the view that GAC > engagement in GNSO
>>>> policy development is essential but that it should be >
>>>> accomplished through established GAC-GNSO liaison
>>>> procedures and not through > extra-procedural fiat. By way
>>>> of example, > I have been vocal in my view that the GAC's
>>>> intervention with the Board > regarding two letter second
>>>> level top level domains was procedurally > improper (and
>>>> also disappointed that the GNSO liaison to the GAC had not
>>>> > alerted the GNSO to this issue earlier. [And, though
>>>> neutrality is a > hallmark of a good liaison, I should also
>>>> make clear that I find GAC claims > that second level
>>>> two-letter domains should be restricted deeply >
>>>> unpersuasive and antithetical to policies that animate the
>>>> NCSG and the > GNSO]. > > Please provide any other
>>>> information that demonstrates your qualifications > for
>>>> this position: It is perhaps of relevance that I have a >
>>>> history of service in the US government and thus a
>>>> reasonable understanding > of the role of governments. In
>>>> the 2005-09 time period I twice served as > the Acting
>>>> Assistant Secretary for International Affairs at the
>>>> Department > of Homeland Security, and thus experience in
>>>> international diplomatic > contexts. I attach a full resume
>>>> for your consideration. > > I would be happy to answer any
>>>> further questions you or other members of the > NCSG might
>>>> have. > > Regards > Paul > > Paul Rosenzweig > Red Branch
>>>> Consulting, PLLC > 509 C St. NE > Washington, DC 20002 >
>>>> paul.rosenzweig at redbranchconsulting.com
>>>> <mailto:paul.rosenzweig at redbranchconsulting.com> > O: +1
>>>> (202) 547-0660 <tel:+1%20202-547-0660> > M: +1 (202)
>>>> 329-9650 <tel:+1%20202-329-9650> > VOIP: +1 (202) 738-1739
>>>> <tel:+1%20202-738-1739> > www.redbranchconsulting.com
>>>> <http://www.redbranchconsulting.com> >
>>>> www.paulrosenzweigesq.com
>>>> <http://www.paulrosenzweigesq.com> > My PGP Key: >
>>>> https://keys.mailvelope.com/pks/lookup?op=get&search=0x9A830097CA066684
>>>> <https://keys.mailvelope.com/pks/lookup?op=get&search=0x9A830097CA066684>
>>>> > > > > ----- End forwarded message ----- > >
>>>> _______________________________________________ > NCSG-PC
>>>> mailing list > NCSG-PC at lists.ncsg.is
>>>> <mailto:NCSG-PC at lists.ncsg.is> >
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>> <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>> _______________________________________________ NCSG-PC
>>>> mailing list NCSG-PC at lists.ncsg.is
>>>> <mailto:NCSG-PC at lists.ncsg.is>
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>> <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>> <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>> <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>> <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170909/8c94f87e/attachment.htm>
More information about the NCSG-PC
mailing list