[CZDS] TLDs playing possum
Despite long-standing complaints, no response to renewal requests: TLD Since #Delegations (last snapshot) ------------- ---------- ----- desi 2022-09-15 1170 xn--1qqw23a 2022-10-31 172 xn--30rr7y 2022-10-31 8 xn--3bst00m 2022-10-31 2861 xn--6qq986b3xl 2022-10-31 12959 xn--9et52u 2022-10-31 2 xn--xhq521b 2022-10-31 349 Is it just me, or are these broadly ignoring requests? -- Viktor.
It appears that Viktor Dukhovni via gtld-tech <ietf-dane@dukhovni.org> said:
Despite long-standing complaints, no response to renewal requests:
TLD Since #Delegations (last snapshot) ------------- ---------- ----- desi 2022-09-15 1170 xn--1qqw23a 2022-10-31 172 xn--30rr7y 2022-10-31 8 xn--3bst00m 2022-10-31 2861 xn--6qq986b3xl 2022-10-31 12959 xn--9et52u 2022-10-31 2 xn--xhq521b 2022-10-31 349
Is it just me, or are these broadly ignoring requests?
It's not just you. All of these had complaints filed after a week of inaction. It's been months since I've seen anything from compliance. Zone Last change How long xn--1qqw23a 2022-10-31T07:04:18Z 80 days, 18:56:37 (佛山) xn--3bst00m 2022-10-31T07:04:18Z 80 days, 18:56:37 (集团) xn--6qq986b3xl 2022-10-31T07:04:18Z 80 days, 18:56:37 (我爱你) voting 2022-11-15T08:04:48Z 65 days, 17:56:07 desi 2022-11-23T23:49:55Z 57 days, 2:11:00 R's, John
Is it just me, or are these broadly ignoring requests?
It's not just you. All of these had complaints filed after a week of inaction. It's been months since I've seen anything from compliance.
Zone Last change How long xn--1qqw23a 2022-10-31T07:04:18Z 80 days, 18:56:37 (佛山) xn--3bst00m 2022-10-31T07:04:18Z 80 days, 18:56:37 (集团) xn--6qq986b3xl 2022-10-31T07:04:18Z 80 days, 18:56:37 (我爱你) voting 2022-11-15T08:04:48Z 65 days, 17:56:07 desi 2022-11-23T23:49:55Z 57 days, 2:11:00
That was amusing. About five minutes after I sent my message. xn--1qqw23a, xn--3bst00m, and xn--6qq986b3xl all approved my requests. Here's my current list: Zone Last change How long voting 2022-11-15T08:04:48Z 66 days, 11:43:19 desi 2022-11-23T23:49:55Z 57 days, 19:58:12 moscow 2023-01-15T08:05:06Z 5 days, 11:43:01 xn--80adxhks 2023-01-15T08:05:06Z 5 days, 11:43:01 (москва) R's, John
John Levine wrote:
desi 2022-11-23T23:49:55Z 57 days, 2:11:00
This is one is still evading all attempts for me. The saga so far: 2022-09-15 - applied for access after expiry 2022-10-20 - filed complaint #1 after being ignored for a month 2022-11-09 - ICANN acks complaint #1 after 3 weeks 2023-02-06 - filed complaint #2 after a few months 2023-03-01 - ICANN closes complaint #2 as a duplicate after 3 weeks 2023-03-09 - sent follow-up to ICANN to complaint #1 The system is still broken. When you submit a complaint, you get back an email that a ticket has been created with some ticket number, but that email does not mention the TLD the complaint pertains to. So unless you manually record the connection, you won't know which ticket is for what TLD until you get the proper acknowledgement with a copy of the complaint several weeks later (I believe this is when ICANN forwards the complaint to the registry - why only after a couple of weeks?). Also ICANN, when you close a complaint as a duplicate because of an existing pending ticket for that TLD and account, can you list the ticket ID of that existing ticket in the email message? Joe Wein SURBL
On 09/03/2023 08:54, Joe Wein via gtld-tech wrote:
John Levine wrote:
desi 2022-11-23T23:49:55Z 57 days, 2:11:00
This is one is still evading all attempts for me.
The saga so far:
2022-09-15 - applied for access after expiry 2022-10-20 - filed complaint #1 after being ignored for a month 2022-11-09 - ICANN acks complaint #1 after 3 weeks 2023-02-06 - filed complaint #2 after a few months 2023-03-01 - ICANN closes complaint #2 as a duplicate after 3 weeks 2023-03-09 - sent follow-up to ICANN to complaint #1
The system is still broken.
When you submit a complaint, you get back an email that a ticket has been created with some ticket number, but that email does not mention the TLD the complaint pertains to. So unless you manually record the connection, you won't know which ticket is for what TLD until you get the proper acknowledgement with a copy of the complaint several weeks later (I believe this is when ICANN forwards the complaint to the registry - why only after a couple of weeks?).
Also ICANN, when you close a complaint as a duplicate because of an existing pending ticket for that TLD and account, can you list the ticket ID of that existing ticket in the email message?
The .DESI gTLD had 1,028 users in the August 2022 report on the CZDS site. It wasn't in the September 2022 report and is not in the latest ZFA-Passwords reports. There are still some registries manually updating access and this is causing coverage problems. The complaints system needs to be improved and the lack of communication from ICANN doesn't help. There are also problems with the monthly CSV ICANN registrar reports. Some registries have temporary reporting failures. The .AFRICA hasn't filed a valid registrar transactions report (net adds and renewal data is missing) since the gTLD was launched. I recovered the ICANN registrar report data from a combination of CSVs and PDFs back to July 2001 and have it in a database updating monthly. Identifying registrars without IANA-ID numbers was a very interesting bit of Internet archeology. At times, I was wondering if it might have been easier to decrypt Minoan Linear A. Regards...jmcc -- ********************************************************** John McCormac * e-mail: jmcc@hosterstats.com MC2 * web: http://www.hosterstats.com/ 22 Viewmount * Domain Registrations Statistics Waterford * Domnomics - the business of domain names Ireland * https://amzn.to/2OPtEIO IE * Skype: hosterstats.com ********************************************************** -- This email has been checked for viruses by Avast antivirus software. www.avast.com
Hello Joe, I have passed your input to our collogues from the Compliance team for them to look into. Regards, --Eduardo A. -----Original Message----- From: gtld-tech <gtld-tech-bounces@icann.org> on behalf of Joe Wein via gtld-tech <gtld-tech@icann.org> Reply-To: Joe Wein <joewein@surbl.org> Date: Thursday, March 9, 2023 at 12:55 AM To: "gtld-tech@icann.org" <gtld-tech@icann.org> Subject: Re: [gtld-tech] [CZDS] TLDs playing possum John Levine wrote: >>desi 2022-11-23T23:49:55Z 57 days, 2:11:00 This is one is still evading all attempts for me. The saga so far: 2022-09-15 - applied for access after expiry 2022-10-20 - filed complaint #1 after being ignored for a month 2022-11-09 - ICANN acks complaint #1 after 3 weeks 2023-02-06 - filed complaint #2 after a few months 2023-03-01 - ICANN closes complaint #2 as a duplicate after 3 weeks 2023-03-09 - sent follow-up to ICANN to complaint #1 The system is still broken. When you submit a complaint, you get back an email that a ticket has been created with some ticket number, but that email does not mention the TLD the complaint pertains to. So unless you manually record the connection, you won't know which ticket is for what TLD until you get the proper acknowledgement with a copy of the complaint several weeks later (I believe this is when ICANN forwards the complaint to the registry - why only after a couple of weeks?). Also ICANN, when you close a complaint as a duplicate because of an existing pending ticket for that TLD and account, can you list the ticket ID of that existing ticket in the email message? Joe Wein SURBL _______________________________________________ gtld-tech mailing list gtld-tech@icann.org https://mm.icann.org/mailman/listinfo/gtld-tech ________________________________________________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.
It appears that Eduardo Alvarez via gtld-tech <eduardo.alvarez@icann.org> said:
-=-=-=-=-=- -=-=-=-=-=-
Hello Joe, I have passed your input to our collogues from the Compliance team for them to look into.
Similar situation here -- .DESI is the only TLD that has never, ever, replied despite many complaints. It's taken a long time but with the extensions and automatic renewals, the number of failed renewals and complaints has gone down a lot. Even .VOTING finally woke up after a pointed messag from Compliance. R's, John
-----Original Message----- From: gtld-tech <gtld-tech-bounces@icann.org> on behalf of Joe Wein via gtld-tech <gtld-tech@icann.org> Reply-To: Joe Wein <joewein@surbl.org> Date: Thursday, March 9, 2023 at 12:55 AM To: "gtld-tech@icann.org" <gtld-tech@icann.org> Subject: Re: [gtld-tech] [CZDS] TLDs playing possum
John Levine wrote:
desi 2022-11-23T23:49:55Z 57 days, 2:11:00
This is one is still evading all attempts for me.
The saga so far:
2022-09-15 - applied for access after expiry 2022-10-20 - filed complaint #1 after being ignored for a month 2022-11-09 - ICANN acks complaint #1 after 3 weeks 2023-02-06 - filed complaint #2 after a few months 2023-03-01 - ICANN closes complaint #2 as a duplicate after 3 weeks 2023-03-09 - sent follow-up to ICANN to complaint #1
The system is still broken.
When you submit a complaint, you get back an email that a ticket has been created with some ticket number, but that email does not mention the TLD the complaint pertains to. So unless you manually record the connection, you won't know which ticket is for what TLD until you get the proper acknowledgement with a copy of the complaint several weeks later (I believe this is when ICANN forwards the complaint to the registry - why only after a couple of weeks?).
Also ICANN, when you close a complaint as a duplicate because of an existing pending ticket for that TLD and account, can you list the ticket ID of that existing ticket in the email message?
Joe Wein SURBL
_______________________________________________ gtld-tech mailing list gtld-tech@icann.org https://mm.icann.org/mailman/listinfo/gtld-tech
________________________________________________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.
-=-=-=-=-=- [Attachment type=application/pkcs7-signature, name=smime.p7s] -=-=-=-=-=- -=-=-=-=-=-
_______________________________________________ gtld-tech mailing list gtld-tech@icann.org https://mm.icann.org/mailman/listinfo/gtld-tech
________________________________________________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 al + together (e.g., for a vacation), and so on. -=-=-=-=-=-
On Thu, Mar 09, 2023 at 02:00:54PM -0500, John Levine via gtld-tech wrote:
Similar situation here -- .DESI is the only TLD that has never, ever, replied despite many complaints.
Same here, my outdated subscriptions are: desi 2022-09-15 berlin 2023-02-25 hamburg 2023-02-27 I am assuming that berlin and hamburg will get around to it even without a complaint, though it is starting to look like one may be needed. -- Viktor.
On Thu, Jan 19, 2023 at 09:04:24PM -0500, John Levine wrote:
It appears that Viktor Dukhovni via gtld-tech <ietf-dane@dukhovni.org> said:
Despite long-standing complaints, no response to renewal requests:
TLD Since #Delegations (last snapshot) ------------- ---------- ----- desi 2022-09-15 1170 xn--1qqw23a 2022-10-31 172 xn--30rr7y 2022-10-31 8 xn--3bst00m 2022-10-31 2861 xn--6qq986b3xl 2022-10-31 12959 xn--9et52u 2022-10-31 2 xn--xhq521b 2022-10-31 349
Is it just me, or are these broadly ignoring requests?
It's not just you. All of these had complaints filed after a week of inaction. It's been months since I've seen anything from compliance.
Zone Last change How long xn--1qqw23a 2022-10-31T07:04:18Z 80 days, 18:56:37 (佛山) xn--3bst00m 2022-10-31T07:04:18Z 80 days, 18:56:37 (集团) xn--6qq986b3xl 2022-10-31T07:04:18Z 80 days, 18:56:37 (我爱你) voting 2022-11-15T08:04:48Z 65 days, 17:56:07 desi 2022-11-23T23:49:55Z 57 days, 2:11:00
Don't know whether my timing was "just right", or proverbs about squeaky wheels are spot on, but today all but "desi" were renewed. -- Viktor.
participants (5)
-
Eduardo Alvarez -
Joe Wein -
John Levine -
John McCormac -
Viktor Dukhovni