12 November 2004
DotCoop, the sponsor of the .coop TLD, adheres to the bulk of the ICANN Transfer Policy since it supports the rights of registrants to control their domain names and to seek the registrar that best supports their needs.
However, based on community input and the desire to provide the co- operative community special services to support the development of the .coop TLD to promote the co-operative model, there are several adaptations of the standard policy that have been implemented for the benefit of .coop registrants and registrars.
Except as noted below, registrants should reference the standard
ICANN Transfer Policy at www.icann.org/transfers.
Supplemental Transfer Procedures for .Coop Registrars
This supplement replaces section A.5 of the ICANN Transfer Policy in its entirety.
A.5. EPP-based Registry Requirements for Registrars
In EPP-based gTLD Registries, Registrars must follow the requirements set forth below.
Registrars must provide the Registered Name Holder with the unique "AuthInfo" code within five (5) calendar days of the Registered Name Holder's initial request if the Registrar does not provide facilities for the Registered Name Holder to generate and manage their own unique "AuthInfo" code.
Registrars may not employ any mechanism for complying with a Registered Name Holder's request to obtain the applicable "AuthInfo Code" that is more restrictive than the mechanisms used for changing any aspect of the Registered Name Holder's contact or name server information.
The Registrar of Record must not refuse to release an "AuthInfo Code" to the Registered Name Holder solely because there is a dispute between the Registered Name Holder and the Registrar over payment.
Registrar-generated "AuthInfo" codes must be unique on a per-domain basis. The "Auth-Info" codes must be used solely to identify a Registered Name Holder, whereas the FOA's still need to be used for authorization or confirmation of a transfer request, as described in Section 2 and Section 4 of this policy.
.Coop Gaining Registrars may also request the AuthInfo Code directly from their DotCoop Sponsor contact based on providing the required information noted in section A.2 of the ICANN Policy on Transfer of Registrations between Registrars to the DotCoop Sponsor contact.
DotCoop will notify the Registrar of Record of any request for such AuthInfo Codes and will confirm the completion of any transfer initiated in this manner to the original Registrar of Record.
A.8. Effect on Term of Registration
The completion by Registry Operator of a holder-authorized transfer under this Part A shall result in a one-year extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) years.
- 0 uporabniku/om je bi članek v pomoč