ICANN/DNSO
DNSO Mailling lists archives

[nc-transfer]


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

[nc-transfer] Draft Resolution - Further change


Following the call this morning, I undertook to try and capture the
suggested change to the second part of the resolution.
Here it is
OLD
2. The ICANN Board should direct the ICANN staff to
conduct negotiations and contract revisions appropriate to
implement the recommendations in the IRDX report. 

NEW
2. The ICANN Board should direct the ICANN staff to form an "Implementation
Committee" of 
affected and interested parties to draft the detailed processes necessary to
give effect to 
the policies included in the Transfer Task Force's IRDX report such that
negotiations and 
contract revisions can be expedited.

Let me know if you have further improvements
Marilyn, will you put this up to the NC before its Amsterdam meeting so that
it can be considered and voted on - or is that too late and this is now
pushed out to 2003 NC meeting?

Grant Forsyth
BC Names Council Representative
BC member of the Transfers Task Force


-----Original Message-----
From: Grant Forsyth 
Sent: Wednesday, 11 December, 2002 09:14
To: 'nc-transfer@dnso.org'
Subject: Draft Resolution


Here is my reworked resolution - it has NOT changed substantially
I have
1. removed references about WLS and the delay that it has caused
2. have NOT updated the url at which TF work is recorded - I presume this
has not changed
3. I have added the url where the final report is currently placed
http://www.byte.org/nc-transfers/final/
4. left in optional wording to recognise minority reports - do you want this
in ?
>>> just a thought: Have you asked me for a "Draft" or  the "Final"
resolution?
5. removed recommendations that the Board direct the 

Let me know if there is further work that is needed on this prior to my
posting it to the TF
Regards

Grant Forsyth

DRAFT RESOLUTION
Whereas in early 2001 complaints were raised regarding denials of requested
transfers which prompted Verisign Registrar on 25 May 2001 to impose its own
approach to the problem, which then prompted ICANN President, Stuart Lynn,
on 27 August 2001 to write to the Registrar Constituency recommending that a
new policy be created, which resulted in the Names Council on a conference
call of 11 October 2001 to form the Transfers Task Force with terms of
reference as recorded at:
http://www.dnso.org/clubpublic/nc-transfer/Arc00/doc00000.doc

Whereas the Transfers Task Force considered the issues surrounding
Transfers, 
took submissions and consultations and drafted a set of policy
recommendations, 
this effort being recorded at:
http://www.dnso.org/clubpublic/nc-transfer/Arc00/mail9.html

Whereas the Names Council Transfers Task Force presents a comprehensive set
of policy and process recommendations in the form of the attached report,
"Inter-Registrar Domain Name Transfer: Principles and Process for Gaining
and Losing Registrars" (IRDX report) version 2 revision 0 (2.0), the latest
copy of which is can be found at:
http://www.byte.org/nc-transfers/final/
or
http://www.dnso.org/clubpublic/nc-transfer/Arc00/ and is attached [Ross to
attach latest report]

[Whereas some members of the Names Council wish to have recorded alternative
wording to the final IRDX report, those Minority Reports can be found at:
<web address included> ](Note: this part of the resolution would only make
its way through to the final resolution should there be a Minority
Report(s))

THE NAMES COUNCIL RESOLVES, on the recommendation of the Transfers Task
Force, that:
1. The ICANN Board accept the policy and process recommendations contained
within the IRDX report <version x.y (final version number to be inserted
here)>; 
2. The ICANN Board should direct the ICANN staff to
conduct negotiations and contract revisions appropriate to
implement the recommendations in the IRDX report. 



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