Re: Meeting Agenda | GNSO Council Informal Meeting [C] | Tuesday, 11 June 2024 13:45 - 15:00 CAT (75 mins) | Room: MH 2 (GNSO)
Hi Everyone: I have some input on the third item. There isn’t remote participation for the call but hope a brief writing will be beneficial. I think the Board has the issue right: that the time to respond to emergency requests should be measured in minutes or hours but time for source verification and validating the issue is genuine will often push that out to a period of days. Since the contract obligation has to be sort of a “lowest common denominator,” it is not possible to generate a meaningful contractual requirement. The Board agrees that an effective cannot be written. Instead, we should concentrate on continual improvement measures: how do registries respond in their own jurisdiction, how verification tools can be developed, what jurisdictions might become “trusted.” Things like that. Without doubt, all contracted parties want to help In life threatening situation. What measures can be taken to facilitate that? Can there be a Policy without a corresponding contractual requirement? I think that is possible. A Policy to encourage, work on, and report on progress in this area would be an approach, including ICANN devoting certain resources towards it. That’s all I have. Thanks for listening. Kurt On 11 Jun 2024, at 7:14 pm, Terri Agnew via Ntfy-gnso-council <ntfy-gnso-council@icann.org<mailto:ntfy-gnso-council@icann.org>> wrote: Hello, This email has been sent to the closed council mailing list which does not allow response back. Here is the agenda for today’s GNSO Council Informal Meeting [C] (reminder - no remote, no zoom available) 13:45 – 15:00 CAT in room MH 2 (GNSO). Agenda: 1. Discuss voting items and determine if there are any questions or concerns (aspirational statement on the consent agenda & expiration items) 2. Potential next steps for the IPC RfR, including the identification of any further SG/C planned actions 3. Letter from ICANN Board - urgent requests 4. SG/C priorities that might NOT be on the ADR? Thank you. Kind regards, Terri Policy Team Supporting the GNSO _______________________________________________ Ntfy-gnso-council mailing list -- ntfy-gnso-council@icann.org<mailto:ntfy-gnso-council@icann.org> To unsubscribe send an email to ntfy-gnso-council-leave@icann.org<mailto:ntfy-gnso-council-leave@icann.org> _______________________________________________ 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.
participants (1)
-
kurt kjpritz.com