From icann at ferdeline.com  Tue Aug  1 19:30:30 2017
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Tue, 01 Aug 2017 12:30:30 -0400
Subject: [NCSG-PC] Staff Report on Revised ICANN Procedure for Handling
	Whois Conflicts with Privacy Law Comment
Message-ID: <Sr2wdpx9z9vj6wG2LIyOCeaH5iRi-xFGNxgtGe7YxoEFTZHZKOwr5_-y5-jcJORU__BnsIJx5EmTKd1hzX7IsHxzKz9CvxB_KzHPjxfuP4A=@ferdeline.com>

Hi all,
ICANN staff have now published their report on comments received in relation to the Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law. [It can be read here.](https://www.icann.org/en/system/files/files/report-comments-whois-privacy-law-28jul17-en.pdf)
Best wishes, Ayden F?rdeline
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170801/07f35c45/attachment.htm>

From matthew at intpolicy.com  Tue Aug  1 19:35:32 2017
From: matthew at intpolicy.com (Matthew Shears)
Date: Tue, 1 Aug 2017 17:35:32 +0100
Subject: [NCSG-PC] NCSG Comment on GNSO operating procedures change
In-Reply-To: <9A97DC8E-D4E8-4110-8AE0-4AD57BCE8E4B@gmail.com>
References: <93940f3e-485d-2678-4f92-a9d85981d313@intpolicy.com>
 <aeac9647-4b76-a3bc-f199-a862597eb1c2@intpolicy.com>
 <30c249d1-c479-003c-0a82-997037d7456a@intpolicy.com>
 <8A6BC6C5-CA17-4CB3-8231-00A39DBD2287@eui.eu>
 <CAH5sThk7c-Oyj+v1Qh_=0gH5a_nN=o2yOvyrymueOxwQW7X9aA@mail.gmail.com>
 <9A97DC8E-D4E8-4110-8AE0-4AD57BCE8E4B@gmail.com>
Message-ID: <6a91a71d-2bed-6011-2d1a-5c743799225b@intpolicy.com>

Hi all

Wanted to get this back at the top of the list of to-do's as time is 
running out.

Appreciate the comments from some of the PC members but would welcome 
additional inputs, thoughts, etc.

See google doc below.

Thanks.

Matthew


On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
> Matt,
> I don?t have any comment to do, I agree with the statements and the 
> wording. Let me know if I can do anything specific to help. Other than 
> that you have my support. Thanks!
>
> Cheers,
> Mart?n
>
>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com 
>> <mailto:rafik.dammak at gmail.com>> wrote:
>>
>> Hi,
>>
>> the deadline for the public comment is the 10th of August, we have to 
>> finish consulting with NCSG members, review and endorsement prior to 
>> that. I suggest 8th August as our internal deadline.
>>
>> Best,
>>
>> Rafik
>>
>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu 
>> <mailto:stefania.milan at eui.eu>>:
>>
>>     Hi Matt, thanks. What's the deadline for this? I am in transit
>>     (and in fact, on holiday), witch sketchy internet access and the
>>     doc doesn't open for me today (might be the poor connection...)
>>
>>     Sent from my iPhone
>>
>>     On Jul 25, 2017, at 9:17 AM, Matthew Shears
>>     <matthew at intpolicy.com <mailto:matthew at intpolicy.com>> wrote:
>>
>>>     Let me qualify the last sentence - ICANN staff are not adding
>>>     new items in addition to the work of the DT, but rather adding
>>>     references to work done previously.
>>>
>>>
>>>     On 25/07/2017 16:05, Matthew Shears wrote:
>>>>     Calling all PCers
>>>>
>>>>     I have started on the above public comment but am still going
>>>>     through the consultation docs.  However, time marches on and we
>>>>     need to get this one underway.
>>>>
>>>>     So, please review the consultation docs here:
>>>>
>>>>     https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>     <https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en>
>>>>
>>>>     And make comments in the google doc here:
>>>>
>>>>     https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit
>>>>     <https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit>
>>>>
>>>>     Note that ICANN staff have used this opportunity to include
>>>>     other changes that the DT did not discuss.
>>>>
>>>>     Many thanks.
>>>>
>>>>     Matthew
>>>>
>>>>
>>>>     -- 
>>>>     Matthew Shears
>>>>     matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>>     +447712472987 <tel:+44%207712%20472987>
>>>>     Skype:mshears
>>>
>>>     -- 
>>>     Matthew Shears
>>>     matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>     +447712472987 <tel:+44%207712%20472987>
>>>     Skype:mshears
>>>     _______________________________________________
>>>     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>
>>
>>     The information transmitted is intended only for the person or
>>     entity to which it is addressed and may contain confidential
>>     and/or privileged material. Any review, retransmission,
>>     dissemination, distribution, forwarding, or other use of, or
>>     taking of any action in reliance upon, this information by
>>     persons or entities other than the intended recipient is
>>     prohibited without the express permission of the sender. If you
>>     received this communication in error, please contact the sender
>>     and delete the material from any computer.
>>
>>
>>     _______________________________________________
>>     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
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
> 	Virus-free. www.avg.com 
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

-- 


Matthew Shears
matthew at intpolicy.com
+447712472987
Skype:mshears

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

From stephanie.perrin at mail.utoronto.ca  Tue Aug  1 20:50:43 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Tue, 1 Aug 2017 13:50:43 -0400
Subject: [NCSG-PC] Fwd: [council] FW: Letter from Akram Atallah to James
 Bladel et alref:_00D1aY7OU._5001aJO2sg:ref
In-Reply-To: <2CB595CA-A12F-4867-AF11-872FE7A4D44A@godaddy.com>
References: <2CB595CA-A12F-4867-AF11-872FE7A4D44A@godaddy.com>
Message-ID: <22a3f221-9d0e-5dbe-cdb0-4a2dc38424f1@mail.utoronto.ca>

For discussion at our next policy meeting, and prefereably on the list 
prior to....

cheers Steph



-------- Forwarded Message --------
Subject: 	[council] FW: Letter from Akram Atallah to James Bladel et 
alref:_00D1aY7OU._5001aJO2sg:ref
Date: 	Tue, 1 Aug 2017 16:21:07 +0000
From: 	James M. Bladel <jbladel at godaddy.com>
To: 	GNSO Council List <council at gnso.icann.org>



Councilors ?

Please see attached for a letter from Akram Attallah (GDD), regarding 
ICANN?s procedure for handing WHOIS conflicts with local law.

I will ask Staff to add this discussion item to the agenda for our next 
meeting.

Thank you,


J.

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

James Bladel

GNSO Chair

*From: *ICANN Correspondence <correspondence at icann.org>
*Date: *Tuesday, August 1, 2017 at 11:16
*To: *"James M. Bladel" <jbladel at godaddy.com>
*Subject: *Letter from Akram Atallah to James Bladel et 
alref:_00D1aY7OU._5001aJO2sg:ref

Dear James Bladel,

Please find the attached letter as a follow up to the corresponndence 
sent on 09 June 2017 from Akram Atallah President of the Global Domains 
Division at ICANN. This letter will be posted shortly to ICANN 
Correspondence (https://www.icann.org/resources/pages/correspondence).

Please submit any questions you may have about this message to 
correspondence at icann.org.

Best Regards,
Hope Shafer

ICANN Correspondence Team
Internet Corporation for Assigned Names and Numbers (ICANN)
correspondence at icann.org

www.icann.org



ref:_00D1aY7OU._5001aJO2sg:ref

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170801/330c2d61/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Atallah to Bladel 01Aug17.pdf
Type: application/pdf
Size: 373664 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170801/330c2d61/attachment.pdf>
-------------- next part --------------
_______________________________________________
council mailing list
council at gnso.icann.org
https://mm.icann.org/mailman/listinfo/council


From mariliamaciel at gmail.com  Thu Aug  3 16:23:31 2017
From: mariliamaciel at gmail.com (Marilia Maciel)
Date: Thu, 3 Aug 2017 15:23:31 +0200
Subject: [NCSG-PC] YOUR FEEDBACK REQUESTED: Planning for 2018 NCPH
 Intersessional & GNSO Council strategic planning sessions
In-Reply-To: <20170730155836.ow6wy27fqgks2xgb@tarvainen.info>
References: <BD7D18AC-6881-4F5B-98D6-34BEA76816E8@icann.org>
 <87ae5419-3629-928c-6c78-2cf887b370f9@mail.utoronto.ca>
 <ZT8NmZ-0eSANsNNmGxQMjbI1MiOPBqSszdyJgMSyZXtYqADRWrs4aorUuEk0oA9C9Yxawlbj5IGpO_j3P8pQOTYhrjI1P2o4CScaDRSxIgA=@ferdeline.com>
 <CAH5sTh=nTotJk5k8bKSpceyQTkXjS6wAazpf5p_ikhadRUvoFA@mail.gmail.com>
 <29049bda-cb7a-f07a-c3d8-1d7942f6cbe0@mail.utoronto.ca>
 <50689cd9-39be-eb87-8d8e-0e8b83e167fa@apc.org>
 <AA0A2B79-A19A-42CA-B70D-21128800812F@gmail.com>
 <20170730155836.ow6wy27fqgks2xgb@tarvainen.info>
Message-ID: <CACpVkK3wMVTH8zMKQcnND4ims3RQ8vBv8LBp6+jFaKzGV8XZ2A@mail.gmail.com>

Hi

On Sun, Jul 30, 2017 at 5:58 PM, Tapani Tarvainen <
ncsg at tapani.tarvainen.info> wrote:

>
>
> So I think intersessionals are useful enough to continue, and while I
> appreciate the concerns of overloading people, Bill's suggestion of
> spreading the load is good: the more people we get involved, the
> better.
>

Agreed.

>
> And with that in mind, Ayden's argument against combining intersessional
> with other meetings makes a lot of sense. I don't have a strong opinion
> on that, though - sometimes it might work very well, sometimes less so.


I think while the interssesional is relevant, it would be much easier to
justify it (from both a practical and financial standpoints) if it was
coupled with some other activity. Someone mentioned the possibility to do
it back to back with GDD meeting too. No strong preferences as to what
meeting it should be coupled with (it could vary from year to year) but the
intersessional should not be a stand alone.


> I share the concerns about time and effort needed to prepare, however,
> and perhaps making them biannual or alternating them with something
> different (like a similar meeting with RrSG/RySG every other year)
> might be worth considering.
>

Great suggestion (re. similar meeting with RrSG/RySG every other year)

>
> As for location, visa-unfriendliness is a big concern. In particular
> USA has been problematic, every time I've been involved at least one
> of our would-be travellers has been unable to make it because of visa
> issues (unless I've forgotten something, in Reykjavik the only one who
> could not make it because of visa issues was Farzaneh, and that was
> due to US regulations, not Iceland's). And we knew in advance some
> people would not have been able to go to Istanbul either. Of course no
> location is perfect, I don't see any place that could guarantee
> everybody will get in, but visa-friendliness should definitely
> weigh heavily on location choice.
>

Agreed.


> Finally, considering 2018 in particular, even though I personally
> don't plan to be there, I think combining it with the Council
> Strategic Session makes a lot of sense.


Same for me.

Marilia



>
>
> On Sun, Jul 30, 2017 at 10:01:07AM +0900, William Drake (wjdrake at gmail.com)
> wrote:
> >
> > (also observer)
> >
> > +1 I thought the two meetings I participated in when chair were useful
> in terms of relational bridge building, clearly identifying areas of
> agreement/disagreement/possible joint actions between NCSG/CSG, and
> thinking about the NCPH trajectory in general in light of the evolution due
> to the new gTLDs.  At one of them, we also managed to do a very good
> outreach session which ultimately helped encourage important CSOs to join.
> If the argument is that some folks e.g. Councilors feel too tapped out to
> attend, then send other members who are available and interested, as long
> as there?s preparation and a clear mandate and any actual decisions come
> back to the general membership and ?leadership? bodies for vetting before
> action I don?t see the problem.  Could help with onboarding into WG work
> etc. too. Proximity to an office for logistics, not wandering the earth in
> search of post-meeting tourism.
> >
> > Bill
> >
> > > On Jul 30, 2017, at 02:01, avri doria <avri at apc.org> wrote:
> > >
> > > (observer)
> > >
> > > I think that the annual conversation between CSG et al and NCSG et al,
> > > is a good thing and an important thing. I think it also should be
> > > coordinated with staff contacts so that both CSG and NCSG can hear the
> > > same things.
> > >
> > > I think the GNSO council et al spending some time in retreat is also
> > > important for building a council that can sustain working together. It
> > > can't happen at the full meetings, so makes sense that it happen
> outside
> > > that.  I think this should also be don with staff access.
> > >
> > > I think all of these meetings are best done in proximity to an ICANN
> > > office and offset from the 3 main meetings.
> > >
> > > The meetings need planning and focus, but I do not believe it wise to
> > > let them drop.
> > >
> > > avri
> > >
> > >
> > >
> > > On 28-Jul-17 18:48, Stephanie Perrin wrote:
> > >>
> > >> I am not enthusiastic about more meetings either.  And I am not keen
> > >> on travelling to the US.....Los Angeles takes way longer than Iceland,
> > >> for me, with way more hassle.  I have never been to Mexico, so I dont
> > >> know how hard that is.  Am indifferent about putting the two meetings
> > >> together, makes sense not to fly twice.
> > >>
> > >> cheers SP
> > >>
> > >>
> > >> On 2017-07-28 18:30, Rafik Dammak wrote:
> > >>> Hi,
> > >>>
> > >>> I am among those who are not really supporting holding another
> > >>> intersessional meeting next year. We are not doing any serious review
> > >>> and trying to improve it but just carrying on because we got a
> budget.
> > >>> if the interesessional will be organized anyway, I think it would
> > >>> make sense to hold it in the same week with the Council planning
> > >>> meeting. that means 1 travel less for councilors at least.
> > >>>
> > >>> Best,
> > >>>
> > >>> Rafik
> > >>>
> > >>>
> > >>> 2017-07-28 19:57 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com
> > >>> <mailto:icann at ferdeline.com <mailto:icann at ferdeline.com>>>:
> > >>>
> > >>>    Thanks for sharing this, Stephanie, and for inviting our feedback.
> > >>>
> > >>>    I think the two meetings should be held separately at different
> > >>>    times of the year, as they serve different purposes and cater to
> > >>>    different audiences [with some overlap].
> > >>>
> > >>>    I understand that ICANN staff try only to travel during business
> > >>>    hours, but some of our participants might find it easier to be
> > >>>    able to travel to a meeting over a weekend and to have the
> > >>>    meeting commence on a Sunday. I am not sure what others think
> > >>>    about this suggestion, particularly those on the GNSO Council who
> > >>>    would be impacted here, but just putting that idea out there...
> > >>>
> > >>>    For the GNSO Council Strategic Planning Meeting, it makes sense
> > >>>    to me to have this in Los Angeles given it is the closest ICANN
> > >>>    office for the majority of the likely participants.
> > >>>
> > >>>    For the Intersessional (which I think should continue, though I
> > >>>    understand that is not a view held by all) I also think Los
> > >>>    Angeles makes a lot of sense, though I understand the participant
> > >>>    profiles vary, and it may be very difficult for many of the
> > >>>    Intersessional participants to travel to the United States. Based
> > >>>    on the participant profiles of everyone who attended the
> > >>>    Intersessional this year, I believe Mexico City would be much
> > >>>    easier for everyone to travel to [anyone with an existing US or
> > >>>    Canadian visa does not need a visa to enter Mexico, and for many
> > >>>    in Latin America, Mexico?s immigration policies are very fair].
> > >>>    It would also be a rather economical choice.
> > >>>
> > >>>    Best wishes, Ayden F?rdeline
> > >>>
> > >>>
> > >>>>    -------- Original Message --------
> > >>>>    Subject: [NCSG-PC] Fwd: YOUR FEEDBACK REQUESTED: Planning for
> > >>>>    2018 NCPH Intersessional & GNSO Council strategic planning
> sessions
> > >>>>    Local Time: July 27, 2017 9:37 PM
> > >>>>    UTC Time: July 27, 2017 8:37 PM
> > >>>>    From: stephanie.perrin at mail.utoronto.ca <mailto:
> stephanie.perrin at mail.utoronto.ca>
> > >>>>    <mailto:stephanie.perrin at mail.utoronto.ca <mailto:
> stephanie.perrin at mail.utoronto.ca>>
> > >>>>    To: ncsg-pc <ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>
> <mailto:ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>>>
> > >>>>
> > >>>>
> > >>>>    Perhaps we ought to discuss this on the broader list as well,
> > >>>>    just forwarding....
> > >>>>
> > >>>>    Stephanie
> > >>>>
> > >>>>
> > >>>>
> > >>>>    -------- Forwarded Message --------
> > >>>>    Subject:
> > >>>>          YOUR FEEDBACK REQUESTED: Planning for 2018 NCPH
> Intersessional
> > >>>>    & GNSO Council strategic planning sessions
> > >>>>    Date:
> > >>>>          Mon, 24 Jul 2017 15:22:29 +0000
> > >>>>    From:
> > >>>>          Mary Wong <mary.wong at icann.org <mailto:mary.wong at icann.org>>
> <mailto:mary.wong at icann.org <mailto:mary.wong at icann.org>>
> > >>>>    To:
> > >>>>          Phil Corwin <psc at vlaw-dc.com <mailto:psc at vlaw-dc.com>>
> <mailto:psc at vlaw-dc.com <mailto:psc at vlaw-dc.com>>, Susan
> > >>>>    Kawaguchi <susankpolicy at gmail.com <mailto:susankpolicy at gmail.com
> >>
> > >>>>    <mailto:susankpolicy at gmail.com <mailto:susankpolicy at gmail.com>>,
> Heather Forrest
> > >>>>    <haforrestesq at gmail.com <mailto:haforrestesq at gmail.com>>
> <mailto:haforrestesq at gmail.com <mailto:haforrestesq at gmail.com>>,
> > >>>>    icannlists <icannlists at winston.com <mailto:
> icannlists at winston.com>>
> > >>>>    <mailto:icannlists at winston.com <mailto:icannlists at winston.com>>,
> Wolf-Ulrich.Knoben
> > >>>>    <wolf-ulrich.knoben at t-online.de <mailto:wolf-ulrich.knoben at t-
> online.de>>
> > >>>>    <mailto:wolf-ulrich.knoben at t-online.de <mailto:
> wolf-ulrich.knoben at t-online.de>>, Anthony Harris
> > >>>>    <anthonyrharris at gmail.com <mailto:anthonyrharris at gmail.com>>
> <mailto:anthonyrharris at gmail.com <mailto:anthonyrharris at gmail.com>>,
> > >>>>    Rafik Dammak <rafik.dammak at gmail.com <mailto:
> rafik.dammak at gmail.com>>
> > >>>>    <mailto:rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>>,
> Milan, Stefania
> > >>>>    <Stefania.Milan at EUI.eu <mailto:Stefania.Milan at eui.eu>> <mailto:
> Stefania.Milan at EUI.eu <mailto:Stefania.Milan at EUI.eu>>, Marilia
> > >>>>    Maciel <mariliamaciel at gmail.com <mailto:mariliamaciel at gmail.com
> >>
> > >>>>    <mailto:mariliamaciel at gmail.com <mailto:mariliamaciel at gmail.com>>,
> Stephanie Perrin
> > >>>>    <stephanie.perrin at mail.utoronto.ca <mailto:
> stephanie.perrin at mail.utoronto.ca>>
> > >>>>    <mailto:stephanie.perrin at mail.utoronto.ca <mailto:
> stephanie.perrin at mail.utoronto.ca>>, Martin Pablo Silva
> > >>>>    Valent <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com
> >>
> > >>>>    <mailto:mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>>,
> Johan Helsingius
> > >>>>    <julf at julf.com <mailto:julf at julf.com>> <mailto:julf at julf.com
> <mailto:julf at julf.com>>
> > >>>>    CC:
> > >>>>          Benedetta Rossi <benedetta.rossi at icann.org <mailto:
> benedetta.rossi at icann.org>>
> > >>>>    <mailto:benedetta.rossi at icann.org <mailto:benedetta.rossi at icann.
> org>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>    Dear Heather, Susan, Marilia, Stefania, Stephanie, Phil, Rafik,
> > >>>>    Tony, Julf, Wolf-Ulrich, Paul and Martin,
> > >>>>
> > >>>>
> > >>>>
> > >>>>    I am writing to seek your input as we (ICANN staff) begin
> > >>>>    working with the GNSO Council leadership and the NCPH leadership
> > >>>>    to plan two face-to-face meetings that have been approved for FY
> > >>>>    2018. One is a 2-3 day strategic planning session for the GNSO
> > >>>>    Council (approved as a pilot project for FY2018), and the other
> > >>>>    is the periodic NCPH Intersessional meeting.
> > >>>>
> > >>>>
> > >>>>
> > >>>>    As the application for the GNSO Council?s strategic planning
> > >>>>    meeting had indicated that this might take place in January
> > >>>>    2018, and as the NCPH Intersessional has traditionally taken
> > >>>>    place in January or February, staff would like to know if you
> > >>>>    believe it will be _preferable for these two meetings to take
> > >>>>    place concurrently, such that both meetings can occur within the
> > >>>>    space of a single week in the same location, or if you think it
> > >>>>    will be better to plan them as two separate meetings taking
> > >>>>    place at different times in the year_.
> > >>>>
> > >>>>
> > >>>>
> > >>>>    You may be interested to know that the ICANN process for
> > >>>>    face-to-face meeting planning has been updated (as of June
> > >>>>    2017), such that meeting requests for location, dates and travel
> > >>>>    now have to be sent in several months ahead of time. For the
> > >>>>    GNSO Council strategic planning meeting, the budget approval
> > >>>>    requires an ICANN office location, with preference for Los
> > >>>>    Angeles ? hence, if you think running both meetings concurrently
> > >>>>    in the same week is better, this will most probably mean that
> > >>>>    the NCPH Intersessional will take place in Los Angeles as well.
> > >>>>
> > >>>>
> > >>>>
> > >>>>    We understand that, as these events are going to take place in
> > >>>>    calendar year 2018, several of you may no longer be on the
> > >>>>    Council by that time. In addition, decisions and programming
> > >>>>    concerning the NCPH Intersessional is the responsibility of the
> > >>>>    NCPH leadership and not the GNSO Council. However, for planning
> > >>>>    purposes we thought it appropriate to seek as much input as
> > >>>>    possible from those community members who may be most affected
> > >>>>    by the dates and timing, and so we hope you are able to provide
> > >>>>    us with your opinion as to which option is preferred.
> > >>>>
> > >>>>
> > >>>>
> > >>>>    Thanks and cheers
> > >>>>
> > >>>>    Mary
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>



-- 

*Mar?lia Maciel*
Digital Policy Senior Researcher, DiploFoundation

WMO Building *|* 7bis, Avenue de la Paix *| *1211 Geneva - Switzerland
*Tel *+41 (0) 22 9073632 *| *
*Email*: *MariliaM at diplomacy.edu <mariliam at diplomacy.edu>* *|** Twitter: *
*@MariliaM*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170803/fcfffdcd/attachment.htm>

From rafik.dammak at gmail.com  Fri Aug  4 10:39:13 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Fri, 4 Aug 2017 16:39:13 +0900
Subject: [NCSG-PC] Fw: [NCUC-DISCUSS] Suggested Comment: Draft Framework
 for Registry Operators to Respond to Security Threats
In-Reply-To: <CAH5sThktSm3qRv-1UH9sOEH0R4j4G4aev73XYTE70Zvn9OgSpw@mail.gmail.com>
References: <E1dbwdr-0005N3-F2@rmmprod06.runbox>
 <viDG_GKZm4MGicRFTne3yEZERwqRoqEYGvaYOBiMDIBmcXZpK3WOzB89GoIPEZ-HorUP_hvNPo6oJg4a9RcFT5qyvmWxwgkO61QEWNen_l4=@ferdeline.com>
 <CAH5sThktSm3qRv-1UH9sOEH0R4j4G4aev73XYTE70Zvn9OgSpw@mail.gmail.com>
Message-ID: <CAH5sThmx08DOsLL4AbzAeyJF9-YEQLjqy0hbyZALxT5=cGr6kA@mail.gmail.com>

Dear PC members,

any comment on the draft? we got an extension till 6th August, we should
review quickly and make a decision.

Best,

Rafik

2017-07-31 19:33 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:

> Hi Ayden,
>
> Yes it is for PC review. We worked on it the last days with Juan, Dina and
> Niels. James cannot response since is off for the coming days. I was going
> to send email to related ICANN staff to inform that we will make a late
> submission, hopefully by end of this week.
>
> Best,
>
> Rafik
>
>
> On Jul 31, 2017 7:18 PM, "Ayden F?rdeline" <icann at ferdeline.com> wrote:
>
> I believe the PC is being asked to review this comment which has been
> drafted by Dina and Juan. The submission deadline for comments on this
> issue is today, but I suspect we will not be able to meet that, so let's
> try for this Friday? I think we need to bring in a topic expert, James
> Gannon (cc'd), to get his opinion on this comment, too -- because I am
> happy to raise my hand and say I do not know anything about this topic.
>
> Best, Ayden
>
>
> -------- Original Message --------
> Subject: [NCUC-DISCUSS] Suggested Comment: Draft Framework for Registry
> Operators to Respond to Security Threats
> Local Time: July 30, 2017 11:24 PM
> UTC Time: July 30, 2017 10:24 PM
> From: thomascovenant at thomascovenant.org
> To: NCUC-discuss <ncuc-discuss at lists.ncuc.org>
>
> Hello,
>
> the comment proposal is underneath, what are your thoughts?
>
> https://docs.google.com/document/d/1TfgHuMqzD660_CHLQMXMW4ph
> nBtLSP94j6X5riY2Ko4/edit
>
> Note from Security Framework Drafting Team wiki workspace:
>
> - Is Public Comment required for the draft Framework?
> - This is not a policy implementation nor a contractual requirements
> document; therefore, a public comment proceeding would not be required.
> However, SFDT has decided to conduct a public comment for broader community
> feedback prior to finalization of the Framework.
>
> Main points:
>
> - Framework should be expanded
> - Several minor details are to be clarified, restructuring proposal
> - as a small step in response to proposed detailed report examination, I
> suggest we include a recommendation on Responsible Threat Disclosure.
>
> Finally, I quote Point 3 from the Comment:
>
> "Since the following examination of threat report is identified in the
> Framework, we strongly suggest including a recommendation on Responsible
> Threat Disclosure to be included in the document:
>
> "Each RO should scrutinize, question or otherwise inquire about the
> legitimacy of the origin
> of a request, in accordance with their own internal policies and
> processes."
>
> We have seen a broad variation in handling security threat reports,
> varying from constructive actions addressing the issues to punishment of
> the reporting party. Benefits of responsible threat submission are obvious.
>
> In this context, it is important to underline benefits and importance of
> responsible threat disclosure. We request recommendation to extend goodwill
> and not cause harm to the reporting party whenever possible:
>
> When applicable, RO should provide:
>
> - an easy way to report security threats and violation
> - encrypted ways of communication
> - option of anonymous submission"
>
> Other:
>
> - This is my first comment drafted with input from Juan Manuel Rojas
> (thank you for commenting). Access to shared document and request for
> review was given to those who expressed interest in working on it. All
> input from the list is very welcome. Please let me know what needs to be
> corrected and I will promptly do it.
> - Comment is a bit late, I will request an extra week to discuss the
> proposal with my humble excuses.
>
> BR,
> Dina Solveig Jalkanen
> --
> * * *
> Friendly geek in Amsterdam, FSFE Fellow
> https://wiki.techinc.nl/index.php/User:Thomascovenant
>
>
> _______________________________________________
> Ncuc-discuss mailing list
> Ncuc-discuss at lists.ncuc.org
> http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>
>
>
> _______________________________________________
> 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/20170804/b7831017/attachment.htm>

From icann at ferdeline.com  Sat Aug  5 00:33:30 2017
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Fri, 04 Aug 2017 17:33:30 -0400
Subject: [NCSG-PC] NCSG Comment on GNSO operating procedures change
In-Reply-To: <6a91a71d-2bed-6011-2d1a-5c743799225b@intpolicy.com>
References: <93940f3e-485d-2678-4f92-a9d85981d313@intpolicy.com>
 <aeac9647-4b76-a3bc-f199-a862597eb1c2@intpolicy.com>
 <30c249d1-c479-003c-0a82-997037d7456a@intpolicy.com>
 <8A6BC6C5-CA17-4CB3-8231-00A39DBD2287@eui.eu>
 <CAH5sThk7c-Oyj+v1Qh_=0gH5a_nN=o2yOvyrymueOxwQW7X9aA@mail.gmail.com>
 <9A97DC8E-D4E8-4110-8AE0-4AD57BCE8E4B@gmail.com>
 <6a91a71d-2bed-6011-2d1a-5c743799225b@intpolicy.com>
Message-ID: <Y7ZkjdojaSn9WDk56j-y3Vw7yEcQqwdiJRuKM37t3Lr8fosCkwhZ0xC_Hd0DirHRzyRWDKGj_KsuFtUUOkMVMvOZJxDbL5tl65EQOFMqsR8=@ferdeline.com>

Hi all,

I have made some minor alterations to style, but added nothing of substance. I hope someone with more knowledge of this issue will be able to contribute to our comment. Submissions are due in six days time. Thanks!

Best wishes, Ayden

> -------- Original Message --------
> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures change
> Local Time: August 1, 2017 5:35 PM
> UTC Time: August 1, 2017 4:35 PM
> From: matthew at intpolicy.com
> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM>
>
> Hi all
>
> Wanted to get this back at the top of the list of to-do's as time is running out.
>
> Appreciate the comments from some of the PC members but would welcome additional inputs, thoughts, etc.
>
> See google doc below.
>
> Thanks.
>
> Matthew
>
> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>
>> Matt,
>> I don?t have any comment to do, I agree with the statements and the wording. Let me know if I can do anything specific to help. Other than that you have my support. Thanks!
>> Cheers,
>> Mart?n
>>
>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
>>>
>>> Hi,
>>> the deadline for the public comment is the 10th of August, we have to finish consulting with NCSG members, review and endorsement prior to that. I suggest 8th August as our internal deadline.
>>> Best,
>>>
>>> Rafik
>>>
>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>>
>>>> Hi Matt, thanks. What's the deadline for this? I am in transit (and in fact, on holiday), witch sketchy internet access and the doc doesn't open for me today (might be the poor connection...)
>>>> Sent from my iPhone
>>>>
>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com> wrote:
>>>>
>>>>> Let me qualify the last sentence - ICANN staff are not adding new items in addition to the work of the DT, but rather adding references to work done previously.
>>>>>
>>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>
>>>>>> Calling all PCers
>>>>>>
>>>>>> I have started on the above public comment but am still going through the consultation docs. However, time marches on and we need to get this one underway.
>>>>>>
>>>>>> So, please review the consultation docs here:
>>>>>>
>>>>>> https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>>>
>>>>>> And make comments in the google doc here:
>>>>>>
>>>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit
>>>>>>
>>>>>> Note that ICANN staff have used this opportunity to include other changes that the DT did not discuss.
>>>>>> Many thanks.
>>>>>> Matthew
>>>>>>
>>>>>> --
>>>>>> Matthew Shears
>>>>>> matthew at intpolicy.com
>>>>>>
>>>>>> [+447712472987](tel:+44%207712%20472987)
>>>>>>
>>>>>> Skype:mshears
>>>>>
>>>>> --
>>>>> Matthew Shears
>>>>> matthew at intpolicy.com
>>>>>
>>>>> [+447712472987](tel:+44%207712%20472987)
>>>>>
>>>>> Skype:mshears
>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>> The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination, distribution, forwarding, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited without the express permission of the sender. If you received this communication in error, please contact the sender and delete the material from any computer.
>>>> _______________________________________________
>>>> 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
>>
>> http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient	Virus-free. [www.avg.com](http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient)
>> #DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>>
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> --
>
> Matthew Shears
> matthew at intpolicy.com
> +447712472987
> Skype:mshears
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170804/189324c0/attachment.htm>

From t.tropina at mpicc.de  Sat Aug  5 00:56:18 2017
From: t.tropina at mpicc.de (Dr. Tatiana Tropina)
Date: Fri, 4 Aug 2017 23:56:18 +0200
Subject: [NCSG-PC] Fw: [NCUC-DISCUSS] Suggested Comment: Draft Framework
 for Registry Operators to Respond to Security Threats
In-Reply-To: <CAH5sThmx08DOsLL4AbzAeyJF9-YEQLjqy0hbyZALxT5=cGr6kA@mail.gmail.com>
References: <E1dbwdr-0005N3-F2@rmmprod06.runbox>
 <viDG_GKZm4MGicRFTne3yEZERwqRoqEYGvaYOBiMDIBmcXZpK3WOzB89GoIPEZ-HorUP_hvNPo6oJg4a9RcFT5qyvmWxwgkO61QEWNen_l4=@ferdeline.com>
 <CAH5sThktSm3qRv-1UH9sOEH0R4j4G4aev73XYTE70Zvn9OgSpw@mail.gmail.com>
 <CAH5sThmx08DOsLL4AbzAeyJF9-YEQLjqy0hbyZALxT5=cGr6kA@mail.gmail.com>
Message-ID: <9814ecaf-9030-2ee6-a39e-176775c71e01@mpicc.de>

Hi all,

I have a couple of comments:

1) I have hard time making sense of the first point:

"1. Registry Response, Responsible Parties

 ?ROs are not necessarily the best parties to address certain security
threats. The identification of the parties considered as being most
relevant and appropriate in resolving the security threat is critical to
the prompt resolution of the matter.?

More specifically, responsibility of identifying security threats
connected to New gTLDs and resolving them when possible rests with ROs."

As this point is a part of the comment that refers to the "issue" I
wonder what is this - a statement? What kind of issue is identified
here? Are we recommending anything?  If not and if this is just an
introduction, may be it's better to rephrase? May be it's just too late
here but I struggling with what this "issue" implies.

2) I wonder if this one is really in line with NSCG values such as due
process:

2. We ask you to consider including the following GAC recommendation in
Registry Response:

?If Registry operator identifies risk of  harm, Registry operator will
notify the relevant registrar and , if the registrar does not take
immediate action, suspend the domain name until the matter is resolved.?

The framework already lists the actions that Registry can take even in
the case if "a negative or non-existent response from the Registrar",
which "should not
preclude the Registry from taking action". I do not like the notion of
"immediate action" as it sound to vague to me and I believe that there
are enough actions listed to address the issue under the framework
rather than suspension of domain name - again, "till the matter is
resolved" looks too vague. I don't think it's acceptable when it comes
to such a matter as a suspension of domain name. I know enough cases of
mistakes when due to abuse claims customers went dark, etc. I suggest we
rather be careful here. But if everyone is comfortable with this
suggestion, I'll surrender.

Warm regards,

Tanya



On 04/08/17 09:39, Rafik Dammak wrote:
> Dear PC members,
>
> any comment on the draft? we got an extension till 6th August, we
> should review quickly and make a decision.
>
> Best,
>
> Rafik
>
> 2017-07-31 19:33 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com
> <mailto:rafik.dammak at gmail.com>>:
>
>     Hi Ayden,
>
>     Yes it is for PC review. We worked on it the last days with Juan,
>     Dina and Niels. James cannot response since is off for the coming
>     days. I was going to send email to related ICANN staff to inform
>     that we will make a late submission, hopefully by end of this week.
>
>     Best,
>
>     Rafik 
>
>
>     On Jul 31, 2017 7:18 PM, "Ayden F?rdeline" <icann at ferdeline.com
>     <mailto:icann at ferdeline.com>> wrote:
>
>         I believe the PC is being asked to review this comment which
>         has been drafted by Dina and Juan. The submission deadline for
>         comments on this issue is today, but I suspect we will not be
>         able to meet that, so let's try for this Friday? I think we
>         need to bring in a topic expert, James Gannon (cc'd), to get
>         his opinion on this comment, too -- because I am happy to
>         raise my hand and say I do not know anything about this topic. 
>
>         Best, Ayden 
>
>
>>         -------- Original Message --------
>>         Subject: [NCUC-DISCUSS] Suggested Comment: Draft Framework
>>         for Registry Operators to Respond to Security Threats
>>         Local Time: July 30, 2017 11:24 PM
>>         UTC Time: July 30, 2017 10:24 PM
>>         From: thomascovenant at thomascovenant.org
>>         <mailto:thomascovenant at thomascovenant.org>
>>         To: NCUC-discuss <ncuc-discuss at lists.ncuc.org
>>         <mailto:ncuc-discuss at lists.ncuc.org>>
>>
>>         Hello,
>>
>>         the comment proposal is underneath, what are your thoughts?
>>
>>         https://docs.google.com/document/d/1TfgHuMqzD660_CHLQMXMW4phnBtLSP94j6X5riY2Ko4/edit
>>         <https://docs.google.com/document/d/1TfgHuMqzD660_CHLQMXMW4phnBtLSP94j6X5riY2Ko4/edit>
>>
>>         Note from Security Framework Drafting Team wiki workspace:
>>
>>         - Is Public Comment required for the draft Framework?
>>         - This is not a policy implementation nor a contractual
>>         requirements document; therefore, a public comment proceeding
>>         would not be required. However, SFDT has decided to conduct a
>>         public comment for broader community feedback prior to
>>         finalization of the Framework.
>>
>>         Main points:
>>
>>         - Framework should be expanded
>>         - Several minor details are to be clarified, restructuring
>>         proposal
>>         - as a small step in response to proposed detailed report
>>         examination, I suggest we include a recommendation on
>>         Responsible Threat Disclosure.
>>
>>         Finally, I quote Point 3 from the Comment:
>>
>>         "Since the following examination of threat report is
>>         identified in the Framework, we strongly suggest including a
>>         recommendation on Responsible Threat Disclosure to be
>>         included in the document:
>>
>>         "Each RO should scrutinize, question or otherwise inquire
>>         about the legitimacy of the origin
>>         of a request, in accordance with their own internal policies
>>         and processes."
>>
>>         We have seen a broad variation in handling security threat
>>         reports, varying from constructive actions addressing the
>>         issues to punishment of the reporting party. Benefits of
>>         responsible threat submission are obvious.
>>
>>         In this context, it is important to underline benefits and
>>         importance of responsible threat disclosure. We request
>>         recommendation to extend goodwill and not cause harm to the
>>         reporting party whenever possible:
>>
>>         When applicable, RO should provide:
>>
>>         - an easy way to report security threats and violation
>>         - encrypted ways of communication
>>         - option of anonymous submission"
>>
>>         Other:
>>
>>         - This is my first comment drafted with input from Juan
>>         Manuel Rojas (thank you for commenting). Access to shared
>>         document and request for review was given to those who
>>         expressed interest in working on it. All input from the list
>>         is very welcome. Please let me know what needs to be
>>         corrected and I will promptly do it.
>>         - Comment is a bit late, I will request an extra week to
>>         discuss the proposal with my humble excuses.
>>
>>         BR,
>>         Dina Solveig Jalkanen
>>         -- 
>>         * * *
>>         Friendly geek in Amsterdam, FSFE Fellow
>>         https://wiki.techinc.nl/index.php/User:Thomascovenant
>>         <https://wiki.techinc.nl/index.php/User:Thomascovenant>
>>
>>
>>         _______________________________________________
>>         Ncuc-discuss mailing list
>>         Ncuc-discuss at lists.ncuc.org <mailto:Ncuc-discuss at lists.ncuc.org>
>>         http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>>         <http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss>
>
>
>         _______________________________________________
>         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/20170804/663c0a16/attachment.htm>

From rafik.dammak at gmail.com  Mon Aug  7 09:07:38 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Mon, 7 Aug 2017 15:07:38 +0900
Subject: [NCSG-PC] NCSG Comment on GNSO operating procedures change
In-Reply-To: <Y7ZkjdojaSn9WDk56j-y3Vw7yEcQqwdiJRuKM37t3Lr8fosCkwhZ0xC_Hd0DirHRzyRWDKGj_KsuFtUUOkMVMvOZJxDbL5tl65EQOFMqsR8=@ferdeline.com>
References: <93940f3e-485d-2678-4f92-a9d85981d313@intpolicy.com>
 <aeac9647-4b76-a3bc-f199-a862597eb1c2@intpolicy.com>
 <30c249d1-c479-003c-0a82-997037d7456a@intpolicy.com>
 <8A6BC6C5-CA17-4CB3-8231-00A39DBD2287@eui.eu>
 <CAH5sThk7c-Oyj+v1Qh_=0gH5a_nN=o2yOvyrymueOxwQW7X9aA@mail.gmail.com>
 <9A97DC8E-D4E8-4110-8AE0-4AD57BCE8E4B@gmail.com>
 <6a91a71d-2bed-6011-2d1a-5c743799225b@intpolicy.com>
 <Y7ZkjdojaSn9WDk56j-y3Vw7yEcQqwdiJRuKM37t3Lr8fosCkwhZ0xC_Hd0DirHRzyRWDKGj_KsuFtUUOkMVMvOZJxDbL5tl65EQOFMqsR8=@ferdeline.com>
Message-ID: <CAH5sThmPjO3SpJ4bkRqA+t8UUCOu633kWOfASJyE_Ed5WBnsdA@mail.gmail.com>

Hi,

the comment is quite straightforward and supporting the changes outlined in
the public consultation.
we can have as the deadline for review and endorsement the 9th August. I
urge councilors, in particular, to review the changes since it concerns the
operating procedures.
Thanks, Matt again for the draft. I resolved the edits made by Ayden. ant
proof-reading and review would be helpful.

Best,

Rafik

2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:

> Hi all,
>
> I have made some minor alterations to style, but added nothing of
> substance. I hope someone with more knowledge of this issue will be able to
> contribute to our comment. Submissions are due in six days time. Thanks!
>
> Best wishes, Ayden
>
>
> -------- Original Message --------
> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures change
> Local Time: August 1, 2017 5:35 PM
> UTC Time: August 1, 2017 4:35 PM
> From: matthew at intpolicy.com
> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM>
>
>
> Hi all
>
> Wanted to get this back at the top of the list of to-do's as time is
> running out.
>
> Appreciate the comments from some of the PC members but would welcome
> additional inputs, thoughts, etc.
>
> See google doc below.
>
> Thanks.
>
> Matthew
>
> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>
> Matt,
> I don?t have any comment to do, I agree with the statements and the
> wording. Let me know if I can do anything specific to help. Other than that
> you have my support. Thanks!
>
> Cheers,
> Mart?n
>
> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
>
> Hi,
>
> the deadline for the public comment is the 10th of August, we have to
> finish consulting with NCSG members, review and endorsement prior to that.
> I suggest 8th August as our internal deadline.
>
> Best,
>
> Rafik
>
>
> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>
> Hi Matt, thanks. What's the deadline for this? I am in transit (and in
>> fact, on holiday), witch sketchy internet access and the doc doesn't open
>> for me today (might be the poor connection...)
>>
>> Sent from my iPhone
>>
>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com>
>> wrote:
>>
>> Let me qualify the last sentence - ICANN staff are not adding new items
>> in addition to the work of the DT, but rather adding references to work
>> done previously.
>>
>> On 25/07/2017 16:05, Matthew Shears wrote:
>>
>> Calling all PCers
>>
>> I have started on the above public comment but am still going through the
>> consultation docs.  However, time marches on and we need to get this one
>> underway.
>>
>> So, please review the consultation docs here:
>>
>> https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>
>> And make comments in the google doc here:
>>
>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>> -ddk_Q9DWja7bZIgsiY/edit
>> Note that ICANN staff have used this opportunity to include other changes
>> that the DT did not discuss.
>>
>> Many thanks.
>>
>> Matthew
>>
>>
>>
>> --
>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>
>>
>> --
>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>>
>>
>> The information transmitted is intended only for the person or entity to
>> which it is addressed and may contain confidential and/or privileged
>> material. Any review, retransmission, dissemination, distribution,
>> forwarding, or other use of, or taking of any action in reliance upon, this
>> information by persons or entities other than the intended recipient is
>> prohibited without the express permission of the sender. If you received
>> this communication in error, please contact the sender and delete the
>> material from any computer.
>>
>> _______________________________________________
>> 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
>
>
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> Virus-free. www.avg.com
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> <#m_2944817719784776093_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
> _______________________________________________
> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
> --
>
>
> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>
>
>
> _______________________________________________
> 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/20170807/07026bf5/attachment.htm>

From pileleji at ymca.gm  Mon Aug  7 13:50:29 2017
From: pileleji at ymca.gm (Poncelet Ileleji)
Date: Mon, 7 Aug 2017 10:50:29 +0000
Subject: [NCSG-PC] NCSG Comment on GNSO operating procedures change
In-Reply-To: <CAH5sThmPjO3SpJ4bkRqA+t8UUCOu633kWOfASJyE_Ed5WBnsdA@mail.gmail.com>
References: <93940f3e-485d-2678-4f92-a9d85981d313@intpolicy.com>
 <aeac9647-4b76-a3bc-f199-a862597eb1c2@intpolicy.com>
 <30c249d1-c479-003c-0a82-997037d7456a@intpolicy.com>
 <8A6BC6C5-CA17-4CB3-8231-00A39DBD2287@eui.eu>
 <CAH5sThk7c-Oyj+v1Qh_=0gH5a_nN=o2yOvyrymueOxwQW7X9aA@mail.gmail.com>
 <9A97DC8E-D4E8-4110-8AE0-4AD57BCE8E4B@gmail.com>
 <6a91a71d-2bed-6011-2d1a-5c743799225b@intpolicy.com>
 <Y7ZkjdojaSn9WDk56j-y3Vw7yEcQqwdiJRuKM37t3Lr8fosCkwhZ0xC_Hd0DirHRzyRWDKGj_KsuFtUUOkMVMvOZJxDbL5tl65EQOFMqsR8=@ferdeline.com>
 <CAH5sThmPjO3SpJ4bkRqA+t8UUCOu633kWOfASJyE_Ed5WBnsdA@mail.gmail.com>
Message-ID: <CAEux40s_XvNdQfR6K+bLBjMzJ76iwq1guL87JG5DaMfecxgwig@mail.gmail.com>

Hi Rafik,

Good day, having gone through the review changes, I endorse but I also
concur our councilors should to take a lead on this as their inputs will be
very valuable on this.

Kind Regards

Poncelet

On 7 August 2017 at 06:07, Rafik Dammak <rafik.dammak at gmail.com> wrote:

> Hi,
>
> the comment is quite straightforward and supporting the changes outlined
> in the public consultation.
> we can have as the deadline for review and endorsement the 9th August. I
> urge councilors, in particular, to review the changes since it concerns the
> operating procedures.
> Thanks, Matt again for the draft. I resolved the edits made by Ayden. ant
> proof-reading and review would be helpful.
>
> Best,
>
> Rafik
>
>
> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>
>> Hi all,
>>
>> I have made some minor alterations to style, but added nothing of
>> substance. I hope someone with more knowledge of this issue will be able to
>> contribute to our comment. Submissions are due in six days time. Thanks!
>>
>> Best wishes, Ayden
>>
>>
>> -------- Original Message --------
>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures change
>> Local Time: August 1, 2017 5:35 PM
>> UTC Time: August 1, 2017 4:35 PM
>> From: matthew at intpolicy.com
>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM>
>>
>>
>> Hi all
>>
>> Wanted to get this back at the top of the list of to-do's as time is
>> running out.
>>
>> Appreciate the comments from some of the PC members but would welcome
>> additional inputs, thoughts, etc.
>>
>> See google doc below.
>>
>> Thanks.
>>
>> Matthew
>>
>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>
>> Matt,
>> I don?t have any comment to do, I agree with the statements and the
>> wording. Let me know if I can do anything specific to help. Other than that
>> you have my support. Thanks!
>>
>> Cheers,
>> Mart?n
>>
>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
>>
>> Hi,
>>
>> the deadline for the public comment is the 10th of August, we have to
>> finish consulting with NCSG members, review and endorsement prior to that.
>> I suggest 8th August as our internal deadline.
>>
>> Best,
>>
>> Rafik
>>
>>
>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>
>> Hi Matt, thanks. What's the deadline for this? I am in transit (and in
>>> fact, on holiday), witch sketchy internet access and the doc doesn't open
>>> for me today (might be the poor connection...)
>>>
>>> Sent from my iPhone
>>>
>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com>
>>> wrote:
>>>
>>> Let me qualify the last sentence - ICANN staff are not adding new items
>>> in addition to the work of the DT, but rather adding references to work
>>> done previously.
>>>
>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>
>>> Calling all PCers
>>>
>>> I have started on the above public comment but am still going through
>>> the consultation docs.  However, time marches on and we need to get this
>>> one underway.
>>>
>>> So, please review the consultation docs here:
>>>
>>> https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>
>>> And make comments in the google doc here:
>>>
>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>> -ddk_Q9DWja7bZIgsiY/edit
>>> Note that ICANN staff have used this opportunity to include other
>>> changes that the DT did not discuss.
>>>
>>> Many thanks.
>>>
>>> Matthew
>>>
>>>
>>>
>>> --
>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>
>>>
>>> --
>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>>
>>>
>>> The information transmitted is intended only for the person or entity to
>>> which it is addressed and may contain confidential and/or privileged
>>> material. Any review, retransmission, dissemination, distribution,
>>> forwarding, or other use of, or taking of any action in reliance upon, this
>>> information by persons or entities other than the intended recipient is
>>> prohibited without the express permission of the sender. If you received
>>> this communication in error, please contact the sender and delete the
>>> material from any computer.
>>>
>>> _______________________________________________
>>> 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
>>
>>
>>
>>
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>> Virus-free. www.avg.com
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>
>> <#m_-7773621495840534939_m_2944817719784776093_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>>
>> _______________________________________________
>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>>
>> --
>>
>>
>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>
>>
>>
>> _______________________________________________
>> 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/20170807/a65f4ec0/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Mon Aug  7 15:41:38 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Mon, 7 Aug 2017 08:41:38 -0400
Subject: [NCSG-PC] NCSG Comment on GNSO operating procedures change
In-Reply-To: <CAH5sThmPjO3SpJ4bkRqA+t8UUCOu633kWOfASJyE_Ed5WBnsdA@mail.gmail.com>
References: <93940f3e-485d-2678-4f92-a9d85981d313@intpolicy.com>
 <aeac9647-4b76-a3bc-f199-a862597eb1c2@intpolicy.com>
 <30c249d1-c479-003c-0a82-997037d7456a@intpolicy.com>
 <8A6BC6C5-CA17-4CB3-8231-00A39DBD2287@eui.eu>
 <CAH5sThk7c-Oyj+v1Qh_=0gH5a_nN=o2yOvyrymueOxwQW7X9aA@mail.gmail.com>
 <9A97DC8E-D4E8-4110-8AE0-4AD57BCE8E4B@gmail.com>
 <6a91a71d-2bed-6011-2d1a-5c743799225b@intpolicy.com>
 <Y7ZkjdojaSn9WDk56j-y3Vw7yEcQqwdiJRuKM37t3Lr8fosCkwhZ0xC_Hd0DirHRzyRWDKGj_KsuFtUUOkMVMvOZJxDbL5tl65EQOFMqsR8=@ferdeline.com>
 <CAH5sThmPjO3SpJ4bkRqA+t8UUCOu633kWOfASJyE_Ed5WBnsdA@mail.gmail.com>
Message-ID: <1e15d66a-e0eb-381f-cdf7-2d4b59236e8d@mail.utoronto.ca>

It looks fine to me. I don't have knowledge of or time to do the 
research on the issues at the moment, so I hope that those who do can 
catch things that need changes.

cheers Stephanie


On 2017-08-07 02:07, Rafik Dammak wrote:
> Hi,
>
> the comment is quite straightforward and supporting the changes 
> outlined in the public consultation.
> we can have as the deadline for review and endorsement the 9th August. 
> I urge councilors, in particular, to review the changes since it 
> concerns the operating procedures.
> Thanks, Matt again for the draft. I resolved the edits made by Ayden. 
> ant proof-reading and review would be helpful.
>
> Best,
>
> Rafik
>
> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com 
> <mailto:icann at ferdeline.com>>:
>
>     Hi all,
>
>     I have made some minor alterations to style, but added nothing of
>     substance. I hope someone with more knowledge of this issue will
>     be able to contribute to our comment. Submissions are due in six
>     days time. Thanks!
>
>     Best wishes, Ayden
>
>
>>     -------- Original Message --------
>>     Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures
>>     change
>>     Local Time: August 1, 2017 5:35 PM
>>     UTC Time: August 1, 2017 4:35 PM
>>     From: matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>     To: ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>,
>>     farzaneh badii <farzaneh.badii at GMAIL.COM
>>     <mailto:farzaneh.badii at GMAIL.COM>>
>>
>>
>>     Hi all
>>
>>     Wanted to get this back at the top of the list of to-do's as time
>>     is running out.
>>
>>     Appreciate the comments from some of the PC members but would
>>     welcome additional inputs, thoughts, etc.
>>
>>     See google doc below.
>>
>>     Thanks.
>>
>>     Matthew
>>
>>
>>     On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>     Matt,
>>>     I don?t have any comment to do, I agree with the statements and
>>>     the wording. Let me know if I can do anything specific to help.
>>>     Other than that you have my support. Thanks!
>>>
>>>     Cheers,
>>>     Mart?n
>>>
>>>>     On Jul 25, 2017, at 8:22 PM, Rafik Dammak
>>>>     <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>> wrote:
>>>>
>>>>     Hi,
>>>>
>>>>     the deadline for the public comment is the 10th of August, we
>>>>     have to finish consulting with NCSG members, review and
>>>>     endorsement prior to that. I suggest 8th August as our internal
>>>>     deadline.
>>>>
>>>>     Best,
>>>>
>>>>     Rafik
>>>>
>>>>
>>>>     2017-07-25 23:28 GMT+09:00 Stefania Milan
>>>>     <stefania.milan at eui.eu <mailto:stefania.milan at eui.eu>>:
>>>>
>>>>         Hi Matt, thanks. What's the deadline for this? I am in
>>>>         transit (and in fact, on holiday), witch sketchy internet
>>>>         access and the doc doesn't open for me today (might be the
>>>>         poor connection...)
>>>>
>>>>         Sent from my iPhone
>>>>
>>>>         On Jul 25, 2017, at 9:17 AM, Matthew Shears
>>>>         <matthew at intpolicy.com <mailto:matthew at intpolicy.com>> wrote:
>>>>
>>>>>         Let me qualify the last sentence - ICANN staff are not
>>>>>         adding new items in addition to the work of the DT, but
>>>>>         rather adding references to work done previously.
>>>>>
>>>>>
>>>>>         On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>         Calling all PCers
>>>>>>
>>>>>>         I have started on the above public comment but am still
>>>>>>         going through the consultation docs.  However, time
>>>>>>         marches on and we need to get this one underway.
>>>>>>
>>>>>>         So, please review the consultation docs here:
>>>>>>
>>>>>>         https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>>>         <https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en>
>>>>>>
>>>>>>         And make comments in the google doc here:
>>>>>>
>>>>>>         https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit
>>>>>>         <https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit>
>>>>>>
>>>>>>         Note that ICANN staff have used this opportunity to
>>>>>>         include other changes that the DT did not discuss.
>>>>>>
>>>>>>         Many thanks.
>>>>>>
>>>>>>         Matthew
>>>>>>
>>>>>>
>>>>>>
>>>>>>         -- 
>>>>>>         Matthew Shears
>>>>>>         matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>>>>         +447712472987 <tel:+44%207712%20472987>
>>>>>>         Skype:mshears
>>>>>
>>>>>         -- 
>>>>>         Matthew Shears
>>>>>         matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>>>         +447712472987 <tel:+44%207712%20472987>
>>>>>         Skype:mshears
>>>>>         _______________________________________________
>>>>>         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>
>>>>
>>>>
>>>>         The information transmitted is intended only for the person
>>>>         or entity to which it is addressed and may contain
>>>>         confidential and/or privileged material. Any review,
>>>>         retransmission, dissemination, distribution, forwarding, or
>>>>         other use of, or taking of any action in reliance upon,
>>>>         this information by persons or entities other than the
>>>>         intended recipient is prohibited without the express
>>>>         permission of the sender. If you received this
>>>>         communication in error, please contact the sender and
>>>>         delete the material from any computer.
>>>>
>>>>
>>>>         _______________________________________________
>>>>         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>
>>>
>>>
>>>     <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>     	Virus-free. www.avg.com
>>>     <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>
>>>
>>>
>>>
>>>     _______________________________________________
>>>     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>
>>>
>>
>>     -- 
>>
>>
>>     Matthew Shears
>>     matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>     +447712472987 <tel:+44%207712%20472987>
>>     Skype:mshears
>
>
>     _______________________________________________
>     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/20170807/7f69e54e/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Mon Aug  7 15:46:43 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Mon, 7 Aug 2017 08:46:43 -0400
Subject: [NCSG-PC] Fwd: Re: [council] Action Items: GNSO Council meeting 13
	July 2017
In-Reply-To: <CADWyk6xtZEdsyuTwGMBDTzPSyN3iRCMWVhkmZT_gK_x-4jKOSQ@mail.gmail.com>
References: <CADWyk6xtZEdsyuTwGMBDTzPSyN3iRCMWVhkmZT_gK_x-4jKOSQ@mail.gmail.com>
Message-ID: <93b25b52-2f9d-647d-bb57-c210a59034cc@mail.utoronto.ca>

Just checking, have we submitted our proposal for the IG item (see 
bolded bit below item 7) to the GNSO list?  Deadline looming....

cheers SP



-------- Forwarded Message --------
Subject: 	Re: [council] Action Items: GNSO Council meeting 13 July 2017
Date: 	Mon, 7 Aug 2017 13:18:38 +1000
From: 	Heather Forrest <haforrestesq at gmail.com>
To: 	James M. Bladel <jbladel at godaddy.com>, council at gnso.icann.org 
<council at gnso.icann.org>, Jeff Neuman <jeff.neuman at comlaude.com>, 
avri at apc.org
CC: 	gnso-secs at icann.org <gnso-secs at icann.org>



Dear colleagues,

Just following up on the point made by James on 18 July about whether or 
not to put the CWG-UCTN Final Report on our August agenda, or hold it to 
September's agenda. FYI the following has taken place since 18 July:

  * ccNSO Council has voted on and approved the CWG-UCTN Final Report
  * SubPro is in the process of creating Work Track 5 on geo names

As a co-chair of this CWG, my personal view is that the GNSO can endorse 
the Final Report, but should make comments in the motion pointing to 
SubPro and the new WT5. In my view, the timing of such a motion (and how 
forcefully we make our comments about WT5) is dependent upon SubPro - 
let's put this on Council's agenda at a time most helpful to SubPro and 
WT5. With that in mind, I suggest we take some guidance from Jeff and 
Avri here.

I note that our document deadline for August meeting is in roughly 7 
days, so we need time to pull together a motion if this is going onto 
the August agenda.

Best wishes,

Heather

On Tue, Jul 18, 2017 at 10:17 AM, James M. Bladel <jbladel at godaddy.com 
<mailto:jbladel at godaddy.com>> wrote:

    Thank you, Nathalie.

    Council Colleagues, a few semi-random thoughts on the items below:

    #6. We have a small team working on the GNSO Response to the GAC's
    Johannesburg communique. Expect final draft language this week, with
    approval via email ballot to follow. The goal is to provide our
    response to the Board in advance of their meeting with the GAC in
    mid-August.

    *#7. CCWG-IG - Please note that this item was **_deferred_**, rather
    than withdrawn. This means that it will appear on our next meeting's
    ballot for a vote. I know that some folks wanted to submit
    amendments, and I urge that these be posted to the Council list by
    the next document deadline (14 AUG), or the motion will head to a
    vote un-amended.**
    ***
    #8. This discussion item has been rescheduled for two subsequent
    meetings, so I'm hopeful that we will give it full consideration
    during our next meeting. I recommend we move it to the top of our
    non-voting agenda.

    #9. Because this item is related to other ongoing activities,
    including follow-up from the GeoNames sessions in Johannesburg and
    the formation of SubPro Work Track 5, a motion for a vote may or may
    not appear on our August agenda. Stay tuned for further developments.

    Thank you,

    J.
    -----------------
    James Bladel
    GNSO Chair

    On Jul 17, 2017, 16:50 -0500, Nathalie Peregrine
    <nathalie.peregrine at icann.org
    <mailto:nathalie.peregrine at icann.org>>, wrote:
>
>     Dear Councilors,
>
>     Please find the action items as stated during the meeting, below
>     and as attachment arising from the GNSO Council meeting held on
>     Thursday 13 July 2017.  Please take note of the action items
>     coming out of the Council sessions and the proposed timing for
>     delivering on these actions.
>
>     *ACTION ITEMS GNSO COUNCIL MEETING 13 July 2017*
>
>     *_Item 3. Consent Agenda - Appointment of James Bladel as the GNSO
>     Representative to the Empowered Community_*
>
>       * the GNSO Secretariat to communicate this decision to the ICANN
>         Secretary which will serve as the required written
>         certification from the GNSO Chair designating the individual
>         who shall represent the Decisional Participant on the EC
>         Administration.
>
>     *__*
>
>     *_Item 4: COUNCIL VOTE ? Proposed Fundamental Bylaw Changes_*
>
>       * GNSO Secretariat to forward the adopted resolution to the
>         Empowered Community Administration before the expiration of
>         the Approval Action Decision Period, as required under Section
>         1.4, Article 1, Annex D of the ICANN Bylaws.
>       * James Bladel, the GNSO?s representative to the Empowered
>         Community Administration, to coordinate with the other four
>         Decisional Participant representatives to ensure that the
>         Empowered Community Administration observes and completes the
>         appropriate process outlined in Section 1.4(b) and (c), Annex D.
>
>     *__*
>
>     *_Item 6. COUNCIL VOTE ? Approval of GNSO Council Review of the
>     GAC Communique from Johannesburg_*
>
>       * Volunteers to revise response to GAC Communique and circulate
>         revised draft to the Council as soon as possible. Volunteers
>         include: Paul, James, Jeff Neuman (if allowed), Rubens,
>         Heather (sanity check), Phil, Darcy, possibly Stephanie (to
>         convey Avri?s views), and Carlos. Volunteers to consider input
>         received in relation to Geo Names section as well as IGO
>         section, including offering the opportunity to detail IGO/INGO
>         CRP recommendations with the ICANN Board prior to a vote being
>         taken to provide details how small group, IGO comments
>         factored into Final Report and recommendations.
>       * GNSO Leadership to provide 7-day notice of e-vote to approve
>         response to GAC Communique
>
>     *__*
>
>     *_Item 7: COUNCIL Vote ? Next steps in relation to Charter for the
>     Cross Community Working Group on Internet Governance_*
>
>       * Motion deferred -  GNSO leadership to add this item to the
>         Council agenda for August meeting.
>       * All Council members to provide input and proposed amendments
>         to the motions as soon as possible so that discussion can
>         continue on the mailing list ahead of the meeting.
>
>     *__*
>
>     *_Item 8. COUNCIL DISCUSSION ? Possible Change to the Name of the
>     GNSO_*
>
>       * Item deferred ? GNSO Council leadership to add this item to
>         the Council agenda for August meeting.
>
>     *__*
>
>     *_Item 9: COUNCIL DISCUSSION ? Cross Community Working Group on
>     the Use of Country and Territory Names_*
>
>       * Council members to consider drafting Motion for August meeting
>         on this topic.
>       * Ben Fuller to solicit input from ccNSO on this topic and
>         provide feedback to the GNSO Council
>
>     *__*
>
>     Please note that all Action Items have been posted on the Action
>     Item wiki page here[community.icann.org]
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_RgZlAg&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=3Tc6XSN5n8FryvXrAqUdyp0sa6kuAUqPfvvw4f3uwKQ&s=4DEDZ2Meg9ZUFIObabj6BRFzEywMdXPo7au4Kd0LSJI&e=>.
>     Please refer to this page for the recent status updates on the
>     Action items.
>
>     Thank you,
>
>     Kind regards,
>
>     Nathalie
>
>     -- 
>
>     Nathalie Peregrine
>
>     Specialist, SOAC Support (GNSO)
>
>     Internet Corporation for Assigned Names and Numbers (ICANN)
>
>     Email: nathalie.peregrine at icann.org
>     <http://nathalie.peregrine at icann.org%20>
>
>     Skype: nathalie.peregrine.icann
>
>     Find out more about the GNSO by taking our interactive courses
>     <http://learn.icann.org/courses/gnso> and visiting the GNSO
>     Newcomer pages[gnso.icann.org]
>     <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DgMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=YXXgWMx7AnEsK0bIjCRJ20RWD6FrJ7eshz4ee3BoCuw&s=z012pgyZrR1-Hdltx67AUtBaeooNRaHBDVfbgPe9pt8&e=>
>

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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170807/383b5b1c/attachment.htm>
-------------- next part --------------
_______________________________________________
council mailing list
council at gnso.icann.org
https://mm.icann.org/mailman/listinfo/council


From farzaneh.badii at gmail.com  Mon Aug  7 15:49:29 2017
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Mon, 7 Aug 2017 08:49:29 -0400
Subject: [NCSG-PC] NCSG Comment on GNSO operating procedures change
In-Reply-To: <1e15d66a-e0eb-381f-cdf7-2d4b59236e8d@mail.utoronto.ca>
References: <93940f3e-485d-2678-4f92-a9d85981d313@intpolicy.com>
 <aeac9647-4b76-a3bc-f199-a862597eb1c2@intpolicy.com>
 <30c249d1-c479-003c-0a82-997037d7456a@intpolicy.com>
 <8A6BC6C5-CA17-4CB3-8231-00A39DBD2287@eui.eu>
 <CAH5sThk7c-Oyj+v1Qh_=0gH5a_nN=o2yOvyrymueOxwQW7X9aA@mail.gmail.com>
 <9A97DC8E-D4E8-4110-8AE0-4AD57BCE8E4B@gmail.com>
 <6a91a71d-2bed-6011-2d1a-5c743799225b@intpolicy.com>
 <Y7ZkjdojaSn9WDk56j-y3Vw7yEcQqwdiJRuKM37t3Lr8fosCkwhZ0xC_Hd0DirHRzyRWDKGj_KsuFtUUOkMVMvOZJxDbL5tl65EQOFMqsR8=@ferdeline.com>
 <CAH5sThmPjO3SpJ4bkRqA+t8UUCOu633kWOfASJyE_Ed5WBnsdA@mail.gmail.com>
 <1e15d66a-e0eb-381f-cdf7-2d4b59236e8d@mail.utoronto.ca>
Message-ID: <CAN1qJvBx5ORLkH8XjM1Fi2qW6mw_CkmBDZDMe5YTakrQFRv8Kw@mail.gmail.com>

Hi

I was on the DT group. I don't have the time to go through every single
change and see if they accord with what we agreed on. If you want in the
public comment we should ask that if later on during implementing the
operating procedures we find out that  changes recommended by  DT   for
some reason are not reflected in the new  GNSO operating procedures, GNSO
should follow the DT advice in those circumstances and allow for the
mistake to be corrected.

Farzaneh

On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> wrote:

> It looks fine to me.  I don't have knowledge of or time to do the research
> on the issues at the moment, so I hope that those who do can catch things
> that need changes.
>
> cheers Stephanie
>
> On 2017-08-07 02:07, Rafik Dammak wrote:
>
> Hi,
>
> the comment is quite straightforward and supporting the changes outlined
> in the public consultation.
> we can have as the deadline for review and endorsement the 9th August. I
> urge councilors, in particular, to review the changes since it concerns the
> operating procedures.
> Thanks, Matt again for the draft. I resolved the edits made by Ayden. ant
> proof-reading and review would be helpful.
>
> Best,
>
> Rafik
>
> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>
>> Hi all,
>>
>> I have made some minor alterations to style, but added nothing of
>> substance. I hope someone with more knowledge of this issue will be able to
>> contribute to our comment. Submissions are due in six days time. Thanks!
>>
>> Best wishes, Ayden
>>
>>
>> -------- Original Message --------
>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures change
>> Local Time: August 1, 2017 5:35 PM
>> UTC Time: August 1, 2017 4:35 PM
>> From: matthew at intpolicy.com
>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM>
>>
>>
>> Hi all
>>
>> Wanted to get this back at the top of the list of to-do's as time is
>> running out.
>>
>> Appreciate the comments from some of the PC members but would welcome
>> additional inputs, thoughts, etc.
>>
>> See google doc below.
>>
>> Thanks.
>>
>> Matthew
>>
>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>
>> Matt,
>> I don?t have any comment to do, I agree with the statements and the
>> wording. Let me know if I can do anything specific to help. Other than that
>> you have my support. Thanks!
>>
>> Cheers,
>> Mart?n
>>
>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
>>
>> Hi,
>>
>> the deadline for the public comment is the 10th of August, we have to
>> finish consulting with NCSG members, review and endorsement prior to that.
>> I suggest 8th August as our internal deadline.
>>
>> Best,
>>
>> Rafik
>>
>>
>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>
>> Hi Matt, thanks. What's the deadline for this? I am in transit (and in
>>> fact, on holiday), witch sketchy internet access and the doc doesn't open
>>> for me today (might be the poor connection...)
>>>
>>> Sent from my iPhone
>>>
>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com>
>>> wrote:
>>>
>>> Let me qualify the last sentence - ICANN staff are not adding new items
>>> in addition to the work of the DT, but rather adding references to work
>>> done previously.
>>>
>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>
>>> Calling all PCers
>>>
>>> I have started on the above public comment but am still going through
>>> the consultation docs.  However, time marches on and we need to get this
>>> one underway.
>>>
>>> So, please review the consultation docs here:
>>>
>>> https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>
>>> And make comments in the google doc here:
>>>
>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>> -ddk_Q9DWja7bZIgsiY/edit
>>> Note that ICANN staff have used this opportunity to include other
>>> changes that the DT did not discuss.
>>>
>>> Many thanks.
>>>
>>> Matthew
>>>
>>>
>>>
>>> --
>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>
>>>
>>> --
>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>>
>>>
>>> The information transmitted is intended only for the person or entity to
>>> which it is addressed and may contain confidential and/or privileged
>>> material. Any review, retransmission, dissemination, distribution,
>>> forwarding, or other use of, or taking of any action in reliance upon, this
>>> information by persons or entities other than the intended recipient is
>>> prohibited without the express permission of the sender. If you received
>>> this communication in error, please contact the sender and delete the
>>> material from any computer.
>>>
>>> _______________________________________________
>>> 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
>>
>>
>>
>>
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>> Virus-free. www.avg.com
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>
>>
>>
>> _______________________________________________
>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>>
>> --
>>
>>
>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>
>>
>>
>> _______________________________________________
>> 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 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/20170807/aaf940a1/attachment.htm>

From rafik.dammak at gmail.com  Mon Aug  7 15:50:55 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Mon, 7 Aug 2017 21:50:55 +0900
Subject: [NCSG-PC] Fwd: Re: [council] Action Items: GNSO Council meeting
 13 July 2017
In-Reply-To: <93b25b52-2f9d-647d-bb57-c210a59034cc@mail.utoronto.ca>
References: <CADWyk6xtZEdsyuTwGMBDTzPSyN3iRCMWVhkmZT_gK_x-4jKOSQ@mail.gmail.com>
 <93b25b52-2f9d-647d-bb57-c210a59034cc@mail.utoronto.ca>
Message-ID: <CAH5sThnEzR7i7hZDiqvZz_xb8AzKnPOALH5sWVPXxANE0KqnFw@mail.gmail.com>

Hi Stephanie,

I shared the proposed amendments in this list just after the last call but
I didn't get any comment
https://lists.ncsg.is/pipermail/ncsg-pc/2017-July/000737.html.
no, we didn't submit the amendments to the council.

Best,

Rafik

2017-08-07 21:46 GMT+09:00 Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca>:

> Just checking, have we submitted our proposal for the IG item (see bolded
> bit below item 7) to the GNSO list?  Deadline looming....
>
> cheers SP
>
>
> -------- Forwarded Message --------
> Subject: Re: [council] Action Items: GNSO Council meeting 13 July 2017
> Date: Mon, 7 Aug 2017 13:18:38 +1000
> From: Heather Forrest <haforrestesq at gmail.com> <haforrestesq at gmail.com>
> To: James M. Bladel <jbladel at godaddy.com> <jbladel at godaddy.com>,
> council at gnso.icann.org <council at gnso.icann.org> <council at gnso.icann.org>,
> Jeff Neuman <jeff.neuman at comlaude.com> <jeff.neuman at comlaude.com>,
> avri at apc.org
> CC: gnso-secs at icann.org <gnso-secs at icann.org> <gnso-secs at icann.org>
>
>
> Dear colleagues,
>
> Just following up on the point made by James on 18 July about whether or
> not to put the CWG-UCTN Final Report on our August agenda, or hold it to
> September's agenda. FYI the following has taken place since 18 July:
>
>    - ccNSO Council has voted on and approved the CWG-UCTN Final Report
>    - SubPro is in the process of creating Work Track 5 on geo names
>
> As a co-chair of this CWG, my personal view is that the GNSO can endorse
> the Final Report, but should make comments in the motion pointing to SubPro
> and the new WT5. In my view, the timing of such a motion (and how
> forcefully we make our comments about WT5) is dependent upon SubPro - let's
> put this on Council's agenda at a time most helpful to SubPro and WT5. With
> that in mind, I suggest we take some guidance from Jeff and Avri here.
>
> I note that our document deadline for August meeting is in roughly 7 days,
> so we need time to pull together a motion if this is going onto the August
> agenda.
>
> Best wishes,
>
> Heather
>
> On Tue, Jul 18, 2017 at 10:17 AM, James M. Bladel <jbladel at godaddy.com>
> wrote:
>
>> Thank you, Nathalie.
>>
>> Council Colleagues, a few semi-random thoughts on the items below:
>>
>> #6. We have a small team working on the GNSO Response to the GAC's
>> Johannesburg communique. Expect final draft language this week, with
>> approval via email ballot to follow. The goal is to provide our response to
>> the Board in advance of their meeting with the GAC in mid-August.
>>
>> *#7. CCWG-IG - Please note that this item was **deferred**, rather than
>> withdrawn. This means that it will appear on our next meeting's ballot for
>> a vote. I know that some folks wanted to submit amendments, and I urge that
>> these be posted to the Council list by the next document deadline (14 AUG),
>> or the motion will head to a vote un-amended.*
>>
>> #8. This discussion item has been rescheduled for two subsequent
>> meetings, so I'm hopeful that we will give it full consideration during our
>> next meeting. I recommend we move it to the top of our non-voting agenda.
>>
>> #9. Because this item is related to other ongoing activities, including
>> follow-up from the GeoNames sessions in Johannesburg and the formation of
>> SubPro Work Track 5, a motion for a vote may or may not appear on our
>> August agenda. Stay tuned for further developments.
>>
>> Thank you,
>>
>> J.
>> -----------------
>> James Bladel
>> GNSO Chair
>>
>> On Jul 17, 2017, 16:50 -0500, Nathalie Peregrine <
>> nathalie.peregrine at icann.org>, wrote:
>>
>> Dear Councilors,
>>
>>
>>
>> Please find the action items as stated during the meeting, below and as
>> attachment arising from the GNSO Council meeting held on Thursday 13 July
>> 2017.  Please take note of the action items coming out of the Council
>> sessions and the proposed timing for delivering on these actions.
>>
>>
>>
>> *ACTION ITEMS GNSO COUNCIL MEETING 13 July 2017*
>>
>>
>>
>> *Item 3. Consent Agenda - Appointment of James Bladel as the GNSO
>> Representative to the Empowered Community*
>>
>>    - the GNSO Secretariat to communicate this decision to the ICANN
>>    Secretary which will serve as the required written certification from the
>>    GNSO Chair designating the individual who shall represent the Decisional
>>    Participant on the EC Administration.
>>
>>
>>
>> *Item 4: COUNCIL VOTE ? Proposed Fundamental Bylaw Changes*
>>
>>    - GNSO Secretariat to forward the adopted resolution to the Empowered
>>    Community Administration before the expiration of the Approval Action
>>    Decision Period, as required under Section 1.4, Article 1, Annex D of the
>>    ICANN Bylaws.
>>    - James Bladel, the GNSO?s representative to the Empowered Community
>>    Administration, to coordinate with the other four Decisional Participant
>>    representatives to ensure that the Empowered Community Administration
>>    observes and completes the appropriate process outlined in Section 1.4(b)
>>    and (c), Annex D.
>>
>>
>>
>> *Item 6. COUNCIL VOTE ? Approval of GNSO Council Review of the GAC
>> Communique from Johannesburg*
>>
>>    - Volunteers to revise response to GAC Communique and circulate
>>    revised draft to the Council as soon as possible. Volunteers include: Paul,
>>    James, Jeff Neuman (if allowed), Rubens, Heather (sanity check), Phil,
>>    Darcy, possibly Stephanie (to convey Avri?s views), and Carlos. Volunteers
>>    to consider input received in relation to Geo Names section as well as IGO
>>    section, including offering the opportunity to detail IGO/INGO CRP
>>    recommendations with the ICANN Board prior to a vote being taken to provide
>>    details how small group, IGO comments factored into Final Report and
>>    recommendations.
>>    - GNSO Leadership to provide 7-day notice of e-vote to approve
>>    response to GAC Communique
>>
>>
>>
>> *Item 7: COUNCIL Vote ? Next steps in relation to Charter for the Cross
>> Community Working Group on Internet Governance*
>>
>>    - Motion deferred -  GNSO leadership to add this item to the Council
>>    agenda for August meeting.
>>    - All Council members to provide input and proposed amendments to the
>>    motions as soon as possible so that discussion can continue on the mailing
>>    list ahead of the meeting.
>>
>>
>>
>> *Item 8. COUNCIL DISCUSSION ? Possible Change to the Name of the GNSO*
>>
>>    - Item deferred ? GNSO Council leadership to add this item to the
>>    Council agenda for August meeting.
>>
>>
>>
>> *Item 9: COUNCIL DISCUSSION ? Cross Community Working Group on the Use of
>> Country and Territory Names*
>>
>>    - Council members to consider drafting Motion for August meeting on
>>    this topic.
>>    - Ben Fuller to solicit input from ccNSO on this topic and provide
>>    feedback to the GNSO Council
>>
>>
>>
>> Please note that all Action Items have been posted on the Action Item
>> wiki page here[community.icann.org]
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_RgZlAg&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=3Tc6XSN5n8FryvXrAqUdyp0sa6kuAUqPfvvw4f3uwKQ&s=4DEDZ2Meg9ZUFIObabj6BRFzEywMdXPo7au4Kd0LSJI&e=>.
>> Please refer to this page for the recent status updates on the Action items.
>>
>>
>>
>> Thank you,
>>
>>
>>
>> Kind regards,
>>
>>
>>
>> Nathalie
>>
>> --
>>
>>
>>
>> Nathalie Peregrine
>>
>> Specialist, SOAC Support (GNSO)
>>
>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>
>> Email: nathalie.peregrine at icann.org
>> <http://nathalie.peregrine at icann.org%20>
>>
>> Skype: nathalie.peregrine.icann
>>
>>
>>
>> Find out more about the GNSO by taking our interactive courses
>> <http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer
>> pages[gnso.icann.org]
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DgMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=YXXgWMx7AnEsK0bIjCRJ20RWD6FrJ7eshz4ee3BoCuw&s=z012pgyZrR1-Hdltx67AUtBaeooNRaHBDVfbgPe9pt8&e=>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> council mailing list
>> council at gnso.icann.org
>> https://mm.icann.org/mailman/listinfo/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/20170807/4e490cf6/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Mon Aug  7 17:24:12 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Mon, 7 Aug 2017 10:24:12 -0400
Subject: [NCSG-PC] NCSG Comment on GNSO operating procedures change
In-Reply-To: <CAN1qJvBx5ORLkH8XjM1Fi2qW6mw_CkmBDZDMe5YTakrQFRv8Kw@mail.gmail.com>
References: <93940f3e-485d-2678-4f92-a9d85981d313@intpolicy.com>
 <aeac9647-4b76-a3bc-f199-a862597eb1c2@intpolicy.com>
 <30c249d1-c479-003c-0a82-997037d7456a@intpolicy.com>
 <8A6BC6C5-CA17-4CB3-8231-00A39DBD2287@eui.eu>
 <CAH5sThk7c-Oyj+v1Qh_=0gH5a_nN=o2yOvyrymueOxwQW7X9aA@mail.gmail.com>
 <9A97DC8E-D4E8-4110-8AE0-4AD57BCE8E4B@gmail.com>
 <6a91a71d-2bed-6011-2d1a-5c743799225b@intpolicy.com>
 <Y7ZkjdojaSn9WDk56j-y3Vw7yEcQqwdiJRuKM37t3Lr8fosCkwhZ0xC_Hd0DirHRzyRWDKGj_KsuFtUUOkMVMvOZJxDbL5tl65EQOFMqsR8=@ferdeline.com>
 <CAH5sThmPjO3SpJ4bkRqA+t8UUCOu633kWOfASJyE_Ed5WBnsdA@mail.gmail.com>
 <1e15d66a-e0eb-381f-cdf7-2d4b59236e8d@mail.utoronto.ca>
 <CAN1qJvBx5ORLkH8XjM1Fi2qW6mw_CkmBDZDMe5YTakrQFRv8Kw@mail.gmail.com>
Message-ID: <02f02565-dc78-3a9d-325f-f5a837351f46@mail.utoronto.ca>

I think that is a really good idea, as these are important procedures, 
and we need to be able to amend if required.  Hard to anticipate 
everything, in my view...

SP


On 2017-08-07 08:49, farzaneh badii wrote:
> Hi
>
> I was on the DT group. I don't have the time to go through every 
> single change and see if they accord with what we agreed on. If you 
> want in the public comment we should ask that if later on during 
> implementing the operating procedures we find out that 
>  changes recommended by  DT   for some reason are not reflected in the 
> new  GNSO operating procedures, GNSO should follow the DT advice in 
> those circumstances and allow for the mistake to be corrected.
>
> Farzaneh
>
> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin 
> <stephanie.perrin at mail.utoronto.ca 
> <mailto:stephanie.perrin at mail.utoronto.ca>> wrote:
>
>     It looks fine to me.  I don't have knowledge of or time to do the
>     research on the issues at the moment, so I hope that those who do
>     can catch things that need changes.
>
>     cheers Stephanie
>
>
>     On 2017-08-07 02:07, Rafik Dammak wrote:
>>     Hi,
>>
>>     the comment is quite straightforward and supporting the changes
>>     outlined in the public consultation.
>>     we can have as the deadline for review and endorsement the 9th
>>     August. I urge councilors, in particular, to review the changes
>>     since it concerns the operating procedures.
>>     Thanks, Matt again for the draft. I resolved the edits made by
>>     Ayden. ant proof-reading and review would be helpful.
>>
>>     Best,
>>
>>     Rafik
>>
>>     2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com
>>     <mailto:icann at ferdeline.com>>:
>>
>>         Hi all,
>>
>>         I have made some minor alterations to style, but added
>>         nothing of substance. I hope someone with more knowledge of
>>         this issue will be able to contribute to our comment.
>>         Submissions are due in six days time. Thanks!
>>
>>         Best wishes, Ayden
>>
>>
>>>         -------- Original Message --------
>>>         Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating
>>>         procedures change
>>>         Local Time: August 1, 2017 5:35 PM
>>>         UTC Time: August 1, 2017 4:35 PM
>>>         From: matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>         To: ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>,
>>>         farzaneh badii <farzaneh.badii at GMAIL.COM
>>>         <mailto:farzaneh.badii at GMAIL.COM>>
>>>
>>>
>>>         Hi all
>>>
>>>         Wanted to get this back at the top of the list of to-do's as
>>>         time is running out.
>>>
>>>         Appreciate the comments from some of the PC members but
>>>         would welcome additional inputs, thoughts, etc.
>>>
>>>         See google doc below.
>>>
>>>         Thanks.
>>>
>>>         Matthew
>>>
>>>
>>>         On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>         Matt,
>>>>         I don?t have any comment to do, I agree with the statements
>>>>         and the wording. Let me know if I can do anything specific
>>>>         to help. Other than that you have my support. Thanks!
>>>>
>>>>         Cheers,
>>>>         Mart?n
>>>>
>>>>>         On Jul 25, 2017, at 8:22 PM, Rafik Dammak
>>>>>         <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>>
>>>>>         wrote:
>>>>>
>>>>>         Hi,
>>>>>
>>>>>         the deadline for the public comment is the 10th of August,
>>>>>         we have to finish consulting with NCSG members, review and
>>>>>         endorsement prior to that. I suggest 8th August as our
>>>>>         internal deadline.
>>>>>
>>>>>         Best,
>>>>>
>>>>>         Rafik
>>>>>
>>>>>
>>>>>         2017-07-25 23:28 GMT+09:00 Stefania Milan
>>>>>         <stefania.milan at eui.eu <mailto:stefania.milan at eui.eu>>:
>>>>>
>>>>>             Hi Matt, thanks. What's the deadline for this? I am in
>>>>>             transit (and in fact, on holiday), witch sketchy
>>>>>             internet access and the doc doesn't open for me today
>>>>>             (might be the poor connection...)
>>>>>
>>>>>             Sent from my iPhone
>>>>>
>>>>>             On Jul 25, 2017, at 9:17 AM, Matthew Shears
>>>>>             <matthew at intpolicy.com <mailto:matthew at intpolicy.com>>
>>>>>             wrote:
>>>>>
>>>>>>             Let me qualify the last sentence - ICANN staff are
>>>>>>             not adding new items in addition to the work of the
>>>>>>             DT, but rather adding references to work done previously.
>>>>>>
>>>>>>
>>>>>>             On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>>             Calling all PCers
>>>>>>>
>>>>>>>             I have started on the above public comment but am
>>>>>>>             still going through the consultation docs. However,
>>>>>>>             time marches on and we need to get this one underway.
>>>>>>>
>>>>>>>             So, please review the consultation docs here:
>>>>>>>
>>>>>>>             https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>>>>             <https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en>
>>>>>>>
>>>>>>>             And make comments in the google doc here:
>>>>>>>
>>>>>>>             https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit
>>>>>>>             <https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit>
>>>>>>>
>>>>>>>             Note that ICANN staff have used this opportunity to
>>>>>>>             include other changes that the DT did not discuss.
>>>>>>>
>>>>>>>             Many thanks.
>>>>>>>
>>>>>>>             Matthew
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>             -- 
>>>>>>>             Matthew Shears
>>>>>>>             matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>>>>>             +447712472987 <tel:+44%207712%20472987>
>>>>>>>             Skype:mshears
>>>>>>
>>>>>>             -- 
>>>>>>             Matthew Shears
>>>>>>             matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>>>>             +447712472987 <tel:+44%207712%20472987>
>>>>>>             Skype:mshears
>>>>>>             _______________________________________________
>>>>>>             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>
>>>>>
>>>>>
>>>>>             The information transmitted is intended only for the
>>>>>             person or entity to which it is addressed and may
>>>>>             contain confidential and/or privileged material. Any
>>>>>             review, retransmission, dissemination, distribution,
>>>>>             forwarding, or other use of, or taking of any action
>>>>>             in reliance upon, this information by persons or
>>>>>             entities other than the intended recipient is
>>>>>             prohibited without the express permission of the
>>>>>             sender. If you received this communication in error,
>>>>>             please contact the sender and delete the material from
>>>>>             any computer.
>>>>>
>>>>>
>>>>>             _______________________________________________
>>>>>             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>
>>>>
>>>>
>>>>         <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>         	Virus-free. www.avg.com
>>>>         <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>
>>>>
>>>>
>>>>
>>>>         _______________________________________________
>>>>         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>
>>>>
>>>
>>>         -- 
>>>
>>>
>>>         Matthew Shears
>>>         matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>         +447712472987 <tel:+44%207712%20472987>
>>>         Skype:mshears
>>
>>
>>         _______________________________________________
>>         NCSG-PC mailing list
>>         NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>
>>
>>
>>
>>     _______________________________________________
>>     NCSG-PC mailing list
>>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>
>
>     _______________________________________________
>     NCSG-PC mailing list
>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>
>

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

From matthew at intpolicy.com  Mon Aug  7 18:20:03 2017
From: matthew at intpolicy.com (Matthew Shears)
Date: Mon, 7 Aug 2017 16:20:03 +0100
Subject: [NCSG-PC] Fwd: Re: [council] Action Items: GNSO Council meeting
 13 July 2017
In-Reply-To: <CAH5sThnEzR7i7hZDiqvZz_xb8AzKnPOALH5sWVPXxANE0KqnFw@mail.gmail.com>
References: <CADWyk6xtZEdsyuTwGMBDTzPSyN3iRCMWVhkmZT_gK_x-4jKOSQ@mail.gmail.com>
 <93b25b52-2f9d-647d-bb57-c210a59034cc@mail.utoronto.ca>
 <CAH5sThnEzR7i7hZDiqvZz_xb8AzKnPOALH5sWVPXxANE0KqnFw@mail.gmail.com>
Message-ID: <09dde1dd-be25-90d5-3cb7-93cc4b2f4362@intpolicy.com>

Hi Rafik

Not sure where this is at the moment, but I am a little confused by this

4. To facilitate the work as requested under Resolved clause #3, 
allowing for a reasonable time to coordinate with other SOs and ACs to 
develop a new structure, and to ensure there is no gap between the 
retirement of the CCWG-IC and the establishment of its successor group, 
the GNSO Council shall withdraw as a Chartering Organization from the 
CCWG-IG effective at the conclusion of ICANN 61 .


So we are suggesting the GNSO is withdrawing only because of the 
structure - have we addressed the Council's other concerns?   (Does this 
assume that whatever other structure the WG-IG assume will not require 
the GNSO's support or endorsement?)   One of the key issues, I 
understood, was that there needed to be some accountability of the WG-IG 
back to the Council or constituencies.  How then would this be accounted 
for?  Or perhaps the discussion has moved on and I am not up to speed.

Thanks.

Matthew



On 07/08/2017 13:50, Rafik Dammak wrote:
> Hi Stephanie,
>
> I shared the proposed amendments in this list just after the last call 
> but I didn't get any comment 
> https://lists.ncsg.is/pipermail/ncsg-pc/2017-July/000737.html.
> no, we didn't submit the amendments to the council.
>
> Best,
>
> Rafik
>
> 2017-08-07 21:46 GMT+09:00 Stephanie Perrin 
> <stephanie.perrin at mail.utoronto.ca 
> <mailto:stephanie.perrin at mail.utoronto.ca>>:
>
>     Just checking, have we submitted our proposal for the IG item (see
>     bolded bit below item 7) to the GNSO list?  Deadline looming....
>
>     cheers SP
>
>
>
>     -------- Forwarded Message --------
>     Subject: 	Re: [council] Action Items: GNSO Council meeting 13 July
>     2017
>     Date: 	Mon, 7 Aug 2017 13:18:38 +1000
>     From: 	Heather Forrest <haforrestesq at gmail.com>
>     <mailto:haforrestesq at gmail.com>
>     To: 	James M. Bladel <jbladel at godaddy.com>
>     <mailto:jbladel at godaddy.com>, council at gnso.icann.org
>     <mailto:council at gnso.icann.org> <council at gnso.icann.org>
>     <mailto:council at gnso.icann.org>, Jeff Neuman
>     <jeff.neuman at comlaude.com> <mailto:jeff.neuman at comlaude.com>,
>     avri at apc.org <mailto:avri at apc.org>
>     CC: 	gnso-secs at icann.org <mailto:gnso-secs at icann.org>
>     <gnso-secs at icann.org> <mailto:gnso-secs at icann.org>
>
>
>
>     Dear colleagues,
>
>     Just following up on the point made by James on 18 July about
>     whether or not to put the CWG-UCTN Final Report on our August
>     agenda, or hold it to September's agenda. FYI the following has
>     taken place since 18 July:
>
>       * ccNSO Council has voted on and approved the CWG-UCTN Final Report
>       * SubPro is in the process of creating Work Track 5 on geo names
>
>     As a co-chair of this CWG, my personal view is that the GNSO can
>     endorse the Final Report, but should make comments in the motion
>     pointing to SubPro and the new WT5. In my view, the timing of such
>     a motion (and how forcefully we make our comments about WT5) is
>     dependent upon SubPro - let's put this on Council's agenda at a
>     time most helpful to SubPro and WT5. With that in mind, I suggest
>     we take some guidance from Jeff and Avri here.
>
>     I note that our document deadline for August meeting is in roughly
>     7 days, so we need time to pull together a motion if this is going
>     onto the August agenda.
>
>     Best wishes,
>
>     Heather
>
>     On Tue, Jul 18, 2017 at 10:17 AM, James M. Bladel
>     <jbladel at godaddy.com <mailto:jbladel at godaddy.com>> wrote:
>
>         Thank you, Nathalie.
>
>         Council Colleagues, a few semi-random thoughts on the items below:
>
>         #6. We have a small team working on the GNSO Response to the
>         GAC's Johannesburg communique. Expect final draft language
>         this week, with approval via email ballot to follow. The goal
>         is to provide our response to the Board in advance of their
>         meeting with the GAC in mid-August.
>
>         *#7. CCWG-IG - Please note that this item was **_deferred_**,
>         rather than withdrawn. This means that it will appear on our
>         next meeting's ballot for a vote. I know that some folks
>         wanted to submit amendments, and I urge that these be posted
>         to the Council list by the next document deadline (14 AUG), or
>         the motion will head to a vote un-amended.**
>         ***
>         #8. This discussion item has been rescheduled for two
>         subsequent meetings, so I'm hopeful that we will give it full
>         consideration during our next meeting. I recommend we move it
>         to the top of our non-voting agenda.
>
>         #9. Because this item is related to other ongoing activities,
>         including follow-up from the GeoNames sessions in Johannesburg
>         and the formation of SubPro Work Track 5, a motion for a vote
>         may or may not appear on our August agenda. Stay tuned for
>         further developments.
>
>         Thank you,
>
>         J.
>         -----------------
>         James Bladel
>         GNSO Chair
>
>         On Jul 17, 2017, 16:50 -0500, Nathalie Peregrine
>         <nathalie.peregrine at icann.org
>         <mailto:nathalie.peregrine at icann.org>>, wrote:
>>
>>         Dear Councilors,
>>
>>         Please find the action items as stated during the meeting,
>>         below and as attachment arising from the GNSO Council meeting
>>         held on Thursday 13 July 2017.  Please take note of the
>>         action items coming out of the Council sessions and the
>>         proposed timing for delivering on these actions.
>>
>>         *ACTION ITEMS GNSO COUNCIL MEETING 13 July 2017*
>>
>>         *_Item 3. Consent Agenda - Appointment of James Bladel as the
>>         GNSO Representative to the Empowered Community_*
>>
>>           * the GNSO Secretariat to communicate this decision to the
>>             ICANN Secretary which will serve as the required written
>>             certification from the GNSO Chair designating the
>>             individual who shall represent the Decisional Participant
>>             on the EC Administration.
>>
>>         *__*
>>
>>         *_Item 4: COUNCIL VOTE ? Proposed Fundamental Bylaw Changes_*
>>
>>           * GNSO Secretariat to forward the adopted resolution to the
>>             Empowered Community Administration before the expiration
>>             of the Approval Action Decision Period, as required under
>>             Section 1.4, Article 1, Annex D of the ICANN Bylaws.
>>           * James Bladel, the GNSO?s representative to the Empowered
>>             Community Administration, to coordinate with the other
>>             four Decisional Participant representatives to ensure
>>             that the Empowered Community Administration observes and
>>             completes the appropriate process outlined in Section
>>             1.4(b) and (c), Annex D.
>>
>>         *__*
>>
>>         *_Item 6. COUNCIL VOTE ? Approval of GNSO Council Review of
>>         the GAC Communique from Johannesburg_*
>>
>>           * Volunteers to revise response to GAC Communique and
>>             circulate revised draft to the Council as soon as
>>             possible. Volunteers include: Paul, James, Jeff Neuman
>>             (if allowed), Rubens, Heather (sanity check), Phil,
>>             Darcy, possibly Stephanie (to convey Avri?s views), and
>>             Carlos. Volunteers to consider input received in relation
>>             to Geo Names section as well as IGO section, including
>>             offering the opportunity to detail IGO/INGO CRP
>>             recommendations with the ICANN Board prior to a vote
>>             being taken to provide details how small group, IGO
>>             comments factored into Final Report and recommendations.
>>           * GNSO Leadership to provide 7-day notice of e-vote to
>>             approve response to GAC Communique
>>
>>         *__*
>>
>>         *_Item 7: COUNCIL Vote ? Next steps in relation to Charter
>>         for the Cross Community Working Group on Internet Governance_*
>>
>>           * Motion deferred -  GNSO leadership to add this item to
>>             the Council agenda for August meeting.
>>           * All Council members to provide input and proposed
>>             amendments to the motions as soon as possible so that
>>             discussion can continue on the mailing list ahead of the
>>             meeting.
>>
>>         *__*
>>
>>         *_Item 8. COUNCIL DISCUSSION ? Possible Change to the Name of
>>         the GNSO_*
>>
>>           * Item deferred ? GNSO Council leadership to add this item
>>             to the Council agenda for August meeting.
>>
>>         *__*
>>
>>         *_Item 9: COUNCIL DISCUSSION ? Cross Community Working Group
>>         on the Use of Country and Territory Names_*
>>
>>           * Council members to consider drafting Motion for August
>>             meeting on this topic.
>>           * Ben Fuller to solicit input from ccNSO on this topic and
>>             provide feedback to the GNSO Council
>>
>>         *__*
>>
>>         Please note that all Action Items have been posted on the
>>         Action Item wiki page here[community.icann.org]
>>         <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_RgZlAg&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=3Tc6XSN5n8FryvXrAqUdyp0sa6kuAUqPfvvw4f3uwKQ&s=4DEDZ2Meg9ZUFIObabj6BRFzEywMdXPo7au4Kd0LSJI&e=>.
>>         Please refer to this page for the recent status updates on
>>         the Action items.
>>
>>         Thank you,
>>
>>         Kind regards,
>>
>>         Nathalie
>>
>>         -- 
>>
>>         Nathalie Peregrine
>>
>>         Specialist, SOAC Support (GNSO)
>>
>>         Internet Corporation for Assigned Names and Numbers (ICANN)
>>
>>         Email: nathalie.peregrine at icann.org
>>         <http://nathalie.peregrine at icann.org%20>
>>
>>         Skype: nathalie.peregrine.icann
>>
>>         Find out more about the GNSO by taking our interactive
>>         courses <http://learn.icann.org/courses/gnso> and visiting
>>         the GNSO Newcomer pages[gnso.icann.org]
>>         <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DgMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=YXXgWMx7AnEsK0bIjCRJ20RWD6FrJ7eshz4ee3BoCuw&s=z012pgyZrR1-Hdltx67AUtBaeooNRaHBDVfbgPe9pt8&e=>
>>
>
>         _______________________________________________
>         council mailing list
>         council at gnso.icann.org <mailto:council at gnso.icann.org>
>         https://mm.icann.org/mailman/listinfo/council
>         <https://mm.icann.org/mailman/listinfo/council>
>
>
>
>     _______________________________________________
>     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>
>
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
> 	Virus-free. www.avg.com 
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

-- 


Matthew Shears
matthew at intpolicy.com
+447712472987
Skype:mshears

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

From ncsg at tapani.tarvainen.info  Mon Aug  7 19:12:46 2017
From: ncsg at tapani.tarvainen.info (Tapani Tarvainen)
Date: Mon, 7 Aug 2017 19:12:46 +0300
Subject: [NCSG-PC] 3rd SSC representative
Message-ID: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>

Dear PC,

I've been reminded we still haven't appointed our 3rd representative
to the GNSO Standing Selection Committee.

It would be nice if we could get it done reasonably soon.

Cheers,

-- 
Tapani Tarvainen


From mpsilvavalent at gmail.com  Mon Aug  7 19:17:01 2017
From: mpsilvavalent at gmail.com (Martin Pablo Silva Valent)
Date: Mon, 7 Aug 2017 13:17:01 -0300
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
Message-ID: <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>

Should we open this call to the discuss list or keep it in the pc members? I know we are still a few month from the election, but if no one else steps in one of the candidate that wasn?t elected could have this position.

Last time Rafik was in the run for this, if he still wants it he should have priority to be considered.

Cheers,
Martin 

> On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen <ncsg at tapani.tarvainen.info> wrote:
> 
> Dear PC,
> 
> I've been reminded we still haven't appointed our 3rd representative
> to the GNSO Standing Selection Committee.
> 
> It would be nice if we could get it done reasonably soon.
> 
> Cheers,
> 
> -- 
> Tapani Tarvainen
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc



From pileleji at ymca.gm  Mon Aug  7 19:45:56 2017
From: pileleji at ymca.gm (Poncelet Ileleji)
Date: Mon, 7 Aug 2017 16:45:56 +0000
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
Message-ID: <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>

Dear Colleagues

We  know the third slot was stalled?, but as the  process had  started
already can that processs be completed.

Kind Regards

Poncelet

On 7 August 2017 at 16:17, Martin Pablo Silva Valent <
mpsilvavalent at gmail.com> wrote:

> Should we open this call to the discuss list or keep it in the pc members?
> I know we are still a few month from the election, but if no one else steps
> in one of the candidate that wasn?t elected could have this position.
>
> Last time Rafik was in the run for this, if he still wants it he should
> have priority to be considered.
>
> Cheers,
> Martin
>
> > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen <ncsg at tapani.tarvainen.info>
> wrote:
> >
> > Dear PC,
> >
> > I've been reminded we still haven't appointed our 3rd representative
> > to the GNSO Standing Selection Committee.
> >
> > It would be nice if we could get it done reasonably soon.
> >
> > Cheers,
> >
> > --
> > Tapani Tarvainen
> > _______________________________________________
> > 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/20170807/4cadb9a5/attachment.htm>

From mpsilvavalent at gmail.com  Mon Aug  7 20:33:20 2017
From: mpsilvavalent at gmail.com (Martin Pablo Silva Valent)
Date: Mon, 7 Aug 2017 14:33:20 -0300
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
Message-ID: <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>

That process is not there in more, we have to make a new one (remember it was questioned and then one of the candidate drop, and then the other also refused to finish the process like that). So we have to go from scratch, but if Rafik is still interested I would promote to have him considered first for many good reasons. If not, the question is if we open the call to the list or we keep it in the PC member list (fue to their leadership role in ncsg policy make sense they are close enough to be part of the SSC of the Council).

Cheers,
Mart?n

> On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji <pileleji at ymca.gm> wrote:
> 
> Dear Colleagues
> 
> We  know the third slot was stalled?, but as the  process had  started already can that processs be completed.
> 
> Kind Regards
> 
> Poncelet
> 
> On 7 August 2017 at 16:17, Martin Pablo Silva Valent <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>> wrote:
> Should we open this call to the discuss list or keep it in the pc members? I know we are still a few month from the election, but if no one else steps in one of the candidate that wasn?t elected could have this position.
> 
> Last time Rafik was in the run for this, if he still wants it he should have priority to be considered.
> 
> Cheers,
> Martin
> 
> > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen <ncsg at tapani.tarvainen.info <mailto:ncsg at tapani.tarvainen.info>> wrote:
> >
> > Dear PC,
> >
> > I've been reminded we still haven't appointed our 3rd representative
> > to the GNSO Standing Selection Committee.
> >
> > It would be nice if we could get it done reasonably soon.
> >
> > Cheers,
> >
> > --
> > Tapani Tarvainen
> > _______________________________________________
> > 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>
> 
> 
> 
> -- 
> 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 <http://www.diplointernetgovernance.org/>
> 
> 
> 
> 

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

From t.tropina at mpicc.de  Mon Aug  7 23:30:52 2017
From: t.tropina at mpicc.de (Dr. Tatiana Tropina)
Date: Mon, 7 Aug 2017 22:30:52 +0200
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
Message-ID: <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>

Dear all,

I agree with Martin about Rafik. If he is still interested -- the best
way to fill in this slot would be to appoint. Him.

Cheers,

Tanya


On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
> That process is not there in more, we have to make a new one (remember
> it was questioned and then one of the candidate drop, and then the
> other also refused to finish the process like that). So we have to go
> from scratch, but if Rafik is still interested I would promote to have
> him considered first for many good reasons. If not, the question is if
> we open the call to the list or we keep it in the PC member list (fue
> to their leadership role in ncsg policy make sense they are close
> enough to be part of the SSC of the Council).
>
> Cheers,
> Mart?n
>
>> On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji <pileleji at ymca.gm
>> <mailto:pileleji at ymca.gm>> wrote:
>>
>> Dear Colleagues
>>
>> We  know the third slot was stalled?, but as the  process had 
>> started already can that processs be completed.
>>
>> Kind Regards
>>
>> Poncelet
>>
>> On 7 August 2017 at 16:17, Martin Pablo Silva Valent
>> <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>> wrote:
>>
>>     Should we open this call to the discuss list or keep it in the pc
>>     members? I know we are still a few month from the election, but
>>     if no one else steps in one of the candidate that wasn?t elected
>>     could have this position.
>>
>>     Last time Rafik was in the run for this, if he still wants it he
>>     should have priority to be considered.
>>
>>     Cheers,
>>     Martin
>>
>>     > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen
>>     <ncsg at tapani.tarvainen.info <mailto:ncsg at tapani.tarvainen.info>>
>>     wrote:
>>     >
>>     > Dear PC,
>>     >
>>     > I've been reminded we still haven't appointed our 3rd
>>     representative
>>     > to the GNSO Standing Selection Committee.
>>     >
>>     > It would be nice if we could get it done reasonably soon.
>>     >
>>     > Cheers,
>>     >
>>     > --
>>     > Tapani Tarvainen
>>     > _______________________________________________
>>     > 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>
>>
>>
>>
>>
>> -- 
>> 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/
>> 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
>> /www.diplointernetgovernance.org
>> <http://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/20170807/e208b5b6/attachment.htm>

From icann at ferdeline.com  Tue Aug  8 00:48:26 2017
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Mon, 07 Aug 2017 17:48:26 -0400
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
 <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
Message-ID: <9Ss39VrjfeqaHXkON9GzqzE7ee1iiGlGgcIENhyto_En1Kd47WjOxlOaEGJ4vz0tsACrIy-KG6PD8JtkOLjJ4N0KZFJoNd_ZSA_EeeB0p5Q=@ferdeline.com>

+1; appointing Rafik - if he has the bandwidth - is an excellent idea, Martin.

Best, Ayden

> -------- Original Message --------
> Subject: Re: [NCSG-PC] 3rd SSC representative
> Local Time: 7 August 2017 9:30 PM
> UTC Time: 7 August 2017 20:30
> From: t.tropina at mpicc.de
> To: ncsg-pc at lists.ncsg.is
>
> Dear all,
>
> I agree with Martin about Rafik. If he is still interested -- the best way to fill in this slot would be to appoint. Him.
>
> Cheers,
>
> Tanya
>
> On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
>
>> That process is not there in more, we have to make a new one (remember it was questioned and then one of the candidate drop, and then the other also refused to finish the process like that). So we have to go from scratch, but if Rafik is still interested I would promote to have him considered first for many good reasons. If not, the question is if we open the call to the list or we keep it in the PC member list (fue to their leadership role in ncsg policy make sense they are close enough to be part of the SSC of the Council).
>> Cheers,
>> Mart?n
>>
>>> On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji <pileleji at ymca.gm> wrote:
>>>
>>> Dear Colleagues
>>> We know the third slot was stalled?, but as the process had started already can that processs be completed.
>>> Kind Regards
>>> Poncelet
>>>
>>> On 7 August 2017 at 16:17, Martin Pablo Silva Valent <mpsilvavalent at gmail.com> wrote:
>>>
>>>> Should we open this call to the discuss list or keep it in the pc members? I know we are still a few month from the election, but if no one else steps in one of the candidate that wasn?t elected could have this position.
>>>> Last time Rafik was in the run for this, if he still wants it he should have priority to be considered.
>>>> Cheers,
>>>> Martin
>>>>
>>>>> On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen <ncsg at tapani.tarvainen.info> wrote:
>>>>>
>>>>> Dear PC,
>>>>>
>>>>> I've been reminded we still haven't appointed our 3rd representative
>>>>> to the GNSO Standing Selection Committee.
>>>>>
>>>>> It would be nice if we could get it done reasonably soon.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> --
>>>>> Tapani Tarvainen
>>>>> _______________________________________________
>>>>> 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/
>>> [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[www.diplointernetgovernance.org](http://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/20170807/f1bf5b32/attachment.htm>

From icann at ferdeline.com  Tue Aug  8 01:10:55 2017
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Mon, 07 Aug 2017 18:10:55 -0400
Subject: [NCSG-PC] ICANN Seeking Mentor for Global Indigenous Ambassador
	Program
Message-ID: <NSYnY4KOe0SL_Xg9-V5ijIPJOmM_qSIiQ57tqa7phPT9_HYa1MmkRmsaflQfN1MMw-GbvZ1-7YcdzhPrX5OE2rrnoOdvOr60K1Tz4mSmrO4=@ferdeline.com>

Applications for mentors for the 'Global Indigenous Ambassador Program' have now closed, but when I clicked on the [link](https://goo.gl/forms/nJq425KPjPtBcofM2) to the application form just now (it is a Google form), it has advised that, "This form is no longer accepting responses, and has been set to automatically close by judithh12 at gmail.com." This is the email address of a community member.
Given that the [announcement](https://www.icann.org/news/announcement-2-2017-08-01-en) on the ICANN website said that mentors must "follow all of the requirements for coaches as described in the ICANN Fellowship Program's handbook", and the listed [selection criteria](https://docs.google.com/document/d/1E1idwhPVdASTKz-Gz7zmb--xXsDoIzSdGqF4yE9WRQs/edit) states that the selected mentor must "Deliver a report ... [and] send it to ICANN Fellowship Coordinator", among other criterions which suggest ICANN staff involvement, I am wondering why a community member is receiving and presumably handling the applications and not ICANN staff. I am also wondering who will be involved in the selection of the mentor.
Do you think these are questions worth pursing?

Thanks, Ayden

> -------- Original Message --------
> Subject: Daily Digest of ICANN.org
> Local Time: 2 August 2017 12:30 AM
> UTC Time: 1 August 2017 23:30
> From: no-reply at icann.org
> To: Ayden F?rdeline <ayden at ferdeline.com>
>
> [ICANN]
>
> Daily Digest of ICANN.org
>
> News & Announcements
>
> ---------------------------------------------------------------
>
> [ICANN Seeking Mentor for Global Indigenous Ambassador Program](http://icann.org/news/announcement-2-2017-08-01-en)
>
> LOS ANGELES ? 27 July 2017 - Today, the Internet Corporation for Assigned Names and Numbers (ICANN) announced a call for a volunteer to serve as a mentor for the Global Indigenous Ambassador Program. ICANN announced the creation of the Global Indigenous Ambassador Program in June 2017. The program establishes two Indigenous Ambassadors, which will be selected from underrepresented indigenous communities. Through the inclusion of a broader and more diverse base of knowledgeable constituents, ICANN will be better equipped to support the next generation of the global Internet community...
> [Read more](http://icann.org/news/announcement-2-2017-08-01-en)
>
> ---------------------------------------------------------------
>
> [Extended Deadline: Request for Proposal for the SSAC Organizational Review](http://icann.org/news/announcement-2017-08-01-en)
>
> The deadline has been extended for the Request for Proposal for the Independent Review of the Security and Stability Advisory Committee (SSAC). The new deadline is 21 Aug 2017 at 11:59 PM PDT. The Internet Corporation for Assigned Names and Numbers (ICANN) is seeking a provider to conduct an independent assessment of the Security and Stability Advisory Committee (SSAC). The provider should have technical knowledge or experience with security matters with the Internet technical community and the operators and managers of critical DNS infrastructure services; demonstrate an understanding of...
> [Read more](http://icann.org/news/announcement-2017-08-01-en)
>
> ---------------------------------------------------------------
>
> [BROWSE ALL NEWS](http://icann.org/news)
>
> This message was sent to ayden at ferdeline.com from:
>
> ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536
>
> [Manage Your Subscription](http://icann.org/user/account_setting/edit?section=news)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170807/67b785cd/attachment.htm>

From rafik.dammak at gmail.com  Tue Aug  8 02:41:38 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 8 Aug 2017 08:41:38 +0900
Subject: [NCSG-PC] Fwd: Re: [council] Action Items: GNSO Council meeting
 13 July 2017
In-Reply-To: <09dde1dd-be25-90d5-3cb7-93cc4b2f4362@intpolicy.com>
References: <CADWyk6xtZEdsyuTwGMBDTzPSyN3iRCMWVhkmZT_gK_x-4jKOSQ@mail.gmail.com>
 <93b25b52-2f9d-647d-bb57-c210a59034cc@mail.utoronto.ca>
 <CAH5sThnEzR7i7hZDiqvZz_xb8AzKnPOALH5sWVPXxANE0KqnFw@mail.gmail.com>
 <09dde1dd-be25-90d5-3cb7-93cc4b2f4362@intpolicy.com>
Message-ID: <CAH5sThmNyDpqLWihzCnA7jU_DtXscU7b2MrZjj0NUHTFqXuHxg@mail.gmail.com>

Hi Matt,

we are not suggesting the withdrawal per se since it is in the initial
motion from Keith. we are proposing amendments in that area to give the
working group more time to provide a proposal (ICANN61 instead of ICANN60
as proposed initially). There was already some question on the transition
phase between withdrawing and resume the working group with a new
structure.

we cannot address the council concerns in the motion. We are proposing a
new amendment asking the council to itemize those concerns. The working
group can then be tasked to respond to them.

the working group will have basically to work on proposing a new vehicle
and responding to the accountability and reporting concerns.

Best,

Rafik

2017-08-08 0:20 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:

> Hi Rafik
>
> Not sure where this is at the moment, but I am a little confused by this
>
> 4. To facilitate the work as requested under Resolved clause #3, allowing
> for a reasonable time to coordinate with other SOs and ACs to develop a new
> structure, and to ensure there is no gap between the retirement of the
> CCWG-IC and the establishment of its successor group, the GNSO Council
> shall withdraw as a Chartering Organization from the CCWG-IG effective at
> the conclusion of ICANN 61 .
>
> So we are suggesting the GNSO is withdrawing only because of the structure
> - have we addressed the Council's other concerns?   (Does this assume that
> whatever other structure the WG-IG assume will not require the GNSO's
> support or endorsement?)   One of the key issues, I understood, was that
> there needed to be some accountability of the WG-IG back to the Council or
> constituencies.  How then would this be accounted for?  Or perhaps the
> discussion has moved on and I am not up to speed.
>
> Thanks.
>
> Matthew
>
>
>
>
> On 07/08/2017 13:50, Rafik Dammak wrote:
>
> Hi Stephanie,
>
> I shared the proposed amendments in this list just after the last call but
> I didn't get any comment https://lists.ncsg.is/
> pipermail/ncsg-pc/2017-July/000737.html.
> no, we didn't submit the amendments to the council.
>
> Best,
>
> Rafik
>
> 2017-08-07 21:46 GMT+09:00 Stephanie Perrin <stephanie.perrin at mail.
> utoronto.ca>:
>
>> Just checking, have we submitted our proposal for the IG item (see bolded
>> bit below item 7) to the GNSO list?  Deadline looming....
>>
>> cheers SP
>>
>>
>> -------- Forwarded Message --------
>> Subject: Re: [council] Action Items: GNSO Council meeting 13 July 2017
>> Date: Mon, 7 Aug 2017 13:18:38 +1000
>> From: Heather Forrest <haforrestesq at gmail.com> <haforrestesq at gmail.com>
>> To: James M. Bladel <jbladel at godaddy.com> <jbladel at godaddy.com>,
>> council at gnso.icann.org <council at gnso.icann.org> <council at gnso.icann.org>,
>> Jeff Neuman <jeff.neuman at comlaude.com> <jeff.neuman at comlaude.com>,
>> avri at apc.org
>> CC: gnso-secs at icann.org <gnso-secs at icann.org> <gnso-secs at icann.org>
>>
>>
>> Dear colleagues,
>>
>> Just following up on the point made by James on 18 July about whether or
>> not to put the CWG-UCTN Final Report on our August agenda, or hold it to
>> September's agenda. FYI the following has taken place since 18 July:
>>
>>    - ccNSO Council has voted on and approved the CWG-UCTN Final Report
>>    - SubPro is in the process of creating Work Track 5 on geo names
>>
>> As a co-chair of this CWG, my personal view is that the GNSO can endorse
>> the Final Report, but should make comments in the motion pointing to SubPro
>> and the new WT5. In my view, the timing of such a motion (and how
>> forcefully we make our comments about WT5) is dependent upon SubPro - let's
>> put this on Council's agenda at a time most helpful to SubPro and WT5. With
>> that in mind, I suggest we take some guidance from Jeff and Avri here.
>>
>> I note that our document deadline for August meeting is in roughly 7
>> days, so we need time to pull together a motion if this is going onto the
>> August agenda.
>>
>> Best wishes,
>>
>> Heather
>>
>> On Tue, Jul 18, 2017 at 10:17 AM, James M. Bladel <jbladel at godaddy.com>
>> wrote:
>>
>>> Thank you, Nathalie.
>>>
>>> Council Colleagues, a few semi-random thoughts on the items below:
>>>
>>> #6. We have a small team working on the GNSO Response to the GAC's
>>> Johannesburg communique. Expect final draft language this week, with
>>> approval via email ballot to follow. The goal is to provide our response to
>>> the Board in advance of their meeting with the GAC in mid-August.
>>>
>>> *#7. CCWG-IG - Please note that this item was **deferred**, rather than
>>> withdrawn. This means that it will appear on our next meeting's ballot for
>>> a vote. I know that some folks wanted to submit amendments, and I urge that
>>> these be posted to the Council list by the next document deadline (14 AUG),
>>> or the motion will head to a vote un-amended.*
>>>
>>> #8. This discussion item has been rescheduled for two subsequent
>>> meetings, so I'm hopeful that we will give it full consideration during our
>>> next meeting. I recommend we move it to the top of our non-voting agenda.
>>>
>>> #9. Because this item is related to other ongoing activities, including
>>> follow-up from the GeoNames sessions in Johannesburg and the formation of
>>> SubPro Work Track 5, a motion for a vote may or may not appear on our
>>> August agenda. Stay tuned for further developments.
>>>
>>> Thank you,
>>>
>>> J.
>>> -----------------
>>> James Bladel
>>> GNSO Chair
>>>
>>> On Jul 17, 2017, 16:50 -0500, Nathalie Peregrine <
>>> nathalie.peregrine at icann.org>, wrote:
>>>
>>> Dear Councilors,
>>>
>>>
>>>
>>> Please find the action items as stated during the meeting, below and as
>>> attachment arising from the GNSO Council meeting held on Thursday 13 July
>>> 2017.  Please take note of the action items coming out of the Council
>>> sessions and the proposed timing for delivering on these actions.
>>>
>>>
>>>
>>> *ACTION ITEMS GNSO COUNCIL MEETING 13 July 2017*
>>>
>>>
>>>
>>> *Item 3. Consent Agenda - Appointment of James Bladel as the GNSO
>>> Representative to the Empowered Community*
>>>
>>>    - the GNSO Secretariat to communicate this decision to the ICANN
>>>    Secretary which will serve as the required written certification from the
>>>    GNSO Chair designating the individual who shall represent the Decisional
>>>    Participant on the EC Administration.
>>>
>>>
>>>
>>> *Item 4: COUNCIL VOTE ? Proposed Fundamental Bylaw Changes*
>>>
>>>    - GNSO Secretariat to forward the adopted resolution to the
>>>    Empowered Community Administration before the expiration of the Approval
>>>    Action Decision Period, as required under Section 1.4, Article 1, Annex D
>>>    of the ICANN Bylaws.
>>>    - James Bladel, the GNSO?s representative to the Empowered Community
>>>    Administration, to coordinate with the other four Decisional Participant
>>>    representatives to ensure that the Empowered Community Administration
>>>    observes and completes the appropriate process outlined in Section 1.4(b)
>>>    and (c), Annex D.
>>>
>>>
>>>
>>> *Item 6. COUNCIL VOTE ? Approval of GNSO Council Review of the GAC
>>> Communique from Johannesburg*
>>>
>>>    - Volunteers to revise response to GAC Communique and circulate
>>>    revised draft to the Council as soon as possible. Volunteers include: Paul,
>>>    James, Jeff Neuman (if allowed), Rubens, Heather (sanity check), Phil,
>>>    Darcy, possibly Stephanie (to convey Avri?s views), and Carlos. Volunteers
>>>    to consider input received in relation to Geo Names section as well as IGO
>>>    section, including offering the opportunity to detail IGO/INGO CRP
>>>    recommendations with the ICANN Board prior to a vote being taken to provide
>>>    details how small group, IGO comments factored into Final Report and
>>>    recommendations.
>>>    - GNSO Leadership to provide 7-day notice of e-vote to approve
>>>    response to GAC Communique
>>>
>>>
>>>
>>> *Item 7: COUNCIL Vote ? Next steps in relation to Charter for the Cross
>>> Community Working Group on Internet Governance*
>>>
>>>    - Motion deferred -  GNSO leadership to add this item to the Council
>>>    agenda for August meeting.
>>>    - All Council members to provide input and proposed amendments to
>>>    the motions as soon as possible so that discussion can continue on the
>>>    mailing list ahead of the meeting.
>>>
>>>
>>>
>>> *Item 8. COUNCIL DISCUSSION ? Possible Change to the Name of the GNSO*
>>>
>>>    - Item deferred ? GNSO Council leadership to add this item to the
>>>    Council agenda for August meeting.
>>>
>>>
>>>
>>> *Item 9: COUNCIL DISCUSSION ? Cross Community Working Group on the Use
>>> of Country and Territory Names*
>>>
>>>    - Council members to consider drafting Motion for August meeting on
>>>    this topic.
>>>    - Ben Fuller to solicit input from ccNSO on this topic and provide
>>>    feedback to the GNSO Council
>>>
>>>
>>>
>>> Please note that all Action Items have been posted on the Action Item
>>> wiki page here[community.icann.org]
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_RgZlAg&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=3Tc6XSN5n8FryvXrAqUdyp0sa6kuAUqPfvvw4f3uwKQ&s=4DEDZ2Meg9ZUFIObabj6BRFzEywMdXPo7au4Kd0LSJI&e=>.
>>> Please refer to this page for the recent status updates on the Action items.
>>>
>>>
>>>
>>> Thank you,
>>>
>>>
>>>
>>> Kind regards,
>>>
>>>
>>>
>>> Nathalie
>>>
>>> --
>>>
>>>
>>>
>>> Nathalie Peregrine
>>>
>>> Specialist, SOAC Support (GNSO)
>>>
>>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>>
>>> Email: nathalie.peregrine at icann.org
>>> <http://nathalie.peregrine at icann.org%20>
>>>
>>> Skype: nathalie.peregrine.icann
>>>
>>>
>>>
>>> Find out more about the GNSO by taking our interactive courses
>>> <http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer
>>> pages[gnso.icann.org]
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DgMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=YXXgWMx7AnEsK0bIjCRJ20RWD6FrJ7eshz4ee3BoCuw&s=z012pgyZrR1-Hdltx67AUtBaeooNRaHBDVfbgPe9pt8&e=>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> council mailing list
>>> council at gnso.icann.org
>>> https://mm.icann.org/mailman/listinfo/council
>>>
>>>
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>>
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
> www.avg.com
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> <#m_6775909980563852075_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
> _______________________________________________
> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
> --
>
>
> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>
>
> _______________________________________________
> 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/20170808/a4ec3777/attachment.htm>

From rafik.dammak at gmail.com  Tue Aug  8 03:28:27 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 8 Aug 2017 09:28:27 +0900
Subject: [NCSG-PC] Drafting/Documenting NCSG Policy Committee Procedures
In-Reply-To: <CAH5sThmXLsSxhEv+QwrsqN8vvusFwXaNXJHs2ftdmh=rdMLQRw@mail.gmail.com>
References: <CAH5sThmXLsSxhEv+QwrsqN8vvusFwXaNXJHs2ftdmh=rdMLQRw@mail.gmail.com>
Message-ID: <CAH5sThkU-gDezYOPoeWd=WH05uFVMpdykH7o+5xWT+=A-DDSGw@mail.gmail.com>

Hi all,

I am resending this to resume discussion on drafting procedures for policy
committee work. I volunteered for drafting and hope to share something soon
for review and discussion.

NCUC used my previous proposal for NCSG comments and tweaked it. I will use
that and add other details such as: creating a template document for our
public statements (similar to what BC has) and adding an item about a
follow-up to check the staff report to see it includes our comment or not
(based on Ayden question).

any other procedure to suggest to those listed above. I recall that we
discussed last year about communication and I guess we can add that to the
list. maybe it is not procedure per se but can be seen as guidelines.

Best,

Rafik



2017-05-08 13:58 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:

> hi all,
>
> by the previous discussion we are having lately with regard to board seat
> election, SSC appointment, comments endorsement, involving and engaging
> NCSG membership, I would like to propose that we kick-off a discussion on
> Policy Committee procedures, processes, working methods, and guidelines.
>
> We can start by listing some items to cover first and work with NCSG EC
> for reviewing them and consulting NCSG membership after agreeing on a
> tentative timeline to get this done.
>
> Getting those procedures are overdue and will definitely help us for our
> work and it is one of the provision of NCSG charter to be filled. Some
> ideas for starters:
>
>
>    - Drafting and approving NCSG Statements
>    - Council Motions (engage with members and other councilors on how one
>    intends to vote with rationale)
>    - Appointments and selection process for NCSG representative
>    - Decision making
>    - Board Seat #14 selection process (as internal process)
>    - GNSO Council Chair and Vice Chair selection process (as internal
>    process)
>    - NCSG PC Chair and Vice Chair selection process
>
>
> I am volunteering to start drafting a strawman and sharing that with the
> policy committee but I am looking for others to join the effort and
> volunteer too.
>
> Best,
>
> Rafik
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170808/ea241a7d/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Tue Aug  8 03:57:23 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Mon, 7 Aug 2017 20:57:23 -0400
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <9Ss39VrjfeqaHXkON9GzqzE7ee1iiGlGgcIENhyto_En1Kd47WjOxlOaEGJ4vz0tsACrIy-KG6PD8JtkOLjJ4N0KZFJoNd_ZSA_EeeB0p5Q=@ferdeline.com>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
 <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
 <9Ss39VrjfeqaHXkON9GzqzE7ee1iiGlGgcIENhyto_En1Kd47WjOxlOaEGJ4vz0tsACrIy-KG6PD8JtkOLjJ4N0KZFJoNd_ZSA_EeeB0p5Q=@ferdeline.com>
Message-ID: <b5da8dba-f02e-944e-bae8-e4f939d09955@mail.utoronto.ca>

+1 for Rafik.

Stephanie


On 2017-08-07 17:48, Ayden F?rdeline wrote:
> +1; appointing Rafik - if he has the bandwidth - is an excellent idea, 
> Martin.
>
> Best, Ayden
>
>> -------- Original Message --------
>> Subject: Re: [NCSG-PC] 3rd SSC representative
>> Local Time: 7 August 2017 9:30 PM
>> UTC Time: 7 August 2017 20:30
>> From: t.tropina at mpicc.de
>> To: ncsg-pc at lists.ncsg.is
>>
>>
>> Dear all,
>>
>> I agree with Martin about Rafik. If he is still interested -- the 
>> best way to fill in this slot would be to appoint. Him.
>>
>> Cheers,
>>
>> Tanya
>>
>>
>> On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
>>> That process is not there in more, we have to make a new one 
>>> (remember it was questioned and then one of the candidate drop, and 
>>> then the other also refused to finish the process like that). So we 
>>> have to go from scratch, but if Rafik is still interested I would 
>>> promote to have him considered first for many good reasons. If not, 
>>> the question is if we open the call to the list or we keep it in the 
>>> PC member list (fue to their leadership role in ncsg policy make 
>>> sense they are close enough to be part of the SSC of the Council).
>>>
>>> Cheers,
>>> Mart?n
>>>
>>>> On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji <pileleji at ymca.gm 
>>>> <mailto:pileleji at ymca.gm>> wrote:
>>>>
>>>> Dear Colleagues
>>>>
>>>> We  know the third slot was stalled?, but as the  process had  
>>>> started already can that processs be completed.
>>>>
>>>>
>>>> Kind Regards
>>>>
>>>>
>>>> Poncelet
>>>>
>>>>
>>>> On 7 August 2017 at 16:17, Martin Pablo Silva Valent 
>>>> <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>> wrote:
>>>>
>>>>     Should we open this call to the discuss list or keep it in the
>>>>     pc members? I know we are still a few month from the election,
>>>>     but if no one else steps in one of the candidate that wasn?t
>>>>     elected could have this position.
>>>>
>>>>     Last time Rafik was in the run for this, if he still wants it
>>>>     he should have priority to be considered.
>>>>
>>>>     Cheers,
>>>>     Martin
>>>>
>>>>
>>>>     > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen
>>>>     <ncsg at tapani.tarvainen.info
>>>>     <mailto:ncsg at tapani.tarvainen.info>> wrote:
>>>>     >
>>>>     > Dear PC,
>>>>     >
>>>>     > I've been reminded we still haven't appointed our 3rd
>>>>     representative
>>>>     > to the GNSO Standing Selection Committee.
>>>>     >
>>>>     > It would be nice if we could get it done reasonably soon.
>>>>     >
>>>>     > Cheers,
>>>>     >
>>>>     > --
>>>>     > Tapani Tarvainen
>>>>     > _______________________________________________
>>>>     > 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>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> 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/
>>>> 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
>>>> /www.diplointernetgovernance.org 
>>>> <http://www.diplointernetgovernance.org/>
>>>>
>>>> *
>>>> *
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20170807/878e7f62/attachment.htm>

From mpsilvavalent at gmail.com  Tue Aug  8 03:57:51 2017
From: mpsilvavalent at gmail.com (Martin Pablo Silva Valent)
Date: Mon, 7 Aug 2017 21:57:51 -0300
Subject: [NCSG-PC] Drafting/Documenting NCSG Policy Committee Procedures
In-Reply-To: <CAH5sThkU-gDezYOPoeWd=WH05uFVMpdykH7o+5xWT+=A-DDSGw@mail.gmail.com>
References: <CAH5sThmXLsSxhEv+QwrsqN8vvusFwXaNXJHs2ftdmh=rdMLQRw@mail.gmail.com>
 <CAH5sThkU-gDezYOPoeWd=WH05uFVMpdykH7o+5xWT+=A-DDSGw@mail.gmail.com>
Message-ID: <49A5EE51-7440-42B3-9BDD-2F3D97CE517B@gmail.com>

I can work with Rafik with this, he?s experiences is way over mine, but for the little I can help I think it is an initiative worth working on. 

Cheers,
Mart?n

> On Aug 7, 2017, at 9:28 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
> 
> Hi all,
> 
> I am resending this to resume discussion on drafting procedures for policy committee work. I volunteered for drafting and hope to share something soon for review and discussion. 
> 
> NCUC used my previous proposal for NCSG comments and tweaked it. I will use that and add other details such as: creating a template document for our public statements (similar to what BC has) and adding an item about a follow-up to check the staff report to see it includes our comment or not (based on Ayden question).
> 
> any other procedure to suggest to those listed above. I recall that we discussed last year about communication and I guess we can add that to the list. maybe it is not procedure per se but can be seen as guidelines.
> 
> Best,
> 
> Rafik
> 
> 
> 
> 2017-05-08 13:58 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>>:
> hi all,
> 
> by the previous discussion we are having lately with regard to board seat election, SSC appointment, comments endorsement, involving and engaging NCSG membership, I would like to propose that we kick-off a discussion on Policy Committee procedures, processes, working methods, and guidelines.
> 
> We can start by listing some items to cover first and work with NCSG EC for reviewing them and consulting NCSG membership after agreeing on a tentative timeline to get this done.
> 
> Getting those procedures are overdue and will definitely help us for our work and it is one of the provision of NCSG charter to be filled. Some ideas for starters:
> 
> 
> Drafting and approving NCSG Statements
> Council Motions (engage with members and other councilors on how one intends to vote with rationale)
> Appointments and selection process for NCSG representative
> Decision making
> Board Seat #14 selection process (as internal process)
> GNSO Council Chair and Vice Chair selection process (as internal process)
> NCSG PC Chair and Vice Chair selection process                                  
> I am volunteering to start drafting a strawman and sharing that with the policy committee but I am looking for others to join the effort and volunteer too.
> 
> 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/20170807/6c6cd4a5/attachment.htm>

From rafik.dammak at gmail.com  Tue Aug  8 08:44:29 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 8 Aug 2017 14:44:29 +0900
Subject: [NCSG-PC] Drafting/Documenting NCSG Policy Committee Procedures
In-Reply-To: <49A5EE51-7440-42B3-9BDD-2F3D97CE517B@gmail.com>
References: <CAH5sThmXLsSxhEv+QwrsqN8vvusFwXaNXJHs2ftdmh=rdMLQRw@mail.gmail.com>
 <CAH5sThkU-gDezYOPoeWd=WH05uFVMpdykH7o+5xWT+=A-DDSGw@mail.gmail.com>
 <49A5EE51-7440-42B3-9BDD-2F3D97CE517B@gmail.com>
Message-ID: <CAH5sTh=9zBWYZ0kX7n=aerf7bnkQzgvhqQ_gaU+eMH8tG+VDjQ@mail.gmail.com>

Hi ,

Thanks, Martin,
I will create a google doc with an outline of those suggestions for
procedures and add some ideas for each. then share it as a strawman
document. that will make easier to cooperate on the same document and
kick-off the discussion.

Best,

Rafik

2017-08-08 9:57 GMT+09:00 Martin Pablo Silva Valent <mpsilvavalent at gmail.com
>:

> I can work with Rafik with this, he?s experiences is way over mine, but
> for the little I can help I think it is an initiative worth working on.
>
> Cheers,
> Mart?n
>
> On Aug 7, 2017, at 9:28 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
>
> Hi all,
>
> I am resending this to resume discussion on drafting procedures for policy
> committee work. I volunteered for drafting and hope to share something soon
> for review and discussion.
>
> NCUC used my previous proposal for NCSG comments and tweaked it. I will
> use that and add other details such as: creating a template document for
> our public statements (similar to what BC has) and adding an item about a
> follow-up to check the staff report to see it includes our comment or not
> (based on Ayden question).
>
> any other procedure to suggest to those listed above. I recall that we
> discussed last year about communication and I guess we can add that to the
> list. maybe it is not procedure per se but can be seen as guidelines.
>
> Best,
>
> Rafik
>
>
>
> 2017-05-08 13:58 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:
>
>> hi all,
>>
>> by the previous discussion we are having lately with regard to board seat
>> election, SSC appointment, comments endorsement, involving and engaging
>> NCSG membership, I would like to propose that we kick-off a discussion on
>> Policy Committee procedures, processes, working methods, and guidelines.
>>
>> We can start by listing some items to cover first and work with NCSG EC
>> for reviewing them and consulting NCSG membership after agreeing on a
>> tentative timeline to get this done.
>>
>> Getting those procedures are overdue and will definitely help us for our
>> work and it is one of the provision of NCSG charter to be filled. Some
>> ideas for starters:
>>
>>
>>    - Drafting and approving NCSG Statements
>>    - Council Motions (engage with members and other councilors on how
>>    one intends to vote with rationale)
>>    - Appointments and selection process for NCSG representative
>>    - Decision making
>>    - Board Seat #14 selection process (as internal process)
>>    - GNSO Council Chair and Vice Chair selection process (as internal
>>    process)
>>    - NCSG PC Chair and Vice Chair selection process
>>
>>
>> I am volunteering to start drafting a strawman and sharing that with the
>> policy committee but I am looking for others to join the effort and
>> volunteer too.
>>
>> 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/20170808/6d35228f/attachment.htm>

From rafik.dammak at gmail.com  Tue Aug  8 09:08:05 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 8 Aug 2017 15:08:05 +0900
Subject: [NCSG-PC] Fw: [NCUC-DISCUSS] Suggested Comment: Draft Framework
 for Registry Operators to Respond to Security Threats
In-Reply-To: <9814ecaf-9030-2ee6-a39e-176775c71e01@mpicc.de>
References: <E1dbwdr-0005N3-F2@rmmprod06.runbox>
 <viDG_GKZm4MGicRFTne3yEZERwqRoqEYGvaYOBiMDIBmcXZpK3WOzB89GoIPEZ-HorUP_hvNPo6oJg4a9RcFT5qyvmWxwgkO61QEWNen_l4=@ferdeline.com>
 <CAH5sThktSm3qRv-1UH9sOEH0R4j4G4aev73XYTE70Zvn9OgSpw@mail.gmail.com>
 <CAH5sThmx08DOsLL4AbzAeyJF9-YEQLjqy0hbyZALxT5=cGr6kA@mail.gmail.com>
 <9814ecaf-9030-2ee6-a39e-176775c71e01@mpicc.de>
Message-ID: <CAH5sTh=5RcbZeHpMqZAtS-h9Uru0jx_huPEi6o=sj7x4eouiCw@mail.gmail.com>

Hi Tatiana,

Thanks for the comments,
while we are late by our deadline to submit a comment, I think we can solve
the concerns.
1/ do you have a proposal of rephrasing for the first statement?
2/ I understand your concerns and indeed doesn't seem aligned with our
previous stances regarding domain suspension. probably we can remove that.

really looking forward to solving this within the next 24hours.

Best,

Rafik
2017-08-05 6:56 GMT+09:00 Dr. Tatiana Tropina <t.tropina at mpicc.de>:

> Hi all,
>
> I have a couple of comments:
>
> 1) I have hard time making sense of the first point:
>
> "1. Registry Response, Responsible Parties
>
>  ?ROs are not necessarily the best parties to address certain security
> threats. The identification of the parties considered as being most
> relevant and appropriate in resolving the security threat is critical to
> the prompt resolution of the matter.?
>
> More specifically, responsibility of identifying security threats
> connected to New gTLDs and resolving them when possible rests with ROs."
>
> As this point is a part of the comment that refers to the "issue" I wonder
> what is this - a statement? What kind of issue is identified here? Are we
> recommending anything?  If not and if this is just an introduction, may be
> it's better to rephrase? May be it's just too late here but I struggling
> with what this "issue" implies.
>
> 2) I wonder if this one is really in line with NSCG values such as due
> process:
>
> 2. We ask you to consider including the following GAC recommendation in
> Registry Response:
>
> ?If Registry operator identifies risk of  harm, Registry operator will
> notify the relevant registrar and , if the registrar does not take
> immediate action, suspend the domain name until the matter is resolved.?
>
> The framework already lists the actions that Registry can take even in the
> case if "a negative or non-existent response from the Registrar", which
> "should not
> preclude the Registry from taking action". I do not like the notion of
> "immediate action" as it sound to vague to me and I believe that there are
> enough actions listed to address the issue under the framework rather than
> suspension of domain name - again, "till the matter is resolved" looks too
> vague. I don't think it's acceptable when it comes to such a matter as a
> suspension of domain name. I know enough cases of mistakes when due to
> abuse claims customers went dark, etc. I suggest we rather be careful here.
> But if everyone is comfortable with this suggestion, I'll surrender.
>
> Warm regards,
>
> Tanya
>
>
>
> On 04/08/17 09:39, Rafik Dammak wrote:
>
> Dear PC members,
>
> any comment on the draft? we got an extension till 6th August, we should
> review quickly and make a decision.
>
> Best,
>
> Rafik
>
> 2017-07-31 19:33 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:
>
>> Hi Ayden,
>>
>> Yes it is for PC review. We worked on it the last days with Juan, Dina
>> and Niels. James cannot response since is off for the coming days. I was
>> going to send email to related ICANN staff to inform that we will make a
>> late submission, hopefully by end of this week.
>>
>> Best,
>>
>> Rafik
>>
>>
>> On Jul 31, 2017 7:18 PM, "Ayden F?rdeline" <icann at ferdeline.com> wrote:
>>
>> I believe the PC is being asked to review this comment which has been
>> drafted by Dina and Juan. The submission deadline for comments on this
>> issue is today, but I suspect we will not be able to meet that, so let's
>> try for this Friday? I think we need to bring in a topic expert, James
>> Gannon (cc'd), to get his opinion on this comment, too -- because I am
>> happy to raise my hand and say I do not know anything about this topic.
>>
>> Best, Ayden
>>
>>
>> -------- Original Message --------
>> Subject: [NCUC-DISCUSS] Suggested Comment: Draft Framework for Registry
>> Operators to Respond to Security Threats
>> Local Time: July 30, 2017 11:24 PM
>> UTC Time: July 30, 2017 10:24 PM
>> From: thomascovenant at thomascovenant.org
>> To: NCUC-discuss <ncuc-discuss at lists.ncuc.org>
>>
>> Hello,
>>
>> the comment proposal is underneath, what are your thoughts?
>>
>> https://docs.google.com/document/d/1TfgHuMqzD660_CHLQMXMW4ph
>> nBtLSP94j6X5riY2Ko4/edit
>>
>> Note from Security Framework Drafting Team wiki workspace:
>>
>> - Is Public Comment required for the draft Framework?
>> - This is not a policy implementation nor a contractual requirements
>> document; therefore, a public comment proceeding would not be required.
>> However, SFDT has decided to conduct a public comment for broader community
>> feedback prior to finalization of the Framework.
>>
>> Main points:
>>
>> - Framework should be expanded
>> - Several minor details are to be clarified, restructuring proposal
>> - as a small step in response to proposed detailed report examination, I
>> suggest we include a recommendation on Responsible Threat Disclosure.
>>
>> Finally, I quote Point 3 from the Comment:
>>
>> "Since the following examination of threat report is identified in the
>> Framework, we strongly suggest including a recommendation on Responsible
>> Threat Disclosure to be included in the document:
>>
>> "Each RO should scrutinize, question or otherwise inquire about the
>> legitimacy of the origin
>> of a request, in accordance with their own internal policies and
>> processes."
>>
>> We have seen a broad variation in handling security threat reports,
>> varying from constructive actions addressing the issues to punishment of
>> the reporting party. Benefits of responsible threat submission are obvious.
>>
>> In this context, it is important to underline benefits and importance of
>> responsible threat disclosure. We request recommendation to extend goodwill
>> and not cause harm to the reporting party whenever possible:
>>
>> When applicable, RO should provide:
>>
>> - an easy way to report security threats and violation
>> - encrypted ways of communication
>> - option of anonymous submission"
>>
>> Other:
>>
>> - This is my first comment drafted with input from Juan Manuel Rojas
>> (thank you for commenting). Access to shared document and request for
>> review was given to those who expressed interest in working on it. All
>> input from the list is very welcome. Please let me know what needs to be
>> corrected and I will promptly do it.
>> - Comment is a bit late, I will request an extra week to discuss the
>> proposal with my humble excuses.
>>
>> BR,
>> Dina Solveig Jalkanen
>> --
>> * * *
>> Friendly geek in Amsterdam, FSFE Fellow
>> https://wiki.techinc.nl/index.php/User:Thomascovenant
>>
>>
>> _______________________________________________
>> Ncuc-discuss mailing list
>> Ncuc-discuss at lists.ncuc.org
>> http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>>
>>
>>
>> _______________________________________________
>> 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 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/20170808/1335cc29/attachment.htm>

From rafik.dammak at gmail.com  Tue Aug  8 10:07:37 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 8 Aug 2017 16:07:37 +0900
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <b5da8dba-f02e-944e-bae8-e4f939d09955@mail.utoronto.ca>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
 <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
 <9Ss39VrjfeqaHXkON9GzqzE7ee1iiGlGgcIENhyto_En1Kd47WjOxlOaEGJ4vz0tsACrIy-KG6PD8JtkOLjJ4N0KZFJoNd_ZSA_EeeB0p5Q=@ferdeline.com>
 <b5da8dba-f02e-944e-bae8-e4f939d09955@mail.utoronto.ca>
Message-ID: <CAH5sTh=aVgpE1bT=du+LgbWfSBPgQyVF8hirPuo_EOGzzTq6Jg@mail.gmail.com>

Hi all,

Thanks for the vote of confidence. I will be glad to appointed as rep to
SSC for a period if that helps. However, I still want that we work on
general process though for selecting and appointing representatives based
on the previous experience (please check the other thread proposing several
procedures to work on).

Best,

Rafik


2017-08-08 9:57 GMT+09:00 Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca>:

> +1 for Rafik.
>
> Stephanie
>
> On 2017-08-07 17:48, Ayden F?rdeline wrote:
>
> +1; appointing Rafik - if he has the bandwidth - is an excellent idea,
> Martin.
>
> Best, Ayden
>
> -------- Original Message --------
> Subject: Re: [NCSG-PC] 3rd SSC representative
> Local Time: 7 August 2017 9:30 PM
> UTC Time: 7 August 2017 20:30
> From: t.tropina at mpicc.de
> To: ncsg-pc at lists.ncsg.is
>
>
> Dear all,
>
> I agree with Martin about Rafik. If he is still interested -- the best way
> to fill in this slot would be to appoint. Him.
>
> Cheers,
>
> Tanya
>
> On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
>
> That process is not there in more, we have to make a new one (remember it
> was questioned and then one of the candidate drop, and then the other also
> refused to finish the process like that). So we have to go from scratch,
> but if Rafik is still interested I would promote to have him considered
> first for many good reasons. If not, the question is if we open the call to
> the list or we keep it in the PC member list (fue to their leadership role
> in ncsg policy make sense they are close enough to be part of the SSC of
> the Council).
>
> Cheers,
> Mart?n
>
> On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji <pileleji at ymca.gm> wrote:
>
> Dear Colleagues
>
> We  know the third slot was stalled?, but as the  process had  started
> already can that processs be completed.
>
>
> Kind Regards
>
>
> Poncelet
>
>
> On 7 August 2017 at 16:17, Martin Pablo Silva Valent <
> mpsilvavalent at gmail.com> wrote:
>
> Should we open this call to the discuss list or keep it in the pc members?
>> I know we are still a few month from the election, but if no one else steps
>> in one of the candidate that wasn?t elected could have this position.
>>
>> Last time Rafik was in the run for this, if he still wants it he should
>> have priority to be considered.
>>
>> Cheers,
>> Martin
>>
>>
>> > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen <
>> ncsg at tapani.tarvainen.info> wrote:
>> >
>> > Dear PC,
>> >
>> > I've been reminded we still haven't appointed our 3rd representative
>> > to the GNSO Standing Selection Committee.
>> >
>> > It would be nice if we could get it done reasonably soon.
>> >
>> > Cheers,
>> >
>> > --
>> > Tapani Tarvainen
>> > _______________________________________________
>> > 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 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
>
>
>
> _______________________________________________
> 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/20170808/c3f61a51/attachment.htm>

From ncsg at tapani.tarvainen.info  Tue Aug  8 10:43:30 2017
From: ncsg at tapani.tarvainen.info (Tapani Tarvainen)
Date: Tue, 8 Aug 2017 10:43:30 +0300
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <b5da8dba-f02e-944e-bae8-e4f939d09955@mail.utoronto.ca>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
 <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
 <9Ss39VrjfeqaHXkON9GzqzE7ee1iiGlGgcIENhyto_En1Kd47WjOxlOaEGJ4vz0tsACrIy-KG6PD8JtkOLjJ4N0KZFJoNd_ZSA_EeeB0p5Q=@ferdeline.com>
 <b5da8dba-f02e-944e-bae8-e4f939d09955@mail.utoronto.ca>
Message-ID: <20170808074330.t4wtghrmmdtnqikn@tarvainen.info>

+1 for Rafik from me, too.

Tapani

On Mon, Aug 07, 2017 at 08:57:23PM -0400, Stephanie Perrin (stephanie.perrin at mail.utoronto.ca) wrote:
> 
> +1 for Rafik.
> 
> Stephanie
> 
> 
> On 2017-08-07 17:48, Ayden F?rdeline wrote:
> > +1; appointing Rafik - if he has the bandwidth - is an excellent idea,
> > Martin.
> > 
> > Best, Ayden
> > 
> > > -------- Original Message --------
> > > Subject: Re: [NCSG-PC] 3rd SSC representative
> > > Local Time: 7 August 2017 9:30 PM
> > > UTC Time: 7 August 2017 20:30
> > > From: t.tropina at mpicc.de
> > > To: ncsg-pc at lists.ncsg.is
> > > 
> > > 
> > > Dear all,
> > > 
> > > I agree with Martin about Rafik. If he is still interested -- the
> > > best way to fill in this slot would be to appoint. Him.
> > > 
> > > Cheers,
> > > 
> > > Tanya
> > > 
> > > 
> > > On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
> > > > That process is not there in more, we have to make a new one
> > > > (remember it was questioned and then one of the candidate drop,
> > > > and then the other also refused to finish the process like
> > > > that). So we have to go from scratch, but if Rafik is still
> > > > interested I would promote to have him considered first for many
> > > > good reasons. If not, the question is if we open the call to the
> > > > list or we keep it in the PC member list (fue to their
> > > > leadership role in ncsg policy make sense they are close enough
> > > > to be part of the SSC of the Council).
> > > > 
> > > > Cheers,
> > > > Mart?n
> > > > 
> > > > > On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji
> > > > > <pileleji at ymca.gm <mailto:pileleji at ymca.gm>> wrote:
> > > > > 
> > > > > Dear Colleagues
> > > > > 
> > > > > We  know the third slot was stalled?, but as the  process
> > > > > had  started already can that processs be completed.
> > > > > 
> > > > > 
> > > > > Kind Regards
> > > > > 
> > > > > 
> > > > > Poncelet
> > > > > 
> > > > > 
> > > > > On 7 August 2017 at 16:17, Martin Pablo Silva Valent
> > > > > <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>>
> > > > > wrote:
> > > > > 
> > > > >     Should we open this call to the discuss list or keep it in the
> > > > >     pc members? I know we are still a few month from the election,
> > > > >     but if no one else steps in one of the candidate that wasn?t
> > > > >     elected could have this position.
> > > > > 
> > > > >     Last time Rafik was in the run for this, if he still wants it
> > > > >     he should have priority to be considered.
> > > > > 
> > > > >     Cheers,
> > > > >     Martin
> > > > > 
> > > > > 
> > > > >     > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen
> > > > >     <ncsg at tapani.tarvainen.info
> > > > >     <mailto:ncsg at tapani.tarvainen.info>> wrote:
> > > > >     >
> > > > >     > Dear PC,
> > > > >     >
> > > > >     > I've been reminded we still haven't appointed our 3rd
> > > > >     representative
> > > > >     > to the GNSO Standing Selection Committee.
> > > > >     >
> > > > >     > It would be nice if we could get it done reasonably soon.
> > > > >     >
> > > > >     > Cheers,
> > > > >     >
> > > > >     > --
> > > > >     > Tapani Tarvainen
> > > > >     > _______________________________________________
> > > > >     > 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>
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > --
> > > > > 
> > > > > 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/
> > > > > 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
> > > > > /www.diplointernetgovernance.org
> > > > > <http://www.diplointernetgovernance.org/>


From matthew at intpolicy.com  Tue Aug  8 11:14:19 2017
From: matthew at intpolicy.com (Matthew Shears)
Date: Tue, 8 Aug 2017 09:14:19 +0100
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <20170808074330.t4wtghrmmdtnqikn@tarvainen.info>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
 <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
 <9Ss39VrjfeqaHXkON9GzqzE7ee1iiGlGgcIENhyto_En1Kd47WjOxlOaEGJ4vz0tsACrIy-KG6PD8JtkOLjJ4N0KZFJoNd_ZSA_EeeB0p5Q=@ferdeline.com>
 <b5da8dba-f02e-944e-bae8-e4f939d09955@mail.utoronto.ca>
 <20170808074330.t4wtghrmmdtnqikn@tarvainen.info>
Message-ID: <1bcb2449-74f3-5d48-c967-1be99ad84052@intpolicy.com>

And from me.


On 08/08/2017 08:43, Tapani Tarvainen wrote:
> +1 for Rafik from me, too.
>
> Tapani
>
> On Mon, Aug 07, 2017 at 08:57:23PM -0400, Stephanie Perrin (stephanie.perrin at mail.utoronto.ca) wrote:
>> +1 for Rafik.
>>
>> Stephanie
>>
>>
>> On 2017-08-07 17:48, Ayden F?rdeline wrote:
>>> +1; appointing Rafik - if he has the bandwidth - is an excellent idea,
>>> Martin.
>>>
>>> Best, Ayden
>>>
>>>> -------- Original Message --------
>>>> Subject: Re: [NCSG-PC] 3rd SSC representative
>>>> Local Time: 7 August 2017 9:30 PM
>>>> UTC Time: 7 August 2017 20:30
>>>> From: t.tropina at mpicc.de
>>>> To: ncsg-pc at lists.ncsg.is
>>>>
>>>>
>>>> Dear all,
>>>>
>>>> I agree with Martin about Rafik. If he is still interested -- the
>>>> best way to fill in this slot would be to appoint. Him.
>>>>
>>>> Cheers,
>>>>
>>>> Tanya
>>>>
>>>>
>>>> On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
>>>>> That process is not there in more, we have to make a new one
>>>>> (remember it was questioned and then one of the candidate drop,
>>>>> and then the other also refused to finish the process like
>>>>> that). So we have to go from scratch, but if Rafik is still
>>>>> interested I would promote to have him considered first for many
>>>>> good reasons. If not, the question is if we open the call to the
>>>>> list or we keep it in the PC member list (fue to their
>>>>> leadership role in ncsg policy make sense they are close enough
>>>>> to be part of the SSC of the Council).
>>>>>
>>>>> Cheers,
>>>>> Mart?n
>>>>>
>>>>>> On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji
>>>>>> <pileleji at ymca.gm <mailto:pileleji at ymca.gm>> wrote:
>>>>>>
>>>>>> Dear Colleagues
>>>>>>
>>>>>> We  know the third slot was stalled?, but as the  process
>>>>>> had  started already can that processs be completed.
>>>>>>
>>>>>>
>>>>>> Kind Regards
>>>>>>
>>>>>>
>>>>>> Poncelet
>>>>>>
>>>>>>
>>>>>> On 7 August 2017 at 16:17, Martin Pablo Silva Valent
>>>>>> <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>>
>>>>>> wrote:
>>>>>>
>>>>>>      Should we open this call to the discuss list or keep it in the
>>>>>>      pc members? I know we are still a few month from the election,
>>>>>>      but if no one else steps in one of the candidate that wasn?t
>>>>>>      elected could have this position.
>>>>>>
>>>>>>      Last time Rafik was in the run for this, if he still wants it
>>>>>>      he should have priority to be considered.
>>>>>>
>>>>>>      Cheers,
>>>>>>      Martin
>>>>>>
>>>>>>
>>>>>>      > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen
>>>>>>      <ncsg at tapani.tarvainen.info
>>>>>>      <mailto:ncsg at tapani.tarvainen.info>> wrote:
>>>>>>      >
>>>>>>      > Dear PC,
>>>>>>      >
>>>>>>      > I've been reminded we still haven't appointed our 3rd
>>>>>>      representative
>>>>>>      > to the GNSO Standing Selection Committee.
>>>>>>      >
>>>>>>      > It would be nice if we could get it done reasonably soon.
>>>>>>      >
>>>>>>      > Cheers,
>>>>>>      >
>>>>>>      > --
>>>>>>      > Tapani Tarvainen
>>>>>>      > _______________________________________________
>>>>>>      > 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>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> 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/
>>>>>> 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
>>>>>> /www.diplointernetgovernance.org
>>>>>> <http://www.diplointernetgovernance.org/>
> _______________________________________________
> 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 AVG.
> http://www.avg.com

-- 


Matthew Shears
matthew at intpolicy.com
+447712472987
Skype:mshears



From t.tropina at mpicc.de  Tue Aug  8 11:40:32 2017
From: t.tropina at mpicc.de (Dr. Tatiana Tropina)
Date: Tue, 8 Aug 2017 10:40:32 +0200
Subject: [NCSG-PC] Fw: [NCUC-DISCUSS] Suggested Comment: Draft Framework
 for Registry Operators to Respond to Security Threats
In-Reply-To: <CAH5sTh=5RcbZeHpMqZAtS-h9Uru0jx_huPEi6o=sj7x4eouiCw@mail.gmail.com>
References: <E1dbwdr-0005N3-F2@rmmprod06.runbox>
 <viDG_GKZm4MGicRFTne3yEZERwqRoqEYGvaYOBiMDIBmcXZpK3WOzB89GoIPEZ-HorUP_hvNPo6oJg4a9RcFT5qyvmWxwgkO61QEWNen_l4=@ferdeline.com>
 <CAH5sThktSm3qRv-1UH9sOEH0R4j4G4aev73XYTE70Zvn9OgSpw@mail.gmail.com>
 <CAH5sThmx08DOsLL4AbzAeyJF9-YEQLjqy0hbyZALxT5=cGr6kA@mail.gmail.com>
 <9814ecaf-9030-2ee6-a39e-176775c71e01@mpicc.de>
 <CAH5sTh=5RcbZeHpMqZAtS-h9Uru0jx_huPEi6o=sj7x4eouiCw@mail.gmail.com>
Message-ID: <bbfbde23-e878-5983-a225-ca39a4667609@mpicc.de>

Hi Rafik,

As I said - I do not quite get what the first statement means in terms
of issues raised so I can't come up with any suggestion. I wish I could.
As this statement doesn't really contribute to anything and doesn't
raise any issue (although it's supposed to as it is placed in the
"issue" section) I suggest we just remove it for the sake of clarity.
Unless the drafters are ready to clarify or rephrase. But I don't think
removal will change anything in the document except making it clearer.

I am totally supporting your suggestion for removal of anotehr statement
- let's not send the mix messages especially with vague wording proposals.

Thanks!

Tanya


On 08/08/17 08:08, Rafik Dammak wrote:
> Hi Tatiana,
>
> Thanks for the comments,
> while we are late by our deadline to submit a comment, I think we can
> solve the concerns.
> 1/ do you have a proposal of rephrasing for the first statement?
> 2/ I understand your concerns and indeed doesn't seem aligned with our
> previous stances regarding domain suspension. probably we can remove that.
>
> really looking forward to solving this within the next 24hours.
>
> Best,
>
> Rafik
> 2017-08-05 6:56 GMT+09:00 Dr. Tatiana Tropina <t.tropina at mpicc.de
> <mailto:t.tropina at mpicc.de>>:
>
>     Hi all,
>
>     I have a couple of comments:
>
>     1) I have hard time making sense of the first point:
>
>     "1. Registry Response, Responsible Parties
>
>      ?ROs are not necessarily the best parties to address certain
>     security threats. The identification of the parties considered as
>     being most relevant and appropriate in resolving the security
>     threat is critical to the prompt resolution of the matter.?
>
>     More specifically, responsibility of identifying security threats
>     connected to New gTLDs and resolving them when possible rests with
>     ROs."
>
>     As this point is a part of the comment that refers to the "issue"
>     I wonder what is this - a statement? What kind of issue is
>     identified here? Are we recommending anything?  If not and if this
>     is just an introduction, may be it's better to rephrase? May be
>     it's just too late here but I struggling with what this "issue"
>     implies.
>
>     2) I wonder if this one is really in line with NSCG values such as
>     due process:
>
>     2. We ask you to consider including the following GAC
>     recommendation in Registry Response:
>
>     ?If Registry operator identifies risk of  harm, Registry operator
>     will notify the relevant registrar and , if the registrar does not
>     take immediate action, suspend the domain name until the matter is
>     resolved.?
>
>     The framework already lists the actions that Registry can take
>     even in the case if "a negative or non-existent response from the
>     Registrar", which "should not
>     preclude the Registry from taking action". I do not like the
>     notion of "immediate action" as it sound to vague to me and I
>     believe that there are enough actions listed to address the issue
>     under the framework rather than suspension of domain name - again,
>     "till the matter is resolved" looks too vague. I don't think it's
>     acceptable when it comes to such a matter as a suspension of
>     domain name. I know enough cases of mistakes when due to abuse
>     claims customers went dark, etc. I suggest we rather be careful
>     here. But if everyone is comfortable with this suggestion, I'll
>     surrender.
>
>     Warm regards,
>
>     Tanya
>
>
>
>     On 04/08/17 09:39, Rafik Dammak wrote:
>>     Dear PC members,
>>
>>     any comment on the draft? we got an extension till 6th August, we
>>     should review quickly and make a decision.
>>
>>     Best,
>>
>>     Rafik
>>
>>     2017-07-31 19:33 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com
>>     <mailto:rafik.dammak at gmail.com>>:
>>
>>         Hi Ayden,
>>
>>         Yes it is for PC review. We worked on it the last days with
>>         Juan, Dina and Niels. James cannot response since is off for
>>         the coming days. I was going to send email to related ICANN
>>         staff to inform that we will make a late submission,
>>         hopefully by end of this week.
>>
>>         Best,
>>
>>         Rafik 
>>
>>
>>         On Jul 31, 2017 7:18 PM, "Ayden F?rdeline"
>>         <icann at ferdeline.com <mailto:icann at ferdeline.com>> wrote:
>>
>>             I believe the PC is being asked to review this comment
>>             which has been drafted by Dina and Juan. The submission
>>             deadline for comments on this issue is today, but I
>>             suspect we will not be able to meet that, so let's try
>>             for this Friday? I think we need to bring in a topic
>>             expert, James Gannon (cc'd), to get his opinion on this
>>             comment, too -- because I am happy to raise my hand and
>>             say I do not know anything about this topic. 
>>
>>             Best, Ayden 
>>
>>
>>>             -------- Original Message --------
>>>             Subject: [NCUC-DISCUSS] Suggested Comment: Draft
>>>             Framework for Registry Operators to Respond to Security
>>>             Threats
>>>             Local Time: July 30, 2017 11:24 PM
>>>             UTC Time: July 30, 2017 10:24 PM
>>>             From: thomascovenant at thomascovenant.org
>>>             <mailto:thomascovenant at thomascovenant.org>
>>>             To: NCUC-discuss <ncuc-discuss at lists.ncuc.org
>>>             <mailto:ncuc-discuss at lists.ncuc.org>>
>>>
>>>             Hello,
>>>
>>>             the comment proposal is underneath, what are your thoughts?
>>>
>>>             https://docs.google.com/document/d/1TfgHuMqzD660_CHLQMXMW4phnBtLSP94j6X5riY2Ko4/edit
>>>             <https://docs.google.com/document/d/1TfgHuMqzD660_CHLQMXMW4phnBtLSP94j6X5riY2Ko4/edit>
>>>
>>>             Note from Security Framework Drafting Team wiki workspace:
>>>
>>>             - Is Public Comment required for the draft Framework?
>>>             - This is not a policy implementation nor a contractual
>>>             requirements document; therefore, a public comment
>>>             proceeding would not be required. However, SFDT has
>>>             decided to conduct a public comment for broader
>>>             community feedback prior to finalization of the Framework.
>>>
>>>             Main points:
>>>
>>>             - Framework should be expanded
>>>             - Several minor details are to be clarified,
>>>             restructuring proposal
>>>             - as a small step in response to proposed detailed
>>>             report examination, I suggest we include a
>>>             recommendation on Responsible Threat Disclosure.
>>>
>>>             Finally, I quote Point 3 from the Comment:
>>>
>>>             "Since the following examination of threat report is
>>>             identified in the Framework, we strongly suggest
>>>             including a recommendation on Responsible Threat
>>>             Disclosure to be included in the document:
>>>
>>>             "Each RO should scrutinize, question or otherwise
>>>             inquire about the legitimacy of the origin
>>>             of a request, in accordance with their own internal
>>>             policies and processes."
>>>
>>>             We have seen a broad variation in handling security
>>>             threat reports, varying from constructive actions
>>>             addressing the issues to punishment of the reporting
>>>             party. Benefits of responsible threat submission are
>>>             obvious.
>>>
>>>             In this context, it is important to underline benefits
>>>             and importance of responsible threat disclosure. We
>>>             request recommendation to extend goodwill and not cause
>>>             harm to the reporting party whenever possible:
>>>
>>>             When applicable, RO should provide:
>>>
>>>             - an easy way to report security threats and violation
>>>             - encrypted ways of communication
>>>             - option of anonymous submission"
>>>
>>>             Other:
>>>
>>>             - This is my first comment drafted with input from Juan
>>>             Manuel Rojas (thank you for commenting). Access to
>>>             shared document and request for review was given to
>>>             those who expressed interest in working on it. All input
>>>             from the list is very welcome. Please let me know what
>>>             needs to be corrected and I will promptly do it.
>>>             - Comment is a bit late, I will request an extra week to
>>>             discuss the proposal with my humble excuses.
>>>
>>>             BR,
>>>             Dina Solveig Jalkanen
>>>             -- 
>>>             * * *
>>>             Friendly geek in Amsterdam, FSFE Fellow
>>>             https://wiki.techinc.nl/index.php/User:Thomascovenant
>>>             <https://wiki.techinc.nl/index.php/User:Thomascovenant>
>>>
>>>
>>>             _______________________________________________
>>>             Ncuc-discuss mailing list
>>>             Ncuc-discuss at lists.ncuc.org
>>>             <mailto:Ncuc-discuss at lists.ncuc.org>
>>>             http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>>>             <http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss>
>>
>>
>>             _______________________________________________
>>             NCSG-PC mailing list
>>             NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>             https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>             <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>
>>
>>
>>
>>
>>     _______________________________________________
>>     NCSG-PC mailing list
>>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>     _______________________________________________ NCSG-PC mailing
>     list NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170808/43612d7a/attachment.htm>

From t.tropina at mpicc.de  Tue Aug  8 11:43:17 2017
From: t.tropina at mpicc.de (Dr. Tatiana Tropina)
Date: Tue, 8 Aug 2017 10:43:17 +0200
Subject: [NCSG-PC] Drafting/Documenting NCSG Policy Committee Procedures
In-Reply-To: <CAH5sTh=9zBWYZ0kX7n=aerf7bnkQzgvhqQ_gaU+eMH8tG+VDjQ@mail.gmail.com>
References: <CAH5sThmXLsSxhEv+QwrsqN8vvusFwXaNXJHs2ftdmh=rdMLQRw@mail.gmail.com>
 <CAH5sThkU-gDezYOPoeWd=WH05uFVMpdykH7o+5xWT+=A-DDSGw@mail.gmail.com>
 <49A5EE51-7440-42B3-9BDD-2F3D97CE517B@gmail.com>
 <CAH5sTh=9zBWYZ0kX7n=aerf7bnkQzgvhqQ_gaU+eMH8tG+VDjQ@mail.gmail.com>
Message-ID: <643b4f37-a76c-a52c-d478-10142566ae0b@mpicc.de>

Hi Rafik and Martin, and all, -

as I have experience both with drafting NCUC procedures and PC
experience, am ready to join the drafting team.

Cheers,

Tanya


On 08/08/17 07:44, Rafik Dammak wrote:
> Hi ,
>
> Thanks, Martin,
> I will create a google doc with an outline of those suggestions for
> procedures and add some ideas for each. then share it as a strawman
> document. that will make easier to cooperate on the same document and
> kick-off the discussion.
>
> Best,
>
> Rafik
>
> 2017-08-08 9:57 GMT+09:00 Martin Pablo Silva Valent
> <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>>:
>
>     I can work with Rafik with this, he?s experiences is way over
>     mine, but for the little I can help I think it is an initiative
>     worth working on. 
>
>     Cheers,
>     Mart?n
>
>>     On Aug 7, 2017, at 9:28 PM, Rafik Dammak <rafik.dammak at gmail.com
>>     <mailto:rafik.dammak at gmail.com>> wrote:
>>
>>     Hi all,
>>
>>     I am resending this to resume discussion on drafting procedures
>>     for policy committee work. I volunteered for drafting and hope to
>>     share something soon for review and discussion. 
>>
>>     NCUC used my previous proposal for NCSG comments and tweaked it.
>>     I will use that and add other details such as: creating a
>>     template document for our public statements (similar to what BC
>>     has) and adding an item about a follow-up to check the staff
>>     report to see it includes our comment or not (based on Ayden
>>     question).
>>
>>     any other procedure to suggest to those listed above. I recall
>>     that we discussed last year about communication and I guess we
>>     can add that to the list. maybe it is not procedure per se but
>>     can be seen as guidelines.
>>
>>     Best,
>>
>>     Rafik
>>
>>
>>
>>     2017-05-08 13:58 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com
>>     <mailto:rafik.dammak at gmail.com>>:
>>
>>         hi all,
>>
>>         by the previous discussion we are having lately with regard
>>         to board seat election, SSC appointment, comments
>>         endorsement, involving and engaging NCSG membership, I would
>>         like to propose that we kick-off a discussion on Policy
>>         Committee procedures, processes, working methods, and guidelines.
>>
>>         We can start by listing some items to cover first and work
>>         with NCSG EC for reviewing them and consulting NCSG
>>         membership after agreeing on a tentative timeline to get this
>>         done.
>>
>>         Getting those procedures are overdue and will definitely help
>>         us for our work and it is one of the provision of NCSG
>>         charter to be filled. Some ideas for starters:
>>
>>
>>           * Drafting and approving NCSG Statements
>>           * Council Motions (engage with members and other councilors
>>             on how one intends to vote with rationale)
>>           * Appointments and selection process for NCSG representative
>>           * Decision making
>>           * Board Seat #14 selection process (as internal process)
>>           * GNSO Council Chair and Vice Chair selection process (as
>>             internal process)
>>           * NCSG PC Chair and Vice Chair selection process          
>>                                    
>>
>>         I am volunteering to start drafting a strawman and sharing
>>         that with the policy committee but I am looking for others to
>>         join the effort and volunteer too.
>>
>>         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
>>     <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/20170808/68e0a392/attachment.htm>

From matthew at intpolicy.com  Tue Aug  8 12:14:01 2017
From: matthew at intpolicy.com (Matthew Shears)
Date: Tue, 8 Aug 2017 10:14:01 +0100
Subject: [NCSG-PC] Drafting/Documenting NCSG Policy Committee Procedures
In-Reply-To: <643b4f37-a76c-a52c-d478-10142566ae0b@mpicc.de>
References: <CAH5sThmXLsSxhEv+QwrsqN8vvusFwXaNXJHs2ftdmh=rdMLQRw@mail.gmail.com>
 <CAH5sThkU-gDezYOPoeWd=WH05uFVMpdykH7o+5xWT+=A-DDSGw@mail.gmail.com>
 <49A5EE51-7440-42B3-9BDD-2F3D97CE517B@gmail.com>
 <CAH5sTh=9zBWYZ0kX7n=aerf7bnkQzgvhqQ_gaU+eMH8tG+VDjQ@mail.gmail.com>
 <643b4f37-a76c-a52c-d478-10142566ae0b@mpicc.de>
Message-ID: <3201f649-c1bf-ddfa-59da-37299aaa8d51@intpolicy.com>

I am happy to participate also.


On 08/08/2017 09:43, Dr. Tatiana Tropina wrote:
>
> Hi Rafik and Martin, and all, -
>
> as I have experience both with drafting NCUC procedures and PC 
> experience, am ready to join the drafting team.
>
> Cheers,
>
> Tanya
>
>
> On 08/08/17 07:44, Rafik Dammak wrote:
>> Hi ,
>>
>> Thanks, Martin,
>> I will create a google doc with an outline of those suggestions for 
>> procedures and add some ideas for each. then share it as a strawman 
>> document. that will make easier to cooperate on the same document and 
>> kick-off the discussion.
>>
>> Best,
>>
>> Rafik
>>
>> 2017-08-08 9:57 GMT+09:00 Martin Pablo Silva Valent 
>> <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>>:
>>
>>     I can work with Rafik with this, he?s experiences is way over
>>     mine, but for the little I can help I think it is an initiative
>>     worth working on.
>>
>>     Cheers,
>>     Mart?n
>>
>>>     On Aug 7, 2017, at 9:28 PM, Rafik Dammak <rafik.dammak at gmail.com
>>>     <mailto:rafik.dammak at gmail.com>> wrote:
>>>
>>>     Hi all,
>>>
>>>     I am resending this to resume discussion on drafting procedures
>>>     for policy committee work. I volunteered for drafting and hope
>>>     to share something soon for review and discussion.
>>>
>>>     NCUC used my previous proposal for NCSG comments and tweaked it.
>>>     I will use that and add other details such as: creating a
>>>     template document for our public statements (similar to what BC
>>>     has) and adding an item about a follow-up to check the staff
>>>     report to see it includes our comment or not (based on Ayden
>>>     question).
>>>
>>>     any other procedure to suggest to those listed above. I recall
>>>     that we discussed last year about communication and I guess we
>>>     can add that to the list. maybe it is not procedure per se but
>>>     can be seen as guidelines.
>>>
>>>     Best,
>>>
>>>     Rafik
>>>
>>>
>>>
>>>     2017-05-08 13:58 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com
>>>     <mailto:rafik.dammak at gmail.com>>:
>>>
>>>         hi all,
>>>
>>>         by the previous discussion we are having lately with regard
>>>         to board seat election, SSC appointment, comments
>>>         endorsement, involving and engaging NCSG membership, I would
>>>         like to propose that we kick-off a discussion on Policy
>>>         Committee procedures, processes, working methods, and
>>>         guidelines.
>>>
>>>         We can start by listing some items to cover first and work
>>>         with NCSG EC for reviewing them and consulting NCSG
>>>         membership after agreeing on a tentative timeline to get
>>>         this done.
>>>
>>>         Getting those procedures are overdue and will definitely
>>>         help us for our work and it is one of the provision of NCSG
>>>         charter to be filled. Some ideas for starters:
>>>
>>>
>>>           * Drafting and approving NCSG Statements
>>>           * Council Motions (engage with members and other
>>>             councilors on how one intends to vote with rationale)
>>>           * Appointments and selection process for NCSG representative
>>>           * Decision making
>>>           * Board Seat #14 selection process (as internal process)
>>>           * GNSO Council Chair and Vice Chair selection process (as
>>>             internal process)
>>>           * NCSG PC Chair and Vice Chair selection process
>>>
>>>         I am volunteering to start drafting a strawman and sharing
>>>         that with the policy committee but I am looking for others
>>>         to join the effort and volunteer too.
>>>
>>>         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
>>>     <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
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
> 	Virus-free. www.avg.com 
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

-- 


Matthew Shears
matthew at intpolicy.com
+447712472987
Skype:mshears

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

From pileleji at ymca.gm  Tue Aug  8 13:54:50 2017
From: pileleji at ymca.gm (Poncelet Ileleji)
Date: Tue, 8 Aug 2017 10:54:50 +0000
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
 <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
Message-ID: <CAEux40tHhFRyXLcCCkQ2V1x_VG0ZqM4UiM+OVvKMCgRkT-=stA@mail.gmail.com>

Concur +1

On 7 August 2017 at 20:30, Dr. Tatiana Tropina <t.tropina at mpicc.de> wrote:

> Dear all,
>
> I agree with Martin about Rafik. If he is still interested -- the best way
> to fill in this slot would be to appoint. Him.
>
> Cheers,
>
> Tanya
>
> On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
>
> That process is not there in more, we have to make a new one (remember it
> was questioned and then one of the candidate drop, and then the other also
> refused to finish the process like that). So we have to go from scratch,
> but if Rafik is still interested I would promote to have him considered
> first for many good reasons. If not, the question is if we open the call to
> the list or we keep it in the PC member list (fue to their leadership role
> in ncsg policy make sense they are close enough to be part of the SSC of
> the Council).
>
> Cheers,
> Mart?n
>
> On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji <pileleji at ymca.gm> wrote:
>
> Dear Colleagues
>
> We  know the third slot was stalled?, but as the  process had  started
> already can that processs be completed.
>
> Kind Regards
>
> Poncelet
>
> On 7 August 2017 at 16:17, Martin Pablo Silva Valent <
> mpsilvavalent at gmail.com> wrote:
>
>> Should we open this call to the discuss list or keep it in the pc
>> members? I know we are still a few month from the election, but if no one
>> else steps in one of the candidate that wasn?t elected could have this
>> position.
>>
>> Last time Rafik was in the run for this, if he still wants it he should
>> have priority to be considered.
>>
>> Cheers,
>> Martin
>>
>> > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen <
>> ncsg at tapani.tarvainen.info> wrote:
>> >
>> > Dear PC,
>> >
>> > I've been reminded we still haven't appointed our 3rd representative
>> > to the GNSO Standing Selection Committee.
>> >
>> > It would be nice if we could get it done reasonably soon.
>> >
>> > Cheers,
>> >
>> > --
>> > Tapani Tarvainen
>> > _______________________________________________
>> > 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 <437%200240>
> Fax:(220) 4390793 <439%200793>
> Cell:(220) 9912508 <991%202508>
> 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 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/20170808/3cf46ade/attachment.htm>

From ncsg at tapani.tarvainen.info  Tue Aug  8 14:28:37 2017
From: ncsg at tapani.tarvainen.info (Tapani Tarvainen)
Date: Tue, 8 Aug 2017 14:28:37 +0300
Subject: [NCSG-PC] Fwd: GNSO Council Vice Chair (NCPH) Election Process;
 GNSO Board Seat (NCPH) Election Process
Message-ID: <20170808112837.GA28325@tehanu.it.jyu.fi>

Dear PC,

Please see below and attached. To mee the cleaned version seems
substantively identical with the one we agreed on in Marrakech, but I
invite you all to read between the lines lest some unintended change
has sneaked in.

Thank you,

Tapani

----- Forwarded message from "Wolf-Ulrich.Knoben" <wolf-ulrich.knoben at t-online.de> -----

Dear Tapani,

on behalf of the CSG-ExComm, I'm writing with regards to the election
process for the GNSO council vice chair position. The next election
round is due before the AGM in Abu Dhabi.

You may recall that the NCPH managed to draft a related process at the
last intersessional meeting in Rejkyavik. However although all issues
seemed to be solved we did not yet formally finalize it. It's now the
right time to catch up.

Attached are 1. the last NCSG suggestion from your email from 07 Nov
2017, 2. a version with the language cleaned up a bit (no intention to
modify the substance!), and 3. a comparison of the two. We'd
appreciate the NCSG reviewing this text and commenting asap in order
to get it adopted by the house before the election takes place.

Thanks and regards

Wolf-Ulrich

----- End forwarded message -----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Compare_Final_Draft_v_NCPH_Process.doc
Type: application/msword
Size: 31744 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170808/30aea29d/attachment.doc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Final_Draft_of_NCPH_Process_to_select_GNSO_Council_Vice_Chair.doc
Type: application/msword
Size: 27648 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170808/30aea29d/attachment-0001.doc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NCPH_Process_for_selecting_GNSO_Council_Vice-Chair.doc
Type: application/msword
Size: 28160 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170808/30aea29d/attachment-0002.doc>

From stephanie.perrin at mail.utoronto.ca  Tue Aug  8 18:10:10 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Tue, 8 Aug 2017 11:10:10 -0400
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <CAH5sTh=aVgpE1bT=du+LgbWfSBPgQyVF8hirPuo_EOGzzTq6Jg@mail.gmail.com>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
 <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
 <9Ss39VrjfeqaHXkON9GzqzE7ee1iiGlGgcIENhyto_En1Kd47WjOxlOaEGJ4vz0tsACrIy-KG6PD8JtkOLjJ4N0KZFJoNd_ZSA_EeeB0p5Q=@ferdeline.com>
 <b5da8dba-f02e-944e-bae8-e4f939d09955@mail.utoronto.ca>
 <CAH5sTh=aVgpE1bT=du+LgbWfSBPgQyVF8hirPuo_EOGzzTq6Jg@mail.gmail.com>
Message-ID: <a4711c36-d73a-4ea5-8626-9fdf38c1ddcb@mail.utoronto.ca>

Thanks for agreeing to do this Fik, and yes we definitely need to work 
on our procedures.  I think the webinar used for the Nomcom process was 
a great idea (even though I regret to say I was not on the call).  Folks 
need to have a clear understanding of workload and expectations in all 
these positions.

cheers steph


On 2017-08-08 03:07, Rafik Dammak wrote:
> Hi all,
>
> Thanks for the vote of confidence. I will be glad to appointed as rep 
> to SSC for a period if that helps. However, I still want that we work 
> on general process though for selecting and appointing representatives 
> based on the previous experience (please check the other thread 
> proposing several procedures to work on).
>
> Best,
>
> Rafik
>
>
> 2017-08-08 9:57 GMT+09:00 Stephanie Perrin 
> <stephanie.perrin at mail.utoronto.ca 
> <mailto:stephanie.perrin at mail.utoronto.ca>>:
>
>     +1 for Rafik.
>
>     Stephanie
>
>
>     On 2017-08-07 17:48, Ayden F?rdeline wrote:
>>     +1; appointing Rafik - if he has the bandwidth - is an excellent
>>     idea, Martin.
>>
>>     Best, Ayden
>>
>>>     -------- Original Message --------
>>>     Subject: Re: [NCSG-PC] 3rd SSC representative
>>>     Local Time: 7 August 2017 9:30 PM
>>>     UTC Time: 7 August 2017 20:30
>>>     From: t.tropina at mpicc.de <mailto:t.tropina at mpicc.de>
>>>     To: ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>
>>>
>>>
>>>     Dear all,
>>>
>>>     I agree with Martin about Rafik. If he is still interested --
>>>     the best way to fill in this slot would be to appoint. Him.
>>>
>>>     Cheers,
>>>
>>>     Tanya
>>>
>>>
>>>     On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
>>>>     That process is not there in more, we have to make a new one
>>>>     (remember it was questioned and then one of the candidate drop,
>>>>     and then the other also refused to finish the process like
>>>>     that). So we have to go from scratch, but if Rafik is still
>>>>     interested I would promote to have him considered first for
>>>>     many good reasons. If not, the question is if we open the call
>>>>     to the list or we keep it in the PC member list (fue to their
>>>>     leadership role in ncsg policy make sense they are close enough
>>>>     to be part of the SSC of the Council).
>>>>
>>>>     Cheers,
>>>>     Mart?n
>>>>
>>>>>     On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji <pileleji at ymca.gm
>>>>>     <mailto:pileleji at ymca.gm>> wrote:
>>>>>
>>>>>     Dear Colleagues
>>>>>
>>>>>     We  know the third slot was stalled?, but as the  process had 
>>>>>     started already can that processs be completed.
>>>>>
>>>>>
>>>>>     Kind Regards
>>>>>
>>>>>
>>>>>     Poncelet
>>>>>
>>>>>
>>>>>     On 7 August 2017 at 16:17, Martin Pablo Silva Valent
>>>>>     <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>> wrote:
>>>>>
>>>>>         Should we open this call to the discuss list or keep it in
>>>>>         the pc members? I know we are still a few month from the
>>>>>         election, but if no one else steps in one of the candidate
>>>>>         that wasn?t elected could have this position.
>>>>>
>>>>>         Last time Rafik was in the run for this, if he still wants
>>>>>         it he should have priority to be considered.
>>>>>
>>>>>         Cheers,
>>>>>         Martin
>>>>>
>>>>>
>>>>>         > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen
>>>>>         <ncsg at tapani.tarvainen.info
>>>>>         <mailto:ncsg at tapani.tarvainen.info>> wrote:
>>>>>         >
>>>>>         > Dear PC,
>>>>>         >
>>>>>         > I've been reminded we still haven't appointed our 3rd
>>>>>         representative
>>>>>         > to the GNSO Standing Selection Committee.
>>>>>         >
>>>>>         > It would be nice if we could get it done reasonably soon.
>>>>>         >
>>>>>         > Cheers,
>>>>>         >
>>>>>         > --
>>>>>         > Tapani Tarvainen
>>>>>         > _______________________________________________
>>>>>         > 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>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>     --
>>>>>
>>>>>     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/
>>>>>     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
>>>>>     <http://www.diplointernetgovernance.org/>
>>>>>
>>>>>     *
>>>>>     *
>>>>
>>>>
>>>>
>>>>     _______________________________________________
>>>>     NCSG-PC mailing list
>>>>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>
>>
>>
>>
>>     _______________________________________________
>>     NCSG-PC mailing list
>>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>
>
>     _______________________________________________
>     NCSG-PC mailing list
>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>
>

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

From rafik.dammak at gmail.com  Wed Aug  9 02:17:50 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Wed, 9 Aug 2017 08:17:50 +0900
Subject: [NCSG-PC] Fwd: GNSO Council Vice Chair (NCPH) Election Process;
 GNSO Board Seat (NCPH) Election Process
In-Reply-To: <20170808112837.GA28325@tehanu.it.jyu.fi>
References: <20170808112837.GA28325@tehanu.it.jyu.fi>
Message-ID: <CAH5sThkGm-Bui2USr2P7__XeohspiR1E4jBje2vLKw2LEaRxxQ@mail.gmail.com>

Hi Tapani,

Thanks,
are you sure that we agreed on this in Marrakech since it mentions Iceland
(February 2016) and November 2016?
anyway, I didn't notice too much difference in the compare/clean versions.
maybe English native speakers can spot something of concern (in particular
for point #10).

Best,

Rafik

2017-08-08 20:28 GMT+09:00 Tapani Tarvainen <ncsg at tapani.tarvainen.info>:

> Dear PC,
>
> Please see below and attached. To mee the cleaned version seems
> substantively identical with the one we agreed on in Marrakech, but I
> invite you all to read between the lines lest some unintended change
> has sneaked in.
>
> Thank you,
>
> Tapani
>
> ----- Forwarded message from "Wolf-Ulrich.Knoben" <
> wolf-ulrich.knoben at t-online.de> -----
>
> Dear Tapani,
>
> on behalf of the CSG-ExComm, I'm writing with regards to the election
> process for the GNSO council vice chair position. The next election
> round is due before the AGM in Abu Dhabi.
>
> You may recall that the NCPH managed to draft a related process at the
> last intersessional meeting in Rejkyavik. However although all issues
> seemed to be solved we did not yet formally finalize it. It's now the
> right time to catch up.
>
> Attached are 1. the last NCSG suggestion from your email from 07 Nov
> 2017, 2. a version with the language cleaned up a bit (no intention to
> modify the substance!), and 3. a comparison of the two. We'd
> appreciate the NCSG reviewing this text and commenting asap in order
> to get it adopted by the house before the election takes place.
>
> Thanks and regards
>
> Wolf-Ulrich
>
> ----- End forwarded message -----
>
> _______________________________________________
> 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/20170809/84087b89/attachment.htm>

From rafik.dammak at gmail.com  Wed Aug  9 05:50:17 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Wed, 9 Aug 2017 11:50:17 +0900
Subject: [NCSG-PC] Fw: [NCUC-DISCUSS] Suggested Comment: Draft Framework
 for Registry Operators to Respond to Security Threats
In-Reply-To: <bbfbde23-e878-5983-a225-ca39a4667609@mpicc.de>
References: <E1dbwdr-0005N3-F2@rmmprod06.runbox>
 <viDG_GKZm4MGicRFTne3yEZERwqRoqEYGvaYOBiMDIBmcXZpK3WOzB89GoIPEZ-HorUP_hvNPo6oJg4a9RcFT5qyvmWxwgkO61QEWNen_l4=@ferdeline.com>
 <CAH5sThktSm3qRv-1UH9sOEH0R4j4G4aev73XYTE70Zvn9OgSpw@mail.gmail.com>
 <CAH5sThmx08DOsLL4AbzAeyJF9-YEQLjqy0hbyZALxT5=cGr6kA@mail.gmail.com>
 <9814ecaf-9030-2ee6-a39e-176775c71e01@mpicc.de>
 <CAH5sTh=5RcbZeHpMqZAtS-h9Uru0jx_huPEi6o=sj7x4eouiCw@mail.gmail.com>
 <bbfbde23-e878-5983-a225-ca39a4667609@mpicc.de>
Message-ID: <CAH5sThmGu1eJtSNBzjUjAGC=TzFNyuRWqF5FO78zMhTvxAYpVQ@mail.gmail.com>

hi Tatiana,

thanks, I removed those 2 statements and we have this version now
https://docs.google.com/document/d/1TfgHuMqzD660_CHLQMXMW4phnBtLSP94j6X5riY2Ko4/edit
. with those changes, I can understand that you are supporting the comment.
looking to hear from other PC members.
if I don't hear any objection by Wednesday 9th August 11:59am UTC, I can
interpret that the comment is endorsed by NCSG Policy committee.

Best,

Rafik

2017-08-08 17:40 GMT+09:00 Dr. Tatiana Tropina <t.tropina at mpicc.de>:

> Hi Rafik,
>
> As I said - I do not quite get what the first statement means in terms of
> issues raised so I can't come up with any suggestion. I wish I could. As
> this statement doesn't really contribute to anything and doesn't raise any
> issue (although it's supposed to as it is placed in the "issue" section) I
> suggest we just remove it for the sake of clarity. Unless the drafters are
> ready to clarify or rephrase. But I don't think removal will change
> anything in the document except making it clearer.
>
> I am totally supporting your suggestion for removal of anotehr statement -
> let's not send the mix messages especially with vague wording proposals.
>
> Thanks!
>
> Tanya
>
> On 08/08/17 08:08, Rafik Dammak wrote:
>
> Hi Tatiana,
>
> Thanks for the comments,
> while we are late by our deadline to submit a comment, I think we can
> solve the concerns.
> 1/ do you have a proposal of rephrasing for the first statement?
> 2/ I understand your concerns and indeed doesn't seem aligned with our
> previous stances regarding domain suspension. probably we can remove that.
>
> really looking forward to solving this within the next 24hours.
>
> Best,
>
> Rafik
> 2017-08-05 6:56 GMT+09:00 Dr. Tatiana Tropina <t.tropina at mpicc.de>:
>
>> Hi all,
>>
>> I have a couple of comments:
>>
>> 1) I have hard time making sense of the first point:
>>
>> "1. Registry Response, Responsible Parties
>>
>>  ?ROs are not necessarily the best parties to address certain security
>> threats. The identification of the parties considered as being most
>> relevant and appropriate in resolving the security threat is critical to
>> the prompt resolution of the matter.?
>>
>> More specifically, responsibility of identifying security threats
>> connected to New gTLDs and resolving them when possible rests with ROs."
>>
>> As this point is a part of the comment that refers to the "issue" I
>> wonder what is this - a statement? What kind of issue is identified here?
>> Are we recommending anything?  If not and if this is just an introduction,
>> may be it's better to rephrase? May be it's just too late here but I
>> struggling with what this "issue" implies.
>>
>> 2) I wonder if this one is really in line with NSCG values such as due
>> process:
>>
>> 2. We ask you to consider including the following GAC recommendation in
>> Registry Response:
>>
>> ?If Registry operator identifies risk of  harm, Registry operator will
>> notify the relevant registrar and , if the registrar does not take
>> immediate action, suspend the domain name until the matter is resolved.?
>>
>> The framework already lists the actions that Registry can take even in
>> the case if "a negative or non-existent response from the Registrar", which
>> "should not
>> preclude the Registry from taking action". I do not like the notion of
>> "immediate action" as it sound to vague to me and I believe that there are
>> enough actions listed to address the issue under the framework rather than
>> suspension of domain name - again, "till the matter is resolved" looks too
>> vague. I don't think it's acceptable when it comes to such a matter as a
>> suspension of domain name. I know enough cases of mistakes when due to
>> abuse claims customers went dark, etc. I suggest we rather be careful here.
>> But if everyone is comfortable with this suggestion, I'll surrender.
>>
>> Warm regards,
>>
>> Tanya
>>
>>
>>
>> On 04/08/17 09:39, Rafik Dammak wrote:
>>
>> Dear PC members,
>>
>> any comment on the draft? we got an extension till 6th August, we should
>> review quickly and make a decision.
>>
>> Best,
>>
>> Rafik
>>
>> 2017-07-31 19:33 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:
>>
>>> Hi Ayden,
>>>
>>> Yes it is for PC review. We worked on it the last days with Juan, Dina
>>> and Niels. James cannot response since is off for the coming days. I was
>>> going to send email to related ICANN staff to inform that we will make a
>>> late submission, hopefully by end of this week.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>>
>>> On Jul 31, 2017 7:18 PM, "Ayden F?rdeline" <icann at ferdeline.com> wrote:
>>>
>>> I believe the PC is being asked to review this comment which has been
>>> drafted by Dina and Juan. The submission deadline for comments on this
>>> issue is today, but I suspect we will not be able to meet that, so let's
>>> try for this Friday? I think we need to bring in a topic expert, James
>>> Gannon (cc'd), to get his opinion on this comment, too -- because I am
>>> happy to raise my hand and say I do not know anything about this topic.
>>>
>>> Best, Ayden
>>>
>>>
>>> -------- Original Message --------
>>> Subject: [NCUC-DISCUSS] Suggested Comment: Draft Framework for Registry
>>> Operators to Respond to Security Threats
>>> Local Time: July 30, 2017 11:24 PM
>>> UTC Time: July 30, 2017 10:24 PM
>>> From: thomascovenant at thomascovenant.org
>>> To: NCUC-discuss <ncuc-discuss at lists.ncuc.org>
>>>
>>> Hello,
>>>
>>> the comment proposal is underneath, what are your thoughts?
>>>
>>> https://docs.google.com/document/d/1TfgHuMqzD660_CHLQMXMW4ph
>>> nBtLSP94j6X5riY2Ko4/edit
>>>
>>> Note from Security Framework Drafting Team wiki workspace:
>>>
>>> - Is Public Comment required for the draft Framework?
>>> - This is not a policy implementation nor a contractual requirements
>>> document; therefore, a public comment proceeding would not be required.
>>> However, SFDT has decided to conduct a public comment for broader community
>>> feedback prior to finalization of the Framework.
>>>
>>> Main points:
>>>
>>> - Framework should be expanded
>>> - Several minor details are to be clarified, restructuring proposal
>>> - as a small step in response to proposed detailed report examination, I
>>> suggest we include a recommendation on Responsible Threat Disclosure.
>>>
>>> Finally, I quote Point 3 from the Comment:
>>>
>>> "Since the following examination of threat report is identified in the
>>> Framework, we strongly suggest including a recommendation on Responsible
>>> Threat Disclosure to be included in the document:
>>>
>>> "Each RO should scrutinize, question or otherwise inquire about the
>>> legitimacy of the origin
>>> of a request, in accordance with their own internal policies and
>>> processes."
>>>
>>> We have seen a broad variation in handling security threat reports,
>>> varying from constructive actions addressing the issues to punishment of
>>> the reporting party. Benefits of responsible threat submission are obvious.
>>>
>>> In this context, it is important to underline benefits and importance of
>>> responsible threat disclosure. We request recommendation to extend goodwill
>>> and not cause harm to the reporting party whenever possible:
>>>
>>> When applicable, RO should provide:
>>>
>>> - an easy way to report security threats and violation
>>> - encrypted ways of communication
>>> - option of anonymous submission"
>>>
>>> Other:
>>>
>>> - This is my first comment drafted with input from Juan Manuel Rojas
>>> (thank you for commenting). Access to shared document and request for
>>> review was given to those who expressed interest in working on it. All
>>> input from the list is very welcome. Please let me know what needs to be
>>> corrected and I will promptly do it.
>>> - Comment is a bit late, I will request an extra week to discuss the
>>> proposal with my humble excuses.
>>>
>>> BR,
>>> Dina Solveig Jalkanen
>>> --
>>> * * *
>>> Friendly geek in Amsterdam, FSFE Fellow
>>> https://wiki.techinc.nl/index.php/User:Thomascovenant
>>>
>>>
>>> _______________________________________________
>>> Ncuc-discuss mailing list
>>> Ncuc-discuss at lists.ncuc.org
>>> http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 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/20170809/8a633bda/attachment.htm>

From ncsg at tapani.tarvainen.info  Wed Aug  9 08:06:15 2017
From: ncsg at tapani.tarvainen.info (Tapani Tarvainen)
Date: Wed, 9 Aug 2017 08:06:15 +0300
Subject: [NCSG-PC] Fwd: GNSO Council Vice Chair (NCPH) Election Process;
 GNSO Board Seat (NCPH) Election Process
In-Reply-To: <CAH5sThkGm-Bui2USr2P7__XeohspiR1E4jBje2vLKw2LEaRxxQ@mail.gmail.com>
References: <20170808112837.GA28325@tehanu.it.jyu.fi>
 <CAH5sThkGm-Bui2USr2P7__XeohspiR1E4jBje2vLKw2LEaRxxQ@mail.gmail.com>
Message-ID: <20170809050615.xmr3ocozwoy3pnek@tarvainen.info>

Hi Rafik,

The reference to Iceland is about the board member selection procedure,
which we discussed there but didn't agree on (and still haven't).

But you are right that it wasn't in Marrakech where the Vice Chair
procedure was agreed on, but in Hyderabad (November 2016).
My apologies for the mistake.

Tapani

On Wed, Aug 09, 2017 at 08:17:50AM +0900, Rafik Dammak (rafik.dammak at gmail.com) wrote:
> 
> Hi Tapani,
> 
> Thanks,
> are you sure that we agreed on this in Marrakech since it mentions Iceland
> (February 2016) and November 2016?
> anyway, I didn't notice too much difference in the compare/clean versions.
> maybe English native speakers can spot something of concern (in particular
> for point #10).
> 
> Best,
> 
> Rafik
> 
> 2017-08-08 20:28 GMT+09:00 Tapani Tarvainen <ncsg at tapani.tarvainen.info>:
> 
> > Dear PC,
> >
> > Please see below and attached. To mee the cleaned version seems
> > substantively identical with the one we agreed on in Marrakech, but I
> > invite you all to read between the lines lest some unintended change
> > has sneaked in.
> >
> > Thank you,
> >
> > Tapani
> >
> > ----- Forwarded message from "Wolf-Ulrich.Knoben" <
> > wolf-ulrich.knoben at t-online.de> -----
> >
> > Dear Tapani,
> >
> > on behalf of the CSG-ExComm, I'm writing with regards to the election
> > process for the GNSO council vice chair position. The next election
> > round is due before the AGM in Abu Dhabi.
> >
> > You may recall that the NCPH managed to draft a related process at the
> > last intersessional meeting in Rejkyavik. However although all issues
> > seemed to be solved we did not yet formally finalize it. It's now the
> > right time to catch up.
> >
> > Attached are 1. the last NCSG suggestion from your email from 07 Nov
> > 2017, 2. a version with the language cleaned up a bit (no intention to
> > modify the substance!), and 3. a comparison of the two. We'd
> > appreciate the NCSG reviewing this text and commenting asap in order
> > to get it adopted by the house before the election takes place.
> >
> > Thanks and regards
> >
> > Wolf-Ulrich
> >
> > ----- End forwarded message -----
> >
> > _______________________________________________
> > NCSG-PC mailing list
> > NCSG-PC at lists.ncsg.is
> > https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> >
> >

-- 
Tapani Tarvainen


From rafik.dammak at gmail.com  Thu Aug 10 02:52:19 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 10 Aug 2017 08:52:19 +0900
Subject: [NCSG-PC] Fw: [NCUC-DISCUSS] Suggested Comment: Draft Framework
 for Registry Operators to Respond to Security Threats
In-Reply-To: <CAH5sThmGu1eJtSNBzjUjAGC=TzFNyuRWqF5FO78zMhTvxAYpVQ@mail.gmail.com>
References: <E1dbwdr-0005N3-F2@rmmprod06.runbox>
 <viDG_GKZm4MGicRFTne3yEZERwqRoqEYGvaYOBiMDIBmcXZpK3WOzB89GoIPEZ-HorUP_hvNPo6oJg4a9RcFT5qyvmWxwgkO61QEWNen_l4=@ferdeline.com>
 <CAH5sThktSm3qRv-1UH9sOEH0R4j4G4aev73XYTE70Zvn9OgSpw@mail.gmail.com>
 <CAH5sThmx08DOsLL4AbzAeyJF9-YEQLjqy0hbyZALxT5=cGr6kA@mail.gmail.com>
 <9814ecaf-9030-2ee6-a39e-176775c71e01@mpicc.de>
 <CAH5sTh=5RcbZeHpMqZAtS-h9Uru0jx_huPEi6o=sj7x4eouiCw@mail.gmail.com>
 <bbfbde23-e878-5983-a225-ca39a4667609@mpicc.de>
 <CAH5sThmGu1eJtSNBzjUjAGC=TzFNyuRWqF5FO78zMhTvxAYpVQ@mail.gmail.com>
Message-ID: <CAH5sThkc9n2q2CiCGrqagMz+O6N7F8rnsYcfUtp5M-=krMs1Lw@mail.gmail.com>

Hi all,

as the deadline already passed with no objection made on the list, I
submitted the attached comment.
Thanks.

Best,

Rafik

2017-08-09 11:50 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:

> hi Tatiana,
>
> thanks, I removed those 2 statements and we have this version now
> https://docs.google.com/document/d/1TfgHuMqzD660_
> CHLQMXMW4phnBtLSP94j6X5riY2Ko4/edit . with those changes, I can
> understand that you are supporting the comment. looking to hear from
> other PC members.
> if I don't hear any objection by Wednesday 9th August 11:59am UTC, I can
> interpret that the comment is endorsed by NCSG Policy committee.
>
> Best,
>
> Rafik
>
>
> 2017-08-08 17:40 GMT+09:00 Dr. Tatiana Tropina <t.tropina at mpicc.de>:
>
>> Hi Rafik,
>>
>> As I said - I do not quite get what the first statement means in terms of
>> issues raised so I can't come up with any suggestion. I wish I could. As
>> this statement doesn't really contribute to anything and doesn't raise any
>> issue (although it's supposed to as it is placed in the "issue" section) I
>> suggest we just remove it for the sake of clarity. Unless the drafters are
>> ready to clarify or rephrase. But I don't think removal will change
>> anything in the document except making it clearer.
>>
>> I am totally supporting your suggestion for removal of anotehr statement
>> - let's not send the mix messages especially with vague wording proposals.
>>
>> Thanks!
>>
>> Tanya
>>
>> On 08/08/17 08:08, Rafik Dammak wrote:
>>
>> Hi Tatiana,
>>
>> Thanks for the comments,
>> while we are late by our deadline to submit a comment, I think we can
>> solve the concerns.
>> 1/ do you have a proposal of rephrasing for the first statement?
>> 2/ I understand your concerns and indeed doesn't seem aligned with our
>> previous stances regarding domain suspension. probably we can remove that.
>>
>> really looking forward to solving this within the next 24hours.
>>
>> Best,
>>
>> Rafik
>> 2017-08-05 6:56 GMT+09:00 Dr. Tatiana Tropina <t.tropina at mpicc.de>:
>>
>>> Hi all,
>>>
>>> I have a couple of comments:
>>>
>>> 1) I have hard time making sense of the first point:
>>>
>>> "1. Registry Response, Responsible Parties
>>>
>>>  ?ROs are not necessarily the best parties to address certain security
>>> threats. The identification of the parties considered as being most
>>> relevant and appropriate in resolving the security threat is critical to
>>> the prompt resolution of the matter.?
>>>
>>> More specifically, responsibility of identifying security threats
>>> connected to New gTLDs and resolving them when possible rests with ROs."
>>>
>>> As this point is a part of the comment that refers to the "issue" I
>>> wonder what is this - a statement? What kind of issue is identified here?
>>> Are we recommending anything?  If not and if this is just an introduction,
>>> may be it's better to rephrase? May be it's just too late here but I
>>> struggling with what this "issue" implies.
>>>
>>> 2) I wonder if this one is really in line with NSCG values such as due
>>> process:
>>>
>>> 2. We ask you to consider including the following GAC recommendation in
>>> Registry Response:
>>>
>>> ?If Registry operator identifies risk of  harm, Registry operator will
>>> notify the relevant registrar and , if the registrar does not take
>>> immediate action, suspend the domain name until the matter is resolved.?
>>>
>>> The framework already lists the actions that Registry can take even in
>>> the case if "a negative or non-existent response from the Registrar", which
>>> "should not
>>> preclude the Registry from taking action". I do not like the notion of
>>> "immediate action" as it sound to vague to me and I believe that there are
>>> enough actions listed to address the issue under the framework rather than
>>> suspension of domain name - again, "till the matter is resolved" looks too
>>> vague. I don't think it's acceptable when it comes to such a matter as a
>>> suspension of domain name. I know enough cases of mistakes when due to
>>> abuse claims customers went dark, etc. I suggest we rather be careful here.
>>> But if everyone is comfortable with this suggestion, I'll surrender.
>>>
>>> Warm regards,
>>>
>>> Tanya
>>>
>>>
>>>
>>> On 04/08/17 09:39, Rafik Dammak wrote:
>>>
>>> Dear PC members,
>>>
>>> any comment on the draft? we got an extension till 6th August, we should
>>> review quickly and make a decision.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> 2017-07-31 19:33 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:
>>>
>>>> Hi Ayden,
>>>>
>>>> Yes it is for PC review. We worked on it the last days with Juan, Dina
>>>> and Niels. James cannot response since is off for the coming days. I was
>>>> going to send email to related ICANN staff to inform that we will make a
>>>> late submission, hopefully by end of this week.
>>>>
>>>> Best,
>>>>
>>>> Rafik
>>>>
>>>>
>>>> On Jul 31, 2017 7:18 PM, "Ayden F?rdeline" <icann at ferdeline.com> wrote:
>>>>
>>>> I believe the PC is being asked to review this comment which has been
>>>> drafted by Dina and Juan. The submission deadline for comments on this
>>>> issue is today, but I suspect we will not be able to meet that, so let's
>>>> try for this Friday? I think we need to bring in a topic expert, James
>>>> Gannon (cc'd), to get his opinion on this comment, too -- because I am
>>>> happy to raise my hand and say I do not know anything about this topic.
>>>>
>>>> Best, Ayden
>>>>
>>>>
>>>> -------- Original Message --------
>>>> Subject: [NCUC-DISCUSS] Suggested Comment: Draft Framework for Registry
>>>> Operators to Respond to Security Threats
>>>> Local Time: July 30, 2017 11:24 PM
>>>> UTC Time: July 30, 2017 10:24 PM
>>>> From: thomascovenant at thomascovenant.org
>>>> To: NCUC-discuss <ncuc-discuss at lists.ncuc.org>
>>>>
>>>> Hello,
>>>>
>>>> the comment proposal is underneath, what are your thoughts?
>>>>
>>>> https://docs.google.com/document/d/1TfgHuMqzD660_CHLQMXMW4ph
>>>> nBtLSP94j6X5riY2Ko4/edit
>>>>
>>>> Note from Security Framework Drafting Team wiki workspace:
>>>>
>>>> - Is Public Comment required for the draft Framework?
>>>> - This is not a policy implementation nor a contractual requirements
>>>> document; therefore, a public comment proceeding would not be required.
>>>> However, SFDT has decided to conduct a public comment for broader community
>>>> feedback prior to finalization of the Framework.
>>>>
>>>> Main points:
>>>>
>>>> - Framework should be expanded
>>>> - Several minor details are to be clarified, restructuring proposal
>>>> - as a small step in response to proposed detailed report examination,
>>>> I suggest we include a recommendation on Responsible Threat Disclosure.
>>>>
>>>> Finally, I quote Point 3 from the Comment:
>>>>
>>>> "Since the following examination of threat report is identified in the
>>>> Framework, we strongly suggest including a recommendation on Responsible
>>>> Threat Disclosure to be included in the document:
>>>>
>>>> "Each RO should scrutinize, question or otherwise inquire about the
>>>> legitimacy of the origin
>>>> of a request, in accordance with their own internal policies and
>>>> processes."
>>>>
>>>> We have seen a broad variation in handling security threat reports,
>>>> varying from constructive actions addressing the issues to punishment of
>>>> the reporting party. Benefits of responsible threat submission are obvious.
>>>>
>>>> In this context, it is important to underline benefits and importance
>>>> of responsible threat disclosure. We request recommendation to extend
>>>> goodwill and not cause harm to the reporting party whenever possible:
>>>>
>>>> When applicable, RO should provide:
>>>>
>>>> - an easy way to report security threats and violation
>>>> - encrypted ways of communication
>>>> - option of anonymous submission"
>>>>
>>>> Other:
>>>>
>>>> - This is my first comment drafted with input from Juan Manuel Rojas
>>>> (thank you for commenting). Access to shared document and request for
>>>> review was given to those who expressed interest in working on it. All
>>>> input from the list is very welcome. Please let me know what needs to be
>>>> corrected and I will promptly do it.
>>>> - Comment is a bit late, I will request an extra week to discuss the
>>>> proposal with my humble excuses.
>>>>
>>>> BR,
>>>> Dina Solveig Jalkanen
>>>> --
>>>> * * *
>>>> Friendly geek in Amsterdam, FSFE Fellow
>>>> https://wiki.techinc.nl/index.php/User:Thomascovenant
>>>>
>>>>
>>>> _______________________________________________
>>>> Ncuc-discuss mailing list
>>>> Ncuc-discuss at lists.ncuc.org
>>>> http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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 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/20170810/6fae6587/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Draft Framework for the Registry Operator to Respond to Security Threats - NCSG comment.pdf
Type: application/pdf
Size: 73275 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170810/6fae6587/attachment.pdf>

From rafik.dammak at gmail.com  Thu Aug 10 03:03:03 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 10 Aug 2017 09:03:03 +0900
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating procedures
	change
Message-ID: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>

Hi all,

the deadline for submission is this Friday. I attached the clean version
for review. I understand that Matt, Poncelet, Stephanie support the
comment. we need to hear from other PC members.

Best,

Rafik

2017-08-07 23:24 GMT+09:00 Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca>:

> I think that is a really good idea, as these are important procedures, and
> we need to be able to amend if required.  Hard to anticipate everything, in
> my view...
>
> SP
>
> On 2017-08-07 08:49, farzaneh badii wrote:
>
> Hi
>
> I was on the DT group. I don't have the time to go through every single
> change and see if they accord with what we agreed on. If you want in the
> public comment we should ask that if later on during implementing the
> operating procedures we find out that  changes recommended by  DT   for
> some reason are not reflected in the new  GNSO operating procedures, GNSO
> should follow the DT advice in those circumstances and allow for the
> mistake to be corrected.
>
> Farzaneh
>
> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <stephanie.perrin at mail.
> utoronto.ca> wrote:
>
>> It looks fine to me.  I don't have knowledge of or time to do the
>> research on the issues at the moment, so I hope that those who do can catch
>> things that need changes.
>>
>> cheers Stephanie
>>
>> On 2017-08-07 02:07, Rafik Dammak wrote:
>>
>> Hi,
>>
>> the comment is quite straightforward and supporting the changes outlined
>> in the public consultation.
>> we can have as the deadline for review and endorsement the 9th August. I
>> urge councilors, in particular, to review the changes since it concerns the
>> operating procedures.
>> Thanks, Matt again for the draft. I resolved the edits made by Ayden. ant
>> proof-reading and review would be helpful.
>>
>> Best,
>>
>> Rafik
>>
>> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>
>>> Hi all,
>>>
>>> I have made some minor alterations to style, but added nothing of
>>> substance. I hope someone with more knowledge of this issue will be able to
>>> contribute to our comment. Submissions are due in six days time. Thanks!
>>>
>>> Best wishes, Ayden
>>>
>>>
>>> -------- Original Message --------
>>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures change
>>> Local Time: August 1, 2017 5:35 PM
>>> UTC Time: August 1, 2017 4:35 PM
>>> From: matthew at intpolicy.com
>>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM>
>>>
>>>
>>> Hi all
>>>
>>> Wanted to get this back at the top of the list of to-do's as time is
>>> running out.
>>>
>>> Appreciate the comments from some of the PC members but would welcome
>>> additional inputs, thoughts, etc.
>>>
>>> See google doc below.
>>>
>>> Thanks.
>>>
>>> Matthew
>>>
>>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>
>>> Matt,
>>> I don?t have any comment to do, I agree with the statements and the
>>> wording. Let me know if I can do anything specific to help. Other than that
>>> you have my support. Thanks!
>>>
>>> Cheers,
>>> Mart?n
>>>
>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com>
>>> wrote:
>>>
>>> Hi,
>>>
>>> the deadline for the public comment is the 10th of August, we have to
>>> finish consulting with NCSG members, review and endorsement prior to that.
>>> I suggest 8th August as our internal deadline.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>>
>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>>
>>> Hi Matt, thanks. What's the deadline for this? I am in transit (and in
>>>> fact, on holiday), witch sketchy internet access and the doc doesn't open
>>>> for me today (might be the poor connection...)
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com>
>>>> wrote:
>>>>
>>>> Let me qualify the last sentence - ICANN staff are not adding new items
>>>> in addition to the work of the DT, but rather adding references to work
>>>> done previously.
>>>>
>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>
>>>> Calling all PCers
>>>>
>>>> I have started on the above public comment but am still going through
>>>> the consultation docs.  However, time marches on and we need to get this
>>>> one underway.
>>>>
>>>> So, please review the consultation docs here:
>>>>
>>>> https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>
>>>> And make comments in the google doc here:
>>>>
>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>>> -ddk_Q9DWja7bZIgsiY/edit
>>>> Note that ICANN staff have used this opportunity to include other
>>>> changes that the DT did not discuss.
>>>>
>>>> Many thanks.
>>>>
>>>> Matthew
>>>>
>>>>
>>>>
>>>> --
>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>
>>>>
>>>> --
>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>>
>>>>
>>>> The information transmitted is intended only for the person or entity
>>>> to which it is addressed and may contain confidential and/or privileged
>>>> material. Any review, retransmission, dissemination, distribution,
>>>> forwarding, or other use of, or taking of any action in reliance upon, this
>>>> information by persons or entities other than the intended recipient is
>>>> prohibited without the express permission of the sender. If you received
>>>> this communication in error, please contact the sender and delete the
>>>> material from any computer.
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>>
>>>
>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>> Virus-free. www.avg.com
>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>
>>>
>>>
>>> _______________________________________________
>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>>
>>> --
>>>
>>>
>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 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/20170810/62b2a9f8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GNSO Operating Procedures and ICANN Bylaws - NCSG Comment.pdf
Type: application/pdf
Size: 65127 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170810/62b2a9f8/attachment.pdf>

From rafik.dammak at gmail.com  Thu Aug 10 03:31:44 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 10 Aug 2017 09:31:44 +0900
Subject: [NCSG-PC] CCWG-IG motion amendments
In-Reply-To: <CAH5sTh=nhNnZEXoBHV=tc5G7XmQYOAiRu6JF2679fFxQanHY-w@mail.gmail.com>
References: <CAH5sTh=nhNnZEXoBHV=tc5G7XmQYOAiRu6JF2679fFxQanHY-w@mail.gmail.com>
Message-ID: <CAH5sThkpU34JtOk9pVyCSVMJ7PAPZXrFgh+itD=jAFr7oXRW9Q@mail.gmail.com>

Hi all,

are you ok with the proposed amendments
https://docs.google.com/document/d/1LQWVaEgppF38Gvnm9SpvftHpdhI1BOGdRdl_YyBe3oA/edit?
we should submit them by the deadline Monday 14th August to be taken into
account.

Best,

Rafik

2017-07-14 8:32 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:

> Hi all,
>
> as you know, we asked for the CCWG-IG motion to be deferred so we can
> continue working on our amendments. that was supported by other groups like
> IPC due to the short time we had since Johannesburg meeting.
>
> Marilia, Farzaneh and I worked on making some amendments to the motion as
> follow-up of our NCSG Policy call this week https://docs.google.com/
> document/d/1LQWVaEgppF38Gvnm9SpvftHpdhI1BOGdRdl_YyBe3oA/edit
>
> we are sharing this so we can discuss them. we will also share them with
> the wider NCSG list.
>
> Best,
>
> Rafik
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170810/c52a6839/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Thu Aug 10 04:34:48 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Wed, 9 Aug 2017 21:34:48 -0400
Subject: [NCSG-PC] CCWG-IG motion amendments
In-Reply-To: <CAH5sThkpU34JtOk9pVyCSVMJ7PAPZXrFgh+itD=jAFr7oXRW9Q@mail.gmail.com>
References: <CAH5sTh=nhNnZEXoBHV=tc5G7XmQYOAiRu6JF2679fFxQanHY-w@mail.gmail.com>
 <CAH5sThkpU34JtOk9pVyCSVMJ7PAPZXrFgh+itD=jAFr7oXRW9Q@mail.gmail.com>
Message-ID: <1e174dac-6ee7-f19c-4101-c0b7889a5f05@mail.utoronto.ca>

There is a typo in the thrid para, amtrying to get edit access to fix a 
few things. More important question is exactly what model did we have in 
mind, if not a CCWG???

cheers Steph


On 2017-08-09 20:31, Rafik Dammak wrote:
> Hi all,
>
> are you ok with the proposed amendments 
> https://docs.google.com/document/d/1LQWVaEgppF38Gvnm9SpvftHpdhI1BOGdRdl_YyBe3oA/edit? 
> we should submit them by the deadline Monday 14th August to be taken 
> into account.
>
> Best,
>
> Rafik
>
> 2017-07-14 8:32 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com 
> <mailto:rafik.dammak at gmail.com>>:
>
>     Hi all,
>
>     as you know, we asked for the CCWG-IG motion to be deferred so we
>     can continue working on our amendments. that was supported by
>     other groups like IPC due to the short time we had since
>     Johannesburg meeting.
>
>     Marilia, Farzaneh and I worked on making some amendments to the
>     motion as follow-up of our NCSG Policy call this week
>     https://docs.google.com/document/d/1LQWVaEgppF38Gvnm9SpvftHpdhI1BOGdRdl_YyBe3oA/edit
>     <https://docs.google.com/document/d/1LQWVaEgppF38Gvnm9SpvftHpdhI1BOGdRdl_YyBe3oA/edit>
>
>     we are sharing this so we can discuss them. we will also share
>     them with the wider NCSG list.
>
>     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/20170809/e118d67a/attachment.htm>

From rafik.dammak at gmail.com  Thu Aug 10 04:54:28 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 10 Aug 2017 10:54:28 +0900
Subject: [NCSG-PC] CCWG-IG motion amendments
In-Reply-To: <1e174dac-6ee7-f19c-4101-c0b7889a5f05@mail.utoronto.ca>
References: <CAH5sTh=nhNnZEXoBHV=tc5G7XmQYOAiRu6JF2679fFxQanHY-w@mail.gmail.com>
 <CAH5sThkpU34JtOk9pVyCSVMJ7PAPZXrFgh+itD=jAFr7oXRW9Q@mail.gmail.com>
 <1e174dac-6ee7-f19c-4101-c0b7889a5f05@mail.utoronto.ca>
Message-ID: <CAH5sTh=ceUbVxVCRDfapyhAozGwKfxuceEe3FA-k6f8e8XqYaw@mail.gmail.com>

Hi Stephanie,

if you recall in Hyderabad, Council asked the working group to align itself
with the uniform framework for CCWG. the working group did a review of its
charter and amended following the framework model (using a charter
template). the amended charter was submitted in Copenhagen meeting.

several councilors are still not satisfied with that and the request now
with this motion is to suggest a new vehicle which is not CCWG but
responding to other requirements and improving accountability and reporting
mechanisms, also about submitting positions on behalf of the community and
how to come back to charter organizations.

The working group had a discussion of the matter and we think we can found
out a new structure having a cross-community structure but not necessarily
a CCWG. There is no model yet and the working group will be tasked to make
a proposal. GNSO created previously several structures such as standing
committee etc (a long list), so the CCWG-IG will end up a new one to the
GNSO structures fauna. basically, it will be like a CCWG, behaving as CCWG
but not having the name of CCWG...

to be more candid and more direct,  several groups within GNSO are
concerned that CCWG becomes more and more the model for any work including
PDP. you can see similar concerns about the subpro WG working track 5
on geonames.

Best,

Rafik

ps I changed the permissions in the google doc, you should be able to
comment there

2017-08-10 10:34 GMT+09:00 Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca>:

> There is a typo in the thrid para, amtrying to get edit access to fix a
> few things.  More important question is exactly what model did we have in
> mind, if not a CCWG???
>
> cheers Steph
>
> On 2017-08-09 20:31, Rafik Dammak wrote:
>
> Hi all,
>
> are you ok with the proposed amendments https://docs.google.com/
> document/d/1LQWVaEgppF38Gvnm9SpvftHpdhI1BOGdRdl_YyBe3oA/edit? we should
> submit them by the deadline Monday 14th August to be taken into account.
>
> Best,
>
> Rafik
>
> 2017-07-14 8:32 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:
>
>> Hi all,
>>
>> as you know, we asked for the CCWG-IG motion to be deferred so we can
>> continue working on our amendments. that was supported by other groups like
>> IPC due to the short time we had since Johannesburg meeting.
>>
>> Marilia, Farzaneh and I worked on making some amendments to the motion as
>> follow-up of our NCSG Policy call this week https://docs.google.com/d
>> ocument/d/1LQWVaEgppF38Gvnm9SpvftHpdhI1BOGdRdl_YyBe3oA/edit
>>
>> we are sharing this so we can discuss them. we will also share them with
>> the wider NCSG list.
>>
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170810/caad34e5/attachment.htm>

From matthew at intpolicy.com  Thu Aug 10 11:05:12 2017
From: matthew at intpolicy.com (Matthew Shears)
Date: Thu, 10 Aug 2017 09:05:12 +0100
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
Message-ID: <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>

Hi all

I draw your attention to this submission by the RySG:

http://mm.icann.org/pipermail/comments-gnso-op-procedures-19jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOperatingProceduresandICANNBylaws-0001.pdf

They note the following which we may wish to emulate (at a minimum the 
first line I would have thought):

/The RySG fully recognises the authority of the GNSO Council to speak on 
behalf of the GNSO as
Decisional Participant in the Empowered Community. This is in line with 
current practice and
working methods and respects the existing equilibrium within the GNSO?s 
structure. The RySG
agrees that on this point no changes need to be made to the ICANN Bylaws 
in relation to the role
and description of the GNSO Council.///

Matthew


On 10/08/2017 01:03, Rafik Dammak wrote:
> Hi all,
>
> the deadline for submission is this Friday. I attached the clean 
> version for review. I understand that Matt, Poncelet, Stephanie 
> support the comment. we need to hear from other PC members.
>
> Best,
>
> Rafik
>
> 2017-08-07 23:24 GMT+09:00 Stephanie Perrin 
> <stephanie.perrin at mail.utoronto.ca 
> <mailto:stephanie.perrin at mail.utoronto.ca>>:
>
>     I think that is a really good idea, as these are important
>     procedures, and we need to be able to amend if required.  Hard to
>     anticipate everything, in my view...
>
>     SP
>
>
>     On 2017-08-07 08:49, farzaneh badii wrote:
>>     Hi
>>
>>     I was on the DT group. I don't have the time to go through every
>>     single change and see if they accord with what we agreed on. If
>>     you want in the public comment we should ask that if later on
>>     during implementing the operating procedures we find out that
>>      changes recommended by  DT   for some reason are not reflected
>>     in the new  GNSO operating procedures, GNSO should follow the DT
>>     advice in those circumstances and allow for the mistake to be
>>     corrected.
>>
>>     Farzaneh
>>
>>     On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin
>>     <stephanie.perrin at mail.utoronto.ca
>>     <mailto:stephanie.perrin at mail.utoronto.ca>> wrote:
>>
>>         It looks fine to me.  I don't have knowledge of or time to do
>>         the research on the issues at the moment, so I hope that
>>         those who do can catch things that need changes.
>>
>>         cheers Stephanie
>>
>>
>>         On 2017-08-07 02:07, Rafik Dammak wrote:
>>>         Hi,
>>>
>>>         the comment is quite straightforward and supporting the
>>>         changes outlined in the public consultation.
>>>         we can have as the deadline for review and endorsement the
>>>         9th August. I urge councilors, in particular, to review the
>>>         changes since it concerns the operating procedures.
>>>         Thanks, Matt again for the draft. I resolved the edits made
>>>         by Ayden. ant proof-reading and review would be helpful.
>>>
>>>         Best,
>>>
>>>         Rafik
>>>
>>>         2017-08-05 6:33 GMT+09:00 Ayden F?rdeline
>>>         <icann at ferdeline.com <mailto:icann at ferdeline.com>>:
>>>
>>>             Hi all,
>>>
>>>             I have made some minor alterations to style, but added
>>>             nothing of substance. I hope someone with more knowledge
>>>             of this issue will be able to contribute to our comment.
>>>             Submissions are due in six days time. Thanks!
>>>
>>>             Best wishes, Ayden
>>>
>>>
>>>>             -------- Original Message --------
>>>>             Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating
>>>>             procedures change
>>>>             Local Time: August 1, 2017 5:35 PM
>>>>             UTC Time: August 1, 2017 4:35 PM
>>>>             From: matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>>             To: ncsg-pc at lists.ncsg.is
>>>>             <mailto:ncsg-pc at lists.ncsg.is>, farzaneh badii
>>>>             <farzaneh.badii at GMAIL.COM
>>>>             <mailto:farzaneh.badii at GMAIL.COM>>
>>>>
>>>>
>>>>             Hi all
>>>>
>>>>             Wanted to get this back at the top of the list of
>>>>             to-do's as time is running out.
>>>>
>>>>             Appreciate the comments from some of the PC members but
>>>>             would welcome additional inputs, thoughts, etc.
>>>>
>>>>             See google doc below.
>>>>
>>>>             Thanks.
>>>>
>>>>             Matthew
>>>>
>>>>
>>>>             On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>>             Matt,
>>>>>             I don?t have any comment to do, I agree with the
>>>>>             statements and the wording. Let me know if I can do
>>>>>             anything specific to help. Other than that you have my
>>>>>             support. Thanks!
>>>>>
>>>>>             Cheers,
>>>>>             Mart?n
>>>>>
>>>>>>             On Jul 25, 2017, at 8:22 PM, Rafik Dammak
>>>>>>             <rafik.dammak at gmail.com
>>>>>>             <mailto:rafik.dammak at gmail.com>> wrote:
>>>>>>
>>>>>>             Hi,
>>>>>>
>>>>>>             the deadline for the public comment is the 10th of
>>>>>>             August, we have to finish consulting with NCSG
>>>>>>             members, review and endorsement prior to that. I
>>>>>>             suggest 8th August as our internal deadline.
>>>>>>
>>>>>>             Best,
>>>>>>
>>>>>>             Rafik
>>>>>>
>>>>>>
>>>>>>             2017-07-25 23:28 GMT+09:00 Stefania Milan
>>>>>>             <stefania.milan at eui.eu <mailto:stefania.milan at eui.eu>>:
>>>>>>
>>>>>>                 Hi Matt, thanks. What's the deadline for this? I
>>>>>>                 am in transit (and in fact, on holiday), witch
>>>>>>                 sketchy internet access and the doc doesn't open
>>>>>>                 for me today (might be the poor connection...)
>>>>>>
>>>>>>                 Sent from my iPhone
>>>>>>
>>>>>>                 On Jul 25, 2017, at 9:17 AM, Matthew Shears
>>>>>>                 <matthew at intpolicy.com
>>>>>>                 <mailto:matthew at intpolicy.com>> wrote:
>>>>>>
>>>>>>>                 Let me qualify the last sentence - ICANN staff
>>>>>>>                 are not adding new items in addition to the work
>>>>>>>                 of the DT, but rather adding references to work
>>>>>>>                 done previously.
>>>>>>>
>>>>>>>
>>>>>>>                 On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>>>                 Calling all PCers
>>>>>>>>
>>>>>>>>                 I have started on the above public comment but
>>>>>>>>                 am still going through the consultation docs.
>>>>>>>>                 However, time marches on and we need to get
>>>>>>>>                 this one underway.
>>>>>>>>
>>>>>>>>                 So, please review the consultation docs here:
>>>>>>>>
>>>>>>>>                 https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>>>>>                 <https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en>
>>>>>>>>
>>>>>>>>                 And make comments in the google doc here:
>>>>>>>>
>>>>>>>>                 https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit
>>>>>>>>                 <https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit>
>>>>>>>>
>>>>>>>>                 Note that ICANN staff have used this
>>>>>>>>                 opportunity to include other changes that the
>>>>>>>>                 DT did not discuss.
>>>>>>>>
>>>>>>>>                 Many thanks.
>>>>>>>>
>>>>>>>>                 Matthew
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>                 -- 
>>>>>>>>                 Matthew Shears
>>>>>>>>                 matthew at intpolicy.com
>>>>>>>>                 <mailto:matthew at intpolicy.com>
>>>>>>>>                 +447712472987 <tel:+44%207712%20472987>
>>>>>>>>                 Skype:mshears
>>>>>>>
>>>>>>>                 -- 
>>>>>>>                 Matthew Shears
>>>>>>>                 matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>>>>>                 +447712472987 <tel:+44%207712%20472987>
>>>>>>>                 Skype:mshears
>>>>>>>                 _______________________________________________
>>>>>>>                 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>
>>>>>>
>>>>>>
>>>>>>                 The information transmitted is intended only for
>>>>>>                 the person or entity to which it is addressed and
>>>>>>                 may contain confidential and/or privileged
>>>>>>                 material. Any review, retransmission,
>>>>>>                 dissemination, distribution, forwarding, or other
>>>>>>                 use of, or taking of any action in reliance upon,
>>>>>>                 this information by persons or entities other
>>>>>>                 than the intended recipient is prohibited without
>>>>>>                 the express permission of the sender. If you
>>>>>>                 received this communication in error, please
>>>>>>                 contact the sender and delete the material from
>>>>>>                 any computer.
>>>>>>
>>>>>>
>>>>>>                 _______________________________________________
>>>>>>                 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>
>>>>>
>>>>>
>>>>>             <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>             	Virus-free. www.avg.com
>>>>>             <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>             _______________________________________________
>>>>>             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>
>>>>>
>>>>
>>>>             -- 
>>>>
>>>>
>>>>             Matthew Shears
>>>>             matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>>             +447712472987 <tel:+44%207712%20472987>
>>>>             Skype:mshears
>>>
>>>
>>>             _______________________________________________
>>>             NCSG-PC mailing list
>>>             NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>             https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>             <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>
>>>
>>>
>>>
>>>         _______________________________________________
>>>         NCSG-PC mailing list
>>>         NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>
>>
>>         _______________________________________________
>>         NCSG-PC mailing list
>>         NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>
>>
>
>
>     _______________________________________________
>     NCSG-PC mailing list
>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>
>
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

-- 


Matthew Shears
matthew at intpolicy.com
+447712472987
Skype:mshears

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

From rafik.dammak at gmail.com  Thu Aug 10 11:13:43 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 10 Aug 2017 17:13:43 +0900
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
Message-ID: <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>

Hi Matt,

are you suggesting a change to the comment? do you have some wording to add?

Best,

Rafik

2017-08-10 17:05 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:

> Hi all
>
> I draw your attention to this submission by the RySG:
>
> http://mm.icann.org/pipermail/comments-gnso-op-procedures-
> 19jun17/attachments/20170807/1d703c9a/RySGpubliccomment-
> GNSOOperatingProceduresandICANNBylaws-0001.pdf
>
> They note the following which we may wish to emulate (at a minimum the
> first line I would have thought):
>
>
>
>
>
> *The RySG fully recognises the authority of the GNSO Council to speak on
> behalf of the GNSO as Decisional Participant in the Empowered Community.
> This is in line with current practice and working methods and respects the
> existing equilibrium within the GNSO?s structure. The RySG agrees that on
> this point no changes need to be made to the ICANN Bylaws in relation to
> the role and description of the GNSO Council.*
> Matthew
>
>
>
> On 10/08/2017 01:03, Rafik Dammak wrote:
>
> Hi all,
>
> the deadline for submission is this Friday. I attached the clean version
> for review. I understand that Matt, Poncelet, Stephanie support the
> comment. we need to hear from other PC members.
>
> Best,
>
> Rafik
>
> 2017-08-07 23:24 GMT+09:00 Stephanie Perrin <stephanie.perrin at mail.
> utoronto.ca>:
>
>> I think that is a really good idea, as these are important procedures,
>> and we need to be able to amend if required.  Hard to anticipate
>> everything, in my view...
>>
>> SP
>>
>> On 2017-08-07 08:49, farzaneh badii wrote:
>>
>> Hi
>>
>> I was on the DT group. I don't have the time to go through every single
>> change and see if they accord with what we agreed on. If you want in the
>> public comment we should ask that if later on during implementing the
>> operating procedures we find out that  changes recommended by  DT   for
>> some reason are not reflected in the new  GNSO operating procedures, GNSO
>> should follow the DT advice in those circumstances and allow for the
>> mistake to be corrected.
>>
>> Farzaneh
>>
>> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <
>> stephanie.perrin at mail.utoronto.ca> wrote:
>>
>>> It looks fine to me.  I don't have knowledge of or time to do the
>>> research on the issues at the moment, so I hope that those who do can catch
>>> things that need changes.
>>>
>>> cheers Stephanie
>>>
>>> On 2017-08-07 02:07, Rafik Dammak wrote:
>>>
>>> Hi,
>>>
>>> the comment is quite straightforward and supporting the changes outlined
>>> in the public consultation.
>>> we can have as the deadline for review and endorsement the 9th August. I
>>> urge councilors, in particular, to review the changes since it concerns the
>>> operating procedures.
>>> Thanks, Matt again for the draft. I resolved the edits made by Ayden.
>>> ant proof-reading and review would be helpful.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>>
>>>> Hi all,
>>>>
>>>> I have made some minor alterations to style, but added nothing of
>>>> substance. I hope someone with more knowledge of this issue will be able to
>>>> contribute to our comment. Submissions are due in six days time. Thanks!
>>>>
>>>> Best wishes, Ayden
>>>>
>>>>
>>>> -------- Original Message --------
>>>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures change
>>>> Local Time: August 1, 2017 5:35 PM
>>>> UTC Time: August 1, 2017 4:35 PM
>>>> From: matthew at intpolicy.com
>>>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM>
>>>>
>>>>
>>>> Hi all
>>>>
>>>> Wanted to get this back at the top of the list of to-do's as time is
>>>> running out.
>>>>
>>>> Appreciate the comments from some of the PC members but would welcome
>>>> additional inputs, thoughts, etc.
>>>>
>>>> See google doc below.
>>>>
>>>> Thanks.
>>>>
>>>> Matthew
>>>>
>>>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>
>>>> Matt,
>>>> I don?t have any comment to do, I agree with the statements and the
>>>> wording. Let me know if I can do anything specific to help. Other than that
>>>> you have my support. Thanks!
>>>>
>>>> Cheers,
>>>> Mart?n
>>>>
>>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> the deadline for the public comment is the 10th of August, we have to
>>>> finish consulting with NCSG members, review and endorsement prior to that.
>>>> I suggest 8th August as our internal deadline.
>>>>
>>>> Best,
>>>>
>>>> Rafik
>>>>
>>>>
>>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>>>
>>>> Hi Matt, thanks. What's the deadline for this? I am in transit (and in
>>>>> fact, on holiday), witch sketchy internet access and the doc doesn't open
>>>>> for me today (might be the poor connection...)
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com>
>>>>> wrote:
>>>>>
>>>>> Let me qualify the last sentence - ICANN staff are not adding new
>>>>> items in addition to the work of the DT, but rather adding references to
>>>>> work done previously.
>>>>>
>>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>
>>>>> Calling all PCers
>>>>>
>>>>> I have started on the above public comment but am still going through
>>>>> the consultation docs.  However, time marches on and we need to get this
>>>>> one underway.
>>>>>
>>>>> So, please review the consultation docs here:
>>>>>
>>>>> https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>>
>>>>> And make comments in the google doc here:
>>>>>
>>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>>>> -ddk_Q9DWja7bZIgsiY/edit
>>>>> Note that ICANN staff have used this opportunity to include other
>>>>> changes that the DT did not discuss.
>>>>>
>>>>> Many thanks.
>>>>>
>>>>> Matthew
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>
>>>>>
>>>>> --
>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>>>
>>>>>
>>>>> The information transmitted is intended only for the person or entity
>>>>> to which it is addressed and may contain confidential and/or privileged
>>>>> material. Any review, retransmission, dissemination, distribution,
>>>>> forwarding, or other use of, or taking of any action in reliance upon, this
>>>>> information by persons or entities other than the intended recipient is
>>>>> prohibited without the express permission of the sender. If you received
>>>>> this communication in error, please contact the sender and delete the
>>>>> material from any computer.
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>>
>>>>
>>>>
>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>> Virus-free. www.avg.com
>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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 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 listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
> --
>
>
> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>
>
> _______________________________________________
> 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/20170810/33156148/attachment.htm>

From matthew at intpolicy.com  Thu Aug 10 11:19:19 2017
From: matthew at intpolicy.com (Matthew Shears)
Date: Thu, 10 Aug 2017 09:19:19 +0100
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
 <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
Message-ID: <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>

I'm drawing it to the attention of the PC - the issue of the role of 
Council was a contentious one in the DT with the BC and other suggesting 
that the Council was exceeding its role if it took on EC 
responsibilities.  NCSG and RySG were aligned on this seeing no issue 
with Council assuming the role.   My question was whether we thought we 
should add a similar line on the role of Council in our submission.

Matthew


On 10/08/2017 09:13, Rafik Dammak wrote:
> Hi Matt,
>
> are you suggesting a change to the comment? do you have some wording 
> to add?
>
> Best,
>
> Rafik
>
> 2017-08-10 17:05 GMT+09:00 Matthew Shears <matthew at intpolicy.com 
> <mailto:matthew at intpolicy.com>>:
>
>     Hi all
>
>     I draw your attention to this submission by the RySG:
>
>     http://mm.icann.org/pipermail/comments-gnso-op-procedures-19jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOperatingProceduresandICANNBylaws-0001.pdf
>     <http://mm.icann.org/pipermail/comments-gnso-op-procedures-19jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOperatingProceduresandICANNBylaws-0001.pdf>
>
>     They note the following which we may wish to emulate (at a minimum
>     the first line I would have thought):
>
>     /The RySG fully recognises the authority of the GNSO Council to
>     speak on behalf of the GNSO as
>     Decisional Participant in the Empowered Community. This is in line
>     with current practice and
>     working methods and respects the existing equilibrium within the
>     GNSO?s structure. The RySG
>     agrees that on this point no changes need to be made to the ICANN
>     Bylaws in relation to the role
>     and description of the GNSO Council.///
>
>     Matthew
>
>
>
>     On 10/08/2017 01:03, Rafik Dammak wrote:
>>     Hi all,
>>
>>     the deadline for submission is this Friday. I attached the clean
>>     version for review. I understand that Matt, Poncelet, Stephanie
>>     support the comment. we need to hear from other PC members.
>>
>>     Best,
>>
>>     Rafik
>>
>>     2017-08-07 23:24 GMT+09:00 Stephanie Perrin
>>     <stephanie.perrin at mail.utoronto.ca
>>     <mailto:stephanie.perrin at mail.utoronto.ca>>:
>>
>>         I think that is a really good idea, as these are important
>>         procedures, and we need to be able to amend if required. 
>>         Hard to anticipate everything, in my view...
>>
>>         SP
>>
>>
>>         On 2017-08-07 08:49, farzaneh badii wrote:
>>>         Hi
>>>
>>>         I was on the DT group. I don't have the time to go through
>>>         every single change and see if they accord with what we
>>>         agreed on. If you want in the public comment we should ask
>>>         that if later on during implementing the operating
>>>         procedures we find out that  changes recommended by  DT for
>>>         some reason are not reflected in the new  GNSO operating
>>>         procedures, GNSO should follow the DT advice in those
>>>         circumstances and allow for the mistake to be corrected.
>>>
>>>         Farzaneh
>>>
>>>         On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin
>>>         <stephanie.perrin at mail.utoronto.ca
>>>         <mailto:stephanie.perrin at mail.utoronto.ca>> wrote:
>>>
>>>             It looks fine to me.  I don't have knowledge of or time
>>>             to do the research on the issues at the moment, so I
>>>             hope that those who do can catch things that need changes.
>>>
>>>             cheers Stephanie
>>>
>>>
>>>             On 2017-08-07 02:07, Rafik Dammak wrote:
>>>>             Hi,
>>>>
>>>>             the comment is quite straightforward and supporting the
>>>>             changes outlined in the public consultation.
>>>>             we can have as the deadline for review and endorsement
>>>>             the 9th August. I urge councilors, in particular, to
>>>>             review the changes since it concerns the operating
>>>>             procedures.
>>>>             Thanks, Matt again for the draft. I resolved the edits
>>>>             made by Ayden. ant proof-reading and review would be
>>>>             helpful.
>>>>
>>>>             Best,
>>>>
>>>>             Rafik
>>>>
>>>>             2017-08-05 6:33 GMT+09:00 Ayden F?rdeline
>>>>             <icann at ferdeline.com <mailto:icann at ferdeline.com>>:
>>>>
>>>>                 Hi all,
>>>>
>>>>                 I have made some minor alterations to style, but
>>>>                 added nothing of substance. I hope someone with
>>>>                 more knowledge of this issue will be able to
>>>>                 contribute to our comment. Submissions are due in
>>>>                 six days time. Thanks!
>>>>
>>>>                 Best wishes, Ayden
>>>>
>>>>
>>>>>                 -------- Original Message --------
>>>>>                 Subject: Re: [NCSG-PC] NCSG Comment on GNSO
>>>>>                 operating procedures change
>>>>>                 Local Time: August 1, 2017 5:35 PM
>>>>>                 UTC Time: August 1, 2017 4:35 PM
>>>>>                 From: matthew at intpolicy.com
>>>>>                 <mailto:matthew at intpolicy.com>
>>>>>                 To: ncsg-pc at lists.ncsg.is
>>>>>                 <mailto:ncsg-pc at lists.ncsg.is>, farzaneh badii
>>>>>                 <farzaneh.badii at GMAIL.COM
>>>>>                 <mailto:farzaneh.badii at GMAIL.COM>>
>>>>>
>>>>>
>>>>>                 Hi all
>>>>>
>>>>>                 Wanted to get this back at the top of the list of
>>>>>                 to-do's as time is running out.
>>>>>
>>>>>                 Appreciate the comments from some of the PC
>>>>>                 members but would welcome additional inputs,
>>>>>                 thoughts, etc.
>>>>>
>>>>>                 See google doc below.
>>>>>
>>>>>                 Thanks.
>>>>>
>>>>>                 Matthew
>>>>>
>>>>>
>>>>>                 On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>>>                 Matt,
>>>>>>                 I don?t have any comment to do, I agree with the
>>>>>>                 statements and the wording. Let me know if I can
>>>>>>                 do anything specific to help. Other than that you
>>>>>>                 have my support. Thanks!
>>>>>>
>>>>>>                 Cheers,
>>>>>>                 Mart?n
>>>>>>
>>>>>>>                 On Jul 25, 2017, at 8:22 PM, Rafik Dammak
>>>>>>>                 <rafik.dammak at gmail.com
>>>>>>>                 <mailto:rafik.dammak at gmail.com>> wrote:
>>>>>>>
>>>>>>>                 Hi,
>>>>>>>
>>>>>>>                 the deadline for the public comment is the 10th
>>>>>>>                 of August, we have to finish consulting with
>>>>>>>                 NCSG members, review and endorsement prior to
>>>>>>>                 that. I suggest 8th August as our internal deadline.
>>>>>>>
>>>>>>>                 Best,
>>>>>>>
>>>>>>>                 Rafik
>>>>>>>
>>>>>>>
>>>>>>>                 2017-07-25 23:28 GMT+09:00 Stefania Milan
>>>>>>>                 <stefania.milan at eui.eu
>>>>>>>                 <mailto:stefania.milan at eui.eu>>:
>>>>>>>
>>>>>>>                     Hi Matt, thanks. What's the deadline for
>>>>>>>                     this? I am in transit (and in fact, on
>>>>>>>                     holiday), witch sketchy internet access and
>>>>>>>                     the doc doesn't open for me today (might be
>>>>>>>                     the poor connection...)
>>>>>>>
>>>>>>>                     Sent from my iPhone
>>>>>>>
>>>>>>>                     On Jul 25, 2017, at 9:17 AM, Matthew Shears
>>>>>>>                     <matthew at intpolicy.com
>>>>>>>                     <mailto:matthew at intpolicy.com>> wrote:
>>>>>>>
>>>>>>>>                     Let me qualify the last sentence - ICANN
>>>>>>>>                     staff are not adding new items in addition
>>>>>>>>                     to the work of the DT, but rather adding
>>>>>>>>                     references to work done previously.
>>>>>>>>
>>>>>>>>
>>>>>>>>                     On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>>>>                     Calling all PCers
>>>>>>>>>
>>>>>>>>>                     I have started on the above public comment
>>>>>>>>>                     but am still going through the
>>>>>>>>>                     consultation docs. However, time marches
>>>>>>>>>                     on and we need to get this one underway.
>>>>>>>>>
>>>>>>>>>                     So, please review the consultation docs here:
>>>>>>>>>
>>>>>>>>>                     https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>>>>>>                     <https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en>
>>>>>>>>>
>>>>>>>>>                     And make comments in the google doc here:
>>>>>>>>>
>>>>>>>>>                     https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit
>>>>>>>>>                     <https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit>
>>>>>>>>>
>>>>>>>>>                     Note that ICANN staff have used this
>>>>>>>>>                     opportunity to include other changes that
>>>>>>>>>                     the DT did not discuss.
>>>>>>>>>
>>>>>>>>>                     Many thanks.
>>>>>>>>>
>>>>>>>>>                     Matthew
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                     -- 
>>>>>>>>>                     Matthew Shears
>>>>>>>>>                     matthew at intpolicy.com
>>>>>>>>>                     <mailto:matthew at intpolicy.com>
>>>>>>>>>                     +447712472987 <tel:+44%207712%20472987>
>>>>>>>>>                     Skype:mshears
>>>>>>>>
>>>>>>>>                     -- 
>>>>>>>>                     Matthew Shears
>>>>>>>>                     matthew at intpolicy.com
>>>>>>>>                     <mailto:matthew at intpolicy.com>
>>>>>>>>                     +447712472987 <tel:+44%207712%20472987>
>>>>>>>>                     Skype:mshears
>>>>>>>>                     _______________________________________________
>>>>>>>>                     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>
>>>>>>>
>>>>>>>
>>>>>>>                     The information transmitted is intended only
>>>>>>>                     for the person or entity to which it is
>>>>>>>                     addressed and may contain confidential
>>>>>>>                     and/or privileged material. Any review,
>>>>>>>                     retransmission, dissemination, distribution,
>>>>>>>                     forwarding, or other use of, or taking of
>>>>>>>                     any action in reliance upon, this
>>>>>>>                     information by persons or entities other
>>>>>>>                     than the intended recipient is prohibited
>>>>>>>                     without the express permission of the
>>>>>>>                     sender. If you received this communication
>>>>>>>                     in error, please contact the sender and
>>>>>>>                     delete the material from any computer.
>>>>>>>
>>>>>>>
>>>>>>>                     _______________________________________________
>>>>>>>                     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>
>>>>>>
>>>>>>
>>>>>>                 <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>                 	Virus-free. www.avg.com
>>>>>>                 <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>                 _______________________________________________
>>>>>>                 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>
>>>>>>
>>>>>
>>>>>                 -- 
>>>>>
>>>>>
>>>>>                 Matthew Shears
>>>>>                 matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>>>                 +447712472987 <tel:+44%207712%20472987>
>>>>>                 Skype:mshears
>>>>
>>>>
>>>>                 _______________________________________________
>>>>                 NCSG-PC mailing list
>>>>                 NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>>                 https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>                 <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>
>>>>
>>>>
>>>>
>>>>             _______________________________________________
>>>>             NCSG-PC mailing list
>>>>             NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>>             https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>             <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>
>>>
>>>             _______________________________________________
>>>             NCSG-PC mailing list
>>>             NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>             https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>             <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>
>>>
>>
>>
>>         _______________________________________________
>>         NCSG-PC mailing list
>>         NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>
>>
>>
>>
>>     _______________________________________________
>>     NCSG-PC mailing list
>>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>
>     -- 
>
>
>     Matthew Shears
>     matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>     +447712472987 <tel:+44%207712%20472987>
>     Skype:mshears
>
>
>     _______________________________________________
>     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>
>
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
> 	Virus-free. www.avg.com 
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

-- 


Matthew Shears
matthew at intpolicy.com
+447712472987
Skype:mshears

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

From rafik.dammak at gmail.com  Thu Aug 10 11:37:32 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 10 Aug 2017 17:37:32 +0900
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
 <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
 <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>
Message-ID: <CAH5sThkuLKYbzotNzga147d-OupdqKPJ24CnP9vvkqLb4BqVKA@mail.gmail.com>

Hi Matt,

I do think we can add a similar line to our comment .

Best,

Rafik

2017-08-10 17:19 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:

> I'm drawing it to the attention of the PC - the issue of the role of
> Council was a contentious one in the DT with the BC and other suggesting
> that the Council was exceeding its role if it took on EC responsibilities.
> NCSG and RySG were aligned on this seeing no issue with Council assuming
> the role.   My question was whether we thought we should add a similar line
> on the role of Council in our submission.
>
> Matthew
>
> On 10/08/2017 09:13, Rafik Dammak wrote:
>
> Hi Matt,
>
> are you suggesting a change to the comment? do you have some wording to
> add?
>
> Best,
>
> Rafik
>
> 2017-08-10 17:05 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>
>> Hi all
>>
>> I draw your attention to this submission by the RySG:
>>
>> http://mm.icann.org/pipermail/comments-gnso-op-procedures-19
>> jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOp
>> eratingProceduresandICANNBylaws-0001.pdf
>>
>> They note the following which we may wish to emulate (at a minimum the
>> first line I would have thought):
>>
>>
>>
>>
>>
>> *The RySG fully recognises the authority of the GNSO Council to speak on
>> behalf of the GNSO as Decisional Participant in the Empowered Community.
>> This is in line with current practice and working methods and respects the
>> existing equilibrium within the GNSO?s structure. The RySG agrees that on
>> this point no changes need to be made to the ICANN Bylaws in relation to
>> the role and description of the GNSO Council.*
>> Matthew
>>
>>
>>
>> On 10/08/2017 01:03, Rafik Dammak wrote:
>>
>> Hi all,
>>
>> the deadline for submission is this Friday. I attached the clean version
>> for review. I understand that Matt, Poncelet, Stephanie support the
>> comment. we need to hear from other PC members.
>>
>> Best,
>>
>> Rafik
>>
>> 2017-08-07 23:24 GMT+09:00 Stephanie Perrin <
>> stephanie.perrin at mail.utoronto.ca>:
>>
>>> I think that is a really good idea, as these are important procedures,
>>> and we need to be able to amend if required.  Hard to anticipate
>>> everything, in my view...
>>>
>>> SP
>>>
>>> On 2017-08-07 08:49, farzaneh badii wrote:
>>>
>>> Hi
>>>
>>> I was on the DT group. I don't have the time to go through every single
>>> change and see if they accord with what we agreed on. If you want in the
>>> public comment we should ask that if later on during implementing the
>>> operating procedures we find out that  changes recommended by  DT   for
>>> some reason are not reflected in the new  GNSO operating procedures, GNSO
>>> should follow the DT advice in those circumstances and allow for the
>>> mistake to be corrected.
>>>
>>> Farzaneh
>>>
>>> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <
>>> stephanie.perrin at mail.utoronto.ca> wrote:
>>>
>>>> It looks fine to me.  I don't have knowledge of or time to do the
>>>> research on the issues at the moment, so I hope that those who do can catch
>>>> things that need changes.
>>>>
>>>> cheers Stephanie
>>>>
>>>> On 2017-08-07 02:07, Rafik Dammak wrote:
>>>>
>>>> Hi,
>>>>
>>>> the comment is quite straightforward and supporting the changes
>>>> outlined in the public consultation.
>>>> we can have as the deadline for review and endorsement the 9th August.
>>>> I urge councilors, in particular, to review the changes since it concerns
>>>> the operating procedures.
>>>> Thanks, Matt again for the draft. I resolved the edits made by Ayden.
>>>> ant proof-reading and review would be helpful.
>>>>
>>>> Best,
>>>>
>>>> Rafik
>>>>
>>>> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I have made some minor alterations to style, but added nothing of
>>>>> substance. I hope someone with more knowledge of this issue will be able to
>>>>> contribute to our comment. Submissions are due in six days time. Thanks!
>>>>>
>>>>> Best wishes, Ayden
>>>>>
>>>>>
>>>>> -------- Original Message --------
>>>>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures change
>>>>> Local Time: August 1, 2017 5:35 PM
>>>>> UTC Time: August 1, 2017 4:35 PM
>>>>> From: matthew at intpolicy.com
>>>>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM>
>>>>>
>>>>>
>>>>> Hi all
>>>>>
>>>>> Wanted to get this back at the top of the list of to-do's as time is
>>>>> running out.
>>>>>
>>>>> Appreciate the comments from some of the PC members but would welcome
>>>>> additional inputs, thoughts, etc.
>>>>>
>>>>> See google doc below.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Matthew
>>>>>
>>>>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>>
>>>>> Matt,
>>>>> I don?t have any comment to do, I agree with the statements and the
>>>>> wording. Let me know if I can do anything specific to help. Other than that
>>>>> you have my support. Thanks!
>>>>>
>>>>> Cheers,
>>>>> Mart?n
>>>>>
>>>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> the deadline for the public comment is the 10th of August, we have to
>>>>> finish consulting with NCSG members, review and endorsement prior to that.
>>>>> I suggest 8th August as our internal deadline.
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>>>
>>>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>>>>
>>>>> Hi Matt, thanks. What's the deadline for this? I am in transit (and in
>>>>>> fact, on holiday), witch sketchy internet access and the doc doesn't open
>>>>>> for me today (might be the poor connection...)
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com>
>>>>>> wrote:
>>>>>>
>>>>>> Let me qualify the last sentence - ICANN staff are not adding new
>>>>>> items in addition to the work of the DT, but rather adding references to
>>>>>> work done previously.
>>>>>>
>>>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>
>>>>>> Calling all PCers
>>>>>>
>>>>>> I have started on the above public comment but am still going through
>>>>>> the consultation docs.  However, time marches on and we need to get this
>>>>>> one underway.
>>>>>>
>>>>>> So, please review the consultation docs here:
>>>>>>
>>>>>> https://www.icann.org/public-comments/gnso-op-procedures-201
>>>>>> 7-06-19-en
>>>>>>
>>>>>> And make comments in the google doc here:
>>>>>>
>>>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>>>>> -ddk_Q9DWja7bZIgsiY/edit
>>>>>> Note that ICANN staff have used this opportunity to include other
>>>>>> changes that the DT did not discuss.
>>>>>>
>>>>>> Many thanks.
>>>>>>
>>>>>> Matthew
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>
>>>>>> _______________________________________________
>>>>>> NCSG-PC mailing list
>>>>>> NCSG-PC at lists.ncsg.is
>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>
>>>>>>
>>>>>>
>>>>>> The information transmitted is intended only for the person or entity
>>>>>> to which it is addressed and may contain confidential and/or privileged
>>>>>> material. Any review, retransmission, dissemination, distribution,
>>>>>> forwarding, or other use of, or taking of any action in reliance upon, this
>>>>>> information by persons or entities other than the intended recipient is
>>>>>> prohibited without the express permission of the sender. If you received
>>>>>> this communication in error, please contact the sender and delete the
>>>>>> material from any computer.
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>> Virus-free. www.avg.com
>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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 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 listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>>
>> --
>>
>>
>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>>
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
> www.avg.com
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> <#m_7701040911500582868_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
> --
>
>
> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170810/a96a5844/attachment.htm>

From farzaneh.badii at gmail.com  Thu Aug 10 11:45:53 2017
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Thu, 10 Aug 2017 04:45:53 -0400
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <CAH5sThkuLKYbzotNzga147d-OupdqKPJ24CnP9vvkqLb4BqVKA@mail.gmail.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
 <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
 <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>
 <CAH5sThkuLKYbzotNzga147d-OupdqKPJ24CnP9vvkqLb4BqVKA@mail.gmail.com>
Message-ID: <CAN1qJvC+jSTv1BAE3dtsOiejK3CmcWub7CxNP=E3=W9xaujxXg@mail.gmail.com>

I think we should add that. please also consider adding what I mentioned in
my previous email. DT had a debate and reached consensus on many important
issues which were contentious, mainly participation of GNSO in the
empowered community through the council and the thresholds to reach
decisions. As Stephanie agreed to add something like that, I kindly ask her
to just come up with a once sentence which encompasses what I said in my
previous email since she knows how the council functions better than I do.

Farzaneh

On Thu, Aug 10, 2017 at 4:37 AM, Rafik Dammak <rafik.dammak at gmail.com>
wrote:

> Hi Matt,
>
> I do think we can add a similar line to our comment .
>
> Best,
>
> Rafik
>
>
> 2017-08-10 17:19 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>
>> I'm drawing it to the attention of the PC - the issue of the role of
>> Council was a contentious one in the DT with the BC and other suggesting
>> that the Council was exceeding its role if it took on EC responsibilities.
>> NCSG and RySG were aligned on this seeing no issue with Council assuming
>> the role.   My question was whether we thought we should add a similar line
>> on the role of Council in our submission.
>>
>> Matthew
>>
>> On 10/08/2017 09:13, Rafik Dammak wrote:
>>
>> Hi Matt,
>>
>> are you suggesting a change to the comment? do you have some wording to
>> add?
>>
>> Best,
>>
>> Rafik
>>
>> 2017-08-10 17:05 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>>
>>> Hi all
>>>
>>> I draw your attention to this submission by the RySG:
>>>
>>> http://mm.icann.org/pipermail/comments-gnso-op-procedures-19
>>> jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOp
>>> eratingProceduresandICANNBylaws-0001.pdf
>>>
>>> They note the following which we may wish to emulate (at a minimum the
>>> first line I would have thought):
>>>
>>>
>>>
>>>
>>>
>>> *The RySG fully recognises the authority of the GNSO Council to speak on
>>> behalf of the GNSO as Decisional Participant in the Empowered Community.
>>> This is in line with current practice and working methods and respects the
>>> existing equilibrium within the GNSO?s structure. The RySG agrees that on
>>> this point no changes need to be made to the ICANN Bylaws in relation to
>>> the role and description of the GNSO Council.*
>>> Matthew
>>>
>>>
>>>
>>> On 10/08/2017 01:03, Rafik Dammak wrote:
>>>
>>> Hi all,
>>>
>>> the deadline for submission is this Friday. I attached the clean version
>>> for review. I understand that Matt, Poncelet, Stephanie support the
>>> comment. we need to hear from other PC members.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> 2017-08-07 23:24 GMT+09:00 Stephanie Perrin <
>>> stephanie.perrin at mail.utoronto.ca>:
>>>
>>>> I think that is a really good idea, as these are important procedures,
>>>> and we need to be able to amend if required.  Hard to anticipate
>>>> everything, in my view...
>>>>
>>>> SP
>>>>
>>>> On 2017-08-07 08:49, farzaneh badii wrote:
>>>>
>>>> Hi
>>>>
>>>> I was on the DT group. I don't have the time to go through every single
>>>> change and see if they accord with what we agreed on. If you want in the
>>>> public comment we should ask that if later on during implementing the
>>>> operating procedures we find out that  changes recommended by  DT   for
>>>> some reason are not reflected in the new  GNSO operating procedures, GNSO
>>>> should follow the DT advice in those circumstances and allow for the
>>>> mistake to be corrected.
>>>>
>>>> Farzaneh
>>>>
>>>> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <
>>>> stephanie.perrin at mail.utoronto.ca> wrote:
>>>>
>>>>> It looks fine to me.  I don't have knowledge of or time to do the
>>>>> research on the issues at the moment, so I hope that those who do can catch
>>>>> things that need changes.
>>>>>
>>>>> cheers Stephanie
>>>>>
>>>>> On 2017-08-07 02:07, Rafik Dammak wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> the comment is quite straightforward and supporting the changes
>>>>> outlined in the public consultation.
>>>>> we can have as the deadline for review and endorsement the 9th August.
>>>>> I urge councilors, in particular, to review the changes since it concerns
>>>>> the operating procedures.
>>>>> Thanks, Matt again for the draft. I resolved the edits made by Ayden.
>>>>> ant proof-reading and review would be helpful.
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>>> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I have made some minor alterations to style, but added nothing of
>>>>>> substance. I hope someone with more knowledge of this issue will be able to
>>>>>> contribute to our comment. Submissions are due in six days time. Thanks!
>>>>>>
>>>>>> Best wishes, Ayden
>>>>>>
>>>>>>
>>>>>> -------- Original Message --------
>>>>>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures
>>>>>> change
>>>>>> Local Time: August 1, 2017 5:35 PM
>>>>>> UTC Time: August 1, 2017 4:35 PM
>>>>>> From: matthew at intpolicy.com
>>>>>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM>
>>>>>>
>>>>>>
>>>>>> Hi all
>>>>>>
>>>>>> Wanted to get this back at the top of the list of to-do's as time is
>>>>>> running out.
>>>>>>
>>>>>> Appreciate the comments from some of the PC members but would welcome
>>>>>> additional inputs, thoughts, etc.
>>>>>>
>>>>>> See google doc below.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Matthew
>>>>>>
>>>>>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>>>
>>>>>> Matt,
>>>>>> I don?t have any comment to do, I agree with the statements and the
>>>>>> wording. Let me know if I can do anything specific to help. Other than that
>>>>>> you have my support. Thanks!
>>>>>>
>>>>>> Cheers,
>>>>>> Mart?n
>>>>>>
>>>>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> the deadline for the public comment is the 10th of August, we have to
>>>>>> finish consulting with NCSG members, review and endorsement prior to that.
>>>>>> I suggest 8th August as our internal deadline.
>>>>>>
>>>>>> Best,
>>>>>>
>>>>>> Rafik
>>>>>>
>>>>>>
>>>>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>>>>>
>>>>>> Hi Matt, thanks. What's the deadline for this? I am in transit (and
>>>>>>> in fact, on holiday), witch sketchy internet access and the doc doesn't
>>>>>>> open for me today (might be the poor connection...)
>>>>>>>
>>>>>>> Sent from my iPhone
>>>>>>>
>>>>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Let me qualify the last sentence - ICANN staff are not adding new
>>>>>>> items in addition to the work of the DT, but rather adding references to
>>>>>>> work done previously.
>>>>>>>
>>>>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>>
>>>>>>> Calling all PCers
>>>>>>>
>>>>>>> I have started on the above public comment but am still going
>>>>>>> through the consultation docs.  However, time marches on and we need to get
>>>>>>> this one underway.
>>>>>>>
>>>>>>> So, please review the consultation docs here:
>>>>>>>
>>>>>>> https://www.icann.org/public-comments/gnso-op-procedures-201
>>>>>>> 7-06-19-en
>>>>>>>
>>>>>>> And make comments in the google doc here:
>>>>>>>
>>>>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>>>>>> -ddk_Q9DWja7bZIgsiY/edit
>>>>>>> Note that ICANN staff have used this opportunity to include other
>>>>>>> changes that the DT did not discuss.
>>>>>>>
>>>>>>> Many thanks.
>>>>>>>
>>>>>>> Matthew
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> NCSG-PC mailing list
>>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The information transmitted is intended only for the person or
>>>>>>> entity to which it is addressed and may contain confidential and/or
>>>>>>> privileged material. Any review, retransmission, dissemination,
>>>>>>> distribution, forwarding, or other use of, or taking of any action in
>>>>>>> reliance upon, this information by persons or entities other than the
>>>>>>> intended recipient is prohibited without the express permission of the
>>>>>>> sender. If you received this communication in error, please contact the
>>>>>>> sender and delete the material from any computer.
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>> Virus-free. www.avg.com
>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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 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 listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>>
>>> --
>>>
>>>
>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>>
>>
>>
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
>> www.avg.com
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>> <#m_8430456596589667341_m_7701040911500582868_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>>
>> --
>>
>>
>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>
>>
>
> _______________________________________________
> 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/20170810/5c9eb24e/attachment.htm>

From mpsilvavalent at gmail.com  Thu Aug 10 14:22:14 2017
From: mpsilvavalent at gmail.com (Martin Pablo Silva Valent)
Date: Thu, 10 Aug 2017 08:22:14 -0300
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
Message-ID: <CAJjnsDEqpjdg98qrUw8PiKBuB=zy1bQJ8mmCbEcRfJRDMskuuA@mail.gmail.com>

I also stated my support a while back, I maintain it.

Cheers,
Martin



On 9 Aug 2017 9:03 pm, "Rafik Dammak" <rafik.dammak at gmail.com> wrote:

> Hi all,
>
> the deadline for submission is this Friday. I attached the clean version
> for review. I understand that Matt, Poncelet, Stephanie support the
> comment. we need to hear from other PC members.
>
> Best,
>
> Rafik
>
> 2017-08-07 23:24 GMT+09:00 Stephanie Perrin <stephanie.perrin at mail.
> utoronto.ca>:
>
>> I think that is a really good idea, as these are important procedures,
>> and we need to be able to amend if required.  Hard to anticipate
>> everything, in my view...
>>
>> SP
>>
>> On 2017-08-07 08:49, farzaneh badii wrote:
>>
>> Hi
>>
>> I was on the DT group. I don't have the time to go through every single
>> change and see if they accord with what we agreed on. If you want in the
>> public comment we should ask that if later on during implementing the
>> operating procedures we find out that  changes recommended by  DT   for
>> some reason are not reflected in the new  GNSO operating procedures, GNSO
>> should follow the DT advice in those circumstances and allow for the
>> mistake to be corrected.
>>
>> Farzaneh
>>
>> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <
>> stephanie.perrin at mail.utoronto.ca> wrote:
>>
>>> It looks fine to me.  I don't have knowledge of or time to do the
>>> research on the issues at the moment, so I hope that those who do can catch
>>> things that need changes.
>>>
>>> cheers Stephanie
>>>
>>> On 2017-08-07 02:07, Rafik Dammak wrote:
>>>
>>> Hi,
>>>
>>> the comment is quite straightforward and supporting the changes outlined
>>> in the public consultation.
>>> we can have as the deadline for review and endorsement the 9th August. I
>>> urge councilors, in particular, to review the changes since it concerns the
>>> operating procedures.
>>> Thanks, Matt again for the draft. I resolved the edits made by Ayden.
>>> ant proof-reading and review would be helpful.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>>
>>>> Hi all,
>>>>
>>>> I have made some minor alterations to style, but added nothing of
>>>> substance. I hope someone with more knowledge of this issue will be able to
>>>> contribute to our comment. Submissions are due in six days time. Thanks!
>>>>
>>>> Best wishes, Ayden
>>>>
>>>>
>>>> -------- Original Message --------
>>>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures change
>>>> Local Time: August 1, 2017 5:35 PM
>>>> UTC Time: August 1, 2017 4:35 PM
>>>> From: matthew at intpolicy.com
>>>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM>
>>>>
>>>>
>>>> Hi all
>>>>
>>>> Wanted to get this back at the top of the list of to-do's as time is
>>>> running out.
>>>>
>>>> Appreciate the comments from some of the PC members but would welcome
>>>> additional inputs, thoughts, etc.
>>>>
>>>> See google doc below.
>>>>
>>>> Thanks.
>>>>
>>>> Matthew
>>>>
>>>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>
>>>> Matt,
>>>> I don?t have any comment to do, I agree with the statements and the
>>>> wording. Let me know if I can do anything specific to help. Other than that
>>>> you have my support. Thanks!
>>>>
>>>> Cheers,
>>>> Mart?n
>>>>
>>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> the deadline for the public comment is the 10th of August, we have to
>>>> finish consulting with NCSG members, review and endorsement prior to that.
>>>> I suggest 8th August as our internal deadline.
>>>>
>>>> Best,
>>>>
>>>> Rafik
>>>>
>>>>
>>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>>>
>>>> Hi Matt, thanks. What's the deadline for this? I am in transit (and in
>>>>> fact, on holiday), witch sketchy internet access and the doc doesn't open
>>>>> for me today (might be the poor connection...)
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com>
>>>>> wrote:
>>>>>
>>>>> Let me qualify the last sentence - ICANN staff are not adding new
>>>>> items in addition to the work of the DT, but rather adding references to
>>>>> work done previously.
>>>>>
>>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>
>>>>> Calling all PCers
>>>>>
>>>>> I have started on the above public comment but am still going through
>>>>> the consultation docs.  However, time marches on and we need to get this
>>>>> one underway.
>>>>>
>>>>> So, please review the consultation docs here:
>>>>>
>>>>> https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>>
>>>>> And make comments in the google doc here:
>>>>>
>>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>>>> -ddk_Q9DWja7bZIgsiY/edit
>>>>> Note that ICANN staff have used this opportunity to include other
>>>>> changes that the DT did not discuss.
>>>>>
>>>>> Many thanks.
>>>>>
>>>>> Matthew
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>
>>>>>
>>>>> --
>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>>>
>>>>>
>>>>> The information transmitted is intended only for the person or entity
>>>>> to which it is addressed and may contain confidential and/or privileged
>>>>> material. Any review, retransmission, dissemination, distribution,
>>>>> forwarding, or other use of, or taking of any action in reliance upon, this
>>>>> information by persons or entities other than the intended recipient is
>>>>> prohibited without the express permission of the sender. If you received
>>>>> this communication in error, please contact the sender and delete the
>>>>> material from any computer.
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>>
>>>>
>>>>
>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>> Virus-free. www.avg.com
>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170810/6285fd70/attachment.htm>

From icann at ferdeline.com  Fri Aug 11 02:34:33 2017
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Thu, 10 Aug 2017 19:34:33 -0400
Subject: [NCSG-PC] Drafting/Documenting NCSG Policy Committee Procedures
In-Reply-To: <3201f649-c1bf-ddfa-59da-37299aaa8d51@intpolicy.com>
References: <CAH5sThmXLsSxhEv+QwrsqN8vvusFwXaNXJHs2ftdmh=rdMLQRw@mail.gmail.com>
 <CAH5sThkU-gDezYOPoeWd=WH05uFVMpdykH7o+5xWT+=A-DDSGw@mail.gmail.com>
 <49A5EE51-7440-42B3-9BDD-2F3D97CE517B@gmail.com>
 <CAH5sTh=9zBWYZ0kX7n=aerf7bnkQzgvhqQ_gaU+eMH8tG+VDjQ@mail.gmail.com>
 <643b4f37-a76c-a52c-d478-10142566ae0b@mpicc.de>
 <3201f649-c1bf-ddfa-59da-37299aaa8d51@intpolicy.com>
Message-ID: <zAe4lyuxEJ9LTBB9ojHJ5u_3bcZrUija0mX9PoH--A7PmeVNX7-WzVXQP6UuhHfMU1crG9rPcuUGUAeYOVZAJLDH9jv0Sbd5B_nPI71yTXw=@ferdeline.com>

I would be pleased to contribute where I can.

Best wishes, Ayden

> -------- Original Message --------
> Subject: Re: [NCSG-PC] Drafting/Documenting NCSG Policy Committee Procedures
> Local Time: 8 August 2017 10:14 AM
> UTC Time: 8 August 2017 09:14
> From: matthew at intpolicy.com
> To: ncsg-pc at lists.ncsg.is
>
> I am happy to participate also.
>
> On 08/08/2017 09:43, Dr. Tatiana Tropina wrote:
>
>> Hi Rafik and Martin, and all, -
>>
>> as I have experience both with drafting NCUC procedures and PC experience, am ready to join the drafting team.
>>
>> Cheers,
>>
>> Tanya
>>
>> On 08/08/17 07:44, Rafik Dammak wrote:
>>
>>> Hi ,
>>>
>>> Thanks, Martin,
>>> I will create a google doc with an outline of those suggestions for procedures and add some ideas for each. then share it as a strawman document. that will make easier to cooperate on the same document and kick-off the discussion.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> 2017-08-08 9:57 GMT+09:00 Martin Pablo Silva Valent <mpsilvavalent at gmail.com>:
>>>
>>>> I can work with Rafik with this, he?s experiences is way over mine, but for the little I can help I think it is an initiative worth working on.
>>>>
>>>> Cheers,
>>>> Mart?n
>>>>
>>>>> On Aug 7, 2017, at 9:28 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I am resending this to resume discussion on drafting procedures for policy committee work. I volunteered for drafting and hope to share something soon for review and discussion.
>>>>>
>>>>> NCUC used my previous proposal for NCSG comments and tweaked it. I will use that and add other details such as: creating a template document for our public statements (similar to what BC has) and adding an item about a follow-up to check the staff report to see it includes our comment or not (based on Ayden question).
>>>>>
>>>>> any other procedure to suggest to those listed above. I recall that we discussed last year about communication and I guess we can add that to the list. maybe it is not procedure per se but can be seen as guidelines.
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>>> 2017-05-08 13:58 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:
>>>>>
>>>>>> hi all,
>>>>>>
>>>>>> by the previous discussion we are having lately with regard to board seat election, SSC appointment, comments endorsement, involving and engaging NCSG membership, I would like to propose that we kick-off a discussion on Policy Committee procedures, processes, working methods, and guidelines.
>>>>>>
>>>>>> We can start by listing some items to cover first and work with NCSG EC for reviewing them and consulting NCSG membership after agreeing on a tentative timeline to get this done.
>>>>>>
>>>>>> Getting those procedures are overdue and will definitely help us for our work and it is one of the provision of NCSG charter to be filled. Some ideas for starters:
>>>>>>
>>>>>> - Drafting and approving NCSG Statements
>>>>>> - Council Motions (engage with members and other councilors on how one intends to vote with rationale)
>>>>>> - Appointments and selection process for NCSG representative
>>>>>> - Decision making
>>>>>> - Board Seat #14 selection process (as internal process)
>>>>>> - GNSO Council Chair and Vice Chair selection process (as internal process)
>>>>>> - NCSG PC Chair and Vice Chair selection process
>>>>>>
>>>>>> I am volunteering to start drafting a strawman and sharing that with the policy committee but I am looking for others to join the effort and volunteer too.
>>>>>>
>>>>>> 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
>>
>> http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient
>> Virus-free. [www.avg.com](http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient)
>>
>> #DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>>
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> --
>
> Matthew Shears
> matthew at intpolicy.com
> +447712472987
> Skype:mshears
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170810/aa10d99f/attachment.htm>

From icann at ferdeline.com  Fri Aug 11 02:39:36 2017
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Thu, 10 Aug 2017 19:39:36 -0400
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
	procedures change
In-Reply-To: <CAJjnsDEqpjdg98qrUw8PiKBuB=zy1bQJ8mmCbEcRfJRDMskuuA@mail.gmail.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <CAJjnsDEqpjdg98qrUw8PiKBuB=zy1bQJ8mmCbEcRfJRDMskuuA@mail.gmail.com>
Message-ID: <yCHeo5tWSpRyA3PBmD8gWZZ3YVEsa2Z1SrUg1Ysa7-byNOkcFJz0C6SbZAyl6ms02lPptjSLyxjvyKOi3cvjYzfudpzTvUr2Pz6ZYMkIzAA=@ferdeline.com>

Hi,

I have reviewed the comment, but I do not have enough knowledge of the proposed changes to the Operating Procedures to be able to speak to what our comment should or should not support. On that basis, I'll go with the majority view here - if other PC members support its submission, count me among them if you need it.

Thanks, Ayden

> -------- Original Message --------
> Subject: Re: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating procedures change
> Local Time: 10 August 2017 12:22 PM
> UTC Time: 10 August 2017 11:22
> From: mpsilvavalent at gmail.com
> To: Rafik Dammak <rafik.dammak at gmail.com>
> ncsg-pc <ncsg-pc at lists.ncsg.is>
>
> I also stated my support a while back, I maintain it.
>
> Cheers,
> Martin
>
> On 9 Aug 2017 9:03 pm, "Rafik Dammak" <rafik.dammak at gmail.com> wrote:
>
>> Hi all,
>>
>> the deadline for submission is this Friday. I attached the clean version for review. I understand that Matt, Poncelet, Stephanie support the comment. we need to hear from other PC members.
>>
>> Best,
>>
>> Rafik
>>
>> 2017-08-07 23:24 GMT+09:00 Stephanie Perrin <stephanie.perrin at mail.utoronto.ca>:
>>
>>> I think that is a really good idea, as these are important procedures, and we need to be able to amend if required.  Hard to anticipate everything, in my view...
>>>
>>> SP
>>>
>>> On 2017-08-07 08:49, farzaneh badii wrote:
>>>
>>>> Hi
>>>>
>>>> I was on the DT group. I don't have the time to go through every single change and see if they accord with what we agreed on. If you want in the public comment we should ask that if later on during implementing the operating procedures we find out that  changes recommended by  DT   for some reason are not reflected in the new  GNSO operating procedures, GNSO should follow the DT advice in those circumstances and allow for the mistake to be corrected.
>>>>
>>>> Farzaneh
>>>>
>>>> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> wrote:
>>>>
>>>>> It looks fine to me.  I don't have knowledge of or time to do the research on the issues at the moment, so I hope that those who do can catch things that need changes.
>>>>>
>>>>> cheers Stephanie
>>>>>
>>>>> On 2017-08-07 02:07, Rafik Dammak wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> the comment is quite straightforward and supporting the changes outlined in the public consultation.
>>>>>> we can have as the deadline for review and endorsement the 9th August. I urge councilors, in particular, to review the changes since it concerns the operating procedures.
>>>>>> Thanks, Matt again for the draft. I resolved the edits made by Ayden. ant proof-reading and review would be helpful.
>>>>>>
>>>>>> Best,
>>>>>>
>>>>>> Rafik
>>>>>>
>>>>>> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I have made some minor alterations to style, but added nothing of substance. I hope someone with more knowledge of this issue will be able to contribute to our comment. Submissions are due in six days time. Thanks!
>>>>>>>
>>>>>>> Best wishes, Ayden
>>>>>>>
>>>>>>>> -------- Original Message --------
>>>>>>>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures change
>>>>>>>> Local Time: August 1, 2017 5:35 PM
>>>>>>>> UTC Time: August 1, 2017 4:35 PM
>>>>>>>> From: matthew at intpolicy.com
>>>>>>>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM>
>>>>>>>>
>>>>>>>> Hi all
>>>>>>>>
>>>>>>>> Wanted to get this back at the top of the list of to-do's as time is running out.
>>>>>>>>
>>>>>>>> Appreciate the comments from some of the PC members but would welcome additional inputs, thoughts, etc.
>>>>>>>>
>>>>>>>> See google doc below.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> Matthew
>>>>>>>>
>>>>>>>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>>>>>
>>>>>>>>> Matt,
>>>>>>>>> I don?t have any comment to do, I agree with the statements and the wording. Let me know if I can do anything specific to help. Other than that you have my support. Thanks!
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Mart?n
>>>>>>>>>
>>>>>>>>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> the deadline for the public comment is the 10th of August, we have to finish consulting with NCSG members, review and endorsement prior to that. I suggest 8th August as our internal deadline.
>>>>>>>>>>
>>>>>>>>>> Best,
>>>>>>>>>>
>>>>>>>>>> Rafik
>>>>>>>>>>
>>>>>>>>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>>>>>>>>>
>>>>>>>>>>> Hi Matt, thanks. What's the deadline for this? I am in transit (and in fact, on holiday), witch sketchy internet access and the doc doesn't open for me today (might be the poor connection...)
>>>>>>>>>>>
>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>
>>>>>>>>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Let me qualify the last sentence - ICANN staff are not adding new items in addition to the work of the DT, but rather adding references to work done previously.
>>>>>>>>>>>>
>>>>>>>>>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Calling all PCers
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have started on the above public comment but am still going through the consultation docs.  However, time marches on and we need to get this one underway.
>>>>>>>>>>>>>
>>>>>>>>>>>>> So, please review the consultation docs here:
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>>>>>>>>>>
>>>>>>>>>>>>> And make comments in the google doc here:
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit
>>>>>>>>>>>>>
>>>>>>>>>>>>> Note that ICANN staff have used this opportunity to include other changes that the DT did not discuss.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Many thanks.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Matthew
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Matthew Shears
>>>>>>>>>>>>> matthew at intpolicy.com
>>>>>>>>>>>>>
>>>>>>>>>>>>> [+447712472987](tel:+44%207712%20472987)
>>>>>>>>>>>>>
>>>>>>>>>>>>> Skype:mshears
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Matthew Shears
>>>>>>>>>>>> matthew at intpolicy.com
>>>>>>>>>>>>
>>>>>>>>>>>> [+447712472987](tel:+44%207712%20472987)
>>>>>>>>>>>>
>>>>>>>>>>>> Skype:mshears
>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> NCSG-PC mailing list
>>>>>>>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>>>>>
>>>>>>>>>>> The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination, distribution, forwarding, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited without the express permission of the sender. If you received this communication in error, please contact the sender and delete the material from any computer.
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>> http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient
>>>>>>>>> Virus-free. [www.avg.com](http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient)
>>>>>>>>>
>>>>>>>>> ______________________________
>>>>>>>>>
>>>>>>>>> _________________
>>>>>>>>> NCSG-PC mailing list
>>>>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>>>>
>>>>>>>>> [https://lists.ncsg.is/mailman/
>>>>>>>>>
>>>>>>>>> listinfo/ncsg-pc](https://lists.ncsg.is/mailman/listinfo/ncsg-pc)
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Matthew Shears
>>>>>>>> matthew at intpolicy.com
>>>>>>>>
>>>>>>>> [+447712472987](tel:+44%207712%20472987)
>>>>>>>>
>>>>>>>> Skype:mshears
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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://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
>>
>> _______________________________________________
>> 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/20170810/7af315f3/attachment.htm>

From rafik.dammak at gmail.com  Fri Aug 11 05:33:31 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Fri, 11 Aug 2017 11:33:31 +0900
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <CAN1qJvC+jSTv1BAE3dtsOiejK3CmcWub7CxNP=E3=W9xaujxXg@mail.gmail.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
 <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
 <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>
 <CAH5sThkuLKYbzotNzga147d-OupdqKPJ24CnP9vvkqLb4BqVKA@mail.gmail.com>
 <CAN1qJvC+jSTv1BAE3dtsOiejK3CmcWub7CxNP=E3=W9xaujxXg@mail.gmail.com>
Message-ID: <CAH5sTh=7jRF6+5a9jtO1TgZwvfNxb3=Ftw=RpDbFmeWcth=d9w@mail.gmail.com>

Hi Matt, Stephanie,

can you please add the two suggested comments to the draft asap?
I see support for the draft but we should add those edits quickly.

Best,

Rafik

2017-08-10 17:45 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com>:

> I think we should add that. please also consider adding what I mentioned
> in my previous email. DT had a debate and reached consensus on many
> important issues which were contentious, mainly participation of GNSO in
> the empowered community through the council and the thresholds to reach
> decisions. As Stephanie agreed to add something like that, I kindly ask her
> to just come up with a once sentence which encompasses what I said in my
> previous email since she knows how the council functions better than I do.
>
> Farzaneh
>
> On Thu, Aug 10, 2017 at 4:37 AM, Rafik Dammak <rafik.dammak at gmail.com>
> wrote:
>
>> Hi Matt,
>>
>> I do think we can add a similar line to our comment .
>>
>> Best,
>>
>> Rafik
>>
>>
>> 2017-08-10 17:19 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>>
>>> I'm drawing it to the attention of the PC - the issue of the role of
>>> Council was a contentious one in the DT with the BC and other suggesting
>>> that the Council was exceeding its role if it took on EC responsibilities.
>>> NCSG and RySG were aligned on this seeing no issue with Council assuming
>>> the role.   My question was whether we thought we should add a similar line
>>> on the role of Council in our submission.
>>>
>>> Matthew
>>>
>>> On 10/08/2017 09:13, Rafik Dammak wrote:
>>>
>>> Hi Matt,
>>>
>>> are you suggesting a change to the comment? do you have some wording to
>>> add?
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> 2017-08-10 17:05 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>>>
>>>> Hi all
>>>>
>>>> I draw your attention to this submission by the RySG:
>>>>
>>>> http://mm.icann.org/pipermail/comments-gnso-op-procedures-19
>>>> jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOp
>>>> eratingProceduresandICANNBylaws-0001.pdf
>>>>
>>>> They note the following which we may wish to emulate (at a minimum the
>>>> first line I would have thought):
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *The RySG fully recognises the authority of the GNSO Council to speak
>>>> on behalf of the GNSO as Decisional Participant in the Empowered Community.
>>>> This is in line with current practice and working methods and respects the
>>>> existing equilibrium within the GNSO?s structure. The RySG agrees that on
>>>> this point no changes need to be made to the ICANN Bylaws in relation to
>>>> the role and description of the GNSO Council.*
>>>> Matthew
>>>>
>>>>
>>>>
>>>> On 10/08/2017 01:03, Rafik Dammak wrote:
>>>>
>>>> Hi all,
>>>>
>>>> the deadline for submission is this Friday. I attached the clean
>>>> version for review. I understand that Matt, Poncelet, Stephanie support the
>>>> comment. we need to hear from other PC members.
>>>>
>>>> Best,
>>>>
>>>> Rafik
>>>>
>>>> 2017-08-07 23:24 GMT+09:00 Stephanie Perrin <
>>>> stephanie.perrin at mail.utoronto.ca>:
>>>>
>>>>> I think that is a really good idea, as these are important procedures,
>>>>> and we need to be able to amend if required.  Hard to anticipate
>>>>> everything, in my view...
>>>>>
>>>>> SP
>>>>>
>>>>> On 2017-08-07 08:49, farzaneh badii wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> I was on the DT group. I don't have the time to go through every
>>>>> single change and see if they accord with what we agreed on. If you want in
>>>>> the public comment we should ask that if later on during implementing the
>>>>> operating procedures we find out that  changes recommended by  DT   for
>>>>> some reason are not reflected in the new  GNSO operating procedures, GNSO
>>>>> should follow the DT advice in those circumstances and allow for the
>>>>> mistake to be corrected.
>>>>>
>>>>> Farzaneh
>>>>>
>>>>> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <
>>>>> stephanie.perrin at mail.utoronto.ca> wrote:
>>>>>
>>>>>> It looks fine to me.  I don't have knowledge of or time to do the
>>>>>> research on the issues at the moment, so I hope that those who do can catch
>>>>>> things that need changes.
>>>>>>
>>>>>> cheers Stephanie
>>>>>>
>>>>>> On 2017-08-07 02:07, Rafik Dammak wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> the comment is quite straightforward and supporting the changes
>>>>>> outlined in the public consultation.
>>>>>> we can have as the deadline for review and endorsement the 9th
>>>>>> August. I urge councilors, in particular, to review the changes since it
>>>>>> concerns the operating procedures.
>>>>>> Thanks, Matt again for the draft. I resolved the edits made by Ayden.
>>>>>> ant proof-reading and review would be helpful.
>>>>>>
>>>>>> Best,
>>>>>>
>>>>>> Rafik
>>>>>>
>>>>>> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I have made some minor alterations to style, but added nothing of
>>>>>>> substance. I hope someone with more knowledge of this issue will be able to
>>>>>>> contribute to our comment. Submissions are due in six days time. Thanks!
>>>>>>>
>>>>>>> Best wishes, Ayden
>>>>>>>
>>>>>>>
>>>>>>> -------- Original Message --------
>>>>>>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures
>>>>>>> change
>>>>>>> Local Time: August 1, 2017 5:35 PM
>>>>>>> UTC Time: August 1, 2017 4:35 PM
>>>>>>> From: matthew at intpolicy.com
>>>>>>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM>
>>>>>>>
>>>>>>>
>>>>>>> Hi all
>>>>>>>
>>>>>>> Wanted to get this back at the top of the list of to-do's as time is
>>>>>>> running out.
>>>>>>>
>>>>>>> Appreciate the comments from some of the PC members but would
>>>>>>> welcome additional inputs, thoughts, etc.
>>>>>>>
>>>>>>> See google doc below.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> Matthew
>>>>>>>
>>>>>>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>>>>
>>>>>>> Matt,
>>>>>>> I don?t have any comment to do, I agree with the statements and the
>>>>>>> wording. Let me know if I can do anything specific to help. Other than that
>>>>>>> you have my support. Thanks!
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Mart?n
>>>>>>>
>>>>>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> the deadline for the public comment is the 10th of August, we have
>>>>>>> to finish consulting with NCSG members, review and endorsement prior to
>>>>>>> that. I suggest 8th August as our internal deadline.
>>>>>>>
>>>>>>> Best,
>>>>>>>
>>>>>>> Rafik
>>>>>>>
>>>>>>>
>>>>>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>>>>>>
>>>>>>> Hi Matt, thanks. What's the deadline for this? I am in transit (and
>>>>>>>> in fact, on holiday), witch sketchy internet access and the doc doesn't
>>>>>>>> open for me today (might be the poor connection...)
>>>>>>>>
>>>>>>>> Sent from my iPhone
>>>>>>>>
>>>>>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Let me qualify the last sentence - ICANN staff are not adding new
>>>>>>>> items in addition to the work of the DT, but rather adding references to
>>>>>>>> work done previously.
>>>>>>>>
>>>>>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>>>
>>>>>>>> Calling all PCers
>>>>>>>>
>>>>>>>> I have started on the above public comment but am still going
>>>>>>>> through the consultation docs.  However, time marches on and we need to get
>>>>>>>> this one underway.
>>>>>>>>
>>>>>>>> So, please review the consultation docs here:
>>>>>>>>
>>>>>>>> https://www.icann.org/public-comments/gnso-op-procedures-201
>>>>>>>> 7-06-19-en
>>>>>>>>
>>>>>>>> And make comments in the google doc here:
>>>>>>>>
>>>>>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>>>>>>> -ddk_Q9DWja7bZIgsiY/edit
>>>>>>>> Note that ICANN staff have used this opportunity to include other
>>>>>>>> changes that the DT did not discuss.
>>>>>>>>
>>>>>>>> Many thanks.
>>>>>>>>
>>>>>>>> Matthew
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> NCSG-PC mailing list
>>>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The information transmitted is intended only for the person or
>>>>>>>> entity to which it is addressed and may contain confidential and/or
>>>>>>>> privileged material. Any review, retransmission, dissemination,
>>>>>>>> distribution, forwarding, or other use of, or taking of any action in
>>>>>>>> reliance upon, this information by persons or entities other than the
>>>>>>>> intended recipient is prohibited without the express permission of the
>>>>>>>> sender. If you received this communication in error, please contact the
>>>>>>>> sender and delete the material from any computer.
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>> Virus-free. www.avg.com
>>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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 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 listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>
>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>>
>>>
>>>
>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
>>> www.avg.com
>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>> <#m_-670827426495722261_m_8430456596589667341_m_7701040911500582868_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>>
>>> --
>>>
>>>
>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>
>>>
>>
>> _______________________________________________
>> 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/20170811/35551db3/attachment.htm>

From matthew at intpolicy.com  Fri Aug 11 15:15:35 2017
From: matthew at intpolicy.com (Matthew Shears)
Date: Fri, 11 Aug 2017 13:15:35 +0100
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <CAH5sTh=7jRF6+5a9jtO1TgZwvfNxb3=Ftw=RpDbFmeWcth=d9w@mail.gmail.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
 <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
 <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>
 <CAH5sThkuLKYbzotNzga147d-OupdqKPJ24CnP9vvkqLb4BqVKA@mail.gmail.com>
 <CAN1qJvC+jSTv1BAE3dtsOiejK3CmcWub7CxNP=E3=W9xaujxXg@mail.gmail.com>
 <CAH5sTh=7jRF6+5a9jtO1TgZwvfNxb3=Ftw=RpDbFmeWcth=d9w@mail.gmail.com>
Message-ID: <dae73deb-65d5-64cb-f7f1-f8f7bf970b2b@intpolicy.com>

Hi

I have added a brief comment on the role of the GNSO Council. Please 
review carefully.

Note that the BC submission refers to this issue extensively.

Matthew


On 11/08/2017 03:33, Rafik Dammak wrote:
> Hi Matt, Stephanie,
>
> can you please add the two suggested comments to the draft asap?
> I see support for the draft but we should add those edits quickly.
>
> Best,
>
> Rafik
>
> 2017-08-10 17:45 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com 
> <mailto:farzaneh.badii at gmail.com>>:
>
>     I think we should add that. please also consider adding what I
>     mentioned in my previous email. DT had a debate and reached
>     consensus on many important issues which were contentious, mainly
>     participation of GNSO in the empowered community through the
>     council and the thresholds to reach decisions. As Stephanie agreed
>     to add something like that, I kindly ask her to just come up with
>     a once sentence which encompasses what I said in my previous email
>     since she knows how the council functions better than I do.
>
>     Farzaneh
>
>     On Thu, Aug 10, 2017 at 4:37 AM, Rafik Dammak
>     <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>> wrote:
>
>         Hi Matt,
>
>         I do think we can add a similar line to our comment .
>
>         Best,
>
>         Rafik
>
>
>         2017-08-10 17:19 GMT+09:00 Matthew Shears
>         <matthew at intpolicy.com <mailto:matthew at intpolicy.com>>:
>
>             I'm drawing it to the attention of the PC - the issue of
>             the role of Council was a contentious one in the DT with
>             the BC and other suggesting that the Council was exceeding
>             its role if it took on EC responsibilities. NCSG and RySG
>             were aligned on this seeing no issue with Council assuming
>             the role. My question was whether we thought we should add
>             a similar line on the role of Council in our submission.
>
>             Matthew
>
>
>             On 10/08/2017 09:13, Rafik Dammak wrote:
>>             Hi Matt,
>>
>>             are you suggesting a change to the comment? do you have
>>             some wording to add?
>>
>>             Best,
>>
>>             Rafik
>>
>>             2017-08-10 17:05 GMT+09:00 Matthew Shears
>>             <matthew at intpolicy.com <mailto:matthew at intpolicy.com>>:
>>
>>                 Hi all
>>
>>                 I draw your attention to this submission by the RySG:
>>
>>                 http://mm.icann.org/pipermail/comments-gnso-op-procedures-19jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOperatingProceduresandICANNBylaws-0001.pdf
>>                 <http://mm.icann.org/pipermail/comments-gnso-op-procedures-19jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOperatingProceduresandICANNBylaws-0001.pdf>
>>
>>                 They note the following which we may wish to emulate
>>                 (at a minimum the first line I would have thought):
>>
>>                 /The RySG fully recognises the authority of the GNSO
>>                 Council to speak on behalf of the GNSO as
>>                 Decisional Participant in the Empowered Community.
>>                 This is in line with current practice and
>>                 working methods and respects the existing equilibrium
>>                 within the GNSO?s structure. The RySG
>>                 agrees that on this point no changes need to be made
>>                 to the ICANN Bylaws in relation to the role
>>                 and description of the GNSO Council.///
>>
>>                 Matthew
>>
>>
>>
>>                 On 10/08/2017 01:03, Rafik Dammak wrote:
>>>                 Hi all,
>>>
>>>                 the deadline for submission is this Friday. I
>>>                 attached the clean version for review. I understand
>>>                 that Matt, Poncelet, Stephanie support the comment.
>>>                 we need to hear from other PC members.
>>>
>>>                 Best,
>>>
>>>                 Rafik
>>>
>>>                 2017-08-07 23:24 GMT+09:00 Stephanie Perrin
>>>                 <stephanie.perrin at mail.utoronto.ca
>>>                 <mailto:stephanie.perrin at mail.utoronto.ca>>:
>>>
>>>                     I think that is a really good idea, as these are
>>>                     important procedures, and we need to be able to
>>>                     amend if required. Hard to anticipate
>>>                     everything, in my view...
>>>
>>>                     SP
>>>
>>>
>>>                     On 2017-08-07 08:49, farzaneh badii wrote:
>>>>                     Hi
>>>>
>>>>                     I was on the DT group. I don't have the time to
>>>>                     go through every single change and see if they
>>>>                     accord with what we agreed on. If you want in
>>>>                     the public comment we should ask that if later
>>>>                     on during implementing the operating procedures
>>>>                     we find out that  changes recommended by  DT  
>>>>                     for some reason are not reflected in the new
>>>>                      GNSO operating procedures, GNSO should follow
>>>>                     the DT advice in those circumstances and allow
>>>>                     for the mistake to be corrected.
>>>>
>>>>                     Farzaneh
>>>>
>>>>                     On Mon, Aug 7, 2017 at 8:41 AM, Stephanie
>>>>                     Perrin <stephanie.perrin at mail.utoronto.ca
>>>>                     <mailto:stephanie.perrin at mail.utoronto.ca>> wrote:
>>>>
>>>>                         It looks fine to me.  I don't have
>>>>                         knowledge of or time to do the research on
>>>>                         the issues at the moment, so I hope that
>>>>                         those who do can catch things that need
>>>>                         changes.
>>>>
>>>>                         cheers Stephanie
>>>>
>>>>
>>>>                         On 2017-08-07 02:07, Rafik Dammak wrote:
>>>>>                         Hi,
>>>>>
>>>>>                         the comment is quite straightforward and
>>>>>                         supporting the changes outlined in the
>>>>>                         public consultation.
>>>>>                         we can have as the deadline for review and
>>>>>                         endorsement the 9th August. I urge
>>>>>                         councilors, in particular, to review the
>>>>>                         changes since it concerns the operating
>>>>>                         procedures.
>>>>>                         Thanks, Matt again for the draft. I
>>>>>                         resolved the edits made by Ayden. ant
>>>>>                         proof-reading and review would be helpful.
>>>>>
>>>>>                         Best,
>>>>>
>>>>>                         Rafik
>>>>>
>>>>>                         2017-08-05 6:33 GMT+09:00 Ayden F?rdeline
>>>>>                         <icann at ferdeline.com
>>>>>                         <mailto:icann at ferdeline.com>>:
>>>>>
>>>>>                             Hi all,
>>>>>
>>>>>                             I have made some minor alterations to
>>>>>                             style, but added nothing of substance.
>>>>>                             I hope someone with more knowledge of
>>>>>                             this issue will be able to contribute
>>>>>                             to our comment. Submissions are due in
>>>>>                             six days time. Thanks!
>>>>>
>>>>>                             Best wishes, Ayden
>>>>>
>>>>>
>>>>>>                             -------- Original Message --------
>>>>>>                             Subject: Re: [NCSG-PC] NCSG Comment
>>>>>>                             on GNSO operating procedures change
>>>>>>                             Local Time: August 1, 2017 5:35 PM
>>>>>>                             UTC Time: August 1, 2017 4:35 PM
>>>>>>                             From: matthew at intpolicy.com
>>>>>>                             <mailto:matthew at intpolicy.com>
>>>>>>                             To: ncsg-pc at lists.ncsg.is
>>>>>>                             <mailto:ncsg-pc at lists.ncsg.is>,
>>>>>>                             farzaneh badii
>>>>>>                             <farzaneh.badii at GMAIL.COM
>>>>>>                             <mailto:farzaneh.badii at GMAIL.COM>>
>>>>>>
>>>>>>
>>>>>>                             Hi all
>>>>>>
>>>>>>                             Wanted to get this back at the top of
>>>>>>                             the list of to-do's as time is
>>>>>>                             running out.
>>>>>>
>>>>>>                             Appreciate the comments from some of
>>>>>>                             the PC members but would welcome
>>>>>>                             additional inputs, thoughts, etc.
>>>>>>
>>>>>>                             See google doc below.
>>>>>>
>>>>>>                             Thanks.
>>>>>>
>>>>>>                             Matthew
>>>>>>
>>>>>>
>>>>>>                             On 27/07/2017 03:08, Martin Pablo
>>>>>>                             Silva Valent wrote:
>>>>>>>                             Matt,
>>>>>>>                             I don?t have any comment to do, I
>>>>>>>                             agree with the statements and the
>>>>>>>                             wording. Let me know if I can do
>>>>>>>                             anything specific to help. Other
>>>>>>>                             than that you have my support. Thanks!
>>>>>>>
>>>>>>>                             Cheers,
>>>>>>>                             Mart?n
>>>>>>>
>>>>>>>>                             On Jul 25, 2017, at 8:22 PM, Rafik
>>>>>>>>                             Dammak <rafik.dammak at gmail.com
>>>>>>>>                             <mailto:rafik.dammak at gmail.com>> wrote:
>>>>>>>>
>>>>>>>>                             Hi,
>>>>>>>>
>>>>>>>>                             the deadline for the public comment
>>>>>>>>                             is the 10th of August, we have to
>>>>>>>>                             finish consulting with NCSG
>>>>>>>>                             members, review and endorsement
>>>>>>>>                             prior to that. I suggest 8th August
>>>>>>>>                             as our internal deadline.
>>>>>>>>
>>>>>>>>                             Best,
>>>>>>>>
>>>>>>>>                             Rafik
>>>>>>>>
>>>>>>>>
>>>>>>>>                             2017-07-25 23:28 GMT+09:00 Stefania
>>>>>>>>                             Milan <stefania.milan at eui.eu
>>>>>>>>                             <mailto:stefania.milan at eui.eu>>:
>>>>>>>>
>>>>>>>>                                 Hi Matt, thanks. What's the
>>>>>>>>                                 deadline for this? I am in
>>>>>>>>                                 transit (and in fact, on
>>>>>>>>                                 holiday), witch sketchy
>>>>>>>>                                 internet access and the doc
>>>>>>>>                                 doesn't open for me today
>>>>>>>>                                 (might be the poor connection...)
>>>>>>>>
>>>>>>>>                                 Sent from my iPhone
>>>>>>>>
>>>>>>>>                                 On Jul 25, 2017, at 9:17 AM,
>>>>>>>>                                 Matthew Shears
>>>>>>>>                                 <matthew at intpolicy.com
>>>>>>>>                                 <mailto:matthew at intpolicy.com>>
>>>>>>>>                                 wrote:
>>>>>>>>
>>>>>>>>>                                 Let me qualify the last
>>>>>>>>>                                 sentence - ICANN staff are not
>>>>>>>>>                                 adding new items in addition
>>>>>>>>>                                 to the work of the DT, but
>>>>>>>>>                                 rather adding references to
>>>>>>>>>                                 work done previously.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                                 On 25/07/2017 16:05, Matthew
>>>>>>>>>                                 Shears wrote:
>>>>>>>>>>                                 Calling all PCers
>>>>>>>>>>
>>>>>>>>>>                                 I have started on the above
>>>>>>>>>>                                 public comment but am still
>>>>>>>>>>                                 going through the
>>>>>>>>>>                                 consultation docs. However,
>>>>>>>>>>                                 time marches on and we need
>>>>>>>>>>                                 to get this one underway.
>>>>>>>>>>
>>>>>>>>>>                                 So, please review the
>>>>>>>>>>                                 consultation docs here:
>>>>>>>>>>
>>>>>>>>>>                                 https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>>>>>>>                                 <https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en>
>>>>>>>>>>
>>>>>>>>>>                                 And make comments in the
>>>>>>>>>>                                 google doc here:
>>>>>>>>>>
>>>>>>>>>>                                 https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit
>>>>>>>>>>                                 <https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit>
>>>>>>>>>>
>>>>>>>>>>                                 Note that ICANN staff have
>>>>>>>>>>                                 used this opportunity to
>>>>>>>>>>                                 include other changes that
>>>>>>>>>>                                 the DT did not discuss.
>>>>>>>>>>
>>>>>>>>>>                                 Many thanks.
>>>>>>>>>>
>>>>>>>>>>                                 Matthew
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                                 -- 
>>>>>>>>>>                                 Matthew Shears
>>>>>>>>>>                                 matthew at intpolicy.com
>>>>>>>>>>                                 <mailto:matthew at intpolicy.com>
>>>>>>>>>>                                 +447712472987
>>>>>>>>>>                                 <tel:+44%207712%20472987>
>>>>>>>>>>                                 Skype:mshears
>>>>>>>>>
>>>>>>>>>                                 -- 
>>>>>>>>>                                 Matthew Shears
>>>>>>>>>                                 matthew at intpolicy.com
>>>>>>>>>                                 <mailto:matthew at intpolicy.com>
>>>>>>>>>                                 +447712472987
>>>>>>>>>                                 <tel:+44%207712%20472987>
>>>>>>>>>                                 Skype:mshears
>>>>>>>>>                                 _______________________________________________
>>>>>>>>>                                 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>
>>>>>>>>
>>>>>>>>
>>>>>>>>                                 The information transmitted is
>>>>>>>>                                 intended only for the person or
>>>>>>>>                                 entity to which it is addressed
>>>>>>>>                                 and may contain confidential
>>>>>>>>                                 and/or privileged material. Any
>>>>>>>>                                 review, retransmission,
>>>>>>>>                                 dissemination, distribution,
>>>>>>>>                                 forwarding, or other use of, or
>>>>>>>>                                 taking of any action in
>>>>>>>>                                 reliance upon, this information
>>>>>>>>                                 by persons or entities other
>>>>>>>>                                 than the intended recipient is
>>>>>>>>                                 prohibited without the express
>>>>>>>>                                 permission of the sender. If
>>>>>>>>                                 you received this communication
>>>>>>>>                                 in error, please contact the
>>>>>>>>                                 sender and delete the material
>>>>>>>>                                 from any computer.
>>>>>>>>
>>>>>>>>
>>>>>>>>                                 _______________________________________________
>>>>>>>>                                 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>
>>>>>>>
>>>>>>>
>>>>>>>                             <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>                             	Virus-free. www.avg.com
>>>>>>>                             <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>                             _______________________________________________
>>>>>>>                             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>
>>>>>>>
>>>>>>
>>>>>>                             -- 
>>>>>>
>>>>>>
>>>>>>                             Matthew Shears
>>>>>>                             matthew at intpolicy.com
>>>>>>                             <mailto:matthew at intpolicy.com>
>>>>>>                             +447712472987 <tel:+44%207712%20472987>
>>>>>>                             Skype:mshears
>>>>>
>>>>>
>>>>>                             _______________________________________________
>>>>>                             NCSG-PC mailing list
>>>>>                             NCSG-PC at lists.ncsg.is
>>>>>                             <mailto:NCSG-PC at lists.ncsg.is>
>>>>>                             https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>                             <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>                         _______________________________________________
>>>>>                         NCSG-PC mailing list
>>>>>                         NCSG-PC at lists.ncsg.is
>>>>>                         <mailto:NCSG-PC at lists.ncsg.is>
>>>>>                         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>                         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>
>>>>
>>>>                         _______________________________________________
>>>>                         NCSG-PC mailing list
>>>>                         NCSG-PC at lists.ncsg.is
>>>>                         <mailto:NCSG-PC at lists.ncsg.is>
>>>>                         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>                         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>
>>>>
>>>
>>>
>>>                     _______________________________________________
>>>                     NCSG-PC mailing list
>>>                     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>                     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>                     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>
>>>
>>>
>>>
>>>                 _______________________________________________
>>>                 NCSG-PC mailing list
>>>                 NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>                 https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>                 <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>
>>                 -- 
>>
>>
>>                 Matthew Shears
>>                 matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>                 +447712472987 <tel:+44%207712%20472987>
>>                 Skype:mshears
>>
>>
>>                 _______________________________________________
>>                 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>
>>
>>
>>
>>             <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>             	Virus-free. www.avg.com
>>             <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>
>>
>>             <#m_-670827426495722261_m_8430456596589667341_m_7701040911500582868_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>             -- 
>
>
>             Matthew Shears
>             matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>             +447712472987 <tel:+44%207712%20472987>
>             Skype:mshears
>
>
>
>         _______________________________________________
>         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>
>
>
>

-- 


Matthew Shears
matthew at intpolicy.com
+447712472987
Skype:mshears

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

From stephanie.perrin at mail.utoronto.ca  Fri Aug 11 17:14:59 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Fri, 11 Aug 2017 10:14:59 -0400
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <dae73deb-65d5-64cb-f7f1-f8f7bf970b2b@intpolicy.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
 <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
 <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>
 <CAH5sThkuLKYbzotNzga147d-OupdqKPJ24CnP9vvkqLb4BqVKA@mail.gmail.com>
 <CAN1qJvC+jSTv1BAE3dtsOiejK3CmcWub7CxNP=E3=W9xaujxXg@mail.gmail.com>
 <CAH5sTh=7jRF6+5a9jtO1TgZwvfNxb3=Ftw=RpDbFmeWcth=d9w@mail.gmail.com>
 <dae73deb-65d5-64cb-f7f1-f8f7bf970b2b@intpolicy.com>
Message-ID: <15206a94-ec0c-3d6c-2b63-57eb5e9bea66@mail.utoronto.ca>

I think it looks fine now.  I endorse it!

cheers SP


On 2017-08-11 08:15, Matthew Shears wrote:
>
> Hi
>
> I have added a brief comment on the role of the GNSO Council. Please 
> review carefully.
>
> Note that the BC submission refers to this issue extensively.
>
> Matthew
>
>
> On 11/08/2017 03:33, Rafik Dammak wrote:
>> Hi Matt, Stephanie,
>>
>> can you please add the two suggested comments to the draft asap?
>> I see support for the draft but we should add those edits quickly.
>>
>> Best,
>>
>> Rafik
>>
>> 2017-08-10 17:45 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com 
>> <mailto:farzaneh.badii at gmail.com>>:
>>
>>     I think we should add that. please also consider adding what I
>>     mentioned in my previous email. DT had a debate and reached
>>     consensus on many important issues which were contentious, mainly
>>     participation of GNSO in the empowered community through the
>>     council and the thresholds to reach decisions. As Stephanie
>>     agreed to add something like that, I kindly ask her to just come
>>     up with a once sentence which encompasses what I said in my
>>     previous email since she knows how the council functions better
>>     than I do.
>>
>>     Farzaneh
>>
>>     On Thu, Aug 10, 2017 at 4:37 AM, Rafik Dammak
>>     <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>> wrote:
>>
>>         Hi Matt,
>>
>>         I do think we can add a similar line to our comment .
>>
>>         Best,
>>
>>         Rafik
>>
>>
>>         2017-08-10 17:19 GMT+09:00 Matthew Shears
>>         <matthew at intpolicy.com <mailto:matthew at intpolicy.com>>:
>>
>>             I'm drawing it to the attention of the PC - the issue of
>>             the role of Council was a contentious one in the DT with
>>             the BC and other suggesting that the Council was
>>             exceeding its role if it took on EC responsibilities. 
>>             NCSG and RySG were aligned on this seeing no issue with
>>             Council assuming the role.   My question was whether we
>>             thought we should add a similar line on the role of
>>             Council in our submission.
>>
>>             Matthew
>>
>>
>>             On 10/08/2017 09:13, Rafik Dammak wrote:
>>>             Hi Matt,
>>>
>>>             are you suggesting a change to the comment? do you have
>>>             some wording to add?
>>>
>>>             Best,
>>>
>>>             Rafik
>>>
>>>             2017-08-10 17:05 GMT+09:00 Matthew Shears
>>>             <matthew at intpolicy.com <mailto:matthew at intpolicy.com>>:
>>>
>>>                 Hi all
>>>
>>>                 I draw your attention to this submission by the RySG:
>>>
>>>                 http://mm.icann.org/pipermail/comments-gnso-op-procedures-19jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOperatingProceduresandICANNBylaws-0001.pdf
>>>                 <http://mm.icann.org/pipermail/comments-gnso-op-procedures-19jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOperatingProceduresandICANNBylaws-0001.pdf>
>>>
>>>                 They note the following which we may wish to emulate
>>>                 (at a minimum the first line I would have thought):
>>>
>>>                 /The RySG fully recognises the authority of the GNSO
>>>                 Council to speak on behalf of the GNSO as
>>>                 Decisional Participant in the Empowered Community.
>>>                 This is in line with current practice and
>>>                 working methods and respects the existing
>>>                 equilibrium within the GNSO?s structure. The RySG
>>>                 agrees that on this point no changes need to be made
>>>                 to the ICANN Bylaws in relation to the role
>>>                 and description of the GNSO Council.///
>>>
>>>                 Matthew
>>>
>>>
>>>
>>>                 On 10/08/2017 01:03, Rafik Dammak wrote:
>>>>                 Hi all,
>>>>
>>>>                 the deadline for submission is this Friday. I
>>>>                 attached the clean version for review. I understand
>>>>                 that Matt, Poncelet, Stephanie support the comment.
>>>>                 we need to hear from other PC members.
>>>>
>>>>                 Best,
>>>>
>>>>                 Rafik
>>>>
>>>>                 2017-08-07 23:24 GMT+09:00 Stephanie Perrin
>>>>                 <stephanie.perrin at mail.utoronto.ca
>>>>                 <mailto:stephanie.perrin at mail.utoronto.ca>>:
>>>>
>>>>                     I think that is a really good idea, as these
>>>>                     are important procedures, and we need to be
>>>>                     able to amend if required. Hard to anticipate
>>>>                     everything, in my view...
>>>>
>>>>                     SP
>>>>
>>>>
>>>>                     On 2017-08-07 08:49, farzaneh badii wrote:
>>>>>                     Hi
>>>>>
>>>>>                     I was on the DT group. I don't have the time
>>>>>                     to go through every single change and see if
>>>>>                     they accord with what we agreed on. If you
>>>>>                     want in the public comment we should ask that
>>>>>                     if later on during implementing the operating
>>>>>                     procedures we find out that
>>>>>                      changes recommended by  DT   for some reason
>>>>>                     are not reflected in the new  GNSO operating
>>>>>                     procedures, GNSO should follow the DT advice
>>>>>                     in those circumstances and allow for the
>>>>>                     mistake to be corrected.
>>>>>
>>>>>                     Farzaneh
>>>>>
>>>>>                     On Mon, Aug 7, 2017 at 8:41 AM, Stephanie
>>>>>                     Perrin <stephanie.perrin at mail.utoronto.ca
>>>>>                     <mailto:stephanie.perrin at mail.utoronto.ca>> wrote:
>>>>>
>>>>>                         It looks fine to me.  I don't have
>>>>>                         knowledge of or time to do the research on
>>>>>                         the issues at the moment, so I hope that
>>>>>                         those who do can catch things that need
>>>>>                         changes.
>>>>>
>>>>>                         cheers Stephanie
>>>>>
>>>>>
>>>>>                         On 2017-08-07 02:07, Rafik Dammak wrote:
>>>>>>                         Hi,
>>>>>>
>>>>>>                         the comment is quite straightforward and
>>>>>>                         supporting the changes outlined in the
>>>>>>                         public consultation.
>>>>>>                         we can have as the deadline for review
>>>>>>                         and endorsement the 9th August. I urge
>>>>>>                         councilors, in particular, to review the
>>>>>>                         changes since it concerns the operating
>>>>>>                         procedures.
>>>>>>                         Thanks, Matt again for the draft. I
>>>>>>                         resolved the edits made by Ayden. ant
>>>>>>                         proof-reading and review would be helpful.
>>>>>>
>>>>>>                         Best,
>>>>>>
>>>>>>                         Rafik
>>>>>>
>>>>>>                         2017-08-05 6:33 GMT+09:00 Ayden F?rdeline
>>>>>>                         <icann at ferdeline.com
>>>>>>                         <mailto:icann at ferdeline.com>>:
>>>>>>
>>>>>>                             Hi all,
>>>>>>
>>>>>>                             I have made some minor alterations to
>>>>>>                             style, but added nothing of
>>>>>>                             substance. I hope someone with more
>>>>>>                             knowledge of this issue will be able
>>>>>>                             to contribute to our comment.
>>>>>>                             Submissions are due in six days time.
>>>>>>                             Thanks!
>>>>>>
>>>>>>                             Best wishes, Ayden
>>>>>>
>>>>>>
>>>>>>>                             -------- Original Message --------
>>>>>>>                             Subject: Re: [NCSG-PC] NCSG Comment
>>>>>>>                             on GNSO operating procedures change
>>>>>>>                             Local Time: August 1, 2017 5:35 PM
>>>>>>>                             UTC Time: August 1, 2017 4:35 PM
>>>>>>>                             From: matthew at intpolicy.com
>>>>>>>                             <mailto:matthew at intpolicy.com>
>>>>>>>                             To: ncsg-pc at lists.ncsg.is
>>>>>>>                             <mailto:ncsg-pc at lists.ncsg.is>,
>>>>>>>                             farzaneh badii
>>>>>>>                             <farzaneh.badii at GMAIL.COM
>>>>>>>                             <mailto:farzaneh.badii at GMAIL.COM>>
>>>>>>>
>>>>>>>
>>>>>>>                             Hi all
>>>>>>>
>>>>>>>                             Wanted to get this back at the top
>>>>>>>                             of the list of to-do's as time is
>>>>>>>                             running out.
>>>>>>>
>>>>>>>                             Appreciate the comments from some of
>>>>>>>                             the PC members but would welcome
>>>>>>>                             additional inputs, thoughts, etc.
>>>>>>>
>>>>>>>                             See google doc below.
>>>>>>>
>>>>>>>                             Thanks.
>>>>>>>
>>>>>>>                             Matthew
>>>>>>>
>>>>>>>
>>>>>>>                             On 27/07/2017 03:08, Martin Pablo
>>>>>>>                             Silva Valent wrote:
>>>>>>>>                             Matt,
>>>>>>>>                             I don?t have any comment to do, I
>>>>>>>>                             agree with the statements and the
>>>>>>>>                             wording. Let me know if I can do
>>>>>>>>                             anything specific to help. Other
>>>>>>>>                             than that you have my support. Thanks!
>>>>>>>>
>>>>>>>>                             Cheers,
>>>>>>>>                             Mart?n
>>>>>>>>
>>>>>>>>>                             On Jul 25, 2017, at 8:22 PM, Rafik
>>>>>>>>>                             Dammak <rafik.dammak at gmail.com
>>>>>>>>>                             <mailto:rafik.dammak at gmail.com>>
>>>>>>>>>                             wrote:
>>>>>>>>>
>>>>>>>>>                             Hi,
>>>>>>>>>
>>>>>>>>>                             the deadline for the public
>>>>>>>>>                             comment is the 10th of August, we
>>>>>>>>>                             have to finish consulting with
>>>>>>>>>                             NCSG members, review and
>>>>>>>>>                             endorsement prior to that. I
>>>>>>>>>                             suggest 8th August as our internal
>>>>>>>>>                             deadline.
>>>>>>>>>
>>>>>>>>>                             Best,
>>>>>>>>>
>>>>>>>>>                             Rafik
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                             2017-07-25 23:28 GMT+09:00
>>>>>>>>>                             Stefania Milan
>>>>>>>>>                             <stefania.milan at eui.eu
>>>>>>>>>                             <mailto:stefania.milan at eui.eu>>:
>>>>>>>>>
>>>>>>>>>                                 Hi Matt, thanks. What's the
>>>>>>>>>                                 deadline for this? I am in
>>>>>>>>>                                 transit (and in fact, on
>>>>>>>>>                                 holiday), witch sketchy
>>>>>>>>>                                 internet access and the doc
>>>>>>>>>                                 doesn't open for me today
>>>>>>>>>                                 (might be the poor connection...)
>>>>>>>>>
>>>>>>>>>                                 Sent from my iPhone
>>>>>>>>>
>>>>>>>>>                                 On Jul 25, 2017, at 9:17 AM,
>>>>>>>>>                                 Matthew Shears
>>>>>>>>>                                 <matthew at intpolicy.com
>>>>>>>>>                                 <mailto:matthew at intpolicy.com>>
>>>>>>>>>                                 wrote:
>>>>>>>>>
>>>>>>>>>>                                 Let me qualify the last
>>>>>>>>>>                                 sentence - ICANN staff are
>>>>>>>>>>                                 not adding new items in
>>>>>>>>>>                                 addition to the work of the
>>>>>>>>>>                                 DT, but rather adding
>>>>>>>>>>                                 references to work done
>>>>>>>>>>                                 previously.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                                 On 25/07/2017 16:05, Matthew
>>>>>>>>>>                                 Shears wrote:
>>>>>>>>>>>                                 Calling all PCers
>>>>>>>>>>>
>>>>>>>>>>>                                 I have started on the above
>>>>>>>>>>>                                 public comment but am still
>>>>>>>>>>>                                 going through the
>>>>>>>>>>>                                 consultation docs. However,
>>>>>>>>>>>                                 time marches on and we need
>>>>>>>>>>>                                 to get this one underway.
>>>>>>>>>>>
>>>>>>>>>>>                                 So, please review the
>>>>>>>>>>>                                 consultation docs here:
>>>>>>>>>>>
>>>>>>>>>>>                                 https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>>>>>>>>                                 <https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en>
>>>>>>>>>>>
>>>>>>>>>>>                                 And make comments in the
>>>>>>>>>>>                                 google doc here:
>>>>>>>>>>>
>>>>>>>>>>>                                 https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit
>>>>>>>>>>>                                 <https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit>
>>>>>>>>>>>
>>>>>>>>>>>                                 Note that ICANN staff have
>>>>>>>>>>>                                 used this opportunity to
>>>>>>>>>>>                                 include other changes that
>>>>>>>>>>>                                 the DT did not discuss.
>>>>>>>>>>>
>>>>>>>>>>>                                 Many thanks.
>>>>>>>>>>>
>>>>>>>>>>>                                 Matthew
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>                                 -- 
>>>>>>>>>>>                                 Matthew Shears
>>>>>>>>>>>                                 matthew at intpolicy.com
>>>>>>>>>>>                                 <mailto:matthew at intpolicy.com>
>>>>>>>>>>>                                 +447712472987
>>>>>>>>>>>                                 <tel:+44%207712%20472987>
>>>>>>>>>>>                                 Skype:mshears
>>>>>>>>>>
>>>>>>>>>>                                 -- 
>>>>>>>>>>                                 Matthew Shears
>>>>>>>>>>                                 matthew at intpolicy.com
>>>>>>>>>>                                 <mailto:matthew at intpolicy.com>
>>>>>>>>>>                                 +447712472987
>>>>>>>>>>                                 <tel:+44%207712%20472987>
>>>>>>>>>>                                 Skype:mshears
>>>>>>>>>>                                 _______________________________________________
>>>>>>>>>>                                 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>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                                 The information transmitted is
>>>>>>>>>                                 intended only for the person
>>>>>>>>>                                 or entity to which it is
>>>>>>>>>                                 addressed and may contain
>>>>>>>>>                                 confidential and/or privileged
>>>>>>>>>                                 material. Any review,
>>>>>>>>>                                 retransmission, dissemination,
>>>>>>>>>                                 distribution, forwarding, or
>>>>>>>>>                                 other use of, or taking of any
>>>>>>>>>                                 action in reliance upon, this
>>>>>>>>>                                 information by persons or
>>>>>>>>>                                 entities other than the
>>>>>>>>>                                 intended recipient is
>>>>>>>>>                                 prohibited without the express
>>>>>>>>>                                 permission of the sender. If
>>>>>>>>>                                 you received this
>>>>>>>>>                                 communication in error, please
>>>>>>>>>                                 contact the sender and delete
>>>>>>>>>                                 the material from any computer.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                                 _______________________________________________
>>>>>>>>>                                 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>
>>>>>>>>
>>>>>>>>
>>>>>>>>                             <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>>                             	Virus-free. www.avg.com
>>>>>>>>                             <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>                             _______________________________________________
>>>>>>>>                             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>
>>>>>>>>
>>>>>>>
>>>>>>>                             -- 
>>>>>>>
>>>>>>>
>>>>>>>                             Matthew Shears
>>>>>>>                             matthew at intpolicy.com
>>>>>>>                             <mailto:matthew at intpolicy.com>
>>>>>>>                             +447712472987 <tel:+44%207712%20472987>
>>>>>>>                             Skype:mshears
>>>>>>
>>>>>>
>>>>>>                             _______________________________________________
>>>>>>                             NCSG-PC mailing list
>>>>>>                             NCSG-PC at lists.ncsg.is
>>>>>>                             <mailto:NCSG-PC at lists.ncsg.is>
>>>>>>                             https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>                             <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>                         _______________________________________________
>>>>>>                         NCSG-PC mailing list
>>>>>>                         NCSG-PC at lists.ncsg.is
>>>>>>                         <mailto:NCSG-PC at lists.ncsg.is>
>>>>>>                         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>                         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>>
>>>>>
>>>>>                         _______________________________________________
>>>>>                         NCSG-PC mailing list
>>>>>                         NCSG-PC at lists.ncsg.is
>>>>>                         <mailto:NCSG-PC at lists.ncsg.is>
>>>>>                         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>                         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>>
>>>>>
>>>>
>>>>
>>>>                     _______________________________________________
>>>>                     NCSG-PC mailing list
>>>>                     NCSG-PC at lists.ncsg.is
>>>>                     <mailto:NCSG-PC at lists.ncsg.is>
>>>>                     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>                     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>
>>>>
>>>>
>>>>
>>>>                 _______________________________________________
>>>>                 NCSG-PC mailing list
>>>>                 NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>>                 https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>                 <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>
>>>                 -- 
>>>
>>>
>>>                 Matthew Shears
>>>                 matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>                 +447712472987 <tel:+44%207712%20472987>
>>>                 Skype:mshears
>>>
>>>
>>>                 _______________________________________________
>>>                 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>
>>>
>>>
>>>
>>>             <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>             	Virus-free. www.avg.com
>>>             <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>
>>>
>>>             <#m_-670827426495722261_m_8430456596589667341_m_7701040911500582868_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>>             -- 
>>
>>
>>             Matthew Shears
>>             matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>             +447712472987 <tel:+44%207712%20472987>
>>             Skype:mshears
>>
>>
>>
>>         _______________________________________________
>>         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>
>>
>>
>>
>
> -- 
>
>
> Matthew Shears
> matthew at intpolicy.com
> +447712472987
> Skype:mshears

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

From farzaneh.badii at gmail.com  Fri Aug 11 17:44:29 2017
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Fri, 11 Aug 2017 10:44:29 -0400
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <15206a94-ec0c-3d6c-2b63-57eb5e9bea66@mail.utoronto.ca>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
 <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
 <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>
 <CAH5sThkuLKYbzotNzga147d-OupdqKPJ24CnP9vvkqLb4BqVKA@mail.gmail.com>
 <CAN1qJvC+jSTv1BAE3dtsOiejK3CmcWub7CxNP=E3=W9xaujxXg@mail.gmail.com>
 <CAH5sTh=7jRF6+5a9jtO1TgZwvfNxb3=Ftw=RpDbFmeWcth=d9w@mail.gmail.com>
 <dae73deb-65d5-64cb-f7f1-f8f7bf970b2b@intpolicy.com>
 <15206a94-ec0c-3d6c-2b63-57eb5e9bea66@mail.utoronto.ca>
Message-ID: <CAN1qJvDrx=-uh_vBk_-WFekcjzv9HOXQ-qQ62hfGux3MKZOkvg@mail.gmail.com>

So I gather that there was not support for my suggested addition. I will
not add it in the document. I also find this sentence problematic:"Finally,
we should note that there was disagreement in the DT as to who should speak
on behalf of the GNSO as a Decisional Participant in the Empowered
Community. " there was disagreement but we reached consensus. This sentence
is not drafted carefully to reflect that there was consensus and only
emphasizes on the disagreement. I suggest reframing it like this: Finally,
we should note that the DT reached a consensus that *GNSO Council* should
speak on behalf of the GNSO as a Decisional Participant in the Empowered
Community.

Farzaneh

On Fri, Aug 11, 2017 at 10:14 AM, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> wrote:

> I think it looks fine now.  I endorse it!
>
> cheers SP
>
> On 2017-08-11 08:15, Matthew Shears wrote:
>
> Hi
>
> I have added a brief comment on the role of the GNSO Council.  Please
> review carefully.
>
> Note that the BC submission refers to this issue extensively.
>
> Matthew
>
> On 11/08/2017 03:33, Rafik Dammak wrote:
>
> Hi Matt, Stephanie,
>
> can you please add the two suggested comments to the draft asap?
> I see support for the draft but we should add those edits quickly.
>
> Best,
>
> Rafik
>
> 2017-08-10 17:45 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com>:
>
>> I think we should add that. please also consider adding what I mentioned
>> in my previous email. DT had a debate and reached consensus on many
>> important issues which were contentious, mainly participation of GNSO in
>> the empowered community through the council and the thresholds to reach
>> decisions. As Stephanie agreed to add something like that, I kindly ask her
>> to just come up with a once sentence which encompasses what I said in my
>> previous email since she knows how the council functions better than I do.
>>
>> Farzaneh
>>
>> On Thu, Aug 10, 2017 at 4:37 AM, Rafik Dammak <rafik.dammak at gmail.com>
>> wrote:
>>
>>> Hi Matt,
>>>
>>> I do think we can add a similar line to our comment .
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>>
>>> 2017-08-10 17:19 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>>>
>>>> I'm drawing it to the attention of the PC - the issue of the role of
>>>> Council was a contentious one in the DT with the BC and other suggesting
>>>> that the Council was exceeding its role if it took on EC responsibilities.
>>>> NCSG and RySG were aligned on this seeing no issue with Council assuming
>>>> the role.   My question was whether we thought we should add a similar line
>>>> on the role of Council in our submission.
>>>>
>>>> Matthew
>>>>
>>>> On 10/08/2017 09:13, Rafik Dammak wrote:
>>>>
>>>> Hi Matt,
>>>>
>>>> are you suggesting a change to the comment? do you have some wording to
>>>> add?
>>>>
>>>> Best,
>>>>
>>>> Rafik
>>>>
>>>> 2017-08-10 17:05 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>>>>
>>>>> Hi all
>>>>>
>>>>> I draw your attention to this submission by the RySG:
>>>>>
>>>>> http://mm.icann.org/pipermail/comments-gnso-op-procedures-19
>>>>> jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOp
>>>>> eratingProceduresandICANNBylaws-0001.pdf
>>>>>
>>>>> They note the following which we may wish to emulate (at a minimum the
>>>>> first line I would have thought):
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *The RySG fully recognises the authority of the GNSO Council to speak
>>>>> on behalf of the GNSO as Decisional Participant in the Empowered Community.
>>>>> This is in line with current practice and working methods and respects the
>>>>> existing equilibrium within the GNSO?s structure. The RySG agrees that on
>>>>> this point no changes need to be made to the ICANN Bylaws in relation to
>>>>> the role and description of the GNSO Council.*
>>>>> Matthew
>>>>>
>>>>>
>>>>>
>>>>> On 10/08/2017 01:03, Rafik Dammak wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> the deadline for submission is this Friday. I attached the clean
>>>>> version for review. I understand that Matt, Poncelet, Stephanie support the
>>>>> comment. we need to hear from other PC members.
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>>> 2017-08-07 23:24 GMT+09:00 Stephanie Perrin <
>>>>> stephanie.perrin at mail.utoronto.ca>:
>>>>>
>>>>>> I think that is a really good idea, as these are important
>>>>>> procedures, and we need to be able to amend if required.  Hard to
>>>>>> anticipate everything, in my view...
>>>>>>
>>>>>> SP
>>>>>>
>>>>>> On 2017-08-07 08:49, farzaneh badii wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> I was on the DT group. I don't have the time to go through every
>>>>>> single change and see if they accord with what we agreed on. If you want in
>>>>>> the public comment we should ask that if later on during implementing the
>>>>>> operating procedures we find out that  changes recommended by  DT   for
>>>>>> some reason are not reflected in the new  GNSO operating procedures, GNSO
>>>>>> should follow the DT advice in those circumstances and allow for the
>>>>>> mistake to be corrected.
>>>>>>
>>>>>> Farzaneh
>>>>>>
>>>>>> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <
>>>>>> stephanie.perrin at mail.utoronto.ca> wrote:
>>>>>>
>>>>>>> It looks fine to me.  I don't have knowledge of or time to do the
>>>>>>> research on the issues at the moment, so I hope that those who do can catch
>>>>>>> things that need changes.
>>>>>>>
>>>>>>> cheers Stephanie
>>>>>>>
>>>>>>> On 2017-08-07 02:07, Rafik Dammak wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> the comment is quite straightforward and supporting the changes
>>>>>>> outlined in the public consultation.
>>>>>>> we can have as the deadline for review and endorsement the 9th
>>>>>>> August. I urge councilors, in particular, to review the changes since it
>>>>>>> concerns the operating procedures.
>>>>>>> Thanks, Matt again for the draft. I resolved the edits made by
>>>>>>> Ayden. ant proof-reading and review would be helpful.
>>>>>>>
>>>>>>> Best,
>>>>>>>
>>>>>>> Rafik
>>>>>>>
>>>>>>> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I have made some minor alterations to style, but added nothing of
>>>>>>>> substance. I hope someone with more knowledge of this issue will be able to
>>>>>>>> contribute to our comment. Submissions are due in six days time. Thanks!
>>>>>>>>
>>>>>>>> Best wishes, Ayden
>>>>>>>>
>>>>>>>>
>>>>>>>> -------- Original Message --------
>>>>>>>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures
>>>>>>>> change
>>>>>>>> Local Time: August 1, 2017 5:35 PM
>>>>>>>> UTC Time: August 1, 2017 4:35 PM
>>>>>>>> From: matthew at intpolicy.com
>>>>>>>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <farzaneh.badii at GMAIL.COM
>>>>>>>> >
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi all
>>>>>>>>
>>>>>>>> Wanted to get this back at the top of the list of to-do's as time
>>>>>>>> is running out.
>>>>>>>>
>>>>>>>> Appreciate the comments from some of the PC members but would
>>>>>>>> welcome additional inputs, thoughts, etc.
>>>>>>>>
>>>>>>>> See google doc below.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> Matthew
>>>>>>>>
>>>>>>>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>>>>>
>>>>>>>> Matt,
>>>>>>>> I don?t have any comment to do, I agree with the statements and the
>>>>>>>> wording. Let me know if I can do anything specific to help. Other than that
>>>>>>>> you have my support. Thanks!
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Mart?n
>>>>>>>>
>>>>>>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> the deadline for the public comment is the 10th of August, we have
>>>>>>>> to finish consulting with NCSG members, review and endorsement prior to
>>>>>>>> that. I suggest 8th August as our internal deadline.
>>>>>>>>
>>>>>>>> Best,
>>>>>>>>
>>>>>>>> Rafik
>>>>>>>>
>>>>>>>>
>>>>>>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>>>>>>>
>>>>>>>> Hi Matt, thanks. What's the deadline for this? I am in transit (and
>>>>>>>>> in fact, on holiday), witch sketchy internet access and the doc doesn't
>>>>>>>>> open for me today (might be the poor connection...)
>>>>>>>>>
>>>>>>>>> Sent from my iPhone
>>>>>>>>>
>>>>>>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <matthew at intpolicy.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Let me qualify the last sentence - ICANN staff are not adding new
>>>>>>>>> items in addition to the work of the DT, but rather adding references to
>>>>>>>>> work done previously.
>>>>>>>>>
>>>>>>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>>>>
>>>>>>>>> Calling all PCers
>>>>>>>>>
>>>>>>>>> I have started on the above public comment but am still going
>>>>>>>>> through the consultation docs.  However, time marches on and we need to get
>>>>>>>>> this one underway.
>>>>>>>>>
>>>>>>>>> So, please review the consultation docs here:
>>>>>>>>>
>>>>>>>>> https://www.icann.org/public-comments/gnso-op-procedures-201
>>>>>>>>> 7-06-19-en
>>>>>>>>>
>>>>>>>>> And make comments in the google doc here:
>>>>>>>>>
>>>>>>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>>>>>>>> -ddk_Q9DWja7bZIgsiY/edit
>>>>>>>>> Note that ICANN staff have used this opportunity to include other
>>>>>>>>> changes that the DT did not discuss.
>>>>>>>>>
>>>>>>>>> Many thanks.
>>>>>>>>>
>>>>>>>>> Matthew
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> NCSG-PC mailing list
>>>>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The information transmitted is intended only for the person or
>>>>>>>>> entity to which it is addressed and may contain confidential and/or
>>>>>>>>> privileged material. Any review, retransmission, dissemination,
>>>>>>>>> distribution, forwarding, or other use of, or taking of any action in
>>>>>>>>> reliance upon, this information by persons or entities other than the
>>>>>>>>> intended recipient is prohibited without the express permission of the
>>>>>>>>> sender. If you received this communication in error, please contact the
>>>>>>>>> sender and delete the material from any computer.
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>> Virus-free. www.avg.com
>>>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>>
>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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 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 listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>>>
>>>>
>>>>
>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
>>>> www.avg.com
>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>> <#m_-1376122550809326803_m_-670827426495722261_m_8430456596589667341_m_7701040911500582868_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>
>>>>
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>>
>>
>
> --
>
>
> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>
>
>
> _______________________________________________
> 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/20170811/e2686ae2/attachment.htm>

From rafik.dammak at gmail.com  Sat Aug 12 10:08:38 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Sat, 12 Aug 2017 16:08:38 +0900
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <CAN1qJvDrx=-uh_vBk_-WFekcjzv9HOXQ-qQ62hfGux3MKZOkvg@mail.gmail.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
 <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
 <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>
 <CAH5sThkuLKYbzotNzga147d-OupdqKPJ24CnP9vvkqLb4BqVKA@mail.gmail.com>
 <CAN1qJvC+jSTv1BAE3dtsOiejK3CmcWub7CxNP=E3=W9xaujxXg@mail.gmail.com>
 <CAH5sTh=7jRF6+5a9jtO1TgZwvfNxb3=Ftw=RpDbFmeWcth=d9w@mail.gmail.com>
 <dae73deb-65d5-64cb-f7f1-f8f7bf970b2b@intpolicy.com>
 <15206a94-ec0c-3d6c-2b63-57eb5e9bea66@mail.utoronto.ca>
 <CAN1qJvDrx=-uh_vBk_-WFekcjzv9HOXQ-qQ62hfGux3MKZOkvg@mail.gmail.com>
Message-ID: <CAH5sThmOdTYXPyNbnJyvp_ZR8P=XZKW8ThV60bi4KVS5oZe3dQ@mail.gmail.com>

Hi Farzaneh, Mathew,


I added your suggestion for rephrasing the last paragraph and I also added
your previous suggestion from the other thread:
*" If later on during implementing the operating procedures, it is found
out that changes recommended by  DT   for some reason are not reflected in
the new  GNSO operating procedures, GNSO should follow the DT advice in
those circumstances and allow for the mistake to be corrected.  "*

please find attached the latest version, if there is no objection in next
12hours, I will submit the comment.

Best,

Rafik

2017-08-11 23:44 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com>:

> So I gather that there was not support for my suggested addition. I will
> not add it in the document. I also find this sentence problematic:"Finally,
> we should note that there was disagreement in the DT as to who should speak
> on behalf of the GNSO as a Decisional Participant in the Empowered
> Community. " there was disagreement but we reached consensus. This
> sentence is not drafted carefully to reflect that there was consensus and
> only emphasizes on the disagreement. I suggest reframing it like this: Finally,
> we should note that the DT reached a consensus that *GNSO Council* should
> speak on behalf of the GNSO as a Decisional Participant in the Empowered
> Community.
>
> Farzaneh
>
> On Fri, Aug 11, 2017 at 10:14 AM, Stephanie Perrin <stephanie.perrin at mail.
> utoronto.ca> wrote:
>
>> I think it looks fine now.  I endorse it!
>>
>> cheers SP
>>
>> On 2017-08-11 08:15, Matthew Shears wrote:
>>
>> Hi
>>
>> I have added a brief comment on the role of the GNSO Council.  Please
>> review carefully.
>>
>> Note that the BC submission refers to this issue extensively.
>>
>> Matthew
>>
>> On 11/08/2017 03:33, Rafik Dammak wrote:
>>
>> Hi Matt, Stephanie,
>>
>> can you please add the two suggested comments to the draft asap?
>> I see support for the draft but we should add those edits quickly.
>>
>> Best,
>>
>> Rafik
>>
>> 2017-08-10 17:45 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com>:
>>
>>> I think we should add that. please also consider adding what I mentioned
>>> in my previous email. DT had a debate and reached consensus on many
>>> important issues which were contentious, mainly participation of GNSO in
>>> the empowered community through the council and the thresholds to reach
>>> decisions. As Stephanie agreed to add something like that, I kindly ask her
>>> to just come up with a once sentence which encompasses what I said in my
>>> previous email since she knows how the council functions better than I do.
>>>
>>> Farzaneh
>>>
>>> On Thu, Aug 10, 2017 at 4:37 AM, Rafik Dammak <rafik.dammak at gmail.com>
>>> wrote:
>>>
>>>> Hi Matt,
>>>>
>>>> I do think we can add a similar line to our comment .
>>>>
>>>> Best,
>>>>
>>>> Rafik
>>>>
>>>>
>>>> 2017-08-10 17:19 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>>>>
>>>>> I'm drawing it to the attention of the PC - the issue of the role of
>>>>> Council was a contentious one in the DT with the BC and other suggesting
>>>>> that the Council was exceeding its role if it took on EC responsibilities.
>>>>> NCSG and RySG were aligned on this seeing no issue with Council assuming
>>>>> the role.   My question was whether we thought we should add a similar line
>>>>> on the role of Council in our submission.
>>>>>
>>>>> Matthew
>>>>>
>>>>> On 10/08/2017 09:13, Rafik Dammak wrote:
>>>>>
>>>>> Hi Matt,
>>>>>
>>>>> are you suggesting a change to the comment? do you have some wording
>>>>> to add?
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>>> 2017-08-10 17:05 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>>>>>
>>>>>> Hi all
>>>>>>
>>>>>> I draw your attention to this submission by the RySG:
>>>>>>
>>>>>> http://mm.icann.org/pipermail/comments-gnso-op-procedures-19
>>>>>> jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOp
>>>>>> eratingProceduresandICANNBylaws-0001.pdf
>>>>>>
>>>>>> They note the following which we may wish to emulate (at a minimum
>>>>>> the first line I would have thought):
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *The RySG fully recognises the authority of the GNSO Council to speak
>>>>>> on behalf of the GNSO as Decisional Participant in the Empowered Community.
>>>>>> This is in line with current practice and working methods and respects the
>>>>>> existing equilibrium within the GNSO?s structure. The RySG agrees that on
>>>>>> this point no changes need to be made to the ICANN Bylaws in relation to
>>>>>> the role and description of the GNSO Council.*
>>>>>> Matthew
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 10/08/2017 01:03, Rafik Dammak wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> the deadline for submission is this Friday. I attached the clean
>>>>>> version for review. I understand that Matt, Poncelet, Stephanie support the
>>>>>> comment. we need to hear from other PC members.
>>>>>>
>>>>>> Best,
>>>>>>
>>>>>> Rafik
>>>>>>
>>>>>> 2017-08-07 23:24 GMT+09:00 Stephanie Perrin <
>>>>>> stephanie.perrin at mail.utoronto.ca>:
>>>>>>
>>>>>>> I think that is a really good idea, as these are important
>>>>>>> procedures, and we need to be able to amend if required.  Hard to
>>>>>>> anticipate everything, in my view...
>>>>>>>
>>>>>>> SP
>>>>>>>
>>>>>>> On 2017-08-07 08:49, farzaneh badii wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> I was on the DT group. I don't have the time to go through every
>>>>>>> single change and see if they accord with what we agreed on. If you want in
>>>>>>> the public comment we should ask that if later on during implementing the
>>>>>>> operating procedures we find out that  changes recommended by  DT   for
>>>>>>> some reason are not reflected in the new  GNSO operating procedures, GNSO
>>>>>>> should follow the DT advice in those circumstances and allow for the
>>>>>>> mistake to be corrected.
>>>>>>>
>>>>>>> Farzaneh
>>>>>>>
>>>>>>> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <
>>>>>>> stephanie.perrin at mail.utoronto.ca> wrote:
>>>>>>>
>>>>>>>> It looks fine to me.  I don't have knowledge of or time to do the
>>>>>>>> research on the issues at the moment, so I hope that those who do can catch
>>>>>>>> things that need changes.
>>>>>>>>
>>>>>>>> cheers Stephanie
>>>>>>>>
>>>>>>>> On 2017-08-07 02:07, Rafik Dammak wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> the comment is quite straightforward and supporting the changes
>>>>>>>> outlined in the public consultation.
>>>>>>>> we can have as the deadline for review and endorsement the 9th
>>>>>>>> August. I urge councilors, in particular, to review the changes since it
>>>>>>>> concerns the operating procedures.
>>>>>>>> Thanks, Matt again for the draft. I resolved the edits made by
>>>>>>>> Ayden. ant proof-reading and review would be helpful.
>>>>>>>>
>>>>>>>> Best,
>>>>>>>>
>>>>>>>> Rafik
>>>>>>>>
>>>>>>>> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> I have made some minor alterations to style, but added nothing of
>>>>>>>>> substance. I hope someone with more knowledge of this issue will be able to
>>>>>>>>> contribute to our comment. Submissions are due in six days time. Thanks!
>>>>>>>>>
>>>>>>>>> Best wishes, Ayden
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -------- Original Message --------
>>>>>>>>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures
>>>>>>>>> change
>>>>>>>>> Local Time: August 1, 2017 5:35 PM
>>>>>>>>> UTC Time: August 1, 2017 4:35 PM
>>>>>>>>> From: matthew at intpolicy.com
>>>>>>>>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <
>>>>>>>>> farzaneh.badii at GMAIL.COM>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi all
>>>>>>>>>
>>>>>>>>> Wanted to get this back at the top of the list of to-do's as time
>>>>>>>>> is running out.
>>>>>>>>>
>>>>>>>>> Appreciate the comments from some of the PC members but would
>>>>>>>>> welcome additional inputs, thoughts, etc.
>>>>>>>>>
>>>>>>>>> See google doc below.
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>> Matthew
>>>>>>>>>
>>>>>>>>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>>>>>>
>>>>>>>>> Matt,
>>>>>>>>> I don?t have any comment to do, I agree with the statements and
>>>>>>>>> the wording. Let me know if I can do anything specific to help. Other than
>>>>>>>>> that you have my support. Thanks!
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Mart?n
>>>>>>>>>
>>>>>>>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> the deadline for the public comment is the 10th of August, we have
>>>>>>>>> to finish consulting with NCSG members, review and endorsement prior to
>>>>>>>>> that. I suggest 8th August as our internal deadline.
>>>>>>>>>
>>>>>>>>> Best,
>>>>>>>>>
>>>>>>>>> Rafik
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>:
>>>>>>>>>
>>>>>>>>> Hi Matt, thanks. What's the deadline for this? I am in transit
>>>>>>>>>> (and in fact, on holiday), witch sketchy internet access and the doc
>>>>>>>>>> doesn't open for me today (might be the poor connection...)
>>>>>>>>>>
>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>
>>>>>>>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <
>>>>>>>>>> matthew at intpolicy.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Let me qualify the last sentence - ICANN staff are not adding new
>>>>>>>>>> items in addition to the work of the DT, but rather adding references to
>>>>>>>>>> work done previously.
>>>>>>>>>>
>>>>>>>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>>>>>
>>>>>>>>>> Calling all PCers
>>>>>>>>>>
>>>>>>>>>> I have started on the above public comment but am still going
>>>>>>>>>> through the consultation docs.  However, time marches on and we need to get
>>>>>>>>>> this one underway.
>>>>>>>>>>
>>>>>>>>>> So, please review the consultation docs here:
>>>>>>>>>>
>>>>>>>>>> https://www.icann.org/public-comments/gnso-op-procedures-201
>>>>>>>>>> 7-06-19-en
>>>>>>>>>>
>>>>>>>>>> And make comments in the google doc here:
>>>>>>>>>>
>>>>>>>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>>>>>>>>> -ddk_Q9DWja7bZIgsiY/edit
>>>>>>>>>> Note that ICANN staff have used this opportunity to include other
>>>>>>>>>> changes that the DT did not discuss.
>>>>>>>>>>
>>>>>>>>>> Many thanks.
>>>>>>>>>>
>>>>>>>>>> Matthew
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> NCSG-PC mailing list
>>>>>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The information transmitted is intended only for the person or
>>>>>>>>>> entity to which it is addressed and may contain confidential and/or
>>>>>>>>>> privileged material. Any review, retransmission, dissemination,
>>>>>>>>>> distribution, forwarding, or other use of, or taking of any action in
>>>>>>>>>> reliance upon, this information by persons or entities other than the
>>>>>>>>>> intended recipient is prohibited without the express permission of the
>>>>>>>>>> sender. If you received this communication in error, please contact the
>>>>>>>>>> sender and delete the material from any computer.
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>>> Virus-free. www.avg.com
>>>>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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 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 listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> NCSG-PC mailing list
>>>>>> NCSG-PC at lists.ncsg.is
>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
>>>>> www.avg.com
>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>> <#m_6197814062825925350_m_-1376122550809326803_m_-670827426495722261_m_8430456596589667341_m_7701040911500582868_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>>
>>>
>>
>> --
>>
>>
>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>
>>
>>
>> _______________________________________________
>> 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/20170812/139fb591/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GNSO Operating Procedures and ICANN Bylaws - NCSG Comment.pdf
Type: application/pdf
Size: 70702 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170812/139fb591/attachment.pdf>

From pileleji at ymca.gm  Sat Aug 12 14:18:39 2017
From: pileleji at ymca.gm (Poncelet Ileleji)
Date: Sat, 12 Aug 2017 11:18:39 +0000
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <CAH5sThmOdTYXPyNbnJyvp_ZR8P=XZKW8ThV60bi4KVS5oZe3dQ@mail.gmail.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
 <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
 <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>
 <CAH5sThkuLKYbzotNzga147d-OupdqKPJ24CnP9vvkqLb4BqVKA@mail.gmail.com>
 <CAN1qJvC+jSTv1BAE3dtsOiejK3CmcWub7CxNP=E3=W9xaujxXg@mail.gmail.com>
 <CAH5sTh=7jRF6+5a9jtO1TgZwvfNxb3=Ftw=RpDbFmeWcth=d9w@mail.gmail.com>
 <dae73deb-65d5-64cb-f7f1-f8f7bf970b2b@intpolicy.com>
 <15206a94-ec0c-3d6c-2b63-57eb5e9bea66@mail.utoronto.ca>
 <CAN1qJvDrx=-uh_vBk_-WFekcjzv9HOXQ-qQ62hfGux3MKZOkvg@mail.gmail.com>
 <CAH5sThmOdTYXPyNbnJyvp_ZR8P=XZKW8ThV60bi4KVS5oZe3dQ@mail.gmail.com>
Message-ID: <CAEux40uviF1HmzkFEXfVtbm5PJ1g_w4o6MW8JPPD+WgHRnfQsQ@mail.gmail.com>

Perfect Rafik,

+1 Good to go for me.

Kind Regards

Poncelet

On 12 August 2017 at 07:08, Rafik Dammak <rafik.dammak at gmail.com> wrote:

> Hi Farzaneh, Mathew,
>
>
> I added your suggestion for rephrasing the last paragraph and I also added
> your previous suggestion from the other thread:
> *" If later on during implementing the operating procedures, it is found
> out that changes recommended by  DT   for some reason are not reflected in
> the new  GNSO operating procedures, GNSO should follow the DT advice in
> those circumstances and allow for the mistake to be corrected.  "*
>
> please find attached the latest version, if there is no objection in next
> 12hours, I will submit the comment.
>
> Best,
>
> Rafik
>
> 2017-08-11 23:44 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com>:
>
>> So I gather that there was not support for my suggested addition. I will
>> not add it in the document. I also find this sentence problematic:"Finally,
>> we should note that there was disagreement in the DT as to who should speak
>> on behalf of the GNSO as a Decisional Participant in the Empowered
>> Community. " there was disagreement but we reached consensus. This
>> sentence is not drafted carefully to reflect that there was consensus and
>> only emphasizes on the disagreement. I suggest reframing it like this: Finally,
>> we should note that the DT reached a consensus that *GNSO Council*
>> should speak on behalf of the GNSO as a Decisional Participant in the
>> Empowered Community.
>>
>> Farzaneh
>>
>> On Fri, Aug 11, 2017 at 10:14 AM, Stephanie Perrin <
>> stephanie.perrin at mail.utoronto.ca> wrote:
>>
>>> I think it looks fine now.  I endorse it!
>>>
>>> cheers SP
>>>
>>> On 2017-08-11 08:15, Matthew Shears wrote:
>>>
>>> Hi
>>>
>>> I have added a brief comment on the role of the GNSO Council.  Please
>>> review carefully.
>>>
>>> Note that the BC submission refers to this issue extensively.
>>>
>>> Matthew
>>>
>>> On 11/08/2017 03:33, Rafik Dammak wrote:
>>>
>>> Hi Matt, Stephanie,
>>>
>>> can you please add the two suggested comments to the draft asap?
>>> I see support for the draft but we should add those edits quickly.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> 2017-08-10 17:45 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com>:
>>>
>>>> I think we should add that. please also consider adding what I
>>>> mentioned in my previous email. DT had a debate and reached consensus on
>>>> many important issues which were contentious, mainly participation of GNSO
>>>> in the empowered community through the council and the thresholds to reach
>>>> decisions. As Stephanie agreed to add something like that, I kindly ask her
>>>> to just come up with a once sentence which encompasses what I said in my
>>>> previous email since she knows how the council functions better than I do.
>>>>
>>>> Farzaneh
>>>>
>>>> On Thu, Aug 10, 2017 at 4:37 AM, Rafik Dammak <rafik.dammak at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Matt,
>>>>>
>>>>> I do think we can add a similar line to our comment .
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>>>
>>>>> 2017-08-10 17:19 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>>>>>
>>>>>> I'm drawing it to the attention of the PC - the issue of the role of
>>>>>> Council was a contentious one in the DT with the BC and other suggesting
>>>>>> that the Council was exceeding its role if it took on EC responsibilities.
>>>>>> NCSG and RySG were aligned on this seeing no issue with Council assuming
>>>>>> the role.   My question was whether we thought we should add a similar line
>>>>>> on the role of Council in our submission.
>>>>>>
>>>>>> Matthew
>>>>>>
>>>>>> On 10/08/2017 09:13, Rafik Dammak wrote:
>>>>>>
>>>>>> Hi Matt,
>>>>>>
>>>>>> are you suggesting a change to the comment? do you have some wording
>>>>>> to add?
>>>>>>
>>>>>> Best,
>>>>>>
>>>>>> Rafik
>>>>>>
>>>>>> 2017-08-10 17:05 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>>>>>>
>>>>>>> Hi all
>>>>>>>
>>>>>>> I draw your attention to this submission by the RySG:
>>>>>>>
>>>>>>> http://mm.icann.org/pipermail/comments-gnso-op-procedures-19
>>>>>>> jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOp
>>>>>>> eratingProceduresandICANNBylaws-0001.pdf
>>>>>>>
>>>>>>> They note the following which we may wish to emulate (at a minimum
>>>>>>> the first line I would have thought):
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *The RySG fully recognises the authority of the GNSO Council to
>>>>>>> speak on behalf of the GNSO as Decisional Participant in the Empowered
>>>>>>> Community. This is in line with current practice and working methods and
>>>>>>> respects the existing equilibrium within the GNSO?s structure. The RySG
>>>>>>> agrees that on this point no changes need to be made to the ICANN Bylaws in
>>>>>>> relation to the role and description of the GNSO Council.*
>>>>>>> Matthew
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 10/08/2017 01:03, Rafik Dammak wrote:
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> the deadline for submission is this Friday. I attached the clean
>>>>>>> version for review. I understand that Matt, Poncelet, Stephanie support the
>>>>>>> comment. we need to hear from other PC members.
>>>>>>>
>>>>>>> Best,
>>>>>>>
>>>>>>> Rafik
>>>>>>>
>>>>>>> 2017-08-07 23:24 GMT+09:00 Stephanie Perrin <
>>>>>>> stephanie.perrin at mail.utoronto.ca>:
>>>>>>>
>>>>>>>> I think that is a really good idea, as these are important
>>>>>>>> procedures, and we need to be able to amend if required.  Hard to
>>>>>>>> anticipate everything, in my view...
>>>>>>>>
>>>>>>>> SP
>>>>>>>>
>>>>>>>> On 2017-08-07 08:49, farzaneh badii wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> I was on the DT group. I don't have the time to go through every
>>>>>>>> single change and see if they accord with what we agreed on. If you want in
>>>>>>>> the public comment we should ask that if later on during implementing the
>>>>>>>> operating procedures we find out that  changes recommended by  DT   for
>>>>>>>> some reason are not reflected in the new  GNSO operating procedures, GNSO
>>>>>>>> should follow the DT advice in those circumstances and allow for the
>>>>>>>> mistake to be corrected.
>>>>>>>>
>>>>>>>> Farzaneh
>>>>>>>>
>>>>>>>> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <
>>>>>>>> stephanie.perrin at mail.utoronto.ca> wrote:
>>>>>>>>
>>>>>>>>> It looks fine to me.  I don't have knowledge of or time to do the
>>>>>>>>> research on the issues at the moment, so I hope that those who do can catch
>>>>>>>>> things that need changes.
>>>>>>>>>
>>>>>>>>> cheers Stephanie
>>>>>>>>>
>>>>>>>>> On 2017-08-07 02:07, Rafik Dammak wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> the comment is quite straightforward and supporting the changes
>>>>>>>>> outlined in the public consultation.
>>>>>>>>> we can have as the deadline for review and endorsement the 9th
>>>>>>>>> August. I urge councilors, in particular, to review the changes since it
>>>>>>>>> concerns the operating procedures.
>>>>>>>>> Thanks, Matt again for the draft. I resolved the edits made by
>>>>>>>>> Ayden. ant proof-reading and review would be helpful.
>>>>>>>>>
>>>>>>>>> Best,
>>>>>>>>>
>>>>>>>>> Rafik
>>>>>>>>>
>>>>>>>>> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> I have made some minor alterations to style, but added nothing of
>>>>>>>>>> substance. I hope someone with more knowledge of this issue will be able to
>>>>>>>>>> contribute to our comment. Submissions are due in six days time. Thanks!
>>>>>>>>>>
>>>>>>>>>> Best wishes, Ayden
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -------- Original Message --------
>>>>>>>>>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures
>>>>>>>>>> change
>>>>>>>>>> Local Time: August 1, 2017 5:35 PM
>>>>>>>>>> UTC Time: August 1, 2017 4:35 PM
>>>>>>>>>> From: matthew at intpolicy.com
>>>>>>>>>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <
>>>>>>>>>> farzaneh.badii at GMAIL.COM>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi all
>>>>>>>>>>
>>>>>>>>>> Wanted to get this back at the top of the list of to-do's as time
>>>>>>>>>> is running out.
>>>>>>>>>>
>>>>>>>>>> Appreciate the comments from some of the PC members but would
>>>>>>>>>> welcome additional inputs, thoughts, etc.
>>>>>>>>>>
>>>>>>>>>> See google doc below.
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>> Matthew
>>>>>>>>>>
>>>>>>>>>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>>>>>>>
>>>>>>>>>> Matt,
>>>>>>>>>> I don?t have any comment to do, I agree with the statements and
>>>>>>>>>> the wording. Let me know if I can do anything specific to help. Other than
>>>>>>>>>> that you have my support. Thanks!
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> Mart?n
>>>>>>>>>>
>>>>>>>>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> the deadline for the public comment is the 10th of August, we
>>>>>>>>>> have to finish consulting with NCSG members, review and endorsement prior
>>>>>>>>>> to that. I suggest 8th August as our internal deadline.
>>>>>>>>>>
>>>>>>>>>> Best,
>>>>>>>>>>
>>>>>>>>>> Rafik
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>
>>>>>>>>>> :
>>>>>>>>>>
>>>>>>>>>> Hi Matt, thanks. What's the deadline for this? I am in transit
>>>>>>>>>>> (and in fact, on holiday), witch sketchy internet access and the doc
>>>>>>>>>>> doesn't open for me today (might be the poor connection...)
>>>>>>>>>>>
>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>
>>>>>>>>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <
>>>>>>>>>>> matthew at intpolicy.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Let me qualify the last sentence - ICANN staff are not adding
>>>>>>>>>>> new items in addition to the work of the DT, but rather adding references
>>>>>>>>>>> to work done previously.
>>>>>>>>>>>
>>>>>>>>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>>>>>>
>>>>>>>>>>> Calling all PCers
>>>>>>>>>>>
>>>>>>>>>>> I have started on the above public comment but am still going
>>>>>>>>>>> through the consultation docs.  However, time marches on and we need to get
>>>>>>>>>>> this one underway.
>>>>>>>>>>>
>>>>>>>>>>> So, please review the consultation docs here:
>>>>>>>>>>>
>>>>>>>>>>> https://www.icann.org/public-comments/gnso-op-procedures-201
>>>>>>>>>>> 7-06-19-en
>>>>>>>>>>>
>>>>>>>>>>> And make comments in the google doc here:
>>>>>>>>>>>
>>>>>>>>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>>>>>>>>>> -ddk_Q9DWja7bZIgsiY/edit
>>>>>>>>>>> Note that ICANN staff have used this opportunity to include
>>>>>>>>>>> other changes that the DT did not discuss.
>>>>>>>>>>>
>>>>>>>>>>> Many thanks.
>>>>>>>>>>>
>>>>>>>>>>> Matthew
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> NCSG-PC mailing list
>>>>>>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The information transmitted is intended only for the person or
>>>>>>>>>>> entity to which it is addressed and may contain confidential and/or
>>>>>>>>>>> privileged material. Any review, retransmission, dissemination,
>>>>>>>>>>> distribution, forwarding, or other use of, or taking of any action in
>>>>>>>>>>> reliance upon, this information by persons or entities other than the
>>>>>>>>>>> intended recipient is prohibited without the express permission of the
>>>>>>>>>>> sender. If you received this communication in error, please contact the
>>>>>>>>>>> sender and delete the material from any computer.
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>>>> Virus-free. www.avg.com
>>>>>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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 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 listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> NCSG-PC mailing list
>>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
>>>>>> www.avg.com
>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>> <#m_3800634356925087449_m_6197814062825925350_m_-1376122550809326803_m_-670827426495722261_m_8430456596589667341_m_7701040911500582868_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>>>
>>>>
>>>
>>> --
>>>
>>>
>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20170812/1a988ef6/attachment.htm>

From t.tropina at mpicc.de  Sat Aug 12 17:19:05 2017
From: t.tropina at mpicc.de (Dr. Tatiana Tropina)
Date: Sat, 12 Aug 2017 16:19:05 +0200
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <CAH5sThmOdTYXPyNbnJyvp_ZR8P=XZKW8ThV60bi4KVS5oZe3dQ@mail.gmail.com>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
 <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
 <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>
 <CAH5sThkuLKYbzotNzga147d-OupdqKPJ24CnP9vvkqLb4BqVKA@mail.gmail.com>
 <CAN1qJvC+jSTv1BAE3dtsOiejK3CmcWub7CxNP=E3=W9xaujxXg@mail.gmail.com>
 <CAH5sTh=7jRF6+5a9jtO1TgZwvfNxb3=Ftw=RpDbFmeWcth=d9w@mail.gmail.com>
 <dae73deb-65d5-64cb-f7f1-f8f7bf970b2b@intpolicy.com>
 <15206a94-ec0c-3d6c-2b63-57eb5e9bea66@mail.utoronto.ca>
 <CAN1qJvDrx=-uh_vBk_-WFekcjzv9HOXQ-qQ62hfGux3MKZOkvg@mail.gmail.com>
 <CAH5sThmOdTYXPyNbnJyvp_ZR8P=XZKW8ThV60bi4KVS5oZe3dQ@mail.gmail.com>
Message-ID: <dad79800-a403-69ee-97ca-37a9550f84a5@mpicc.de>

Hi all,

I support the amended version.

Cheers,

Tanya


On 12/08/17 09:08, Rafik Dammak wrote:
> Hi Farzaneh, Mathew,
>
>
> I added your suggestion for rephrasing the last paragraph and I also
> added your previous suggestion from the other thread:
> /"If later on during implementing the operating procedures, it is
> found out that changes recommended by  DT   for some reason are not
> reflected in the new  GNSO operating procedures, GNSO should follow
> the DT advice in those circumstances and allow for the mistake to be
> corrected.  "/
>
> please find attached the latest version, if there is no objection in
> next 12hours, I will submit the comment.
>
> Best,
>
> Rafik
>
> 2017-08-11 23:44 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com
> <mailto:farzaneh.badii at gmail.com>>:
>
>     So I gather that there was not support for my suggested addition.
>     I will not add it in the document. I also find this sentence
>     problematic:"Finally, we should note that there was disagreement
>     in the DT as to who should speak on behalf of the GNSO as a
>     Decisional Participant in the Empowered Community. " there was
>     disagreement but we reached consensus. This sentence is not
>     drafted carefully to reflect that there was consensus and only
>     emphasizes on the disagreement. I suggest reframing it like
>     this: Finally, we should note that the DT reached a consensus that
>     _GNSO Council_ should speak on behalf of the GNSO as a Decisional
>     Participant in the Empowered Community.
>
>     Farzaneh
>
>     On Fri, Aug 11, 2017 at 10:14 AM, Stephanie Perrin
>     <stephanie.perrin at mail.utoronto.ca
>     <mailto:stephanie.perrin at mail.utoronto.ca>> wrote:
>
>         I think it looks fine now.  I endorse it!
>
>         cheers SP
>
>
>         On 2017-08-11 08:15, Matthew Shears wrote:
>>
>>         Hi
>>
>>         I have added a brief comment on the role of the GNSO
>>         Council.  Please review carefully.
>>
>>         Note that the BC submission refers to this issue extensively.
>>
>>         Matthew
>>
>>
>>         On 11/08/2017 03:33, Rafik Dammak wrote:
>>>         Hi Matt, Stephanie,
>>>
>>>         can you please add the two suggested comments to the draft asap?
>>>         I see support for the draft but we should add those edits
>>>         quickly.
>>>
>>>         Best,
>>>
>>>         Rafik 
>>>
>>>         2017-08-10 17:45 GMT+09:00 farzaneh badii
>>>         <farzaneh.badii at gmail.com <mailto:farzaneh.badii at gmail.com>>:
>>>
>>>             I think we should add that. please also consider adding
>>>             what I mentioned in my previous email. DT had a debate
>>>             and reached consensus on many important issues which
>>>             were contentious, mainly participation of GNSO in the
>>>             empowered community through the council and the
>>>             thresholds to reach decisions. As Stephanie agreed to
>>>             add something like that, I kindly ask her to just come
>>>             up with a once sentence which encompasses what I said in
>>>             my previous email since she knows how the council
>>>             functions better than I do.
>>>
>>>             Farzaneh
>>>
>>>             On Thu, Aug 10, 2017 at 4:37 AM, Rafik Dammak
>>>             <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>>
>>>             wrote:
>>>
>>>                 Hi Matt,
>>>
>>>                 I do think we can add a similar line to our comment .
>>>
>>>                 Best,
>>>
>>>                 Rafik
>>>
>>>
>>>                 2017-08-10 17:19 GMT+09:00 Matthew Shears
>>>                 <matthew at intpolicy.com <mailto:matthew at intpolicy.com>>:
>>>
>>>                     I'm drawing it to the attention of the PC - the
>>>                     issue of the role of Council was a contentious
>>>                     one in the DT with the BC and other suggesting
>>>                     that the Council was exceeding its role if it
>>>                     took on EC responsibilities.  NCSG and RySG were
>>>                     aligned on this seeing no issue with Council
>>>                     assuming the role.   My question was whether we
>>>                     thought we should add a similar line on the role
>>>                     of Council in our submission.
>>>
>>>                     Matthew
>>>
>>>
>>>                     On 10/08/2017 09:13, Rafik Dammak wrote:
>>>>                     Hi Matt,
>>>>
>>>>                     are you suggesting a change to the comment? do
>>>>                     you have some wording to add?
>>>>
>>>>                     Best,
>>>>
>>>>                     Rafik
>>>>
>>>>                     2017-08-10 17:05 GMT+09:00 Matthew Shears
>>>>                     <matthew at intpolicy.com
>>>>                     <mailto:matthew at intpolicy.com>>:
>>>>
>>>>                         Hi all
>>>>
>>>>                         I draw your attention to this submission by
>>>>                         the RySG:
>>>>
>>>>                         http://mm.icann.org/pipermail/comments-gnso-op-procedures-19jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOperatingProceduresandICANNBylaws-0001.pdf
>>>>                         <http://mm.icann.org/pipermail/comments-gnso-op-procedures-19jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOperatingProceduresandICANNBylaws-0001.pdf>
>>>>
>>>>                         They note the following which we may wish
>>>>                         to emulate (at a minimum the first line I
>>>>                         would have thought):
>>>>
>>>>                         /The RySG fully recognises the authority of
>>>>                         the GNSO Council to speak on behalf of the
>>>>                         GNSO as
>>>>                         Decisional Participant in the Empowered
>>>>                         Community. This is in line with current
>>>>                         practice and
>>>>                         working methods and respects the existing
>>>>                         equilibrium within the GNSO?s structure.
>>>>                         The RySG
>>>>                         agrees that on this point no changes need
>>>>                         to be made to the ICANN Bylaws in relation
>>>>                         to the role
>>>>                         and description of the GNSO Council.///
>>>>
>>>>                         Matthew
>>>>
>>>>
>>>>
>>>>                         On 10/08/2017 01:03, Rafik Dammak wrote:
>>>>>                         Hi all,
>>>>>
>>>>>                         the deadline for submission is this
>>>>>                         Friday. I attached the clean version for
>>>>>                         review. I understand that Matt, Poncelet,
>>>>>                         Stephanie support the comment. we need to
>>>>>                         hear from other PC members.
>>>>>
>>>>>                         Best,
>>>>>
>>>>>                         Rafik
>>>>>
>>>>>                         2017-08-07 23:24 GMT+09:00 Stephanie
>>>>>                         Perrin <stephanie.perrin at mail.utoronto.ca
>>>>>                         <mailto:stephanie.perrin at mail.utoronto.ca>>:
>>>>>
>>>>>                             I think that is a really good idea, as
>>>>>                             these are important procedures, and we
>>>>>                             need to be able to amend if required. 
>>>>>                             Hard to anticipate everything, in my
>>>>>                             view...
>>>>>
>>>>>                             SP
>>>>>
>>>>>
>>>>>                             On 2017-08-07 08:49, farzaneh badii wrote:
>>>>>>                             Hi
>>>>>>
>>>>>>                             I was on the DT group. I don't have
>>>>>>                             the time to go through every single
>>>>>>                             change and see if they accord with
>>>>>>                             what we agreed on. If you want in the
>>>>>>                             public comment we should ask that if
>>>>>>                             later on during implementing the
>>>>>>                             operating procedures we find out that
>>>>>>                              changes recommended by  DT   for
>>>>>>                             some reason are not reflected in the
>>>>>>                             new  GNSO operating procedures, GNSO
>>>>>>                             should follow the DT advice in those
>>>>>>                             circumstances and allow for the
>>>>>>                             mistake to be corrected.  
>>>>>>
>>>>>>                             Farzaneh
>>>>>>
>>>>>>                             On Mon, Aug 7, 2017 at 8:41 AM,
>>>>>>                             Stephanie Perrin
>>>>>>                             <stephanie.perrin at mail.utoronto.ca
>>>>>>                             <mailto:stephanie.perrin at mail.utoronto.ca>>
>>>>>>                             wrote:
>>>>>>
>>>>>>                                 It looks fine to me.  I don't
>>>>>>                                 have knowledge of or time to do
>>>>>>                                 the research on the issues at the
>>>>>>                                 moment, so I hope that those who
>>>>>>                                 do can catch things that need
>>>>>>                                 changes.
>>>>>>
>>>>>>                                 cheers Stephanie
>>>>>>
>>>>>>
>>>>>>                                 On 2017-08-07 02:07, Rafik Dammak
>>>>>>                                 wrote:
>>>>>>>                                 Hi,
>>>>>>>
>>>>>>>                                 the comment is quite
>>>>>>>                                 straightforward and supporting
>>>>>>>                                 the changes outlined in the
>>>>>>>                                 public consultation.
>>>>>>>                                 we can have as the deadline for
>>>>>>>                                 review and endorsement the 9th
>>>>>>>                                 August. I urge councilors, in
>>>>>>>                                 particular, to review the
>>>>>>>                                 changes since it concerns the
>>>>>>>                                 operating procedures.
>>>>>>>                                 Thanks, Matt again for the
>>>>>>>                                 draft. I resolved the edits made
>>>>>>>                                 by Ayden. ant proof-reading and
>>>>>>>                                 review would be helpful.
>>>>>>>
>>>>>>>                                 Best,
>>>>>>>
>>>>>>>                                 Rafik
>>>>>>>
>>>>>>>                                 2017-08-05 6:33 GMT+09:00 Ayden
>>>>>>>                                 F?rdeline <icann at ferdeline.com
>>>>>>>                                 <mailto:icann at ferdeline.com>>:
>>>>>>>
>>>>>>>                                     Hi all,
>>>>>>>
>>>>>>>                                     I have made some minor
>>>>>>>                                     alterations to style, but
>>>>>>>                                     added nothing of substance.
>>>>>>>                                     I hope someone with more
>>>>>>>                                     knowledge of this issue will
>>>>>>>                                     be able to contribute to our
>>>>>>>                                     comment. Submissions are due
>>>>>>>                                     in six days time. Thanks!
>>>>>>>
>>>>>>>                                     Best wishes, Ayden 
>>>>>>>
>>>>>>>
>>>>>>>>                                     -------- Original Message
>>>>>>>>                                     --------
>>>>>>>>                                     Subject: Re: [NCSG-PC] NCSG
>>>>>>>>                                     Comment on GNSO operating
>>>>>>>>                                     procedures change
>>>>>>>>                                     Local Time: August 1, 2017
>>>>>>>>                                     5:35 PM
>>>>>>>>                                     UTC Time: August 1, 2017
>>>>>>>>                                     4:35 PM
>>>>>>>>                                     From: matthew at intpolicy.com
>>>>>>>>                                     <mailto:matthew at intpolicy.com>
>>>>>>>>                                     To: ncsg-pc at lists.ncsg.is
>>>>>>>>                                     <mailto:ncsg-pc at lists.ncsg.is>,
>>>>>>>>                                     farzaneh badii
>>>>>>>>                                     <farzaneh.badii at GMAIL.COM
>>>>>>>>                                     <mailto:farzaneh.badii at GMAIL.COM>>
>>>>>>>>
>>>>>>>>
>>>>>>>>                                     Hi all
>>>>>>>>
>>>>>>>>                                     Wanted to get this back at
>>>>>>>>                                     the top of the list of
>>>>>>>>                                     to-do's as time is running out.
>>>>>>>>
>>>>>>>>                                     Appreciate the comments
>>>>>>>>                                     from some of the PC members
>>>>>>>>                                     but would welcome
>>>>>>>>                                     additional inputs,
>>>>>>>>                                     thoughts, etc.
>>>>>>>>
>>>>>>>>                                     See google doc below.
>>>>>>>>
>>>>>>>>                                     Thanks.
>>>>>>>>
>>>>>>>>                                     Matthew
>>>>>>>>
>>>>>>>>
>>>>>>>>                                     On 27/07/2017 03:08, Martin
>>>>>>>>                                     Pablo Silva Valent wrote:
>>>>>>>>>                                     Matt,
>>>>>>>>>                                     I don?t have any comment
>>>>>>>>>                                     to do, I agree with the
>>>>>>>>>                                     statements and the
>>>>>>>>>                                     wording. Let me know if I
>>>>>>>>>                                     can do anything specific
>>>>>>>>>                                     to help. Other than that
>>>>>>>>>                                     you have my support. Thanks!
>>>>>>>>>
>>>>>>>>>                                     Cheers,
>>>>>>>>>                                     Mart?n
>>>>>>>>>
>>>>>>>>>>                                     On Jul 25, 2017, at 8:22
>>>>>>>>>>                                     PM, Rafik Dammak
>>>>>>>>>>                                     <rafik.dammak at gmail.com
>>>>>>>>>>                                     <mailto:rafik.dammak at gmail.com>>
>>>>>>>>>>                                     wrote:
>>>>>>>>>>
>>>>>>>>>>                                     Hi,
>>>>>>>>>>
>>>>>>>>>>                                     the deadline for the
>>>>>>>>>>                                     public comment is the
>>>>>>>>>>                                     10th of August, we have
>>>>>>>>>>                                     to finish consulting with
>>>>>>>>>>                                     NCSG members, review and
>>>>>>>>>>                                     endorsement prior to
>>>>>>>>>>                                     that. I suggest 8th
>>>>>>>>>>                                     August as our internal
>>>>>>>>>>                                     deadline.
>>>>>>>>>>
>>>>>>>>>>                                     Best,
>>>>>>>>>>
>>>>>>>>>>                                     Rafik
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                                     2017-07-25 23:28
>>>>>>>>>>                                     GMT+09:00 Stefania Milan
>>>>>>>>>>                                     <stefania.milan at eui.eu
>>>>>>>>>>                                     <mailto:stefania.milan at eui.eu>>:
>>>>>>>>>>
>>>>>>>>>>                                         Hi Matt, thanks.
>>>>>>>>>>                                         What's the deadline
>>>>>>>>>>                                         for this? I am in
>>>>>>>>>>                                         transit (and in fact,
>>>>>>>>>>                                         on holiday), witch
>>>>>>>>>>                                         sketchy internet
>>>>>>>>>>                                         access and the doc
>>>>>>>>>>                                         doesn't open for me
>>>>>>>>>>                                         today (might be the
>>>>>>>>>>                                         poor connection...)
>>>>>>>>>>
>>>>>>>>>>                                         Sent from my iPhone
>>>>>>>>>>
>>>>>>>>>>                                         On Jul 25, 2017, at
>>>>>>>>>>                                         9:17 AM, Matthew
>>>>>>>>>>                                         Shears
>>>>>>>>>>                                         <matthew at intpolicy.com
>>>>>>>>>>                                         <mailto:matthew at intpolicy.com>>
>>>>>>>>>>                                         wrote:
>>>>>>>>>>
>>>>>>>>>>>                                         Let me qualify the
>>>>>>>>>>>                                         last sentence -
>>>>>>>>>>>                                         ICANN staff are not
>>>>>>>>>>>                                         adding new items in
>>>>>>>>>>>                                         addition to the work
>>>>>>>>>>>                                         of the DT, but
>>>>>>>>>>>                                         rather adding
>>>>>>>>>>>                                         references to work
>>>>>>>>>>>                                         done previously.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>                                         On 25/07/2017 16:05,
>>>>>>>>>>>                                         Matthew Shears wrote:
>>>>>>>>>>>>                                         Calling all PCers
>>>>>>>>>>>>
>>>>>>>>>>>>                                         I have started on
>>>>>>>>>>>>                                         the above public
>>>>>>>>>>>>                                         comment but am
>>>>>>>>>>>>                                         still going through
>>>>>>>>>>>>                                         the consultation
>>>>>>>>>>>>                                         docs.  However,
>>>>>>>>>>>>                                         time marches on and
>>>>>>>>>>>>                                         we need to get this
>>>>>>>>>>>>                                         one underway. 
>>>>>>>>>>>>
>>>>>>>>>>>>                                         So, please review
>>>>>>>>>>>>                                         the consultation
>>>>>>>>>>>>                                         docs here:
>>>>>>>>>>>>
>>>>>>>>>>>>                                         https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en
>>>>>>>>>>>>                                         <https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en>
>>>>>>>>>>>>
>>>>>>>>>>>>                                         And make comments
>>>>>>>>>>>>                                         in the google doc here:
>>>>>>>>>>>>
>>>>>>>>>>>>                                         https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit
>>>>>>>>>>>>                                         <https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF-ddk_Q9DWja7bZIgsiY/edit>
>>>>>>>>>>>>
>>>>>>>>>>>>                                         Note that ICANN
>>>>>>>>>>>>                                         staff have used
>>>>>>>>>>>>                                         this opportunity to
>>>>>>>>>>>>                                         include other
>>>>>>>>>>>>                                         changes that the DT
>>>>>>>>>>>>                                         did not discuss.
>>>>>>>>>>>>
>>>>>>>>>>>>                                         Many thanks.
>>>>>>>>>>>>
>>>>>>>>>>>>                                         Matthew
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>                                         -- 
>>>>>>>>>>>>                                         Matthew Shears
>>>>>>>>>>>>                                         matthew at intpolicy.com
>>>>>>>>>>>>                                         <mailto:matthew at intpolicy.com>
>>>>>>>>>>>>                                         +447712472987
>>>>>>>>>>>>                                         <tel:+44%207712%20472987>
>>>>>>>>>>>>                                         Skype:mshears
>>>>>>>>>>>
>>>>>>>>>>>                                         -- 
>>>>>>>>>>>                                         Matthew Shears
>>>>>>>>>>>                                         matthew at intpolicy.com
>>>>>>>>>>>                                         <mailto:matthew at intpolicy.com>
>>>>>>>>>>>                                         +447712472987
>>>>>>>>>>>                                         <tel:+44%207712%20472987>
>>>>>>>>>>>                                         Skype:mshears
>>>>>>>>>>>                                         _______________________________________________
>>>>>>>>>>>                                         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>
>>>>>>>>>>
>>>>>>>>>>                                          
>>>>>>>>>>
>>>>>>>>>>                                         The information
>>>>>>>>>>                                         transmitted is
>>>>>>>>>>                                         intended only for the
>>>>>>>>>>                                         person or entity to
>>>>>>>>>>                                         which it is addressed
>>>>>>>>>>                                         and may contain
>>>>>>>>>>                                         confidential and/or
>>>>>>>>>>                                         privileged material.
>>>>>>>>>>                                         Any review,
>>>>>>>>>>                                         retransmission,
>>>>>>>>>>                                         dissemination,
>>>>>>>>>>                                         distribution,
>>>>>>>>>>                                         forwarding, or other
>>>>>>>>>>                                         use of, or taking of
>>>>>>>>>>                                         any action in
>>>>>>>>>>                                         reliance upon, this
>>>>>>>>>>                                         information by
>>>>>>>>>>                                         persons or entities
>>>>>>>>>>                                         other than the
>>>>>>>>>>                                         intended recipient is
>>>>>>>>>>                                         prohibited without
>>>>>>>>>>                                         the express
>>>>>>>>>>                                         permission of the
>>>>>>>>>>                                         sender. If you
>>>>>>>>>>                                         received this
>>>>>>>>>>                                         communication in
>>>>>>>>>>                                         error, please contact
>>>>>>>>>>                                         the sender and delete
>>>>>>>>>>                                         the material from any
>>>>>>>>>>                                         computer.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                                         _______________________________________________
>>>>>>>>>>                                         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>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                                     <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>>>                                     	Virus-free. www.avg.com
>>>>>>>>>                                     <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                                     _______________________________________________
>>>>>>>>>                                     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>
>>>>>>>>>
>>>>>>>>                                     -- 
>>>>>>>>
>>>>>>>>
>>>>>>>>                                     Matthew Shears
>>>>>>>>                                     matthew at intpolicy.com
>>>>>>>>                                     <mailto:matthew at intpolicy.com>
>>>>>>>>                                     +447712472987
>>>>>>>>                                     <tel:+44%207712%20472987>
>>>>>>>>                                     Skype:mshears
>>>>>>>                                     _______________________________________________
>>>>>>>                                     NCSG-PC mailing list
>>>>>>>                                     NCSG-PC at lists.ncsg.is
>>>>>>>                                     <mailto:NCSG-PC at lists.ncsg.is>
>>>>>>>                                     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>                                     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>>>>
>>>>>>>
>>>>>>>                                 _______________________________________________
>>>>>>>                                 NCSG-PC mailing list
>>>>>>>                                 NCSG-PC at lists.ncsg.is
>>>>>>>                                 <mailto:NCSG-PC at lists.ncsg.is>
>>>>>>>                                 https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>                                 <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>>>                                 _______________________________________________
>>>>>>                                 NCSG-PC mailing list
>>>>>>                                 NCSG-PC at lists.ncsg.is
>>>>>>                                 <mailto:NCSG-PC at lists.ncsg.is>
>>>>>>                                 https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>                                 <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>>>
>>>>>>
>>>>>                             _______________________________________________
>>>>>                             NCSG-PC mailing list
>>>>>                             NCSG-PC at lists.ncsg.is
>>>>>                             <mailto:NCSG-PC at lists.ncsg.is>
>>>>>                             https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>                             <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>>
>>>>>
>>>>>                         _______________________________________________
>>>>>                         NCSG-PC mailing list
>>>>>                         NCSG-PC at lists.ncsg.is
>>>>>                         <mailto:NCSG-PC at lists.ncsg.is>
>>>>>                         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>                         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>
>>>>                         -- 
>>>>
>>>>
>>>>                         Matthew Shears
>>>>                         matthew at intpolicy.com
>>>>                         <mailto:matthew at intpolicy.com>
>>>>                         +447712472987 <tel:+44%207712%20472987>
>>>>                         Skype:mshears
>>>>
>>>>                         _______________________________________________
>>>>                         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>
>>>>
>>>>
>>>>                     <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>                     	Virus-free. www.avg.com
>>>>                     <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>
>>>>
>>>>                     <#m_6197814062825925350_m_-1376122550809326803_m_-670827426495722261_m_8430456596589667341_m_7701040911500582868_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>>                     -- 
>>>
>>>
>>>                     Matthew Shears
>>>                     matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>>                     +447712472987 <tel:+44%207712%20472987>
>>>                     Skype:mshears
>>>
>>>                 _______________________________________________
>>>                 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> 
>>>
>>         -- 
>>
>>
>>         Matthew Shears
>>         matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>>         +447712472987 <tel:+44%207712%20472987>
>>         Skype:mshears
>         _______________________________________________ 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/20170812/a675dec6/attachment.htm>

From rafik.dammak at gmail.com  Sun Aug 13 14:38:33 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Sun, 13 Aug 2017 20:38:33 +0900
Subject: [NCSG-PC] Endorsement of NCSG Comment on GNSO operating
 procedures change
In-Reply-To: <dad79800-a403-69ee-97ca-37a9550f84a5@mpicc.de>
References: <CAH5sThnKC2B0Zr_PAbu0OMLHZy2CEio4x4U3R6aXMEs74mD2fw@mail.gmail.com>
 <ae96bf49-8064-1423-7e3b-2d6ded0b8e88@intpolicy.com>
 <CAH5sTh=SEnOuY71Bs9+K3dekA_8pb7n7dLpcPf9YuROCKrWeuQ@mail.gmail.com>
 <c0ea9737-777d-2d2b-a067-fb623cd5e6da@intpolicy.com>
 <CAH5sThkuLKYbzotNzga147d-OupdqKPJ24CnP9vvkqLb4BqVKA@mail.gmail.com>
 <CAN1qJvC+jSTv1BAE3dtsOiejK3CmcWub7CxNP=E3=W9xaujxXg@mail.gmail.com>
 <CAH5sTh=7jRF6+5a9jtO1TgZwvfNxb3=Ftw=RpDbFmeWcth=d9w@mail.gmail.com>
 <dae73deb-65d5-64cb-f7f1-f8f7bf970b2b@intpolicy.com>
 <15206a94-ec0c-3d6c-2b63-57eb5e9bea66@mail.utoronto.ca>
 <CAN1qJvDrx=-uh_vBk_-WFekcjzv9HOXQ-qQ62hfGux3MKZOkvg@mail.gmail.com>
 <CAH5sThmOdTYXPyNbnJyvp_ZR8P=XZKW8ThV60bi4KVS5oZe3dQ@mail.gmail.com>
 <dad79800-a403-69ee-97ca-37a9550f84a5@mpicc.de>
Message-ID: <CAH5sTh=EU+28GEN-MQaMKKi9WZymxxU_kTTsMWT6Yna5HUavWQ@mail.gmail.com>

thanks all,
seeing the support for the comment and no objection made, I submitted the
draft. we are already 3 days passed the deadline. I included Farzaneh edits
since it was proposed a few days ago to the list.

thanks again to Matt for drafting.

Best,

Rafik

2017-08-12 23:19 GMT+09:00 Dr. Tatiana Tropina <t.tropina at mpicc.de>:

> Hi all,
>
> I support the amended version.
>
> Cheers,
>
> Tanya
>
> On 12/08/17 09:08, Rafik Dammak wrote:
>
> Hi Farzaneh, Mathew,
>
>
> I added your suggestion for rephrasing the last paragraph and I also added
> your previous suggestion from the other thread:
> *" If later on during implementing the operating procedures, it is found
> out that changes recommended by  DT   for some reason are not reflected in
> the new  GNSO operating procedures, GNSO should follow the DT advice in
> those circumstances and allow for the mistake to be corrected.  "*
>
> please find attached the latest version, if there is no objection in next
> 12hours, I will submit the comment.
>
> Best,
>
> Rafik
>
> 2017-08-11 23:44 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com>:
>
>> So I gather that there was not support for my suggested addition. I will
>> not add it in the document. I also find this sentence problematic:"Finally,
>> we should note that there was disagreement in the DT as to who should speak
>> on behalf of the GNSO as a Decisional Participant in the Empowered
>> Community. " there was disagreement but we reached consensus. This
>> sentence is not drafted carefully to reflect that there was consensus and
>> only emphasizes on the disagreement. I suggest reframing it like this: Finally,
>> we should note that the DT reached a consensus that *GNSO Council*
>> should speak on behalf of the GNSO as a Decisional Participant in the
>> Empowered Community.
>>
>> Farzaneh
>>
>> On Fri, Aug 11, 2017 at 10:14 AM, Stephanie Perrin <
>> stephanie.perrin at mail.utoronto.ca> wrote:
>>
>>> I think it looks fine now.  I endorse it!
>>>
>>> cheers SP
>>>
>>> On 2017-08-11 08:15, Matthew Shears wrote:
>>>
>>> Hi
>>>
>>> I have added a brief comment on the role of the GNSO Council.  Please
>>> review carefully.
>>>
>>> Note that the BC submission refers to this issue extensively.
>>>
>>> Matthew
>>>
>>> On 11/08/2017 03:33, Rafik Dammak wrote:
>>>
>>> Hi Matt, Stephanie,
>>>
>>> can you please add the two suggested comments to the draft asap?
>>> I see support for the draft but we should add those edits quickly.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> 2017-08-10 17:45 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com>:
>>>
>>>> I think we should add that. please also consider adding what I
>>>> mentioned in my previous email. DT had a debate and reached consensus on
>>>> many important issues which were contentious, mainly participation of GNSO
>>>> in the empowered community through the council and the thresholds to reach
>>>> decisions. As Stephanie agreed to add something like that, I kindly ask her
>>>> to just come up with a once sentence which encompasses what I said in my
>>>> previous email since she knows how the council functions better than I do.
>>>>
>>>> Farzaneh
>>>>
>>>> On Thu, Aug 10, 2017 at 4:37 AM, Rafik Dammak <rafik.dammak at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Matt,
>>>>>
>>>>> I do think we can add a similar line to our comment .
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>>>
>>>>> 2017-08-10 17:19 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>>>>>
>>>>>> I'm drawing it to the attention of the PC - the issue of the role of
>>>>>> Council was a contentious one in the DT with the BC and other suggesting
>>>>>> that the Council was exceeding its role if it took on EC responsibilities.
>>>>>> NCSG and RySG were aligned on this seeing no issue with Council assuming
>>>>>> the role.   My question was whether we thought we should add a similar line
>>>>>> on the role of Council in our submission.
>>>>>>
>>>>>> Matthew
>>>>>>
>>>>>> On 10/08/2017 09:13, Rafik Dammak wrote:
>>>>>>
>>>>>> Hi Matt,
>>>>>>
>>>>>> are you suggesting a change to the comment? do you have some wording
>>>>>> to add?
>>>>>>
>>>>>> Best,
>>>>>>
>>>>>> Rafik
>>>>>>
>>>>>> 2017-08-10 17:05 GMT+09:00 Matthew Shears <matthew at intpolicy.com>:
>>>>>>
>>>>>>> Hi all
>>>>>>>
>>>>>>> I draw your attention to this submission by the RySG:
>>>>>>>
>>>>>>> http://mm.icann.org/pipermail/comments-gnso-op-procedures-19
>>>>>>> jun17/attachments/20170807/1d703c9a/RySGpubliccomment-GNSOOp
>>>>>>> eratingProceduresandICANNBylaws-0001.pdf
>>>>>>>
>>>>>>> They note the following which we may wish to emulate (at a minimum
>>>>>>> the first line I would have thought):
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *The RySG fully recognises the authority of the GNSO Council to
>>>>>>> speak on behalf of the GNSO as Decisional Participant in the Empowered
>>>>>>> Community. This is in line with current practice and working methods and
>>>>>>> respects the existing equilibrium within the GNSO?s structure. The RySG
>>>>>>> agrees that on this point no changes need to be made to the ICANN Bylaws in
>>>>>>> relation to the role and description of the GNSO Council.*
>>>>>>> Matthew
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 10/08/2017 01:03, Rafik Dammak wrote:
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> the deadline for submission is this Friday. I attached the clean
>>>>>>> version for review. I understand that Matt, Poncelet, Stephanie support the
>>>>>>> comment. we need to hear from other PC members.
>>>>>>>
>>>>>>> Best,
>>>>>>>
>>>>>>> Rafik
>>>>>>>
>>>>>>> 2017-08-07 23:24 GMT+09:00 Stephanie Perrin <
>>>>>>> stephanie.perrin at mail.utoronto.ca>:
>>>>>>>
>>>>>>>> I think that is a really good idea, as these are important
>>>>>>>> procedures, and we need to be able to amend if required.  Hard to
>>>>>>>> anticipate everything, in my view...
>>>>>>>>
>>>>>>>> SP
>>>>>>>>
>>>>>>>> On 2017-08-07 08:49, farzaneh badii wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> I was on the DT group. I don't have the time to go through every
>>>>>>>> single change and see if they accord with what we agreed on. If you want in
>>>>>>>> the public comment we should ask that if later on during implementing the
>>>>>>>> operating procedures we find out that  changes recommended by  DT   for
>>>>>>>> some reason are not reflected in the new  GNSO operating procedures, GNSO
>>>>>>>> should follow the DT advice in those circumstances and allow for the
>>>>>>>> mistake to be corrected.
>>>>>>>>
>>>>>>>> Farzaneh
>>>>>>>>
>>>>>>>> On Mon, Aug 7, 2017 at 8:41 AM, Stephanie Perrin <
>>>>>>>> stephanie.perrin at mail.utoronto.ca> wrote:
>>>>>>>>
>>>>>>>>> It looks fine to me.  I don't have knowledge of or time to do the
>>>>>>>>> research on the issues at the moment, so I hope that those who do can catch
>>>>>>>>> things that need changes.
>>>>>>>>>
>>>>>>>>> cheers Stephanie
>>>>>>>>>
>>>>>>>>> On 2017-08-07 02:07, Rafik Dammak wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> the comment is quite straightforward and supporting the changes
>>>>>>>>> outlined in the public consultation.
>>>>>>>>> we can have as the deadline for review and endorsement the 9th
>>>>>>>>> August. I urge councilors, in particular, to review the changes since it
>>>>>>>>> concerns the operating procedures.
>>>>>>>>> Thanks, Matt again for the draft. I resolved the edits made by
>>>>>>>>> Ayden. ant proof-reading and review would be helpful.
>>>>>>>>>
>>>>>>>>> Best,
>>>>>>>>>
>>>>>>>>> Rafik
>>>>>>>>>
>>>>>>>>> 2017-08-05 6:33 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> I have made some minor alterations to style, but added nothing of
>>>>>>>>>> substance. I hope someone with more knowledge of this issue will be able to
>>>>>>>>>> contribute to our comment. Submissions are due in six days time. Thanks!
>>>>>>>>>>
>>>>>>>>>> Best wishes, Ayden
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -------- Original Message --------
>>>>>>>>>> Subject: Re: [NCSG-PC] NCSG Comment on GNSO operating procedures
>>>>>>>>>> change
>>>>>>>>>> Local Time: August 1, 2017 5:35 PM
>>>>>>>>>> UTC Time: August 1, 2017 4:35 PM
>>>>>>>>>> From: matthew at intpolicy.com
>>>>>>>>>> To: ncsg-pc at lists.ncsg.is, farzaneh badii <
>>>>>>>>>> farzaneh.badii at GMAIL.COM>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi all
>>>>>>>>>>
>>>>>>>>>> Wanted to get this back at the top of the list of to-do's as time
>>>>>>>>>> is running out.
>>>>>>>>>>
>>>>>>>>>> Appreciate the comments from some of the PC members but would
>>>>>>>>>> welcome additional inputs, thoughts, etc.
>>>>>>>>>>
>>>>>>>>>> See google doc below.
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>> Matthew
>>>>>>>>>>
>>>>>>>>>> On 27/07/2017 03:08, Martin Pablo Silva Valent wrote:
>>>>>>>>>>
>>>>>>>>>> Matt,
>>>>>>>>>> I don?t have any comment to do, I agree with the statements and
>>>>>>>>>> the wording. Let me know if I can do anything specific to help. Other than
>>>>>>>>>> that you have my support. Thanks!
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> Mart?n
>>>>>>>>>>
>>>>>>>>>> On Jul 25, 2017, at 8:22 PM, Rafik Dammak <rafik.dammak at gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> the deadline for the public comment is the 10th of August, we
>>>>>>>>>> have to finish consulting with NCSG members, review and endorsement prior
>>>>>>>>>> to that. I suggest 8th August as our internal deadline.
>>>>>>>>>>
>>>>>>>>>> Best,
>>>>>>>>>>
>>>>>>>>>> Rafik
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2017-07-25 23:28 GMT+09:00 Stefania Milan <stefania.milan at eui.eu>
>>>>>>>>>> :
>>>>>>>>>>
>>>>>>>>>> Hi Matt, thanks. What's the deadline for this? I am in transit
>>>>>>>>>>> (and in fact, on holiday), witch sketchy internet access and the doc
>>>>>>>>>>> doesn't open for me today (might be the poor connection...)
>>>>>>>>>>>
>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>
>>>>>>>>>>> On Jul 25, 2017, at 9:17 AM, Matthew Shears <
>>>>>>>>>>> matthew at intpolicy.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Let me qualify the last sentence - ICANN staff are not adding
>>>>>>>>>>> new items in addition to the work of the DT, but rather adding references
>>>>>>>>>>> to work done previously.
>>>>>>>>>>>
>>>>>>>>>>> On 25/07/2017 16:05, Matthew Shears wrote:
>>>>>>>>>>>
>>>>>>>>>>> Calling all PCers
>>>>>>>>>>>
>>>>>>>>>>> I have started on the above public comment but am still going
>>>>>>>>>>> through the consultation docs.  However, time marches on and we need to get
>>>>>>>>>>> this one underway.
>>>>>>>>>>>
>>>>>>>>>>> So, please review the consultation docs here:
>>>>>>>>>>>
>>>>>>>>>>> https://www.icann.org/public-comments/gnso-op-procedures-201
>>>>>>>>>>> 7-06-19-en
>>>>>>>>>>>
>>>>>>>>>>> And make comments in the google doc here:
>>>>>>>>>>>
>>>>>>>>>>> https://docs.google.com/document/d/1gydCJ3IFGsptk8BTYa8aQ5lF
>>>>>>>>>>> -ddk_Q9DWja7bZIgsiY/edit
>>>>>>>>>>> Note that ICANN staff have used this opportunity to include
>>>>>>>>>>> other changes that the DT did not discuss.
>>>>>>>>>>>
>>>>>>>>>>> Many thanks.
>>>>>>>>>>>
>>>>>>>>>>> Matthew
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> NCSG-PC mailing list
>>>>>>>>>>> NCSG-PC at lists.ncsg.is
>>>>>>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The information transmitted is intended only for the person or
>>>>>>>>>>> entity to which it is addressed and may contain confidential and/or
>>>>>>>>>>> privileged material. Any review, retransmission, dissemination,
>>>>>>>>>>> distribution, forwarding, or other use of, or taking of any action in
>>>>>>>>>>> reliance upon, this information by persons or entities other than the
>>>>>>>>>>> intended recipient is prohibited without the express permission of the
>>>>>>>>>>> sender. If you received this communication in error, please contact the
>>>>>>>>>>> sender and delete the material from any computer.
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>>>> Virus-free. www.avg.com
>>>>>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>>>>
>>>>>>>>>> _______________________________________________ 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
>>>>>>>>> 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 listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>>
>>>>>>> _______________________________________________ NCSG-PC mailing
>>>>>>> list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/
>>>>>>> listinfo/ncsg-pc
>>>>>>
>>>>>>
>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
>>>>>> www.avg.com
>>>>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>> <#m_593785527486172838_m_6197814062825925350_m_-1376122550809326803_m_-670827426495722261_m_8430456596589667341_m_7701040911500582868_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>>>>
>>>>>> _______________________________________________ NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>> --
>>>
>>>
>>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>>
>>> _______________________________________________ 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 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/20170813/cbb990d3/attachment.htm>

From rafik.dammak at gmail.com  Mon Aug 14 03:35:10 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Mon, 14 Aug 2017 09:35:10 +0900
Subject: [NCSG-PC] CCWG-IG motion amendments
In-Reply-To: <CAH5sTh=ceUbVxVCRDfapyhAozGwKfxuceEe3FA-k6f8e8XqYaw@mail.gmail.com>
References: <CAH5sTh=nhNnZEXoBHV=tc5G7XmQYOAiRu6JF2679fFxQanHY-w@mail.gmail.com>
 <CAH5sThkpU34JtOk9pVyCSVMJ7PAPZXrFgh+itD=jAFr7oXRW9Q@mail.gmail.com>
 <1e174dac-6ee7-f19c-4101-c0b7889a5f05@mail.utoronto.ca>
 <CAH5sTh=ceUbVxVCRDfapyhAozGwKfxuceEe3FA-k6f8e8XqYaw@mail.gmail.com>
Message-ID: <CAH5sThnGJKBC9TtVwABY-3DJczdVJ0bWjx7kyh6soOVR+ZC87g@mail.gmail.com>

Hi all,

the deadline for submission is this monday. please send your comments asap.
I will submit the current proposal by the deadline.

Best,

Rafik

2017-08-10 10:54 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:

> Hi Stephanie,
>
> if you recall in Hyderabad, Council asked the working group to align
> itself with the uniform framework for CCWG. the working group did a review
> of its charter and amended following the framework model (using a charter
> template). the amended charter was submitted in Copenhagen meeting.
>
> several councilors are still not satisfied with that and the request now
> with this motion is to suggest a new vehicle which is not CCWG but
> responding to other requirements and improving accountability and reporting
> mechanisms, also about submitting positions on behalf of the community and
> how to come back to charter organizations.
>
> The working group had a discussion of the matter and we think we can found
> out a new structure having a cross-community structure but not necessarily
> a CCWG. There is no model yet and the working group will be tasked to make
> a proposal. GNSO created previously several structures such as standing
> committee etc (a long list), so the CCWG-IG will end up a new one to the
> GNSO structures fauna. basically, it will be like a CCWG, behaving as CCWG
> but not having the name of CCWG...
>
> to be more candid and more direct,  several groups within GNSO are
> concerned that CCWG becomes more and more the model for any work including
> PDP. you can see similar concerns about the subpro WG working track 5
> on geonames.
>
> Best,
>
> Rafik
>
> ps I changed the permissions in the google doc, you should be able to
> comment there
>
>
> 2017-08-10 10:34 GMT+09:00 Stephanie Perrin <stephanie.perrin at mail.
> utoronto.ca>:
>
>> There is a typo in the thrid para, amtrying to get edit access to fix a
>> few things.  More important question is exactly what model did we have in
>> mind, if not a CCWG???
>>
>> cheers Steph
>>
>> On 2017-08-09 20:31, Rafik Dammak wrote:
>>
>> Hi all,
>>
>> are you ok with the proposed amendments https://docs.google.com/docume
>> nt/d/1LQWVaEgppF38Gvnm9SpvftHpdhI1BOGdRdl_YyBe3oA/edit? we should submit
>> them by the deadline Monday 14th August to be taken into account.
>>
>> Best,
>>
>> Rafik
>>
>> 2017-07-14 8:32 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:
>>
>>> Hi all,
>>>
>>> as you know, we asked for the CCWG-IG motion to be deferred so we can
>>> continue working on our amendments. that was supported by other groups like
>>> IPC due to the short time we had since Johannesburg meeting.
>>>
>>> Marilia, Farzaneh and I worked on making some amendments to the motion
>>> as follow-up of our NCSG Policy call this week https://docs.google.com/d
>>> ocument/d/1LQWVaEgppF38Gvnm9SpvftHpdhI1BOGdRdl_YyBe3oA/edit
>>>
>>> we are sharing this so we can discuss them. we will also share them with
>>> the wider NCSG list.
>>>
>>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170814/e315cc95/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Mon Aug 14 22:20:05 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Mon, 14 Aug 2017 15:20:05 -0400
Subject: [NCSG-PC] Fwd: Re: [council] Action Items: GNSO Council meeting
 13 July 2017
In-Reply-To: <CAH5sThmNyDpqLWihzCnA7jU_DtXscU7b2MrZjj0NUHTFqXuHxg@mail.gmail.com>
References: <CADWyk6xtZEdsyuTwGMBDTzPSyN3iRCMWVhkmZT_gK_x-4jKOSQ@mail.gmail.com>
 <93b25b52-2f9d-647d-bb57-c210a59034cc@mail.utoronto.ca>
 <CAH5sThnEzR7i7hZDiqvZz_xb8AzKnPOALH5sWVPXxANE0KqnFw@mail.gmail.com>
 <09dde1dd-be25-90d5-3cb7-93cc4b2f4362@intpolicy.com>
 <CAH5sThmNyDpqLWihzCnA7jU_DtXscU7b2MrZjj0NUHTFqXuHxg@mail.gmail.com>
Message-ID: <3c5e83a7-a111-277e-dabe-a95226b6404c@mail.utoronto.ca>

So it looks like significant opposition (Michele and Rubens both)., do 
you want to seek a compromise?

SP


On 2017-08-07 19:41, Rafik Dammak wrote:
> Hi Matt,
>
> we are not suggesting the withdrawal per se since it is in the initial 
> motion from Keith. we are proposing amendments in that area to give 
> the working group more time to provide a proposal (ICANN61 instead of 
> ICANN60 as proposed initially). There was already some question on the 
> transition phase between withdrawing and resume the working group with 
> a new structure.
>
> we cannot address the council concerns in the motion. We are proposing 
> a new amendment asking the council to itemize those concerns. The 
> working group can then be tasked to respond to them.
>
> the working group will have basically to work on proposing a new 
> vehicle and responding to the accountability and reporting concerns.
>
> Best,
>
> Rafik
>
> 2017-08-08 0:20 GMT+09:00 Matthew Shears <matthew at intpolicy.com 
> <mailto:matthew at intpolicy.com>>:
>
>     Hi Rafik
>
>     Not sure where this is at the moment, but I am a little confused
>     by this
>
>     4. To facilitate the work as requested under Resolved clause #3,
>     allowing for a reasonable time to coordinate with other SOs and
>     ACs to develop a new structure, and to ensure there is no gap
>     between the retirement of the CCWG-IC and the establishment of its
>     successor group, the GNSO Council shall withdraw as a Chartering
>     Organization from the CCWG-IG effective at the conclusion of ICANN
>     61 .
>
>
>     So we are suggesting the GNSO is withdrawing only because of the
>     structure - have we addressed the Council's other concerns?  
>     (Does this assume that whatever other structure the WG-IG assume
>     will not require the GNSO's support or endorsement?)   One of the
>     key issues, I understood, was that there needed to be some
>     accountability of the WG-IG back to the Council or
>     constituencies.  How then would this be accounted for? Or perhaps
>     the discussion has moved on and I am not up to speed.
>
>     Thanks.
>
>     Matthew
>
>
>
>
>     On 07/08/2017 13:50, Rafik Dammak wrote:
>>     Hi Stephanie,
>>
>>     I shared the proposed amendments in this list just after the last
>>     call but I didn't get any comment
>>     https://lists.ncsg.is/pipermail/ncsg-pc/2017-July/000737.html
>>     <https://lists.ncsg.is/pipermail/ncsg-pc/2017-July/000737.html>.
>>     no, we didn't submit the amendments to the council.
>>
>>     Best,
>>
>>     Rafik
>>
>>     2017-08-07 21:46 GMT+09:00 Stephanie Perrin
>>     <stephanie.perrin at mail.utoronto.ca
>>     <mailto:stephanie.perrin at mail.utoronto.ca>>:
>>
>>         Just checking, have we submitted our proposal for the IG item
>>         (see bolded bit below item 7) to the GNSO list?  Deadline
>>         looming....
>>
>>         cheers SP
>>
>>
>>
>>         -------- Forwarded Message --------
>>         Subject: 	Re: [council] Action Items: GNSO Council meeting 13
>>         July 2017
>>         Date: 	Mon, 7 Aug 2017 13:18:38 +1000
>>         From: 	Heather Forrest <haforrestesq at gmail.com>
>>         <mailto:haforrestesq at gmail.com>
>>         To: 	James M. Bladel <jbladel at godaddy.com>
>>         <mailto:jbladel at godaddy.com>, council at gnso.icann.org
>>         <mailto:council at gnso.icann.org> <council at gnso.icann.org>
>>         <mailto:council at gnso.icann.org>, Jeff Neuman
>>         <jeff.neuman at comlaude.com> <mailto:jeff.neuman at comlaude.com>,
>>         avri at apc.org <mailto:avri at apc.org>
>>         CC: 	gnso-secs at icann.org <mailto:gnso-secs at icann.org>
>>         <gnso-secs at icann.org> <mailto:gnso-secs at icann.org>
>>
>>
>>
>>         Dear colleagues,
>>
>>         Just following up on the point made by James on 18 July about
>>         whether or not to put the CWG-UCTN Final Report on our August
>>         agenda, or hold it to September's agenda. FYI the following
>>         has taken place since 18 July:
>>
>>           * ccNSO Council has voted on and approved the CWG-UCTN
>>             Final Report
>>           * SubPro is in the process of creating Work Track 5 on geo
>>             names
>>
>>         As a co-chair of this CWG, my personal view is that the GNSO
>>         can endorse the Final Report, but should make comments in the
>>         motion pointing to SubPro and the new WT5. In my view, the
>>         timing of such a motion (and how forcefully we make our
>>         comments about WT5) is dependent upon SubPro - let's put this
>>         on Council's agenda at a time most helpful to SubPro and WT5.
>>         With that in mind, I suggest we take some guidance from Jeff
>>         and Avri here.
>>
>>         I note that our document deadline for August meeting is in
>>         roughly 7 days, so we need time to pull together a motion if
>>         this is going onto the August agenda.
>>
>>         Best wishes,
>>
>>         Heather
>>
>>         On Tue, Jul 18, 2017 at 10:17 AM, James M. Bladel
>>         <jbladel at godaddy.com <mailto:jbladel at godaddy.com>> wrote:
>>
>>             Thank you, Nathalie.
>>
>>             Council Colleagues, a few semi-random thoughts on the
>>             items below:
>>
>>             #6. We have a small team working on the GNSO Response to
>>             the GAC's Johannesburg communique. Expect final draft
>>             language this week, with approval via email ballot to
>>             follow. The goal is to provide our response to the Board
>>             in advance of their meeting with the GAC in mid-August.
>>
>>             *#7. CCWG-IG - Please note that this item was
>>             **_deferred_**, rather than withdrawn. This means that it
>>             will appear on our next meeting's ballot for a vote. I
>>             know that some folks wanted to submit amendments, and I
>>             urge that these be posted to the Council list by the next
>>             document deadline (14 AUG), or the motion will head to a
>>             vote un-amended.**
>>             ***
>>             #8. This discussion item has been rescheduled for two
>>             subsequent meetings, so I'm hopeful that we will give it
>>             full consideration during our next meeting. I recommend
>>             we move it to the top of our non-voting agenda.
>>
>>             #9. Because this item is related to other ongoing
>>             activities, including follow-up from the GeoNames
>>             sessions in Johannesburg and the formation of SubPro Work
>>             Track 5, a motion for a vote may or may not appear on our
>>             August agenda. Stay tuned for further developments.
>>
>>             Thank you,
>>
>>             J.
>>             -----------------
>>             James Bladel
>>             GNSO Chair
>>
>>             On Jul 17, 2017, 16:50 -0500, Nathalie Peregrine
>>             <nathalie.peregrine at icann.org
>>             <mailto:nathalie.peregrine at icann.org>>, wrote:
>>>
>>>             Dear Councilors,
>>>
>>>             Please find the action items as stated during the
>>>             meeting, below and as attachment arising from the GNSO
>>>             Council meeting held on Thursday 13 July 2017.  Please
>>>             take note of the action items coming out of the Council
>>>             sessions and the proposed timing for delivering on these
>>>             actions.
>>>
>>>             *ACTION ITEMS GNSO COUNCIL MEETING 13 July 2017*
>>>
>>>             *_Item 3. Consent Agenda - Appointment of James Bladel
>>>             as the GNSO Representative to the Empowered Community_*
>>>
>>>               * the GNSO Secretariat to communicate this decision to
>>>                 the ICANN Secretary which will serve as the required
>>>                 written certification from the GNSO Chair
>>>                 designating the individual who shall represent the
>>>                 Decisional Participant on the EC Administration.
>>>
>>>             *__*
>>>
>>>             *_Item 4: COUNCIL VOTE ? Proposed Fundamental Bylaw
>>>             Changes_*
>>>
>>>               * GNSO Secretariat to forward the adopted resolution
>>>                 to the Empowered Community Administration before the
>>>                 expiration of the Approval Action Decision Period,
>>>                 as required under Section 1.4, Article 1, Annex D of
>>>                 the ICANN Bylaws.
>>>               * James Bladel, the GNSO?s representative to the
>>>                 Empowered Community Administration, to coordinate
>>>                 with the other four Decisional Participant
>>>                 representatives to ensure that the Empowered
>>>                 Community Administration observes and completes the
>>>                 appropriate process outlined in Section 1.4(b) and
>>>                 (c), Annex D.
>>>
>>>             *__*
>>>
>>>             *_Item 6. COUNCIL VOTE ? Approval of GNSO Council Review
>>>             of the GAC Communique from Johannesburg_*
>>>
>>>               * Volunteers to revise response to GAC Communique and
>>>                 circulate revised draft to the Council as soon as
>>>                 possible. Volunteers include: Paul, James, Jeff
>>>                 Neuman (if allowed), Rubens, Heather (sanity check),
>>>                 Phil, Darcy, possibly Stephanie (to convey Avri?s
>>>                 views), and Carlos. Volunteers to consider input
>>>                 received in relation to Geo Names section as well as
>>>                 IGO section, including offering the opportunity to
>>>                 detail IGO/INGO CRP recommendations with the ICANN
>>>                 Board prior to a vote being taken to provide details
>>>                 how small group, IGO comments factored into Final
>>>                 Report and recommendations.
>>>               * GNSO Leadership to provide 7-day notice of e-vote to
>>>                 approve response to GAC Communique
>>>
>>>             *__*
>>>
>>>             *_Item 7: COUNCIL Vote ? Next steps in relation to
>>>             Charter for the Cross Community Working Group on
>>>             Internet Governance_*
>>>
>>>               * Motion deferred - GNSO leadership to add this item
>>>                 to the Council agenda for August meeting.
>>>               * All Council members to provide input and proposed
>>>                 amendments to the motions as soon as possible so
>>>                 that discussion can continue on the mailing list
>>>                 ahead of the meeting.
>>>
>>>             *__*
>>>
>>>             *_Item 8. COUNCIL DISCUSSION ? Possible Change to the
>>>             Name of the GNSO_*
>>>
>>>               * Item deferred ? GNSO Council leadership to add this
>>>                 item to the Council agenda for August meeting.
>>>
>>>             *__*
>>>
>>>             *_Item 9: COUNCIL DISCUSSION ? Cross Community Working
>>>             Group on the Use of Country and Territory Names_*
>>>
>>>               * Council members to consider drafting Motion for
>>>                 August meeting on this topic.
>>>               * Ben Fuller to solicit input from ccNSO on this topic
>>>                 and provide feedback to the GNSO Council
>>>
>>>             *__*
>>>
>>>             Please note that all Action Items have been posted on
>>>             the Action Item wiki page here[community.icann.org]
>>>             <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_RgZlAg&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=3Tc6XSN5n8FryvXrAqUdyp0sa6kuAUqPfvvw4f3uwKQ&s=4DEDZ2Meg9ZUFIObabj6BRFzEywMdXPo7au4Kd0LSJI&e=>.
>>>             Please refer to this page for the recent status updates
>>>             on the Action items.
>>>
>>>             Thank you,
>>>
>>>             Kind regards,
>>>
>>>             Nathalie
>>>
>>>             -- 
>>>
>>>             Nathalie Peregrine
>>>
>>>             Specialist, SOAC Support (GNSO)
>>>
>>>             Internet Corporation for Assigned Names and Numbers (ICANN)
>>>
>>>             Email: nathalie.peregrine at icann.org
>>>             <http://nathalie.peregrine at icann.org%20>
>>>
>>>             Skype: nathalie.peregrine.icann
>>>
>>>             Find out more about the GNSO by taking our interactive
>>>             courses <http://learn.icann.org/courses/gnso> and
>>>             visiting the GNSO Newcomer pages[gnso.icann.org]
>>>             <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DgMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=YXXgWMx7AnEsK0bIjCRJ20RWD6FrJ7eshz4ee3BoCuw&s=z012pgyZrR1-Hdltx67AUtBaeooNRaHBDVfbgPe9pt8&e=>
>>>
>>
>>             _______________________________________________
>>             council mailing list
>>             council at gnso.icann.org <mailto:council at gnso.icann.org>
>>             https://mm.icann.org/mailman/listinfo/council
>>             <https://mm.icann.org/mailman/listinfo/council>
>>
>>
>>
>>         _______________________________________________
>>         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>
>>
>>
>>
>>     <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>     	Virus-free. www.avg.com
>>     <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>
>>
>>     <#m_6775909980563852075_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>>
>>     _______________________________________________
>>     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>
>
>     -- 
>
>
>     Matthew Shears
>     matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>     +447712472987 <tel:+44%207712%20472987>
>     Skype:mshears
>
>
>     _______________________________________________
>     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/20170814/d3aa1270/attachment.htm>

From avri at apc.org  Thu Aug 17 13:54:07 2017
From: avri at apc.org (avri doria)
Date: Thu, 17 Aug 2017 12:54:07 +0200
Subject: [NCSG-PC] Fwd: []Ws2-staff_acct Updated Report
In-Reply-To: <10fccd5a-d0aa-083c-5a08-7fe0b2fd95f6@apc.org>
References: <10fccd5a-d0aa-083c-5a08-7fe0b2fd95f6@apc.org>
Message-ID: <3d157d53-42ba-5ab8-5732-f41804b81701@apc.org>


Just an FYI.

avri



-------- Forwarded Message --------
Subject: 	[Ws2-staff_acct] Updated Report
Date: 	Thu, 17 Aug 2017 12:35:06 +0200
From: 	avri doria <avri at apc.org>
To: 	ws2-staff_acct at icann.org <ws2-staff_acct at icann.org>



Hi,

As was requested at our last meeting Patrick made the edits recommended
in his contribution, which we discussed during the meeting, in response
to the Board WS2 Caucus' objections to the recommendations from the group..

These changes are still in suggest mode and can be found at:
<https://docs.google.com/document/d/1vH5su7SDGE0i_rTstbYJ7tIaOFuRnV4dfqpwMTPoYa8/edit?usp=sharing>
(pdf attached)

The document remains open for comments and suggestions.  Our main item
of discussion at our next meeting will focus on these changes in an
attempt to produce a document acceptable to the ICANN trinity of
Organization, Board and Community in time to meet the current schedule
for plenary reading. Please take the time to review and comment before
our next meeting on 30 Aug at 19UTC.

Thanks to Patrick for the work done and thanks to the rest of you in
advance for your review of these suggested changes.

Avri



-------------- next part --------------
A non-text attachment was scrubbed...
Name: Report Staff Acct - Rev 1.2 + comments.pdf
Type: application/pdf
Size: 600919 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170817/9554a1f0/attachment.pdf>
-------------- next part --------------
_______________________________________________
Ws2-staff_acct mailing list
Ws2-staff_acct at icann.org
https://mm.icann.org/mailman/listinfo/ws2-staff_acct


From rafik.dammak at gmail.com  Thu Aug 17 14:41:47 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 17 Aug 2017 20:41:47 +0900
Subject: [NCSG-PC] Fwd: []Ws2-staff_acct Updated Report
In-Reply-To: <3d157d53-42ba-5ab8-5732-f41804b81701@apc.org>
References: <10fccd5a-d0aa-083c-5a08-7fe0b2fd95f6@apc.org>
 <3d157d53-42ba-5ab8-5732-f41804b81701@apc.org>
Message-ID: <CAH5sTh=GUj10c7beJ=dk6sTS=R--oe74eYUc+51ieq+OegK2mQ@mail.gmail.com>

Hi Avri,

Thanks for sharing this.
I guess if the report is sent to next plenary and approved there, it will
go into public comment period?
good heads-up for us to prepare an NCSG comment.

Best,

Rafik

2017-08-17 19:54 GMT+09:00 avri doria <avri at apc.org>:

>
> Just an FYI.
>
> avri
>
>
>
> -------- Forwarded Message --------
> Subject:        [Ws2-staff_acct] Updated Report
> Date:   Thu, 17 Aug 2017 12:35:06 +0200
> From:   avri doria <avri at apc.org>
> To:     ws2-staff_acct at icann.org <ws2-staff_acct at icann.org>
>
>
>
> Hi,
>
> As was requested at our last meeting Patrick made the edits recommended
> in his contribution, which we discussed during the meeting, in response
> to the Board WS2 Caucus' objections to the recommendations from the group..
>
> These changes are still in suggest mode and can be found at:
> <https://docs.google.com/document/d/1vH5su7SDGE0i_
> rTstbYJ7tIaOFuRnV4dfqpwMTPoYa8/edit?usp=sharing>
> (pdf attached)
>
> The document remains open for comments and suggestions.  Our main item
> of discussion at our next meeting will focus on these changes in an
> attempt to produce a document acceptable to the ICANN trinity of
> Organization, Board and Community in time to meet the current schedule
> for plenary reading. Please take the time to review and comment before
> our next meeting on 30 Aug at 19UTC.
>
> Thanks to Patrick for the work done and thanks to the rest of you in
> advance for your review of these suggested changes.
>
> Avri
>
>
>
>
> _______________________________________________
> 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/20170817/dfcf4a6d/attachment.htm>

From avri at apc.org  Thu Aug 17 23:27:07 2017
From: avri at apc.org (avri doria)
Date: Thu, 17 Aug 2017 22:27:07 +0200
Subject: [NCSG-PC] Fwd: []Ws2-staff_acct Updated Report
In-Reply-To: <CAH5sTh=GUj10c7beJ=dk6sTS=R--oe74eYUc+51ieq+OegK2mQ@mail.gmail.com>
References: <10fccd5a-d0aa-083c-5a08-7fe0b2fd95f6@apc.org>
 <3d157d53-42ba-5ab8-5732-f41804b81701@apc.org>
 <CAH5sTh=GUj10c7beJ=dk6sTS=R--oe74eYUc+51ieq+OegK2mQ@mail.gmail.com>
Message-ID: <01c48262-ea08-7261-787b-de6287ab312d@apc.org>

Hi,

we need two reading yet.  we failed out first attempt at a reading.

avri

On 17-Aug-17 13:41, Rafik Dammak wrote:
> Hi Avri,

>
> Thanks for sharing this.
> I guess if the report is sent to next plenary and approved there, it
> will go into public comment period?
> good heads-up for us to prepare an NCSG comment. 
>
> Best,
>
> Rafik
>
> 2017-08-17 19:54 GMT+09:00 avri doria <avri at apc.org
> <mailto:avri at apc.org>>:
>
>
>     Just an FYI.
>
>     avri
>
>
>
>     -------- Forwarded Message --------
>     Subject:        [Ws2-staff_acct] Updated Report
>     Date:   Thu, 17 Aug 2017 12:35:06 +0200
>     From:   avri doria <avri at apc.org <mailto:avri at apc.org>>
>     To:     ws2-staff_acct at icann.org <mailto:ws2-staff_acct at icann.org>
>     <ws2-staff_acct at icann.org <mailto:ws2-staff_acct at icann.org>>
>
>
>
>     Hi,
>
>     As was requested at our last meeting Patrick made the edits
>     recommended
>     in his contribution, which we discussed during the meeting, in
>     response
>     to the Board WS2 Caucus' objections to the recommendations from
>     the group..
>
>     These changes are still in suggest mode and can be found at:
>     <https://docs.google.com/document/d/1vH5su7SDGE0i_rTstbYJ7tIaOFuRnV4dfqpwMTPoYa8/edit?usp=sharing
>     <https://docs.google.com/document/d/1vH5su7SDGE0i_rTstbYJ7tIaOFuRnV4dfqpwMTPoYa8/edit?usp=sharing>>
>     (pdf attached)
>
>     The document remains open for comments and suggestions.  Our main item
>     of discussion at our next meeting will focus on these changes in an
>     attempt to produce a document acceptable to the ICANN trinity of
>     Organization, Board and Community in time to meet the current schedule
>     for plenary reading. Please take the time to review and comment before
>     our next meeting on 30 Aug at 19UTC.
>
>     Thanks to Patrick for the work done and thanks to the rest of you in
>     advance for your review of these suggested changes.
>
>     Avri
>
>
>
>
>     _______________________________________________
>     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



From rafik.dammak at gmail.com  Fri Aug 18 03:33:47 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Fri, 18 Aug 2017 09:33:47 +0900
Subject: [NCSG-PC] Update on GDPR
In-Reply-To: <CAH5sThmNDiVEM9i5wyhXACEWQy5ZowLW6Ek==cZ5F+ErK+U4+w@mail.gmail.com>
References: <CAH5sThnFA4eu4pPRtSLVyHHiG-wEE3dk8QCnp0LumeHuf7_buA@mail.gmail.com>
 <CAH5sTh=9FVWNvvbdEdyRBhXMQar7xFeHKFjdriBYPWMeSzF1HA@mail.gmail.com>
 <CAH5sThmNDiVEM9i5wyhXACEWQy5ZowLW6Ek==cZ5F+ErK+U4+w@mail.gmail.com>
Message-ID: <CAH5sThkO_Q3pnd7fpjfXZafotmwEFFWxycvX-UdXmV=NZ+9FuA@mail.gmail.com>

Hi Stephanie, Ayden, Wendy,

We will have NCSG Policy Call next Tuesday. Do you have any update you want
share from the GDPR taskforce prior or during the call?

Best,

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

From rafik.dammak at gmail.com  Fri Aug 18 03:35:59 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Fri, 18 Aug 2017 09:35:59 +0900
Subject: [NCSG-PC] Update on auctions and Whois RT
In-Reply-To: <CAH5sThnQ9Ayiq3-cL--JfpHZTotGrtFj+p5xXbLKKZXbp40o7w@mail.gmail.com>
References: <CAH5sThkqWU6SVAZ5y-D9oJMhmE9d-mqXsvsgfk68TJjNttnw7w@mail.gmail.com>
 <CAH5sThnQ9Ayiq3-cL--JfpHZTotGrtFj+p5xXbLKKZXbp40o7w@mail.gmail.com>
Message-ID: <CAH5sThkbaEUnZC0fRX=E8w_bX5Huxxevatsi2AY0xB6xGpRp7g@mail.gmail.com>

Hi  Stephanie,

As we discussed , I think you will share updates on auctions proceeds work
and WHOIS RT. It will be great to have that prior to NCSG call.
Thanks!

Best,

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

From rafik.dammak at gmail.com  Fri Aug 18 03:52:16 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Fri, 18 Aug 2017 09:52:16 +0900
Subject: [NCSG-PC] Prep for NCSG Policy call 22nd August and Council call
Message-ID: <CAH5sThmNUiE1PE_BJSZJH5hb5ysER6kSdid159rHW8KmL3KXkw@mail.gmail.com>

Hi All,

we will have our NCSG Polic call next week Tuesday and the council call.
I copied the draft agenda but it is going to be amended

we have 2 motions to vote on:
- on CCWG-IG, we submitted some amnendments. not all seen as friendly and
it is still under discussion. I am checking if we can reach common ground
with Keith. Wolf-Ulrich suggested some edits.
- on  rep replacement to SSR RT, and that is placeholder for the selection
from the SSC. Poncelet probably can give more updates.

it was proposed that the item #6 to be replaced with discussion about
subsequent procedure WG and WT5. as you recall there was thread ongoing on
council list https://mm.icann.org/pipermail/council/2017-August/020268.html
regarding the working methods of WT5 (some are concerend that will follow
CCWG model for decision-making).

there is also the topic regarding the procedure for handling whois
conflict. we made comment in the last public consulation in July.

please review the agenda and material prior to the call, since we need to
brief our members and explain our votes.

I would also like to suggest of someone can volunteer to take notes on the
discusson and/decisions we reach during the call.

Best,

Rafik

---------- Forwarded message ----------

Dear councilors,


Please find the Proposed Final Agenda for the GNSO Council Meeting on 24
August 2017 at 12:00 UTC. Additional necessary information will be added
upon receipt and an updated version circulated at that moment.

*Final Proposed Agenda 24 August 2017 - GNSO Council Meeting*



Please note that *all documents *referenced *in the agenda have been
gathered on a Wiki page for convenience and easier access:
https://community.icann.org/x/igwhB <https://community.icann.org/x/igwhB>*

This agenda was established according to the GNSO Operating Procedures
<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_council_op-2Dprocedures-2D01sep16-2Den.pdf&d=DQMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=55oYi9y1UeIL5juaxAkqpioz33PyWq>
v3.2,
updated on 01 September 2016.

For convenience:

   - An excerpt of the ICANN Bylaws defining the voting thresholds is
   provided in *Appendix 1* at the end of this agenda.
   - An excerpt from the Council Operating Procedures defining the absentee
   voting procedures is provided in *Appendix 2* at the end of this agenda.

Coordinated Universal Time: 12:00 UTC: http://tinyurl.com/y8tmfkkd

05:00 Los Angeles; 08:00 Washington; 13:00 London; 15:00 Istanbul; 22:00
Hobart

*GNSO Council Meeting Audio Cast*
To join the event click on the link: http://stream.icann.org:8000/gnso.m3u
Councilors should notify the GNSO Secretariat in advance if they will not
be able to attend and/or need a dial out call.

*___________________________________*

*Item 1. Administrative Matters (5 mins)*

1.1 - Roll Call

1.2 - Updates to Statements of Interest

1.3 - Review / Amend Agenda

1.4 - Note the status of minutes for the previous Council meetings per the
GNSO Operating Procedures:

Minutes <https://gnso.icann.org/en/meetings/minutes-council-28jun17-en.pdf> of
the meeting of the GNSO Council on 28 June 2017, posted on 20 July 2017.

Minutes <https://gnso.icann.org/en/meetings/minutes-council-13jul17-en.pdf>
of the meeting of the GNSO Council on 13 July 2017, posted on 03 August
2017.

*Item 2. Opening Remarks / Review of Projects & Action List (10 mins)*

2.1 - Review focus areas and provide updates on specific key themes /
topics, to include review of Projects List
<https://gnso.icann.org/en/council/project>and Action Item List
<https://community.icann.org/x/RgZlAg>

2.2 - Report results of e-vote on the Council response to the GAC
Communique.



*Item 3. Consent Agenda (5 mins)*

None



*Item 4: COUNCIL VOTE ? Updated Charter for the Cross Community Working
Group on Internet Governance (20 minutes)*

At ICANN57 in Hyderabad in November 2016, the GNSO Council approved a
motion conditioning the future participation of the GNSO as a Chartering
Organization of the CCWG on Internet Governance (CCWG-IG) upon a
comprehensive review of the group?s Charter by the CCWG-IG, in accordance
with the Framework of Uniform Principles for CCWGs that had been adopted
recently by the ccNSO and GNSO Councils
(*http://gnso.icann.org/en/drafts/uniform-framework-principles-recommendations-16sep16-en.pdf
<http://gnso.icann.org/en/drafts/uniform-framework-principles-recommendations-16sep16-en.pdf>*).
In its resolution, the GNSO Council had noted that the CCWG-IG?s future
work is expected to be subject to a clear work plan, with regular updates
and clear deliverables, and had requested that, by ICANN58, the CCWG-IG was
to report on its findings, which report may include a revised charter, and
the CCWG-IG was to also consider whether it will be preferable to
reconstitute the group under a new structure
(*https://gnso.icann.org/en/council/resolutions
- 20161107-3 <https://gnso.icann.org/en/council/resolutions#20161107-3>*).
The CCWG-IG provided a written report on its 2016 activity and a draft
revised Charter for the GNSO Council?s consideration on 10th March
2017 (*http://mm.icann.org/pipermail/council/2017-March/019816.html
<http://mm.icann.org/pipermail/council/2017-March/019816.html>*)

At its Public Meeting at ICANN58 in Copenhagen on 15 March 2017 and its
joint meeting with the ccNSO Council on 13 March 2017, the Council engaged
in a discussion with the CCWG-IG co-chairs regarding the group?s reports.
At the GNSO Council?s call on 18 May 2017, the Council continued its
discussion of the topic as well as during ICANN59 during which it became
clear that although there is strong support to continue the GNSO?s
involvement in Internet Governance, a CCWG is not considered the
appropriate vehicle for such involvement.

The Council discussed this motion on its 13 July 2017 call, where the vote
was deferred. Here the Council will consider the motion that has been
submitted in relation to this topic.

4.1 ? Presentation of *motion <https://community.icann.org/x/kAwhB>* (Keith
Drazek)

4.2 ? Council discussion

4.3 ? Council vote (voting threshold: simple majority)



*Item 5. COUNCIL VOTE ? Replacement for GNSO member for the Second
Security, Stability, and Resiliency of the DNS (SSR2) Review Team*

On 19 January 2017, the GNSO Council voted to approve its three primary
candidates for the Second Security, Stability, and Resiliency Review Team
(SSR2-RT). Emily Taylor, one of those three candidates, has since resigned
from the SSR2-RT. The Standing Selection Committee (SSC) has been tasked
with recommending a replacement candidate to be considered by the GNSO
Council.

Taking into account the criteria outlined in the call for volunteers, the
SSC has performed its review process and selected [name] to replace Emily
Taylor on the SSR2-RT.

Here, the Council will vote to approve [name] as the replacement for Emily
Taylor on the SSR2-RT.

5.1 ? Presentation of motion <https://community.icann.org/x/kAwhB> (Johan
Helsingius)

5.2 ? Council discussion

5.3 ? Council vote (voting threshold: simple majority)



*Item 6. COUNCIL DISCUSSION ? Changing the Name of the GNSO (15 minutes)*

Some in the community have noted that as domain name are available
globally, the term ?generic? has certain meanings to different parts of the
ICANN community, that the usage of ?generic? to describe a .brand is
potentially confusing, and among other reasons, that it might make sense to
substitute the word ?Generic? for ?Global? in Generic Names Supporting
Organization.

To consider this change, some on the GNSO Council have suggested that a
narrowly scoped Drafting Team should be formed to determine whether a
change of this nature is recommended and if so, develop a proposed
implementation plan to effectuate that change.

Here, the Council will discuss whether it supports the premise of changing
the name of the GNSO and if so, what next steps might be.

6.1 ? Presentation of discussion topic (Paul McGrady)

6.2 ? Council discussion

6.3 ? Next Steps



*Item 7: COUNCIL DISCUSSION ? Review of the Revised ICANN Procedure for
Handling Whois Conflicts with Privacy Law (20 minutes)*

As a result of community input and the work of the Implementation Advisory
Group (IAG), ICANN made effective the revised Whois Procedure
<https://whois.icann.org/en/revised-icann-procedure-handling-whois-conflicts-privacy-law>
on 18 April 2017 to better accommodate issues where Whois requirements
conflict with applicable laws.

As requested by this GNSO Council, ICANN published a paper
<https://www.icann.org/en/system/files/files/whois-privacy-conflicts-procedure-03may17-en.pdf>
for public comment
<https://www.icann.org/public-comments/whois-privacy-law-2017-05-03-en> to
provide analysis and solicit community input on the practicality and
feasibility of the triggers identified in the revised Whois procedure. The
public comment period was also intended to collect suggestions for moving
forward with the review. The public comment period closed on 7 July 2017
and the staff report of public comments
<https://www.icann.org/en/system/files/files/report-comments-whois-privacy-law-28jul17-en.pdf>
was published on 28 July 2017.

On 1 August 2017, the Council received a letter
<https://gnso.icann.org/en/correspondence/atallah-to-bladel-et-al-01aug17-en.pdf>
from Akram Attalah, providing a collection of possible options for
proceeding with the review, and offering to discuss those options or others
identified by Council.

Here, the Council will discuss options for moving forward with the review
of the Whois Procedure.

7.1 ? Update on current status (GNSO Council chairs)

7.2 ? Council Discussion

7.3 ? Next Steps



*Item 8: COUNCIL DISCUSSION ? PLANNING FOR ICANN60 (10 minutes)*

During ICANN59, the proposed block schedule for ICANN60 was shared (
https://gnso.icann.org/en/drafts/icann60-draft-prelim-block
-schedule-27jun17-en.pdf) ? note that further updates have been made as a
result of the SO/AC Planning Committee and the resulting cross-community
session selections. Based on requests received to date from the different
GNSO PDP WGs, CCWGs WGs, and cross community session landscape, the Council
leadership has revised its draft GNSO schedule for Council input and
review, available here. Following Council review, this draft GNSO schedule
will again be shared with the GNSO Stakeholder Groups and Constituencies to
facilitate their planning and scheduling.

8.1 - Update on planning for ICANN60 (Council leadership)

8.2 ? Council discussion

8.3 ? Next steps



*Item 9: ANY OTHER BUSINESS (5 minutes)*

9.1 ? Report from chairs on our call with Subsequent Procedures (?SubPro?)
PDP co-chairs, regarding the creation of Work Track 5 (WT5)

9.2 ? Update from CCWG-ACCT WS2

*________________________________*



*Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11,
Section 11.3(i))*

See https://www.icann.org/resources/pages/governance/bylaws-en/#article11*.*

*Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating
Procedures, Section 4.4)*

See https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170818/c87315f0/attachment.htm>

From icann at ferdeline.com  Sat Aug 19 14:39:19 2017
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Sat, 19 Aug 2017 07:39:19 -0400
Subject: [NCSG-PC] Prep for NCSG Policy call 22nd August and Council call
In-Reply-To: <CAH5sThmNUiE1PE_BJSZJH5hb5ysER6kSdid159rHW8KmL3KXkw@mail.gmail.com>
References: <CAH5sThmNUiE1PE_BJSZJH5hb5ysER6kSdid159rHW8KmL3KXkw@mail.gmail.com>
Message-ID: <lWs9lIIm8L_UIjse0BTky6jCU7EqvlQOvC0AhXOjm4rn3WvIAgjSTZn8i0xEg8nrWt4fzQx1AMKD1Tk0HcqMDYSziAM9TKN7piTcRkLzHNQ=@ferdeline.com>

Hi,

> I would also like to suggest of someone can volunteer to take notes on the discusson and/decisions we reach during the call.

Isn't note taking a staff responsibility? Certainly in the PDP WGs, staff kindly prepare action items and take notes which are circulated to members a few hours after the call, and they are generally accurate and neutral in tone. I would be grateful if staff were to take notes during our PC calls too, as it frees up our time to work on drafting comments.

Many thanks, Ayden

> -------- Original Message --------
> Subject: [NCSG-PC] Prep for NCSG Policy call 22nd August and Council call
> Local Time: 18 August 2017 1:52 AM
> UTC Time: 18 August 2017 00:52
> From: rafik.dammak at gmail.com
> To: ncsg-pc <ncsg-pc at lists.ncsg.is>
>
> Hi All,
>
> we will have our NCSG Polic call next week Tuesday and the council call.
> I copied the draft agenda but it is going to be amended
>
> we have 2 motions to vote on:
> - on CCWG-IG, we submitted some amnendments. not all seen as friendly and it is still under discussion. I am checking if we can reach common ground with Keith. Wolf-Ulrich suggested some edits.
> - on  rep replacement to SSR RT, and that is placeholder for the selection from the SSC. Poncelet probably can give more updates.
>
> it was proposed that the item #6 to be replaced with discussion about subsequent procedure WG and WT5. as you recall there was thread ongoing on council list https://mm.icann.org/pipermail/council/2017-August/020268.html regarding the working methods of WT5 (some are concerend that will follow CCWG model for decision-making).
>
> there is also the topic regarding the procedure for handling whois conflict. we made comment in the last public consulation in July.
>
> please review the agenda and material prior to the call, since we need to brief our members and explain our votes.
>
> I would also like to suggest of someone can volunteer to take notes on the discusson and/decisions we reach during the call.
>
> Best,
>
> Rafik
>
> ---------- Forwarded message ----------
>
> Dear councilors,
>
> Please find the Proposed Final Agenda for the GNSO Council Meeting on 24 August 2017 at 12:00 UTC. Additional necessary information will be added upon receipt and an updated version circulated at that moment.
>
> Final Proposed Agenda 24 August 2017 - GNSO Council Meeting
>
> Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/igwhB
>
> This agenda was established according to the [GNSO Operating Procedures](https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_council_op-2Dprocedures-2D01sep16-2Den.pdf&d=DQMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=55oYi9y1UeIL5juaxAkqpioz33PyWq) v3.2, updated on 01 September 2016.
>
> For convenience:
>
> - An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda.
>
> - An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda.
>
> Coordinated Universal Time: 12:00 UTC: http://tinyurl.com/y8tmfkkd
>
> 05:00 Los Angeles; 08:00 Washington; 13:00 London; 15:00 Istanbul; 22:00 Hobart
>
> GNSO Council Meeting Audio Cast
> To join the event click on the link: http://stream.icann.org:8000/gnso.m3u
> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call.
>
> ___________________________________
>
> Item 1. Administrative Matters (5 mins)
>
> 1.1 - Roll Call
>
> 1.2 - Updates to Statements of Interest
>
> 1.3 - Review / Amend Agenda
>
> 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures:
>
> [Minutes](https://gnso.icann.org/en/meetings/minutes-council-28jun17-en.pdf) of the meeting of the GNSO Council on 28 June 2017, posted on 20 July 2017.
>
> [Minutes](https://gnso.icann.org/en/meetings/minutes-council-13jul17-en.pdf) of the meeting of the GNSO Council on 13 July 2017, posted on 03 August 2017.
>
> Item 2. Opening Remarks / Review of Projects & Action List (10 mins)
>
> 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of [Projects List ](https://gnso.icann.org/en/council/project)and [Action Item List](https://community.icann.org/x/RgZlAg)
>
> 2.2 - Report results of e-vote on the Council response to the GAC Communique.
>
> Item 3. Consent Agenda (5 mins)
>
> None
>
> Item 4: COUNCIL VOTE ? Updated Charter for the Cross Community Working Group on Internet Governance (20 minutes)
>
> At ICANN57 in Hyderabad in November 2016, the GNSO Council approved a motion conditioning the future participation of the GNSO as a Chartering Organization of the CCWG on Internet Governance (CCWG-IG) upon a comprehensive review of the group?s Charter by the CCWG-IG, in accordance with the Framework of Uniform Principles for CCWGs that had been adopted recently by the ccNSO and GNSO Councils (http://gnso.icann.org/en/drafts/uniform-framework-principles-recommendations-16sep16-en.pdf). In its resolution, the GNSO Council had noted that the CCWG-IG?s future work is expected to be subject to a clear work plan, with regular updates and clear deliverables, and had requested that, by ICANN58, the CCWG-IG was to report on its findings, which report may include a revised charter, and the CCWG-IG was to also consider whether it will be preferable to reconstitute the group under a new structure ([https://gnso.icann.org/en/council/resolutions - 20161107-3](https://gnso.icann.org/en/council/resolutions#20161107-3)). The CCWG-IG provided a written report on its 2016 activity and a draft revised Charter for the GNSO Council?s consideration on 10th March 2017 (http://mm.icann.org/pipermail/council/2017-March/019816.html)
>
> At its Public Meeting at ICANN58 in Copenhagen on 15 March 2017 and its joint meeting with the ccNSO Council on 13 March 2017, the Council engaged in a discussion with the CCWG-IG co-chairs regarding the group?s reports. At the GNSO Council?s call on 18 May 2017, the Council continued its discussion of the topic as well as during ICANN59 during which it became clear that although there is strong support to continue the GNSO?s involvement in Internet Governance, a CCWG is not considered the appropriate vehicle for such involvement.
>
> The Council discussed this motion on its 13 July 2017 call, where the vote was deferred. Here the Council will consider the motion that has been submitted in relation to this topic.
>
> 4.1 ? Presentation of [motion](https://community.icann.org/x/kAwhB) (Keith Drazek)
>
> 4.2 ? Council discussion
>
> 4.3 ? Council vote (voting threshold: simple majority)
>
> Item 5. COUNCIL VOTE ? Replacement for GNSO member for the Second Security, Stability, and Resiliency of the DNS (SSR2) Review Team
>
> On 19 January 2017, the GNSO Council voted to approve its three primary candidates for the Second Security, Stability, and Resiliency Review Team (SSR2-RT). Emily Taylor, one of those three candidates, has since resigned from the SSR2-RT. The Standing Selection Committee (SSC) has been tasked with recommending a replacement candidate to be considered by the GNSO Council.
>
> Taking into account the criteria outlined in the call for volunteers, the SSC has performed its review process and selected [name] to replace Emily Taylor on the SSR2-RT.
>
> Here, the Council will vote to approve [name] as the replacement for Emily Taylor on the SSR2-RT.
>
> 5.1 ? Presentation of [motion](https://community.icann.org/x/kAwhB) (Johan Helsingius)
>
> 5.2 ? Council discussion
>
> 5.3 ? Council vote (voting threshold: simple majority)
>
> Item 6. COUNCIL DISCUSSION ? Changing the Name of the GNSO (15 minutes)
>
> Some in the community have noted that as domain name are available globally, the term ?generic? has certain meanings to different parts of the ICANN community, that the usage of ?generic? to describe a .brand is potentially confusing, and among other reasons, that it might make sense to substitute the word ?Generic? for ?Global? in Generic Names Supporting Organization.
>
> To consider this change, some on the GNSO Council have suggested that a narrowly scoped Drafting Team should be formed to determine whether a change of this nature is recommended and if so, develop a proposed implementation plan to effectuate that change.
>
> Here, the Council will discuss whether it supports the premise of changing the name of the GNSO and if so, what next steps might be.
>
> 6.1 ? Presentation of discussion topic (Paul McGrady)
>
> 6.2 ? Council discussion
>
> 6.3 ? Next Steps
>
> Item 7: COUNCIL DISCUSSION ? Review of the Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law (20 minutes)
>
> As a result of community input and the work of the Implementation Advisory Group (IAG), ICANN made effective the revised [Whois Procedure](https://whois.icann.org/en/revised-icann-procedure-handling-whois-conflicts-privacy-law) on 18 April 2017 to better accommodate issues where Whois requirements conflict with applicable laws.
>
> As requested by this GNSO Council, ICANN published a [paper](https://www.icann.org/en/system/files/files/whois-privacy-conflicts-procedure-03may17-en.pdf) for [public comment](https://www.icann.org/public-comments/whois-privacy-law-2017-05-03-en) to provide analysis and solicit community input on the practicality and feasibility of the triggers identified in the revised Whois procedure. The public comment period was also intended to collect suggestions for moving forward with the review. The public comment period closed on 7 July 2017 and the [staff report of public comments](https://www.icann.org/en/system/files/files/report-comments-whois-privacy-law-28jul17-en.pdf) was published on 28 July 2017.
>
> On 1 August 2017, the Council received a [letter](https://gnso.icann.org/en/correspondence/atallah-to-bladel-et-al-01aug17-en.pdf) from Akram Attalah, providing a collection of possible options for proceeding with the review, and offering to discuss those options or others identified by Council.
>
> Here, the Council will discuss options for moving forward with the review of the Whois Procedure.
>
> 7.1 ? Update on current status (GNSO Council chairs)
>
> 7.2 ? Council Discussion
>
> 7.3 ? Next Steps
>
> Item 8: COUNCIL DISCUSSION ? PLANNING FOR ICANN60 (10 minutes)
>
> During ICANN59, the proposed block schedule for ICANN60 was shared (https://gnso.icann.org/en/drafts/icann60-draft-prelim-block-schedule-27jun17-en.pdf) ? note that further updates have been made as a result of the SO/AC Planning Committee and the resulting cross-community session selections. Based on requests received to date from the different GNSO PDP WGs, CCWGs WGs, and cross community session landscape, the Council leadership has revised its draft GNSO schedule for Council input and review, available here. Following Council review, this draft GNSO schedule will again be shared with the GNSO Stakeholder Groups and Constituencies to facilitate their planning and scheduling.
>
> 8.1 - Update on planning for ICANN60 (Council leadership)
>
> 8.2 ? Council discussion
>
> 8.3 ? Next steps
>
> Item 9: ANY OTHER BUSINESS (5 minutes)
>
> 9.1 ? Report from chairs on our call with Subsequent Procedures (?SubPro?) PDP co-chairs, regarding the creation of Work Track 5 (WT5)
>
> 9.2 ? Update from CCWG-ACCT WS2
>
> ________________________________
>
> Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i))
>
> See https://www.icann.org/resources/pages/governance/bylaws-en/#article11.
>
> Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4)
>
> See https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170819/434ff198/attachment.htm>

From rafik.dammak at gmail.com  Sun Aug 20 06:03:10 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Sun, 20 Aug 2017 12:03:10 +0900
Subject: [NCSG-PC] agenda for NCSG Policy Call
Message-ID: <CAH5sThkZHLHq=koB+bJBXR1fNL4aVMEr1uKmXGdCcKEH0jVw+g@mail.gmail.com>

Hi all,

please find the draft agenda for NCSG Policy call,

I. Roll call/Introduction
II. GNSO Council Call Preparation

   - Council Agenda :
   https://gnso.icann.org/en/meetings/agenda-council-24aug17-en.htm
   - Motions:
   https://community.icann.org/display/gnsocouncilmeetings/Motions+24+August+2017

III. Policy Update
- Planning public comments responses:
https://www.icann.org/public-comments#open-public

   - Statistical Analysis of DNS Abuse in gTLDs (SADAG) Report (19th Sep)
   - Address Supporting Organization (ASO) Review Final Report (6th Sep)

- Update from Working Groups:
  * GDPR task force
  * WHOIS Review Team & RDS Working Group
  * Auctions Proceeds
  * Others: RPM, new gTLD Subsequent procedures, CCT RT, SSR RT
  reference active GNSO project list
https://gnso.icann.org/en/meetings/projects-list-16aug17-en.pdf
  * Any other activity?
IV. AOB
   * Planning for Abu Dhabi meeting

Best,

Rafik
IV. AO
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170820/7be44fe4/attachment.htm>

From ncsg at tapani.tarvainen.info  Mon Aug 21 13:15:07 2017
From: ncsg at tapani.tarvainen.info (Tapani Tarvainen)
Date: Mon, 21 Aug 2017 13:15:07 +0300
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <a4711c36-d73a-4ea5-8626-9fdf38c1ddcb@mail.utoronto.ca>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
 <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
 <9Ss39VrjfeqaHXkON9GzqzE7ee1iiGlGgcIENhyto_En1Kd47WjOxlOaEGJ4vz0tsACrIy-KG6PD8JtkOLjJ4N0KZFJoNd_ZSA_EeeB0p5Q=@ferdeline.com>
 <b5da8dba-f02e-944e-bae8-e4f939d09955@mail.utoronto.ca>
 <CAH5sTh=aVgpE1bT=du+LgbWfSBPgQyVF8hirPuo_EOGzzTq6Jg@mail.gmail.com>
 <a4711c36-d73a-4ea5-8626-9fdf38c1ddcb@mail.utoronto.ca>
Message-ID: <20170821101507.GJ17935@tehanu.it.jyu.fi>

Picking up an old thread,

Terri Agnew asked me where we are with this. Seems to me we are in
perfect agreement here, so I guess I can tell her it's Rafik.

Tapani

On Aug 08 11:10, Stephanie Perrin (stephanie.perrin at mail.utoronto.ca) wrote:

> Thanks for agreeing to do this Fik, and yes we definitely need to
> work on our procedures.  I think the webinar used for the Nomcom
> process was a great idea (even though I regret to say I was not on
> the call).  Folks need to have a clear understanding of workload and
> expectations in all these positions.
> 
> cheers steph
> 
> 
> On 2017-08-08 03:07, Rafik Dammak wrote:
> >Hi all,
> >
> >Thanks for the vote of confidence. I will be glad to appointed as
> >rep to SSC for a period if that helps. However, I still want that
> >we work on general process though for selecting and appointing
> >representatives based on the previous experience (please check the
> >other thread proposing several procedures to work on).
> >
> >Best,
> >
> >Rafik
> >
> >
> >2017-08-08 9:57 GMT+09:00 Stephanie Perrin
> ><stephanie.perrin at mail.utoronto.ca
> ><mailto:stephanie.perrin at mail.utoronto.ca>>:
> >
> >    +1 for Rafik.
> >
> >    Stephanie
> >
> >
> >    On 2017-08-07 17:48, Ayden F?rdeline wrote:
> >>    +1; appointing Rafik - if he has the bandwidth - is an excellent
> >>    idea, Martin.
> >>
> >>    Best, Ayden
> >>
> >>>    -------- Original Message --------
> >>>    Subject: Re: [NCSG-PC] 3rd SSC representative
> >>>    Local Time: 7 August 2017 9:30 PM
> >>>    UTC Time: 7 August 2017 20:30
> >>>    From: t.tropina at mpicc.de <mailto:t.tropina at mpicc.de>
> >>>    To: ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>
> >>>
> >>>
> >>>    Dear all,
> >>>
> >>>    I agree with Martin about Rafik. If he is still interested --
> >>>    the best way to fill in this slot would be to appoint. Him.
> >>>
> >>>    Cheers,
> >>>
> >>>    Tanya
> >>>
> >>>
> >>>    On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
> >>>>    That process is not there in more, we have to make a new one
> >>>>    (remember it was questioned and then one of the candidate drop,
> >>>>    and then the other also refused to finish the process like
> >>>>    that). So we have to go from scratch, but if Rafik is still
> >>>>    interested I would promote to have him considered first for
> >>>>    many good reasons. If not, the question is if we open the call
> >>>>    to the list or we keep it in the PC member list (fue to their
> >>>>    leadership role in ncsg policy make sense they are close enough
> >>>>    to be part of the SSC of the Council).
> >>>>
> >>>>    Cheers,
> >>>>    Mart?n
> >>>>
> >>>>>    On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji <pileleji at ymca.gm
> >>>>>    <mailto:pileleji at ymca.gm>> wrote:
> >>>>>
> >>>>>    Dear Colleagues
> >>>>>
> >>>>>    We  know the third slot was stalled?, but as the
> >>>>>process had     started already can that processs be
> >>>>>completed.
> >>>>>
> >>>>>
> >>>>>    Kind Regards
> >>>>>
> >>>>>
> >>>>>    Poncelet
> >>>>>
> >>>>>
> >>>>>    On 7 August 2017 at 16:17, Martin Pablo Silva Valent
> >>>>>    <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>> wrote:
> >>>>>
> >>>>>        Should we open this call to the discuss list or keep it in
> >>>>>        the pc members? I know we are still a few month from the
> >>>>>        election, but if no one else steps in one of the candidate
> >>>>>        that wasn?t elected could have this position.
> >>>>>
> >>>>>        Last time Rafik was in the run for this, if he still wants
> >>>>>        it he should have priority to be considered.
> >>>>>
> >>>>>        Cheers,
> >>>>>        Martin
> >>>>>
> >>>>>
> >>>>>        > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen
> >>>>>        <ncsg at tapani.tarvainen.info
> >>>>>        <mailto:ncsg at tapani.tarvainen.info>> wrote:
> >>>>>        >
> >>>>>        > Dear PC,
> >>>>>        >
> >>>>>        > I've been reminded we still haven't appointed our 3rd
> >>>>>        representative
> >>>>>        > to the GNSO Standing Selection Committee.
> >>>>>        >
> >>>>>        > It would be nice if we could get it done reasonably soon.
> >>>>>        >
> >>>>>        > Cheers,
> >>>>>        >
> >>>>>        > --
> >>>>>        > Tapani Tarvainen
> >>>>>        > _______________________________________________
> >>>>>        > 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>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>    --
> >>>>>
> >>>>>    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/
> >>>>>    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
> >>>>>    <http://www.diplointernetgovernance.org/>
> >>>>>


From matthew at intpolicy.com  Mon Aug 21 13:17:48 2017
From: matthew at intpolicy.com (Matthew Shears)
Date: Mon, 21 Aug 2017 11:17:48 +0100
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <20170821101507.GJ17935@tehanu.it.jyu.fi>
References: <20170807161246.7uo3qx4orjtcnzte@tarvainen.info>
 <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
 <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
 <9Ss39VrjfeqaHXkON9GzqzE7ee1iiGlGgcIENhyto_En1Kd47WjOxlOaEGJ4vz0tsACrIy-KG6PD8JtkOLjJ4N0KZFJoNd_ZSA_EeeB0p5Q=@ferdeline.com>
 <b5da8dba-f02e-944e-bae8-e4f939d09955@mail.utoronto.ca>
 <CAH5sTh=aVgpE1bT=du+LgbWfSBPgQyVF8hirPuo_EOGzzTq6Jg@mail.gmail.com>
 <a4711c36-d73a-4ea5-8626-9fdf38c1ddcb@mail.utoronto.ca>
 <20170821101507.GJ17935@tehanu.it.jyu.fi>
Message-ID: <db0c9a73-efe9-1800-cf8f-6dd8859c5625@intpolicy.com>

Apologies, was intending on picking this one up some time ago.  I agree 
that Rafik has the support and his name should be put forward.

Matthew


On 21/08/2017 11:15, Tapani Tarvainen wrote:
> Picking up an old thread,
>
> Terri Agnew asked me where we are with this. Seems to me we are in
> perfect agreement here, so I guess I can tell her it's Rafik.
>
> Tapani
>
> On Aug 08 11:10, Stephanie Perrin (stephanie.perrin at mail.utoronto.ca) wrote:
>
>> Thanks for agreeing to do this Fik, and yes we definitely need to
>> work on our procedures.  I think the webinar used for the Nomcom
>> process was a great idea (even though I regret to say I was not on
>> the call).  Folks need to have a clear understanding of workload and
>> expectations in all these positions.
>>
>> cheers steph
>>
>>
>> On 2017-08-08 03:07, Rafik Dammak wrote:
>>> Hi all,
>>>
>>> Thanks for the vote of confidence. I will be glad to appointed as
>>> rep to SSC for a period if that helps. However, I still want that
>>> we work on general process though for selecting and appointing
>>> representatives based on the previous experience (please check the
>>> other thread proposing several procedures to work on).
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>>
>>> 2017-08-08 9:57 GMT+09:00 Stephanie Perrin
>>> <stephanie.perrin at mail.utoronto.ca
>>> <mailto:stephanie.perrin at mail.utoronto.ca>>:
>>>
>>>     +1 for Rafik.
>>>
>>>     Stephanie
>>>
>>>
>>>     On 2017-08-07 17:48, Ayden F?rdeline wrote:
>>>>     +1; appointing Rafik - if he has the bandwidth - is an excellent
>>>>     idea, Martin.
>>>>
>>>>     Best, Ayden
>>>>
>>>>>     -------- Original Message --------
>>>>>     Subject: Re: [NCSG-PC] 3rd SSC representative
>>>>>     Local Time: 7 August 2017 9:30 PM
>>>>>     UTC Time: 7 August 2017 20:30
>>>>>     From: t.tropina at mpicc.de <mailto:t.tropina at mpicc.de>
>>>>>     To: ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>
>>>>>
>>>>>
>>>>>     Dear all,
>>>>>
>>>>>     I agree with Martin about Rafik. If he is still interested --
>>>>>     the best way to fill in this slot would be to appoint. Him.
>>>>>
>>>>>     Cheers,
>>>>>
>>>>>     Tanya
>>>>>
>>>>>
>>>>>     On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
>>>>>>     That process is not there in more, we have to make a new one
>>>>>>     (remember it was questioned and then one of the candidate drop,
>>>>>>     and then the other also refused to finish the process like
>>>>>>     that). So we have to go from scratch, but if Rafik is still
>>>>>>     interested I would promote to have him considered first for
>>>>>>     many good reasons. If not, the question is if we open the call
>>>>>>     to the list or we keep it in the PC member list (fue to their
>>>>>>     leadership role in ncsg policy make sense they are close enough
>>>>>>     to be part of the SSC of the Council).
>>>>>>
>>>>>>     Cheers,
>>>>>>     Mart?n
>>>>>>
>>>>>>>     On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji <pileleji at ymca.gm
>>>>>>>     <mailto:pileleji at ymca.gm>> wrote:
>>>>>>>
>>>>>>>     Dear Colleagues
>>>>>>>
>>>>>>>     We  know the third slot was stalled?, but as the
>>>>>>> process had     started already can that processs be
>>>>>>> completed.
>>>>>>>
>>>>>>>
>>>>>>>     Kind Regards
>>>>>>>
>>>>>>>
>>>>>>>     Poncelet
>>>>>>>
>>>>>>>
>>>>>>>     On 7 August 2017 at 16:17, Martin Pablo Silva Valent
>>>>>>>     <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>> wrote:
>>>>>>>
>>>>>>>         Should we open this call to the discuss list or keep it in
>>>>>>>         the pc members? I know we are still a few month from the
>>>>>>>         election, but if no one else steps in one of the candidate
>>>>>>>         that wasn?t elected could have this position.
>>>>>>>
>>>>>>>         Last time Rafik was in the run for this, if he still wants
>>>>>>>         it he should have priority to be considered.
>>>>>>>
>>>>>>>         Cheers,
>>>>>>>         Martin
>>>>>>>
>>>>>>>
>>>>>>>         > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen
>>>>>>>         <ncsg at tapani.tarvainen.info
>>>>>>>         <mailto:ncsg at tapani.tarvainen.info>> wrote:
>>>>>>>         >
>>>>>>>         > Dear PC,
>>>>>>>         >
>>>>>>>         > I've been reminded we still haven't appointed our 3rd
>>>>>>>         representative
>>>>>>>         > to the GNSO Standing Selection Committee.
>>>>>>>         >
>>>>>>>         > It would be nice if we could get it done reasonably soon.
>>>>>>>         >
>>>>>>>         > Cheers,
>>>>>>>         >
>>>>>>>         > --
>>>>>>>         > Tapani Tarvainen
>>>>>>>         > _______________________________________________
>>>>>>>         > 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>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>     --
>>>>>>>
>>>>>>>     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/
>>>>>>>     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
>>>>>>>     <http://www.diplointernetgovernance.org/>
>>>>>>>
> _______________________________________________
> 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 AVG.
> http://www.avg.com

-- 


Matthew Shears
matthew at intpolicy.com
+447712472987
Skype:mshears



From ncsg at tapani.tarvainen.info  Tue Aug 22 17:04:56 2017
From: ncsg at tapani.tarvainen.info (Tapani Tarvainen)
Date: Tue, 22 Aug 2017 17:04:56 +0300
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <db0c9a73-efe9-1800-cf8f-6dd8859c5625@intpolicy.com>
References: <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
 <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
 <9Ss39VrjfeqaHXkON9GzqzE7ee1iiGlGgcIENhyto_En1Kd47WjOxlOaEGJ4vz0tsACrIy-KG6PD8JtkOLjJ4N0KZFJoNd_ZSA_EeeB0p5Q=@ferdeline.com>
 <b5da8dba-f02e-944e-bae8-e4f939d09955@mail.utoronto.ca>
 <CAH5sTh=aVgpE1bT=du+LgbWfSBPgQyVF8hirPuo_EOGzzTq6Jg@mail.gmail.com>
 <a4711c36-d73a-4ea5-8626-9fdf38c1ddcb@mail.utoronto.ca>
 <20170821101507.GJ17935@tehanu.it.jyu.fi>
 <db0c9a73-efe9-1800-cf8f-6dd8859c5625@intpolicy.com>
Message-ID: <20170822140456.4rrsntiq55mycd6s@tarvainen.info>

Hi,

Following agreement on today's call I notified Terri & the secretariat
that Rafik it is.

Tapani

On Mon, Aug 21, 2017 at 11:17:48AM +0100, Matthew Shears (matthew at intpolicy.com) wrote:
> 
> Apologies, was intending on picking this one up some time ago.  I agree that
> Rafik has the support and his name should be put forward.
> 
> Matthew
> 
> 
> On 21/08/2017 11:15, Tapani Tarvainen wrote:
> > Picking up an old thread,
> > 
> > Terri Agnew asked me where we are with this. Seems to me we are in
> > perfect agreement here, so I guess I can tell her it's Rafik.
> > 
> > Tapani
> > 
> > On Aug 08 11:10, Stephanie Perrin (stephanie.perrin at mail.utoronto.ca) wrote:
> > 
> > > Thanks for agreeing to do this Fik, and yes we definitely need to
> > > work on our procedures.  I think the webinar used for the Nomcom
> > > process was a great idea (even though I regret to say I was not on
> > > the call).  Folks need to have a clear understanding of workload and
> > > expectations in all these positions.
> > > 
> > > cheers steph
> > > 
> > > 
> > > On 2017-08-08 03:07, Rafik Dammak wrote:
> > > > Hi all,
> > > > 
> > > > Thanks for the vote of confidence. I will be glad to appointed as
> > > > rep to SSC for a period if that helps. However, I still want that
> > > > we work on general process though for selecting and appointing
> > > > representatives based on the previous experience (please check the
> > > > other thread proposing several procedures to work on).
> > > > 
> > > > Best,
> > > > 
> > > > Rafik
> > > > 
> > > > 
> > > > 2017-08-08 9:57 GMT+09:00 Stephanie Perrin
> > > > <stephanie.perrin at mail.utoronto.ca
> > > > <mailto:stephanie.perrin at mail.utoronto.ca>>:
> > > > 
> > > >     +1 for Rafik.
> > > > 
> > > >     Stephanie
> > > > 
> > > > 
> > > >     On 2017-08-07 17:48, Ayden F?rdeline wrote:
> > > > >     +1; appointing Rafik - if he has the bandwidth - is an excellent
> > > > >     idea, Martin.
> > > > > 
> > > > >     Best, Ayden
> > > > > 
> > > > > >     -------- Original Message --------
> > > > > >     Subject: Re: [NCSG-PC] 3rd SSC representative
> > > > > >     Local Time: 7 August 2017 9:30 PM
> > > > > >     UTC Time: 7 August 2017 20:30
> > > > > >     From: t.tropina at mpicc.de <mailto:t.tropina at mpicc.de>
> > > > > >     To: ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>
> > > > > > 
> > > > > > 
> > > > > >     Dear all,
> > > > > > 
> > > > > >     I agree with Martin about Rafik. If he is still interested --
> > > > > >     the best way to fill in this slot would be to appoint. Him.
> > > > > > 
> > > > > >     Cheers,
> > > > > > 
> > > > > >     Tanya
> > > > > > 
> > > > > > 
> > > > > >     On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
> > > > > > >     That process is not there in more, we have to make a new one
> > > > > > >     (remember it was questioned and then one of the candidate drop,
> > > > > > >     and then the other also refused to finish the process like
> > > > > > >     that). So we have to go from scratch, but if Rafik is still
> > > > > > >     interested I would promote to have him considered first for
> > > > > > >     many good reasons. If not, the question is if we open the call
> > > > > > >     to the list or we keep it in the PC member list (fue to their
> > > > > > >     leadership role in ncsg policy make sense they are close enough
> > > > > > >     to be part of the SSC of the Council).
> > > > > > > 
> > > > > > >     Cheers,
> > > > > > >     Mart?n
> > > > > > > 
> > > > > > > >     On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji <pileleji at ymca.gm
> > > > > > > >     <mailto:pileleji at ymca.gm>> wrote:
> > > > > > > > 
> > > > > > > >     Dear Colleagues
> > > > > > > > 
> > > > > > > >     We  know the third slot was stalled?, but as the
> > > > > > > > process had     started already can that processs be
> > > > > > > > completed.
> > > > > > > > 
> > > > > > > > 
> > > > > > > >     Kind Regards
> > > > > > > > 
> > > > > > > > 
> > > > > > > >     Poncelet
> > > > > > > > 
> > > > > > > > 
> > > > > > > >     On 7 August 2017 at 16:17, Martin Pablo Silva Valent
> > > > > > > >     <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>> wrote:
> > > > > > > > 
> > > > > > > >         Should we open this call to the discuss list or keep it in
> > > > > > > >         the pc members? I know we are still a few month from the
> > > > > > > >         election, but if no one else steps in one of the candidate
> > > > > > > >         that wasn?t elected could have this position.
> > > > > > > > 
> > > > > > > >         Last time Rafik was in the run for this, if he still wants
> > > > > > > >         it he should have priority to be considered.
> > > > > > > > 
> > > > > > > >         Cheers,
> > > > > > > >         Martin
> > > > > > > > 
> > > > > > > > 
> > > > > > > >         > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen
> > > > > > > >         <ncsg at tapani.tarvainen.info
> > > > > > > >         <mailto:ncsg at tapani.tarvainen.info>> wrote:
> > > > > > > >         >
> > > > > > > >         > Dear PC,
> > > > > > > >         >
> > > > > > > >         > I've been reminded we still haven't appointed our 3rd
> > > > > > > >         representative
> > > > > > > >         > to the GNSO Standing Selection Committee.
> > > > > > > >         >
> > > > > > > >         > It would be nice if we could get it done reasonably soon.
> > > > > > > >         >
> > > > > > > >         > Cheers,
> > > > > > > >         >
> > > > > > > >         > --
> > > > > > > >         > Tapani Tarvainen
> > > > > > > >         > _______________________________________________
> > > > > > > >         > 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>
> > > > > > > > 
> > > > > > > > 
> > > > > > > > 
> > > > > > > > 
> > > > > > > >     --
> > > > > > > > 
> > > > > > > >     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/
> > > > > > > >     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
> > > > > > > >     <http://www.diplointernetgovernance.org/>
> > > > > > > > 
> > _______________________________________________
> > 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 AVG.
> > http://www.avg.com
> 
> -- 
> 
> 
> Matthew Shears
> matthew at intpolicy.com
> +447712472987
> Skype:mshears


From pileleji at ymca.gm  Tue Aug 22 17:37:48 2017
From: pileleji at ymca.gm (Poncelet Ileleji)
Date: Tue, 22 Aug 2017 14:37:48 +0000
Subject: [NCSG-PC] 3rd SSC representative
In-Reply-To: <20170822140456.4rrsntiq55mycd6s@tarvainen.info>
References: <6166CA63-D9DD-47E2-B107-E6CA6D416B19@gmail.com>
 <CAEux40vRF7O2ruBs1q0ieyzOcD9+0i9zRhAgkMZC_w_s+eTddQ@mail.gmail.com>
 <C47A71B1-0D66-46EE-A4F4-4D0622EC3D8B@gmail.com>
 <0ec300fc-831c-97cd-d0f4-012813a1aa6c@mpicc.de>
 <9Ss39VrjfeqaHXkON9GzqzE7ee1iiGlGgcIENhyto_En1Kd47WjOxlOaEGJ4vz0tsACrIy-KG6PD8JtkOLjJ4N0KZFJoNd_ZSA_EeeB0p5Q=@ferdeline.com>
 <b5da8dba-f02e-944e-bae8-e4f939d09955@mail.utoronto.ca>
 <CAH5sTh=aVgpE1bT=du+LgbWfSBPgQyVF8hirPuo_EOGzzTq6Jg@mail.gmail.com>
 <a4711c36-d73a-4ea5-8626-9fdf38c1ddcb@mail.utoronto.ca>
 <20170821101507.GJ17935@tehanu.it.jyu.fi>
 <db0c9a73-efe9-1800-cf8f-6dd8859c5625@intpolicy.com>
 <20170822140456.4rrsntiq55mycd6s@tarvainen.info>
Message-ID: <CAEux40sENAboOOs6BCB_j8e5NpJhnVGYen4BXbFneC5cK-MJtw@mail.gmail.com>

Thanks Tapani,

Now  NCSG is now complete on the SSC.

Kind Regards

Poncelet



On 22 August 2017 at 14:04, Tapani Tarvainen <ncsg at tapani.tarvainen.info>
wrote:

> Hi,
>
> Following agreement on today's call I notified Terri & the secretariat
> that Rafik it is.
>
> Tapani
>
> On Mon, Aug 21, 2017 at 11:17:48AM +0100, Matthew Shears (
> matthew at intpolicy.com) wrote:
> >
> > Apologies, was intending on picking this one up some time ago.  I agree
> that
> > Rafik has the support and his name should be put forward.
> >
> > Matthew
> >
> >
> > On 21/08/2017 11:15, Tapani Tarvainen wrote:
> > > Picking up an old thread,
> > >
> > > Terri Agnew asked me where we are with this. Seems to me we are in
> > > perfect agreement here, so I guess I can tell her it's Rafik.
> > >
> > > Tapani
> > >
> > > On Aug 08 11:10, Stephanie Perrin (stephanie.perrin at mail.utoronto.ca)
> wrote:
> > >
> > > > Thanks for agreeing to do this Fik, and yes we definitely need to
> > > > work on our procedures.  I think the webinar used for the Nomcom
> > > > process was a great idea (even though I regret to say I was not on
> > > > the call).  Folks need to have a clear understanding of workload and
> > > > expectations in all these positions.
> > > >
> > > > cheers steph
> > > >
> > > >
> > > > On 2017-08-08 03:07, Rafik Dammak wrote:
> > > > > Hi all,
> > > > >
> > > > > Thanks for the vote of confidence. I will be glad to appointed as
> > > > > rep to SSC for a period if that helps. However, I still want that
> > > > > we work on general process though for selecting and appointing
> > > > > representatives based on the previous experience (please check the
> > > > > other thread proposing several procedures to work on).
> > > > >
> > > > > Best,
> > > > >
> > > > > Rafik
> > > > >
> > > > >
> > > > > 2017-08-08 9:57 GMT+09:00 Stephanie Perrin
> > > > > <stephanie.perrin at mail.utoronto.ca
> > > > > <mailto:stephanie.perrin at mail.utoronto.ca>>:
> > > > >
> > > > >     +1 for Rafik.
> > > > >
> > > > >     Stephanie
> > > > >
> > > > >
> > > > >     On 2017-08-07 17:48, Ayden F?rdeline wrote:
> > > > > >     +1; appointing Rafik - if he has the bandwidth - is an
> excellent
> > > > > >     idea, Martin.
> > > > > >
> > > > > >     Best, Ayden
> > > > > >
> > > > > > >     -------- Original Message --------
> > > > > > >     Subject: Re: [NCSG-PC] 3rd SSC representative
> > > > > > >     Local Time: 7 August 2017 9:30 PM
> > > > > > >     UTC Time: 7 August 2017 20:30
> > > > > > >     From: t.tropina at mpicc.de <mailto:t.tropina at mpicc.de>
> > > > > > >     To: ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>
> > > > > > >
> > > > > > >
> > > > > > >     Dear all,
> > > > > > >
> > > > > > >     I agree with Martin about Rafik. If he is still interested
> --
> > > > > > >     the best way to fill in this slot would be to appoint. Him.
> > > > > > >
> > > > > > >     Cheers,
> > > > > > >
> > > > > > >     Tanya
> > > > > > >
> > > > > > >
> > > > > > >     On 07/08/17 19:33, Martin Pablo Silva Valent wrote:
> > > > > > > >     That process is not there in more, we have to make a new
> one
> > > > > > > >     (remember it was questioned and then one of the
> candidate drop,
> > > > > > > >     and then the other also refused to finish the process
> like
> > > > > > > >     that). So we have to go from scratch, but if Rafik is
> still
> > > > > > > >     interested I would promote to have him considered first
> for
> > > > > > > >     many good reasons. If not, the question is if we open
> the call
> > > > > > > >     to the list or we keep it in the PC member list (fue to
> their
> > > > > > > >     leadership role in ncsg policy make sense they are close
> enough
> > > > > > > >     to be part of the SSC of the Council).
> > > > > > > >
> > > > > > > >     Cheers,
> > > > > > > >     Mart?n
> > > > > > > >
> > > > > > > > >     On Aug 7, 2017, at 1:45 PM, Poncelet Ileleji <
> pileleji at ymca.gm
> > > > > > > > >     <mailto:pileleji at ymca.gm>> wrote:
> > > > > > > > >
> > > > > > > > >     Dear Colleagues
> > > > > > > > >
> > > > > > > > >     We  know the third slot was stalled?, but as the
> > > > > > > > > process had     started already can that processs be
> > > > > > > > > completed.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >     Kind Regards
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >     Poncelet
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >     On 7 August 2017 at 16:17, Martin Pablo Silva Valent
> > > > > > > > >     <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.
> com>> wrote:
> > > > > > > > >
> > > > > > > > >         Should we open this call to the discuss list or
> keep it in
> > > > > > > > >         the pc members? I know we are still a few month
> from the
> > > > > > > > >         election, but if no one else steps in one of the
> candidate
> > > > > > > > >         that wasn?t elected could have this position.
> > > > > > > > >
> > > > > > > > >         Last time Rafik was in the run for this, if he
> still wants
> > > > > > > > >         it he should have priority to be considered.
> > > > > > > > >
> > > > > > > > >         Cheers,
> > > > > > > > >         Martin
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >         > On Aug 7, 2017, at 1:12 PM, Tapani Tarvainen
> > > > > > > > >         <ncsg at tapani.tarvainen.info
> > > > > > > > >         <mailto:ncsg at tapani.tarvainen.info>> wrote:
> > > > > > > > >         >
> > > > > > > > >         > Dear PC,
> > > > > > > > >         >
> > > > > > > > >         > I've been reminded we still haven't appointed
> our 3rd
> > > > > > > > >         representative
> > > > > > > > >         > to the GNSO Standing Selection Committee.
> > > > > > > > >         >
> > > > > > > > >         > It would be nice if we could get it done
> reasonably soon.
> > > > > > > > >         >
> > > > > > > > >         > Cheers,
> > > > > > > > >         >
> > > > > > > > >         > --
> > > > > > > > >         > Tapani Tarvainen
> > > > > > > > >         > _______________________________________________
> > > > > > > > >         > 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>
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >     --
> > > > > > > > >
> > > > > > > > >     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/
> > > > > > > > >     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
> > > > > > > > >     <http://www.diplointernetgovernance.org/>
> > > > > > > > >
> > > _______________________________________________
> > > 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 AVG.
> > > http://www.avg.com
> >
> > --
> >
> >
> > Matthew Shears
> > matthew at intpolicy.com
> > +447712472987
> > Skype:mshears
> _______________________________________________
> 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/20170822/2fb0a29d/attachment.htm>

From rafik.dammak at gmail.com  Thu Aug 24 02:50:16 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 24 Aug 2017 08:50:16 +0900
Subject: [NCSG-PC] Fwd: [council] Updated Motion on the CCWG-IG
In-Reply-To: <504F95D0035A264EBB1BFAABAA772B957F32EBB7@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <504F95D0035A264EBB1BFAABAA772B957F32EBB7@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Message-ID: <CAH5sThksaFAzv8Qz=hveXQrLC-ncOyBrUcfV3YSYB4JvA0QO2g@mail.gmail.com>

Hi all,

here the response from Keith. I discussed with him regarding the amendments
and I am ok with the changes. the new version is an acceptable one.

Best,

Rafik

---------- Forwarded message ----------
From: Drazek, Keith via council <council at gnso.icann.org>
Date: 2017-08-23 17:18 GMT+09:00
Subject: [council] Updated Motion on the CCWG-IG
To: "council at gnso.icann.org" <council at gnso.icann.org>


Hi all,



To prepare for our vote on the CCWG-IG motion this Thursday, here?s where
we stand.



I?d like to thank both Rafik and Wolf-Ulrich for their input last week.
Rafik and I exchanged emails again this week and I believe we are in sync.



As the maker of the motion:



   1. I accept the proposed change of the withdrawal deadline from ICANN 60
   to ICANN 61.
   2. I agree that we need some additional clarity about the expected
   timeline leading up to ICANN 61, so the transition can be as seamless as
   possible. I suggest we target a GNSO Council meeting mid-way between ICANN
   60 and ICANN 61 as the opportunity for the GNSO Council to review the
   proposed replacement structure. I?m also support acknowledging further that
   the GNSO Council expects a replacement to be created by ICANN 61.
   3. With the extension, ICANN 61 needs to be the clear date for
   withdrawal. If we leave wiggle room in the motion, then the work of finding
   a replacement will not have the urgency or attention it requires. We are
   extending the date to allow for the necessary work, but I think that new
   date needs to be firm. We have all seen how, at ICANN, ?work fills the time
   and space provided.? We need to avoid further slippage and set clear
   expectations for ourselves and for the other Chartering Organizations.



As such, I?ve attached updated motion language that I believe addresses the
points raised to date.



James, as the seconder of the motion, do you concur or have any concerns?



Regards,

Keith

_______________________________________________
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/20170824/011d239b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Motion CCWG IG - 24 August 2017.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 21246 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170824/011d239b/attachment.docx>

From matthew at intpolicy.com  Thu Aug 24 15:39:02 2017
From: matthew at intpolicy.com (Matthew Shears)
Date: Thu, 24 Aug 2017 13:39:02 +0100
Subject: [NCSG-PC] Fwd: [council] Updated Motion on the CCWG-IG
In-Reply-To: <CAH5sThksaFAzv8Qz=hveXQrLC-ncOyBrUcfV3YSYB4JvA0QO2g@mail.gmail.com>
References: <504F95D0035A264EBB1BFAABAA772B957F32EBB7@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
 <CAH5sThksaFAzv8Qz=hveXQrLC-ncOyBrUcfV3YSYB4JvA0QO2g@mail.gmail.com>
Message-ID: <41cb5039-0c10-43aa-6092-b2a001329f13@intpolicy.com>

This looks good - thanks Rafik.


On 24/08/2017 00:50, Rafik Dammak wrote:
> Hi all,
>
> here the response from Keith. I discussed with him regarding the 
> amendments and I am ok with the changes. the new version is an 
> acceptable one.
>
> Best,
>
> Rafik
>
> ---------- Forwarded message ----------
> From: *Drazek, Keith via council* <council at gnso.icann.org 
> <mailto:council at gnso.icann.org>>
> Date: 2017-08-23 17:18 GMT+09:00
> Subject: [council] Updated Motion on the CCWG-IG
> To: "council at gnso.icann.org <mailto:council at gnso.icann.org>" 
> <council at gnso.icann.org <mailto:council at gnso.icann.org>>
>
>
> Hi all,
>
> To prepare for our vote on the CCWG-IG motion this Thursday, here?s 
> where we stand.
>
> I?d like to thank both Rafik and Wolf-Ulrich for their input last 
> week.  Rafik and I exchanged emails again this week and I believe we 
> are in sync.
>
> As the maker of the motion:
>
>  1. I accept the proposed change of the withdrawal deadline from ICANN
>     60 to ICANN 61.
>  2. I agree that we need some additional clarity about the expected
>     timeline leading up to ICANN 61, so the transition can be as
>     seamless as possible. I suggest we target a GNSO Council meeting
>     mid-way between ICANN 60 and ICANN 61 as the opportunity for the
>     GNSO Council to review the proposed replacement structure. I?m
>     also support acknowledging further that the GNSO Council expects a
>     replacement to be created by ICANN 61.
>  3. With the extension, ICANN 61 needs to be the clear date for
>     withdrawal. If we leave wiggle room in the motion, then the work
>     of finding a replacement will not have the urgency or attention it
>     requires. We are extending the date to allow for the necessary
>     work, but I think that new date needs to be firm. We have all seen
>     how, at ICANN, ?work fills the time and space provided.? We need
>     to avoid further slippage and set clear expectations for ourselves
>     and for the other Chartering Organizations.
>
> As such, I?ve attached updated motion language that I believe 
> addresses the points raised to date.
>
> James, as the seconder of the motion, do you concur or have any concerns?
>
> Regards,
>
> Keith
>
>
> _______________________________________________
> council mailing list
> council at gnso.icann.org <mailto:council at gnso.icann.org>
> https://mm.icann.org/mailman/listinfo/council 
> <https://mm.icann.org/mailman/listinfo/council>
>
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
> 	Virus-free. www.avg.com 
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

-- 


Matthew Shears
matthew at intpolicy.com
+447712472987
Skype:mshears

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

From farzaneh.badii at gmail.com  Thu Aug 24 16:31:03 2017
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Thu, 24 Aug 2017 13:31:03 +0000
Subject: [NCSG-PC] Fwd: [council] Updated Motion on the CCWG-IG
In-Reply-To: <41cb5039-0c10-43aa-6092-b2a001329f13@intpolicy.com>
References: <504F95D0035A264EBB1BFAABAA772B957F32EBB7@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
 <CAH5sThksaFAzv8Qz=hveXQrLC-ncOyBrUcfV3YSYB4JvA0QO2g@mail.gmail.com>
 <41cb5039-0c10-43aa-6092-b2a001329f13@intpolicy.com>
Message-ID: <CAN1qJvBpH08JD+KdVG4WazseZ4x-2uc5H93ZHOwKFP2n2869Ew@mail.gmail.com>

Observer - I agree. Thanks Rafik for getting this done. It was time
consuming and hard to fight for.

On Thu, Aug 24, 2017 at 8:42 AM Matthew Shears <matthew at intpolicy.com>
wrote:

> This looks good - thanks Rafik.
>
> On 24/08/2017 00:50, Rafik Dammak wrote:
>
> Hi all,
>
> here the response from Keith. I discussed with him regarding the
> amendments and I am ok with the changes. the new version is an acceptable
> one.
>
> Best,
>
> Rafik
>
> ---------- Forwarded message ----------
> From: Drazek, Keith via council <council at gnso.icann.org>
> Date: 2017-08-23 17:18 GMT+09:00
> Subject: [council] Updated Motion on the CCWG-IG
> To: "council at gnso.icann.org" <council at gnso.icann.org>
>
>
> Hi all,
>
>
>
> To prepare for our vote on the CCWG-IG motion this Thursday, here?s where
> we stand.
>
>
>
> I?d like to thank both Rafik and Wolf-Ulrich for their input last week.
> Rafik and I exchanged emails again this week and I believe we are in sync.
>
>
>
> As the maker of the motion:
>
>
>
>    1. I accept the proposed change of the withdrawal deadline from ICANN
>    60 to ICANN 61.
>    2. I agree that we need some additional clarity about the expected
>    timeline leading up to ICANN 61, so the transition can be as seamless as
>    possible. I suggest we target a GNSO Council meeting mid-way between ICANN
>    60 and ICANN 61 as the opportunity for the GNSO Council to review the
>    proposed replacement structure. I?m also support acknowledging further that
>    the GNSO Council expects a replacement to be created by ICANN 61.
>    3. With the extension, ICANN 61 needs to be the clear date for
>    withdrawal. If we leave wiggle room in the motion, then the work of finding
>    a replacement will not have the urgency or attention it requires. We are
>    extending the date to allow for the necessary work, but I think that new
>    date needs to be firm. We have all seen how, at ICANN, ?work fills the time
>    and space provided.? We need to avoid further slippage and set clear
>    expectations for ourselves and for the other Chartering Organizations.
>
>
>
> As such, I?ve attached updated motion language that I believe addresses
> the points raised to date.
>
>
>
> James, as the seconder of the motion, do you concur or have any concerns?
>
>
>
> Regards,
>
> Keith
>
> _______________________________________________
> council mailing list
> council at gnso.icann.org
> https://mm.icann.org/mailman/listinfo/council
>
>
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
> www.avg.com
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> <#m_-2938874596675133609_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
>
> _______________________________________________
> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
> --
>
>
> Matthew Shearsmatthew at intpolicy.com
> +447712472987Skype:mshears
>
> _______________________________________________
> 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/20170824/c0eaca59/attachment.htm>

From rafik.dammak at gmail.com  Thu Aug 24 16:32:12 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 24 Aug 2017 22:32:12 +0900
Subject: [NCSG-PC] Fwd: [council] Updated Motion on the CCWG-IG
In-Reply-To: <CAN1qJvBpH08JD+KdVG4WazseZ4x-2uc5H93ZHOwKFP2n2869Ew@mail.gmail.com>
References: <504F95D0035A264EBB1BFAABAA772B957F32EBB7@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
 <CAH5sThksaFAzv8Qz=hveXQrLC-ncOyBrUcfV3YSYB4JvA0QO2g@mail.gmail.com>
 <41cb5039-0c10-43aa-6092-b2a001329f13@intpolicy.com>
 <CAN1qJvBpH08JD+KdVG4WazseZ4x-2uc5H93ZHOwKFP2n2869Ew@mail.gmail.com>
Message-ID: <CAH5sThk31w8kUve3rd7QfWkdU6G3+K99TG1sDoOpakCtuVdjAg@mail.gmail.com>

hi all,

the motion was approved :) work starts for the CCWG-IG

Rafik

 2017-08-24 22:31 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com>:

> Observer - I agree. Thanks Rafik for getting this done. It was time
> consuming and hard to fight for.
>
> On Thu, Aug 24, 2017 at 8:42 AM Matthew Shears <matthew at intpolicy.com>
> wrote:
>
>> This looks good - thanks Rafik.
>>
>> On 24/08/2017 00:50, Rafik Dammak wrote:
>>
>> Hi all,
>>
>> here the response from Keith. I discussed with him regarding the
>> amendments and I am ok with the changes. the new version is an acceptable
>> one.
>>
>> Best,
>>
>> Rafik
>>
>> ---------- Forwarded message ----------
>> From: Drazek, Keith via council <council at gnso.icann.org>
>> Date: 2017-08-23 17:18 GMT+09:00
>> Subject: [council] Updated Motion on the CCWG-IG
>> To: "council at gnso.icann.org" <council at gnso.icann.org>
>>
>>
>> Hi all,
>>
>>
>>
>> To prepare for our vote on the CCWG-IG motion this Thursday, here?s where
>> we stand.
>>
>>
>>
>> I?d like to thank both Rafik and Wolf-Ulrich for their input last week.
>> Rafik and I exchanged emails again this week and I believe we are in sync.
>>
>>
>>
>> As the maker of the motion:
>>
>>
>>
>>    1. I accept the proposed change of the withdrawal deadline from ICANN
>>    60 to ICANN 61.
>>    2. I agree that we need some additional clarity about the expected
>>    timeline leading up to ICANN 61, so the transition can be as seamless as
>>    possible. I suggest we target a GNSO Council meeting mid-way between ICANN
>>    60 and ICANN 61 as the opportunity for the GNSO Council to review the
>>    proposed replacement structure. I?m also support acknowledging further that
>>    the GNSO Council expects a replacement to be created by ICANN 61.
>>    3. With the extension, ICANN 61 needs to be the clear date for
>>    withdrawal. If we leave wiggle room in the motion, then the work of finding
>>    a replacement will not have the urgency or attention it requires. We are
>>    extending the date to allow for the necessary work, but I think that new
>>    date needs to be firm. We have all seen how, at ICANN, ?work fills the time
>>    and space provided.? We need to avoid further slippage and set clear
>>    expectations for ourselves and for the other Chartering Organizations.
>>
>>
>>
>> As such, I?ve attached updated motion language that I believe addresses
>> the points raised to date.
>>
>>
>>
>> James, as the seconder of the motion, do you concur or have any concerns?
>>
>>
>>
>> Regards,
>>
>> Keith
>>
>> _______________________________________________
>> council mailing list
>> council at gnso.icann.org
>> https://mm.icann.org/mailman/listinfo/council
>>
>>
>>
>>
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
>> www.avg.com
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>> <#m_-7052838523074276160_m_-2938874596675133609_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>>
>>
>> _______________________________________________
>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>>
>> --
>>
>>
>> Matthew Shearsmatthew at intpolicy.com+447712472987 <+44%207712%20472987>Skype:mshears
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
> --
> Farzaneh
>
> _______________________________________________
> 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/20170824/5c5f0118/attachment.htm>

From avri at apc.org  Fri Aug 25 13:59:48 2017
From: avri at apc.org (avri doria)
Date: Fri, 25 Aug 2017 12:59:48 +0200
Subject: [NCSG-PC] *** SPAM ***Re: Fwd: [council] Updated Motion on the
 CCWG-IG
In-Reply-To: <CAH5sThk31w8kUve3rd7QfWkdU6G3+K99TG1sDoOpakCtuVdjAg@mail.gmail.com>
References: <504F95D0035A264EBB1BFAABAA772B957F32EBB7@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
 <CAH5sThksaFAzv8Qz=hveXQrLC-ncOyBrUcfV3YSYB4JvA0QO2g@mail.gmail.com>
 <41cb5039-0c10-43aa-6092-b2a001329f13@intpolicy.com>
 <CAN1qJvBpH08JD+KdVG4WazseZ4x-2uc5H93ZHOwKFP2n2869Ew@mail.gmail.com>
 <CAH5sThk31w8kUve3rd7QfWkdU6G3+K99TG1sDoOpakCtuVdjAg@mail.gmail.com>
Message-ID: <a9f60070-aa5d-566a-9eeb-3d9c24c43fb6@apc.org>

observer

congratulations on pulling it off.

thanks

avri


On 24-Aug-17 15:32, Rafik Dammak wrote:
> hi all,
>
> the motion was approved :) work starts for the CCWG-IG
>
> Rafik
>
> ?2017-08-24 22:31 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com
> <mailto:farzaneh.badii at gmail.com>>:
>
>     Observer - I agree. Thanks Rafik for getting this done. It was
>     time consuming and hard to fight for.?
>
>     On Thu, Aug 24, 2017 at 8:42 AM Matthew Shears
>     <matthew at intpolicy.com <mailto:matthew at intpolicy.com>> wrote:
>
>         This looks good - thanks Rafik.
>
>
>         On 24/08/2017 00:50, Rafik Dammak wrote:
>>         Hi all,
>>
>>         here the response from Keith. I discussed with him regarding
>>         the amendments and I am ok with the changes. the new version
>>         is an acceptable one.
>>
>>         Best,
>>
>>         Rafik
>>
>>         ---------- Forwarded message ----------
>>         From: *Drazek, Keith via council* <council at gnso.icann.org
>>         <mailto:council at gnso.icann.org>>
>>         Date: 2017-08-23 17:18 GMT+09:00
>>         Subject: [council] Updated Motion on the CCWG-IG
>>         To: "council at gnso.icann.org <mailto:council at gnso.icann.org>"
>>         <council at gnso.icann.org <mailto:council at gnso.icann.org>>
>>
>>
>>         Hi all,
>>
>>         ?
>>
>>         To prepare for our vote on the CCWG-IG motion this Thursday,
>>         here?s where we stand.
>>
>>         ?
>>
>>         I?d like to thank both Rafik and Wolf-Ulrich for their input
>>         last week.? Rafik and I exchanged emails again this week and
>>         I believe we are in sync.
>>
>>         ?
>>
>>         As the maker of the motion:
>>
>>         ?
>>
>>          1. I accept the proposed change of the withdrawal deadline
>>             from ICANN 60 to ICANN 61.
>>          2. I agree that we need some additional clarity about the
>>             expected timeline leading up to ICANN 61, so the
>>             transition can be as seamless as possible. I suggest we
>>             target a GNSO Council meeting mid-way between ICANN 60
>>             and ICANN 61 as the opportunity for the GNSO Council to
>>             review the proposed replacement structure. I?m also
>>             support acknowledging further that the GNSO Council
>>             expects a replacement to be created by ICANN 61.
>>          3. With the extension, ICANN 61 needs to be the clear date
>>             for withdrawal. If we leave wiggle room in the motion,
>>             then the work of finding a replacement will not have the
>>             urgency or attention it requires. We are extending the
>>             date to allow for the necessary work, but I think that
>>             new date needs to be firm. We have all seen how, at
>>             ICANN, ?work fills the time and space provided.? We need
>>             to avoid further slippage and set clear expectations for
>>             ourselves and for the other Chartering Organizations.
>>
>>         ?
>>
>>         As such, I?ve attached updated motion language that I believe
>>         addresses the points raised to date.
>>
>>         ?
>>
>>         James, as the seconder of the motion, do you concur or have
>>         any concerns?
>>
>>         ?
>>
>>         Regards,
>>
>>         Keith
>>
>>
>>         _______________________________________________
>>         council mailing list
>>         council at gnso.icann.org <mailto:council at gnso.icann.org>
>>         https://mm.icann.org/mailman/listinfo/council
>>         <https://mm.icann.org/mailman/listinfo/council>
>>
>>
>>
>>         <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>         	Virus-free. www.avg.com
>>         <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>
>>
>>         <#m_-7052838523074276160_m_-2938874596675133609_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>>
>>         _______________________________________________
>>         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>
>
>         -- 
>
>
>         Matthew Shears
>         matthew at intpolicy.com <mailto:matthew at intpolicy.com>
>         +447712472987 <tel:+44%207712%20472987>
>         Skype:mshears
>
>         _______________________________________________
>         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>
>
>     -- 
>     Farzaneh
>
>     _______________________________________________
>     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




From icann at ferdeline.com  Sat Aug 26 16:45:27 2017
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Sat, 26 Aug 2017 09:45:27 -0400
Subject: [NCSG-PC] Update on GDPR
In-Reply-To: <CAH5sThkO_Q3pnd7fpjfXZafotmwEFFWxycvX-UdXmV=NZ+9FuA@mail.gmail.com>
References: <CAH5sThnFA4eu4pPRtSLVyHHiG-wEE3dk8QCnp0LumeHuf7_buA@mail.gmail.com>
 <CAH5sTh=9FVWNvvbdEdyRBhXMQar7xFeHKFjdriBYPWMeSzF1HA@mail.gmail.com>
 <CAH5sThmNDiVEM9i5wyhXACEWQy5ZowLW6Ek==cZ5F+ErK+U4+w@mail.gmail.com>
 <CAH5sThkO_Q3pnd7fpjfXZafotmwEFFWxycvX-UdXmV=NZ+9FuA@mail.gmail.com>
Message-ID: <vdnWtIPK2E2FvSn89F8QlHL0_fn84GePv_DtK2TKqXToGUUNPwEsiQ8IPd3i8KZnrHD1Zh5IHxFw6tbDZhF3dSiA77kJM3h57s4HkGOnAZQ=@ferdeline.com>

There is not much to report at this time. We have been asked to provide input on the [dataflow matrix](https://www.icann.org/resources/pages/gtld-registration-dataflow-matrix-2017-07-24-en), but have not done so. I find ALAC's contributions very troubling, and the others - from the likes of the IPC, and Europol - less surprising. The review period for this closed last Thursday, but I suspect if we email something in this weekend it will probably still be added to the matrix. [My suggested input is here](https://docs.google.com/document/d/1Fg2RvjsLobGAKXfTYhQm5YJQRzlIOuhNdZ2cBkFdynQ/edit?usp=sharing); if there is support from the PC I will submit it on behalf of the NCSG, if not, I will submit it in my personal capacity.

Best wishes, Ayden F?rdeline

> -------- Original Message --------
> Subject: Update on GDPR
> Local Time: 18 August 2017 1:33 AM
> UTC Time: 18 August 2017 00:33
> From: rafik.dammak at gmail.com
> To: ncsg-pc <ncsg-pc at lists.ncsg.is>, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca>, Ayden F?rdeline <icann at ferdeline.com>, Wendy Seltzer <wendy at seltzer.org>
>
> Hi Stephanie, Ayden, Wendy,
>
> We will have NCSG Policy Call next Tuesday. Do you have any update you want share from the GDPR taskforce prior or during the call?
>
> Best,
>
> Rafik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170826/a7b9b71d/attachment.htm>

From rafik.dammak at gmail.com  Sat Aug 26 18:09:18 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Sun, 27 Aug 2017 00:09:18 +0900
Subject: [NCSG-PC] Update on GDPR
In-Reply-To: <vdnWtIPK2E2FvSn89F8QlHL0_fn84GePv_DtK2TKqXToGUUNPwEsiQ8IPd3i8KZnrHD1Zh5IHxFw6tbDZhF3dSiA77kJM3h57s4HkGOnAZQ=@ferdeline.com>
References: <CAH5sThnFA4eu4pPRtSLVyHHiG-wEE3dk8QCnp0LumeHuf7_buA@mail.gmail.com>
 <CAH5sTh=9FVWNvvbdEdyRBhXMQar7xFeHKFjdriBYPWMeSzF1HA@mail.gmail.com>
 <CAH5sThmNDiVEM9i5wyhXACEWQy5ZowLW6Ek==cZ5F+ErK+U4+w@mail.gmail.com>
 <CAH5sThkO_Q3pnd7fpjfXZafotmwEFFWxycvX-UdXmV=NZ+9FuA@mail.gmail.com>
 <vdnWtIPK2E2FvSn89F8QlHL0_fn84GePv_DtK2TKqXToGUUNPwEsiQ8IPd3i8KZnrHD1Zh5IHxFw6tbDZhF3dSiA77kJM3h57s4HkGOnAZQ=@ferdeline.com>
Message-ID: <CAH5sThmpnPToh6i64d0Bv4EQ+qqAEACuy62RFao4Yv-q_UJA=g@mail.gmail.com>

Hi Ayden,

thanks for the info. I do think we should submit something. We wanted to
participate in the process.
To be honest, I didn't notice the consultation till it was mentioned by you
and Stephanie in the policy call. I don't recall receiving an official
communication from staff or seeing the proposal under usual public comment
space. Staff is using the blog and new data protection space for
communicating about the issue but it doesn't seem efficient.
so let's review during the weekend and submit the comment if endorsed.

Best,

Rafik


2017-08-26 22:45 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:

> There is not much to report at this time. We have been asked to provide
> input on the dataflow matrix
> <https://www.icann.org/resources/pages/gtld-registration-dataflow-matrix-2017-07-24-en>,
> but have not done so. I find ALAC's contributions very troubling, and the
> others - from the likes of the IPC, and Europol - less surprising. The
> review period for this closed last Thursday, but I suspect if we email
> something in this weekend it will probably still be added to the matrix. My
> suggested input is here
> <https://docs.google.com/document/d/1Fg2RvjsLobGAKXfTYhQm5YJQRzlIOuhNdZ2cBkFdynQ/edit?usp=sharing>;
> if there is support from the PC I will submit it on behalf of the NCSG, if
> not, I will submit it in my personal capacity.
>
> Best wishes, Ayden F?rdeline
>
>
> -------- Original Message --------
> Subject: Update on GDPR
> Local Time: 18 August 2017 1:33 AM
> UTC Time: 18 August 2017 00:33
> From: rafik.dammak at gmail.com
> To: ncsg-pc <ncsg-pc at lists.ncsg.is>, Stephanie Perrin <
> stephanie.perrin at mail.utoronto.ca>, Ayden F?rdeline <icann at ferdeline.com>,
> Wendy Seltzer <wendy at seltzer.org>
>
> Hi Stephanie, Ayden, Wendy,
>
> We will have NCSG Policy Call next Tuesday. Do you have any update you
> want share from the GDPR taskforce prior or during the call?
>
> Best,
>
> Rafik
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170827/0a570ebb/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Sun Aug 27 16:02:50 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Sun, 27 Aug 2017 09:02:50 -0400
Subject: [NCSG-PC] Fwd: [RDS-WHOIS2-RT] Replacement and Removal of Members
In-Reply-To: <3656ed43-074e-4cf8-8795-9b9f0599724c@EXHUB2010-3.campus.MCGILL.CA>
References: <3656ed43-074e-4cf8-8795-9b9f0599724c@EXHUB2010-3.campus.MCGILL.CA>
Message-ID: <6a0a6a2a-0bf4-2ff7-4bfb-9dbbc985f916@mail.utoronto.ca>

This seems important enough to warrant consideration by PC.  What do you 
think?  iS it normal for a REview team to figure out how to remove people?

I dont actually remember anyone asking Alan to figure this out.

cheers SP



-------- Forwarded Message --------
Subject: 	[RDS-WHOIS2-RT] Replacement and Removal of Members
Date: 	Sat, 26 Aug 2017 22:51:59 -0400
From: 	Alan Greenberg <alan.greenberg at mcgill.ca>
To: 	RDS-WHOIS2-RT <rds-whois2-rt at icann.org>



I was asked to propose wording for the section of the Terms of
Reference on Replacement and Removal of Members

I would like to propose the following wording for the consideration of the RT.

Alan

=======

If a Review Team member is no longer able or willing to serve, or if
an SO/AC withdraws its endorsement of the member, the SO/AC making
the original endorsement will be requested to refill the position
with a replacement member. The SO/AC will make the selection
according to their own processes and will not be bound to consider
only those candidates who originally applied requesting their endorsement.

If a Review Team member is sufficiently inactive or disruptive as to
cause at least 50% of Review Team members (excluding the member in
question) to request their removal, the member will be asked to
resign. If the member fails to resign, the SO/AC that endorsed the
member will be requested to withdraw their endorsement and replace
the member. Should the SO/AC not take action, the member can be
removed by a 2/3 majority vote of the remaining Review Team members.
In all cases, the balloting will be carried out in such a way as to
not reveal how individual members voted.

_______________________________________________
RDS-WHOIS2-RT mailing list
RDS-WHOIS2-RT at icann.org
https://mm.icann.org/mailman/listinfo/rds-whois2-rt

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

From icann at ferdeline.com  Sun Aug 27 19:37:03 2017
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Sun, 27 Aug 2017 12:37:03 -0400
Subject: [NCSG-PC] Fwd: [RDS-WHOIS2-RT] Replacement and Removal of
	Members
In-Reply-To: <6a0a6a2a-0bf4-2ff7-4bfb-9dbbc985f916@mail.utoronto.ca>
References: <3656ed43-074e-4cf8-8795-9b9f0599724c@EXHUB2010-3.campus.MCGILL.CA>
 <6a0a6a2a-0bf4-2ff7-4bfb-9dbbc985f916@mail.utoronto.ca>
Message-ID: <EUWrzLhfcLd9E-UO5wktudDyhJfDp3jDzqkzJmLUGhfpYoFSFyqy0a5y3e69qjUTIV8fZwMQtv0Ihypu931HIXZZXdTDSVSIx_0LGp5_7w0=@ferdeline.com>

I would like to know who asked Alan to do this, too.

I'm still wondering why Judith collected the applications for the tribal fellowship programme, too - why was this not done by ICANN staff? Seems members of ALAC are taking on some interesting new responsibilities.

I disagree with the proposed procedure. I think it is one thing for the SO/AC to withdraw their endorsement of their nominee, but QUITE another for Review Team members to band together and demand someone resign simply because they are "disruptive". What an ambiguous term. That to me is wholly inappropriate.

Best wishes, Ayden

> -------- Original Message --------
> Subject: [NCSG-PC] Fwd: [RDS-WHOIS2-RT] Replacement and Removal of Members
> Local Time: 27 August 2017 2:02 PM
> UTC Time: 27 August 2017 13:02
> From: stephanie.perrin at mail.utoronto.ca
> To: ncsg-pc <ncsg-pc at lists.ncsg.is>
>
> This seems important enough to warrant consideration by PC.  What do you think?  iS it normal for a REview team to figure out how to remove people?
>
> I dont actually remember anyone asking Alan to figure this out.
>
> cheers SP
>
> -------- Forwarded Message --------
> Subject:	[RDS-WHOIS2-RT] Replacement and Removal of Members
> Date:	Sat, 26 Aug 2017 22:51:59 -0400
> From:	Alan Greenberg [<alan.greenberg at mcgill.ca>](mailto:alan.greenberg at mcgill.ca)
>
> To:	RDS-WHOIS2-RT [<rds-whois2-rt at icann.org>](mailto:rds-whois2-rt at icann.org)
>
> I was asked to propose wording for the section of the Terms of
> Reference on Replacement and Removal of Members
>
> I would like to propose the following wording for the consideration of the RT.
>
> Alan
>
> =======
>
> If a Review Team member is no longer able or willing to serve, or if
> an SO/AC withdraws its endorsement of the member, the SO/AC making
> the original endorsement will be requested to refill the position
> with a replacement member. The SO/AC will make the selection
> according to their own processes and will not be bound to consider
> only those candidates who originally applied requesting their endorsement.
>
> If a Review Team member is sufficiently inactive or disruptive as to
> cause at least 50% of Review Team members (excluding the member in
> question) to request their removal, the member will be asked to
> resign. If the member fails to resign, the SO/AC that endorsed the
> member will be requested to withdraw their endorsement and replace
> the member. Should the SO/AC not take action, the member can be
> removed by a 2/3 majority vote of the remaining Review Team members.
> In all cases, the balloting will be carried out in such a way as to
> not reveal how individual members voted.
>
> _______________________________________________
> RDS-WHOIS2-RT mailing list
> RDS-WHOIS2-RT at icann.org
>
> https://mm.icann.org/mailman/listinfo/rds-whois2-rt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170827/176d0e91/attachment.htm>

From rafik.dammak at gmail.com  Mon Aug 28 02:23:56 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Mon, 28 Aug 2017 08:23:56 +0900
Subject: [NCSG-PC] Fwd: [RDS-WHOIS2-RT] Replacement and Removal of
	Members
In-Reply-To: <6a0a6a2a-0bf4-2ff7-4bfb-9dbbc985f916@mail.utoronto.ca>
References: <3656ed43-074e-4cf8-8795-9b9f0599724c@EXHUB2010-3.campus.MCGILL.CA>
 <6a0a6a2a-0bf4-2ff7-4bfb-9dbbc985f916@mail.utoronto.ca>
Message-ID: <CAH5sThk8AGGKqaJgGb2u6S3y+P3jGwUWt_xzO5R+qYA33gpDXQ@mail.gmail.com>

Hi Stephanie,


thanks for this,
if I understand correctly, each review team set its own terms of reference
and/or operating rules and has enough freedom to set them up.  I guess that
may vary between one review team or another. There may be a provision in
groups on how (co-)chairs deal with some cases for members/participants but
I don't recall provision for removing.  We can check with Avri, David,
Kathy as there were members in different review teams if there was any
similar provision in their respective review teams.

Best,

Rafik

2017-08-27 22:02 GMT+09:00 Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca>:

> This seems important enough to warrant consideration by PC.  What do you
> think?  iS it normal for a REview team to figure out how to remove people?
>
> I dont actually remember anyone asking Alan to figure this out.
>
> cheers SP
>
>
> -------- Forwarded Message --------
> Subject: [RDS-WHOIS2-RT] Replacement and Removal of Members
> Date: Sat, 26 Aug 2017 22:51:59 -0400
> From: Alan Greenberg <alan.greenberg at mcgill.ca> <alan.greenberg at mcgill.ca>
> To: RDS-WHOIS2-RT <rds-whois2-rt at icann.org> <rds-whois2-rt at icann.org>
>
> I was asked to propose wording for the section of the Terms of
> Reference on Replacement and Removal of Members
>
> I would like to propose the following wording for the consideration of the RT.
>
> Alan
>
> =======
>
> If a Review Team member is no longer able or willing to serve, or if
> an SO/AC withdraws its endorsement of the member, the SO/AC making
> the original endorsement will be requested to refill the position
> with a replacement member. The SO/AC will make the selection
> according to their own processes and will not be bound to consider
> only those candidates who originally applied requesting their endorsement.
>
> If a Review Team member is sufficiently inactive or disruptive as to
> cause at least 50% of Review Team members (excluding the member in
> question) to request their removal, the member will be asked to
> resign. If the member fails to resign, the SO/AC that endorsed the
> member will be requested to withdraw their endorsement and replace
> the member. Should the SO/AC not take action, the member can be
> removed by a 2/3 majority vote of the remaining Review Team members.
> In all cases, the balloting will be carried out in such a way as to
> not reveal how individual members voted.
>
> _______________________________________________
> RDS-WHOIS2-RT mailing listRDS-WHOIS2-RT at icann.orghttps://mm.icann.org/mailman/listinfo/rds-whois2-rt
>
>
> _______________________________________________
> 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/20170828/7157b12c/attachment.htm>

From icann at ferdeline.com  Mon Aug 28 13:52:33 2017
From: icann at ferdeline.com (=?UTF-8?Q?Ayden_F=C3=A9rdeline?=)
Date: Mon, 28 Aug 2017 06:52:33 -0400
Subject: [NCSG-PC] Update on GDPR
In-Reply-To: <CAH5sThmpnPToh6i64d0Bv4EQ+qqAEACuy62RFao4Yv-q_UJA=g@mail.gmail.com>
References: <CAH5sThnFA4eu4pPRtSLVyHHiG-wEE3dk8QCnp0LumeHuf7_buA@mail.gmail.com>
 <CAH5sTh=9FVWNvvbdEdyRBhXMQar7xFeHKFjdriBYPWMeSzF1HA@mail.gmail.com>
 <CAH5sThmNDiVEM9i5wyhXACEWQy5ZowLW6Ek==cZ5F+ErK+U4+w@mail.gmail.com>
 <CAH5sThkO_Q3pnd7fpjfXZafotmwEFFWxycvX-UdXmV=NZ+9FuA@mail.gmail.com>
 <vdnWtIPK2E2FvSn89F8QlHL0_fn84GePv_DtK2TKqXToGUUNPwEsiQ8IPd3i8KZnrHD1Zh5IHxFw6tbDZhF3dSiA77kJM3h57s4HkGOnAZQ=@ferdeline.com>
 <CAH5sThmpnPToh6i64d0Bv4EQ+qqAEACuy62RFao4Yv-q_UJA=g@mail.gmail.com>
Message-ID: <4Z0rdKJm5v5ky7P66oSe6uh9Y4qzLhPZxwXssk5EAztSIZdocHv2trHhBNVo07BuG31pXGjr_hRP0UY9G76Yvf50sGCJ_9819kH-0DtHnTw=@ferdeline.com>

I am submitting this now in my personal capacity.

Best, Ayden

> -------- Original Message --------
> Subject: Re: Update on GDPR
> Local Time: 26 August 2017 4:09 PM
> UTC Time: 26 August 2017 15:09
> From: rafik.dammak at gmail.com
> To: Ayden F?rdeline <icann at ferdeline.com>
> ncsg-pc <ncsg-pc at lists.ncsg.is>, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca>, Wendy Seltzer <wendy at seltzer.org>
>
> Hi Ayden,
>
> thanks for the info. I do think we should submit something. We wanted to participate in the process.
> To be honest, I didn't notice the consultation till it was mentioned by you and Stephanie in the policy call. I don't recall receiving an official communication from staff or seeing the proposal under usual public comment space. Staff is using the blog and new data protection space for communicating about the issue but it doesn't seem efficient.
> so let's review during the weekend and submit the comment if endorsed.
>
> Best,
>
> Rafik
>
> 2017-08-26 22:45 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>
>> There is not much to report at this time. We have been asked to provide input on the [dataflow matrix](https://www.icann.org/resources/pages/gtld-registration-dataflow-matrix-2017-07-24-en), but have not done so. I find ALAC's contributions very troubling, and the others - from the likes of the IPC, and Europol - less surprising. The review period for this closed last Thursday, but I suspect if we email something in this weekend it will probably still be added to the matrix. [My suggested input is here](https://docs.google.com/document/d/1Fg2RvjsLobGAKXfTYhQm5YJQRzlIOuhNdZ2cBkFdynQ/edit?usp=sharing); if there is support from the PC I will submit it on behalf of the NCSG, if not, I will submit it in my personal capacity.
>>
>> Best wishes, Ayden F?rdeline
>>
>>> -------- Original Message --------
>>> Subject: Update on GDPR
>>> Local Time: 18 August 2017 1:33 AM
>>> UTC Time: 18 August 2017 00:33
>>> From: rafik.dammak at gmail.com
>>> To: ncsg-pc <ncsg-pc at lists.ncsg.is>, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca>, Ayden F?rdeline <icann at ferdeline.com>, Wendy Seltzer <wendy at seltzer.org>
>>>
>>> Hi Stephanie, Ayden, Wendy,
>>>
>>> We will have NCSG Policy Call next Tuesday. Do you have any update you want share from the GDPR taskforce prior or during the call?
>>>
>>> Best,
>>>
>>> Rafik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170828/39b314af/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Mon Aug 28 18:18:22 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Mon, 28 Aug 2017 11:18:22 -0400
Subject: [NCSG-PC] Fwd: Re: [RDS-WHOIS2-RT] Replacement and Removal of
	Members
In-Reply-To: <09016100-0de3-55f4-4363-8d86c6d11c35@mail.utoronto.ca>
References: <09016100-0de3-55f4-4363-8d86c6d11c35@mail.utoronto.ca>
Message-ID: <2819e84b-8560-317a-c257-03cf741166fd@mail.utoronto.ca>

I just sent the following to the list, got a fist bump from volker who 
must have been telepathically connected since he was sending a longer 
version expressing reservations.  I understand James' point about 
needing procedures for removing disruptive members, but this needs to be 
seriously circumscribed, in my experience. They would have loved to 
remove me from the EWG.

cheers Steph



-------- Forwarded Message --------
Subject: 	Re: [RDS-WHOIS2-RT] Replacement and Removal of Members
Date: 	Mon, 28 Aug 2017 11:00:22 -0400
From: 	Stephanie Perrin <stephanie.perrin at mail.utoronto.ca>
To: 	rds-whois2-rt at icann.org



I do think that we should define "disruptive".  I have been a minority 
viewpoint on many committees here now, largely because I remind people 
of how data protection law is drafted, implemented and further defined 
in policy.  Given the contentious nature of the WHOIS debates, that has 
been a very lonely position, but since I appear to have been the only 
person with any actual experience in these matters on several of those 
committees, I am quite unrepentant. ICANN has a long history of ignoring 
the privacy perspective.  It would not be hard to find 50% of people who 
would like to get rid of me, just to speed things up and not be bothered 
with the facts/alternate view.  I think if we don't define "disruptive", 
we at least need to make it a larger majority of members, so I support 
Erika's suggestion of 70%.

Stephanie Perrin


On 2017-08-27 19:43, SUN Lili wrote:
> Dear Alan,
> Thanks for sharing the proposed text.
> I'm fine with the first paragraph. For the second paragraph, I believe the disputing part will be how to define "disruptive", a 50% team member's request for removal will be persuasive. I was just wondering the meaning that "the member fails to resign", would it be better to change it to "the member refuses to resign"?
> For your and other team member's consideration.
> Thanks and regards,
> Lili
>
> -----Original Message-----
> From:rds-whois2-rt-bounces at icann.org  [mailto:rds-whois2-rt-bounces at icann.org] On Behalf Of Alan Greenberg
> Sent: Sunday, 27 August, 2017 10:52 AM
> To: RDS-WHOIS2-RT<rds-whois2-rt at icann.org>
> Subject: [RDS-WHOIS2-RT] Replacement and Removal of Members
>
> I was asked to propose wording for the section of the Terms of Reference on Replacement and Removal of Members
>
> I would like to propose the following wording for the consideration of the RT.
>
> Alan
>
> =======
>
> If a Review Team member is no longer able or willing to serve, or if an SO/AC withdraws its endorsement of the member, the SO/AC making the original endorsement will be requested to refill the position with a replacement member. The SO/AC will make the selection according to their own processes and will not be bound to consider only those candidates who originally applied requesting their endorsement.
>
> If a Review Team member is sufficiently inactive or disruptive as to cause at least 50% of Review Team members (excluding the member in
> question) to request their removal, the member will be asked to resign. If the member fails to resign, the SO/AC that endorsed the member will be requested to withdraw their endorsement and replace the member. Should the SO/AC not take action, the member can be removed by a 2/3 majority vote of the remaining Review Team members.
> In all cases, the balloting will be carried out in such a way as to not reveal how individual members voted.
>
> _______________________________________________
> RDS-WHOIS2-RT mailing list
> RDS-WHOIS2-RT at icann.org
> https://mm.icann.org/mailman/listinfo/rds-whois2-rt
>
> ***************************************************************************************************
> This message, and any attachment contained, are confidential and subject of legal privilege. It may be used solely for the designated police/justice purpose and by the individual or entity to whom it is addressed. The information is not to be disseminated to another agency or third party without the author?s consent, and must not be retained longer than is necessary for the fulfilment of the purpose for which the information is to be used. All practicable steps shall be taken by the recipients to ensure that information is protected against unauthorised access or processing. INTERPOL reserves the right to enquire about the use of the information provided.
> If you are not the intended recipient, be advised that you have received this message in error. In such a case, you should not print it, copy it, make any use of it or disclose it, but please notify us immediately and delete the message from any computer.
> *************************************************************************************************
> _______________________________________________
> RDS-WHOIS2-RT mailing list
> RDS-WHOIS2-RT at icann.org
> https://mm.icann.org/mailman/listinfo/rds-whois2-rt

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

From rafik.dammak at gmail.com  Tue Aug 29 02:20:48 2017
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 29 Aug 2017 08:20:48 +0900
Subject: [NCSG-PC] Update on GDPR
In-Reply-To: <4Z0rdKJm5v5ky7P66oSe6uh9Y4qzLhPZxwXssk5EAztSIZdocHv2trHhBNVo07BuG31pXGjr_hRP0UY9G76Yvf50sGCJ_9819kH-0DtHnTw=@ferdeline.com>
References: <CAH5sThnFA4eu4pPRtSLVyHHiG-wEE3dk8QCnp0LumeHuf7_buA@mail.gmail.com>
 <CAH5sTh=9FVWNvvbdEdyRBhXMQar7xFeHKFjdriBYPWMeSzF1HA@mail.gmail.com>
 <CAH5sThmNDiVEM9i5wyhXACEWQy5ZowLW6Ek==cZ5F+ErK+U4+w@mail.gmail.com>
 <CAH5sThkO_Q3pnd7fpjfXZafotmwEFFWxycvX-UdXmV=NZ+9FuA@mail.gmail.com>
 <vdnWtIPK2E2FvSn89F8QlHL0_fn84GePv_DtK2TKqXToGUUNPwEsiQ8IPd3i8KZnrHD1Zh5IHxFw6tbDZhF3dSiA77kJM3h57s4HkGOnAZQ=@ferdeline.com>
 <CAH5sThmpnPToh6i64d0Bv4EQ+qqAEACuy62RFao4Yv-q_UJA=g@mail.gmail.com>
 <4Z0rdKJm5v5ky7P66oSe6uh9Y4qzLhPZxwXssk5EAztSIZdocHv2trHhBNVo07BuG31pXGjr_hRP0UY9G76Yvf50sGCJ_9819kH-0DtHnTw=@ferdeline.com>
Message-ID: <CAH5sThn0DJ36NLNLq4-Wib+_RGeXSSWtVzWsavD=c0eUWAzqHA@mail.gmail.com>

Thanks Ayden,
we can try to agree on endorsing your comment.
@All please indicate if you want to endorse or not the comment.

Best,

Rafik

2017-08-28 19:52 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:

> I am submitting this now in my personal capacity.
>
> Best, Ayden
>
>
> -------- Original Message --------
> Subject: Re: Update on GDPR
> Local Time: 26 August 2017 4:09 PM
> UTC Time: 26 August 2017 15:09
> From: rafik.dammak at gmail.com
> To: Ayden F?rdeline <icann at ferdeline.com>
> ncsg-pc <ncsg-pc at lists.ncsg.is>, Stephanie Perrin <stephanie.perrin at mail.
> utoronto.ca>, Wendy Seltzer <wendy at seltzer.org>
>
> Hi Ayden,
>
> thanks for the info. I do think we should submit something. We wanted to
> participate in the process.
> To be honest, I didn't notice the consultation till it was mentioned by
> you and Stephanie in the policy call. I don't recall receiving an official
> communication from staff or seeing the proposal under usual public comment
> space. Staff is using the blog and new data protection space for
> communicating about the issue but it doesn't seem efficient.
> so let's review during the weekend and submit the comment if endorsed.
>
> Best,
>
> Rafik
>
>
> 2017-08-26 22:45 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>
>> There is not much to report at this time. We have been asked to provide
>> input on the dataflow matrix
>> <https://www.icann.org/resources/pages/gtld-registration-dataflow-matrix-2017-07-24-en>,
>> but have not done so. I find ALAC's contributions very troubling, and the
>> others - from the likes of the IPC, and Europol - less surprising. The
>> review period for this closed last Thursday, but I suspect if we email
>> something in this weekend it will probably still be added to the matrix. My
>> suggested input is here
>> <https://docs.google.com/document/d/1Fg2RvjsLobGAKXfTYhQm5YJQRzlIOuhNdZ2cBkFdynQ/edit?usp=sharing>;
>> if there is support from the PC I will submit it on behalf of the NCSG, if
>> not, I will submit it in my personal capacity.
>>
>> Best wishes, Ayden F?rdeline
>>
>>
>> -------- Original Message --------
>> Subject: Update on GDPR
>> Local Time: 18 August 2017 1:33 AM
>> UTC Time: 18 August 2017 00:33
>> From: rafik.dammak at gmail.com
>> To: ncsg-pc <ncsg-pc at lists.ncsg.is>, Stephanie Perrin <
>> stephanie.perrin at mail.utoronto.ca>, Ayden F?rdeline <icann at ferdeline.com>,
>> Wendy Seltzer <wendy at seltzer.org>
>>
>> Hi Stephanie, Ayden, Wendy,
>>
>> We will have NCSG Policy Call next Tuesday. Do you have any update you
>> want share from the GDPR taskforce prior or during the call?
>>
>> Best,
>>
>> Rafik
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170829/467b8384/attachment.htm>

From farzaneh.badii at gmail.com  Tue Aug 29 04:47:35 2017
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Mon, 28 Aug 2017 21:47:35 -0400
Subject: [NCSG-PC] Update on GDPR
In-Reply-To: <CAH5sThn0DJ36NLNLq4-Wib+_RGeXSSWtVzWsavD=c0eUWAzqHA@mail.gmail.com>
References: <CAH5sThnFA4eu4pPRtSLVyHHiG-wEE3dk8QCnp0LumeHuf7_buA@mail.gmail.com>
 <CAH5sTh=9FVWNvvbdEdyRBhXMQar7xFeHKFjdriBYPWMeSzF1HA@mail.gmail.com>
 <CAH5sThmNDiVEM9i5wyhXACEWQy5ZowLW6Ek==cZ5F+ErK+U4+w@mail.gmail.com>
 <CAH5sThkO_Q3pnd7fpjfXZafotmwEFFWxycvX-UdXmV=NZ+9FuA@mail.gmail.com>
 <vdnWtIPK2E2FvSn89F8QlHL0_fn84GePv_DtK2TKqXToGUUNPwEsiQ8IPd3i8KZnrHD1Zh5IHxFw6tbDZhF3dSiA77kJM3h57s4HkGOnAZQ=@ferdeline.com>
 <CAH5sThmpnPToh6i64d0Bv4EQ+qqAEACuy62RFao4Yv-q_UJA=g@mail.gmail.com>
 <4Z0rdKJm5v5ky7P66oSe6uh9Y4qzLhPZxwXssk5EAztSIZdocHv2trHhBNVo07BuG31pXGjr_hRP0UY9G76Yvf50sGCJ_9819kH-0DtHnTw=@ferdeline.com>
 <CAH5sThn0DJ36NLNLq4-Wib+_RGeXSSWtVzWsavD=c0eUWAzqHA@mail.gmail.com>
Message-ID: <CAN1qJvAGCcZoTVm6jOwsj4Mk_D3OyrTqf7E67PA4AYvhjAD-CQ@mail.gmail.com>

Observer here: why is there no action from PC members? Please pay attention
to this some of you are avid privacy advocates outside of ICANN. We need to
action on this! It's just a matter of reading endorsing or not endorsing
what Ayden has, you don't have to do much.

Farzaneh

On Mon, Aug 28, 2017 at 7:20 PM, Rafik Dammak <rafik.dammak at gmail.com>
wrote:

> Thanks Ayden,
> we can try to agree on endorsing your comment.
> @All please indicate if you want to endorse or not the comment.
>
> Best,
>
> Rafik
>
>
> 2017-08-28 19:52 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>
>> I am submitting this now in my personal capacity.
>>
>> Best, Ayden
>>
>>
>> -------- Original Message --------
>> Subject: Re: Update on GDPR
>> Local Time: 26 August 2017 4:09 PM
>> UTC Time: 26 August 2017 15:09
>> From: rafik.dammak at gmail.com
>> To: Ayden F?rdeline <icann at ferdeline.com>
>> ncsg-pc <ncsg-pc at lists.ncsg.is>, Stephanie Perrin <
>> stephanie.perrin at mail.utoronto.ca>, Wendy Seltzer <wendy at seltzer.org>
>>
>> Hi Ayden,
>>
>> thanks for the info. I do think we should submit something. We wanted to
>> participate in the process.
>> To be honest, I didn't notice the consultation till it was mentioned by
>> you and Stephanie in the policy call. I don't recall receiving an official
>> communication from staff or seeing the proposal under usual public comment
>> space. Staff is using the blog and new data protection space for
>> communicating about the issue but it doesn't seem efficient.
>> so let's review during the weekend and submit the comment if endorsed.
>>
>> Best,
>>
>> Rafik
>>
>>
>> 2017-08-26 22:45 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com>:
>>
>>> There is not much to report at this time. We have been asked to provide
>>> input on the dataflow matrix
>>> <https://www.icann.org/resources/pages/gtld-registration-dataflow-matrix-2017-07-24-en>,
>>> but have not done so. I find ALAC's contributions very troubling, and the
>>> others - from the likes of the IPC, and Europol - less surprising. The
>>> review period for this closed last Thursday, but I suspect if we email
>>> something in this weekend it will probably still be added to the matrix. My
>>> suggested input is here
>>> <https://docs.google.com/document/d/1Fg2RvjsLobGAKXfTYhQm5YJQRzlIOuhNdZ2cBkFdynQ/edit?usp=sharing>;
>>> if there is support from the PC I will submit it on behalf of the NCSG, if
>>> not, I will submit it in my personal capacity.
>>>
>>> Best wishes, Ayden F?rdeline
>>>
>>>
>>> -------- Original Message --------
>>> Subject: Update on GDPR
>>> Local Time: 18 August 2017 1:33 AM
>>> UTC Time: 18 August 2017 00:33
>>> From: rafik.dammak at gmail.com
>>> To: ncsg-pc <ncsg-pc at lists.ncsg.is>, Stephanie Perrin <
>>> stephanie.perrin at mail.utoronto.ca>, Ayden F?rdeline <icann at ferdeline.com>,
>>> Wendy Seltzer <wendy at seltzer.org>
>>>
>>> Hi Stephanie, Ayden, Wendy,
>>>
>>> We will have NCSG Policy Call next Tuesday. Do you have any update you
>>> want share from the GDPR taskforce prior or during the call?
>>>
>>> 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/20170828/a96dd33f/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Tue Aug 29 06:18:54 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Mon, 28 Aug 2017 23:18:54 -0400
Subject: [NCSG-PC] Update on GDPR
In-Reply-To: <CAN1qJvAGCcZoTVm6jOwsj4Mk_D3OyrTqf7E67PA4AYvhjAD-CQ@mail.gmail.com>
References: <CAH5sThnFA4eu4pPRtSLVyHHiG-wEE3dk8QCnp0LumeHuf7_buA@mail.gmail.com>
 <CAH5sTh=9FVWNvvbdEdyRBhXMQar7xFeHKFjdriBYPWMeSzF1HA@mail.gmail.com>
 <CAH5sThmNDiVEM9i5wyhXACEWQy5ZowLW6Ek==cZ5F+ErK+U4+w@mail.gmail.com>
 <CAH5sThkO_Q3pnd7fpjfXZafotmwEFFWxycvX-UdXmV=NZ+9FuA@mail.gmail.com>
 <vdnWtIPK2E2FvSn89F8QlHL0_fn84GePv_DtK2TKqXToGUUNPwEsiQ8IPd3i8KZnrHD1Zh5IHxFw6tbDZhF3dSiA77kJM3h57s4HkGOnAZQ=@ferdeline.com>
 <CAH5sThmpnPToh6i64d0Bv4EQ+qqAEACuy62RFao4Yv-q_UJA=g@mail.gmail.com>
 <4Z0rdKJm5v5ky7P66oSe6uh9Y4qzLhPZxwXssk5EAztSIZdocHv2trHhBNVo07BuG31pXGjr_hRP0UY9G76Yvf50sGCJ_9819kH-0DtHnTw=@ferdeline.com>
 <CAH5sThn0DJ36NLNLq4-Wib+_RGeXSSWtVzWsavD=c0eUWAzqHA@mail.gmail.com>
 <CAN1qJvAGCcZoTVm6jOwsj4Mk_D3OyrTqf7E67PA4AYvhjAD-CQ@mail.gmail.com>
Message-ID: <a9b8ffe4-0a90-6ec0-bc0d-730bce9ba54c@mail.utoronto.ca>

I am sorry, I am swamped with School work.  However, I have read Ayden's 
comment.  My own view is that while I like this approach, we need 
balance.  This user type is "miscreant" .  We need to have some balance 
to this, such as by providing a "consumer" profile.I have not thought 
that one through, it is mostly a bogus claim that a consumer checks 
whois to see if a person is operating a legit site.  Let us imagine a 
few examples:  a web site for cancer survivors, household repair tips, 
spiritual guidance tips, counselling for rape victims, etc.  In those 
instances, if there is no personal infomration provided, how would a 
consumer construe that?  WOuld they trust the website?  Frankly, I would 
never go to WHOIS to determine whether to trust a website, but others 
do,  We need to come up with a postion on this one....IMHO

cheers Steph


On 2017-08-28 9:47 PM, farzaneh badii wrote:
> Observer here: why is there no action from PC members? Please pay 
> attention to this some of you are avid privacy advocates outside of 
> ICANN. We need to action on this! It's just a matter of reading 
> endorsing or not endorsing what Ayden has, you don't have to do much.
>
> Farzaneh
>
> On Mon, Aug 28, 2017 at 7:20 PM, Rafik Dammak <rafik.dammak at gmail.com 
> <mailto:rafik.dammak at gmail.com>> wrote:
>
>     Thanks Ayden,
>     we can try to agree on endorsing your comment.
>     @All please indicate if you want to endorse or not the comment.
>
>     Best,
>
>     Rafik
>
>
>     2017-08-28 19:52 GMT+09:00 Ayden F?rdeline <icann at ferdeline.com
>     <mailto:icann at ferdeline.com>>:
>
>         I am submitting this now in my personal capacity.
>
>         Best, Ayden
>
>
>>         -------- Original Message --------
>>         Subject: Re: Update on GDPR
>>         Local Time: 26 August 2017 4:09 PM
>>         UTC Time: 26 August 2017 15:09
>>         From: rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>
>>         To: Ayden F?rdeline <icann at ferdeline.com
>>         <mailto:icann at ferdeline.com>>
>>         ncsg-pc <ncsg-pc at lists.ncsg.is
>>         <mailto:ncsg-pc at lists.ncsg.is>>, Stephanie Perrin
>>         <stephanie.perrin at mail.utoronto.ca
>>         <mailto:stephanie.perrin at mail.utoronto.ca>>, Wendy Seltzer
>>         <wendy at seltzer.org <mailto:wendy at seltzer.org>>
>>
>>         Hi Ayden,
>>
>>         thanks for the info. I do think we should submit something.
>>         We wanted to participate in the process.
>>         To be honest, I didn't notice the consultation till it was
>>         mentioned by you and Stephanie in the policy call. I don't
>>         recall receiving an official communication from staff or
>>         seeing the proposal under usual public comment space. Staff
>>         is using the blog and new data protection space for
>>         communicating about the issue but it doesn't seem efficient.
>>         so let's review during the weekend and submit the comment if
>>         endorsed.
>>
>>         Best,
>>
>>         Rafik
>>
>>
>>         2017-08-26 22:45 GMT+09:00 Ayden F?rdeline
>>         <icann at ferdeline.com <mailto:icann at ferdeline.com>>:
>>
>>             There is not much to report at this time. We have been
>>             asked to provide input on the dataflow matrix
>>             <https://www.icann.org/resources/pages/gtld-registration-dataflow-matrix-2017-07-24-en>,
>>             but have not done so. I find ALAC's contributions very
>>             troubling, and the others - from the likes of the IPC,
>>             and Europol - less surprising. The review period for this
>>             closed last Thursday, but I suspect if we email something
>>             in this weekend it will probably still be added to the
>>             matrix. My suggested input is here
>>             <https://docs.google.com/document/d/1Fg2RvjsLobGAKXfTYhQm5YJQRzlIOuhNdZ2cBkFdynQ/edit?usp=sharing>;
>>             if there is support from the PC I will submit it on
>>             behalf of the NCSG, if not, I will submit it in my
>>             personal capacity.
>>
>>             Best wishes, Ayden F?rdeline
>>
>>
>>>             -------- Original Message --------
>>>             Subject: Update on GDPR
>>>             Local Time: 18 August 2017 1:33 AM
>>>             UTC Time: 18 August 2017 00:33
>>>             From: rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>
>>>             To: ncsg-pc <ncsg-pc at lists.ncsg.is
>>>             <mailto:ncsg-pc at lists.ncsg.is>>, Stephanie Perrin
>>>             <stephanie.perrin at mail.utoronto.ca
>>>             <mailto:stephanie.perrin at mail.utoronto.ca>>, Ayden
>>>             F?rdeline <icann at ferdeline.com
>>>             <mailto:icann at ferdeline.com>>, Wendy Seltzer
>>>             <wendy at seltzer.org <mailto:wendy at seltzer.org>>
>>>
>>>             Hi Stephanie, Ayden, Wendy,
>>>
>>>             We will have NCSG Policy Call next Tuesday. Do you have
>>>             any update you want share from the GDPR taskforce prior
>>>             or during the call?
>>>
>>>             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
>     <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/20170828/2413b078/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Tue Aug 29 20:46:10 2017
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Tue, 29 Aug 2017 13:46:10 -0400
Subject: [NCSG-PC] Fwd: [RDS-WHOIS2-RT] Formation of the RDS-WHOIS2 Board
	Caucus Group
In-Reply-To: <6C5F9787-3121-4237-9008-F776E11DB341@disspain.uk>
References: <6C5F9787-3121-4237-9008-F776E11DB341@disspain.uk>
Message-ID: <30033d3b-15b4-0e62-b36e-287774b590be@mail.utoronto.ca>


FYI

-------- Forwarded Message --------
Subject: 	[RDS-WHOIS2-RT] Formation of the RDS-WHOIS2 Board Caucus Group
Date: 	Tue, 29 Aug 2017 17:40:43 +0100
From: 	Chris Disspain <chris at disspain.uk>
To: 	RDS WHOIS2-RT List <rds-whois2-rt at icann.org>



Greetings All,

In line with best practice experience from the Transition-related work, 
the Board is using Caucus Groups as a mechanism for the Board to provide 
input to Specific Review Teams on the scope of work, feasibility of 
recommendations and other key matters.  These Caucus Groups are small 
groups of Board members with expertise and interest in the particular 
Review-related topics. The goal is to create an interactive environment 
where the Board can engage with the Review Teams to offer input and 
observations for Review Teams? consideration on a timely basis, via the 
Board Caucus Group.
The Board Caucus Group for the RDS-WHOIS2 Review has been formed, and 
currently consists of Rinalia Abdul Rahim, Cherine Chalaby, Steve 
Crocker, Markus Kummer, Akinori Maemura, Kaveh Ranjbar and me.
It is important to highlight that the formation of the Caucus Groups is 
the Board?s internal method of conducting their work. All of the final 
results are seen and reviewed by the full Board so any response or 
feedback provided to the Review Team by the Caucus Group is on behalf of 
the full Board.

I hope this information is helpful and will be happy to answer any 
questions you may have.


Cheers,


Chris


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170829/37d5eaa0/attachment.htm>
-------------- next part --------------
_______________________________________________
RDS-WHOIS2-RT mailing list
RDS-WHOIS2-RT at icann.org
https://mm.icann.org/mailman/listinfo/rds-whois2-rt


From matthew at intpolicy.com  Tue Aug 29 20:59:25 2017
From: matthew at intpolicy.com (matthew shears)
Date: Tue, 29 Aug 2017 17:59:25 +0000
Subject: [NCSG-PC] Fwd: Re: [RDS-WHOIS2-RT] Replacement and Removal
	of	Members
In-Reply-To: <2819e84b-8560-317a-c257-03cf741166fd@mail.utoronto.ca>
References: <09016100-0de3-55f4-4363-8d86c6d11c35@mail.utoronto.ca>,
 <2819e84b-8560-317a-c257-03cf741166fd@mail.utoronto.ca>
Message-ID: <LOXP123MB0055589F3DBF97B03ED18F45B09F0@LOXP123MB0055.GBRP123.PROD.OUTLOOK.COM>

Totally agree with your note stephanie

Sent from my Windows 10 phone

From: Stephanie Perrin<mailto:stephanie.perrin at mail.utoronto.ca>
Sent: 28 August 2017 16:18
To: ncsg-pc<mailto:ncsg-pc at lists.ncsg.is>
Subject: [NCSG-PC] Fwd: Re: [RDS-WHOIS2-RT] Replacement and Removal of Members


I just sent the following to the list, got a fist bump from volker who must have been telepathically connected since he was sending a longer version expressing reservations.  I understand James' point about needing procedures for removing disruptive members, but this needs to be seriously circumscribed, in my experience.  They would have loved to remove me from the EWG.

cheers Steph


-------- Forwarded Message --------
Subject:        Re: [RDS-WHOIS2-RT] Replacement and Removal of Members
Date:   Mon, 28 Aug 2017 11:00:22 -0400
From:   Stephanie Perrin <stephanie.perrin at mail.utoronto.ca><mailto:stephanie.perrin at mail.utoronto.ca>
To:     rds-whois2-rt at icann.org<mailto:rds-whois2-rt at icann.org>



I do think that we should define "disruptive".  I have been a minority viewpoint on many committees here now, largely because I remind people of how data protection law is drafted, implemented and further defined in policy.  Given the contentious nature of the WHOIS debates, that has been a very lonely position, but since I appear to have been the only person with any actual experience in these matters on several of those committees, I am quite unrepentant. ICANN has a long history of ignoring the privacy perspective.  It would not be hard to find 50% of people who would like to get rid of me, just to speed things up and not be bothered with the facts/alternate view.  I think if we don't define "disruptive", we at least need to make it a larger majority of members, so I support Erika's suggestion of 70%.

Stephanie Perrin

On 2017-08-27 19:43, SUN Lili wrote:

Dear Alan,
Thanks for sharing the proposed text.
I'm fine with the first paragraph. For the second paragraph, I believe the disputing part will be how to define "disruptive", a 50% team member's request for removal will be persuasive. I was just wondering the meaning that "the member fails to resign", would it be better to change it to "the member refuses to resign"?
For your and other team member's consideration.
Thanks and regards,
Lili

-----Original Message-----
From: rds-whois2-rt-bounces at icann.org<mailto:rds-whois2-rt-bounces at icann.org> [mailto:rds-whois2-rt-bounces at icann.org] On Behalf Of Alan Greenberg
Sent: Sunday, 27 August, 2017 10:52 AM
To: RDS-WHOIS2-RT <rds-whois2-rt at icann.org><mailto:rds-whois2-rt at icann.org>
Subject: [RDS-WHOIS2-RT] Replacement and Removal of Members

I was asked to propose wording for the section of the Terms of Reference on Replacement and Removal of Members

I would like to propose the following wording for the consideration of the RT.

Alan

=======

If a Review Team member is no longer able or willing to serve, or if an SO/AC withdraws its endorsement of the member, the SO/AC making the original endorsement will be requested to refill the position with a replacement member. The SO/AC will make the selection according to their own processes and will not be bound to consider only those candidates who originally applied requesting their endorsement.

If a Review Team member is sufficiently inactive or disruptive as to cause at least 50% of Review Team members (excluding the member in
question) to request their removal, the member will be asked to resign. If the member fails to resign, the SO/AC that endorsed the member will be requested to withdraw their endorsement and replace the member. Should the SO/AC not take action, the member can be removed by a 2/3 majority vote of the remaining Review Team members.
In all cases, the balloting will be carried out in such a way as to not reveal how individual members voted.

_______________________________________________
RDS-WHOIS2-RT mailing list
RDS-WHOIS2-RT at icann.org<mailto:RDS-WHOIS2-RT at icann.org>
https://mm.icann.org/mailman/listinfo/rds-whois2-rt

***************************************************************************************************
This message, and any attachment contained, are confidential and subject of legal privilege. It may be used solely for the designated police/justice purpose and by the individual or entity to whom it is addressed. The information is not to be disseminated to another agency or third party without the author?s consent, and must not be retained longer than is necessary for the fulfilment of the purpose for which the information is to be used. All practicable steps shall be taken by the recipients to ensure that information is protected against unauthorised access or processing. INTERPOL reserves the right to enquire about the use of the information provided.
If you are not the intended recipient, be advised that you have received this message in error. In such a case, you should not print it, copy it, make any use of it or disclose it, but please notify us immediately and delete the message from any computer.
*************************************************************************************************
_______________________________________________
RDS-WHOIS2-RT mailing list
RDS-WHOIS2-RT at icann.org<mailto:RDS-WHOIS2-RT at icann.org>
https://mm.icann.org/mailman/listinfo/rds-whois2-rt


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