[CPWG] Circleid - Universal acceptance issues

[David Mackey]

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 at 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 at icann.org> wrote:
>
>
>
> https://circleid.com/posts/20231014-universal-acceptance-issues-with-.tube-ascii-and-idn-domains
>
> _______________________________________________
> CPWG mailing list
> CPWG at 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 at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/cpwg/attachments/20231023/537199a5/attachment.html>