[alac] Updated Transfer Assistance Group Drafts.

[Thomas Roessler <roessler@xxxxxxxxxxxxxxxxxx>]

FYI.  Comments welcome.
-- 
Thomas Roessler                 <roessler (at) does-not-exist.org>





----- Forwarded message from Bruce Tonkin <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx> 
-----

From: Bruce Tonkin <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx>
To: Tina Dam <dam@xxxxxxxxx>, Jeff.Neuman@xxxxxxxxxxxx,
        paul@xxxxxxxxxxxxxxxxxx, roessler@xxxxxxxxxxxxxxxxxx,
        grant.forsyth@xxxxxxxxxxxxxxxxxxxxxxx, sricciardi@xxxxxxxxxxxxxxx
Date: Tue, 9 Sep 2003 16:22:26 +1000
Subject: Second Draft Standardised Form of Authorisation
X-Spam-Level: 


Hello All,

See below for revised text.  To provide for some flexibility, we could
allow a registrar to either use the standardised text as provided in the
contract, or a registar could request approval from ICANN staff for any
change to the text.  ICANN staff would need to ensure that the main
elements of the text are preserved.  I prefer this approach at this
stage to being more general and just including general principles, as
there are existing problems with misleading messages in the transfers
process and it is better to start with a more defined approach that can
be enforced, rather than repeating the mistakes of the past in creating
something that can not be easily (and cheaply) enforced.  Once the
transfer process has been running for say 6 months we can review the
text - this process of regular review has worked quite effectively in
Australia for .au.

Text in square brackets [ ] is for comments, and is not part of the
standardised form seen by the registrant.

Text in angle brackets < > is to indicate where information needs to be
inserted.  The registrant would only see the inserted text and not the
angle bracket.

I removed the information about the new expiry date to reduce
complexity.

I added the information about no transfer for another 60 days.

I removed the URL for the WHOIS service.

I think the ability to refer to a reseller is now made clearer as part
of the text to insert about the where the request has come from.

Regards,
Bruce Tonkin


***********************************************************************

STANDARDIZED FORM OF AUTHORIZATION
DOMAIN NAME TRANSFER - REQUEST FOR CONFIRMATION

An English version of this message is contained below.

<Insert translation of English version in preferred language of the
registrant if known>

ENGLISH VERSION

Attention: <insert Registrant or Administrative Contact of Record as
listed in the WHOIS>

Re: Transfer of <insert domain name>

The current registrar of record for this domain name is <insert name of
losing registrar>.

<insert name of gaining registrar> has received a request from 
<insert name of person/entity/reseller requesting transfer> on 
<insert date of request> for us to become the new registrar of record.

You have received this message because you are listed as the registrant
or 
 administrative contact for this domain name in the WHOIS database. 

Please read the following important information about transferring your
domain name:

* You must agree to enter into a new Registration Agreement with us. 
You can review the full terms and conditions of the Agreement at 
<insert URL of new terms and conditions>

* Once you have entered into the Agreement, the transfer will take place

within five (5) calendar days.

* Once a transfer takes place, you will not be able to transfer to
another registrar for 60 days, apart from a transfer back to the
original registrar. 

If you wish to proceed with the transfer:

[NOTE: a registrar can choose to include one or more of the following in
the message sent to the registrant/admin contact, and additional
processes may be added with ICANN approval.]

[option 1] please email us <insert contact details> with the following
message:

"I confirm that I have read the Domain Name Transfer - Request for
Confirmation Message.  

I confirm that I wish to proceed with the transfer of 
<insert domain name> from <insert name of losing registrar> 
to <insert name of gaining registrar>."


[option 2] please go to our website, <insert URL of confirmation
webpage> 
to confirm.
[Note: website to contain text as above, with the option to confirm or
deny the transfer]

[option 3] please print out a copy of this message and send a signed
copy to 
<insert fax or postal address details>

You are under no obligation to respond to this message.  If you do not
respond, 
the transfer will not proceed.  If you have any questions about this
process, 
please contact <insert contact details>.


