From rafik.dammak at gmail.com  Mon Apr  1 02:26:28 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Mon, 1 Apr 2019 08:26:28 +0900
Subject: [NCSG-PC] Fw: [council] GNSO Council Leadership Team
 Correspondence to Mr. Kirikos and Mr. Shatan
In-Reply-To: <I2f6JeyDyGO9UouTBEwnOOW2EMW6pv9NuQP7bBz8cca3x563QgAtp_5KoarS1kyVdDinpb3SWVx2YFuWSIbZ97DHviCFNv-FmuF9ADx7GhY=@ferdeline.com>
References: <7aea5400375546238809a345a9081486@verisign.com>
 <I2f6JeyDyGO9UouTBEwnOOW2EMW6pv9NuQP7bBz8cca3x563QgAtp_5KoarS1kyVdDinpb3SWVx2YFuWSIbZ97DHviCFNv-FmuF9ADx7GhY=@ferdeline.com>
Message-ID: <CAH5sThkQgC4YRfAomewYj4CuaiBNTi+u7FZAaKyQJ35_9zy+1A@mail.gmail.com>

Hi,

it is the GNSO Council leadership sending the letters, not the council.

Best,

Rafik

Le sam. 30 mars 2019 ? 19:50, Ayden F?rdeline <icann at ferdeline.com> a
?crit :

> Sharing for information purposes. The first time that I've heard that the
> GNSO Council was sending such correspondence is after it has already been
> sent...
>
> Ayden
>
>
> ??????? Original Message ???????
> On Friday, March 29, 2019 7:39 PM, Drazek, Keith via council <
> council at gnso.icann.org> wrote:
>
> Hi all,
>
>
>
> Keeping everyone informed of the latest developments, today I delivered
> the attached letters concerning enforcement of ICANN?s Expected Standards
> of Behavior to Mr. Kirikos and Mr. Shatan. Let me know if you have any
> questions.
>
>
>
> Best regards,
>
> Keith
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190401/016fed0f/attachment.htm>

From rafik.dammak at gmail.com  Mon Apr  1 09:05:18 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Mon, 1 Apr 2019 15:05:18 +0900
Subject: [NCSG-PC] NCSG representatives to EPDP team
In-Reply-To: <CABDXvWq3Y_5R2PE-RX8hvHNyfZdoxD37uNJpdFiW1dRu0BwauQ@mail.gmail.com>
References: <CAH5sTh=vRw3YuRXSWeWSXDsDx-55LihhOnRHQszqV_9L=NUW1A@mail.gmail.com>
 <CAH5sThkac-eeZAQ-ke8MD9qZOBJ5ysDjs82ynbKS3Z8a+QgXpw@mail.gmail.com>
 <6d84d832-a099-4aeb-dfd8-f0e563d48da0@mail.utoronto.ca>
 <CAH5sThm6QDHqrxcf4T71QTa6EFXn3tPvQX97mVOKx-SOG19jZg@mail.gmail.com>
 <CAH5sThnnsX430pj7o4O=4Rcge83CNsYDXUPkYKrjY-AW-Y8YaA@mail.gmail.com>
 <CABDXvWq3Y_5R2PE-RX8hvHNyfZdoxD37uNJpdFiW1dRu0BwauQ@mail.gmail.com>
Message-ID: <CAH5sThkCt5cDSdcbu1PNA9fESTxbbfnNq5XcFrm3_2LwA3C4aQ@mail.gmail.com>

hi all

for the replacement, I proposed before to tweak the previous call for
candidates to replace Collin and update with bits relevant to phase 2 but
also regarding expected knowledge of phase 1. if there is no objection, I
will share the draft call within this week so we can start a short call by
next week.

Best,

Rafik

Le ven. 29 mars 2019 ? 19:09, Ars?ne Tungali <arsenebaguma at gmail.com> a
?crit :

> Thanks, everyone for willing to continue, I believe this is good for
> us that you are willling to continue representing us throughout phase
> 2.
>
> I am sure we will be able to have a replacement for Collin whom I
> would like to thank for being there during phase 1 as an alternate.
>
> 2019-03-29 2:04 UTC+02:00, Rafik Dammak <rafik.dammak at gmail.com>:
> > Hi,
> >
> > all current EPDP representatives confirmed they will continue for phase 2
> > and Tatiana and David as alternates.
> > we only have to replace Collin as alternate.
> >
> > Best,
> >
> > Rafik
> > Le mer. 27 mars 2019 ? 23:47, Rafik Dammak <rafik.dammak at gmail.com> a
> > ?crit :
> >
> >> thanks Stephanie.
> >> we are still missing Ayden and Julf confirmation. I thought Ayden
> >> expressed his intention to not continue previously but stated he was
> >> still
> >> thinking during Kobe meeting in PC session.
> >> I would like to close this quickly and that we do call for candidates
> >> asap.
> >>
> >> Best,
> >>
> >> Rafik
> >>
> >> Le mer. 27 mars 2019 ? 00:48, Stephanie Perrin <
> >> stephanie.perrin at mail.utoronto.ca> a ?crit :
> >>
> >>> Sorry, I thought I had confirmed. Yes, I am in for the next haul.
> >>>
> >>> Stephanie
> >>> On 2019-03-26 00:11, Rafik Dammak wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I am resuming the discussion for this. First action will to finalize
> the
> >>> confirmation with all members.
> >>> I only heard from Farzaneh, Milton, Amr that they will continue as rep
> >>> and Tatiana and David as alternate.I assume Stephanie will continue.
> >>> I aiming to confirm by Friday so we can have fairly quick call to
> >>> replace
> >>> if needed.
> >>>
> >>> Best,
> >>>
> >>> Rafik
> >>> Le mar. 5 mars 2019 ? 08:17, Rafik Dammak <rafik.dammak at gmail.com> a
> >>> ?crit :
> >>>
> >>>> Hi all,
> >>>>
> >>>> Keith communicated last week with all chairs of groups represented in
> >>>> EPDP team to confirm or replace their members there for phase 2. The
> >>>> same
> >>>> communication was shared with EPDP team.
> >>>>
> >>>> We are confirming with our NCSG representatives if they are willing to
> >>>> continue for phase 2. We might need to do some replacements and we
> have
> >>>> to
> >>>> act quickly in order for new appointees to catch-up. It also depends
> on
> >>>> the
> >>>> expected workload and that is ongoing discussion.
> >>>>
> >>>> One way is to tweak the previous call for candidates and send it asap
> >>>> in
> >>>> order to get a good pool of candidates from where to select.
> >>>> please let me know your thoughts and suggestions.
> >>>>
> >>>> Best,
> >>>>
> >>>> Rafik
> >>>>
> >>>
> >>> _______________________________________________
> >>> NCSG-PC mailing
> >>> listNCSG-PC at lists.ncsg.ishttps://
> lists.ncsg.is/mailman/listinfo/ncsg-pc
> >>>
> >>> _______________________________________________
> >>> NCSG-PC mailing list
> >>> NCSG-PC at lists.ncsg.is
> >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> >>>
> >>
> >
>
>
> --
> ------------------------
> **Ars?ne Tungali* <http://about.me/ArseneTungali>*
> Co-Founder & Executive Director, *Rudi international
> <http://www.rudiinternational.org>*,
> CEO,* Smart Services Sarl <https://www.smart-kitoko.com/>*,
> Tel: +243 993810967 (DRC)
> GPG: 523644A0
>
> 2015 Mandela Washington Fellow
> <
>
> http://tungali.blogspot.com/2015/06/selected-for-2015-mandela-washington.html
> >
>
> (YALI) - ICANN GNSO Council Member
> <https://gnso.icann.org/en/about/gnso-council.htm> Member. UN IGF MAG
> <https://www.un.org/press/en/2018/pi2247.doc.htm> Member
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190401/b32b0321/attachment.htm>

From elsa.saade at gmail.com  Mon Apr  1 21:51:29 2019
From: elsa.saade at gmail.com (Elsa S)
Date: Mon, 1 Apr 2019 14:51:29 -0400
Subject: [NCSG-PC] Fw: [council] GNSO Council Leadership Team
 Correspondence to Mr. Kirikos and Mr. Shatan
In-Reply-To: <CAH5sThkQgC4YRfAomewYj4CuaiBNTi+u7FZAaKyQJ35_9zy+1A@mail.gmail.com>
References: <7aea5400375546238809a345a9081486@verisign.com>
 <I2f6JeyDyGO9UouTBEwnOOW2EMW6pv9NuQP7bBz8cca3x563QgAtp_5KoarS1kyVdDinpb3SWVx2YFuWSIbZ97DHviCFNv-FmuF9ADx7GhY=@ferdeline.com>
 <CAH5sThkQgC4YRfAomewYj4CuaiBNTi+u7FZAaKyQJ35_9zy+1A@mail.gmail.com>
Message-ID: <CAHFwYbfAzN3sDXGEdYddmL+QARK0Bb4iP46ZaNDph6CUdM7PJA@mail.gmail.com>

So I do have a question about this! Is leadership basing the correspondence
on legal advice? Only on GNSO OP basis? Or what exactly?

E.
?

On Sun, Mar 31, 2019 at 7:26 PM Rafik Dammak <rafik.dammak at gmail.com> wrote:

> Hi,
>
> it is the GNSO Council leadership sending the letters, not the council.
>
> Best,
>
> Rafik
>
> Le sam. 30 mars 2019 ? 19:50, Ayden F?rdeline <icann at ferdeline.com> a
> ?crit :
>
>> Sharing for information purposes. The first time that I've heard that the
>> GNSO Council was sending such correspondence is after it has already been
>> sent...
>>
>> Ayden
>>
>>
>> ??????? Original Message ???????
>> On Friday, March 29, 2019 7:39 PM, Drazek, Keith via council <
>> council at gnso.icann.org> wrote:
>>
>> Hi all,
>>
>>
>>
>> Keeping everyone informed of the latest developments, today I delivered
>> the attached letters concerning enforcement of ICANN?s Expected Standards
>> of Behavior to Mr. Kirikos and Mr. Shatan. Let me know if you have any
>> questions.
>>
>>
>>
>> Best regards,
>>
>> Keith
>>
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-- 
--

Elsa Saade
Consultant
Gulf Centre for Human Rights
Twitter: @Elsa_Saade
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190401/77e6b87e/attachment.htm>

From rafik.dammak at gmail.com  Tue Apr  2 04:18:27 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 2 Apr 2019 10:18:27 +0900
Subject: [NCSG-PC] Fw: [council] GNSO Council Leadership Team
 Correspondence to Mr. Kirikos and Mr. Shatan
In-Reply-To: <CAHFwYbfAzN3sDXGEdYddmL+QARK0Bb4iP46ZaNDph6CUdM7PJA@mail.gmail.com>
References: <7aea5400375546238809a345a9081486@verisign.com>
 <I2f6JeyDyGO9UouTBEwnOOW2EMW6pv9NuQP7bBz8cca3x563QgAtp_5KoarS1kyVdDinpb3SWVx2YFuWSIbZ97DHviCFNv-FmuF9ADx7GhY=@ferdeline.com>
 <CAH5sThkQgC4YRfAomewYj4CuaiBNTi+u7FZAaKyQJ35_9zy+1A@mail.gmail.com>
 <CAHFwYbfAzN3sDXGEdYddmL+QARK0Bb4iP46ZaNDph6CUdM7PJA@mail.gmail.com>
Message-ID: <CAH5sTh=+dxFx8dc-nPCsMAk7Ur-yo+BkN+pvZZzKdMUZq6C8xw@mail.gmail.com>

Hi,

I am not sure to understand the question but I will try to respond. The
letters include references to the correspondence received from ICANN legal
council regarding the enforcement of expected standard of behavior by PDP
WG leadership and also explanation about the background leading to the
actions. The ICANN legal counsel was reached to give guidance regarding the
enforceability of ESB as it was challenged. The whole process started when
the GNSO OP process section 3.4 initiated by complain from Greg Shatan
against Georges Kirkios and having council leadership involvement by
co-chairs request (it was with the previous council leadership team in
May/June and so this handed over to current team).

Best,

Rafik

Le mar. 2 avr. 2019 ? 03:51, Elsa S <elsa.saade at gmail.com> a ?crit :

> So I do have a question about this! Is leadership basing the
> correspondence on legal advice? Only on GNSO OP basis? Or what exactly?
>
> E.
> ?
>
> On Sun, Mar 31, 2019 at 7:26 PM Rafik Dammak <rafik.dammak at gmail.com>
> wrote:
>
>> Hi,
>>
>> it is the GNSO Council leadership sending the letters, not the council.
>>
>> Best,
>>
>> Rafik
>>
>> Le sam. 30 mars 2019 ? 19:50, Ayden F?rdeline <icann at ferdeline.com> a
>> ?crit :
>>
>>> Sharing for information purposes. The first time that I've heard that
>>> the GNSO Council was sending such correspondence is after it has already
>>> been sent...
>>>
>>> Ayden
>>>
>>>
>>> ??????? Original Message ???????
>>> On Friday, March 29, 2019 7:39 PM, Drazek, Keith via council <
>>> council at gnso.icann.org> wrote:
>>>
>>> Hi all,
>>>
>>>
>>>
>>> Keeping everyone informed of the latest developments, today I delivered
>>> the attached letters concerning enforcement of ICANN?s Expected Standards
>>> of Behavior to Mr. Kirikos and Mr. Shatan. Let me know if you have any
>>> questions.
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Keith
>>>
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
> --
> --
>
> Elsa Saade
> Consultant
> Gulf Centre for Human Rights
> Twitter: @Elsa_Saade
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190402/415dc0e2/attachment.htm>

From rafik.dammak at gmail.com  Tue Apr  2 04:52:02 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 2 Apr 2019 10:52:02 +0900
Subject: [NCSG-PC] Fwd: [council] Recommendations Report on EPDP
In-Reply-To: <BA2CD0EE-D03E-4AB6-BD8E-A75538FE2E92@icann.org>
References: <71A201B7-F4B7-4A4B-8E56-773BB8729D05@icann.org>
 <SZn6gq3bFspetd-G8gKVWEWtLy7sokxPiYatSh0b05hNeZoumJp9ynWZZzmVoOK0kPw91yaem4D0C179lxGUu4NgFQG8RlpudCQttPXQ3qo=@ferdeline.com>
 <67a02fc2-8c2e-4bd3-92ff-5ca876fcf69e.pam.little@alibaba-inc.com>
 <98bc77e2d3b41accb1a0e1edc8b6bee6@gutierrez.se>
 <31282667-EE12-4B6D-A687-6DE65FD21B46@icann.org>
 <4026454764394bef6837be804c3c9ed5@gutierrez.se>
 <BA2CD0EE-D03E-4AB6-BD8E-A75538FE2E92@icann.org>
Message-ID: <CAH5sThk+KYWphzA6jLzgmdUPM-d2VwDvanGoexL4XyEEnyqgjw@mail.gmail.com>

Hi,

sharing the latest version of council report to board regarding EPDP phase
1 recommendations and final report, as it will considered for vote in the
next council meeting.

Best,

Rafik

---------- Forwarded message ---------
De : Caitlin Tubergen <caitlin.tubergen at icann.org>
Date: mar. 2 avr. 2019 ? 05:13
Subject: Re: [council] Recommendations Report on EPDP
To: Carlos Raul Gutierrez <carlosraul at gutierrez.se>, Marika Konings <
marika.konings at icann.org>
Cc: council at gnso.icann.org <council at gnso.icann.org>


Dear Councilors:



Thank you for the speedy and helpful feedback thus far.



Per Carlos? suggestion, I have added a table of contents to the report. I
have also addressed some of the questions in the document.



@Pam: regarding your suggestion about the policy impact analysis, the EPDP
Team, in p. 77 of its report, noted the following:



*Per the EPDP Team?s Charter, the goal of this effort is to determine if
the Temporary Specification for gTLD Registration Data should become an
ICANN Consensus Policy, as is or with modifications, while complying with
the GDPR and other relevant privacy and data protection law. As part of
this determination, the EPDP Team has considered the elements of the
Temporary Specification as outlined in the charter and answered the charter
questions. The EPDP Team has considered what subsidiary recommendations it
might make for future work by the GNSO which might be necessary to ensure
relevant Consensus Policies, including those related to registration data,
are reassessed to become consistent with applicable law (see relevant
recommendations). The EPDP Team recommends that as part of the
implementation process further consideration will be given to a set of
metrics to help inform the evaluation to measure success of these policy
recommendations.*



Accordingly, the metrics and effectiveness of the Policy will be items
covered in the implementation of the policy, and we will certainly flag
this for our colleagues in GDD. The impact analysis metrics would generally
be reviewed by the PDP WG in its Final Report; however, given the
externally-imposed deadline the EPDP Team was working under, this item was
moved to implementation.



Best regards,



Caitlin







*From: *council <council-bounces at gnso.icann.org> on behalf of Carlos Raul
Gutierrez <carlosraul at gutierrez.se>
*Date: *Monday, April 1, 2019 at 7:49 AM
*To: *Marika Konings <marika.konings at icann.org>
*Cc: *"council at gnso.icann.org" <council at gnso.icann.org>
*Subject: *Re: [council] Recommendations Report on EPDP



Thanks Marika,

1. If you can send me a table of contents as per my initial suggestion
yesterday, I'm happy to thelp with the logic of the document.

2. I can't help much with a trasnlation into standard english, but it would
really help us, English as a second or third language, to get to the core
and or purpose of the document and make a rational decision on the next
Coucnil meeting

3. Sorry, I was not there in 2004.

Cheers



---

Carlos Ra?l Guti?rrez

carlosraul at gutierrez.se

+506 8837 7176

Aparatado 1571-1000

COSTA RICA



El 2019-03-31 21:27, Marika Konings escribi?:



Hi All,



To provide a little bit of background on the approach and style of this
report, it was one of the improvements that came out of the 2004 GNSO
review during which the PDP in its current format was conceived. At the
time not all Board materials were published so there was no real visibility
as to what information was being provided to the ICANN Board. As such, the
GNSO decided that in addition to the Board Paper that is prepared by Org,
the GNSO Council would accompany the approval of GNSO policy
recommendations with a GNSO Council recommendations report to the ICANN
Board which would include the information that the Board would typically
review in its assessment of GNSO policy recommendations. Hopefully this
background is helpful as you further consider updates / edits.



Best regards,



Marika


On 31 Mar 2019, at 21:11, Carlos Raul Gutierrez <carlosraul at gutierrez.se>
wrote:

Hello Pam,

I certainly think that neither the chronological structure, nor the
recommendations-cum-recommendations style is appropriate for other people
than the insiders of the process.

Since I was not a direct participant I didn't dare to ask for more than a
table of contents and a clear statement of the purpose of the document.
Otherwise I don't think in this version is going to make the Council and
the PDP 3.0 very popular in the community. But I respect the voice of the
majority before making more marginal comments. In my view it needs a clear
structure and clear international standard english style, to which I can't
add much. The PDP members deserve better for their arduous work.

Carlos Ra?l Guti?rrez

carlosraul at gutierrez.se

+506 8837 7176

Aparatado 1571-1000

COSTA RICA



El 2019-03-31 18:13, Pam Little escribi?:

Hi all,



I have added more comments and minor edits to the version Ayden circulated
earlier.





I admit this is the first time I read a GNSO Council Recommendations Report
to the Board and it strikes me that the report template might need to be
updated.


Specifically, what seem missing in this draft report are things like policy
goals, policy impact analysis and metrics to measure effectiveness of the
new policy. These were recommendations from the Data & Metrics Working
Group and the most recent GNSO Review, which were approved by the Council
and supposedly fully implemented but neither the EPDP Charter, the EPDP
Final Report nor this draft report cover these topics. I would have thought
these topic are essential for the Council and the Board when approving any
PDP/EPDP final recommendations.



I note there are relevant sections (such as 3 and 10) in the draft report
but, as currently drafted, Section 3 reads like a restatement of the
concerns or positions of certain SGs and Cs while Section 10 does not
contain substantive analysis:



*"3 (An analysis of how the issue(s) would affect each Constituency or
Stakeholder Group, including any financial impact on the Constituency or
Stakeholder Group) seems to be just a rehash of concerns or positions each
SG's/**C's*

....

*10. Impact/implementation considerations from ICANN staff *



The internal ICANN org implementation team has formed and has begun to
review the recommendations to analyze the implementation requirements.
ICANN org considers the scope of effort required for this implementation to
be significant and extensive. "



I welcome others' thoughts.



Kind regards,



Pam



------------------------------------------------------------------

Sender:Ayden F?rdeline <icann at ferdeline.com>

Sent At:2019 Mar. 30 (Sat.) 21:43

Recipient:Caitlin Tubergen <caitlin.tubergen at icann.org>

Cc:gnso-secs at icann.org <gnso-secs at icann.org>; council at gnso.icann.org <
council at gnso.icann.org>

Subject:Re: [council] Recommendations Report on EPDP



Hi Caitlin, all-



Please find attached some suggested edits to this document.



Thanks,

Ayden





??????? Original Message ???????

On Saturday, March 30, 2019 12:07 AM, Caitlin Tubergen <
caitlin.tubergen at icann.org> wrote:



Dear Councilors:



Attached, please find the draft GNSO Council Report to the ICANN Board on
the EPDP recommendations for your consideration.



Following the customary practice, this report will be added to the Council's
18 April consent agenda, unless there are any comments or concerns with
this approach.



If you have any proposed edits or comments on the report, please kindly
submit them by the document deadline of *Monday,* *8 April 2018*.



Thank you.



Kind regards,



Caitlin



*--*

*Caitlin Tubergen*

Policy Senior Manager - GNSO

ICANN











_______________________________________________
council mailing list
council at gnso.icann.org
https://mm.icann.org/mailman/listinfo/council

_______________________________________________
council mailing list
council at gnso.icann.org
https://mm.icann.org/mailman/listinfo/council

_______________________________________________
council mailing list
council at gnso.icann.org
https://mm.icann.org/mailman/listinfo/council
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190402/6ed1f253/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: EPDP - GNSO Council Recommendations Report to the Board_29Mar19 - AF edits + Pam_CT.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 140530 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190402/6ed1f253/attachment.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4621 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190402/6ed1f253/attachment.bin>

From elsa.saade at gmail.com  Tue Apr  2 06:35:10 2019
From: elsa.saade at gmail.com (Elsa S)
Date: Mon, 1 Apr 2019 23:35:10 -0400
Subject: [NCSG-PC] Fw: [council] GNSO Council Leadership Team
 Correspondence to Mr. Kirikos and Mr. Shatan
In-Reply-To: <CAH5sTh=+dxFx8dc-nPCsMAk7Ur-yo+BkN+pvZZzKdMUZq6C8xw@mail.gmail.com>
References: <7aea5400375546238809a345a9081486@verisign.com>
 <I2f6JeyDyGO9UouTBEwnOOW2EMW6pv9NuQP7bBz8cca3x563QgAtp_5KoarS1kyVdDinpb3SWVx2YFuWSIbZ97DHviCFNv-FmuF9ADx7GhY=@ferdeline.com>
 <CAH5sThkQgC4YRfAomewYj4CuaiBNTi+u7FZAaKyQJ35_9zy+1A@mail.gmail.com>
 <CAHFwYbfAzN3sDXGEdYddmL+QARK0Bb4iP46ZaNDph6CUdM7PJA@mail.gmail.com>
 <CAH5sTh=+dxFx8dc-nPCsMAk7Ur-yo+BkN+pvZZzKdMUZq6C8xw@mail.gmail.com>
Message-ID: <CAHFwYbdUHrMhyPxcbfCYcL0h9kkQXDaPWA_N+GcTRCVEJeEOsg@mail.gmail.com>

Thanks Rafik. I understand how this came about. I'm just wondering if the
drafting of these exchanges by the leadership team are being reviewed by
any entity for legal advice prior to sending to the two parties? Or if the
drafting is being based solely on the developments and language used in
previous communication.

Best,

Elsa
--

On Mon, Apr 1, 2019 at 9:18 PM Rafik Dammak <rafik.dammak at gmail.com> wrote:

> Hi,
>
> I am not sure to understand the question but I will try to respond. The
> letters include references to the correspondence received from ICANN legal
> council regarding the enforcement of expected standard of behavior by PDP
> WG leadership and also explanation about the background leading to the
> actions. The ICANN legal counsel was reached to give guidance regarding the
> enforceability of ESB as it was challenged. The whole process started when
> the GNSO OP process section 3.4 initiated by complain from Greg Shatan
> against Georges Kirkios and having council leadership involvement by
> co-chairs request (it was with the previous council leadership team in
> May/June and so this handed over to current team).
>
> Best,
>
> Rafik
>
> Le mar. 2 avr. 2019 ? 03:51, Elsa S <elsa.saade at gmail.com> a ?crit :
>
>> So I do have a question about this! Is leadership basing the
>> correspondence on legal advice? Only on GNSO OP basis? Or what exactly?
>>
>> E.
>> ?
>>
>> On Sun, Mar 31, 2019 at 7:26 PM Rafik Dammak <rafik.dammak at gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> it is the GNSO Council leadership sending the letters, not the council.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> Le sam. 30 mars 2019 ? 19:50, Ayden F?rdeline <icann at ferdeline.com> a
>>> ?crit :
>>>
>>>> Sharing for information purposes. The first time that I've heard that
>>>> the GNSO Council was sending such correspondence is after it has already
>>>> been sent...
>>>>
>>>> Ayden
>>>>
>>>>
>>>> ??????? Original Message ???????
>>>> On Friday, March 29, 2019 7:39 PM, Drazek, Keith via council <
>>>> council at gnso.icann.org> wrote:
>>>>
>>>> Hi all,
>>>>
>>>>
>>>>
>>>> Keeping everyone informed of the latest developments, today I delivered
>>>> the attached letters concerning enforcement of ICANN?s Expected Standards
>>>> of Behavior to Mr. Kirikos and Mr. Shatan. Let me know if you have any
>>>> questions.
>>>>
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Keith
>>>>
>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>> --
>> --
>>
>> Elsa Saade
>> Consultant
>> Gulf Centre for Human Rights
>> Twitter: @Elsa_Saade
>>
>

-- 
--

Elsa Saade
Consultant
Gulf Centre for Human Rights
Twitter: @Elsa_Saade
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190401/5f30c22e/attachment.htm>

From rafik.dammak at gmail.com  Tue Apr  2 07:38:18 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 2 Apr 2019 13:38:18 +0900
Subject: [NCSG-PC] Fw: [council] GNSO Council Leadership Team
 Correspondence to Mr. Kirikos and Mr. Shatan
In-Reply-To: <CAHFwYbdUHrMhyPxcbfCYcL0h9kkQXDaPWA_N+GcTRCVEJeEOsg@mail.gmail.com>
References: <7aea5400375546238809a345a9081486@verisign.com>
 <I2f6JeyDyGO9UouTBEwnOOW2EMW6pv9NuQP7bBz8cca3x563QgAtp_5KoarS1kyVdDinpb3SWVx2YFuWSIbZ97DHviCFNv-FmuF9ADx7GhY=@ferdeline.com>
 <CAH5sThkQgC4YRfAomewYj4CuaiBNTi+u7FZAaKyQJ35_9zy+1A@mail.gmail.com>
 <CAHFwYbfAzN3sDXGEdYddmL+QARK0Bb4iP46ZaNDph6CUdM7PJA@mail.gmail.com>
 <CAH5sTh=+dxFx8dc-nPCsMAk7Ur-yo+BkN+pvZZzKdMUZq6C8xw@mail.gmail.com>
 <CAHFwYbdUHrMhyPxcbfCYcL0h9kkQXDaPWA_N+GcTRCVEJeEOsg@mail.gmail.com>
Message-ID: <CAH5sTh=_3sJzaW-wYDA0hgb24sdznvmhN4z3Vi1JdUbY==coVA@mail.gmail.com>

Hi,

The letters were drafted within council leadership team, feedback was
shared but there was no a formal legal review or advice other than what was
sent prior to Kobe meeting.

Best,

Rafik


Le mar. 2 avr. 2019 ? 12:35, Elsa S <elsa.saade at gmail.com> a ?crit :

> Thanks Rafik. I understand how this came about. I'm just wondering if the
> drafting of these exchanges by the leadership team are being reviewed by
> any entity for legal advice prior to sending to the two parties? Or if the
> drafting is being based solely on the developments and language used in
> previous communication.
>
> Best,
>
> Elsa
> --
>
> On Mon, Apr 1, 2019 at 9:18 PM Rafik Dammak <rafik.dammak at gmail.com>
> wrote:
>
>> Hi,
>>
>> I am not sure to understand the question but I will try to respond. The
>> letters include references to the correspondence received from ICANN legal
>> council regarding the enforcement of expected standard of behavior by PDP
>> WG leadership and also explanation about the background leading to the
>> actions. The ICANN legal counsel was reached to give guidance regarding the
>> enforceability of ESB as it was challenged. The whole process started when
>> the GNSO OP process section 3.4 initiated by complain from Greg Shatan
>> against Georges Kirkios and having council leadership involvement by
>> co-chairs request (it was with the previous council leadership team in
>> May/June and so this handed over to current team).
>>
>> Best,
>>
>> Rafik
>>
>> Le mar. 2 avr. 2019 ? 03:51, Elsa S <elsa.saade at gmail.com> a ?crit :
>>
>>> So I do have a question about this! Is leadership basing the
>>> correspondence on legal advice? Only on GNSO OP basis? Or what exactly?
>>>
>>> E.
>>> ?
>>>
>>> On Sun, Mar 31, 2019 at 7:26 PM Rafik Dammak <rafik.dammak at gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> it is the GNSO Council leadership sending the letters, not the council.
>>>>
>>>> Best,
>>>>
>>>> Rafik
>>>>
>>>> Le sam. 30 mars 2019 ? 19:50, Ayden F?rdeline <icann at ferdeline.com> a
>>>> ?crit :
>>>>
>>>>> Sharing for information purposes. The first time that I've heard that
>>>>> the GNSO Council was sending such correspondence is after it has already
>>>>> been sent...
>>>>>
>>>>> Ayden
>>>>>
>>>>>
>>>>> ??????? Original Message ???????
>>>>> On Friday, March 29, 2019 7:39 PM, Drazek, Keith via council <
>>>>> council at gnso.icann.org> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>>
>>>>>
>>>>> Keeping everyone informed of the latest developments, today I
>>>>> delivered the attached letters concerning enforcement of ICANN?s Expected
>>>>> Standards of Behavior to Mr. Kirikos and Mr. Shatan. Let me know if you
>>>>> have any questions.
>>>>>
>>>>>
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Keith
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>> --
>>> --
>>>
>>> Elsa Saade
>>> Consultant
>>> Gulf Centre for Human Rights
>>> Twitter: @Elsa_Saade
>>>
>>
>
> --
> --
>
> Elsa Saade
> Consultant
> Gulf Centre for Human Rights
> Twitter: @Elsa_Saade
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190402/f881c7f3/attachment.htm>

From icann at ferdeline.com  Tue Apr  2 13:08:05 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Tue, 02 Apr 2019 10:08:05 +0000
Subject: [NCSG-PC] Fw: [council] GNSO Council Leadership Team
 Correspondence to Mr. Kirikos and Mr. Shatan
In-Reply-To: <CAH5sTh=_3sJzaW-wYDA0hgb24sdznvmhN4z3Vi1JdUbY==coVA@mail.gmail.com>
References: <7aea5400375546238809a345a9081486@verisign.com>
 <I2f6JeyDyGO9UouTBEwnOOW2EMW6pv9NuQP7bBz8cca3x563QgAtp_5KoarS1kyVdDinpb3SWVx2YFuWSIbZ97DHviCFNv-FmuF9ADx7GhY=@ferdeline.com>
 <CAH5sThkQgC4YRfAomewYj4CuaiBNTi+u7FZAaKyQJ35_9zy+1A@mail.gmail.com>
 <CAHFwYbfAzN3sDXGEdYddmL+QARK0Bb4iP46ZaNDph6CUdM7PJA@mail.gmail.com>
 <CAH5sTh=+dxFx8dc-nPCsMAk7Ur-yo+BkN+pvZZzKdMUZq6C8xw@mail.gmail.com>
 <CAHFwYbdUHrMhyPxcbfCYcL0h9kkQXDaPWA_N+GcTRCVEJeEOsg@mail.gmail.com>
 <CAH5sTh=_3sJzaW-wYDA0hgb24sdznvmhN4z3Vi1JdUbY==coVA@mail.gmail.com>
Message-ID: <PQcgZqteCdb1pWFNEmNwqGswfmetEI3QPuMg9MzGJvtqSZ_8iUMxFGj4hShYSQXKgfvyiMqYpVs6mV1fCtmqxn3iATCFWO7AOv1dvY_Ks7U=@ferdeline.com>

I do not think it is appropriate for Council leadership to send correspondence like this without at least giving the Council the courtesy of a briefing. It would be nice to invite our feedback, too. But this is not a new issue, and communication between Council leadership and the Council has been poor for several months now. I do hope this will improve.

Ayden

??????? Original Message ???????
On Tuesday, April 2, 2019 6:38 AM, Rafik Dammak <rafik.dammak at gmail.com> wrote:

> Hi,
>
> The letters were drafted within council leadership team, feedback was shared but there was no a formal legal review or advice other than what was sent prior to Kobe meeting.
>
> Best,
>
> Rafik
>
> Le mar. 2 avr. 2019 ? 12:35, Elsa S <elsa.saade at gmail.com> a ?crit :
>
>> Thanks Rafik. I understand how this came about. I'm just wondering if the drafting of these exchanges by the leadership team are being reviewed by any entity for legal advice prior to sending to the two parties? Or if the drafting is being based solely on the developments and language used in previous communication.
>>
>> Best,
>>
>> Elsa
>> --
>>
>> On Mon, Apr 1, 2019 at 9:18 PM Rafik Dammak <rafik.dammak at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I am not sure to understand the question but I will try to respond. The letters include references to the correspondence received from ICANN legal council regarding the enforcement of expected standard of behavior by PDP WG leadership and also explanation about the background leading to the actions. The ICANN legal counsel was reached to give guidance regarding the enforceability of ESB as it was challenged. The whole process started when the GNSO OP process section 3.4 initiated by complain from Greg Shatan against Georges Kirkios and having council leadership involvement by co-chairs request (it was with the previous council leadership team in May/June and so this handed over to current team).
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> Le mar. 2 avr. 2019 ? 03:51, Elsa S <elsa.saade at gmail.com> a ?crit :
>>>
>>>> So I do have a question about this! Is leadership basing the correspondence on legal advice? Only on GNSO OP basis? Or what exactly?
>>>>
>>>> E.
>>>> ?
>>>>
>>>> On Sun, Mar 31, 2019 at 7:26 PM Rafik Dammak <rafik.dammak at gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> it is the GNSO Council leadership sending the letters, not the council.
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>>> Le sam. 30 mars 2019 ? 19:50, Ayden F?rdeline <icann at ferdeline.com> a ?crit :
>>>>>
>>>>>> Sharing for information purposes. The first time that I've heard that the GNSO Council was sending such correspondence is after it has already been sent...
>>>>>>
>>>>>> Ayden
>>>>>>
>>>>>> ??????? Original Message ???????
>>>>>> On Friday, March 29, 2019 7:39 PM, Drazek, Keith via council <council at gnso.icann.org> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Keeping everyone informed of the latest developments, today I delivered the attached letters concerning enforcement of ICANN?s Expected Standards of Behavior to Mr. Kirikos and Mr. Shatan. Let me know if you have any questions.
>>>>>>>
>>>>>>> Best regards,
>>>>>>>
>>>>>>> Keith
>>>>>>
>>>>>> _______________________________________________
>>>>>> NCSG-PC mailing list
>>>>>> NCSG-PC at lists.ncsg.is
>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>> --
>>>> --
>>>>
>>>> Elsa Saade
>>>> Consultant
>>>> Gulf Centre for Human Rights
>>>> Twitter: @Elsa_Saade
>>
>> --
>> --
>>
>> Elsa Saade
>> Consultant
>> Gulf Centre for Human Rights
>> Twitter: @Elsa_Saade
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190402/64bdaf98/attachment.htm>

From rafik.dammak at gmail.com  Wed Apr 10 14:36:20 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Wed, 10 Apr 2019 20:36:20 +0900
Subject: [NCSG-PC] Fwd: [NCSG-Discuss] [Public Comment] NCSG Comment on the
 EPDP on Temp Spec for Board Consideration
In-Reply-To: <CA+Ks+AC=nz37JNrVrsM-Si_n4BMdnZvrKn0XDPWH3_Mk5h0wHQ@mail.gmail.com>
References: <CA+Ks+AC=nz37JNrVrsM-Si_n4BMdnZvrKn0XDPWH3_Mk5h0wHQ@mail.gmail.com>
Message-ID: <CAH5sThnA0W=81bAvyPP-0=Li2BMfP09gHmT7ff8o4EQBhDYr9A@mail.gmail.com>

Hi,

We have a draft comment to review for endorsement. Deadline for submission
is in 17th April.

Best,

Rafik

---------- Forwarded message ---------
From: Louise Marie Hurel <louise.marie.hsd at gmail.com>
Date: Wed, Apr 10, 2019, 20:33
Subject: [NCSG-Discuss] [Public Comment] NCSG Comment on the EPDP on Temp
Spec for Board Consideration
To: <NCSG-DISCUSS at listserv.syr.edu>


Hi all,

Here's the link to the draft version of the NCSG comment on the *GNSO
Expedited Policy Development Process (EPDP) on the Temporary Specification
for gTLD Registration Data Policy Recommendations for ICANN Board
Consideration*:
https://docs.google.com/document/d/1YZe-AtxIMso3sobLSFSn_SsdDcsZS3myu8GNFfqZCQI/edit


As you will note, the main objective of this comment is to provide an
account and narrative as to where we compromised (and *not* to re-open
substantive policy discussions) and re-state our positions. Please feel
free to review the draft comment and share your thoughts, particularly
those that were on the EPDP team during Phase 1 and can provide a more
detailed background to the final report.

The deadline for submission is *17 April*.

Many thanks to Amr, Farzi and Stefan Filipovic for the comments!

All the best,

*Louise Marie Hurel*

Research and Project Development

Cybersecurity and Digital Liberties Programme | Igarap? Institute

Publications
<https://www.researchgate.net/profile/Louise_Marie_Hurel/publications>
Skype: louise.dias
louise at igarape.org.br
louise.marie.hsd at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190410/5413672d/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Fri Apr 12 02:58:04 2019
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Thu, 11 Apr 2019 23:58:04 +0000
Subject: [NCSG-PC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] Topic Proposals
 for ICANN65 Marrakech
