[GNSO-TPR] STARTS IN 15 MINUTES Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 05 April 2022

Tue Apr 5 16:11:09 UTC 2022

Dear fellow TP Working Group Members,

Below is the text version of the BC’s summary on three different transfer locks as read out in the call today. Many thanks to Arinola for assisting with presenting the issues to the BC along with me.

Summary of BC Transfer Policy Working Group Call

Post-Creation Lock
Ten days is too short. Leave it at 60 days if possible. Maybe 30 days is a happy medium, but 60 days is still preferable. The longer the better from a trademark enforcement perspective as it prevents having to redo a UDRP or demand letter, and also assists with preventing registrar hopping when a registrar is asked to take enforcement proceedings against an infringing or unlawfully used domain name.

There may be an issue in shortening the period from a registrar’s perspective, in that a registrar customer may take advantage of promotional / loss-leader type pricing for the initial year and then the customer moves away to another registrar.

Change of Registrant Lock
The default rule should be a transfer lock following a change of registrant. However, a registrar should be required in a transparent manner, to enable a registrant, upon request to opt-out of the transfer lock or to reduce the transfer lock, rather then leave it to each registrar to decide whether they will generally permit opt-outs. Nevertheless, each registrar should retain discretion as to whether to permit a transfer even if the registrant has ostensibly opted out, for security reasons. A transfer lock should not prevent registrants and businesses from effecting bona fide transfers when necessary or desirable. There should be a fact-based rationale for the determination of the length of the default transfer lock, whether it is 60 or 30 days, for example. A BC member is looking to see whether Domain Abuse Activity Reporting data can provide any insight into the appropriate length for transfer locks.

Change of Registrar Lock
This lock does not appear to be of significant concern as it would usually coincide with a change of registrant lock. However, a registrant should not be prevented from transferring a domain name from one registrar to another, even after a recent registrar change, unless there is another type of lock at play.

Zak

From: GNSO-TPR <gnso-tpr-bounces at icann.org> On Behalf Of Julie Bisland
Sent: Tuesday, April 5, 2022 11:45 AM
To: gnso-tpr at icann.org
Cc: Julie Bisland via Gnso-secs <gnso-secs at icann.org>
Subject: [GNSO-TPR] **STARTS IN 15 MINUTES** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 05 April 2022

**STARTS IN 15 MINUTES**

Dear all,

The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 05 April 2022 at 16:00 UTC for 90 minutes.

Zoom Room Information:
Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09__;!!PtGJab4!vQUeA6MJfcr-A_RjhiKhyIK1tDOvuMfUmK-p7PBbKXVpTpDJDFh1Vx2q69ln_-UMqtsw69TfeA$>
Passcode: @TP/^*4wg#

If you are joining via audio only:
One tap mobile:
US: +19294362866,,95363727469#,,,,*7490739013#   or  +13017158592,,95363727469#,,,,*7490739013#

Telephone: Dial (for higher quality, dial a number based on your current location):
US: +1 929 436 2866  or  +1 301 715 8592  or  +1 312 626 6799  or  +1 669 900 6833  or  +1 253 215 8782  or  +1 346 248 7799  or  888 788 0099 (Toll Free) or  877 853 5247 (Toll Free)

Webinar ID: 953 6372 7469
Passcode: 7490739013
International numbers available: https://icann.zoom.us/u/acdLFXPLp6 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!vQUeA6MJfcr-A_RjhiKhyIK1tDOvuMfUmK-p7PBbKXVpTpDJDFh1Vx2q69ln_-UMqtvZAh2uYw$>

Members, alternates, and observers all have different access and participation directions, please read below!

ALL: Before joining the call:

  *   Please send apologies and dial out requests to gnso-secs at icann.org<mailto:gnso-secs at icann.org> only
  *   Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en>
  *   Visit the Wiki Agenda meeting page: https://community.icann.org/x/LBAiCw
  *   Check your time zone: https://tinyurl.com/yfh6jc8x [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/yfh6jc8x__;!!PtGJab4!v8Q3co55s59EZ8Wl6wzD4pEgS-gPjLuDxoxEHvAP5ZrHQCd2yMgrOaae9_ILkb2UzK2ux9UO-g$>

ONLY FOR MEMBERS & ALTERNATES:

  *   Please join via the Main Zoom Webinar link above; staff will promote you to panelist.
  *   Chat: Members (and alternates replacing members), please select Everyone so everyone can see and so it’s captured afterwards.
  *   Alternate replacement confirmations – For tracking alternate replacements, use the google form [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUIRytxM4d-TDoSQAQ/viewform__;!!PtGJab4!vQUeA6MJfcr-A_RjhiKhyIK1tDOvuMfUmK-p7PBbKXVpTpDJDFh1Vx2q69ln_-UMqtszsVGk9Q$> to communicate the replacement (alternate) and the duration. This information will be publicly posted to the Alternate Log-Transfer Policy Review PDP<https://community.icann.org/x/V4aUCQ> wiki page.
  *   Alternates (not replacing a member): Rename your line by adding THREE Zs (zzz) before your name and add, in parentheses (your affiliation - alternate) after your name. To rename in Zoom, hover over your name and click ‘rename’.
  *   Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing.
 ONLY FOR OBSERVERS:

  *   Observers will have ability to view member chat and information shared in the zoom webinar room. Observers will not be able to use chat or raise hands.

Thank you.
Kind regards,

Julie

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/gnso-tpr/attachments/20220405/0387e957/attachment-0001.html>