Updated reporting specification, per IRT feedback
Dear Colleagues, Attached is an updated version of the reporting specification. To summarize the changes that were made: 1. We updated the report frequency to quarterly (initial proposal was monthly) 2. We eliminated the per-TLD report requirement 3. We eliminated a few of the unnecessary fields (e.g., publication requests for IP and LEA, some of the "total" fields at the top) 4. We added a couple of fields for "other" requests (non-LEA or IP) We have considered the IRT's feedback on use of RRI. ICANN org believes that the use of RRI is preferable for both ICANN org and providers, as opposed to accepting emailed forms because: * The only difference on the provider side is using an API (the report format will be the same, and ICANN is providing a template to create the CSV file that will be submitted via the API); * Using the API will allow real-time confirmation that the report format is valid, eliminating the need for manual communications back and forth between ICANN org and the provider * ICANN org will provide training materials for using the API for providers who are unfamiliar with the process. If you have any further feedback on this, please send it to the list. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins@icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>
Hi Amy, you say using when RRI, the only difference is using an API. I would counter that by saying that the use of RRI requires an API for an otherwise totally manual process. As provider, we would make our report by gathering data in a spreadsheet and copying that into an email, there is no need for any implementation. While ICANN org believes an API would be preferable, this is not the case for providers, who again derive no benefit from this decision but face implementation costs that could otherwise be avoided. Please reconsider using this IRT as an opportunity to drive up provider costs. Best, Volker Am 26.03.2018 um 16:56 schrieb Amy Bivins:
Dear Colleagues,
Attached is an updated version of the reporting specification. To summarize the changes that were made:
1. We updated the report frequency to quarterly (initial proposal was monthly) 2. We eliminated the per-TLD report requirement 3. We eliminated a few of the unnecessary fields (e.g., publication requests for IP and LEA, some of the “total” fields at the top) 4. We added a couple of fields for “other” requests (non-LEA or IP)
We have considered the IRT’s feedback on use of RRI. ICANN org believes that the use of RRI is preferable for both ICANN org and providers, as opposed to accepting emailed forms because:
* The only difference on the provider side is using an API (the report format will be the same, and ICANN is providing a template to create the CSV file that will be submitted via the API); * Using the API will allow real-time confirmation that the report format is valid, eliminating the need for manual communications back and forth between ICANN org and the provider * ICANN org will provide training materials for using the API for providers who are unfamiliar with the process.
If you have any further feedback on this, please send it to the list.
Best,
Amy
*Amy E. Bivins*
Registrar Services and Engagement Senior Manager
Registrar Services and Industry Relations
Internet Corporation for Assigned Names and Numbers (ICANN)
Direct: +1 (202) 249-7551
Fax: +1 (202) 789-0104
Email: amy.bivins@icann.org <mailto:amy.bivins@icann.org>
www.icann.org <http://www.icann.org>
_______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl
-- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
participants (2)
-
Amy Bivins -
Volker Greimann