RE: [gnso-irtp-b-jun09] Proposed Draft Language: Reason for Denial #6
Hi James, Thanks for drafting the language. Overall I like it but would recommend modifying the last sent to stop after "opt-in basis". I believe that if the name has either clientTransferProhibited or serverTransferProhibited status assigned, the transfer request command would error out and there would be nothing to which the Transfer Contact would need to object. The additional language seems more appropriate to denial reason 7 relating to the lock scenario. Just my two cents. 6. Express objection to the transfer by the Transfer Contact. Objection could take the form of specific request (either by paper or electronic means) by the Transfer Contact to deny a particular transfer request, or a general objection to all transfer requests received by the Registrar, either temporarily or indefinitely. In all cases, the objection must be provided with the express and informed consent of the Transfer Contact on an opt-in basis." Barbara -----Original Message----- From: owner-gnso-irtp-b-jun09@xxxxxxxxx [mailto:owner-gnso-irtp-b-jun09@xxxxxxxxx] On Behalf Of James M. Bladel Sent: Wednesday, January 05, 2011 11:51 AM To: ITRP-B Mailing List Mailing List Subject: [gnso-irtp-b-jun09] Proposed Draft Language: Reason for Denial #6 Team: As discussed on previous calls, I was tasked to present draft language for a new (clearer) version of "Reason for Denial #6." Currently, RfD #6 reads: ------------------------------------------------------- 6. Express written objection to the transfer from the Transfer Contact. (e.g. - email, fax, paper document or other processes by which the Transfer Contact has expressly and voluntarily objected through opt-in means). ------------------------------------------------------- Reading through the earlier WG thread (from August) and Staff notes on this subject, the general idea is that this should be clarified as to whether the objection was for a specific transfer request, or all transfer requests, and that the Registrant should be aware this is occurring (i.e. no "secret" locks). With these thoughts in mind, I have taken Staff's initial language and modified it slightly, and submit this Proposed RfD #6 text for your comment: ------------------------------------------------------- 6. Express objection to the transfer by the Transfer Contact. Objection could take the form of specific request (either by paper or electronic means) by the Transfer Contact to deny a particular transfer request, or a general objection to all transfer requests received by the Registrar, either temporarily or indefinitely. In all cases, the objection must be provided with the express and informed consent of the Transfer Contact on an opt-in basis, and the Registrar must provide a reasonably accessible method to remove the lock on a timely basis, subject to the terms, conditions, and limitations of the Registrar's Registration Agreement with the Transfer Contact." ------------------------------------------------------- Thanks-- J. Attachment:
smime.p7s
|