In-Reply-To: <BD090E4C-1460-40D5-A5C3-A784AC5079CA@icann.org>
References: <BD090E4C-1460-40D5-A5C3-A784AC5079CA@icann.org>
Message-ID: <572f8350-fbb7-3bdd-c239-4aafece2cc42@mail.utoronto.ca>


given the deadline for proposals, perhaps we should kick a few ideas around at the policy committee meeting this week folks.
Steph
-------- Forwarded Message --------
Subject:        [SOAC-Leaders-ICANNMeeting-Planning] Topic Proposals for ICANN65 Marrakech
Date:   Thu, 11 Apr 2019 19:53:28 +0000
From:   Tanzanica S. King <tanzanica.king at icann.org><mailto:tanzanica.king at icann.org>
To:     SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning at icann.org><mailto:soac-leaders-icannmeeting-planning at icann.org>


Dear Community Leaders:

Several important issues were raised during the ICANN65 Kickoff in Kobe, and it?s been good to see discussions continue on the mailing list after the meeting.

So far, the suggested topics for cross-community or high-interest sessions in Marrakech are as follows:


  1.  Policy around Universal Acceptance and steps to be taken by TLD operators/registrars, software developers and hosting companies
  2.  DNS over HTTPS (DoH) ? hot subject for many stakeholders: TLDs, users, governments, lawyers, ISPs, etc.
  3.  Nominating Committee Review
  4.  Evolution of ICANN Multi-stakeholder model of Governance
  5.  Hijacking / Account Take-Over / Attacks

To move us forward in the selection of topics, the ICANN65 Topic Proposal Form<https://icann.wufoo.com/forms/icannn65-topic-proposal-form/> is now open for submissions. Before completing a form, please continue to share all proposed topics with the group to avoid duplicate submissions.

ICANN65 Topic Proposal Form<https://icann.wufoo.com/forms/icannn65-topic-proposal-form/>
Submission Deadline: 19 April 2019

The group also suggested that we reduce the number of CC/HIT slots to allow more time for progressing policy work, with an understanding that the final slots will be based on necessity and prioritization of topics. This approach aligns perfectly with the intentions of the block schedule. However, for schedule development, it may be helpful to know which of the seven slots is most likely to be freed up. Given the CC/HIT slots on Monday and Wednesday conflict with Tech Day and the GAC Communiqu?, can we assume these would be the first to drop off? Again, even if not final, this guidance will help support schedule planning for your groups.

Best,

Tanzanica


_______________________________________________
Tanzanica S. King
Sr. Manager, Meeting Strategy and Design
ICANN

Office   +1 310 301 5800
Mobile  +1 310 995 3038
www.icann.org<http://www.icann.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190411/de2eba63/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Attached Message Part
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190411/de2eba63/attachment.ksh>

From stephanie.perrin at mail.utoronto.ca  Fri Apr 12 21:39:53 2019
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Fri, 12 Apr 2019 18:39:53 +0000
Subject: [NCSG-PC] Fwd: Re: [ICANN Community Leaders] Accountability and
 community input on IRP standing panel
In-Reply-To: <b06ff5ff-410c-1678-8471-293b470ed270@tucows.com>
References: <b06ff5ff-410c-1678-8471-293b470ed270@tucows.com>
Message-ID: <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>

I think we should jump in and support this as well, any dissent?

Steph


-------- Forwarded Message --------
Subject:        Re: [ICANN Community Leaders] Accountability and community input on IRP standing panel
Date:   Fri, 12 Apr 2019 11:40:12 -0400
From:   Graeme Bunton <gbunton at tucows.com><mailto:gbunton at tucows.com>
To:     so-ac-sg-cleaders at icann.org<mailto:so-ac-sg-cleaders at icann.org>



These are good points Katrina, thank you.

The RrSG shares these process concerns too, and expressed them directly to GDD staff already.

Graeme

On 2019-04-12 11:12 a.m., Austin, Donna via SO-AC-SG-CLeaders wrote:
Dear Katrina

Thank you for raising this important issue. The RySG has similar concerns about important request for input being buried in blog posts as opposed to the familiar public comment process. We agree that the timing of this particular blog and request was unfortunate given it was, as you pointed out, posted right before ICANN64 when most people were travelling.

The RySG supports your request for an extension and also your request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future.

Donna

Donna Austin
Chair, RySG

From: SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces at icann.org] On Behalf Of Katrina Sataki
Sent: Friday, April 12, 2019 12:55 AM
To: 'Goran Marby' <goran.marby at icann.org><mailto:goran.marby at icann.org>
Cc: ccnso-council at icann.org<mailto:ccnso-council at icann.org>; 'Chris Disspain' <chris at disspain.uk><mailto:chris at disspain.uk>; 'Nigel Roberts' <nigel.roberts at board.icann.org><mailto:nigel.roberts at board.icann.org>; so-ac-sg-cleaders at icann.org<mailto:so-ac-sg-cleaders at icann.org>
Subject: [ICANN Community Leaders] Accountability and community input on IRP standing panel

Dear G?ran:

In your blog post of 9 March 2019, you invited community inputs on the process for the selection of a standing panel to hear Independent Review Process (IRP) complaints. You included a series of questions, with a deadline for responses by 15 April 2019:


-          Qualifications for Standing Panelists: Are there specific qualifications that should be included? If so, what are they? Anything disqualifying? Should the SOs and ACs recommend qualifications? And if so, how?

-          Identifying a Slate of Well-Qualified Panelists: We?ve heard concerns from some members of the ICANN community as to whether the broader community has the appropriate experience and skill for this selection work, and have suggested the possibility that ICANN instead contract with experts to perform this vetting process. Should the community rely on expertise to help vet and recommend a final slate for the standing panel?

-          Board Approval of Panel Slate ? Further Questions: After there is a slate of well-qualified applicants, the Board must confirm the panel. If the Board has questions that might impact its confirmation, to whom should those questions be addressed? If experts are used to develop the slate, should the experts, the SOs and ACs, or some combination thereof be part of that conversation?

-          Future Selections: Should the process being designed today be reviewed for effectiveness after the first slating is completed, prior to making it standard operating procedure for future selection rounds?

The IRP, as you correctly stated, is an accountability mechanism arising from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for breaches of ICANN?s own policies, core values or because decisions have been made on the basis of incorrect information.

Matters of high importance that fall within scope include disputes involving the rights of the Empowered Community, enforcement of ICANN?s contractual rights with respect to the IANA Naming Function Contract, and claims regarding PTI service complaints by direct customers of the IANA naming functions (that are not resolved through mediation). The appointment of appropriately qualified and independent panellists who will be making these review decision is therefore a high concern to us.

Taking into account that:
1)    the blog post was published right before ICANN64, when most volunteers are travelling or busy preparing for the meeting,
2)    no corresponding public comments request has been published on the ICANN website,
3)    no information about the request was published in ICANN Community Leadership Digest (the questions were first mentioned only on 11 April),
and to ensure that:
1)    all community members are aware of the opportunity to provide input,
2)    everyone has sufficient time to discuss the issue and submit their considerations,
3)    the process is transparent and all comments are published in due time,
we would like to encourage you to re-launch the call for community inputs in accordance with the established procedures.

Furthermore, we request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future. While a blog post may remain to be a good tool for reminders, and senior staff commentary may encourage engagement and participation, they are no substitute for due process.

Yours sincerely,

Katrina Sataki
On behalf of the ccNSO Council



_______________________________________________
SO-AC-SG-CLeaders mailing list
SO-AC-SG-CLeaders at icann.org<mailto:SO-AC-SG-CLeaders at icann.org>
https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders


--
____________________________
Graeme Bunton
Director, Analytics & Policy
Tucows Inc.
PH: 416 535 0123 ext 1634
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190412/40dabb72/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Attached Message Part
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190412/40dabb72/attachment.ksh>

From arsenebaguma at gmail.com  Fri Apr 12 22:21:25 2019
From: arsenebaguma at gmail.com (=?utf-8?Q?Ars=C3=A8ne_Tungali?=)
Date: Fri, 12 Apr 2019 21:21:25 +0200
Subject: [NCSG-PC] Fwd: Re: [ICANN Community Leaders] Accountability and
 community input on IRP standing panel
In-Reply-To: <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
References: <b06ff5ff-410c-1678-8471-293b470ed270@tucows.com>
 <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
Message-ID: <3F361B56-B0B5-4DF5-B283-9B158655A0F7@gmail.com>

No objection from me!

Sent from my iPhone

> On 12 Apr 2019, at 20:39, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> wrote:
> 
> I think we should jump in and support this as well, any dissent?
> 
> Steph
> 
> 
> 
> -------- Forwarded Message --------
> Subject:	Re: [ICANN Community Leaders] Accountability and community input on IRP standing panel
> Date:	Fri, 12 Apr 2019 11:40:12 -0400
> From:	Graeme Bunton <gbunton at tucows.com>
> To:	so-ac-sg-cleaders at icann.org
> 
> 
> These are good points Katrina, thank you.
> 
> The RrSG shares these process concerns too, and expressed them directly to GDD staff already.
> 
> Graeme
> 
>> On 2019-04-12 11:12 a.m., Austin, Donna via SO-AC-SG-CLeaders wrote:
>> Dear Katrina
>>  
>> Thank you for raising this important issue. The RySG has similar concerns about important request for input being buried in blog posts as opposed to the familiar public comment process. We agree that the timing of this particular blog and request was unfortunate given it was, as you pointed out, posted right before ICANN64 when most people were travelling.
>>  
>> The RySG supports your request for an extension and also your request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future.
>>  
>> Donna
>>  
>> Donna Austin
>> Chair, RySG
>>  
>> From: SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces at icann.org] On Behalf Of Katrina Sataki
>> Sent: Friday, April 12, 2019 12:55 AM
>> To: 'Goran Marby' <goran.marby at icann.org>
>> Cc: ccnso-council at icann.org; 'Chris Disspain' <chris at disspain.uk>; 'Nigel Roberts' <nigel.roberts at board.icann.org>; so-ac-sg-cleaders at icann.org
>> Subject: [ICANN Community Leaders] Accountability and community input on IRP standing panel
>>  
>> Dear G?ran:
>>  
>> In your blog post of 9 March 2019, you invited community inputs on the process for the selection of a standing panel to hear Independent Review Process (IRP) complaints. You included a series of questions, with a deadline for responses by 15 April 2019:
>>  
>> -          Qualifications for Standing Panelists: Are there specific qualifications that should be included? If so, what are they? Anything disqualifying? Should the SOs and ACs recommend qualifications? And if so, how?
>> -          Identifying a Slate of Well-Qualified Panelists: We?ve heard concerns from some members of the ICANN community as to whether the broader community has the appropriate experience and skill for this selection work, and have suggested the possibility that ICANN instead contract with experts to perform this vetting process. Should the community rely on expertise to help vet and recommend a final slate for the standing panel?
>> -          Board Approval of Panel Slate ? Further Questions: After there is a slate of well-qualified applicants, the Board must confirm the panel. If the Board has questions that might impact its confirmation, to whom should those questions be addressed? If experts are used to develop the slate, should the experts, the SOs and ACs, or some combination thereof be part of that conversation?
>> -          Future Selections: Should the process being designed today be reviewed for effectiveness after the first slating is completed, prior to making it standard operating procedure for future selection rounds?
>>  
>> The IRP, as you correctly stated, is an accountability mechanism arising from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for breaches of ICANN?s own policies, core values or because decisions have been made on the basis of incorrect information.
>>  
>> Matters of high importance that fall within scope include disputes involving the rights of the Empowered Community, enforcement of ICANN?s contractual rights with respect to the IANA Naming Function Contract, and claims regarding PTI service complaints by direct customers of the IANA naming functions (that are not resolved through mediation). The appointment of appropriately qualified and independent panellists who will be making these review decision is therefore a high concern to us.
>>  
>> Taking into account that:
>> 1)    the blog post was published right before ICANN64, when most volunteers are travelling or busy preparing for the meeting,
>> 2)    no corresponding public comments request has been published on the ICANN website,
>> 3)    no information about the request was published in ICANN Community Leadership Digest (the questions were first mentioned only on 11 April),
>> and to ensure that:
>> 1)    all community members are aware of the opportunity to provide input,
>> 2)    everyone has sufficient time to discuss the issue and submit their considerations,
>> 3)    the process is transparent and all comments are published in due time,
>> we would like to encourage you to re-launch the call for community inputs in accordance with the established procedures.
>>  
>> Furthermore, we request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future. While a blog post may remain to be a good tool for reminders, and senior staff commentary may encourage engagement and participation, they are no substitute for due process.
>>  
>> Yours sincerely,
>>  
>> Katrina Sataki
>> On behalf of the ccNSO Council
>> 
>> 
>> _______________________________________________
>> SO-AC-SG-CLeaders mailing list
>> SO-AC-SG-CLeaders at icann.org
>> https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders
> -- 
> ____________________________
> Graeme Bunton
> Director, Analytics & Policy
> Tucows Inc.
> PH: 416 535 0123 ext 1634
> <Attached Message Part>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190412/ed147f87/attachment.htm>

From farzaneh.badii at gmail.com  Fri Apr 12 23:25:35 2019
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Fri, 12 Apr 2019 22:25:35 +0200
Subject: [NCSG-PC] Fwd: Re: [ICANN Community Leaders] Accountability and
 community input on IRP standing panel
In-Reply-To: <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
References: <b06ff5ff-410c-1678-8471-293b470ed270@tucows.com>
 <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
Message-ID: <CAN1qJvDXnXpLRBzzda7486MGw3LYwVXFDQNPExmMijZq8=UOaw@mail.gmail.com>

(Observer )

Yes I agree it's important and we need to give them a strong comment in
regarding IRP related questions as well.

On Fri, Apr 12, 2019 at 8:40 PM Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> wrote:

> I think we should jump in and support this as well, any dissent?
>
> Steph
>
>
> -------- Forwarded Message --------
> Subject: Re: [ICANN Community Leaders] Accountability and community input
> on IRP standing panel
> Date: Fri, 12 Apr 2019 11:40:12 -0400
> From: Graeme Bunton <gbunton at tucows.com> <gbunton at tucows.com>
> To: so-ac-sg-cleaders at icann.org
>
> These are good points Katrina, thank you.
>
> The RrSG shares these process concerns too, and expressed them directly to
> GDD staff already.
>
> Graeme
> On 2019-04-12 11:12 a.m., Austin, Donna via SO-AC-SG-CLeaders wrote:
>
> Dear Katrina
>
>
>
> Thank you for raising this important issue. The RySG has similar concerns
> about important request for input being buried in blog posts as opposed to
> the familiar public comment process. We agree that the timing of this
> particular blog and request was unfortunate given it was, as you pointed
> out, posted right before ICANN64 when most people were travelling.
>
>
>
> The RySG supports your request for an extension and also your request that
> only one process for seeking community feedback, i.e. ICANN public comments
> procedure, is used in the future.
>
>
>
> Donna
>
>
>
> Donna Austin
>
> Chair, RySG
>
>
>
> *From:* SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces at icann.org
> <so-ac-sg-cleaders-bounces at icann.org>] *On Behalf Of *Katrina Sataki
> *Sent:* Friday, April 12, 2019 12:55 AM
> *To:* 'Goran Marby' <goran.marby at icann.org> <goran.marby at icann.org>
> *Cc:* ccnso-council at icann.org; 'Chris Disspain' <chris at disspain.uk>
> <chris at disspain.uk>; 'Nigel Roberts' <nigel.roberts at board.icann.org>
> <nigel.roberts at board.icann.org>; so-ac-sg-cleaders at icann.org
> *Subject:* [ICANN Community Leaders] Accountability and community input
> on IRP standing panel
>
>
>
> Dear G?ran:
>
>
>
> In your blog post of 9 March 2019, you invited community inputs on the
> process for the selection of a standing panel to hear Independent Review
> Process (IRP) complaints. You included a series of questions, with a
> deadline for responses by 15 April 2019:
>
>
>
> -          Qualifications for Standing Panelists: Are there specific
> qualifications that should be included? If so, what are they? Anything
> disqualifying? Should the SOs and ACs recommend qualifications? And if so,
> how?
>
> -          Identifying a Slate of Well-Qualified Panelists: We?ve heard
> concerns from some members of the ICANN community as to whether the broader
> community has the appropriate experience and skill for this selection work,
> and have suggested the possibility that ICANN instead contract with experts
> to perform this vetting process. Should the community rely on expertise to
> help vet and recommend a final slate for the standing panel?
>
> -          Board Approval of Panel Slate ? Further Questions: After there
> is a slate of well-qualified applicants, the Board must confirm the panel.
> If the Board has questions that might impact its confirmation, to whom
> should those questions be addressed? If experts are used to develop the
> slate, should the experts, the SOs and ACs, or some combination thereof be
> part of that conversation?
>
> -          Future Selections: Should the process being designed today be
> reviewed for effectiveness after the first slating is completed, prior to
> making it standard operating procedure for future selection rounds?
>
>
>
> The IRP, as you correctly stated, is an accountability mechanism arising
> from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for
> breaches of ICANN?s own policies, core values or because decisions have
> been made on the basis of incorrect information.
>
>
>
> Matters of high importance that fall within scope include disputes
> involving the rights of the Empowered Community, enforcement of ICANN?s
> contractual rights with respect to the IANA Naming Function Contract, and
> claims regarding PTI service complaints by direct customers of the IANA
> naming functions (that are not resolved through mediation). The appointment
> of appropriately qualified and independent panellists who will be making
> these review decision is therefore a high concern to us.
>
>
>
> Taking into account that:
>
> 1)    the blog post was published right before ICANN64, when most
> volunteers are travelling or busy preparing for the meeting,
>
> 2)    no corresponding public comments request has been published on the
> ICANN website,
>
> 3)    no information about the request was published in ICANN Community
> Leadership Digest (the questions were first mentioned only on 11 April),
>
> and to ensure that:
>
> 1)    all community members are aware of the opportunity to provide input,
>
> 2)    everyone has sufficient time to discuss the issue and submit their
> considerations,
>
> 3)    the process is transparent and all comments are published in due
> time,
>
> we would like to encourage you to re-launch the call for community inputs
> in accordance with the established procedures.
>
>
>
> Furthermore, we request that only one process for seeking community
> feedback, i.e. ICANN public comments procedure, is used in the future.
> While a blog post may remain to be a good tool for reminders, and senior
> staff commentary may encourage engagement and participation, they are no
> substitute for due process.
>
>
>
> Yours sincerely,
>
>
>
> Katrina Sataki
>
> On behalf of the ccNSO Council
>
> _______________________________________________
> SO-AC-SG-CLeaders mailing listSO-AC-SG-CLeaders at icann.orghttps://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders
>
> --
> ____________________________
> Graeme Bunton
> Director, Analytics & Policy
> Tucows Inc.
> PH: 416 535 0123 ext 1634
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-- 
Farzaneh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190412/7fd16452/attachment.htm>

From tatiana.tropina at gmail.com  Fri Apr 12 23:31:35 2019
From: tatiana.tropina at gmail.com (Tatiana Tropina)
Date: Fri, 12 Apr 2019 21:31:35 +0100
Subject: [NCSG-PC] Fwd: Re: [ICANN Community Leaders] Accountability and
 community input on IRP standing panel
In-Reply-To: <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
References: <b06ff5ff-410c-1678-8471-293b470ed270@tucows.com>
 <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
Message-ID: <CADxLtgfkGoqQ0cROnrG31d8Xsw71xzc+QamPWVJ+Y1k=gkTT3A@mail.gmail.com>

Full support from me.
Cheers,
Tanya

On Fri 12. Apr 2019 at 19:40, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> wrote:

> I think we should jump in and support this as well, any dissent?
>
> Steph
>
>
> -------- Forwarded Message --------
> Subject: Re: [ICANN Community Leaders] Accountability and community input
> on IRP standing panel
> Date: Fri, 12 Apr 2019 11:40:12 -0400
> From: Graeme Bunton <gbunton at tucows.com> <gbunton at tucows.com>
> To: so-ac-sg-cleaders at icann.org
>
> These are good points Katrina, thank you.
>
> The RrSG shares these process concerns too, and expressed them directly to
> GDD staff already.
>
> Graeme
> On 2019-04-12 11:12 a.m., Austin, Donna via SO-AC-SG-CLeaders wrote:
>
> Dear Katrina
>
>
>
> Thank you for raising this important issue. The RySG has similar concerns
> about important request for input being buried in blog posts as opposed to
> the familiar public comment process. We agree that the timing of this
> particular blog and request was unfortunate given it was, as you pointed
> out, posted right before ICANN64 when most people were travelling.
>
>
>
> The RySG supports your request for an extension and also your request that
> only one process for seeking community feedback, i.e. ICANN public comments
> procedure, is used in the future.
>
>
>
> Donna
>
>
>
> Donna Austin
>
> Chair, RySG
>
>
>
> *From:* SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces at icann.org
> <so-ac-sg-cleaders-bounces at icann.org>] *On Behalf Of *Katrina Sataki
> *Sent:* Friday, April 12, 2019 12:55 AM
> *To:* 'Goran Marby' <goran.marby at icann.org> <goran.marby at icann.org>
> *Cc:* ccnso-council at icann.org; 'Chris Disspain' <chris at disspain.uk>
> <chris at disspain.uk>; 'Nigel Roberts' <nigel.roberts at board.icann.org>
> <nigel.roberts at board.icann.org>; so-ac-sg-cleaders at icann.org
> *Subject:* [ICANN Community Leaders] Accountability and community input
> on IRP standing panel
>
>
>
> Dear G?ran:
>
>
>
> In your blog post of 9 March 2019, you invited community inputs on the
> process for the selection of a standing panel to hear Independent Review
> Process (IRP) complaints. You included a series of questions, with a
> deadline for responses by 15 April 2019:
>
>
>
> -          Qualifications for Standing Panelists: Are there specific
> qualifications that should be included? If so, what are they? Anything
> disqualifying? Should the SOs and ACs recommend qualifications? And if so,
> how?
>
> -          Identifying a Slate of Well-Qualified Panelists: We?ve heard
> concerns from some members of the ICANN community as to whether the broader
> community has the appropriate experience and skill for this selection work,
> and have suggested the possibility that ICANN instead contract with experts
> to perform this vetting process. Should the community rely on expertise to
> help vet and recommend a final slate for the standing panel?
>
> -          Board Approval of Panel Slate ? Further Questions: After there
> is a slate of well-qualified applicants, the Board must confirm the panel.
> If the Board has questions that might impact its confirmation, to whom
> should those questions be addressed? If experts are used to develop the
> slate, should the experts, the SOs and ACs, or some combination thereof be
> part of that conversation?
>
> -          Future Selections: Should the process being designed today be
> reviewed for effectiveness after the first slating is completed, prior to
> making it standard operating procedure for future selection rounds?
>
>
>
> The IRP, as you correctly stated, is an accountability mechanism arising
> from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for
> breaches of ICANN?s own policies, core values or because decisions have
> been made on the basis of incorrect information.
>
>
>
> Matters of high importance that fall within scope include disputes
> involving the rights of the Empowered Community, enforcement of ICANN?s
> contractual rights with respect to the IANA Naming Function Contract, and
> claims regarding PTI service complaints by direct customers of the IANA
> naming functions (that are not resolved through mediation). The appointment
> of appropriately qualified and independent panellists who will be making
> these review decision is therefore a high concern to us.
>
>
>
> Taking into account that:
>
> 1)    the blog post was published right before ICANN64, when most
> volunteers are travelling or busy preparing for the meeting,
>
> 2)    no corresponding public comments request has been published on the
> ICANN website,
>
> 3)    no information about the request was published in ICANN Community
> Leadership Digest (the questions were first mentioned only on 11 April),
>
> and to ensure that:
>
> 1)    all community members are aware of the opportunity to provide input,
>
> 2)    everyone has sufficient time to discuss the issue and submit their
> considerations,
>
> 3)    the process is transparent and all comments are published in due
> time,
>
> we would like to encourage you to re-launch the call for community inputs
> in accordance with the established procedures.
>
>
>
> Furthermore, we request that only one process for seeking community
> feedback, i.e. ICANN public comments procedure, is used in the future.
> While a blog post may remain to be a good tool for reminders, and senior
> staff commentary may encourage engagement and participation, they are no
> substitute for due process.
>
>
>
> Yours sincerely,
>
>
>
> Katrina Sataki
>
> On behalf of the ccNSO Council
>
> _______________________________________________
> SO-AC-SG-CLeaders mailing listSO-AC-SG-CLeaders at icann.orghttps://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders
>
> --
> ____________________________
> Graeme Bunton
> Director, Analytics & Policy
> Tucows Inc.
> PH: 416 535 0123 ext 1634
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190412/65fa3c1c/attachment.htm>

From rafik.dammak at gmail.com  Sat Apr 13 04:08:47 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Sat, 13 Apr 2019 10:08:47 +0900
Subject: [NCSG-PC] Draft Agenda for NCSG Monthly Policy Call 15th April
In-Reply-To: <CAH5sThmZKL3UCDRJ3xJ_L7wCoVxrEyjznQ55ktb04fS2CobDCw@mail.gmail.com>
References: <CAH5sTh=dibp_WPUiwuPGYx-3skb_H12u6Be4YMAz65C6HndyVw@mail.gmail.com>
 <CAH5sThnpaeE+6B01x53DGYTK4CGr2DbFtrR-HyOJ1YnVVPc4fQ@mail.gmail.com>
 <CAH5sThnAct3eNiGiYqX8FdD=sO49jMwVt2agdYZVaCi558kd+g@mail.gmail.com>
 <CAH5sThnCSih6WXi=8Z2KcOtio9L7VR-Wwh7h-7P5Fu41RQyWvA@mail.gmail.com>
 <CAH5sThmZKL3UCDRJ3xJ_L7wCoVxrEyjznQ55ktb04fS2CobDCw@mail.gmail.com>
Message-ID: <CAH5sThk2RuZ3Cf552rbwOPjD+VFuFQ6FhHDsB6EB1ghkStV8eg@mail.gmail.com>

Hi all,

I am sharing here the NCSG Policy call draft agenda.
For council agenda, the main topic would be the IGO-INGO curative rights
motion as we are going to vote on that. In term of policy discussion, we
will have more time since we are in transition phase between phase 1 and 2
of the EPDP. We might hear some updates from reps there about next steps
and phase 1 implementation (there is update scheduled during council call
too). For other PDPs, that will be under agenda item III.

Please review and feel free to suggest  addition/amendment to the agenda.

I. Introduction
II. GNSO Council Call Preparation

   - Council agenda:
   https://gnso.icann.org/sites/default/files/policy/2019/agenda/agenda-council-18apr19-en.pdf


III. Policy Update
- Policy topics:
  * PDPs & Review Teams Update
- Public comments status:  https://www.icann.org/public-comments#open-public
& list of volunteers
https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2019

IV. Others
   - ICANN65 planning
   - IRP standing panel

Best Regards,

Rafik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190413/a3e9d3de/attachment.htm>

From rafik.dammak at gmail.com  Sat Apr 13 04:19:01 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Sat, 13 Apr 2019 10:19:01 +0900
Subject: [NCSG-PC] Draft Agenda for NCSG Monthly Policy Call 15th April
In-Reply-To: <CAH5sThk2RuZ3Cf552rbwOPjD+VFuFQ6FhHDsB6EB1ghkStV8eg@mail.gmail.com>
References: <CAH5sTh=dibp_WPUiwuPGYx-3skb_H12u6Be4YMAz65C6HndyVw@mail.gmail.com>
 <CAH5sThnpaeE+6B01x53DGYTK4CGr2DbFtrR-HyOJ1YnVVPc4fQ@mail.gmail.com>
 <CAH5sThnAct3eNiGiYqX8FdD=sO49jMwVt2agdYZVaCi558kd+g@mail.gmail.com>
 <CAH5sThnCSih6WXi=8Z2KcOtio9L7VR-Wwh7h-7P5Fu41RQyWvA@mail.gmail.com>
 <CAH5sThmZKL3UCDRJ3xJ_L7wCoVxrEyjznQ55ktb04fS2CobDCw@mail.gmail.com>
 <CAH5sThk2RuZ3Cf552rbwOPjD+VFuFQ6FhHDsB6EB1ghkStV8eg@mail.gmail.com>
Message-ID: <CAH5sThmeVtxbpin_hjQcYX_LANcGvdS4-c14Vv5szW5F4AEUAg@mail.gmail.com>

correction the Policy Call is scheduled for the 16th April.

Best,

Rafik

Le sam. 13 avr. 2019 ? 10:08, Rafik Dammak <rafik.dammak at gmail.com> a
?crit :

> Hi all,
>
> I am sharing here the NCSG Policy call draft agenda.
> For council agenda, the main topic would be the IGO-INGO curative rights
> motion as we are going to vote on that. In term of policy discussion, we
> will have more time since we are in transition phase between phase 1 and 2
> of the EPDP. We might hear some updates from reps there about next steps
> and phase 1 implementation (there is update scheduled during council call
> too). For other PDPs, that will be under agenda item III.
>
> Please review and feel free to suggest  addition/amendment to the agenda.
>
> I. Introduction
> II. GNSO Council Call Preparation
>
>    - Council agenda:
>    https://gnso.icann.org/sites/default/files/policy/2019/agenda/agenda-council-18apr19-en.pdf
>
>
> III. Policy Update
> - Policy topics:
>   * PDPs & Review Teams Update
> - Public comments status:
> https://www.icann.org/public-comments#open-public  & list of volunteers
> https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2019
>
>
> IV. Others
>    - ICANN65 planning
>    - IRP standing panel
>
> Best Regards,
>
> Rafik
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190413/9f4cecae/attachment.htm>

From dgdorothydg at gmail.com  Sat Apr 13 09:59:16 2019
From: dgdorothydg at gmail.com (dorothy g)
Date: Sat, 13 Apr 2019 06:59:16 +0000
Subject: [NCSG-PC] Fwd: Re: [ICANN Community Leaders] Accountability and
 community input on IRP standing panel
In-Reply-To: <CADxLtgfkGoqQ0cROnrG31d8Xsw71xzc+QamPWVJ+Y1k=gkTT3A@mail.gmail.com>
References: <b06ff5ff-410c-1678-8471-293b470ed270@tucows.com>
 <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
 <CADxLtgfkGoqQ0cROnrG31d8Xsw71xzc+QamPWVJ+Y1k=gkTT3A@mail.gmail.com>
Message-ID: <CAH2xXE6HgAiesbbmeKy_bEOHyfB3DuvKuT9MTAoxf8otv5cacQ@mail.gmail.com>

Definitely but was the initial fault deliberate or from lack of awareness?
best

On Fri, Apr 12, 2019 at 8:31 PM Tatiana Tropina <tatiana.tropina at gmail.com>
wrote:

> Full support from me.
> Cheers,
> Tanya
>
> On Fri 12. Apr 2019 at 19:40, Stephanie Perrin <
> stephanie.perrin at mail.utoronto.ca> wrote:
>
>> I think we should jump in and support this as well, any dissent?
>>
>> Steph
>>
>>
>> -------- Forwarded Message --------
>> Subject: Re: [ICANN Community Leaders] Accountability and community
>> input on IRP standing panel
>> Date: Fri, 12 Apr 2019 11:40:12 -0400
>> From: Graeme Bunton <gbunton at tucows.com> <gbunton at tucows.com>
>> To: so-ac-sg-cleaders at icann.org
>>
>> These are good points Katrina, thank you.
>>
>> The RrSG shares these process concerns too, and expressed them directly
>> to GDD staff already.
>>
>> Graeme
>> On 2019-04-12 11:12 a.m., Austin, Donna via SO-AC-SG-CLeaders wrote:
>>
>> Dear Katrina
>>
>>
>>
>> Thank you for raising this important issue. The RySG has similar concerns
>> about important request for input being buried in blog posts as opposed to
>> the familiar public comment process. We agree that the timing of this
>> particular blog and request was unfortunate given it was, as you pointed
>> out, posted right before ICANN64 when most people were travelling.
>>
>>
>>
>> The RySG supports your request for an extension and also your request
>> that only one process for seeking community feedback, i.e. ICANN public
>> comments procedure, is used in the future.
>>
>>
>>
>> Donna
>>
>>
>>
>> Donna Austin
>>
>> Chair, RySG
>>
>>
>>
>> *From:* SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces at icann.org
>> <so-ac-sg-cleaders-bounces at icann.org>] *On Behalf Of *Katrina Sataki
>> *Sent:* Friday, April 12, 2019 12:55 AM
>> *To:* 'Goran Marby' <goran.marby at icann.org> <goran.marby at icann.org>
>> *Cc:* ccnso-council at icann.org; 'Chris Disspain' <chris at disspain.uk>
>> <chris at disspain.uk>; 'Nigel Roberts' <nigel.roberts at board.icann.org>
>> <nigel.roberts at board.icann.org>; so-ac-sg-cleaders at icann.org
>> *Subject:* [ICANN Community Leaders] Accountability and community input
>> on IRP standing panel
>>
>>
>>
>> Dear G?ran:
>>
>>
>>
>> In your blog post of 9 March 2019, you invited community inputs on the
>> process for the selection of a standing panel to hear Independent Review
>> Process (IRP) complaints. You included a series of questions, with a
>> deadline for responses by 15 April 2019:
>>
>>
>>
>> -          Qualifications for Standing Panelists: Are there specific
>> qualifications that should be included? If so, what are they? Anything
>> disqualifying? Should the SOs and ACs recommend qualifications? And if so,
>> how?
>>
>> -          Identifying a Slate of Well-Qualified Panelists: We?ve heard
>> concerns from some members of the ICANN community as to whether the broader
>> community has the appropriate experience and skill for this selection work,
>> and have suggested the possibility that ICANN instead contract with experts
>> to perform this vetting process. Should the community rely on expertise to
>> help vet and recommend a final slate for the standing panel?
>>
>> -          Board Approval of Panel Slate ? Further Questions: After
>> there is a slate of well-qualified applicants, the Board must confirm the
>> panel. If the Board has questions that might impact its confirmation, to
>> whom should those questions be addressed? If experts are used to develop
>> the slate, should the experts, the SOs and ACs, or some combination thereof
>> be part of that conversation?
>>
>> -          Future Selections: Should the process being designed today be
>> reviewed for effectiveness after the first slating is completed, prior to
>> making it standard operating procedure for future selection rounds?
>>
>>
>>
>> The IRP, as you correctly stated, is an accountability mechanism arising
>> from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for
>> breaches of ICANN?s own policies, core values or because decisions have
>> been made on the basis of incorrect information.
>>
>>
>>
>> Matters of high importance that fall within scope include disputes
>> involving the rights of the Empowered Community, enforcement of ICANN?s
>> contractual rights with respect to the IANA Naming Function Contract, and
>> claims regarding PTI service complaints by direct customers of the IANA
>> naming functions (that are not resolved through mediation). The appointment
>> of appropriately qualified and independent panellists who will be making
>> these review decision is therefore a high concern to us.
>>
>>
>>
>> Taking into account that:
>>
>> 1)    the blog post was published right before ICANN64, when most
>> volunteers are travelling or busy preparing for the meeting,
>>
>> 2)    no corresponding public comments request has been published on the
>> ICANN website,
>>
>> 3)    no information about the request was published in ICANN Community
>> Leadership Digest (the questions were first mentioned only on 11 April),
>>
>> and to ensure that:
>>
>> 1)    all community members are aware of the opportunity to provide input,
>>
>> 2)    everyone has sufficient time to discuss the issue and submit their
>> considerations,
>>
>> 3)    the process is transparent and all comments are published in due
>> time,
>>
>> we would like to encourage you to re-launch the call for community inputs
>> in accordance with the established procedures.
>>
>>
>>
>> Furthermore, we request that only one process for seeking community
>> feedback, i.e. ICANN public comments procedure, is used in the future.
>> While a blog post may remain to be a good tool for reminders, and senior
>> staff commentary may encourage engagement and participation, they are no
>> substitute for due process.
>>
>>
>>
>> Yours sincerely,
>>
>>
>>
>> Katrina Sataki
>>
>> On behalf of the ccNSO Council
>>
>> _______________________________________________
>> SO-AC-SG-CLeaders mailing listSO-AC-SG-CLeaders at icann.orghttps://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders
>>
>> --
>> ____________________________
>> Graeme Bunton
>> Director, Analytics & Policy
>> Tucows Inc.
>> PH: 416 535 0123 ext 1634
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>


-- 
Dorothy Gordon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190413/71ec1c41/attachment.htm>

From icann at ferdeline.com  Sat Apr 13 14:05:20 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Sat, 13 Apr 2019 11:05:20 +0000
Subject: [NCSG-PC] Fwd: Re: [ICANN Community Leaders] Accountability and
 community input on IRP standing panel
In-Reply-To: <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
References: <b06ff5ff-410c-1678-8471-293b470ed270@tucows.com>
 <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
Message-ID: <grG1RcSYWRkXWpe2tL4QFmCLvGfQySFallLDhI-RqRo7SO0kULVxahzmXarc9JHZ1aGh9V_5n8L8qEJLrERXSUFrYmFgOuwWnMdrQCZEWKI=@ferdeline.com>

I fully agree; hearing no objections, I will add a brief comment of support on the Council list.

Best wishes,

Ayden

??????? Original Message ???????
On Friday, April 12, 2019 8:39 PM, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> wrote:

