Not sure I see a technical problem here. It's a "is it worth the effort" problem, a market problem as David describes. Of course Meta wants a LOT from ICANN so perhaps a swap could be arranged? Jonathan Zuck Director, Future of Work Project Innovators Network Foundation www.InnovatorsNetwork.org ________________________________ From: CPWG <cpwg-bounces@icann.org> on behalf of Bill Jouris via CPWG <cpwg@icann.org> Sent: Monday, October 23, 2023 8:00:22 PM To: David Mackey <mackey361@gmail.com> Cc: CPWG <cpwg@icann.org> Subject: Re: [CPWG] Circleid - Universal acceptance issues Perhaps someone more knowledgeable than I knows which IETF group would be dealing with this. It might be a good idea to contact them, just to find out if they have something already in process. If not, it seems like our next step should be to lay out a clear statement of what (technical) problem we would like IETF to devise a solution for, and what we feel the desired characteristics of the solution are. Bill Jouris On Monday, October 23, 2023 at 08:58:51 AM PDT, David Mackey via CPWG <cpwg@icann.org> wrote: Hi Maureen, I agree with Hadia, thanks for sharing. I think it's a good idea to be concerned about how policy is implemented in the real world and not just policy creation in an ivory tower vacuum. ICANN policy implementation depends on both the development and vendor communities to bring policy to the real world. I don't think it's wise for us to expect vendors to change their business models in order for us to achieve our policy goals. However, if we understand vendor business models and the market dynamics that ensue, we can make sure to tailor our policy work to align with a speedy deployment environment. This statement from the article pops out to me ... "First, while IANA maintains a canonical list of TLDs, there is no RFC nor any guidance from ICANN as to clear best practices for the use of such a list in software applications". Standardization is often a useful tool to reduce deployment friction, and therefore, make it easier to fit policy into any vendor's business model. Can someone confirm that deployment of the Universal Acceptance policy would benefit by new/modified IETF Standards relating to the DNS system? If yes, then it would be good for the At-Large community to encourage IETF standards development work in this direction. If not, we may have no other choice than to accept the gap between policy development (ICANN) and market based rollout timelines (Meta, Google, Apple, etc) exists. In the meantime, we should continue to lobby the vendor community to help them understand how our Universal Acceptance policy development aligns with their business model objective to develop new markets. Just a thought. Cheers, David On Thu, Oct 19, 2023 at 5:56 AM Hadia El Miniawi via CPWG <cpwg@icann.org<mailto:cpwg@icann.org>> wrote: Thanks Maureen for sharing Hadia On Tuesday, October 17, 2023 at 10:40:15 AM GMT+3, Maureen Hilyard via CPWG <cpwg@icann.org<mailto:cpwg@icann.org>> wrote: https://circleid.com/posts/20231014-universal-acceptance-issues-with-.tube-a... _______________________________________________ CPWG mailing list CPWG@icann.org<mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ 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. _______________________________________________ CPWG mailing list CPWG@icann.org<mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ 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. _______________________________________________ CPWG mailing list CPWG@icann.org<mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ 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.