The team has informed that existing complaints that are already in progress with the Registry Operators would remain active when the request is cancelled, as long as a subsequent request is submitted immediately with the Registry Operator, without the need to submit a new complaint to ICANN Contractual Compliance by the requestor.
Typically I would cancel a ZFA request if it hasn't been actioned for several months AND a previous complaint did not resolve the issue. If complaints remain active when a request gets canceled and resubmitted, it means no new complaint can be filed if the resubmitted request is not processed either. It will automatically be rejected as a duplicate by the system. The only way to complain then is to do a follow-up on the ticket number of the original complaint (pre-cancel) but that will be hard to do when the ICANN complaint acknowledgement mails don't disclose which ticket number relates to what TLD. The rejection message for "duplicate" complaints does not mention the ticket number of the original complaint either.
Furthermore, ICANN Contractual Compliance sends an additional manual confirmation once the complaint is being initiated with the contracted party and the TLD should be included in the manual confirmations.
That's correct, but in the case of my first complaint about .citadel, the manual confirmation you mention arrived *4 months* after the complaint submission. I am sure you would agree that's unacceptably long. Is it much better now? Checking my records, a few complaints I submitted on April 3 have only generated the initial ticket number mail ("A new case has been created...") so far but no manual confirmation yet that would link the ticket number and the TLD as you describe. That suggests that some submitted tickets may be sitting there for weeks before ICANN sends them to the contracted parties. Joe Wein SURBL
Best regards,
Eduardo Alvarez ICANN
-----Original Message----- From: gtld-tech <gtld-tech-bounces@icann.org> on behalf of Viktor Dukhovni via gtld-tech <gtld-tech@icann.org> Reply-To: "gtld-tech@icann.org" <gtld-tech@icann.org>, Viktor Dukhovni <ietf-dane@dukhovni.org> Date: Thursday, April 28, 2022 at 7:46 AM To: "gtld-tech@icann.org" <gtld-tech@icann.org> Subject: Re: [gtld-tech] CZDS Support for Request Cancellation On Thu, Apr 28, 2022 at 07:05:37PM +0900, Joe Wein via gtld-tech wrote: > > I think my question has a broader audience, so I am asking it here > > instead: > > > > What effect does cancelling a long neglected "pending" request have > > on outstanding complaints? Are they also automatically closed? > > > > The reason I ask, is that after closing long neglected requests I am > > opening fresh requests in the hope that they might get approved this > > time around. If they don't get processed in a fairly generous time > > frame (say 4 weeks), I'd like to file a fresh complaint, and would > > like it to not register as a duplicate... > > Yes, that's a very likely source of proplems unless addressed. Meanwhile I wrote to compliance requesting that the extant complaints be closed... I hope that happens. > A request that I have made before: Can we please have the TLD mentioned in > the email that acknowleges that a complaint has been filed? Otherwise it is > very difficult to match ticket numbers to TLDs from our end. Yes, the email notices from the ZFA form have zero content, and should not be sent, I now just delete them unread. Only once the compliance department processes the filed complaint should there be an email notice. Everything in the email from the ZFA form was already conveyed when the website completed form submission. -- Viktor. _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.