> I think we should jump in and support this as well, any dissent?
>
> Steph
>
> -------- Forwarded Message --------
> Subject:	Re: [ICANN Community Leaders] Accountability and community input on IRP standing panel
> Date:	Fri, 12 Apr 2019 11:40:12 -0400
> From:	Graeme Bunton [<gbunton at tucows.com>](mailto:gbunton at tucows.com)
>
> To:	so-ac-sg-cleaders at icann.org
>
> These are good points Katrina, thank you.
>
> The RrSG shares these process concerns too, and expressed them directly to GDD staff already.
>
> Graeme
>
> On 2019-04-12 11:12 a.m., Austin, Donna via SO-AC-SG-CLeaders wrote:
>
>> Dear Katrina
>>
>> Thank you for raising this important issue. The RySG has similar concerns about important request for input being buried in blog posts as opposed to the familiar public comment process. We agree that the timing of this particular blog and request was unfortunate given it was, as you pointed out, posted right before ICANN64 when most people were travelling.
>>
>> The RySG supports your request for an extension and also your request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future.
>>
>> Donna
>>
>> Donna Austin
>>
>> Chair, RySG
>>
>> From: SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces at icann.org] On Behalf Of Katrina Sataki
>> Sent: Friday, April 12, 2019 12:55 AM
>> To: 'Goran Marby' [<goran.marby at icann.org>](mailto:goran.marby at icann.org)
>> Cc: ccnso-council at icann.org; 'Chris Disspain' [<chris at disspain.uk>](mailto:chris at disspain.uk); 'Nigel Roberts' [<nigel.roberts at board.icann.org>](mailto:nigel.roberts at board.icann.org); so-ac-sg-cleaders at icann.org
>> Subject: [ICANN Community Leaders] Accountability and community input on IRP standing panel
>>
>> Dear G?ran:
>>
>> In your blog post of 9 March 2019, you invited community inputs on the process for the selection of a standing panel to hear Independent Review Process (IRP) complaints. You included a series of questions, with a deadline for responses by 15 April 2019:
>>
>> -          Qualifications for Standing Panelists: Are there specific qualifications that should be included? If so, what are they? Anything disqualifying? Should the SOs and ACs recommend qualifications? And if so, how?
>>
>> -          Identifying a Slate of Well-Qualified Panelists: We?ve heard concerns from some members of the ICANN community as to whether the broader community has the appropriate experience and skill for this selection work, and have suggested the possibility that ICANN instead contract with experts to perform this vetting process. Should the community rely on expertise to help vet and recommend a final slate for the standing panel?
>>
>> -          Board Approval of Panel Slate ? Further Questions: After there is a slate of well-qualified applicants, the Board must confirm the panel. If the Board has questions that might impact its confirmation, to whom should those questions be addressed? If experts are used to develop the slate, should the experts, the SOs and ACs, or some combination thereof be part of that conversation?
>>
>> -          Future Selections: Should the process being designed today be reviewed for effectiveness after the first slating is completed, prior to making it standard operating procedure for future selection rounds?
>>
>> The IRP, as you correctly stated, is an accountability mechanism arising from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for breaches of ICANN?s own policies, core values or because decisions have been made on the basis of incorrect information.
>>
>> Matters of high importance that fall within scope include disputes involving the rights of the Empowered Community, enforcement of ICANN?s contractual rights with respect to the IANA Naming Function Contract, and claims regarding PTI service complaints by direct customers of the IANA naming functions (that are not resolved through mediation). The appointment of appropriately qualified and independent panellists who will be making these review decision is therefore a high concern to us.
>>
>> Taking into account that:
>>
>> 1)    the blog post was published right before ICANN64, when most volunteers are travelling or busy preparing for the meeting,
>>
>> 2)    no corresponding public comments request has been published on the ICANN website,
>>
>> 3)    no information about the request was published in ICANN Community Leadership Digest (the questions were first mentioned only on 11 April),
>>
>> and to ensure that:
>>
>> 1)    all community members are aware of the opportunity to provide input,
>>
>> 2)    everyone has sufficient time to discuss the issue and submit their considerations,
>>
>> 3)    the process is transparent and all comments are published in due time,
>>
>> we would like to encourage you to re-launch the call for community inputs in accordance with the established procedures.
>>
>> Furthermore, we request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future. While a blog post may remain to be a good tool for reminders, and senior staff commentary may encourage engagement and participation, they are no substitute for due process.
>>
>> Yours sincerely,
>>
>> Katrina Sataki
>>
>> On behalf of the ccNSO Council
>>
>> _______________________________________________
>> SO-AC-SG-CLeaders mailing list
>> SO-AC-SG-CLeaders at icann.org
>>
>> https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders
>
> --
> ____________________________
> Graeme Bunton
> Director, Analytics & Policy
> Tucows Inc.
> PH: 416 535 0123 ext 1634
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190413/afe0747a/attachment.htm>

From icann at ferdeline.com  Sat Apr 13 14:10:58 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Sat, 13 Apr 2019 11:10:58 +0000
Subject: [NCSG-PC] Draft Agenda for NCSG Monthly Policy Call 15th April
In-Reply-To: <CAH5sThmeVtxbpin_hjQcYX_LANcGvdS4-c14Vv5szW5F4AEUAg@mail.gmail.com>
References: <CAH5sTh=dibp_WPUiwuPGYx-3skb_H12u6Be4YMAz65C6HndyVw@mail.gmail.com>
 <CAH5sThnpaeE+6B01x53DGYTK4CGr2DbFtrR-HyOJ1YnVVPc4fQ@mail.gmail.com>
 <CAH5sThnAct3eNiGiYqX8FdD=sO49jMwVt2agdYZVaCi558kd+g@mail.gmail.com>
 <CAH5sThnCSih6WXi=8Z2KcOtio9L7VR-Wwh7h-7P5Fu41RQyWvA@mail.gmail.com>
 <CAH5sThmZKL3UCDRJ3xJ_L7wCoVxrEyjznQ55ktb04fS2CobDCw@mail.gmail.com>
 <CAH5sThk2RuZ3Cf552rbwOPjD+VFuFQ6FhHDsB6EB1ghkStV8eg@mail.gmail.com>
 <CAH5sThmeVtxbpin_hjQcYX_LANcGvdS4-c14Vv5szW5F4AEUAg@mail.gmail.com>
Message-ID: <vUQd_HpTZXsR--3WND2rHce4Frq9ptY-zSZjiZbZY_KjBGLJ_oY8TDNN1ExV_n5fFK5szRCQke58TqG6t6k8zG6DhA9o_-fl33nr1rMRXpA=@ferdeline.com>

Agenda looks good to me. Thanks.

- Ayden

??????? Original Message ???????
On Saturday, April 13, 2019 3:19 AM, Rafik Dammak <rafik.dammak at gmail.com> wrote:

> correction the Policy Call is scheduled for the 16th April.
>
> Best,
>
> Rafik
>
> Le sam. 13 avr. 2019 ? 10:08, Rafik Dammak <rafik.dammak at gmail.com> a ?crit :
>
>> Hi all,
>>
>> I am sharing here the NCSG Policy call draft agenda.
>> For council agenda, the main topic would be the IGO-INGO curative rights motion as we are going to vote on that. In term of policy discussion, we will have more time since we are in transition phase between phase 1 and 2 of the EPDP. We might hear some updates from reps there about next steps and phase 1 implementation (there is update scheduled during council call too). For other PDPs, that will be under agenda item III.
>>
>> Please review and feel free to suggest  addition/amendment to the agenda.
>>
>> I. Introduction
>> II. GNSO Council Call Preparation
>>
>> - Council agenda: https://gnso.icann.org/sites/default/files/policy/2019/agenda/agenda-council-18apr19-en.pdf
>>
>> III. Policy Update
>> - Policy topics:
>>   * PDPs & Review Teams Update
>> - Public comments status:  https://www.icann.org/public-comments#open-public  & list of volunteers https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2019
>>
>> IV. Others
>>    - ICANN65 planning
>>    - IRP standing panel
>>
>> Best Regards,
>>
>> Rafik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190413/6ef309a5/attachment.htm>

From icann at ferdeline.com  Sat Apr 13 14:42:35 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Sat, 13 Apr 2019 11:42:35 +0000
Subject: [NCSG-PC] Fw: [ccwg-internet-governance] IGF deadlines extended
 with 48 hours
In-Reply-To: <39d99d905ef3476da9423613e807ee4a@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG>
References: <39d99d905ef3476da9423613e807ee4a@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG>
Message-ID: <b4wuIjFA5ZpO2dwUdGgmmEwtUGs9WsYPpN9vjPSbmkxFnFztef9fhP-PFB4_1nfDud6CQGkG7RGT33GRiN2u5p3DQY2_2X7HUJVw44bjquI=@ferdeline.com>

FYI - deadline for IGF proposals is now extended until tomorrow, in case we are looking to submit something.

- Ayden

??????? Original Message ???????
On Thursday, April 11, 2019 10:17 AM, Veni Markovski <veni.markovski at icann.org> wrote:

> Hi.
>
> Just so that you know, this is from Lynn just now:
>
> I THINK YOU ARE PROBABLY ALL AWARE THAT WE EXTENDED THE DEADLINE FROM TOMORROW TO SUNDAY, 2359 UTC TO BE EXACT.
>
> And on the website:
>
> The [Call for IGF Workshop Proposals](https://www.intgovforum.org/multilingual/content/igf-2019-call-for-workshop-proposals-0) is EXTENDED until 14 April 2019.
>
> The [Call for DC Sessions](https://www.intgovforum.org/multilingual/content/igf-2019-call-for-dynamic-coalition-dc-sessions) is EXTENDED until 14 April 2019.
>
> The [Call for Open Forums](https://www.intgovforum.org/multilingual/content/igf-2019-call-for-open-forums) is EXTENDED until 14 April 2019.
>
> The [Call for Pre-Events](https://www.intgovforum.org/multilingual/content/igf-2019-call-for-pre-events-day-0-events) is EXTENDED until 14 April 2019.
>
> The [Call for Booths](https://www.intgovforum.org/multilingual/content/igf-2019-village-call-for-booths) is EXTENDED until 14 April 2019.
>
> Hope this is useful for folks, working on the workshop and other proposals. They extended it in response to some folks asking me if that would be possible, given the fact the deadline was end of Friday, and the UN would not review the applications during the weekend. I conveyed the question to the IGF Secretariat during day one of the current MAG meeting, and they agreed it makes sense.
>
> Best regards from Geneva.
>
> v/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190413/b333d70f/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Sat Apr 13 17:13:02 2019
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Sat, 13 Apr 2019 14:13:02 +0000
Subject: [NCSG-PC] Fwd: Re: [ICANN Community Leaders] Accountability and
 community input on IRP standing panel
In-Reply-To: <CAH2xXE6HgAiesbbmeKy_bEOHyfB3DuvKuT9MTAoxf8otv5cacQ@mail.gmail.com>
References: <b06ff5ff-410c-1678-8471-293b470ed270@tucows.com>
 <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
 <CADxLtgfkGoqQ0cROnrG31d8Xsw71xzc+QamPWVJ+Y1k=gkTT3A@mail.gmail.com>
 <CAH2xXE6HgAiesbbmeKy_bEOHyfB3DuvKuT9MTAoxf8otv5cacQ@mail.gmail.com>
Message-ID: <67d28714-8895-f5ba-06d4-970b81170d5c@mail.utoronto.ca>

The problem is that they are seeking comments on a blog post.  Some of us only follow the calls for comments....and frankly, there should be only one formal process for comments, we cannot start looking at every wretched blog or wiki or utterance coming from ICANN.org.

So we are just insisting on proper process, as would be expected from an MS organization.

Cheers Stephanie

On 2019-04-13 02:59, dorothy g wrote:
Definitely but was the initial fault deliberate or from lack of awareness?
best

On Fri, Apr 12, 2019 at 8:31 PM Tatiana Tropina <tatiana.tropina at gmail.com<mailto:tatiana.tropina at gmail.com>> wrote:
Full support from me.
Cheers,
Tanya

On Fri 12. Apr 2019 at 19:40, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca<mailto:stephanie.perrin at mail.utoronto.ca>> wrote:

I think we should jump in and support this as well, any dissent?

Steph


-------- Forwarded Message --------
Subject:        Re: [ICANN Community Leaders] Accountability and community input on IRP standing panel
Date:   Fri, 12 Apr 2019 11:40:12 -0400
From:   Graeme Bunton <gbunton at tucows.com><mailto:gbunton at tucows.com>
To:     so-ac-sg-cleaders at icann.org<mailto:so-ac-sg-cleaders at icann.org>



These are good points Katrina, thank you.

The RrSG shares these process concerns too, and expressed them directly to GDD staff already.

Graeme

On 2019-04-12 11:12 a.m., Austin, Donna via SO-AC-SG-CLeaders wrote:
Dear Katrina

Thank you for raising this important issue. The RySG has similar concerns about important request for input being buried in blog posts as opposed to the familiar public comment process. We agree that the timing of this particular blog and request was unfortunate given it was, as you pointed out, posted right before ICANN64 when most people were travelling.

The RySG supports your request for an extension and also your request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future.

Donna

Donna Austin
Chair, RySG

From: SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces at icann.org] On Behalf Of Katrina Sataki
Sent: Friday, April 12, 2019 12:55 AM
To: 'Goran Marby' <goran.marby at icann.org><mailto:goran.marby at icann.org>
Cc: ccnso-council at icann.org<mailto:ccnso-council at icann.org>; 'Chris Disspain' <chris at disspain.uk><mailto:chris at disspain.uk>; 'Nigel Roberts' <nigel.roberts at board.icann.org><mailto:nigel.roberts at board.icann.org>; so-ac-sg-cleaders at icann.org<mailto:so-ac-sg-cleaders at icann.org>
Subject: [ICANN Community Leaders] Accountability and community input on IRP standing panel

Dear G?ran:

In your blog post of 9 March 2019, you invited community inputs on the process for the selection of a standing panel to hear Independent Review Process (IRP) complaints. You included a series of questions, with a deadline for responses by 15 April 2019:


-          Qualifications for Standing Panelists: Are there specific qualifications that should be included? If so, what are they? Anything disqualifying? Should the SOs and ACs recommend qualifications? And if so, how?

-          Identifying a Slate of Well-Qualified Panelists: We?ve heard concerns from some members of the ICANN community as to whether the broader community has the appropriate experience and skill for this selection work, and have suggested the possibility that ICANN instead contract with experts to perform this vetting process. Should the community rely on expertise to help vet and recommend a final slate for the standing panel?

-          Board Approval of Panel Slate ? Further Questions: After there is a slate of well-qualified applicants, the Board must confirm the panel. If the Board has questions that might impact its confirmation, to whom should those questions be addressed? If experts are used to develop the slate, should the experts, the SOs and ACs, or some combination thereof be part of that conversation?

-          Future Selections: Should the process being designed today be reviewed for effectiveness after the first slating is completed, prior to making it standard operating procedure for future selection rounds?

The IRP, as you correctly stated, is an accountability mechanism arising from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for breaches of ICANN?s own policies, core values or because decisions have been made on the basis of incorrect information.

Matters of high importance that fall within scope include disputes involving the rights of the Empowered Community, enforcement of ICANN?s contractual rights with respect to the IANA Naming Function Contract, and claims regarding PTI service complaints by direct customers of the IANA naming functions (that are not resolved through mediation). The appointment of appropriately qualified and independent panellists who will be making these review decision is therefore a high concern to us.

Taking into account that:
1)    the blog post was published right before ICANN64, when most volunteers are travelling or busy preparing for the meeting,
2)    no corresponding public comments request has been published on the ICANN website,
3)    no information about the request was published in ICANN Community Leadership Digest (the questions were first mentioned only on 11 April),
and to ensure that:
1)    all community members are aware of the opportunity to provide input,
2)    everyone has sufficient time to discuss the issue and submit their considerations,
3)    the process is transparent and all comments are published in due time,
we would like to encourage you to re-launch the call for community inputs in accordance with the established procedures.

Furthermore, we request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future. While a blog post may remain to be a good tool for reminders, and senior staff commentary may encourage engagement and participation, they are no substitute for due process.

Yours sincerely,

Katrina Sataki
On behalf of the ccNSO Council



_______________________________________________
SO-AC-SG-CLeaders mailing list
SO-AC-SG-CLeaders at icann.org<mailto:SO-AC-SG-CLeaders at icann.org>
https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders


--
____________________________
Graeme Bunton
Director, Analytics & Policy
Tucows Inc.
PH: 416 535 0123 ext 1634

_______________________________________________
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
_______________________________________________
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


--
Dorothy Gordon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190413/32c20a87/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Sat Apr 13 17:17:07 2019
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Sat, 13 Apr 2019 14:17:07 +0000
Subject: [NCSG-PC] Fwd: Re: [ICANN Community Leaders] Accountability and
 community input on IRP standing panel
In-Reply-To: <grG1RcSYWRkXWpe2tL4QFmCLvGfQySFallLDhI-RqRo7SO0kULVxahzmXarc9JHZ1aGh9V_5n8L8qEJLrERXSUFrYmFgOuwWnMdrQCZEWKI=@ferdeline.com>
References: <b06ff5ff-410c-1678-8471-293b470ed270@tucows.com>
 <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
 <grG1RcSYWRkXWpe2tL4QFmCLvGfQySFallLDhI-RqRo7SO0kULVxahzmXarc9JHZ1aGh9V_5n8L8qEJLrERXSUFrYmFgOuwWnMdrQCZEWKI=@ferdeline.com>
Message-ID: <5f24344a-f3a0-f76b-49d1-54b3bd6f3e07@mail.utoronto.ca>

and I did the same on the leaders planning list, indicating you had commented at COuncil.

thanks!

Steph

On 2019-04-13 07:05, Ayden F?rdeline wrote:
I fully agree; hearing no objections, I will add a brief comment of support on the Council list.

Best wishes,

Ayden


??????? Original Message ???????
On Friday, April 12, 2019 8:39 PM, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca><mailto:stephanie.perrin at mail.utoronto.ca> wrote:


I think we should jump in and support this as well, any dissent?

Steph


-------- Forwarded Message --------
Subject:
        Re: [ICANN Community Leaders] Accountability and community input on IRP standing panel

Date:
        Fri, 12 Apr 2019 11:40:12 -0400

From:
        Graeme Bunton <gbunton at tucows.com><mailto:gbunton at tucows.com>

To:
        so-ac-sg-cleaders at icann.org<mailto:so-ac-sg-cleaders at icann.org>




These are good points Katrina, thank you.

The RrSG shares these process concerns too, and expressed them directly to GDD staff already.

Graeme

On 2019-04-12 11:12 a.m., Austin, Donna via SO-AC-SG-CLeaders wrote:

Dear Katrina



Thank you for raising this important issue. The RySG has similar concerns about important request for input being buried in blog posts as opposed to the familiar public comment process. We agree that the timing of this particular blog and request was unfortunate given it was, as you pointed out, posted right before ICANN64 when most people were travelling.



The RySG supports your request for an extension and also your request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future.



Donna



Donna Austin

Chair, RySG



From: SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces at icann.org] On Behalf Of Katrina Sataki
Sent: Friday, April 12, 2019 12:55 AM
To: 'Goran Marby' <goran.marby at icann.org><mailto:goran.marby at icann.org>
Cc: ccnso-council at icann.org<mailto:ccnso-council at icann.org>; 'Chris Disspain' <chris at disspain.uk><mailto:chris at disspain.uk>; 'Nigel Roberts' <nigel.roberts at board.icann.org><mailto:nigel.roberts at board.icann.org>; so-ac-sg-cleaders at icann.org<mailto:so-ac-sg-cleaders at icann.org>
Subject: [ICANN Community Leaders] Accountability and community input on IRP standing panel



Dear G?ran:



In your blog post of 9 March 2019, you invited community inputs on the process for the selection of a standing panel to hear Independent Review Process (IRP) complaints. You included a series of questions, with a deadline for responses by 15 April 2019:



-          Qualifications for Standing Panelists: Are there specific qualifications that should be included? If so, what are they? Anything disqualifying? Should the SOs and ACs recommend qualifications? And if so, how?

-          Identifying a Slate of Well-Qualified Panelists: We?ve heard concerns from some members of the ICANN community as to whether the broader community has the appropriate experience and skill for this selection work, and have suggested the possibility that ICANN instead contract with experts to perform this vetting process. Should the community rely on expertise to help vet and recommend a final slate for the standing panel?

-          Board Approval of Panel Slate ? Further Questions: After there is a slate of well-qualified applicants, the Board must confirm the panel. If the Board has questions that might impact its confirmation, to whom should those questions be addressed? If experts are used to develop the slate, should the experts, the SOs and ACs, or some combination thereof be part of that conversation?

-          Future Selections: Should the process being designed today be reviewed for effectiveness after the first slating is completed, prior to making it standard operating procedure for future selection rounds?



The IRP, as you correctly stated, is an accountability mechanism arising from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for breaches of ICANN?s own policies, core values or because decisions have been made on the basis of incorrect information.



Matters of high importance that fall within scope include disputes involving the rights of the Empowered Community, enforcement of ICANN?s contractual rights with respect to the IANA Naming Function Contract, and claims regarding PTI service complaints by direct customers of the IANA naming functions (that are not resolved through mediation). The appointment of appropriately qualified and independent panellists who will be making these review decision is therefore a high concern to us.



Taking into account that:

1)    the blog post was published right before ICANN64, when most volunteers are travelling or busy preparing for the meeting,

2)    no corresponding public comments request has been published on the ICANN website,

3)    no information about the request was published in ICANN Community Leadership Digest (the questions were first mentioned only on 11 April),

and to ensure that:

1)    all community members are aware of the opportunity to provide input,

2)    everyone has sufficient time to discuss the issue and submit their considerations,

3)    the process is transparent and all comments are published in due time,

we would like to encourage you to re-launch the call for community inputs in accordance with the established procedures.



Furthermore, we request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future. While a blog post may remain to be a good tool for reminders, and senior staff commentary may encourage engagement and participation, they are no substitute for due process.



Yours sincerely,



Katrina Sataki

On behalf of the ccNSO Council


_______________________________________________
SO-AC-SG-CLeaders mailing list
SO-AC-SG-CLeaders at icann.org<mailto:SO-AC-SG-CLeaders at icann.org>
https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders



--
____________________________
Graeme Bunton
Director, Analytics & Policy
Tucows Inc.
PH: 416 535 0123 ext 1634


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190413/be0b21ab/attachment.htm>

From icann at ferdeline.com  Sat Apr 13 17:19:16 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Sat, 13 Apr 2019 14:19:16 +0000
Subject: [NCSG-PC] Fwd: Re: [ICANN Community Leaders] Accountability and
 community input on IRP standing panel
In-Reply-To: <5f24344a-f3a0-f76b-49d1-54b3bd6f3e07@mail.utoronto.ca>
References: <b06ff5ff-410c-1678-8471-293b470ed270@tucows.com>
 <30012dbd-1a49-59af-7156-32a9ad8937d5@mail.utoronto.ca>
 <grG1RcSYWRkXWpe2tL4QFmCLvGfQySFallLDhI-RqRo7SO0kULVxahzmXarc9JHZ1aGh9V_5n8L8qEJLrERXSUFrYmFgOuwWnMdrQCZEWKI=@ferdeline.com>
 <5f24344a-f3a0-f76b-49d1-54b3bd6f3e07@mail.utoronto.ca>
Message-ID: <E5AvObeeacjBcQgdZocDeKTMvLLc5Y4rlvUKnZ8xVQmsncqe43RhbjM0u-jtvYKtwHMM9n5IHuuxLJHpyq6ck-4NxHB7u3ciYL1vhPSeYzU=@ferdeline.com>

Thanks Stephanie,

This is so upsetting. ICANN org continually plays us (the community) for fools... they have no respect for us, and to a large degree I can understand why, given what we in the community let them get away with.

- Ayden

??????? Original Message ???????
On Saturday, April 13, 2019 4:17 PM, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> wrote:

> and I did the same on the leaders planning list, indicating you had commented at COuncil.
>
> thanks!
>
> Steph
>
> On 2019-04-13 07:05, Ayden F?rdeline wrote:
>
>> I fully agree; hearing no objections, I will add a brief comment of support on the Council list.
>>
>> Best wishes,
>>
>> Ayden
>>
>> ??????? Original Message ???????
>> On Friday, April 12, 2019 8:39 PM, Stephanie Perrin [<stephanie.perrin at mail.utoronto.ca>](mailto:stephanie.perrin at mail.utoronto.ca) wrote:
>>
>>> I think we should jump in and support this as well, any dissent?
>>>
>>> Steph
>>>
>>> -------- Forwarded Message --------
>>> Subject:	Re: [ICANN Community Leaders] Accountability and community input on IRP standing panel
>>> Date:	Fri, 12 Apr 2019 11:40:12 -0400
>>> From:	Graeme Bunton [<gbunton at tucows.com>](mailto:gbunton at tucows.com)
>>>
>>> To:	so-ac-sg-cleaders at icann.org
>>>
>>> These are good points Katrina, thank you.
>>>
>>> The RrSG shares these process concerns too, and expressed them directly to GDD staff already.
>>>
>>> Graeme
>>>
>>> On 2019-04-12 11:12 a.m., Austin, Donna via SO-AC-SG-CLeaders wrote:
>>>
>>>> Dear Katrina
>>>>
>>>> Thank you for raising this important issue. The RySG has similar concerns about important request for input being buried in blog posts as opposed to the familiar public comment process. We agree that the timing of this particular blog and request was unfortunate given it was, as you pointed out, posted right before ICANN64 when most people were travelling.
>>>>
>>>> The RySG supports your request for an extension and also your request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future.
>>>>
>>>> Donna
>>>>
>>>> Donna Austin
>>>>
>>>> Chair, RySG
>>>>
>>>> From: SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces at icann.org] On Behalf Of Katrina Sataki
>>>> Sent: Friday, April 12, 2019 12:55 AM
>>>> To: 'Goran Marby' [<goran.marby at icann.org>](mailto:goran.marby at icann.org)
>>>> Cc: ccnso-council at icann.org; 'Chris Disspain' [<chris at disspain.uk>](mailto:chris at disspain.uk); 'Nigel Roberts' [<nigel.roberts at board.icann.org>](mailto:nigel.roberts at board.icann.org); so-ac-sg-cleaders at icann.org
>>>> Subject: [ICANN Community Leaders] Accountability and community input on IRP standing panel
>>>>
>>>> Dear G?ran:
>>>>
>>>> In your blog post of 9 March 2019, you invited community inputs on the process for the selection of a standing panel to hear Independent Review Process (IRP) complaints. You included a series of questions, with a deadline for responses by 15 April 2019:
>>>>
>>>> -          Qualifications for Standing Panelists: Are there specific qualifications that should be included? If so, what are they? Anything disqualifying? Should the SOs and ACs recommend qualifications? And if so, how?
>>>>
>>>> -          Identifying a Slate of Well-Qualified Panelists: We?ve heard concerns from some members of the ICANN community as to whether the broader community has the appropriate experience and skill for this selection work, and have suggested the possibility that ICANN instead contract with experts to perform this vetting process. Should the community rely on expertise to help vet and recommend a final slate for the standing panel?
>>>>
>>>> -          Board Approval of Panel Slate ? Further Questions: After there is a slate of well-qualified applicants, the Board must confirm the panel. If the Board has questions that might impact its confirmation, to whom should those questions be addressed? If experts are used to develop the slate, should the experts, the SOs and ACs, or some combination thereof be part of that conversation?
>>>>
>>>> -          Future Selections: Should the process being designed today be reviewed for effectiveness after the first slating is completed, prior to making it standard operating procedure for future selection rounds?
>>>>
>>>> The IRP, as you correctly stated, is an accountability mechanism arising from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for breaches of ICANN?s own policies, core values or because decisions have been made on the basis of incorrect information.
>>>>
>>>> Matters of high importance that fall within scope include disputes involving the rights of the Empowered Community, enforcement of ICANN?s contractual rights with respect to the IANA Naming Function Contract, and claims regarding PTI service complaints by direct customers of the IANA naming functions (that are not resolved through mediation). The appointment of appropriately qualified and independent panellists who will be making these review decision is therefore a high concern to us.
>>>>
>>>> Taking into account that:
>>>>
>>>> 1)    the blog post was published right before ICANN64, when most volunteers are travelling or busy preparing for the meeting,
>>>>
>>>> 2)    no corresponding public comments request has been published on the ICANN website,
>>>>
>>>> 3)    no information about the request was published in ICANN Community Leadership Digest (the questions were first mentioned only on 11 April),
>>>>
>>>> and to ensure that:
>>>>
>>>> 1)    all community members are aware of the opportunity to provide input,
>>>>
>>>> 2)    everyone has sufficient time to discuss the issue and submit their considerations,
>>>>
>>>> 3)    the process is transparent and all comments are published in due time,
>>>>
>>>> we would like to encourage you to re-launch the call for community inputs in accordance with the established procedures.
>>>>
>>>> Furthermore, we request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future. While a blog post may remain to be a good tool for reminders, and senior staff commentary may encourage engagement and participation, they are no substitute for due process.
>>>>
>>>> Yours sincerely,
>>>>
>>>> Katrina Sataki
>>>>
>>>> On behalf of the ccNSO Council
>>>>
>>>> _______________________________________________
>>>> SO-AC-SG-CLeaders mailing list
>>>> SO-AC-SG-CLeaders at icann.org
>>>>
>>>> https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders
>>>
>>> --
>>> ____________________________
>>> Graeme Bunton
>>> Director, Analytics & Policy
>>> Tucows Inc.
>>> PH: 416 535 0123 ext 1634
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190413/5f9f7080/attachment.htm>

From icann at ferdeline.com  Sat Apr 13 18:06:44 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Sat, 13 Apr 2019 15:06:44 +0000
Subject: [NCSG-PC] Fw: Re: [ccwg-internet-governance] Action Items re:
 Organisation of an IGF Workshop (was: Re: CCWG-IG call of Thursday,
 March 28)
In-Reply-To: <6457c9bc9e3f47e193c8fa053f4097f4@verisign.com>
References: <DD37CC04-25FA-4BD6-B12A-3D0341DEEC59@icann.org>
 <bc1d1d4f-5a1e-bd2f-637a-33fd3fe07f1e@gih.com>
 <5446a274-0553-f7ae-e8ea-373954784f2a@gih.com>
 <DM6PR05MB63323979B7B78524BCEBE643D3510@DM6PR05MB6332.namprd05.prod.outlook.com>
 <e8b9b64b-3174-1ac0-eb2d-d5679972bb18@gih.com>
 <C3C31383-3E6A-4F0D-A30F-2686483C275C@icann.org>
 <6457c9bc9e3f47e193c8fa053f4097f4@verisign.com>
Message-ID: <oixR4RKi64f75b98qdLJEQ6XhboxbQk74ziwhL4VdimtOZ5UEESLTHXUPU4S1uzKhEXPlb7-sWeEthBhZvsiL5qbU3KLmKzsJeW6vVos29E=@ferdeline.com>

Important email from the Council chair - good intervention on his part.

- Ayden

??????? Original Message ???????
On Thursday, April 11, 2019 10:46 PM, Drazek, Keith via ccwg-internet-governance <ccwg-internet-governance at icann.org> wrote:

