ICANN ICANN Email List Archives

[gnso-improvem-impl-sc]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [gnso-improvem-impl-sc] Adopted SCI Review Requests from GNSO Council Meeting 16 April

  • To: "Aikman-Scalese, Anne" <AAikman@xxxxxxxxxx>, "'avri@xxxxxxx'" <avri@xxxxxxx>, "<gnso-improvem-impl-sc@xxxxxxxxx>" <gnso-improvem-impl-sc@xxxxxxxxx>
  • Subject: Re: [gnso-improvem-impl-sc] Adopted SCI Review Requests from GNSO Council Meeting 16 April
  • From: Julie Hedlund <julie.hedlund@xxxxxxxxx>
  • Date: Mon, 20 Apr 2015 20:57:34 +0000

Dear Anne,

Per item 1 below, I have sent a request to the list and also a reminder to
have members confirm their Primary and Alternate representatives from each
group as you had suggested.  I am still awaiting some responses.  Also, as
Lori is now the Alternate member from the IPC she would not be eligible to
serve as Vice Chair as only Primary representatives can serve as Chair or
Vice Chair.  So, once we confirm Primary and Alternate members the next step
would be to ask for volunteers for the position of Vice Chair and, if there
are multiple volunteers, to proceed to an election per the Charter.

Best regards,
Julie

Julie Hedlund, Policy Director

From:  <Aikman-Scalese>, Anne <AAikman@xxxxxxxxxx>
Date:  Monday, April 20, 2015 2:08 PM
To:  "'avri@xxxxxxx'" <avri@xxxxxxx>, Julie Hedlund
<julie.hedlund@xxxxxxxxx>, "<gnso-improvem-impl-sc@xxxxxxxxx>"
<gnso-improvem-impl-sc@xxxxxxxxx>
Subject:  RE: [gnso-improvem-impl-sc] Adopted SCI Review Requests from GNSO
Council Meeting 16 April

