<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [registrars] Proliferation of registrar locks
So lets start a laundry list:
1. Does the policy appropriately deal with registrar_lock proliferation
and implementation? How can the policy be amended/modified/improved to
take into account the evolution of practices in the market over the last
12 months?
2. A fixed URL for lock and authinfo by registrars that will be sent to
ICANN/registries that would be available for registrars to query or remove the protection/
request the authinfos via the FOA at the loosing registrar. With this solution the protection
can be removed easily and the authinfos can be requested and sent to the admin of the domain.
hope more will come...
Paul
Contact info: http://www.blogware.com/profiles/ross
Skydasher: A great way to start your day
My weblog: http://www.byte.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-nr1 (Windows XP)
iD8DBQFBmMH56sL06XjirooRAlMzAJ99JlFD8rw37ZEs9ArqFqHF6mi7EACcClnk
mgQAqqMcCIh0/35Lb1br82Y=
=QjY1
-----END PGP SIGNATURE-----
--
CORE Internet Council of Registrars http://corenic.org
WTC II, 29 route de Pre-Bois, CH-1215 Geneva, Switzerland
Tel +4122 929-5744 Fax +4122 929-5745 secretariat@xxxxxxxxxxx
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|