> Hi all,
>
> I have concerns about the CCEG-IG and ICANN Org proposing an IGF workshop on SSR (or on any subject) without adequate coordination and vetting of the proposal, panelists, subject matter, and messaging. I was happy to have been able to jump in and help with today?s WSIS Forum session on the EPDP, but I think we need to be more deliberate in our planning and decision-making around externally-facing engagements. I am not comfortable with proposing this session without sufficient preparation and agreement, neither of which I?ve seen. We?re probably better off not proposing a session at all, rather than scrambling to fit something in at the 11th hour.
>
> Regards,
>
> Keith
>
> From: ccwg-internet-governance <ccwg-internet-governance-bounces at icann.org> On Behalf Of Nigel Hickson
> Sent: Thursday, April 11, 2019 5:41 AM
> To: Olivier MJ Cr?pin-Leblond <ocl at gih.com>; Marilyn Cade <marilynscade at hotmail.com>; ccwg-internet-governance at icann.org
> Subject: [EXTERNAL] Re: [ccwg-internet-governance] Action Items re: Organisation of an IGF Workshop (was: Re: CCWG-IG call of Thursday, March 28)
>
> Colleagues
>
> Good morning.  Let me just note a few points:
>
> 1. If the CCWG decides to go forward with Option 2 (as outlined below); we would need;
>
> (i) A few paragraphs describing the objective of Workshop and what it would cover;
>
> (ii) The identification of at least 3-4 diverse panellists that have agreed to take part;
>
> 2. We need to conclude this by close tomorrow to allow submission through the IGF site etc;
>
> best
>
> Nigel
>
> From: ccwg-internet-governance <ccwg-internet-governance-bounces at icann.org> on behalf of Olivier MJ Crepin-Leblond <ocl at gih.com>
> Date: Thursday, 11 April 2019 at 11:15
> To: Marilyn Cade <marilynscade at hotmail.com>, ccwg <ccwg-internet-governance at icann.org>
> Subject: Re: [ccwg-internet-governance] Action Items re: Organisation of an IGF Workshop (was: Re: CCWG-IG call of Thursday, March 28)
>
> Dear colleagues,
>
> thank you for your input. I have received further input offline and need to also let you know that there have been some changes to our WSIS Forum session.
> Originally we thought that we could get a discussion going on the results of EPDP Phase 1. However we were faced with a lack of people being at WSIS, thus leading to an unbalanced panel. I understand that since Phase 1 is intimately connected to Phase 2 and since this has been a very sensitive topic, we have had to change the format so as to avoid interfering with the process. Thus the WSIS Forum proposal has been changed to an informational session whereas we'll have the GNSO Chair Keith Drazek reporting remotely on how the GNSO creates policy, how an EPDP is different from a PDP. We'll then have Phase 1 Chair Kurt Pritz reporting on the process of the EPDP Phase 1 as well as its main findings. Then an ICANN member of Staff Elena Plexida, explaining the role of the TSG, and finally I'll provide a list of the Phase 2 issues.
>
> Given this change, this also affects any proposal we make for IGF. With the Phase 2 issues being what they are, there is no guarantee today that Phase 2 work will have been concluded by the time the IGF takes place. As a result, it would probably be unwise to open up a debate outside the EPDP Phase 2 group, that is outward facing and that could complicate the search for consensus within the EPDP. For this reason, and given the sensitivities revolving about this topic, going for Option 2 with a focus on SSR, thus inviting SSAC and RSSAC, as well as OCTO to discuss threats to the Global Internet's system identifiers, given the recent OCTO Press releases, sounds like a good idea.
> [https://www.icann.org/news/announcement-2019-02-04-en [icann.org]](https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2019-2D02-2D04-2Den&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=8imFzo8oKctQYlfEgaj0m1z7awTUPGsi4iiGj_bg0Ug&e=)
> [https://www.icann.org/news/announcement-2019-02-15-en [icann.org]](https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2019-2D02-2D15-2Den&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=GiLvGebyWKCSK9dmsa6J7xqedrlwFcr3rd5dRhfmgO0&e=)
> [https://www.icann.org/news/announcement-2019-02-22-en [icann.org]](https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2019-2D02-2D22-2Den&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=vZEh4mOHy2oy_GE7YEFTXg4y7cEBcM9PqFPrOC8FZiI&e=)
>
> Please comment as soon as possible, including suggesting speakers. We have until this coming Sunday to submit the proposal, but would really like to have a first draft out by tomorrow, Friday 12th April.
> Kindest regards,
>
> Olivier
>
> On 05/04/2019 11:56, Marilyn Cade wrote:
>
>> As I nominated, and strongly support Option 2, with a focus on SSR, I will try to again champion that and explain why.
>>
>> I fail to see the benefit of having a status update about EPDP -- and that is in fact, not what the IGF is supposed to be about.  Workshop criteria requires that there be all views, and increasingly, there is an effort to identify possible "outcomes/outputs" from the workshops and main sessions.
>>
>> What would an EPDP "workshop" look like? would it be "to EPDP, or not to EPDP? If it is about why to EPDP, or is an update overall about the issues about access to accurate data, someone should do a mini write up to describe it.
>>
>> On the other hand, the risks and threats to the global Internet from security; alternate proposals from nation states, protection of end users -- both businesses and citizens, and indeed government supplied services -- could make a very interesting workshop and allow us to bring in more senior speakers/experts.
>>
>> So, I advocate again for option 2.
>>
>> M
>>
>> ---------------------------------------------------------------
>>
>> From: ccwg-internet-governance [<ccwg-internet-governance-bounces at icann.org>](mailto:ccwg-internet-governance-bounces at icann.org) on behalf of Olivier MJ Cr?pin-Leblond [<ocl at gih.com>](mailto:ocl at gih.com)
>> Sent: Friday, April 5, 2019 2:45 AM
>> To: ccwg-internet-governance at icann.org
>> Subject: Re: [ccwg-internet-governance] Action Items re: Organisation of an IGF Workshop (was: Re: CCWG-IG call of Thursday, March 28)
>>
>> Dear Colleagues,
>>
>> a kind reminder - I have received no response to the enquiry below and our original deadline was yesterday 4th April. Please be so kind to comment ASAP.
>> Kindest regards,
>>
>> Olivier
>>
>> On 28/03/2019 18:46, Olivier MJ Cr?pin-Leblond wrote:
>>
>>> Dear Colleagues,
>>>
>>> on today's CCWG IG call, agenda item (3) focussed on the organisation of an IGF workshop in Berlin.
>>>
>>> The CCWG IG has made a proposal for an IGF workshop/roundtable for several years: [https://community.icann.org/display/CPMMB/Internet+Governance+Forum [nam01.safelinks.protection.outlook.com]](https://urldefense.proofpoint.com/v2/url?u=https-3A__nam01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fcommunity.icann.org-252Fdisplay-252FCPMMB-252FInternet-252BGovernance-252BForum-26data-3D02-257C01-257C-257C8dca14b4882e44d6b71108d6b9924e10-257C84df9e7fe9f640afb435aaaaaaaaaaaa-257C1-257C0-257C636900435403535674-26sdata-3D98DuMjRk8yY9gdCHygAKK09KDQi3PaNLeqOHqLPhk2M-253D-26reserved-3D0&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=9tUQzMx2D8jxiEv_-HzBjXTKpnJNpiXTLexpJLRjhzU&e=)
>>> Last year was the first year a workshop proposal was not approved and this was likely due to IGF Paris being much shorter than usual. In 2019, it is anticipated that the IGF in Berlin will revert to its usual format, thus there is a better chance that a workshop proposal would be accepted than last year.
>>>
>>> On today's call several options were proposed:
>>>
>>> Option 1
>>>
>>> A workshop/roundtable focussed on EPDP topic - similar to the topic we have proposed for the WSIS Forum: a workshop that puts together stakeholders taking part in the EPDP phases 1 and 2.
>>> By November 2019, implementation of phase 1 would have started and phase 2 would be in full swing. Some of the discussions taking place at IGF might benefit the work of the EPDP Team
>>> Workshop based on phase 1 but concentrating on phase 2. Focus should be on Phase 2. The workshop could be useful in brainstorming standardised access.
>>>
>>> Option 2
>>>
>>> 3 topical areas:
>>>
>>> - Data governance
>>> - Security
>>> - Stability (needs community speakers) of the DNS. A growing concern for safety and security of individuals. How resilient is the Internet / Alternative Security in the Internet.
>>> This topic has the advantage to be more predictable than a focus that is solely on EPDP Work Stream 2. We could work with SSAC and RSSAC but also all stakeholders at ICANN that work on stability and security, across all SOs and ACs to populate the workshop.
>>>
>>> One could argue that the EPDP Phase 2 work, access, is part of security. Security and Stability workshop could include the sub-topic of Phase 2 EPDP - the need or use of gTLD registration data to preserve security and stability of the DNS.
>>>
>>> If Option 2 is preferred instead of Option 1, one could have the topic of Option 1 proposed as a Flash session on WorkStream 2. A way to provide a briefing and an update on WorkStream 2.
>>>
>>> On the call, our action item was that I should share Option 1 and 2 on the mailing list, with a deadline of 5 working days (4th April 2019), to give the Team enough time to build the Session Proposal. The deadline for submitting workshop proposals at the IGF is 12th April.
>>>
>>> Kindest regards,
>>>
>>> Olivier
>>>
>>> On 25/03/2019 21:05, Desiree Cabrera wrote:
>>>
>>>> Dear all,
>>>>
>>>> The CCWG IG call is scheduled for Thursday, March 28 at 15:30 UTC.
>>>>
>>>> For more time zone information, please go to: [http://www.timeanddate.com/worldclock/converter.html [nam01.safelinks.protection.outlook.com]](https://urldefense.proofpoint.com/v2/url?u=https-3A__nam01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Fwww.timeanddate.com-252Fworldclock-252Fconverter.html-26data-3D02-257C01-257C-257C8dca14b4882e44d6b71108d6b9924e10-257C84df9e7fe9f640afb435aaaaaaaaaaaa-257C1-257C0-257C636900435403545686-26sdata-3D-252FiWpGDYqQ-252FDOnzXzFhd19AK-252BVSq41-252BPThM9q7fpJOh0-253D-26reserved-3D0&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=8Ya-m0W8iY9VqlDMNQpgF-0xgzQwG-XwZ7PdznaE-EY&e=)
>>>>
>>>> Wiki: [https://community.icann.org/display/CPMMB/CCWG+on+IG+Teleconference+-+2019.03.28 [nam01.safelinks.protection.outlook.com]](https://urldefense.proofpoint.com/v2/url?u=https-3A__nam01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fcommunity.icann.org-252Fdisplay-252FCPMMB-252FCCWG-252Bon-252BIG-252BTeleconference-252B-2D-252B2019.03.28-26data-3D02-257C01-257C-257C8dca14b4882e44d6b71108d6b9924e10-257C84df9e7fe9f640afb435aaaaaaaaaaaa-257C1-257C0-257C636900435403555691-26sdata-3D0P-252Fj96MrkkCy1NMErJkdfnn4yHtrq-252BvYhbxq6UB-252FGTo-253D-26reserved-3D0&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=A55L-v53ifHW0LydSs2kq3elQJ0KRV127BTFEd4GJAk&e=)
>>>>
>>>> DRAFT AGENDA:
>>>>
>>>> - Roll Call, welcome, adoption of the agenda and Introduction
>>>>
>>>> - Organisation of the WSIS Forum workshop
>>>>
>>>> - Organisation of an IGF Workshop
>>>>
>>>> - Charter update
>>>>
>>>> - AoB
>>>>
>>>> Please join this call by clicking on the Adobe Connect link, upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number (Remember to change the Country Code if needed).
>>>>
>>>> Please follow these steps to log into Adobe Connect.
>>>>
>>>> Click on the link to Adobe Connect: [https://participate.icann.org/ccwg/ [nam01.safelinks.protection.outlook.com]](https://urldefense.proofpoint.com/v2/url?u=https-3A__nam01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fparticipate.icann.org-252Fccwg-252F-26data-3D02-257C01-257C-257C8dca14b4882e44d6b71108d6b9924e10-257C84df9e7fe9f640afb435aaaaaaaaaaaa-257C1-257C0-257C636900435403565702-26sdata-3DQ3OmCMiZzmFQ-252BbROLfRU1SK9kjmtJzcDg-252BQl60RtKno-253D-26reserved-3D0&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=bWfBWfC0DugAn8L_rL8Fo6ZerUFaE0lgNKKHQ-RNZy8&e=)
>>>>
>>>> When the window pops up, type in your phone number and click ?Join?. Please do not click on ?Listen Only? or you will not be able to speak.
>>>>
>>>> [var/folders/xk/tbx61qn97n3f4g6j1vzl1hgspb9gmr/T]
>>>>
>>>> After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again.
>>>>
>>>> Only use the phone option if you are travelling and cannot access Adobe Connect.
>>>>
>>>> If you are Unable to log into Adobe Connect and can only join via phone:
>>>>
>>>> List of International Dial In Numbers: [https://mtginfo.pgi.com/globalcallmanagement.asp?bwebid=9820041&cid=da6ce6bed7eb5a11d77dfcea4d49&confid=da6be6bad7e75a1ed779fceb&brandid=1 [nam01.safelinks.protection.outlook.com]](https://urldefense.proofpoint.com/v2/url?u=https-3A__nam01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fmtginfo.pgi.com-252Fglobalcallmanagement.asp-253Fbwebid-253D9820041-2526cid-253Dda6ce6bed7eb5a11d77dfcea4d49-2526confid-253Dda6be6bad7e75a1ed779fceb-2526brandid-253D1-26data-3D02-257C01-257C-257C8dca14b4882e44d6b71108d6b9924e10-257C84df9e7fe9f640afb435aaaaaaaaaaaa-257C1-257C0-257C636900435403575707-26sdata-3DmTTrGU-252F6xTJBBtBWupwcwrqtdoa3lfkPqfmlbe8R9RQ-253D-26reserved-3D0&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=e0tyoOwYP10HDqOsv3kDx-SYe0BLEAy_1KjyrQ86xoQ&e=)
>>>>
>>>> Participant Passcode: 6596520924
>>>>
>>>> All the best,
>>>>
>>>> Desiree
>>>>
>>>> ____
>>>>
>>>> Desiree Cabrera
>>>>
>>>> Executive Assistant
>>>>
>>>> Internet Corporation for Assigned Names and Numbers
>>>>
>>>> 12025 Waterfront Drive, Suite 300
>>>>
>>>> Los Angeles, CA 90094 USA
>>>>
>>>> Office: +1 310 578 8625
>>>>
>>>> Mobile: +1 424 384 9359
>>>>
>>>> _______________________________________________
>>>>
>>>> ccwg-internet-governance mailing list
>>>>
>>>> ccwg-internet-governance at icann.org
>>>>
>>>> [https://mm.icann.org/mailman/listinfo/ccwg-internet-governance [nam01.safelinks.protection.outlook.com]](https://urldefense.proofpoint.com/v2/url?u=https-3A__nam01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fmm.icann.org-252Fmailman-252Flistinfo-252Fccwg-2Dinternet-2Dgovernance-26data-3D02-257C01-257C-257C8dca14b4882e44d6b71108d6b9924e10-257C84df9e7fe9f640afb435aaaaaaaaaaaa-257C1-257C0-257C636900435403585719-26sdata-3DO0K9KM4p5oWX0kYOTi0340J58K-252FHUiMM4f3cH0-252BDR1g-253D-26reserved-3D0&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=GtnsNevSgiZx7vttlXNjUQsYVzw7swjj_9tHocOh7ww&e=)
>>>
>>> --
>>>
>>> Olivier MJ Cr?pin-Leblond, PhD
>>>
>>> [http://www.gih.com/ocl.html [nam01.safelinks.protection.outlook.com]](https://urldefense.proofpoint.com/v2/url?u=https-3A__nam01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Fwww.gih.com-252Focl.html-26data-3D02-257C01-257C-257C8dca14b4882e44d6b71108d6b9924e10-257C84df9e7fe9f640afb435aaaaaaaaaaaa-257C1-257C0-257C636900435403595724-26sdata-3DuZ3knS7Ql4UL3UvTinDrgKBz-252BsFNuvG7CPpoeEI47KE-253D-26reserved-3D0&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=5sYSrS5Gp0P2Fj-sJI4lddsOXyhcIRfZOJ6KUA0jF_8&e=)
>>>
>>> _______________________________________________
>>>
>>> ccwg-internet-governance mailing list
>>>
>>> ccwg-internet-governance at icann.org
>>>
>>> [https://mm.icann.org/mailman/listinfo/ccwg-internet-governance [nam01.safelinks.protection.outlook.com]](https://urldefense.proofpoint.com/v2/url?u=https-3A__nam01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fmm.icann.org-252Fmailman-252Flistinfo-252Fccwg-2Dinternet-2Dgovernance-26data-3D02-257C01-257C-257C8dca14b4882e44d6b71108d6b9924e10-257C84df9e7fe9f640afb435aaaaaaaaaaaa-257C1-257C0-257C636900435403605741-26sdata-3DcC6M8xawsO56rQTKcKI-252Fqh-252F5dKDv2koGpkhLzpfjrGg-253D-26reserved-3D0&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=1kYUvjC2EuXvJOBrwlVjlK1kLwnqNl06ZqhMJjqeQ3U&e=)
>>
>> --
>>
>> Olivier MJ Cr?pin-Leblond, PhD
>>
>> [http://www.gih.com/ocl.html [nam01.safelinks.protection.outlook.com]](https://urldefense.proofpoint.com/v2/url?u=https-3A__nam01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Fwww.gih.com-252Focl.html-26data-3D02-257C01-257C-257C8dca14b4882e44d6b71108d6b9924e10-257C84df9e7fe9f640afb435aaaaaaaaaaaa-257C1-257C0-257C636900435403615752-26sdata-3DY5e7fghUoYC4BADfYILMaepBXXAfDZr-252F1VLVu5xHnMI-253D-26reserved-3D0&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=hXXiigReHMRIorGXLxguOMSX1D7GiZKEHKKJ2DKllB4&e=)
>
> --
>
> Olivier MJ Cr?pin-Leblond, PhD
>
> [http://www.gih.com/ocl.html [gih.com]](https://urldefense.proofpoint.com/v2/url?u=http-3A__www.gih.com_ocl.html&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=RrrXyaBfa00GH1liTedM3FwobVakuhJ-qs1N8-Ji8VE&m=enu6yHtxB75FR8dL8MfOlTxXUY6wef-KVmlyJWIdrMQ&s=aunU_ivUpNV90zjSAB14ObgeKoV3KHt8Sp4ImfUPEV8&e=)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190413/dcb17502/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14963 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190413/dcb17502/attachment.png>

From rafik.dammak at gmail.com  Mon Apr 15 12:50:37 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Mon, 15 Apr 2019 18:50:37 +0900
Subject: [NCSG-PC] [NCSG-Discuss] [Public Comment] NCSG Comment on the
 EPDP on Temp Spec for Board Consideration
In-Reply-To: <CAH5sThnA0W=81bAvyPP-0=Li2BMfP09gHmT7ff8o4EQBhDYr9A@mail.gmail.com>
References: <CA+Ks+AC=nz37JNrVrsM-Si_n4BMdnZvrKn0XDPWH3_Mk5h0wHQ@mail.gmail.com>
 <CAH5sThnA0W=81bAvyPP-0=Li2BMfP09gHmT7ff8o4EQBhDYr9A@mail.gmail.com>
Message-ID: <CAH5sThmdFAwQO+j321eyMczid5Yo+TkBTKL6cBhg5Yg4OpLnwA@mail.gmail.com>

Hi,

reminder to review the draft comment.
the deadline for submission is the 17th april.

Best,

Rafik

Le mer. 10 avr. 2019 ? 20:36, Rafik Dammak <rafik.dammak at gmail.com> a
?crit :

> Hi,
>
> We have a draft comment to review for endorsement. Deadline for submission
> is in 17th April.
>
> Best,
>
> Rafik
>
> ---------- Forwarded message ---------
> From: Louise Marie Hurel <louise.marie.hsd at gmail.com>
> Date: Wed, Apr 10, 2019, 20:33
> Subject: [NCSG-Discuss] [Public Comment] NCSG Comment on the EPDP on Temp
> Spec for Board Consideration
> To: <NCSG-DISCUSS at listserv.syr.edu>
>
>
> Hi all,
>
> Here's the link to the draft version of the NCSG comment on the *GNSO
> Expedited Policy Development Process (EPDP) on the Temporary Specification
> for gTLD Registration Data Policy Recommendations for ICANN Board
> Consideration*:
> https://docs.google.com/document/d/1YZe-AtxIMso3sobLSFSn_SsdDcsZS3myu8GNFfqZCQI/edit
>
>
> As you will note, the main objective of this comment is to provide an
> account and narrative as to where we compromised (and *not* to re-open
> substantive policy discussions) and re-state our positions. Please feel
> free to review the draft comment and share your thoughts, particularly
> those that were on the EPDP team during Phase 1 and can provide a more
> detailed background to the final report.
>
> The deadline for submission is *17 April*.
>
> Many thanks to Amr, Farzi and Stefan Filipovic for the comments!
>
> All the best,
>
> *Louise Marie Hurel*
>
> Research and Project Development
>
> Cybersecurity and Digital Liberties Programme | Igarap? Institute
>
> Publications
> <https://www.researchgate.net/profile/Louise_Marie_Hurel/publications>
> Skype: louise.dias
> louise at igarape.org.br
> louise.marie.hsd at gmail.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190415/deb222f6/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Mon Apr 15 23:14:13 2019
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Mon, 15 Apr 2019 20:14:13 +0000
Subject: [NCSG-PC] Fwd: REMINDER - Response needed (NCSG): Definition for
 ICANN acronyms and terms feature | Response requested by Tuesday, 16 April
In-Reply-To: <4D64D81E-106D-4772-8B3C-00A6F9B611FB@icann.org>
References: <4D64D81E-106D-4772-8B3C-00A6F9B611FB@icann.org>
Message-ID: <2e9056e7-d43e-c06f-af7d-20d07f763ab6@mail.utoronto.ca>

Anybody got a better definition?

SP


-------- Forwarded Message --------
Subject:        REMINDER - Response needed (NCSG): Definition for ICANN acronyms and terms feature | Response requested by Tuesday, 16 April
Date:   Mon, 15 Apr 2019 20:11:55 +0000
From:   Chantelle Doerksen <chantelle.doerksen at icann.org><mailto:chantelle.doerksen at icann.org>
To:     Stephanie Perrin <stephanie.perrin at mail.utoronto.ca><mailto:stephanie.perrin at mail.utoronto.ca>
CC:     Maryam Bakoshi <maryam.bakoshi at icann.org><mailto:maryam.bakoshi at icann.org>, Mary Wong <mary.wong at icann.org><mailto:mary.wong at icann.org>, Carlos Reyes <carlos.reyes at icann.org><mailto:carlos.reyes at icann.org>, Chantelle Doerksen <chantelle.doerksen at icann.org><mailto:chantelle.doerksen at icann.org>


Dear Stephanie,



As a friendly reminder, we are updating the ICANN acronyms and terms[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_icann-2Dacronyms-2Dand-2Dterms_icann-2Dacronyms-2Dand-2Dterms_en_nav_A&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=wL3Zo2cS0E1587i1K6plo1c3_QE_VYKpzxK_zxU6nHchrvvSIST7VWCi3I7o_dqG&m=FVsRWO-PITkkYOVO2bCWCXfNUJdZTJHNDlTVG8QPfn4&s=xGufnlhBNbKjWjOz55latbEwVNDr3EjmS9TgmEGqaSs&e=> feature on icann.org to include a definition for the NCSG.



Please let us know by Tuesday, 16 April if you have any minor changes to suggest to the definition suggested below.



Thank you again.

Kind regards,

Chantelle


From: chantelle doerksen <chantelle.doerksen at icann.org><mailto:chantelle.doerksen at icann.org>
Date: Monday, April 8, 2019 at 14:13
To: Stephanie Perrin <stephanie.perrin at mail.utoronto.ca><mailto:stephanie.perrin at mail.utoronto.ca>
Cc: Maryam Bakoshi <maryam.bakoshi at icann.org><mailto:maryam.bakoshi at icann.org>, Mary Wong <mary.wong at icann.org><mailto:mary.wong at icann.org>, Carlos Reyes <carlos.reyes at icann.org><mailto:carlos.reyes at icann.org>, chantelle doerksen <chantelle.doerksen at icann.org><mailto:chantelle.doerksen at icann.org>
Subject: Response needed (NCSG): Definition for ICANN acronyms and terms feature

Dear Stephanie,


As part of the ongoing Information Transparency Initiative (ITI)<https://www.icann.org/news/blog/the-information-transparency-initiative-iti-and-the-open-data-initiative-odi-similarities-differences-and-what-these-projects-mean-for-you>, we are updating the ICANN acronyms and terms<https://www.icann.org/icann-acronyms-and-terms/icann-acronyms-and-terms/en/nav/A> feature on icann.org. Our goal is to provide simple and consistent definitions for the community, including non-native English speakers and newcomers.

We propose the following definition for the NCSG. Please let us know by Tuesday, 16 April if we can proceed with the following definition, or if you have any minor changes to suggest:
 A stakeholder group within the Generic Names Supporting Organization that represents the interests of noncommercial registrants and noncommercial Internet users of generic top-level domains. The NCSG is a member of the Non-Contracted Parties House within the Generic Names Supporting Organization Council.

The NCSG consists of two constituencies:

?          Non-Commercial Users Constituency (NCUC)
?          Not-for-Profit Operational Concerns Constituency (NPOC)


We will also include a link to your community?s website, so that a user can learn additional information about your group.

Thank you in advance, and we look forward to your feedback.


Kind regards,

Chantelle



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190415/9c2c7aa2/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Mon Apr 15 23:27:49 2019
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Mon, 15 Apr 2019 20:27:49 +0000
Subject: [NCSG-PC] Fwd: Re: [ICANN Community Leaders] [Ext] RE:
 Accountability and community input on IRP standing panel
In-Reply-To: <23797A76-8418-4831-9F54-E0CBEBB896A2@icann.org>
References: <23797A76-8418-4831-9F54-E0CBEBB896A2@icann.org>
Message-ID: <11027db0-eca5-d8db-42a7-21bf7116d6e1@mail.utoronto.ca>

why can't he say he is sorry?  I guess this is  input for our meeting

SP


-------- Forwarded Message --------
Subject:        Re: [ICANN Community Leaders] [Ext] RE: Accountability and community input on IRP standing panel
Date:   Mon, 15 Apr 2019 20:14:59 +0000
From:   Goran Marby <goran.marby at icann.org><mailto:goran.marby at icann.org>
To:     Austin, Donna <Donna.Austin at team.neustar><mailto:Donna.Austin at team.neustar>, Katrina Sataki <katrina at nic.lv><mailto:katrina at nic.lv>, David Olive <david.olive at icann.org><mailto:david.olive at icann.org>, Samantha Eisner <Samantha.Eisner at icann.org><mailto:Samantha.Eisner at icann.org>
CC:     ccnso-council at icann.org<mailto:ccnso-council at icann.org> <ccnso-council at icann.org><mailto:ccnso-council at icann.org>, 'Chris Disspain' <chris at disspain.uk><mailto:chris at disspain.uk>, so-ac-sg-cleaders at icann.org<mailto:so-ac-sg-cleaders at icann.org> <so-ac-sg-cleaders at icann.org><mailto:so-ac-sg-cleaders at icann.org>, 'Nigel Roberts' <nigel.roberts at board.icann.org><mailto:nigel.roberts at board.icann.org>


Hi friends,

I wish to thank you for the e-mails, noting the importance to the community of the selection of a Standing Panel for Independent Review Processes (IRPs), and suggesting that ICANN Org relaunch the call for community input via the public comment process. I would like to take this opportunity to assure everyone that our publication of a blog post on this topic on 9 March was intended to supplement, and not displace, the existing processes through which we seek the community?s feedback. This is why the same request was circulated after the conclusion of the ICANN64 Kobe meeting in the Community Leadership Digest.

On this specific topic, what we have tried to do is provide more specific and targeted ways for the community to provide feedback, since the establishment of an IRP Standing Panel has been a long-standing topic of community discussion. You will recall that a webinar was held in January 2018, followed by a public session at ICANN61 in March 2018. The questions that we have developed result from these discussions to date and builds on work done by the community-based IRP Implementation Oversight Team. We had hoped that this continuous process will allow for multiple opportunities for the community to provide its views, as we work toward completing the important task of seating the Standing Panel.

I take the point that publishing the blog post on 9 March without providing more specific information about how else we intend to collect community feedback may have sent the wrong signal. In addition, I understand that the suggested 15 April deadline may not be feasible at this stage. I therefore invite you and your community groups to continue to provide your feedback via email to the publicly-archived mailing list that was set up some time ago for the community to continue its discussions in a transparent and accessible way: https://mm.icann.org/pipermail/irp-standing-panel/. If possible, I ask that you provide your input by 15 May 2019<x-apple-data-detectors://17>.

In relation to the need to provide greater clarity while ensuring transparency in our operations, you may be interested to know that, prior to the ICANN64 Kobe meeting, I had already requested that David Olive and his team prepare a comprehensive set of guidelines regarding the appropriate use of public comment proceedings and other community consultations. I expect to hold a discussion about this with my Executive Team around the time of ICANN65 in Marrakech.

In closing, I thank you all for your helpful and constructive feedback. I look forward to sharing very shortly with you further information about the remaining work to be done on the IRP Standing Panel, as well as our plans to clarify the use of public comment and consultation opportunities.


Regards

G?ran




From: "Austin, Donna" <Donna.Austin at team.neustar><mailto:Donna.Austin at team.neustar>
Date: Monday, April 15, 2019 at 10:27 AM
To: Katrina Sataki <katrina at nic.lv><mailto:katrina at nic.lv>, Goran Marby <goran.marby at icann.org><mailto:goran.marby at icann.org>
Cc: "ccnso-council at icann.org"<mailto:ccnso-council at icann.org> <ccnso-council at icann.org><mailto:ccnso-council at icann.org>, 'Chris Disspain' <chris at disspain.uk><mailto:chris at disspain.uk>, 'Nigel Roberts' <nigel.roberts at board.icann.org><mailto:nigel.roberts at board.icann.org>, "so-ac-sg-cleaders at icann.org"<mailto:so-ac-sg-cleaders at icann.org> <so-ac-sg-cleaders at icann.org><mailto:so-ac-sg-cleaders at icann.org>
Subject: [Ext] RE: [ICANN Community Leaders] Accountability and community input on IRP standing panel

As the deadline for responses is today 15 April 2019, do we have any update on whether the deadline will be extended as requested by Katrina.

From: SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces at icann.org] On Behalf Of Katrina Sataki
Sent: Friday, April 12, 2019 12:55 AM
To: 'Goran Marby' <goran.marby at icann.org><mailto:goran.marby at icann.org>
Cc: ccnso-council at icann.org<mailto:ccnso-council at icann.org>; 'Chris Disspain' <chris at disspain.uk><mailto:chris at disspain.uk>; 'Nigel Roberts' <nigel.roberts at board.icann.org><mailto:nigel.roberts at board.icann.org>; so-ac-sg-cleaders at icann.org<mailto:so-ac-sg-cleaders at icann.org>
Subject: [ICANN Community Leaders] Accountability and community input on IRP standing panel

Dear G?ran:

In your blog post of 9 March 2019, you invited community inputs on the process for the selection of a standing panel to hear Independent Review Process (IRP) complaints. You included a series of questions, with a deadline for responses by 15 April 2019:


  *   Qualifications for Standing Panelists: Are there specific qualifications that should be included? If so, what are they? Anything disqualifying? Should the SOs and ACs recommend qualifications? And if so, how?
  *   Identifying a Slate of Well-Qualified Panelists: We?ve heard concerns from some members of the ICANN community as to whether the broader community has the appropriate experience and skill for this selection work, and have suggested the possibility that ICANN instead contract with experts to perform this vetting process. Should the community rely on expertise to help vet and recommend a final slate for the standing panel?
  *   Board Approval of Panel Slate ? Further Questions: After there is a slate of well-qualified applicants, the Board must confirm the panel. If the Board has questions that might impact its confirmation, to whom should those questions be addressed? If experts are used to develop the slate, should the experts, the SOs and ACs, or some combination thereof be part of that conversation?
  *   Future Selections: Should the process being designed today be reviewed for effectiveness after the first slating is completed, prior to making it standard operating procedure for future selection rounds?

The IRP, as you correctly stated, is an accountability mechanism arising from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for breaches of ICANN?s own policies, core values or because decisions have been made on the basis of incorrect information.

Matters of high importance that fall within scope include disputes involving the rights of the Empowered Community, enforcement of ICANN?s contractual rights with respect to the IANA Naming Function Contract, and claims regarding PTI service complaints by direct customers of the IANA naming functions (that are not resolved through mediation). The appointment of appropriately qualified and independent panellists who will be making these review decision is therefore a high concern to us.

Taking into account that:
1)    the blog post was published right before ICANN64, when most volunteers are travelling or busy preparing for the meeting,
2)    no corresponding public comments request has been published on the ICANN website,
3)    no information about the request was published in ICANN Community Leadership Digest (the questions were first mentioned only on 11 April),
and to ensure that:
1)    all community members are aware of the opportunity to provide input,
2)    everyone has sufficient time to discuss the issue and submit their considerations,
3)    the process is transparent and all comments are published in due time,
we would like to encourage you to re-launch the call for community inputs in accordance with the established procedures.

Furthermore, we request that only one process for seeking community feedback, i.e. ICANN public comments procedure, is used in the future. While a blog post may remain to be a good tool for reminders, and senior staff commentary may encourage engagement and participation, they are no substitute for due process.

Yours sincerely,

Katrina Sataki
On behalf of the ccNSO Council
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190415/042a6c4b/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Attached Message Part
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190415/042a6c4b/attachment.ksh>

From rafik.dammak at gmail.com  Tue Apr 16 02:15:45 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 16 Apr 2019 08:15:45 +0900
Subject: [NCSG-PC] Fwd: Re: [ICANN Community Leaders] [Ext] RE:
 Accountability and community input on IRP standing panel
In-Reply-To: <11027db0-eca5-d8db-42a7-21bf7116d6e1@mail.utoronto.ca>
References: <23797A76-8418-4831-9F54-E0CBEBB896A2@icann.org>
 <11027db0-eca5-d8db-42a7-21bf7116d6e1@mail.utoronto.ca>
Message-ID: <CAH5sThkW97DmxCAK-MjjjXwT--6JU7p09AksA6_vuhWzw2P39w@mail.gmail.com>

Hi,

I think the urgent thing to do is to prepare responses to the questions.
the process for setting the standing panel is taking too much time and you
can notice that some parts in ICANN are interested to push in some
direction for the implementation.
I put Robin and Farzaneh in cc as they followed closely the work on IRP and
what the Implementation Oversight Team (IOT) did.

Best

Rafik

Le mar. 16 avr. 2019 ? 05:28, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> a ?crit :

> why can't he say he is sorry?  I guess this is  input for our meeting
>
> SP
>
>
> -------- Forwarded Message --------
> Subject: Re: [ICANN Community Leaders] [Ext] RE: Accountability and
> community input on IRP standing panel
> Date: Mon, 15 Apr 2019 20:14:59 +0000
> From: Goran Marby <goran.marby at icann.org> <goran.marby at icann.org>
> To: Austin, Donna <Donna.Austin at team.neustar> <Donna.Austin at team.neustar>,
> Katrina Sataki <katrina at nic.lv> <katrina at nic.lv>, David Olive
> <david.olive at icann.org> <david.olive at icann.org>, Samantha Eisner
> <Samantha.Eisner at icann.org> <Samantha.Eisner at icann.org>
> CC: ccnso-council at icann.org <ccnso-council at icann.org>
> <ccnso-council at icann.org>, 'Chris Disspain' <chris at disspain.uk>
> <chris at disspain.uk>, so-ac-sg-cleaders at icann.org
> <so-ac-sg-cleaders at icann.org> <so-ac-sg-cleaders at icann.org>, 'Nigel
> Roberts' <nigel.roberts at board.icann.org> <nigel.roberts at board.icann.org>
>
> Hi friends,
>
>
>
> I wish to thank you for the e-mails, noting the importance to the
> community of the selection of a Standing Panel for Independent Review
> Processes (IRPs), and suggesting that ICANN Org relaunch the call for
> community input via the public comment process. I would like to take this
> opportunity to assure everyone that our publication of a blog post on this
> topic on 9 March was intended to supplement, and not displace, the existing
> processes through which we seek the community?s feedback. This is why the
> same request was circulated after the conclusion of the ICANN64 Kobe
> meeting in the Community Leadership Digest.
>
>
>
> On this specific topic, what we have tried to do is provide more specific
> and targeted ways for the community to provide feedback, since the
> establishment of an IRP Standing Panel has been a long-standing topic of
> community discussion. You will recall that a webinar was held in January
> 2018, followed by a public session at ICANN61 in March 2018. The questions
> that we have developed result from these discussions to date and builds on
> work done by the community-based IRP Implementation Oversight Team. We had
> hoped that this continuous process will allow for multiple opportunities
> for the community to provide its views, as we work toward completing the
> important task of seating the Standing Panel.
>
>
>
> I take the point that publishing the blog post on 9 March without
> providing more specific information about how else we intend to collect
> community feedback may have sent the wrong signal. In addition, I
> understand that the suggested 15 April deadline may not be feasible at this
> stage. I therefore invite you and your community groups to continue to
> provide your feedback via email to the publicly-archived mailing list that
> was set up some time ago for the community to continue its discussions in a
> transparent and accessible way:
> https://mm.icann.org/pipermail/irp-standing-panel/. If possible, I ask
> that you provide your input by *15 May 2019*.
>
>
>
> In relation to the need to provide greater clarity while ensuring
> transparency in our operations, you may be interested to know that, prior
> to the ICANN64 Kobe meeting, I had already requested that David Olive and
> his team prepare a comprehensive set of guidelines regarding the
> appropriate use of public comment proceedings and other community
> consultations. I expect to hold a discussion about this with my Executive
> Team around the time of ICANN65 in Marrakech.
>
>
>
> In closing, I thank you all for your helpful and constructive feedback. I
> look forward to sharing very shortly with you further information about the
> remaining work to be done on the IRP Standing Panel, as well as our plans
> to clarify the use of public comment and consultation opportunities.
>
>
>
> Regards
>
>
>
> G?ran
>
>
>
>
>
>
>
> *From: *"Austin, Donna" <Donna.Austin at team.neustar>
> <Donna.Austin at team.neustar>
> *Date: *Monday, April 15, 2019 at 10:27 AM
> *To: *Katrina Sataki <katrina at nic.lv> <katrina at nic.lv>, Goran Marby
> <goran.marby at icann.org> <goran.marby at icann.org>
> *Cc: *"ccnso-council at icann.org" <ccnso-council at icann.org>
> <ccnso-council at icann.org> <ccnso-council at icann.org>, 'Chris Disspain'
> <chris at disspain.uk> <chris at disspain.uk>, 'Nigel Roberts'
> <nigel.roberts at board.icann.org> <nigel.roberts at board.icann.org>,
> "so-ac-sg-cleaders at icann.org" <so-ac-sg-cleaders at icann.org>
> <so-ac-sg-cleaders at icann.org> <so-ac-sg-cleaders at icann.org>
> *Subject: *[Ext] RE: [ICANN Community Leaders] Accountability and
> community input on IRP standing panel
>
>
>
> As the deadline for responses is today 15 April 2019, do we have any
> update on whether the deadline will be extended as requested by Katrina.
>
>
>
> *From:* SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces at icann.org
> <so-ac-sg-cleaders-bounces at icann.org>] *On Behalf Of *Katrina Sataki
> *Sent:* Friday, April 12, 2019 12:55 AM
> *To:* 'Goran Marby' <goran.marby at icann.org> <goran.marby at icann.org>
> *Cc:* ccnso-council at icann.org; 'Chris Disspain' <chris at disspain.uk>
> <chris at disspain.uk>; 'Nigel Roberts' <nigel.roberts at board.icann.org>
> <nigel.roberts at board.icann.org>; so-ac-sg-cleaders at icann.org
> *Subject:* [ICANN Community Leaders] Accountability and community input
> on IRP standing panel
>
>
>
> Dear G?ran:
>
>
>
> In your blog post of 9 March 2019, you invited community inputs on the
> process for the selection of a standing panel to hear Independent Review
> Process (IRP) complaints. You included a series of questions, with a
> deadline for responses by 15 April 2019:
>
>
>
>    - Qualifications for Standing Panelists: Are there specific
>    qualifications that should be included? If so, what are they? Anything
>    disqualifying? Should the SOs and ACs recommend qualifications? And if so,
>    how?
>    - Identifying a Slate of Well-Qualified Panelists: We?ve heard
>    concerns from some members of the ICANN community as to whether the broader
>    community has the appropriate experience and skill for this selection work,
>    and have suggested the possibility that ICANN instead contract with experts
>    to perform this vetting process. Should the community rely on expertise to
>    help vet and recommend a final slate for the standing panel?
>    - Board Approval of Panel Slate ? Further Questions: After there is a
>    slate of well-qualified applicants, the Board must confirm the panel. If
>    the Board has questions that might impact its confirmation, to whom should
>    those questions be addressed? If experts are used to develop the slate,
>    should the experts, the SOs and ACs, or some combination thereof be part of
>    that conversation?
>    - Future Selections: Should the process being designed today be
>    reviewed for effectiveness after the first slating is completed, prior to
>    making it standard operating procedure for future selection rounds?
>
>
>
> The IRP, as you correctly stated, is an accountability mechanism arising
> from the ICANN Bylaws. ICANN Board and staff decisions may be reviewed for
> breaches of ICANN?s own policies, core values or because decisions have
> been made on the basis of incorrect information.
>
>
>
> Matters of high importance that fall within scope include disputes
> involving the rights of the Empowered Community, enforcement of ICANN?s
> contractual rights with respect to the IANA Naming Function Contract, and
> claims regarding PTI service complaints by direct customers of the IANA
> naming functions (that are not resolved through mediation). The appointment
> of appropriately qualified and independent panellists who will be making
> these review decision is therefore a high concern to us.
>
>
>
> Taking into account that:
>
> 1)    the blog post was published right before ICANN64, when most
> volunteers are travelling or busy preparing for the meeting,
>
> 2)    no corresponding public comments request has been published on the
> ICANN website,
>
> 3)    no information about the request was published in ICANN Community
> Leadership Digest (the questions were first mentioned only on 11 April),
>
> and to ensure that:
>
> 1)    all community members are aware of the opportunity to provide input,
>
> 2)    everyone has sufficient time to discuss the issue and submit their
> considerations,
>
> 3)    the process is transparent and all comments are published in due
> time,
>
> we would like to encourage you to re-launch the call for community inputs
> in accordance with the established procedures.
>
>
>
> Furthermore, we request that only one process for seeking community
> feedback, i.e. ICANN public comments procedure, is used in the future.
> While a blog post may remain to be a good tool for reminders, and senior
> staff commentary may encourage engagement and participation, they are no
> substitute for due process.
>
>
>
> Yours sincerely,
>
>
>
> Katrina Sataki
>
> On behalf of the ccNSO Council
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190416/24f5a463/attachment.htm>

From icann at ferdeline.com  Tue Apr 16 13:18:56 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Tue, 16 Apr 2019 10:18:56 +0000
Subject: [NCSG-PC] Fwd: REMINDER - Response needed (NCSG): Definition
 for ICANN acronyms and terms feature | Response requested by Tuesday,
 16 April
In-Reply-To: <2e9056e7-d43e-c06f-af7d-20d07f763ab6@mail.utoronto.ca>
References: <4D64D81E-106D-4772-8B3C-00A6F9B611FB@icann.org>
 <2e9056e7-d43e-c06f-af7d-20d07f763ab6@mail.utoronto.ca>
Message-ID: <5NJxC3jM9UQfqk1Bs4arX8mF7RvMH2p2YRIJrDafe0y3hzeMWRFIZB85Vhr-fTL4FpxAANKMk135s3DmsPKeKyc_YLBrmQ-feas11XLfCOg=@ferdeline.com>

How about this?

The Non-Commercial Stakeholder Group (NCSG) is a stakeholder group within the Generic Names Supporting Organization (GNSO). The NCSG is the only place within ICANN that is specifically reserved for the advancement of non-state and non-market interests. The NCSG represents more than 600 non-profit organisations and individuals from over 150 countries who wish to advance non-commercial policy objectives at ICANN such as human rights, education, access to knowledge, freedom of expression, privacy rights and other non-commercial goals. The NCSG?s members include universities, civil liberties groups, free software groups, religious organisations, artistic groups, ICT development organisations and other non-commercial actors dedicated to the public interest.

The NCSG consists of two constituencies:

?          Non-Commercial Users Constituency (NCUC)

?          Not-for-Profit Operational Concerns Constituency (NPOC)

-- Ayden

??????? Original Message ???????
On Monday, April 15, 2019 10:14 PM, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> wrote:

