<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [registrars] FW: Registrar Failover Working Group Invitation
- To: "Ross Rader" <ross@xxxxxxxxxx>, "Bhavin Turakhia" <bhavin.t@xxxxxxxxxxx>
- Subject: Re: [registrars] FW: Registrar Failover Working Group Invitation
- From: "Nevett, Jonathon" <jnevett@xxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 18 Mar 2006 10:19:37 -0500
- Cc: <registrars@xxxxxxxxxxxxxx>
- Sender: owner-registrars@xxxxxxxxxxxxxx
- Thread-index: AcZKl4/v/NDltFUCTz6fDHt75sX1FgACHQ72
- Thread-topic: [registrars] FW: Registrar Failover Working Group Invitation
I'll participate as well. Thanks. Jon
-----Original Message-----
From: Ross Rader [mailto:ross@xxxxxxxxxx]
Sent: Sat Mar 18 09:23:43 2006
To: Bhavin Turakhia
Cc: registrars@xxxxxxxxxxxxxx
Subject: Re: [registrars] FW: Registrar Failover Working Group Invitation
Before we commit to sending representatives, we should inquire regarding
who else will be on this "working group". This is purely a registrar
matter and not a policy development exercise. Participation in the
exercise should be limited as closely as possible to ICANN technical and
operational staff and members of the registrar community.
In parallel, we should also discuss, prior to meeting with this working
group, the appropriateness and scope of these provisions. In reading
them again, I'm struck by how exceptionally vague and one-sided they
are. I would not agree to these terms in a normal commercial agreement.
I would also like to participate in this effort.
Bhavin Turakhia wrote:
> Hi all,
>
> Have recvd the below email from ICANN. This is an important item since it
> results in a compliance cost for registrars, and at the same time the
> provision ensures stability. Any volunteers from the constituency for this
> task force?
>
> bhavin
>
> -----Original Message-----
> From: Mike Zupke [mailto:mike.zupke@xxxxxxxxx]
> Sent: Wednesday, March 15, 2006 8:24 PM
> To: 'Bhavin Turakhia'
> Cc: 'Tim Cole'
> Subject: Registrar Failover Working Group Invitation
>
> Dear Bhavin,
>
> In furtherance of our mission to promote stability in the domain name space,
> ICANN is beginning preparations to launch a registrar failover program. We
> hope to involve the Registrars' Constituency in these early stages so that
> the program will best take into account the needs the registrar community.
>
> As you are probably aware, paragraph 3.6 of the Registrar Accreditation
> Agreement calls for all accredited registrars to escrow certain domain name
> registration data with ICANN or an ICANN-approved escrow services provider
> on a schedule established by ICANN. Until now, ICANN has never invoked this
> provision of the RAA. Some time ago, a working group drafted specifications
> and proposed procedures for a data escrow program, but the project has not
> advanced beyond the planning stages due to budget constraints.
>
> We now wish to revisit and update the original working group's
> recommendations as we look to implement data escrow and a broader registrar
> failover plan. To do this, we would like to request participation from
> members of the registrar community in a working group that will meet
> initially at the ICANN meeting in Wellington, New Zealand, and thereafter by
> telephone and email.
>
> Would you kindly solicit the membership of your constituency for interest in
> participation in this working group and forward to me a list of volunteers?
>
> Thank you for your help with this.
>
> Best regards,
>
> Mike Zupke
> Registrar Liaison Manager
> Internet Corporation for Assigned Names and Numbers
> 4676 Admiralty Way; Suite 330
> Marina del Rey, California 90292, USA
>
>
>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|