Thanks Anne.  I do disagree with this and probably didn’t do well explaining why, but I will try again.

 

The GNSO Council is not intended as a body that can take quick actions.  It is not as if the GNSO Council Chair can get a request and use her or his discretion to forward it to the SPIRT Team.  The Council Chair would have to send it to the rest of the Council.  Then the Council does not have a process where it can approve the forwarding of the request to the SPIRT team immediately.  It would have to take that action at a meeting.  And if the request does not come in within 14 days before a meeting (I may have the number of days wrong), then it cannot be dealt with at that next meeting, but has to be dealt with at the following one or a newly set up extraordinary meeting (which could be up to 40+ days after the request comes in).

 

Then, if the SPIRT team is just going to discuss and recommend that it is a policy level change and must be dealt with through the GNSO anyway.  So, that process could take at least another 30 days to send it back from where it came.

 

So, in total now, you could have up to 70 days just to get to the point of sending back the request to the body that initially had the quest.  That is a VERY long time if the request is urgent.

 

We have to think of the gTLD Program like a business.  It needs to move efficiently. 

 

If something is clearly policy on its face, then it should go straight to the GNSO to deal with.  But most things are never that clear.  And sending it directly to the SPIRT to get its thoughts and recommendations to help the Council and Community is essentially.  The Council can accept/reject those as it sees fit.

 

Please look out for an email from me in next couple of days with a better explanation about why this is needed. 

 

 

 

Hi all,

I think Donna’s suggestion to run through GNSO Council if request comes from Board or from Councilor FIRST to determine whether an issue is policy or is implementation and should be addressed by SPIRT makes perfect sense.  (Jeff may disagree with this.)

 

If issue is raised by staff, it should be reviewed by SPIRT and SPIRT should make a recommendation to GNSO Council as to whether it is policy or implementation.  (Any Council member could challenge and invoke a process that is in the Annexes.  This is true even if SPIRT treats the issue as implementation but someone on Council believes it is policy.)

 

I still believe it may be prudent to limit requests to the SPIRT team on which it commences work to those coming from either (a) staff or from (b) GNSO Council.  Community members can still give input to the Board, the GNSO Council, and/or staff.  It’s just chatter until a written request comes

 

(a) From the Board to the GNSO Council and from GNSO Council to the SPIRT 

 

OR

 

(b) from staff to the SPIRT with a recommendation from SPIRT to the GNSO Council.

 

That would be my view of a possible compromise – not sure Jeff would agree.

Anne

 

 

 

Anne E. Aikman-Scalese

Of Counsel

520.629.4428 office

520.879.4725 fax

AAikman@lrrc.com

_____________________________

Lewis Roca Rothgerber Christie LLP

One South Church Avenue, Suite 2000

Tucson, Arizona 85701-1611

lrrc.com

Because what matters

to you, matters to us.™

 

 

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.