ICANN ICANN Email List Archives

[gnso-otf-dt]


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

Re: [gnso-otf-dt] FOR REVIEW/APPROVAL: Revised Draft Charter

  • To: Julie Hedlund <julie.hedlund@xxxxxxxxx>
  • Subject: Re: [gnso-otf-dt] FOR REVIEW/APPROVAL: Revised Draft Charter
  • From: Olga Cavalli <olgacavalli@xxxxxxxxx>
  • Date: Mon, 17 Oct 2011 12:49:26 -0300

ok for me
thanks Julie for doing this so quickly and so good!
best
Olga

2011/10/17 Julie Hedlund <julie.hedlund@xxxxxxxxx>

>  Dear DT members,
>
> I have revised the Charter according to the following suggestions provided
> by Chuck (see my notes below appended to Chuck’s suggestions).  The changes
> are redlined.  I also identified several areas in the Decision-making
> Methodologies section that required changes because of the fact that the
> Chair is also the Council Liaison.
>
> ***NOTE:  If there are no objections to the changes in the document by
> 1600 UTC/Noon EDT tomorrow, I will accept the changes and send the Charter
> and motion for Olga to submit to the Council.**
> *
> Thank you very much for all your work on this effort!
>
> Best regards,
>
> Julie
>
>
>    1. Membership Criteria and Roles, Functions, Duties: We tried to state
>    more clearly the size and composition of the OTF at the start of the 
> section
>    and we decided to make the Steering Committee contingent on the size of the
>    OTF/number of volunteers. *[Gomes, Chuck] *I like the way you changed
>    the steering committee but I have one more caution: you shouldn’t be
>    surprised if you cannot get a volunteer from every constituency or
>    stakeholder group.  It is a good goal to do that but I think it would be
>    wise to word the goal in a way that allows for the eventuality that one or
>    more constituencies or stakeholder groups may not be represented.  How 
> about
>    something like this: “. . . small Steering Committee that would include
>    the Chair, Vice Chair, and at least one representative from each 
> Stakeholder
>    Group or at least two representatives from each House.”  Note that this
>    might result in a steering committee as small as six but it could still be
>    larger if there were enough volunteers.  Note that changes in this regard
>    would affect wording in several other places in your document.  JULIE:
>     I INSERTED CHUCK’S REVISED LANGUAGE.
>    2. Additional Change:  We realized that we needed to reflect that the
>    Council will appoint the Chair and Vice Chair, so we included this step.  
> In
>    addition, since there initially would not be a Steering Committee, we
>    assigned the recruitment role to the Chair, Vice Chair, and support staff.
>     This should be reflected throughout the document.*[Gomes, Chuck] *This 
> seems fine to me but I do want to comment on the following: “
>    *Objective 1:* The GNSO Council shall approve the Charter and appoint
>    the OTF Chair, who also is the GNSO Council Liaison, and the Vice Chair.”
>     It appears to me that this requires the OTF Chair to be a Councilor; are
>    you sure you want to do that? I believe that Council liaisons are normally
>    Councilors.  Assuming that is true, what happens if you cannot find a
>    Councilor who will be OTF Chair?  If I was you, I would consider deleting
>    “who also is the GNSO Council Liaison”.   Qualified chairs are hard enough
>    to find without be too restrictive.  On the other hand, if it is okay for
>    the liaison to be a non-Councilor, your language may be okay, but if that 
> is
>    the case I suggest you make that clear.  Note that this issue occurs again
>    in Deliverable # 1, in the steering committee discussion, under Formation
>    and in Roles, Functions & Duties. JULIE:  I INSERTED LANGUAGE THAT
>    CLARIFIES THAT THE CHAIR DOES NOT HAVE TO BE A COUNCILOR.
>    3. Size of the OTF: JULIE: I INSERTED CHUCK’S SUGGESTED LANGUGE OF A
>    MINIMUM OF 2 MEMBERS FROM EACH GEOGRAPHIC REGION.
>    4. Public Form change to Forum:  JULIE: I MADE THE CORRECTIONS.
>
>


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

Privacy Policy | Terms of Service | Cookies Policy