> Dear SCI Members and Staff,
>  
> Many thanks to Avri and staff for obtaining our work orders from the Council.
> Moving forward, we need to:
>  
> 1.      Address the Office of Vice Chair.  (Lori held this post but has moved
> to the IPC so it may not be appropriate for her to continue in that office
> given that it would result in two officers from the same constituency.)
> 
> 2.      Set a schedule for our meetings to address the two assigned work items
> and to determine priorities and timelines, e.g. address both items at once
> with subteams or address one item at a time with the whole group?
> 
> 3.      Discuss the ³periodic review² aspect of SCI responsibilities and
> whether or not we need to be doing any work in this regard at this time.
> 
>  
> I am thinking it might be best to have a short call with members to address
> these procedural matters before beginning our work on the two assignments from
> Council.  
>  
> If we stick with the same day and time as in the past, could we do Tuesday,
> April 28 or Tuesday, May 12?  (I am not available Tuesday May 5 due to the
> International Trademark Association Meeting.)
>  
> Will members please reply with any thoughts you have regarding the above,
> including call dates?
>  
> Thank you,
> Anne
> Anne E. Aikman-Scalese, Of Counsel
> Lewis Roca Rothgerber LLP |
> One South Church Avenue Suite 700 | Tucson, Arizona 85701-1611
> (T) 520.629.4428 | (F) 520.879.4725
> AAikman@xxxxxxxxxx | www.LRRLaw.com <http://www.lrrlaw.com/>
>  
>  
>  
> 
> From: owner-gnso-improvem-impl-sc@xxxxxxxxx
> [mailto:owner-gnso-improvem-impl-sc@xxxxxxxxx] On Behalf Of Avri Doria
> Sent: Thursday, April 16, 2015 11:37 AM
> To: Julie Hedlund; <gnso-improvem-impl-sc@xxxxxxxxx>
> Subject: Re: [gnso-improvem-impl-sc] Adopted SCI Review Requests from GNSO
> Council Meeting 16 April
>  
> Hi,
> 
> Thanks for reporting on this and for all your help in getting these written
> and submitted.
> 
> So now there are two work items.
> 
> 
> avri
> 
> 
> On 16-Apr-15 11:43, Julie Hedlund wrote:
>> 
>> Dear SCI members,
>> 
>>  
>> 
>> As Avri Doria has previously reported, she submitted to the GNSO Council in
>> March two SCI review requests (attached).  These were discussed during the
>> Council meeting on 19 March, but action on them was deferred to the GNSO
>> Council meeting on 16 April.   For reference, here is the link to the
>> transcript from the 19 March meeting:
>> http://gnso.icann.org/en/meetings/transcript-council-19mar15-en.pdf.
>> 
>>  
>> 
>> The two requests were placed on the Consent Agenda for today's GNSO Council
>> meeting as follows: (See the agenda at
>> http://gnso.icann.org/en/meetings/agenda-council-16apr15-en.htm.)
>> "Item 3: Consent agenda (5 mins): 3.1 ­ Approval to refer two matters
>> <http://gnso.icann.org/en/council/drafts>  (first submitted to the Council on
>> 5 March 2015) to the GNSO's Standing Committee for Improvements
>> Implementation (SCI). The first
>> <https://community.icann.org/display/gnsocouncilmeetings/Motions+16+April+201
>> 5>  concerning GNSO Council practices for proposing, seconding and amendment
>> of motions and the second
>> <https://community.icann.org/display/gnsocouncilmeetings/Motions+16+April+201
>> 5>  on clarifying the Operating Procedures regarding the waiver and
>> resubmission of motions."
>> As there were no requests to have these items removed from the consent
>> agenda, the items proceeded to a vote and were adopted.  See the resolutions
>> at: http://gnso.icann.org/en/council/resolutions. If you wish to review the
>> transcript of today's Council meeting it will be posted at:
>> http://gnso.icann.org/en/group-activities/calendar#apr.  The MP3 is available
>> at: http://audio.icann.org/gnso/gnso-council-16apr15-en.mp3. For reference
>> concerning the Consent Agenda procedures, the relevant section from the GNSO
>> Operating Procedures is included below.
>> 
>> Best regards,
>> 
>> Julie
>> 
>> Julie Hedlund, Policy Director
>> 
>> --------Excerpt from the GNSO Council Operating Procedures----------
>> 4.9    Consent Agenda
>> When preparing the meeting agenda, the Council Chair in consultation with the
>> Council Vice-Chairs determines whether an item belongs on the consent agenda.
>> All items that are subject to a different voting threshold than a simple
>> majority vote (see ICANN Bylaws, Article X, section 3-9) or are subject to
>> absentee voting (see section 4.4 ­ Absentee Voting) are not eligible for
>> inclusion in the consent agenda. A numbered list of consent items is included
>> as part of the meeting agenda. The list and supporting documents are included
>> in the Council agenda in sufficient time to be read by all Council members
>> prior to the meeting in accordance with section 3.3 ­ Notice of Meetings of
>> these Operating Procedures.
>>  
>> At the beginning of the meeting, the Chair asks members what items they wish
>> to have removed from the consent agenda and discussed individually. If any
>> Council member requests that an item be removed from the consent agenda, it
>> must be removed. Council members may request that an item be removed for any
>> reason. They may wish, for example, to discuss the item, to query the item,
>> or to register a vote against the item. If an item is removed from the
>> consent agenda, it is added to the meeting agenda for that meeting, unless
>> the Council Chair in consultation with the Council Vice-Chairs determines
>> differently.
>>  
>> When there are no more items to be removed, the Chair reads out the number of
>> the remaining consent items. Then the Chair calls for a vote.
>>  
>> When preparing the minutes, the full text of (or links to) the resolutions,
>> reports or recommendations that were adopted as part of the consent agenda
>> are included. In addition the minutes should include a statement regarding
>> the composition/threshold that approved the consent agenda.
> 
> 
> 
>  <http://www.avast.com/> This email has been checked for viruses by Avast
> antivirus software.
> www.avast.com <http://www.avast.com/>
> 
>  
> 
> 
> 
> This message and any attachments are intended only for the use of the
> individual or entity to which they are addressed. If the reader of this
> message or an attachment is not the intended recipient or the employee or
> agent responsible for delivering the message or attachment to the intended
> recipient you are hereby notified that any dissemination, distribution or
> copying of this message or any attachment is strictly prohibited. If you have
> received this communication in error, please notify us immediately by replying
> to the sender. The information transmitted in this message and any attachments
> may be privileged, is intended only for the personal and confidential use of
> the intended recipients, and is covered by the Electronic Communications
> Privacy Act, 18 U.S.C. §2510-2521.
> 

Attachment: image001.gif
Description: GIF image

Attachment: smime.p7s
Description: S/MIME cryptographic signature



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy