[NCSG-PC] Fwd: Request for Early Input - GNSO Transfer Policy Review PDP

[Johan Helsingius]

Many thanks!

	Julf


On 01/03/2023 22:42, Juan Manuel Rojas wrote:
> Dear Julf and all,
> Those questions were the same were discussed on the last WG meeting. It 
> is important to say that WG is now discussing about TEAC (Transfer 
> Emergency Action Contact) and the call for input is to have the view 
> from diverse opinions on this regard. In the meeting was made in survey 
> mode. As far I understand this process is related to when the registrars 
> need contact the registrant of a domain been transfered.
> 
> My answer on the survey questions were:
> 
> 1.Isadditionaldata neededtosupport 
> evaluationoftheeffectivenessoftheTEACmechanism?
> As I said it was in survey mode inside Zoom room, there's no many 
> information about the effectiveness of TEAC mechanism, so I answered 
> YES. The next question is What data is needed? It wasn't on the survey 
> what it was made, so here my answer is related to assess the mechanism, 
> but I do not have more information
> 
> 2. The time frame for registrants respond to communicatoins via TEAC 
> channel, according with Status Quo said is 4 hours. So here my answer it 
> was to let a window for at least 24 hours to respond. Here is important 
> note that the time zone differences could be significant. And also the 
> registrars will have to implement mechanisms to receive requests coming 
> in other languagues than English.
> 
> 3. This question is similar to previous.
> 
> 4. This question it was not on the survey made either. But I think about 
> "Communications to a TEAC must be initiated in a timely manner". In 
> order to being able to react if an small organization doesn't want to 
> lose its domain I think a reasonable period of time would be a year 
> later or let, at least, after renovation window (if apply) to use the 
> dispute resolution process.
> 
> 5. According to the survey this question is about the means of 
> communication "theTEACmaybedesignated
> asa telephonenumber,andthereforesomeTEACcommunicationsmaytakeplace 
> byphone". Here my answer was directed that the contact should be made 
> through e-mail also due to the fact that sometimes the phone is not 
> enough to contact an organization or even their representative on this 
> issues.
> 
> Those were some of the question discussed on the last WG meeting, I 
> think these answers can be helpful if anyone wants to add or amplify 
> some of them.
> 
> Best Regards,
> 
> 
> *JUAN MANUEL ROJAS P.*
> Director - MINKA DIGITAL Colombia
> NPOC Policy Chair - NCSG/GNSO
> Master IT candidate, UNAD
> Registered Linux User No.*533108.*
> 
> 
> /Cel. +57 301 743 56 00
> Instagram/Twitter: @JmanuRojas <http://www.twitter.com/jmanurojas>/
> 
> 
> 
> 
> 
> 
> 
> El martes, 28 de febrero de 2023, 03:34:43 p. m. GMT-5, Johan Helsingius 
> <julf at julf.com> escribió:
> 
> 
> 
> 
> 
> -------- Forwarded Message --------
> Subject:     Request for Early Input - GNSO Transfer Policy Review PDP
> Date:     Tue, 28 Feb 2023 20:26:53 +0000
> From:     Devan Reed <devan.reed at icann.org <mailto:devan.reed at icann.org>>
> To: julf at julf.com <mailto:julf at julf.com> <julf at julf.com 
> <mailto:julf at julf.com>>, Andrea Glandon
> <andrea.glandon at icann.org <mailto:andrea.glandon at icann.org>>
> CC: gnso-secs at icann.org <mailto:gnso-secs at icann.org> 
> <gnso-secs at icann.org <mailto:gnso-secs at icann.org>>, Emily Barabas
> <emily.barabas at icann.org <mailto:emily.barabas at icann.org>>, Berry Cobb 
> <Berry.Cobb at icann.org <mailto:Berry.Cobb at icann.org>>, Julie
> Hedlund <julie.hedlund at icann.org <mailto:julie.hedlund at icann.org>>, 
> Caitlin Tubergen
> <caitlin.tubergen at icann.org <mailto:caitlin.tubergen at icann.org>>
> 
> 
> 
> Dear Julf,
> 
> Please find attached a request from the GNSO Transfer Policy Review
> Policy Development Process Working Group forinputfrom your group on
> Group 2 topics within the PDP’s charter. Responses are requested by 4
> April 2023 and may be sent tognso-secs at icann.org 
> <mailto:tognso-secs at icann.org>
> <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>.
> 
> Kind regards,
> 
> Devan
> 
> *Devan Reed*
> Policy Development Support - TEMP
> Internet Corporation for Assigned Names and Numbers (ICANN)
> 
> www.icann.org
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=5Q2VHFiILluU8bvJHD3YjtNb84SyquCx2HSNHYn1ybs&m=X5iO0FCI3T2FxZ0KhKQ1iY0GhPzLH7XaiK8LfLcHSPY&s=grheVbJRc-hQqrXXGzMqUK3Htr0S5Z74HFOhmrag-Js&e= <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=5Q2VHFiILluU8bvJHD3YjtNb84SyquCx2HSNHYn1ybs&m=X5iO0FCI3T2FxZ0KhKQ1iY0GhPzLH7XaiK8LfLcHSPY&s=grheVbJRc-hQqrXXGzMqUK3Htr0S5Z74HFOhmrag-Js&e=>>
> 
> cidimage001.png at 01D4E0C6.320C4B80 <mailto:cidimage001.png at 01D4E0C6.320C4B80>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc 
> <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>