> Anybody got a better definition?
>
> SP
>
> -------- Forwarded Message --------
> Subject:	REMINDER - Response needed (NCSG): Definition for ICANN acronyms and terms feature | Response requested by Tuesday, 16 April
> Date:	Mon, 15 Apr 2019 20:11:55 +0000
> From:	Chantelle Doerksen [<chantelle.doerksen at icann.org>](mailto:chantelle.doerksen at icann.org)
>
> To:	Stephanie Perrin [<stephanie.perrin at mail.utoronto.ca>](mailto:stephanie.perrin at mail.utoronto.ca)
>
> CC:	Maryam Bakoshi [<maryam.bakoshi at icann.org>](mailto:maryam.bakoshi at icann.org), Mary Wong [<mary.wong at icann.org>](mailto:mary.wong at icann.org), Carlos Reyes [<carlos.reyes at icann.org>](mailto:carlos.reyes at icann.org), Chantelle Doerksen [<chantelle.doerksen at icann.org>](mailto:chantelle.doerksen at icann.org)
>
> Dear Stephanie,
>
> As a friendly reminder, we are updating the [ICANN acronyms and terms[icann.org]](https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_icann-2Dacronyms-2Dand-2Dterms_icann-2Dacronyms-2Dand-2Dterms_en_nav_A&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=wL3Zo2cS0E1587i1K6plo1c3_QE_VYKpzxK_zxU6nHchrvvSIST7VWCi3I7o_dqG&m=FVsRWO-PITkkYOVO2bCWCXfNUJdZTJHNDlTVG8QPfn4&s=xGufnlhBNbKjWjOz55latbEwVNDr3EjmS9TgmEGqaSs&e=) feature on icann.org to include a definition for the NCSG.
>
> Please let us know by Tuesday, 16 April if you have any minor changes to suggest to the definition suggested below.
>
> Thank you again.
>
> Kind regards,
>
> Chantelle
>
> From: chantelle doerksen [<chantelle.doerksen at icann.org>](mailto:chantelle.doerksen at icann.org)
> Date: Monday, April 8, 2019 at 14:13
> To: Stephanie Perrin [<stephanie.perrin at mail.utoronto.ca>](mailto:stephanie.perrin at mail.utoronto.ca)
> Cc: Maryam Bakoshi [<maryam.bakoshi at icann.org>](mailto:maryam.bakoshi at icann.org), Mary Wong [<mary.wong at icann.org>](mailto:mary.wong at icann.org), Carlos Reyes [<carlos.reyes at icann.org>](mailto:carlos.reyes at icann.org), chantelle doerksen [<chantelle.doerksen at icann.org>](mailto:chantelle.doerksen at icann.org)
> Subject: Response needed (NCSG): Definition for ICANN acronyms and terms feature
>
> Dear Stephanie,
>
> As part of the ongoing [Information Transparency Initiative (ITI)](https://www.icann.org/news/blog/the-information-transparency-initiative-iti-and-the-open-data-initiative-odi-similarities-differences-and-what-these-projects-mean-for-you), we are updating the [ICANN acronyms and terms](https://www.icann.org/icann-acronyms-and-terms/icann-acronyms-and-terms/en/nav/A) feature on icann.org. Our goal is to provide simple and consistent definitions for the community, including non-native English speakers and newcomers.
>
> We propose the following definition for the NCSG. Please let us know by Tuesday, 16 April if we can proceed with the following definition, or if you have any minor changes to suggest:
>
>  A stakeholder group within the Generic Names Supporting Organization that represents the interests of noncommercial registrants and noncommercial Internet users of generic top-level domains. The NCSG is a member of the Non-Contracted Parties House within the Generic Names Supporting Organization Council.
>
> The NCSG consists of two constituencies:
>
> ?          Non-Commercial Users Constituency (NCUC)
>
> ?          Not-for-Profit Operational Concerns Constituency (NPOC)
>
> We will also include a link to your community?s website, so that a user can learn additional information about your group.
>
> Thank you in advance, and we look forward to your feedback.
>
> Kind regards,

>
> Chantelle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190416/ff5894dd/attachment.htm>

From rafik.dammak at gmail.com  Wed Apr 17 13:57:43 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Wed, 17 Apr 2019 19:57:43 +0900
Subject: [NCSG-PC] Reminder NCSG Comment on the EPDP on Temp Spec for Board
 Consideration
In-Reply-To: <CAH5sThmdFAwQO+j321eyMczid5Yo+TkBTKL6cBhg5Yg4OpLnwA@mail.gmail.com>
References: <CA+Ks+AC=nz37JNrVrsM-Si_n4BMdnZvrKn0XDPWH3_Mk5h0wHQ@mail.gmail.com>
 <CAH5sThnA0W=81bAvyPP-0=Li2BMfP09gHmT7ff8o4EQBhDYr9A@mail.gmail.com>
 <CAH5sThmdFAwQO+j321eyMczid5Yo+TkBTKL6cBhg5Yg4OpLnwA@mail.gmail.com>
Message-ID: <CAH5sThm25unY=4Fg4n3oPBKeTkQdiSvowk4Op_xP+WzNpLo7ig@mail.gmail.com>

Hi all,

the final draft is a good shape and edits were solved. there are some
comments from Amr adding some background.
the deadline is today and we need to submit by the deadline. if there is no
objection, the comment will be submitted on time.

Best,

Rafik

Le lun. 15 avr. 2019 ? 18:50, Rafik Dammak <rafik.dammak at gmail.com> a
?crit :

> Hi,
>
> reminder to review the draft comment.
> the deadline for submission is the 17th april.
>
> Best,
>
> Rafik
>
> Le mer. 10 avr. 2019 ? 20:36, Rafik Dammak <rafik.dammak at gmail.com> a
> ?crit :
>
>> Hi,
>>
>> We have a draft comment to review for endorsement. Deadline for
>> submission is in 17th April.
>>
>> Best,
>>
>> Rafik
>>
>> ---------- Forwarded message ---------
>> From: Louise Marie Hurel <louise.marie.hsd at gmail.com>
>> Date: Wed, Apr 10, 2019, 20:33
>> Subject: [NCSG-Discuss] [Public Comment] NCSG Comment on the EPDP on Temp
>> Spec for Board Consideration
>> To: <NCSG-DISCUSS at listserv.syr.edu>
>>
>>
>> Hi all,
>>
>> Here's the link to the draft version of the NCSG comment on the *GNSO
>> Expedited Policy Development Process (EPDP) on the Temporary Specification
>> for gTLD Registration Data Policy Recommendations for ICANN Board
>> Consideration*:
>> https://docs.google.com/document/d/1YZe-AtxIMso3sobLSFSn_SsdDcsZS3myu8GNFfqZCQI/edit
>>
>>
>> As you will note, the main objective of this comment is to provide an
>> account and narrative as to where we compromised (and *not* to re-open
>> substantive policy discussions) and re-state our positions. Please feel
>> free to review the draft comment and share your thoughts, particularly
>> those that were on the EPDP team during Phase 1 and can provide a more
>> detailed background to the final report.
>>
>> The deadline for submission is *17 April*.
>>
>> Many thanks to Amr, Farzi and Stefan Filipovic for the comments!
>>
>> All the best,
>>
>> *Louise Marie Hurel*
>>
>> Research and Project Development
>>
>> Cybersecurity and Digital Liberties Programme | Igarap? Institute
>>
>> Publications
>> <https://www.researchgate.net/profile/Louise_Marie_Hurel/publications>
>> Skype: louise.dias
>> louise at igarape.org.br
>> louise.marie.hsd at gmail.com
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190417/fe2b3c9a/attachment.htm>

From rafik.dammak at gmail.com  Wed Apr 17 14:01:42 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Wed, 17 Apr 2019 20:01:42 +0900
Subject: [NCSG-PC] Replacement of representative to CCWG auctions proceeds
Message-ID: <CAH5sTh=dWC3LFss4cPYciFWkV3bdO_0xqC8Xj+pOMKTX_UrvwA@mail.gmail.com>

hello,

till now, Stephanie is the NCSG representative in CCWG Auctions proceeds.
She expressed her desire to step down and to be replaced by Julf. while the
WG is open , the representative has the ability to vote when it comes to
consensus call.
We just need to confirm this here and send the notice to GNSO secretariat
so the replacement to be confirmed by GNSO council in May meeting.

Best,

Rafik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190417/9c210ad7/attachment.htm>

From tatiana.tropina at gmail.com  Wed Apr 17 14:02:25 2019
From: tatiana.tropina at gmail.com (Tatiana Tropina)
Date: Wed, 17 Apr 2019 13:02:25 +0200
Subject: [NCSG-PC] Reminder NCSG Comment on the EPDP on Temp Spec for
 Board Consideration
In-Reply-To: <CAH5sThm25unY=4Fg4n3oPBKeTkQdiSvowk4Op_xP+WzNpLo7ig@mail.gmail.com>
References: <CA+Ks+AC=nz37JNrVrsM-Si_n4BMdnZvrKn0XDPWH3_Mk5h0wHQ@mail.gmail.com>
 <CAH5sThnA0W=81bAvyPP-0=Li2BMfP09gHmT7ff8o4EQBhDYr9A@mail.gmail.com>
 <CAH5sThmdFAwQO+j321eyMczid5Yo+TkBTKL6cBhg5Yg4OpLnwA@mail.gmail.com>
 <CAH5sThm25unY=4Fg4n3oPBKeTkQdiSvowk4Op_xP+WzNpLo7ig@mail.gmail.com>
Message-ID: <CADxLtgcsMzkA8S+JayxKfNMYiScyK5+JC9LnYK+xaoWUNO7saQ@mail.gmail.com>

Thank you Rafik, Amr and all. Supporting the submission.
Cheers,
Tanya

On Wed 17. Apr 2019 at 12:58, Rafik Dammak <rafik.dammak at gmail.com> wrote:

> Hi all,
>
> the final draft is a good shape and edits were solved. there are some
> comments from Amr adding some background.
> the deadline is today and we need to submit by the deadline. if there is
> no objection, the comment will be submitted on time.
>
> Best,
>
> Rafik
>
> Le lun. 15 avr. 2019 ? 18:50, Rafik Dammak <rafik.dammak at gmail.com> a
> ?crit :
>
>> Hi,
>>
>> reminder to review the draft comment.
>> the deadline for submission is the 17th april.
>>
>> Best,
>>
>> Rafik
>>
>> Le mer. 10 avr. 2019 ? 20:36, Rafik Dammak <rafik.dammak at gmail.com> a
>> ?crit :
>>
>>> Hi,
>>>
>>> We have a draft comment to review for endorsement. Deadline for
>>> submission is in 17th April.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> ---------- Forwarded message ---------
>>> From: Louise Marie Hurel <louise.marie.hsd at gmail.com>
>>> Date: Wed, Apr 10, 2019, 20:33
>>> Subject: [NCSG-Discuss] [Public Comment] NCSG Comment on the EPDP on
>>> Temp Spec for Board Consideration
>>> To: <NCSG-DISCUSS at listserv.syr.edu>
>>>
>>>
>>> Hi all,
>>>
>>> Here's the link to the draft version of the NCSG comment on the *GNSO
>>> Expedited Policy Development Process (EPDP) on the Temporary Specification
>>> for gTLD Registration Data Policy Recommendations for ICANN Board
>>> Consideration*:
>>> https://docs.google.com/document/d/1YZe-AtxIMso3sobLSFSn_SsdDcsZS3myu8GNFfqZCQI/edit
>>>
>>>
>>> As you will note, the main objective of this comment is to provide an
>>> account and narrative as to where we compromised (and *not* to re-open
>>> substantive policy discussions) and re-state our positions. Please feel
>>> free to review the draft comment and share your thoughts, particularly
>>> those that were on the EPDP team during Phase 1 and can provide a more
>>> detailed background to the final report.
>>>
>>> The deadline for submission is *17 April*.
>>>
>>> Many thanks to Amr, Farzi and Stefan Filipovic for the comments!
>>>
>>> All the best,
>>>
>>> *Louise Marie Hurel*
>>>
>>> Research and Project Development
>>>
>>> Cybersecurity and Digital Liberties Programme | Igarap? Institute
>>>
>>> Publications
>>> <https://www.researchgate.net/profile/Louise_Marie_Hurel/publications>
>>> Skype: louise.dias
>>> louise at igarape.org.br
>>> louise.marie.hsd at gmail.com
>>>
>>> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190417/a78c8151/attachment.htm>

From farell at benin2point0.org  Wed Apr 17 14:04:25 2019
From: farell at benin2point0.org (Ekue Farell Folly)
Date: Wed, 17 Apr 2019 13:04:25 +0200
Subject: [NCSG-PC] Reminder NCSG Comment on the EPDP on Temp Spec for
 Board Consideration
In-Reply-To: <CAH5sThm25unY=4Fg4n3oPBKeTkQdiSvowk4Op_xP+WzNpLo7ig@mail.gmail.com>
References: <CA+Ks+AC=nz37JNrVrsM-Si_n4BMdnZvrKn0XDPWH3_Mk5h0wHQ@mail.gmail.com>
 <CAH5sThnA0W=81bAvyPP-0=Li2BMfP09gHmT7ff8o4EQBhDYr9A@mail.gmail.com>
 <CAH5sThmdFAwQO+j321eyMczid5Yo+TkBTKL6cBhg5Yg4OpLnwA@mail.gmail.com>
 <CAH5sThm25unY=4Fg4n3oPBKeTkQdiSvowk4Op_xP+WzNpLo7ig@mail.gmail.com>
Message-ID: <6c275684e77f483f03a475c76f82f4db69a2ebfd.camel@benin2point0.org>

Thanks Rafik for the reminder.
As you said, the report is in a good shape, in a very good shape I
would confirm. 
I think we can submit it. Once more, many thanks to all the drafters
and contributors.

On Wed, 2019-04-17 at 19:57 +0900, Rafik Dammak wrote:
> Hi all,
> 
> the final draft is a good shape and edits were solved. there are some
> comments from Amr adding some background.
> the deadline is today and we need to submit by the deadline. if there
> is no objection, the comment will be submitted on time.
> 
> Best,
> 
> Rafik
> 
> Le lun. 15 avr. 2019 ? 18:50, Rafik Dammak <rafik.dammak at gmail.com> a
> ?crit :
> > Hi,
> > 
> > reminder to review the draft comment.
> > the deadline for submission is the 17th april.
> > 
> > Best,
> > 
> > Rafik
> > 
> > Le mer. 10 avr. 2019 ? 20:36, Rafik Dammak <rafik.dammak at gmail.com>
> > a ?crit :
> > > Hi,
> > > 
> > > We have a draft comment to review for endorsement. Deadline for
> > > submission is in 17th April.
> > > 
> > > Best,
> > > 
> > > Rafik 
> > > 
> > > ---------- Forwarded message ---------
> > > From: Louise Marie Hurel <louise.marie.hsd at gmail.com>
> > > Date: Wed, Apr 10, 2019, 20:33
> > > Subject: [NCSG-Discuss] [Public Comment] NCSG Comment on the EPDP
> > > on Temp Spec for Board Consideration
> > > To:  <NCSG-DISCUSS at listserv.syr.edu>
> > > 
> > > 
> > > Hi all,
> > > Here's the link to the draft version of the NCSG comment on the
> > > GNSO Expedited Policy Development Process (EPDP) on the Temporary
> > > Specification for gTLD Registration Data Policy Recommendations
> > > for ICANN Board Consideration: 
> > > https://docs.google.com/document/d/1YZe-AtxIMso3sobLSFSn_SsdDcsZS3myu8GNFfqZCQI/edit
> > >  
> > > 
> > > As you will note, the main objective of this comment is to
> > > provide an account and narrative as to where we compromised (and
> > > not to re-open substantive policy discussions) and re-state
> > > our positions. Please feel free to review the draft comment and
> > > share your thoughts, particularly those that were on the EPDP
> > > team during Phase 1 and can provide a more detailed background to
> > > the final report.
> > > 
> > > The deadline for submission is 17 April.
> > > 
> > > Many thanks to Amr, Farzi and Stefan Filipovic for the comments! 
> > > 
> > > All the best, 
> > > 
> > > Louise Marie Hurel
> > > Research and Project Development 
> > > Cybersecurity and Digital Liberties Programme | Igarap? Institute
> > > Publications
> > > Skype: louise.dias
> > > louise at igarape.org.br
> > > louise.marie.hsd at gmail.com 
> > > 
> > > 
> > > 
> 
> _______________________________________________NCSG-PC mailing
> listNCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190417/243cd668/attachment.htm>

From rafik.dammak at gmail.com  Wed Apr 17 14:11:33 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Wed, 17 Apr 2019 20:11:33 +0900
Subject: [NCSG-PC] [Urgent] NCSG Candidate to PIR advisory council
Message-ID: <CAH5sThkfo99jT6Gs+TV75ja+j_NXBApXoNUj1Vi0f4iGbQF5eg@mail.gmail.com>

hello all,

we got an urgent selection to do in timely manner as we have a strict
deadline.
if you recall there was a call for candidates in NCSG list (
https://listserv.syr.edu/scripts/wa.exe?A2=NCSG-DISCUSS;5adc76d6.1902) to
to be nominated to PIR advisory council for PIR nominating committee
consideration. We should send slate of 3 candidates by 24th April.

I will send the names of those who applied offlist for PC members
consideration. However, 2 members of NCSG PC should recuse themselves from
the selection as they have applied.
let me know if you have any objection with proceeding. otherwise I will
send the application and we can start the process.

Best,

Rafik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190417/4dd3d683/attachment.htm>

From rafik.dammak at gmail.com  Wed Apr 17 14:28:38 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Wed, 17 Apr 2019 20:28:38 +0900
Subject: [NCSG-PC] Call for NCSG alternate to EPDP team
In-Reply-To: <CAH5sThkCt5cDSdcbu1PNA9fESTxbbfnNq5XcFrm3_2LwA3C4aQ@mail.gmail.com>
References: <CAH5sTh=vRw3YuRXSWeWSXDsDx-55LihhOnRHQszqV_9L=NUW1A@mail.gmail.com>
 <CAH5sThkac-eeZAQ-ke8MD9qZOBJ5ysDjs82ynbKS3Z8a+QgXpw@mail.gmail.com>
 <6d84d832-a099-4aeb-dfd8-f0e563d48da0@mail.utoronto.ca>
 <CAH5sThm6QDHqrxcf4T71QTa6EFXn3tPvQX97mVOKx-SOG19jZg@mail.gmail.com>
 <CAH5sThnnsX430pj7o4O=4Rcge83CNsYDXUPkYKrjY-AW-Y8YaA@mail.gmail.com>
 <CABDXvWq3Y_5R2PE-RX8hvHNyfZdoxD37uNJpdFiW1dRu0BwauQ@mail.gmail.com>
 <CAH5sThkCt5cDSdcbu1PNA9fESTxbbfnNq5XcFrm3_2LwA3C4aQ@mail.gmail.com>
Message-ID: <CAH5sThkcmLC+r5qNnCZz4m8auuAA=UxyeSigU8GgAnZWTM4P=g@mail.gmail.com>

Hi all,

since the start of phase 2 is close we need to replace Collin as alternate.
here a draft call for candidates tweaked from the call we made in last
summer  and adjust it to phase 2
https://docs.google.com/document/d/1NqqaDC0aSOgLCOFe4flKQ2MTA0hTbw8xgloFAzTauSw/edit
 .

As timeline, I think 1 week for a call and 3 days for selection is enough
since we only have one slot of fill.
please share your thoughts as we should start this process quickly and have
an alternate on time to be able to follow the discussions and be ready to
step up.

Best,

Rafik

---------- Forwarded message ---------
De : Rafik Dammak <rafik.dammak at gmail.com>
Date: lun. 1 avr. 2019 ? 15:05
Subject: Re: [NCSG-PC] NCSG representatives to EPDP team
To: ncsg-pc at lists.ncsg.is <ncsg-pc at lists.ncsg.is>


hi all

for the replacement, I proposed before to tweak the previous call for
candidates to replace Collin and update with bits relevant to phase 2 but
also regarding expected knowledge of phase 1. if there is no objection, I
will share the draft call within this week so we can start a short call by
next week.

Best,

Rafik

Le ven. 29 mars 2019 ? 19:09, Ars?ne Tungali <arsenebaguma at gmail.com> a
?crit :

> Thanks, everyone for willing to continue, I believe this is good for
> us that you are willling to continue representing us throughout phase
> 2.
>
> I am sure we will be able to have a replacement for Collin whom I
> would like to thank for being there during phase 1 as an alternate.
>
> 2019-03-29 2:04 UTC+02:00, Rafik Dammak <rafik.dammak at gmail.com>:
> > Hi,
> >
> > all current EPDP representatives confirmed they will continue for phase 2
> > and Tatiana and David as alternates.
> > we only have to replace Collin as alternate.
> >
> > Best,
> >
> > Rafik
> > Le mer. 27 mars 2019 ? 23:47, Rafik Dammak <rafik.dammak at gmail.com> a
> > ?crit :
> >
> >> thanks Stephanie.
> >> we are still missing Ayden and Julf confirmation. I thought Ayden
> >> expressed his intention to not continue previously but stated he was
> >> still
> >> thinking during Kobe meeting in PC session.
> >> I would like to close this quickly and that we do call for candidates
> >> asap.
> >>
> >> Best,
> >>
> >> Rafik
> >>
> >> Le mer. 27 mars 2019 ? 00:48, Stephanie Perrin <
> >> stephanie.perrin at mail.utoronto.ca> a ?crit :
> >>
> >>> Sorry, I thought I had confirmed. Yes, I am in for the next haul.
> >>>
> >>> Stephanie
> >>> On 2019-03-26 00:11, Rafik Dammak wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I am resuming the discussion for this. First action will to finalize
> the
> >>> confirmation with all members.
> >>> I only heard from Farzaneh, Milton, Amr that they will continue as rep
> >>> and Tatiana and David as alternate.I assume Stephanie will continue.
> >>> I aiming to confirm by Friday so we can have fairly quick call to
> >>> replace
> >>> if needed.
> >>>
> >>> Best,
> >>>
> >>> Rafik
> >>> Le mar. 5 mars 2019 ? 08:17, Rafik Dammak <rafik.dammak at gmail.com> a
> >>> ?crit :
> >>>
> >>>> Hi all,
> >>>>
> >>>> Keith communicated last week with all chairs of groups represented in
> >>>> EPDP team to confirm or replace their members there for phase 2. The
> >>>> same
> >>>> communication was shared with EPDP team.
> >>>>
> >>>> We are confirming with our NCSG representatives if they are willing to
> >>>> continue for phase 2. We might need to do some replacements and we
> have
> >>>> to
> >>>> act quickly in order for new appointees to catch-up. It also depends
> on
> >>>> the
> >>>> expected workload and that is ongoing discussion.
> >>>>
> >>>> One way is to tweak the previous call for candidates and send it asap
> >>>> in
> >>>> order to get a good pool of candidates from where to select.
> >>>> please let me know your thoughts and suggestions.
> >>>>
> >>>> Best,
> >>>>
> >>>> Rafik
> >>>>
> >>>
> >>> _______________________________________________
> >>> NCSG-PC mailing
> >>> listNCSG-PC at lists.ncsg.ishttps://
> lists.ncsg.is/mailman/listinfo/ncsg-pc
> >>>
> >>> _______________________________________________
> >>> NCSG-PC mailing list
> >>> NCSG-PC at lists.ncsg.is
> >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> >>>
> >>
> >
>
>
> --
> ------------------------
> **Ars?ne Tungali* <http://about.me/ArseneTungali>*
> Co-Founder & Executive Director, *Rudi international
> <http://www.rudiinternational.org>*,
> CEO,* Smart Services Sarl <https://www.smart-kitoko.com/>*,
> Tel: +243 993810967 (DRC)
> GPG: 523644A0
>
> 2015 Mandela Washington Fellow
> <
>
> http://tungali.blogspot.com/2015/06/selected-for-2015-mandela-washington.html
> >
>
> (YALI) - ICANN GNSO Council Member
> <https://gnso.icann.org/en/about/gnso-council.htm> Member. UN IGF MAG
> <https://www.un.org/press/en/2018/pi2247.doc.htm> Member
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190417/b3cc1935/attachment.htm>

From rafik.dammak at gmail.com  Wed Apr 17 14:44:19 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Wed, 17 Apr 2019 20:44:19 +0900
Subject: [NCSG-PC] =?utf-8?q?Adding_NCSG_rep_to_GNSO_Drafting_Team_to_Furt?=
	=?utf-8?q?her_Develop_Guidelines_and_Principles_for_the_GNSO?=
	=?utf-8?q?=E2=80=99s_Roles_and_Obligations_as_a_Decisional_Partici?=
	=?utf-8?q?pant_in_the_Empowered_Community?=
Message-ID: <CAH5sThnOL_bQP2cYd=pSRdLtWFyNkqTcWaAZNMQKTc5sfWyb+Q@mail.gmail.com>

Hi all,

as you might know there is a drafting team working on "Develop Guidelines
and Principles for the GNSO?s Roles and Obligations as a Decisional
Participant in the Empowered Community". We have there Stephanie and
Farzaneh as members but Farzaneh expressed that she cannot continue and
would like to be replaced. Stephanie also expressed that she needs support.
When the deliverable will come to council it would be too late to make
substantial changes.

We need someone with experience on CWG/CCWG recommendations and to some
extent familiarity with GNSO OP. Based on DT timeline shared in council,
the work will finish by June/July. Therefore such participation will be
time limited and shouldn't represent a huge commitment.
I was thinking to volunteer Tatiana but I don't want to press. so looking
to hear if there is any suggestion so the member can get on board quickly.

Best,

Rafik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190417/99dcbac3/attachment.htm>

From tatiana.tropina at gmail.com  Wed Apr 17 15:04:30 2019
From: tatiana.tropina at gmail.com (Tatiana Tropina)
Date: Wed, 17 Apr 2019 14:04:30 +0200
Subject: [NCSG-PC] 
	=?utf-8?q?Adding_NCSG_rep_to_GNSO_Drafting_Team_to_Fur?=
	=?utf-8?q?ther_Develop_Guidelines_and_Principles_for_the_GNSO?=
	=?utf-8?q?=E2=80=99s_Roles_and_Obligations_as_a_Decisional_Partici?=
	=?utf-8?q?pant_in_the_Empowered_Community?=
In-Reply-To: <CAH5sThnOL_bQP2cYd=pSRdLtWFyNkqTcWaAZNMQKTc5sfWyb+Q@mail.gmail.com>
References: <CAH5sThnOL_bQP2cYd=pSRdLtWFyNkqTcWaAZNMQKTc5sfWyb+Q@mail.gmail.com>
Message-ID: <CADxLtgeTy=pBgvSCa+HHDy7SbOsbrrfj3FqdX8AvqLK0HS=ciA@mail.gmail.com>

Rafik,
I had time to think after policy call ? yes. I will join.
Cheers,
Tanya

On Wed 17. Apr 2019 at 13:44, Rafik Dammak <rafik.dammak at gmail.com> wrote:

> Hi all,
>
> as you might know there is a drafting team working on "Develop Guidelines
> and Principles for the GNSO?s Roles and Obligations as a Decisional
> Participant in the Empowered Community". We have there Stephanie and
> Farzaneh as members but Farzaneh expressed that she cannot continue and
> would like to be replaced. Stephanie also expressed that she needs support.
> When the deliverable will come to council it would be too late to make
> substantial changes.
>
> We need someone with experience on CWG/CCWG recommendations and to some
> extent familiarity with GNSO OP. Based on DT timeline shared in council,
> the work will finish by June/July. Therefore such participation will be
> time limited and shouldn't represent a huge commitment.
> I was thinking to volunteer Tatiana but I don't want to press. so looking
> to hear if there is any suggestion so the member can get on board quickly.
>
> Best,
>
> Rafik
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190417/d84e5ce1/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Wed Apr 17 18:54:09 2019
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Wed, 17 Apr 2019 15:54:09 +0000
Subject: [NCSG-PC] [Urgent] NCSG Candidate to PIR advisory council
In-Reply-To: <CAH5sThkfo99jT6Gs+TV75ja+j_NXBApXoNUj1Vi0f4iGbQF5eg@mail.gmail.com>
References: <CAH5sThkfo99jT6Gs+TV75ja+j_NXBApXoNUj1Vi0f4iGbQF5eg@mail.gmail.com>
Message-ID: <78fcb416-7d65-0d57-1cd2-472f09b18003@mail.utoronto.ca>

Go for it.  I applied so will recuse myself.

Thanks

Stephanie

On 2019-04-17 07:11, Rafik Dammak wrote:
hello all,

we got an urgent selection to do in timely manner as we have a strict deadline.
if you recall there was a call for candidates in NCSG list (https://listserv.syr.edu/scripts/wa.exe?A2=NCSG-DISCUSS;5adc76d6.1902) to to be nominated to PIR advisory council for PIR nominating committee consideration. We should send slate of 3 candidates by 24th April.

I will send the names of those who applied offlist for PC members consideration. However, 2 members of NCSG PC should recuse themselves from the selection as they have applied.
let me know if you have any objection with proceeding. otherwise I will send the application and we can start the process.

Best,

Rafik



_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190417/5003497c/attachment.htm>

From rafik.dammak at gmail.com  Thu Apr 18 01:49:36 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 18 Apr 2019 07:49:36 +0900
Subject: [NCSG-PC] 
	=?utf-8?q?Adding_NCSG_rep_to_GNSO_Drafting_Team_to_Fur?=
	=?utf-8?q?ther_Develop_Guidelines_and_Principles_for_the_GNSO?=
	=?utf-8?q?=E2=80=99s_Roles_and_Obligations_as_a_Decisional_Partici?=
	=?utf-8?q?pant_in_the_Empowered_Community?=
In-Reply-To: <CADxLtgeTy=pBgvSCa+HHDy7SbOsbrrfj3FqdX8AvqLK0HS=ciA@mail.gmail.com>
References: <CAH5sThnOL_bQP2cYd=pSRdLtWFyNkqTcWaAZNMQKTc5sfWyb+Q@mail.gmail.com>
 <CADxLtgeTy=pBgvSCa+HHDy7SbOsbrrfj3FqdX8AvqLK0HS=ciA@mail.gmail.com>
Message-ID: <CAH5sTh=avYHP_AERU31K91CMduLymeDyNS4_POM=p+A1fD6WiQ@mail.gmail.com>

thanks Tatiana, I will notify the GNSO secretariat.

Best,

Rafik

Le mer. 17 avr. 2019 ? 21:04, Tatiana Tropina <tatiana.tropina at gmail.com> a
?crit :

> Rafik,
> I had time to think after policy call ? yes. I will join.
> Cheers,
> Tanya
>
> On Wed 17. Apr 2019 at 13:44, Rafik Dammak <rafik.dammak at gmail.com> wrote:
>
>> Hi all,
>>
>> as you might know there is a drafting team working on "Develop Guidelines
>> and Principles for the GNSO?s Roles and Obligations as a Decisional
>> Participant in the Empowered Community". We have there Stephanie and
>> Farzaneh as members but Farzaneh expressed that she cannot continue and
>> would like to be replaced. Stephanie also expressed that she needs support.
>> When the deliverable will come to council it would be too late to make
>> substantial changes.
>>
>> We need someone with experience on CWG/CCWG recommendations and to some
>> extent familiarity with GNSO OP. Based on DT timeline shared in council,
>> the work will finish by June/July. Therefore such participation will be
>> time limited and shouldn't represent a huge commitment.
>> I was thinking to volunteer Tatiana but I don't want to press. so looking
>> to hear if there is any suggestion so the member can get on board quickly.
>>
>> Best,
>>
>> Rafik
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190418/7d1bae89/attachment.htm>

From icann at ferdeline.com  Thu Apr 18 15:21:58 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Thu, 18 Apr 2019 12:21:58 +0000
Subject: [NCSG-PC] [Urgent] NCSG Candidate to PIR advisory council
In-Reply-To: <78fcb416-7d65-0d57-1cd2-472f09b18003@mail.utoronto.ca>
References: <CAH5sThkfo99jT6Gs+TV75ja+j_NXBApXoNUj1Vi0f4iGbQF5eg@mail.gmail.com>
 <78fcb416-7d65-0d57-1cd2-472f09b18003@mail.utoronto.ca>
Message-ID: <9XPn8vxFzrX_gyVipKIVNcYehQcvn_ooIwz3gfHPe220cKkRGVz9RsLPLlVpcI7Y7JoIJ9aUvrOuQCeamP-fM3xwzGD_nw3btdBOCRc6yjg=@ferdeline.com>

I also wish to recuse myself, as I submitted an application as well.

Many thanks,
Ayden

??????? Original Message ???????
On Wednesday, April 17, 2019 5:54 PM, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> wrote:

> Go for it.  I applied so will recuse myself.
>
> Thanks
>
> Stephanie
>
> On 2019-04-17 07:11, Rafik Dammak wrote:
>
>> hello all,
>>
>> we got an urgent selection to do in timely manner as we have a strict deadline.
>> if you recall there was a call for candidates in NCSG list (https://listserv.syr.edu/scripts/wa.exe?A2=NCSG-DISCUSS;5adc76d6.1902) to to be nominated to PIR advisory council for PIR nominating committee consideration. We should send slate of 3 candidates by 24th April.
>>
>> I will send the names of those who applied offlist for PC members consideration. However, 2 members of NCSG PC should recuse themselves from the selection as they have applied.
>> let me know if you have any objection with proceeding. otherwise I will send the application and we can start the process.
>>
>> Best,
>>
>> Rafik
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>>
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190418/d5ea772e/attachment.htm>

From icann at ferdeline.com  Thu Apr 18 15:54:27 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Thu, 18 Apr 2019 12:54:27 +0000
Subject: [NCSG-PC] Replacement of representative to CCWG auctions
 proceeds
In-Reply-To: <CAH5sTh=dWC3LFss4cPYciFWkV3bdO_0xqC8Xj+pOMKTX_UrvwA@mail.gmail.com>
References: <CAH5sTh=dWC3LFss4cPYciFWkV3bdO_0xqC8Xj+pOMKTX_UrvwA@mail.gmail.com>
Message-ID: <tihH0m1TZRRKysM80v1Q4A7gdorXGZog_2sJWMWcf9F40QUGYcO5leGyYDnKDqCgQ9EuoCBNZzXrqFnM5Umh_p4zoxMkLMgA49M0-WsjcVM=@ferdeline.com>

If we are being asked if we have any objections to this change, I have none and would be happy to see Julf become our member there. Thanks.

-- Ayden

??????? Original Message ???????
On Wednesday, April 17, 2019 1:01 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:

> hello,
>
> till now, Stephanie is the NCSG representative in CCWG Auctions proceeds. She expressed her desire to step down and to be replaced by Julf. while the WG is open , the representative has the ability to vote when it comes to consensus call.
> We just need to confirm this here and send the notice to GNSO secretariat so the replacement to be confirmed by GNSO council in May meeting.
>
> Best,
>
> Rafik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190418/7ef81430/attachment.htm>

From tatiana.tropina at gmail.com  Thu Apr 18 15:59:51 2019
From: tatiana.tropina at gmail.com (Tatiana Tropina)
Date: Thu, 18 Apr 2019 14:59:51 +0200
Subject: [NCSG-PC] Replacement of representative to CCWG auctions
 proceeds
In-Reply-To: <tihH0m1TZRRKysM80v1Q4A7gdorXGZog_2sJWMWcf9F40QUGYcO5leGyYDnKDqCgQ9EuoCBNZzXrqFnM5Umh_p4zoxMkLMgA49M0-WsjcVM=@ferdeline.com>
References: <CAH5sTh=dWC3LFss4cPYciFWkV3bdO_0xqC8Xj+pOMKTX_UrvwA@mail.gmail.com>
 <tihH0m1TZRRKysM80v1Q4A7gdorXGZog_2sJWMWcf9F40QUGYcO5leGyYDnKDqCgQ9EuoCBNZzXrqFnM5Umh_p4zoxMkLMgA49M0-WsjcVM=@ferdeline.com>
Message-ID: <CADxLtgcv5+rfKXkYxzQzdf1xbP+DQTLNYCoqcCyubKLnd2-BJA@mail.gmail.com>

+1, absolutely no objection.
Cheers
Tanya

On Thu 18. Apr 2019 at 14:54, Ayden F?rdeline <icann at ferdeline.com> wrote:

> If we are being asked if we have any objections to this change, I have
> none and would be happy to see Julf become our member there. Thanks.
>
> -- Ayden
>
>
> ??????? Original Message ???????
> On Wednesday, April 17, 2019 1:01 PM, Rafik Dammak <rafik.dammak at gmail.com>
> wrote:
>
> hello,
>
> till now, Stephanie is the NCSG representative in CCWG Auctions proceeds.
> She expressed her desire to step down and to be replaced by Julf. while the
> WG is open , the representative has the ability to vote when it comes to
> consensus call.
> We just need to confirm this here and send the notice to GNSO secretariat
> so the replacement to be confirmed by GNSO council in May meeting.
>
> Best,
>
> Rafik
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190418/a9c165f8/attachment.htm>

From pileleji at ymca.gm  Thu Apr 18 18:28:29 2019
From: pileleji at ymca.gm (Poncelet Ileleji)
Date: Thu, 18 Apr 2019 16:28:29 +0100
Subject: [NCSG-PC] [Urgent] NCSG Candidate to PIR advisory council
In-Reply-To: <9XPn8vxFzrX_gyVipKIVNcYehQcvn_ooIwz3gfHPe220cKkRGVz9RsLPLlVpcI7Y7JoIJ9aUvrOuQCeamP-fM3xwzGD_nw3btdBOCRc6yjg=@ferdeline.com>
References: <CAH5sThkfo99jT6Gs+TV75ja+j_NXBApXoNUj1Vi0f4iGbQF5eg@mail.gmail.com>
 <78fcb416-7d65-0d57-1cd2-472f09b18003@mail.utoronto.ca>
 <9XPn8vxFzrX_gyVipKIVNcYehQcvn_ooIwz3gfHPe220cKkRGVz9RsLPLlVpcI7Y7JoIJ9aUvrOuQCeamP-fM3xwzGD_nw3btdBOCRc6yjg=@ferdeline.com>
Message-ID: <CAEux40ug-XY9upyThDkaptWpB0+ff2Qx5t_JOk_jyyjhEp-4xQ@mail.gmail.com>

Hello All,

Am also recusing myself, as I submitted an application too.

Kind Regards

Poncelet

On Thu, 18 Apr 2019 at 13:22, Ayden F?rdeline <icann at ferdeline.com> wrote:

> I also wish to recuse myself, as I submitted an application as well.
>
> Many thanks,
> Ayden
>
>
> ??????? Original Message ???????
> On Wednesday, April 17, 2019 5:54 PM, Stephanie Perrin <
> stephanie.perrin at mail.utoronto.ca> wrote:
>
> Go for it.  I applied so will recuse myself.
>
> Thanks
>
> Stephanie
> On 2019-04-17 07:11, Rafik Dammak wrote:
>
> hello all,
>
> we got an urgent selection to do in timely manner as we have a strict
> deadline.
> if you recall there was a call for candidates in NCSG list (
> https://listserv.syr.edu/scripts/wa.exe?A2=NCSG-DISCUSS;5adc76d6.1902) to
> to be nominated to PIR advisory council for PIR nominating committee
> consideration. We should send slate of 3 candidates by 24th April.
>
> I will send the names of those who applied offlist for PC members
> consideration. However, 2 members of NCSG PC should recuse themselves from
> the selection as they have applied.
> let me know if you have any objection with proceeding. otherwise I will
> send the application and we can start the process.
>
> Best,
>
> Rafik
>
> _______________________________________________
> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>


-- 
Poncelet O. Ileleji MBCS
Coordinator
The Gambia YMCAs Computer Training Centre & Digital Studio
MDI Road Kanifing South
P. O. Box 421 Banjul
The Gambia, West Africa
Tel: (220) 4370240
Fax:(220) 4390793
Cell:(220) 9912508
Skype: pons_utd






*www.ymca.gm <http://www.ymca.gm>http://jokkolabs.net/en/
<http://jokkolabs.net/en/>www.waigf.org
<http://www.waigf.org>www,insistglobal.com <http://www.itag.gm>www.npoc.org
<http://www.npoc.org>http://www.wsa-mobile.org/node/753
<http://www.wsa-mobile.org/node/753>*www.diplointernetgovernance.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190418/a7cf6eb6/attachment.htm>

From arsenebaguma at gmail.com  Thu Apr 18 20:08:34 2019
From: arsenebaguma at gmail.com (=?utf-8?Q?Ars=C3=A8ne_Tungali?=)
Date: Thu, 18 Apr 2019 19:08:34 +0200
Subject: [NCSG-PC] Replacement of representative to CCWG auctions
 proceeds
In-Reply-To: <CADxLtgcv5+rfKXkYxzQzdf1xbP+DQTLNYCoqcCyubKLnd2-BJA@mail.gmail.com>
References: <CAH5sTh=dWC3LFss4cPYciFWkV3bdO_0xqC8Xj+pOMKTX_UrvwA@mail.gmail.com>
 <tihH0m1TZRRKysM80v1Q4A7gdorXGZog_2sJWMWcf9F40QUGYcO5leGyYDnKDqCgQ9EuoCBNZzXrqFnM5Umh_p4zoxMkLMgA49M0-WsjcVM=@ferdeline.com>
 <CADxLtgcv5+rfKXkYxzQzdf1xbP+DQTLNYCoqcCyubKLnd2-BJA@mail.gmail.com>
Message-ID: <FCDC7274-D36A-4B78-A45B-FD9C479A5F2F@gmail.com>

No objection from me as well!

Sent from my iPhone

> On 18 Apr 2019, at 14:59, Tatiana Tropina <tatiana.tropina at gmail.com> wrote:
> 
> +1, absolutely no objection. 
> Cheers 
> Tanya 
> 
>> On Thu 18. Apr 2019 at 14:54, Ayden F?rdeline <icann at ferdeline.com> wrote:
>> If we are being asked if we have any objections to this change, I have none and would be happy to see Julf become our member there. Thanks.
>> 
>> -- Ayden 
>> 
>> 
>> ??????? Original Message ???????
>>> On Wednesday, April 17, 2019 1:01 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
>>> 
>>> hello,
>>> 
>>> till now, Stephanie is the NCSG representative in CCWG Auctions proceeds. She expressed her desire to step down and to be replaced by Julf. while the WG is open , the representative has the ability to vote when it comes to consensus call.
>>> We just need to confirm this here and send the notice to GNSO secretariat so the replacement to be confirmed by GNSO council in May meeting.
>>> 
>>> Best,
>>> 
>>> Rafik
>>> 
>> 
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190418/651c530c/attachment.htm>

From pileleji at ymca.gm  Thu Apr 18 20:09:25 2019
From: pileleji at ymca.gm (Poncelet Ileleji)
Date: Thu, 18 Apr 2019 18:09:25 +0100
Subject: [NCSG-PC] Replacement of representative to CCWG auctions
 proceeds
In-Reply-To: <FCDC7274-D36A-4B78-A45B-FD9C479A5F2F@gmail.com>
References: <CAH5sTh=dWC3LFss4cPYciFWkV3bdO_0xqC8Xj+pOMKTX_UrvwA@mail.gmail.com>
 <tihH0m1TZRRKysM80v1Q4A7gdorXGZog_2sJWMWcf9F40QUGYcO5leGyYDnKDqCgQ9EuoCBNZzXrqFnM5Umh_p4zoxMkLMgA49M0-WsjcVM=@ferdeline.com>
 <CADxLtgcv5+rfKXkYxzQzdf1xbP+DQTLNYCoqcCyubKLnd2-BJA@mail.gmail.com>
 <FCDC7274-D36A-4B78-A45B-FD9C479A5F2F@gmail.com>
Message-ID: <CAEux40t9quLPKgB3JnVgeE4iHURbjG1ScXoWyjxpZj+xM+AsGQ@mail.gmail.com>

+1 also

On Thu, 18 Apr 2019 at 18:08, Ars?ne Tungali <arsenebaguma at gmail.com> wrote:

> No objection from me as well!
>
> Sent from my iPhone
>
> On 18 Apr 2019, at 14:59, Tatiana Tropina <tatiana.tropina at gmail.com>
> wrote:
>
> +1, absolutely no objection.
> Cheers
> Tanya
>
> On Thu 18. Apr 2019 at 14:54, Ayden F?rdeline <icann at ferdeline.com> wrote:
>
>> If we are being asked if we have any objections to this change, I have
>> none and would be happy to see Julf become our member there. Thanks.
>>
>> -- Ayden
>>
>>
>> ??????? Original Message ???????
>> On Wednesday, April 17, 2019 1:01 PM, Rafik Dammak <
>> rafik.dammak at gmail.com> wrote:
>>
>> hello,
>>
>> till now, Stephanie is the NCSG representative in CCWG Auctions proceeds.
>> She expressed her desire to step down and to be replaced by Julf. while the
>> WG is open , the representative has the ability to vote when it comes to
>> consensus call.
>> We just need to confirm this here and send the notice to GNSO secretariat
>> so the replacement to be confirmed by GNSO council in May meeting.
>>
>> Best,
>>
>> Rafik
>>
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>


-- 
Poncelet O. Ileleji MBCS
Coordinator
The Gambia YMCAs Computer Training Centre & Digital Studio
MDI Road Kanifing South
P. O. Box 421 Banjul
The Gambia, West Africa
Tel: (220) 4370240
Fax:(220) 4390793
Cell:(220) 9912508
Skype: pons_utd






*www.ymca.gm <http://www.ymca.gm>http://jokkolabs.net/en/
<http://jokkolabs.net/en/>www.waigf.org
<http://www.waigf.org>www,insistglobal.com <http://www.itag.gm>www.npoc.org
<http://www.npoc.org>http://www.wsa-mobile.org/node/753
<http://www.wsa-mobile.org/node/753>*www.diplointernetgovernance.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190418/b9aa104e/attachment.htm>

From rafik.dammak at gmail.com  Fri Apr 19 15:11:11 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Fri, 19 Apr 2019 21:11:11 +0900
Subject: [NCSG-PC] Replacement of representative to CCWG auctions
 proceeds
In-Reply-To: <CAEux40t9quLPKgB3JnVgeE4iHURbjG1ScXoWyjxpZj+xM+AsGQ@mail.gmail.com>
References: <CAH5sTh=dWC3LFss4cPYciFWkV3bdO_0xqC8Xj+pOMKTX_UrvwA@mail.gmail.com>
 <tihH0m1TZRRKysM80v1Q4A7gdorXGZog_2sJWMWcf9F40QUGYcO5leGyYDnKDqCgQ9EuoCBNZzXrqFnM5Umh_p4zoxMkLMgA49M0-WsjcVM=@ferdeline.com>
 <CADxLtgcv5+rfKXkYxzQzdf1xbP+DQTLNYCoqcCyubKLnd2-BJA@mail.gmail.com>
 <FCDC7274-D36A-4B78-A45B-FD9C479A5F2F@gmail.com>
 <CAEux40t9quLPKgB3JnVgeE4iHURbjG1ScXoWyjxpZj+xM+AsGQ@mail.gmail.com>
Message-ID: <CAH5sThkNrCC7Tzn-dCOd8cmM9QkE0U7nF1hf0kGNtBw6jhHKGQ@mail.gmail.com>

Hi all,

seeing no objection, I will inform the GNSO secretariat about the
replacement.

Best,

Rafik

Le ven. 19 avr. 2019 ? 02:09, Poncelet Ileleji <pileleji at ymca.gm> a ?crit :

> +1 also
>
> On Thu, 18 Apr 2019 at 18:08, Ars?ne Tungali <arsenebaguma at gmail.com>
> wrote:
>
>> No objection from me as well!
>>
>> Sent from my iPhone
>>
>> On 18 Apr 2019, at 14:59, Tatiana Tropina <tatiana.tropina at gmail.com>
>> wrote:
>>
>> +1, absolutely no objection.
>> Cheers
>> Tanya
>>
>> On Thu 18. Apr 2019 at 14:54, Ayden F?rdeline <icann at ferdeline.com>
>> wrote:
>>
>>> If we are being asked if we have any objections to this change, I have
>>> none and would be happy to see Julf become our member there. Thanks.
>>>
>>> -- Ayden
>>>
>>>
>>> ??????? Original Message ???????
>>> On Wednesday, April 17, 2019 1:01 PM, Rafik Dammak <
>>> rafik.dammak at gmail.com> wrote:
>>>
>>> hello,
>>>
>>> till now, Stephanie is the NCSG representative in CCWG Auctions
>>> proceeds. She expressed her desire to step down and to be replaced by Julf.
>>> while the WG is open , the representative has the ability to vote when it
>>> comes to consensus call.
>>> We just need to confirm this here and send the notice to GNSO
>>> secretariat so the replacement to be confirmed by GNSO council in May
>>> meeting.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>
>
> --
> Poncelet O. Ileleji MBCS
> Coordinator
> The Gambia YMCAs Computer Training Centre & Digital Studio
> MDI Road Kanifing South
> P. O. Box 421 Banjul
> The Gambia, West Africa
> Tel: (220) 4370240
> Fax:(220) 4390793
> Cell:(220) 9912508
> Skype: pons_utd
>
>
>
>
>
>
> *www.ymca.gm <http://www.ymca.gm>http://jokkolabs.net/en/
> <http://jokkolabs.net/en/>www.waigf.org
> <http://www.waigf.org>www,insistglobal.com <http://www.itag.gm>www.npoc.org
> <http://www.npoc.org>http://www.wsa-mobile.org/node/753
> <http://www.wsa-mobile.org/node/753>*www.diplointernetgovernance.org
>
>
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190419/75aabc19/attachment.htm>

From mkaranicolas at gmail.com  Tue Apr 23 05:42:34 2019
From: mkaranicolas at gmail.com (Michael Karanicolas)
Date: Mon, 22 Apr 2019 23:42:34 -0300
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
Message-ID: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>

Hello all,

Hope you are well. I am just writing regarding the public comment for
renewing the .org registry agreement.

I reached out to Stephanie a few days ago about the possibility of an NCSG
submission, and she suggested there might be some possibility to get
something approved in advance of the April 29 deadline. I am attaching a
first draft, and would be keen to hear what you think.

Best wishes,

Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190422/ab10ca57/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Org Letter Rev.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 19412 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190422/ab10ca57/attachment.docx>

From mpsilvavalent at gmail.com  Tue Apr 23 06:09:20 2019
From: mpsilvavalent at gmail.com (Martin Pablo Silva Valent)
Date: Mon, 22 Apr 2019 23:09:20 -0400
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
Message-ID: <F0AB883C-29F6-4DF4-A695-39C5F753D8C2@gmail.com>

I like it! You have my full support!

Martin Silva Valent

mpsilvavalent at gmail.com

Partner | Silva.legal
martin at silva.legal

Director | Dat.as
martin.silva at dat.as

Skype ID: mpsilvavalent
Tel: +5491164993943
Libertador 5990, Off. 406
Buenos Aires, Argentina.

Este email, incluyendo adjuntos, podr?a contener informaci?n  confidencial protegida por ley y es para uso exclusivo de su destinatario. Si  Ud. no es el destinatario, se le advierte que cualquier uso, difusi?n, copia o  retenci?n de este email o su contenido est? estrictamente prohibido.  Si Ud.  recibi? este email por error, por favor avise inmediatamente al remitente por  tel?fono o email y borre el mismo de su computadora. / This  e-mail, including any attachments, may contain information that is protected by  law as privileged and confidential, and is transmitted for the sole use of the  intended recipient. If you are not the intended recipient, you are hereby  notified that any use, dissemination, copying or retention of this e-mail or the  information contained herein is strictly prohibited. If you have received this  e-mail in error, please immediately notify the sender by telephone or reply  e-mail, and permanently delete this e-mail from your computer system. 

> On Apr 22, 2019, at 10:42 PM, Michael Karanicolas <mkaranicolas at gmail.com> wrote:
> 
> Hello all,
> 
> Hope you are well. I am just writing regarding the public comment for renewing the .org registry agreement. 
> 
> I reached out to Stephanie a few days ago about the possibility of an NCSG submission, and she suggested there might be some possibility to get something approved in advance of the April 29 deadline. I am attaching a first draft, and would be keen to hear what you think.
> 
> Best wishes,
> 
> Michael
> <Org Letter Rev.docx>_______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190422/98ed84e7/attachment.htm>

From icann at ferdeline.com  Tue Apr 23 15:29:40 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Tue, 23 Apr 2019 12:29:40 +0000
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <F0AB883C-29F6-4DF4-A695-39C5F753D8C2@gmail.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <F0AB883C-29F6-4DF4-A695-39C5F753D8C2@gmail.com>
Message-ID: <w8kysaJMSSjqFsGzbTub-bDQrE1M_Ri47KcuzirhOEJSr2vzJ-BDVnsCld70YNvnldKEMkV-gPauZExwVUcrM7V1mi4ITDLL_muIeBfDtJc=@ferdeline.com>

Thanks for drafting this, Michael. It is a great comment.

I am wondering about the recommendation on price caps.

Perhaps they should remain in place and, if anything, be lowered or remain stable? I am not sure I understand why they should be raised. It is not like PIR is struggling - because their costs have declined, not increased, over the past five years.

But this is not a topic I know a lot about, so looking forward to hearing other views here. Thanks!

-- Ayden

??????? Original Message ???????
On Tuesday, April 23, 2019 5:09 AM, Martin Pablo Silva Valent <mpsilvavalent at gmail.com> wrote:

> I like it! You have my full support!
>
> Martin Silva Valent
>
> mpsilvavalent at gmail.com
>
> Partner | Silva.legalmartin at silva.legal
> Director | Dat.as
> martin.silva at dat.as
>
> Skype ID: mpsilvavalent
> Tel: +5491164993943
> Libertador 5990, Off. 406
> Buenos Aires, Argentina.
>
> Este email, incluyendo adjuntos, podr?a contener informaci?n  confidencial protegida por ley y es para uso exclusivo de su destinatario. Si  Ud. no es el destinatario, se le advierte que cualquier uso, difusi?n, copia o  retenci?n de este email o su contenido est? estrictamente prohibido.  Si Ud.  recibi? este email por error, por favor avise inmediatamente al remitente por  tel?fono o email y borre el mismo de su computadora. / This  e-mail, including any attachments, may contain information that is protected by  law as privileged and confidential, and is transmitted for the sole use of the  intended recipient. If you are not the intended recipient, you are hereby  notified that any use, dissemination, copying or retention of this e-mail or the  information contained herein is strictly prohibited. If you have received this  e-mail in error, please immediately notify the sender by telephone or reply  e-mail, and permanently delete this e-mail from your computer system.
>
>> On Apr 22, 2019, at 10:42 PM, Michael Karanicolas <mkaranicolas at gmail.com> wrote:
>>
>> Hello all,
>>
>> Hope you are well. I am just writing regarding the public comment for renewing the .org registry agreement.
>>
>> I reached out to Stephanie a few days ago about the possibility of an NCSG submission, and she suggested there might be some possibility to get something approved in advance of the April 29 deadline. I am attaching a first draft, and would be keen to hear what you think.
>>
>> Best wishes,
>>
>> Michael
>> <Org Letter Rev.docx>_______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190423/fc4114d5/attachment.htm>

From mkaranicolas at gmail.com  Tue Apr 23 17:07:41 2019
From: mkaranicolas at gmail.com (Michael Karanicolas)
Date: Tue, 23 Apr 2019 11:07:41 -0300
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <w8kysaJMSSjqFsGzbTub-bDQrE1M_Ri47KcuzirhOEJSr2vzJ-BDVnsCld70YNvnldKEMkV-gPauZExwVUcrM7V1mi4ITDLL_muIeBfDtJc=@ferdeline.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <F0AB883C-29F6-4DF4-A695-39C5F753D8C2@gmail.com>
 <w8kysaJMSSjqFsGzbTub-bDQrE1M_Ri47KcuzirhOEJSr2vzJ-BDVnsCld70YNvnldKEMkV-gPauZExwVUcrM7V1mi4ITDLL_muIeBfDtJc=@ferdeline.com>
Message-ID: <CAGQVoThkfb0YcFpRyWR3nn+XBevD0eXZaQQ2y0o8gyeQ=zOgUw@mail.gmail.com>

Hi,

Thanks so much for the kind words. I think the price caps is a challenging
issue. Obviously PIR wants to raise revenues and, as they noted in their
feedback to Stephanie on this (copied below), they put money towards some
good causes.

To me it's fundamentally a market question - which is why I was so cautious
about it. Most NGOs aren't holding big portfolios of domain names, and
costs still look quite reasonable to me, in absolute terms, such that I
don't imagine it would be a huge obstacle even to small organizations if
they went up a bit, just so long as any increases were managed and imposed
in consideration of the role that .org plays, as distinct from other
domains. Honestly, it's a bit puzzling to me as to why they would want to
get rid of the caps, if they're not even utilizing the 10% raises that
they're allowed at the moment. But I'm also not sure that NCSG necessarily
wants to pick a fight with them over this, which is another reason I
phrased things in cautious terms.

Anyway - happy to defer to the PCs thoughts here - I'm sort of in two minds
myself on the position we should take.

Best,

Michael



   - Because ICANN is not a regulator and having price restrictions in this
   scenario is highly unusual.
   - PIR, with .ORG, does not have market power.  The Department of Justice
   has gone through the exercise of looking at what Registries have market
   power and came to the conclusion that only .COM does.  Without market
   power, it would be inappropriate and inconsistent with a market economy to
   maintain price caps on .ORG.
      - This is particularly true as .ORG is moving onto the new TLD
      Agreement.
   - With any price increase, registrants will have the ability to lock in
   their pricing for the next 10 years without any price fluctuation.
   - PIR is a non-profit and has a public interest mission; not every
   decision for us is purely financial.  Under the legacy agreement for .ORG,
   we have had the right to raise prices each and every year up to 10%.  That
   being said, we have not chosen to raise prices in the last three years at
   all.
   - More than 50 cents of every dollar that comes into PIR goes directly
   to fund the work of the Internet Society and the amazing work they do.  Any
   eventual price increase does not go to bolster the ?bottom line? for PIR,
   but rather, to end up doing more good and providing more accessible and
   better internet around the world.



On Tue, Apr 23, 2019 at 9:29 AM Ayden F?rdeline <icann at ferdeline.com> wrote:

> Thanks for drafting this, Michael. It is a great comment.
>
> I am wondering about the recommendation on price caps.
>
> Perhaps they should remain in place and, if anything, be lowered or remain
> stable? I am not sure I understand why they should be raised. It is not
> like PIR is struggling - because their costs have declined, not increased,
> over the past five years.
>
> But this is not a topic I know a lot about, so looking forward to hearing
> other views here. Thanks!
>
> -- Ayden
>
>
> ??????? Original Message ???????
> On Tuesday, April 23, 2019 5:09 AM, Martin Pablo Silva Valent <
> mpsilvavalent at gmail.com> wrote:
>
> I like it! You have my full support!
>
> Martin Silva Valent
>
> mpsilvavalent at gmail.com
>
>
> *Partner | Silva.legal*martin at silva.legal
> *Director | Dat.as*
> martin.silva at dat.as
>
> Skype ID: mpsilvavalent
> Tel: +5491164993943
> Libertador 5990, Off. 406
> Buenos Aires, Argentina.
>
> Este email, incluyendo adjuntos, podr?a contener informaci?n  confidencial
> protegida por ley y es para uso exclusivo de su destinatario. Si  Ud. no es
> el destinatario, se le advierte que cualquier uso, difusi?n, copia o
>  retenci?n de este email o su contenido est? estrictamente prohibido.
> Si Ud.  recibi? este email por error, por favor avise inmediatamente al
> remitente por  tel?fono o email y borre el mismo de su computadora. /
> This  e-mail, including any attachments, may contain information that is
> protected by  law as privileged and confidential, and is transmitted for
> the sole use of the  intended recipient. If you are not the intended
> recipient, you are hereby  notified that any use, dissemination, copying or
> retention of this e-mail or the  information contained herein is strictly
> prohibited. If you have received this  e-mail in error, please immediately
> notify the sender by telephone or reply  e-mail, and permanently delete
> this e-mail from your computer system.
>
> On Apr 22, 2019, at 10:42 PM, Michael Karanicolas <mkaranicolas at gmail.com>
> wrote:
>
> Hello all,
>
> Hope you are well. I am just writing regarding the public comment for
> renewing the .org registry agreement.
>
> I reached out to Stephanie a few days ago about the possibility of an NCSG
> submission, and she suggested there might be some possibility to get
> something approved in advance of the April 29 deadline. I am attaching a
> first draft, and would be keen to hear what you think.
>
> Best wishes,
>
> Michael
> <Org Letter Rev.docx>_______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190423/d813bece/attachment.htm>

From kathy at kathykleiman.com  Wed Apr 24 17:15:22 2019
From: kathy at kathykleiman.com (Kathy Kleiman)
Date: Wed, 24 Apr 2019 10:15:22 -0400
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <F0AB883C-29F6-4DF4-A695-39C5F753D8C2@gmail.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <F0AB883C-29F6-4DF4-A695-39C5F753D8C2@gmail.com>
Message-ID: <2e2c8c32-b7b1-f304-c4ed-7311a01cfc08@kathykleiman.com>

Looks good to me. It seems timely to submit these comments -- deadline 
in a few days.?? Tx to Michael for drafting!

Kathy (observer)

On 4/22/2019 11:09 PM, Martin Pablo Silva Valent wrote:
> I like it! You have my full support!
>
> Martin Silva Valent
>
> mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>
>
> *Partner | Silva.legal
> *martin at silva.legal <mailto:martin at silva.legal>
>
> *Director | Dat.as*
> martin.silva at dat.as <mailto:martin.silva at dat.as>
>
> Skype ID: mpsilvavalent
> Tel: +5491164993943
> Libertador 5990, Off. 406
> Buenos Aires, Argentina.
>
> Este email, incluyendo adjuntos, podr?a contener?informaci?n 
> ?confidencial protegida por ley y es?para uso exclusivo de su 
> destinatario. Si ?Ud. no?es el destinatario, se le advierte que 
> cualquier?uso, difusi?n, copia o ?retenci?n de este email o?su 
> contenido est? estrictamente prohibido. ?Si?Ud. ?recibi? este email 
> por error, por favor avise?inmediatamente al remitente por ?tel?fono 
> o?email y borre el mismo de su computadora. / This??e-mail, including 
> any attachments, may contain?information that is protected by ?law as 
> privileged?and confidential, and is transmitted for the sole?use of 
> the ?intended recipient. If you are not the?intended recipient, you 
> are hereby ?notified that?any use, dissemination, copying or retention 
> of?this e-mail or the ?information contained herein is?strictly 
> prohibited. If you have received this ?e-mail in error, please 
> immediately notify the?sender by telephone or reply ?e-mail, 
> and?permanently delete this e-mail from your?computer system.
>
>> On Apr 22, 2019, at 10:42 PM, Michael Karanicolas 
>> <mkaranicolas at gmail.com <mailto:mkaranicolas at gmail.com>> wrote:
>>
>> Hello all,
>>
>> Hope you are well. I am just writing regarding the?public comment for 
>> renewing the .org registry agreement.
>>
>> I reached out to Stephanie a few days ago about the possibility of an 
>> NCSG submission, and she suggested there might be some possibility to 
>> get something approved in advance of the April 29 deadline. I am 
>> attaching a first draft, and would be keen to hear what you think.
>>
>> Best wishes,
>>
>> Michael
>> <Org Letter Rev.docx>_______________________________________________
>> 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
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190424/8c108cec/attachment.htm>

From kathy at kathykleiman.com  Wed Apr 24 17:19:37 2019
From: kathy at kathykleiman.com (Kathy Kleiman)
Date: Wed, 24 Apr 2019 10:19:37 -0400
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <w8kysaJMSSjqFsGzbTub-bDQrE1M_Ri47KcuzirhOEJSr2vzJ-BDVnsCld70YNvnldKEMkV-gPauZExwVUcrM7V1mi4ITDLL_muIeBfDtJc=@ferdeline.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <F0AB883C-29F6-4DF4-A695-39C5F753D8C2@gmail.com>
 <w8kysaJMSSjqFsGzbTub-bDQrE1M_Ri47KcuzirhOEJSr2vzJ-BDVnsCld70YNvnldKEMkV-gPauZExwVUcrM7V1mi4ITDLL_muIeBfDtJc=@ferdeline.com>
Message-ID: <b9f88886-fc0b-0769-88f5-8ef312abb34e@kathykleiman.com>

Good point, Adyen. Why the price caps have been taken off is a mystery 
-- and the idea of an unbounded upper limit for raising rates is 
shocking. Especially with an embedded base of approx 10 million domain 
names. Raising the rates high could really hurt a lot of small 
nonprofits and civil society groups.

PIR is certainly not struggling :-).

Best, Kathy

On 4/23/2019 8:29 AM, Ayden F?rdeline wrote:
> Thanks for drafting this, Michael. It is a great comment.
>
> I am wondering about the recommendation on price caps.
>
> Perhaps they should remain in place and, if anything, be lowered or 
> remain stable? I am not sure I understand why they should be raised. 
> It is not like PIR is struggling - because their costs have declined, 
> not increased, over the past five years.
>
> But this is not a topic I know a lot about, so looking forward to 
> hearing other views here. Thanks!
>
> -- Ayden
>
>
> ??????? Original Message ???????
> On Tuesday, April 23, 2019 5:09 AM, Martin Pablo Silva Valent 
> <mpsilvavalent at gmail.com> wrote:
>
>> I like it! You have my full support!
>>
>> Martin Silva Valent
>>
>> mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>
>>
>> *Partner | Silva.legal
>> *martin at silva.legal <mailto:martin at silva.legal>
>> *Director | Dat.as*
>> martin.silva at dat.as <mailto:martin.silva at dat.as>
>>
>> Skype ID: mpsilvavalent
>> Tel: +5491164993943
>> Libertador 5990, Off. 406
>> Buenos Aires, Argentina.
>>
>> Este email, incluyendo adjuntos, podr?a contener?informaci?n 
>> ?confidencial protegida por ley y es?para uso exclusivo de su 
>> destinatario. Si ?Ud. no?es el destinatario, se le advierte que 
>> cualquier?uso, difusi?n, copia o ?retenci?n de este email o?su 
>> contenido est? estrictamente prohibido. ?Si?Ud. ?recibi? este email 
>> por error, por favor avise?inmediatamente al remitente por ?tel?fono 
>> o?email y borre el mismo de su computadora. / This??e-mail, including 
>> any attachments, may contain?information that is protected by ?law as 
>> privileged?and confidential, and is transmitted for the sole?use of 
>> the ?intended recipient. If you are not the?intended recipient, you 
>> are hereby ?notified that?any use, dissemination, copying or 
>> retention of?this e-mail or the ?information contained herein 
>> is?strictly prohibited. If you have received this ?e-mail in error, 
>> please immediately notify the?sender by telephone or reply ?e-mail, 
>> and?permanently delete this e-mail from your?computer system.
>>
>>> On Apr 22, 2019, at 10:42 PM, Michael Karanicolas 
>>> <mkaranicolas at gmail.com <mailto:mkaranicolas at gmail.com>> wrote:
>>>
>>> Hello all,
>>>
>>> Hope you are well. I am just writing regarding the?public comment 
>>> for renewing the .org registry agreement.
>>>
>>> I reached out to Stephanie a few days ago about the possibility of 
>>> an NCSG submission, and she suggested there might be some 
>>> possibility to get something approved in advance of the April 29 
>>> deadline. I am attaching a first draft, and would be keen to hear 
>>> what you think.
>>>
>>> Best wishes,
>>>
>>> Michael
>>> <Org Letter Rev.docx>_______________________________________________
>>> 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
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190424/63bf4423/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Wed Apr 24 19:54:23 2019
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Wed, 24 Apr 2019 16:54:23 +0000
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <2e2c8c32-b7b1-f304-c4ed-7311a01cfc08@kathykleiman.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <F0AB883C-29F6-4DF4-A695-39C5F753D8C2@gmail.com>
 <2e2c8c32-b7b1-f304-c4ed-7311a01cfc08@kathykleiman.com>
Message-ID: <3799beba-6328-0154-9954-06870ed2ac19@mail.utoronto.ca>

I agree, it is a great comment.  My gut would say leave the caps, allow small increases.  Seems like a reasonable compromise.  And ICANN actually is a regulator, just not a government....

On 2019-04-24 10:15, Kathy Kleiman wrote:

Looks good to me. It seems timely to submit these comments -- deadline in a few days.   Tx to Michael for drafting!

Kathy (observer)

On 4/22/2019 11:09 PM, Martin Pablo Silva Valent wrote:
I like it! You have my full support!

Martin Silva Valent

mpsilvavalent at gmail.com<mailto:mpsilvavalent at gmail.com>

Partner | Silva.legal
martin at silva.legal<mailto:martin at silva.legal>

Director | Dat.as
martin.silva at dat.as<mailto:martin.silva at dat.as>

Skype ID: mpsilvavalent
Tel: +5491164993943
Libertador 5990, Off. 406
Buenos Aires, Argentina.

Este email, incluyendo adjuntos, podr?a contener informaci?n  confidencial protegida por ley y es para uso exclusivo de su destinatario. Si  Ud. no es el destinatario, se le advierte que cualquier uso, difusi?n, copia o  retenci?n de este email o su contenido est? estrictamente prohibido.  Si Ud.  recibi? este email por error, por favor avise inmediatamente al remitente por  tel?fono o email y borre el mismo de su computadora. / This  e-mail, including any attachments, may contain information that is protected by  law as privileged and confidential, and is transmitted for the sole use of the  intended recipient. If you are not the intended recipient, you are hereby  notified that any use, dissemination, copying or retention of this e-mail or the  information contained herein is strictly prohibited. If you have received this  e-mail in error, please immediately notify the sender by telephone or reply  e-mail, and permanently delete this e-mail from your computer system.

On Apr 22, 2019, at 10:42 PM, Michael Karanicolas <mkaranicolas at gmail.com<mailto:mkaranicolas at gmail.com>> wrote:

Hello all,

Hope you are well. I am just writing regarding the public comment for renewing the .org registry agreement.

I reached out to Stephanie a few days ago about the possibility of an NCSG submission, and she suggested there might be some possibility to get something approved in advance of the April 29 deadline. I am attaching a first draft, and would be keen to hear what you think.

Best wishes,

Michael
<Org Letter Rev.docx>_______________________________________________
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




_______________________________________________
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




_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190424/a204118b/attachment.htm>

From mpsilvavalent at gmail.com  Wed Apr 24 20:01:25 2019
From: mpsilvavalent at gmail.com (Martin Pablo Silva Valent)
Date: Wed, 24 Apr 2019 13:01:25 -0400
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <3799beba-6328-0154-9954-06870ed2ac19@mail.utoronto.ca>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <F0AB883C-29F6-4DF4-A695-39C5F753D8C2@gmail.com>
 <2e2c8c32-b7b1-f304-c4ed-7311a01cfc08@kathykleiman.com>
 <3799beba-6328-0154-9954-06870ed2ac19@mail.utoronto.ca>
Message-ID: <77980EB7-F729-4BBA-B002-6A79271E1827@gmail.com>

*coordintaor 

Overtime I say regulator someone throws a shoe at me at icann.

Martin Silva Valent

mpsilvavalent at gmail.com

Partner | Silva.legal
martin at silva.legal

Director | Dat.as
martin.silva at dat.as

Skype ID: mpsilvavalent
Tel: +5491164993943
Libertador 5990, Off. 406
Buenos Aires, Argentina.

Este email, incluyendo adjuntos, podr?a contener informaci?n  confidencial protegida por ley y es para uso exclusivo de su destinatario. Si  Ud. no es el destinatario, se le advierte que cualquier uso, difusi?n, copia o  retenci?n de este email o su contenido est? estrictamente prohibido.  Si Ud.  recibi? este email por error, por favor avise inmediatamente al remitente por  tel?fono o email y borre el mismo de su computadora. / This  e-mail, including any attachments, may contain information that is protected by  law as privileged and confidential, and is transmitted for the sole use of the  intended recipient. If you are not the intended recipient, you are hereby  notified that any use, dissemination, copying or retention of this e-mail or the  information contained herein is strictly prohibited. If you have received this  e-mail in error, please immediately notify the sender by telephone or reply  e-mail, and permanently delete this e-mail from your computer system. 

> On Apr 24, 2019, at 12:54 PM, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> wrote:
> 
> I agree, it is a great comment.  My gut would say leave the caps, allow small increases.  Seems like a reasonable compromise.  And ICANN actually is a regulator, just not a government....
> On 2019-04-24 10:15, Kathy Kleiman wrote:
>> Looks good to me. It seems timely to submit these comments -- deadline in a few days.   Tx to Michael for drafting!
>> 
>> Kathy (observer) 
>> On 4/22/2019 11:09 PM, Martin Pablo Silva Valent wrote:
>>> I like it! You have my full support!
>>> 
>>> Martin Silva Valent
>>> 
>>> mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>
>>> 
>>> Partner | Silva.legal
>>> martin at silva.legal <mailto:martin at silva.legal>
>>> 
>>> Director | Dat.as
>>> martin.silva at dat.as <mailto:martin.silva at dat.as>
>>> 
>>> Skype ID: mpsilvavalent
>>> Tel: +5491164993943
>>> Libertador 5990, Off. 406
>>> Buenos Aires, Argentina.
>>> 
>>> Este email, incluyendo adjuntos, podr?a contener informaci?n  confidencial protegida por ley y es para uso exclusivo de su destinatario. Si  Ud. no es el destinatario, se le advierte que cualquier uso, difusi?n, copia o  retenci?n de este email o su contenido est? estrictamente prohibido.  Si Ud.  recibi? este email por error, por favor avise inmediatamente al remitente por  tel?fono o email y borre el mismo de su computadora. / This  e-mail, including any attachments, may contain information that is protected by  law as privileged and confidential, and is transmitted for the sole use of the  intended recipient. If you are not the intended recipient, you are hereby  notified that any use, dissemination, copying or retention of this e-mail or the  information contained herein is strictly prohibited. If you have received this  e-mail in error, please immediately notify the sender by telephone or reply  e-mail, and permanently delete this e-mail from your computer system. 
>>> 
>>>> On Apr 22, 2019, at 10:42 PM, Michael Karanicolas <mkaranicolas at gmail.com <mailto:mkaranicolas at gmail.com>> wrote:
>>>> 
>>>> Hello all,
>>>> 
>>>> Hope you are well. I am just writing regarding the public comment for renewing the .org registry agreement. 
>>>> 
>>>> I reached out to Stephanie a few days ago about the possibility of an NCSG submission, and she suggested there might be some possibility to get something approved in advance of the April 29 deadline. I am attaching a first draft, and would be keen to hear what you think.
>>>> 
>>>> Best wishes,
>>>> 
>>>> Michael
>>>> <Org Letter Rev.docx>_______________________________________________
>>>> 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
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190424/5464899f/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Wed Apr 24 20:24:07 2019
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Wed, 24 Apr 2019 17:24:07 +0000
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <77980EB7-F729-4BBA-B002-6A79271E1827@gmail.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <F0AB883C-29F6-4DF4-A695-39C5F753D8C2@gmail.com>
 <2e2c8c32-b7b1-f304-c4ed-7311a01cfc08@kathykleiman.com>
 <3799beba-6328-0154-9954-06870ed2ac19@mail.utoronto.ca>
 <77980EB7-F729-4BBA-B002-6A79271E1827@gmail.com>
Message-ID: <6add1a0a-9c3e-f5c1-16c2-d2c7778a97c4@mail.utoronto.ca>

They are every bit a regulator.  Global monopoly controller is maybe a better phrase?

:-)
On 2019-04-24 13:01, Martin Pablo Silva Valent wrote:
*coordintaor

Overtime I say regulator someone throws a shoe at me at icann.

Martin Silva Valent

mpsilvavalent at gmail.com<mailto:mpsilvavalent at gmail.com>

Partner | Silva.legal
martin at silva.legal<mailto:martin at silva.legal>

Director | Dat.as
martin.silva at dat.as<mailto:martin.silva at dat.as>

Skype ID: mpsilvavalent
Tel: +5491164993943
Libertador 5990, Off. 406
Buenos Aires, Argentina.

Este email, incluyendo adjuntos, podr?a contener informaci?n  confidencial protegida por ley y es para uso exclusivo de su destinatario. Si  Ud. no es el destinatario, se le advierte que cualquier uso, difusi?n, copia o  retenci?n de este email o su contenido est? estrictamente prohibido.  Si Ud.  recibi? este email por error, por favor avise inmediatamente al remitente por  tel?fono o email y borre el mismo de su computadora. / This  e-mail, including any attachments, may contain information that is protected by  law as privileged and confidential, and is transmitted for the sole use of the  intended recipient. If you are not the intended recipient, you are hereby  notified that any use, dissemination, copying or retention of this e-mail or the  information contained herein is strictly prohibited. If you have received this  e-mail in error, please immediately notify the sender by telephone or reply  e-mail, and permanently delete this e-mail from your computer system.

On Apr 24, 2019, at 12:54 PM, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca<mailto:stephanie.perrin at mail.utoronto.ca>> wrote:


I agree, it is a great comment.  My gut would say leave the caps, allow small increases.  Seems like a reasonable compromise.  And ICANN actually is a regulator, just not a government....

On 2019-04-24 10:15, Kathy Kleiman wrote:

Looks good to me. It seems timely to submit these comments -- deadline in a few days.   Tx to Michael for drafting!

Kathy (observer)

On 4/22/2019 11:09 PM, Martin Pablo Silva Valent wrote:
I like it! You have my full support!

Martin Silva Valent

mpsilvavalent at gmail.com<mailto:mpsilvavalent at gmail.com>

Partner | Silva.legal
martin at silva.legal<mailto:martin at silva.legal>

Director | Dat.as
martin.silva at dat.as<mailto:martin.silva at dat.as>

Skype ID: mpsilvavalent
Tel: +5491164993943
Libertador 5990, Off. 406
Buenos Aires, Argentina.

Este email, incluyendo adjuntos, podr?a contener informaci?n  confidencial protegida por ley y es para uso exclusivo de su destinatario. Si  Ud. no es el destinatario, se le advierte que cualquier uso, difusi?n, copia o  retenci?n de este email o su contenido est? estrictamente prohibido.  Si Ud.  recibi? este email por error, por favor avise inmediatamente al remitente por  tel?fono o email y borre el mismo de su computadora. / This  e-mail, including any attachments, may contain information that is protected by  law as privileged and confidential, and is transmitted for the sole use of the  intended recipient. If you are not the intended recipient, you are hereby  notified that any use, dissemination, copying or retention of this e-mail or the  information contained herein is strictly prohibited. If you have received this  e-mail in error, please immediately notify the sender by telephone or reply  e-mail, and permanently delete this e-mail from your computer system.

On Apr 22, 2019, at 10:42 PM, Michael Karanicolas <mkaranicolas at gmail.com<mailto:mkaranicolas at gmail.com>> wrote:

Hello all,

Hope you are well. I am just writing regarding the public comment for renewing the .org registry agreement.

I reached out to Stephanie a few days ago about the possibility of an NCSG submission, and she suggested there might be some possibility to get something approved in advance of the April 29 deadline. I am attaching a first draft, and would be keen to hear what you think.

Best wishes,

Michael
<Org Letter Rev.docx>_______________________________________________
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




_______________________________________________
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




_______________________________________________
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


_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190424/69c9d661/attachment.htm>

From tatiana.tropina at gmail.com  Wed Apr 24 20:35:49 2019
From: tatiana.tropina at gmail.com (Tatiana Tropina)
Date: Wed, 24 Apr 2019 19:35:49 +0200
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
Message-ID: <CADxLtge5sPy1Xz8q=bxJG4QDWN5GQ9X6WxBdhSB3jbwwt_9Uyg@mail.gmail.com>

Hi all,
Thanks to Michael for drafting the comment, I support the submission of it!
Cheers,
Tanya

On Tue, 23 Apr 2019 at 04:43, Michael Karanicolas <mkaranicolas at gmail.com>
wrote:

> Hello all,
>
> Hope you are well. I am just writing regarding the public comment for
> renewing the .org registry agreement.
>
> I reached out to Stephanie a few days ago about the possibility of an NCSG
> submission, and she suggested there might be some possibility to get
> something approved in advance of the April 29 deadline. I am attaching a
> first draft, and would be keen to hear what you think.
>
> Best wishes,
>
> Michael
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190424/66826722/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Wed Apr 24 20:37:14 2019
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Wed, 24 Apr 2019 17:37:14 +0000
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <CADxLtge5sPy1Xz8q=bxJG4QDWN5GQ9X6WxBdhSB3jbwwt_9Uyg@mail.gmail.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <CADxLtge5sPy1Xz8q=bxJG4QDWN5GQ9X6WxBdhSB3jbwwt_9Uyg@mail.gmail.com>
Message-ID: <32a0083f-381f-6e9b-f919-a60175610996@mail.utoronto.ca>

Shall we send it out to the NCSG discuss list for comments?

or not?


Rafik, can you get ready to send it in for us please?

cheers Steph

On 2019-04-24 13:35, Tatiana Tropina wrote:
Hi all,
Thanks to Michael for drafting the comment, I support the submission of it!
Cheers,
Tanya

On Tue, 23 Apr 2019 at 04:43, Michael Karanicolas <mkaranicolas at gmail.com<mailto:mkaranicolas at gmail.com>> wrote:
Hello all,

Hope you are well. I am just writing regarding the public comment for renewing the .org registry agreement.

I reached out to Stephanie a few days ago about the possibility of an NCSG submission, and she suggested there might be some possibility to get something approved in advance of the April 29 deadline. I am attaching a first draft, and would be keen to hear what you think.

Best wishes,

Michael
_______________________________________________
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



_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190424/410e3b63/attachment.htm>

From ayden at ferdeline.com  Thu Apr 25 15:44:48 2019
From: ayden at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Thu, 25 Apr 2019 12:44:48 +0000
Subject: [NCSG-PC] Fw: Fwd: Important: Help Us Avoid Domain Price Increases
In-Reply-To: <CAMCMt7r+3Y3_aZg6WHvp8mxZA9CKVXjpReS_uQaM9Ssw27c3qQ@mail.gmail.com>
References: <wKJd6UFwQkecakULjGdkJg@ismtpd0050p1iad1.sendgrid.net>
 <CAMCMt7r+3Y3_aZg6WHvp8mxZA9CKVXjpReS_uQaM9Ssw27c3qQ@mail.gmail.com>
Message-ID: <oPyBQhrwgfPVyF4E-svzEEtrD-3ikSpS0i7Z4Wg6P_lSD2UHWn0hCbIm62i9lm53Fu5FKvKRfE0QT5CNhLeU11oSKpgoGfFvlPfAo0UkDLw=@ferdeline.com>

FYI

-- Ayden

> ---------- Forwarded message ---------
> From: Namecheap <support at namecheap.com>
> Date: Thu, Apr 25, 2019 at 2:04 PM
> Subject: Important: Help Us Avoid Domain Price Increases
>
> We have important information to share with you that can affect the price of your domains.
>  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ? ?
>
> [Namecheap](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnW1cXFxSbbBDESBbekfxCqvLHlnZr5YtjKjux8kfg4GXjwP7r-Sy22hCXRjyGrQR8EUAQbYeeEo2HpGuEZSpfYsZBOsAu0RQ93tCU0S4w4FwC1yWr8znlA4l3F9ZEKx5cT6tRC3gM8TTw0Ro_0ZGEK5YBu32fd7HY555xmVaRAqopt8YAYmZ3qhGEv7nr2Zv5ZW_FDCy6IG6nQpX3cQq3WZGenCPcmnOF7A9B-E_oF1h9SpOCw8ds2Rav0cuCJAHAu4p1JPNcnkBW8CsounwIfmh3HIii55_gULUC8howd-MwZSMRHdP3ZX8Ghjj9CLYepx0kBdgqEDyiVoT6rXUcxf)
>
> [View in browser](https://links.namecheap.com/e/evib?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=dNtiCa3cqnQEnJcm0qkVYQDrRaEKaO7xBoV4on0jsMgPQxr2fwIs-9IoxIEce2ErqYIDSJUtOvNkk2DR39pEbLP3TF4idHHffdopOqZWgO_VyAJ7stFWmunQF-ifcKYy)
>
> https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnVVUB6dQQDNZV3TgxvovBGi94PmEZJxI5BgWZKuUUVYYhFGQdTkbKHEzFdXq9TjA6_fiMppcmT2FEol-KsT_zUDHydfeHq1uGc8m9sEFicJP_wFxsp5Vp8wby2LW_g24Ral9fHU3ymtmm9nCVq-MG025v5XUMruT6a2BRsOJHdDXnKf_T7wMstocy4xAbG9raaq9Kszd0BjV1oG4UWKWkfnDsWNN7u48LII-SnbvIuoT82cDGp7j266keQWnPlhQWJmt_Z8cjBGM1o93keQ9zVac1LNxbI393EcCMsKYKnaJcSOOy_MvbZnEK7EuwtsxWz0jdzP3Ua5cEji7SaYjPw2S4CJsHBmufa44seC8kC9DZm4bLRNpWZX6A9K5ZfvVJ8%3D
>
> Help Us Avoid Domain
> Price Increases
> Hi [REDACTED],
>
> We have [important information](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnVVUB6dQQDNZV3TgxvovBGi94PmEZJxI5BgWZKuUUVYYhFGQdTkbKHEzFdXq9TjA6_fiMppcmT2FEol-KsT_zUDHydfeHq1uGc8m9sEFicJP_wFxsp5Vp8wby2LW_g24Ral9fHU3ymtmm9nCVq-MG025v5XUMruT6a2BRsOJHdDXki0C9uyfB59yWwHbanT7nSHlWQwIa9uBZc6M0OWfjSytvlP2IcojQO4vPUCf_UiV6TxK7BXwf_XrKBMsdj973PLd1jJYc1iqrObDaugj_jSpR5cfEbJVvg4HLPyGn1gQyTlmHCR0al-pmNNrLHxG3YZPkjpD-8Z-vVE6eQYxpOB3dys5arNbA24UB8ZzhH5bnCQ18xQ7vvvDLQDa5roQro%3D) to share with you that can affect the price of your domains.
> What?s Happening
> ICANN, the organization that oversees domain names, has proposed removing price caps on all .org, .info, and .biz top level domains. This change could significantly increase the wholesale price that Namecheap pays for domains, and would force us to pass along those increases to you.
> Who Sets the Prices
> Wholesale registries charge Namecheap a set fee per domain name per year. Namecheap then adds a little markup to cover things like support, provisioning domain services, transaction fees, etc. ICANN includes a provision in its contracts with registries that limits what they can charge.
> Why ICANN is Doing This
> ICANN?s current contract with Public Interest Registry (PIR), the group that runs the .org domain name, allows PIR to increase the wholesale price of .org domains by 10% a year. Now ICANN is proposing extending the contract to operate .org but letting PIR set whatever prices it wants.
> Rather than a 10% increase to renew your domain next year, PIR could suddenly start charging registrars like Namecheap 100 times as much. In turn, registrars would have no choice but to pass these charges on to customers. Similar contract proposals may also impact .info and .biz prices.
> Speak Up Against the Change
> The good news is that domain owners like yourself can take action to stop these price increases. Act now by sending your comments to ICANN before April 29, 2019.
>
> You can leave your comment on each proposal here:
>
> [.Org comment period](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol2ic87iXDt2alUiwNw9eAurkNCdXOK9wgfDwwkiyGEQhpix3ivHam362pvUZRhm31gssH2lY201jmg1bLZuWzlCpGpdC295XE4P4wM95_8Dsi1JESGsSIrwRUSUEFYq3bKrhdl00ze4Y_EdTz871PY565C7edZoKgyJkX6Ij9fQpdDH4fto9hRR4OrddNCoQ_utY5n7xggwhYGL1UV9WHU1oJW0Zvpyk5zK_GZSfC8f0iWQ6mVA9b4JR1fj-QkPCu1h4azSJx2WMPY9ctzse6DxKfT_qyP6RO0cObQwJLrIyYpLPHuhPrWKV2rykJwdYMDUMPt_CdrRqkbuI-FGliTYHq7WZDWuEnb82UQGmOEH_AmFNIAAB1vEoGND83WR3tGvCNkduGfjDcuVGmTQOTyI%3D)
> [.Info comment period](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol2ic87iXDt2alUiwNw9eAurrtIOONR__bF-1vxlnSvbHPuH07iaPXcPNqOkn0JHh7Ovv37OzYaTnSyLxhN9shIfLk6g4aA7DBpayboDsbjQNxvv6iB_hKMCTj65Rmc5b-qkW43Qeon1iIH-trg_OPvfn4lvSVWiySfxb9JpF_5uKTTj-dfQDn753Vhr5W4uUVGB1mNe5l-exK3qOlLXVsn6rcsl_Y-htb_mAjWmqpGp54scvHwSgdBZuVwK_Br6GZy7Mh4x3k7g8VzylpsQO__8Qr6ozHK-Z_Vy-iLXN9eE7_HiFxaWKvUObJMSSWkRAazmcnAGL8eJR1__5MsyYOvX8z2T0Wd4gw3wJ0QVc8ugNIp-ZAVkJ2XTXr_2Uy3WpZQlqyoeF-1036b8qlNab9G0%3D)
> [.Biz comment period](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol2ic87iXDt2alUiwNw9eAuqQnYSE5ts7nOfh18LDPnKQFaOy43zeD8flfQIfbFSFu02DthS7FzVgWkWJP4lTQ4tiDuJLIQB0JGZhKtw0oHsJ7q0psYdv21e1GYT0RAXeADVlExEDVBWyb3rx0vXtQocUFNlxPmR7hQb_7fTOSEx-bZkmYQaWJ9HsFHUAN_Cw7jjd9u8BNURIXqDNnrJXzSB5y_8jOas6dWIbYiQMKN1hfkgkM7qz60w-Cfjp-bGEgly7zMBmZ-9g5SZC-GKUlQr7J69UkjO6HCcn2Ek-n3BeJrli_PEzdDxWA402DkV0sFmRyhorCLlRKoMh9zA2nKZ0o1-CYg5Ql_d_EW8YhlqANf-PRoggsRZ11n802CTZipnQ_TYEGAiJQU8B5TT-bT0%3D)
>
> [Find Out More](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnVVUB6dQQDNZV3TgxvovBGi94PmEZJxI5BgWZKuUUVYYhFGQdTkbKHEzFdXq9TjA6_fiMppcmT2FEol-KsT_zUDHydfeHq1uGc8m9sEFicJP_wFxsp5Vp8wby2LW_g24Ral9fHU3ymtmm9nCVq-MG025v5XUMruT6a2BRsOJHdDXoGfKu-CugiH72xPZw5boP-cYyKxYT1ljVEa8aYAEN3HLsXnMOUp06VhSwYdDR88kwNNlY_suNAW_ijGJmdqr6otzisji-wM6CfOIosZ5Djc69NY7wpUojlzJceMeTxxm86RHPVLOV84wI7WmYa4QHnO3w15SYRAuTAQUQwc5iofS7GFqxxk1GRE9CkECEk3DY6gvOcSpi27HoTmgLwb-Hc%3D)
>
> FOLLOW NAMECHEAP
>
> [F](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0RgaolwRZOJqxpElfs_RG46BOKn_iAqo6sCEhS0_JDboupy8RoaDVJLpUM1N-mHFidpMcQHNW7huhXr3QnyVm_1anxsDz1muN8DQ9Wp8MHCe3EdSnODT8fhSYl60LsK17JJaDyxHPzgJFffJFs8byjsXrqHKlz6moodriF1OVEKPMeaFfMzzHZNUVM_DCx_iG0Y-MsK8OVaPxfPW9tdTSN46Z90z3HiVKuuO1l5naL-sEIi-mdTiyVeVYZbvFRbdoAG9901C3k1eSsXhJXm4jIvX2-7Ph0p-st-pm6OAuom5QKhaV2avGcj9o0B3efBpImzUp7XqhUTUzPPLX7qcJN9mFzwYONX98KbXPXApwQaaCLS7W)
> [T](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol3v5iPKTjUJkEf_9am56iBElIaAlaGUGWkVWdjJn12DEF2HdYtdof_TI2BW1n-bS-B9G_p0NLtXCvttmrGnrbT9qJcOpsGea4SV0vMDnQYnRWoI5RcZ8rV8PZ4ILXT-AmECz2LZB74wd4BlRE7q3MHYuCzu2p73x1G1LGOQKmyY6eefqOEzOCreynt_3vGamb7Ww7uQ8vIgZMHOhN8pWcK6yVWJegA3YIEwmRNo97dau8sqd10iWTjSfEipZJwMUvIxnRi9dR1WPTT1O7B5P1URQQp1Ml_1oxmTMfsA2poOL_acEd2W0Dz2pMIV0s5IUBfUqRRCKpjExwl4FRtUjJuP9Dv560uhv_g-Ih5lYTl0V)
> [B](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnWhRKKbj67__D7yvPSFgTm7ilo2vRGsf4TCfFTa4mbQy8GA_gOp4a8sW7K62Fpy3kaB1cOayZR8RgT0ywPJ0n4LCwhAjdJf-1NahT4JVVKJ1MJcPUgh8emIiVwBj_1tI4ZqsF66AAVPqrZmD7KafRlHu2FNMdQnP3mIN4QOY_WU7EwV7zGg1T5zehazRZraki39E0qsIyc-UoFjlOHrz24ShG23uCQ0CARAjkLtWwNMYeMclUqGm-QYgqV8Syh3P6qf8903YyDlA40-7JQvnoftb6Ln2UcvdxEmqtCeemrNYlvIj0tpqND4qwrXmdrzmcSFdPPYPWd1KVX0SR7h5fNm)
>
> [About Us](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnXc3zFg3deFn6u4qiJAZdWloD-6xqBIlEI3_8jM2j_cMomawGPfDQOYtWEtJhW-lR8RvWSMJ3JpBw2KSacwqCYGMi5_sbHyuT2mtwLMGmAhxlmUKgRFiRr_uIkKL1_lK3ibgBeQVL2dq7ckCfTwz0ZWNnGEZoU9adSI80AdYsc5mGvigRd297O3pr4yk9hErxdS-y4-z_J5M_Y8cQdLUfVP86PxPyQ-gACo0fvOCup9L2-Yu34e3J65pd_4z8UkG9ejEPHwzy-l5DVq5CkSz_HystSlDXBEdmgcImiEWFDIf3u86Y1hJA9AnweAqKXt2mtCWvaA8yDbmP5EclsNoEXJ) | [Support](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnW9UCyBaQtnhvnmIunY3CnARVfjSFnF0BR1pEgYC26FooEKldeWF_Nz-oRoGAS7PAVBpCwHFSgwnTELDzkeTZk9LMaciIsEyqcb6R9nMy4G6ERKgQmRFJF-prXk9t_4hy-b3wUVcAwghgQG5hbOcZ6H1EgxGaRIM2kckqBVR_dDj0jwAQD9Gu_ps605XS-RT7oaCIhWx6c4by4UplMJHDejMlbFVlG7YayY8vIGAI3xJ1gwt0-DxFGnumD7VV5d_C7wHjXSG3D-s5JWKeBE-JS4-RVGdIc5UdA-WQSxA5soP-lAvD86VJ5d6bx8XHpgLgQURXY8rXqHCzFBxwsM08FhHtESCb5nrkjzz_YwAiTjAw%3D%3D) | [Privacy Policy](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnUXuZVM7_OJtrs4sVKqRL69ZcWx_mQsxFjp2q-yzg93hBRF6MOExGa7DyheZ28NmMBrclfkkC1fijhAbGyM7BsomMzjRnmeQBpm_VhsP0dymtLfWc_HkVfvcQmNJ-3DeP7GJieCvkVJaudgF-AEQYhbjZKMwZK-UR2hauzr8QqfjCwqJwM6ucao95-pGw1raoYg7U7Y3FbklVfIndEVyYKAbaTqJBTA9DoDDs4MUNac3G-b6h-7QTVqJz_VhAcAe7gkXFEQ_Ir6L56wk44zwe4KE_3g6HtauBe-rtelsXV5BMgi_5D75o0B5acmlUd-eMC_cxPPob1_otX_k8GEwCAQNnJOGER91z5BH55ZK5M1xg5I_DOgWsNizKgSetUegmQ%3D) | [Terms & Conditions](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnUvvbr8cQlppI2PVz5oOFn71UzG5U-yoDUk0zhO7T88kiXf--5iQwe940SunePjMQMS2SKsmDg-zT_cUfcOANAbL0MiRezCpos13tZaQOEMtvB60MRYv7vFRJ3o-i7Dr_VgvpJq042EmizrQA2CQfEgUTPzUYpUTIhVxdmUN85qW7iPCJzAahckkGGI5hSNdGJttb_7BZCOxLwHYy4nxFEKKvbpf7fqj65zrU5yO0_inqWQOy3uctEgSx5PUw_PdQJVeByyttnirLS8jgU4cQd-2iQXmo-k9NT9asuQi5zLAMcPQVPSdsJ_5hqBJCD3xLp46aKz1jjRGjxcX6bdTX1j)
>
> 4600 East Washington Street, Suite 305, Phoenix, AZ 85034, USA
>
> Copyright ? 2019 [Namecheap.com](https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnW1cXFxSbbBDESBbekfxCqvLHlnZr5YtjKjux8kfg4GXjwP7r-Sy22hCXRjyGrQR8EUAQbYeeEo2HpGuEZSpfYsZBOsAu0RQ93tCU0S4w4FwC1yWr8znlA4l3F9ZEKx5cT7GzcA1lH23OYuu8tnku652lYR6mUmK0wTimEBOuaCFXoWvPmhqPm-AEXnqVMIAZLoqzb6mxLQrNhgYwB6CmNeU-afwpiKHeOAbrJq92kelkePoylLe_K3UbbGpEuYr7BxGJ75Yt84T49hTdOngE88Mlvtm5b4OJajVQ7iGJq7VTBzryLdk2f2Rc06hB8n2vaxgQ36vHC8aFuylhl1jrYG)
>
> https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnW1cXFxSbbBDESBbekfxCqvLHlnZr5YtjKjux8kfg4GXjwP7r-Sy22hCXRjyGrQR8EUAQbYeeEo2HpGuEZSpfYsZBOsAu0RQ93tCU0S4w4FwC1yWr8znlA4l3F9ZEKx5cRPyOnJSiz4lfQmkPp6ntSni8e_9XnUzDpDv0IY8c55px4JCRhkWeSVFB4sZQIEjrP-6BfsijekNp4SIeGZyyWr5EXqDuWZT82dsdPB49u0uQB0omf8vdK-ubic6YEAB4hOlBJQCKtYw_ElhgiZKM28J5yEZKOlmrpfSQKKHAovP-rPZPENiTi2PGqCkTTGGwHpWwwa_kOME3jVZWG_d6N_
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190425/02c0069d/attachment.htm>

From farell at benin2point0.org  Fri Apr 26 16:59:36 2019
From: farell at benin2point0.org (Farell FOLLY)
Date: Fri, 26 Apr 2019 15:59:36 +0200
Subject: [NCSG-PC] Important: Help Us Avoid Domain Price Increases
In-Reply-To: <oPyBQhrwgfPVyF4E-svzEEtrD-3ikSpS0i7Z4Wg6P_lSD2UHWn0hCbIm62i9lm53Fu5FKvKRfE0QT5CNhLeU11oSKpgoGfFvlPfAo0UkDLw=@ferdeline.com>
References: <wKJd6UFwQkecakULjGdkJg@ismtpd0050p1iad1.sendgrid.net>
 <CAMCMt7r+3Y3_aZg6WHvp8mxZA9CKVXjpReS_uQaM9Ssw27c3qQ@mail.gmail.com>
 <oPyBQhrwgfPVyF4E-svzEEtrD-3ikSpS0i7Z4Wg6P_lSD2UHWn0hCbIm62i9lm53Fu5FKvKRfE0QT5CNhLeU11oSKpgoGfFvlPfAo0UkDLw=@ferdeline.com>
Message-ID: <D4E6CA57-6CB3-483C-A4D6-DC51087F2875@benin2point0.org>

Interesting to read!

@__f_f__

Best Regards
____________________________________

(Ekue) Farell FOLLY
NCUC Rep. to the NCSG Policy Committee
linkedin.com/in/farellf 






> On 25 Apr 2019, at 14:44, Ayden F?rdeline <ayden at ferdeline.com> wrote:
> 
> FYI
> 
> -- Ayden 
> 
> 
> 
>> ---------- Forwarded message ---------
>> From: Namecheap <support at namecheap.com <mailto:support at namecheap.com>>
>> Date: Thu, Apr 25, 2019 at 2:04 PM
>> Subject: Important: Help Us Avoid Domain Price Increases
>> 
>> 
>> 
>> 
>> We have important information to share with you that can affect the price of your domains. 
>>  <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnW1cXFxSbbBDESBbekfxCqvLHlnZr5YtjKjux8kfg4GXjwP7r-Sy22hCXRjyGrQR8EUAQbYeeEo2HpGuEZSpfYsZBOsAu0RQ93tCU0S4w4FwC1yWr8znlA4l3F9ZEKx5cT6tRC3gM8TTw0Ro_0ZGEK5YBu32fd7HY555xmVaRAqopt8YAYmZ3qhGEv7nr2Zv5ZW_FDCy6IG6nQpX3cQq3WZGenCPcmnOF7A9B-E_oF1h9SpOCw8ds2Rav0cuCJAHAu4p1JPNcnkBW8CsounwIfmh3HIii55_gULUC8howd-MwZSMRHdP3ZX8Ghjj9CLYepx0kBdgqEDyiVoT6rXUcxf>
>> View in browser <https://links.namecheap.com/e/evib?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=dNtiCa3cqnQEnJcm0qkVYQDrRaEKaO7xBoV4on0jsMgPQxr2fwIs-9IoxIEce2ErqYIDSJUtOvNkk2DR39pEbLP3TF4idHHffdopOqZWgO_VyAJ7stFWmunQF-ifcKYy>
>>  <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnVVUB6dQQDNZV3TgxvovBGi94PmEZJxI5BgWZKuUUVYYhFGQdTkbKHEzFdXq9TjA6_fiMppcmT2FEol-KsT_zUDHydfeHq1uGc8m9sEFicJP_wFxsp5Vp8wby2LW_g24Ral9fHU3ymtmm9nCVq-MG025v5XUMruT6a2BRsOJHdDXnKf_T7wMstocy4xAbG9raaq9Kszd0BjV1oG4UWKWkfnDsWNN7u48LII-SnbvIuoT82cDGp7j266keQWnPlhQWJmt_Z8cjBGM1o93keQ9zVac1LNxbI393EcCMsKYKnaJcSOOy_MvbZnEK7EuwtsxWz0jdzP3Ua5cEji7SaYjPw2S4CJsHBmufa44seC8kC9DZm4bLRNpWZX6A9K5ZfvVJ8%3D>
>> Help Us Avoid Domain 
>> Price Increases
>> Hi [REDACTED],
>> We have important information <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnVVUB6dQQDNZV3TgxvovBGi94PmEZJxI5BgWZKuUUVYYhFGQdTkbKHEzFdXq9TjA6_fiMppcmT2FEol-KsT_zUDHydfeHq1uGc8m9sEFicJP_wFxsp5Vp8wby2LW_g24Ral9fHU3ymtmm9nCVq-MG025v5XUMruT6a2BRsOJHdDXki0C9uyfB59yWwHbanT7nSHlWQwIa9uBZc6M0OWfjSytvlP2IcojQO4vPUCf_UiV6TxK7BXwf_XrKBMsdj973PLd1jJYc1iqrObDaugj_jSpR5cfEbJVvg4HLPyGn1gQyTlmHCR0al-pmNNrLHxG3YZPkjpD-8Z-vVE6eQYxpOB3dys5arNbA24UB8ZzhH5bnCQ18xQ7vvvDLQDa5roQro%3D> to share with you that can affect the price of your domains.
>> What?s Happening
>> ICANN, the organization that oversees domain names, has proposed removing price caps on all .org, .info, and .biz top level domains. This change could significantly increase the wholesale price that Namecheap pays for domains, and would force us to pass along those increases to you.
>> Who Sets the Prices
>> Wholesale registries charge Namecheap a set fee per domain name per year. Namecheap then adds a little markup to cover things like support, provisioning domain services, transaction fees, etc. ICANN includes a provision in its contracts with registries that limits what they can charge.
>> Why ICANN is Doing This
>> ICANN?s current contract with Public Interest Registry (PIR), the group that runs the .org domain name, allows PIR to increase the wholesale price of .org domains by 10% a year. Now ICANN is proposing extending the contract to operate .org but letting PIR set whatever prices it wants.
>> Rather than a 10% increase to renew your domain next year, PIR could suddenly start charging registrars like Namecheap 100 times as much. In turn, registrars would have no choice but to pass these charges on to customers. Similar contract proposals may also impact .info and .biz prices.
>> Speak Up Against the Change
>> The good news is that domain owners like yourself can take action to stop these price increases. Act now by sending your comments to ICANN before April 29, 2019. 
>> 
>> You can leave your comment on each proposal here:
>> 
>> .Org comment period <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol2ic87iXDt2alUiwNw9eAurkNCdXOK9wgfDwwkiyGEQhpix3ivHam362pvUZRhm31gssH2lY201jmg1bLZuWzlCpGpdC295XE4P4wM95_8Dsi1JESGsSIrwRUSUEFYq3bKrhdl00ze4Y_EdTz871PY565C7edZoKgyJkX6Ij9fQpdDH4fto9hRR4OrddNCoQ_utY5n7xggwhYGL1UV9WHU1oJW0Zvpyk5zK_GZSfC8f0iWQ6mVA9b4JR1fj-QkPCu1h4azSJx2WMPY9ctzse6DxKfT_qyP6RO0cObQwJLrIyYpLPHuhPrWKV2rykJwdYMDUMPt_CdrRqkbuI-FGliTYHq7WZDWuEnb82UQGmOEH_AmFNIAAB1vEoGND83WR3tGvCNkduGfjDcuVGmTQOTyI%3D>
>> .Info comment period <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol2ic87iXDt2alUiwNw9eAurrtIOONR__bF-1vxlnSvbHPuH07iaPXcPNqOkn0JHh7Ovv37OzYaTnSyLxhN9shIfLk6g4aA7DBpayboDsbjQNxvv6iB_hKMCTj65Rmc5b-qkW43Qeon1iIH-trg_OPvfn4lvSVWiySfxb9JpF_5uKTTj-dfQDn753Vhr5W4uUVGB1mNe5l-exK3qOlLXVsn6rcsl_Y-htb_mAjWmqpGp54scvHwSgdBZuVwK_Br6GZy7Mh4x3k7g8VzylpsQO__8Qr6ozHK-Z_Vy-iLXN9eE7_HiFxaWKvUObJMSSWkRAazmcnAGL8eJR1__5MsyYOvX8z2T0Wd4gw3wJ0QVc8ugNIp-ZAVkJ2XTXr_2Uy3WpZQlqyoeF-1036b8qlNab9G0%3D>
>> .Biz comment period <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol2ic87iXDt2alUiwNw9eAuqQnYSE5ts7nOfh18LDPnKQFaOy43zeD8flfQIfbFSFu02DthS7FzVgWkWJP4lTQ4tiDuJLIQB0JGZhKtw0oHsJ7q0psYdv21e1GYT0RAXeADVlExEDVBWyb3rx0vXtQocUFNlxPmR7hQb_7fTOSEx-bZkmYQaWJ9HsFHUAN_Cw7jjd9u8BNURIXqDNnrJXzSB5y_8jOas6dWIbYiQMKN1hfkgkM7qz60w-Cfjp-bGEgly7zMBmZ-9g5SZC-GKUlQr7J69UkjO6HCcn2Ek-n3BeJrli_PEzdDxWA402DkV0sFmRyhorCLlRKoMh9zA2nKZ0o1-CYg5Ql_d_EW8YhlqANf-PRoggsRZ11n802CTZipnQ_TYEGAiJQU8B5TT-bT0%3D>
>> Find Out More <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnVVUB6dQQDNZV3TgxvovBGi94PmEZJxI5BgWZKuUUVYYhFGQdTkbKHEzFdXq9TjA6_fiMppcmT2FEol-KsT_zUDHydfeHq1uGc8m9sEFicJP_wFxsp5Vp8wby2LW_g24Ral9fHU3ymtmm9nCVq-MG025v5XUMruT6a2BRsOJHdDXoGfKu-CugiH72xPZw5boP-cYyKxYT1ljVEa8aYAEN3HLsXnMOUp06VhSwYdDR88kwNNlY_suNAW_ijGJmdqr6otzisji-wM6CfOIosZ5Djc69NY7wpUojlzJceMeTxxm86RHPVLOV84wI7WmYa4QHnO3w15SYRAuTAQUQwc5iofS7GFqxxk1GRE9CkECEk3DY6gvOcSpi27HoTmgLwb-Hc%3D>
>> FOLLOW NAMECHEAP
>>  <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0RgaolwRZOJqxpElfs_RG46BOKn_iAqo6sCEhS0_JDboupy8RoaDVJLpUM1N-mHFidpMcQHNW7huhXr3QnyVm_1anxsDz1muN8DQ9Wp8MHCe3EdSnODT8fhSYl60LsK17JJaDyxHPzgJFffJFs8byjsXrqHKlz6moodriF1OVEKPMeaFfMzzHZNUVM_DCx_iG0Y-MsK8OVaPxfPW9tdTSN46Z90z3HiVKuuO1l5naL-sEIi-mdTiyVeVYZbvFRbdoAG9901C3k1eSsXhJXm4jIvX2-7Ph0p-st-pm6OAuom5QKhaV2avGcj9o0B3efBpImzUp7XqhUTUzPPLX7qcJN9mFzwYONX98KbXPXApwQaaCLS7W>
>>  <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol3v5iPKTjUJkEf_9am56iBElIaAlaGUGWkVWdjJn12DEF2HdYtdof_TI2BW1n-bS-B9G_p0NLtXCvttmrGnrbT9qJcOpsGea4SV0vMDnQYnRWoI5RcZ8rV8PZ4ILXT-AmECz2LZB74wd4BlRE7q3MHYuCzu2p73x1G1LGOQKmyY6eefqOEzOCreynt_3vGamb7Ww7uQ8vIgZMHOhN8pWcK6yVWJegA3YIEwmRNo97dau8sqd10iWTjSfEipZJwMUvIxnRi9dR1WPTT1O7B5P1URQQp1Ml_1oxmTMfsA2poOL_acEd2W0Dz2pMIV0s5IUBfUqRRCKpjExwl4FRtUjJuP9Dv560uhv_g-Ih5lYTl0V>
>>  <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnWhRKKbj67__D7yvPSFgTm7ilo2vRGsf4TCfFTa4mbQy8GA_gOp4a8sW7K62Fpy3kaB1cOayZR8RgT0ywPJ0n4LCwhAjdJf-1NahT4JVVKJ1MJcPUgh8emIiVwBj_1tI4ZqsF66AAVPqrZmD7KafRlHu2FNMdQnP3mIN4QOY_WU7EwV7zGg1T5zehazRZraki39E0qsIyc-UoFjlOHrz24ShG23uCQ0CARAjkLtWwNMYeMclUqGm-QYgqV8Syh3P6qf8903YyDlA40-7JQvnoftb6Ln2UcvdxEmqtCeemrNYlvIj0tpqND4qwrXmdrzmcSFdPPYPWd1KVX0SR7h5fNm>
>> About Us <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnXc3zFg3deFn6u4qiJAZdWloD-6xqBIlEI3_8jM2j_cMomawGPfDQOYtWEtJhW-lR8RvWSMJ3JpBw2KSacwqCYGMi5_sbHyuT2mtwLMGmAhxlmUKgRFiRr_uIkKL1_lK3ibgBeQVL2dq7ckCfTwz0ZWNnGEZoU9adSI80AdYsc5mGvigRd297O3pr4yk9hErxdS-y4-z_J5M_Y8cQdLUfVP86PxPyQ-gACo0fvOCup9L2-Yu34e3J65pd_4z8UkG9ejEPHwzy-l5DVq5CkSz_HystSlDXBEdmgcImiEWFDIf3u86Y1hJA9AnweAqKXt2mtCWvaA8yDbmP5EclsNoEXJ> | Support <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnW9UCyBaQtnhvnmIunY3CnARVfjSFnF0BR1pEgYC26FooEKldeWF_Nz-oRoGAS7PAVBpCwHFSgwnTELDzkeTZk9LMaciIsEyqcb6R9nMy4G6ERKgQmRFJF-prXk9t_4hy-b3wUVcAwghgQG5hbOcZ6H1EgxGaRIM2kckqBVR_dDj0jwAQD9Gu_ps605XS-RT7oaCIhWx6c4by4UplMJHDejMlbFVlG7YayY8vIGAI3xJ1gwt0-DxFGnumD7VV5d_C7wHjXSG3D-s5JWKeBE-JS4-RVGdIc5UdA-WQSxA5soP-lAvD86VJ5d6bx8XHpgLgQURXY8rXqHCzFBxwsM08FhHtESCb5nrkjzz_YwAiTjAw%3D%3D> | Privacy Policy <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnUXuZVM7_OJtrs4sVKqRL69ZcWx_mQsxFjp2q-yzg93hBRF6MOExGa7DyheZ28NmMBrclfkkC1fijhAbGyM7BsomMzjRnmeQBpm_VhsP0dymtLfWc_HkVfvcQmNJ-3DeP7GJieCvkVJaudgF-AEQYhbjZKMwZK-UR2hauzr8QqfjCwqJwM6ucao95-pGw1raoYg7U7Y3FbklVfIndEVyYKAbaTqJBTA9DoDDs4MUNac3G-b6h-7QTVqJz_VhAcAe7gkXFEQ_Ir6L56wk44zwe4KE_3g6HtauBe-rtelsXV5BMgi_5D75o0B5acmlUd-eMC_cxPPob1_otX_k8GEwCAQNnJOGER91z5BH55ZK5M1xg5I_DOgWsNizKgSetUegmQ%3D> | Terms?&?Conditions <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnUvvbr8cQlppI2PVz5oOFn71UzG5U-yoDUk0zhO7T88kiXf--5iQwe940SunePjMQMS2SKsmDg-zT_cUfcOANAbL0MiRezCpos13tZaQOEMtvB60MRYv7vFRJ3o-i7Dr_VgvpJq042EmizrQA2CQfEgUTPzUYpUTIhVxdmUN85qW7iPCJzAahckkGGI5hSNdGJttb_7BZCOxLwHYy4nxFEKKvbpf7fqj65zrU5yO0_inqWQOy3uctEgSx5PUw_PdQJVeByyttnirLS8jgU4cQd-2iQXmo-k9NT9asuQi5zLAMcPQVPSdsJ_5hqBJCD3xLp46aKz1jjRGjxcX6bdTX1j>
>> 4600 East Washington Street, Suite 305, Phoenix,?AZ?85034,?USA <>
>> Copyright ? 2019 Namecheap.com <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnW1cXFxSbbBDESBbekfxCqvLHlnZr5YtjKjux8kfg4GXjwP7r-Sy22hCXRjyGrQR8EUAQbYeeEo2HpGuEZSpfYsZBOsAu0RQ93tCU0S4w4FwC1yWr8znlA4l3F9ZEKx5cT7GzcA1lH23OYuu8tnku652lYR6mUmK0wTimEBOuaCFXoWvPmhqPm-AEXnqVMIAZLoqzb6mxLQrNhgYwB6CmNeU-afwpiKHeOAbrJq92kelkePoylLe_K3UbbGpEuYr7BxGJ75Yt84T49hTdOngE88Mlvtm5b4OJajVQ7iGJq7VTBzryLdk2f2Rc06hB8n2vaxgQ36vHC8aFuylhl1jrYG>
>>  <https://links.namecheap.com/u/click?_t=9a766a4fa5294d089b01463bac20344b&_m=edd807860a164000ae7c07e2d2fd9968&_e=px-UPF_fgOnHzDd0Rgaol7h0El2A41UOGPC6e1ikUnW1cXFxSbbBDESBbekfxCqvLHlnZr5YtjKjux8kfg4GXjwP7r-Sy22hCXRjyGrQR8EUAQbYeeEo2HpGuEZSpfYsZBOsAu0RQ93tCU0S4w4FwC1yWr8znlA4l3F9ZEKx5cRPyOnJSiz4lfQmkPp6ntSni8e_9XnUzDpDv0IY8c55px4JCRhkWeSVFB4sZQIEjrP-6BfsijekNp4SIeGZyyWr5EXqDuWZT82dsdPB49u0uQB0omf8vdK-ubic6YEAB4hOlBJQCKtYw_ElhgiZKM28J5yEZKOlmrpfSQKKHAovP-rPZPENiTi2PGqCkTTGGwHpWwwa_kOME3jVZWG_d6N_>
>>  
> 
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190426/42e84dc3/attachment.htm>

From kathy at kathykleiman.com  Sat Apr 27 02:37:17 2019
From: kathy at kathykleiman.com (Kathy Kleiman)
Date: Fri, 26 Apr 2019 19:37:17 -0400
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <CADxLtge5sPy1Xz8q=bxJG4QDWN5GQ9X6WxBdhSB3jbwwt_9Uyg@mail.gmail.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <CADxLtge5sPy1Xz8q=bxJG4QDWN5GQ9X6WxBdhSB3jbwwt_9Uyg@mail.gmail.com>
Message-ID: <6c3a0203-5c6e-bc12-3d0f-739e5f634175@kathykleiman.com>

All,

I've created a Google Docs version for our .ORG renewal agreement -- 
everyone should have edit privileges:

https://docs.google.com/document/d/11tJsAL1F1thYTGUIrytqU9U8m_AEMPMSzn-IgUqaGxA/edit?usp=sharing 


Best, Kathy

On 4/24/2019 1:35 PM, Tatiana Tropina wrote:
> Hi all,
> Thanks to Michael for drafting the comment, I support the submission 
> of it!
> Cheers,
> Tanya
>
> On Tue, 23 Apr 2019 at 04:43, Michael Karanicolas 
> <mkaranicolas at gmail.com <mailto:mkaranicolas at gmail.com>> wrote:
>
>     Hello all,
>
>     Hope you are well. I am just writing regarding the?public comment
>     for renewing the .org registry agreement.
>
>     I reached out to Stephanie a few days ago about the possibility of
>     an NCSG submission, and she suggested there might be some
>     possibility to get something approved in advance of the April 29
>     deadline. I am attaching a first draft, and would be keen to hear
>     what you think.
>
>     Best wishes,
>
>     Michael
>     _______________________________________________
>     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
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190426/8a233bd4/attachment.htm>

From icann at ferdeline.com  Sun Apr 28 17:02:08 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Sun, 28 Apr 2019 14:02:08 +0000
Subject: [NCSG-PC] Fw: [council] FOR REVIEW: Final Draft PPSAI Response to
 Cyrus
In-Reply-To: <826e762590e44bd59af1d7afbd38c695@verisign.com>
References: <826e762590e44bd59af1d7afbd38c695@verisign.com>
Message-ID: <zilga1koDxOj5lrfp0hC_iChxW3V0CiPmhkfZGMZI26aNUfETJCNPw9JYSy0_fa8BaPSc3g66HOSS8xQZi1nkn_pR9xQVrNLTtzhQVxao_4=@ferdeline.com>

Does the NCSG have any concerns re: attached letter?

Thanks, Ayden

??????? Original Message ???????
On Friday, April 26, 2019 11:08 PM, Drazek, Keith via council <council at gnso.icann.org> wrote:

> Hi all,
>
> Following our discussions in Kobe and on the list, I have attached the final draft of the PPSAI response to Cyrus.
>
> The latest edits are acceptance of IPC suggested edits, except the reference to the GAC Communique, which I understand was agreed to.
>
> I?d like to send this out early next week, so please review. If I don?t hear anything back, I will send it on Tuesday at 2300 UTC.
>
> Thanks,
>
> Keith
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190428/15df5253/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Draft Letter_ Council to ICANN org re PPSAI Implementaton  Transfer Issues -- Draft 26-april-2019 - Drazek Redline.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 27430 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190428/15df5253/attachment.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Draft Letter_ Council to ICANN org re PPSAI Implementaton  Transfer Issues -- Draft 26-april-2019 Drazek.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 26264 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190428/15df5253/attachment-0001.docx>

From kathy at kathykleiman.com  Sun Apr 28 18:10:20 2019
From: kathy at kathykleiman.com (Kathy Kleiman)
Date: Sun, 28 Apr 2019 11:10:20 -0400
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <6c3a0203-5c6e-bc12-3d0f-739e5f634175@kathykleiman.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <CADxLtge5sPy1Xz8q=bxJG4QDWN5GQ9X6WxBdhSB3jbwwt_9Uyg@mail.gmail.com>
 <6c3a0203-5c6e-bc12-3d0f-739e5f634175@kathykleiman.com>
Message-ID: <31783edc-9d1d-9c8c-382b-a18941c00c1a@kathykleiman.com>

Quick note that I've updated the .ORG letter to include objection to not 
only the Uniform Rapid suspension (URS), but also the other New gTLD 
rights protections mechanisms (RPMs) that ICANN is putting into the 
legacy gTLDs.

The decision of the review and extension of these RPMs to legacy gTLDs 
is now before the GNSO and RPM WG and we are evaluating, discussing, 
researching, etc. Thus, the same concerns apply... and I expanded the 
comment slightly to include them. All visible via redline.

Please review. Can we send?

Best, Kathy

On 4/26/2019 7:37 PM, Kathy Kleiman wrote:
>
> All,
>
> I've created a Google Docs version for our .ORG renewal agreement -- 
> everyone should have edit privileges:
>
> https://docs.google.com/document/d/11tJsAL1F1thYTGUIrytqU9U8m_AEMPMSzn-IgUqaGxA/edit?usp=sharing 
>
>
> Best, Kathy
>
> On 4/24/2019 1:35 PM, Tatiana Tropina wrote:
>> Hi all,
>> Thanks to Michael for drafting the comment, I support the submission 
>> of it!
>> Cheers,
>> Tanya
>>
>> On Tue, 23 Apr 2019 at 04:43, Michael Karanicolas 
>> <mkaranicolas at gmail.com <mailto:mkaranicolas at gmail.com>> wrote:
>>
>>     Hello all,
>>
>>     Hope you are well. I am just writing regarding the?public comment
>>     for renewing the .org registry agreement.
>>
>>     I reached out to Stephanie a few days ago about the possibility
>>     of an NCSG submission, and she suggested there might be some
>>     possibility to get something approved in advance of the April 29
>>     deadline. I am attaching a first draft, and would be keen to hear
>>     what you think.
>>
>>     Best wishes,
>>
>>     Michael
>>     _______________________________________________
>>     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
>>
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190428/d632af52/attachment.htm>

From icann at ferdeline.com  Sun Apr 28 18:53:16 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Sun, 28 Apr 2019 15:53:16 +0000
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <31783edc-9d1d-9c8c-382b-a18941c00c1a@kathykleiman.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <CADxLtge5sPy1Xz8q=bxJG4QDWN5GQ9X6WxBdhSB3jbwwt_9Uyg@mail.gmail.com>
 <6c3a0203-5c6e-bc12-3d0f-739e5f634175@kathykleiman.com>
 <31783edc-9d1d-9c8c-382b-a18941c00c1a@kathykleiman.com>
Message-ID: <gYZavULHtiFeAxwSD4C2_1v3Vrk-rYaP4lUWhD5vzii6xDAGsKvPxVNk4jaokKuoTauGP_iz_pcB9Z7CTIBmnvoF-oidPfjFW6-Uv9-JGVU=@ferdeline.com>

Thanks Kathy, this is looking good to me. I have made some suggested edits to the Google Doc, and hope we can submit this ASAP.

Best wishes, Ayden

??????? Original Message ???????
On Sunday, April 28, 2019 5:10 PM, Kathy Kleiman <kathy at kathykleiman.com> wrote:

> Quick note that I've updated the .ORG letter to include objection to not only the Uniform Rapid suspension (URS), but also the other New gTLD rights protections mechanisms (RPMs) that ICANN is putting into the legacy gTLDs.
>
> The decision of the review and extension of these RPMs to legacy gTLDs is now before the GNSO and RPM WG and we are evaluating, discussing, researching, etc. Thus, the same concerns apply... and I expanded the comment slightly to include them. All visible via redline.
>
> Please review. Can we send?
>
> Best, Kathy
>
> On 4/26/2019 7:37 PM, Kathy Kleiman wrote:
>
>> All,
>>
>> I've created a Google Docs version for our .ORG renewal agreement -- everyone should have edit privileges:
>>
>> https://docs.google.com/document/d/11tJsAL1F1thYTGUIrytqU9U8m_AEMPMSzn-IgUqaGxA/edit?usp=sharing
>>
>> Best, Kathy
>>
>> On 4/24/2019 1:35 PM, Tatiana Tropina wrote:
>>
>>> Hi all,
>>> Thanks to Michael for drafting the comment, I support the submission of it!
>>> Cheers,
>>> Tanya
>>>
>>> On Tue, 23 Apr 2019 at 04:43, Michael Karanicolas <mkaranicolas at gmail.com> wrote:
>>>
>>>> Hello all,
>>>>
>>>> Hope you are well. I am just writing regarding the public comment for renewing the .org registry agreement.
>>>>
>>>> I reached out to Stephanie a few days ago about the possibility of an NCSG submission, and she suggested there might be some possibility to get something approved in advance of the April 29 deadline. I am attaching a first draft, and would be keen to hear what you think.
>>>>
>>>> Best wishes,
>>>>
>>>> Michael
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>>
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>>
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon
> Virus-free. [www.avast.com](https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link)
>
> #DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190428/72e5f0a5/attachment.htm>

From kathy at kathykleiman.com  Mon Apr 29 03:41:33 2019
From: kathy at kathykleiman.com (Kathy Kleiman)
Date: Sun, 28 Apr 2019 20:41:33 -0400
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <gYZavULHtiFeAxwSD4C2_1v3Vrk-rYaP4lUWhD5vzii6xDAGsKvPxVNk4jaokKuoTauGP_iz_pcB9Z7CTIBmnvoF-oidPfjFW6-Uv9-JGVU=@ferdeline.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <CADxLtge5sPy1Xz8q=bxJG4QDWN5GQ9X6WxBdhSB3jbwwt_9Uyg@mail.gmail.com>
 <6c3a0203-5c6e-bc12-3d0f-739e5f634175@kathykleiman.com>
 <31783edc-9d1d-9c8c-382b-a18941c00c1a@kathykleiman.com>
 <gYZavULHtiFeAxwSD4C2_1v3Vrk-rYaP4lUWhD5vzii6xDAGsKvPxVNk4jaokKuoTauGP_iz_pcB9Z7CTIBmnvoF-oidPfjFW6-Uv9-JGVU=@ferdeline.com>
Message-ID: <2b7e534d-c856-353b-a843-4455a352a797@kathykleiman.com>

Tx for the edits, Ayden. They definitely make the comment better and 
clearer.

What a quote you posted from National Council of Nonprofits (NCSG 
list)!? It's amazing to see the number and breadth of nonprofits 
expressing deep concerns in this proceeding.

Quick note: deadline tomorrow (Mon).

Best, Kathy

On 4/28/2019 11:53 AM, Ayden F?rdeline wrote:
> Thanks Kathy, this is looking good to me. I have made some suggested 
> edits to the Google Doc, and hope we can submit this ASAP.
>
> Best wishes, Ayden
>
>
> ??????? Original Message ???????
> On Sunday, April 28, 2019 5:10 PM, Kathy Kleiman 
> <kathy at kathykleiman.com> wrote:
>
>> Quick note that I've updated the .ORG letter to include objection to 
>> not only the Uniform Rapid suspension (URS), but also the other New 
>> gTLD rights protections mechanisms (RPMs) that ICANN is putting into 
>> the legacy gTLDs.
>>
>> The decision of the review and extension of these RPMs to legacy 
>> gTLDs is now before the GNSO and RPM WG and we are evaluating, 
>> discussing, researching, etc. Thus, the same concerns apply... and I 
>> expanded the comment slightly to include them. All visible via redline.
>>
>> Please review. Can we send?
>>
>> Best, Kathy
>>
>> On 4/26/2019 7:37 PM, Kathy Kleiman wrote:
>>>
>>> All,
>>>
>>> I've created a Google Docs version for our .ORG renewal agreement -- 
>>> everyone should have edit privileges:
>>>
>>> https://docs.google.com/document/d/11tJsAL1F1thYTGUIrytqU9U8m_AEMPMSzn-IgUqaGxA/edit?usp=sharing 
>>>
>>>
>>> Best, Kathy
>>>
>>> On 4/24/2019 1:35 PM, Tatiana Tropina wrote:
>>>> Hi all,
>>>> Thanks to Michael for drafting the comment, I support the 
>>>> submission of it!
>>>> Cheers,
>>>> Tanya
>>>>
>>>> On Tue, 23 Apr 2019 at 04:43, Michael Karanicolas 
>>>> <mkaranicolas at gmail.com <mailto:mkaranicolas at gmail.com>> wrote:
>>>>
>>>>     Hello all,
>>>>
>>>>     Hope you are well. I am just writing regarding the?public
>>>>     comment for renewing the .org registry agreement.
>>>>
>>>>     I reached out to Stephanie a few days ago about the possibility
>>>>     of an NCSG submission, and she suggested there might be some
>>>>     possibility to get something approved in advance of the April
>>>>     29 deadline. I am attaching a first draft, and would be keen to
>>>>     hear what you think.
>>>>
>>>>     Best wishes,
>>>>
>>>>     Michael
>>>>     _______________________________________________
>>>>     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
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>
>>> _______________________________________________
>>> 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://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon>
>> 	Virus-free. www.avast.com 
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
>>
>>
>


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190428/302ebe89/attachment.htm>

From farell at benin2point0.org  Mon Apr 29 09:53:13 2019
From: farell at benin2point0.org (Farell FOLLY)
Date: Mon, 29 Apr 2019 08:53:13 +0200
Subject: [NCSG-PC] Call for NCSG alternate to EPDP team
In-Reply-To: <CAH5sThkcmLC+r5qNnCZz4m8auuAA=UxyeSigU8GgAnZWTM4P=g@mail.gmail.com>
References: <CAH5sTh=vRw3YuRXSWeWSXDsDx-55LihhOnRHQszqV_9L=NUW1A@mail.gmail.com>
 <CAH5sThkac-eeZAQ-ke8MD9qZOBJ5ysDjs82ynbKS3Z8a+QgXpw@mail.gmail.com>
 <6d84d832-a099-4aeb-dfd8-f0e563d48da0@mail.utoronto.ca>
 <CAH5sThm6QDHqrxcf4T71QTa6EFXn3tPvQX97mVOKx-SOG19jZg@mail.gmail.com>
 <CAH5sThnnsX430pj7o4O=4Rcge83CNsYDXUPkYKrjY-AW-Y8YaA@mail.gmail.com>
 <CABDXvWq3Y_5R2PE-RX8hvHNyfZdoxD37uNJpdFiW1dRu0BwauQ@mail.gmail.com>
 <CAH5sThkCt5cDSdcbu1PNA9fESTxbbfnNq5XcFrm3_2LwA3C4aQ@mail.gmail.com>
 <CAH5sThkcmLC+r5qNnCZz4m8auuAA=UxyeSigU8GgAnZWTM4P=g@mail.gmail.com>
Message-ID: <BD7E9196-10C2-46A2-A5BC-1E0973572408@benin2point0.org>

Dear Rafik,

I am ok with that.

@__f_f__

Best Regards
____________________________________

(Ekue) Farell FOLLY
NCUC Rep. to the NCSG Policy Committee
linkedin.com/in/farellf 






> On 17 Apr 2019, at 13:28, Rafik Dammak <rafik.dammak at GMAIL.COM> wrote:
> 
> Hi all,
> 
> since the start of phase 2 is close we need to replace Collin as alternate.
> here a draft call for candidates tweaked from the call we made in last summer  and adjust it to phase 2 https://docs.google.com/document/d/1NqqaDC0aSOgLCOFe4flKQ2MTA0hTbw8xgloFAzTauSw/edit <https://docs.google.com/document/d/1NqqaDC0aSOgLCOFe4flKQ2MTA0hTbw8xgloFAzTauSw/edit> .
> 
> As timeline, I think 1 week for a call and 3 days for selection is enough since we only have one slot of fill.
> please share your thoughts as we should start this process quickly and have an alternate on time to be able to follow the discussions and be ready to step up.
> 
> Best,
> 
> Rafik
> 
> ---------- Forwarded message ---------
> De : Rafik Dammak <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>>
> Date: lun. 1 avr. 2019 ? 15:05
> Subject: Re: [NCSG-PC] NCSG representatives to EPDP team
> To: ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is> <ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>>
> 
> 
> hi all
> 
> for the replacement, I proposed before to tweak the previous call for candidates to replace Collin and update with bits relevant to phase 2 but also regarding expected knowledge of phase 1. if there is no objection, I will share the draft call within this week so we can start a short call by next week.
> 
> Best,
> 
> Rafik
> 
> Le ven. 29 mars 2019 ? 19:09, Ars?ne Tungali <arsenebaguma at gmail.com <mailto:arsenebaguma at gmail.com>> a ?crit :
> Thanks, everyone for willing to continue, I believe this is good for
> us that you are willling to continue representing us throughout phase
> 2.
> 
> I am sure we will be able to have a replacement for Collin whom I
> would like to thank for being there during phase 1 as an alternate.
> 
> 2019-03-29 2:04 UTC+02:00, Rafik Dammak <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>>:
> > Hi,
> >
> > all current EPDP representatives confirmed they will continue for phase 2
> > and Tatiana and David as alternates.
> > we only have to replace Collin as alternate.
> >
> > Best,
> >
> > Rafik
> > Le mer. 27 mars 2019 ? 23:47, Rafik Dammak <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>> a
> > ?crit :
> >
> >> thanks Stephanie.
> >> we are still missing Ayden and Julf confirmation. I thought Ayden
> >> expressed his intention to not continue previously but stated he was
> >> still
> >> thinking during Kobe meeting in PC session.
> >> I would like to close this quickly and that we do call for candidates
> >> asap.
> >>
> >> Best,
> >>
> >> Rafik
> >>
> >> Le mer. 27 mars 2019 ? 00:48, Stephanie Perrin <
> >> stephanie.perrin at mail.utoronto.ca <mailto:stephanie.perrin at mail.utoronto.ca>> a ?crit :
> >>
> >>> Sorry, I thought I had confirmed. Yes, I am in for the next haul.
> >>>
> >>> Stephanie
> >>> On 2019-03-26 00:11, Rafik Dammak wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I am resuming the discussion for this. First action will to finalize the
> >>> confirmation with all members.
> >>> I only heard from Farzaneh, Milton, Amr that they will continue as rep
> >>> and Tatiana and David as alternate.I assume Stephanie will continue.
> >>> I aiming to confirm by Friday so we can have fairly quick call to
> >>> replace
> >>> if needed.
> >>>
> >>> Best,
> >>>
> >>> Rafik
> >>> Le mar. 5 mars 2019 ? 08:17, Rafik Dammak <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>> a
> >>> ?crit :
> >>>
> >>>> Hi all,
> >>>>
> >>>> Keith communicated last week with all chairs of groups represented in
> >>>> EPDP team to confirm or replace their members there for phase 2. The
> >>>> same
> >>>> communication was shared with EPDP team.
> >>>>
> >>>> We are confirming with our NCSG representatives if they are willing to
> >>>> continue for phase 2. We might need to do some replacements and we have
> >>>> to
> >>>> act quickly in order for new appointees to catch-up. It also depends on
> >>>> the
> >>>> expected workload and that is ongoing discussion.
> >>>>
> >>>> One way is to tweak the previous call for candidates and send it asap
> >>>> in
> >>>> order to get a good pool of candidates from where to select.
> >>>> please let me know your thoughts and suggestions.
> >>>>
> >>>> Best,
> >>>>
> >>>> Rafik
> >>>>
> >>>
> >>> _______________________________________________
> >>> NCSG-PC mailing
> >>> listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc <http://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>
> >>>
> >>
> >
> 
> 
> -- 
> ------------------------
> **Ars?ne Tungali* <http://about.me/ArseneTungali <http://about.me/ArseneTungali>>*
> Co-Founder & Executive Director, *Rudi international
> <http://www.rudiinternational.org <http://www.rudiinternational.org/>>*,
> CEO,* Smart Services Sarl <https://www.smart-kitoko.com/ <https://www.smart-kitoko.com/>>*,
> Tel: +243 993810967 (DRC)
> GPG: 523644A0
> 
> 2015 Mandela Washington Fellow
> <
> http://tungali.blogspot.com/2015/06/selected-for-2015-mandela-washington.html <http://tungali.blogspot.com/2015/06/selected-for-2015-mandela-washington.html>>
> 
> (YALI) - ICANN GNSO Council Member
> <https://gnso.icann.org/en/about/gnso-council.htm <https://gnso.icann.org/en/about/gnso-council.htm>> Member. UN IGF MAG
> <https://www.un.org/press/en/2018/pi2247.doc.htm <https://www.un.org/press/en/2018/pi2247.doc.htm>> Member
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190429/c2a3d5eb/attachment.htm>

From rafik.dammak at gmail.com  Mon Apr 29 14:28:36 2019
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Mon, 29 Apr 2019 20:28:36 +0900
Subject: [NCSG-PC] Review of Comment on Renewal of .org Registry Agreement
In-Reply-To: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
Message-ID: <CAH5sThnLqOskwj5oj5g8ZMKxLEY+3ZCMX0GeH9S=z3NNe2ys5Q@mail.gmail.com>

Hi all,

I think all the edits in the draft are accepted (
https://docs.google.com/document/d/11tJsAL1F1thYTGUIrytqU9U8m_AEMPMSzn-IgUqaGxA/edit).
I understand there is still some disagreement raised in the list about the
the price cap and there is also some proposed middle ground in the draft to
not object totally to the cap removal. I am happy there was discussion in
NCSG list regarding such issue and hoped that such draft was shared earlier.
the deadline for public comment is today at 23:59 UTC so looking to hear
from the rest of NCSG PC members if there is any strong disagreement
regarding sending the draft.

Best Regards,

Rafik


Le mar. 23 avr. 2019 ? 11:43, Michael Karanicolas <mkaranicolas at gmail.com>
a ?crit :

> Hello all,
>
> Hope you are well. I am just writing regarding the public comment for
> renewing the .org registry agreement.
>
> I reached out to Stephanie a few days ago about the possibility of an NCSG
> submission, and she suggested there might be some possibility to get
> something approved in advance of the April 29 deadline. I am attaching a
> first draft, and would be keen to hear what you think.
>
> Best wishes,
>
> Michael
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190429/127f75f5/attachment.htm>

From icann at ferdeline.com  Mon Apr 29 23:37:51 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Mon, 29 Apr 2019 20:37:51 +0000
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <2b7e534d-c856-353b-a843-4455a352a797@kathykleiman.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <CADxLtge5sPy1Xz8q=bxJG4QDWN5GQ9X6WxBdhSB3jbwwt_9Uyg@mail.gmail.com>
 <6c3a0203-5c6e-bc12-3d0f-739e5f634175@kathykleiman.com>
 <31783edc-9d1d-9c8c-382b-a18941c00c1a@kathykleiman.com>
 <gYZavULHtiFeAxwSD4C2_1v3Vrk-rYaP4lUWhD5vzii6xDAGsKvPxVNk4jaokKuoTauGP_iz_pcB9Z7CTIBmnvoF-oidPfjFW6-Uv9-JGVU=@ferdeline.com>
 <2b7e534d-c856-353b-a843-4455a352a797@kathykleiman.com>
Message-ID: <chY8v4ffRhChWO9R6iHHVTDwDpi5xgcTqztHI_AzEpAnCuI4qGA2bgVXBjjagXAZSfze6igv4k8aVTHr10HiTFOr2uEWwgd2WptAeAldDks=@ferdeline.com>

Hi all,

Are we able to submit this comment today?

Best wishes,

Ayden

Sent from ProtonMail Mobile

On Mon, Apr 29, 2019 at 02:41, Kathy Kleiman <kathy at kathykleiman.com> wrote:

> Tx for the edits, Ayden. They definitely make the comment better and clearer.
>
> What a quote you posted from National Council of Nonprofits (NCSG list)!  It's amazing to see the number and breadth of nonprofits expressing deep concerns in this proceeding.
>
> Quick note: deadline tomorrow (Mon).
>
> Best, Kathy
>
> On 4/28/2019 11:53 AM, Ayden F?rdeline wrote:
>
>> Thanks Kathy, this is looking good to me. I have made some suggested edits to the Google Doc, and hope we can submit this ASAP.
>>
>> Best wishes, Ayden
>>
>> ??????? Original Message ???????
>> On Sunday, April 28, 2019 5:10 PM, Kathy Kleiman [<kathy at kathykleiman.com>](mailto:kathy at kathykleiman.com) wrote:
>>
>>> Quick note that I've updated the .ORG letter to include objection to not only the Uniform Rapid suspension (URS), but also the other New gTLD rights protections mechanisms (RPMs) that ICANN is putting into the legacy gTLDs.
>>>
>>> The decision of the review and extension of these RPMs to legacy gTLDs is now before the GNSO and RPM WG and we are evaluating, discussing, researching, etc. Thus, the same concerns apply... and I expanded the comment slightly to include them. All visible via redline.
>>>
>>> Please review. Can we send?
>>>
>>> Best, Kathy
>>>
>>> On 4/26/2019 7:37 PM, Kathy Kleiman wrote:
>>>
>>>> All,
>>>>
>>>> I've created a Google Docs version for our .ORG renewal agreement -- everyone should have edit privileges:
>>>>
>>>> https://docs.google.com/document/d/11tJsAL1F1thYTGUIrytqU9U8m_AEMPMSzn-IgUqaGxA/edit?usp=sharing
>>>>
>>>> Best, Kathy
>>>>
>>>> On 4/24/2019 1:35 PM, Tatiana Tropina wrote:
>>>>
>>>>> Hi all,
>>>>> Thanks to Michael for drafting the comment, I support the submission of it!
>>>>> Cheers,
>>>>> Tanya
>>>>>
>>>>> On Tue, 23 Apr 2019 at 04:43, Michael Karanicolas <mkaranicolas at gmail.com> wrote:
>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> Hope you are well. I am just writing regarding the public comment for renewing the .org registry agreement.
>>>>>>
>>>>>> I reached out to Stephanie a few days ago about the possibility of an NCSG submission, and she suggested there might be some possibility to get something approved in advance of the April 29 deadline. I am attaching a first draft, and would be keen to hear what you think.
>>>>>>
>>>>>> Best wishes,
>>>>>>
>>>>>> Michael
>>>>>> _______________________________________________
>>>>>> NCSG-PC mailing list
>>>>>> NCSG-PC at lists.ncsg.is
>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>>
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>>
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon
>>> Virus-free. [www.avast.com](https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link)
>
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon	Virus-free. [www.avast.com](https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link)#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190429/29fdd1bc/attachment.htm>

From farzaneh.badii at gmail.com  Tue Apr 30 00:10:39 2019
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Mon, 29 Apr 2019 17:10:39 -0400
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <chY8v4ffRhChWO9R6iHHVTDwDpi5xgcTqztHI_AzEpAnCuI4qGA2bgVXBjjagXAZSfze6igv4k8aVTHr10HiTFOr2uEWwgd2WptAeAldDks=@ferdeline.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <CADxLtge5sPy1Xz8q=bxJG4QDWN5GQ9X6WxBdhSB3jbwwt_9Uyg@mail.gmail.com>
 <6c3a0203-5c6e-bc12-3d0f-739e5f634175@kathykleiman.com>
 <31783edc-9d1d-9c8c-382b-a18941c00c1a@kathykleiman.com>
 <gYZavULHtiFeAxwSD4C2_1v3Vrk-rYaP4lUWhD5vzii6xDAGsKvPxVNk4jaokKuoTauGP_iz_pcB9Z7CTIBmnvoF-oidPfjFW6-Uv9-JGVU=@ferdeline.com>
 <2b7e534d-c856-353b-a843-4455a352a797@kathykleiman.com>
 <chY8v4ffRhChWO9R6iHHVTDwDpi5xgcTqztHI_AzEpAnCuI4qGA2bgVXBjjagXAZSfze6igv4k8aVTHr10HiTFOr2uEWwgd2WptAeAldDks=@ferdeline.com>
Message-ID: <CAN1qJvDyxQQdZfFbhteV5Gdwk8s0rvDq-zfP=H0kJtbJTw6_1w@mail.gmail.com>

I am sorry I am late to the game. But there two issues that greatly concern
me and I might just be wrong.

1. What do they mean searchable WHOIS should be included? As far as I know
.ORG is not a thick registry. Or am I wrong?
Basically .NGO that is being operated by PIR doesn't allow registrars to
sell domains to sanctioned countries because of US sanctions.  I have not
looked into this but I am worried that some changes in .ORG agreement
create a barrier for registrars to register domain names based in
sanctioned countries. Might be a baseless concern.

2. I Might have  been removed from the PIR advisory council mailing list.
Otherwise I have not received any email whatsoever about this renewal. Did
they not see the need to inform the advisory council? Did they inform them
and we were not included?

Just two points I wanted to raise. Doesn't have to be included .

On Mon, Apr 29, 2019 at 4:38 PM Ayden F?rdeline <icann at ferdeline.com> wrote:

> Hi all,
>
> Are we able to submit this comment today?
>
> Best wishes,
>
> Ayden
>
> Sent from ProtonMail Mobile
>
>
> On Mon, Apr 29, 2019 at 02:41, Kathy Kleiman <kathy at kathykleiman.com>
> wrote:
>
> Tx for the edits, Ayden. They definitely make the comment better and
> clearer.
>
> What a quote you posted from National Council of Nonprofits (NCSG list)!
> It's amazing to see the number and breadth of nonprofits expressing deep
> concerns in this proceeding.
>
> Quick note: deadline tomorrow (Mon).
>
> Best, Kathy
> On 4/28/2019 11:53 AM, Ayden F?rdeline wrote:
>
> Thanks Kathy, this is looking good to me. I have made some suggested edits
> to the Google Doc, and hope we can submit this ASAP.
>
> Best wishes, Ayden
>
>
> ??????? Original Message ???????
> On Sunday, April 28, 2019 5:10 PM, Kathy Kleiman <kathy at kathykleiman.com>
> <kathy at kathykleiman.com> wrote:
>
> Quick note that I've updated the .ORG letter to include objection to not
> only the Uniform Rapid suspension (URS), but also the other New gTLD rights
> protections mechanisms (RPMs) that ICANN is putting into the legacy gTLDs.
>
> The decision of the review and extension of these RPMs to legacy gTLDs is
> now before the GNSO and RPM WG and we are evaluating, discussing,
> researching, etc. Thus, the same concerns apply... and I expanded the
> comment slightly to include them. All visible via redline.
>
> Please review. Can we send?
>
> Best, Kathy
> On 4/26/2019 7:37 PM, Kathy Kleiman wrote:
>
> All,
>
> I've created a Google Docs version for our .ORG renewal agreement --
> everyone should have edit privileges:
>
> https://docs.google.com/document/d/11tJsAL1F1thYTGUIrytqU9U8m_AEMPMSzn-IgUqaGxA/edit?usp=sharing
>
>
> Best, Kathy
> On 4/24/2019 1:35 PM, Tatiana Tropina wrote:
>
> Hi all,
> Thanks to Michael for drafting the comment, I support the submission of
> it!
> Cheers,
> Tanya
>
> On Tue, 23 Apr 2019 at 04:43, Michael Karanicolas <mkaranicolas at gmail.com>
> wrote:
>
>> Hello all,
>>
>> Hope you are well. I am just writing regarding the public comment for
>> renewing the .org registry agreement.
>>
>> I reached out to Stephanie a few days ago about the possibility of an
>> NCSG submission, and she suggested there might be some possibility to get
>> something approved in advance of the April 29 deadline. I am attaching a
>> first draft, and would be keen to hear what you think.
>>
>> Best wishes,
>>
>> Michael
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>
> _______________________________________________
> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
> _______________________________________________
> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon>
> Virus-free. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
>
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
> <#m_4635106092708622390_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-- 
Farzaneh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190429/09c89977/attachment.htm>

From icann at ferdeline.com  Tue Apr 30 00:57:55 2019
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Mon, 29 Apr 2019 21:57:55 +0000
Subject: [NCSG-PC] Proposed Renewal of .org Registry Agreement
In-Reply-To: <CAN1qJvDyxQQdZfFbhteV5Gdwk8s0rvDq-zfP=H0kJtbJTw6_1w@mail.gmail.com>
References: <CAGQVoTic1Df7x6Xyop4Z=9Jfi7b_rvLhz_EHEMGfeUhndo3CYw@mail.gmail.com>
 <CADxLtge5sPy1Xz8q=bxJG4QDWN5GQ9X6WxBdhSB3jbwwt_9Uyg@mail.gmail.com>
 <6c3a0203-5c6e-bc12-3d0f-739e5f634175@kathykleiman.com>
 <31783edc-9d1d-9c8c-382b-a18941c00c1a@kathykleiman.com>
 <gYZavULHtiFeAxwSD4C2_1v3Vrk-rYaP4lUWhD5vzii6xDAGsKvPxVNk4jaokKuoTauGP_iz_pcB9Z7CTIBmnvoF-oidPfjFW6-Uv9-JGVU=@ferdeline.com>
 <2b7e534d-c856-353b-a843-4455a352a797@kathykleiman.com>
 <chY8v4ffRhChWO9R6iHHVTDwDpi5xgcTqztHI_AzEpAnCuI4qGA2bgVXBjjagXAZSfze6igv4k8aVTHr10HiTFOr2uEWwgd2WptAeAldDks=@ferdeline.com>
 <CAN1qJvDyxQQdZfFbhteV5Gdwk8s0rvDq-zfP=H0kJtbJTw6_1w@mail.gmail.com>
Message-ID: <OxWl3IqzUMvusEJKDXNcBbDxu5PYeYW2wBLWDwvyyDb6dIYUsFwMxUJDaI1qTVRoIRL7PUDyR9vnCRIQ97UAo2eb6c6wpVRArpqTvtRTZ7g=@ferdeline.com>

I believe .org is already a thick registry.

Best, Ayden

??????? Original Message ???????
On Monday, April 29, 2019 11:10 PM, farzaneh badii <farzaneh.badii at gmail.com> wrote:

> I am sorry I am late to the game. But there two issues that greatly concern me and I might just be wrong.
>
> 1. What do they mean searchable WHOIS should be included? As far as I know .ORG is not a thick registry. Or am I wrong?
> Basically .NGO that is being operated by PIR doesn't allow registrars to sell domains to sanctioned countries because of US sanctions.  I have not looked into this but I am worried that some changes in .ORG agreement create a barrier for registrars to register domain names based in sanctioned countries. Might be a baseless concern.
>
> 2. I Might have  been removed from the PIR advisory council mailing list. Otherwise I have not received any email whatsoever about this renewal. Did they not see the need to inform the advisory council? Did they inform them and we were not included?
>
> Just two points I wanted to raise. Doesn't have to be included .
>
> On Mon, Apr 29, 2019 at 4:38 PM Ayden F?rdeline <icann at ferdeline.com> wrote:
>
>> Hi all,
>>
>> Are we able to submit this comment today?
>>
>> Best wishes,
>>
>> Ayden
>>
>> Sent from ProtonMail Mobile
>>
>> On Mon, Apr 29, 2019 at 02:41, Kathy Kleiman <kathy at kathykleiman.com> wrote:
>>
>>> Tx for the edits, Ayden. They definitely make the comment better and clearer.
>>>
>>> What a quote you posted from National Council of Nonprofits (NCSG list)!  It's amazing to see the number and breadth of nonprofits expressing deep concerns in this proceeding.
>>>
>>> Quick note: deadline tomorrow (Mon).
>>>
>>> Best, Kathy
>>>
>>> On 4/28/2019 11:53 AM, Ayden F?rdeline wrote:
>>>
>>>> Thanks Kathy, this is looking good to me. I have made some suggested edits to the Google Doc, and hope we can submit this ASAP.
>>>>
>>>> Best wishes, Ayden
>>>>
>>>> ??????? Original Message ???????
>>>> On Sunday, April 28, 2019 5:10 PM, Kathy Kleiman [<kathy at kathykleiman.com>](mailto:kathy at kathykleiman.com) wrote:
>>>>
>>>>> Quick note that I've updated the .ORG letter to include objection to not only the Uniform Rapid suspension (URS), but also the other New gTLD rights protections mechanisms (RPMs) that ICANN is putting into the legacy gTLDs.
>>>>>
>>>>> The decision of the review and extension of these RPMs to legacy gTLDs is now before the GNSO and RPM WG and we are evaluating, discussing, researching, etc. Thus, the same concerns apply... and I expanded the comment slightly to include them. All visible via redline.
>>>>>
>>>>> Please review. Can we send?
>>>>>
>>>>> Best, Kathy
>>>>>
>>>>> On 4/26/2019 7:37 PM, Kathy Kleiman wrote:
>>>>>
>>>>>> All,
>>>>>>
>>>>>> I've created a Google Docs version for our .ORG renewal agreement -- everyone should have edit privileges:
>>>>>>
>>>>>> https://docs.google.com/document/d/11tJsAL1F1thYTGUIrytqU9U8m_AEMPMSzn-IgUqaGxA/edit?usp=sharing
>>>>>>
>>>>>> Best, Kathy
>>>>>>
>>>>>> On 4/24/2019 1:35 PM, Tatiana Tropina wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>> Thanks to Michael for drafting the comment, I support the submission of it!
>>>>>>> Cheers,
>>>>>>> Tanya
>>>>>>>
>>>>>>> On Tue, 23 Apr 2019 at 04:43, Michael Karanicolas <mkaranicolas at gmail.com> wrote:
>>>>>>>
>>>>>>>> Hello all,
>>>>>>>>
>>>>>>>> Hope you are well. I am just writing regarding the public comment for renewing the .org registry agreement.
>>>>>>>>
>>>>>>>> I reached out to Stephanie a few days ago about the possibility of an NCSG submission, and she suggested there might be some possibility to get something approved in advance of the April 29 deadline. I am attaching a first draft, and would be keen to hear what you think.
>>>>>>>>
>>>>>>>> Best wishes,
>>>>>>>>
>>>>>>>> Michael
>>>>>>>> _______________________________________________
>>>>>>>> NCSG-PC mailing list
>>>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> NCSG-PC mailing list
>>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>>
>>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>
>>>>>> _______________________________________________
>>>>>> NCSG-PC mailing list
>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>
>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon
>>>>> Virus-free. [www.avast.com](https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link)
>>>
>>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon
>>> Virus-free. [www.avast.com](https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link)
>>>
>>> #m_4635106092708622390_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> --
> Farzaneh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190429/6d27a5f9/attachment.htm>