Dear Colleagues,
Thanks so much for your active participation on today’s Privacy/Proxy IRT call. If you were unable to attend, I encourage you to listen to the recording because we covered a lot of ground today. The recording is available on the wiki,
https://participate.icann.org/p6bxagpwaq9/
IRT Action Items
(1)
Please submit any additional feedback you have on the draft v1 applicant guide (attached) by Friday. We will be discussing again and there will be more opportunities for discussion, but the more feedback we have now the better,
as we will use the feedback received this week in drafting v2. A summary of your feedback received to date on the applicant guide is attached. I am also attaching the results of the IRT survey of initial operational questions that you completed back in February—this
came up briefly on today’s call. I apologize that I over-stated the point referenced today on the call—I said that the majority of the IRT said in the poll that the existence of a PP Provider application and/or the contents of an application for accreditation
should not be made public. This is true—there was a slight majority of the IRT for this point on each of the questions, but it was a very close result for both questions and the number of participants was relatively low for this poll.
(2)
Please submit your feedback on the RDDS labeling proposals discussed on today’s call no later than Friday. For those not on the call, the Registrar Subteam has developed two possible solutions to implementing the recommendation
that registrations involving privacy and/or proxy services should be clearly labeled as such in WHOIS. The first solution would be to (a) require that the privacy/proxy service provider name and ICANN ID appear in the registrant name and/or the registrant
organization field (the “or” is to accommodate privacy services where the customer’s name appears in the Registrant Name field--this was discussed further on the call). The second solution was (b) require that the privacy/proxy service provider’s name, ICANN
ID and a URL to the ICANN webpage listing of all accredited providers and contact information.
The IRT was roughly split on these proposals. Some IRT members saw an added benefit to the URL (which would provide an easily-identifiable source of Provider contact information that may not be visible in WHOIS), while others
thought the URL was unnecessary and could complicate automated uses of the label. If no clear consensus is reached on the list on the path forward on this one, we will take this to a poll.
(3)
Please submit any additional feedback you have regarding the “unaffiliated provider” issue raised by the registrar subteam today on the call. In summary, members of the registrar subteam have suggested that certain operational issues
may make the accreditation of providers that are not affiliated with a registrar highly undesirable or impossible.
There have been challenges noted by IRT members and staff throughout this IRT related to unaffiliated providers (particularly in the area of de-accreditation). However, as noted on the call, the Final Report does clearly reference
unaffiliated providers, which seems to indicate an intent that unaffiliated providers should be permitted to become accredited. As a result, any potential question/action that would limit eligibility for accreditation by providers that are not affiliated with
a registrar would likely need to be taken to the GNSO Council for guidance. At this stage, we are hoping to gather as much IRT input as possible on this so that we can determine how best to proceed. Please send your feedback to the list on this topic this
week. As any changes on this point would have a substantial impact on the overall implementation of this program, any action on this should be taken as soon as practicable.
Thanks so much for your attention to these matters. Please don’t hesitate to contact me or write to the list directly if you have additional comments or questions.
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