<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [registrars] Policy Development process associated with changes in operation of a gtld registry
- To: "Elana Broitman" <ebroitman@xxxxxxxxxxxx>, <registrars@xxxxxxxx>
- Subject: RE: [registrars] Policy Development process associated with changes in operation of a gtld registry
- From: "Rob Hall" <rob@xxxxxxxxxxxxx>
- Date: Fri, 5 Dec 2003 12:43:47 -0500
- Importance: Normal
- In-reply-to: <BCAAA5D64C837641A9EBB93E2A50894807731FC6@ex2k01.corp.register.com>
- Sender: owner-registrars@xxxxxxxxxxxxxx
Elana,
I am ok with your suggestion, with one condition.
I believe it should be someone that has no connection to a "Registry". To
avoid any conflict of interest, our rep should not be connected in any way
to a Registry (this would include owning shares in one, such as afilias).
This is a critical topic for our consituency, and we need to avoid even the
appearance of conflict.
Rob.
-----Original Message-----
From: owner-registrars@xxxxxxxxxxxxxx
[mailto:owner-registrars@xxxxxxxxxxxxxx]On Behalf Of Elana Broitman
Sent: Wednesday, December 03, 2003 1:09 PM
To: Bruce Tonkin; registrars@xxxxxxxx
Subject: RE: [registrars] Policy Development process associated with
changes in operation of a gtld registry
I would recommend that we ask one of our current reps to gather constituency
views since we are facing a short timeline and this is really just a
consensus reporting role.
What do people think?
Bob - would you please set up a telecon for this topic for next week?
Bruce - could you please brief people on the call?
Thank you
-----Original Message-----
From: Bruce Tonkin
Sent: Wed Dec 03 01:02:22 2003
To: registrars@xxxxxxxx
Subject: [registrars] Policy Development process associated with changes in
operation of a gtld registry
Hello All,
The GNSO Council voted to initiate the policy development process to
develop a procedure for use by ICANN when ICANN is required to give
consent or a contractual amendment is required to allow changes in the
architecture or operation of a gTLD registry.
The GNSO Council also voted not to form a task force, but instead to
manage the policy process directly at the Council level by forming a
committee of the whole council. This will follow section 8 of the
Policy Development Process
(see http://www.icann.org/general/bylaws.htm#AnnexA)
In particular, section 8a states:
"a. If the Council decides not to convene a task force, the Council will
request that, within ten (10) calendar days thereafter, each
constituency appoint a representative to solicit the constituency's
views on the issue. Each such representative shall be asked to submit a
Constituency Statement to the Staff Manager within thirty-five (35)
calendar days after initiation of the PDP."
Thus the registrars constituency must select a representative to gather
the constituency's views into a constituency statement, and provide this
to the ICANN staff manager.
Perhaps the executive committeee of the registrar constituency could
call for nominations and an election to appoint a representative (to
take 10 days), or alternatively one of the existing three GNSO Council
members could be assigned the task.
Regards,
Bruce Tonkin
Registrars rep on the GNSO Council
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|