----- End forwarded message -----
----- Forwarded message from Bruce Tonkin <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx> 
-----

From: Bruce Tonkin <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx>
To: Tina Dam <dam@xxxxxxxxx>, Jeff.Neuman@xxxxxxxxxxxx,
        paul@xxxxxxxxxxxxxxxxxx, roessler@xxxxxxxxxxxxxxxxxx,
        grant.forsyth@xxxxxxxxxxxxxxxxxxxxxxx, sricciardi@xxxxxxxxxxxxxxx
Date: Tue, 9 Sep 2003 17:39:06 +1000
Subject: Second Draft  Standard form of authorisation for use by losing 
registrars after a transfer is initiated
X-Spam-Level: 





************************************************************************
******************

An English version of this message is contained below.

<Insert translation of English version in preferred language of the
registrant if known>

ENGLISH VERSION

DOMAIN NAME TRANSFER 

Attention: <insert Registrant or Administrative Contact of Record as
listed in the WHOIS>

Re: Transfer of <insert domain name>

<insert name of losing registrar> is the current registrar of record 
for this domain name.

<insert name of losing registrar and/or name of reseller> received
notification 
on <insert date of notification> that you have requested 
a transfer to <insert name of gaining registrar>. 

This means that <insert name of gaining registrar> will become the new 
registrar of record for your domain name on or before
<add 5 days to date of notification>, unless you deny the transfer
request before then.

If you have authorised this transfer, you are under no obligation to
respond to this message, and the transfer will proceed.

To cancel the transfer, please contact us 
<insert contact details> within <insert timeframe> days, or the transfer
will proceed.

[optional] or please go to our website within <insert timeframe> days, 
<insert URL of confirmation webpage> 
to confirm or deny the transfer.
[Note: website to contain text as above, with the option to confirm or
deny the transfer]


----- End forwarded message -----
----- Forwarded message from Bruce Tonkin <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx> 
-----

From: Bruce Tonkin <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx>
To: Tina Dam <dam@xxxxxxxxx>, Jeff.Neuman@xxxxxxxxxxxx,
        Charles A Gomes <cgomes@xxxxxxxxxxxx>, rrader@xxxxxxxxxx,
        ebroitman@xxxxxxxxxxxx, paul@xxxxxxxxxxxxxxxxxx,
        roessler@xxxxxxxxxxxxxxxxxx, grant.forsyth@xxxxxxxxxxxxxxxxxxxxxxx,
        sricciardi@xxxxxxxxxxxxxxx
Date: Tue, 9 Sep 2003 18:01:33 +1000
Subject: Timelines in transfers policy
X-Spam-Level: 

Hello All,

As discussed at the last meeting, here are the current timelines in the
transfers policy.

The intent is that the transfers policy would specify an initial
timeframe, but the timeframe could be changed by approval of ICANN staff
after a review 6 months after launch.

(1) From Recommendation 3:
Time to respond to issue received on registrar's private transfer email
address:
-suggest initial maximum time of 5 calendar days

(2) From recommendation 6:
Time to provide AuthInfo Code:
- suggest 72 hours provided contact details are accurate (e.g email
address is current)
[this assumes that automated procedures can be employed]
- reasonable commercial endeavours to provide the password within 7
days, if contact details are not accurate and separate manual
authentication processes are required

(3) From recommendation 11:
Time to send out transfer audit message after a losing registrar
receives notification from the registry of a transfer
- 24 hours
[note this does not relate to any marketing messages that may be sent
before or after this timeframe]

(4) From recommendation 23:
Time to respond to request for copy of Standardised Form of
Authorisation
- 3 business days
[should this be 3 calendar days to avoid problems of different business
days in different locations?]

(5) From recommendation 24:
Time after a transfer, when a fresh transfer to a registrar other than
the original registrar
- 60 days
[this matches the time period currently after initial registration]

Please provide feedback on whether any of these timelines should be
different.

Regards,
Bruce Tonkin







----- End forwarded message -----