From m.alzoba at gmail.com Wed Feb 19 19:09:11 2020 From: m.alzoba at gmail.com (Maxim Alzoba) Date: Wed, 19 Feb 2020 22:09:11 +0300 Subject: [gnso-rds-pdp-wg] #12 RPMs Message-ID: Dates of the issues with TMCH: Cases can be requested via ICANN GDD (IBM has own case system) 1. between 02SEP2019 and 26AUG2019 some LORDN files were not uploading to TMDB answer from IBM " We are not sure why you got such errors. It seems to us that the data sent did not reach our servers properly. " 2. between 23 August 2018 and 26 September 2018. Text of the notification > Earlier this year, ICANN org was alerted to a configuration issue within the Trademark Database (TMDB). Based on research by the TMDB?s administrator, IBM, this issue was introduced to the TMDB on 23 August 2018 and affected a limited number of gTLDs that were in the Claims Period between 23 August 2018 and 26 September 2018. This issue may have resulted in registrars not displaying the required Claims Notice to the then potential registrant and the registry of the affected gTLDs not reporting the registration to the TMDB. > > By receiving this communication, ICANN org has identified $REGISTRY as having TLD(s) with domain name registration(s) that have been impacted by the issue. The impacted domain name(s) are listed in the attached .csv file. > > Recommended Action: > To facilitate providing registrants with the required Claims Notice information, ICANN org is requesting that $REGISTRY communicate with the registrar(s) of the impacted domain name(s). For your convenience, ICANN org has prepared messaging for you to use when communicating the issue to impacted registrars. It explains the issue and includes the necessary next steps for the registrar and registrant. > > Once the registrars have completed the needed actions, $REGISTRY can incorporate the resulting data into what would be the standard flow for reporting the registrations to the TMDB via the List of Registered Domain Names (LORDN) file, which will result in notification to the trademark holders/agents. ICANN org is requesting that $REGISTRY submit any LORDN files to the TMDB ninety (90) days from the date of this letter. > > To complete these actions within the requested time frame, the following sequence of activities should be completed: > > ? each respective registrar to be notified > ? the registrar will need to notify the respective registrant and send the Claims Notice > ? the registrant will have sixty (60) days to acknowledge or reject the Claims Notice and for the $REGISTRY to upload the LORDN files to the TMDB. > > Because the Claims Notice information will be dated after the registration, a warning message will be returned upon submission of the LORDN file to the TMDB, but the file will be processed successfully. > > ICANN org appreciates your assistance with this matter and is available to discuss these instructions or answer any questions about these recommended actions. > Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID Current UTC offset: +3.00 (.Moscow) From rubensk at nic.br Wed Feb 19 19:15:15 2020 From: rubensk at nic.br (Rubens Kuhl) Date: Wed, 19 Feb 2020 16:15:15 -0300 Subject: [gnso-rds-pdp-wg] #12 RPMs In-Reply-To: References: Message-ID: BTW, arguing with GDD that IBM should be manually uploading Claims ACKs to TMDB instead of registries went nowhere. ICANN opted to place work on the hands of parties that did nothing wrong. I hope IBM got a permanent block on ICANN RFPs after that. Rubens > Em 19 de fev de 2020, ?(s) 16:09:000, Maxim Alzoba escreveu: > > Dates of the issues with TMCH: > Cases can be requested via ICANN GDD (IBM has own case system) > > 1. between 02SEP2019 and 26AUG2019 > some LORDN files were not uploading to TMDB > answer from IBM > " > We are not sure why you got such errors. It seems to us that the data sent did not reach our servers properly. > " > > 2. between 23 August 2018 and 26 September 2018. > Text of the notification > >> Earlier this year, ICANN org was alerted to a configuration issue within the Trademark Database (TMDB). Based on research by the TMDB?s administrator, IBM, this issue was introduced to the TMDB on 23 August 2018 and affected a limited number of gTLDs that were in the Claims Period between 23 August 2018 and 26 September 2018. This issue may have resulted in registrars not displaying the required Claims Notice to the then potential registrant and the registry of the affected gTLDs not reporting the registration to the TMDB. >> >> By receiving this communication, ICANN org has identified $REGISTRY as having TLD(s) with domain name registration(s) that have been impacted by the issue. The impacted domain name(s) are listed in the attached .csv file. >> >> Recommended Action: >> To facilitate providing registrants with the required Claims Notice information, ICANN org is requesting that $REGISTRY communicate with the registrar(s) of the impacted domain name(s). For your convenience, ICANN org has prepared messaging for you to use when communicating the issue to impacted registrars. It explains the issue and includes the necessary next steps for the registrar and registrant. >> >> Once the registrars have completed the needed actions, $REGISTRY can incorporate the resulting data into what would be the standard flow for reporting the registrations to the TMDB via the List of Registered Domain Names (LORDN) file, which will result in notification to the trademark holders/agents. ICANN org is requesting that $REGISTRY submit any LORDN files to the TMDB ninety (90) days from the date of this letter. >> >> To complete these actions within the requested time frame, the following sequence of activities should be completed: >> >> ? each respective registrar to be notified >> ? the registrar will need to notify the respective registrant and send the Claims Notice >> ? the registrant will have sixty (60) days to acknowledge or reject the Claims Notice and for the $REGISTRY to upload the LORDN files to the TMDB. >> >> Because the Claims Notice information will be dated after the registration, a warning message will be returned upon submission of the LORDN file to the TMDB, but the file will be processed successfully. >> >> ICANN org appreciates your assistance with this matter and is available to discuss these instructions or answer any questions about these recommended actions. >> > > > > Sincerely Yours, > > Maxim Alzoba > Special projects manager, > International Relations Department, > FAITID > > Current UTC offset: +3.00 (.Moscow) > > _______________________________________________ > gnso-rds-pdp-wg mailing list > gnso-rds-pdp-wg at icann.org > https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg > _______________________________________________ > 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 528 bytes Desc: Message signed with OpenPGP URL: